Communication method, apparatus and system, and readable storage medium and program product

Abstract

A communication method, apparatus and system, and a readable storage medium and a program product. The communication method comprises: receiving from a first functional entity a first target policy and / or a second target policy, and a first identifier, wherein the first target policy is used for indicating a separation mode for a communication function of a first target entity and a communication function of a second target entity, and the second target policy is used for indicating a separation mode for the communication function of the second target entity and a communication function of a third target entity; and on the basis of an association relationship between the first identifier and a second identifier, sending the first target policy and / or the second target policy to a second functional entity indicated by the second identifier, wherein the second functional entity comprises at least one of the first target entity, the second target entity and the third target entity. In the embodiments of the present application, during the process of configuring corresponding target policies for different functional entities, the isolation between the first functional entity and the second functional entity is realized by means of a correspondence between a real identifier and a virtual identifier, thereby improving the security of a network.

Description

Communication method, device, system, readable storage medium and program product

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on February 8, 2024, with application number "202410178315.9" and invention name "Communication method, device, system, readable storage medium and program product", the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to communication methods, devices, systems, computer-readable storage media, and computer program products. Background Art

[0003] Base stations in fourth-generation mobile networks (4G) use a bottom-layer splitting approach, splitting the base station into two functional entities: the baseband unit (BBU) and the remote radio unit (RRU). Base stations in fifth-generation mobile networks (5G) use a top-layer splitting approach, splitting the base station into two functional entities: the central unit (CU) and the distributed unit (DU).

[0004] The current functional division of 5G base stations is poorly adaptable, so a solution with better performance is urgently needed. Summary of the Invention

[0005] The present application provides a communication method, device, system, computer-readable storage medium and computer program product. In the process of configuring corresponding target policies for different functional entities, isolation between different functional entities is achieved through the correspondence between real identifiers and virtual identifiers, thereby improving the security of the network.

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

[0007] In a first aspect, a communication method is provided. The method can be used on the side of a third functional entity, such as a third functional entity or a component in the third functional entity (such as a circuit or a chip or a chip system). The method may include: receiving a first target policy and / or a second target policy from the first functional entity, and a first identifier. The first target policy is used to indicate the way in which the communication functions of the first target entity and the second target entity are divided, and the second target policy is used to indicate the way in which the communication functions of the second target entity and the third target entity are divided. Based on the association relationship between the first identifier and the second identifier, the first target policy and / or the second target policy are sent to the second functional entity indicated by the second identifier. The second functional entity includes at least one of the first target entity, the second target entity and the third target entity.

[0008] In the process of configuring corresponding target policies for different functional entities, the present application realizes isolation between the first functional entity and the second functional entity through the correspondence between the real identifier and the virtual identifier, thereby improving the security of the network.

[0009] In one possible design, before receiving the first target policy and / or the second target policy from the first functional entity, the method further includes: obtaining the second identifier and the first information corresponding to the second identifier. Based on the association relationship between the second identifier and the first identifier, the second identifier is mapped to the first identifier. The first identifier and the first information are sent to the first functional entity. The first information includes at least one of the following: second information corresponding to the communication interface, wherein the second information is used to indicate the network communication status corresponding to the communication interface, the communication interface includes a first interface and a second interface, the first interface is the communication interface between the first target entity and the second target entity, and the second interface is the communication interface between the second target entity and the third target entity; third information corresponding to the second functional entity, wherein the third information is used to indicate the processing resource status corresponding to the second functional entity; or fourth information, wherein the fourth information is used to indicate the quality of service (QoS) requirement corresponding to at least one service.

[0010] This application can prevent the first functional entity from knowing the true second functional entity when the first functional entity comprehensively determines the target strategy based on dimensions such as the network communication status of the communication interface, the processing resource status of the functional entity, and the QoS requirements of the service, thereby ensuring the security of the corresponding information of the second functional entity.

[0011] In one possible design, the method further includes: allocating the first identifier associated with the second identifier.

[0012] In this application, the third functional entity can allocate the first identifier associated with the second identifier, which can more flexibly implement the configuration of the first identifier.

[0013] In one possible design, the second identifier comes from at least one second functional entity.

[0014] The present application obtains the second identifier of at least one second functional entity so that the third functional entity configures the corresponding first identifier for the second identifier, thereby ensuring the security of information related to the second functional entity.

[0015] In one possible design, the first target policy and / or the second target policy corresponds to any terminal among different terminals; or, the first target policy and / or the second target policy corresponds to any PDU session among different protocol data unit (PDU) sessions; or, the first target policy and / or the second target policy corresponds to any QoS flow among different QoS flows; or, the first target policy and / or the second target policy corresponds to any data radio bearer (DRB) among different DRBs; or, the first target policy and / or the second target policy corresponds to any data packet among different data packets.

[0016] This application can determine target strategies at different granularities so that flexible adjustment of communication functions can be achieved at corresponding granularities.

[0017] In one possible design, the method further includes: receiving at least one alternative function splitting method and / or fifth information. The fifth information is used to indicate the communication function configured for each second functional entity corresponding to the alternative function splitting method. Sending the at least one alternative function splitting method and / or the fifth information to the second functional entity.

[0018] The present application can also inform the second functional entity of multiple alternative function segmentation methods and / or corresponding communication functions in advance, so that only part of the information needs to be indicated when indicating the target policy, thereby reducing resource overhead during the communication process.

[0019] In a possible design, communication with different second functional entities is performed by transparent transmission to intermediate nodes.

[0020] By adopting the transparent transmission mode of the intermediate node, any second functional entity cannot obtain information related to other second functional entities, thereby ensuring the security of information between different second functional entities.

[0021] In one possible design, the method is applied to a third functional entity, and the third functional entity is independent of the first functional entity and the second functional entity. Alternatively, the third functional entity is integrated into the second functional entity.

[0022] This application provides multiple deployment methods for the third functional entity, which is applicable to various possible network architectures. This allows various network architectures to ensure the security of communications between different functional entities while flexibly segmenting network functions, including radio access network (RAN) functions.

[0023] In one possible design, the third functional entity has a communication connection with at least one of the second functional entities.

[0024] In this application, the third functional entity can establish a communication connection with one or more second functional entities in a scenario independent of the first functional entity and the second functional entity. The number of third functional entities and the connection method with the second functional entities can be dynamically selected in different scenarios. This ensures isolation between the first functional entity and the second functional entity in various scenarios, ensuring the security of data transmission.

[0025] In one possible design, the second functional entity is a functional entity in a wireless local area network RAN, a core network, or a network management domain.

[0026] This application can dynamically divide multiple communication functions such as wireless access network, core network and network management domain to improve universality.

[0027] In a possible design, the second functional entity is a functional entity in the RAN, and the second functional entity includes at least one of the following functional entities: a CU; a DU; or a radio unit (RU).

[0028] This application implements flexible adjustment of the communication functions of multiple functional entities such as CU, DU, and RU in the RAN, so as to adapt to the service quality requirements of different services, improve the utilization of bandwidth and computing resources, and reduce the deployment cost of different functional entities in the RAN.

[0029] In one possible design, the method is applied to a CU, and the second functional entity includes a DU and / or an RU. Alternatively, the method is applied to a DU, and the second functional entity includes a CU and / or an RU. Alternatively, the method is applied to an RU, and the second functional entity includes a CU and / or an RU.

[0030] This application can also be applied to functional entities in the RAN, eliminating the need to deploy independent network elements separately, reducing deployment costs, and being applicable to more network architectures, thereby improving universality.

[0031] In one possible design, the method of dividing the communication function includes dividing a set consisting of at least one of the following communication functions: communication functions corresponding to the RAN protocol layer; communication functions corresponding to one or more network elements in the core network; or communication functions corresponding to at least one entity used for network management.

[0032] This application can flexibly divide various communication functions so that different functional entities are configured with different communication functions to adapt to the service quality requirements of different businesses in different scenarios.

[0033] In one possible design, the second information includes at least one of the following parameters: bandwidth resources of the communication interface; transmission delay of the communication interface; packet loss rate of the communication interface; or reliability of the communication interface.

[0034] The present application provides a variety of possible parameters included in the second information, so that the first functional entity can determine a suitable target strategy according to the parameters in the second information.

[0035] In one possible design, the third information includes at least one of the following parameters: processor utilization; memory utilization; or disk utilization.

[0036] The present application provides a variety of possible parameters included in the third information, so that the first functional entity can determine a suitable target strategy according to the parameters in the third information.

[0037] In one possible design, the fourth information includes at least one of the following parameters: packet delay budget (PDB); guaranteed bit rate (GBR); or packet error rate (PER).

[0038] The present application provides a variety of possible parameters included in the fourth information, so that the first functional entity can determine a suitable target strategy according to the parameters in the fourth information, thereby meeting a variety of possible QoS requirements.

[0039] In one possible design, the communication function includes at least one of the following states: an activated state; or a deactivated state.

[0040] This application can flexibly select the communication function to be executed through the activation state and deactivation state.

[0041] According to a second aspect, a communication system is provided, comprising a first functional entity and a third functional entity, wherein the first functional entity is configured to send a first target policy and / or a second target policy, and a first identifier to the third functional entity. The first target policy is configured to indicate a method for dividing the communication functions of the first target entity and the second target entity, and the second target policy is configured to indicate a method for dividing the communication functions of the second target entity and the third target entity. The third functional entity is configured to send the first target policy and / or the second target policy to the second functional entity indicated by the second identifier based on an association relationship between the first identifier and the second identifier. The second functional entity includes at least one of the first target entity, the second target entity, and the third target entity.

[0042] In the process of configuring corresponding target policies for different functional entities, the present application realizes isolation between the first functional entity and the second functional entity through the correspondence between the real identifier and the virtual identifier, thereby improving the security of the network.

[0043] In one possible design, the system further includes a second functional entity, wherein the second functional entity is configured to send the second identifier and first information corresponding to the second identifier to the third functional entity. The third functional entity is further configured to map the second identifier to the first identifier based on the association between the second identifier and the first identifier. The third functional entity sends the first identifier and the first information to the first functional entity. The first information includes at least one of the following: second information corresponding to a communication interface, wherein the second information is used to indicate the network communication status corresponding to the communication interface, the communication interface including a first interface and a second interface, the first interface being the communication interface between the first target entity and the second target entity, and the second interface being the communication interface between the second target entity and the third target entity; third information corresponding to the second functional entity, wherein the third information is used to indicate the processing resource status corresponding to the second functional entity; or fourth information, wherein the fourth information is used to indicate the quality of service (QoS) requirement corresponding to at least one service.

[0044] In a possible design, the third functional entity is further used to: allocate the first identifier associated with the second identifier.

[0045] In one possible design, the second identifier comes from at least one second functional entity.

[0046] In one possible design, the first target policy and / or the second target policy corresponds to any terminal among different terminals; or, the first target policy and / or the second target policy corresponds to any PDU session among different protocol data unit PDU sessions; or, the first target policy and / or the second target policy corresponds to any QoS flow among different QoS flows; or, the first target policy and / or the second target policy corresponds to any DRB among different data radio bearers DRB; or, the first target policy and / or the second target policy corresponds to any data packet among different data packets.

[0047] In one possible design, the first functional entity is further configured to send at least one alternative function splitting mode and / or fifth information to the third functional entity. The fifth information is used to indicate the communication function configured for each second functional entity corresponding to the alternative function splitting mode. The third functional entity is further configured to send the at least one alternative function splitting mode and / or the fifth information to the second functional entity.

[0048] In a possible design, the third functional entity communicates with different second functional entities by transparently transmitting to intermediate nodes.

[0049] In one possible design, the third functional entity, the first functional entity and the second functional entity are independent functional entities; or, the third functional entity is integrated into the second functional entity.

[0050] In one possible design, the third functional entity has a communication connection with at least one of the second functional entities.

[0051] In one possible design, the second functional entity is a functional entity in the RAN, core network or network management domain.

[0052] In a possible design, the second functional entity is a functional entity in the RAN, and the second functional entity includes at least one of the following functional entities: CU; DU; or RU.

[0053] In one possible design, the third functional entity is a CU, and the second functional entity includes a DU and / or a RU; or, the third functional entity is a DU, and the second functional entity includes a CU and / or a RU; or, the third functional entity is a RU, and the second functional entity includes a CU and / or a DU.

