Communication method and apparatus

Abstract

The present application provides a communication method and apparatus. The method is applied to a first functional entity comprising N first data processing functional modules for implementing N first data processing functions. The method comprises: receiving first data, different first data corresponding to different data processing modes, and the data processing modes comprising executing M1 first data processing functions, and / or skipping M2 first data processing functions; processing the first data on the basis of a data processing mode corresponding to the first data; or, sending the first data. In the present application, on the basis of a data processing mode corresponding to the data, a corresponding functional entity executes a corresponding data processing function, and / or skips the corresponding data processing function. Therefore, the first functional entity can meet data processing requirements of different communication scenarios.

Description

Communication method and apparatus

[0001] The present application claims priority from the Chinese patent application No. 202411017684.6 filed on July 27, 2024, and entitled "Communication method and apparatus", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] Embodiments of the present application relate to the field of wireless communication, in particular to a communication method and apparatus. BACKGROUND

[0003] In the current communication system, the functions of a base station can be split to obtain multiple function entities. Different function entities are used to implement different communication protocol functions in the base station. For example, the base station is split into a baseband unit (BBU) and a remote radio unit (RRU) for deployment. Or, the base station is split into a central unit (CU) and a distributed unit (DU) for deployment. The CU can also be referred to as a centralized unit.

[0004] For different function entities, different communication protocol function modules can be deployed. However, currently, fixed communication protocol function modules are usually configured on different function entities. For different communication protocol function division modes between different function entities, the applicable communication scenarios are usually different, which means that different communication scenarios have different requirements. However, the fixed communication protocol function modules on the function entities cannot meet the multiple requirements of different communication scenarios. SUMMARY

[0005] The present application provides a communication method and apparatus. By deploying partially same function modules on different function entities, the function entities execute or skip part of the function modules according to different communication scenarios to which the data is applicable, so as to meet the different data processing requirements of different communication scenarios for the function entities.

[0006] To achieve the above object, the present application adopts the following technical solutions:

[0007] In a first aspect, a communication method is provided. The method is applied to a first function entity. The first function entity can be a network device, a component (e.g., a processor, a circuit, a chip, or a chip system) of the network device, or a logic module or software that can implement all or part of the function of the network device. For ease of description, the following description is given by way of example of being performed by a network device. The first function entity includes N first data processing function modules. N is a positive integer. The first data processing function modules can be used to implement first data processing functions. The method can include receiving first data. Different first data corresponds to different data processing manners. For example, the data processing manners include performing M1 first data processing functions and / or skipping M2 first data processing functions. The sum of M1 and M2 is equal to N. The M1 first data processing functions performed by different data processing manners are partially the same or completely different, and the M2 first data processing functions skipped by different data processing manners are partially the same or completely different. The first data is processed according to the data processing manner corresponding to the first data. Alternatively, the first data is transmitted.

[0008] In the present application, different data can be associated with different data processing manners. The corresponding function entity can perform corresponding data processing functions and / or skip corresponding data processing functions based on the data processing manner corresponding to the data, to complete the processing of the data. The first function entity can meet the data processing requirements of different communication scenarios.

[0009] In a possible design, the first data carries a first identifier. Different first data corresponds to different data processing manners, which can include that different first data corresponding to different first identifiers corresponds to different data processing manners.

[0010] The present application can distinguish the first data applicable to different communication scenarios by the first identifier, to improve the accuracy of processing the first data by the first function entity.

[0011] In a possible design, the method can further include at least one of the following steps: generating first information. The first information can be used to indicate the association between the first identifier and the data processing scenario, and / or the association between the first identifier and the data processing manner. Different data processing scenarios are associated with different data processing manners. The first information is transmitted. Alternatively, the first information is received.

[0012] The present application provides multiple ways to obtain the first information, so that the first function entity can quickly and accurately obtain the first information in different scenarios by selecting a suitable way.

[0013] In a possible design, the data processing scenario can include at least one of the following scenarios: a scenario supporting large-scale multiple-input multiple-output (MIMO) and a bandwidth greater than a first threshold; a dynamic spectrum sharing (DSS) signal processing scenario; an artificial intelligence for radio access network (AI4RAN) scenario; an uplink (UL) coordinated multiple points (CoMP) signal processing scenario; a downlink (DL) CoMP signal processing scenario; a duplex signal processing scenario; or, a sensing signal processing scenario.

[0014] The present application can be applicable to a plurality of different data processing scenarios, and can meet data processing requirements of the functional entity on data in different data processing scenarios.

[0015] In a possible design, the first identifier can include a first identifier of a first type and / or a first identifier of a second type. The first identifier of the first type can be used to indicate one in-phase quadrature (IQ) data message. The first identifier of the second type can be used to indicate a group of IQ data messages, and the group of IQ data messages includes a plurality of IQ data messages.

[0016] In the present application, the first identifier can be indicated based on each IQ data signal or a group of IQ data signals, so as to select a suitable manner to indicate the first identifier in different scenarios, and improve communication efficiency.

[0017] In a possible design, the first identifier can include at least one of the following: an identifier of the functional entity, where the functional entity includes the first functional entity; an identifier of a cell; an identifier of a terminal; an identifier of a service flow; or, an identifier of a radio resource.

[0018] The present application provides a plurality of possible forms of the first identifier, and can use a suitable first identifier to indicate the first data in different scenarios, so as to meet data processing requirements of the functional entity on different communication scenarios.

[0019] In a possible design, the identifier of the functional entity can include at least one of the following: an identifier of a central unit (CU); an identifier of a distributed unit (DU); or, an identifier of a radio unit (RU).

[0020] The application provides a plurality of possible function entity identifications to indicate the first data based on different function entities in a suitable scenario, so as to meet the data processing requirements of data for different function entities in different communication scenarios.

[0021] In a possible design, the identification of the service flow can include at least one of the following: identification of a data radio bearer (DRB); identification of a protocol data unit (PDU) session; identification of quality of service (QoS); or, identification of a data packet.

[0022] The application provides a plurality of possible service flow identifications to indicate the first data based on different service flows in a suitable scenario, so as to meet the data processing requirements of data for different service flows in different communication scenarios.

[0023] In a possible design, the identification of the wireless resource can include at least one of the following: identification of a physical channel; identification of an antenna port; identification of a symbol; identification of a time slot; identification of a frame; identification of a subframe; identification of a beam; or, identification of a frequency domain resource.

[0024] The application provides a plurality of possible wireless resource identifications to indicate the first data based on different wireless resources in a suitable scenario, so as to meet the data processing requirements of data for different wireless resources in different communication scenarios.

[0025] In a possible design, the first identification is used to indicate that the first data has been processed by M1 first data processing functions, and / or the first identification is used to indicate that the first data needs to be processed by M2 first data processing functions.

[0026] The application can indicate which function processing the first data has been processed and / or needs to be processed by sending the first data carrying the first identification. So that the device receiving the data performs corresponding function processing on the first data, so as to meet the data processing requirements of function entities in different communication scenarios.

[0027] In a possible design, the first data processing function module can include at least one of the following: a function module for uplink data processing; a function module for downlink data processing; a function module for generating downlink precoding parameters for a single user; a function module for generating downlink precoding parameters for a single user based on artificial intelligence (AI); a function module for generating downlink precoding parameters for multiple users; a function module for generating downlink precoding parameters for multiple users based on AI; a function of generating downlink precoding parameters based on uplink reference signal measurement; a function of generating downlink precoding parameters based on AI and uplink reference signal measurement; or, a function module for processing sensing data.

[0028] The present application provides a plurality of communication protocol function modules that can be deployed by the first function entity, so that the first function entity can more flexibly select to perform appropriate functions for different data to meet the data processing requirements of data in different communication scenarios.

[0029] In a possible design, the function module for uplink data processing can include at least one of the following: a resource element (RE) demapping function module; a first channel estimation function module, the channel estimation result obtained by the first channel estimation function module being used for uplink signal combination; a function module for implementing uplink signal combination; a second channel estimation function module, the channel estimation result obtained by the second channel estimation function module being used for signal equalization; an AI-based second channel estimation function module; an equalization function module; or, an AI-based equalization function module.

[0030] The present application provides a plurality of communication protocol function modules that can be involved in uplink communication scenarios to meet the data processing requirements of different uplink data of the function entity.

[0031] In a possible design, the function module for downlink data processing includes at least one of the following: a modulation function module; a layer mapping function module; or, a precoding function module.

[0032] The present application provides a plurality of communication protocol function modules that can be involved in downlink communication scenarios to meet the data processing requirements of different downlink data of the function entity.

[0033] In a possible design, the function module for processing sensing data includes at least one of the following: a sensing least square (LS) function module for the frequency domain; a sensing LS function module for the time domain; or, a sensing range-velocity-angle (RVA) spectrum estimation function module.

[0034] The application provides a plurality of communication protocol function modules possibly involved in a perception communication scenario, to meet data processing requirements of a function entity for different perception data.

[0035] In a possible design, the first identifier is further used to indicate that the first data is perception symbol data or communication symbol data.

[0036] In the application, different types of the first data are indicated by the first identifier, so that the function entity selects appropriate communication protocol functions based on the perception symbol data and the communication symbol data, to meet data processing requirements of data in different communication scenarios.

[0037] In a second aspect, a communication method is provided, which is applied to a first function entity. The first function entity can be a network device, a component (for example, a processor, a circuit, a chip, or a chip system) of the network device, or a logic module or software capable of implementing all or part of the function of the network device. For ease of description, the following is described by taking the network device as an example. The first function entity is used to implement a first physical layer protocol function. The method can include: receiving first data from a second function entity. The second function entity is used to implement a second physical layer protocol function. The first physical layer protocol function and the second physical layer protocol function constitute a complete physical layer protocol function. That is, the physical layer protocol function can be divided into two parts and deployed on the first function entity and the second function entity respectively. It can also be considered that the communication protocol function division manner between the first function entity and the second function entity is a division within the physical layer. According to the data type of the first data, a target data processing manner corresponding to the data type is used to process the first data. Alternatively, according to the second physical layer protocol function, a target data processing manner is used to process the first data. Different second physical layer protocol functions correspond to different target data processing manners. The target data processing manner mentioned above can include executing one or more first physical layer protocol functions and / or skipping one or more first physical layer protocol functions. The one or more first physical layer protocol functions executed by different target data processing manners are partially the same or completely different, and the one or more first physical layer protocol functions skipped by different target data processing manners are partially the same or completely different.

[0038] The application processes different data by using appropriate data processing manners according to the data type or the physical layer protocol function possessed by the second function entity. In a scenario where the division of the physical layer protocol functions of the first function entity and the second function entity is relatively fixed, the data processing requirements of the function entity for data in different communication scenarios are met.

[0039] In a possible design, the manner of physical layer protocol function division between the first physical layer protocol function and the second physical layer protocol function can include at least one of the following: division between scrambling function and modulation function; division between a second channel estimation function and a function for implementing uplink signal combination, where a channel estimation result obtained through the second channel estimation function is used for signal equalization; division between equalization function and inverse discrete fourier transform (IDFT) function; or, division between the second channel estimation function and the equalization function.

[0040] The present application can be applicable to communication scenarios corresponding to various manners of function division, and improve universality.

[0041] In a possible design, the second function entity can include at least one of the following entities: a second target entity having uplink signal combination function and second channel estimation function; a second target entity having uplink signal combination function, second channel estimation function and equalization function; or, a second target entity having uplink signal combination function.

[0042] The present application provides various physical layer protocol functions that the second function entity can have, and can adapt to corresponding second function entities in different communication scenarios, and can meet data processing requirements of the function entity on data in different communication scenarios.

[0043] In a possible design, the second function entity has uplink signal combination function, second channel estimation function and equalization function, and the target data processing manner can include skipping the second channel estimation function and the equalization function.

[0044] The present application avoids the first data from performing repeated second channel estimation function and equalization function, and improves data processing accuracy. Moreover, the present application can meet data processing requirements of the first function entity on data in different communication scenarios.

[0045] In a possible design, the data type of the first data includes perceptual symbol data type, and the target data processing manner can include performing at least one of the following first physical layer protocol functions: perceptual LS function for frequency domain; perceptual LS function for time domain; or, perceptual RVA spectrum estimation function.

[0046] In a possible design, the second function entity has uplink signal combination function, and the data type of the first data can include perceptual symbol data type. The data processing function of the second target entity can include skipping the uplink signal combination function.

[0047] The second functional entity of the present application can also process data of different data types in a suitable manner, thereby meeting the data processing requirements of the second functional entity in different communication scenarios.

[0048] In a possible design, the first data is downlink data, and the first physical layer protocol function and / or the second physical layer protocol function includes at least one of the following functions: a function for generating downlink precoding parameters for a single user; a function for generating downlink precoding parameters for multiple users; or a function for generating downlink precoding parameters based on uplink reference signal measurement.

[0049] The present application can be applied to a scenario where the SU-BF function, the MU-BF function and the SRS-BF function are deployed in different functional entities, thereby meeting the data processing requirements of the functional entities in different communication scenarios.

[0050] In a third aspect, a communication apparatus is provided, which can be deployed with a first functional entity, such as a network device, or a communication module in the network device, or a chip responsible for communication functions in the network device, such as a modem chip (also known as a baseband chip), or a system on chip (SoC) or a system in package (SIP) chip containing a modem module. It can also be a logical module or software that can implement all or part of the functions of the network device. For ease of description, the following describes an example of being executed by a network device. The first functional entity includes N first data processing function modules. N is a positive integer. The first data processing function modules can be used to implement first data processing functions. The first data processing function modules include: a transceiver, configured to receive first data. Different data processing manners are different for different first data. For example, the data processing manners include performing M1 first data processing functions and / or skipping M2 first data processing functions. M1 and M2 are equal to N. The M1 first data processing functions performed by different data processing manners are partially the same or completely different, and the M2 first data processing functions skipped by different data processing manners are partially the same or completely different. A processing unit is configured to process the first data according to the data processing manner corresponding to the first data. Alternatively, the transceiver is configured to transmit the first data.

[0051] In a possible design, the first data carries a first identifier. Different data processing manners are different for different first data, which can include that different data processing manners are different for first data of different first identifiers.

[0052] In a possible design, the processing unit is further configured to generate the first information. The first information can be used to indicate an association between the first identifier and a data processing scenario, and / or an association between the first identifier and a data processing manner. Different data processing manners are associated with different data processing scenarios. The transceiver is further configured to send the first information. Alternatively, the transceiver is further configured to receive the first information.

[0053] In a possible design, the data processing scenario can include at least one of the following scenarios: a scenario supporting massive MIMO and a bandwidth greater than a first threshold; a DSS signal processing scenario; an AI4RAN scenario; an UL CoMP signal processing scenario; a DL CoMP signal processing scenario; a duplex signal processing scenario; or a sensing signal processing scenario.

[0054] In a possible design, the first identifier can include a first-type first identifier and / or a second-type first identifier. The first-type first identifier can be used to indicate one IQ data message. The second-type first identifier can be used to indicate a group of IQ data messages, and the group of IQ data messages includes a plurality of IQ data messages.

[0055] In a possible design, the first identifier can include at least one of the following: an identifier of a functional entity, where the functional entity includes a first functional entity; an identifier of a cell; an identifier of a terminal; an identifier of a service flow; or an identifier of a radio resource.

[0056] In a possible design, the identifier of the functional entity can include at least one of the following: an identifier of a CU; an identifier of a DU; or an identifier of an RU.

[0057] In a possible design, the identifier of the service flow can include at least one of the following: an identifier of a DRB; an identifier of a PDU session; an identifier of QoS; or an identifier of a data packet.

[0058] In a possible design, the identifier of the radio resource can include at least one of the following: an identifier of a physical channel; an identifier of an antenna port; an identifier of a symbol; an identifier of a time slot; an identifier of a frame; an identifier of a subframe; an identifier of a beam; or an identifier of a frequency domain resource.

[0059] In a possible design, the first identifier is used to indicate that the first data is processed by M1 first data processing functions, and / or the first identifier is used to indicate that the first data needs to be processed by M2 first data processing functions.

[0060] In a possible design, the first data processing function module can include at least one of the following: a function module for uplink data processing; a function module for downlink data processing; a function module for generating downlink precoding parameters for a single user; a function module for generating downlink precoding parameters for a single user based on AI; a function module for generating downlink precoding parameters for multiple users; a function module for generating downlink precoding parameters for multiple users based on AI; a function of generating downlink precoding parameters based on uplink reference signal measurement; a function of generating downlink precoding parameters based on AI and uplink reference signal measurement; or, a function module for processing sensing data.

[0061] In a possible design, the function module for uplink data processing can include at least one of the following: an RE demapping function module; a first channel estimation function module, a channel estimation result obtained by the first channel estimation function module being used for uplink signal combination; a function module for implementing uplink signal combination; a second channel estimation function module, a channel estimation result obtained by the second channel estimation function module being used for signal equalization; an AI-based second channel estimation function module; an equalization function module; or, an AI-based equalization function module.

[0062] In a possible design, the function module for downlink data processing includes at least one of the following: a modulation function module; a layer mapping function module; or, a precoding function module.

[0063] In a possible design, the function module for processing sensing data includes at least one of the following: a sensing LS function module for a frequency domain; a sensing LS function module for a time domain; or, a sensing RVA spectrum estimation function module.

[0064] In a possible design, the first identifier is further used to indicate that the first data is sensing symbol data or communication symbol data.

[0065] In a fourth aspect, a communication apparatus is provided, which can be deployed with a first functional entity, such as a network device, or a communication module in the network device, or a chip responsible for communication function in the network device, such as a modem chip (also referred to as a baseband chip), or a SoC or SIP chip containing a modem module. It can also be a logic module or software capable of implementing all or part of the functions of the network device. For ease of description, the following is described by way of example of being executed by a network device. The first functional entity is configured to implement a first physical layer protocol function. It includes: a transceiver configured to receive first data from a second functional entity. The second functional entity is configured to implement a second physical layer protocol function. The first physical layer protocol function and the second physical layer protocol function constitute a complete physical layer protocol function. A processing unit is configured to process the first data by using a target data processing manner corresponding to a data type of the first data. Alternatively, the processing unit is configured to process the first data by using a target data processing manner according to the second physical layer protocol function. Different second physical layer protocol functions correspond to different target data processing manners. The target data processing manner mentioned above can include executing one or more first physical layer protocol functions, and / or skipping one or more first physical layer protocol functions. The one or more first physical layer protocol functions executed by different target data processing manners are partially the same or completely different, and the one or more first physical layer protocol functions skipped by different target data processing manners are partially the same or completely different.

[0066] In a possible design, the division of the physical layer protocol function between the first physical layer protocol function and the second physical layer protocol function can include at least one of the following: division between a scrambling function and a modulation function; division between a second channel estimation function and a function for implementing uplink signal combination, wherein a channel estimation result obtained by the second channel estimation function is used for signal equalization; division between an equalization function and an IDFT function; or, division between the second channel estimation function and the equalization function.

[0067] In a possible design, the second functional entity can include at least one of the following entities: a second target entity having a function of uplink signal combination and a second channel estimation function; a second target entity having a function of uplink signal combination, a second channel estimation function and an equalization function; or, a second target entity having a function of uplink signal combination.

[0068] In a possible design, the second functional entity has a function of uplink signal combination, a second channel estimation function and an equalization function, and the target data processing manner can include skipping the second channel estimation function and the equalization function.

