Communication protocol function determination method and apparatus

Abstract

Provided in the present application are a network communication protocol function determination method and an apparatus. The method comprises: determining first information, wherein the first information may be used for instructing migrating a first communication protocol functional module to a second functional entity, for example, the first communication protocol functional module may comprise a layer 2 communication protocol functional module and / or a layer 3 communication protocol functional module; and sending the first information to the second functional entity. Alternatively, the method may comprise receiving first information; and, on the basis of the first information, determining to migrate a first communication protocol functional module to a second functional entity. In the present application, a first functional entity can determine to migrate the first communication protocol functional module to the second functional entity, such that the first communication protocol functional module can be flexibly migrated between the first functional entity and the second functional entity, thereby ensuring communication efficiency and reducing resource consumption in situations where communication scenarios flexibly change.

Description

Method and apparatus for determining communication protocol functions

[0001] This application claims priority to Chinese Patent Application No. 202410874381.X, filed on June 29, 2024, entitled "Method and Apparatus for Determining Communication Protocol Functions", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication, and more particularly to a method and apparatus for determining communication protocol functions. Background Technology

[0003] In current communication systems, base station functions can be functionally decomposed into multiple functional entities. Different functional entities are used to implement different communication protocol functions within the base station. For example, a base station can be deployed as two parts: a baseband unit (BBU) and a remote radio unit (RRU). Alternatively, a base station can be divided into two functional entities: a central unit (CU) and a distributed unit (DU). The CU can also be referred to as a centralized unit.

[0004] Different functional entities may have different communication protocol modules deployed on them; however, currently, fixed communication protocol modules are typically configured on different functional entities. When communication scenarios change flexibly, the fixed configuration of communication protocol modules on functional entities cannot adapt to different communication scenarios. For example, communication latency may not be met, leading to greater resource consumption. Summary of the Invention

[0005] This application provides a method and apparatus for determining communication protocol functions. A first functional entity can determine whether to migrate a first communication protocol function module to a second functional entity. This allows the first communication protocol function module to flexibly migrate between the first and second functional entities, thereby ensuring communication efficiency and reducing resource consumption in the face of flexible changes in communication scenarios.

[0006] To achieve the above objectives, this application adopts the following technical solution:

[0007] Firstly, a method for determining network communication protocol functions is provided. This method is applied to a first functional entity, which can be a network device, a component of the network device (e.g., a processor, circuit, chip, or chip system), or a logic module or software capable of implementing all or part of the network device's functions. For ease of description, the following explanation uses an example executed by a network device. The method may include: determining first information; sending the first information to a second functional entity. The first information may be used to instruct the migration of a first communication protocol function module to the second functional entity. For example, the first communication protocol function module may include a layer 2 communication protocol function module and / or a layer 3 communication protocol function module. Alternatively, the method may include receiving the first information; determining the migration of the first communication protocol function module to the second functional entity based on the first information. It is understood that the "migration of the first communication protocol function module" in the embodiments of this application can be considered as the migration of the "first communication protocol function". In the embodiments of this application, "migration" may also be referred to as "switching," "adjustment," "moving," etc. This indicates that the first communication protocol function module (or the first communication protocol function implemented) running in the first functional entity is changed to the first communication protocol function module (or the first communication protocol function implemented) running in the second functional entity.

[0008] The first functional entity of this application can determine whether to migrate the first communication protocol functional module to the second functional entity. This allows the first communication protocol functional module to be flexibly migrated between the first and second functional entities, thereby ensuring communication efficiency and reducing resource consumption in the face of flexible changes in communication scenarios.

[0009] In one possible design, the method may further include sending third information to the second functional entity. The third information may be used to indicate parameters related to the first communication protocol functional module. These parameters related to the first communication protocol functional module may be used to configure the first communication protocol functional module.

[0010] This application allows the first functional entity to obtain corresponding parameters when the first communication protocol functional module is a certain functional module, based on actual conditions. This ensures that the state is synchronized after the functional module is migrated to the second functional entity, improving system stability and guaranteeing the continuity of data transmission.

[0011] In one possible design, when the first functional entity sends the first information, the method may further include: determining the first information based on a first parameter. The first parameter may include at least one of the following: a parameter indicating the service load status of the first functional entity; a parameter indicating the computing power status of the first functional entity; a parameter indicating the energy consumption status of the first functional entity; or a parameter indicating the traffic status of the interface between the first functional entity and the second functional entity.

[0012] This application can use appropriate first parameters to determine the instruction to migrate the first communication protocol function module to the second function entity according to the actual situation, thereby improving the universality of the system.

[0013] In one possible design, the first functional entity is configured with a first communication protocol function module, which can be set to a deactivated state, a deregistered state, or a disabled state.

[0014] In this application, the first functional entity can also activate, deactivate, or disable the first communication protocol function module configured in the first functional entity to avoid resource waste caused by the first functional entity and the second functional entity running the same first communication protocol function module at the same time.

[0015] In one possible design, the method may further include: receiving or generating fourth information. This fourth information can be used to configure the first communication protocol functional module. The fourth information is then sent to the second functional entity.

[0016] In this embodiment, the second functional entity can also be pre-configured with the first communication protocol functional module so that the module does not need to be re-established during subsequent migration, thereby improving communication efficiency.

[0017] In one possible design, the fourth piece of information can be determined based on a first Quality of Service (QoS) parameter. This first QoS parameter can be used to indicate the QoS requirements of the service. Accordingly, a first communication protocol function module is used to meet the QoS requirements of the service.

[0018] This application allows for the configuration of a first communication protocol function module based on the QoS requirements of the service, enabling the functional entity to meet the QoS requirements of the service and ensure user experience during the execution of its corresponding functions.

[0019] In one possible design, the fourth information can configure the first communication protocol functional module based on at least one of the following granularities: granularity based on functional entities; granularity based on cells; granularity based on terminals; or granularity based on services.

[0020] This application can pre-configure the first communication protocol function module with appropriate granularity according to actual conditions, so as to use more appropriate functional entities to run the corresponding communication protocol function module in different scenarios, thereby improving system energy efficiency and service capacity.

[0021] In one possible design, the granularity based on functional entities may include at least one of the following: granularity based on a central unit (CU); granularity based on a distributed unit (DU); or granularity based on a radio unit (RU).

[0022] This application can configure the fourth information with appropriate granularity according to the actual situation, so that each functional entity under different granularities can communicate according to the appropriate communication protocol function, thereby improving the universality of the system.

[0023] In one possible design, the service-based granularity may include at least one of the following: granularity based on data radio bearer (DRB); granularity based on protocol data unit (PDU) sessions; granularity based on QoS; or granularity based on data packets.

[0024] This application can configure the fourth information with appropriate granularity according to the actual situation, so that each functional entity under different granularities can communicate according to the appropriate communication protocol function, thereby improving the universality of the system.

[0025] In one possible design, the first functional entity can be deployed in a CU, DU, or RU.

[0026] This application is applicable to any possible first functional entity based on the actual situation, thereby improving the system's versatility.

[0027] In one possible design, the first communication protocol functional module may include at least one of the following functional modules: a functional module for processing the medium access control (MAC) protocol layer; or a functional module for processing the radio link control (RLC) protocol layer.

[0028] This application can be applied to various functional modules, including the first communication protocol module. By flexibly migrating appropriate communication protocol functional modules according to actual needs, the system's versatility is improved.

[0029] In one possible design, the first communication protocol functional module is a functional module for processing the MAC protocol layer. Parameters related to the first communication protocol functional module may include at least one of the following: a MAC hybrid automatic repeat request (HARQ) process list, frame number, subframe number, resource block (RB) resource allocation, modulation and coding scheme (MCS) order, multi-user pairing information, precoding coefficients for superimposing different data streams supported by multiple-input multiple-output (MIMO), weighting coefficients for superimposing different data streams in MIMO, or RLC sequence number.

[0030] This application can obtain and send appropriate parameters according to the actual situation to ensure the continuity of data processing after the migration of the first communication protocol functional module.

[0031] In one possible design, the first communication protocol functional module is a functional module for processing the RLC protocol layer. Parameters related to the first communication protocol functional module may include at least one of the following: the mapping relationship between the logical channel identifier (LCID) and the logical channel, the mapping relationship between the DRB and the logical channel, the mapping relationship between the logical channel and the transport channel, an ACK flag for packet retransmission, a NACK flag for packet retransmission, an RLC sequence number, and a packet data convergence protocol (PDCP) sequence number. The logical channel can be a channel between the RLC protocol layer and the MAC protocol layer, and the transport channel can be a channel between the MAC protocol layer and the physical (PHY) protocol layer.

[0032] This application can obtain and send appropriate parameters according to the actual situation to ensure the continuity of data processing after the migration of the first communication protocol functional module.

[0033] In one possible design, the second functional entity can be deployed in the CU, DU, or RU.

[0034] This application is applicable to any possible second functional entity based on the actual situation, thereby improving the system's versatility.

[0035] In one possible design, the first communication protocol function module configured in the first functional entity can be in an active or enabled state.

[0036] In this application, the first functional entity may be configured with an activated or enabled first communication protocol functional module. In this case, the first functional entity may decide to migrate the first communication protocol functional module to the second functional entity. By flexibly migrating the first communication protocol function, the first functional entity and the second functional entity can flexibly adapt to different communication scenarios, ensure communication efficiency, and reduce resource consumption.

[0037] In one possible design, the second functional entity may be configured with a first communication protocol functional module. The first communication protocol functional module configured in the second functional entity is used to simulate data processing.

[0038] This application enables the first communication protocol function module to run simultaneously in the first functional entity and the second functional entity, so that the same communication protocol function modules between different functional entities remain synchronized, ensuring a consistent user experience while also guaranteeing business continuity and avoiding packet loss.

[0039] In one possible design, the first communication protocol function module configured in the second functional entity can be in an active or enabled state.

[0040] The second functional entity of this application can be configured with an activated or enabled first communication protocol functional module. In this case, the migration speed and efficiency of the first communication protocol functional module can be improved, and the communication latency can be reduced.

[0041] Secondly, a method for determining network communication protocol functions is provided. This method is applied to a first functional entity, which can be a network device, a component of the network device (e.g., a processor, circuit, chip, or chip system), or a logic module or software capable of implementing all or part of the network device's functions. For ease of description, the following explanation uses an example executed by a network device. The method may include: sending or receiving first information. This first information may be used to instruct the migration of a first communication protocol function module to a second functional entity. For example, the first communication protocol function module may include a layer 2 communication protocol function module and / or a layer 3 communication protocol function module. The first functional entity may be configured with the first communication protocol function module. The method further involves determining a processing method for cached data in the first communication protocol function module, and processing the cached data in the first communication protocol function module based on the processing method.

[0042] This application configures the processing method for cached data in the first communication protocol functional module deployed within the first functional entity during the migration process. This enables the first functional entity to process the cached data of its internally deployed first communication protocol functional module according to this method. This avoids data packet loss, ensures the continuity of data transmission, and improves user experience.

[0043] In one possible design, the method may further include receiving second information. This second information can be used to indicate the method for processing cached data in the first communication protocol functional module.

[0044] This application can also determine the processing method of cached data in the first communication protocol functional module through other devices or functional entities, thereby realizing flexible processing of cached data.

[0045] In one possible design, the cached data in the first communication protocol functional module can be processed in any of the following ways: discarding the cached data in the first communication protocol functional module; or continuing to send the cached data in the first communication protocol functional module; or continuously sending the cached data in the first communication protocol functional module within a first time period, wherein the start time of the first time period is the time when the first communication protocol functional module stops receiving newly arrived data, and the duration of the first time period is a first duration; or determining to discard the remaining unsent cached data based on the remaining unsent cached data packets.

[0046] This application provides a variety of different methods for processing cached data, so that the appropriate processing method can be used to process cached data according to the actual situation, ensuring data processing latency and data transmission stability.

[0047] In one possible design, determining to discard the remaining unsent cached data based on the remaining unsent cached data may include: continuing to send cached data in the first communication protocol functional module until the ratio between the sent cached data and the remaining unsent cached data is greater than or equal to a first threshold; or, continuing to send cached data in the first communication protocol functional module until the ratio between the sent cached data and the cache capacity corresponding to the first communication protocol functional module is greater than or equal to a second threshold; or, continuing to send cached data in the first communication protocol functional module until the ratio between the remaining unsent cached data and the cache capacity corresponding to the first communication protocol functional module is less than or equal to a third threshold.

[0048] This application provides several methods for handling cached data based on the remaining unsent cached data. This allows for the selection of an appropriate method to process cached data according to the actual situation, ensuring data processing latency and data transmission stability.

[0049] In one possible design, the method may also include: stopping the reception of newly arriving data from the first communication protocol functional module.

[0050] This application can prevent the first communication protocol function module that needs to be migrated from continuously receiving newly arrived data, thus preventing data packet loss and ensuring the continuity and stability of data transmission.

[0051] In one possible design, the method may further include sending third information to the second functional entity. The third information may be used to indicate parameters related to the first communication protocol functional module. These parameters related to the first communication protocol functional module may be used to configure the first communication protocol functional module.

[0052] In one possible design, when the first functional entity sends the first information, the method may further include: determining the first information based on a first parameter. The first parameter may include at least one of the following: a parameter indicating the service load status of the first functional entity; a parameter indicating the computing power status of the first functional entity; a parameter indicating the energy consumption status of the first functional entity; or a parameter indicating the traffic status of the interface between the first functional entity and the second functional entity.

[0053] In one possible design, the first functional entity is configured with a first communication protocol function module, which can be set to a deactivated state, a deregistered state, or a disabled state.

[0054] In one possible design, the method may further include: receiving or generating fourth information. This fourth information can be used to configure the first communication protocol functional module. The fourth information is then sent to the second functional entity.

[0055] In one possible design, the fourth piece of information can be determined based on the first QoS parameter. This first QoS parameter can be used to indicate the QoS requirements of the service. Accordingly, the first communication protocol function module is used to meet the QoS requirements of the service.

[0056] In one possible design, the fourth information can configure the first communication protocol functional module based on at least one of the following granularities: granularity based on functional entities; granularity based on cells; granularity based on terminals; or granularity based on services.

[0057] In one possible design scheme, the granularity based on functional entities may include at least one of the following granularities: CU-based granularity; DU-based granularity; or RU-based granularity.

[0058] In one possible design, the service-based granularity may include at least one of the following: DRB-based granularity; PDU session-based granularity; QoS-based granularity; or packet-based granularity.

[0059] In one possible design, the first functional entity can be deployed in a CU, DU, or RU.

[0060] In one possible design, the first communication protocol functional module may include at least one of the following functional modules: a functional module for processing the MAC protocol layer; or, a functional module for processing the RLC protocol layer.

[0061] In one possible design, the first communication protocol functional module is a functional module for processing the MAC protocol layer. The parameters related to the first communication protocol functional module may include at least one of the following: MAC HARQ process list, frame number, subframe number, RB resource allocation, MCS order, multi-user pairing information, precoding coefficients for superimposing different data streams supported by MIMO, weighting coefficients for superimposing different data streams of MIMO, or RLC sequence number.

[0062] In one possible design, the first communication protocol functional module is a functional module for processing the RLC protocol layer. Parameters related to the first communication protocol functional module may include at least one of the following: the mapping relationship between LCID and logical channel, the mapping relationship between DRB and logical channel, the mapping relationship between logical channel and transport channel, an ACK flag for packet retransmission, a NACK flag for packet retransmission, an RLC sequence number, and a PDCP sequence number. The logical channel can be a channel between the RLC protocol layer and the MAC protocol layer, and the transport channel can be a channel between the MAC protocol layer and the PHY protocol layer.

[0063] In one possible design, the second functional entity can be deployed in the CU, DU, or RU.

[0064] In one possible design, the first communication protocol function module configured in the first functional entity can be in an active or enabled state.

[0065] In one possible design, the second functional entity may be configured with a first communication protocol functional module. The first communication protocol functional module configured in the second functional entity is used to simulate data processing.

[0066] In one possible design, the first communication protocol function module configured in the second functional entity can be in an active or enabled state.

[0067] Thirdly, a method for determining network communication protocol functions is provided. This method is applied to a second functional entity, which can be a network device, a component of the network device (e.g., a processor, circuit, chip, or chip system), or a logic module or software capable of implementing all or part of the network device's functions. For ease of description, the following explanation uses an example executed by a network device. The method may include: receiving first information. The first information may be used to instruct the migration of a first communication protocol function module to the second functional entity. For example, the first communication protocol function module may include a layer 2 communication protocol function module and / or a layer 3 communication protocol function module. The method determines the migration of the first communication protocol function module to the second functional entity based on the first information. Alternatively, the method determines the first information and sends the first information to the first functional entity.

[0068] In one possible design, the method may further include: receiving third information from a first functional entity. This third information may be used to indicate parameters related to the first communication protocol functional module. These parameters related to the first communication protocol functional module are used to configure the first communication protocol functional module.

[0069] In one possible design, when the second functional entity sends the first information, the method may further include: determining the first information based on a first parameter. The first parameter may include at least one of the following: a parameter indicating the service load status of the first functional entity; a parameter indicating the computing power status of the first functional entity; a parameter indicating the energy consumption status of the first functional entity; or a parameter indicating the traffic status of the interface between the first and second functional entities.

[0070] In one possible design, the method may further include: receiving or generating fourth information. This fourth information is used to configure the first communication protocol functional module. Generating the first communication protocol functional module based on the fourth information allows the first communication protocol functional module to be set to a deactivated or disabled state.

[0071] In one possible design, the fourth piece of information is determined based on the first QoS parameter. This first QoS parameter can be used to indicate the QoS requirements of the service. Accordingly, the first communication protocol function module can be used to meet the QoS requirements of the service.

[0072] In one possible design, the fourth information can configure the first communication protocol functional module based on at least one of the following granularities: granularity based on functional entities; granularity based on cells; granularity based on terminals; or granularity based on services.

[0073] In one possible design scheme, the granularity based on functional entities may include at least one of the following granularities: CU-based granularity; DU-based granularity; or RU-based granularity.

[0074] In one possible design, the service-based granularity may include at least one of the following: DRB-based granularity; PDU session-based granularity; QoS-based granularity; or packet-based granularity.

[0075] In one possible design, the second functional entity can be deployed in the CU, DU, or RU.

[0076] In one possible design, the first communication protocol functional module may include at least one of the following functional modules: a functional module for processing the MAC protocol layer; or, a functional module for processing the RLC protocol layer.

[0077] In one possible design, the first communication protocol functional module is a functional module for processing the MAC protocol layer. The parameters related to the first communication protocol functional module may include at least one of the following: MAC HARQ process list, frame number, subframe number, RB resource allocation, MCS order, multi-user pairing information, precoding coefficients for superimposing different data streams supported by MIMO, weighting coefficients for superimposing different data streams of MIMO, or RLC sequence number.

[0078] In one possible design, the first communication protocol functional module is a functional module for processing the RLC protocol layer. Parameters related to the first communication protocol functional module may include at least one of the following: the mapping relationship between LCID and logical channel, the mapping relationship between DRB and logical channel, the mapping relationship between logical channel and transport channel, an ACK flag for packet retransmission, a NACK flag for packet retransmission, an RLC sequence number, and a PDCP sequence number. The logical channel can be a channel between the RLC protocol layer and the MAC protocol layer, and the transport channel can be a channel between the MAC protocol layer and the PHY protocol layer.

[0079] In one possible design, the first functional entity can be deployed in a CU, DU, or RU.

[0080] In one possible design, the first communication protocol function module configured in the first functional entity can be in an active or enabled state.

[0081] In one possible design, the second functional entity is configured with a first communication protocol function module. This first communication protocol function module in the second functional entity can be used to simulate data processing.

[0082] In one possible design, the first communication protocol function module configured in the second functional entity can be in an active or enabled state.

[0083] Fourthly, a method for determining network communication protocol functions is provided. This method is applied to a second functional entity, which can be a network device, a component of the network device (e.g., a processor, circuit, chip, or chip system), or a logic module or software capable of implementing all or part of the network device's functions. For ease of description, the following explanation uses an example executed by a network device. The method may include: receiving or sending first information. The first information may be used to instruct the migration of a first communication protocol function module to the second functional entity. For example, the first communication protocol function module may include a layer 2 communication protocol function module and / or a layer 3 communication protocol function module. The first functional entity may be configured with the first communication protocol function module. First data is cached. The first data is data sent to the first communication protocol function module in the first functional entity. The cached first data is then processed.

[0084] In one possible design, the method may further include: determining second information; and sending the second information. The second information may be used to indicate the method for processing cached data in the first communication protocol functional module configured for the first functional entity.

[0085] In one possible design, the cached data in the first communication protocol function module configured by the first functional entity can be processed in any of the following ways: discarding the cached data in the first communication protocol function module; or continuing to send the cached data in the first communication protocol function module; or continuously sending the cached data in the first communication protocol function module within a first time period, wherein the start time of the first time period is the time when the first communication protocol function module stops receiving newly arrived data, and the duration of the first time period is a first duration; or determining to discard the remaining unsent cached data based on the remaining unsent cached data packets.

[0086] In one possible design, determining to discard the remaining unsent cached data based on the remaining unsent cached data may include: continuing to send cached data in the first communication protocol functional module until the ratio between the sent cached data and the remaining unsent cached data is greater than or equal to a first threshold; or, continuing to send cached data in the first communication protocol functional module until the ratio between the sent cached data and the cache capacity corresponding to the first communication protocol functional module is greater than or equal to a second threshold; or, continuing to send cached data in the first communication protocol functional module until the ratio between the remaining unsent cached data and the cache capacity corresponding to the first communication protocol functional module is less than or equal to a third threshold.

[0087] In one possible design, the method may further include: receiving third information from a first functional entity. This third information may be used to indicate parameters related to the first communication protocol functional module. These parameters related to the first communication protocol functional module are used to configure the first communication protocol functional module.

[0088] In one possible design, when the second functional entity sends the first information, the method may further include: determining the first information based on a first parameter. The first parameter may include at least one of the following: a parameter indicating the service load status of the first functional entity; a parameter indicating the computing power status of the first functional entity; a parameter indicating the energy consumption status of the first functional entity; or a parameter indicating the traffic status of the interface between the first and second functional entities.

[0089] In one possible design, the method may further include: receiving or generating fourth information. This fourth information is used to configure the first communication protocol functional module. Generating the first communication protocol functional module based on the fourth information allows the first communication protocol functional module to be set to a deactivated or disabled state.

[0090] In one possible design, the fourth piece of information is determined based on the first QoS parameter. This first QoS parameter can be used to indicate the QoS requirements of the service. Accordingly, the first communication protocol function module can be used to meet the QoS requirements of the service.

[0091] In one possible design, the fourth information can configure the first communication protocol functional module based on at least one of the following granularities: granularity based on functional entities; granularity based on cells; granularity based on terminals; or granularity based on services.

[0092] In one possible design scheme, the granularity based on functional entities may include at least one of the following granularities: CU-based granularity; DU-based granularity; or RU-based granularity.

[0093] In one possible design, the service-based granularity may include at least one of the following: DRB-based granularity; PDU session-based granularity; QoS-based granularity; or packet-based granularity.

[0094] In one possible design, the second functional entity can be deployed in the CU, DU, or RU.

[0095] In one possible design, the first communication protocol functional module may include at least one of the following functional modules: a functional module for processing the MAC protocol layer; or, a functional module for processing the RLC protocol layer.

[0096] In one possible design, the first communication protocol functional module is a functional module for processing the MAC protocol layer. The parameters related to the first communication protocol functional module may include at least one of the following: MAC HARQ process list, frame number, subframe number, RB resource allocation, MCS order, multi-user pairing information, precoding coefficients for superimposing different data streams supported by MIMO, weighting coefficients for superimposing different data streams of MIMO, or RLC sequence number.