[0054] In one possible design, the method of dividing the communication function includes dividing a set consisting of at least one of the following communication functions: communication functions corresponding to the RAN protocol layer; communication functions corresponding to one or more network elements in the core network; and communication functions corresponding to at least one entity used for network management.

[0055] In one possible design, the second information includes at least one of the following parameters: bandwidth resources of the communication interface; transmission delay of the communication interface; packet loss rate of the communication interface; or reliability of the communication interface.

[0056] In one possible design, the third information includes at least one of the following parameters: processor utilization; memory utilization; or disk utilization.

[0057] In one possible design, the fourth information includes at least one of the following parameters: PDB; GBR; or PER.

[0058] In one possible design, the communication function includes at least one of the following states: an activated state; or a deactivated state.

[0059] In a third aspect, a communication device is provided. The communication device is used to implement the various communication methods involved in the first aspect. The communication device includes modules, units, or means corresponding to the above-mentioned communication methods. The modules, units, or means can be implemented through hardware, software, or hardware executing corresponding software implementations. The hardware or software includes one or more modules or units corresponding to the above-mentioned functions.

[0060] In a fourth aspect, a communication device is provided, which includes at least one processor for supporting the communication device to implement the functions involved in any of the above aspects.

[0061] In one possible design, the communication device further includes a memory, which is used to store program instructions and / or data necessary for the communication device.

[0062] In one possible design, the communication device further includes: a communication interface for receiving and / or sending signals; or the communication interface is used for the processor to communicate with other devices or components.

[0063] In a fifth aspect, a communication device is provided, comprising: at least one processor and a communication interface, wherein the communication interface is used to receive and / or send signals, and the processor is configured to enable the communication method of any of the above aspects to be executed.

[0064] In a sixth aspect, a communication device is provided. The communication device includes: at least one processor and a memory; the memory is configured to store computer instructions, and when the processor executes the instructions, the communication device executes the communication method according to any of the above aspects.

[0065] In the seventh aspect, a chip system is provided, which includes a processor and an input / output port, the processor is used to implement the processing functions involved in the communication method of any aspect of the above aspects, and the input / output port is used to implement the transceiver functions involved in the communication method of any aspect of the above aspects.

[0066] In one possible design, the chip system also includes a memory, which is used to store program instructions and data for implementing the functions involved in the communication method of any of the above aspects.

[0067] The chip system may be composed of chips, or may include chips and other discrete devices.

[0068] In an eighth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores computer instructions, which, when executed on a computer, cause the computer to execute any communication method designed in any of the above aspects.

[0069] In a ninth aspect, a computer program product is provided, which includes a computer program or instructions, and when the computer program or instructions are executed on a computer, the computer executes the communication method according to any one of the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] FIG1 is an exemplary diagram of the architecture of a communication system provided in an embodiment of the present application;

[0071] FIG2 is a schematic diagram of a 5G wireless access network architecture provided in an embodiment of the present application;

[0072] FIG3 is a schematic diagram of functional division of an access network device provided in an embodiment of the present application;

[0073] FIG4 is a schematic diagram of a communication scenario provided in an embodiment of the present application;

[0074] FIG5 is a schematic diagram of a communication method provided in an embodiment of the present application;

[0075] FIG6 is a schematic diagram of an alternative function segmentation method provided in an embodiment of the present application;

[0076] FIG7 is a schematic diagram of another alternative function segmentation method provided in an embodiment of the present application;

[0077] FIG8 is a schematic diagram of another alternative function segmentation method provided in an embodiment of the present application;

[0078] FIG9 is a schematic diagram of a network structure of a third functional entity provided in an embodiment of the present application;

[0079] FIG10 is a schematic diagram of a network structure of another third functional entity provided in an embodiment of the present application;

[0080] FIG11 is a schematic diagram of a network structure of another third functional entity provided in an embodiment of the present application;

[0081] FIG12 is a schematic diagram of a network structure of yet another third functional entity provided in an embodiment of the present application;

[0082] FIG13 is a schematic diagram of another communication method provided in an embodiment of the present application;

[0083] FIG14 is a schematic diagram of another communication method provided in an embodiment of the present application;

[0084] FIG15 is a schematic diagram of a communication device provided in an embodiment of the present application;

[0085] FIG16 is a schematic diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0086] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0087] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0088] The terms "first" and "second" in the description and drawings of the embodiments of the present application are used to distinguish different objects, or to distinguish different treatments of the same object. Words such as "first" and "second" can distinguish between identical or similar items with substantially the same functions and effects. For example, the first device and the second device are merely used to distinguish different devices and do not limit their order. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit differences.

[0089] "At least one" means one or more, and "a plurality" means two or more.

[0090] In the description of the embodiments of the present application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in the embodiments of the present application is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.

[0091] In the description of the embodiments of this application, unless otherwise specified, "multiple" means two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural.

[0092] In addition, to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first" and "second" do not limit the quantity or execution order, and the words "first" and "second" do not necessarily mean different.

[0093] Furthermore, the terms "including," "having," and any variations thereof, mentioned in the description of the embodiments of the present application are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to the process, method, product, or apparatus.

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

[0095] It will be understood that the “embodiment” mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the embodiment of the present application. Therefore, the various embodiments in the entire specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It will be understood that in the various embodiments of the embodiment of the present application, the size of the sequence number of each process does not mean 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 embodiment of the present application.

[0096] It can be understood that in the embodiments of the present application, "when" and "if" both mean that corresponding processing will be performed under certain objective circumstances, and do not limit the time, nor do they require any judgment action when implementing, nor do they mean that there are other limitations.

[0097] It is understood that some optional features in the embodiments of the present application may, in certain scenarios, be implemented independently of other features, such as the solution on which they are currently based, to solve corresponding technical problems and achieve corresponding effects. In certain scenarios, they may also be combined with other features as needed. Accordingly, the devices provided in the embodiments of the present application may also implement these features or functions accordingly, which will not be described in detail here.

[0098] In the embodiments of the present application, unless otherwise specified, the same or similar parts between the various embodiments can refer to each other. In the various embodiments of the present application, and the various implementation methods / implementation methods / implementation methods in the various embodiments, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments and the various implementation methods / implementation methods / implementation methods in the various embodiments are consistent and can be referenced to each other. The technical features in different embodiments and the various implementation methods / implementation methods / implementation methods in the various embodiments can be combined to form new embodiments, implementation methods, implementation methods, or implementation methods according to their inherent logical relationships. The implementation methods of the embodiments of the present application described below do not constitute a limitation on the scope of protection of the embodiments of the present application.

[0099] The collection, storage, use, processing, transmission, provision, and disclosure of user personal information in the technical solutions of the embodiments of this application are in compliance with relevant laws and regulations and do not violate public order and good morals. For example, in the technical solutions of the embodiments of this application, the processing of user personal information is performed with the user's authorization, which is explained here and will not be repeated below.

[0100] FIG1 is an example diagram of the architecture of a communication system provided in an embodiment of the present application.

[0101] As shown in FIG. 1 , the communication system involved in the embodiment of the present application may include at least one terminal 110 and a network device 120 .

[0102] Terminal 110 and network device 120 communicate wirelessly. Network device 120 may be a wireless access network device. Terminals and wireless access network devices may be connected to each other via wired or wireless means. Figure 1 is merely a schematic diagram. The communication system may also include other network devices, such as wireless relay devices, wireless backhaul devices, and core network devices, which are not shown in Figure 1. The connection relationships between devices are not limited to the methods listed above.

[0103] The radio access network device may be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNodeB / gNB) in a 5G mobile communication system, a next generation base station in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system; it may also be a module or unit that performs some of the functions of a base station, for example, a centralized unit (CU) or a distributed unit (DU). The radio access network device may be a macro base station, a micro base station, an indoor station, a relay node, a donor node, etc. In other embodiments, the radio access network device may also be an access network device in an open RAN (O-RAN). In O-RAN, the CU may be referred to as an open CU (O-CU), the DU may be referred to as an open DU (O-DU), and the radio unit (RU) may be referred to as an open RU (O-RU). The embodiments of the present application do not limit the specific technologies and device forms used by the wireless access network equipment. The wireless access network equipment is sometimes referred to as the network equipment. For ease of description, the following description uses a base station as an example of the wireless access network equipment.

[0104] A terminal may also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminal devices 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 grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. Terminal devices can be mobile phones, tablet computers, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal devices.

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

[0106] Communication between base stations and terminals, between base stations, and between terminals can be carried out through authorized spectrum, unauthorized spectrum, or both; communication can be carried out through spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or spectrum below 6 GHz and spectrum above 6 GHz. The embodiments of the present application do not limit the spectrum resources used for wireless communication.

[0107] In an embodiment of the present application, the function of the base station may also be performed by a module (such as a chip) in the base station, or by a control subsystem including a base station function. The control subsystem including the base station function here may be a control center in the application scenarios of the above-mentioned terminal devices such as smart grid, industrial control, intelligent transportation, smart city, etc. The function of the repeater may also be performed by a module (such as a chip or a modem) in the repeater, or by a device including a relay function. The function of the terminal may also be performed by a module (such as a chip or a modem) in the terminal, or by a device including a terminal function.

[0108] A wireless communication system includes communication devices, which can communicate wirelessly using air interface resources. Communication devices can include network devices and terminal devices. Network devices can also be referred to as base station devices. Air interface resources can include at least one of time domain resources, frequency domain resources, code resources, and spatial resources. Communication devices can also be referred to as communication devices.

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

[0110] The embodiments of the present application can be used for possible communication links such as uplink (UL), downlink (DL), access link, backhaul link, sidelink (SL), etc., and the embodiments of the present application are not limited here. From the perspective of business scenarios, the embodiments of the present application are applicable to a variety of scenarios, such as extended reality (XR) business, artificial intelligence (AI) business, large-capacity scenarios, etc., and the embodiments of the present application are not limited here. Among them, SL can also be called side link, side line, etc., and the embodiments of the present application are not limited here.

[0111] A 4G base station can be divided into two parts: the baseband unit (BBU) and the radio frequency unit (RRU). The BBU is connected to one or more RRUs via optical fiber, metal wiring, or microwave links. The BBU primarily performs upper-layer centralized processing of baseband signals. The RRU primarily performs functions such as baseband signal reception and transmission, as well as radio frequency signal modulation and demodulation, data processing, and power amplification. The RRU is closer to the antenna, resulting in lower feeder losses. In some cases, the RRU can also be referred to as a RU. In this case, the BBU can process baseband signals in a highly centralized manner, allowing computing resources to be centrally deployed, resulting in high resource utilization and low deployment costs. However, this underlying split places high demands on the bandwidth of the fronthaul link between the BBU and RRU, leading to high fiber deployment costs.

[0112] To reduce the pressure on fronthaul link bandwidth and deployment costs caused by the underlying splitting method, the 3rd Generation Partnership Project (3GPP)'s 5G radio access network considers splitting the base station into two functional entities, such as the CU and DU, at a higher layer. The midhaul link between the CU and DU has lower network bandwidth requirements, so splitting can be performed specifically on the CU and DU. The 5G radio access network is also called the next-generation radio access network (NG-RAN).

[0113] Referring to FIG2 , a 5G wireless access network architecture is shown. For example, the access network device may be a gNB, and the gNB may be composed of two parts: a CU and a DU. Of course, the DU may include one or more parts, which is not limited in the embodiment of the present application. The gNB and the core network elements of the 5G core network (5GC) may communicate via a next generation (NG) interface, and different gNBs may communicate via an Xn interface, such as an Xn-control (C) interface. The CU and different DUs may communicate via an F1 interface.

[0114] In some examples, a static splitting method is adopted for the functional splitting between CU and DU in 5G access network equipment, and a fixed division is made according to the functional granularity of the protocol stack. As shown in Figure 3, protocol stacks such as radio link control (RLC), media access control (MAC) and physical layer (PHY) can be located in the DU of the access network device. Among them, MAC can also be called media access control, medium access control, etc., which is not limited in the embodiments of the present application. Protocol stacks such as radio resource control (RRC), service data adaptation protocol (SDAP) and packet data convergence protocol (PDCP) can be located in the CU of the access network device. Among them, RRC implements air interface radio resources and air interface connection control, and belongs to the control plane (CP) protocol; SDAP performs mapping between quality of service flow (QoS-flow) and data radio bearer (DRB), and belongs to the user plane (UP) protocol. A QoS-flow is represented as a business data flow with specific quality of service (QoS) requirements.

