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

Abstract

A communication method, apparatus and system, and a storage medium and a program product. The communication method comprises: acquiring a first quality of service (QoS) parameter and a second QoS parameter, wherein the first QoS parameter is used for indicating a QoS requirement corresponding to a communication link between two different types of second functional entities having a communication connection, and the second QoS parameter is used for indicating a QoS requirement of a service; and obtaining a new second QoS parameter on the basis of the first QoS parameter and the second QoS parameter. In the embodiments of the present application, a QoS parameter of the service is adjusted to obtain a new QoS parameter, so that after a DRB is established on the basis of the new QoS parameter, the QoS requirement of the service can be met, thereby improving the user experience.

Description

Communication method, device, system, 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 "202410179465.1" and invention name "Communication Method, Device, System, 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, storage media, and 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] Considering that 5G base stations can be divided into different functional entities, communication between different functional entities will have a certain impact on the quality of service (QoS) of the service, resulting in the QoS of the service failing to meet its QoS requirements. Summary of the Invention

[0005] The present application provides a communication method, device, system, storage medium and program product, which adjusts the QoS parameters of the service to obtain new QoS parameters, so that after establishing DRB based on the new QoS parameters, the QoS requirements of the service can be met and the user experience can be improved.

[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 is applied to a first functional entity, such as the first functional entity or a component (such as a circuit, chip, or chip system) within the first functional entity. The method may include: obtaining a first QoS parameter and a second QoS parameter. The first QoS parameter is used to indicate the QoS requirement corresponding to a communication link between two different types of second functional entities having a communication connection. The second QoS parameter is used to indicate the QoS requirement of a service. A new second QoS parameter is obtained based on the first QoS parameter and the second QoS parameter.

[0008] This application obtains new QoS parameters by adjusting the QoS parameters of the service, so that after establishing DRB based on the new QoS parameters, the QoS requirements of the service can be met and the user experience can be improved.

[0009] In one possible design, the first QoS parameter is obtained by at least one of the following methods: based on the first correspondence and the target policy, determining the first QoS parameter corresponding to the target policy. The first correspondence represents the association between the first QoS parameter and the alternative function splitting method, the alternative function splitting method is a method for splitting the communication function of two different types of second functional entities with communication connections, the alternative function splitting method includes a target function splitting method, and the target function splitting method has an association with the target policy. Alternatively, the first QoS parameter is obtained based on the first information. The first information is used to indicate the network communication status corresponding to the first interface, and the first interface is a communication interface between two different types of second functional entities with communication connections.

[0010] The present application provides multiple ways to determine the first QoS parameter, so that the first functional entity can determine the first QoS parameter in an appropriate way according to different requirements, thereby improving universality.

[0011] In one possible design, the first functional entity is integrated into the second functional entity.

[0012] The present application can be applied to the scenario where the first functional entity is integrated on the second functional entity, so that the QoS parameters of the service can be adjusted in this scenario, and a DRB can be established based on the new QoS parameters to meet the QoS requirements of the service and improve the user experience.

[0013] In one possible design, the first functional entity is integrated in a centralized unit CU, and the method further includes: initiating a wireless data bearer establishment process based on a new second QoS parameter.

[0014] This application is applicable to the scenario where the first functional entity is integrated in the CU. In this scenario, the CU can establish a DRB based on new QoS parameters to meet the QoS requirements of the service, thereby improving the user experience.

[0015] In a possible design, the first functional entity and the second functional entity are independent functional entities.

[0016] The present application can be applied to scenarios where the first functional entity and the second functional entity are independent of each other, so that the QoS parameters of the service can be adjusted in this scenario, and DRB can be established based on the new QoS parameters to meet the QoS requirements of the service and improve user experience.

[0017] In one possible design, the first functional entity and the CU are independent of each other, and the method also includes: sending a new second QoS parameter to the CU or the core network functional network element.

[0018] This application is applicable to the scenario where the first functional entity and the CU are independent of each other, so that in this scenario the CU can establish a DRB based on new QoS parameters to meet the QoS requirements of the service, thereby improving the user experience.

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

[0020] This application can adjust the QoS parameters of the service when the second functional entity includes different communication functions, thereby improving universality.

[0021] 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 radio unit (RU).

[0022] This application provides multiple forms of the second functional entity to be applicable to any possible form, so as to adjust the QoS parameters of the service to meet the QoS requirements of the service and improve the user experience.

[0023] In one possible design, the method further includes sending second information, where the second information is used to indicate the first QoS parameter.

[0024] The present application indicates a first QoS parameter to a second functional entity through a first functional entity, so that the second functional entity can configure communication resources that meet corresponding QoS requirements according to the first QoS parameter.

[0025] In one possible design, the second information is the first QoS parameter, or the second information is information used to indicate a target function segmentation method. The alternative function segmentation method includes the target function segmentation method, and the alternative function segmentation method is a segmentation method for communication functions of two different types of second function entities with communication connections.

[0026] The present application provides multiple ways of indicating the first QoS parameter to the second functional entity, so that the first functional entity can flexibly select an appropriate way to indicate the first QoS parameter to the second functional entity according to actual conditions.

[0027] In one possible design, the second information is information used to represent the target policy, and the method also includes: sending at least one alternative function splitting method and a first QoS parameter corresponding to the alternative function splitting method.

[0028] The present application configures the first corresponding relationship for the second functional entity in advance so that the first functional entity indirectly indicates the first QoS parameter to the second functional entity through the target policy, thereby reducing the resource consumption of sending the second information.

[0029] In one possible design, the method further includes determining a target policy based on one or more of first information corresponding to the first interface, fourth information, and third information corresponding to the second functional entity, wherein the third information is used to indicate a processing resource state corresponding to the second functional entity, and the fourth information is used to indicate a second QoS parameter corresponding to at least one service.

[0030] This application comprehensively determines the target policy based on the network communication status of the communication interface, the processing resource status of the functional entity, and the QoS requirements of the service. While using the target policy to allocate communication functions to different functional entities, the QoS parameters of the service can be adjusted to meet the QoS requirements of the service and improve the user experience.

[0031] In one possible design, the two different types of second functional entities corresponding to the first interface include a first target entity and a second target entity. The method further includes: obtaining first information from the second functional entity. The first information includes at least one of the following parameters: bandwidth resources of the first interface; transmission delay of the first interface; packet loss rate of the first interface; reliability of the first interface; internal processing delay of the first target entity; or internal processing delay of the second target entity.

[0032] The present application provides a variety of possible parameters included in the first information, so that the first functional entity can determine an appropriate first QoS parameter according to one or more parameters in the first information.

[0033] In one possible design, the method further includes: obtaining third information from the second functional entity, wherein the third information includes at least one of the following parameters: processor utilization; memory utilization; or disk utilization.

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

[0035] In one possible design, the method further includes obtaining fourth information from the second functional entity and / or the core network device. The fourth information includes at least one of the following parameters: a packet delay budget (PDB); a guaranteed bit rate (GBR); or a packet error rate (PER).

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

[0037] In a second aspect, a communication method is provided, which is applied to a third functional entity side, such as a third functional entity or a component in the third functional entity (such as a circuit or chip or chip system). The method may include: receiving a new second QoS parameter from the first functional entity. The new second QoS parameter is obtained based on the first QoS parameter and the second QoS parameter. The first QoS parameter is used to indicate the QoS requirement corresponding to the communication link between two different types of second functional entities with communication connections, and the second QoS parameter is used to indicate the QoS requirement of the service. A first operation is performed based on the new second QoS parameter. The first operation includes any one of the following: establishing a wireless data bearer; or sending a new second QoS parameter.

[0038] This application obtains new QoS parameters by adjusting the QoS parameters of the service, so that after establishing DRB based on the new QoS parameters, the QoS requirements of the service can be met and the user experience can be improved.

[0039] In one possible design, the third functional entity is a centralized unit CU, which receives new second QoS parameters from the first functional entity, including: receiving new second QoS parameters sent by the first functional entity; or receiving new second QoS parameters forwarded by the core network element.

[0040] In one possible design, performing the first operation based on the new second QoS parameter includes establishing a wireless data bearer based on the new second QoS parameter.

[0041] In a possible design, the third functional entity is a core network element, and receiving the new second QoS parameter from the first functional entity includes: receiving the new second QoS parameter sent by the first functional entity.

[0042] In one possible design, performing the first operation based on the new second QoS parameter includes sending the new second QoS parameter.

[0043] In one possible design, the first QoS parameter is obtained by at least one of the following methods: based on the first correspondence and the target policy, determining the first QoS parameter corresponding to the target policy. The first correspondence represents the association between the first QoS parameter and the alternative function splitting method, the alternative function splitting method is a method for splitting the communication function of two different types of second functional entities with communication connections, the alternative function splitting method includes a target function splitting method, and the target function splitting method has an association with the target policy. Alternatively, the first QoS parameter is obtained based on the first information. The first information is used to indicate the network communication status corresponding to the first interface, and the first interface is a communication interface between two different types of second functional entities with communication connections.

[0044] In one possible design, the first functional entity is integrated into the second functional entity.

[0045] In a possible design, the first functional entity and the second functional entity are independent functional entities.

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

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

[0048] In one possible design, the second functional entity and the third functional entity are the same functional entity.

[0049] In a third aspect, a communication method is provided, which is applied to a second functional entity side, such as a second functional entity or a component in the second functional entity (such as a circuit or a chip or a chip system), and the method may include: receiving second information. The second information is used to indicate a first QoS parameter, and the first QoS parameter is used to indicate the QoS requirement corresponding to the communication link between two different types of second functional entities with communication connections. The communication resources of the second functional entity are configured according to the first QoS parameter. The service transmitted on the communication resource corresponds to the second QoS parameter, and the first QoS parameter is also used to obtain a new second QoS parameter by combining the first functional entity with the second QoS parameter.

[0050] This application can enable the second functional entity to configure its own communication resources according to the first QoS parameter, thereby ensuring the QoS requirements of the service and improving user experience.

[0051] In a fourth aspect, a communication system is provided, comprising a first functional entity, a third functional entity, and a core network element, wherein the first functional entity is configured to obtain a first QoS parameter. The first QoS parameter is used to indicate the QoS requirement corresponding to the communication link between two second functional entities of different types having a communication connection. The core network element is configured to send a second QoS parameter to the first functional entity. The second QoS parameter is used to indicate the QoS requirement of the service. The first functional entity is further configured to obtain a new second QoS parameter based on the first QoS parameter and the second QoS parameter. The first functional entity is integrated into the third functional entity, and the third functional entity is configured to perform a first operation based on the new second QoS parameter; or the first functional entity and the third functional entity are deployed independently, and the first functional entity is further configured to send the new second QoS parameter to the third functional entity. The third functional entity is further configured to perform the first operation based on the new second QoS parameter. The first operation includes any one of the following: establishing a wireless data bearer; or sending a new second QoS parameter.

[0052] This application obtains new QoS parameters by adjusting the QoS parameters of the service, so that after establishing DRB based on the new QoS parameters, the QoS requirements of the service can be met and the user experience can be improved.

[0053] In one possible design, the first functional entity is further used to determine the first QoS parameter corresponding to the target policy based on the first correspondence and the target policy. The first correspondence represents the association between the first QoS parameter and the alternative function splitting method, the alternative function splitting method is a method for splitting the communication function of two different types of second functional entities with communication connections, the alternative function splitting method includes a target function splitting method, and the target function splitting method has an association with the target policy. Alternatively, the first functional entity is further used to obtain the first QoS parameter based on the first information. The first information is used to indicate the network communication status corresponding to the first interface, and the first interface is a communication interface between two different types of second functional entities with communication connections.

[0054] In one possible design, the first functional entity is integrated into the second functional entity.

[0055] In a possible design, the first functional entity is integrated in a centralized unit CU, and the first functional entity is further used to initiate a wireless data bearer establishment process based on the new second QoS parameter.

[0056] In one possible design, the first functional entity and the second functional entity are independent functional entities.

[0057] In one possible design, the first functional entity is independent of the CU, and the first functional entity is also used to send the new second QoS parameter to the CU or the core network functional network element.

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

[0059] In one 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.

[0060] In one possible design, the system further includes a second functional entity, wherein the first functional entity is further configured to send second information to the second functional entity. The second information is configured to indicate the first QoS parameter. The second functional entity is configured to configure communication resources of the second functional entity based on the first QoS parameter.

[0061] In one possible design, the second information is the first QoS parameter, or the second information is information used to indicate a target function splitting method. The alternative function splitting method includes the target function splitting method, and the alternative function splitting method is a method for splitting the communication functions of two different types of second function entities with communication connections.

[0062] In one possible design, the second information is information used to represent the target policy, and the first functional entity is also used to send at least one of the alternative function splitting methods and the first QoS parameter corresponding to the alternative function splitting method to the second functional entity.

[0063] In one possible design, the first functional entity is further configured to determine the target policy based on one or more of the first information and fourth information corresponding to the first interface and third information corresponding to the second functional entity, wherein the third information is configured to indicate a processing resource state corresponding to the second functional entity, and the fourth information is configured to indicate a second QoS parameter corresponding to at least one service.

[0064] In one possible design, the two different types of second functional entities corresponding to the first interface include a first target entity and a second target entity. The first functional entity is further configured to obtain the first information from the second functional entity. The first information includes at least one of the following parameters: bandwidth resources of the first interface; transmission delay of the first interface; packet loss rate of the first interface; reliability of the first interface; internal processing delay of the first target entity; or internal processing delay of the second target entity.

[0065] In one possible design, the first functional entity is further configured to obtain the third information from the second functional entity, wherein the third information includes at least one of the following parameters: processor utilization; memory utilization; or disk utilization.

[0066] In one possible design, the first functional entity is further configured to obtain the fourth information from the second functional entity and / or the core network device, wherein the fourth information includes at least one of the following parameters: PDB; GBR; or PER.

[0067] In a fifth aspect, a communication device is provided. The communication device is used to implement the various communication methods involved in the first, second, and / or third aspects above. The communication device includes modules, units, or means corresponding to the above 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 functions.

[0068] In a sixth 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.

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

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

[0071] In a seventh 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.

[0072] In an eighth 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.

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

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

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

[0076] In a tenth 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.

[0077] In an eleventh aspect, a computer program product is provided, which includes a computer program or instructions, and when the computer program or instructions are run on a computer, the computer is caused to execute the communication method as designed in any of the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0081] FIG4 is a schematic diagram of latency and bandwidth requirements for different slicing methods provided in an embodiment of the present application;

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

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

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

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

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

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

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