[0097] In one possible design, the first communication protocol functional module is a functional module for processing the RLC protocol layer. Parameters related to the first communication protocol functional module may include at least one of the following: the mapping relationship between LCID and logical channel, the mapping relationship between DRB and logical channel, the mapping relationship between logical channel and transport channel, an ACK flag for packet retransmission, a NACK flag for packet retransmission, an RLC sequence number, and a PDCP sequence number. The logical channel can be a channel between the RLC protocol layer and the MAC protocol layer, and the transport channel can be a channel between the MAC protocol layer and the PHY protocol layer.

[0098] In one possible design, the first functional entity can be deployed in a CU, DU, or RU.

[0099] In one possible design, the first communication protocol function module configured in the first functional entity can be in an active or enabled state.

[0100] In one possible design, the second functional entity is configured with a first communication protocol function module. This first communication protocol function module in the second functional entity can be used to simulate data processing.

[0101] In one possible design, the first communication protocol function module configured in the second functional entity can be in an active or enabled state.

[0102] Fifthly, a communication protocol function determination apparatus is provided. This apparatus may deploy a first functional entity, such as a network device, or a communication module within the network device, or a chip within the network device responsible for communication functions, such as a modem chip (also known as a baseband chip), or a system-on-chip (SoC) or system-in-package (SIP) chip containing a modem module. It may also be a logic module or software capable of implementing all or part of the network device's functions. For ease of description, the following explanation uses an example executed by a network device. The apparatus includes: a processing unit for determining first information. The first information may be used to instruct the migration of a first communication protocol function module to a second functional entity. For example, the first communication protocol function module may include a layer 2 communication protocol function module and / or a layer 3 communication protocol function module. A transceiver unit for sending the first information to the second functional entity. Alternatively, a transceiver unit for receiving the first information. A processing unit for determining the migration of the first communication protocol function module to the second functional entity based on the first information.

[0103] In one possible design, the transceiver unit is further configured to: send third information to the second functional entity. This third information may be used to indicate parameters related to the first communication protocol functional module. These parameters related to the first communication protocol functional module may be used to configure the first communication protocol functional module.

[0104] In one possible design, when the first functional entity sends the first information, the processing unit is further configured to: determine the first information based on a first parameter. The first parameter may include at least one of the following: a parameter indicating the service load status of the first functional entity; a parameter indicating the computing power status of the first functional entity; a parameter indicating the energy consumption status of the first functional entity; or a parameter indicating the traffic status of the interface between the first functional entity and the second functional entity.

[0105] In one possible design, the first functional entity is configured with a first communication protocol function module, which can be set to a deactivated state, a deregistered state, or a disabled state.

[0106] In one possible design, the transceiver unit is further configured to receive fourth information; or the processing unit is further configured to generate fourth information. This fourth information can be used to configure the first communication protocol function module. The transceiver unit is also configured to send the fourth information to the second functional entity.

[0107] In one possible design, the fourth piece of information can be determined based on the first QoS parameter. This first QoS parameter can be used to indicate the QoS requirements of the service. Accordingly, the first communication protocol function module is used to meet the QoS requirements of the service.

[0108] In one possible design, the fourth information can configure the first communication protocol functional module based on at least one of the following granularities: granularity based on functional entities; granularity based on cells; granularity based on terminals; or granularity based on services.

[0109] In one possible design scheme, the granularity based on functional entities may include at least one of the following granularities: CU-based granularity; DU-based granularity; or RU-based granularity.

[0110] In one possible design, the service-based granularity may include at least one of the following: DRB-based granularity; PDU session-based granularity; QoS-based granularity; or packet-based granularity.

[0111] In one possible design, the first functional entity can be deployed in a CU, DU, or RU.

[0112] In one possible design, the first communication protocol functional module may include at least one of the following functional modules: a functional module for processing the MAC protocol layer; or, a functional module for processing the RLC protocol layer.

[0113] In one possible design, the first communication protocol functional module is a functional module for processing the MAC protocol layer. The parameters related to the first communication protocol functional module may include at least one of the following: MAC HARQ process list, frame number, subframe number, RB resource allocation, MCS order, multi-user pairing information, precoding coefficients for superimposing different data streams supported by MIMO, weighting coefficients for superimposing different data streams of MIMO, or RLC sequence number.

[0114] In one possible design, the first communication protocol functional module is a functional module for processing the RLC protocol layer. Parameters related to the first communication protocol functional module may include at least one of the following: the mapping relationship between LCID and logical channel, the mapping relationship between DRB and logical channel, the mapping relationship between logical channel and transport channel, an ACK flag for packet retransmission, a NACK flag for packet retransmission, an RLC sequence number, and a PDCP sequence number. The logical channel can be a channel between the RLC protocol layer and the MAC protocol layer, and the transport channel can be a channel between the MAC protocol layer and the PHY protocol layer.

[0115] In one possible design, the second functional entity can be deployed in the CU, DU, or RU.

[0116] In one possible design, the first communication protocol function module configured in the first functional entity can be in an active or enabled state.

[0117] In one possible design, the second functional entity may be configured with a first communication protocol functional module. The first communication protocol functional module configured in the second functional entity is used to simulate data processing.

[0118] In one possible design, the first communication protocol function module configured in the second functional entity can be in an active or enabled state.

[0119] Sixthly, a communication protocol function determination apparatus is provided. This apparatus may be equipped with a first functional entity, such as a network device, a communication module within the network device, or a chip within the network device responsible for communication functions, such as a modem chip (also known as a baseband chip), or a SoC or SIP chip containing a modem module. It may also be a logic module or software capable of implementing all or part of the network device's functions. For ease of description, the following description uses an example executed by a network device. It includes: a transceiver unit for sending or receiving first information. This first information may be used to instruct the migration of a first communication protocol function module to a second functional entity. For example, the first communication protocol function module may include a layer 2 communication protocol function module and / or a layer 3 communication protocol function module. The first functional entity may be configured with the first communication protocol function module. A processing unit is used to determine the processing method for cached data in the first communication protocol function module. The processing unit is also used to process the cached data in the first communication protocol function module based on the processing method.

[0120] In one possible design, the transceiver unit is further configured to: receive second information. This second information can be used to indicate the method for processing cached data in the first communication protocol functional module.

[0121] In one possible design, the cached data in the first communication protocol functional module can be processed in any of the following ways: discarding the cached data in the first communication protocol functional module; or continuing to send the cached data in the first communication protocol functional module; or continuously sending the cached data in the first communication protocol functional module within a first time period, wherein the start time of the first time period is the time when the first communication protocol functional module stops receiving newly arrived data, and the duration of the first time period is a first duration; or determining to discard the remaining unsent cached data based on the remaining unsent cached data packets.

[0122] In one possible design, determining to discard the remaining unsent cached data based on the remaining unsent cached data may include: continuing to send cached data in the first communication protocol functional module until the ratio between the sent cached data and the remaining unsent cached data is greater than or equal to a first threshold; or, continuing to send cached data in the first communication protocol functional module until the ratio between the sent cached data and the cache capacity corresponding to the first communication protocol functional module is greater than or equal to a second threshold; or, continuing to send cached data in the first communication protocol functional module until the ratio between the remaining unsent cached data and the cache capacity corresponding to the first communication protocol functional module is less than or equal to a third threshold.

[0123] In one possible design, the processing unit is also used to: control the transceiver unit to stop receiving newly arriving data from the first communication protocol function module.

[0124] In one possible design, the transceiver unit is further configured to: send third information to the second functional entity. This third information may be used to indicate parameters related to the first communication protocol functional module. These parameters related to the first communication protocol functional module may be used to configure the first communication protocol functional module.

[0125] In one possible design, when the first functional entity sends the first information, the processing unit is further configured to: determine the first information based on a first parameter. The first parameter may include at least one of the following: a parameter indicating the service load status of the first functional entity; a parameter indicating the computing power status of the first functional entity; a parameter indicating the energy consumption status of the first functional entity; or a parameter indicating the traffic status of the interface between the first functional entity and the second functional entity.

[0126] In one possible design, the first functional entity is configured with a first communication protocol function module, which can be set to a deactivated state, a deregistered state, or a disabled state.

[0127] In one possible design, the transceiver unit is further configured to receive fourth information; or the processing unit is further configured to generate fourth information. This fourth information can be used to configure the first communication protocol function module. The transceiver unit is also configured to send the fourth information to the second functional entity.

[0128] In one possible design, the fourth piece of information can be determined based on the first QoS parameter. This first QoS parameter can be used to indicate the QoS requirements of the service. Accordingly, the first communication protocol function module is used to meet the QoS requirements of the service.

[0129] In one possible design, the fourth information can configure the first communication protocol functional module based on at least one of the following granularities: granularity based on functional entities; granularity based on cells; granularity based on terminals; or granularity based on services.

[0130] In one possible design scheme, the granularity based on functional entities may include at least one of the following granularities: CU-based granularity; DU-based granularity; or RU-based granularity.

[0131] In one possible design, the service-based granularity may include at least one of the following: DRB-based granularity; PDU session-based granularity; QoS-based granularity; or packet-based granularity.

[0132] In one possible design, the first functional entity can be deployed in a CU, DU, or RU.

[0133] In one possible design, the first communication protocol functional module may include at least one of the following functional modules: a functional module for processing the MAC protocol layer; or, a functional module for processing the RLC protocol layer.

[0134] In one possible design, the first communication protocol functional module is a functional module for processing the MAC protocol layer. The parameters related to the first communication protocol functional module may include at least one of the following: MAC HARQ process list, frame number, subframe number, RB resource allocation, MCS order, multi-user pairing information, precoding coefficients for superimposing different data streams supported by MIMO, weighting coefficients for superimposing different data streams of MIMO, or RLC sequence number.

[0135] In one possible design, the first communication protocol functional module is a functional module for processing the RLC protocol layer. Parameters related to the first communication protocol functional module may include at least one of the following: the mapping relationship between LCID and logical channel, the mapping relationship between DRB and logical channel, the mapping relationship between logical channel and transport channel, an ACK flag for packet retransmission, a NACK flag for packet retransmission, an RLC sequence number, and a PDCP sequence number. The logical channel can be a channel between the RLC protocol layer and the MAC protocol layer, and the transport channel can be a channel between the MAC protocol layer and the PHY protocol layer.

[0136] In one possible design, the second functional entity can be deployed in the CU, DU, or RU.

[0137] In one possible design, the first communication protocol function module configured in the first functional entity can be in an active or enabled state.

[0138] In one possible design, the second functional entity may be configured with a first communication protocol functional module. The first communication protocol functional module configured in the second functional entity is used to simulate data processing.

[0139] In one possible design, the first communication protocol function module configured in the second functional entity can be in an active or enabled state.

[0140] In a seventh aspect, a communication protocol function determination apparatus is provided. This apparatus may be equipped with a first functional entity, such as a network device, or a communication module within the network device, or a chip within the network device responsible for communication functions, such as a modem chip (also known as a baseband chip), or a SoC or SIP chip containing a modem module. It may also be a logic module or software capable of implementing all or part of the network device's functions. For ease of description, the following description uses an example executed by a network device. It includes: a transceiver unit for receiving first information. This first information may be used to instruct the migration of a first communication protocol function module to a second functional entity. For example, the first communication protocol function module may include a layer 2 communication protocol function module and / or a layer 3 communication protocol function module. A processing unit for determining the migration of the first communication protocol function module to the second functional entity based on the first information. Alternatively, the processing unit is used to determine the first information. A transceiver unit for sending the first information to the first functional entity.

[0141] In one possible design, the transceiver unit is further configured to: receive third information from the first functional entity. This third information may be used to indicate parameters related to the first communication protocol functional module. These parameters related to the first communication protocol functional module are used to configure the first communication protocol functional module.

[0142] In one possible design, when the second functional entity sends the first information, the processing unit is further configured to: determine the first information based on a first parameter. The first parameter may include at least one of the following: a parameter indicating the service load status of the first functional entity; a parameter indicating the computing power status of the first functional entity; a parameter indicating the energy consumption status of the first functional entity; or a parameter indicating the traffic status of the interface between the first and second functional entities.

[0143] In one possible design, the transceiver unit is further configured to: receive fourth information; or the processing unit is further configured to: generate fourth information. The fourth information is used to configure the first communication protocol function module. The processing unit is further configured to: generate the first communication protocol function module based on the fourth information, and may set the first communication protocol function module to a deactivated state or a disabled state.

[0144] In one possible design, the fourth piece of information is determined based on the first QoS parameter. This first QoS parameter can be used to indicate the QoS requirements of the service. Accordingly, the first communication protocol function module can be used to meet the QoS requirements of the service.

[0145] In one possible design, the fourth information can configure the first communication protocol functional module based on at least one of the following granularities: granularity based on functional entities; granularity based on cells; granularity based on terminals; or granularity based on services.

[0146] In one possible design scheme, the granularity based on functional entities may include at least one of the following granularities: CU-based granularity; DU-based granularity; or RU-based granularity.

[0147] In one possible design, the service-based granularity may include at least one of the following: DRB-based granularity; PDU session-based granularity; QoS-based granularity; or packet-based granularity.

[0148] In one possible design, the second functional entity can be deployed in the CU, DU, or RU.

[0149] In one possible design, the first communication protocol functional module may include at least one of the following functional modules: a functional module for processing the MAC protocol layer; or, a functional module for processing the RLC protocol layer.

[0150] In one possible design, the first communication protocol functional module is a functional module for processing the MAC protocol layer. The parameters related to the first communication protocol functional module may include at least one of the following: MAC HARQ process list, frame number, subframe number, RB resource allocation, MCS order, multi-user pairing information, precoding coefficients for superimposing different data streams supported by MIMO, weighting coefficients for superimposing different data streams of MIMO, or RLC sequence number.

[0151] In one possible design, the first communication protocol functional module is a functional module for processing the RLC protocol layer. Parameters related to the first communication protocol functional module may include at least one of the following: the mapping relationship between LCID and logical channel, the mapping relationship between DRB and logical channel, the mapping relationship between logical channel and transport channel, an ACK flag for packet retransmission, a NACK flag for packet retransmission, an RLC sequence number, and a PDCP sequence number. The logical channel can be a channel between the RLC protocol layer and the MAC protocol layer, and the transport channel can be a channel between the MAC protocol layer and the PHY protocol layer.

[0152] In one possible design, the first functional entity can be deployed in a CU, DU, or RU.

[0153] In one possible design, the first communication protocol function module configured in the first functional entity can be in an active or enabled state.

[0154] In one possible design, the second functional entity is configured with a first communication protocol function module. This first communication protocol function module in the second functional entity can be used to simulate data processing.

[0155] In one possible design, the first communication protocol function module configured in the second functional entity can be in an active or enabled state.

[0156] Eighthly, a communication protocol function determination apparatus is provided. This apparatus may be equipped with a first functional entity, such as a network device, a communication module within the network device, or a chip within the network device responsible for communication functions, such as a modem chip (also known as a baseband chip), or a SoC or SIP chip containing a modem module. It may also be a logic module or software capable of implementing all or part of the network device's functions. For ease of description, the following description uses an example executed by a network device. It includes: a transceiver module for receiving or sending first information. This first information may be used to instruct the migration of a first communication protocol function module to a second functional entity. For example, the first communication protocol function module may include a layer 2 communication protocol function module and / or a layer 3 communication protocol function module. The first functional entity may be configured with the first communication protocol function module. A processing unit is used to cache first data. The first data is data sent to the first communication protocol function module in the first functional entity. The processing unit is also used to process the cached first data.

[0157] In one possible design, the processing unit is further configured to determine second information. The transceiver unit is further configured to send the second information. This second information can be used to indicate the method of processing cached data in the first communication protocol function module configured for the first functional entity.

[0158] In one possible design, the cached data in the first communication protocol function module configured by the first functional entity can be processed in any of the following ways: discarding the cached data in the first communication protocol function module; or continuing to send the cached data in the first communication protocol function module; or continuously sending the cached data in the first communication protocol function module within a first time period, wherein the start time of the first time period is the time when the first communication protocol function module stops receiving newly arrived data, and the duration of the first time period is a first duration; or determining to discard the remaining unsent cached data based on the remaining unsent cached data packets.

[0159] In one possible design, determining to discard the remaining unsent cached data based on the remaining unsent cached data may include: continuing to send cached data in the first communication protocol functional module until the ratio between the sent cached data and the remaining unsent cached data is greater than or equal to a first threshold; or, continuing to send cached data in the first communication protocol functional module until the ratio between the sent cached data and the cache capacity corresponding to the first communication protocol functional module is greater than or equal to a second threshold; or, continuing to send cached data in the first communication protocol functional module until the ratio between the remaining unsent cached data and the cache capacity corresponding to the first communication protocol functional module is less than or equal to a third threshold.

[0160] In one possible design, the transceiver unit is further configured to: receive third information from the first functional entity. This third information may be used to indicate parameters related to the first communication protocol functional module. These parameters related to the first communication protocol functional module are used to configure the first communication protocol functional module.

[0161] In one possible design, when the second functional entity sends the first information, the processing unit is further configured to: determine the first information based on a first parameter. The first parameter may include at least one of the following: a parameter indicating the service load status of the first functional entity; a parameter indicating the computing power status of the first functional entity; a parameter indicating the energy consumption status of the first functional entity; or a parameter indicating the traffic status of the interface between the first and second functional entities.

[0162] In one possible design, the transceiver unit is further configured to receive fourth information; or the processing unit is further configured to generate fourth information. This fourth information is used to configure the first communication protocol function module. The processing unit is further configured to generate the first communication protocol function module based on the fourth information, and can set the first communication protocol function module to a deactivated state or a disabled state.

[0163] In one possible design, the fourth piece of information is determined based on the first QoS parameter. This first QoS parameter can be used to indicate the QoS requirements of the service. Accordingly, the first communication protocol function module can be used to meet the QoS requirements of the service.

[0164] In one possible design, the fourth information can configure the first communication protocol functional module based on at least one of the following granularities: granularity based on functional entities; granularity based on cells; granularity based on terminals; or granularity based on services.

[0165] In one possible design scheme, the granularity based on functional entities may include at least one of the following granularities: CU-based granularity; DU-based granularity; or RU-based granularity.

[0166] In one possible design, the service-based granularity may include at least one of the following: DRB-based granularity; PDU session-based granularity; QoS-based granularity; or packet-based granularity.

[0167] In one possible design, the second functional entity can be deployed in the CU, DU, or RU.

[0168] In one possible design, the first communication protocol functional module may include at least one of the following functional modules: a functional module for processing the MAC protocol layer; or, a functional module for processing the RLC protocol layer.

[0169] In one possible design, the first communication protocol functional module is a functional module for processing the MAC protocol layer. The parameters related to the first communication protocol functional module may include at least one of the following: MAC HARQ process list, frame number, subframe number, RB resource allocation, MCS order, multi-user pairing information, precoding coefficients for superimposing different data streams supported by MIMO, weighting coefficients for superimposing different data streams of MIMO, or RLC sequence number.

[0170] In one possible design, the first communication protocol functional module is a functional module for processing the RLC protocol layer. Parameters related to the first communication protocol functional module may include at least one of the following: the mapping relationship between LCID and logical channel, the mapping relationship between DRB and logical channel, the mapping relationship between logical channel and transport channel, an ACK flag for packet retransmission, a NACK flag for packet retransmission, an RLC sequence number, and a PDCP sequence number. The logical channel can be a channel between the RLC protocol layer and the MAC protocol layer, and the transport channel can be a channel between the MAC protocol layer and the PHY protocol layer.

[0171] In one possible design, the first functional entity can be deployed in a CU, DU, or RU.

[0172] In one possible design, the first communication protocol function module configured in the first functional entity can be in an active or enabled state.

[0173] In one possible design, the second functional entity is configured with a first communication protocol function module. This first communication protocol function module in the second functional entity can be used to simulate data processing.

[0174] In one possible design, the first communication protocol function module configured in the second functional entity can be in an active or enabled state.

[0175] A ninth aspect provides a communication protocol function determination apparatus, which may be equipped with a first functional entity, such as a network device, or a communication module within the network device, or a chip within the network device responsible for communication functions, such as a modem chip (also known as a baseband chip), or a SoC or SIP chip containing a modem module. It may also be a logic module or software capable of implementing all or part of the network device's functions. For ease of description, the following description assumes execution by a network device. It includes: a processor for determining first information. The first information may be used to instruct the migration of a first communication protocol function module to a second functional entity. For example, the first communication protocol function module may include a layer 2 communication protocol function module and / or a layer 3 communication protocol function module. A transceiver for sending the first information to the second functional entity. Alternatively, a transceiver for receiving the first information. A processor for determining the migration of the first communication protocol function module to the second functional entity based on the first information.

[0176] In one possible design, the transceiver is further configured to send third information to the second functional entity. This third information may indicate parameters related to the first communication protocol functional module. These parameters can be used to configure the first communication protocol functional module.

[0177] In one possible design, when the first functional entity sends the first information, the processor is further configured to: determine the first information based on a first parameter. The first parameter may include at least one of the following: a parameter indicating the service load status of the first functional entity; a parameter indicating the computing power status of the first functional entity; a parameter indicating the energy consumption status of the first functional entity; or a parameter indicating the traffic status of the interface between the first functional entity and the second functional entity.

[0178] In one possible design, the first functional entity is configured with a first communication protocol function module, which can be set to a deactivated state, a deregistered state, or a disabled state.

[0179] In one possible design, the transceiver is further configured to receive fourth information; or the processor is further configured to generate fourth information. This fourth information can be used to configure the first communication protocol functional module. The transceiver is also configured to send the fourth information to the second functional entity.

[0180] In one possible design, the fourth piece of information can be determined based on the first QoS parameter. This first QoS parameter can be used to indicate the QoS requirements of the service. Accordingly, the first communication protocol function module is used to meet the QoS requirements of the service.

[0181] In one possible design, the fourth information can configure the first communication protocol functional module based on at least one of the following granularities: granularity based on functional entities; granularity based on cells; granularity based on terminals; or granularity based on services.

[0182] In one possible design scheme, the granularity based on functional entities may include at least one of the following granularities: CU-based granularity; DU-based granularity; or RU-based granularity.

[0183] In one possible design, the service-based granularity may include at least one of the following: DRB-based granularity; PDU session-based granularity; QoS-based granularity; or packet-based granularity.

[0184] In one possible design, the first functional entity can be deployed in a CU, DU, or RU.

[0185] In one possible design, the first communication protocol functional module may include at least one of the following functional modules: a functional module for processing the MAC protocol layer; or, a functional module for processing the RLC protocol layer.

[0186] In one possible design, the first communication protocol functional module is a functional module for processing the MAC protocol layer. The parameters related to the first communication protocol functional module may include at least one of the following: MAC HARQ process list, frame number, subframe number, RB resource allocation, MCS order, multi-user pairing information, precoding coefficients for superimposing different data streams supported by MIMO, weighting coefficients for superimposing different data streams of MIMO, or RLC sequence number.

[0187] In one possible design, the first communication protocol functional module is a functional module for processing the RLC protocol layer. Parameters related to the first communication protocol functional module may include at least one of the following: the mapping relationship between LCID and logical channel, the mapping relationship between DRB and logical channel, the mapping relationship between logical channel and transport channel, an ACK flag for packet retransmission, a NACK flag for packet retransmission, an RLC sequence number, and a PDCP sequence number. The logical channel can be a channel between the RLC protocol layer and the MAC protocol layer, and the transport channel can be a channel between the MAC protocol layer and the PHY protocol layer.

[0188] In one possible design, the second functional entity can be deployed in the CU, DU, or RU.

[0189] In one possible design, the first communication protocol function module configured in the first functional entity can be in an active or enabled state.