[0115] As shown in Figure 3, for the DU, both the control plane protocol stack and the user plane protocol stack involve RLC, MAC, and PHY. For the CU, PDCP applies to both the control plane protocol stack and the user plane protocol stack, while RRC applies only to the control plane protocol stack and SDAP applies only to the user plane protocol stack. For control plane protocol stack functions, the CU and DU communicate via the F1-C interface; for user plane protocol stack functions, the CU and DU communicate via the F1-User U interface. Based on the separation of the CU and DU, the CU of the access network device can be separated into a CP unit and an UP unit. The CP of the access network device's CU can be denoted as gNB-CU-CP, and the UP of the access network device's CU can be denoted as gNB-CU-UP. The PDCP layer protocol exists in both the gNB-CU-CP unit and the gNB-CU-UP unit. The RRC layer resides above the PDCP layer in the gNB-CU-CP unit, and the SDAP layer resides above the PDCP layer in the gNB-CU-UP unit.

[0116] The RLC layer can provide transparent data transmission as well as data transmission in both non-deterministic and deterministic modes. The MAC layer is primarily responsible for controlling the physical medium connecting to the physical layer. The PHY layer is responsible for transmitting bits or groups of bits on the physical medium, including encoding transmitted information and decoding received information. For specific protocols, please refer to relevant technologies, such as 3GPP Technical Specification (TS) 38.300, and this embodiment will not be described in detail here.

[0117] Currently, during the network deployment phase, a fixed RAN functional partitioning scheme can be set to deploy CUs and DUs based on a priori statistical information, such as network peak rate and average data rate requirements. Obviously, this functional partitioning based solely on fixed or static access network equipment cannot adapt to real-time changes in service traffic. Figure 3 illustrates only one possible functional partitioning scheme; other fixed partitioning schemes will result in insufficient utilization of computing resources and bandwidth resources.

[0118] Regardless of the fixed segmentation method, real-time changes in traffic services will lead to insufficient computing resource utilization and bandwidth utilization. In other words, different services have different QoS requirements for network latency, speed, and reliability, and static segmentation cannot dynamically adapt to diverse service QoS requirements.

[0119] Furthermore, given that the communication process between different functional entities may expose some of the information they share to the public, this presents a certain risk. For example, attackers could exploit server load, cache, and bandwidth information on certain network nodes to identify network vulnerabilities. If a network node experiences excessive load, cache overflow, or transmission link congestion, attackers could launch targeted malicious attacks, potentially paralyzing the network.

[0120] Therefore, the present application provides a communication method, which, in the process of configuring corresponding target strategies for different functional entities, realizes isolation between different functional entities through the correspondence between real identifiers and virtual identifiers, thereby improving the security of the network.

[0121] FIG4 is a schematic diagram of a communication scenario provided in an embodiment of the present application.

[0122] As shown in Figure 4, the access network equipment can be further 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 RUs 210, one or more DUs 220, and one or more CUs 230. The CU 230 is connected to the 5GC 240 to achieve communication with the core network equipment. In the various embodiments of the present application, the core network equipment may also be referred to as a core network element.

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

[0124] In some examples, the access network device may be a gNB. The protocol function entities of the access network device may include a CU 230 and a DU 220. The access network device provides new radio (NR) user and control plane protocol endpoints to the terminal and communicates with the 5GC 240 via an NG interface. NR stands for 5G radio access technology. The access network device provides wireless network connectivity between the terminal and the core network.

[0125] In some examples, CU 230 can host RRC, SDAP, and PDCP protocols for access network devices and control one or more DU operations. CU 230 communicates with DU 220 via an F1 interface.

[0126] In some examples, the DU 220 may host the RLC, MAC, and PHY layers of the access network equipment, whose operations are controlled by the CU 230. One DU 220 may support one or more cells, and one cell may support one DU 220.

[0127] In some examples, 5GC 240 may include any possible core network elements such as an access and mobility management function (AMF) entity, a session management function (SMF) entity, a user plane function (UPF) entity, and a unified data management (UDM) entity.

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

[0129] In some embodiments, the access network device may be split into two functional entities. For example, if the CU 230 and DU 220 are deployed on the same physical device, the CU 230 and DU 220 can be considered as one functional entity. Alternatively, if the DU 220 and RU 210 are deployed on the same physical device, the DU 220 and RU 210 can be considered as one functional entity.

[0130] Of course, the present application is not limited to the 5G network architecture. The embodiments of the present application are also applicable to future possible network architectures such as the long term evolution (LTE) network and the 6G network. It should be understood that the embodiments of the present application can be applied to any network architecture with communication connection capabilities.

[0131] FIG5 is a flow chart of a communication method provided in an embodiment of the present application.

[0132] As shown in FIG5, the communication process can be applied to but not limited to the communication scenarios shown in FIG1 and FIG4. The method may include the following steps:

[0133] S101: A first functional entity sends a first target policy and / or a second target policy, and a first identifier to a third functional entity.

[0134] In some embodiments, the third functional entity may receive the first target policy and / or the second target policy, and the first identifier from the first functional entity.

[0135] Among them, the first target strategy can be used to indicate the way in which the communication functions of the first target entity and the second target entity are divided. The second target strategy can be used to indicate the way in which the communication functions of the second target entity and the third target entity are divided. Among them, the first identifier can be considered as a virtual identifier, which is used to indicate the virtual first target entity, the second target entity and / or the third target entity. For example, the first target entity can have a real identifier, and the first target entity can be uniquely indicated by the real identifier. At the same time, the first target entity can have a virtual identifier, and the virtual identifier can indicate functional entity A, which can be equivalent to the first target entity, but the virtual identifier can only uniquely indicate functional entity A, and the first target entity cannot be determined.

[0136] For example, the identifier may be an identity (ID) or an index. For example, the first identifier may be a virtual ID of the first target entity, the second target entity, and / or the third target entity.

[0137] In some examples, the first functional entity can be considered a functional entity that determines one or more target policies, that is, a functional entity used to flexibly divide communication functions between different target entities. For example, the first functional entity can be called a radio access network split control function (RSCF). Of course, the embodiment of the present application does not limit the name of the first functional entity.

[0138] In some embodiments, the first target entity, the second target entity, and the third target entity are functional entities in a radio access network (RAN), a core network, and / or a network management domain.

[0139] For example, the second functional entity is a CU. Alternatively, the second functional entity is a functional entity that includes CU and AMF functions. Alternatively, the second functional entity is a functional entity that includes CU and UPF functions. Alternatively, the second functional entity is a functional entity that includes CU and operations administration and maintenance (OAM) functions, etc. Among them, OAM can be considered as a function belonging to the network management domain. It will be understood that the above descriptions are merely some exemplary descriptions and are not limited in the embodiments of the present application.

[0140] The embodiments of the present application can dynamically divide multiple communication functions such as wireless access network, core network and network management domain to improve universality.

[0141] In some embodiments, in the case where the first target entity, the second target entity, and the third target entity are functional entities in the RAN, the functional entities in the RAN may include at least one functional entity of a CU, a DU, and a RU.

[0142] For example, if the first functional entity determines a first target policy and a second target policy, in this case, the first target entity may be a CU, the second target entity may be a DU, and the third target entity may be a RU. Alternatively, the first target entity may be a RU, the second target entity may be a DU, and the third target entity may be a CU.

[0143] For another example, if the first functional entity determines the first target strategy or the second target strategy. Then the first target entity, the second target entity and the third target entity can be any of the functional entities mentioned above. Taking the first target entity and the second target entity as an example, the first target entity can be a CU and the second target entity can be a DU. Or, the first target entity can be a DU and the second target entity can be an RU. Alternatively, the first target entity can be a functional entity with CU and DU functions and the second target entity can be an RU. Alternatively, the first target entity can be a CU and the second target entity can be a functional entity with DU and RU functions. Similarly, the division of the second target entity and the third target entity is similar to the division of the first target entity and the second target entity, and the embodiments of the present application will not be repeated here.

[0144] The embodiments of the present application implement flexible adjustment of the communication functions of multiple functional entities such as CU, DU, and RU in the RAN, so as to adapt to the service quality requirements of different services, improve the utilization of bandwidth and computing resources, and reduce the deployment cost of different functional entities in the RAN.

[0145] Next, the embodiments of the present application provide a first target strategy and / or a second target strategy based on different granularities.

[0146] Scenario A:

[0147] In some embodiments, the first target policy and / or the second target policy corresponds to any terminal among different terminals.

[0148] For example, the first functional entity may determine, for different terminals, the first target policy and / or the second target policy corresponding to any terminal. In other words, the first functional entity may determine, for each possible terminal based on the granularity of the terminal, the first target policy and / or the second target policy corresponding to the terminal.

[0149] For example, for terminal 1, the first target policy and / or the second target policy corresponding to terminal 1 is determined; for terminal 2, the first target policy and / or the second target policy corresponding to terminal 2 is determined.

[0150] Case B:

[0151] In some embodiments, the first target policy and / or the second target policy corresponds to any protocol data unit (PDU) session in different PDU sessions.

[0152] For example, the first functional entity may determine, for different PDU sessions, the first target policy and / or the second target policy corresponding to any PDU session. In other words, the first functional entity may determine, for each possible PDU session based on the granularity of the PDU session, the first target policy and / or the second target policy corresponding to the PDU session.

[0153] For example, for PDU session 1, determine the first target policy and / or second target policy corresponding to PDU session 1; for PDU session 2, determine the first target policy and / or second target policy corresponding to PDU session 2.

[0154] Case C:

[0155] In some embodiments, the first target policy and / or the second target policy corresponds to any QoS flow among different QoS flows.

[0156] For example, the first functional entity can determine the first target policy and / or second target policy corresponding to any QoS flow for different QoS flows. In other words, the first functional entity can determine the first target policy and / or second target policy corresponding to each possible QoS flow based on the granularity of the QoS flow.

[0157] For example, for QoS flow 1, the first target policy and / or the second target policy corresponding to QoS flow 1 is determined; for QoS flow 2, the first target policy and / or the second target policy corresponding to QoS flow 2 is determined.

[0158] Situation D:

[0159] In some embodiments, the first target policy and / or the second target policy corresponds to any DRB in different data radio bearers (DRBs).

[0160] For example, the first functional entity may determine the first target policy and / or second target policy corresponding to any DRB for different DRBs. In other words, the first functional entity may determine the first target policy and / or second target policy corresponding to each possible DRB based on the granularity of the DRB.

[0161] For example, for DRB 1, determine the first target policy and / or the second target policy corresponding to DRB 1; for DRB 2, determine the first target policy and / or the second target policy corresponding to DRB 2.

[0162] Case E:

[0163] In some embodiments, the first target policy and / or the second target policy correspond to any data packet in different data packets.

[0164] For example, the first functional entity can determine the first target policy and / or second target policy corresponding to any data packet for different data packets. In other words, the first functional entity can determine the first target policy and / or second target policy corresponding to each possible data packet based on the granularity of the data packet.

[0165] For example, for data packet 1, the first target policy and / or the second target policy corresponding to data packet 1 is determined; for data packet 2, the first target policy and / or the second target policy corresponding to data packet 2 is determined.

[0166] Case F:

[0167] In some embodiments, the first functional entity may determine a target policy corresponding to any RU for different RUs. When the target policy is the first target policy, the first target entity may be the DU and the second target entity may be the RU, or the first target entity may be the RU and the second target entity may be the DU. When the target policy is the second target policy, the second target entity may be the DU and the third target entity may be the RU.

[0168] In this case, considering that a DU can be connected to one or more different RUs, the first functional entity can determine the first target policy corresponding to each possible RU based on the granularity of the RU.

[0169] For example, a DU is connected to two RUs, including RU 1 and RU 2. For RU 1, the target policy corresponding to RU 1 is determined; for RU 2, the target policy corresponding to RU 2 is determined.

[0170] Case G:

[0171] In some embodiments, the first functional entity may determine, for different cells, a first target strategy and / or a second target strategy corresponding to any cell. Considering that a DU may correspond to one or more different cells, the first functional entity may determine, for each possible cell based on the cell granularity, a first target strategy and / or a second target strategy corresponding to the cell.