[0089] FIG12 is a schematic diagram showing the connection between the first functional entity and the second functional entity provided in an embodiment of the present application;

[0090] FIG13 is a schematic diagram of a network structure of another first functional entity provided in an embodiment of the present application;

[0091] FIG14 is a schematic diagram of a network structure of another first functional entity provided in an embodiment of the present application;

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

[0093] FIG16 is a schematic diagram of a network structure of another first functional entity provided in an embodiment of the present application;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0120] 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."

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

[0122] For 4G base stations, they can be divided into two parts: the BBU and the RRU. The BBU is connected to one or more RRUs via optical fiber, metal wiring, or microwave links. The BBU mainly performs upper-layer centralized processing of baseband signals. The RRU mainly performs functions such as reception and transmission of baseband signals, as well as modulation and demodulation, data processing, and power amplification of radio frequency signals. The RRU is closer to the antenna, and the feeder loss is smaller. In some cases, the RRU can also be called a radio unit (RU). In this case, the BBU can process baseband signals in a highly centralized manner, so computing resources can 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, and the fiber deployment cost is high.

[0123] 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).

[0124] 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 (5G core network, 5GC) may communicate through a next generation (NG) interface, and different gNBs may communicate through an Xn interface, for example, through an Xn-control (C) interface. The CU and different DUs may communicate through an F1 interface.

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

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

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

[0128] At present, during the network deployment phase, a fixed radio access network (RAN) functional split can be set to deploy CU and DU based on prior statistical information, such as network peak rate and average data rate requirements. Obviously, the functional division based only on fixed or static access network equipment cannot adapt to real-time changes in service traffic. Of course, Figure 3 only shows one possible functional division method. For other fixed division methods, insufficient computing resource utilization and insufficient bandwidth resource utilization will occur. As shown in Figure 4, for example, under the conditions of a channel bandwidth of 100 MHz, a modulation method of 256 quadrature amplitude modulation (QAM), and multiple-input multiple-output (MIMO) for uplink and downlink, different functional division methods have requirements for uplink and downlink transmission bandwidth and transmission delay. Among them, the MIMO condition can be, for example, 8 MIMO layers. It can be understood from Figure 4 that the closer the division method is to the lower-layer division, the higher the demand for link bandwidth capacity, and the corresponding fiber deployment cost will also be higher. The closer the partitioning method is to the upper layer, the more decentralized the processing functions involved in the functional entities at the lower layer will be, which will relatively increase energy consumption and the overall computing resource deployment cost. Of course, no matter which fixed partitioning method is used, there will be insufficient computing resource utilization and bandwidth utilization due to real-time changes in traffic services. In other words, different services have different QoS requirements such as network latency, rate, and reliability. Static partitioning methods cannot dynamically adapt to the diverse QoS requirements of services.