[0190] In one possible design, the second functional entity may be configured with a first communication protocol functional module. The first communication protocol functional module configured in the second functional entity is used to simulate data processing.

[0191] In one possible design, the first communication protocol function module configured in the second functional entity can be in an active or enabled state.

[0192] In a tenth aspect, a communication protocol function determination apparatus is provided. This apparatus may be equipped with a first functional entity, such as a network device, a communication module within the network device, or a chip within the network device responsible for communication functions, such as a modem chip (also known as a baseband chip), or a SoC or SIP chip containing a modem module. It may also be a logic module or software capable of implementing all or part of the network device's functions. For ease of description, the following description assumes execution by a network device. The apparatus includes: a transceiver for sending or receiving first information. This first information may be used to instruct the migration of a first communication protocol function module to a second functional entity. For example, the first communication protocol function module may include a layer 2 communication protocol function module and / or a layer 3 communication protocol function module. The first functional entity may be configured with the first communication protocol function module. A processor is used to determine a processing method for cached data in the first communication protocol function module. The processor is also used to process the cached data in the first communication protocol function module based on the processing method.

[0193] In one possible design, the transceiver is further configured to receive second information. This second information can be used to indicate the method for processing cached data in the first communication protocol functional module.

[0194] In one possible design, the cached data in the first communication protocol functional module can be processed in any of the following ways: discarding the cached data in the first communication protocol functional module; or continuing to send the cached data in the first communication protocol functional module; or continuously sending the cached data in the first communication protocol functional module within a first time period, wherein the start time of the first time period is the time when the first communication protocol functional module stops receiving newly arrived data, and the duration of the first time period is a first duration; or determining to discard the remaining unsent cached data based on the remaining unsent cached data packets.

[0195] In one possible design, determining to discard the remaining unsent cached data based on the remaining unsent cached data may include: continuing to send cached data in the first communication protocol functional module until the ratio between the sent cached data and the remaining unsent cached data is greater than or equal to a first threshold; or, continuing to send cached data in the first communication protocol functional module until the ratio between the sent cached data and the cache capacity corresponding to the first communication protocol functional module is greater than or equal to a second threshold; or, continuing to send cached data in the first communication protocol functional module until the ratio between the remaining unsent cached data and the cache capacity corresponding to the first communication protocol functional module is less than or equal to a third threshold.

[0196] In one possible design, the processor is also used to: control the transceiver to stop receiving newly arriving data from the first communication protocol function module.

[0197] In one possible design, the transceiver is further configured to send third information to the second functional entity. This third information may indicate parameters related to the first communication protocol functional module. These parameters can be used to configure the first communication protocol functional module.

[0198] In one possible design, when the first functional entity sends the first information, the processor is further configured to: determine the first information based on a first parameter. The first parameter may include at least one of the following: a parameter indicating the service load status of the first functional entity; a parameter indicating the computing power status of the first functional entity; a parameter indicating the energy consumption status of the first functional entity; or a parameter indicating the traffic status of the interface between the first functional entity and the second functional entity.

[0199] In one possible design, the first functional entity is configured with a first communication protocol function module, which can be set to a deactivated state, a deregistered state, or a disabled state.

[0200] In one possible design, the transceiver is further configured to receive fourth information; or the processor is further configured to generate fourth information. This fourth information can be used to configure the first communication protocol functional module. The transceiver is also configured to send the fourth information to the second functional entity.

[0201] In one possible design, the fourth piece of information can be determined based on the first QoS parameter. This first QoS parameter can be used to indicate the QoS requirements of the service. Accordingly, the first communication protocol function module is used to meet the QoS requirements of the service.

[0202] In one possible design, the fourth information can configure the first communication protocol functional module based on at least one of the following granularities: granularity based on functional entities; granularity based on cells; granularity based on terminals; or granularity based on services.

[0203] In one possible design scheme, the granularity based on functional entities may include at least one of the following granularities: CU-based granularity; DU-based granularity; or RU-based granularity.

[0204] In one possible design, the service-based granularity may include at least one of the following: DRB-based granularity; PDU session-based granularity; QoS-based granularity; or packet-based granularity.

[0205] In one possible design, the first functional entity can be deployed in a CU, DU, or RU.

[0206] In one possible design, the first communication protocol functional module may include at least one of the following functional modules: a functional module for processing the MAC protocol layer; or, a functional module for processing the RLC protocol layer.

[0207] In one possible design, the first communication protocol functional module is a functional module for processing the MAC protocol layer. The parameters related to the first communication protocol functional module may include at least one of the following: MAC HARQ process list, frame number, subframe number, RB resource allocation, MCS order, multi-user pairing information, precoding coefficients for superimposing different data streams supported by MIMO, weighting coefficients for superimposing different data streams of MIMO, or RLC sequence number.

[0208] In one possible design, the first communication protocol functional module is a functional module for processing the RLC protocol layer. Parameters related to the first communication protocol functional module may include at least one of the following: the mapping relationship between LCID and logical channel, the mapping relationship between DRB and logical channel, the mapping relationship between logical channel and transport channel, an ACK flag for packet retransmission, a NACK flag for packet retransmission, an RLC sequence number, and a PDCP sequence number. The logical channel can be a channel between the RLC protocol layer and the MAC protocol layer, and the transport channel can be a channel between the MAC protocol layer and the PHY protocol layer.

[0209] In one possible design, the second functional entity can be deployed in the CU, DU, or RU.

[0210] In one possible design, the first communication protocol function module configured in the first functional entity can be in an active or enabled state.

[0211] In one possible design, the second functional entity may be configured with a first communication protocol functional module. The first communication protocol functional module configured in the second functional entity is used to simulate data processing.

[0212] In one possible design, the first communication protocol function module configured in the second functional entity can be in an active or enabled state.

[0213] Eleventhly, a communication protocol function determination apparatus is provided. This apparatus may be equipped with a first functional entity, such as a network device, a communication module within the network device, or a chip within the network device responsible for communication functions, such as a modem chip (also known as a baseband chip), or a SoC or SIP chip containing a modem module. It may also be a logic module or software capable of implementing all or part of the network device's functions. For ease of description, the following description assumes execution by a network device. It includes: a transceiver for receiving first information. This first information may be used to instruct the migration of a first communication protocol function module to a second functional entity. For example, the first communication protocol function module may include a layer 2 communication protocol function module and / or a layer 3 communication protocol function module. A processor for determining the migration of the first communication protocol function module to the second functional entity based on the first information. Alternatively, the processor is used to determine the first information. The transceiver is used to send the first information to the first functional entity.

[0214] In one possible design, the transceiver is further configured to receive third information from the first functional entity. This third information may be used to indicate parameters related to the first communication protocol functional module. These parameters are used to configure the first communication protocol functional module.

[0215] In one possible design, when the second functional entity sends the first information, the processor is further configured to: determine the first information based on a first parameter. The first parameter may include at least one of the following: a parameter indicating the service load status of the first functional entity; a parameter indicating the computing power status of the first functional entity; a parameter indicating the energy consumption status of the first functional entity; or a parameter indicating the traffic status of the interface between the first and second functional entities.

[0216] In one possible design, the transceiver is further configured to: receive fourth information; or the processor is further configured to: generate fourth information. This fourth information is used to configure the first communication protocol functional module. The processor is further configured to: generate the first communication protocol functional module based on the fourth information, and may set the first communication protocol functional module to a deactivated state or a disabled state.

[0217] In one possible design, the fourth piece of information is determined based on the first QoS parameter. This first QoS parameter can be used to indicate the QoS requirements of the service. Accordingly, the first communication protocol function module can be used to meet the QoS requirements of the service.

[0218] In one possible design, the fourth information can configure the first communication protocol functional module based on at least one of the following granularities: granularity based on functional entities; granularity based on cells; granularity based on terminals; or granularity based on services.

[0219] In one possible design scheme, the granularity based on functional entities may include at least one of the following granularities: CU-based granularity; DU-based granularity; or RU-based granularity.

[0220] In one possible design, the service-based granularity may include at least one of the following: DRB-based granularity; PDU session-based granularity; QoS-based granularity; or packet-based granularity.

[0221] In one possible design, the second functional entity can be deployed in the CU, DU, or RU.

[0222] In one possible design, the first communication protocol functional module may include at least one of the following functional modules: a functional module for processing the MAC protocol layer; or, a functional module for processing the RLC protocol layer.

[0223] In one possible design, the first communication protocol functional module is a functional module for processing the MAC protocol layer. The parameters related to the first communication protocol functional module may include at least one of the following: MAC HARQ process list, frame number, subframe number, RB resource allocation, MCS order, multi-user pairing information, precoding coefficients for superimposing different data streams supported by MIMO, weighting coefficients for superimposing different data streams of MIMO, or RLC sequence number.

[0224] In one possible design, the first communication protocol functional module is a functional module for processing the RLC protocol layer. Parameters related to the first communication protocol functional module may include at least one of the following: the mapping relationship between LCID and logical channel, the mapping relationship between DRB and logical channel, the mapping relationship between logical channel and transport channel, an ACK flag for packet retransmission, a NACK flag for packet retransmission, an RLC sequence number, and a PDCP sequence number. The logical channel can be a channel between the RLC protocol layer and the MAC protocol layer, and the transport channel can be a channel between the MAC protocol layer and the PHY protocol layer.

[0225] In one possible design, the first functional entity can be deployed in a CU, DU, or RU.

[0226] In one possible design, the first communication protocol function module configured in the first functional entity can be in an active or enabled state.

[0227] In one possible design, the second functional entity is configured with a first communication protocol function module. This first communication protocol function module in the second functional entity can be used to simulate data processing.

[0228] In one possible design, the first communication protocol function module configured in the second functional entity can be in an active or enabled state.

[0229] In a twelfth aspect, a communication protocol function determination apparatus is provided. This apparatus may deploy a first functional entity, such as a network device, or a communication module within the network device, or a chip within the network device responsible for communication functions, such as a modem chip (also known as a baseband chip), or a SoC or SIP chip containing a modem module. It may also be a logic module or software capable of implementing all or part of the network device's functions. For ease of description, the following description uses an example executed by a network device. It includes: a transceiver module for receiving or sending first information. This first information may be used to instruct the migration of a first communication protocol function module to a second functional entity. For example, the first communication protocol function module may include a layer 2 communication protocol function module and / or a layer 3 communication protocol function module. The first functional entity may be configured with the first communication protocol function module. A processor is used to cache first data. The first data is data sent to the first communication protocol function module in the first functional entity. The processor is also used to process the cached first data.

[0230] In one possible design, the processor is further configured to determine second information. The transceiver is further configured to transmit the second information. This second information can be used to indicate the method of processing cached data in the first communication protocol functional module configured for the first functional entity.

[0231] In one possible design, the cached data in the first communication protocol function module configured by the first functional entity can be processed in any of the following ways: discarding the cached data in the first communication protocol function module; or continuing to send the cached data in the first communication protocol function module; or continuously sending the cached data in the first communication protocol function module within a first time period, wherein the start time of the first time period is the time when the first communication protocol function module stops receiving newly arrived data, and the duration of the first time period is a first duration; or determining to discard the remaining unsent cached data based on the remaining unsent cached data packets.

[0232] In one possible design, determining to discard the remaining unsent cached data based on the remaining unsent cached data may include: continuing to send cached data in the first communication protocol functional module until the ratio between the sent cached data and the remaining unsent cached data is greater than or equal to a first threshold; or, continuing to send cached data in the first communication protocol functional module until the ratio between the sent cached data and the cache capacity corresponding to the first communication protocol functional module is greater than or equal to a second threshold; or, continuing to send cached data in the first communication protocol functional module until the ratio between the remaining unsent cached data and the cache capacity corresponding to the first communication protocol functional module is less than or equal to a third threshold.

[0233] In one possible design, the transceiver is further configured to receive third information from the first functional entity. This third information may be used to indicate parameters related to the first communication protocol functional module. These parameters are used to configure the first communication protocol functional module.

[0234] In one possible design, when the second functional entity sends the first information, the processor is further configured to: determine the first information based on a first parameter. The first parameter may include at least one of the following: a parameter indicating the service load status of the first functional entity; a parameter indicating the computing power status of the first functional entity; a parameter indicating the energy consumption status of the first functional entity; or a parameter indicating the traffic status of the interface between the first and second functional entities.

[0235] In one possible design, the transceiver is further configured to receive fourth information; or the processor is further configured to generate the fourth information. This fourth information is used to configure the first communication protocol functional module. The processor is also configured to generate the first communication protocol functional module based on the fourth information, and can set the first communication protocol functional module to a deactivated or disabled state.

[0236] In one possible design, the fourth piece of information is determined based on the first QoS parameter. This first QoS parameter can be used to indicate the QoS requirements of the service. Accordingly, the first communication protocol function module can be used to meet the QoS requirements of the service.

[0237] In one possible design, the fourth information can configure the first communication protocol functional module based on at least one of the following granularities: granularity based on functional entities; granularity based on cells; granularity based on terminals; or granularity based on services.

[0238] In one possible design scheme, the granularity based on functional entities may include at least one of the following granularities: CU-based granularity; DU-based granularity; or RU-based granularity.

[0239] In one possible design, the service-based granularity may include at least one of the following: DRB-based granularity; PDU session-based granularity; QoS-based granularity; or packet-based granularity.

[0240] In one possible design, the second functional entity can be deployed in the CU, DU, or RU.

[0241] In one possible design, the first communication protocol functional module may include at least one of the following functional modules: a functional module for processing the MAC protocol layer; or, a functional module for processing the RLC protocol layer.

[0242] In one possible design, the first communication protocol functional module is a functional module for processing the MAC protocol layer. The parameters related to the first communication protocol functional module may include at least one of the following: MAC HARQ process list, frame number, subframe number, RB resource allocation, MCS order, multi-user pairing information, precoding coefficients for superimposing different data streams supported by MIMO, weighting coefficients for superimposing different data streams of MIMO, or RLC sequence number.

[0243] In one possible design, the first communication protocol functional module is a functional module for processing the RLC protocol layer. Parameters related to the first communication protocol functional module may include at least one of the following: the mapping relationship between LCID and logical channel, the mapping relationship between DRB and logical channel, the mapping relationship between logical channel and transport channel, an ACK flag for packet retransmission, a NACK flag for packet retransmission, an RLC sequence number, and a PDCP sequence number. The logical channel can be a channel between the RLC protocol layer and the MAC protocol layer, and the transport channel can be a channel between the MAC protocol layer and the PHY protocol layer.

[0244] In one possible design, the first functional entity can be deployed in a CU, DU, or RU.

[0245] In one possible design, the first communication protocol function module configured in the first functional entity can be in an active or enabled state.

[0246] In one possible design, the second functional entity is configured with a first communication protocol function module. This first communication protocol function module in the second functional entity can be used to simulate data processing.

[0247] In one possible design, the first communication protocol function module configured in the second functional entity can be in an active or enabled state.

[0248] In a thirteenth aspect, a network communication protocol function determination system is provided. The system includes a first functional entity and a second functional entity. The first and second functional entities can be network devices, components of network devices (e.g., processors, circuits, chips, or chip systems), or logic modules or software capable of implementing all or part of the network device's functions. For ease of description, the following explanation uses an example executed by a network device. The system may include: the first functional entity determining first information. The first information can be used to instruct the migration of a first communication protocol function module to the second functional entity. For example, the first communication protocol function module may include a layer 2 communication protocol function module and / or a layer 3 communication protocol function module. The first functional entity sends the first information to the second functional entity. Correspondingly, the second functional entity receives the first information from the first functional entity. The second functional entity determines the migration of the first communication protocol function module to the second functional entity based on the first information. Alternatively, the second functional entity determines the first information. The second functional entity sends the first information to the first functional entity. Correspondingly, the first functional entity receives the first information from the second functional entity. The first functional entity determines the migration of the first communication protocol function module to the second functional entity based on the first information.

[0249] In one possible design, the system may further include: a first functional entity sending third information to a second functional entity. Correspondingly, the second functional entity receives the third information from the first functional entity. The third information may be used to indicate parameters related to the first communication protocol functional module. These parameters related to the first communication protocol functional module may be used to configure the first communication protocol functional module.

[0250] In one possible design, when the first functional entity sends the first information, the system may further include: the first functional entity determining the first information based on a first parameter. When the second functional entity sends the first information, the system may further include: the second functional entity determining the first information based on a first parameter. The first parameter may include at least one of the following: a parameter indicating the service load status of the first functional entity; a parameter indicating the computing power status of the first functional entity; a parameter indicating the energy consumption status of the first functional entity; or a parameter indicating the traffic status of the interface between the first and second functional entities.

[0251] In one possible design, the first functional entity is configured with a first communication protocol function module, which can be set to a deactivated state, a deregistered state, or a disabled state.

[0252] In one possible design, the system may further include: a first functional entity generating fourth information; the first functional entity sending the fourth information to a second functional entity; and the second functional entity receiving the fourth information from the first functional entity. This fourth information can be used to configure a first communication protocol functional module. Alternatively, the second functional entity generates the fourth information; the second functional entity sending the fourth information to the first functional entity; and the first functional entity receiving the fourth information from the second functional entity. This fourth information can also be used to configure a first communication protocol functional module. The second functional entity then generates the first communication protocol functional module based on the fourth information.

[0253] In one possible design, the fourth piece of information can be determined based on the first QoS parameter. This first QoS parameter can be used to indicate the QoS requirements of the service. Accordingly, the first communication protocol function module is used to meet the QoS requirements of the service.

[0254] In one possible design, the fourth information can configure the first communication protocol functional module based on at least one of the following granularities: granularity based on functional entities; granularity based on cells; granularity based on terminals; or granularity based on services.

[0255] In one possible design scheme, the granularity based on functional entities may include at least one of the following granularities: CU-based granularity; DU-based granularity; or RU-based granularity.

[0256] In one possible design, the service-based granularity may include at least one of the following: DRB-based granularity; PDU session-based granularity; QoS-based granularity; or packet-based granularity.

[0257] In one possible design, the first functional entity can be deployed in a CU, DU, or RU.

[0258] In one possible design, the first communication protocol functional module may include at least one of the following functional modules: a functional module for processing the MAC protocol layer; or, a functional module for processing the RLC protocol layer.

[0259] In one possible design, the first communication protocol functional module is a functional module for processing the MAC protocol layer. The parameters related to the first communication protocol functional module may include at least one of the following: MAC HARQ process list, frame number, subframe number, RB resource allocation, MCS order, multi-user pairing information, precoding coefficients for superimposing different data streams supported by MIMO, weighting coefficients for superimposing different data streams of MIMO, or RLC sequence number.

[0260] In one possible design, the first communication protocol functional module is a functional module for processing the RLC protocol layer. Parameters related to the first communication protocol functional module may include at least one of the following: the mapping relationship between LCID and logical channel, the mapping relationship between DRB and logical channel, the mapping relationship between logical channel and transport channel, an ACK flag for packet retransmission, a NACK flag for packet retransmission, an RLC sequence number, and a PDCP sequence number. The logical channel can be a channel between the RLC protocol layer and the MAC protocol layer, and the transport channel can be a channel between the MAC protocol layer and the PHY protocol layer.

[0261] In one possible design, the second functional entity can be deployed in the CU, DU, or RU.

[0262] In one possible design, the first communication protocol function module configured in the first functional entity can be in an active or enabled state.

[0263] In one possible design, the second functional entity may be configured with a first communication protocol functional module. The first communication protocol functional module configured in the second functional entity is used to simulate data processing.

[0264] In one possible design, the first communication protocol function module configured in the second functional entity can be in an active or enabled state.

[0265] In a fourteenth aspect, a network communication protocol function determination system is provided. This system includes a first functional entity and a second functional entity. The first and second functional entities can be network devices, components of network devices (e.g., processors, circuits, chips, or chip systems), or logic modules or software capable of implementing all or part of the network device's functions. For ease of description, the following explanation uses an example executed by a network device. The system may include: the first functional entity sending or receiving first information. Correspondingly, the second functional entity receives or sends the first information. The first information can be used to instruct the migration of a first communication protocol function module to the second functional entity. For example, the first communication protocol function module may include a layer 2 communication protocol function module and / or a layer 3 communication protocol function module. The first functional entity may be configured with the first communication protocol function module. The first functional entity determines a processing method for cached data in the first communication protocol function module. The first functional entity processes the cached data in the first communication protocol function module based on the processing method. The second functional entity caches first data. The first data is data sent to the first communication protocol function module in the first functional entity. The second functional entity processes the cached first data.

[0266] In one possible design, the method may further include: a second functional entity determining second information; the second functional entity sending the second information to a first functional entity; and correspondingly, the first functional entity receiving the second information from the second functional entity. This second information can be used to indicate the method for processing cached data in the first communication protocol functional module.

[0267] In one possible design, the cached data in the first communication protocol functional module can be processed in any of the following ways: discarding the cached data in the first communication protocol functional module; or continuing to send the cached data in the first communication protocol functional module; or continuously sending the cached data in the first communication protocol functional module within a first time period, wherein the start time of the first time period is the time when the first communication protocol functional module stops receiving newly arrived data, and the duration of the first time period is a first duration; or determining to discard the remaining unsent cached data based on the remaining unsent cached data packets.

[0268] In one possible design, determining to discard the remaining unsent cached data based on the remaining unsent cached data may include: continuing to send cached data in the first communication protocol functional module until the ratio between the sent cached data and the remaining unsent cached data is greater than or equal to a first threshold; or, continuing to send cached data in the first communication protocol functional module until the ratio between the sent cached data and the cache capacity corresponding to the first communication protocol functional module is greater than or equal to a second threshold; or, continuing to send cached data in the first communication protocol functional module until the ratio between the remaining unsent cached data and the cache capacity corresponding to the first communication protocol functional module is less than or equal to a third threshold.

[0269] In one possible design, the system may further include: a first functional entity stopping receiving newly arriving data from the first communication protocol functional module.

[0270] In one possible design, the system may further include: a first functional entity sending third information to a second functional entity. Correspondingly, the second functional entity receives the third information from the first functional entity. The third information may be used to indicate parameters related to the first communication protocol functional module. These parameters related to the first communication protocol functional module may be used to configure the first communication protocol functional module.

[0271] In one possible design, when the first functional entity sends the first information, the system may further include: the first functional entity determining the first information based on a first parameter. When the second functional entity sends the first information, the system may further include: the second functional entity determining the first information based on a first parameter. The first parameter may include at least one of the following: a parameter indicating the service load status of the first functional entity; a parameter indicating the computing power status of the first functional entity; a parameter indicating the energy consumption status of the first functional entity; or a parameter indicating the traffic status of the interface between the first and second functional entities.

[0272] In one possible design, the first functional entity is configured with a first communication protocol function module, which can be set to a deactivated state, a deregistered state, or a disabled state.

[0273] In one possible design, the system may further include: a first functional entity generating fourth information; the first functional entity sending the fourth information to a second functional entity; and the second functional entity receiving the fourth information from the first functional entity. This fourth information can be used to configure a first communication protocol functional module. Alternatively, the second functional entity generates the fourth information; the second functional entity sending the fourth information to the first functional entity; and the first functional entity receiving the fourth information from the second functional entity. This fourth information can also be used to configure a first communication protocol functional module. The second functional entity then generates the first communication protocol functional module based on the fourth information.

[0274] In one possible design, the fourth piece of information can be determined based on the first QoS parameter. This first QoS parameter can be used to indicate the QoS requirements of the service. Accordingly, the first communication protocol function module is used to meet the QoS requirements of the service.

[0275] In one possible design, the fourth information can configure the first communication protocol functional module based on at least one of the following granularities: granularity based on functional entities; granularity based on cells; granularity based on terminals; or granularity based on services.

[0276] In one possible design scheme, the granularity based on functional entities may include at least one of the following granularities: CU-based granularity; DU-based granularity; or RU-based granularity.