[0069] In a possible design, the data type of the first data includes a sensing symbol data type, and the target data processing manner can include performing at least one of the following first physical layer protocol functions: a sensing LS function for a frequency domain; a sensing LS function for a time domain; or a sensing RVA spectrum estimation function.

[0070] In a possible design, the second function entity has an uplink signal combining function, and the data type of the first data can include a sensing symbol data type. The data processing function of the second target entity can include a function of skipping the uplink signal combining.

[0071] In a possible design, the first data is downlink data, and the first physical layer protocol function and / or the second physical layer protocol function includes at least one of the following functions: a function for generating downlink precoding parameters for a single user; a function for generating downlink precoding parameters for multiple users; or a function of generating downlink precoding parameters based on uplink reference signal measurement.

[0072] In a fifth aspect, a communication apparatus is provided, which can be deployed with a first function entity, such as a network device, or a communication module in the network device, or a chip responsible for communication functions in the network device, such as a modem chip (also referred to as a baseband chip) or a SoC or SIP chip containing a modem module. It can also be a logic module or software capable of implementing all or part of the functions of the network device. For ease of description, the following is described by way of example of being executed by the network device. The first function entity includes N first data processing function modules. N is a positive integer. The first data processing function modules can be used to implement first data processing functions. The first data processing function modules include: a transceiver, configured to receive first data. Different data processing manners correspond to different first data. For example, the data processing manner includes performing M1 first data processing functions and / or skipping M2 first data processing functions. M1 and M2 are equal to N. The M1 first data processing functions performed by different data processing manners are partially the same or completely different, and the M2 first data processing functions skipped by different data processing manners are partially the same or completely different. A processor, configured to process the first data according to the data processing manner corresponding to the first data. Alternatively, the transceiver is configured to send the first data.

[0073] In a possible design, the first data carries a first identifier. Different data processing manners correspond to different first data, which can include that different data processing manners correspond to different first identifiers.

[0074] In a possible design, the processor is further configured to generate the first information. The first information can be used to indicate an association between the first identifier and a data processing scenario, and / or an association between the first identifier and a data processing manner. Different data processing manners are associated with different data processing scenarios. The transceiver is further configured to send the first information. Or, the transceiver is further configured to receive the first information.

[0075] In a possible design, the data processing scenario can include at least one of the following scenarios: a scenario supporting massive MIMO and a bandwidth greater than a first threshold; a DSS signal processing scenario; an AI4RAN scenario; an UL CoMP signal processing scenario; a DL CoMP signal processing scenario; a duplex signal processing scenario; or, a sensing signal processing scenario.

[0076] In a possible design, the first identifier can include a first-type first identifier and / or a second-type first identifier. The first-type first identifier can be used to indicate one IQ data message. The second-type first identifier can be used to indicate a group of IQ data messages, and the group of IQ data messages includes a plurality of IQ data messages.

[0077] In a possible design, the first identifier can include at least one of the following: an identifier of a functional entity, where the functional entity includes a first functional entity; an identifier of a cell; an identifier of a terminal; an identifier of a service flow; or, an identifier of a radio resource.

[0078] In a possible design, the identifier of the functional entity can include at least one of the following: an identifier of a CU; an identifier of a DU; or, an identifier of an RU.

[0079] In a possible design, the identifier of the service flow can include at least one of the following: an identifier of a DRB; an identifier of a PDU session; an identifier of QoS; or, an identifier of a data packet.

[0080] In a possible design, the identifier of the radio resource can include at least one of the following: an identifier of a physical channel; an identifier of an antenna port; an identifier of a symbol; an identifier of a time slot; an identifier of a frame; an identifier of a subframe; an identifier of a beam; or, an identifier of a frequency domain resource.

[0081] In a possible design, the first identifier is used to indicate that first data is processed by M1 first data processing functions, and / or the first identifier is used to indicate that the first data needs to be processed by M2 first data processing functions.

[0082] In a possible design, the first data processing function module can include at least one of the following: a function module for uplink data processing; a function module for downlink data processing; a function module for generating downlink precoding parameters for a single user; a function module for generating downlink precoding parameters for a single user based on AI; a function module for generating downlink precoding parameters for multiple users; a function module for generating downlink precoding parameters for multiple users based on AI; a function of generating downlink precoding parameters based on uplink reference signal measurement; a function of generating downlink precoding parameters based on AI and uplink reference signal measurement; or, a function module for processing sensing data.

[0083] In a possible design, the function module for uplink data processing can include at least one of the following: an RE demapping function module; a first channel estimation function module, a channel estimation result obtained by the first channel estimation function module being used for uplink signal combination; a function module for implementing uplink signal combination; a second channel estimation function module, a channel estimation result obtained by the second channel estimation function module being used for signal equalization; an AI-based second channel estimation function module; an equalization function module; or, an AI-based equalization function module.

[0084] In a possible design, the function module for downlink data processing includes at least one of the following: a modulation function module; a layer mapping function module; or, a precoding function module.

[0085] In a possible design, the function module for processing sensing data includes at least one of the following: a sensing LS function module for a frequency domain; a sensing LS function module for a time domain; or, a sensing RVA spectrum estimation function module.

[0086] In a possible design, the first identifier is further used to indicate that the first data is sensing symbol data or communication symbol data.

[0087] In a sixth aspect, a communication apparatus is provided, which can be deployed with a first functional entity, such as a network device, or a communication module in the network device, or a chip responsible for communication function in the network device, such as a modem chip (also referred to as a baseband chip), or a SoC or SIP chip containing a modem module. It can also be a logic module or software capable of implementing all or part of the functions of the network device. For ease of description, the following is described by way of example of being executed by a network device. The first functional entity is configured to implement a first physical layer protocol function. It includes: a transceiver configured to receive first data from a second functional entity. The second functional entity is configured to implement a second physical layer protocol function. The first physical layer protocol function and the second physical layer protocol function constitute a complete physical layer protocol function. A processor is configured to process the first data by using a target data processing manner corresponding to a data type of the first data. Alternatively, the processor is configured to process the first data by using a target data processing manner according to the second physical layer protocol function. Different second physical layer protocol functions correspond to different target data processing manners. The target data processing manner mentioned above can include executing one or more first physical layer protocol functions, and / or skipping one or more first physical layer protocol functions. The one or more first physical layer protocol functions executed by different target data processing manners are partially the same or completely different, and the one or more first physical layer protocol functions skipped by different target data processing manners are partially the same or completely different.

[0088] In a possible design, the division of the physical layer protocol function between the first physical layer protocol function and the second physical layer protocol function can include at least one of the following: division between a scrambling function and a modulation function; division between a second channel estimation function and a function for implementing uplink signal combination, wherein a channel estimation result obtained by the second channel estimation function is used for signal equalization; division between an equalization function and an IDFT function; or, division between the second channel estimation function and the equalization function.

[0089] In a possible design, the second functional entity can include at least one of the following entities: a second target entity having a function of uplink signal combination and a second channel estimation function; a second target entity having a function of uplink signal combination, a second channel estimation function and an equalization function; or, a second target entity having a function of uplink signal combination.

[0090] In a possible design, the second functional entity has a function of uplink signal combination, a second channel estimation function and an equalization function, and the target data processing manner can include skipping the second channel estimation function and the equalization function.

[0091] In a possible design, the data type of the first data includes a sensing symbol data type, and the target data processing manner can include performing at least one of the following first physical layer protocol functions: a sensing LS function for a frequency domain; a sensing LS function for a time domain; or, a sensing RVA spectrum estimation function.

[0092] In a possible design, the second function entity has an uplink signal combining function, and the data type of the first data can include a sensing symbol data type. The data processing function of the second target entity can include a function of skipping the uplink signal combining.

[0093] In a possible design, the first data is downlink data, and the first physical layer protocol function and / or the second physical layer protocol function includes at least one of the following functions: a function for generating a downlink precoding parameter for a single user; a function for generating a downlink precoding parameter for multiple users; or, a function of generating a downlink precoding parameter based on uplink reference signal measurement.

[0094] In a seventh aspect, a communication system is provided, which includes a first function entity and a second function entity. The first function entity includes N first data processing function modules. N is a positive integer. The first data processing function modules are configured to implement a first data processing function. The system includes: the second function entity is configured to send first data to the first function entity. Different first data correspond to different data processing manners. The data processing manner can include executing M1 first data processing functions, and / or skipping M2 first data processing functions. The sum of M1 and M2 is equal to N. The M1 first data processing functions executed by different data processing manners are partially the same or completely different, and the M2 first data processing functions skipped by different data processing manners are partially the same or completely different. The first function entity is configured to process the first data according to the data processing manner corresponding to the first data. Alternatively, the first function entity is configured to send the first data to the second function entity.

[0095] In a possible design, the first data carries a first identifier. Different first data correspond to different data processing manners, which can include that first data with different first identifiers correspond to different data processing manners.

[0096] In a possible design, the first function entity is further configured to generate first information. The first information can be used to indicate an association relationship between the first identifier and a data processing scenario, and / or an association relationship between the first identifier and a data processing manner. Different data processing scenarios are associated with different data processing manners. The first function entity is further configured to send the first information to the second function entity. Alternatively, the second function entity is further configured to send the first information to the first function entity.

[0097] In a possible design, the data processing scenario can include at least one of the following scenarios: a scenario supporting massive MIMO and a bandwidth greater than a first threshold; a DSS signal processing scenario; an AI4RAN scenario; an UL CoMP signal processing scenario; a DL CoMP signal processing scenario; a duplex signal processing scenario; or a sensing signal processing scenario.

[0098] In a possible design, the first identifier can include a first-type first identifier and / or a second-type first identifier. The first-type first identifier can be used to indicate one IQ data message. The second-type first identifier can be used to indicate a group of IQ data messages, and the group of IQ data messages includes multiple IQ data messages.

[0099] In a possible design, the first identifier can include at least one of the following: an identifier of a function entity, where the function entity includes the first function entity; an identifier of a cell; an identifier of a terminal; an identifier of a service flow; or an identifier of a radio resource.

[0100] In a possible design, the identifier of the function entity can include at least one of the following: an identifier of a CU; an identifier of a DU; or an identifier of an RU.

[0101] In a possible design, the identifier of the service flow can include at least one of the following: an identifier of a DRB; an identifier of a PDU session; an identifier of QoS; or an identifier of a data packet.

[0102] In a possible design, the identifier of the radio resource can include at least one of the following: an identifier of a physical channel; an identifier of an antenna port; an identifier of a symbol; an identifier of a time slot; an identifier of a frame; an identifier of a subframe; an identifier of a beam; or an identifier of a frequency domain resource.

[0103] In a possible design, the first identifier is used to indicate that the first data is processed by M1 first data processing functions, and / or the first identifier is used to indicate that the first data needs to be processed by M2 first data processing functions.

[0104] In a possible design, the first data processing function module can include at least one of the following: a function module for uplink data processing; a function module for downlink data processing; a function module for generating downlink precoding parameters for a single user; a function module for generating downlink precoding parameters for a single user based on AI; a function module for generating downlink precoding parameters for multiple users; a function module for generating downlink precoding parameters for multiple users based on AI; a function of generating downlink precoding parameters based on uplink reference signal measurement; a function of generating downlink precoding parameters based on AI and uplink reference signal measurement; or a function module for processing sensing data.

[0105] In a possible design, the functional modules for uplink data processing can include at least one of the following: a RE demapping functional module; a first channel estimation functional module, a channel estimation result obtained by the first channel estimation functional module being used for uplink signal combining; a functional module for implementing uplink signal combining; a second channel estimation functional module, a channel estimation result obtained by the second channel estimation functional module being used for signal equalization; an AI-based second channel estimation functional module; an equalization functional module; or an AI-based equalization functional module.

[0106] In a possible design, the functional modules for downlink data processing include at least one of the following: a modulation functional module; a layer mapping functional module; or a precoding functional module.

[0107] In a possible design, the functional modules for processing sensing data include at least one of the following: a sensing LS functional module for a frequency domain; a sensing LS functional module for a time domain; or a sensing RVA spectrum estimation functional module.

[0108] In a possible design, the first identifier is further used to indicate that the first data is sensing symbol data or communication symbol data.

[0109] In an eighth aspect, a communication system is provided, and the system includes a first functional entity and a second functional entity. The first functional entity is configured to implement a first physical layer protocol function, and the second functional entity is configured to implement a second physical layer protocol function. The first physical layer protocol function and the second physical layer protocol function constitute a complete physical layer protocol function. The system includes: the second functional entity is further configured to send first data to the first functional entity. The first functional entity is further configured to process the first data by using a target data processing manner corresponding to a data type of the first data, or the first functional entity is further configured to process the first data by using the target data processing manner according to the second physical layer protocol function. Different second physical layer protocol functions correspond to different target data processing manners. The target data processing manner includes executing one or more first physical layer protocol functions and / or skipping one or more first physical layer protocol functions. The one or more first physical layer protocol functions executed by different target data processing manners are partially the same or completely different, and the one or more first physical layer protocol functions skipped by different target data processing manners are partially the same or completely different.

[0110] In a possible design, the physical layer protocol function division manner between the first physical layer protocol function and the second physical layer protocol function can include at least one of the following: division between scrambling function and modulation function; division between second channel estimation function and function for implementing uplink signal combination, where a channel estimation result obtained through the second channel estimation function is used for signal equalization; division between equalization function and IDFT function; or, division between the second channel estimation function and the equalization function.

[0111] In a possible design, the second function entity can include at least one of the following entities: a second target entity with the uplink signal combination function and the second channel estimation function; a second target entity with the uplink signal combination function, the second channel estimation function and the equalization function; or, a second target entity with the uplink signal combination function.

[0112] In a possible design, the second function entity has the uplink signal combination function, the second channel estimation function and the equalization function, and the target data processing manner can include skipping the second channel estimation function and the equalization function.

[0113] In a possible design, the data type of the first data includes a perception symbol data type, and the target data processing manner can include performing at least one of the following first physical layer protocol functions: a perception LS function for a frequency domain; a perception LS function for a time domain; or, a perception RVA spectrum estimation function.

[0114] In a possible design, the second function entity has the uplink signal combination function, and the data type of the first data can include a perception symbol data type. The data processing function of the second target entity can include skipping the uplink signal combination function.

[0115] In a possible design, the first data is downlink data, and the first physical layer protocol function and / or the second physical layer protocol function includes at least one of the following functions: a function for generating downlink precoding parameters for a single user; a function for generating downlink precoding parameters for multiple users; or, a function for generating downlink precoding parameters based on uplink reference signal measurement.

[0116] In a ninth aspect, a communication system is provided, the system comprising a first network device and a second network device. The first network device comprises N first data processing function modules. N is a positive integer. The first data processing function modules are configured to implement first data processing functions. The system comprises: the second network device is configured to send first data to the first network device. Different first data correspond to different data processing manners. The data processing manners can comprise executing M1 first data processing functions and / or skipping M2 first data processing functions. The sum of M1 and M2 is equal to N. The M1 first data processing functions executed by different data processing manners are partially the same or completely different, and the M2 first data processing functions skipped by different data processing manners are partially the same or completely different. The first network device is configured to process the first data according to the data processing manner corresponding to the first data. Alternatively, the first network device is configured to send the first data to the second network device.

[0117] In a possible design, the first data carries a first identifier. Different first data correspond to different data processing manners, which can comprise: first data of different first identifiers correspond to different data processing manners.

[0118] In a possible design, the first network device is further configured to generate first information. The first information can be used to indicate an association relationship between the first identifier and a data processing scenario, and / or an association relationship between the first identifier and a data processing manner. Different data processing scenarios are associated with different data processing manners. The first network device is further configured to send the first information to the second network device. Alternatively, the second network device is further configured to send the first information to the first network device.

[0119] In a possible design, the data processing scenario can comprise at least one of the following scenarios: a scenario supporting large-scale MIMO and a bandwidth greater than a first threshold; a DSS signal processing scenario; an AI4RAN scenario; an UL CoMP signal processing scenario; a DL CoMP signal processing scenario; a duplex signal processing scenario; or a sensing signal processing scenario.

[0120] In a possible design, the first identifier can comprise a first type of first identifier and / or a second type of first identifier. The first type of first identifier can be used to indicate one IQ data message. The second type of first identifier can be used to indicate a group of IQ data messages, and the group of IQ data messages comprises a plurality of IQ data messages.

[0121] In a possible design, the first identifier can comprise at least one of the following: an identifier of a function entity, wherein the function entity comprises the first network device; an identifier of a cell; an identifier of a terminal; an identifier of a service flow; or an identifier of a radio resource.

[0122] In a possible design, the identifier of the function entity can include at least one of the following: an identifier of the CU; an identifier of the DU; or, an identifier of the RU.

[0123] In a possible design, the identifier of the service flow can include at least one of the following: an identifier of the DRB; an identifier of the PDU session; an identifier of the QoS; or, an identifier of the data packet.

[0124] In a possible design, the identifier of the radio resource can include at least one of the following: an identifier of a physical channel; an identifier of an antenna port; an identifier of a symbol; an identifier of a time slot; an identifier of a frame; an identifier of a subframe; an identifier of a beam; or, an identifier of a frequency domain resource.

[0125] In a possible design, the first identifier is used to indicate that the first data needs to be processed by M1 first data processing functions, and / or the first identifier is used to indicate that the first data needs to be processed by M2 first data processing functions.

[0126] In a possible design, the first data processing function module can include at least one of the following: a function module for uplink data processing; a function module for downlink data processing; a function module for generating downlink precoding parameters for a single user; a function module for generating downlink precoding parameters for a single user based on AI; a function module for generating downlink precoding parameters for multiple users; a function module for generating downlink precoding parameters for multiple users based on AI; a function of generating downlink precoding parameters based on uplink reference signal measurement; a function of generating downlink precoding parameters based on AI and uplink reference signal measurement; or, a function module for processing sensing data.

[0127] In a possible design, the function module for uplink data processing can include at least one of the following: a RE demapping function module; a first channel estimation function module, a channel estimation result obtained by the first channel estimation function module being used for uplink signal combination; a function module for implementing uplink signal combination; a second channel estimation function module, a channel estimation result obtained by the second channel estimation function module being used for signal equalization; an AI-based second channel estimation function module; an equalization function module; or, an AI-based equalization function module.

[0128] In a possible design, the function module for downlink data processing includes at least one of the following: a modulation function module; a layer mapping function module; or, a precoding function module.

[0129] In a possible design, the function module for processing sensing data includes at least one of the following: a sensing LS function module for a frequency domain; a sensing LS function module for a time domain; or, a sensing RVA spectrum estimation function module.

[0130] In a possible design, the first identifier is further used to indicate that the first data is the sensing symbol data or the communication symbol data.

[0131] In a tenth aspect, a communication system is provided, which includes a first network device and a second network device. The first network device is configured to implement a first physical layer protocol function, and the second network device is configured to implement a second physical layer protocol function. The first physical layer protocol function and the second physical layer protocol function constitute a complete physical layer protocol function. The system includes that the second network device is further configured to send first data to the first network device. The first network device is further configured to process the first data by using a target data processing manner corresponding to a data type of the first data, or the first network device is further configured to process the first data by using the target data processing manner according to the second physical layer protocol function. Different second physical layer protocol functions correspond to different target data processing manners. The target data processing manner includes performing one or more first physical layer protocol functions and / or skipping one or more first physical layer protocol functions. The one or more first physical layer protocol functions performed by different target data processing manners are partially same or completely different, and the one or more first physical layer protocol functions skipped by different target data processing manners are partially same or completely different.