[0172] For example, for cell 1, the first target strategy and / or the second target strategy corresponding to cell 1 is determined; for cell 2, the first target strategy and / or the second target strategy corresponding to cell 2 is determined.

[0173] The embodiments of the present application can determine target strategies at different granularities so that flexible adjustment of communication functions can be achieved at corresponding granularities.

[0174] S102: The third functional entity sends the first target policy and / or the second target policy to the second functional entity indicated by the second identifier based on the association relationship between the first identifier and the second identifier.

[0175] In some embodiments, the third functional entity may send the first target policy and / or the second target policy to the second functional entity indicated by the second identifier based on the association relationship between the first identifier and the second identifier.

[0176] The second functional entity includes at least one of the first target entity, the second target entity, and the third target entity. That is, the first target entity, the second target entity, and the third target entity can be collectively referred to as the second functional entity.

[0177] In some examples, the second identifier can be considered a real identifier, used to indicate the real first target entity, the second target entity, and / or the third target entity. For example, the second identifier can be the real ID of the first target entity, the second target entity, and / or the third target entity. The real identifier can be, for example, a real ID, a real index, etc., which is not limited in this embodiment of the present application.

[0178] As can be understood, the third functional entity maps and converts the real and virtual identities of different second functional entities, thereby isolating the second functional entities from the first functional entity. This ensures that the first functional entity is unaware of the real second functional entities when determining target policies. Instead, communication functions are divided for each virtual second functional entity, thereby ensuring the security of the second functional entities.

[0179] In some examples, the third functional entity can be considered as a functional entity for implementing mutual conversion between the first identifier and the second identifier. For example, the third functional entity can be called a proxy, a proxy entity, a proxy functional entity, or a proxy server, etc. The embodiment of the present application does not limit the name of the third functional entity.

[0180] In some examples, the second functional entity may configure the communication function corresponding to its own functional entity according to the received target policy.

[0181] For example, the first target entity receives the first target policy and configures the communication function corresponding to the first target entity based on the first target policy. Similarly, the second target entity and the third target entity are similar, and the embodiments of the present application are not repeated here.

[0182] Of course, for the second target entity, the first target policy and the second target policy may be involved at the same time. In this case, the function configured for the second target entity by one of the target policies is often a subset of the function configured for the second target entity by another target policy. For example, when the first target entity is CU, the second target entity is DU, and the third target entity is RU. The functions configured for DU by the first target policy actually include the functions configured for DU and RU by the second target policy. The functions configured for DU by the second target policy are part of the functions configured for DU by the first target policy. Therefore, DU can actually configure corresponding communication functions for the DU based on the second target policy.

[0183] In the process of configuring corresponding target policies for different functional entities, the embodiment of the present application realizes isolation between the first functional entity and the second functional entity through the correspondence between the real identifier and the virtual identifier, thereby improving the security of the network.

[0184] In the communication method provided in the embodiment of the present application, in order to make the communication function division corresponding to different second functional entities more reasonable, the first functional entity can determine the first target strategy and / or the second target strategy based on the first information of the second functional entity.

[0185] In some embodiments, the second functional entity may send a second identifier and the first information corresponding to the second identifier to the third functional entity. It can be understood that the second identifier is used to identify the second functional entity. For example, the first target entity sends a second identifier indicating the first target entity and the first information corresponding to the first target entity to the third functional entity. For another example, the second target entity sends a second identifier indicating the second target entity and the first information corresponding to the second target entity to the third functional entity. For another example, the third target entity sends a second identifier indicating the third target entity and the first information corresponding to the third target entity to the third functional entity. The third functional entity may map the second identifier to the first identifier based on the association between the second identifier and the first identifier. The third functional entity may send the first identifier and the first information to the first functional entity.

[0186] For example, the third functional entity may send a first identifier indicating a first target entity and first information corresponding to the first target entity to the first functional entity. For another example, the third functional entity may send a first identifier indicating a second target entity and first information corresponding to the second target entity to the first functional entity. For another example, the third functional entity may send a first identifier indicating a third target entity and first information corresponding to the third target entity to the first functional entity.

[0187] In some embodiments, the third functional entity may obtain the second identifier from at least one second functional entity. For example, the second identifier may be sent from the second functional entity to the third functional entity together with the first information corresponding to the second identifier. Of course, the second identifier may also be sent independently from the second functional entity to the third functional entity.

[0188] In some embodiments, the third functional entity may allocate a first identifier associated with the second identifier to the second identifier, so that the third functional entity can obtain the association relationship between the first identifier and the second identifier.

[0189] In some examples, the first identifier assigned by the third functional entity to the second identifier may have a certain validity period. For example, the assigned first identifier may be allowed to be used within certain specific time periods. For example, it may be allowed to be used during this PDU session, or it may be allowed to be used within one day, etc. When the validity period expires, the first identifier becomes invalid. The third functional entity may again assign a new first identifier to the second identifier, or reconfigure a new validity period for the invalid first identifier, etc., which is not limited in the embodiments of the present application.

[0190] It is understood that, in general, a unique first identifier is assigned to a second identifier. Different second identifiers correspond to different first identifiers. In some examples, the third functional entity assigns the first identifier associated with the second identifier, which can also be represented as the third functional entity generating the first identifier associated with the second identifier.

[0191] In the embodiment of the present application, the third functional entity can allocate the first identifier associated with the second identifier, which can more flexibly implement the configuration of the first identifier.

[0192] At the same time, the embodiment of the present application obtains the second identifier of at least one second functional entity so that the third functional entity configures the corresponding first identifier for the second identifier, thereby ensuring the security of information related to the second functional entity.

[0193] In some embodiments, the first information may include second information corresponding to the communication interface, wherein the second information is used to indicate the network communication status corresponding to the communication interface.

[0194] For example, the communication interface may include a first interface and a second interface, wherein the first interface is a communication interface between the first target entity and the second target entity, and the second interface is a communication interface between the second target entity and the third target entity.

[0195] In some examples, the second information may include bandwidth resources of the communication interface.

[0196] In some examples, the second information may include a transmission delay of the communication interface.

[0197] In some examples, the second information may include a packet loss rate of the communication interface.

[0198] In some examples, the second information may include reliability of the communication interface.

[0199] In some examples, the second information may include bandwidth resources of the communication interface and transmission delay of the communication interface. In some examples, the second information may include bandwidth resources of the communication interface, transmission delay of the communication interface, and reliability of the communication interface. In some examples, the second information may include bandwidth resources of the communication interface, transmission delay of the communication interface, packet loss rate of the communication interface, and reliability of the communication interface.

[0200] It can be understood that the above only shows a limited number of examples, and the second information may also include any other two or three items, which is not limited in the embodiments of the present application.

[0201] In other examples, the second information may also include any other parameters related to the network communication status, which is not limited in the embodiment of the present application.

[0202] The embodiment of the present application provides a variety of possible parameters included in the second information, so that the first functional entity can determine a suitable target strategy according to the parameters in the second information.

[0203] In some embodiments, the first information may include third information corresponding to the second functional entity. The third information is used to indicate the processing resource status corresponding to the second functional entity. For example, the third information corresponding to the first target entity may indicate the processing resource status corresponding to the first target entity. For another example, the third information corresponding to the second target entity may indicate the processing resource status corresponding to the second target entity. For another example, the third information corresponding to the third target entity may indicate the processing resource status corresponding to the third target entity.

[0204] In some examples, the first functional entity may further obtain third information from the first target entity, the second target entity, and / or the third target entity. For example, the first functional entity may obtain third information corresponding to the first target entity from the first target entity. For another example, the first functional entity may obtain third information corresponding to the second target entity from the second target entity. For another example, the first functional entity may obtain third information corresponding to the third target entity from the third target entity.

[0205] In some examples, the third information may include processor utilization.

[0206] In some examples, the third information may include memory utilization.

[0207] In some examples, the third information may include disk utilization.

[0208] In some examples, the third information may include processor utilization and memory utilization. In some examples, the third information may include processor utilization and disk utilization. In some examples, the third information may include memory utilization and disk utilization. In some examples, the third information may include processor utilization, memory utilization, and disk utilization.

[0209] In other examples, the third information may also include any other parameters related to the processing resource status, which is not limited in the embodiment of the present application.

[0210] The embodiment of the present application provides a variety of possible parameters included in the third information, so that the first functional entity can determine a suitable target strategy according to the parameters in the third information.

[0211] In some embodiments, the first information may include fourth information, where the fourth information is used to indicate a quality of service (QoS) requirement corresponding to at least one service.

[0212] In some embodiments, the fourth information may include a packet delay budget (PDB).

[0213] In some embodiments, the fourth information may include a guaranteed bit rate (GBR).

[0214] In some embodiments, the fourth information may include a packet error rate (PER).

[0215] In some embodiments, the fourth information may include PDB and GBR. In some embodiments, the fourth information may include PDB and PER. In some embodiments, the fourth information may include GBR and PER. In some embodiments, the fourth information may include PDB, GBR, and PER.

[0216] In other examples, the fourth information may also include any other parameters related to QoS, which is not limited in the embodiment of the present application.

[0217] The embodiment of the present application provides a variety of possible parameters included in the fourth information, so that the first functional entity can determine a suitable target strategy according to the parameters in the fourth information, thereby meeting a variety of possible QoS requirements.

[0218] In some embodiments, the first functional entity can determine the first target strategy and / or the second target strategy based on one or more of the second information corresponding to the first interface, the second information corresponding to the second interface, the fourth information, the third information corresponding to the first target entity, the third information corresponding to the second target entity, and the third information corresponding to the third target entity.

[0219] For example, the first functional entity may determine the first target policy based on the second information corresponding to the first interface. For another example, the first functional entity may determine the second target policy based on the second information corresponding to the second interface and the third information corresponding to the second target entity. For another example, the first functional entity may determine the first target policy based on the second information corresponding to the first interface, the third information corresponding to the first target entity, and the third information corresponding to the second target entity. For another example, the first functional entity may determine the first target policy and the second target policy based on the second information corresponding to the first interface, the fourth information, the third information corresponding to the first target entity, and the third information corresponding to the third target entity. For another example, the first functional entity may determine the first target policy and the second target policy based on the second information corresponding to the first interface, the second information corresponding to the second interface, the fourth information, the third information corresponding to the first target entity, and the third information corresponding to the third target entity. For another example, the first functional entity may determine the first target policy and the second target policy based on the second information corresponding to the first interface, the second information corresponding to the second interface, the fourth information, the third information corresponding to the first target entity, the third information corresponding to the second target entity, and the third information corresponding to the third target entity.

[0220] Of course, the above only shows a limited number of examples. The first functional entity can also include any other one, two, three, four, five or six parameters to determine the first target strategy and / or the second target strategy. The embodiments of the present application are not limited here.

[0221] In some examples, the first interface may be a communication interface between a first target entity and a second target entity. For example, if the first target entity is a CU and the second target entity is a DU, the first interface may be an interface corresponding to a midhaul link. In other examples, the second interface may be a communication interface between a second target entity and a third target entity. For example, if the second target entity is a DU and the second target entity is a RU, the second interface may be an interface corresponding to a fronthaul link.

[0222] In the embodiment of the present application, when the first functional entity comprehensively determines the target strategy based on the network communication status of the communication interface, the processing resource status of the functional entity, the QoS requirements of the service, and other dimensions, the first functional entity cannot know the true second functional entity, thereby ensuring the security of the corresponding information of the second functional entity.

[0223] In the communication method provided in the embodiment of the present application, in order to ensure that any second functional entity cannot obtain information related to other second functional entities, the third functional entity communicates with different second functional entities by transparent transmission to the intermediate node.

[0224] In some embodiments, when the third functional entity sends target policies to different second functional entities, for example, a first target policy is associated with the first and second target entities but not the third target entity. Meanwhile, a second target policy is associated with the second and third target entities but not the first target entity. Therefore, the third functional entity can use an intermediate node transparent transmission method to send different target policies to each second functional entity.

[0225] For example, the first target entity is CU, the second target entity is DU, and the third target entity is RU. The first target policy is related to CU and DU, and the second target policy is related to DU and RU. The third functional entity can send the first target policy and the second target policy to the CU. However, since the second target policy is irrelevant to the CU, the CU cannot parse out the information related to the second target policy. It can also be considered that the information related to the second target policy is transparent to the CU. The CU forwards the second target policy to the DU.