[0277] In one possible design, the service-based granularity may include at least one of the following: DRB-based granularity; PDU session-based granularity; QoS-based granularity; or packet-based granularity.

[0278] In one possible design, the first functional entity can be deployed in a CU, DU, or RU.

[0279] In one possible design, the first communication protocol functional module may include at least one of the following functional modules: a functional module for processing the MAC protocol layer; or, a functional module for processing the RLC protocol layer.

[0280] In one possible design, the first communication protocol functional module is a functional module for processing the MAC protocol layer. The parameters related to the first communication protocol functional module may include at least one of the following: MAC HARQ process list, frame number, subframe number, RB resource allocation, MCS order, multi-user pairing information, precoding coefficients for superimposing different data streams supported by MIMO, weighting coefficients for superimposing different data streams of MIMO, or RLC sequence number.

[0281] In one possible design, the first communication protocol functional module is a functional module for processing the RLC protocol layer. Parameters related to the first communication protocol functional module may include at least one of the following: the mapping relationship between LCID and logical channel, the mapping relationship between DRB and logical channel, the mapping relationship between logical channel and transport channel, an ACK flag for packet retransmission, a NACK flag for packet retransmission, an RLC sequence number, and a PDCP sequence number. The logical channel can be a channel between the RLC protocol layer and the MAC protocol layer, and the transport channel can be a channel between the MAC protocol layer and the PHY protocol layer.

[0282] In one possible design, the second functional entity can be deployed in the CU, DU, or RU.

[0283] In one possible design, the first communication protocol function module configured in the first functional entity can be in an active or enabled state.

[0284] In one possible design, the second functional entity may be configured with a first communication protocol functional module. The first communication protocol functional module configured in the second functional entity is used to simulate data processing.

[0285] In one possible design, the first communication protocol function module configured in the second functional entity can be in an active or enabled state.

[0286] In a fifteenth aspect, a chip is provided, comprising an interface circuit and one or more processors. The one or more processors are coupled to a memory. The memory is used to store part or all of the necessary computer programs or instructions for implementing the functions described in the first, second, third, and fourth aspects. The one or more processors are capable of executing the computer programs or instructions, which, when executed, cause the communication device to implement the methods in any possible design or implementation of the first, second, third, and fourth aspects. The interface circuit is used to implement communication functions within the communication device and / or communication functions between the communication device and other devices or components.

[0287] In a sixteenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores computer instructions; when the computer instructions are executed on a computer, the computer causes the computer to perform a communication method as designed in any of the foregoing aspects.

[0288] In a seventeenth aspect, a computer program product is provided. The computer program product includes a computer program or instructions that, when executed on a computer, cause the computer to perform a communication method as designed in any of the foregoing aspects.

[0289] The beneficial effects of the methods in any of the second to seventeenth aspects mentioned above can be referred to the description of the beneficial effects of the methods in the first aspect, and will not be repeated here. Attached Figure Description

[0290] Figure 1 is a schematic diagram of the architecture of a communication system applied in an embodiment of this application;

[0291] Figure 2 is a schematic diagram of the functional segmentation of the communication protocol between BBU and RRU provided in an embodiment of this application;

[0292] Figure 3 is a schematic diagram of a wireless access network architecture provided in an embodiment of this application;

[0293] Figure 4 is a schematic diagram of another wireless access network architecture provided in an embodiment of this application;

[0294] Figure 5 is a schematic diagram of the functional division of an access network device provided in an embodiment of this application;

[0295] Figure 6 is a schematic diagram of a communication protocol function segmentation method provided in an embodiment of this application;

[0296] Figure 7 is a schematic diagram of another communication protocol function segmentation method provided in the embodiments of this application;

[0297] Figure 8 is a schematic diagram of another communication protocol function segmentation method provided in the embodiments of this application;

[0298] Figure 9 is a schematic diagram of a communication scenario provided in an embodiment of this application;

[0299] Figure 10 is a schematic diagram of network communication protocol function migration provided in an embodiment of this application;

[0300] Figure 11 is a schematic diagram of a method for determining network communication protocol functions according to an embodiment of this application;

[0301] Figure 12 is a schematic diagram of another method for determining network communication protocol functions provided in an embodiment of this application;

[0302] Figure 13 is a schematic diagram of another network communication protocol function migration provided in an embodiment of this application;

[0303] Figure 14 is a schematic diagram of another network communication protocol function migration provided in an embodiment of this application;

[0304] Figure 15 is a schematic diagram of another network communication protocol function migration provided in an embodiment of this application;

[0305] Figure 16 is a schematic diagram of another method for determining network communication protocol functions provided in an embodiment of this application;

[0306] Figure 17 is a schematic diagram of another method for determining network communication protocol functions provided in an embodiment of this application;

[0307] Figure 18 is a schematic diagram of another communication scenario provided by an embodiment of this application;

[0308] Figure 19 is a schematic diagram of another network communication protocol function migration provided in an embodiment of this application;

[0309] Figure 20 is a schematic diagram of a network structure provided in an embodiment of this application;

[0310] Figure 21 is a schematic diagram of another network structure provided in an embodiment of this application;

[0311] Figure 22 is a schematic diagram of another network structure provided in an embodiment of this application;

[0312] Figure 23 is a schematic diagram of another network structure provided in an embodiment of this application;

[0313] Figure 24 is a schematic diagram of another method for determining network communication protocol functions provided in an embodiment of this application;

[0314] Figure 25 is a schematic diagram of a communication protocol function determination device provided in an embodiment of this application;

[0315] Figure 26 is a schematic diagram of another communication protocol function determination device provided in an embodiment of this application. Detailed Implementation

[0316] Figure 1 is a schematic diagram of the architecture of a communication system 1000 provided in an embodiment of this application. As shown in Figure 1, the communication system 1000 includes a radio access network (RAN) 100, wherein the RAN 100 includes at least one RAN node (110a and 110b in Figure 1, collectively referred to as 110), and may also include at least one terminal (120a-120j in Figure 1, collectively referred to as 120). The RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1). The terminal 120 is wirelessly connected to the RAN node 110. Terminals and RAN nodes can be interconnected via wired or wireless means. The communication system 1000 may also include a core network 200. The RAN node 110 is connected to the core network 200 via wireless or wired means. The core network equipment in core network 200 and the RAN node 110 in RAN 100 can be independent and different physical devices, or they can be the same physical device that integrates the logical functions of the core network equipment and the logical functions of the RAN node. The communication system 1000 may also include the Internet 300.

[0317] RAN100 can be an evolved universal terrestrial radio access (E-UTRA) system, a new radio (NR) system, a future communications network, or a future radio access system as defined in the 3rd generation partnership project (3GPP). RAN100 can also include two or more of the above-mentioned different radio access systems. RAN100 can also be an open RAN (O-RAN).

[0318] RAN nodes, also known as radio access network devices, RAN entities, or access nodes, are used to help terminals access communication systems wirelessly. In one application scenario, an RAN node can be a base station (BS), an evolved NodeB (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. RAN nodes can be macro base stations (as shown in Figure 1, 110a), micro base stations or indoor stations (as shown in Figure 1, 110b), relay nodes, or master nodes.

[0319] In another application scenario, multiple RAN nodes can collaborate to help terminals achieve wireless access, with different RAN nodes implementing different functions of the base station. For example, a RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). An RU can also be called a radio frequency unit. Here, the CU performs the functions of the base station's radio resource control protocol and packet data convergence protocol (PDCP), and can also perform the functions of the service data adaptation protocol (SDAP). The DU performs the functions of the base station's radio link control layer and medium access control (MAC) layer, and can also perform some or all of the physical layer functions. For specific descriptions of these protocol layers, refer to the relevant 3GPP technical specifications. The RU can be used to implement radio frequency signal transmission and reception. The CU and DU can be two independent RAN nodes, or they can be integrated into the same RAN node, such as within a baseband unit (BBU). RUs can be included in radio frequency equipment, such as remote radio units (RRUs) or active antenna units (AAUs). CUs can be further divided into two types of RAN nodes: CU-control plane and CU-user plane.

[0320] In different systems, RAN nodes may have different names. For example, in an open radio access network (O-RAN) system, a CU can be called an open CU (O-CU), a DU can be called an open DU (O-DU), and an RU can be called an open RU (O-RU). The RAN nodes in the embodiments of this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. For example, an RAN node can be a server loaded with the corresponding software modules. The embodiments of this application do not limit the specific technology or device form used in the RAN nodes. For ease of description, a base station is used as an example of a RAN node in the following description.

[0321] A terminal is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from a base station. Terminals can also be called terminal equipment, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used 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, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal.

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

[0323] Base stations and terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the base stations and terminals.

[0324] The roles of base stations and terminals can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile base station. For terminals 120j that access the wireless access network 100 through 120i, terminal 120i is a base station; however, for base station 110a, 120i is a terminal, meaning that 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a base station-to-base station interface protocol. In this case, relative to 110a, 120i is also a base station. Therefore, both base stations and terminals can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be called communication devices with base station functions, and 120a-120j in Figure 1 can be called communication devices with terminal functions.

[0325] Communication between base stations and terminals, between base stations, and between terminals can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can be conducted using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0326] In the embodiments of this application, the functions of the base station can be executed by modules (such as chips) within the base station, or by a control subsystem that includes base station functions. This control subsystem, including base station functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal can be executed by modules (such as chips or modems) within the terminal, or by a device that includes terminal functions.

[0327] In a wireless communication system, communication devices are included, and these devices can communicate wirelessly using air interface resources. These communication devices can include network devices and terminal devices; network devices can also be called base station devices, i.e., the wireless access network devices mentioned above. Air interface resources can include at least one of time-domain resources, frequency-domain resources, code resources, and spatial resources. These communication devices can also be called communication apparatuses.

[0328] The solutions provided in this application can be applied to wireless communication between communication devices. Wireless communication can include: wireless communication between network devices and terminals, wireless communication between network devices, and wireless communication between terminals. In this application, the term "wireless communication" can also be simply referred to as "communication," and the term "communication" can also be described as "data transmission," "information transmission," or "transmission."

[0329] In global system for mobile communications (GSM), wideband code division multiple access (WCDMA), universal mobile telecommunications system (UMTS), long term evolution (LTE), and 5G systems, base stations can be deployed by dividing them into two functional entities: a base unit (BBU) and a radio frequency unit (RRU), according to a bottom-layer partitioning method. This bottom-layer partitioning method can be a partitioning of the physical layer and the radio frequency (RF) portion. It is understood that in the various embodiments of this application, "partitioning" and "division" can be used interchangeably. The BBU is connected to one or more RRUs via optical fiber, metallic cabling, or microwave links. The BBU primarily performs centralized upper-layer processing of baseband signals. The RRU primarily performs baseband signal reception and transmission, as well as RF signal modulation and demodulation, data processing, and power amplification. The RRU is closer to the antenna, resulting in lower feeder loss. In some cases, the RRU can also be called an RU or an AAU. The interface between the BBU and RRU can be called a fronthaul interface or a bottom-layer partitioning interface.

[0330] Referring to Figure 2, which illustrates a functional division of the communication protocol between a BBU and an RRU, in related technologies, the interface between the BBU and RRU can use the Common Public Radio Interface (CPRI) protocol for communication interaction. The CPRI protocol defines the key communication interface specifications for communication between radio equipment control (REC) and radio equipment (RE) in a wireless communication network. For example, the REC can be considered the aforementioned BBU, and the radio equipment can be considered the aforementioned RRU. As shown in Figure 2, the CPRI interface allocates the radio frequency (RF) layer functions to RRU 1, and the physical (PHY) layer and above protocol layer functions to BBU 1. The PHY layer can be further divided into a high PHY layer and a low PHY layer. The high PHY layer can also be called High PHY, and the low PHY layer can also be called Low PHY. Protocol layer functions above the PHY layer can include the radio resource control (RRC) layer, SDAP layer, PDCP layer, radio link control (RLC) layer, and MAC layer.

[0331] The amount of data transmitted between the BBU's PHY layer and the RRU's RF layer is directly related to the antenna array size. The splitting method specified by the CPRI protocol results in excessively large data volumes on the fronthaul interface, making it unsuitable for scenarios with large-scale antenna arrays. For example, suppose a 9.8 gigabits per second (Gbps) fiber carries two 4-transmit, 4-receive (4T4R) antennas on a CPRI-compliant fronthaul interface, along with a cell with a 20 MHz wireless bandwidth. Then, for a cell with 64 antennas and a 100 MHz bandwidth, approximately 32 9.8 Gbps fibers would need to be deployed on the CPRI interface.

[0332] Some solutions propose an evolution of the CPRI protocol, namely an enhanced CPRI protocol, denoted as eCPRI. Referring again to Figure 2, the eCPRI protocol further refines the communication protocol of the wireless network, such as dividing the PHY layer into a higher PHY layer and a lower PHY layer. The lower PHY layer is deployed in the RRU, and the higher PHY layer is deployed in the BBU. Furthermore, the interface specification between the BBU and RRU, i.e., between the higher and lower PHY layers, has been redefined. The eCPRI protocol transforms the interface between the BBU and RRU from the interface between the RF layer and the PHY layer as defined in the CPRI protocol to an interface between the higher and lower PHY layers. This transforms the original fiber optic communication between the RF layer and the PHY layer into communication within the RRU's internal board or field-programmable gate array (FPGA) chip. Moreover, the data dimension of the communication between the higher PHY layer of the BBU and the lower PHY layer of the RRU is reduced, no longer directly related to the antenna array size on the RRU.

[0333] The splitting method used in the aforementioned CPRI or eCPRI interfaces allows the BBU to process baseband signals in a highly centralized manner. This enables centralized deployment of computing resources, resulting in high resource utilization and low deployment costs. However, it also places a significant demand on fronthaul link bandwidth, leading to higher fiber optic deployment costs.

[0334] Referring to Figure 3, a new RAN architecture potentially applicable to future communication systems is proposed. This architecture reclassifies base station functions into RU functions, radio network area (RNA) functions, and RNA automation functions. The RNA and RU functions communicate via a low-layer split (LLS) interface, while the RU function and the terminal can establish a RAN-UE interface for communication. The RNA function and the core network (CN) communicate via the RAN-CN interface. The RAN automation function manages the RU and RNA functions through a network function (NF) management interface. The RAN automation function is controlled through network management. In this architecture, the RU function can be viewed as the aforementioned RRU or AAU, and the RNA function as the aforementioned BBU.

[0335] In related technologies, to reduce the pressure on fronthaul link bandwidth and deployment costs caused by the underlying segmentation method, 3GPP proposed a base station function partitioning method. For example, for gNBs in 5G, a higher-layer segmentation method is adopted, splitting the base station into two functional entities such as CU and DU. The midhaul link between CU and DU has lower network bandwidth requirements. The radio access network shown in Figure 4 is divided according to CU and DU. For example, the access network equipment can be a gNB, which can be composed of CU and DU. Of course, DU can include one or more, which is not limited in this embodiment. The gNB can communicate with the core network elements of the 5G core network (5GC) through the NG interface. Different gNBs can communicate with each other through the Xn interface, for example, through the Xn-control (C) interface. The CU can communicate with different DUs through the F1 interface.

[0336] In this application, the functional decomposition between the CU and DU in the access network device can be achieved using a static decomposition method, with a fixed division based on the functional granularity of the protocol stack. As shown in Figure 5, the protocol stacks such as the RLC layer, MAC layer, and PHY layer can be located in the DU of the access network device. The MAC layer can also be referred to as Media Access Control, etc., which is not limited to this embodiment. The protocol stacks such as the RRC layer, SDAP layer, and PDCP layer can be located in the CU of the access network device. RRC implements air interface radio resource and air interface connection control, belonging to the control plane (CP) protocol; SDAP performs the mapping between quality of service flow (QoS-flow) and data radio bearer (DRB), belonging to the user plane (UP) protocol. QoS-flow represents the service data flow with specific quality of service (QoS) requirements.

[0337] As shown in Figure 5, for the DU, both the control plane protocol stack and the user plane protocol stack involve RLC, MAC, and PHY. For the CU, PDCP is applicable to both 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 executing control plane protocol stack functions, the CU and DU can communicate via the F1-C interface; for executing user plane protocol stack functions, the CU and DU can communicate via the F1-user (user)U interface. Based on the separation of CU and DU, the CU of the access network device can also have separate CP and UP units. The CP of the CU of the access network device can be denoted as gNB-CU-CP, and the UP of the CU can be denoted as gNB-CU-UP. The PDCP layer protocol exists in both the gNB-CU-CP and gNB-CU-UP units, while 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.

[0338] The RLC layer can provide transparent data transmission as well as non-deterministic and deterministic data transmission modes. The MAC layer is mainly responsible for controlling and connecting the physical medium of the physical layer. The PHY layer is responsible for the transmission of bits or groups of bits on the physical medium, including encoding the transmitted information and decoding the received information. Specific protocols can be found in relevant technologies, such as the 3GPP technical specification (TS) 38.300, which will not be elaborated further in this application.

[0339] Referring to Figure 6, several possible communication protocol function segmentation methods are illustrated. Communication protocol functions can be divided according to protocol layer granularity. For example, options 1 through 8 are provided. Option 1 can be the communication function segmentation between the RRC layer and the PDCP layer as shown in Figure 6, or option 2 can be the communication function segmentation between the SDAP layer and the PDCP layer as shown in Figure 6. It is understood that subsequent embodiments of this application will be described using the control plane RRC layer as an example. For user plane segmentation, the RRC layer can be replaced with the SDAP layer, and this will not be elaborated further in the embodiments of this application.

[0340] Option 2 can be the communication function division between the PDCP layer and the higher RLC layer, as shown in Figure 6. Option 3 can be the communication function division between the higher RLC layer and the lower RLC layer, as shown in Figure 6. Therefore, Option 3 can also be considered as communication function division within the RLC layer. Option 4 can be the communication function division between the lower RLC layer and the higher MAC layer, as shown in Figure 6. Option 5 can be the communication function division between the higher MAC layer and the lower MAC layer, as shown in Figure 6. Therefore, Option 5 can also be considered as communication function division within the MAC layer. Option 6 can be the communication function division between the lower MAC layer and the higher PHY layer, as shown in Figure 6. Option 7 can be the communication function division between the higher PHY layer and the lower PHY layer, as shown in Figure 6. Therefore, Option 7 can also be considered as communication function division within the PHY layer. Option 8 can be the communication function division between the lower PHY layer and the RF layer, as shown in Figure 6. The division method of Option 8 is exactly the same as the division method specified in the CPRI protocol.

[0341] As can be seen, more granular division of communication protocol functions can be performed within certain protocol layers. For example, protocol layers such as the RLC layer, MAC layer, and PHY layer can be divided into higher and lower layers. The following description uses the PHY layer as an example to illustrate the division of communication protocol functions within a protocol layer. The division methods for other protocol layers are similar, the difference being that the communication protocol functions within different protocol layers can differ. For specific details, please refer to the communication protocol functions within the corresponding protocol layer; this application does not impose limitations on these aspects. Referring to Figure 7, the communication functions within the PHY layer are divided for downlink (DL) communication. Assume the PHY layer can be further divided into functions such as coding, rate mapping, scrambling, modulation, layer mapping, precoding, resource element (RE) mapping, digital beamforming (DBF), inverse fast fourier transform (IFFT) / addition of cyclic prefix (CP), digital-to-analog conversion, analog beamforming, and RF. Here, a resource element can be a unit of radio resource consisting of a subcarrier and a symbol. Therefore, the segmentation method for Option 7 could also include Option 7-1, Option 7-2, Option 7-2a, and Option 7-3.

[0342] It is worth noting that both radio equipment and resource particles can be abbreviated as RE. Therefore, in order to distinguish between radio equipment and resource particles, in the embodiments of this application, RE can refer to resource particles, while radio equipment is not described by abbreviation.

[0343] The analog beamforming module shown in Figure 7 can generate a beam in a specific direction by adjusting the phase of the digital signal on the antenna using a phase shifter in the analog domain. It can be assumed that all antennas are processing the same signal. In some scenarios, digital beamforming and precoding in Figure 7 can be the same module, thus digital beamforming can also be called precoding. Precoding involves adjusting the phase and amplitude of baseband signals from different data streams to create beams with different directions and power intensities, allowing for more flexible generation of beams. This effectively utilizes spatial diversity or spatial multiplexing. Beamforming is a signal processing technique that uses antenna arrays to transmit and receive signals in a directional manner. By adjusting the basic units and phase parameters of the antenna array, signals at certain angles undergo constructive interference, while signals at other angles undergo destructive interference, ensuring that only the target signal is aligned with the target receiving device.

[0344] For example, referring to Figure 7, option 7-1 could be a functional division of the communication protocol between IFFT / adding CP and DBF. Option 7-2 could be a functional division of the communication protocol between precoding and layer mapping. Option 7-2a could be a functional division of the communication protocol between DBF and RE mapping. Option 7-3 could be a functional division of the communication protocol between modulation and scrambling. Option 7-2a can also be called category A, and option 7-2 can also be called category B. Option 7-3 can also be considered the same as the downlink segmentation method of the eCPRI protocol. Option 7-3 can also be called interface e (Ie) for downlink, Ie segmentation for downlink, Ie2 for downlink, Ie2 segmentation for downlink, etc. In Figure 7, if the functional division of the communication protocol is performed between IFFT / adding CP and digital-to-analog, it corresponds to option 8 mentioned above, i.e., the segmentation method corresponding to the CPRI protocol.

[0345] Referring to Figure 8, the communication functions within the PHY layer in uplink (UL) communication are divided. It is assumed that the PHY layer can be further divided into functions such as decoding, rate demapping, descrambling, demodulation, channel estimation, equalization, RE demapping, DBF, fast fourier transform (FFT) / CP removal, analog-to-digital conversion, analog beamforming, and RF. Therefore, the segmentation method for option 7 can also include options 7-1', 7-2', 7-2a', and 7-3'. Demodulation can also be referred to as demodulation.

[0346] For example, referring to Figure 8, option 7-1' could be a division of communication protocol functions between FFT / CP removal and DBF. Option 7-2' could be a division of communication protocol functions between RE demapping and channel estimation. Option 7-2a' could be a division of communication protocol functions between DBF and RE demapping. Option 7-3' could be a division of communication protocol functions between demodulation and descrambling. Option 7-2' can also be referred to as Ie', Ie for uplink, or Ie segmentation for uplink. Option 7-2' can be considered the same as the uplink segmentation method of the eCPRI protocol. In some examples, if the communication protocol functions are divided between equalization and demodulation, this segmentation point can be called uplink performance improvement (ULIP)-A, Ie2 for uplink, Ie2 segmentation for uplink, NG-LLS, etc. If the communication protocol functions are divided between channel estimation and equalization, this segmentation point can be called ULIP-B.

[0347] It is clear that the segmentation method within the MAC and RLC layers can refer to the segmentation method within the PHY layer. The specific communication functions involved in each protocol layer and the determination of which functions to be segmented together can be determined according to the actual situation. This application does not limit this.

[0348] Typically, a fixed segmentation method can be used to deploy the communication protocol functions on each entity. For example, before deployment, the segmentation points for the communication protocol functions can be set based on prior statistical information, such as network peak rate and average data rate requirements, and the functional entities can be deployed according to this segmentation method. After deployment, the communication protocol functions on each entity remain unchanged. For example, the segmentation methods mentioned above, such as CPRI, eCPRI, or the segmentation methods mentioned in options 1 to 8, can be used.

[0349] Referring to Table 1, taking a channel bandwidth of 100MHz, modulation scheme of 256 quadrature amplitude modulation (QAM), and uplink and downlink multiple-input multiple-output (MIMO) streams of 8 as an example, the bandwidth and transmission delay requirements of the fronthaul interface for different splitting methods are shown.

[0350] Table 1