[0132] In a possible design, the physical layer protocol function division manner between the first physical layer protocol function and the second physical layer protocol function can include at least one of the following: division between a scrambling function and a modulation function; division between a second channel estimation function and a function for implementing uplink signal combination, where a channel estimation result obtained by the second channel estimation function is used for signal equalization; division between an equalization function and an IDFT function; or division between the second channel estimation function and the equalization function.

[0133] In a possible design, the second network device can include at least one of the following entities: a second target entity having a function for uplink signal combination and a second channel estimation function; a second target entity having a function for uplink signal combination, a second channel estimation function and an equalization function; or a second target entity having a function for uplink signal combination.

[0134] In a possible design, the second network device has a function for uplink signal combination, a second channel estimation function and an equalization function, and the target data processing manner can include skipping the second channel estimation function and the equalization function.

[0135] In a possible design, the data type of the first data includes a sensing symbol data type, and the target data processing manner can include performing at least one of the following first physical layer protocol functions: a sensing LS function for a frequency domain; a sensing LS function for a time domain; or a sensing RVA spectrum estimation function.

[0136] In a possible design, the second network device has an uplink signal combination function, and the data type of the first data can include a sensing symbol data type. The data processing function of the second target entity can include a function of skipping the uplink signal combination.

[0137] In a possible design, the first data is downlink data, and the first physical layer protocol function and / or the second physical layer protocol function includes at least one of the following functions: a function of generating a downlink precoding parameter for a single user; a function of generating a downlink precoding parameter for multiple users; or a function of generating a downlink precoding parameter based on uplink reference signal measurement.

[0138] In an eleventh aspect, a chip is provided, which includes an interface circuit and one or more processors. The one or more processors are coupled with a memory. The memory is configured to store part or all of a computer program or instructions necessary for implementing the functions of the first aspect and the second aspect. The one or more processors can execute the computer program or instructions, and when the computer program or instructions are executed, cause the communication apparatus to implement the method in any possible design or implementation manner of the first aspect and the second aspect. The interface circuit is configured to implement a communication function within the communication apparatus and / or a communication function of the communication apparatus with other apparatuses or components.

[0139] In a twelfth aspect, a computer readable storage medium is provided. The computer readable storage medium stores computer instructions; when the computer instructions are run on a computer, cause the computer to execute the communication method in any design of any aspect.

[0140] In a thirteenth aspect, a computer program product is provided. The computer program product includes computer programs or instructions, and when the computer programs or instructions are run on a computer, cause the computer to execute the communication method in any design of any aspect.

[0141] The method in any of the second aspect to the thirteenth aspect has the beneficial effects corresponding to the methods in the first aspect, which are not repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0142] FIG. 1 is a schematic diagram of an architecture of a communication system to which embodiments of the present application are applied;

[0143] Figure 2 is a schematic diagram of a communication protocol function split between a BBU and a RRU according to an embodiment of the present application;

[0144] Figure 3 is a schematic diagram of a radio access network architecture according to an embodiment of the present application;

[0145] Figure 4 is a schematic diagram of another radio access network architecture according to an embodiment of the present application;

[0146] Figure 5 is a schematic diagram of an access network device function split according to an embodiment of the present application;

[0147] Figure 6 is a schematic diagram of a communication protocol function split according to an embodiment of the present application;

[0148] Figure 7 is a schematic diagram of another communication protocol function split according to an embodiment of the present application;

[0149] Figure 8 is a schematic diagram of yet another communication protocol function split according to an embodiment of the present application;

[0150] Figure 9 is a schematic diagram of a physical layer function split for downlink according to an embodiment of the present application;

[0151] Figure 10 is a schematic diagram of a physical layer function split for uplink according to an embodiment of the present application;

[0152] Figure 11 is a schematic diagram of a communication scenario according to an embodiment of the present application;

[0153] Figure 12 is a schematic diagram of a communication method according to an embodiment of the present application;

[0154] Figure 13 is a schematic diagram of another communication method according to an embodiment of the present application;

[0155] Figure 14 is a schematic diagram of a downlink communication architecture according to an embodiment of the present application;

[0156] Figure 15 is a schematic diagram of an uplink communication architecture according to an embodiment of the present application;

[0157] Figure 16 is a schematic diagram of yet another communication method according to an embodiment of the present application;

[0158] Figure 17 is a schematic diagram of another downlink communication architecture according to an embodiment of the present application;

[0159] Figure 18 is a schematic diagram of another uplink communication architecture according to an embodiment of the present application;

[0160] Figure 19 is a schematic diagram of another communication scenario according to an embodiment of the present application;

[0161] Figure 20 is a schematic diagram of yet another downlink communication architecture according to an embodiment of the present application;

[0162] FIG. 21 is a schematic diagram of another communication method provided by an embodiment of the application;

[0163] FIG. 22 is a schematic diagram of a communication apparatus provided by an embodiment of the application;

[0164] FIG. 23 is a schematic diagram of another communication apparatus provided by an embodiment of the application. DETAILED DESCRIPTION

[0165] FIG. 1 is a schematic diagram of an architecture of a communication system 1000 provided by an embodiment of the application. As shown in FIG. 1, the communication system 1000 includes a radio access network (RAN) 100, wherein the RAN 100 includes at least one RAN node (e.g., 110a and 110b in FIG. 1, collectively referred to as 110), and can further include at least one terminal (e.g., 120a-120j in FIG. 1, collectively referred to as 120). The RAN 100 can further include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in FIG. 1). The terminals 120 are connected to the RAN nodes 110 in a wireless manner. Terminals and terminals, and RAN nodes and RAN nodes can be connected to each other in a wired or wireless manner. The communication system 1000 can further include a core network 200. The RAN nodes 110 are connected to the core network 200 in a wireless or wired manner. The core network devices in the core network 200 and the RAN nodes 110 in the RAN 100 can be independent and different physical devices, or can be the same physical device integrated with the logical functions of the core network devices and the logical functions of the RAN nodes. The communication system 1000 can further include the Internet 300.

[0166] The RAN 100 can be an evolved universal terrestrial radio access (E-UTRA) system, a new radio (NR) system, a future communication network, and a future wireless access system defined in the 3rd generation partnership project (3GPP). The RAN 100 can further include two or more different wireless access systems described above. The RAN 100 can also be an open RAN (O-RAN).

[0167] A RAN node, also referred to as a radio access network device, a RAN entity, or an access node, is configured to help a terminal to access a communication system through wireless means. In one application scenario, the RAN node can be a base station (BS), an evolved Node B (eNodeB / eNB), a transmission reception point (TRP), a generation NodeB (gNB) in a 5th generation (5G) mobile communication system, a future base station in a future communication network, or a base station in a future mobile communication system. The RAN node can be a macro base station (e.g., 110a in FIG. 1), a micro base station or an indoor station (e.g., 110b in FIG. 1), a relay node, or a donor node.

[0168] In another application scenario, a terminal can access a communication system through wireless means with the help of cooperation among a plurality of RAN nodes, each of which implements part of functionalities of a base station. For example, the RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). The RU can also be referred to as a radio frequency unit. The CU here implements functionalities of a radio resource control protocol and a packet data convergence protocol (PDCP) of a base station, and can further implement functionalities of a service data adaptation protocol (SDAP). The DU implements functionalities of a radio link control layer and a medium access control (MAC) layer of a base station, and can further implement functionalities of part of a physical layer or the whole physical layer. Details of the protocol layers described above can be referred to relevant technical specifications of the 3GPP. The RU can be configured to implement functions of transmitting and receiving radio frequency signals. The CU and the DU can be two independent RAN nodes, or can be integrated in the same RAN node, for example, in a baseband unit (BBU). The RU can be included in a radio frequency device, for example, in a remote radio unit (RRU) or an active antenna unit (AAU). The CU can be further divided into two types of RAN nodes, i.e., a CU-control plane and a CU-user plane.

[0169] The RAN node can have different names in different systems, for example, in an open radio access network (O-RAN) system, the CU can be referred to as an open CU (O-CU), the DU can be referred to as an open DU (O-DU), and the RU can be referred to as an open RU (O-RU). The RAN node in the embodiments of the present application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module. For example, the RAN node can be a server loaded with a corresponding software module. The embodiments of the present application do not limit the specific technology and specific device form of the RAN node. For ease of description, a base station is described as an example of the RAN node in the following.

[0170] A terminal is a device with wireless transceiving function, which can send a signal to a base station or receive a signal from a base station. The terminal can also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. The terminal can be widely applied in various scenarios, such as device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), internet of things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, remote medical treatment, smart power grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiving function, wearable device, vehicle, airplane, ship, robot, mechanical arm, smart home device, etc. The embodiments of the present application do not limit the specific technology and specific device form of the terminal.

[0171] In some examples, the core network 200 can include an access and mobility management function (AMF) entity, a session management function (SMF) entity, a user plane function (UPF) entity, a sensing service control function (SSCF), a sensing data processing function (SDPF), a unified data management (UDM), etc. any core network device.

[0172] The base station and the terminal can be fixed in position or mobile. The base station and the terminal can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on water; can also be deployed on an airplane, balloon and artificial satellite. Embodiments of the present application do not limit the application scenarios of the base station and the terminal.

[0173] The roles of the base station and the terminal can be relative, for example, the helicopter or the unmanned aerial vehicle 120i in FIG. 1 can be configured as a mobile base station, and for those terminals 120j that access the wireless access network 100 through 120i, the terminal 120i is a base station; but for the base station 110a, 120i is a terminal, that is, 110a and 120i communicate with each other through a wireless air interface protocol. Of course, 110a and 120i can also communicate with each other through a base station-to-base station interface protocol, and in this case, 120i is also a base station relative to 110a. Therefore, the base station and the terminal can be collectively referred to as a communication device, 110a and 110b in FIG. 1 can be referred to as a communication device with a base station function, and 120a-120j in FIG. 1 can be referred to as a communication device with a terminal function.

[0174] The base station and the terminal, the base station and the base station, and the terminal and the terminal can communicate through a licensed frequency spectrum, or through an unlicensed frequency spectrum, or through both the licensed frequency spectrum and the unlicensed frequency spectrum; can communicate through a frequency spectrum below 6 gigahertz (GHz), or through a frequency spectrum above 6 GHz, or through both the frequency spectrum below 6 GHz and the frequency spectrum above 6 GHz. Embodiments of the present application do not limit the frequency spectrum resources used for wireless communication.

[0175] In embodiments of the present application, the functions of the base station can also be performed by a module (such as a chip) in the base station, or by a control subsystem containing base station functions. The control subsystem containing base station functions herein can be a control center in the above-mentioned application scenarios such as smart grid, industrial control, intelligent transportation and smart city. The functions of the terminal can also be performed by a module (such as a chip or a modem) in the terminal, or by a device containing terminal functions.

[0176] In a wireless communication system, communication devices can utilize air interface resources for wireless communication. The communication devices can include network devices and terminal devices, and the network devices can also be referred to as base station devices, i.e., the wireless access network devices mentioned above. The air interface resources can include at least one of time domain resources, frequency domain resources, code resources and spatial resources. The communication devices can also be referred to as communication devices.

[0177] The scheme provided in the embodiments of the present application can be applied to wireless communication between communication devices. The wireless communication can include wireless communication between a network device and a terminal, wireless communication between network devices, and wireless communication between terminals. In the embodiments of the present application, the term "wireless communication" can also be referred to as "communication", and the term "communication" can also be described as "data transmission", "information transmission" or "transmission".

[0178] In a global system for mobile communications (GSM), wideband code division multiple access (WCDMA), universal mobile telecommunications system (UMTS), long term evolution (LTE) and a 5G system, a base station can be divided into two functional entities, BBU and RRU, for deployment in a bottom split manner. The bottom split manner can be a split manner of a physical layer and a radio frequency part. It can be understood that "split" and "divide" can be used interchangeably in the embodiments of the present application. The BBU is connected to one or more RRUs through optical fibers, metal wiring or microwave links. The BBU mainly completes the upper layer centralized processing of baseband signals. The RRU mainly completes the reception and transmission of baseband signals, as well as the functions of modulation and demodulation of radio frequency signals, data processing, power amplification and the like. The RRU is closer to the antenna and has smaller feeder loss. In some cases, the RRU can also be referred to as RU or AAU. The interface between the BBU and the RRU can be referred to as a front-haul interface or a bottom split interface.

[0179] Referring to FIG. 2, a schematic diagram of a communication protocol function division between a BBU and a RRU is shown. In the related art, an interface between a BBU and a RRU can use a common public radio interface (CPRI) protocol to communicate with each other. The CPRI protocol defines a key communication interface specification between a radio equipment control (REC) and a radio equipment (RE) in a wireless communication network. For example, the REC can be considered as the aforementioned BBU, and the radio equipment can be considered as the aforementioned RRU. As can be seen from FIG. 2, the CPRI interface divides radio frequency (RF) layer functions to the RRU 1, and divides physical (PHY) layer and above protocol layer functions to the BBU 1. The PHY layer can be further divided into a PHY high layer (High PHY) and a PHY low layer (Low PHY). The PHY layer above protocol layer functions can include a radio resource control (RRC) layer, an SDAP layer, a PDCP layer, a radio link control (RLC) layer, and a MAC layer.

[0180] Since the amount of data transmitted between the PHY layer of the BBU and the RF layer of the RRU is directly related to the size of the antenna array. The splitting manner specified in the CPRI protocol can cause the amount of data on the fronthaul interface to be too large, and cannot support a large-scale antenna array scenario. For example, assuming that a 9.8 gigabits per second (Gbps) optical fiber is used on the fronthaul interface of the CPRI protocol to carry 2 4 transmit and 4 receive (4T4R) antennas, and a cell with a wireless bandwidth of 20 megahertz (MHz). Then for a cell with 64 antennas and a bandwidth of 100 MHz, about 32 9.8 Gbps optical fibers need to be deployed on the CPRI interface.

[0181] In some scenarios, an evolution of the CPRI protocol is proposed, namely an enhanced CPRI protocol, denoted as eCPRI. Still referring to FIG. 2, the eCPRI protocol makes a finer division of the communication protocol of the wireless network, such as dividing the PHY layer into a PHY high layer and a PHY low layer. The PHY low layer is deployed in the RRU, and the PHY high layer is deployed into the BBU. And the interface specification between the BBU and the RRU, i.e., between the PHY high layer and the PHY low layer, is re-formulated. The eCPRI protocol converts the interface between the BBU and the RRU from the interface between the RF layer and the PHY layer as specified in the CPRI protocol into an interface between the PHY high layer and the PHY low layer, so that the original fiber communication between the RF layer and the PHY layer is converted into communication within a board or a field programmable gate array (FPGA) chip inside the RRU. And the data dimension of the communication between the PHY high layer of the BBU and the PHY low layer of the RRU is reduced, and is no longer directly related to the size of the antenna array on the RRU.

[0182] The splitting manner adopted by the above CPRI interface or eCPRI interface enables the BBU to process the baseband signal in a highly centralized manner, so that the computing resources can be deployed in a centralized manner, resulting in high resource utilization and low deployment cost. However, the above-mentioned CPRI interface or eCPRI interface has a large demand for the bandwidth of the fronthaul link, and the deployment cost of the optical fiber is high.

[0183] Referring to FIG. 3, a new RAN architecture that can be applied in future communication systems is proposed. In this architecture, the functions of the base station are re-divided into RU functions, radio network area (RNA) functions, and RNA automation functions. Among them, the RNA functions and the RU functions communicate through a low layer split (LLS) interface, and the RU functions and the terminals can establish a RAN-UE interface to communicate. The RNA functions and the core network (CN) can communicate through a RAN-CN interface. The RAN automation functions can manage the RU functions and the RNA functions through a network function (NF) management interface. The RAN automation functions can be controlled through network management. In this architecture, the RU functions can be regarded as the aforementioned RRU or AAU, and the RNA functions can be regarded as the aforementioned BBU.

[0184] In the related art, in order to reduce the pressure of the underlying split mode on the bandwidth of the fronthaul link and the deployment cost, 3GPP proposes a base station function division mode. For example, for gNB in 5G, a high layer split mode is adopted to split the base station into two function entities such as CU and DU. The midhaul link between CU and DU has lower network bandwidth demand, and the radio access network shown in FIG. 4 is divided into CU and DU. For example, the access network device can be a gNB, which can be composed of CU and DU. Of course, the DU can include one or more, which is not limited in the embodiments of the present application. The gNB and the core network element of the 5G core network (5G core network, 5GC) can communicate through the next generation interface (next generation, NG) interface. Different gNBs can communicate through the Xn interface, for example, through the Xn-control (control, C) interface. The CU and the different DUs can communicate through the F1 interface.

[0185] Among them, for the function split between CU and DU in the access network device, a static split mode is adopted, and fixed division is performed according to the protocol stack function granularity. As shown in FIG. 5, the RLC layer, the MAC layer and the PHY layer and the like protocol stack can be located in the DU of the access network device. Among them, the MAC layer can also be referred to as the medium access control, the medium access control, and the like, which is not limited in the embodiments of the present application. The RRC layer, the SDAP layer and the PDCP layer and the like protocol stack can be located in the CU of the access network device. Among them, RRC realizes air interface radio resource and air interface connection control, which belongs to the control plane (control plane, CP) protocol; SDAP performs mapping between quality of service flow (quality of service flow, QoS-flow) and data radio bearer (data radio bearer, DRB), which belongs to the user plane (user plane, UP) protocol. QoS-flow represents a service data flow with specific quality of service (quality of service, QoS) requirements.

[0186] As can be seen from FIG. 5, for the DU, the control plane protocol stack or the user plane protocol stack involves RLC, MAC and PHY. For the CU, PDCP is applicable to the control plane protocol stack and the user plane protocol stack, RRC corresponds to the control plane protocol stack, and SDAP corresponds to the user plane protocol stack. For performing the control plane protocol stack function, the CU and the DU can communicate through an F1-C interface; for performing the user plane protocol stack function, the CU and the DU can communicate through an F1-user (U) interface. On the basis of separation of the CU and the DU, the CU of the access network device can further be separated into a CP unit and a UP unit. The CP of the CU of the access network device can be denoted as gNB-CU-CP, and the UP of the CU of the access network device can be denoted as gNB-CU-UP. The PDCP layer protocol exists on both the gNB-CU-CP unit and the gNB-CU-UP unit, the RRC layer is located above the PDCP layer in the gNB-CU-CP unit, and the SDAP layer is located above the PDCP layer in the gNB-CU-UP unit.

[0187] The RLC layer can provide transparent data transmission and non-deterministic mode and deterministic mode data transmission. The MAC layer is mainly responsible for controlling the physical medium connected to the physical layer. The PHY layer is responsible for transmission of bits or bit groups on the physical medium, including encoding of transmitted information and decoding of received information.