[0226] For another example, when the second functional entity sends the first information to the third functional entity. Assume that the first target entity is CU, the second target entity is DU, and the third target entity is RU. RU can send the third information corresponding to RU to DU, which cannot be parsed for DU and CU. DU forwards the third information corresponding to RU to CU, and DU can also send the third information corresponding to DU to CU. For CU, the third information corresponding to RU and the third information corresponding to DU cannot be parsed. CU continues to forward the third information corresponding to RU and the third information corresponding to DU to the third functional entity. In this case, CU can also send the third information corresponding to CU to the third functional entity.

[0227] For example, the third information of any second functional entity may be carried in a container message that is visible only to the third functional entity.

[0228] It can be understood that the specific implementation process of the intermediate node transparent transmission method can refer to relevant technologies, and the embodiments of this application will not be repeated here.

[0229] The embodiment of the present application adopts the method of transparent transmission through intermediate nodes, so that any second functional entity cannot obtain information related to other second functional entities, thereby ensuring the security of information between different second functional entities.

[0230] In the communication method provided in an embodiment of the present application, in order to reduce resource overhead during the communication process of indicating the first target policy and / or the second target policy to the second functional entity, the method may further include: the first functional entity sending at least one alternative function splitting method and / or fifth information to the third functional entity. The fifth information is used to indicate the communication function configured for each second functional entity corresponding to the alternative function splitting method. The third functional entity sends at least one alternative function splitting method and / or the fifth information to the second functional entity.

[0231] In some embodiments, the first functional entity may send at least one alternative function segmentation method to the third functional entity. For example, the first functional entity sends any possible segmentation method involved in the above embodiments, such as method 1, option 3, and method 7, to the first target entity.

[0232] For example, in the case where the first functional entity sends at least one alternative functional splitting method, the first information sent by the first functional entity may include an identifier representing the first target functional splitting method, and / or an identifier representing the second target functional splitting method. Among them, the alternative functional splitting methods may include the first target functional splitting method and the second target functional splitting method. The first target strategy may include the first target functional splitting method, and / or the communication function of each second functional entity under the first target functional splitting method. The second target strategy may include the second target functional splitting method, and / or the communication function of each second functional entity under the second target functional splitting method. In this case, the first information may include identifier 1, which is used to indicate that the first target functional splitting method is "method 2", assuming that the first target entity is CU and the second target entity is DU. This allows the CU to determine the communication function corresponding to the CU based on method 2 indicated by the first information.

[0233] In other embodiments, the first functional entity may send fifth information to the third functional entity. The fifth information may indicate the communication function of each functional entity corresponding to the alternative functional segmentation method. For example, taking the alternative functional segmentation method including method 2, and the two second functional entities corresponding to the alternative functional segmentation method are CU and DU as an example, the fifth information includes the communication function corresponding to the CU divided by method 2, and the communication function corresponding to the DU. For another example, taking the alternative functional segmentation method including method 2 and method 5, and the two second functional entities corresponding to the alternative functional segmentation method are CU and DU as an example, the fifth information includes the communication function corresponding to the CU divided by method 2, and the communication function corresponding to the DU; and the communication function corresponding to the CU divided by method 5, and the communication function corresponding to the DU.

[0234] For example, when the first functional entity sends the fifth information, the first information sent by the first functional entity may include identifiers indicating the communication functions corresponding to different functional entities. For example, the first information may include identifier 2, and the second functional entity may determine the communication functions of each corresponding functional entity based on identifier 2 and configure the corresponding communication functions of its own functional entity.

[0235] In some further embodiments, the first functional entity may send at least one alternative functional division method and fifth information to the third functional entity. It is understood that in this embodiment, the fifth information should include the communication functions of each functional entity corresponding to each alternative functional division method in the at least one alternative functional division method sent. For example, if the at least one alternative functional division method sent by the first functional entity to the second functional entity includes Method 2 and Method 6, then the fifth information sent by the first functional entity to the second functional entity should include the communication functions corresponding to the two second functional entities divided by Method 2, and the communication functions corresponding to the two second functional entities divided by Method 6.

[0236] In some embodiments, the third functional entity may forward the received at least one alternative function splitting mode and / or the fifth information to one or more second functional entities.

[0237] The embodiment of the present application can also inform the second functional entity in advance of multiple alternative function division methods and / or corresponding communication functions, so that when indicating the target policy, only part of the information needs to be indicated, thereby reducing resource overhead during the communication process.

[0238] In the communication method provided in the embodiment of the present application, the method of dividing the communication function may include a method of dividing a set consisting of at least one of the following communication functions: the communication function corresponding to the RAN protocol layer; the communication function corresponding to one or more network elements in the core network; and the communication function corresponding to at least one entity used for network management.

[0239] In some embodiments, the communication function segmentation method may be a segmentation method for the communication function corresponding to the RAN protocol layer, wherein the segmentation method may include at least one of an alternative function segmentation method, a first target function segmentation method, and a second target function segmentation method.

[0240] In some examples, reference is made to FIG6 showing a variety of possible alternative function division methods. The communication functions can be divided according to the protocol layer granularity. For example, a variety of possible alternative function division methods such as options 1 to 8 are provided. Among them, option 1 can be the communication function division between RRC and PDCP shown in FIG6, or option 1 can be the communication function division between SDAP and PDCP shown in FIG6. It can be understood that the subsequent embodiments of this application are described using the control plane RRC as an example. For the division of the user plane, RRC can be replaced with SDAP, and the embodiments of this application will not be repeated.

[0241] In each embodiment of the present application, an option may also be referred to as a method, a functional segmentation method, a segmentation method, etc., and may be used interchangeably.

[0242] Option 2 may be the division of communication functions between the PDCP and RLC upper layers, as shown in FIG6 . Option 3 may be the division of communication functions between the RLC upper layer and the RLC lower layer, as shown in FIG6 . Therefore, Option 3 may also be considered as the division of communication functions within the RLC layer. Option 4 may be the division of communication functions between the RLC lower layer and the MAC upper layer, as shown in FIG6 . Option 5 may be the division of communication functions between the MAC upper layer and the MAC lower layer, as shown in FIG6 . Therefore, Option 5 may also be considered as the division of communication functions within the MAC layer. Option 6 may be the division of communication functions between the MAC lower layer and the PHY upper layer, as shown in FIG6 . Option 7 may be the division of communication functions between the PHY upper layer and the PHY lower layer, as shown in FIG6 . Therefore, Option 7 may also be considered as the division of communication functions within the PHY layer. Option 8 may be the division of communication functions between the PHY lower layer and the radio frequency (RF) layer, as shown in FIG6 .

[0243] In other examples, for the division of communication functions within certain protocol layers (intra), such as RLC, MAC and PHY, the protocol layer can be divided into a high layer and a low layer. Next, PHY will be used as an example to describe the division of communication functions within the protocol layer. The division methods of other protocol layers are similar, except that the communication functions within the protocol layer are different. For details, please refer to the communication functions configured in the corresponding protocol layer. The embodiments of the present application are not limited here. Referring to Figure 7, the communication functions within PHY are divided for downlink communication. Assume that the PHY can also be divided into coding, rate mapping, scrambling, modulation, layer mapping, precoding, resource element (RE) mapping, digital beam forming (DBF), inverse fast Fourier transformation (IFFT) / addition of cyclic prefix (CP), digital to analog, analog beamforming and other functions. Here, RE can be a unit radio resource consisting of one subcarrier and one symbol. Then, the splitting method of option 7 can also include option 7-1, option 7-2, option 7-2x and option 7-3.

[0244] For example, Option 7-1 may be the division of communication functionality between IFFT / CP addition and DBF as shown in FIG7 . Option 7-2 may be the division of communication functionality between precoding and layer mapping as shown in FIG7 . Option 7-2x may be the division of communication functionality between DBF and RE mapping as shown in FIG7 . Option 7-3 may be the division of communication functionality between layer mapping and modulation as shown in FIG7 .

[0245] Referring to Figure 8, the communication functions within the PHY are divided for uplink communication. Assume that the PHY can also be divided into decoding (de-coding), rate demapping (rate de-mapping), descrambling (de-scrambling), demodulation (de-modulation), channel estimation (channel estimation) / equalization (equalization), RE demapping (de-mapping), DBF, fast fourier transform (fast fourier transformation, FFT) / CP removal (CP removal), analog to digital (analog to digital), analog beamforming and other functions. Then, the splitting method of Option 7 can also include Option 7-1', Option 7-2', Option 7-2x' and Option 7-3'. Among them, demodulation can also be called demodulation.

[0246] For example, Option 7-1' may be the division of communication functions between FFT / CP removal and DBF as shown in FIG8. Option 7-2' may be the division of communication functions between RE demapping and channel estimation / equalization as shown in FIG8. Option 7-2x' may be the division of communication functions between DBF and RE demapping as shown in FIG8. Option 7-3' may be the division of communication functions between demodulation and descrambling as shown in FIG8.

[0247] Of course, the segmentation method within MAC and RLC can refer to the segmentation method within PHY. Of course, the specific communication functions involved in each protocol layer and the determination of which functions to be segmented together can be determined according to actual conditions, and the embodiments of this application are not limited here.

[0248] It is understood that any of the multiple options shown in Figures 6 to 8 can be considered an alternative functional segmentation method. One or more of the above options constitute one or more alternative functional segmentation methods. The first functional entity can select an option from the one or more alternative functional segmentation methods as the first target functional segmentation method.

[0249] Similarly, the process of the first functional entity determining the second target function segmentation method is similar to the process of determining the first target function segmentation method, and the embodiments of the present application will not be repeated here.

[0250] It is worth noting that the above Figures 6 to 8 only show a limited number of alternative function segmentation methods. In other examples, more or fewer other possible segmentation methods may be included, and the embodiments of the present application are not limited here.

[0251] It is understood that if the first functional entity determines the first target policy and / or the second target policy for different granularities, assuming that the granularity is PDU session, the first target entity is CU and the second target entity is DU. The first target policy corresponding to option 2 can be determined for PDU session 1; and the first target policy corresponding to option 5 can be determined for PDU session 2. Of course, the above description is merely illustrative and is not limited in the present embodiment.

[0252] In some examples, the communication functions involved in the alternative function segmentation method may also include core network functions, network management domain functions, etc. For example, it may also include the mobility management function, user plane function, identity management function, etc. of the core network, which is not limited in this embodiment of the present application.

[0253] The embodiment of the present application provides multiple alternative function segmentation methods in advance and selects the segmentation method corresponding to the target policy from them, thereby reducing the computational complexity of dynamically configuring the target policy and avoiding unreasonable segmentation of the communication function.

[0254] In other embodiments, the communication function may be divided into two types: one type of communication function and one type of communication function corresponding to one or more network elements in the core network.

[0255] For example, the communication functions corresponding to network elements such as AMF, SMF, and UPF in the core network can be divided.

[0256] In some other embodiments, the communication function may be divided into communication functions corresponding to at least one entity used for network management.

[0257] For example, the communication functions corresponding to functional entities in the network management domain such as OAM can be segmented.

[0258] In some embodiments, the communication function may be divided into the communication function corresponding to the RAN protocol layer and the communication function corresponding to one or more network elements in the core network; or, the communication function may be divided into the communication function corresponding to the RAN protocol layer and the communication function corresponding to at least one entity used for network management; or, the communication function may be divided into the communication function corresponding to one or more network elements in the core network and the communication function corresponding to at least one entity used for network management; or, the communication function may be divided into the communication function corresponding to the RAN protocol layer, the communication function corresponding to one or more network elements in the core network, and the communication function corresponding to at least one entity used for network management.

[0259] The embodiments of the present application can flexibly divide various communication functions so that different functional entities are configured with different communication functions to adapt to the service quality requirements of different services in different scenarios.

[0260] Based on the various alternative function division methods provided in Figures 6 to 8, the embodiments of the present application also provide various division situations of the communication functions of different functional entities indicated by multiple first target strategies and second target strategies.

[0261] Case 1:

[0262] In some embodiments, the first target policy indicates that the communication functions of the first target entity include RRC. The second target policy indicates that the communication functions of the second target entity include PDCP, RLC, MAC, and a high physical layer (HIGH PHY). The second target policy indicates that the communication functions of the third target entity include a low physical layer (LOW PHY).