[0351] It can be seen that the closer the segmentation method is to the lower layer, the more communication protocol functions are handled on the BBU or DU, resulting in higher computing resource utilization and lower energy consumption. However, the closer the segmentation is to the lower layer, the higher the demand for link bandwidth capacity and transmission latency. Conversely, the closer the segmentation method is to the upper layer, the lower the demand for fronthaul link bandwidth and transmission latency. However, this also leads to the deployment of more communication protocol functions on the RRU or RU, resulting in greater energy consumption and reduced computing resource utilization.

[0352] Currently, functional entity configuration often employs a fixed partitioning method. This fixed partitioning approach cannot meet the demands of various communication scenarios that require flexible configuration. In some scenarios, communication latency may not be adequately met. Alternatively, in others, larger data processing volumes may be needed, leading to increased resource consumption by the functional entities.

[0353] Therefore, embodiments of this application provide a method for determining communication protocol functions, in which a first functional entity can determine to migrate a first communication protocol function module to a second functional entity. This allows the first communication protocol function module to flexibly migrate between the first and second functional entities, thereby ensuring communication efficiency and reducing resource consumption in the face of flexible changes in communication scenarios.

[0354] The method and apparatus for determining network communication protocol functions will be further described below with reference to the accompanying drawings. It is understood that the embodiments of this application use a first functional entity and a second functional entity as examples of the execution subjects of the interaction illustration, but this application does not limit the execution subjects of the interaction illustration. For example, the first functional entity and the second functional entity can be network devices. The method executed by the network device in this application can also be implemented by modules (e.g., circuits, chips, or chip systems) in the network device, or by logical nodes, logical modules, or software that can implement all or part of the functions of the network device.

[0355] In the embodiments of this application, the term "wireless communication" can also be abbreviated as "communication", and the term "communication" can also be described as "data transmission", "information transmission" or "transmission".

[0356] Figure 9 is a schematic diagram of a communication scenario provided in an embodiment of this application.

[0357] As shown in Figure 9, the access network equipment can be divided into multiple functional entities such as RU 210, DU 220, and CU 230. Of course, the access network equipment may include one or more RU 210s, one or more DU 220s, and one or more CU 230s. The CU 230 is connected to the 5GC 240 and is used to realize communication with the core network equipment. In various embodiments of this application, the core network equipment may also be referred to as a core network element.

[0358] Among them, 5GC 240 can be connected to multiple CU 230, one CU 230 can be connected to multiple DU 220, and one DU 220 can be connected to multiple RU 210.

[0359] 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 via the NG interface. The access network device is used to provide wireless network connectivity between the terminal and the core network.

[0360] The CU 230 can manage the RRC, SDAP, and PDCP layer protocols of access network devices and control one or more DU operations. The CU 230 communicates with the DU 220 via the F1 interface.

[0361] The DU 220 can host the RLC, MAC, and PHY layers of access network devices, 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.

[0362] The RU 210 can be referred to as a wireless unit, radio frequency unit, or radio frequency remote unit. Its main functions include receiving and transmitting baseband signals, as well as modulation and demodulation of radio frequency signals, data processing, and power amplification. The RU can be deployed close to the antenna, resulting in low feeder loss.

[0363] The 5GC 240 can include any possible core network elements such as AMF entities, SMF entities, UPF entities, and UDM entities. Together with the RAN, the 5GC constitutes the 5G network, providing users with service channels to connect to data networks and servers.

[0364] The RAN provides wireless network connectivity between the UE and the core network. The RAN can include access network equipment, such as gNBs. In some cases, "access network equipment" can refer to the entire RAN. RAN deployment can include centralized RAN (CRAN) and distributed RAN (DRAN). CRAN uses a separate BBU and RRU architecture, with each BBU located in a central equipment room, forming a BBU pool. It communicates with the RRUs via the fronthaul network. DRAN uses a distributed deployment of BBUs and RRUs. Each BBU is deployed separately in a rack, while the RRUs can be deployed together in the rack with the BBUs, or the RRUs can be deployed close to the antenna on a tower.

[0365] In some examples, RU 210, DU 220, and CU 230 can be deployed on the same physical device or on different physical devices. Alternatively, some functional entities of RU 210, DU 220, and CU 230 may be deployed on the same physical device, while other functional entities may be deployed on different physical devices. This embodiment of the application does not impose any limitations on this.

[0366] It is understandable that access network equipment can also include cases where it is split into two functional entities. For example, if CU 230 and DU 220 are deployed on the same physical device, CU 230 and DU 220 can be regarded as one functional entity. Alternatively, if DU 220 and RU 210 are deployed on the same physical device, DU 220 and RU 210 can be regarded as one functional entity.

[0367] Of course, this application is not limited to the 5G network architecture; the embodiments of this application are also applicable to LTE networks and other possible future network architectures such as future communication networks. It should be understood that the embodiments of this application can be applied to any network architecture with communication connectivity capabilities.

[0368] Referring to Figure 10, assuming the first communication protocol function module is deployed in the first functional entity, when the first communication protocol module needs to be migrated to the second functional entity, it is necessary to ensure that the state of the first communication protocol function module after the migration is synchronized. Therefore, this can be achieved using the method shown in Figure 11.

[0369] Figure 11 is a schematic diagram of a method for determining network communication protocol functions provided in an embodiment of this application.

[0370] This communication process is applicable to, but not limited to, the communication scenarios shown in Figures 1 and 9. This method can be applied to LTE, LTE frequency division duplex (FDD) systems, LTE TDD, 5G systems, or NR systems, future communication systems (such as future communication systems), and V2X. V2X can include vehicle-to-network (V2N), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), long-term evolution-vehicle (LTE-V), vehicle-to-everything (V2X), MTC, IoT, long-term evolution-machine (LTE-M), machine-to-machine (M2M), and device-to-device (D2D) wireless communication scenarios. The first and second functional entities involved in this application embodiment can be network devices. The first and second functional entities can be deployed on the same network device or on different network devices; this application embodiment does not impose any limitations on this. In the various embodiments of this application, the network device can generally be considered as an access network device. However, in some cases, the network device can also be a core network device. The method may include the following steps:

[0371] This application will describe two scenarios in its embodiments:

[0372] Scenario 1:

[0373] S101, the first functional entity determines the first information.

[0374] The first information can be used to instruct the migration of a first communication protocol function module to a second functional entity. It can be considered that the first information instructs the second functional entity to generate, establish, activate, enable, or run the first communication protocol function module. For example, the first information can also be called a function migration request, function migration instruction, function migration instruction information, communication protocol function migration information, function activation instruction, or function establishment instruction, etc., and this application embodiment does not limit the scope of the description. In the various embodiments of this application, "running" a certain function module can be considered as the business flow needing to be processed through that function module.

[0375] In some examples, the first communication protocol functional module includes a Layer 2 communication protocol functional module and / or a Layer 3 communication protocol functional module. It can be understood that the wireless air interface protocol stack can be divided into three layers: the physical layer (Layer 1), the data link layer (Layer 2), and the network layer (Layer 3). The data link layer (Layer 2) can include the MAC layer, RLC layer, PDCP layer, and SDAP layer. The SDAP layer is located in the user plane and is responsible for mapping from QoS flows to DRBs. The other three sub-layers of the data link layer, excluding the SDAP layer, can be located in both the control plane and the user plane. For example, in the control plane, they are responsible for the transmission, encryption, and integrity protection of radio bearer signaling; in the user plane, they are responsible for the transmission and encryption of user service data. The network layer (Layer 3) can refer to the RRC layer, located in the control plane of the access network, and is responsible for all signaling processing between access network devices and terminals.

[0376] In other words, Layer 3 communication protocol function modules can implement control plane signaling interaction with the UE, while Layer 2 communication protocol function modules do not. Furthermore, Layer 2 communication protocol function modules have higher protocol functions than the physical layer. The physical layer can also be referred to as Layer 1. For example, Layer 2 communication protocol function modules may include MAC layer function modules, RLC layer function modules, PDCP layer function modules, etc. Layer 3 communication protocol function modules may include RRC layer function modules, etc.

[0377] The first communication protocol functional module may include functional modules for processing the MAC protocol layer, such as a MAC layer functional module. Alternatively, the first communication protocol functional module may include functional modules for processing the RLC protocol layer, such as an RLC layer functional module.

[0378] The embodiments of this application can be applied to various different functional modules for the first communication protocol module. By flexibly migrating suitable communication protocol functional modules according to actual conditions, the system's versatility is improved.

[0379] In some embodiments, a first functional entity may determine first information based on a first parameter. The first parameter may include: a parameter indicating the service load status of the first functional entity; or a parameter indicating the computing power status of the first functional entity; or a parameter indicating the energy consumption status of the first functional entity; or a parameter indicating the traffic status of the interface between the first functional entity and the second functional entity; or a parameter indicating both the service load status and the computing power status of the first functional entity; or a parameter indicating both the service load status and the energy consumption status of the first functional entity; or a parameter indicating both the service load status and the traffic status of the interface between the first functional entity and the second functional entity; or a parameter indicating both the computing power status and the energy consumption status of the first functional entity; or a parameter indicating both the computing power status and the traffic status of the interface between the first functional entity and the second functional entity; or a parameter indicating both the energy consumption status and the traffic status of the interface between the first functional entity and the second functional entity. Parameters indicating the traffic status of the interface between the first and second functional entities; or, parameters indicating the service load status of the first functional entity, parameters indicating the computing power status of the first functional entity, and parameters indicating the energy consumption status of the first functional entity; or, parameters indicating the service load status of the first functional entity, parameters indicating the computing power status of the first functional entity, and parameters indicating the traffic status of the interface between the first and second functional entities; or, parameters indicating the service load status of the first functional entity, parameters indicating the energy consumption status of the first functional entity, and parameters indicating the traffic status of the interface between the first and second functional entities; or, parameters indicating the computing power status of the first functional entity, parameters indicating the energy consumption status of the first functional entity, and parameters indicating the traffic status of the interface between the first and second functional entities; or, parameters indicating the service load status of the first functional entity, parameters indicating the computing power status of the first functional entity, parameters indicating the energy consumption status of the first functional entity, and parameters indicating the traffic status of the interface between the first and second functional entities.

[0380] The embodiments of this application can use appropriate first parameters to determine the instruction to migrate the first communication protocol function module to the second function entity according to the actual situation, thereby improving the universality of the system.

[0381] In some cases, the first functional entity can be deployed in the CU. Alternatively, the first functional entity can be considered as the CU.

[0382] For example, the first functional entity can be deployed in a DU. Or, the first functional entity can be considered as a DU.

[0383] Alternatively, the first functional entity can be deployed in the RU. Or, the first functional entity can be considered as the RU.

[0384] The embodiments of this application are applicable to any possible first functional entity according to the actual situation, thereby improving the universality of the system.

[0385] In some examples, a first communication protocol function module may be configured in the first functional entity. In some examples, the first communication protocol function module may be running; for example, it can be considered to be in an active or enabled state. That is, the first communication protocol function module in the first functional entity has already processed communication signals and may be currently being used for communication signal processing. The first functional entity may determine to migrate the first communication protocol function module to the second functional entity.

[0386] In this embodiment, the first functional entity can be configured with a first communication protocol function module in an active or enabled state. In this case, the first functional entity can determine to migrate the first communication protocol function module to the second functional entity. By flexibly migrating the first communication protocol function, the first functional entity and the second functional entity can flexibly adapt to different communication scenarios, ensure communication efficiency, and reduce resource consumption.

[0387] In some examples, the first functional entity may be configured with a first communication protocol functional module. The first functional entity can then consider setting the first communication protocol functional module to a deactivated, deregistered, or disabled state. The deactivated or disabled state can be understood as the first communication functional module still being retained, but no longer used. Deactivation can also be referred to as de-enabling, pausing, suspending, interrupting, aborting, or terminating. The deregistered state can be considered as directly deregistering the first communication protocol functional module, or it can be considered as deleting the first communication protocol functional module.

[0388] In this embodiment, the first functional entity can also be activated, deactivated, or deactivated to avoid resource waste caused by the first functional entity and the second functional entity running the same first communication protocol functional module at the same time.

[0389] S102, the first functional entity sends first information to the second functional entity. Correspondingly, the second functional entity receives the first information from the first functional entity.

[0390] For example, the second functional entity can be deployed in the CU. Alternatively, the second functional entity can be considered as the CU.

[0391] For example, the second functional entity can be deployed in the DU. Or, the second functional entity can be considered as the DU.

[0392] Alternatively, the second functional entity can be deployed within the RU. Or, the second functional entity can be considered as the RU.

[0393] The embodiments of this application are applicable to any possible second functional entity according to the actual situation, thereby improving the universality of the system.

[0394] In S102, the first functional entity sends first information to the second functional entity so that the second functional entity knows that the first communication protocol functional module needs to be migrated to the second functional entity.

[0395] Scenario 2:

[0396] S103, the second functional entity sends first information to the first functional entity. Correspondingly, the first functional entity receives the first information from the second functional entity.

[0397] It can be assumed that the first information in case 2 is determined by the second functional entity. For example, the second functional entity can determine the first information based on the first parameter. The specific implementation process is similar to the process in S101 where the first functional entity determines the first information based on the first parameter, and will not be described again in this embodiment.

[0398] S104, the first functional entity determines to migrate the first communication protocol functional module to the second functional entity based on the first information.

[0399] The first functional entity can parse the first information received in S103 to determine that the first communication protocol function module needs to be migrated to the second functional entity. This allows the first functional entity to be triggered to migrate the first communication protocol function module to the second functional entity in the future.

[0400] In this embodiment, the first functional entity can determine whether to migrate the first communication protocol functional module to the second functional entity. This allows the first communication protocol functional module to be flexibly migrated between the first and second functional entities, thereby ensuring communication efficiency and reducing resource consumption in the face of flexible changes in communication scenarios.

[0401] In the network communication protocol function determination method provided in this application, in order to ensure that the first communication protocol function module can achieve state synchronization during the migration process, the method may further include: the first functional entity sending third information to the second functional entity. The third information can be used to indicate parameters related to the first communication protocol function module. These parameters can be used to configure the first communication protocol function module in the second functional entity. In some examples, the third information may be called state synchronization indication information, state synchronization indication, physical layer state synchronization indication, etc., and this application embodiment does not limit the scope of the terminology used.

[0402] In the various embodiments of this application, the communication protocol function module and the communication protocol function can be considered to have the same meaning and can be used interchangeably.

[0403] For example, the first communication protocol functional module is a functional module used to process the MAC protocol layer. Then, the parameters related to the first communication protocol functional module may include at least one of the following: MAC hybrid automatic repeat request (HARQ) process list, frame number, subframe number, resource block (RB) resource allocation, modulation and coding scheme (MCS) order, multi-user pairing information, precoding coefficients for superimposing different data streams supported by multiple-input multiple-output (MIMO), weighting coefficients for superimposing different data streams in MIMO, or RLC sequence number.

[0404] The superposition of different data streams in MIMO can also be referred to as the superposition of different layers of data streams in MIMO. This layer does not refer to the protocol layer mentioned earlier, but rather to the number of concurrent streams supported by MIMO. The number of MIMO layers can be considered equivalent to the number of MIMO streams, which in turn is equivalent to the rank of the MIMO channel.

[0405] Parameters related to the first communication protocol functional module may include: MAC HARQ process list; or, subframe number, RB resource allocation; or, RB resource allocation, MCS order, multi-user pairing information; or, MAC HARQ process list, frame number, precoding coefficients used for superposition between different data streams supported by MIMO, RLC sequence number; or, MAC HARQ process list, frame number, RB resource allocation, MCS order, multi-user pairing information; or, MAC HARQ process list, frame number, RB resource allocation, MCS order, multi-user pairing information, RLC sequence number; or, MAC HARQ process list, frame number, RB resource allocation, MCS order, multi-user pairing information, precoding coefficients used for superposition between different data streams supported by MIMO, RLC sequence number; or, MAC HARQ process list, frame number, subframe number, RB resource allocation, MCS order, multi-user pairing information, precoding coefficients used for superposition between different data streams supported by MIMO, RLC sequence number; or, MAC HARQ process list, frame number, subframe number, RB resource allocation, MCS order, multi-user pairing information, precoding coefficients for superimposing different data streams supported by MIMO, weighting coefficients for superimposing different data streams of MIMO, and RLC sequence number.

[0406] It is understood that the parameters related to the first communication protocol functional module may also include any one, two, three, four, five, six, seven or eight of the above parameters. For ease of description, the embodiments of this application will not list them one by one here.

[0407] The RLC sequence number can be the RLC sequence number corresponding to the last data packet processed by the first communication protocol functional module. This RLC sequence number can be used for synchronization of data processing by the first communication protocol functional module in the second functional entity. For example, the first communication protocol functional module in the second functional entity can continue to number the data to be processed based on this RLC sequence number to ensure the continuity of data transmission.

[0408] When the first communication protocol function module is a function module used to process the MAC protocol layer, the parameters related to the first communication protocol function module can also be called MAC scheduling information.

[0409] For example, the first communication protocol functional module is a functional module used to process the RLC protocol layer. Then, the parameters related to the first communication protocol functional module may include at least one of the following: the mapping relationship between the logical channel identifier (LCID) and the logical channel, the mapping relationship between the DRB and the logical channel, the mapping relationship between the logical channel and the transport channel, the acknowledgment (ACK) flag for packet retransmission, the negative acknowledgment (NACK) flag for packet retransmission, the RLC sequence number, and the PDCP sequence number.

[0410] The logical channel can be a communication channel located between the MAC layer and the RLC layer. It can include channels provided to MAC layer functional modules for different data types. For example, a radio bearer can be mapped to an RLC channel, and the RLC channel can then be mapped to a logical channel. Therefore, the LCID can be considered to have a mapping relationship with the RLC channel identifier (ID) and the radio bearer ID.

[0411] Logical channels can include control channels for transmitting control plane information, such as: downlink channels for transmitting broadcast system control information, i.e., broadcast control channels (BCCH); downlink channels for forwarding paging messages and system information changes, i.e., paging control channels (PCCH); channels for transmitting control information between the UE and the network device when no RRC connection has been established, i.e., common control channels (CCCH), such as those used to transmit signalalling radio bearers (SRBs); and one-to-one channels for transmitting control information between the UE and the network device when an RRC connection has been established, i.e., dedicated control channels (DCCH), such as those used to transmit SRB1, SRB2, etc. Logical channels can also include traffic channels for transmitting user plane information, such as dedicated traffic channels (DTCH). A DTCH can be considered a one-to-one channel, pointing to a single UE, used to transmit the UE's service data, and exists in both uplink and downlink. Of course, logical channels may also include other possible channels, which will not be listed one by one in the embodiments of this application.

[0412] A transport channel can be a communication channel located between the MAC layer and the PHY layer, used to transmit different types of data. Transport channels have a mapping relationship with logical channels and physical channels. For example, a transport channel can map data from multiple logical channels to a physical channel.

[0413] For the uplink, CCCH, DCCH, and DTCH can all be mapped to transport channels, such as the uplink shared channel (UL-SCH). Correspondingly, the physical channel corresponding to this UL-SCH can be the physical uplink shared channel (PUSCH).

[0414] For downlink, the transport channel corresponding to the PCCH can be the paging channel (PCH), and the corresponding physical channel for this PCH can be the physical downlink shared channel (PDSCH). The transport channel mapped to the BCCH can be divided into two parts: one part can be mapped to the broadcast channel (BCH), and the corresponding physical channel for this BCH can be the physical broadcast channel (PBCH). This PBCH can primarily carry the master information block (MIB). The other part can be mapped to the downlink shared channel (DL-SCH), and the corresponding physical channel for this DL-SCH can be the physical downlink shared channel (PDSCH). This PDSCH can carry other system messages, such as system information block (SIB) 1, SIB 2, etc. The CCCH, DCCH, DTCH, and multicast control channel (MCCH) can be mapped to the transport channel DL-SCH, and the corresponding physical channel can be PDSCH. When a multicast traffic channel (MTCH) carries single-cell data, it can be mapped to a transport channel (DL-SCH). Correspondingly, the physical channel can be PDSCH. Conversely, when the MTCH carries multi-cell data, it can be mapped to a multicast channel (MCH). Correspondingly, the physical channel can be a physical multicast channel (PMCH).

[0415] Parameters related to the first communication protocol functional module may include: the mapping relationship between LCID and logical channel; or, the mapping relationship between LCID and logical channel, and the ACK flag for packet retransmission; or, the mapping relationship between DRB and logical channel, and the NACK flag for packet retransmission, and the RLC sequence number; or, the mapping relationship between logical channel and transport channel, and the NACK flag for packet retransmission, the RLC sequence number, and the PDCP sequence number; or, the mapping relationship between DRB and logical channel, and the ACK flag for packet retransmission, and the NACK flag for packet retransmission, the RLC sequence number, and the PDCP sequence number; or, the mapping relationship between LCID and logical channel, and the mapping relationship between DRB and logical channel, and the mapping relationship between logical channel and transport channel, and the ACK flag for packet retransmission, and the NACK flag for packet retransmission, the RLC sequence number, and the PDCP sequence number; or, the mapping relationship between LCID and logical channel, and the mapping relationship between DRB and logical channel, and the mapping relationship between logical channel and transport channel, and the ACK flag for packet retransmission, and the NACK flag for packet retransmission, the RLC sequence number, and the PDCP sequence number.

[0416] It is understood that the parameters related to the first communication protocol functional module may also include any one, two, three, four, five or six of the above parameters. For ease of description, the embodiments of this application will not be listed one by one here.

[0417] When the first communication protocol functional module is used to process the RLC protocol layer, parameters such as the mapping relationship between LCID and logical channel, the mapping relationship between DRB and logical channel, and the mapping relationship between logical channel and transport channel can also be called RLC logical channel related parameter information. This type of information is mainly related to the logical channel. Parameters such as the ACK flag used for packet retransmission, the NACK flag used for packet retransmission, the RLC sequence number, and the PDCP sequence number can also be called RLC buffer retransmission information. This mainly includes parameters indicating buffering in the RLC to ensure the continuity of data processing during the migration of RLC layer functional modules.

[0418] In various embodiments of this application, the identifier can be an ID or an index.

[0419] The parameters related to the various first communication protocol functional modules mentioned above can be created or dynamically modified by the first communication protocol functional modules. For example, the values ​​of the corresponding parameters can be adjusted during data processing. Some parameters can be dynamically adjusted within each slot or subframe, and the specific adjustment period can be configured according to the actual situation. This application embodiment does not limit this.

[0420] According to the embodiments of this application, when the first communication protocol functional module is a certain functional module, the first functional entity can obtain the corresponding parameters. This allows the state to remain synchronized after the functional module is migrated to the second functional entity, improving system stability and ensuring the continuity of data transmission.

[0421] Considering that during the migration of the first communication protocol functional module from the first functional entity to the second functional entity, the first communication protocol functional module may contain a certain amount of buffered data. Related technologies do not consider how to handle the buffered data in the original communication protocol functional module and newly arrived data. This can lead to discontinuous data processing and packet loss. In severe cases, it can even cause communication interruption, affecting the consistency of user experience. Therefore, this application embodiment will describe, with reference to Figure 12, how to process the buffered data and potentially newly arrived data in the first communication protocol functional module during the migration process.

[0422] Figure 12 is a schematic diagram of a method for determining network communication protocol functions provided in an embodiment of this application.