[0129] In a 5G communication scenario, a communication channel can be provided for data transmission between a terminal and an application server located in a data network by establishing a protocol data unit (PDU) session establishment process. For example, establishing a PDU session can include: establishing a data radio bearer (DRB) between the terminal and the RAN, and establishing a next generation interface user plane channel (NG-U Tunnel) between the RAN and the user plane function (UPF) of the core network, and providing corresponding QoS guarantees. Referring to Figure 5, a PDU session channel is established between the terminal 210, the access network device 220, and the core network element 230, which may include a DRB between the terminal 210 and the access network device 220, and a next generation (NG) channel between the access network device 220 and the core network element 230. The NG channel may be the NG-U Tunnel mentioned above. The core network element 230 may be, for example, a UPF. The core network element 230 can establish a communication connection with the cloud server 240 to schedule functions in the cloud server 240. The access network device 220 can establish a DRB with the terminal 210 based on the QoS requirements of the service issued by the core network. For example, the access network device obtains the QoS requirements issued by the core network element 230 through the NG channel. The access network device 220 can map the QoS flow of the service to the corresponding DRB for transmission to meet the QoS requirements corresponding to the QoS flow, such as transmission delay, bit rate, and other requirements.

[0130] It can be understood that the terminal 210 is similar to the terminal 110 , and the access network device 220 and the core network element 230 may belong to the network device 120 .

[0131] However, during the PDU session establishment process, the access network device establishes a DRB based on the QoS configuration issued by the core network. This DRB is used to ensure that the air interface transmission between the terminal and the access network device meets the QoS requirements. However, this QoS does not take into account the QoS impact that may exist within the access network device. For example, if the access network device is divided into CU, DU, and / or RU, then the QoS of the entire PDU session cannot be guaranteed for the mid-transmission link between the CU and DU, and / or the front-transmission link between the DU and RU.

[0132] Therefore, the present application provides a communication method, which obtains new QoS parameters by adjusting the QoS parameters of the service, so that after establishing DRB based on the new QoS parameters, the QoS requirements of the service can be met and the user experience can be improved.

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

[0134] As shown in Figure 6, the access network equipment can be further divided into multiple functional entities, such as RU 320, DU 330, and CU 340. Of course, the access network equipment may include one or more RU 320, one or more DU 330, and one or more CU 340. The CU 340 is connected to the 5GC 350 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.

[0135] The 5GC 350 can be connected to multiple CUs 340, a CU 340 can be connected to multiple DUs 330, and a DU 330 can be connected to multiple RUs 320. A terminal 310 can access the network through any RU 320. There can be one or more terminals 310. It is understood that the terminal 310 is similar to the terminal 110 and will not be described in detail in this embodiment of the present application.

[0136] In some examples, the access network device may be a gNB. The protocol function entities of the access network device may include a CU 340 and a DU 330. The access network device provides new radio (NR) user and control plane protocol endpoints to the terminal and communicates with the 5GC 350 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.

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

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

[0139] In some examples, 5GC 350 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.

[0140] In some examples, the RU 320, DU 330, and CU 340 can be deployed on the same physical device or on different physical devices. Alternatively, some functional entities in the RU 320, DU 330, and CU 340 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.

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

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

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

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

[0145] S101: A first functional entity obtains a first QoS parameter and a second QoS parameter.

[0146] In some examples, the first functional entity may be considered as a functional entity for adjusting QoS parameters.

[0147] In some embodiments, the first functional entity may obtain the first information from the second functional entity and determine the first QoS parameter based on the first information. This approach may be referred to as approach A. Alternatively, the first functional entity may determine the first QoS parameter based on a corresponding configuration. This approach may be referred to as approach B. The first QoS parameter may be used to indicate the QoS requirement corresponding to a communication link between two second functional entities of different types having a communication connection.

[0148] In some embodiments, the first functional entity may obtain a second QoS parameter sent by a core network element. The second QoS parameter is used to indicate a QoS requirement of the service.

[0149] In the embodiments of the present application, there is no limitation on the specific implementation method of obtaining the first QoS parameter and the second QoS parameter. In other embodiments, the above QoS parameters can also be obtained from other network elements.

[0150] In some embodiments, the second functional entity may be a functional entity in the RAN, core network, or network management domain.

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

[0152] The embodiment of the present application can adjust the QoS parameters of the service when the second functional entity includes different communication functions, thereby improving universality.

[0153] In some embodiments, in the case where the second functional entity is a functional entity in the RAN, the second functional entity may include at least one functional entity of a CU, a DU, and a RU.

[0154] In some examples, two different types of second functional entities with a communication connection may include a first target entity and a second target entity. For example, the first target entity may be a CU and the second target entity may be a DU; or, the first target entity may be a DU and the second target entity may be an RU. For another example, the first target entity may be a DU and the second target entity may be a CU; or, the first target entity may be a RU and the second target entity may be a DU. For another example, the first target entity may be a functional entity with CU and DU functions and the second target entity may be an RU; or, the first target entity may be a CU and the second target entity may be a functional entity with DU and RU functions. Of course, the above are only some possible examples, and the embodiments of the present application are not limited here.

[0155] The embodiments of the present application provide multiple forms of the second functional entity to be applicable to any possible form, so as to adjust the QoS parameters of the service to meet the QoS requirements of the service and improve the user experience.

[0156] The following describes the above-mentioned method A and method B for obtaining the first QoS parameter:

[0157] Method A:

[0158] In some embodiments, the first functional entity may receive first information corresponding to a first interface sent by the second functional entity to obtain a first QoS parameter, wherein the first information is used to indicate a network communication state corresponding to the first interface, where the first interface is a communication interface between two different types of second functional entities having a communication connection.

[0159] In some examples, the first information may include bandwidth resources of the first interface.

[0160] In some examples, the first information may include a transmission delay of the first interface.

[0161] In some examples, the first information may include a packet loss rate of the first interface.

[0162] In some examples, the first information may include reliability of the first interface.

[0163] In some examples, the first information may include an internal processing delay of the first target entity.

[0164] For example, if the first target entity is a CU and the second target entity is a DU, the CU obtains the CU's internal processing delay and sends the CU's internal processing delay to the first functional entity in the first information corresponding to the first interface. For another example, the CU obtains the CU's internal processing delay and sends the CU's internal processing delay to the DU. The DU then sends the first information corresponding to the first interface to the first functional entity, carrying the CU's internal processing delay.

[0165] In some examples, the first information may include an internal processing delay of the second target entity.

[0166] For example, if the first target entity is a CU and the second target entity is a DU, the DU obtains the internal processing delay of the DU and sends it to the first functional entity along with the first information corresponding to the first interface. For another example, the DU obtains the internal processing delay of the DU and sends it to the CU. The first information corresponding to the first interface sent by the CU to the first functional entity also carries the internal processing delay of the DU.

[0167] In some examples, the first information may include the bandwidth resources of the first interface, and the transmission delay of the first interface. In some examples, the first information may include the bandwidth resources of the first interface, the transmission delay of the first interface, and the reliability of the first interface. In some examples, the first information may include the bandwidth resources of the first interface, the transmission delay of the first interface, the packet loss rate of the first interface, and the reliability of the first interface. In some examples, the first information may include the bandwidth resources of the first interface, the transmission delay of the first interface, the packet loss rate of the first interface, the reliability of the first interface, and the internal processing delay of the first target entity. In some examples, the first information may include the bandwidth resources of the first interface, the transmission delay of the first interface, the packet loss rate of the first interface, the reliability of the first interface, the internal processing delay of the first target entity, and the internal processing delay of the second target entity.

[0168] It can be understood that the above only shows a limited number of examples, and the first information can also include any other two, three, four or five items, which are not limited in the embodiments of the present application.

[0169] In other examples, the first information may also include any other parameters related to the network communication status. That is, the first information may include, but is not limited to, one or more of the above information, and this embodiment of the application does not limit this.

[0170] For example, the first functional entity may determine the QoS parameters of the first interface between the current first target entity and the second target entity according to any one or more parameters in the above-mentioned first information.

[0171] For example, the first functional entity may determine the packet delay budget (PDB) corresponding to the first interface based on the transmission delay of the first interface. For another example, the first functional entity may determine the transmission and processing delays corresponding to the first interface based on the transmission delay of the first interface and the internal processing delay of the first target entity. The transmission and processing delays corresponding to the first interface may be collectively referred to as the delay of the first interface. For another example, the first functional entity may determine the packet error rate (PER) corresponding to the first interface based on the packet loss rate of the first interface.