[0188] FIG. 6 shows a plurality of possible communication protocol function division manners. The communication protocol function can be divided according to the protocol layer granularity. For example, a plurality of possible communication protocol function division manners such as option 1 to option 8 are provided. The option 1 can be communication function division between the RRC layer and the PDCP layer as shown in FIG. 6, or the option 1 can be communication function division between the SDAP layer and the PDCP layer as shown in FIG. 6. It can be understood that each of the subsequent embodiments of the present application takes the control plane RRC layer as an example for description, and for the user plane, the RRC layer can be replaced by the SDAP layer, and the embodiments of the present application will not be described again.

[0189] Option 2 can be a communication function split between the PDCP layer and the RLC high layer as shown in FIG. 6. Option 3 can be a communication function split between the RLC high layer and the RLC low layer as shown in FIG. 6. Thus, Option 3 can also be considered as a communication function split within the RLC layer. Option 4 can be a communication function split between the RLC low layer and the MAC high layer as shown in FIG. 6. Option 5 can be a communication function split between the MAC high layer and the MAC low layer as shown in FIG. 6. Thus, Option 5 can also be considered as a communication function split within the MAC layer. Option 6 can be a communication function split between the MAC low layer and the PHY high layer as shown in FIG. 6. Option 7 can be a communication function split between the PHY high layer and the PHY low layer as shown in FIG. 6. Thus, Option 7 can also be considered as a communication function split within the PHY layer. Option 8 can be a communication function split between the PHY low layer and the RF layer as shown in FIG. 6. This split of Option 8 is exactly the same as the split specified by the CPRI protocol.

[0190] It can be seen that the communication protocol function is divided more finely for the intra of some protocol layers. For example, the protocol layers such as the RLC layer, the MAC layer, and the PHY layer can be divided into high layers and low layers. Next, the PHY layer will be taken as an example to describe the communication protocol function division for the intra of the protocol layer, and the division manners of other protocol layers are similar, and the difference is that the communication protocol functions in the in tra of different protocol layers can be different, and the specific communication protocol functions can be referred to the corresponding protocol layer, and the embodiments of the present application are not limited here. Referring to FIG. 7, the communication function division for the intra of the PHY layer in the downlink (DL) communication is performed. It is assumed that the intra of the PHY layer can also be divided into coding, rate mapping, scrambling, modulation, layer mapping, precoding, resource element (RE) mapping, digital beam forming (DBF), inverse fast fourier transformation (IFFT) / addition cyclic prefix (CP), digital to analog, analog beamforming, RF, and the like. Among them, the resource element can be a unit wireless resource composed of one subcarrier and one symbol. Then, for the division manner of the option 7, the option 7-1, the option 7-2, the option 7-2a, and the option 7-3, and the like can be further included. Among them, the resource element can also be referred to as a resource unit.

[0191] For the modulation function involved in the embodiments of the present application, it can also be referred to as constellation modulation function, and the embodiments of the present application are not limited here.

[0192] It is worth noting that the English abbreviations of the radio device and the resource element can both be RE, and therefore, in order to distinguish the radio device and the resource element, in the embodiments of the present application, the RE can refer to the resource element, and the radio device is not described by using the abbreviation.

[0193] In the analog beamforming module shown in FIG. 7, the phase of the digital signal on the antenna can be adjusted by the phase shifter in the analog domain, so as to generate a beam in a specific direction. It can be considered that all antennas process the same signal. In some scenarios, the digital beamforming and precoding in FIG. 7 can be the same module, so the digital beamforming can also be called precoding. Precoding is to adjust the phase and amplitude of the baseband signal of different data streams, so that the transmission signal on the antenna is different, and multiple beams with different directions and power intensities can be generated more flexibly. Thus, the spatial diversity or spatial multiplexing can be effectively utilized. Beamforming is a signal processing technology for directional transmission and reception of signals using an antenna array. By adjusting the basic unit and phase parameters of the antenna array, the signals at certain angles are in phase interference, and the signals at other angles are in destructive interference, that is, only the target signal is aligned with the target receiving device.

[0194] For example, referring to FIG. 7, option 7-1 can be a communication protocol function division between IFFT / add CP and DBF. Option 7-2 can be a communication protocol function division between precoding and layer mapping. Option 7-2a can be a communication protocol function division between DBF and RE mapping. Option 7-3 can be a communication protocol function division between modulation and scrambling. Among them, option 7-2a can also be called category A, and option 7-2 can also be called category B. For option 7-3, it can also be considered to be the same as the splitting mode of the eCPRI protocol for downlink. Option 7-3 can also be called interface e (Ie) for downlink, Ie splitting for downlink, Ie2 for downlink, Ie2 splitting for downlink, and the like. For FIG. 7, if the communication protocol function division is performed between IFFT / add CP and digital-to-analog, it corresponds to the aforementioned option 8, that is, the splitting mode of the CPRI protocol.

[0195] Referring to FIG. 8, the communication function division within the PHY layer is divided for uplink (UL) communication. It is assumed that the PHY layer can also be divided into de-coding, rate de-mapping, de-scrambling, de-modulation, channel estimation, equalization, RE de-mapping, DBF, fast fourier transformation (FFT) / CP removal, analog to digital, analog beamforming, RF, and the like. Then, for the option 7 split mode, option 7-1', option 7-2', option 7-2a', and option 7-3' and the like can also be included. Wherein, the de-modulation can also be referred to as demodulation.

[0196] For example, referring to FIG. 8, the option 7-1' can be a communication protocol function division between FFT / CP removal and DBF. The option 7-2' can be a communication protocol function division between RE de-mapping and channel estimation. The option 7-2a' can be a communication protocol function division between DBF and RE de-mapping. The option 7-3' can be a communication protocol function division between de-modulation and de-scrambling. Wherein, the option 7-2' can also be referred to as Ie', Ie for uplink, Ie split for uplink, and the like. The option 7-2' can be considered to be the same as the eCPRI protocol split mode for uplink. In some examples, if the communication protocol function division is between equalization and de-modulation, the split point can be referred to as uplink performance improvement (ULPI)-A, Ie2 for uplink, Ie2 split for uplink, NG-LLS, and the like. If the communication protocol function division is between channel estimation and equalization, the split point can be referred to as ULPI-B. It is worth noting that the channel estimation mentioned in the embodiments of the present application can be considered to be channel estimation using a demodulation reference signal (DMRS) signal.

[0197] The Ie and Ie2 can be considered to be an uplink / downlink asymmetric split mode. Of course, for the split mode within the MAC and RLC, the PHY internal split mode can be referred to. The communication functions involved in each protocol layer and the specific functions to be divided together can be determined according to the actual situation, and the embodiments of the present application do not limit this.

[0198] Generally, a fixed splitting manner can be adopted to deploy the communication protocol functions on each entity. For example, the splitting points of the communication protocol functions can be set according to prior statistical information, such as network peak rate, average data rate requirement, etc., before deployment, and the deployment of the functional entities is performed according to the splitting manner. After deployment, the communication protocol functions on each entity remain unchanged. For example, the splitting manners of the aforementioned CPRI, eCPRI, etc., or the splitting manners mentioned in the aforementioned options 1 to 8, etc.

[0199] In some communication systems, a sounding reference signal-based beamforing (SRS-BF) module, a single-user beamforing (SU-BF) module and / or a multi-user beamforing (MU-BF) module can also be deployed on the BBU. The SU-BF module can be used to generate weight coefficients of a single-user signal for providing to a precoding module for use in precoding the signal; the MU-BF module can be used to generate weight coefficients of a multi-user signal for providing to a precoding module for use in precoding the signal.

[0200] A sounding reference signal (SRS) is a kind of reference signal sent by a terminal to a base station, which is used to measure an uplink channel state. The base station can measure the SRS signal to obtain an SRS measurement report. The SRS measurement report can include a precoding matrix indication (PMI) for uplink, a channel quality indicator (CQI) for uplink and a rank indication (RI) for uplink. The base station can send the PMI to the UE for beamforing of the uplink. Alternatively, for a time division duplex (TDD) scenario, the base station can input the SRS measurement report to the SU-BF module or the MU-BF module by means of reciprocity between the uplink channel and the downlink channel, so that the SU-BF module or the MU-BF module generates weight coefficients for downlink precoding.

[0201] Similar to SRS is channel state information reference signal (CSI-RS), which is a reference signal sent by a base station to a terminal for measuring a downlink channel state. The terminal measures the CSI-RS to obtain a CSI-RS measurement report, or channel state information (CSI). The CSI can include a PMI for downlink, a CQI for downlink, and an RI for downlink. The terminal reports the CSI to the base station, so that the base station inputs the CSI into a SU-BF module or a MU-BF module to generate a weight coefficient for downlink precoding.

[0202] In the process of uplink or downlink communication of the UE and the base station, the DMRS can also be sent together with the data signal. So that the receiving end demodulates the uplink data signal or the downlink data signal, such as performing channel estimation and equalization on the data signal. The receiving end usually performs channel estimation according to the reception result of the DMRS signal and the pilot sequence carried by the DMRS signal.

[0203] In some examples, the base station can determine to deploy certain functional modules on a certain functional entity according to the QoS requirements (such as experience rate) of the services of different users, the service load state between different functional entities, the computing power state, the traffic state of the interface, etc.

[0204] Referring to FIG. 9, the communication protocol functional modules in the physical layer for downlink are similar to those shown in FIG. 7. The difference is that the digital beamforming and precoding in FIG. 9 are regarded as the same module. For the scenario of downlink communication, the functional modules such as modulation, layer mapping, and precoding can be flexibly selected to be deployed on a certain functional entity, such as being deployed on the functional entity 2 or being deployed on the functional entity 1'. The remaining communication protocol functional modules of the physical layer are respectively deployed on the functional entity 1 and the functional entity 2, or are respectively deployed on the functional entity 1' and the functional entity 2', according to the order of data processing. For example, in the case that the traffic load of the front-end interface is relatively high, the deployment according to the functional entity 1 and the functional entity 2 can be considered. To reduce the total traffic of the front-end interface. It can be understood that the interface between the functional entity 1 and the functional entity 2 is the front-end interface. For another example, if the load or functional complexity of the functional entity 2 is considered to be high, the deployment according to the functional entity 1' and the functional entity 2' can be considered. Compared with the functional entity 2, the load and functional complexity of the functional entity 2' are reduced, but the total traffic on the front-end interface is increased. It can be understood that the interface between the functional entity 1' and the functional entity 2' is also the front-end interface.

[0205] Referring to FIG. 10, the communication protocol function modules in the physical layer for the uplink are similar to those shown in FIG. 8. The difference is that between the channel estimation and demodulation, there is an inverse discrete fourier transform (IDFT) module, which is mainly used to convert the signal from the frequency domain to the time domain. For the uplink symbol or the terminal with poor uplink air interface transmission rate, the channel estimation module and / or the equalization module can be deployed on a higher layer function entity, such as function entity 3. This deployment mode can obtain the multiplexing gain and diversity gain brought by the cooperative processing of the uplink signal, and improve the uplink coverage and uplink transmission rate. For example, the function entity 3 can combine the possible user signals and channel information of other function entities 4 to make more accurate uplink channel estimation and signal equalization for the target UE. For example, the interference channel and the interference signal component are filtered to improve the reception quality of the base station. For another example, the channel estimation module and / or the equalization module can also be deployed on a lower layer function entity, such as function entity 4. In this way, the traffic of the front-haul interface will be lower, reducing the bandwidth requirement of the front-haul interface and the complexity of signal processing.

[0206] For the uplink communication scenario, the data transmitted by the front-haul interface can also be data for sensing, which can be referred to as sensing data. The signal for sensing can be referred to as sensing signal. For example, the terminal or network device can send the sensing signal for sensing, and the device receiving the sensing signal can determine the corresponding sensing data based on the measurement result of the sensing signal. The sensing data is different from the ordinary data for communication in the uplink communication process. For example, the sensing data needs to be processed by the sensing least square (LS) function module and the sensing range-velocity-angle (RVA) spectrum estimation function module. The equalization function module and the modulation function module are no longer needed. The sensing LS function module can also be referred to as a sensing channel estimation function module. The sensing RVA spectrum estimation function module can also be deployed and executed in the core network element.

[0207] For different communication scenarios, the requirements of each communication scenario for each functional module to perform corresponding communication protocol functions are different, for example, as shown in Table 1. The communication scenarios can include at least one of the following scenarios: a scenario supporting large-scale multiple-input multiple-output (MIMO) and a bandwidth greater than a first threshold; a scenario supporting dynamic spectrum sharing (DSS) signal processing; a scenario supporting artificial intelligence for radio access network (AI4RAN); a UL coordinated multiple points (CoMP) signal processing scenario; a DL CoMP signal processing scenario; a duplex signal processing scenario; or, a sensing signal processing scenario. Of course, for O-RAN, it can also include possible scenarios such as O-RAN category (Cat), O-RAN Cat B, etc.

[0208] Table 1

[0209] Among them, for the "cancellation" mentioned in the duplex scenario, it can be understood as interference cancellation, that is, eliminating the interference signal component collected and reconstructed from the received signal to obtain the useful signal.

[0210] As can be seen, different communication scenarios have different requirements for DUs and RUs, but the functional modules currently deployed on different functional entities are relatively fixed and cannot meet the differentiated requirements of different communication scenarios.

[0211] Therefore, the embodiments of the present application provide a communication method, by deploying part of the same functional modules on different functional entities, so that the functional entities execute or bypass part of the functional modules according to different communication scenarios to which the data is applied, to meet the different data processing requirements of different communication scenarios for the functional entities.

[0212] The communication method and device will be further described below in conjunction with the drawings. It can be understood that the first functional entity and the second functional entity are taken as an example of the execution subject of the interaction in the embodiments of the present application, but the present application does not limit the execution subject of the interaction. For example, the first functional entity and the second functional entity can be network devices. The methods performed by the network devices in the present application can also be implemented by modules (such as circuits, chips or chip systems, etc.) in the network devices, or logical nodes, logical modules or software capable of implementing all or part of the functions of the network devices.

[0213] In the embodiments of the present application, the term "wireless communication" can also be referred to as "communication", and the term "communication" can also be described as "data transmission", "information transmission" or "transmission".

[0214] FIG. 11 is a schematic diagram of a communication scenario provided by the embodiments of the present application.

[0215] As shown in FIG. 11, the access network device can be divided into multiple functional entities such as RU 210, DU 220 and CU 230. Of course, the access network device can include one or more RUs 210, one or more DUs 220 and one or more CUs 230. Among them, the CU 230 is connected with the 5GC 240, used to realize the communication with the core network device. In the embodiments of the present application, the core network device can also be referred to as a core network network element.

[0216] Among them, the 5GC 240 can be connected with multiple CUs 230, one CU 230 can also be connected with multiple DUs 220, and one DU 220 can also be connected with multiple RUs 210.

[0217] The access network device can be a gNB. The access network device provides NR user plane and control plane protocol endpoints to the terminal, and communicates with the 5GC 240 through the NG interface. The access network device is used to provide the function of wireless network connection between the terminal and the core network.

[0218] The CU 230 can host the RRC layer, SDAP layer and PDCP layer protocols of the access network device and control the operation of one or more DUs. The CU 230 communicates with the DU 220 through the F1 interface.

[0219] The DU 220 can host the RLC layer, MAC layer and PHY layer of the access network device, and its operation is controlled by the CU 230. One DU 220 can support one or more cells, and one cell supports one DU 220.

[0220] The RU 210 can be referred to as a radio unit, a radio frequency unit or a radio frequency remote unit, etc. It mainly completes the functions of receiving and transmitting baseband signals, and modulating and demodulating radio frequency signals, data processing, power amplification, etc. The RU can be deployed close to the antenna, with small feeder loss.

[0221] The 5GC 240 can include one or more of any possible core network network elements such as AMF entity, SMF entity, UPF entity, UDM entity, etc. The 5GC and the RAN together constitute the 5G network to provide a service channel for the user to connect to the data network, server. Of course, the 5GC 240 can also be replaced by the core network in the future communication system, and the embodiments of the present application do not limit it here.

[0222] The RAN is configured to provide radio access network connection functionality between the UE and the core network. The RAN can include an access network device, such as a gNB. In some cases, the access network device can refer to the entire RAN. The deployment form of the RAN can include a centralized RAN (CRAN) and a distributed RAN (DRAN). Among them, the CRAN adopts a BBU and RRU separation architecture, each BBU is located in the central machine room to form a BBU pool. The BBU communicates with the RRU through a front network. The DRAN adopts a BBU and RRU distributed deployment, each BBU is independently deployed in a cabinet, the RRU can be deployed together with the BBU in the cabinet, or the RRU is deployed close to the antenna on the tower.

[0223] In some examples, the RU 210, the DU 220, and the CU 230 can be deployed on the same physical device, or can be deployed on different physical devices respectively. Alternatively, part of the functional entities in the RU 210, the DU 220, and the CU 230 are deployed on the same physical device, and part of the functional entities are deployed on different physical devices, which is not limited in the embodiments of the present application.

[0224] It can be understood that the access network device can also include a case of being split into two functional entities, for example, the CU 230 and the DU 220 are deployed on the same physical device, and the CU 230 and the DU 220 can be regarded as one functional entity. Alternatively, the DU 220 and the RU 210 are deployed on the same physical device, and the DU 220 and the RU 210 can be regarded as one functional entity.

[0225] Of course, the present application is not limited to the network architecture of 5G, and the embodiments of the present application are also applicable to LTE networks and future possible network architectures such as future communication networks. It should be understood that the embodiments of the present application can be applied to any network architecture with communication connection capability.

[0226] FIG. 12 is a schematic diagram of a network communication protocol function determination method provided by an embodiment of the present application.

[0227] The communication process can be applied to, but not limited to, the communication scenarios shown in FIG. 1 and FIG. 11. The method can be applied to LTE, LTE frequency division duplex (FDD) system, LTE TDD, 5G system or NR system, subsequent communication systems (such as future communication systems), V2X, etc., vehicle to network (V2N), vehicle to vehicle (V2V), vehicle to infrastructure (V2I), vehicle to pedestrian (V2P), etc., inter-vehicle communication long term evolution (LTE-V), Internet of Vehicles, MTC, IoT, inter-machine communication long term evolution (LTE-M), machine to machine (M2M), D2D, etc. The first function entity and the second function entity involved in the embodiments of the present application can be network devices. The first function entity and the second function entity can be deployed on the same network device, or can be deployed on different network devices, which is not limited in the embodiments of the present application. In the embodiments of the present application, the network device can be considered as an access network device in general. Of course, in some cases, the network device can also be a core network device.

[0228] Next, the steps performed by the first function entity will be described from two aspects respectively. The method can include the following steps:

[0229] Scheme 1:

[0230] S101, the second function entity sends first data to the first function entity. Correspondingly, the first function entity receives the first data from the second function entity.

[0231] For example, the first function entity can include N first data processing function modules. N is a positive integer. The first data processing function module can be used to implement a first data processing function. For example, any communication protocol function mentioned in FIG. 6 to FIG. 10. Different first data corresponds to different data processing methods. The data processing method can include executing M1 first data processing functions, and / or skipping M2 first data processing functions. It can be understood that the sum of M1 and M2 should be equal to N. M1 and M2 are positive integers.

[0232] In some examples, "skipping" certain functions means that the first function entity does not perform these "skipped" functions in the process of data processing. In the embodiments of the present application, "skipping" can also be described as "not doing", "ignoring", "bypassing", "transmitting through" and the like, which are not limited in the embodiments of the present application. "Transmitting through" means that the data passes through these "skipped" function modules, but is not processed. "Skipping" can be considered as the data being directly transmitted to the function module that needs to be processed, without passing through these "skipped" function modules. "Bypassing" means that the data performs other paths for data processing. The subsequent embodiments of the present application will be described by taking "skipping" as an example.