[0423] This communication process is applicable to, but not limited to, the communication scenarios shown in Figures 1 and 9. This method can be applied to LTE, LTE FDD, LTE TDD, 5G, or NR systems, future communication systems (such as future communication systems), V2X (which 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 first and second functional entities involved in this application embodiment can be network devices. The first and second functional entities can be deployed on the same network device or on different network devices; this application embodiment does not impose such limitations. 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:

[0424] S201, the first functional entity sends first information to the second functional entity. Correspondingly, the second functional entity receives the first information from the first functional entity.

[0425] The first functional entity can determine the first information based on the first parameter, and then send the first information to the second functional entity.

[0426] S202, the second functional entity sends first information to the first functional entity. Correspondingly, the first functional entity receives the first information from the second functional entity.

[0427] It is understood that the implementation process of S201 can refer to the description of the corresponding embodiments in S101 and S102, and the implementation process of S202 can refer to the description of the corresponding embodiments in S103. The embodiments of this application will not repeat the details here. Furthermore, S201 and S202 can be executed selectively. For example, executing S201 without executing S202, or executing S202 without executing S201, is not limited in this application embodiment.

[0428] In some examples, upon receiving, determining, or sending the first information, the first functional entity may stop receiving newly arriving data from the first communication protocol functional module. That is, for the first communication protocol functional module deployed and running in the first functional entity, if it is determined that the first communication protocol functional module needs to be migrated to the second functional entity, receiving newly arriving data from that first communication protocol functional module can be stopped immediately.

[0429] This avoids the need for the first communication protocol function module to be migrated to continuously receive newly arriving data, preventing data packet loss and ensuring the continuity and stability of data transmission.

[0430] S203, the first functional entity determines the processing method of the cached data in the first communication protocol functional module.

[0431] The following sections will describe various methods for processing cached data.

[0432] Solution 1:

[0433] For example, the processing of cached data may include discarding cached data in the first communication protocol functional module. That is, if the first functional entity determines to migrate the first communication protocol functional module to the second functional entity, it may decide to directly discard the cached data in the first communication protocol functional module without further processing of the cached data in the first communication protocol functional module.

[0434] In this case, the migrated first communication protocol function module in the second functional entity can directly process the newly arrived data, thereby reducing the data packet processing latency during the migration process of the first communication protocol function module.

[0435] Solution 2:

[0436] For example, the processing of cached data may include continuing to send cached data from the first communication protocol functional module. That is, if the first functional entity determines to migrate the first communication protocol functional module to the second functional entity, it may decide to continue sending the cached data from the first communication protocol functional module until all cached data in the first communication protocol functional module has been sent, or until there is no more cached data in the first communication protocol functional module. This processing ensures that all cached data in the first communication protocol functional module deployed in the first functional entity can be processed, thereby avoiding data packet loss during the migration of the first communication protocol functional module.

[0437] Solution 3:

[0438] For example, the processing method for cached data may include continuously sending cached data from the first communication protocol functional module within a first time period. The start time of the first time period can be the moment when the first communication protocol functional module stops receiving newly arriving data, and the duration of the first time period is called the first duration. The first duration may also be referred to as the maximum transmission duration, maximum sending duration, maximum transmission time, remaining usage time, remaining sending time, remaining sending duration, remaining maximum sending time, etc., and is not limited to these terms in this embodiment.

[0439] In this example, the first communication protocol module within the first functional entity can continuously process cached data during a first time period and stop processing cached data, such as discarding it, after the first time period. This maintains a balance between the cached data loss rate and the latency of processing new data packets. For example, the first functional entity can dynamically adjust the duration of the first time period based on the number of new data arriving at the first communication protocol module. Of course, the duration of the first time period can also be determined by the second functional entity, or by any other device or functional entity; this embodiment does not limit this. Accordingly, once the duration of the first time period is determined by a functional entity or device other than the first functional entity, a new duration of the first time period can be sent to the first functional entity. The first functional entity then receives the new duration of the first time period from the other functional entity or device.

[0440] Solution 4:

[0441] For example, the processing method for cached data may include determining whether to discard the remaining unsent cached data based on the remaining unsent cached data packets. In other words, the first functional entity can decide whether to discard the remaining unsent cached data based on the situation of the remaining unsent cached data in the first communication protocol functional module.

[0442] For example, the first functional entity can determine the ratio between the sent buffered data and the remaining unsent buffered data, referred to as the first ratio. The first functional entity can continue sending buffered data in the first communication protocol functional module. When the first functional entity determines that the first ratio is greater than or equal to a first threshold, the first functional entity can discard the remaining unsent buffered data. Otherwise, the first functional entity continues sending buffered data in the first communication protocol functional module. The first threshold can be any positive number greater than or equal to 0. The sent buffered data should be considered as the buffered data sent after the first communication protocol functional module stops receiving new data.

[0443] It's clear that for the case where the first threshold is 0, the processing method is similar to processing method 1. This condition is met if the amount of cached data already sent is 0. The larger the first threshold, the closer the processing method is to processing method 2. In other words, a larger first threshold means that more cached data needs to be sent compared to the remaining unsent cached data to meet the condition.

[0444] For example, the first functional entity can determine the ratio between the sent cached data and the cache capacity corresponding to the first communication protocol functional module, referred to as the second ratio. The first functional entity can continue to send cached data in the first communication protocol functional module. When the first functional entity determines that the second ratio is greater than or equal to a second threshold, the first functional entity can discard the remaining unsent cached data. Otherwise, the first functional entity continues to send cached data in the first communication protocol functional module. The second threshold can be any positive number greater than or equal to 0 and less than or equal to 1.

[0445] For the case where the second threshold is 0, the processing method is similar to processing method 1. For example, if the amount of sent buffered data is 0, this condition is met. Considering that the buffered data in the first communication protocol functional module may not fill the buffer capacity (e.g., the buffer capacity is 5KB, but when the first communication protocol functional module stops receiving new data, the remaining unsent buffered data is only 3KB), the upper limit of the second threshold can be dynamically adjusted. For example, the second threshold can be less than or equal to the ratio between the remaining unsent buffered data and the corresponding buffer capacity of the first communication protocol functional module when it stops receiving new data.

[0446] The second threshold is set as the ratio between the remaining unsent buffered data and the buffer capacity corresponding to the first communication protocol functional module when the first communication protocol functional module stops receiving new data. Therefore, the case where the second ratio equals the second threshold is similar to processing method 2.

[0447] For example, the first functional entity can determine the ratio between the remaining unsent cached data and the cache capacity corresponding to the first communication protocol functional module, referred to as the third ratio. The first functional entity can continue to send cached data in the first communication protocol functional module. If the first functional entity determines that the third ratio is less than or equal to a third threshold, the first functional entity can discard the remaining unsent cached data. Otherwise, the first functional entity continues to send cached data in the first communication protocol functional module. The third threshold can be any positive number greater than or equal to 0 and less than or equal to 1.

[0448] For the case where the third threshold is 0, the processing method is similar to processing method 2. For example, if the remaining unsent cached data is 0, the condition is met. For the case where the third threshold is 1, the processing method is similar to processing method 1. For example, if the remaining unsent cached data is the same as the cache capacity corresponding to the first communication protocol functional module, the third ratio is 1. Therefore, in all cases, this third ratio will be less than or equal to 1. Thus, when the third threshold is 1, the condition can be considered directly met, and the remaining unsent cached data can be discarded.

[0449] This application provides various methods for processing cached data based on the remaining unsent cached data. This allows for the selection of an appropriate method to process cached data according to the actual situation, ensuring data processing latency and data transmission stability.

[0450] This application also provides various different methods for processing cached data, so as to use the appropriate processing method to process cached data according to the actual situation, and ensure data processing latency and data transmission stability.

[0451] In some examples, the first functional entity can decide on its own how to process the cached data in the first communication protocol functional module. Of course, in other examples, the processing method for the cached data in the first communication protocol functional module can also be determined by other devices or functional entities besides the first functional entity. In this case, the first functional entity can also receive second information. This second information is used to indicate the method for processing the cached data in the first communication protocol functional module.

[0452] For example, the second functional entity can determine the second information. The second functional entity sends the second information to the first functional entity, and correspondingly, the first functional entity receives the second information from the second functional entity.

[0453] In scenarios where the first functional entity receives the first information, to reduce signaling resource consumption, the second information and the first information can be carried in the same signaling. For example, the second functional entity can instruct the first functional entity to migrate the first communication protocol module while simultaneously instructing how to process the cached data in the first communication protocol module.

[0454] The embodiments of this application can also determine the processing method of cached data in the first communication protocol functional module through other devices or functional entities, thereby realizing flexible processing of cached data.

[0455] S204, the first functional entity processes the cached data in the first communication protocol functional module according to the processing method.

[0456] The first functional entity can process the cached data in the first communication protocol functional module according to the processing method determined in S203. This could involve continuing to send cached data, discarding the remaining unsent cached data, or sending a portion of the cached data first and discarding the remaining unsent cached data if certain conditions are met. These conditions could include, for example, the duration of a first time period, the relationship between a first proportion and a first threshold, the relationship between a second proportion and a second threshold, and the relationship between a third proportion and a third threshold. For details, please refer to the corresponding description in S203; this embodiment will not be repeated here.

[0457] In some examples, after the first functional entity processes the cached data according to any of the above processing methods, the first communication protocol function module on the second functional entity can process subsequent new data accordingly.

[0458] For example, regarding processing method 1, the first functional entity can, upon determining to migrate the first communication protocol function module to the second functional entity, stop receiving newly arriving data from the first communication protocol function module within the first functional entity, and determine to directly discard the cached data of the first communication protocol function module within the first functional entity. Then, the second functional entity can receive data that should have arrived at the first communication protocol function module in the first functional entity but was not received, thus achieving data redirection. Furthermore, the second functional entity can immediately process newly arriving data from the first communication protocol function module within the second functional entity. This is because the first functional entity no longer processes the cached data of the first communication protocol function module within the first functional entity. Therefore, the first communication protocol function module in the second functional entity, which has the same communication protocol functionality, can process subsequent data to ensure the continuity of data transmission and reduce transmission latency.

[0459] For example, regarding processing method 2, the first functional entity can continue sending cached data from the first communication protocol function module after determining to migrate it to the second functional entity, until all cached data in the first communication protocol function module has been sent. During this period, the first functional entity stops receiving new data arriving at the first communication protocol function module within the first functional entity. Furthermore, the second functional entity can receive data that should have arrived at the first communication protocol function module in the first functional entity but was not received, thus achieving data redirection. It should be noted that since the first functional entity is still processing the cached data in the first communication protocol function module during this stage, the first communication protocol function module in the second functional entity is used to receive new data and cache it. This continues until the first functional entity has processed all cached data in the first communication protocol function module. The second functional entity can then process the new data cached in the first communication protocol function module within the second functional entity to ensure the continuity of data transmission.

[0460] The first functional entity can send an instruction to the second functional entity after processing all cached data in its first communication protocol functional module. This instruction informs the second functional entity that it can process new data cached in its first communication protocol functional module. For example, this instruction can be the aforementioned third information. This allows the second functional entity to continue processing the newly cached data based on the corresponding parameters in the third information, ensuring the continuity of data transmission. The specific parameters in the third information can be found in the descriptions of the aforementioned embodiments, and will not be repeated here.

[0461] For example, regarding processing method 3, if the first functional entity determines to migrate the first communication protocol function module to the second functional entity, it can continuously send cached data in the first communication protocol function module during the first time period. During the first time period, this processing method is similar to that of processing method 2; the specific implementation process is described in the relevant embodiments of processing method 2 and will not be repeated here. Until the end of the first time period, the first functional entity discards any remaining unsent cached data in the first communication protocol function module. The first functional entity can send an indication message to the second functional entity to inform it that it can process new data cached in the first communication protocol function module of the second functional entity. For example, this indication message can be the aforementioned third information. The second functional entity can continue to process the newly cached data based on the corresponding parameters in the third information to ensure the continuity of data transmission.

[0462] Of course, if the first functional entity finishes sending all the cached data in the first communication protocol function module within the first time period, it can perform subsequent corresponding operations, such as sending an instruction message to instruct the second functional entity to continue processing the data, either when all the cached data has been sent or when it continues to wait until the end of the first time period.

[0463] For example, regarding processing method 4, if the first functional entity determines to migrate the first communication protocol function module to the second functional entity, it can decide whether to continue sending cached data or discard the remaining unsent cached data based on the remaining unsent cached data packets. For instance, if the first functional entity determines that the first proportion is less than the first threshold, it continues sending the remaining unsent cached data until it determines that the first proportion is greater than or equal to the first threshold, at which point it stops sending cached data and discards the remaining unsent cached data. Similarly, if the first functional entity determines that the second proportion is less than the second threshold, it continues sending the remaining unsent cached data until it determines that the second proportion is greater than or equal to the second threshold, at which point it stops sending cached data and discards the remaining unsent cached data. Furthermore, if the first functional entity determines that the third proportion is greater than the first threshold, it continues sending the remaining unsent cached data until it determines that the third proportion is less than or equal to the first threshold, at which point it stops sending cached data and discards the remaining unsent cached data.

[0464] It is understood that, for cases where the first proportion equals the first threshold, the second proportion equals the second threshold, and the third proportion equals the third threshold, the first functional entity may also send the remaining unsent data. In other words, for such critical points, the entity may choose to continue sending the remaining unsent cached data or choose to stop sending and discard the remaining unsent cached data, depending on the actual situation. This application embodiment does not limit this choice.

[0465] In processing method 4, if the first functional entity determines to discard the remaining unsent cached data, the first functional entity can send an indication message to the second functional entity to inform it that it can process the new data cached by the first communication protocol function module in the second functional entity. For example, this indication message can be the aforementioned third information. This allows the second functional entity to continue processing the newly cached data based on the corresponding parameters in the third information, ensuring the continuity of data transmission.

[0466] The data that the second functional entity receives but which should have reached the first communication protocol functional module in the first functional entity but was not received, as mentioned in the above example, can be referred to as the first data.

[0467] In this embodiment of the application, during the migration of the first communication protocol functional module, a processing method for cached data in the first communication protocol functional module deployed within the first functional entity is configured. This enables the first functional entity to process the cached data of its internally deployed first communication protocol functional module according to this processing method. This avoids data packet loss, ensures the continuity of data transmission, and improves the user experience.

[0468] In the network communication protocol function determination method provided in this application embodiment, the communication protocol function modules in each functional entity can be pre-configured. Therefore, the method shown in Figures 11 and 12 above may further include: a first functional entity receiving or generating fourth information. The fourth information is used to configure the first communication protocol function module. The first functional entity sends the fourth information to a second functional entity.

[0469] The fourth piece of information can be determined based on the first QoS parameter. The first QoS parameter indicates the QoS requirements of the service. Therefore, it can be understood that the first functional module configured through the fourth information can be used to meet the QoS requirements of the service. In some examples, the fourth information can be determined based on different granularities, such as different functional entities, services, cells, terminals, QoS, DRB, data packets, etc., and different QoS requirements can correspond to different granularities.

[0470] In some examples, the fourth information can be obtained at the granularity of the functional entity. That is, the fourth information can be configured according to the actual situation of the first and / or second functional entities. For example, configuring the deployment of the MAC layer functional module in the first functional entity, or configuring the deployment of both the MAC layer and RLC layer functional modules in the first functional entity. Another example is configuring the deployment of the RLC layer functional module in the first functional entity, or configuring both the MAC layer and RLC layer functional modules in the first functional entity.

[0471] For example, the fourth piece of information can be obtained at the granularity of CU. As another example, the fourth piece of information can be obtained at the granularity of DU. And yet another example, the fourth piece of information can be obtained at the granularity of RU.

[0472] In other examples, the fourth information can be obtained at the cell level. That is, the fourth information can be configured according to the actual situation of the cell corresponding to the first functional entity and / or the second functional entity.

[0473] In other examples, the fourth information can be obtained at the terminal level. For instance, if the terminal communicating with the first or second functional entity changes from a first type of terminal to a second type of terminal, fourth information applicable to the first type of terminal and fourth information applicable to the second type of terminal can be configured separately. The first type of terminal and the second type of terminal can be terminals from different manufacturers or different models; this application does not limit this.

[0474] In other examples, the fourth piece of information can be obtained at the business level. For instance, when the business changes, different fourth pieces of information can be configured for different businesses.

[0475] For example, the fourth piece of information can be obtained at the DRB (Diagnosis Related Groups) level. Another example is that the fourth piece of information can be obtained at the QoS (Quality of Service) level. Yet another example is that the fourth piece of information can be obtained at the packet level.

[0476] The embodiments of this application can use appropriate granularity to configure the fourth information according to the actual situation, so as to enable functional entities at different granularities to communicate according to appropriate communication protocol functions, thereby improving the system's versatility.

[0477] The embodiments of this application can pre-configure the first communication protocol function module with appropriate granularity according to actual conditions, so as to use more appropriate functional entities to run the corresponding communication protocol function module in different scenarios, thereby improving system energy efficiency and service capacity.

[0478] Based on the aforementioned fourth information at different granularities, for example, the first communication protocol function module can be configured using this fourth information during the initialization of the first and second functional entities. Assume the first functional entity is CU and the second functional entity is DU. CU can divide the communication protocol functions between CU and DU. Furthermore, CU can generate configuration information for the corresponding communication protocol functions on CU and DU. The configuration information for the corresponding communication protocol functions on CU may include the fourth information. CU can perform initialization configuration based on the configuration information for the corresponding communication protocol functions on CU, during which the first communication protocol function module can be initialized.

[0479] For example, suppose the first functional entity is DU and the second functional entity is RU. The communication protocol functions between DU and RU can be divided using CU. Furthermore, CU can generate configuration information for the corresponding communication protocol functions on DU and RU. The configuration information for the corresponding communication protocol functions on DU may include a fourth piece of information. CU can then send the configuration information for the corresponding communication protocol functions on DU, including the fourth piece of information, to DU. DU can perform initialization configuration based on the received configuration information for the corresponding communication protocol functions on DU, during which the first communication protocol function module can be initialized.

[0480] In some cases, the CU can send configuration information for the corresponding communication protocol function on the CU, including the fourth information, to the DU. The DU can then initialize the first communication protocol function module based on the fourth information. Since the DU is not running the first communication protocol function module at this time, the DU can configure the initialized first communication protocol function module to a deactivated or disabled state. This allows the first communication protocol function module to be activated or enabled later if it needs to be migrated to the DU.

[0481] In this embodiment, the second functional entity can also be pre-configured with the first communication protocol functional module so that the module does not need to be re-established during subsequent migration, thereby improving communication efficiency.

[0482] In the network communication protocol function determination method provided in this application embodiment, a first communication protocol function module may also be deployed and run in the second functional entity. That is, both the first and second functional entities have a first communication protocol function module deployed and running. In this case, assuming the first communication protocol function module deployed and running in the first functional entity participates in the actual data processing, the first communication protocol function module deployed and running in the second functional entity can be used to simulate data processing. In other words, both the first communication protocol function modules deployed and running in the second and first functional entities are used to process data. The difference is that the first communication protocol function module deployed and running in the first functional entity sends the processed data to subsequent communication protocol function modules after data processing, while the first communication protocol function module deployed and running in the second functional entity does not send the processed data to other modules after data processing. Obviously, the first communication protocol function module configured in the second functional entity can be in an active or enabled state.

[0483] Simulated data processing can be achieved through methods such as online model training to simulate data packet processing. Assume that both the CU and DU have MAC and RLC layer functional modules deployed, and that the MAC and RLC layer functional modules deployed in the DU are used in actual communication. Then, the PDCP layer functional module can simultaneously send data to both the RLC layer functional modules deployed in the CU and DU. The RLC layer functional modules in the CU and DU can process data synchronously. The RLC layer functional module in the CU can send the processed data to the MAC layer functional module in the CU, and the RLC layer functional module in the DU can send the processed data to the MAC layer functional module in the DU. Afterward, the MAC layer functional module in the DU can send the processed data to the PHY layer functional module, while the MAC layer functional module in the CU will not send the processed data.

[0484] In the scenario described above, the first functional entity can cease sending parameters related to the first communication protocol functional module. Since the first communication protocol functional module in the second functional entity is also running and may update its parameters periodically, when the first functional entity decides to migrate the first communication protocol functional module, it can directly stop sending data processed by the first communication protocol functional module to other modules. Similarly, the second functional entity can directly send data processed by the first communication protocol functional module to the corresponding modules, ensuring data transmission continuity and significantly reducing communication latency.

[0485] Of course, in other examples, to further ensure that the state of the first communication protocol functional module can be synchronized, the first functional entity can also send parameters related to the first communication protocol functional module to the second functional entity. Similar to the aforementioned embodiments, after receiving the relevant parameters, the second functional entity can update the first communication protocol functional module in the second functional entity based on these parameters to ensure that the data can be processed more accurately and improve communication accuracy.

[0486] The above scheme will now be described with more specific examples.

[0487] Referring to Figures 13 to 15, three scenarios for migrating the first communication protocol functional modules are illustrated. It can be understood that Figures 13 and 14 consider the MAC layer functional module and the RLC layer functional module as a whole for migration; however, in some cases, the MAC layer functional module and the RLC layer functional module can also be relatively independent. For example, the MAC layer functional module can be migrated without migrating the RLC layer functional module; or, the RLC layer functional module can be migrated without migrating the MAC layer functional module.

[0488] Scene 1 (corresponding to Figure 13):

[0489] The MAC layer functional module and the RLC layer functional module are deployed in DU, and need to be migrated from DU to CU.

[0490] Scene 2 (corresponding to Figure 14):

[0491] The MAC layer functional module and the RLC layer functional module are deployed in the CU, and need to be migrated from the CU to the DU.

[0492] Scene 3 (corresponding to Figure 15):

[0493] Both the CU and DU have MAC and RLC layer functional modules deployed. Data processing is performed using the MAC and RLC layer functional modules deployed in the DU. The MAC and RLC layer functional modules deployed in the CU are used for simulation data processing. It is necessary to migrate the MAC and RLC layer functional modules from the DU to the CU; that is, to change the data processing method from using the MAC and RLC layer functional modules deployed in the DU to using the MAC and RLC layer functional modules deployed in the CU.

[0494] In Figure 15, the solid lines connecting the MAC layer functional modules, RLC layer functional modules, and other modules represent the connection methods used in actual communication. Data is exchanged between these modules through the connections shown by the solid lines. The dashed lines connecting the MAC layer functional modules, RLC layer functional modules, and other modules in Figure 15 represent simulated data processing. This simulated data is not used in actual communication. For example, the MAC layer functional module used for simulated data processing may not send simulated data to the PHY layer functional module. The RLC layer functional module used for simulated data processing may not send simulated data to the PDCP layer functional module. Alternatively, the MAC layer functional module can send simulated data to the PHY layer functional module, but in this case, the PHY layer functional module may not expect to receive this data, such as discarding it directly. The RLC layer functional module can also send simulated data to the PDCP layer functional module. Similar to the MAC layer functional modules, the PDCP layer functional module may not expect to receive this data, such as discarding it directly.

[0495] In other examples, the migration direction of the communication protocol functional modules in Scenario 3 can be reversed. For instance, data processing can be changed from using the MAC layer and RLC layer functional modules deployed in the CU to using the MAC layer and RLC layer functional modules deployed in the DU. The specific implementation process is similar to that in Scenario 3.

[0496] It is understood that Figures 13 to 15 above are merely illustrative descriptions, and DU in each figure can be replaced with CU, and RU can be replaced with DU accordingly.

[0497] Figure 16 is a schematic diagram of another method for determining network communication protocol functions provided in an embodiment of this application.

[0498] This communication process is applicable to, but not limited to, the communication scenarios shown in Figures 1 and 9. This method can be applied to LTE, LTE FDD, LTE TDD, 5G, or NR systems, as well as future communication systems (such as future communication systems), V2X (which can include V2N, V2V, V2I, V2P, etc.), LTE-V, vehicle-to-everything (V2X), MTC, IoT, LTE-M, M2M, D2D, and other wireless communication scenarios. Figure 16 illustrates this using the division of access network equipment into CU and DU, and the migration of the first communication protocol functional module between CU and DU as an example. However, it should be understood that in other examples, the first communication protocol functional module can also migrate between DU and RU, or between RNA and RU; this application does not limit this.

[0499] The method may include the following steps:

[0500] S301, the core network element sends the fifth message to the CU. Correspondingly, the CU receives the fifth message from the core network element.

[0501] The fifth piece of information can trigger the access network device to establish DRB configuration. This fifth piece of information can be an initial context setup request, a protocol data unit (PDU) session resource setup request, or a PDU session resource modification request. Core network elements can be elements of the core network control plane.

[0502] For example, the fifth piece of information can carry a PDU session resource setup request list, which may include QoS requirements.

[0503] In some cases, core network elements can be core network control plane (CN-C) functions, such as AMF elements.

[0504] It is clear that the S301 process can be considered as the UE initial access process, the PDU session establishment process, or the PDU session adjustment process.

[0505] The following sections will describe how to configure the communication protocol function module in two different ways.

[0506] Method 1:

[0507] S302, CU determines DRB configuration.

[0508] For example, the CU can determine the DRB configuration based on the fifth information received in S301. For instance, the CU can determine the DRB configuration based on the PDU session resource establishment request information.

[0509] The DRB configuration can include CU protocol layer configuration information and DU protocol layer configuration information. The CU protocol layer configuration information can include parameters corresponding to the CU communication protocol function modules. The DU protocol layer configuration information can include parameters corresponding to the DU communication protocol function modules. The parameters corresponding to the communication protocol function modules can be used to configure the corresponding communication protocol function modules. Clearly, the protocol layer configuration information containing the parameters corresponding to the first communication protocol function module can be considered as the fourth information mentioned above.

[0510] Optionally, the DRB configuration may include indication information regarding the functional partitioning method between CU and DU. This indication information may instruct CU and DU to be partitioned according to a certain partitioning method described in the aforementioned embodiments. CU can inform DU of this indication information so that CU and DU can configure the corresponding protocol layer functions according to this partitioning method. In some examples, the corresponding protocol layer functions can be configured according to default parameters. In this case, the DRB configuration may not include the protocol layer configuration information of each functional entity mentioned above. Each functional entity can complete the initialization configuration of the corresponding protocol layer in its respective functional entity according to the indicated partitioning method and the default parameters.

[0511] S303, the CU sends DU protocol layer configuration information to the DU. Correspondingly, the DU receives the DU protocol layer configuration information from the CU.

[0512] For example, CU and DU can explicitly instruct each functional entity to configure its initial functions. Taking the aforementioned scenario 1 as an example, CU can send DRB configuration information to DU, such as PHY layer configuration information, MAC layer configuration information, and RLC layer configuration information. DU then establishes the PHY layer functional module, MAC layer functional module, and RLC layer functional module according to the above configuration information and configures the relevant parameters.

[0513] Optionally, the CU can also create backups of the MAC layer functional modules and RLC layer functional modules locally, keeping them in a deactivated or disabled state. The CU can copy the MAC layer configuration information to the locally deactivated or disabled MAC layer functional modules, and the RLC layer configuration information to the locally deactivated or disabled RLC layer functional modules. Of course, for scenario 3, this process can be considered a step that needs to be performed.

[0514] The DRB configuration information may include parameters such as: DRB ID, DRB QoS, LCID, radio network temporary identifier (RNTI), the association between DRB and RLC logical channels, the mapping relationship between RLC logical channels and transport channels, RLC transmission mode (e.g., transparent transmission, no-response mode transmission, responsive mode transmission), RLC timer values, and channel quality indicator (CQI). These parameters can be used to configure MAC layer functional modules and RLC layer functional modules. These parameters are considered to be related to UE connection and DRB, and are relatively static and do not change frequently. They are typically created or modified when the UE establishes a connection, the UE disconnects, or the CU actively configures the UE. In some examples, the above parameters may also be sent by the UE to the CU via RRC messages, and then sent by the CU to the DU. For example, the CU may be an RRC functional entity.

[0515] In some cases, DU protocol layer configuration information and / or indications of the function splitting method between CU and DU can be carried in the UE context establishment request or UE context adjustment message sent by CU to DU.

[0516] The processes S301 to S303 described above can also be replaced by the F1 interface management process, where the F1 interface is the communication interface between the CU and DU. The CU can send F1 interface establishment request messages, CU configuration update messages, or DU configuration update messages to the DU. These messages carry DU protocol layer configuration information and / or indication information on the function splitting method between the CU and DU. The CU instructs the DU to establish the initial functional modules and configure the corresponding parameters.

[0517] Alternatively, CU and DU can be configured with their initial functional modules according to the default functional partitioning method. For example, the functional partitioning method and corresponding parameters are pre-set at the factory.

[0518] Both CU and DU can support configuring different function segmentation methods at different granularities. The CU can instruct the DU to configure function segmentation methods based on the granularity of CU, DU, RU, cell, UE, PDU session, QoS flow, and / or data packet. For example, the CU can configure different CU / DU function segmentation methods for different CUs, different DUs, different RUs, different cells, different UEs, different PDU sessions, different QoS flows, and / or different data packets based on the node load information and service QoS requirements of the CU, DU, and / or RU. Different function segmentation methods can be associated with CU ID, DU ID, RU ID, cell ID, UE ID, PDU session ID, QoS flow ID, and data packet ID. The CU can send this association to the DU, so that the CU and DU can deploy different functional entities according to the association and the CU ID, DU ID, RU ID, cell ID, UE ID, PDU session ID, QoS flow ID, and data packet ID (if it can be carried with the data packet), for data belonging to different CUs, different DUs, different RUs, different cells, different UEs, different PDU sessions, different QoS flows, and different data packets, according to the above association and the corresponding functional segmentation method.

[0519] Method 2:

[0520] S304, CU sends the sixth message to DU. Correspondingly, DU receives the sixth message from CU.

[0521] The sixth piece of information can be used to indicate QoS requirements. These QoS requirements are those carried in the PDU session resource establishment request list in the fifth piece of information. In other words, the CU can forward the QoS requirements in the PDU session resource establishment request list to the DU so that the DU can execute S304.

[0522] S305, DU determines the CU protocol layer configuration information and the DU protocol layer configuration information.

[0523] For example, the DU generates CU protocol layer configuration information and DU protocol layer configuration information based on this QoS requirement. Specific protocol layer configuration information can be found in the description in S302, and will not be repeated here in this embodiment.

[0524] S306, the DU sends CU protocol layer configuration information to the CU. Correspondingly, the CU receives the CU protocol layer configuration information from the DU.

[0525] S306 is similar to S303, except that the roles of the sender and receiver are interchanged, and the transmitted information is used to configure the protocol layer functions of the CU. For details, please refer to the description of S303; this embodiment will not repeat them here.

[0526] S307, Each functional entity configures the communication protocol function module according to the protocol layer configuration information.

[0527] For example, the DU configures the various communication protocol function modules on the DU according to the DU protocol layer configuration information, and the CU configures the various communication protocol function modules on the CU according to the CU protocol layer configuration information.

[0528] Taking Scenario 1 above as an example, the CU can establish and configure SDAP layer functional modules, RRC layer functional modules, and PDCP layer functional modules, while the DU can establish and configure RLC layer functional modules, MAC layer functional modules, and PHY layer functional modules. In some examples, the CU can also locally back up RLC layer functional modules and MAC layer functional modules, and set the RLC layer functional modules and MAC layer functional modules to a deactivated or disabled state.

[0529] Taking Scenario 2 above as an example, the CU can create and configure SDAP layer functional modules, RRC layer functional modules, PDCP layer functional modules, RLC layer functional modules, and MAC layer functional modules, while the DU can create and configure PHY layer functional modules. In some examples, the DU can also locally back up RLC layer functional modules and MAC layer functional modules, and set the RLC layer functional modules and MAC layer functional modules to a deactivated or disabled state.

[0530] Taking Scenario 2 above as an example, the CU can establish and configure SDAP layer functional modules, RRC layer functional modules, PDCP layer functional modules, RLC layer functional modules, and MAC layer functional modules, while the DU can establish and configure RLC layer functional modules, MAC layer functional modules, and PHY layer functional modules. Among them, the RLC layer functional modules and MAC layer functional modules in the CU can be used to simulate data processing.

[0531] The following will describe the options A through D, where the CU or DU decides whether to migrate the first communication protocol function module and decides whether to migrate it to the CU or DU.

[0532] For scenarios 1 and 3, either solution A or solution C can be used.

[0533] Option A (the CU decides to move the first communication protocol function module from the DU to the CU):

[0534] S308, CU determines to migrate the first communication protocol function module to CU.

[0535] For example, the CU can determine whether to migrate the first communication protocol function module from the DU to the CU and redirect traffic to the CU based on parameters such as local service load, DU service responsibilities, computing power status, energy consumption status, and QoS requirements of the PDU session. Specifically, traffic redirection to the CU could involve changing the transmission of data from the PDCP layer function module to the RLC layer function module, for instance, from sending data to the RLC layer function module in the DU to sending it to the RLC layer function module in the CU.

[0536] For example, the CU redirects a newly arrived PDU from the PDCP layer functional module to the CU. The buffer module in the CU's RLC layer functional module can then begin receiving the newly arrived data packets. It can be understood that data packets received in the CU's RLC layer functional module will only begin processing after the buffered data in the DU's RLC layer functional module and / or the DU's MAC layer functional module has been processed.

[0537] Alternatively, other network elements such as CN-C and OAM can first decide to migrate the first communication protocol function module from DU to CU based on parameters such as CU service load, DU service load, computing power status, energy consumption status, and PDU session QoS requirements, and then inform CU of this decision.

[0538] S309, the CU sends first information and second information to the DU. Correspondingly, the DU receives the first information and second information from the CU.

[0539] For example, the CU can send a first message to the DU to instruct the DU to activate, deactivate, or deactivate the MAC layer functional module and the RLC layer functional module. Alternatively, the first message can be interpreted as instructing the DU to migrate the MAC layer functional module and the RLC layer functional module to the CU. The second message may include the processing method for the cached data of the DU's MAC layer functional module and the processing method for the cached data of the DU's RLC layer functional module. For example, not discarding, discarding all, or partially discarding.

[0540] The cached data of the MAC layer functional module can include data packets to be retransmitted, and the cached data of the RLC layer functional module can include data packets to be sent and retransmitted.

[0541] The methods for handling cached data can include:

[0542] 1. Directly instruct the DU to discard cached data from the DU MAC layer functional module and the DU RLC layer functional module, so that newly arriving data packets on the CU can be processed directly and quickly, reducing the processing latency of data packets during function switching.

[0543] 2. The instruction specifies that the DU must not discard cached data from the DU MAC layer functional module and the DU RLC layer functional module; that is, all cached data from the DU MAC layer functional module and the DU RLC layer functional module must be scheduled and transmitted to the UE. Newly arriving data packets on the CU must wait until all cached data on the DU has been transmitted to the UE before processing can continue, in order to avoid packet loss during function handover.

[0544] 3. Configure the first time period, also known as the maximum transmission time or remaining usage time. After this first time period is exceeded, the DU stops scheduling cached data from the DU MAC layer functional module and the DU RLC layer functional module, and discards the remaining cached data. In some examples, the CU can adaptively adjust the duration of the first time period based on the arrival rate of PDCP layer data to balance the packet loss rate in the cached data and the processing latency of newly arriving data on the CU.

[0545] 4. Configure a first threshold, such as a packet transmission quantity threshold or a packet transmission ratio threshold. When the buffered data of the transmitted DU MAC layer functional modules and the buffered data of the remaining untransmitted MAC layer functional modules exceed the first threshold, and / or when the buffered data of the transmitted DU RLC layer functional modules and the buffered data of the remaining untransmitted RLC layer functional modules exceed the first threshold, DU stops scheduling the buffered data of the DU MAC layer functional modules and / or the buffered data of the DU RLC layer functional modules, and discards the remaining packets.

[0546] 5. Configure a second threshold, such as a packet transmission quantity threshold or a packet transmission ratio threshold. When the proportion of the buffered data of the DU MAC layer functional module and / or the buffered data of the DU RLC layer functional module that has been transmitted exceeds the second threshold, DU stops scheduling the buffered data of the DU MAC layer functional module and / or the buffered data of the DU RLC layer functional module, and discards the remaining packets.

[0547] 6. Configure a third threshold, such as a packet drop count threshold or a packet drop ratio threshold. When the proportion of the remaining unsent cached data of the DU MAC layer functional module and / or the cached data of the DU RLC layer functional module to the cache capacity is lower than the third threshold, DU stops scheduling the cached data of the DU MAC layer functional module and / or the cached data of the DU RLC layer functional module and drops the remaining packets.

[0548] S310, DU processes the cached data in the first communication protocol function module according to the second information.

[0549] S311, DU sends third information to CU. Correspondingly, CU receives the third information from DU.

[0550] For example, the third piece of information may include RLC logical channel related parameter information, RLC buffer retransmission information, MAC scheduling information, etc. The RLC logical channel related parameter information may include the mapping relationship between LCID, DRB, and logical channel. Optionally, it may also include the mapping relationship between logical channel and transport channel. MAC scheduling information may include a MAC HARQ process list, frame number, subframe number, time slot number, RB resource allocation, MCS order, multi-user pairing information, precoding for MIMO data superposition at different layers, and weighting coefficients for MIMO data superposition at different layers. RLC buffer retransmission information may include ACK ID, NACK ID, RLC sequence number, etc., for packet retransmission.

[0551] The above parameters can be created or modified through the MAC layer functional module and / or the RLC layer functional module, and some parameters can change dynamically within each time slot or subframe.

[0552] S312, CU configures the first communication protocol function module according to the third information.

[0553] For example, the CU can generate MAC layer functional modules and RLC layer functional modules through virtualization or container technology based on the third information indicated by the DU. One approach is to directly generate the final MAC layer functional modules and RLC layer functional modules based on the third information. Alternatively, the MAC layer functional modules and RLC layer functional modules can be generated first, and then configured according to the DRB configuration or default parameters. Finally, the parameters in the MAC layer functional modules and RLC layer functional modules can be updated based on the third information. This application does not limit the scope of the embodiments described herein.

[0554] For example, the CU can set the same LCID, DRB, and logical channel mapping relationship for MAC layer functional modules and / or RLC layer functional modules. Optionally, it can also include setting the mapping relationship between logical channels and transport channels. Based on this DRB-logical channel mapping relationship and the logical channel-transport channel mapping relationship, each downlink data packet can be mapped from DRB to logical channel and from logical channel to transport channel; and each uplink data packet can be mapped from transport channel to transport channel and from logical channel to DRB.

[0555] You can also set the same ACK ID, NACK ID, RLC sequence number, etc., and transmit data packets starting from the RLC sequence number or retransmit the data packets indicated by the NACK ID based on the ACK ID, NACK ID, and RLC sequence number.

[0556] You can also set the same frame number, subframe number, timeslot number, HARQ process list, RE resource allocation, MCS order, multi-user pairing, precoding for MIMO data overlay, and weighting coefficients for MIMO data overlay, among other MAC scheduling parameters. Data packets can be scheduled according to frame number, subframe number, timeslot number, and HARQ process list.

[0557] In some examples, during the subsequent F1 interface management process, the CU configuration update information sent by the CU to the DU includes third-party information, and the DU configuration update information sent by the DU to the CU includes functional configuration information related to the PHY layer.

[0558] In the case of the opposite migration method in Scenario 3, Scenario 2 can adopt either Solution B or Solution D.

[0559] Option B (the CU decides to move the first communication protocol function module from the CU to the DU):

[0560] S313, CU determines to migrate the first communication protocol function module to DU.

[0561] It is understood that the implementation process of S313 is similar to that of S308, the difference being that the location of the first communication protocol function module is replaced by DU. For details, please refer to the relevant description of S308, which will not be repeated here in the embodiments of this application.

[0562] It is understandable that S313 requires determining whether to redirect traffic to the DU. Specifically, redirecting traffic to the DU means, for example, changing the data sent from the PDCP layer functional module to the RLC layer functional module from being sent to the RLC layer functional module in the CU to being sent to the RLC layer functional module in the DU.

[0563] For example, the CU redirects the newly arrived PDU from the PDCP layer functional module to the DU. The buffer module in the DU's RLC layer functional module can then begin receiving the newly arrived data packets. It can be understood that the data packets received in the DU's RLC layer functional module need to wait until the buffered data in the CU's RLC layer functional module and / or the buffered data in the CU's MAC layer functional module has been processed before processing begins.

[0564] S314, CU sends the first message to DU. Correspondingly, DU receives the first message from CU.

[0565] It is understood that the implementation processes of S314 and S309 are similar, the difference being that no second information needs to be sent. This is because the processing method for cached data is determined by the CU and needs to be executed by the CU; therefore, the CU does not need to instruct the DU on the processing method for cached data. For a detailed implementation process, please refer to the relevant description of S309; ​​this embodiment will not be repeated here.

[0566] S315, CU determines the processing method for cached data in the first communication protocol function module, and processes the cached data according to that method.

[0567] It is understood that the implementation process of S315 is similar to that of S310. The difference lies in the fact that the processing method of the cached data in the first communication protocol functional module is determined and executed by the CU. For the specific implementation process, please refer to the relevant description of S310. This embodiment of the application will not repeat it here.

[0568] Of course, there is no strict order of execution between S314 and S315. For example, S314 may be executed first and then S315, or S315 may be executed first and then S314, or S314 and S315 may be executed simultaneously. This embodiment of the application does not limit this.

[0569] S316, CU sends third information to DU. Correspondingly, DU receives the third information from CU.

[0570] It is understood that the implementation process of S316 is similar to that of S311, the difference being the substitution of the execution subject. For details, please refer to the relevant description of S311. This application embodiment will not repeat the details here.

[0571] S317, DU configures the first communication protocol function module according to the third information.

[0572] It is understood that the implementation process of S317 is similar to that of S312, the difference being the different execution entities. For details, please refer to the relevant description of S312. This application embodiment will not repeat the details here.

[0573] Referring to Figure 17, Scheme C or Scheme D is further illustrated.

[0574] Option C (the DU decides to move the first communication protocol function module from the DU to the CU):

[0575] S401, DU determines to migrate the first communication protocol function module to CU.

[0576] It is understood that the implementation process of S401 is similar to that of S308, the difference being the different executing entities. For details, please refer to the relevant description of S308. The embodiments of this application will not be repeated here.

[0577] S402, DU sends the first message to CU. Correspondingly, CU receives the first message from DU.

[0578] It is understood that the implementation processes of S401 and S309 are similar, the difference being the different executing entities and the absence of the need to send second information. This is because the processing method for cached data is determined by the DU and needs to be executed by the DU; therefore, the DU does not need to instruct the CU on the processing method for cached data. For a detailed implementation process, please refer to the relevant description in S309; ​​this embodiment will not be repeated here.

[0579] S403, DU determines the processing method for cached data in the first communication protocol function module, and processes the cached data according to that method.

[0580] It is understood that the implementation process of S403 is similar to that of S310, the difference being that the processing method of the cached data in the first communication protocol functional module is determined by DU. For the specific implementation process, please refer to the relevant description of S310; this embodiment will not be repeated here.

[0581] Of course, there is no strict order of execution between S402 and S403. For example, S402 may be executed first and then S403, or S403 may be executed first and then S402, or S402 and S403 may be executed simultaneously. This embodiment of the application does not limit this.

[0582] S404, DU sends third information to CU. Correspondingly, CU receives the third information from DU.

[0583] S405, CU configures the first communication protocol function module according to the third information.

[0584] It is understood that the implementation process of S404 is similar to that of S311, and the implementation process of S405 is similar to that of S312. For details, please refer to the relevant descriptions of S311 and S312. The embodiments of this application will not be repeated here.

[0585] Option D (the DU decides to move the first communication protocol function module from the DU to the CU):

[0586] S406, DU determines to migrate the first communication protocol function module to DU.

[0587] It is understood that the implementation process of S406 is similar to that of S313, the difference being the different executing entities. For details, please refer to the relevant description of S308. This application embodiment will not repeat the details here.

[0588] S407, DU sends first information and second information to CU. Correspondingly, CU receives the first information and second information from DU.

[0589] It is understood that the implementation process of S407 is similar to that of S309, the difference being the substitution of the execution subject. For the specific implementation process, please refer to the relevant description of S309. The embodiments of this application will not be repeated here.

[0590] S408, CU processes the cached data in the first communication protocol function module according to the second information.

[0591] It is understood that the implementation process of S408 is similar to that of S310, the difference being the substitution of the execution subject. For the specific implementation process, please refer to the relevant description of S310. The embodiments of this application will not be repeated here.

[0592] S409, CU sends third information to DU. Correspondingly, DU receives the third information from CU.

[0593] S410, DU configures the first communication protocol function module according to the third information.

[0594] It is understood that the implementation process of S409 is similar to that of S316, and the implementation process of S410 is similar to that of S317. For details, please refer to the relevant descriptions of S316 and S317. The embodiments of this application will not be repeated here.

[0595] In the schemes described in Figures 16 and 17 above, DU can also be replaced by RU, and CU can also be replaced by DU. The first communication protocol function module can also be a layer 3 communication protocol function module or a layer 1 communication protocol function module, and this application embodiment does not limit it here.

[0596] This application embodiment triggers the migration of the first communication protocol functional module and redirects data. It also appropriately handles cached data within the first communication protocol functional module to minimize data loss and maintain business continuity. Simultaneously, by feeding back relevant parameters of the first communication protocol functional module, it ensures that the module maintains state synchronization during the migration process, preventing communication fluctuations and guaranteeing a consistent user experience.

[0597] Considering that in scenario 3 above, both the DU and CU have MAC layer functional modules and RLC layer functional modules activated (or enabled) and running, in scenario 3, regardless of whether the CU or DU decides to migrate the first communication protocol functional module, it is unnecessary to consider whether the migration is from CU to DU or vice versa. No second information needs to be sent, i.e., no instruction is needed on how to process the cached data.

[0598] For example, while the second functional entity is sending first information to the first functional entity, it can request the first functional entity to send third information to the second functional entity. Similarly, while the CU is sending first information to the DU, it can request the DU to send third information to the CU.

[0599] Since both the MAC layer and RLC layer functional modules are activated (or enabled) and running in both the DU and CU, these modules can process data simultaneously during the migration process. For example, in Scenario 3, although the MAC and RLC layer functional modules in the DU stop receiving new data, they can still continue processing the remaining buffered data. The PHY layer functional module may simultaneously receive data from both the MAC layer functional modules in the CU and the DU. In this case, the PHY layer functional module can ignore the data from the MAC layer functional module in the CU until the MAC layer functional module in the DU stops sending data to the PHY layer functional module. Then, the PHY layer functional module will process the data from the MAC layer functional module in the CU. During this process, the PHY layer functional module can directly discard the data from the MAC layer functional module in the CU.

[0600] Alternatively, the DU can distinguish data from the MAC layer functional module in the CU and filter it out to prevent such data from being sent to the DU's PHY layer functional module.

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

[0602] Considering that the aforementioned embodiments can also be applied to the O-RAN network architecture, Figure 18 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).

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

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