[0172] In some examples, the first QoS parameter may be a parameter directly in the first information.

[0173] The embodiment of the present application provides a variety of possible parameters included in the first information, so that the first functional entity can determine an appropriate first QoS parameter according to one or more parameters in the first information.

[0174] It can be understood that the first functional entity can obtain various status information of the first interface more timely by adopting method A, so that the first functional entity can determine more reasonable first QoS parameters according to the status information.

[0175] Method B:

[0176] In other embodiments, the first functional entity determines the first QoS parameter based on the corresponding configuration. For example, the first functional entity may determine the first QoS parameter corresponding to the target policy based on the first correspondence and the target policy. The first correspondence represents an association between the first QoS parameter and an alternative function segmentation method, wherein the alternative function segmentation method is a method for segmenting the communication function of two different types of second functional entities with a communication connection, the alternative function segmentation method includes a target function segmentation method, and the target function segmentation method has an association with the target policy.

[0177] In some examples, the first functional entity may also be a functional entity that determines one or more target policies, i.e., a functional entity that is used to flexibly divide communication functions between different target entities. For example, the first functional entity may 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.

[0178] For example, the first functional entity may determine a target policy. The target policy is used to indicate how the communication functions of the first target entity and the second target entity are divided. In some examples, the first functional entity may determine a target policy corresponding to any QoS flow for different QoS flows. In other words, the first functional entity may determine a target policy corresponding to each possible QoS flow based on the granularity of the QoS flow.

[0179] In some examples, reference is made to FIG8 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 option 1 to option 8 are provided. Among them, option 1 can be the communication function division between RRC and PDCP shown in FIG8, or option 1 can be the communication function division between SDAP and PDCP shown in FIG8. 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 by SDAP, and the embodiments of this application will not be repeated.

[0180] Option 2 may be the division of communication functions between the PDCP and RLC upper layers, as shown in FIG8 . Option 3 may be the division of communication functions between the RLC upper layer and the RLC lower layer, as shown in FIG8 . Therefore, Option 3 can 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 FIG8 . Option 5 may be the division of communication functions between the MAC upper layer and the MAC lower layer, as shown in FIG8 . Therefore, Option 5 can 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 FIG8 . Option 7 may be the division of communication functions between the PHY upper layer and the PHY lower layer, as shown in FIG8 . Therefore, Option 7 can 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 FIG8 .

[0181] For example, taking the first target entity as CU and the second target entity as DU, for option 2, CU can be used to implement the functions of PDCP and PDCP upper layers (such as RRC), and DU can be used to implement the functions of RLC and lower layers.

[0182] 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 high and low layers. 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 9, the communication functions within PHY are divided for downlink communication. Assume that the internal 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.

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

[0184] Referring to Figure 10, 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, for the splitting method of Option 7, it can also include Option 7-1', Option 7-2', Option 7-2x' and Option 7-3' and other methods. Among them, demodulation can also be called demodulation.

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

[0186] Of course, the segmentation method within MAC and RLC can refer to the segmentation method within PHY. 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.

[0187] It can be understood that any one of the multiple options shown in Figures 8 to 10 can be considered as an alternative function segmentation method. One or more of the above options constitute one or more alternative function segmentation methods. The first functional entity can select an option from one or more alternative function segmentation methods as the target function segmentation method. Among them, the target function segmentation method can be used to obtain a target strategy. It can be considered that the target strategy includes a target function segmentation method that indicates how to perform function segmentation, and the communication functions corresponding to the first target entity and the second target entity corresponding to the target strategy.

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

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

[0190] 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, they may also include the core network's mobility management function, user plane function, identity management function, etc., which are not limited in this embodiment of the present application. For example, functions such as the AMF and UPF of the core network may be divided into the communication functions corresponding to the first target entity. For another example, the OAM functions of the network management domain may be divided into the communication functions corresponding to the first target entity.

[0191] It can be understood that the first functional entity can determine the target policies corresponding to the first target entity and the second target entity to configure the communication functions corresponding to the first target entity and the second target entity respectively.

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

[0193] Based on the various alternative functional segmentation methods provided in Figures 8 to 10, the embodiments of the present application also provide various target strategies to indicate the various divisions of communication functions of different functional entities. Assume that the first target entity is a CU and the second target entity is a DU. Alternatively, assume that the first target entity is a DU and the second target entity is a RU.

[0194] Case 1:

[0195] For example, the communication functions of the CU include RRC; the communication functions of the DU include PDCP, RLC, MAC, the upper physical layer (high physical layer, HIGH PHY), and the lower physical layer (low physical layer, LOW PHY). For another example, the communication functions of the DU include PDCP, RLC, MAC, and high physical layer; the communication functions of the RU include low physical layer.

[0196] Case 2:

[0197] For example, the communication functions of a CU include RRC and PDCP; the communication functions of a DU include RLC, MAC, High PHY, and Low PHY. For another example, the communication functions of a DU include RLC, MAC, and High PHY, while the communication functions of a RU include Low PHY.

[0198] Case 3:

[0199] For example, the communication functions of a CU include RRC, PDCP, and RLC; the communication functions of a DU include MAC, High PHY, and Low PHY. For another example, the communication functions of a DU include MAC and High PHY; the communication functions of a RU include Low PHY.

[0200] Case 4:

[0201] In some embodiments, the communication functions of the CU include RRC, PDCP, RLC, and MAC; the communication functions of the DU include HIGH PHY and LOW PHY. For another example, the communication functions of the DU include HIGH PHY; the communication functions of the RU include LOW PHY.

[0202] Case 5:

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

[0204] 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 9 and 10. 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.

[0205] The embodiments of the present application provide a division method for multiple functional entities corresponding to communication functions, which can be adapted to the QoS requirements of different services.

[0206] In some examples, any of the above-mentioned alternative function splitting methods may correspond to one or more first QoS parameters. For example, the alternative function splitting method may correspond to a first QoS parameter, which is used to represent the QoS parameter corresponding to the first interface between the first target entity and the second target entity. Different alternative function splitting methods may correspond to their respective first QoS parameters. The correspondence between the alternative function splitting method and the corresponding first QoS parameter may be referred to as a first correspondence. At the same time, the alternative function splitting method may include a target splitting method, which may be used to obtain a target policy. Therefore, based on the target policy and the first correspondence, the first QoS parameter corresponding to the target policy may be obtained.

[0207] When the first functional entity adopts method B, the first QoS parameter can be determined more quickly according to the first corresponding relationship and the target policy, thereby reducing processing delay and improving execution efficiency.

[0208] The embodiments of the present application provide multiple ways to determine the first QoS parameter, so that the first functional entity can determine the first QoS parameter in an appropriate way according to different requirements, thereby improving universality.

[0209] In some embodiments, the first functional entity may receive fourth information sent by a core network element. In other embodiments, the first functional entity may receive fourth information forwarded by a second functional entity. The fourth information may be sent by the core network element to the second functional entity and forwarded by the second functional entity to the first functional entity. The fourth information may indicate a second QoS parameter corresponding to at least one service.

[0210] In some embodiments, the fourth information may include a PDB.

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

[0212] In some embodiments, the fourth information may include PER.

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

[0214] In other examples, the fourth information may also include any other parameters related to QoS, such as possible new QoS parameters in the future, which are not limited in the embodiments of the present application.

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

[0216] Of course, the first QoS parameter may also include any one or more of the above parameters, which will not be described in detail in this application.

[0217] S102: The first functional entity obtains a new second QoS parameter according to the first QoS parameter and the second QoS parameter.

[0218] In some embodiments, the first functional entity may adjust the second QoS parameter according to the first QoS parameter acquired in S101 to obtain a new second QoS parameter.

[0219] For example, assuming that the QoS parameter is a PDB, and the second QoS parameter is the first PDB, and the first QoS parameter of the first interface between the CU and DU is the second PDB, the first functional entity can subtract the second PDB from the first PDB to obtain a third PDB. This third PDB can be considered the new second QoS parameter.

[0220] For another example, assuming the QoS parameter is a PDB, assuming the second QoS parameter is the first PDB, the first QoS parameter of the first interface between the CU and DU is the second PDB, and the first QoS parameter of the first interface between the DU and RU is the fourth PDB. The first functional entity then subtracts the second PDB from the first PDB, and then subtracts the fourth PDB to obtain the fifth PDB. This fifth PDB can be considered the new second QoS parameter.