[0233] In some examples, a plurality of communication protocol function modules can be deployed in the first function entity, and each communication protocol function module is used to implement a corresponding communication protocol function. For different data, the M1 first data processing functions performed by the corresponding data processing manner are partially the same or completely different, and the M2 first data processing functions skipped by the corresponding data processing manner are partially the same or completely different.

[0234] For example, the communication protocol functions that can be implemented by the first function entity include function 1, function 2, function 3, function 4 and function 5. For the data processing manner corresponding to data identifier 1, it can include executing function 1, function 2 and function 3, and skipping function 4 and function 5. For the data processing manner corresponding to data identifier 2, it can include executing function 1 and function 2, and skipping function 3, function 4 and function 5. For the data processing manner corresponding to data identifier 3, it can include skipping function 1, function 2, function 3, function 4 and function 5. For the data processing manner corresponding to data identifier 4, it can include executing function 1, function 2, function 3, function 4 and function 5. It can be seen that the functions executed for data identifier 3 and data identifier 4 are completely different, and the functions skipped are also completely different. For data identifier 1 and data identifier 2, the functions executed are partially the same, such as executing function 1 and function 2; and the functions executed are partially different, such as executing function 3 for data identifier 1 and not executing function 3 for data identifier 2. Correspondingly, for data identifier 1 and data identifier 2, the functions skipped are partially the same, such as skipping function 4 and function 5; and the functions skipped are partially different, such as skipping function 3 for data identifier 2 and not skipping function 3 for data identifier 1.

[0235] In some examples, the first function entity can be a DU, and the second function entity can be an RU. For another example, the first function entity can be an RU, and the second function entity can be a DU. For another example, the first function entity can be a CU, and the second function entity can be a DU. For another example, the first function entity can be a DU, and the second function entity can be a CU. In some other examples, the first function entity can be a BBU, and the second function entity can be an RRU. For another example, the first function entity can be an RRU, and the second function entity can be a BBU. In some other examples, the first function entity can be an RNA, and the second function entity can be an RU. For another example, the first function entity can be an RU, and the second function entity can be an RNA. The embodiments of the present application do not limit the specific forms of the first function entity and the second function entity.

[0236] In S102, the first function entity processes the first data according to the data processing mode corresponding to the first data.

[0237] For example, the first function entity can perform corresponding processing on the first data according to the data processing mode corresponding to the first data. For example, the first function entity can perform M1 first data processing functions on the first data, and / or skip M2 first data processing functions.

[0238] Solution 2:

[0239] In S103, the first function entity sends the first data to the second function entity. Correspondingly, the second function entity receives the first data from the first function entity.

[0240] For example, the first function entity itself can be aware of which functions need to be performed on the data that needs to be processed. Therefore, the first function entity can perform corresponding functions on the data to obtain the first data. In this case, the first function entity can send the first data to the second function entity. For the second function entity, after receiving the first data, the second function entity can perform similar operations as in S101 and S102. For the sake of brevity, the embodiments of the present application will not be described here. That is, the second function entity can determine which functions have been performed on the first data at the first function entity based on the data processing mode corresponding to the first data, and can determine which functions need to be performed on the first data at the second function entity.

[0241] It can be understood that the above-mentioned solution 1 and solution 2 can be executed alternatively, or both solution 1 and solution 2 can be executed, that is, the first function entity receives the first data and continues to send the processed data, which is not limited in the embodiments of the present application.

[0242] Different data in the embodiments of the present application can be associated with different data processing manners. The corresponding function entity can perform corresponding data processing functions based on the data processing manner corresponding to the data, and / or skip the corresponding data processing function to complete the processing of the data. The first function entity can meet the data processing needs of different communication scenarios.

[0243] In the communication method provided in the embodiments of the present application, one possible way is to indicate the correspondence between different data and data processing manners in an implicit manner. For example, the first function entity can determine which port the first data comes from. That is, different second function entities send the first data by using different ports, and the first function entity can determine which second function entity sends the first data according to the port. For example, the first data sent by different second function entities means that the communication scenarios to which the first data applies are different. Therefore, the first function entity can adopt a corresponding data processing manner to process the first data from different second function entities.

[0244] Another possible way is to indicate the correspondence between different data and data processing manners in an explicit manner. For example, different first data can be identified by a first identifier. That is, the first data received by the first function entity can carry a first identifier, and the data processing manner corresponding to the first data with different first identifiers is different. The embodiments of the present application can distinguish the first data applicable to different communication scenarios by the first identifier, so as to improve the accuracy of the first function entity in processing the first data.

[0245] In some embodiments, the first identifier can include a first type of first identifier and / or a second type of first identifier. For example, the first type of first identifier can be used to indicate one in-phase quadrature (IQ) data message. The first type of first identifier can also be referred to as an IQ data transmission message identifier. The second type of first identifier can be used to indicate a group of IQ data messages. The group of IQ data messages can include a plurality of IQ data messages. The second type of first identifier can also be referred to as an IQ data transmission series message identifier or an IQ data transmission message series identifier, etc. The embodiments of the present application do not limit the specific names of the first type of first identifier and the second type of first identifier.

[0246] For example, the IQ data transfer message identifier can identify data on different orthogonal frequency division multiplexing (OFDM) symbols or resource blocks. For the O-RAN scenario, the IQ data transfer message identifier can be ecpriSeqid, or a sequence (SEQ) ID specified in the eCPRI 2.0 protocol, denoted as SEQ ID. For another example, the IQ data transfer message series identifier can be used to identify a group of IQ data transfer messages. For example, the group of IQ data transfer messages corresponding to different physical channels, users, layers, antenna ports, etc. For the O-RAN scenario, the IQ data transfer message series identifier can be ecpriPcid or a PC ID specified in the eCPRI 2.0 protocol. In the O-RAN protocol, the PC ID can also be referred to as ecpriPcid, i.e., an IQ data transfer message series identifier, which can also be referred to as an extended antenna-carrier identifier, or eAxC ID. The eAxC ID can be used to identify a specific data stream related to each C-plane (ecpriRtcid) or U-plane (ecpriPcid) message. The eAxC ID can be considered as an analog value of the antenna carrier (AxC) value of the CPRI. The eAxC refers to the AxC with an identifier extended (extended, e) to accommodate multiple frequency bands and multiple component carriers. In the O-RAN, multiple O-DU processors can contribute to a single eAxC. Details can be referred to related technical implementations, which will not be described herein.

[0247] In the embodiments of the present application, the first identifier can be indicated based on each IQ data signal or a group of IQ data signals, so as to select a suitable way to indicate the first identifier in different scenarios and improve communication efficiency.

[0248] For the first type of first identifier mentioned above or the second type of first identifier, a way of indicating each IQ data message separately or indicating based on a group of IQ data messages is shown. Specifically, the first identifier can include the following multiple cases.

[0249] In some embodiments, the first identifier can comprise a functional entity identifier. That is, the first identifier can indicate different functional entities respectively. For example, the first identifier can comprise an identifier of a CU. For another example, the first identifier can comprise an identifier of a DU. For yet another example, the first identifier can comprise an identifier of an RU. Of course, the first identifier can also comprise an identifier of a CU and an identifier of a DU, or the first identifier can also comprise an identifier of a CU and an identifier of an RU, or the first identifier can also comprise an identifier of a DU and an identifier of an RU, or the first identifier can also comprise an identifier of a CU, an identifier of a DU and an identifier of an RU.

[0250] The embodiments of the present application provide a plurality of possible functional entity identifiers to indicate the first data based on different functional entities in appropriate scenarios, so as to meet the data processing requirements of data for different functional entities in different communication scenarios.

[0251] In some other embodiments, the first identifier can comprise a cell identifier. For example, the data processing manners corresponding to data from different cells can be different.

[0252] In yet some other embodiments, the first identifier can comprise an identifier of a terminal. For example, the data processing manners corresponding to data for communication with different terminals can be different.

[0253] In some other embodiments, the first identifier can comprise an identifier of a service flow. For example, the first identifier can comprise an identifier of a DRB. For another example, the first identifier can comprise an identifier of a protocol data unit (PDU) session. For yet another example, the first identifier can comprise an identifier of a QoS flow. For another example, the first identifier can comprise an identifier of a data packet. Of course, the first identifier can also comprise an identifier of a DRB and an identifier of a QoS flow, or the first identifier can also comprise an identifier of a PDU session, an identifier of a QoS flow and an identifier of a data packet, or the first identifier can also comprise an identifier of a DRB, an identifier of a PDU session, an identifier of a QoS flow and an identifier of a data packet, etc. For the convenience of description, the embodiments of the present application will not enumerate the combination forms of the various identifiers of service flows that the first identifier can comprise, such as the first identifier can comprise a combination of any one, two or three of the above identifiers.

[0254] The embodiments of the present application provide a plurality of possible service flow identifiers to indicate the first data based on different service flows in appropriate scenarios, so as to meet the data processing requirements of data for different service flows in different communication scenarios.

[0255] In some embodiments, the first identifier can comprise an identifier of a wireless resource. For example, the first identifier can comprise an identifier of a physical channel. For another example, the first identifier can comprise an identifier of an antenna port. For yet another example, the first identifier can comprise an identifier of a symbol. For yet another example, the first identifier can comprise an identifier of a time slot. For yet another example, the first identifier can comprise an identifier of a frame. For yet another example, the first identifier can comprise an identifier of a subframe. For yet another example, the first identifier can comprise an identifier of a beam. For yet another example, the first identifier can comprise an identifier of a frequency domain resource.

[0256] Of course, the first identifier can further comprise an identifier of a physical channel and an identifier of an antenna port, or the first identifier can further comprise an identifier of a symbol, an identifier of a time slot, and an identifier of a frame, or the first identifier can further comprise an identifier of an antenna port, an identifier of a symbol, an identifier of a beam, and an identifier of a frequency domain resource, or the first identifier can further comprise an identifier of a physical channel, an identifier of an antenna port, an identifier of a time slot, an identifier of a beam, and an identifier of a frequency domain resource, or the first identifier can further comprise an identifier of a physical channel, an identifier of an antenna port, an identifier of a symbol, an identifier of a time slot, an identifier of a subframe, and an identifier of a beam, or the first identifier can further comprise an identifier of a physical channel, an identifier of an antenna port, an identifier of a symbol, an identifier of a time slot, an identifier of a frame, an identifier of a beam, and an identifier of a frequency domain resource, or the first identifier can further comprise an identifier of a physical channel, an identifier of an antenna port, an identifier of a symbol, an identifier of a time slot, an identifier of a frame, an identifier of a subframe, an identifier of a beam, and an identifier of a frequency domain resource. For convenience of description, the present embodiments will not enumerate all possible combinations of the identifiers of the various wireless resources that the first identifier can comprise, such as a combination of any one, two, three, four, five, six, or seven of the above identifiers.

[0257] The present embodiments provide various possible identifiers of wireless resources, so as to indicate the first data based on different wireless resources in appropriate scenarios, and meet the data processing requirements of data of different wireless resources in different communication scenarios.

[0258] The selection of appropriate functions for processing improves the efficiency of service processing and the performance of the system.

[0259] In the embodiments of the present application, the mentioned identifier can be an identity (ID) or an index.

[0260] The present embodiments provide various possible forms of the first identifier, which can be used to indicate the first data in different scenarios, so as to meet the data processing requirements of the functional entity in different communication scenarios.

[0261] Of course, the correspondence between the first identifier and the data processing manner mentioned in the above examples can be protocol predefined or determined based on the first information. For example, the first functional entity can obtain the first information before sending the first data. That is, the method can further include generating the first information before the first functional entity sends the first data. The first information can be used to indicate the association between the first identifier and the data processing scenario. In this case, different data processing manners are associated with different data processing scenarios. And / or, the first information can directly indicate the association between the first identifier and the data processing manner.

[0262] For example, the association between the data identifier and the data processing manner indicated by the first information can be protocol predefined. Or the first functional entity can determine the first information based on some possible parameters such as the running state of the functional entity, interface traffic information, etc. In this case, the first functional entity can also send the first information to the second functional entity, so that the second functional entity can perform similar operations as the first functional entity based on the first information.

[0263] In some other embodiments, the association between the data identifier and the data processing manner indicated by the first information can also be configured by a network device, such as an access network device, a core network device, a network management device, and / or a terminal, etc. For example, it can be configured by other functional entities different from the first functional entity. In this case, the first functional entity can receive the first information from other functional entities, such as the second functional entity sending the first information to the first functional entity, and accordingly, the first functional entity receives the first information from the second functional entity.

[0264] In this case, the first information can be carried by a management plane message, a radio resource control (RRC), a media access control (MAC) control element (CE), and / or a downlink control information (DCI), etc. The embodiments of the present application do not limit this.

[0265] Of course, for the case that the first function entity is not the second function entity, the first function entity can also send the first information it receives to the second function entity. For example, the first function entity sends the first information related to the second function entity to the second function entity. For example, the first information received by the first function entity includes the association relationship between the data identifier and the data processing manner related to the first function entity, and the association relationship between the data identifier and the data processing manner related to the second function entity. Then the first function entity can send the association relationship between the data identifier and the data processing manner related to the second function entity to the second function entity. So as to reduce unnecessary resource consumption.

[0266] The embodiments of the present application provide a plurality of ways to obtain the first information, so that the first function entity can quickly and accurately obtain the first information by selecting a suitable way in different scenarios.

[0267] In some embodiments, the above-mentioned data processing scenario can be considered as a communication scenario. That is, different data processing scenarios and different communication scenarios have the same meaning. For example, the data processing scenario can include a scenario supporting large-scale MIMO and a bandwidth greater than a first threshold. It can also be called a large-scale MIMO and large bandwidth scenario. Wherein, the large bandwidth can be considered as a bandwidth greater than the first threshold. In some examples, the first threshold can be 200MHz or 400MHz. Of course, the above only shows some possible first thresholds, and a suitable first threshold can be selected according to the actual situation, and the embodiments of the present application are not limited here.

[0268] For another example, the data processing scenario can include a DSS signal processing scenario.

[0269] For another example, the data processing scenario can include an AI4RAN scenario.

[0270] For another example, the data processing scenario can include an UL CoMP signal processing scenario.

[0271] For another example, the data processing scenario can include a DL CoMP signal processing scenario.

[0272] For another example, the data processing scenario can include a duplex signal processing scenario.

[0273] For another example, the data processing scenario can include a perception signal processing scenario.

[0274] In some examples, the data processing scenarios can further include: a scenario supporting massive MIMO and a bandwidth greater than a first threshold, a scenario supporting DSS signal processing; a scenario supporting AI4RAN, a duplex signal processing scenario, a sensing signal processing scenario; a scenario supporting AI4RAN, a UL CoMP signal processing scenario, a duplex signal processing scenario, a sensing signal processing scenario; a scenario supporting massive MIMO and a bandwidth greater than a first threshold, a scenario supporting DSS signal processing, a scenario supporting AI4RAN, a DL CoMP signal processing scenario, a sensing signal processing scenario; a scenario supporting massive MIMO and a bandwidth greater than a first threshold, a scenario supporting DSS signal processing, a scenario supporting AI4RAN, a UL CoMP signal processing scenario, a duplex signal processing scenario, a sensing signal processing scenario; a scenario supporting massive MIMO and a bandwidth greater than a first threshold, a scenario supporting DSS signal processing, a scenario supporting AI4RAN, a UL CoMP signal processing scenario, a DL CoMP signal processing scenario, a duplex signal processing scenario, a sensing signal processing scenario. It can be understood that the data processing scenarios can further include any two, three, four, five, or six of the above data processing scenarios, and for the convenience of description, the embodiments of the present application will not be listed one by one here.

[0275] In other examples, the data processing scenarios can further include O-RAN Cat A, O-RAN Cat B, and other possible scenarios, which are not limited herein.

[0276] It can be understood that the one or more data processing scenarios mentioned above can refer to the description of Table 1, and the embodiments of the present application will not be described here.

[0277] The embodiments of the present application can be applied to a variety of different data processing scenarios and can meet the data processing needs of functional entities in different data processing scenarios.

[0278] In some embodiments, the first identifier mentioned above can also be used to indicate that the first data has undergone M1 first data processing functions, and / or the first identifier can also be used to indicate that the first data needs to undergo M2 first data processing functions on the second functional entity, i.e., the first data skips the functions not executed on the first functional entity and needs to be executed on the second functional entity.

[0279] The embodiments of the present application can indicate which functions the data has undergone and / or which functions the data needs to undergo by sending the first data carrying the first identifier. In order for the device receiving the data to perform the corresponding function processing on the first data, the data processing needs of functional entities in different communication scenarios are met.

[0280] In the communication method provided in the embodiments of the present application, the first data processing function module mentioned in each of the above embodiments can include any of the communication protocol function modules mentioned in FIGS. 6-10.

[0281] In some embodiments, the first data processing function module can include a function module for uplink data processing. For example, the first data processing function module can include an RE demapping function module. For another example, the first data processing function module can include a first channel estimation function module. The channel estimation result obtained by the first channel estimation function module can be used for uplink signal combination. For another example, the first data processing function module can include a function module for implementing uplink signal combination. For example, the function module for implementing uplink signal combination can be referred to as an UL BF function module. The UL BF function module can use the channel estimation result obtained by the first channel estimation function module to combine uplink signals. In some examples, UL BF can also be referred to as uplink beam selection, feature beam dimension reduction, antenna port combination, antenna-to-beam mapping, etc., and the name of UL BF is not limited in the embodiments of the present application. For another example, the first data processing function module can include a second channel estimation function module. The channel estimation result obtained by the second channel estimation function module can be used for signal equalization. For another example, the first data processing function module can include an AI-based second channel estimation function module. For another example, the first data processing function module can include an equalization function module. For another example, the first data processing function module can include an AI-based equalization function module. As can be seen in combination with FIG. 10, the first data processing function module can also include any one or more of an analog beamforming function module, an analog-to-digital function module, an FFT / CP removal function module, an RE demapping function module, an IDFT function module, a demodulation function module, a descrambling function module, a rate demapping function module, and a decoding function module. For the convenience of description, the various combinations of communication protocol function modules that the first data processing function module can include will not be listed one by one in the embodiments of the present application, for example, the first data processing function module can include a combination of any of the above-mentioned multiple communication protocol functions.

[0282] It can be understood that the channel estimation function module in FIG. 10 can be considered as a second channel estimation function module.

[0283] For example, the first data processing function module includes a RE demapping function module, a second channel estimation function module and an equalization function module. The data processing mode corresponding to data A can include performing RE demapping function, and skipping the second channel estimation function and the equalization function. The data processing mode corresponding to data B can include performing RE demapping function, the second channel estimation function and the equalization function. The data processing mode corresponding to data C can include performing RE demapping function and the second channel estimation function, and skipping the equalization function.

[0284] Embodiments of the present application provide a plurality of communication protocol function modules that can be involved in the uplink communication scenario, to meet the data processing requirements of the function entity for different uplink data.