[0263] In some examples, in this case, the first target policy indicates the communication function of the first target entity, and the second target policy may indicate the sum of the communication functions of the second target entity and the third target entity, such as PDCP, RLC, MAC, HIGH PHY, and LOW PHY.

[0264] Case 2:

[0265] In some embodiments, the first target policy indicates that the communication functions of the first target entity include RRC and PDCP. The second target policy indicates that the communication functions of the second target entity include RLC, MAC, and HIGH PHY. The second target policy indicates that the communication functions of the third target entity include LOW PHY.

[0266] In some examples, in this case, the first target policy indicates the communication function of the first target entity, and the second target policy may indicate the sum of the communication functions of the second target entity and the third target entity, such as RLC, MAC, HIGH PHY, and LOW PHY.

[0267] Case 3:

[0268] In some embodiments, the first target policy indicates that the communication functions of the first target entity include RRC, PDCP, and RLC. The second target policy indicates that the communication functions of the second target entity include MAC and HIGH PHY. The second target policy indicates that the communication functions of the third target entity include LOW PHY.

[0269] In some examples, in this case, the first target policy indicates the communication function of the first target entity, and the second target policy may indicate the sum of the communication functions of the second target entity and the third target entity, such as MAC, HIGH PHY, and LOW PHY.

[0270] Case 4:

[0271] In some embodiments, the first target policy indicates that the communication functions of the first target entity include RRC, PDCP, RLC, and MAC. The second target policy indicates that the communication functions of the second target entity include HIGH PHY. The second target policy indicates that the communication functions of the third target entity include LOW PHY.

[0272] In some examples, in this case, the first target policy indicates the communication function of the first target entity, and the second target policy may indicate the sum of the communication functions of the second target entity and the third target entity, such as HIGH PHY and LOW PHY.

[0273] Case 5:

[0274] In some embodiments, the first target policy indicates that the communication functions of the first target entity include RRC, PDCP, RLC, MAC, and HIGH PHY. The first target policy indicates that the communication functions of the second target entity include LOW PHY. It is understood that in this case, the first functional entity can only determine the first target policy.

[0275] For any of the above cases 1 to 5, the HIGH PHY and LOW PHY functions can be separated and relaxed by referring to Figures 7 and 8. After the internal PHY functions are separated, the part closer to the MAC layer can be considered HIGH PHY, and the part closer to the RF layer can be considered LOW PHY.

[0276] In the communication method provided in the embodiments of the present application, the possible manifestations of the first functional entity in the network communication system are taken into consideration. In any of the above embodiments, the first functional entity, the second functional entity, and the third functional entity are independent functional entities. Alternatively, the third functional entity is integrated into the second functional entity.

[0277] In some embodiments, the first functional entity, the second functional entity, and the third functional entity are independent functional entities.

[0278] In some embodiments, the third functional entity has a communication connection with at least one of said second functional entities.

[0279] In some examples, as shown in Figures 9, 10, and 11, the first functional entity, the second functional entity, and the third functional entity are independent and different functional entities. The third functional entity can have a communication connection with any one or more functional entities of the first target entity, the second target entity, and the third target entity.

[0280] For example, the first functional entity can be deployed as an independent network element in the RAN, core network, or network management domain. The first functional entity is connected to one or more second functional entities through a third functional entity. The third functional entity isolates the first functional entity from each second functional entity. By assigning virtual identity information to the second functional entity, the first functional entity can be shielded from the second functional entity's true identity information. For example, if the second functional entity sends information related to network status, processing status, etc., the first functional entity is unaware of the true identity of the second functional entity described in this information.

[0281] For example, referring to Figure 9, a first functional entity can be connected to a third functional entity. The third functional entity can be connected to multiple second functional entities. For example, the third functional entity can be connected to a first target entity, the third functional entity can be connected to a second target entity, and the third functional entity can be connected to a third target entity.

[0282] For another example, referring to Figure 10 , a first functional entity can be connected to multiple third functional entities. Different third functional entities are each connected to a second functional entity. For example, the first target entity, the second target entity, and the third target entity are each connected to a third functional entity. In this case, the corresponding three third functional entities are connected to one first functional entity.

[0283] For another example, referring to Figure 11, a first functional entity can be connected to a third functional entity. This third functional entity can also be connected to a second functional entity. As shown in Figure 11, the third functional entity is connected to a third target entity, and the first functional entity is connected to the third functional entity. In this case, for other second functional entities, for example, the first target entity can be connected to the second target entity, and the second target entity can be connected to the third target entity. In other words, other second functional entities can be indirectly connected to the third functional entity through the third target entity.

[0284] In the embodiments of the present application, the third functional entity can establish a communication connection with one or more second functional entities in a scenario independent of the first functional entity and the second functional entity. The number of third functional entities and the connection method with the second functional entities can be dynamically selected in different scenarios. This ensures isolation between the first functional entity and the second functional entity in various scenarios, thereby guaranteeing the security of data transmission.

[0285] In some other embodiments, as shown in Figure 12, the third functional entity may be integrated into the second functional entity. For example, the third functional entity may be integrated into the first target entity, the second target entity, or the third target entity.

[0286] For example, the second functional entity is a functional entity in the RAN, such as the second functional entity is a CU, DU, and / or RU. Then the third functional entity can be integrated into the CU, DU, and / or RU. For another example, the third functional entity can also be integrated into a near-real-time radio access network intelligent controller (NRT-RIC) or a non-real-time radio access network intelligent controller (Non-RT RIC) in the O-RAN architecture.

[0287] For another example, the second functional entity is a functional entity in the core network, such as the second functional entity is an AMF. The third functional entity can be integrated into the AMF.

[0288] For another example, the second functional entity is a functional entity in the network management domain, such as the second functional entity is an OAM, and the third functional entity may be integrated into the OAM.

[0289] Of course, Figures 9 to 12 are described using 5G NR as an example. The embodiments of the present application can also be applied to the future 6G network architecture. For example, the first functional entity is deployed in any network element function such as the RAN, core network or network management domain defined in the 6G network. For example, a possible 6G network architecture includes a radio network area (RNA) and an RU. The RNA may include a CU, a DU and / or a core network function. The first functional entity can be deployed on the RNA and / or the RU to realize the division of communication functions between the RNA and the RU.

[0290] The embodiments of the present application provide multiple deployment methods for the third functional entity, which are applicable to various possible network architectures, so that various network architectures can ensure the security of communication between different functional entities while flexibly dividing network functions including RAN functions.

[0291] In the communication method provided in the embodiment of the present application, the method is applied to the CU, and the second functional entity includes the DU and / or RU; or, the method is applied to the DU, and the second functional entity includes the CU and / or RU; or, the method is applied to the RU, and the second functional entity includes the CU and / or DU.

[0292] In some embodiments, the third functional entity may be a CU. In this case, the second functional entity may include a DU. Alternatively, the second functional entity may include an RU. Alternatively, the second functional entity may include a DU and an RU.

[0293] In some embodiments, the third functional entity may be a DU. In this case, the second functional entity may include a CU. Alternatively, the second functional entity may include an RU. Alternatively, the second functional entity may include a CU and an RU.

[0294] In some embodiments, the third functional entity may be an RU. In this case, the second functional entity may include a CU. Alternatively, the second functional entity may include a DU. Alternatively, the second functional entity may include a CU and a DU.

[0295] The embodiments of the present application can also be applied to functional entities in the RAN, eliminating the need to deploy independent network elements separately, reducing deployment costs, and being applicable to more network architectures, thereby improving universality.

[0296] Next, the above solution will be described based on more specific examples.

[0297] Example A:

[0298] In some embodiments, the third functional entity is deployed independently of the first functional entity and the second functional entity. The third functional entity is communicatively connected to each second functional entity. The second functional entity may include a CU, a DU, and an RU. The first target entity may be a CU, the second target entity may be a DU, and the third target entity may be an RU. The CU and the DU may communicate via an F1 interface, and the DU and the RU may communicate via an F2 interface.

[0299] As shown in FIG13 , an embodiment of the present application further provides a communication method, which may include:

[0300] S201: The first functional entity sends an alternative function splitting method and / or fifth information to the third functional entity.

[0301] For example, the first functional entity may send at least one alternative function segmentation mode and / or fifth information to the third functional entity.

[0302] S202: The third functional entity sends an alternative function splitting method and / or fifth information to the second functional entity.

[0303] In some examples, the third functional entity may forward the at least one alternative function splitting method received in S201 and / or the fifth information to the CU.

[0304] For example, when the third functional entity sends at least one alternative functional splitting method and / or the fifth information to the CU, it may only send the alternative functional splitting method and / or the fifth information related to the communication function splitting of the CU and DU. That is to say, some of the at least one alternative functional splitting methods may be used only for the communication function splitting of the DU and RU, and this part does not need to be sent to the CU. Similarly, the fifth information may also contain communication functions of each functional entity that are only related to the communication function splitting of the DU and RU, and this part does not need to be sent to the CU.

[0305] Similarly, the third functional entity may forward the at least one alternative functional segmentation method and / or the fifth information received in S201 to the DU. Furthermore, the third functional entity may forward the at least one alternative functional segmentation method and / or the fifth information received in S201 to the RU. This process is similar to the process of sending to the CU and will not be further described in detail in this embodiment of the present application.

[0306] It is understandable that S201 and S202 are optional steps. In some cases, at least one alternative function division method and / or the fifth information may also be pre-configured on the CU, DU and / or RU.

[0307] S203: The second functional entity configures the communication function of the functional entity based on the default function segmentation mode.

[0308] For example, any second functional entity, such as a CU, DU, or RU, can configure its own communication functions based on a default functional partitioning scheme. The default functional partitioning scheme can be predefined by the protocol or preconfigured. This ensures that communication services can function normally before the first functional entity adjusts the communication functions of the second functional entity.

[0309] In some examples, if there is no communication service, S203 may not be performed.

[0310] In some examples, the second functional entity may also back up the corresponding communication functions to be executed locally in advance based on at least one alternative function splitting method and / or the fifth information. Assume that there is option 2, the communication functions of each functional entity corresponding to option 2, option 5, and the communication functions of each functional entity corresponding to option 5. Taking DU as an example, DU can configure the communication function corresponding to DU under option 2 based on option 2 and / or the communication functions of each functional entity corresponding to option 2; DU can configure the communication function corresponding to DU under option 5 based on option 5 and / or the communication functions of each functional entity corresponding to option 5. At this time, the communication function corresponding to DU under option 2 and the communication function corresponding to DU under option 5 configured above can both be set to a deactivated state. Of course, if a certain option happens to be the default function splitting method, the communication function corresponding to DU under this option can be set to an activated state.

[0311] For another example, the second functional entity can use virtualization technology or container technology to generate or cancel the communication function corresponding to the second functional entity under different options as needed. The specific implementation process of virtualization technology or container technology can refer to related technologies and will not be repeated in this embodiment of the present application.

[0312] S204, the RU sends an RU state report to the third functional entity.

[0313] In some examples, the RU status report may include third information corresponding to the RU and the second identifier of the RU. In other examples, the RU status report may also include second information corresponding to the second interface.

[0314] S205: The DU sends a DU status report to the third functional entity.

[0315] In some examples, the DU status report may include third information corresponding to the DU, a second identifier of the DU, and second information corresponding to the second interface. The second information corresponding to the second interface may be sent by the RU to the third functional entity in S204. In this case, the DU status report may not include the second information corresponding to the second interface.

[0316] In other examples, the DU status report may also include second information corresponding to the first interface.

[0317] In some examples, if a DU is connected to multiple RUs, the DU status may also include the real IDs of the multiple RUs connected to the DU.

[0318] S206: The CU sends a CU status report to the third functional entity.

[0319] In some examples, the CU status report may include third information corresponding to the CU, the second identifier of the CU, and the second information corresponding to the first interface. The second information corresponding to the first interface may be sent by the DU to the third functional entity in S205. In this case, the CU status report may not include the second information corresponding to the first interface.

[0320] In other examples, the CU status report may further include fourth information.

[0321] In some examples, if a CU is connected to multiple DUs, the CU status may also include the real IDs of the multiple DUs connected to the CU.

[0322] It can be understood that there is no strict order of execution for the steps S204 to S206, and the embodiments of the present application do not limit this.

[0323] S207: The third functional entity replaces the second identifier with the first identifier.