[0221] For another example, let's assume that the QoS parameter is transmission delay. Assuming the second QoS parameter is the first delay, the first QoS parameter for the first interface between the DU and the RU includes the second delay and the third delay. The second delay can be the transmission delay of the first interface, and the third delay can be the processing delay of the first interface, such as the internal processing delay of the RU. The first functional entity then subtracts the second delay from the first delay, and then subtracts the third delay, to obtain the fourth delay. This fourth delay can be considered the new second QoS parameter.

[0222] In some examples, if the QoS parameter is GBR, the first functional entity may use the minimum QoS parameter between the first QoS parameter and the second QoS parameter as the new second QoS parameter.

[0223] In other examples, if the QoS parameter is PER, the first functional entity can obtain a new second QoS parameter based on the first QoS parameter, the second QoS parameter, and a corresponding algorithm. Of course, the algorithm can adopt any algorithm for calculating PER based on actual conditions. For details, please refer to relevant technologies and this embodiment of the present application is not limited here.

[0224] S103: The first functional entity sends a new second QoS parameter to the third functional entity.

[0225] In some embodiments, the first functional entity may send the second QoS parameter obtained in S102 to the third functional entity.

[0226] In some examples, the first functional entity and the second functional entity may be independent functional entities. As shown in FIG11 , the first functional entity and the second functional entity may be independent and distinct functional entities. The first functional entity may have a communication connection with the second functional entity. The first functional entity may be deployed on the RAN side, the core network side, or the network management domain side.

[0227] For example, if a first functional entity is located on the RAN side, the communication connection between the first functional entity and any second functional entity can be based on a newly defined interface. In this example, the newly defined interface is used to implement communication between the first functional entity and the second functional entity. For example, if the second functional entity is a functional entity within the RAN, the newly defined interface is used to implement communication within the RAN.

[0228] For another example, if a first functional entity is located on the core network side, the communication connection between the first functional entity and any second functional entity can be based on a newly defined interface. Alternatively, the communication connection between the first functional entity and any second functional entity can partially reuse the interface between the core network and the RAN. Referring to Figure 12 , assuming the core network elements also include an AMF, a task management function (TMF), a policy control function (PCF), an SMF, a UPF, and a network exposure function (NEF), etc. Assuming the second functional entity communicates with the AMF on the RAN side via the N2 interface, the first functional entity can reuse the N2 interface. For example, the first functional entity communicates with the second functional entity via a newly defined service-based interface with the AMF and the N2 interface. The newly defined service-based interface in this example can be used to enable communication between the first functional entity and the AMF. Of course, if the second functional entity has communication connections with other core network elements, the newly defined service-based interface can also include communication between the first functional entity and the core network elements that have communication connections with the second functional entity.

[0229] For another example, if a first functional entity is located in the network management domain, the communication connection between the first functional entity and any second functional entity can be based on a newly defined interface. In this example, the newly defined interface is used to implement communication between the functional entity in the network management domain and the second functional entity. For example, if the second functional entity is a functional entity in the RAN, the newly defined interface is used to implement communication between the functional entity in the network management domain and the RAN.

[0230] The embodiments of the present application can be applied to scenarios where the first functional entity and the second functional entity are independent of each other, so that the QoS parameters of the service can be adjusted in this scenario, and a DRB can be established based on the new QoS parameters to meet the QoS requirements of the service and improve user experience.

[0231] In other examples, as shown in Figure 13, the first functional entity may be integrated into the second functional entity. In other words, the first functional entity may be integrated into one or more second functional entities.

[0232] 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 first functional entity can be integrated into the CU, DU, and / or RU. For another example, the first 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.

[0233] 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 first functional entity can be integrated into the AMF.

[0234] 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 first functional entity can be integrated into the OAM.

[0235] In some examples, the first functional entity may be deployed on multiple second functional entities at the same time. For example, the first functional entity may be deployed in a CU or a DU; or the first functional entity may be deployed in a DU or a RU.

[0236] The embodiments of the present application can be applied to the scenario where the first functional entity is integrated on the second functional entity, so that the QoS parameters of the service can be adjusted in this scenario, and a DRB can be established based on the new QoS parameters to meet the QoS requirements of the service and improve the user experience.

[0237] Of course, Figures 11 to 13 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.

[0238] In some embodiments, referring to the scenarios of Figures 11 to 13 above, for the case where the first functional entity and the CU are independent of each other. For example, the first functional entity and the second functional entity are independent of each other, and the CU is a possible second functional entity. For another example, the first functional entity is integrated on the DU and / or RU, and the second functional entity may include the CU, DU, and RU. The first functional entity may also send new second QoS parameters to the third functional entity. The third functional entity can be considered as a functional entity that receives the new second QoS parameters sent by the first functional entity.

[0239] The third functional entity may be a CU, or a network element with core network functions. The network element with core network functions may be the core network element or core network device mentioned in the above embodiments. It is understood that when the third functional entity is a CU, the CU can be considered as either a second functional entity or a third functional entity.

[0240] In some examples, it is considered that the establishment of the DRB with the terminal is actually implemented through the CU in the access network device. Therefore, if the first functional entity and the CU are independent of each other, if the first functional entity and the CU have a communication connection, the first functional entity can directly send the new second QoS parameters to the CU. In other examples, if there is a communication connection between the first functional entity and the core network network element, there is no direct communication connection between the first functional entity and the CU, and there is a communication connection between the CU and the core network network element. In this case, the first functional entity can send the new second QoS parameters to the core network network element, and forward the new second QoS parameters to the CU through the core network network element.

[0241] For the CU, a DRB establishment process may be initiated based on the new second QoS parameters.

[0242] The embodiment of the present application is applicable to the scenario where the first functional entity and the CU are independent of each other, so that in this scenario the CU can establish a DRB based on new QoS parameters to meet the QoS requirements of the service, thereby improving the user experience.

[0243] In some embodiments, referring to the scenarios of FIG. 11 to FIG. 13 , in a scenario where the first functional entity is integrated into a CU, the first functional entity may inform the CU of the new second QoS parameters through data interaction within the CU, so that the CU can initiate a radio data bearer establishment process based on the new second QoS parameters.

[0244] In some examples, the CU may send a message to the terminal carrying a DRB establishment request. The message may include configuration information for air interface transmission. Such configuration information for air interface transmission may be associated with the new second QoS parameter. For example, the time-frequency resources configured based on the configuration information are used to ensure that the QoS requirements corresponding to the new second QoS parameter are met.

[0245] In some examples, the configuration information for air interface transmission may be used to configure any one or more layers from RRC to PHY as shown in FIG. 8 to FIG. 10 .

[0246] It is understandable that, in a scenario where the first functional entity is integrated into the CU, S103 may not be executed.

[0247] The embodiment of the present application is applicable to the scenario where the first functional entity is integrated into the CU. In this scenario, the CU can establish a DRB based on new QoS parameters to meet the QoS requirements of the service, thereby improving the user experience.

[0248] Referring to the solution shown in Figure 7, if the CU establishes a DRB based on the second QoS parameter, in this case, although the air interface between the terminal and the access network device meets the QoS requirements, there will be certain QoS impacts inside the access network device. Therefore, the QoS of the communication link for the entire service cannot meet the QoS requirements corresponding to the second QoS parameter. Therefore, the embodiment of the present application can use the first QoS parameter to adjust the second QoS parameter to obtain a new second QoS parameter. The CU can establish a DRB based on the new second QoS parameter, so that the QoS of the communication link for the entire service can meet the QoS requirements corresponding to the second QoS parameter. Thereby improving the user experience.

[0249] In the communication method provided in the embodiment of the present application, the first functional entity may send second information, where the second information is used to indicate the first QoS parameter.

[0250] In some embodiments, when the first functional entity determines the first QoS parameter based on the first correspondence and the target policy, the first functional entity may further send second information to the second functional entity. This second information may indicate the first QoS parameter determined by the first functional entity, allowing the second functional entity to configure transmission resources based on the first QoS parameter indicated by the received second information. The transmission resources configured based on the first QoS parameter meet the QoS requirements corresponding to the first QoS parameter, such as latency requirements and packet error rate requirements.

[0251] In some examples, the second information is a first QoS parameter. That is, the first functional entity directly sends the first QoS parameter to the second functional entity.

[0252] In some examples, the second information is information indicating a target function segmentation method. That is, the second information can indicate a target policy, i.e., the first functional entity informs the second functional entity of the target policy. The second functional entity determines, based on the target policy, a first QoS parameter corresponding to the target policy and configures transmission resources based on the first QoS parameter.