[0285] In some other embodiments, the first data processing function module can include a function module for downlink data processing. For example, the first data processing function module can include a modulation function module. For another example, the first data processing function module can include a layer mapping function module. For yet another example, the first data processing function module can include a precoding function module. In combination with FIG. 9, the first data processing function module can also include any one or more of an encoding function module, a rate mapping function module, a scrambling function module, a modulation function module, a layer mapping function module, a precoding function module, a RE mapping function module, an IFFT / add CP function module, a data-to-analog function module, an analog beamforming function module, etc. For the convenience of description, embodiments of the present application will not enumerate the combination forms of various communication protocol function modules that the first data processing function module can include, for example, the first data processing function module can include a combination of any plurality of communication protocol function modules described above.

[0286] For example, the first data processing function module includes a modulation function module, a layer mapping function module and a precoding function module. The data processing mode corresponding to data A' can include performing modulation function, layer mapping function and precoding function. The data processing mode corresponding to data B' can include skipping modulation function, layer mapping function and precoding function. The data processing mode corresponding to data C' can include performing modulation function and layer mapping function, and skipping precoding function.

[0287] Embodiments of the present application provide a plurality of communication protocol function modules that can be involved in the downlink communication scenario, to meet the data processing requirements of the function entity for different downlink data.

[0288] In yet some other embodiments, the first data processing function module can include a function module for generating downlink precoding parameters for a single user. For example, the function module for generating downlink precoding parameters for a single user can be the SU-BF function module mentioned above.

[0289] In some embodiments, the first data processing function module can include a function module for generating downlink precoding parameters for a single user based on AI, or referred to as an AI-based SU-BF function module.

[0290] In some embodiments, the first data processing function module can include a function module for generating downlink precoding parameters for multiple users. For example, the function module for generating downlink precoding parameters for multiple users can be the aforementioned MU-BF function module.

[0291] In some embodiments, the first data processing function module can include a function module for generating downlink precoding parameters for multiple users based on AI, or referred to as an AI-based MU-BF function module.

[0292] In some embodiments, the first data processing function module can include a function module for generating downlink precoding parameters based on uplink reference signal measurement. For example, the function module for generating downlink precoding parameters based on uplink reference signal measurement can be the aforementioned SRS-BF function module.

[0293] In some embodiments, the first data processing function module can include an AI-based function module for generating downlink precoding parameters based on uplink reference signal measurement, or referred to as an AI-based SRS-BF function module.

[0294] In some embodiments, the first data processing function module can include a function module for generating downlink precoding parameters based on uplink reference signal measurement. For example, the function module for generating downlink precoding parameters based on uplink reference signal measurement can be the aforementioned SRS-BF function module.

[0295] In yet some embodiments, the first data processing function module can include a function module for data processing of the sensing data. For example, the first data processing function module can include a sensing LS function module for frequency domain. For another example, the first data processing function module can include a sensing LS function module for time domain. For yet another example, the first data processing function module can include a sensing range-velocity-angle (RVA) spectrum estimation function module. In some examples, the first data processing function module can further include any one or more of a sensing LS function module for frequency domain, a sensing LS function module for time domain, a sensing RVA spectrum estimation function module, a sensing constant false-alarm rate (CFAR) function module, a clustering function module, a target tracking and filtering function module, a target identification function module, etc. For convenience of description, the present embodiments will not enumerate all possible combinations of various communication protocol function modules that the first data processing function module can include, such as the first data processing function module can include a combination of any multiple of the above communication protocol function modules.

[0296] The frequency domain sensing LS function can be used to perform channel estimation on the received sensing signal in frequency domain. The time domain sensing LS function can be used to perform channel estimation on the received sensing signal in time domain.

[0297] The sensing RVA spectrum estimation function can be used to obtain the distribution of the range, velocity and angle of the sensing target at each frequency component. For example, it can be obtained by performing multi-dimensional FFT transform on the sensing signal.

[0298] The sensing CFAR function can be used to reliably detect targets in complex signal environment. For example, it can detect signals in the presence of background noise. In particular, it detects when the noise level changes over time. The core idea is to estimate the noise characteristics in a local range and use it to set the detection threshold, thereby achieving control of the fixed false alarm rate.

[0299] The clustering function of the sensing target can be used to classify the detection results of the sensing signal. For example, a machine learning algorithm can be used for processing.

[0300] The target tracking and filtering function can be used to track the objects of the sensing detection, and filter the clutter.

[0301] The target identification function can be used to identify the detection results of the sensing signal. For example, a machine learning algorithm can be used for processing.

[0302] The specific implementation of each of the above-mentioned functions for sensing can refer to related technologies, and the present embodiments will not be repeated here.

[0303] The embodiments of the present application provide a plurality of communication protocol function modules that can be involved in a perception communication scenario, so as to meet the data processing requirements of the function entity for different perception data.

[0304] In combination with the above embodiments, it can be seen that the embodiments of the present application provide a plurality of communication protocol function modules that can be deployed by the first function entity, so that the first function entity can more flexibly select to perform appropriate functions for different data, so as to meet the data processing requirements of the data in different communication scenarios.

[0305] In some examples, in the case that the above first data processing function module includes a function module for processing perception data, it means that the first data can be perception data. The first identifier can also be used to indicate that the first data is perception symbol data or communication symbol data. For the uplink communication scenario, the first function entity can determine to perform a communication protocol function related to perception data according to the first data being perception symbol data. Alternatively, the first function entity can determine to perform a communication protocol function related to communication data according to the first data being communication symbol data.

[0306] In some examples, the first data being perception symbol data or communication symbol data can be indicated by one field or one bit.

[0307] In some examples, the various cases of the first identifier mentioned in the above embodiments can be considered as cases where the first data is communication symbol data. The above various first identifiers can be jointly designed. When the first identifier is of a certain value, it can indicate different function entities, or different terminals, or different cells, or different service flows, or different wireless resources, or whether it is perception symbol data.

[0308] In other examples, a separate bit can be used to indicate whether the first data is perception symbol data or communication symbol data. For example, in the case where the first identifier indicates different function entities, or different terminals, or different cells, or different service flows, or different wireless resources, a bit can be further used to indicate whether the first data is perception symbol data.

[0309] In the embodiments of the present application, the first identifier can be used to indicate different types of first data, so that the function entity can select appropriate communication protocol functions based on perception symbol data and communication symbol data for processing, so as to meet the data processing requirements of the data in different communication scenarios.

[0310] The scheme described in FIG. 12 can be applied to a scenario where the split mode of the communication protocol function between the first function entity and the second function entity dynamically changes. Then, for the scenario where the communication protocol function between the first function entity and the second function entity is deployed according to a fixed split mode. How to make the function entity meet the data processing requirements of data in different communication scenarios. The scheme described in FIG. 13 can be referred to.

[0311] FIG. 13 is a schematic diagram of a network communication protocol function determination method provided by an embodiment of the present application.

[0312] The communication process can be applied to, but is not limited to, the communication scenarios shown in FIG. 1 and FIG. 11. The method can be applied to LTE, LTE FDD system, LTE TDD, 5G system or NR system, subsequent evolution of communication system (such as future communication system), V2X, LTE-V, vehicle networking, MTC, IoT, LTE-M, M2M, D2D and other wireless communication scenarios. The first function entity and the second function entity involved in the embodiments of the present application can be network devices. The first function entity and the second function entity can be deployed on the same network device, or can be deployed on different network devices, which is not limited in the embodiments of the present application. In the embodiments of the present application, the network device can be considered as an access network device in general. Of course, in some cases, the network device can also be a core network device. The method can include the following steps:

[0313] S201, the second function entity sends first data to the first function entity. Correspondingly, the first function entity receives the first data from the second function entity.

[0314] The first function entity is configured to implement a first physical layer protocol function, and the second function entity is configured to implement a second physical layer protocol function. The first physical layer protocol function and the second physical layer protocol function constitute a complete physical layer protocol function.

[0315] The implementation process of S201 is similar to that of S101. The difference is that the communication protocol function in S201 is a physical layer protocol function.

[0316] S202, the first function entity processes the first data by using a target data processing mode corresponding to the data type of the first data according to the data type of the first data.

[0317] For example, the first function entity can select different data processing manners to process the first data according to whether the first data is perceptual symbol data or communication symbol data. For example, if the first data is perceptual symbol data, the first function entity adopts a target data processing manner related to the perceptual symbol data to process the perceptual symbol data. For example, if the first data is communication symbol data, the first function entity adopts a target data processing manner related to the communication symbol data to process the communication symbol data.

[0318] S203, the first function entity adopts a target data processing manner to process the first data according to a second physical layer protocol function.

[0319] For example, different second function entities can deploy different second physical layer protocol functions. Then the first function entity can adopt different target data processing manners to process the first data according to the source of the first data, such as the first data sent by different second function entities.

[0320] For example, the second function entity 1 deploys the second physical layer protocol functions of function 1, function 2 and function 3, and the second function entity 1 deploys the second physical layer protocol functions of function 1 and function 2. The first data sent by the second function entity 1 is suitable for communication scenario 1, and the first data sent by the second function entity 1 is suitable for communication scenario 2. The first function entity corresponding to communication scenario 1 needs to perform function 4 and function 5, and the first function entity corresponding to communication scenario 1 needs to perform function 3, function 4 and function 5. Then the first function entity can determine whether to perform function 3, function 4 and function 5 or perform function 4 and function 5 on the first data according to the source of the first data, that is, which second function entity sends the first data.

[0321] In some examples, the target data processing manner mentioned in S202 and S203 can include performing one or more first physical layer protocol functions and / or skipping one or more first physical layer protocol functions. Similar to the execution of M1 first data processing functions and / or the skipping of M2 first data processing functions mentioned in S101. The one or more first physical layer protocol functions performed by different target data processing manners are partially the same or completely different, and the one or more first physical layer protocol functions skipped by different target data processing manners are partially the same or completely different. For details, please refer to the corresponding description in S101, which will not be repeated here.

[0322] It can be understood that S202 and S203 are parallel steps, that is, the first function entity can execute one of them.

[0323] The specific implementation process of the first data processing in FIG. 12 can refer to the description of the corresponding embodiment in FIG. 11, and the embodiments of the present application will not be repeated here.

[0324] The embodiments of the present application process different data by using appropriate data processing methods according to the data types or the physical layer protocol functions of the second function entity. In the case of relatively fixed division of the physical layer protocol functions of the first function entity and the second function entity, the data processing requirements of the function entities for data in different communication scenarios are met.

[0325] In the communication method provided by the embodiments of the present application, considering that the communication protocol function division manner between the first function entity and the second function entity can adopt a fixed division manner, i.e., relatively fixed communication protocol function modules are deployed on the first function entity and the second function entity. Therefore, the physical layer protocol function division manner between the first physical layer protocol function and the second physical layer protocol function can include division between scrambling function and modulation function. For example, option 7-3 shown in FIG. 7.

[0326] For another example, the physical layer protocol function division manner between the first physical layer protocol function and the second physical layer protocol function can include division between the second channel estimation function and the function for implementing uplink signal combination. For example, referring to FIG. 10, the channel estimation function is the second channel estimation function, and the UL BF function can be included between the second channel estimation function and the RE demapping function. In this case, the division manner of the physical layer protocol between the first function entity and the second function entity can be divided between the second channel estimation function and the UL BF function. That is, the UL BF function and the functions before it are deployed on one function entity, and the second channel estimation function and the functions after it are deployed on another function entity. The channel estimation result obtained through the second channel estimation function can be used for signal equalization. That is, the channel estimation result output by the second channel estimation function module is used as the input of the equalization function module, so as to perform signal equalization processing.

[0327] For another example, the physical layer protocol function division manner between the first physical layer protocol function and the second physical layer protocol function can include division between the equalization function and the IDFT function. For example, the physical layer protocol function division manner between the function entity 3 and the function entity 4 in FIG. 10.

[0328] For another example, the physical layer protocol function division manner between the first physical layer protocol function and the second physical layer protocol function can include division between the second channel estimation function and the equalization function. For example, the division manner of the UL PI-B shown in FIG. 8.

[0329] Of course in other examples, the communication protocol function division manner between the first function entity and the second function entity can also be divided between any two adjacent function modules, and the embodiments of the present application are not limited here.

[0330] In some examples, the division between the first function entity and the second function entity can also be considered between protocol layers or within a protocol layer other than the physical layer, such as the possible division manners shown in FIGS. 5 and 6, and the embodiments of the present application are not limited here.

[0331] The embodiments of the present application can be applied to communication scenarios corresponding to various function division manners, improving the universality.

[0332] In some embodiments, based on the above-mentioned various intra-physical layer division manners, the second function entity can be a second target entity with the functions of uplink signal merging and second channel estimation. That is, the second function entity is at least deployed with an UL BF function module and a second channel estimation module. This case can correspond to the case where the first function entity and the second function entity are divided between the second channel estimation function and the equalization function. For example, the UL PI-B division manner shown in FIG. 8.

[0333] For another example, the second function entity can be a second target entity with the functions of uplink signal merging, second channel estimation, and equalization. That is, the second function entity is at least deployed with an UL BF function module, a second channel estimation module, and an equalization module. This case can correspond to the case where the first function entity and the second function entity are divided between the equalization function and the IDFT function. For example, the physical layer protocol function division manner between the function entity 3 and the function entity 4 in FIG. 10.

[0334] In this case, considering that the first data can have already performed the second channel estimation function and the equalization function on the second function entity, for the first function entity, the second channel estimation function and the equalization function can be determined to be skipped after receiving the first data. Avoiding the first data from performing repeated second channel estimation function and equalization function, improving the accuracy of data processing. It can be seen that the first function entity can be adapted to the second function entity that performs or does not perform the second channel estimation function and the equalization function, and can meet the data processing needs of the first function entity for data in different communication scenarios.

[0335] For another example, the second function entity can be a second target entity with the function of uplink signal merging. That is, the second function entity is at least deployed with an UL BF function module. This case can correspond to the case where the first function entity and the second function entity are divided between the second channel estimation function and the function for realizing uplink signal merging.

[0336] In this case, there can be a case that the data type of the first data is the sensing symbol data type, that is, the first data is sensing symbol data. Then for the second function entity, the function of uplink signal combination can be skipped. That is, the second function entity does not perform the UL BF function on the first data. The reason is that there is no need to perform uplink signal combination for sensing symbol data.

[0337] The second function entity of the embodiment of the present application can also process different data types of data by using appropriate data processing methods, which can meet the data processing needs of the second function entity in different communication scenarios.

[0338] Of course, one or more of the above-mentioned second function entities can be simultaneously provided, which is not limited in the embodiment of the present application.

[0339] The embodiment of the present application provides a plurality of physical layer protocol functions that the second function entity can have, which can adapt to the corresponding second function entity in different communication scenarios, and can meet the data processing needs of the function entity in different communication scenarios.

[0340] In the communication method provided by the embodiment of the present application, it is considered that the first data can be downlink data, that is, for the downlink communication scenario, the first physical layer protocol function possessed by the first function entity can include a function for generating downlink precoding parameters for single user, that is, SU-BF function. Alternatively, the first physical layer protocol function possessed by the first function entity can include a function for generating downlink precoding parameters for multiple users, that is, MU-BF function. Alternatively, the first physical layer protocol function possessed by the first function entity can include a function for generating downlink precoding parameters based on uplink reference signal measurement, that is, SRS-BF function.

[0341] In some examples, the first physical layer protocol function possessed by the first function entity can also include: SU-BF function and MU-BF function; SU-BF function and SRS-BF function; MU-BF function and SRS-BF function; SU-BF function, MU-BF function and SRS-BF function, which is not limited in the embodiment of the present application.

[0342] Similarly, the second physical layer protocol function possessed by the second function entity can include a function for generating downlink precoding parameters for single user, that is, SU-BF function. Alternatively, the second physical layer protocol function possessed by the second function entity can include a function for generating downlink precoding parameters for multiple users, that is, MU-BF function. Alternatively, the second physical layer protocol function possessed by the second function entity can include a function for generating downlink precoding parameters based on uplink reference signal measurement, that is, SRS-BF function.

[0343] In some examples, the second physical layer protocol function possessed by the second function entity can further include: SU-BF function and MU-BF function; SU-BF function and SRS-BF function; MU-BF function and SRS-BF function; SU-BF function, MU-BF function and SRS-BF function, which are not limited herein.

[0344] In some examples, the above-mentioned SU-BF function, MU-BF function and SRS-BF function can be deployed with corresponding function modules on one function entity, and not deployed with the same function modules on another function entity. For example, the first function entity is deployed with SU-BF function module, and the second function entity is deployed with MU-BF function module and SRS-BF function module; for another example, the SU-BF function module, MU-BF function module and SRS-BF function module are all deployed on the first function entity, and the like. It can be understood that the above-mentioned examples only describe some possible cases, and the specific deployment position of each function module is not limited herein.

[0345] The embodiments of the present application can be applied to the scenario that the SU-BF function, MU-BF function and SRS-BF function are respectively deployed on different function entities, so as to meet the data processing requirement of the function entity for data in different communication scenarios.

[0346] It can be understood that the implementation process of each embodiment corresponding to FIG. 13 can refer to the description of some embodiments in FIG. 12, and the embodiments of the present application will not be repeated herein.

[0347] Next, the above-mentioned schemes will be described in combination with more specific examples.

[0348] It can be assumed that there are two function entities, function entity A and function entity B. Any one of the function entities can be used as the first function entity, and the other function entity can be used as the second function entity.

[0349] Referring to FIG. 14, a schematic diagram of a downlink network architecture is shown. The function entity A can be deployed with a precoding function module, a layer mapping function module, a modulation function module, an SRS-BF function module, an SU-BF function module, and an MU-BF function module. So that the function entity A can implement the precoding function, the layer mapping function, the modulation function, the SRS-BF function, the SU-BF function, and the MU-BF function. The function entity B can be deployed with a scrambling function module, an SRS-BF function module, an AI-based SRS-BF function module, an SU-BF function module, an AI-based SU-BF function module, an MU-BF function module, and an AI-based MU-BF function module. So that the function entity B can implement the scrambling function, the SRS-BF function, the AI-based SRS-BF function, the SU-BF function, the AI-based SU-BF function, the MU-BF function, and the AI-based MU-BF function. For example, the function entity A in FIG. 14 can be an RU, and the function entity B can be a DU.

[0350] It can be understood that generally, the DU has stronger computing and global processing capabilities than the RU, and therefore, some function modules based on AI can generally be selected to be deployed on the DU. Of course, for the RU with certain processing capabilities, some function modules based on AI can also be deployed, and the embodiments of the present application do not limit this.

[0351] Referring to FIG. 15, a schematic diagram of an uplink network architecture is shown. The function entity A can be deployed with a second channel estimation function module, an equalization function module, a sensing LS function module, and an IDFT function module. So that the function entity A can implement the second channel estimation function, the equalization function, the sensing LS function, and the IDFT function. The function entity B can be deployed with an RE demapping function module, an UL BF function module, a first channel estimation function module, a second channel estimation function module, and an equalization function module. So that the function entity B can implement the RE demapping function, the UL BF function, the first channel estimation function, the second channel estimation function, and the equalization function. For example, the function entity A in FIG. 15 can be a DU, and the function entity B can be an RU.

[0352] Of course, FIG. 14 and FIG. 15 only show one possible function entity and the functions that can be implemented on each function entity, and each function entity can also be deployed with other more or less communication protocol function modules according to actual conditions to implement corresponding communication protocol functions, and the embodiments of the present application do not repeat them here.