[0324] For example, the second identifier of each second functional entity obtained in S204, S205, and S206 is replaced with the corresponding first identifier. For example, the real ID of the RU is replaced with the virtual ID of the RU, the real ID of the DU is replaced with the virtual ID of the DU, and the real ID of the CU is replaced with the virtual ID of the CU.

[0325] In some examples, the second identifier of each second functional entity may be preconfigured by the third functional entity, for example, allocated by the third functional entity to each second functional entity during the process of establishing a service interface between the second functional entity and the third functional entity.

[0326] It is understood that the first identifier can be uniquely identifiable at the third functional entity, so that other devices or functional entities cannot identify the real second functional entity based on the first identifier, thereby ensuring network security.

[0327] S208: The third functional entity sends the first identifier and the first information to the first functional entity.

[0328] For example, the third functional entity sends one or more of the following to the first functional entity: the virtual ID of the RU, the third information of the RU, the virtual ID of the DU, the third information of the DU, the virtual ID of the CU, the third information of the CU, the fourth information, the second information of the first interface, and the second information of the second interface.

[0329] S209: The first functional entity determines a first target policy and / or a second target policy.

[0330] For example, the first functional entity determines a first target policy and / or a second target policy based on the first information. For example, the first target function segmentation method and / or the second target function segmentation method can be determined from at least one alternative function segmentation method. The first target policy is obtained based on the first target function segmentation method, and the second target policy is obtained based on the second target function segmentation method.

[0331] S210: The first functional entity sends a target policy and a first identifier to the third functional entity.

[0332] For example, the first functional entity sends the first target policy and / or the second target policy, as well as the first identifier of the second functional entity involved in each target policy, to the third functional entity. For example, the first target policy corresponds to the virtual ID of the CU and the virtual ID of the DU; the second target policy corresponds to the virtual ID of the DU and the virtual ID of the RU.

[0333] S211: The third functional entity sends a target policy to the second functional entity.

[0334] For example, the third functional entity determines which real second functional entities correspond to each target policy based on the first identifier. For example, the third functional entity determines the real ID of the CU and the real ID of the DU based on the virtual ID of the CU and the virtual ID of the DU corresponding to the first target policy. The third functional entity can send the first target policy to the CU. The third functional entity can also send the first target policy to the DU. Similarly, the third functional entity can send the second target policy to the DU. The third functional entity can also send the second target policy to the RU.

[0335] S212: The second functional entity configures the communication function of the functional entity based on the target policy.

[0336] For example, any second functional entity, such as CU, DU, and RU, may configure the communication function of its respective functional entity based on the target policy it receives.

[0337] In some examples, if the second functional entity has pre-configured communication functions corresponding to each alternative function splitting method and is set to a deactivated state, in S212, the matching communication functions can be set to an activated state based on the target policy. The remaining unmatched communication functions can be set to a deactivated state or disabled. The matching communication functions can be understood as, assuming the target policy corresponds to Option 2. Therefore, the communication functions corresponding to Option 2 for the second functional entity are the matching communication functions.

[0338] In some cases, a DU may receive both the first and second target policies simultaneously. In this case, the communication functions configured for the DU by one target policy are often a subset of the communication functions configured for the DU by another target policy. Taking the scenario shown in Figure 13 as an example, the DU can be configured with the corresponding communication functions in the split between the DU and the RU.

[0339] It can be understood that the specific implementation process of S201 to S212 can refer to the description of the embodiments in Figures 5 to 12, and the embodiments of the present application will not be repeated here.

[0340] The embodiment described in Example A above describes a method in which a first functional entity obtains status information of a second functional entity through a third functional entity and performs communication function segmentation. This allows real-time acquisition of the network transmission status and processor resource status of one or more second functional entities without revealing the true identity of the second functional entity. This allows for flexible functional segmentation of network entities to meet service traffic demands while reducing overall network operational overhead.

[0341] Example B:

[0342] In some embodiments, the third functional entity is deployed independently of the first functional entity and the second functional entity. The second functional entity may include a CU, a DU, and an RU. The first target entity may be a CU, the second target entity may be a DU, and the third target entity may be an RU. The CU and the DU may communicate via the F1 interface, and the DU and the RU may communicate via the F2 interface. The third functional entity has a communication connection with a second functional entity, such as a CU.

[0343] As shown in FIG14 , an embodiment of the present application further provides a communication method, which may include:

[0344] S301: The first functional entity sends an alternative function splitting method and / or fifth information to the third functional entity.

[0345] S302: The third functional entity sends an alternative function splitting method and / or fifth information to the CU.

[0346] It can be understood that the implementation process of S301 and S302 is similar to that of S201 and S202, and will not be repeated here in the embodiment of the present application.

[0347] S303: The CU sends an alternative function splitting method and / or fifth information to the DU.

[0348] S304: The DU sends the alternative function splitting method and / or the fifth information to the RU.

[0349] It can be understood that the implementation process of S303 and S304 is similar to that of S202, and will not be repeated here in the embodiment of the present application.

[0350] It is understandable that S301 to S304 are optional steps. In some cases, at least one alternative function division method and / or the fifth information may also be pre-configured on the CU, DU and / or RU.

[0351] S305: The second functional entity configures the communication function of the functional entity based on the default function division mode.

[0352] S306: The RU sends an RU status report to the DU.

[0353] It can be understood that the implementation process of S305 and S306 is similar to that of S203 and S204, and will not be repeated here in the embodiment of the present application.

[0354] S307: The DU sends a DU status report to the CU.

[0355] It can be understood that the implementation process of S307 is similar to that of S205, except that the status report of the DU in S307 may include the third information of the RU.

[0356] S308: The CU sends a CU status report to the third functional entity.

[0357] It can be understood that the implementation process of S308 is similar to that of S206, except that the status report of the CU in S308 may include the third information of the RU and the third information of the DU.

[0358] S309: The third functional entity replaces the second identifier with the first identifier.

[0359] S310: The third functional entity sends a first identifier and first information to the first functional entity.

[0360] S311: The first functional entity determines a first target policy and / or a second target policy.

[0361] S312: The first functional entity sends the target policy and the first identifier to the third functional entity.

[0362] S313: The third functional entity sends the target policy to the CU.

[0363] In some examples, the third functional entity may also send the first identifier to the CU, such as the real ID of the DU or the real ID of the RU.

[0364] S314, CU sends the target policy to DU.

[0365] For example, the CU may send the first target policy and / or the second target policy to the DU according to the real ID of the DU.

[0366] S315, DU sends the target policy to RU.

[0367] For example, the DU may send the second target policy to the RU according to the real ID of the RU.

[0368] It can be understood that the implementation process of S309 to S315 is similar to that of S207 to S211, and will not be repeated here in the embodiment of the present application.

[0369] S316: The second functional entity configures the communication function of the functional entity based on the target policy.

[0370] It can be understood that the implementation process of S316 is similar to that of S212, and will not be repeated here in the embodiment of the present application.

[0371] It can be understood that the specific implementation process of S301 to S316 can refer to the description of the embodiments in Figures 5 to 12, and the embodiments of the present application will not be repeated here.

[0372] Of course, if the third functional entity is only connected to the DU or RU, you can refer to the implementation process of Example B. The difference is that each second functional entity needs to communicate with the third functional entity through the second functional entity connected to the third functional entity.

[0373] In some embodiments, for the solution described in Example B, the CU can actually also realize the replacement of the real ID of the RU and DU. For example, the CU can be used to realize the mutual conversion between the real ID and virtual ID of the RU and DU. And the CU can be used to configure the virtual IDs corresponding to the RU and DU respectively. It can be understood that the third functional entity can only configure and replace the real ID of the CU. In this case, the third functional entity can also send a second identifier to the CU, such as the virtual ID of the DU and the virtual ID of the RU. So that the CU can send the corresponding target policy to the real DU and RU based on the second identifier.

[0374] The embodiment described in Example B above provides a method for a first functional entity to obtain status information of each second functional entity solely from the CU via a third functional entity and perform functional segmentation. This allows for real-time acquisition of network transmission status and processor resource status, as well as flexible division of communication functions between different functional entities, without exposing the true identity of each second functional entity and with only an interface to the CU. This allows for meeting service traffic requirements while avoiding excessive interfaces and reducing overall network operational overhead.

[0375] In the communication method provided in the embodiments of the present application, for the case where the third functional entity is integrated into the second functional entity, reference may be made to the implementation process of Figures 13 and 14 . The difference is that the third functional entity is integrated into a second functional entity. For example, if the third functional entity is integrated into a CU, then the CU sending and receiving information to the third functional entity can be considered as data transfer within the functional entity. This embodiment of the present application will not be further described here.

[0376] In the communication method provided in the embodiments of the present application, it is considered that future network nodes may not only have the function of transmission, but also the function of processing application services. For example, artificial intelligence (AI) training and reasoning. Therefore, the embodiments of the present application are also applicable to splitting the computing function of the application server together with the RAN function and the core network function, and instructing them to different functional entities. The embodiments of the present application are not limited here.

[0377] It should be noted that the above-mentioned multiple embodiments can be combined and the combined solutions can be implemented. Optionally, some operations in the process of each method embodiment are optionally combined, and / or the order of some operations is optionally changed. In addition, the execution order between the steps of each process is only exemplary and does not constitute a limitation on the execution order between the steps. There can also be other execution orders between the steps. It is not intended to indicate that the execution order is the only order in which these operations can be performed. Ordinary technicians in this field will think of many ways to reorder the operations of this article. In addition, it should be pointed out that the process details involved in a certain embodiment of this article are also applicable to other embodiments in a similar manner, or different embodiments can be used in combination.

[0378] It is understood that in order to implement the functions in the above embodiments, the base station and the terminal include hardware structures and / or software modules that perform the corresponding functions. Those skilled in the art should readily appreciate that, in combination with the units and method steps of the various examples described in the embodiments disclosed in the present application, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a computer software-driven hardware manner depends on the specific application scenario and design constraints of the technical solution.

[0379] Figures 15 and 16 are schematic diagrams of possible communication devices provided in embodiments of the present application. These communication devices can be used to implement the functions of any possible transmitter in the above-described method embodiments, thereby also achieving the beneficial effects of the above-described method embodiments. In embodiments of the present application, the communication device can be a third functional entity or a module applied to the third functional entity, for example, a chip.

[0380] As shown in FIG. 15 , the communication device 1500 includes a processing unit 1510 .

[0381] In a possible implementation, the communication device 1500 may further include a transceiver unit 1520 .

[0382] In a possible implementation, the communication device 1500 may further include a storage unit 1530 .

[0383] In a possible implementation, the communication device 1500 may further include a transceiver unit 1520 and a storage unit 1530 .

[0384] The communication device 1500 is used to implement the functions of the third functional entity in the method embodiments shown in Figures 5, 13 and 14 above.

[0385] When the communication device 1500 is used to implement the function of the third functional entity in the method embodiment shown in Figure 5: the transceiver unit 1520 is used to receive the first target policy and / or the second target policy. The transceiver unit 1520 is also used to send the first target policy and / or the second target policy to the second functional entity indicated by the second identifier based on the association relationship between the first identifier and the second identifier. The processing unit 1510 is used to execute all operations except the transceiver operation performed by the communication device 1500 in the embodiment shown in Figure 5, and / or other processes for supporting the technology described in this document. The storage unit 1530 is used to store any data, computer instructions and / or computer programs that may be involved in the various embodiments of the present application.

[0386] For a more detailed description of the processing unit 1510 and the transceiver unit 1520, please refer to the relevant descriptions of the method embodiments shown in Figures 5, 13, and 14. The processing unit 1510 and the transceiver unit 1520 may also perform other steps, and the specific implementation can refer to the method embodiments, which will not be repeated here.

[0387] Optionally, the transceiver unit 1520 may be a transceiver, which may include an antenna and a radio frequency circuit, etc.

[0388] The processing unit 1510 may be a processor (or a processing circuit), such as a baseband processor, which may include one or more CPUs.

[0389] As shown in FIG16 , the communication device 1600 includes at least one processor 1610 . In one possible implementation, the communication device 1600 may further include an interface circuit 1620 .

[0390] In a possible implementation, the communication device 1600 may further include a memory 1630 .

[0391] In a possible implementation, the communication device 1600 may further include a memory 1630 and an interface circuit 1620 .