[0253] The embodiments of the present application provide multiple ways of indicating the first QoS parameter to the second functional entity, so that the first functional entity can flexibly select an appropriate way to indicate the first QoS parameter to the second functional entity according to actual conditions.

[0254] In some embodiments, when the second information is information for indicating a target policy, the first functional entity may send at least one alternative functional segmentation method and a first QoS parameter corresponding to the alternative functional segmentation method to the second functional entity in advance.

[0255] For example, before sending the second information, the first functional entity may send at least one alternative functional segmentation method and the first QoS parameter corresponding to the alternative functional segmentation method to the second functional entity. The alternative functional segmentation method can refer to the description of the above embodiment, and the embodiments of the present application will not be repeated here. After the second functional entity receives at least one alternative functional segmentation method and the first QoS parameter corresponding to the alternative functional segmentation method, if the second functional entity receives the second information sent by the first functional entity indicating the target policy, the second functional entity can determine its corresponding first QoS parameter according to the target policy, so that the second functional entity can configure the transmission resources based on the first QoS parameter.

[0256] Among them, the alternative function segmentation method and the first QoS parameter corresponding to the alternative function segmentation method are the first corresponding relationship mentioned above.

[0257] In the embodiment of the present application, the first corresponding relationship is pre-configured for the second functional entity so that the first functional entity indirectly indicates the first QoS parameter to the second functional entity through the target policy, thereby reducing the resource consumption of sending the second information.

[0258] It can be understood that in the embodiment of the present application, the first functional entity indicates the first QoS parameter to the second functional entity, so that the second functional entity can configure communication resources that meet the corresponding QoS requirements according to the first QoS parameter.

[0259] In the communication method provided in the embodiments of the present application, for the target policy mentioned in each of the above embodiments, the first functional entity may determine the target policy based on one or more of the first information corresponding to the first interface, the fourth information, and the 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.

[0260] In some embodiments, the first functional entity may determine the target policy based on one or more of the first information corresponding to the first interface, the fourth information, and the third information corresponding to the second functional entity.

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

[0262] Of course, the above only shows a limited number of examples. The first functional entity can also determine the target strategy based on any other one or two parameters, which is not limited in the embodiments of the present application.

[0263] In some examples, such as when 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, such as when the first target entity is a DU and the second target entity is a RU, the first interface may be an interface corresponding to a fronthaul link.

[0264] In some examples, the first functional entity may also obtain third information from the second functional entity.

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

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

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

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

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

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

[0271] It will be appreciated that the embodiments of the present application comprehensively determine target policies based on factors 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. When using target policies to allocate communication functions to different functional entities, QoS parameters for the service can be adjusted to meet the QoS requirements of the service and enhance the user experience.

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

[0273] Example A:

[0274] In some embodiments, referring to the network architecture diagram shown in Figure 14, the first functional entity can be deployed in the CU, and the second functional entity can include the CU, DU, and RU. The CU and DU can communicate via the F1 interface, and the DU and RU can communicate via the F2 interface.

[0275] As shown in FIG15 , an embodiment of the present application further provides a communication method, which is applied to the network architecture shown in FIG14 . The method may include:

[0276] S201: The terminal sends a PDU session establishment request to the core network device.

[0277] In some embodiments, the terminal may send a PDU session establishment request to the core network device.

[0278] In other examples, the PDU session establishment request may also be generated by the core network device itself. In this case, S201 may not be executed.

[0279] In some examples, the PDU session establishment request may also be equivalent to other service requests, such as requests for computing tasks, requests for artificial intelligence (AI) tasks, requests for data services, etc. Furthermore, the present embodiment does not limit the name of the request.

[0280] S202: The core network device sends a PDU session resource establishment request to the CU.

[0281] In some embodiments, a core network device may obtain a second QoS parameter associated with a PDU session based on a PDU session establishment request. The core network device may send a PDU session resource establishment request to the CU. The request may include the second QoS parameter. The second QoS parameter may be QoS flow granular.

[0282] S203: The first functional entity sends the alternative function segmentation mode and the first QoS parameter corresponding to the alternative function segmentation mode to the second functional entity.

[0283] In some embodiments, the first functional entity may send at least one alternative function splitting mode to the second functional entity, and send a first QoS parameter corresponding to each alternative function splitting mode in the at least one alternative function splitting mode.

[0284] S204: The first functional entity determines a target policy according to the first information and the fourth information of the first interface and the third information of the second functional entity.

[0285] S205: The first functional entity sends the target policy to the second functional entity.

[0286] For example, the CU may send the target policy corresponding to the CU and DU, and / or the target policy corresponding to the DU and RU to the DU. For another example, the CU may send the target policy corresponding to the DU and RU to the RU.

[0287] S206: The second functional entity configures communication resources for the second functional entity.

[0288] In some embodiments, the second functional entity may determine the first QoS parameter corresponding to the target policy according to the target policy sent by the second functional entity and the first QoS parameters corresponding to each alternative functional segmentation method. The second functional entity configures communication resources for its own functional entity based on the first QoS parameter.

[0289] For example, the DU can determine the first QoS parameter corresponding to the midhaul link based on the target policy corresponding to the CU and DU. The DU configures the communication resources corresponding to the midhaul link based on the first QoS parameter corresponding to the midhaul link. Similarly, the RU can determine the first QoS parameter corresponding to the fronthaul link. The DU configures the communication resources corresponding to the fronthaul link based on the first QoS parameter corresponding to the fronthaul link.

[0290] It is understood that the purpose of S203 to S206 is to pre-configure the communication resources corresponding to the fronthaul link and the communication resources corresponding to the midhaul link. In some possible examples, the first functional entity may also directly send the first QoS parameter to the second functional entity. In this case, S203 to S205 may not be performed.

[0291] Meanwhile, S203 to S206 are optional steps and may also be performed before S201, which is not limited in the present embodiment.

[0292] S207: The first functional entity obtains a new second QoS parameter according to the first QoS parameter and the second QoS parameter.

[0293] In some examples, the first functional entity may modify the second QoS parameter issued by the core network device based on the first QoS parameter corresponding to the fronthaul link and / or the first QoS parameter corresponding to the midhaul link to obtain a new second QoS parameter. For example, taking the QoS parameter as a PDB, the first functional entity subtracts the PDB of the first QoS parameter corresponding to the fronthaul link and / or the midhaul link from the PDB of the second QoS parameter to obtain the new PDB of the second QoS parameter.

[0294] In some examples, if S203 to S206 are not executed, the first functional entity may determine the first QoS parameter based on the first information of the first interface sent by the second functional entity, and obtain a new second QoS parameter using the first QoS parameter and the second QoS parameter.

[0295] S208: The CU initiates DRB establishment based on the new second QoS parameters.

[0296] It can be understood that after the CU establishes the DRB with the terminal, the CU can map the QoS flow to the DRB.

[0297] It can be understood that the specific implementation process of S201 to S208 can refer to the description of the embodiments in Figures 7 to 13, and the embodiments of the present application will not be repeated here.

[0298] The embodiment described in Example A above enables the first functional entity integrated in the CU to select an appropriate functional segmentation method and ensure the QoS requirements of the corresponding fronthaul and midhaul links. At the same time, session QoS is modified based on the QoS information of the fronthaul and midhaul links, thereby more accurately ensuring the QoS requirements of data transmission between the access network device and the terminal, improving the user experience.

[0299] Example B:

[0300] In some embodiments, referring to the network architecture diagram shown in Figure 16, the first functional entity can be deployed in the DU, and the second functional entity can include the CU, DU, and RU. The CU and DU can communicate via the F1 interface, and the DU and RU can communicate via the F2 interface.

[0301] As shown in FIG17 , an embodiment of the present application further provides a communication method, which is applied to the network architecture shown in FIG16 . The method may include:

[0302] S301: The terminal sends a PDU session establishment request to the core network device.

[0303] S302: The core network device sends a PDU session resource establishment request to the CU.

[0304] The above S301 and S302 are similar to S201 and S202. For details, please refer to the description of the corresponding embodiment in Figure 15. The embodiment of this application will not be repeated here.

[0305] S303: The CU sends a second QoS parameter to the first functional entity.

[0306] In some examples, because the PDU session resource establishment request sent by the core network to the CU carries the second QoS parameter, the CU may send the second QoS parameter to the first functional entity through the F1 interface.

[0307] In some examples, the second QoS parameter may be at a PDU session granularity or a QoS flow granularity.

[0308] S304: The first functional entity obtains a new second QoS parameter according to the first QoS parameter and the second QoS parameter.