[0605] Referring to Figure 19, the schemes described in Figures 10 to 18 above, in the O-RAN scenario, can have computation, decision-making, and other operations implemented by functional modules outside the RAN. This functional module can be called a RAN split control function (RSCF). It is understood that RSCF is only one possible name, and this application does not limit the name of this type of functional module; it can also be called a control module, decision-making module, etc. Subsequent embodiments of this application will use RSCF as an example for description.

[0606] The RSCF module can be deployed in a near real-time RIC, an SMO, or a non-real-time RIC; this embodiment does not limit the deployment. The RSCF module can be used to generate DRB configurations and configure the communication protocol modules of each functional entity as shown in Figures 10 to 18. The RSCF can also be used to decide whether to trigger the migration of the first communication protocol functional module, and to send first and second information to the corresponding functional entities. Communication can be achieved through the corresponding interfaces shown in Figure 18. The specific communication process can be referred to in the foregoing embodiments and implemented in conjunction with the corresponding interfaces in Figure 18; this embodiment will not elaborate further.

[0607] It is understood that the SMO and the functional entities in the O-RAN can communicate directly through the O1 interface; alternatively, the SMO can send data to the near real-time RIC through the A1 interface, and then the near real-time RIC can send it to the corresponding functional entity through the E2 interface. The appropriate communication path can be selected based on the actual situation, and this embodiment does not impose any limitations on it.