[0392] In some embodiments, the processor 1610 and the memory 1630 are coupled to each other; and / or the processor 1610 and the interface circuit 1620 are coupled to each other. It will be appreciated that the interface circuit 1620 may be a transceiver or an input / output interface. The memory 1630 may be used to store computer instructions executed by the processor 1610, input data required by the processor 1610 to execute computer instructions, or data generated by the processor 1610 after executing computer instructions.

[0393] When the communication device 1600 is used to implement the method shown in Figures 5, 13 and 14, the processor 1610 can be used to implement the functions of the above-mentioned processing unit 1510, and / or the interface circuit 1620 can be used to implement the functions of the above-mentioned transceiver unit 1520, and / or the memory 1630 can be used to implement the functions of the above-mentioned storage unit 1530.

[0394] The communication device shown in FIG. 15 or 16 is merely an example, and in actual applications the communication device may have more or fewer components than those shown in FIG. 15 or 16 , may combine two or more components, or may have a different component configuration.

[0395] In the embodiments of the present application, when entity A sends information to entity B, A may send the information directly to B or indirectly to B through another entity. Similarly, when entity B receives information from entity A, entity B may directly receive the information sent by entity A or indirectly receive the information sent by entity A through another entity. Entities A and B herein may be RAN nodes or terminals, or modules within a RAN node or terminal. The sending and receiving of information may be information exchange between a RAN node and a terminal, for example, information exchange between a network device and a terminal; the sending and receiving of information may also be information exchange between two RAN nodes, for example, information exchange between a CU and a DU; the sending and receiving of information may also be information exchange between different modules within a device, for example, information exchange between a terminal chip and other modules of the terminal, or information exchange between a network device chip and other modules within the network device.

[0396] In the embodiments of the present application, a network device sends downlink signals or downlink information to a terminal device, and the downlink information is carried on a downlink channel. The terminal device sends uplink signals or uplink information to the network device, and the uplink information is carried on an uplink channel. To communicate with the network device, the terminal device needs to establish a wireless connection with a cell controlled by the network device. The cell with which the terminal device has established a wireless connection is called the serving cell of the terminal device.

[0397] It can be understood that in the embodiment of the present application, the physical downlink shared channel (PDSCH) and the physical uplink shared channel (PUSCH) are only used as examples of downlink data channels and uplink data channels. In different systems and different scenarios, data channels and control channels may have different names, and the embodiment of the present application does not limit this.

[0398] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0399] The method steps in the embodiments of the present application can be implemented in hardware or in software instructions that can be executed by a processor. The software instructions can be composed of corresponding software modules, and the software modules 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 disk, mobile hard disk, CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. The storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in a network device or a terminal. The processor and storage medium can also exist in a network device or a terminal as discrete components.

[0400] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented 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 the present application are performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may 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 may 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 may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

[0401] In each embodiment of the present application, unless otherwise specified or provided by logic, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0402] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

Claims

1. A communication method, characterized in that: include: Receiving a first target policy and / or a second target policy, and a first identifier from a first functional entity, wherein the first target policy is used to indicate a splitting method of communication functions between the first target entity and the second target entity, and the second target policy is used to indicate a splitting method of communication functions between the second target entity and the third target entity; Based on the association relationship between the first identifier and the second identifier, the first target policy and / or the second target policy is sent to the second functional entity indicated by the second identifier, wherein the second functional entity includes at least one of the first target entity, the second target entity and the third target entity.

2. The method according to claim 1, characterized in that Before receiving the first target policy and / or the second target policy from the first functional entity, the method further includes: Acquire the second identifier and the first information corresponding to the second identifier; Mapping the second identifier to the first identifier based on the association relationship between the second identifier and the first identifier; Sending the first identifier and the first information to a first functional entity; The first information includes at least one of the following: Second information corresponding to a communication interface, wherein the second information is used to indicate a network communication status corresponding to the communication interface, the communication interface comprising a first interface and a second interface, the first interface being a communication interface between the first target entity and the second target entity, and the second interface being a communication interface between the second target entity and the third target entity; third information corresponding to the second functional entity, wherein the third information is used to indicate a processing resource status corresponding to the second functional entity; or Fourth information, where the fourth information is used to indicate a quality of service (QoS) requirement corresponding to at least one service.

3. The method according to claim 1 or 2, characterized in that The method further comprises: The first identifier associated with the second identifier is allocated.

4. The method according to any one of claims 1 to 3, characterized in that The second identifier comes from at least one second functional entity.

5. The method according to any one of claims 1 to 4, characterized in that The first target policy and / or the second target policy corresponds to any terminal among different terminals; or The first target policy and / or the second target policy corresponds to any PDU session in different protocol data unit PDU sessions; or, The first target policy and / or the second target policy corresponds to any QoS flow among different QoS flows; or, The first target strategy and / or the second target strategy corresponds to any DRB in different data radio bearers (DRBs); or The first target policy and / or the second target policy corresponds to any data packet in different data packets.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: receiving at least one alternative function splitting mode and / or fifth information, wherein the fifth information is used to indicate the communication function configured for each second function entity corresponding to the alternative function splitting mode; Send the at least one alternative function splitting mode and / or the fifth information to the second function entity.

7. The method according to any one of claims 1 to 6, characterized in that Communicate with different second function entities in a manner of transparent transmission to intermediate nodes.

8. The method according to any one of claims 1 to 7, characterized in that The method is applied to a third functional entity, and the third functional entity is independent of the first functional entity and the second functional entity; or, the third functional entity is integrated into the second functional entity.

9. The method according to claim 8, characterized in that The third functional entity has a communication connection with at least one of the second functional entities.

10. The method according to any one of claims 1 to 9, characterized in that The second functional entity is a functional entity in a wireless local area network RAN, a core network or a network management domain.

11. The method according to claim 10, characterized in that The second functional entity is a functional entity in the RAN, and the second functional entity includes at least one of the following functional entities: Centralized unit CU; Distributed Unit DU; or, Radio frequency unit RU.

12. The method according to any one of claims 1 to 10, characterized in that The method is applied to a CU, and the second functional entity includes a DU and / or a RU; or, The method is applied to DU, and the second functional entity includes CU and / or RU; or, The method is applied to RU, and the second functional entity includes CU and / or DU.

13. The method according to any one of claims 1 to 12, characterized in that The communication function segmentation method includes segmentation for a set consisting of at least one of the following communication functions: Communication functions corresponding to the RAN protocol layer; The communication functions corresponding to one or more network elements in the core network; or, At least one communication function corresponding to an entity used for network management.

14. The method according to claim 2, characterized in that The second information includes at least one of the following parameters: Bandwidth resources of the communication interface; Transmission delay of the communication interface; Packet loss rate of the communication interface; or, Reliability of communication interfaces.

15. The method according to claim 2, characterized in that The third information includes at least one of the following parameters: Processor utilization; Memory utilization; or, Disk utilization.

16. The method according to claim 2, characterized in that The fourth information includes at least one of the following parameters: Packet delay budget PDB; Guaranteed Bit Rate GBR; or, Packet Error Rate PER.

17. The method according to any one of claims 1 to 16, characterized in that The communication function includes at least one of the following states: Active state; or, Deactivated state.

18. A communication system, characterized in that: It includes a first functional entity and a third functional entity, wherein: The first functional entity is used to send a first target policy and / or a second target policy, and a first identifier to the third functional entity, wherein the first target policy is used to indicate a splitting method of the communication function of the first target entity and the second target entity, and the second target policy is used to indicate a splitting method of the communication function of the second target entity and the third target entity; The third functional entity is used to send the first target policy and / or the second target policy to the second functional entity indicated by the second identifier based on the association relationship between the first identifier and the second identifier, wherein the second functional entity includes at least one of the first target entity, the second target entity and the third target entity.

19. The system according to claim 18, wherein: The system further comprises a second functional entity, wherein, The second functional entity is configured to send the second identifier and first information corresponding to the second identifier to the third functional entity; The third functional entity is further configured to, based on an association relationship between the second identifier and the first identifier, map the second identifier to the first identifier; The third functional entity sends the first identifier and the first information to the first functional entity; The first information includes at least one of the following: Second information corresponding to a communication interface, wherein the second information is used to indicate a network communication status corresponding to the communication interface, the communication interface comprising a first interface and a second interface, the first interface being a communication interface between the first target entity and the second target entity, and the second interface being a communication interface between the second target entity and the third target entity; third information corresponding to the second functional entity, wherein the third information is used to indicate a processing resource status corresponding to the second functional entity; or Fourth information, where the fourth information is used to indicate a quality of service (QoS) requirement corresponding to at least one service.

20. The system according to claim 18 or 19, characterized in that The third functional entity is further configured to: The first identifier associated with the second identifier is allocated.

21. The system according to any one of claims 18 to 20, characterized in that The second identifier comes from at least one second functional entity.

22. The system according to any one of claims 18 to 21, characterized in that The first target policy and / or the second target policy corresponds to any terminal among different terminals; or The first target policy and / or the second target policy corresponds to any PDU session in different protocol data unit PDU sessions; or, The first target policy and / or the second target policy corresponds to any QoS flow among different QoS flows; or, The first target strategy and / or the second target strategy corresponds to any DRB in different data radio bearers (DRBs); or The first target policy and / or the second target policy corresponds to any data packet in different data packets.

23. The system according to any one of claims 18 to 22, characterized in that The first functional entity is further configured to send at least one alternative function splitting mode and / or fifth information to the third functional entity, wherein the fifth information is used to indicate the communication function configured for each of the second functional entities corresponding to the alternative function splitting mode; The third functional entity is further configured to send the at least one alternative function splitting mode and / or the fifth information to the second functional entity.

24. The system according to any one of claims 18 to 23, wherein: The third functional entity communicates with different second functional entities by transparently transmitting to intermediate nodes.

25. The system according to any one of claims 18 to 24, characterized in that The third functional entity, the first functional entity and the second functional entity are independent functional entities; or, the third functional entity is integrated into the second functional entity.

26. The system according to claim 25, characterized in that The third functional entity has a communication connection with at least one of the second functional entities.

27. The system according to any one of claims 18 to 26, characterized in that The second functional entity is a functional entity in a wireless local area network RAN, a core network or a network management domain.

28. The system according to claim 27, wherein: The second functional entity is a functional entity in the RAN, and the second functional entity includes at least one of the following functional entities: Centralized unit CU; Distributed Unit DU; or, Radio frequency unit RU.

29. The system according to any one of claims 18 to 27, wherein: The third functional entity is a CU, and the second functional entity includes a DU and / or a RU; or, The third functional entity is a DU, and the second functional entity includes a CU and / or a RU; or, The third functional entity is RU, and the second functional entity includes CU and / or DU.

30. The system according to any one of claims 18 to 29, wherein: The communication function segmentation method includes segmentation for a set consisting of at least one of the following communication functions: Communication functions corresponding to the RAN protocol layer; The communication functions corresponding to one or more network elements in the core network; or, At least one communication function corresponding to an entity used for network management.

31. The system according to claim 19, wherein: The second information includes at least one of the following parameters: Bandwidth resources of the communication interface; Transmission delay of the communication interface; Packet loss rate of the communication interface; or, Reliability of communication interfaces.

32. The system according to claim 19, wherein: The third information includes at least one of the following parameters: Processor utilization; Memory utilization; or, Disk utilization.

33. The system according to claim 19, wherein: The fourth information includes at least one of the following parameters: Packet delay budget PDB; Guaranteed bit rate GBR; or, packet error rate PER.

34. The system according to any one of claims 18 to 22, wherein: The communication function includes at least one of the following states: Active state; or, Deactivated state.

35. A communication device, characterized in that: include: processing module and communication module; The communication module is used to receive and / or send signals, and the processing module is configured to enable the method according to any one of claims 1 to 17 to be executed.

36. A communication device, characterized in that include: At least one processor and a communication interface, the communication interface being configured to receive and / or send signals, the processor being configured to enable the method according to any one of claims 1 to 17 to be executed.

37. A communication device, characterized in that: include: At least one processor and a memory, the memory being configured to store computer instructions, the processor being configured to execute the computer instructions so as to cause the communication device to perform the method according to any one of claims 1 to 17.

38. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions or programs, and when the instructions or programs are executed on the communication device, the communication device is caused to execute the method according to any one of claims 1 to 17.

39. A computer program product, characterized in that The computer program product comprises a computer program or instructions, which, when executed on a computer, causes the computer to perform the method according to any one of claims 1 to 17.

Images