[0309] The above S304 is similar to S207. For details, please refer to the description of the corresponding embodiment in Figure 15. The embodiment of this application will not be repeated here.

[0310] In some embodiments, the first functional entity may also send an alternative functional segmentation method and a first QoS parameter corresponding to the alternative functional segmentation method to each second functional entity. The first functional entity may also determine a target policy and send the target policy to the second functional entity. The first functional entity may also send the first QoS parameter to the second functional entity, so that the second functional entity can configure the communication resources of the second functional entity based on the first QoS parameter. Of course, the above-mentioned specific implementation process can be referred to the relevant description of S203 to S206, and the embodiments of this application will not be repeated here.

[0311] S305: The first functional entity sends a new second QoS parameter to the CU.

[0312] It can be understood that since the first functional entity and the CU are independent of each other, the first functional entity sends the new second QoS parameter to the CU so that the CU performs subsequent operations.

[0313] S306: The CU initiates DRB establishment based on the new second QoS parameters.

[0314] The above S306 is similar to S208. For details, please refer to the description of the corresponding embodiment in Figure 15, and the embodiment of this application will not be repeated here.

[0315] It can be understood that the specific implementation process of S301 to S306 can refer to the description of the embodiments in Figures 7 to 13, and the embodiments of the present application will not be repeated here.

[0316] The embodiment described in Example B above enables the first functional entity integrated in the DU to obtain more real-time network status information, select the appropriate functional segmentation method in a more timely manner, and ensure the QoS requirements of the corresponding fronthaul and midhaul links. At the same time, based on the QoS information of the fronthaul and midhaul links, the session QoS is modified, thereby more accurately ensuring the QoS requirements of data transmission between the access network device and the terminal, improving the user experience.

[0317] Example C:

[0318] As shown in FIG18 , an embodiment of the present application further provides a communication method, which is applied to the network architecture shown in FIG11 and FIG12 . The second functional entity may include a CU, a DU, and 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. The method may include:

[0319] S401: The terminal sends a PDU session establishment request to the core network device.

[0320] In some examples, the core network device may be, for example, an SMF.

[0321] S402: The core network device sends a PDU session resource establishment request to the CU.

[0322] The above S301 and S302 are similar to S201 and S202. For details, please refer to the description of the corresponding embodiment in Figure 15. The embodiment of this application will not be repeated here.

[0323] S403: The first functional entity obtains a new second QoS parameter according to the first QoS parameter and the second QoS parameter.

[0324] The above S403 is similar to S207. For details, please refer to the description of the corresponding embodiment in Figure 15. The embodiment of this application will not be repeated here.

[0325] In some embodiments, the first functional entity may also send an alternative functional segmentation method and a first QoS parameter corresponding to the alternative functional segmentation method to each second functional entity. The first functional entity may also determine a target policy and send the target policy to the second functional entity. The first functional entity may also send the first QoS parameter to the second functional entity, so that the second functional entity can configure the communication resources of the second functional entity based on the first QoS parameter. Of course, the above-mentioned specific implementation process can be referred to the relevant description of S203 to S206, and the embodiments of this application will not be repeated here.

[0326] S404: The first functional entity sends a new second QoS parameter to the core network device.

[0327] It can be understood that since the first functional entity and the CU are independent of each other, the first functional entity sends the new second QoS parameter to the core network device so that the new second QoS parameter is forwarded to the CU through the core network device.

[0328] S405: The core network device sends a PDU session resource establishment request to the second functional entity.

[0329] In some examples, the PDU session resource establishment request may carry the new second QoS parameter received by the core network device in S404.

[0330] Of course, in some examples, when the first functional entity has a communication connection with the CU, the first functional entity directly sends the new second QoS parameter to the CU in S404. The PDU session resource establishment request in S405 may also not carry the new second QoS parameter.

[0331] S406: CU initiates DRB establishment based on the new second QoS parameters.

[0332] The above S406 is similar to S208. For details, please refer to the description of the corresponding embodiment in Figure 15, and the embodiment of this application will not be repeated here.

[0333] It can be understood that the specific implementation process of S401 to S406 can refer to the description of the embodiments in Figures 7 to 13, and the embodiments of the present application will not be repeated here.

[0334] In the embodiment described in Example C above, the first functional entity deployed in the core network selects an appropriate functional segmentation method and ensures the corresponding QoS requirements for the fronthaul and midhaul links. Furthermore, the first functional entity modifies the session QoS based on the QoS information for the fronthaul and midhaul links. This more accurately ensures the QoS requirements for data transmission between the access network device and the terminal, improving the user experience. It can be seen that the core network device can obtain more comprehensive network status information and make more comprehensive decisions.

[0335] Of course, the above examples A to C are only some possible specific implementations. Of course, the first functional entity can also be deployed on the RU, and its process is similar to that of example B. For details, please refer to the relevant description of example B, and the embodiments of this application will not be repeated here.

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

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

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

[0339] Figures 19 and 20 are schematic diagrams of the structures 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-mentioned method embodiments, thereby also achieving the beneficial effects of the above-mentioned method embodiments. In the embodiments of the present application, the communication device can be a transmitter or a module applied to the transmitter, for example, a chip.

[0340] As shown in FIG. 19 , the communication device 1900 includes a processing unit 1910 .

[0341] In a possible implementation, the communication device 1900 may further include a transceiver unit 1920 .

[0342] In a possible implementation, the communication device 1900 may further include a storage unit 1930 .

[0343] In a possible implementation, the communication device 1900 may further include a transceiver unit 1920 and a storage unit 1930 .

[0344] The communication device 1900 is used to implement the functions of any node in the method embodiments shown in Figures 7, 15, 17 and 18 above.

[0345] When communication device 1900 is used to implement the functions of the first functional entity in the method embodiment shown in FIG7 : transceiver unit 1920 is used to obtain first QoS parameters and second QoS parameters. Processing unit 1910 is used to obtain new second QoS parameters based on the first QoS parameters and the second QoS parameters. Processing unit 1910 is also used to perform all operations performed by communication device 1900 in the embodiment shown in FIG7 , except for the transceiver operations, and / or other processes used to support the technology described herein. Storage unit 1930 is used to store any data, computer instructions, and / or computer programs that may be involved in the various embodiments of this application.

[0346] When communication device 1900 is used to implement the functions of the third functional entity in the method embodiment shown in FIG7 : transceiver unit 1920 is used to receive new second QoS parameters from the first functional entity. Processing unit 1910 is used to perform a first operation based on the new second QoS parameters. Processing unit 1910 is also used to perform all operations performed by communication device 1900 in the embodiment shown in FIG7 , except for the transceiver operations, and / or other processes used to support the techniques described herein. Storage unit 1930 is used to store any data, computer instructions, and / or computer programs that may be involved in the various embodiments of this application.

[0347] When communication device 1900 is used to implement the functions of the second functional entity in the method embodiment shown in FIG15 : transceiver unit 1920 is used to receive second information. Processing unit 1910 is used to configure communication resources for the second functional entity based on the first QoS parameter. Processing unit 1910 is also used to perform all operations performed by communication device 1900 in the embodiment shown in FIG15 , except for the transceiver operations, and / or other processes used to support the techniques described herein. Storage unit 1930 is used to store any data, computer instructions, and / or computer programs that may be involved in the various embodiments of this application.

[0348] For a more detailed description of the processing unit 1910 and the transceiver unit 1920, please refer to the relevant descriptions of the method embodiments shown in Figures 7, 15, 17, and 18. The processing unit 1910 and the transceiver unit 1920 may also perform other steps, and the specific implementation can refer to the method embodiments, which will not be repeated here.

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

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

[0351] As shown in FIG20 , the communication device 2000 includes at least one processor 2010. In one possible implementation, the communication device 2000 may further include an interface circuit 2020.

[0352] In a possible implementation, the communication device 2000 may further include a memory 2030 .

[0353] In a possible implementation, the communication device 2000 may further include a memory 2030 and an interface circuit 2020 .

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

[0355] When the communication device 2000 is used to implement the methods shown in Figures 7, 15, 17 and 18, the processor 2010 can be used to implement the functions of the above-mentioned processing unit 1910, and / or the interface circuit 2020 can be used to implement the functions of the above-mentioned transceiver unit 1920, and / or the memory 2030 can be used to implement the functions of the above-mentioned storage unit 1930.

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

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

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

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

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

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

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

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

[0364] 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: The method is applied to a first functional entity, comprising: Obtain a first quality of service QoS parameter and a second QoS parameter, where the first QoS parameter is used to indicate a QoS requirement corresponding to a communication link between two different types of second functional entities having a communication connection, and the second QoS parameter is used to indicate a QoS requirement of a service; A new second QoS parameter is obtained according to the first QoS parameter and the second QoS parameter.