[0353] It should be understood that the dashed boxes in Figures 14 and 15 represent data processing steps that skip a specific functional module, meaning the data is processed without going through that module's functionality. This does not mean that multiple identical functional modules are deployed on the same functional entity. Refer to the arrows in different rows of Figures 14 and 15 to indicate the data processing flow for a specific set of data.

[0354] Figure 16 is a schematic diagram of a communication method provided by an embodiment of this application. This communication process can be applied to, but is not limited to, the communication scenarios shown in Figures 1 and 11. This method can be applied to LTE, LTE FDD systems, LTE TDD, 5G systems or NR systems, subsequent evolving communication systems (such as future communication systems), V2X (where V2X can include V2N, V2V, V2I, V2P, etc.), LTE-V, vehicle-to-everything (V2X), MTC, IoT, LTE-M, M2M, D2D, and other wireless communication scenarios. The DU and RU involved in the embodiments of this application can be network devices. The DU and RU can be deployed on the same network device or on different network devices; this is not limited in this embodiment. In the embodiments of this application, the network device can generally be considered an access network device. Of course, in some cases, the network device can also be a core network device. The method can include the following steps:

[0355] S301, Functional entity A and functional entity B perform functional initialization configuration.

[0356] For example, functional entities A and B complete the functional initialization configuration or update. The specific physical layer protocol functions configured on functional entities A and B can be referred to Figures 14 and 15, which will not be repeated here in this embodiment. It is understood that if different functional divisions are performed at the RU granularity, the PHY layer protocol functions of different RUs may differ.

[0357] S302, functional entity A sends first information to functional entity B. Correspondingly, functional entity B receives the first information from functional entity A. Alternatively, functional entity B sends first information to functional entity A. Correspondingly, functional entity A receives the first information from functional entity B.

[0358] For example, functional entity A is a DU, and functional entity B is an RU; or functional entity A is an RU, and functional entity B is a DU. The DU sends to the RU information about the functional characteristics supported by at least one of the following types of identifiers: RU ID, cell ID, UE ID, PDU session ID, DRB ID, QoS flow ID, or packet ID; or the associated data processing method of the DU or the RU. The functional characteristics information refers to the various communication scenarios (or data processing scenarios) mentioned above, such as massive MIMO and bandwidth exceeding a first threshold scenarios, DSS signal processing scenarios, UL CoMP signal processing scenarios, DL CoMP signal processing scenarios, AI4RAN scenarios, sensing signal processing scenarios, and duplex signal processing scenarios. The data processing methods of the DU and the RU may include the corresponding functional entity performing certain functions or skipping (or bypassing) certain functions.

[0359] In other examples, the above information can also be sent from RU to DU, and the RU ID can be replaced with the DU ID accordingly. When DU sends the first information to RU, the content of the first information can be generated by DU, or sent to DU by other functional entities or devices. When RU sends the first information to DU, the content of the first information can be generated by RU, or sent to RU by other functional entities or devices. This application does not limit the scope of the embodiments described herein.

[0360] Next, referring to Figures 14 and 15, we will further describe the data processing methods corresponding to functional entities A and B, respectively, using different communication scenarios as examples.

[0361] For scenarios supporting massive MIMO and bandwidth greater than the first threshold, as well as scenarios supporting DSS signal processing:

[0362] For downlink data, functional entity B performs scrambling and subsequent higher-level functions, while functional entity A performs modulation and subsequent lower-level functions. Functional entity B may skip the SRS BF, SU BF, and / or MU BF functions. Correspondingly, functional entity A performs the SRS BF, SU BF, and / or MU BF functions.

[0363] For uplink data, functional entity B performs equalization, second channel estimation, and previous lower-level functions. In some examples, functional entity B may perform UL BF (Ultra-Low-Level Browsing) or not, depending on the actual situation; this application does not limit this choice. Functional entity A skips the second channel estimation and equalization functions, and performs IDFT and higher-level functions.

[0364] For AI4RAN, UL CoMP signal processing, DL CoMP signal processing, and duplex signal processing scenarios:

[0365] For downlink data, functional entity B performs the SRS BF function (or AI-based SRS BF function), SU BF function (or AI-based SU BF function), or MU BF function (or AI-based MU BF function), while functional entity A skips the SRS BF function, SU BF function, or MU BF function.

[0366] For uplink data, functional entity B performs the first channel estimation function, UL BF function, RE demapping function, and the previous lower-level functions. Functional entity B skips the second channel estimation function and equalization function. Functional entity A performs the second channel estimation (or AI-based second channel estimation function), equalization function (or AI-based equalization function), IDFT, and the subsequent higher-level functions.

[0367] For scenarios that support sensing signal processing:

[0368] For uplink data, functional entity B performs the RE demapping function and the underlying functions. Functional entity B can skip the first channel estimation function, UL BF function, second channel estimation function, and equalization function. Functional entity A performs the sensing LS function and the underlying functions. The sensing LS function can also be called the channel estimation function of the sensing signal, which is not limited to this embodiment.

[0369] Optionally, the first information can be indicated by the CU to the DU, or by the core network control plane function (which can be SMF) to the CU, and then the CU informs the DU. This embodiment of the application does not limit this. Different communication scenarios or different data processing methods can be associated with the first identifier. The first identifier can be an IQ data transmission message series identifier or an IQ data transmission message identifier. The IQ data transmission message series identifier is an identifier for a series of IQ data, which can be used to identify a series of messages belonging to different physical channels, users, layers, or antenna ports. It can be ecpriPcid as specified in the O-RAN protocol or PC_ID as specified in the eCPRI 2.0 protocol. The IQ data transmission message identifier is an identifier for each message in a series of IQ data transmission messages, which can identify data on different OFDM symbols or resource blocks. It can be ecpriSeqid as specified in the O-RAN protocol or SEQ_ID as specified in the eCPRI 2.0 protocol. The IQ data transmission message series identifier or IQ data transmission message identifier can also be represented by the extended antenna-carrier (eAxC) ID specified in the O-RAN protocol. This embodiment of the application does not limit this.

[0370] In some cases, the first information may be carried in separate control plane signaling (such as O-RAN CP messages) sent by the DU to the RU, or separate management plane (MP) signaling (such as O-RAN MP messages) sent by the RU to the DU.

[0371] S303, Functional entity B processes the second data according to the data processing method corresponding to the first identifier to obtain the first data.

[0372] In the following example, functional entity B can be a DU. Functional entity B can skip or bypass the corresponding function for the data corresponding to the identifier based on the functional characteristics supported by different RU IDs, cell IDs, UE IDs, PDU session IDs, DRB IDs, QoS flow IDs, or packet IDs, or the data processing method of the associated DU. One implementation is that functional entity B internally knows the entire processing procedure of each data packet from its reception by the CU until it is sent to functional entity A. Functional entity B can determine the PDU session ID, DRB ID, QoS flow ID, or packet identifier associated with each data packet received by functional entity A through methods such as packet tagging.

[0373] In some examples, for the processing of packets belonging to different QoS flows, CU and DU perform a one-to-one mapping of QoS flows to DRBs to avoid packets from multiple QoS flows being mapped to the same DRB, which would cause these multiple packets to be processed by the MAC layer and form a transport block (TB) that cannot be distinguished at the Low-PHY layer.

[0374] For example, for scenarios supporting massive MIMO and bandwidths greater than a first threshold, and scenarios supporting DSS signal processing, functional entity B can perform scrambling functions and higher-level functions. Functional entity B can skip SRS BF, SU BF, and / or MU BF functions.

[0375] For example, in scenarios supporting AI4RAN and DL CoMP signal processing, functional entity B can perform SRS BF (or AI-based SRS BF), SU BF (or AI-based SU BF), and / or MU BF (or AI-based MU BF).

[0376] In the above example, functional entity B can be a RU (Remote Root). Functional entity B can skip or bypass the corresponding function based on the functional characteristics supported by different RU IDs, cell IDs, UE IDs, PDU session IDs, DRB IDs, QoS flow IDs, or packet IDs, or the data processing method of the associated DU. One implementation is that the UE's Low-PHY layer marks uplink data packets sent to functional entity B with identifiers for PDU sessions, DRBs, QoS flows, or data packets. The UE sends uplink data packets to functional entity B via the air interface, and the low-PHY layer of functional entity B can recognize this identifier. For example, the UE's low-PHY layer adds the above identifier to the header of the generated symbol message before or after performing the iFFT transformation. Correspondingly, the low-PHY layer of functional entity B can recognize this identifier before or after performing the FFT transformation. Similarly, for data packets belonging to different QoS flows, the UE performs a one-to-one mapping from QoS flow to DRB to avoid multiple QoS flow data packets being mapped to the same DRB and becoming indistinguishable.

[0377] For example, for scenarios supporting massive MIMO and bandwidth greater than the first threshold, as well as scenarios supporting DSS signal processing, functional entity B can perform equalization functions, second channel estimation functions, UL BF functions, and even lower-level functions.

[0378] For example, for scenarios supporting AI4RAN, UL CoMP signal processing, and duplex signal processing, functional entity B can perform the first channel estimation function, UL BF function, RE demapping function, and previous lower-level functions. Functional entity B can skip the second channel estimation function and equalization function.

[0379] For example, in a sensing signal processing scenario, functional entity B can perform RE demapping and even lower-level functions. Functional entity B can skip the first channel estimation function, UL BF function, second channel estimation function, and equalization function.

[0380] S304, functional entity B sends first data carrying a first identifier to functional entity A. Accordingly, functional entity A receives the first data carrying the first identifier from functional entity B.

[0381] For example, the first data carries the RU ID, cell ID, UE ID, PDU session ID, DRB ID, QoS flow ID, or packet ID. The first identifier can be indicated by an IQ data transmission message sequence identifier (such as ecpriPcid or PC_ID), an IQ data transmission message identifier (such as ecpriSeqid or SEQ_ID), or an eAxC ID, and is carried in the eCPRI packet header.

[0382] S305, Functional entity A processes the first data according to the data processing method corresponding to the first identifier.

[0383] For example, functional entity A receives the first data and reads the header information. Based on the RU ID, cell ID, UE ID, PDU session ID, DRB ID, QoS flow ID or packet ID carried in the packet header (such as the eCPRI header), and the functional characteristics or associated data processing methods supported by that identifier, functional entity A performs the corresponding function on the first data.

[0384] When the first data is upstream data, there are several processing methods:

[0385] 1) For scenarios supporting massive MIMO and bandwidth greater than the first threshold, as well as scenarios supporting DSS signal processing, functional entity A skips the second channel estimation function and equalization function. Functional entity A performs IDFT and higher-level functions.

[0386] 2) For AI4RAN, UL CoMP signal processing, and duplex signal processing scenarios, functional entity A performs second channel estimation (or AI-based second channel estimation), equalization (or AI-based equalization), IDFT, and subsequent higher-level functions.

[0387] 3) For the sensing signal processing scenario. Functional entity A performs the sensing LS function and subsequent higher-level functions.

[0388] When the first data is downlink data, the following processing methods exist:

[0389] 4) For scenarios supporting massive MIMO and bandwidths greater than the first threshold, as well as scenarios supporting DSS signal processing, functional entity A performs modulation and subsequent lower-level functions. Functional entity A performs SRS BF, SU BF, and / or MU BF functions.

[0390] 5) For AI4RAN and DL CoMP signal processing scenarios, functional entity A skips the SRS BF, SU BF, and / or MU BF functions.

[0391] The embodiments of this application can also be extended to other ways of dividing functional entities, and different data processing methods may be applicable to different data for different functional entities. The embodiments of this application are not limited here.

[0392] The above example provides a fronthaul splitting architecture that supports bypassing specific functions. On one hand, the DU sends information about the communication scenarios or associated data processing methods supported by different first identifiers to the RU. This enables the RU to perform skip / bypass specific functions on the data corresponding to the first identifier. On the other hand, the DU or RU performs skip / bypass specific functions on the data corresponding to the first identifier based on the first identifier carried in the data packet, and can correctly complete the remaining function processing of the data packet. This satisfies the requirements for bypassing data processing methods or functions of DU and RU in various communication scenarios. The communication scenarios may include at least one of the following: scenarios supporting massive MIMO and bandwidth greater than a first threshold, scenarios supporting DSS signal processing, UL CoMP signal processing, DL CoMP signal processing, AI4RAN, sensing signal processing, and duplex signal processing.

[0393] The division of different functional entities described in Figures 14 to 16 above may be dynamically adjusted. However, in some scenarios, the division of different functional entities may be relatively static and fixed. In such cases, it is still necessary for the functional entities to be able to accommodate the data processing requirements of different communication scenarios. Figures 17 and 18 illustrate one possible division of functional entities.

[0394] For example, as shown in Figure 17, the physical layer protocol function division between the first functional entity and the second functional entity is based on the division between the scrambling function and the modulation function, i.e., division method A in Figure 17. The SRS BF function (or AI-based SRS BF function), SU BF function (or AI-based SU BF function), and / or MU BF function (or AI-based MU BF function) can be deployed on either the first or second functional entity; this embodiment does not limit this. Of course, since this embodiment uses a relatively fixed division method, the functional modules corresponding to the SRS BF function, SU BF function, and / or MU BF function can be deployed on a specific functional entity. Of course, in other examples, division methods B, C, or any possible division method shown in Figure 7 can also be used; this embodiment does not limit this.

[0395] It is understandable that deploying SRS BF (or AI-based SRS BF), SU BF (or AI-based SU BF), and / or MU BF (or AI-based MU BF) functions on relatively higher-level functional entities enables deep learning collaboration. Conversely, deploying SRS BF (or AI-based SRS BF), SU BF (or AI-based SU BF), and / or MU BF (or AI-based MU BF) functions on relatively lower-level functional entities can reduce the traffic on the fronthaul interface.

[0396] For example, as shown in Figure 18, the physical layer protocol function division between the first functional entity and the second functional entity is between the second channel estimation function and the UL BF function. Alternatively, the division can be between the second channel estimation function and the RE demapping function. In this case, the functional module used to implement the RE demapping function can also implement the UL BF function after implementing the RE demapping function. Specifically, whether to deploy the corresponding UL BF functional module can be selected according to the actual situation, and this application embodiment does not limit it.

[0397] Figure 18 illustrates two possible second functional entities: functional entity B1 and functional entity B2. The difference lies in that functional entity B1 may optionally deploy a UL BF functional module, while functional entity B2 typically deploys a UL BF functional module and a first channel estimation functional module.

[0398] In the uplink communication scenario shown in Figure 18, there may be several situations.

[0399] Scenario 1:

[0400] The functional entity A and functional entity B2 are divided between the second channel estimation function and the UL BF function. This is to support UL CoMP signal processing scenarios, duplex signal processing scenarios, and AI4RAN scenarios, etc.

[0401] Scenario 2:

[0402] To allow functional entity A to interface with functional entity B1 to support DSS functionality, a function bypass execution method is introduced in functional entity A. That is, functional entity A skips the second channel estimation function and equalization function when receiving uplink data from the shared functional entity B1, and performs subsequent functions such as IDFT.

[0403] Scenario 3:

[0404] To support sensing signal processing scenarios, functional entity B2 bypasses or skips the UL BF function and the first channel estimation function for UL BF for sensing symbol data. Functional entity A performs the sensing LS function and subsequent functions on the first data from functional entity B2.

[0405] The above embodiments provide a unified underlying segmentation architecture that takes into account the data processing requirements of different data in multiple communication scenarios, thereby reducing the complexity of signal processing on functional entities.

[0406] Figure 19 is a schematic diagram of another communication scenario provided by an embodiment of this application.

[0407] Considering that the aforementioned embodiments can also be applied to the O-RAN network architecture, Figure 19 illustrates a scenario under the O-RAN architecture. In this O-RAN architecture, access network devices can be divided into three functional entities: O-RU, O-DU, and O-CU. The O-RU is similar to the aforementioned RU, the O-DU is similar to the aforementioned DU, and the O-CU is similar to the aforementioned CU. The interfaces between these functional entities can be referred to the descriptions in the aforementioned embodiments, and will not be repeated here. The O-RAN network architecture may also include a near-real-time RAN intelligent controller (RIC) and service management and orchestration (SMO).

[0408] The near real-time RIC is primarily used to collect network information and perform necessary optimization tasks. The near real-time RIC communicates with the O-CU and O-DU via the E2 interface. The near real-time RIC may include a QoS management module, a radio connection management module, an interference management module, and a mobility management module.

[0409] The SMO can include multiple functional modules, such as non-real-time RIC, configuration, policy, design, and inventory modules. The main functions of the SMO can include cloud infrastructure operation, administration, and maintenance (OAM). For example, it can operate, maintain, and manage cloud infrastructure through the O2 interface. The SMO can also operate, maintain, and manage the RAN through the O1 interface. The SMO can also include a non-real-time RIC, such as one that combines artificial intelligence (AI) and big data analytics to achieve non-real-time macro-control and intervention of the O-RAN through the A1 interface. Each functional entity in the O-RAN can function as an independent entity, communicating with the SMO independently using the O1 interface. In some examples, the SMO and near-real-time RIC can communicate via either the A1 or O1 interface; the appropriate communication path can be selected based on the specific circumstances, which will not be elaborated further in this embodiment.

[0410] The following section, using Figures 20 and 21, describes how to implement the above solution in the O-RAN scenario.

[0411] Figure 20 illustrates the partitioning architecture among different functional entities in a downlink O-RAN scenario. This architecture satisfies the O-RAN Cat A and O-RAN Cat B scenarios specified in the O-RAN protocol. Furthermore, based on the functional entities in these scenarios, it further supports scenarios requiring large-scale MIMO and bandwidth exceeding a first threshold by bypassing some functions. As shown in Figure 20, modulation, layer mapping, precoding, and RE mapping functions can be flexibly selected to be executed on the O-RU and O-DU.

[0412] Figure 21 is a schematic diagram of a communication method provided by an embodiment of this application. This communication process can be applied to, but is not limited to, the communication scenarios shown in Figures 1 and 11. This method can be applied to LTE, LTE FDD systems, LTE TDD, 5G systems or NR systems, subsequent evolving communication systems (such as future communication systems), V2X (where V2X can include V2N, V2V, V2I, V2P, etc.), LTE-V, vehicle-to-everything (V2X), MTC, IoT, LTE-M, M2M, D2D, and other wireless communication scenarios. The O-DU and O-RU involved in the embodiments of this application can be network devices. The O-DU and O-RU can be deployed on the same network device or on different network devices; this is not limited in the embodiments of this application. In the embodiments of this application, the network device can generally be considered an access network device. Of course, in some cases, the network device can also be a core network device. The method can include the following steps:

[0413] S401, O-DU and O-RU perform functional initialization configuration.

[0414] For example, the functions of an O-DU may include scrambling, modulation, layer mapping, precoding, RE mapping, and one or more higher-level functions preceding the scrambling function. Similarly, the functions of an O-RU may include modulation, layer mapping, precoding, and lower-level functions following the precoding function.

[0415] Regarding how the O-DU and O-RU obtain information related to initialization, one possibility is that the device itself generates the information, another possibility is that it receives information sent from the O-CU, or it may be sent by the near real-time RIC or SMO. This application does not limit the specific information provided in this embodiment.