[0608] Referring to Figures 20 to 23, the RSCF module can also be deployed in a CU, DU, and / or RU, or deployed independently. The RSCF can be connected to one or more CUs, and / or one or more DUs, and / or one or more RUs. It is understood that Figures 20 to 23 only show some possible scenarios; the specific deployment method of the RSCF can be determined according to the actual situation, and this application embodiment does not limit this.

[0609] In some examples, RSCF can also be used to flexibly adjust the splitting method between the first and second functional entities. For instance, it can dynamically adjust the splitting method based on parameters such as the business requirements of each functional entity, the status of fronthaul resources, and the resource processing status of each functional entity. This allows for flexible switching between options 2 and 6.

[0610] The following section, using Figure 24, describes how to migrate the communication protocol function modules in the O-RAN scenario.

[0611] S501, the core network element sends the fifth message to the O-CU. Correspondingly, the O-CU receives the fifth message from the core network element.

[0612] The implementation process of S501 is similar to that of S301. For details, please refer to the description of S301. The embodiments of this application will not be repeated here.

[0613] In step S502, the O-CU sends the fifth information to the near-real-time RIC or SMO. Correspondingly, the near-real-time RIC or SMO receives the fifth information from the O-CU. Alternatively, the O-CU can be considered to forward the fourth information received in step S501 to the near-real-time RIC or SMO, enabling the near-real-time RIC or SMO to determine the DRB configuration based on the fifth information.

[0614] For example, the O-CU sends the fifth message to the near real-time RIC via the E2 interface, or to the SMO via the O1 interface. In some examples, the O-CU can first send the fifth message to the near real-time RIC via the E2 interface, and then the near real-time RIC can send the fifth message to the SMO via the A1 interface.

[0615] S503, near real-time RIC or SMO determines DRB configuration.

[0616] For example, near real-time RIC or SMO generates DRB configuration based on PDU session resource establishment requests. This DRB configuration may include O-CU protocol layer configuration information and O-DU protocol layer configuration information.

[0617] The following sections will describe how to configure O-DU and O-RU in two ways.

[0618] Method 3:

[0619] In step S504, the SMO sends the O-CU protocol layer configuration information and the O-DU protocol layer configuration information to the O-CU. Correspondingly, the O-CU receives the O-CU protocol layer configuration information and the O-DU protocol layer configuration information from the SMO. In other words, the SMO can inform the O-CU of the protocol layer configuration information of each functional entity determined in step S503.

[0620] S505, the O-CU sends the O-DU protocol layer configuration information to the O-DU. Correspondingly, the O-DU receives the O-DU protocol layer configuration information from the O-CU.

[0621] For example, the SMO can directly send the O-CU and O-DU protocol layer configuration information to the O-CU and O-DU via the O1 interface. Alternatively, the SMO can first send the O-CU and O-DU protocol layer configuration information to the near real-time RIC via the A1 interface. In this case, the near real-time RIC can forward the information to the O-CU via the E2 interface, and then the O-CU can forward the O-DU protocol layer configuration information (optionally including the O-CU protocol layer configuration information) to the O-DU via the F1 interface. Alternatively, the near real-time RIC can also send the O-CU and O-DU protocol layer configuration information to the O-CU and O-DU respectively via different E2 interfaces.

[0622] Method 4:

[0623] In step S506, the near real-time RIC sends O-CU protocol layer configuration information and O-DU protocol layer configuration information to the O-CU. Correspondingly, the O-CU receives the O-CU protocol layer configuration information and O-DU protocol layer configuration information from the near real-time RIC. In other words, the SMO can inform the O-CU of the protocol layer configuration information of each functional entity determined in step S303.

[0624] S507, the O-CU sends the O-DU protocol layer configuration information to the O-DU. Correspondingly, the O-DU receives the O-DU protocol layer configuration information from the O-CU.

[0625] For example, a near real-time RIC can send O-CU protocol layer configuration information and O-DU protocol layer configuration information to O-CU through the E2 interface, and then O-CU can send O-DU protocol layer configuration information (optionally also including O-CU protocol layer configuration information) to O-DU through the F1 interface.

[0626] Alternatively, near real-time RIC can send O-CU protocol layer configuration information and O-DU protocol layer configuration information to O-CU and O-CU respectively through different E2 interfaces.

[0627] Optionally, the near real-time RIC or SMO can also configure the communication protocol function modules deployed in the O-CU and O-DU according to the initial default protocol layer function partitioning method. In this case, it is not necessary to determine the aforementioned O-CU protocol layer configuration information and O-DU protocol layer configuration information. It is clear that each functional entity can know in advance which communication protocol function modules need to be deployed under different partitioning methods, so the functional entities can be deployed directly based on the default partitioning method. When it is necessary to dynamically adjust the communication protocol function modules deployed on the O-CU and O-DU, the near real-time RIC or SMO can then determine the aforementioned O-CU protocol layer configuration information and O-DU protocol layer configuration information.

[0628] In some examples, near real-time RICs or SMOs can configure the protocol layer configuration information of each functional entity at different granularities. For instance, different execution functions can be configured for each functional entity at granularities such as O-CU, O-DU, O-RU, cell, UE, DRB, PDU session, QoS flow, and data packet. For example, near real-time RICs or SMOs can select different CU and DU functions to execute for different O-CUs, O-DUs, O-RUs, UEs, DRBs, PDU sessions, QoS flows, and data packets based on dimensions such as O-CU capabilities, O-DU capabilities, O-RU capabilities, service load of each functional entity, computing power status, energy consumption status, traffic status of interfaces between functional entities, and QoS requirements. Furthermore, O-CU and O-DU functions can be associated with identifiers such as O-CU identifier, O-DU identifier, O-RU identifier, cell identifier, UE identifier, DRB identifier, PDU session identifier, QoS flow identifier, and data packet identifier (which can be carried with the data packet).

[0629] S508, each functional entity configures the communication protocol function module according to the protocol layer configuration information.

[0630] It is understood that S508 is similar to S307, and the specific details can be found in the description of S307. The embodiments of this application will not be repeated here.

[0631] S509, O-DU and / or O-CU send functional entity status reports to near real-time RIC or SMO.

[0632] For example, the O-DU can report local service load, computing power status, and energy consumption status to the near real-time RIC or SMO. For instance, the O-DU can first send its local service load, computing power status, and energy consumption status to the O-CU via the F1 interface. Then, the O-CU, along with its functional entity status report, sends it to the near real-time RIC via the E2 interface; or the O-CU, along with its functional entity status report, sends it to the SMO via the O1 interface; or the O-CU, along with its functional entity status report, sends it to the near real-time RIC via the E2 interface, and the near real-time RIC then sends it to the SMO via the A1 interface.

[0633] The functional entity status report of O-DU can include information such as O-DU local business load, computing power status, and energy consumption status.

[0634] For example, the O-DU can directly report local service load, computing power status, and energy consumption status to the SMO through the O1 interface. In the above example, the O-CU can also simply send the O-CU functional entity status report; this embodiment of the application does not impose any limitations on this.

[0635] For example, O-DU and O-CU can send their respective functional entity status reports to the near real-time RIC via their respective E2 interfaces. Alternatively, the near real-time RIC can forward the O-DU and O-CU functional entity status reports to the SMO via the AI ​​interface.

[0636] S510, near real-time RIC or SMO determines to migrate the first communication protocol function module.

[0637] It is understood that S510 is similar to S308, S313, S401, and S406, the difference being the executing entity. For details, please refer to the descriptions of S308, S313, S401, and S406, which will not be repeated here in the embodiments of this application.

[0638] For example, near real-time RIC or SMO can determine whether to trigger the switching or migration of the first communication protocol function module based on information such as the local service load, computing power status, mutual interference energy consumption status, and QoS requirements of the O-RU and / or O-DU.

[0639] The migration process of the first communication protocol functional module will be described next using methods E and F respectively.

[0640] Method E (the first communication protocol function module is migrated from DU to CU):

[0641] S511, the near real-time RIC or SMO sends first and second information to the O-DU. Correspondingly, the O-DU receives the first and second information from the near real-time RIC or SMO.

[0642] S512, O-DU processes the cached data in the first communication protocol function module according to the second information.

[0643] S513, the O-DU sends third information to the O-CU. Correspondingly, the O-CU receives the third information from the O-DU.

[0644] S514, O-CU configures the first communication protocol function module according to the third information.

[0645] For example, the SMO can directly send the first and second information to the O-DU via the O1 interface. Alternatively, the SMO can first send the first and second information to the O-CU via the O1 interface, and then the O-CU can forward them to the O-DU. Alternatively, the SMO can first send the first and second information to the near real-time RIC via the A1 interface, and then the near real-time RIC can forward them to the O-CU via the E2 interface, and the O-CU can forward them to the O-DU. Alternatively, the SMO can first send the first and second information to the near real-time RIC function via the A1 interface, and then the near real-time RIC can send them to the O-DU via the E2 interface.

[0646] For example, a near real-time RIC can first forward the first and second information to the O-CU via the E2 interface, and then the O-CU can forward them to the O-DU. Alternatively, a near real-time RIC can send the first and second information to the O-DU via the E2 interface.

[0647] The first and second information mentioned above can be sent separately or via different paths, and this application embodiment does not limit this. Therefore, if the O-DU does not receive the first information from the O-CU (including if the O-CU does not forward the first information), the near real-time RIC or SMO can still send the first information to the O-CU via the various paths mentioned above, so that the O-CU can activate (enable or establish) or deactivate (de-enable or deregister) the corresponding first communication protocol function module based on the first information.

[0648] The O-DU can activate (enable or establish) or deactivate (de-enable or deregister) the corresponding first communication protocol function module based on the first information. The O-DU can also process cached data based on the second information.

[0649] Regarding the processing method of the second information indicating cached data, please refer to the description of the foregoing related embodiments; the embodiments of this application will not be repeated here.

[0650] The O-CU and / or O-DU can redirect data based on the first information. The first communication protocol function module in the CU will only process newly arrived data after the cached data in the DU has been processed. The specific implementation process can be found in the descriptions of the aforementioned related examples; these will not be repeated here.

[0651] Method F (The first communication protocol function module is migrated from CU to DU):

[0652] S515, the near real-time RIC or SMO sends first and second information to the O-CU. Correspondingly, the O-CU receives the first and second information from the near real-time RIC or SMO.

[0653] S516, O-CU processes the cached data in the first communication protocol function module according to the second information.

[0654] S517, the O-CU sends third information to the O-DU. Correspondingly, the O-DU receives the third information from the O-CU.

[0655] S518, O-RU configures the first communication protocol function module according to the first information.

[0656] The specific interaction process from S515 to S518 can be referred to the description in Method E. The difference lies in the change of the execution subject, which will not be repeated here in the embodiments of this application.

[0657] It is understandable that the interaction between any entity in Figure 24 and the SMO can be considered as the interaction between each entity and the non-real-time RIC in the SMO.

[0658] It is also understood that the specific implementation process of each step in Figure 24 can be referred to the corresponding descriptions in Figures 16 and 17, as well as the descriptions of the various embodiments corresponding to Figures 11 and 12. The embodiments of this application will not be repeated here.

[0659] Considering that in future communication systems, RAN nodes may also possess some core network functions, as well as capabilities such as AI training and inference computation, the functional entities in the embodiments of this application may also include core network functions.

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

[0661] 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 by hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0662] Figures 25 and 26 are schematic diagrams illustrating the possible communication protocol function determination apparatuses provided in embodiments of this application. These communication protocol function determination apparatuses can be used to implement the functions of the first or second functional entity in the above method embodiments, thus achieving the beneficial effects of the above method embodiments. In embodiments of this application, the communication protocol function determination apparatus can be the RAN node 110 shown in Figure 1, wherein the RAN node can also be referred to as an access network device or a network device. The communication protocol function determination apparatus can also be a module (such as a chip) applied to a network device.

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

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

[0665] As shown in Figure 25, the communication protocol function determination device 2500 includes a processing unit 2510 and a transceiver unit 2520. The communication protocol function determination device 2500 is used to implement the functions of the network device in the method embodiments shown in Figures 11, 12, 16, 17, and 24.

[0666] When the communication protocol function determination device 2500 is used to implement the function of the first functional entity in the method embodiment shown in FIG11: the processing unit 2510 is used to determine the first information; the transceiver unit 2520 is used to send the first information to the second functional entity. Alternatively, the transceiver unit 2520 is used to receive the first information; the processing unit 2510 is used to determine, based on the first information, to migrate the first communication protocol function module to the second functional entity.

[0667] When the communication protocol function determination device 2500 is used to implement the function of the first functional entity in the method embodiment shown in FIG12: the transceiver unit 2520 is used to send or receive first information; the processing unit 2510 is used to determine the processing method of the cached data in the first communication protocol function module; the processing unit 2510 is also used to process the cached data in the first communication protocol function module based on the processing method.

[0668] When the communication protocol function determination device 2500 is used to implement the function of the second functional entity in the method embodiment shown in FIG11: the transceiver unit 2520 is used to receive first information; the processing unit 2510 is used to determine, based on the first information, that the first communication protocol function module is migrated to the second functional entity. Alternatively, the processing unit 2510 is used to determine the first information; the transceiver unit 2520 is used to send the first information to the first functional entity.

[0669] When the communication protocol function determination device 2500 is used to implement the function of the second functional entity in the method embodiment shown in FIG12: the transceiver unit 2520 is used to send or receive first information; the processing unit 2510 is used to cache first data; the processing unit 2510 is also used to process the cached first data.

[0670] For a more detailed description of the processing unit 2510 and the transceiver unit 2520, please refer to the relevant description of the method embodiments shown in Figures 11, 12, 16, 17, and 24.

[0671] As shown in Figure 26, the communication protocol function determination device 2600 includes a processor 2610 and an interface circuit 2620. The processor 2610 and the interface circuit 2620 are coupled together. It is understood that the interface circuit 2620 can be a transceiver or an input / output interface. Optionally, the communication protocol function determination device 2600 may also include a memory 2630 for storing instructions executed by the processor 2610, or storing input data required by the processor 2610 to execute instructions, or storing data generated after the processor 2610 executes instructions. Sometimes, the interface circuit 2620 can also be understood as part of the processor 2610, in which case the communication protocol function determination device 2600 includes the processor 2610.

[0672] When the communication protocol function determination device 2600 is used to implement the methods shown in FIG11, FIG12, FIG16, FIG17 and FIG24, the processor 2610 is used to implement the functions of the processing unit 2510, and the interface circuit 2620 is used to implement the functions of the transceiver unit 2520.

[0673] When the aforementioned communication protocol function determination 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0689] 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 method for determining the function of a communication protocol, characterized in that, The method is applied to a first functional entity, and the method includes: Determine first information, which is used to instruct the migration of a first communication protocol function module to a second functional entity, wherein the first communication protocol function module includes a layer 2 communication protocol function module and / or a layer 3 communication protocol function module; send the first information to the second functional entity; or, Receive the first information; determine, based on the first information, to migrate the first communication protocol function module to the second functional entity.

2. A method for migrating communication protocol functions, characterized in that, The method is applied to a first functional entity, and the method includes: Sending or receiving first information, the first information being used to instruct the migration of a first communication protocol function module to the second functional entity, wherein the first communication protocol function module includes a layer 2 communication protocol function module and / or a layer 3 communication protocol function module, and the first functional entity is configured with the first communication protocol function module; Determine the processing method for cached data in the first communication protocol functional module; The cached data in the first communication protocol functional module is processed based on the aforementioned processing method.

3. The method according to claim 2, characterized in that, The method further includes: Receive second information, which indicates how to process the cached data in the first communication protocol function module.

4. The method according to claim 2 or 3, characterized in that, The cached data in the first communication protocol functional module can be processed using any of the following methods: Discard the cached data in the first communication protocol function module; or, Continue sending the cached data in the first communication protocol function module; or, During a first time period, buffered data in the first communication protocol functional module is continuously transmitted, wherein the start time of the first time period is the moment when the first communication protocol functional module stops receiving newly arriving data, and the duration of the first time period is a first duration; or, The remaining unsent cached data is determined to be discarded based on the remaining unsent cached data packets.

5. The method according to claim 4, characterized in that, The step of determining to discard the remaining unsent cached data based on the remaining unsent cached data includes: Continue sending cached data from the first communication protocol function module until the ratio between the sent cached data and the remaining unsent cached data is greater than or equal to a first threshold; or, Continue sending cached data from the first communication protocol function module until the ratio between the sent cached data and the cache capacity corresponding to the first communication protocol function module is greater than or equal to the second threshold; or, Continue sending cached data from the first communication protocol function module until the ratio between the remaining unsent cached data and the cache capacity corresponding to the first communication protocol function module is less than or equal to the third threshold.

6. The method according to any one of claims 2-5, characterized in that, The method further includes: Stop receiving newly arrived data from the first communication protocol function module.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: Send a third message to the second functional entity, wherein the third message is used to indicate parameters related to the first communication protocol functional module, and the parameters related to the first communication protocol functional module are used to configure the first communication protocol functional module.

8. The method according to any one of claims 1-7, characterized in that, The method for sending the first information further includes: The first information is determined based on the first parameter; The first parameter includes at least one of the following parameters: Parameters used to indicate the business load status of the first functional entity; Parameters used to indicate the computing power status of the first functional entity; Parameters used to indicate the energy consumption status of the first functional entity; or, Parameters used to indicate the traffic status of the interface between the first functional entity and the second functional entity.

9. The method according to any one of claims 1-8, characterized in that, The first functional entity is configured with the first communication protocol function module, and the first communication protocol function module is set to a deactivated state, a deregistered state, or a disabled state.

10. The method according to any one of claims 1-9, characterized in that, The method further includes: Receive or generate the fourth information, wherein the fourth information is used to configure the first communication protocol function module; The fourth information is sent to the second functional entity.

11. The method according to claim 10, characterized in that, The fourth information is determined based on the first Quality of Service (QoS) parameter, wherein the first QoS parameter is used to indicate the QoS requirements of the service, and the first communication protocol function module is used to meet the QoS requirements of the service.

12. The method according to claim 10 or 11, characterized in that, The fourth information configures the first communication protocol function module based on at least one of the following granularities: Granularity based on functional entities; Based on the granularity of the cell; Granularity based on the terminal; or, Based on business granularity.

13. The method according to claim 12, characterized in that, The granularity based on functional entities includes at least one of the following granularities: Granularity based on centralized unit (CU); Granularity based on distributed unit (DU); or, Granularity based on radio frequency unit (RU).

14. The method according to claim 12, characterized in that, The business-based granularity includes at least one of the following granularities: Granularity based on Data Radio Bearer (DRB); Granularity of sessions based on Protocol Data Unit (PDU); QoS-based granularity; or, Data packet-based granularity.

15. The method according to any one of claims 1-14, characterized in that, The first functional entity is deployed in CU, DU or RU.

16. The method according to any one of claims 1-15, characterized in that, The first communication protocol functional module includes at least one of the following functional modules: Functional modules used for handling media access control MAC protocol layer functions; or, Functional modules used to handle the Radio Link Control (RLC) protocol layer.

17. The method according to claim 16, characterized in that, The first communication protocol functional module is a functional module for processing the MAC protocol layer. The parameters related to the first communication protocol functional module include: a MAC Hybrid Automatic Repeat Request (HARQ) process list, frame number, subframe number, resource block (RB) resource allocation, modulation and coding scheme (MCS) order, multi-user pairing information, precoding coefficients for superimposing different data streams supported by MIMO, weighting coefficients for superimposing different data streams in MIMO, or at least one of the following: The first communication protocol function module is a function module for processing the RLC protocol layer. The parameters related to the first communication protocol function module include at least one of the following: the mapping relationship between the logical channel identifier LCID and the logical channel, the mapping relationship between the DRB and the logical channel, the mapping relationship between the logical channel and the transport channel, the ACK identifier for positive acknowledgment for data packet retransmission, the NACK identifier for negative acknowledgment for data packet retransmission, the RLC sequence number, and the PDCP sequence number. Wherein, the logical channel is the channel between the RLC protocol layer and the MAC protocol layer, and the transmission channel is the channel between the MAC protocol layer and the physical PHY protocol layer.

18. The method according to any one of claims 1-17, characterized in that, The second functional entity is deployed in CU, DU or RU.

19. The method according to any one of claims 1-18, characterized in that, The first communication protocol function module configured in the first functional entity is in an active or enabled state.

20. The method according to any one of claims 1-19, characterized in that, The second functional entity is configured with the first communication protocol function module, wherein the first communication protocol function module configured in the second functional entity is used to simulate data processing.

21. The method according to claim 20, characterized in that, The first communication protocol function module configured in the second functional entity is in an active or enabled state.

22. A method for determining the function of a communication protocol, characterized in that, The method is applied to a second functional entity, and the method includes: Receive first information, the first information being used to instruct the migration of a first communication protocol function module to the second functional entity, wherein the first communication protocol function module includes a layer 2 communication protocol function module and / or a layer 3 communication protocol function module; determine, based on the first information, that the first communication protocol function module is migrated to the second functional entity; or, Determine the first information; send the first information to the first functional entity.

23. A method for migrating communication protocol functions, characterized in that, The method is applied to a second functional entity, and the method includes: Receive or send first information, the first information being used to instruct the migration of a first communication protocol function module to the second functional entity, wherein the first communication protocol function module includes a layer 2 communication protocol function module and / or a layer 3 communication protocol function module, and the first functional entity is configured with the first communication protocol function module; Cache the first data, wherein the first data is the data sent to the first communication protocol function module in the first functional entity; The first cached data is processed.

24. The method according to claim 23, characterized in that, The method further includes: Determine the second information, which is used to indicate the method of processing cached data in the first communication protocol function module configured by the first functional entity; Send the second message.

25. The method according to any one of claims 22-24, characterized in that, The method further includes: Receive third information from the first functional entity, wherein the third information is used to indicate parameters related to the first communication protocol functional module, and the parameters related to the first communication protocol functional module are used to configure the first communication protocol functional module.

26. The method according to any one of claims 22-25, characterized in that, The method further includes: Receive or generate the fourth information, wherein the fourth information is used to configure the first communication protocol function module; The first communication protocol function module is generated based on the fourth information, and the first communication protocol function module is set to a deactivated state or a disabled state.

27. A communication device, characterized in that, It includes a module for performing the method of any one of claims 1 to 21, or a module for performing the method of any one of claims 22 to 26.

28. A communication device, characterized in that, The device includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices and transmit them to the processor or to send signals from the processor to other communication devices, and the processor is used to implement the method as described in any one of claims 1 to 21, or to implement the method as described in any one of claims 22 to 26, through logic circuits or executing code instructions.

29. A chip, characterized in that, The device includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices and transmit them to the processor or to send signals from the processor to other communication devices, and the processor is used to implement the method as described in any one of claims 1 to 21, or to implement the method as described in any one of claims 22 to 26, through logic circuits or executing code instructions.

30. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1 to 21, or the method as described in any one of claims 22 to 26.

31. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by the communication device, they implement the method as described in any one of claims 1 to 21, or the method as described in any one of claims 22 to 26.

Images