2. The method according to claim 1, characterized in that The first QoS parameter is obtained by at least one of the following methods: Determining, based on a first correspondence and a target policy, the first QoS parameter corresponding to the target policy, wherein the first correspondence represents an association between the first QoS parameter and an alternative function splitting method, the alternative function splitting method being a method for splitting a communication function of two different types of second function entities having a communication connection, the alternative function splitting method including a target function splitting method, and the target function splitting method having an association with the target policy; or The first QoS parameter is obtained based on first information, wherein the first information is used to indicate a network communication state corresponding to a first interface, and the first interface is a communication interface between two different types of second functional entities with communication connections.

3. The method according to claim 1 or 2, characterized in that The first functional entity is integrated into the second functional entity.

4. The method according to claim 3, characterized in that The first functional entity is integrated in a centralized unit CU, and the method further includes: A radio data bearer establishment process is initiated based on the new second QoS parameter.

5. The method according to claim 1 or 2, characterized in that The first functional entity and the second functional entity are independent functional entities.

6. The method according to claim 5, characterized in that The first functional entity and the CU are independent of each other, and the method further includes: Send the new second QoS parameter to the CU or core network function network element.

7. The method according to any one of claims 1 to 6, characterized in that The second functional entity is a functional entity in a radio access network RAN, a core network or a network management domain.

8. The method according to claim 7, 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; CU; Distributed Unit DU; or, Radio frequency unit RU.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: Send second information, where the second information is used to indicate the first QoS parameter.

10. The method according to claim 9, characterized in that The second information is the first QoS parameter, or the second information is information used to represent the target function splitting method, wherein the alternative function splitting method includes the target function splitting method, and the alternative function splitting method is a method for splitting the communication function of two different types of second function entities with communication connections.

11. The method according to claim 10, characterized in that The second information is information used to represent a target policy, and the method further includes: Send at least one of the alternative function splitting methods and the first QoS parameter corresponding to the alternative function splitting method.

12. The method according to claim 2, characterized in that The method further comprises: The target policy is determined based on one or more of the first information corresponding to the first interface, the fourth information and the 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, and the fourth information is used to indicate a second QoS parameter corresponding to at least one service.

13. The method according to claim 2 or 12, characterized in that The two different types of second functional entities corresponding to the first interface include a first target entity and a second target entity; the method further includes: Acquire the first information from the second functional entity; The first information includes at least one of the following parameters: Bandwidth resources of the first interface; Transmission delay of the first interface; Packet loss rate of the first interface; Reliability of the first interface; Internal processing delay of the first target entity; or, Internal processing delay of the second target entity.

14. The method according to claim 12, characterized in that The method further comprises: Acquire the third information from the second functional entity; The third information includes at least one of the following parameters: Processor utilization; Memory utilization; or, Disk utilization.

15. The method according to claim 12, characterized in that The method further comprises: Acquire the fourth information from the second functional entity and / or core network device; The fourth information includes at least one of the following parameters: Packet delay budget PDB; Guaranteed Bit Rate GBR; or, Packet Error Rate PER.

16. A communication method, characterized in that: The method is applied to a third functional entity, comprising: receiving a new second quality of service (QoS) parameter from the first functional entity, wherein the new second QoS parameter is obtained based on the first QoS parameter and the second QoS parameter, the first QoS parameter being used to indicate a QoS requirement corresponding to a communication link between two second functional entities of different types having a communication connection, and the second QoS parameter being used to indicate a QoS requirement for a service; performing a first operation based on the new second QoS parameter; The first operation includes any one of the following: Establishing a wireless data bearer; or, The new second QoS parameter is sent.

17. The method according to claim 16, characterized in that The third functional entity is a centralized unit CU, and the receiving of the new second QoS parameter from the first functional entity includes: receiving the new second QoS parameter sent by the first functional entity; or, Receive the new second QoS parameter forwarded by the core network element.

18. The method according to claim 17, characterized in that The performing the first operation based on the new second QoS parameter includes: establishing a wireless data bearer based on the new second QoS parameter.

19. The method according to claim 16, wherein The third functional entity is a core network element, and the receiving the new second QoS parameter from the first functional entity includes: Receive the new second QoS parameter sent by the first functional entity.

20. The method according to claim 19, characterized in that The performing the first operation based on the new second QoS parameter includes: sending the new second QoS parameter.

21. The method according to any one of claims 16 to 20, characterized in that: The first QoS parameter is obtained by at least one of the following methods: Determining, based on a first correspondence and a target policy, the first QoS parameter corresponding to the target policy, wherein the first correspondence represents an association between the first QoS parameter and an alternative function splitting method, the alternative function splitting method being a method for splitting a communication function of two different types of second function entities having a communication connection, the alternative function splitting method including a target function splitting method, and the target function splitting method having an association with the target policy; or The first QoS parameter is obtained based on first information, wherein the first information is used to indicate a network communication state corresponding to a first interface, and the first interface is a communication interface between two different types of second functional entities with communication connections.

22. The method according to any one of claims 16 to 21, characterized in that The first functional entity is integrated into the second functional entity.

23. The method according to any one of claims 16 to 21, characterized in that The first functional entity and the second functional entity are independent functional entities.

24. The method according to any one of claims 16 to 23, characterized in that The second functional entity is a functional entity in a radio access network RAN, a core network or a network management domain.

25. The method according to claim 24, 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; CU; Distributed Unit DU; or, Radio frequency unit RU.

26. The method according to claim 24, characterized in that The second functional entity and the third functional entity are the same functional entity.

27. A communication method, characterized in that: The method is applied to a second functional entity, comprising: receiving second information, where the second information is used to indicate a first quality of service (QoS) parameter, where the first QoS parameter is used to indicate a QoS requirement corresponding to a communication link between two second functional entities of different types having a communication connection; The communication resources of the second functional entity are configured according to the first QoS parameter, wherein the service transmitted on the communication resource corresponds to the second QoS parameter, and the first QoS parameter is also used to obtain a new second QoS parameter by combining the second QoS parameter through the first functional entity.

28. A communication system, characterized in that: It includes a first functional entity, a third functional entity and a core network element, wherein: The first functional entity is configured to obtain a first quality of service QoS parameter, where the first QoS parameter is used to indicate a QoS requirement corresponding to a communication link between two second functional entities of different types having communication connections; The core network element is configured to send a second QoS parameter to the first functional entity, where the second QoS parameter is used to indicate a QoS requirement of the service; The first functional entity is further configured to obtain a new second QoS parameter according to the first QoS parameter and the second QoS parameter; The first functional entity is integrated into a third functional entity, and the third functional entity is configured to perform a first operation based on the new second QoS parameter; or The first functional entity and the third functional entity are deployed independently, and the first functional entity is further configured to send the new second QoS parameter to the third functional entity; and the third functional entity is further configured to perform the first operation based on the new second QoS parameter. The first operation includes any one of the following: Establishing a wireless data bearer; or, The new second QoS parameter is sent.

29. The system according to claim 28, wherein: The system further comprises a second functional entity, wherein, The first functional entity is further configured to send second information to the second functional entity, where the second information is used to indicate a first quality of service QoS parameter; The second functional entity is used to configure communication resources of the second functional entity according to the first QoS parameter.

30. A communication device, characterized in that: include: processing module and communication module; The communication module is used to receive and / or send signals, the processing module is configured to enable the method of any one of claims 1 to 15 to be executed, or the processing module is configured to enable the method of any one of claims 16 to 26 to be executed, or the processing module is configured to enable the method of claim 27 to be executed.

31. A communication device, characterized in that: include: At least one processor and a communication interface, the communication interface being used to receive and / or send signals, the processor being configured to enable the method of any one of claims 1 to 15 to be executed, or the processor being configured to enable the method of any one of claims 16 to 26 to be executed, or the processor being configured to enable the method of claim 27 to be executed.

32. 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 that the communication device performs the method according to any one of claims 1 to 15, or the communication device performs the method according to any one of claims 16 to 26, or the communication device performs the method according to claim 27.

33. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions or programs. When the instructions or programs are executed on the communication device, the communication device executes the method according to any one of claims 1 to 15, or the communication device executes the method according to any one of claims 16 to 26, or the communication device executes the method according to claim 27.

34. A computer program product, characterized in that The computer program product includes 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 15, causes the computer to perform the method according to any one of claims 16 to 26, or causes the computer to perform the method according to claim 27.

Images