[0416] It is understandable that if different functions are divided at the RU granularity, the PHY layer protocol functions of different RUs may differ.

[0417] S402, the O-DU sends the first information to the O-RU. Correspondingly, the O-RU receives the first information from the O-DU. Alternatively, the O-RU sends the first information to the O-DU. Correspondingly, the O-DU receives the first information from the O-RU.

[0418] For example, the O-DU sends to the O-RU information about the functional characteristics supported by at least one of the following types of identifiers: RU ID, cell ID, UE ID, PDU session ID, DRB ID, QoS flow ID, or packet ID, or the associated O-DU data processing method and O-RU data processing method. The functional characteristics information includes, as mentioned above, scenarios such as large-scale MIMO and bandwidth exceeding a first threshold, O-RAN Cat A scenarios, and O-RAN Cat B scenarios. The data processing methods of the DU and RU may include the corresponding functional entities performing certain functions or skipping (or bypassing) certain functions.

[0419] For O-RAN Cat A scenarios:

[0420] The O-DU performs scrambling, modulation, layer mapping, precoding, RE mapping, and functions at higher levels before scrambling. The O-RU skips modulation, layer mapping, precoding, and RE mapping; it performs iFFT, adds CP, and then performs functions at lower levels.

[0421] For O-RAN Cat B scenarios:

[0422] The O-DU performs scrambling, modulation, layer mapping, RE mapping, and functions at higher layers prior to scrambling. The O-DU skips precoding. The O-RU skips modulation, layer mapping, and resource mapping. The O-RU performs precoding, iFFT, CP addition, and functions at lower layers.

[0423] For scenarios that support massive MIMO and bandwidth greater than the first threshold:

[0424] The O-DU performs scrambling and subsequent higher-level functions. The O-DU skips modulation, layer mapping, precoding, and RE mapping functions. The O-RU performs modulation and subsequent lower-level functions.

[0425] In some cases, the first information may be carried in separate control plane signaling (such as an O-RAN CP message) sent by the O-DU to the O-RU, or separate management plane signaling (such as an O-RAN MP message) sent by the O-RU to the O-DU.

[0426] S403, O-DU processes the second data according to the data processing method corresponding to the first identifier to obtain the first data.

[0427] For example, in the O-RAN Cat A scenario, the O-DU performs scrambling, modulation, layer mapping, precoding, RE mapping, and higher-level functions preceding the scrambling function.

[0428] For example, in the O-RAN Cat B scenario, the O-DU performs scrambling, modulation, layer mapping, RE mapping, and functions at higher layers before scrambling, while skipping precoding.

[0429] For example, it supports large-scale MIMO and scenarios with bandwidth greater than the first threshold. The O-DU performs scrambling and higher-level functions, skipping modulation, layer mapping, precoding, and RE mapping functions.

[0430] S404, the O-DU sends first data carrying a first identifier to the O-RU. Correspondingly, the O-RU receives the first data carrying the first identifier from the O-DU.

[0431] The implementation process of S404 is similar to that of S304, except that the execution subject is different. For details, please refer to the relevant description of S304. This application embodiment will not repeat the details here.

[0432] S405, O-RU processes the first data according to the data processing method corresponding to the first identifier.

[0433] For example, the O-RU receives the first data and reads the header information. Based on the RU ID, cell ID, UE ID, PDU session ID, DRB ID, QoS flow ID or packet ID carried in the packet header (such as the eCPRI header), and the functional characteristics or associated data processing methods supported by that identifier, the O-RU performs the corresponding function on the first data.

[0434] The following processing methods exist:

[0435] 6) For scenarios supporting O-RAN Cat A, O-RU skips modulation, layer mapping, precoding and RE mapping functions, while O-RAN performs iFFT, adds CP function and subsequent lower-level functions.

[0436] 7) For scenarios supporting O-RAN Cat B, the O-RU skips the modulation function, layer mapping function and RE mapping function, and performs the precoding function, iFFT function, CP addition function and subsequent lower-level functions.

[0437] 8) For scenarios that support large-scale MIMO and bandwidth greater than the first threshold, the O-RU performs modulation functions and subsequent lower-level functions.

[0438] The O-RAN architecture in the above embodiments can support partial function bypass. It not only meets the data processing requirements of each functional entity in scenarios with large-scale MIMO and bandwidth greater than a first threshold, but also meets the data processing requirements of each functional entity in O-RAN Cat A and O-RAN Cat B scenarios as specified in the O-RAN protocol.

[0439] It is understood that each of the above embodiments of this application can be implemented independently or in combination with each other; there is no absolute subordinate relationship between the embodiments, and they can be combined with each other under any conditions to obtain the corresponding effect.

[0440] It is understood that, in order to achieve the functions in the above embodiments, the network device includes hardware structures and / or software modules corresponding to the execution of 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.

[0441] Figures 22 and 23 are schematic diagrams of possible communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of the first or second functional entity 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 the RAN node 110 shown in Figure 1, wherein the RAN node can also be called an access network device or a network device. The communication device can also be a module (such as a chip) applied to the network device.

[0442] In this embodiment of the application, the device for implementing the function of the network device can be the network device itself, or it can be a device that enables the network device to implement the function, such as a chip system. The device can be installed in the network device or used in conjunction with the network device.

[0443] In this embodiment of the application, the chip system may be composed of chips, or it may include chips and other discrete devices.

[0444] As shown in Figure 22, the communication device 2200 includes a processing unit 2210 and a transceiver unit 2220. The communication device 2200 is used to implement the functions of the network device in the method embodiments shown in Figures 12, 13, 16, and 21.

[0445] When the communication device 2200 is used to implement the function of the first functional entity in the method embodiment shown in FIG12: the transceiver unit 2220 is used to receive first data. The processing unit 2210 is used to process the first data according to the data processing method corresponding to the first data. Alternatively, the transceiver unit 2220 is used to send the first data.

[0446] When the communication device 2200 is used to implement the function of the first functional entity in the method embodiment shown in FIG13: the transceiver unit 2220 is used to receive first data from the second functional entity. The processing unit 2210 is used to process the first data according to the data type of the first data using the target data processing method corresponding to the data type. Alternatively, the processing unit 2210 is used to process the first data according to the second physical layer protocol function using the target data processing method.

[0447] For a more detailed description of the processing unit 2210 and the transceiver unit 2220, please refer to the relevant description of the method embodiments shown in Figures 12, 13, 16, and 21.

[0448] As shown in Figure 23, the communication device 2300 includes a processor 2310 and an interface circuit 2320. The processor 2310 and the interface circuit 2320 are coupled together. It is understood that the interface circuit 2320 can be a transceiver or an input / output interface. Optionally, the communication device 2300 may also include a memory 2330 for storing instructions executed by the processor 2310, or storing input data required by the processor 2310 to execute instructions, or storing data generated after the processor 2310 executes instructions. Sometimes, the interface circuit 2320 can also be understood as part of the processor 2310, in which case the communication device 2300 includes the processor 2310.

[0449] When the communication device 2300 is used to implement the methods shown in FIG12, FIG13, FIG16 and FIG21, the processor 2310 is used to implement the functions of the processing unit 2210, and the interface circuit 2320 is used to implement the functions of the transceiver unit 2220.

[0450] When the aforementioned communication device is a chip applied to an access network device, the access network device chip implements the functions of the access network device in the above method embodiments. The access network device chip receives information from a terminal or core network device, which can be understood as the information being first received by other modules (such as radio frequency modules or antennas) in the access network device, and then sent to the access network device chip by these modules. The access network device chip sends information to a terminal or core network device, which can be understood as the information being sent down to other modules (such as radio frequency modules or antennas) in the terminal or core network device, and then sent back to the terminal or core network device by these modules.

[0451] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be RAN nodes or terminals, or modules within RAN nodes or terminals. Information transmission and reception can be between RAN nodes and terminals, such as between a base station and a terminal; between two RAN nodes, such as between a CU and a DU; or between different modules within a single device, such as between a terminal chip and other modules of the terminal, or between a base station chip and other modules of the base station.

[0452] It is understood that the processor in the embodiments of this application can be a central processing unit, or other general-purpose processors, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, 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.

[0453] 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 application-specific integrated circuits (ASICs). Alternatively, the ASIC can reside in a base station or terminal. The processor and storage medium can also exist as discrete components in a base station or terminal.

[0454] 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. The 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 entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program 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 that a computer can access 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 may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0455] 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.

[0456] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects. "Including at least one of A, B, and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C.

[0457] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0458] In this application, the base station sends downlink signals or downlink information to the terminal, with the downlink information carried on the downlink channel; the terminal sends uplink signals or uplink information to the base station, with the uplink information carried on the uplink channel. To communicate with the base station, the terminal needs to establish a radio connection on a cell controlled by the base station. The cell with which the terminal has established a radio connection is called the terminal's serving cell. When the terminal communicates with this serving cell, it is also susceptible to interference from signals from neighboring cells.

[0459] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0460] The terms "first" and "second," etc., used in the specification and drawings of the embodiments of this application are used to distinguish different objects or to distinguish different processing of the same object. The terms "first" and "second," etc., can distinguish identical or similar items with substantially the same function and effect. For example, "first device" and "second device" are merely to distinguish different devices and do not limit their order. Those skilled in the art will understand that the terms "first" and "second," etc., do not limit the quantity or execution order, and that "first" and "second," etc., do not necessarily imply that they are different.

[0461] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of the embodiments of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0462] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0463] It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of the embodiments of this application. Therefore, the various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of the embodiments of this application, the sequence number of each process does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0464] It is understood that in the embodiments of this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a time, nor do they require a judgment action during implementation, nor do they imply any other limitations.

[0465] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0466] In the embodiments of this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, and in the various implementation methods / methods / implementations within each embodiment, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments and between the various implementation methods / methods / implementations within each embodiment are consistent and can be mutually referenced. The technical features in different embodiments and the various implementation methods / methods / implementations within each embodiment can be combined to form new embodiments, implementation methods, methods, or implementation approaches based on their inherent logical relationships. The following descriptions of the embodiments of this application do not constitute a limitation on the scope of protection of the embodiments of this application.

Claims

1. A communication method characterized by comprising: The method is applied to a first function entity, the first function entity includes N first data processing function modules, the first data processing function modules are used to implement first data processing functions, N is a positive integer, and the method includes: receiving first data, wherein different first data correspond to different data processing modes, the data processing modes include executing M1 first data processing functions and / or skipping M2 first data processing functions, the M1 first data processing functions executed by different data processing modes are partially the same or completely different, and the M2 first data processing functions skipped by different data processing modes are partially the same or completely different, and the sum of M1 and M2 is equal to N; processing the first data according to the data processing mode corresponding to the first data; or, sending the first data.

2. The method of claim 1, wherein, The first data carries a first identifier, and the data processing modes corresponding to different first data are different, including that the data processing modes corresponding to first data of different first identifiers are different.

3. The method of claim 2, wherein, The method further includes at least one of the following steps: generating first information, wherein the first information is used to indicate an association relationship between the first identifier and a data processing scenario, and / or an association relationship between the first identifier and a data processing mode, wherein different data processing modes are associated with different data processing scenarios; sending the first information; or receiving the first information.

4. The method of claim 3, wherein, The data processing scenario includes at least one of the following scenarios: a scenario supporting large-scale multiple-input multiple-output (MIMO) and a bandwidth greater than a first threshold; a dynamic spectrum sharing (DSS) signal processing scenario; an artificial intelligence for radio access network (AI4RAN) scenario; an uplink coordinated multi-point (UL CoMP) signal processing scenario; a downlink coordinated multi-point (DL CoMP) signal processing scenario; a duplex signal processing scenario; or a sensing signal processing scenario.

5. The method according to any one of claims 2-4, characterized in that, The first identifier includes: a first type of first identifier used to indicate one in-phase and quadrature (IQ) data message; and / or a second type of first identifier used to indicate a group of IQ data messages, the group of IQ data messages including a plurality of IQ data messages.

6. The method according to any one of claims 2-5, characterized in that, The first identifier includes at least one of the following: an identifier of a function entity, the function entity including the first function entity; an identifier of a cell; an identifier of a terminal; an identifier of a service flow; or an identifier of a radio resource.

7. The method of claim 6, wherein, The identifier of the function entity includes at least one of the following: an identifier of a centralized unit (CU); an identifier of a distributed unit (DU); or an identifier of a radio frequency unit (RU).

8. The method of claim 6, wherein, The identifier of the service flow includes at least one of the following: an identifier of a data radio bearer (DRB); an identifier of a protocol data unit (PDU) session; an identifier of a quality of service (QoS); or an identifier of a data packet.

9. The method of claim 6, wherein, The identifier of the radio resource includes at least one of the following: an identifier of a physical channel; an identifier of an antenna port; an identifier of a symbol; an identifier of a time slot; an identifier of a frame; an identifier of a subframe; an identifier of a beam; or an identifier of a frequency domain resource.

10. The method according to any one of claims 2-9, characterized in that, The first identifier is used to indicate that the first data is processed by M1 first data processing functions, and / or the first identifier is used to indicate that the first data needs to be processed by M2 first data processing functions.

11. The method according to any one of claims 1-10, characterized in that, The first data processing function module comprises at least one of: a function module for uplink data processing; a function module for downlink data processing; a function module for generating downlink precoding parameters for a single user; a function module for generating downlink precoding parameters for a single user based on artificial intelligence (AI); a function module for generating downlink precoding parameters for multiple users; a function module for generating downlink precoding parameters for multiple users based on AI; a function of generating downlink precoding parameters based on uplink reference signal measurement; a function of generating downlink precoding parameters based on AI and uplink reference signal measurement; or a function module for processing sensing data.

12. The method of claim 11, wherein, The function module for uplink data processing comprises at least one of: a resource element (RE) demapping function module; a first channel estimation function module, wherein the channel estimation result obtained by the first channel estimation function module is used for uplink signal combination; a function module for implementing uplink signal combination; a second channel estimation function module, wherein the channel estimation result obtained by the second channel estimation function module is used for signal equalization; an AI-based second channel estimation function module; an equalization function module; or an AI-based equalization function module. The function module for downlink data processing comprises at least one of:

13. The method of claim 11, wherein, a modulation function module; a layer mapping function module; or a precoding function module. The function module for processing sensing data comprises at least one of:

14. The method of claim 11, wherein, a sensing least square (LS) function module for frequency domain; a sensing LS function module for time domain; or a sensing range velocity angle (RVA) spectrum estimation function module. The first identifier is also used to indicate that the first data is sensing symbol data or communication symbol data.

15. The method of any of claims 2-10, wherein, The method is applied to a first function entity, wherein the first function entity is used to implement a first physical layer protocol function, and the method comprises:

16. A method of communication, comprising: receiving first data from a second function entity, wherein the second function entity is used to implement a second physical layer protocol function, and the first physical layer protocol function and the second physical layer protocol function constitute a complete physical layer protocol function; processing the first data by using a target data processing mode corresponding to a data type of the first data according to the data type of the first data; or processing the first data by using a target data processing mode according to the second physical layer protocol function, wherein the target data processing mode corresponding to different second physical layer protocol functions is different; wherein the target data processing mode comprises executing one or more first physical layer protocol functions, and / or skipping one or more first physical layer protocol functions, and the one or more first physical layer protocol functions executed by different target data processing modes are partially the same or completely different, and the one or more first physical layer protocol functions skipped by different target data processing modes are partially the same or completely different. ​ 17. The method of claim 16, wherein, The physical layer protocol function division manner between the first physical layer protocol function and the second physical layer protocol function comprises at least one of the following: Division between scrambling function and modulation function; Division between second channel estimation function and function for implementing uplink signal combination, wherein the channel estimation result obtained through the second channel estimation function is used for signal equalization; Division between equalization function and inverse discrete Fourier transform (IDFT) function; or Division between the second channel estimation function and equalization function.

18. The method of claim 16 or 17, wherein, The second function entity comprises at least one of the following: Second target entity with uplink signal combination function, second channel estimation function and equalization function; Second target entity with uplink signal combination function, second channel estimation function and equalization function; or Second target entity with uplink signal combination function.

19. The method of claim 18, wherein, The second function entity has uplink signal combination function, second channel estimation function and equalization function, and the target data processing manner comprises skipping the second channel estimation function and the equalization function.

20. The method of any of claims 16-19, wherein, The data type of the first data comprises perceptual symbol data type, and the target data processing manner comprises executing at least one of the following first physical layer protocol functions: Perceptual least square (LS) function for frequency domain; Perceptual LS function for time domain; or Perceptual range velocity angle (RVA) spectrum estimation function.

21. The method of claim 18, wherein, The second function entity has uplink signal combination function, the data type of the first data comprises perceptual symbol data type, and the data processing function of the second target entity comprises skipping the uplink signal combination function.

22. The method of any of claims 16-21, wherein, The first data is downlink data, and the first physical layer protocol function and / or the second physical layer protocol function comprises at least one of the following functions: Function for generating downlink precoding parameters for single user; Function for generating downlink precoding parameters for multiple users; or Function for generating downlink precoding parameters based on uplink reference signal measurement.

23. A communication system, characterized by The system comprises a first function entity and a second function entity, the first function entity comprises N first data processing function modules, the first data processing function modules are used for implementing first data processing functions, and N is a positive integer, The second function entity is used for sending first data to the first function entity, wherein different first data correspond to different data processing manners, the data processing manner comprises executing M1 first data processing functions and / or skipping M2 first data processing functions, the M1 first data processing functions executed by different data processing manners are partially same or completely different, and the M2 first data processing functions skipped by different data processing manners are partially same or completely different, and the sum of M1 and M2 is equal to N; the first function entity is used for processing the first data according to the data processing manner corresponding to the first data; or The first function entity is used for sending the first data to the second function entity.

24. A communication system, characterized by The system comprises a first functional entity and a second functional entity, the first functional entity is configured to implement a first physical layer protocol function, the second functional entity is configured to implement a second physical layer protocol function, the first physical layer protocol function and the second physical layer protocol function constitute a complete physical layer protocol function, The second functional entity is further configured to send first data to the first functional entity; The first functional entity is further configured to process the first data by using a target data processing mode corresponding to a data type of the first data according to the data type; or The first functional entity is further configured to process the first data by using a target data processing mode according to the second physical layer protocol function, and the target data processing mode corresponding to different second physical layer protocol functions is different; The target data processing mode comprises executing one or more first physical layer protocol functions and / or skipping one or more first physical layer protocol functions, and one or more first physical layer protocol functions executed by different target data processing modes are partially same or completely different, and one or more first physical layer protocol functions skipped by different target data processing modes are partially same or completely different.

25. A communications device, characterized by A module for executing the method of any one of claims 1 to 15, or a module for executing the method of any one of claims 16 to 22.

26. A communications device, characterized by A processor and an interface circuit, the interface circuit is configured to receive signals from other communication devices and transmit signals to the processor or send signals from the processor to other communication devices, the processor is configured to implement the method of any one of claims 1 to 15 or the method of any one of claims 16 to 22 by logic circuit or executing code instructions.

27. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, when the computer program or instructions are executed by the communication device, the method of any one of claims 1 to 15 is implemented, or the method of any one of claims 16 to 22 is implemented.

28. A computer program product comprising computer programs or instructions, characterized in that, The computer program or instructions are executed by the communication device to implement the method of any one of claims 1 to 15, or implement the method of any one of claims 16 to 22.

Images