Method for adjusting service feature or quality-of-service parameter of service and wireless communication device

Abstract

The present disclosure provides a method for adjusting a service feature or quality-of-service parameter of a service, comprising: a first network node receives a first message from a second network node, wherein the first message comprises configuration parameters related to at least one of a service feature, quality-of-service, and a data radio bearer (DRB), i.e., the first message comprises dynamically changing configuration parameters. Transmitting these dynamically changing configuration parameters via a user plane protocol, compared to a control plane protocol, allows for more flexible message configuration and scheduling and lower latency.

Description

Method for adjusting service characteristics or service quality parameters of a service and wireless communication device Technical Field

[0001] The present disclosure relates to the field of wireless communications, and in particular to a method for adjusting service characteristics or service quality parameters of a service and a wireless communication device. Background Art

[0002] In the field of mobile communications, Quality of Service (QoS) measures a mobile communication system's ability to meet user needs and plays a crucial role. QoS ensures that even in situations of network congestion or high load, the system can allocate bandwidth and resources to guarantee user communication quality. However, QoS management mechanisms still need improvement. Therefore, a method for adjusting service characteristics or quality of service parameters, as well as wireless communication equipment, is needed to improve existing technologies.

[0003] Summary of the Invention

[0004] The technical problem to be solved by the present invention is to provide a method for adjusting the service characteristics or service quality parameters of a service in view of the above-mentioned defects of the prior art, aiming to solve the problems existing in the prior art.

[0005] According to one aspect of the present disclosure, a method for adjusting service characteristics or quality of service parameters of a service is provided, which is executed by a first network node and includes:

[0006] A first message of configuration parameters related to at least one of service characteristics, service quality, and data radio bearer (DRB) is received from a second network node, wherein the first message is a message based on a user plane protocol.

[0007] According to one aspect of the present disclosure, a method for adjusting service characteristics or service quality parameters of a service is provided, which is executed by a second network node, and the method includes:

[0008] A first message of configuration parameters related to at least one of service characteristics, service quality, and data radio bearer (DRB) is sent, wherein the first message is a message based on a user plane protocol.

[0009] According to one aspect of the present disclosure, a wireless communication device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the steps in the data processing method as described in any one of the above items.

[0010] Beneficial effects of the present invention: In the present disclosure, a first network node receives a first message from a second network node, and the first message includes configuration parameters related to at least one of service characteristics, service quality, and data radio bearer (DRB), that is, the first message includes configuration parameters that need to be dynamically changed. These configuration parameters that need to be dynamically changed are transmitted based on the user plane protocol. Compared with the control plane protocol, the configuration and scheduling of the message are more flexible and the delay is shorter. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the embodiments of the present disclosure or related technologies, the following drawings will be briefly introduced in the embodiments. Obviously, the drawings are only some embodiments of the present disclosure, and ordinary technicians in this field can derive other drawings based on these drawings without inventive work.

[0012] FIG1 illustrates a schematic diagram of a wireless communication system architecture provided by the present disclosure.

[0013] FIG2 a illustrates a schematic diagram of a data bearing structure provided by the present disclosure.

[0014] FIG2 b illustrates a schematic diagram of a data bearing structure provided by the present disclosure.

[0015] FIG3 illustrates a schematic diagram of a wireless communication system framework provided by the present disclosure.

[0016] FIG4 illustrates a schematic diagram of a wireless communication system framework provided by the present disclosure.

[0017] FIG5 a illustrates a schematic diagram of adjusting service characteristics or service quality parameters of the service provided by the present disclosure.

[0018] FIG5 b illustrates a schematic diagram of adjusting service characteristics or service quality parameters of the service provided by the present disclosure.

[0019] FIG6 illustrates a schematic diagram of a 3GPP Uu interface user plane protocol stack architecture diagram provided by the present disclosure.

[0020] FIG7 illustrates a schematic diagram of a Control PDU provided by the present disclosure.

[0021] FIG8 illustrates a schematic diagram of a Control PDU provided by the present disclosure.

[0022] FIG9 illustrates a schematic diagram of a Control PDU provided by the present disclosure.

[0023] FIG10 illustrates a schematic diagram of a MAC CE provided by the present disclosure.

[0024] FIG11 illustrates a schematic diagram of a MAC CE provided by the present disclosure.

[0025] FIG12 illustrates a schematic diagram of a mapping relationship between a QoS flow and a DRB provided by the present disclosure.

[0026] FIG13 is a schematic diagram illustrating a mapping relationship between a QoS flow and a DRB provided in the present disclosure.

[0027] FIG14 is a schematic diagram illustrating a mapping relationship between a QoS flow and an RLC entity provided by the present disclosure.

[0028] FIG15 is a schematic diagram illustrating a mapping relationship between a QoS flow and an RLC entity provided by the present disclosure.

[0029] FIG16 illustrates an exemplary block diagram of a wireless communication system provided by the present disclosure. DETAILED DESCRIPTION

[0030] The embodiments of the present disclosure describe technical matters, structural features, objectives and effects in detail with reference to the accompanying drawings, as described below. Specifically, the terms in the embodiments of the present disclosure are only used to describe the purpose of specific embodiments, rather than to limit the present disclosure.

[0031] The relevant technical terms in this article are explained as follows:

[0032] Table 1

[0033] In this disclosure, "A or B" may mean "only A," "only B," or "both A and B."

[0034] In other words, in the present disclosure, "A or B" may be interpreted as "A and / or B." For example, in the present disclosure, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B, and C."

[0035] As used in this disclosure, a slash ( / ) or a comma may mean "and / or". For example, "A / B" may mean "A and / or B". Thus, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B, or C".

[0036] In the present disclosure, “at least one of A and B” may mean “only A”, “only B”, or “both A and B”. In addition, in the present disclosure, the expression “at least one of A or B” or “at least one of A and / or B” may be interpreted as “at least one of A and B”.

[0037] In addition, in the present disclosure, “at least one of A, B, and C” may mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.” In addition, “at least one of A, B, or C” or “at least one of A, B, and / or C” may mean “at least one of A, B, and C.”

[0038] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features being referred to. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the described features. Throughout the description of this application, "plurality" means two or more, unless otherwise specifically defined.

[0039] Those skilled in the art will recognize and appreciate that the details of the described examples are merely illustrative of some embodiments and that the teachings set forth herein are applicable to various alternative arrangements.

[0040] The technical solution disclosed herein can be applied to various wireless communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, 5G communication system or future wireless communication systems, etc.

[0041] Exemplarily, a wireless communication system 100 applied in the present disclosure is shown in FIG1 . The wireless communication system 100 may include a base station 110, which may be a device that communicates with a user equipment 120 (User Equipment, UE). The base station 110 may provide communication coverage for a specific geographical area and may communicate with user equipment located within the coverage area. Optionally, the base station 110 may be an evolved base station (eNB or eNodeB) in an LTE system, or the base station may be a mobile switching center, a relay station, an access point, an in-vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a base station in a future communication system, etc.

[0042] The wireless communication system 100 also includes at least one user equipment 120 located within the coverage area of ​​the base station 110. As used herein, "user equipment" includes, but is not limited to, a device configured to receive / send communication signals via a wired connection, such as a Public Switched Telephone Network (PSTN), a Digital Subscriber Line (DSL), a digital cable, a direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as a cellular network, a Wireless Local Area Network (WLAN), a digital television network such as a Digital Video Broadcasting Handheld (DVB-H) network, a satellite network, an AM-FM (Amplitude Modulation-Fequency Modulation) broadcast transmitter; and / or another user equipment; and / or an Internet of Things (IoT) device. A user equipment configured to communicate via a wireless interface may be referred to as a "wireless communication terminal," "wireless terminal," or "mobile terminal." Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that can combine cellular radiotelephones with data processing, fax, and data communication capabilities; PDAs that can include radiotelephones, pagers, Internet / Intranet access, web browsers, notepads, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or palmtop receivers or other electronic devices that include radiotelephone transceivers. User equipment can refer to access terminals, subscriber units, subscriber stations, mobile stations, mobile stations, remote stations, remote user equipment, mobile devices, wireless communication devices, or user agents. An access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a user device in a 5G network, or a user device in a future evolved PLMN, etc.

[0043] Optionally, the user equipments 120 may perform device-to-device (D2D) communication with each other.

[0044] Optionally, the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.

[0045] The wireless communication system 100 also includes a core network 130. Core network 130 may be an IP mobile communication network operated by a mobile communication operator. For example, core network 130 may be a core network used by a mobile communication operator that operates and manages the wireless communication system 100, or may be a core network used by a virtual mobile communication operator such as an MVNO (Mobile Virtual Network Operator).

[0046] The core network 130 can be connected to the base station 110 and serve as a relay device for transmitting user data. The user equipment 120 transmits and receives user data via the core network 130. It should be noted that the communication of user data is not limited to IP communication and can also be non-IP communication.

[0047] FIG1 exemplarily shows a base station 110 , two user equipments 120 and a core network 130 . Optionally, the wireless communication system 100 may include multiple base stations and each base station may include other numbers of user equipments within its coverage area, which is not limited in the present disclosure.

[0048] Optionally, the wireless communication system 100 may further include other network entities such as a network controller, a mobility management entity, and a network element, which is not limited in this disclosure. For example, the core network 130 may include other network entities such as a network controller, a mobility management entity, and a network element, which is not limited in this disclosure.

[0049] It should be understood that in this disclosure, a device with wireless communication capabilities in a network / system may be referred to as a wireless communication device. Taking the wireless communication system 100 shown in Figure 1 as an example, the wireless communication device may include a base station 110 with communication capabilities, a user device 120, and a core network 130. The base station 110 and the user device 120 may be the specific devices described above and will not be described in detail here. The wireless communication device may also include other devices in the wireless communication system 100 (core network 130). For example, the core network 130 may include other network entities such as a network controller and a mobility management entity, but this disclosure does not limit this.

[0050] To facilitate understanding of the technical solutions of the present disclosure, the technical solutions related to the present disclosure are described below.

[0051] Before describing the present disclosure in further detail, the following glossary is provided for a better understanding of the present disclosure.

[0052] QoS, or Quality of Service, refers to the quality of service within a network. In the mobile communications field, QoS refers to the quality of service provided to users within a mobile network. In other words, QoS measures the ability of a mobile communications system to meet user needs. QoS plays a vital role in mobile communications. It ensures that even in situations of network congestion or high load, the system can allocate bandwidth and resources to guarantee user communication quality. QoS parameters include basic parameters such as data rate, latency, packet loss rate, and jitter. Different QoS parameters can be used to evaluate and compare the needs of different services. To meet the needs of different services, services are divided into different service types, and different QoS parameters are defined for each service type. By setting QoS parameters and policies, mobile communications systems can monitor and optimize channel quality, while improving the user communication experience.

[0053] QoS parameters and configuration are managed through a set of technologies and processes. For example, in the 3GPP 4G (i.e., LTE (Long Term Evolution) + EPS (Evolved Packet System)) mobile communication system standard, QoS is managed based on the EPS bearer, and the minimum granularity of QoS management is the EPS bearer. As shown in Figure 2a, the EPS bearer is located between the UE (User Equipment) and the PDN GateWay (PDN Gateway). The part of the EPS bearer related to the radio access network is called the Electronic Resource Access Protocol (E-RAB). The E-RAB further includes the RB (Radio Bearer) and the S1 interface user plane data transmission bearer S1-Bearer (General Packet Radio Service Technology Tunneling Protocol User Plane GTP-U (GPRS Tunneling Protocol-User Plane) tunnel). The various components of the EPS bearer have a one-to-one relationship. That is, one EPS bearer corresponds to one EAB, and one EAB corresponds to one DRB and one S1-Bearer. QoS management of the EPS bearer is achieved by configuring a set of QoS parameters. This set of parameters applies to each component of the EPS bearer, including RBs and S1-Bearers.

[0054] In the 3GPP 5G (i.e., 5GC (5G Core Network) + NR (New Radio)) mobile communication system standard, Quality of Service (QoS) is managed based on QoS Flows, with the minimum granularity of QoS management being QoS Flows. As shown in Figure 2b, the QoS flow is located between the UE and the UPF (User Plane Function). Unlike 4G, the QoS flow is end-to-end and is further mapped to the N3 tunnel (GTP-U tunnel, the user plane data transmission bearer of the NG interface) and RB (Radio Bearer) in the radio access network. One PDU session corresponds to multiple QoS flows, multiple QoS flows are mapped to one N3 tunnel, and multiple QoS flows are mapped to one or more RBs, but one QoS flow can only be mapped to one RB. QoS management of QoS flows is achieved by configuring a set of QoS parameters, which apply to all parts of the QoS flow mapping, including the RB and N3 tunnel.

[0055] 3GPP's QoS management approach in 4G and 5G systems can be modeled as shown in Figure 3, including the user equipment (UE), radio access network (RAN), core network (CN), and data network (DN). The core network is typically divided into the control plane (CP) and user plane (UP). The CP controls QoS policies, determining QoS parameters, and then configures these parameters to the UE, RAN, and UP via control plane messages. During actual data transmission, the UE, RAN, and UP coordinate and allocate resources to meet QoS requirements.

[0056] Taking the 5G system as an example, as shown in Figure 4, the control plane-related network functions or nodes of the core network 5GC include at least the session management function SMF (Session Management Function) and the access and mobility management function AMF (Access and Mobility Management Function). The QoS flow is managed by the SMF of the core network 5GC. During the PDU session establishment and modification process, the QoS parameters are determined according to the established business requirements and configured to the UE, RAN and UPF through the PDU session establishment and modification process. Specifically:

[0057] On the UE side: QoS parameters are sent by the SMF to the AMF during the Packet Data Unit Session (PDU Session) establishment or modification process, and then sent to the UE through the control plane Non-Access Stratum (NAS) message of the N1 interface. Some parameters can be derived by the UE through the reflective QoS mechanism;

[0058] On the UPF side: QoS parameters are sent by the SMF to the UPF via the control plane message of the N2 interface during the PDU Session establishment or modification process;

[0059] On the RAN side: QoS parameters are sent by SMF to AMF during the PDU Session establishment or modification process, and then sent to RAN through the control plane NGAP message of the N2 interface.

[0060] After receiving the QoS parameters in the PDU session establishment and modification processes (PDU SESSION RESOURCE SETUP) and PDU SESSION RESOURCE MODIFY), the RAN establishes or modifies a data radio bearer (DRB) (a radio bearer used to carry service data) through the Uu interface control plane RRC (Radio Resource Control) message and sends the DRB-related QoS parameters to the UE.

[0061] Existing QoS management mechanisms are static and based on the control plane. With the continuous advancement of technology, new service requirements are constantly emerging, requiring support for dynamic changes in service characteristics. Dynamic changes in service characteristics can be divided into at least two types: the service type remains unchanged, but only some characteristics change; or the service type changes.

[0062] Based on existing technology, QoS parameter configuration for 3G, 4G, and 5G is statically configured and modified based on control plane processes and messages. This approach assumes that QoS parameters rarely, if ever, change after service establishment. However, WT#2 of the aforementioned SA Rel-19XRM project proposes a new, transformative QoS parameter configuration requirement that supports dynamic changes to QoS parameters via the user plane. In mobile communication networks, QoS control mechanisms are primarily tied to the RAN. It is foreseeable that the need to support dynamic changes to QoS parameters on the user plane will have a significant impact on the RAN, including the interface protocols between the RAN and CN, and between base stations within the RAN and UEs, potentially leading to some transformative requirements.

[0063] An analysis of existing technologies reveals that existing RAN node-related interfaces currently do not support dynamic changes in service characteristics. Therefore, the issue that needs to be addressed is how RAN node-related interfaces can support such dynamic changes in service characteristics, particularly dynamic changes via the user plane.

[0064] Exemplary Methods

[0065] This embodiment provides a method for adjusting service characteristics or service quality parameters of a service, which can be applied to a first network node (the first network node can be a base station, a user equipment, or a distributed unit of a base station). Specifically, as shown in FIG5a , the method includes:

[0066] Step S100: Receive a first message sent by a second network node containing configuration parameters related to at least one of service characteristics, quality of service, and data radio bearer (DRB), wherein the first message is a message based on a user plane protocol.

[0067] This embodiment provides a method for adjusting service characteristics or service quality parameters of a service, which can be applied to a second network node (the second network node can be a core network device, a base station, or a central unit of a base station). Specifically, as shown in FIG5b , the method includes:

[0068] Step H100: Send a first message of configuration parameters related to at least one of service characteristics, service quality, and data radio bearer (DRB), wherein the first message is a message based on a user plane protocol.

[0069] Specifically, the first network node receives a first message of configuration parameters related to at least one of service characteristics, quality of service, and data radio bearer (DRB) sent by the second network node, wherein the configuration parameters related to service characteristics include periodicity, burst arrival time, jitter, etc., the configuration parameters related to quality of service include (5G QoS Identifier, 5QI) parameters, and the configuration parameters related to DRB include discard time (discardTimer), uplink packet data convergence protocol sequence size (pdcp-SN-SizeUL), etc. It should be noted that the above parameter enumeration is only an example and is not a specific limitation. Furthermore, the first message regarding configuration parameters related to at least one of service features, quality of service, and data radio bearer (DRB) is based on a user plane protocol. Furthermore, based on the user plane protocol's General Packet Radio Service (GPRS) Tunneling Protocol-User Plane Extension Header (GTP-U Extension Header), or referred to as a General Packet Radio Service (GPRS) Tunneling Protocol-User Plane (GTP-U Container), a CN node dynamically sends information related to QoS features to a RAN node, or a RAN node sends information related to QoS features to another RAN node. Between different network nodes, a General Packet Radio Service (GPRS) Tunneling Protocol-User Plane (GTP-U tunnel) is first established via a control plane protocol, and then user plane data packets are transmitted and carried via GTP-U protocol PDUs. While GTP-U protocol PDUs carry user-plane data packets, the GTP-U Extension Header of the PDUs also carries dynamic configuration parameter messages related to at least one of service characteristics, quality of service, and data radio bearer (DRB). This supports dynamic changes in service characteristics and / or QoS requirements. Compared to control-plane protocols, user-plane protocol-based message configuration and scheduling are more flexible and have lower latency. Furthermore, dynamic changes to configuration parameter messages related to at least one of service characteristics, quality of service, and data radio bearer (DRB) can be categorized into two methods: dynamic and semi-static.

[0070] In the existing 5G system, information about all parameters related to service characteristics or QoS is shown in Table 2. Except for the Preamble Sequence Index (PSI), all other parameters are statically configured through the NG interface control plane NGAP protocol. The PSI is dynamically indicated through the GTP-U container of the NG interface user plane protocol. Most parameters are configured based on QoS flow. The 5G QoS Identifier (5QI) parameter refers to a parameter related to 5QI. Dynamic 5QI (dynamic5QI) in the 5QI parameter configuration method refers to a method for configuring 5QI parameters to non-standard values. In this case, each 5QI parameter can be configured to a value other than the standardized 5QI standard parameter as needed. Non-dynamic 5QI (non-dynamic5QI) refers to a method for configuring 5QI parameters to standardized 5QIs defined in the standard. In this case, only one 5QI needs to be configured. 5QI is an index value. Each 5QI value corresponds to a row in the standardized 5QI table, which includes the values ​​of all related 5QI parameters. The Alternative QoS Parameter Set List (Alternative 5QI) in the 5QI parameter configuration method QoS Parameters Set List) refers to configuring an additional optional QoS parameter set for the QoS flow. The parameter set only includes the guaranteed flow bit rate (Guaranteed Flow Bit Rate, GFBR), packet delay budget (Packet Delay Budget, PDB), and packet error rate (Packet Error Rate, PER); this parameter set list is selected by the base station when the main QoS parameter configuration (i.e., the QoS parameters configured by dynamic5QI and Non-dynamic5QI) cannot be met. The applicable parameter set list can be selected and notified to 5GC.

[0071] Table 2 Configuration parameters related to at least one of service characteristics, service quality, and data radio bearer (DRB)

[0072] In order to solve the problem of dynamic configuration of configuration parameters related to at least one of service characteristics, service quality, and data radio bearer (DRB) in the above-mentioned 5G system, the present disclosure proposes a first message based on a user plane protocol receiving a configuration parameter sent by a second network node related to at least one of service characteristics, service quality, and data radio bearer (DRB) at the NG / Xn interface.

[0073] Example 1

[0074] In some embodiments, the first network node is a base station, the second network node is a core network device, and the base station receives a first message based on a user plane protocol, which is sent by the second network node and contains configuration parameters related to at least one of service features, quality of service, and a data radio bearer (DRB). The first message is a message based on the user plane protocol, and the message based on the user plane protocol includes a General Packet Radio Service Tunneling Protocol user plane container (GTP-U Container). The GTP-U Container includes at least one of the following: a first protocol data unit type, a first quality of service flow identifier (QOS flow ID), configuration parameters related to service features or QOS parameters, and a second activation indication corresponding to the QOS parameter. The second activation indication is used to indicate whether the QOS parameter has changed.

[0075] Specifically, the GTP-U Container may also be a GTP-U Extension Header, the first protocol data unit type is the PDU type (also known as PDU Type) hereinafter; the first quality of service flow identifier QOS flow ID is also the identifier corresponding to the quality of service flow hereinafter. The first configuration information includes the first QOS flow ID (also known as QoS Flow Identifier hereinafter), and the GTP-U Container includes at least one of the following: the first protocol data unit type, the first quality of service flow identifier QOS flow ID, and configuration parameters or QOS parameters related to service features. In this way, the base station determines, based on the first quality of service flow identifier QOS flow ID and the configuration parameters or QOS parameters related to service features, which QOS flow's configuration parameters or QOS parameters related to service features need to be dynamically changed to reduce the delay of dynamically changing the parameter set. Different configuration information or data transmission content can further be distinguished by the protocol data unit type, so that the base station and the core network device can understand more fine-grained data information.

[0076] The following is a detailed explanation using a practical example. When a 5G system supports TSN (Time Sensitive Network) and XR services, it involves configuration parameters related to service characteristics, including periodicity, burst arrival time, and / or jitter. The definitions of these parameters are shown in Table 3.

[0077] Table 3 Configuration parameters related to service features

[0078] For XR services, users may change service configurations at any time during the service, such as the video frame rate. These configurations may cause changes in characteristic parameters such as periodicity, burst arrival time, and jitter. Taking the NG interface between the core network equipment CN and the base station as an example, in order to support the dynamic changes of these service characteristics or QoS parameter information, the solution to support the dynamic changes of these service characteristics information based on user plane protocol messages is at least one of the following:

[0079] In some implementations, based on the GTP-U Container, with reference to the PDU Session User Plane Protocol (see 3GPP standard protocol 38.415 for details), a PDU type (PDU Type (=2)) is predefined or the existing PDU is extended to transmit service features or QoS parameter information between the UPF and the base station, as shown in Table 4. When these service feature information or QoS parameters change, the new service feature or QoS parameter information is sent by including a GTP-U Container of this PDU Type in the GTP-U PDU. In particular, in the 5G system, these service features or QoS parameters are configured and sent in units of QoS flow, and the GTP-U Container is also sent in units of QoS flow, so this PDU type includes a QoS flow identifier (QoS Flow Identifier).

[0080] Table 4 Configuration parameters or QOS parameters related to service features transmitted based on user plane protocol (PDU Type (=2))

[0081] In other implementations, the protocol data unit type may be predefined, and the protocol data unit PDU type (PDU Type (=3)) may be used to indicate service features or QoS parameter information transmitted between the UPF and the base station. The message also includes second configuration information. The second activation indication contained in the second configuration information indicates whether a parameter related to the service feature or QoS parameter has changed through a predefined bitmap. If the ind bit is set to 1, it indicates that the value of the parameter has changed; if the ind bit is set to 0, it indicates that the value of the parameter has not changed. The length of the bitmap depends on the number of predefined parameters. If a parameter has changed, the changed value of the parameter is further included, i.e., parameter1 / 2 / 3. These parameter values ​​correspond to multiple parameters with the ind bit set to 1 in sequence, as shown in Table 5. When these parameters related to the service feature or QoS parameter information change, the new service feature or QoS parameter information is sent by including a GTP-U Container of this PDU Type in the GTP-U PDU.The parameters or QoS parameters related to service characteristics include but are not limited to at least one of the following parameters: downlink periodicity, downlink burst arrival time, downlink jitter, uplink periodicity, uplink burst arrival time, uplink jitter, 5QI, allocation and retention priority (ARP), guaranteed flow bit rate (GFBR), maximum flow bit rate (MFBR), maximum packet loss rate, notification control, reflective quality of service attribute (RQA), user equipment-access and mobility management bearer (UE-AMBR), session mobility management bearer (Session-AMBR), survival time, PSDB, PSER, PSIHI, default priority level, packet delay budget (PDB), and so on. Budget (PDB), Packet Error Rate (PER), default maximum data burst volume, and default averaging window. In particular, these parameters can be categorized and grouped, with different PDU types predefined for different groups of parameters to transmit the service characteristics or QoS parameters that require adjustment.

[0082] Table 5 Configuration parameters or QOS parameters related to service features transmitted based on user plane protocol (PDU Type (=3))

[0083] In particular, the existing PDU type carrying capacity can be further expanded based on the existing PDU type to transmit service characteristics or QoS parameter information between the UPF and the base station. The specific expansion method can refer to the solution in Table 4 / 5 above.

[0084] In particular, for a certain QoS flow, the CN control plane node can also enable it through control plane message settings to determine whether it supports dynamic changes in service characteristics or QoS parameters: if enabled, the above method can be used to dynamically adjust the service characteristics or QoS parameters for the QoS flow; otherwise, the above method cannot be used to dynamically adjust the service characteristics or QoS parameters.

[0085] In particular, the above method for sending service characteristics or QoS parameter information based on GTP-U Container is also applicable to the Xn interface, that is, one base station sends service characteristics or QoS parameter information to another base station through the Xn interface based on GTP-U Container.

[0086] Example 2

[0087] In some embodiments, the first network node is a base station, and the method includes receiving a second message based on a control plane protocol, wherein the QOS parameter is a QOS parameter set, and the second message includes at least one of the following: the first QOS flow ID, status information corresponding to the QOS parameter set, several QOS parameter sets corresponding to the first QOS flow, and an identifier corresponding to the QOS parameter set; receiving a first message sent by the second network node containing configuration parameters related to at least one of service characteristics, quality of service, and data radio bearer (DRB), wherein the first message is a message based on a user plane protocol, the message based on the user plane protocol includes a general packet radio service tunneling protocol user plane container GTP-U Container, and the GTP-U Container includes at least one of the following: a first protocol data unit type, a first quality of service flow identifier QOS flow ID, and a second activation indication corresponding to the QOS parameter set, the second activation indication being used to indicate activation or deactivation of the QOS parameter set.

[0088] Specifically, when a first QOS flow corresponds to multiple QOS parameter sets, the multiple QOS parameter sets corresponding to the first QOS flow and their initial state information can be configured via a control plane protocol. When the QOS parameter set used in the first QOS flow needs to be changed, the second activation indicator corresponding to the QOS parameter set in the user plane protocol is adjusted (e.g., the previously configured QOS parameter set in the control plane is set to a deactivated state and the new QOS parameter set to be used is set to an activated state). Since each QOS flow has multiple QOS parameter sets, the second activation indicator corresponding to the QOS parameter set in the user plane protocol is adjusted to correspond to the corresponding QOS flow ID. The presentation of the GTP-U container can be distinguished by the first protocol data unit type. In this way, for a large number of QOS parameter set changes, the initial QOS parameter set and the corresponding state of the QOS parameter set are configured via a control plane protocol, and then the corresponding state of the QOS parameter set is adjusted via an activation indicator included in the user plane protocol (generally, a single bit is sufficient), which can significantly reduce the delay in adjusting the QOS parameter set.

[0089] The following is a practical example to illustrate this in detail. When performing XR or Cloud gaming services in a 5G system, the real-time video service may be temporarily suspended or interrupted as the service progresses or due to user control. This can lead to the download of configuration files or AI models (if AI is supported), which can significantly change service characteristics and core parameters. For example, the 5QI (5QI), a core parameter for QoS, can change. While these service characteristic changes occur randomly and involve a large number of parameters, the changes in service characteristics or configuration parameters related to these characteristics are predictable. In order to solve the problem of dynamic configuration of configuration parameters related to service characteristics or service quality in the above-mentioned 5G system, the present disclosure configures multiple sets of service characteristics or QoS parameter set information for a QoS flow through control plane processes and / or messages, which include at least one of the following information: QoS flow identification information, parameter set identifier (identifier) ​​or index (index) corresponding to the parameter set, parameter set status information and QOS parameter set; dynamically send the service characteristics or QoS parameter set information of the QoS flow through user plane processes and / or messages, and the processes and / or messages include at least one of the following information: QoS flow identification information, parameter set identifier or index information or parameter set status information.

[0090] In the control plane protocol:

[0091] In the 5G system, taking the NG interface between the CN and the base station as an example, in the relevant process of service establishment or modification, that is, the PDU session establishment and modification process, multiple sets of QOS parameter sets are configured for a certain QoS flow (each QoS flow corresponds to a QOS flow ID) (each set of multiple QOS parameter sets is placed in a QOS parameter set list), where each set of QOS parameter sets corresponds to an identifier or index, including but not limited to at least one of the following parameters: 5QI (including non-dynamic 5QINon-dynamic5QI and / or dynamic 5QIDynamic5QI), ARP, GFBR, MFBR, Maximum Packet Loss Rate, Notification control, RQA, Periodicity, Burst Arrival Time, Survival Time, Jitter Arrange, PSDB, PSER, PSIHI. Specifically:

[0092] In the messages of the PDU session establishment and modification process of the NGAP protocol on the control plane of the NG interface, for example, the information units "PDU Session Resource Setup Request Transfer" and "PDU Session Resource Modify Request Transfer" can be enhanced to enhance the QoS Flow Level QoS Parameters configuration to a list configuration form. In another embodiment, for GBR services, the information unit "Alternative QoS Parameters Set List" can be enhanced to include: further adding other service features or QoS parameters, wherein the alternative QoS parameter set list includes an alternative set of QoS parameters, and the NG-RAN node can indicate that these alternative QoS parameters are satisfied when notification control is enabled and the requested QoS parameter list is not satisfied or when an alternative QoS parameter set index is received in the GTP-U container.

[0093] Furthermore, the application scope of the "Alternative QoS Parameters Set List" unit can be expanded, that is, when the base station receives an "Alternative QoS Parameters Set Index" indication through the GTP-U Container, the base station must meet the QoS parameter configuration indicated by the index.

[0094] For multiple QOS parameter sets or configuration parameter sets related to service features in the "QoS Flow Level QoS Parameters Set List" or the "Alternative QoS Parameters Set List", one of them can be set as the QOS parameter set for initial use, and the other QOS parameter sets are unused parameter sets. The setting method includes: implicitly indicating that the QOS parameter set with the smallest identifier or index value is the QOS parameter set for initial use, or explicitly indicating that a certain QOS parameter set is the QOS parameter set for initial use through a second activation indication information unit corresponding to the QOS parameter. The QOS parameter set that is configured and set for use may be referred to as an activated QOS parameter set (activated QoS Flow Level QoS Parameters Set or activated Alternative QoS Parameters Set), and the configured unused parameter set may be referred to as a deactivated parameter set (deactivated QoS Flow Level QoS Parameters Set or deactivated Alternative QoS Parameters Set). In practice, a second activation indication corresponding to the QOS parameter set may also be used to indicate that a certain QOS parameter set is the QOS parameter set initially used or the QOS parameter set configured and set for use.

[0095] In the user plane protocol

[0096] After the control plane completes the above configuration, based on the GTP-U Container, a PDU type is predefined or an existing PDU is extended to send a second activation indication (i.e., parameter set identifier or index information) corresponding to the service feature or QoS parameter set of the QoS flow configured on the control plane in the downlink and / or uplink directions between the UPF and the base station (in this case, PDU Type (=4), see Table 6), wherein each second activation indication has a corresponding first QoS flow ID. In this case, the first QoS flow ID does not change, and only any service feature or QoS parameter set corresponding to the first QoS flow ID is changed. In addition, a predefined bitmap can also be used, in which each second activation indication bit (Ind bit) is used to indicate the activation or deactivation of a service feature parameter or QoS parameter set. When the value of the bit is set to 1, it indicates the activation of the corresponding service feature parameter or QoS parameter set. When the value of the bit is set to 0, it indicates the deactivation of the corresponding service feature parameter or QoS parameter set. The predefined method includes: the second activation indicator is a QFI or QoS parameter set identifier, and each bit in the bitmap is sequentially mapped from high to low or from low to high in descending order according to the value of the QFI or QoS parameter set identifier (in this case, PDU Type (=5), see Table 7). The length of the bitmap depends on the number of parameter sets. After the control plane completes the above configuration, when a service feature or QoS parameter set changes, the UPF sends the new downlink and / or uplink service feature or QoS parameter set to the base station by including this type of PDU in the GTP-U Container. In the base station, the parameter set corresponding to the parameter set index included in the PDU Type (=4) is set as the new parameter set to be used, i.e., the service feature or QoS parameter set in the activated state, and the previously used service feature or QoS parameter set is changed to an inactive service feature or QoS parameter set, i.e., the deactivated service feature or QoS parameter set. The service feature or QoS parameter set is set to the activated or deactivated state according to each corresponding second activation indicator in the PDU Type (=4) or PDU Type (=5). In this way, a large number of service features or QoS parameter sets are configured through the control plane, and then the service features or QoS parameter sets are changed through activation indications that occupy a small amount of bit overhead configured on the user plane, making the scheduling of service features or QoS parameter sets more flexible and shortening the latency.

[0097] In addition, in the 5G system, these service feature parameters are configured and sent in units of QoS flow, and the GTP-U Container is also sent in units of QoS flow, so this PDU type includes a QoS flow identifier, which is the identifier of this QoS flow.

[0098] Table 6 Configuration parameter set or QOS parameter set related to service features transmitted based on user plane protocol (PDU Type (=4))

[0099] Table 7 Configuration parameter set or QOS parameter set related to service features transmitted based on user plane protocol (PDU Type (=5))

[0100] Example 3

[0101] In some embodiments, the first network node is a base station, and the method for adjusting the service characteristics or service quality parameters of the service includes the base station receiving a third message based on a control plane protocol, wherein the third message includes the first QOS flow ID and / or status information corresponding to the first QOS flow ID; receiving a first message sent by a second network node containing configuration parameters related to at least one of service characteristics, quality of service, and data radio bearer (DRB), wherein the first message is a message based on a user plane protocol, and the message based on the user plane protocol includes a general packet radio service tunneling protocol user plane container GTP-U Container, and the GTP-U Container includes at least one of the following: a first protocol data unit type, a first quality of service flow identifier QOS flow ID, and a first activation indication corresponding to the first quality of service flow QOS flow, and the first activation indication is used to indicate activation or deactivation of the first QOS flow corresponding to the first QOS flow ID.

[0102] Specifically, when a first QOS flow corresponds to a QOS parameter set, the parameter set can be adjusted by modifying the state of the first QOS flow (e.g., activation or deactivation). The control plane protocol receives the first QOS flow ID and / or state information corresponding to the first QOS flow ID to determine the initial state of each QOS flow (e.g., activation or deactivation). On the user plane, when the QOS parameter set used in the first QOS flow needs to be changed, the second activation indicator corresponding to the first QOS flow in the user plane protocol is adjusted (e.g., setting the previously configured first QOS flow in the control plane to a deactivated state and the newly used first QOS flow to an activated state). The presentation of the GTP-U Container can be distinguished by the type of the first protocol data unit. In this way, for a large number of QOS parameter set changes, the initial first QOS flow state is configured through the control plane protocol, and then the state corresponding to the first QOS flow is adjusted using the activation indicator contained in the user plane protocol (generally, a single bit is sufficient). This can significantly reduce the delay in adjusting the QOS parameter set.

[0103] The following is a detailed explanation using a practical example. When performing extended reality (XR) services or cloud gaming services in a 5G system, as the service progresses or under user control, the real-time video service will be temporarily paused or interrupted, and some configuration files or AI models (if AI is supported) will be downloaded, causing significant changes in service characteristics and core parameters. In order to solve the problem of dynamic configuration of configuration parameters related to service characteristics or service quality in the above-mentioned 5G system, the present disclosure configures multiple corresponding QoS flow information through the control plane based on multiple sets of variable service characteristics or QoS parameter set requirements contained in the control plane protocol message, wherein the QoS flow information includes at least one of the following information: QoS flow identification information, QoS flow status information (activated or deactivated); then dynamically changes the QoS flow to the activated state or deactivated state through the user plane process and / or message, and the process and / or message includes at least one of the following information: QoS flow identification information, QoS flow status information (activated or deactivated).

[0104] In the control plane protocol:

[0105] In a 5G system, taking the NG interface between the CN and the base station as an example, during the service establishment or modification process, namely the PDU session establishment and modification process, multiple QoS flows are established or modified based on multiple service characteristics or QoS parameter set requirements. Some of these QoS flows are configured to be activated and others to be deactivated. Specifically, for a PDU session, at least one QoS flow is always activated, such as the default QoS flow.

[0106] In the messages of the PDU session establishment and modification process of the control plane NG interface protocol (NGAP) of the interface (NG interface) between the radio access network and the 5G core network, for example, the information units "PDU Session Resource Setup Request Transfer" and "PDU Session Resource Modify Request Transfer" can be enhanced to add a first activation indication (i.e., status indication information) for each established or modified QoS flow, indicating that the QoS flow is configured as activated or deactivated; or an implicit indication, such as the one with the smallest identifier value is the default QoS flow, and the default QoS flow is always configured as activated.

[0107] In the user plane protocol:

[0108] After the control plane completes the above configuration, a predefined PDU type is used to transmit one or more first QoS flow IDs (i.e., QoS flow identifiers) or indices and first activation indicators (PDU Type (=6), see Table 8) configured for the control plane in the downlink and / or uplink directions between the UPF and the base station, or a predefined bitmap. Each first activation indicator (Ind) bit indicates the activation or deactivation of a QoS flow. When the value of this bit is set to 1, the corresponding QoS flow is activated; when the value of this bit is set to 0, the corresponding QoS flow is deactivated. The predefined method includes: sequentially assigning each bit in the bitmap from high to low or from low to high, in descending order of the QoS flow ID (QFI) value (PDU Type (=7), see Table 9). The length of the bitmap depends on the number of QoS flows. When the configuration parameter set or QoS parameter set related to a service feature changes, the UPF sends the new downlink and / or uplink service feature or QoS parameter information to the base station by including this type of PDU in the GTP-U container. In the base station, specifically:

[0109] Setting each QoS flow in PDU Type (=6) or PDU Type (=7) to an activated state or a deactivated state according to the first activation indication corresponding to the QoS flow;

[0110] In particular, in the 5G system, these service feature parameters are configured and sent in units of QoS flow, and the GTP-U Container is also sent in units of QoS flow, so this PDU type includes a QoS flow identifier, which is the identifier of this QoS flow.

[0111] Table 8 Configuration parameter set or QOS parameter set related to service features transmitted based on user plane protocol (PDU Type (=6))

[0112] Table 9 Configuration parameter set or QOS parameter set related to service features transmitted based on user plane protocol (PDU Type (=7))

[0113] In particular, the existing PDU type can be further expanded based on the existing PDU type to transmit service feature information between the user plane function (UPF) and the base station. For specific expansion methods, please refer to the solutions in Tables 6 / 7 / 8 / 9 above.

[0114] In particular, the above method is also applicable to the Xn interface, supporting dynamic changes in service characteristics or QoS parameters between base stations, namely:

[0115] On the one hand, one or more sets of service features or QoS parameter set information, or one or more pieces of QoS flow information are configured through the control plane (XNAP protocol) of the Xn interface; wherein the configuration includes at least one of the following information: QoS parameter set information of the QoS flow, QoS parameter set identification information, QoS parameter set status information, QoS parameter information of the QoS flow, QoS flow identification information, and QoS flow status information;

[0116] On the other hand, based on the GTP-U Container, a base station sends service characteristics or QoS parameter information, or QoS flow information to another base station; the information includes at least one of the following information: QoS parameter set identification information, QoS parameter set status information, QoS flow identification information, and QoS flow status information.

[0117] In practice, QoS flow to DRB mapping is involved within the RAN to support changes in service characteristics, such as dynamic relocation (mapping relocation). In the 5G mobile communication system, the RAN receives the QoS flow and its QoS parameter configuration information during the PDU session establishment and modification process, and then establishes or modifies the DRB on the Uu interface user plane, and establishes a mapping relationship between the QoS flow and the DRB. As shown in Figure 6, this is the 3GPP Uu interface user plane protocol stack architecture diagram (for details, please refer to the 3GPP standard protocol 38.300), where the establishment and modification of the DRB includes the establishment or modification of the SDAP protocol layer or entity, the PDCP protocol layer or entity, the RLC protocol layer or entity, and / or the MAC protocol layer or entity. For details, please refer to the information element (IE) Radio Bearer Configuration (RadioBearerConfig) in 38.331 and the sub-information units it contains. The technical requirements related to the establishment and modification of DRB, and the mapping relationship between QoS flow and DRB are:

[0118] 1. A protocol data unit session (PDU session) can have one or more QoS flows, which can correspond to one or more DRBs; however, a DRB can only be associated with one PDU session;

[0119] 2. The protocol stipulates that a QoS flow must and can only be mapped to one DRB. Multiple QoS flows can be mapped to the same DRB. However, the protocol can actually implement the function of mapping a QoS flow to multiple DRBs.

[0120] 3. All DRB parameters are statically configured through RRC messages on the Uu interface control plane;

[0121] 4. The protocol stipulates that each DRB is established to support a specific type or category of QoS requirements and has at least one QoS flow mapped to it. Multiple QoS flows with the same or similar QoS parameters can be mapped to the same DRB. However, it is actually possible to configure an empty DRB, that is, no QoS flow is mapped to the DRB.

[0122] 5. Each DRB is associated with a PDCP protocol entity and can be further associated with one or more RLC entities, but all RLC entities are targeted at the same QoS requirements, namely the QoS requirements corresponding to the DRB.

[0123] 6. If the PDU session associated with a DRB is configured with the sdap-HeaderDL parameter, reflective mapping and relocation of other QoS flows to the DRB can be achieved.

[0124] In order to meet the above technical requirements, the following technical solutions are adopted:

[0125] Example 4

[0126] In some embodiments, the first network node is a user equipment, and the message based on the user plane protocol includes a control protocol data unit control PDU. When the control PDU is a service data adaptation protocol SDAP control PDU, a packet data convergence protocol PDCP control PDU, or an RLC control PDU, the control PDU includes at least one of the following: a second protocol data unit type, the DRB parameters, and a third activation indication corresponding to the DRB parameters.

[0127] Specifically, since the service flow QOS flow to the RAN side involves changes in DRB parameters, the base station transmits the DRB parameters (including the ID of the DRB parameters) and / or the third activation indication corresponding to the DRB parameters to be changed (for example, activating the DRB parameters) through the user plane protocol to determine which DRB parameters need to be dynamically changed to reduce the delay of dynamically changing the parameter set. Furthermore, different configuration information or data transmission content can be distinguished by the protocol data unit type, so that the user equipment and the base station can understand more fine-grained data information.

[0128] The following is a detailed explanation using a practical example. Taking the 5G RAN system as an example, when the configuration parameter set or QoS parameter set related to the service characteristics corresponding to the QoS flow changes, or the status of the QoS flow changes, within the RAN system, the base station can dynamically adjust the DRB parameters through the Control PDU of the user plane protocol, thereby supporting the dynamic change of the configuration parameter set or QoS parameter set related to the service characteristics on the Uu interface. As a specific example, the method of dynamically adjusting the PDCP protocol or entity-related configuration parameters through the PDCP Control PDU includes at least one of the following:

[0129] Method 1: Use different types of Control PDUs (such as SDAP control PDU, PDCP control PDU, and RLC control PDU) to adjust different parameters or groups of parameters, where the Control PDU includes at least one of the following information: PDU Type and the DRB parameter (actually the adjusted value of the DRB parameter). As an example, the Control PDU is shown in Figure 7:

[0130] Among them, PDU Type: is used to indicate the type of control information in the PDCP Control PDU, for example, to adjust a certain parameter type. Parameter: is used to indicate the adjustment value of the DRB parameter. The length of this field depends on the actual requirements of the parameter type. The number of bits and bytes required for different types of parameters may be different; in particular, it may also include a group, i.e., multiple parameters. The adjusted DRB parameter types or DRB parameters include but are not limited to the following DRB parameters or DRB parameter types: discard time (discardTimer), uplink PDCP sequence size (pdcp-SN-SizeUL), downlink PDCP sequence size (pdcp-SN-SizeDL), time record (t-Reordering), and out-of-order delivery (outOfOrderDelivery).

[0131] Method 2: Multiple parameters are adjusted simultaneously in a Control PDU, where the Control PDU includes at least one of the following information: PDU Type, a predefined third activation indicator corresponding to the DRB parameter, a bitmap indicating whether the third activation indicator corresponding to the DRB parameter has an adjustment value for each parameter type, and adjustment values ​​for one or more parameter types. An example of a Control PDU is shown in Figure 8.

[0132] The second protocol data unit type PDU Type is used to indicate the type of control information in the PDCP Control PDU, for example, to adjust multiple parameter types at the same time.

[0133] Third activation indication Ind: The third activation indication bit (ind) at each position is predefined to correspond to a parameter type. If the ind bit is set to 1, it indicates that the Control PDU includes the adjustment value of the parameter type; if the ind bit is set to 0, it indicates that the Control PDU does not include the adjustment value of the parameter type. The number of ind bits depends on the number of predefined parameter types. The predefined corresponding parameter types include but are not limited to the following parameter types: discard time (discardTimer), uplink PDCP sequence size (pdcp-SN-SizeUL), downlink PDCP sequence size (pdcp-SN-SizeDL), reordering timer (t-Reordering), and out-of-order delivery (outOfOrderDelivery).

[0134] The DRB parameters Parameter 1 / 2 / 3... correspond, in order, to the adjusted values ​​of one or more parameters whose third activation indication (ind) bit is set to 1. The length of this field depends on the number of parameters whose ind bit is set to 1 and the parameter type. Different parameter types may require different numbers of bits and bytes.

[0135] For example, the ind bit reserves five parameter types in sequence: discardTimer, pdcp-SN-SizeUL, pdcp-SN-SizeDL, t-Reordering, and outOfOrderDelivery. If the discardTimer and t-Reordering parameters need to be modified in a Control PDU, the schematic diagram of the Control PDU is shown in Figure 9.

[0136] In particular, for the dynamic adjustment of parameters corresponding to the RLC protocol layer or entity, a method similar to that of the PDCP protocol layer and entity may also be adopted. That is, one or more related parameters may be adjusted through different types of RLC control PDUs, including but not limited to the following parameter types: SN-FieldLengthAM (acknowledgement mode sequence number field length), T-PollRetransmit (poll retransmit timer), sn-FieldLength (sequence number field length), t-Reassembly (downlink AM) (reassembly timer), SN-FieldLengthUM (uplink) (acknowledgement mode sequence number field length), SN-FieldLengthUM (downlink) (acknowledgement mode sequence number field length), T-Reassembly (downlink UM) (reassembly timer), prioritizedBitRate (prioritized bit rate), and bucketSizeDuration (token bucket size duration).

[0137] In particular, for a certain DRB, gN can enable it to support dynamic changes of DRB parameters through the control plane RRC message: if enabled, the DRB parameters can be dynamically adjusted using the above method for the DRB; otherwise, the DRB parameters cannot be dynamically adjusted using the above method.

[0138] Example 5

[0139] In some embodiments, the first network node is a user equipment, and the message based on the user plane protocol includes a control protocol data unit control PDU. When the control PDU is a media access control element MAC CE, the control PDU includes at least one of the following: the DRB parameters, the logical channel identifier LCID, the length value, the protocol entity type, the entity identifier and the third activation indication corresponding to the DRB parameters.

[0140] Specifically, due to changes in the configuration parameter set or QoS parameter set related to service characteristics, the service flow QOS flow will bring about changes in DRB parameters when it reaches the RAN side. In this way, the base station transmits the DRB parameters (including the ID of the DRB parameters) and / or the third activation indication corresponding to the DRB parameters to be changed (for example: activating the DRB parameters) through the user plane protocol to determine which DRB parameters need to be dynamically changed to reduce the delay of dynamically changing the parameter set. Different configuration information or data transmission content can be further distinguished by the protocol data unit type, so that the user equipment and the base station can understand more fine-grained data information. The difference from Example 4 is that the control PDU in Example 5 is the media access control element MAC CE.

[0141] The following is a detailed description using an actual example. The method of dynamically adjusting DRB parameters through MAC CE may include at least one of the following:

[0142] Method 1: Use different types of MAC CEs to adjust different parameters or groups of parameters. The MAC CE includes at least one of the following information: logical channel identifier (LCID), length (L), protocol entity type, entity identifier, and parameter adjustment value. An example of a MAC CE is shown in Figure 10:

[0143] The logical channel identifier (LCID) is used to indicate the type of the MAC CE, such as the type of the parameter to be adjusted. The length of the LCID may also include a 1-byte or 2-byte enhanced logical channel identifier (eLCID) (see 3GPP 38.321 for details).

[0144] Length value L: used to indicate the length of the MCE (see 3GPP38.321 protocol for details); Entity Type: used to indicate one of the SDAP, PDCP, and RLC entity types; Entity identity: used to indicate the relevant SDAP, PDCP, and RLC entity identifiers, or the associated DRB identifiers; DRB parameter Parameter: used to indicate the adjusted or updated value of the parameter. The length of this field depends on the actual requirements of the parameter type. The number of bits and bytes required for different types of parameters may be different. In particular, a group, i.e., multiple parameters, may also be included. The parameter types that are adjusted or updated include, but are not limited to, the following parameter types: PDCP protocol and entity-related parameters and RLC protocol and entity-related parameters; the PDCP protocol and entity-related parameters include at least one of the following: discardTimer, pdcp-SN-SizeUL, pdcp-SN-SizeDL, t-Reordering, and outOfOrderDelivery. The RLC protocol and entity-related parameters include at least one of the following: SN-FieldLengthAM, T-PollRetransmit, sn-FieldLength, t-Reassembly (downlink AM), SN-FieldLengthUM (uplink), SN-FieldLengthUM (downlink), T-Reassembly (downlink UM), prioritizedBitRate, and bucketSizeDuration.

[0145] Method 2: Multiple parameters are adjusted simultaneously in a single MAC CE. The MAC CE includes at least one of the following information: LCID, L, protocol entity type, entity identifier, predefined bitmap information indicating whether each parameter type has an adjustment value, and adjustment values ​​for one or more parameter types. Specifically, a single MAC CE may include one or more protocol entities and adjustment values ​​for one or more parameter types for one or more protocol entities. An example of a MAC CE is shown in Figure 11.

[0146] Wherein: LCID, L, entity type (Entity Type), entity identity (Entity identity), the adjusted parameter type is the same as described above; Ind: the ind bit position is predefined to correspond to a parameter type. If the ind bit is set to 1, it means that the Control PDU includes the adjustment value of the parameter type; if the ind bit is set to 0, it means that the Control PDU does not include the adjustment value of the parameter type; the number of ind bits depends on the predetermined number of parameter types.

[0147] The DRB parameters Parameter1 / 2 / 3... correspond, in order, to the adjustment values ​​of one or more parameters whose ind bits are set to 1. The length of this field depends on the number of parameters whose ind bits are set to 1 and the parameter type. Different parameter types may require different numbers of bits and bytes.

[0148] In particular, for a certain DRB, gN can enable it to support dynamic changes of DRB parameters through the control plane RRC message: if enabled, the DRB parameters can be dynamically adjusted using the above method for the DRB; otherwise, the DRB parameters cannot be dynamically adjusted using the above method.

[0149] In order to support the dynamic change requirements of service features and QoS parameters in the RAN, especially the requirements of dynamically changing service features or QoS parameters received from the CN in a semi-static manner, the present disclosure provides the following solutions:

[0150] Example 6

[0151] In some embodiments, the first network node is a user device, and the user device receives a fourth message based on a control plane protocol, wherein the fourth message includes at least one of the following: a mapping relationship between the second QoS flow and the DRB and status information corresponding to the DRB; receiving a first message sent by the second network node of configuration parameters related to at least one of service characteristics, quality of service, and data radio bearer (DRB), wherein the first message is a message based on the user plane protocol, and the message based on the user plane protocol includes a control protocol data unit control PDU, and the control PDU includes at least one of the following: configuration information for adjusting the second QOS flow and the DRB, and a third activation indication corresponding to the DRB. The configuration information of adjusting the second QOS flow and DRB includes at least one of the following operations: indicating whether to activate a DRB through a user plane message; adjusting the mapping relationship between the second QoS flow and the DRB by sending a downlink SDAP PDU; when the second QoS flow relocation results in no QoS flow being mapped to a DRB, or only one or more deactivated second QoS flows mapping the DRB, the DRB is set to a deactivated state; setting a DRB to a deactivated state through a user plane message; canceling the mapping relationship between one or more second QoS flows and the DRB through a user plane message. When the third activation indication is used to indicate the activation or deactivation of the DRB corresponding to the second QOS flow ID, one second QOS flow ID corresponds to multiple DRBs, and the multiple DRBs corresponding to each second QOS flow ID are configured with different configuration parameters.

[0152] Specifically, the user equipment receives the mapping relationship information between the second QoS flow and the DRB and the status information (activated state or deactivated state) corresponding to the DRB from the base station based on the control plane protocol, establishes a mapping relationship between the second QoS flow and multiple DRBs, and also establishes a mapping relationship between the second QoS flow and the second QoS flow ID corresponding to each second QoS flow and the multiple DRBs. At the base station end, the base station is configured with multiple parameter sets corresponding to each second QoS flow ID and related to at least one of the service characteristics, service quality, and data radio bearer (DRB), such as {parameter set 1, parameter set 2}, and then configures multiple parameter sets and multiple DRBs as a mapping relationship, such as: parameter set 1 corresponds to DRB1, parameter set 2 corresponds to DRB2, then when the base station configures the user equipment with the initial third activation indication corresponding to the DRB, the base station will instruct the user equipment to activate or deactivate a DRB. Since each DRB has a corresponding parameter set, that is, the initial indication is configured to instruct the user equipment to activate or deactivate the parameter set corresponding to the DRB, and then receives the message based on the user plane protocol sent by the base station, so that the user equipment activates or deactivates the QOS flow according to the base station indication. The new DRB in the ID is then adjusted, and the configuration information of the second QOS flow and the DRB is reversely mapped to the corresponding second QOS flow, that is, the purpose of dynamically changing the parameter set in a QOS flow is achieved; by dynamically changing the parameter set in this way, signaling overhead can be saved.

[0153] The following is a detailed description using a practical example. To support the dynamic change requirements of service features and QoS parameters, especially the requirements for dynamic change of service features or QoS parameters received from the CN in a semi-static manner, the present disclosure discloses the following processing method in the RAN (including the UE):

[0154] 1. Establish or modify one or more DRBs through control plane processes and / or messages, which include at least one of the following information: DRB identification information, DRB status information (activated or deactivated), and QoS flow-DRB mapping information;

[0155] 2. Dynamically activate or deactivate DRB through user plane messages and / or processes, which include at least one of the following information: DRB identification information, DRB status information, and QoS flow and DRB mapping relationship information.

[0156] Specifically, taking the 5G RAN system as an example, in the control plane, referring to the Uu interface control plane protocol (Radio Resource Control (RRC) protocol specification, see 3GPP standard protocol 38.331 for details), in response to the service establishment or modification process, that is, the PDU session establishment and modification process, the RRC reconfiguration process and related messages will be triggered to establish one or more DRBs and configure them to be activated or deactivated, and further include at least one of the following operations and related information:

[0157] If a second QoS flow is configured with multiple service features or QoS parameter sets, one or more DRBs are established or modified. These DRBs can each support one or more service features or QoS parameter sets of the second QoS flow. A mapping relationship is established between the second QoS flow and these DRBs. The mapping method includes at least one of the following methods:

[0158] The second QoS flow can be mapped to multiple DRBs, but only one DRB is set to active at a time. That is, for a second QoS flow, only one mapping relationship with the DRB is active and valid. For example, only the DRB corresponding to the activation parameter set is configured as active, and the DRB corresponding to the deactivation parameter set is configured as deactivated.

[0159] Only the DRB corresponding to one activation parameter set is configured as activation state, and a mapping relationship is established between the second QoS flow and the DRB; the DRBs corresponding to other deactivation parameter sets are configured as deactivation state and are idle state, that is, the second QoS flow is not mapped to these DRBs.

[0160] Set the value of the "downlink SDAP header (sdap-HeaderDL)" of the service data adaptation protocol (SDAP) entity corresponding to the DRB to "present", that is, the SDAP PDU corresponding to the DRB will include the SDAP header (SDAP header);

[0161] In particular, for a PDU session, a default DRB can be configured, which is always active. Typically, the default QoS flow is mapped to the default DRB.

[0162] The configuration of the mapping relationship between the second QoS flow and the DRB includes downlink and / or uplink directions.

[0163] In one implementation, the RRC message is sent by the base station to the UE, and the RRC message is exchanged between the base station and the UE. Based on the modifications made to the ASN.1 of the RRC protocol, in the RRC message, a DRB status information "drbStatus" can be added in the information element "DRB-ToAddMod" for each added or modified DRB, and at the same time, the restriction that the second QoS flow can only be mapped to one DRB is removed.

[0164] In the user plane protocol

[0165] In one implementation, after completing the above-mentioned control plane configuration, when the state of the second QoS flow changes, within the RAN system, the base station may adjust the configuration information of the second QoS flow and the DRB through user plane messages and procedures, wherein the configuration information includes the adjustment configuration / mapping relationship between the QoS flow and the DRB, and / or the state of the QoS flow and / or the DRB, thereby supporting dynamic changes in service characteristics on the Uu interface. The configuration information includes at least one of the following:

[0166] 1. When the service characteristics or QoS parameter set changes, the original parameter set and its corresponding DRB are set to the deactivated state, the new parameter set and its corresponding DRB are set to the activated state, and / or the mapping relationship between the second QoS flow and the DRB is relocated;

[0167] 2. When the state of the second QoS flow changes from active to deactivated, the DRB with which it has a mapping relationship may be set to deactivated, and / or the mapping relationship between the second QoS flow and the DRB may be relocated;

[0168] 3. When the state of the second QoS flow changes from the deactivated state to the activated state, the DRB to which it will have a mapping relationship will be set to the activated state, and / or the mapping relationship between the second QoS flow and the DRB will be relocated.

[0169] In one implementation, for a 5G RAN system, adjusting the configuration information of the second QoS flow and the DRB includes at least one of the following operations:

[0170] 1. Activate a DRB via a user plane message. Specifically, the DRB can be activated or deactivated by sending a predefined SDAP Control PDU, PDCP Control PDU, RLC Control PDU, or MAC CE (Control Element) instruction. The activation or deactivation instruction method includes at least one of the following methods:

[0171] 1) The message includes one or more DRB identities or indexes and activation or deactivation indication information;

[0172] 2) Include a predefined bitmap in the message, where each bit indicates activation or deactivation of a DRB. When the bit value is set to 1, the corresponding DRB is activated; when the bit value is set to 0, the corresponding DRB is deactivated. The predefined method includes: Sequentially assigning each bit in the bitmap, in descending order or descending order, to the DRB identity value.

[0173] 2. Send a downlink SDAP PDU through a DRB, set the RDI field in the SDAP header to 1, set the QFI field to the QoS Flow Identity of a QoS flow, and redirect a QoS flow to the DRB;

[0174] 3. When QoS flow relocation results in no QoS flow being mapped to a DRB, or only one or more deactivated QoS flows are mapped to the DRB, the DRB can be set to the deactivated state;

[0175] 4. Set a DRB to deactivated state through user plane messaging;

[0176] 5. Cancel the mapping relationship between one or more QoS flows and DRBs through user plane messages, such as when the QoS flow or DRB is deactivated;

[0177] 6. Adjust the mapping between QoS flows and DRBs, including downlink and / or uplink directions.

[0178] The user plane message is sent by the base station to the UE, and the user plane message is exchanged between the base station and the UE.

[0179] As shown in Figure 12, the second QoS flow is configured with {parameter set 1, parameter set 2}; DRB 1 is established corresponding to parameter set 1, and DRB2 is established corresponding to parameter set 2; the activation parameter set of the second QoS flow is changed from parameter set 1 to parameter set 2. Before the change, DRB 1 is activated and DRB 2 is deactivated; after the change, DRB 2 is activated and DRB 1 is deactivated; the second QoS flow 1 is relocated from DRB1 to DRB2.

[0180] Example 7

[0181] In some embodiments, the first network node is a user device, and the user device receives a fourth message based on a control plane protocol, wherein the fourth message includes at least one of the following: mapping relationship information between the second QoS flow and the DRB and status information corresponding to the DRB; receiving a first message sent by the second network node of configuration parameters related to at least one of service characteristics, quality of service, and data radio bearer (DRB), wherein the first message is a message based on the user plane protocol, and the message based on the user plane protocol includes a control protocol data unit control PDU, and the control PDU includes at least one of the following: configuration information for adjusting the second QOS flow and the DRB, and a third activation indication corresponding to the DRB. The configuration information of adjusting the second QOS flow and DRB includes at least one of the following operations: indicating whether to activate a DRB through a user plane message; adjusting the mapping relationship between the second QoS flow and the DRB by sending a downlink SDAP PDU; when the second QoS flow relocation results in no QoS flow being mapped to a DRB, or only one or more deactivated second QoS flows mapping the DRB, the DRB is set to a deactivated state; setting a DRB to a deactivated state through a user plane message; canceling the mapping relationship between one or more second QoS flows and the DRB through a user plane message. When the third activation indication is used to indicate the activation or deactivation of the DRB corresponding to the second QOS flow ID, one second QOS flow ID corresponds to multiple DRBs, and the multiple DRBs corresponding to each second QOS flow ID are configured with different configuration parameters.

[0182] Specifically, the user equipment receives mapping relationship information between at least one of the second QoS flows and the DRB and status information corresponding to the DRB from the base station based on the control plane protocol, establishes a mapping relationship between at least one of the second QoS flows and a DRB, and may also establish a mapping relationship between the second QoS flow ID corresponding to at least one of the second QoS flows and a DRB. At the base station end, the base station is configured with service features corresponding to at least one second QoS flow ID. When the service features change, it is only necessary to adjust the configuration information of the second QOS flow and the DRB and / or activate or deactivate the DRB through the third activation indication to achieve the change of the service features corresponding to at least one second QoS flow. By dynamically changing the service features in this way, signaling overhead can be saved.

[0183] The following is a detailed description using a practical example. In order to support the dynamic change requirements of service features and QoS parameters in the radio interface (Uu interface) between the network-side node in the RAN and the UE, especially the requirements for dynamic change of service features or QoS parameters received from the CN in a semi-static manner, the present disclosure discloses the following processing method in the RAN (including the UE):

[0184] 1. Establish or modify one or more DRBs through control plane processes and / or messages, which include at least one of the following information: DRB identification information, DRB status information (activated or deactivated), and QoS flow and DRB mapping relationship information.

[0185] 2. Dynamically activate or deactivate DRB through user plane messages and / or processes, which include at least one of the following information: DRB identification information, DRB status information, and QoS flow and DRB mapping relationship information.

[0186] Specifically, taking the 5G RAN system as an example, on the control plane, if one or more second QoS flows are configured, where the second QoS flows are activated or deactivated, one or more DRBs are established or modified. These DRBs can respectively support one or more second QoS flows, and the mapping relationship information between these second QoS flows and these DRBs is configured. The mapping information includes at least one of the following methods:

[0187] 1. Multiple second QoS flows can be mapped to one DRB;

[0188] 2. A second QoS flow can also be mapped to multiple DRBs, but only one DRB is active at a time.

[0189] 3. A second QoS flow may not be mapped to any DRB, for example, a second QoS flow that is set to be deactivated;

[0190] 4. A DRB is not mapped to any second QoS flow and is in the idle state. The DRB is set to the deactivated state.

[0191] 5. If there is no second QoS flow, or only a deactivated second QoS flow is mapped to a DRB, the DRB can be set to the deactivated state;

[0192] 6. If there is at least one active second QoS flow mapped to a DRB, the DRB will be set to active.

[0193] Set the value of "sdap-HeaderDL" of the SDAP entity corresponding to the DRB to "present", that is, the SDAP PDU corresponding to the DRB will include the SDAP header;

[0194] In particular, for a PDU session, a default DRB can be configured, which is always active. Typically, a default QoS flow is mapped to the default DRB.

[0195] The configuration of the mapping relationship between the second QoS flow and the DRB includes downlink and / or uplink directions.

[0196] In the user plane protocol

[0197] In one implementation, after completing the above-mentioned control plane configuration, when the state of the second QoS flow changes, within the RAN system, the base station may adjust the configuration information of the second QoS flow and the DRB through user plane messages and procedures, wherein the configuration information includes the adjustment configuration / mapping relationship between the QoS flow and the DRB, and / or the state information of the QoS flow and / or the state information of the DRB, thereby supporting dynamic changes in service characteristics on the Uu interface. The configuration information includes at least one of the following:

[0198] 1. When the service characteristics or QoS parameter set changes, the original parameter set and its corresponding DRB are set to the deactivated state, the new parameter set and its corresponding DRB are set to the activated state, and / or the mapping relationship between the second QoS flow and the DRB is relocated;

[0199] 2. When the state of the second QoS flow changes from active to deactivated, the DRB with which it has a mapping relationship may be set to deactivated, and / or the mapping relationship between the second QoS flow and the DRB may be relocated;

[0200] 3. When the state of the second QoS flow changes from the deactivated state to the activated state, the DRB to which it will have a mapping relationship will be set to the activated state, and / or the mapping relationship between the second QoS flow and the DRB will be relocated.

[0201] In one implementation, for a 5G RAN system, adjusting the configuration information of the second QoS flow and the DRB includes at least one of the following operations:

[0202] 1. Activate a DRB via a user plane message. Specifically, the DRB can be activated or deactivated by sending a predefined SDAP Control PDU, PDCP Control PDU, RLC Control PDU, or MAC CE (Control Element) instruction. The activation or deactivation instruction method includes at least one of the following methods:

[0203] 1) The message includes one or more DRB identities or indexes and activation or deactivation indication information;

[0204] 2) Include a predefined bitmap in the message, where each bit indicates activation or deactivation of a DRB. When the bit value is set to 1, the corresponding DRB is activated; when the bit value is set to 0, the corresponding DRB is deactivated. The predefined method includes: Sequentially assigning each bit in the bitmap, in descending order or descending order, to the DRB identity value.

[0205] 2. Send a downlink SDAP PDU through a DRB, set the RDI field in the SDAP header to 1, set the QFI field to the QoS Flow Identity of a QoS flow, and redirect a QoS flow to the DRB;

[0206] 3. When QoS flow relocation results in no QoS flow being mapped to a DRB, or only one or more deactivated QoS flows are mapped to the DRB, the DRB can be set to the deactivated state;

[0207] 4. Set a DRB to deactivated state through user plane messaging;

[0208] 5. Cancel the mapping relationship between one or more QoS flows and DRBs through user plane messages, such as when the QoS flow or DRB is deactivated;

[0209] 6. Adjust the mapping between QoS flows and DRBs, including downlink and / or uplink directions.

[0210] The user plane message is sent by the base station to the UE, and the user plane message is exchanged between the base station and the UE.

[0211] As shown in Figure 13, a mapping relationship is established between QoS flow 1 / 2 and DRB 1, a mapping relationship is established between QoS flow 3 and DRB 2, and a mapping relationship is established between QoS flow 4 and DRB 3. When QoS flow 1 / 2 changes from an activated state to a deactivated state, and QoS flow 4 changes from a deactivated state to an activated state, before the change, DRB 1 is activated and DRB 3 is deactivated; after the change, DRB 3 is activated and DRB 1 is deactivated.

[0212] Example 8

[0213] In some embodiments, the first network node is a user equipment, and receives a fifth message based on the control plane protocol, the fifth message including at least one of the following: mapping relationship information between the second QoS flow and the DRB, information about the DRB-associated PDCP entity, information about the DRB-configured RLC entity and status information corresponding to the RLC entity, and mapping relationship information between the PDCP entity and the RLC entity, and receives a first message sent by the second network node of configuration parameters related to at least one of service characteristics, quality of service, and data radio bearer (DRB), wherein the first message is a message based on the user plane protocol, the message based on the user plane protocol includes a control protocol data unit control PDU, and the control PDU includes: a fourth activation indication corresponding to the radio link control RLC entity.

[0214] Specifically, the user equipment receives at least one of the following information from the base station based on the control plane protocol: mapping relationship information between the second QoS flow and the DRB, information about the DRB-associated PDCP entity, information about the DRB-configured RLC entity and status information corresponding to the RLC entity, and mapping relationship information between the PDCP entity and the RLC entity, and establishes a mapping relationship between the second QoS flow and the DRB. It can also establish a mapping relationship between the second QoS flow ID corresponding to each second QoS flow and multiple DRBs. On the base station side, the base station is configured with multiple parameter sets corresponding to each second QoS flow ID and related to at least one of the service characteristics, service quality, and data radio bearer (DRB), such as {parameter set 1, parameter set 2}, and then according to the QoS The mapping relationship between flow and DRB and the number of RLC entities configured by DRB establishes a mapping relationship between multiple parameter sets and multiple RLC entities, such as: parameter set 1 corresponds to RLC entity 1, parameter set 2 corresponds to RLC entity 2. Then, when the base station configures the initial status information corresponding to the RLC entity to the user equipment, the base station will instruct the user equipment to activate or deactivate an RLC entity. Since each RLC entity has a corresponding parameter set, the initial indication is configured to instruct the user equipment to activate or deactivate the parameter set corresponding to the RLC entity, and then receive the user plane protocol-based message sent by the base station. In this way, the user equipment activates or deactivates the new RLC entity in the QOS flow ID according to the base station indication, and then adjusts the information of the RLC entity, and reversely maps the RLC entity to the corresponding second QOS flow, that is, realizing the purpose of dynamically changing the parameter set in a QOS flow; dynamically changing the parameter set in this way can save signaling overhead.

[0215] The following is a detailed description using a practical example. In order to support the dynamic change requirements of service features and QoS parameters, especially the requirements for dynamic changes of service features or QoS parameters or DRB parameters received from the CN in a semi-static manner, the present disclosure discloses the following method for adjusting the mapping or association relationship between a DRB-related PDCP entity and an RLC entity.

[0216] 1. A DRB can be established or modified via a control plane message (fifth message), including at least one of the following operations and related information:

[0217] 1) Establish a mapping relationship between the QoS flow and the DRB;

[0218] 2) Establish a PDCP entity associated with the DRB;

[0219] 3) DRB configuration RLC entity information (establishing one or more RLC entities associated with the DRB, configuring state information corresponding to the RLC entity (each RLC entity is in an activated state or a deactivated state), where multiple RLC entities can support different service features or QoS parameter requirements;

[0220] 4) Mapping relationship information between PDCP entity and RLC entity (establishing a mapping or association relationship between the PDCP entity and one or more RLC entities).

[0221] 2. Dynamically activate or deactivate the RLC entity through user plane messages and / or processes, which include at least one of the following information: DRB identification information, RLC entity identification information, and a fourth activation indication corresponding to the RLC entity (RLC entity status information (activated state or deactivated state)).

[0222] On the control surface

[0223] With reference to the Uu interface control plane protocol (Radio Resource Control (RRC) protocol specification, see 3GPP standard protocol 38.331 for details), in response to the service establishment or modification process, that is, the PDU session establishment and modification process, the RRC reconfiguration process and related messages will be triggered to establish or modify a DRB and the mapping relationship between the second QoS flow and the DRB. At the same time, a PDCP entity and one or more RLC entities associated with the DRB are also established or modified, and a fourth activation indication corresponding to the RLC entity is configured (each RLC entity is in an activated state or a deactivated state), and further includes at least one of the following operations and related information:

[0224] 1. If a mapping relationship exists between a second QoS flow and the DRB, and multiple service features or QoS parameter sets are configured, each of the one or more RLC entities may support the service features or QoS parameter sets of the one or more second QoS flows. The state of the RLC entity is configured according to the state of the parameter sets supported by the RLC entity: the RLC entity corresponding to the activation state parameter set is configured to the activation state, and the RLC entity corresponding to the deactivation state parameter set is configured to the deactivation state, as indicated by a fourth activation indication.

[0225] 2. If there are multiple second QoS flows associated with the DRB, where the second QoS flows are in an activated state or a deactivated state, each of the one or more RLC entities may support one or more second QoS flows. The state of the RLC entity is configured according to the state of the second QoS flows supported by the RLC entity: the RLC entity corresponding to the activated second QoS flow is configured to be in an activated state, and the RLC entity corresponding to the deactivated second QoS flow is configured to be in a deactivated state, as indicated by a fourth activation indication.

[0226] 3. Establish an association (or mapping) between the PDCP entity and the active RLC entity, including downlink and / or uplink directions;

[0227] 4. For DRBs with different functions, one RLC entity may contain one or more RLC entities. Typically, one DRB contains one UM RLC entity (unidirectional), two UM RLC entities (bidirectional), or one AM RLC entity. However, for split DRBs or DRBs supporting duplication, one RLC entity may contain twice the number of RLC entities compared to the normal case.

[0228] 5. Establish an association between a service feature or QoS parameter set and an RLC entity. The association method includes at least one of the following methods:

[0229] 1. Multiple parameter sets or multiple second QoS flows can be associated with one RLC entity;

[0230] 2. A parameter set or a second QoS flow can also be associated with multiple RLC entities, but only one RLC entity is active at a time.

[0231] 3. A parameter set or a second QoS flow may not be associated with any RLC entity, for example, a parameter set or a second QoS flow that is set to a deactivated state;

[0232] 4. An RLC entity is not associated with any parameter set or second QoS flow, the RLC entity is in an idle state, and the RLC entity is set to a deactivated state;

[0233] 5. If only one or more parameter sets in the deactivated state are associated with an RLC entity, the RLC entity may be set to the deactivated state, as indicated by the fourth activation indication;

[0234] 6. If at least one active parameter set is associated with an RLC entity, the RLC entity will be set to the active state, as indicated by the fourth activation indication;

[0235] 7. Configuration of the association between parameter sets and RLC entities, including downlink and / or uplink directions.

[0236] In one implementation, the RRC message is sent by the base station to the UE, and user plane messages are exchanged between the base station and the UE. In the RRC message, status indication information "rlcStatus" can be added for each added or modified RLC entity in the information element "RLC-BearerConfig" and / or conditional restrictions on associated DRB information can be deleted.

[0237] In the user plane protocol

[0238] After completing the above control plane configuration, when the service characteristics or QoS parameter set or DRB parameter set corresponding to the second QoS flow changes, within the RAN system, the base station can dynamically activate or deactivate the RLC entity type through user plane messages, thereby supporting the dynamic change of service characteristics or QoS parameter sets on the Uu interface. Specifically, for the 5G RAN system, at least one of the following operations is included:

[0239] 1. Activate an RLC entity using a fourth activation indication corresponding to the RLC entity in a user plane message. Specifically, activation or deactivation of an RLC entity may be indicated by sending a fourth activation indication included in a predefined SDAP Control PDU, PDCP Control PDU, RLC Control PDU, or MAC CE (Control Element). The activation or deactivation indication method includes at least one of the following methods:

[0240] 1) The message includes the logical channel identity (logicalChannelIdentity) corresponding to one or more RLC entities and the fourth activation indication (i.e., activation or deactivation indication information) activation or deactivation indication information;

[0241] 2) The message includes a fourth activation indication (a predefined bitmap corresponding to each RLC entity), where each bit is used to indicate activation or deactivation of an RLC entity. When the value of the bit is set to 1, the corresponding RLC entity is activated; when the value of the bit is set to 0, the corresponding RLC entity is deactivated. The predefined method includes: sequentially corresponding to each bit in the bitmap from high to low or from low to high in the order of the logicalChannelIdentity value.

[0242] 2. When an RLC entity is set to the deactivated state, the PDCP entity corresponding to its DRB will cancel its association with the RLC entity, i.e., it will not send PDCP PDUs to or receive PDCP PDUs from the RLC entity. Conversely, when an RLC entity is set to the activated state, the PDCP entity corresponding to its DRB will establish an association with the RLC entity, i.e., it will send PDCP PDUs to or receive PDCP PDUs from the RLC entity.

[0243] The user plane message is sent by the base station to the UE, and the user plane message is exchanged between the base station and the UE.

[0244] As shown in Figure 14, the second QoS flow is configured with {parameter set 1, parameter set 2}; parameter set 1 is established for RLC entity 1, and parameter set 2 is established for RLC entity 2; the activation parameter set of the second QoS flow is changed from parameter set 1 to parameter set 2. Before the change, RLC entity 1 is activated and RLC entity 2 is deactivated; after the change, RLC entity 2 is activated and RLC entity 1 is deactivated; QoS flow 1 is relocated from DRB1 to DRB2.

[0245] Embodiment 9

[0246] In some embodiments, the first network node is a user equipment, and receives a fifth message based on the control plane protocol, the fifth message including at least one of the following: mapping relationship information between the second QoS flow and the DRB, information about the DRB-associated PDCP entity, information about the DRB-configured RLC entity and status information corresponding to the RLC entity, and mapping relationship information between the PDCP entity and the RLC entity, and receives a first message sent by the second network node of configuration parameters related to at least one of service characteristics, quality of service, and data radio bearer (DRB), wherein the first message is a message based on the user plane protocol, the message based on the user plane protocol includes a control protocol data unit control PDU, and the control PDU includes: a fourth activation indication corresponding to the radio link control RLC entity.

[0247] Specifically, the user equipment receives at least one of the following information from the base station based on the control plane protocol: mapping relationship information between the second QoS flow and the DRB, information about the DRB-associated PDCP entity, information about the DRB-configured RLC entity and status information corresponding to the RLC entity, and mapping relationship information between the PDCP entity and the RLC entity. A mapping relationship is established between the second QoS flow and the DRB, and a mapping relationship can also be established between the second QoS flow ID corresponding to each second QoS flow and multiple DRBs. On the base station side, service features corresponding to one or more second QoS flow IDs are configured in the base station. When the service features change, it is only necessary to deactivate or deactivate the RLC entity through the fourth activation indication to achieve the change of the service features corresponding to one or more second QoS flows. Dynamically changing the service features in this way can save signaling overhead.

[0248] The following is a detailed description using a practical example. In order to support the dynamic change requirements of service features and QoS parameters, especially the requirements for dynamic changes of service features or QoS parameters or DRB parameters received from the CN in a semi-static manner, the present disclosure discloses the following method for adjusting the mapping or association relationship between a DRB-related PDCP entity and an RLC entity.

[0249] 1. A DRB can be established or modified via a control plane message (fifth message), including at least one of the following operations and related information:

[0250] 1) Establish a mapping relationship between the QoS flow and the DRB;

[0251] 2) Establish a PDCP entity associated with the DRB;

[0252] 3) establishing one or more RLC entities associated with the DRB, and configuring a fourth activation indication corresponding to the RLC entity (each RLC entity is in an activated state or a deactivated state), where the multiple RLC entities may support different service features or QoS parameter requirements;

[0253] 4) Establish a mapping or association relationship between the PDCP entity and one or more RLC entities.

[0254] 2. Dynamically activate or deactivate the RLC entity through user plane messages and / or processes, which include at least one of the following information: DRB identification information, RLC entity identification information, and a fourth activation indication corresponding to the RLC entity (RLC entity status information (activated state or deactivated state)).

[0255] On the control surface

[0256] With reference to the Uu interface control plane protocol (Radio Resource Control (RRC) protocol specification, see 3GPP standard protocol 38.331 for details), in response to the service establishment or modification process, that is, the PDU session establishment and modification process, the RRC reconfiguration process and related messages will be triggered to establish or modify a DRB and the mapping relationship between the second QoS flow and the DRB. At the same time, a PDCP entity and one or more RLC entities associated with the DRB are also established or modified, and a fourth activation indication corresponding to the RLC entity is configured (each RLC entity is in an activated state or a deactivated state), and further includes at least one of the following operations and related information:

[0257] 1. If a mapping relationship exists between a second QoS flow and the DRB, and multiple service features or QoS parameter sets are configured, each of the one or more RLC entities may support the service features or QoS parameter sets of the one or more second QoS flows. The state of the RLC entity is configured according to the state of the parameter sets supported by the RLC entity: the RLC entity corresponding to the activation state parameter set is configured to the activation state, and the RLC entity corresponding to the deactivation state parameter set is configured to the deactivation state, as indicated by a fourth activation indication.

[0258] 2. If there are multiple second QoS flows associated with the DRB, where the second QoS flows are in an activated state or a deactivated state, each of the one or more RLC entities may support one or more second QoS flows. The state of the RLC entity is configured according to the state of the second QoS flows supported by the RLC entity: the RLC entity corresponding to the activated second QoS flow is configured to be in an activated state, and the RLC entity corresponding to the deactivated second QoS flow is configured to be in a deactivated state, as indicated by a fourth activation indication.

[0259] 3. Establish an association (or mapping) between the PDCP entity and the active RLC entity, including downlink and / or uplink directions;

[0260] 4. For DRBs with different functions, one RLC entity may contain one or more RLC entities. Typically, one DRB contains one UM RLC entity (unidirectional), two UM RLC entities (bidirectional), or one AM RLC entity. However, for split DRBs or DRBs supporting duplication, one RLC entity may contain twice the number of RLC entities compared to the normal case.

[0261] 5. Establish an association between a service feature or QoS parameter set and an RLC entity. The association method includes at least one of the following methods:

[0262] 1) Multiple parameter sets or multiple second QoS flows can be associated with one RLC entity;

[0263] 2) A parameter set or a second QoS flow can also be associated with multiple RLC entities, but only one RLC entity is active at a time.

[0264] 3) A parameter set or a second QoS flow may not be associated with any RLC entity, for example, a parameter set or a second QoS flow that is set to a deactivated state;

[0265] 4) An RLC entity is not associated with any parameter set or second QoS flow, the RLC entity is in an idle state, and the RLC entity is set to a deactivated state;

[0266] 5) If only one or more deactivated parameter sets are associated with an RLC entity, the RLC entity may be set to the deactivated state, as indicated by the fourth activation indication;

[0267] 6) If at least one active parameter set is associated with an RLC entity, the RLC entity will be set to an active state, indicated by a fourth activation indication;

[0268] 7) Configuration of the association between parameter sets and RLC entities, including downlink and / or uplink directions.

[0269] In one implementation, the RRC message is sent by the base station to the UE, and user plane messages are exchanged between the base station and the UE. In the RRC message, status indication information "rlcStatus" can be added for each added or modified RLC entity in the information element "RLC-BearerConfig" and / or conditional restrictions on associated DRB information can be deleted.

[0270] In the user plane protocol

[0271] After completing the above control plane configuration, when the service characteristics or QoS parameter set or DRB parameter set corresponding to the second QoS flow changes, within the RAN system, the base station can dynamically activate or deactivate the RLC entity type through user plane messages, thereby supporting the dynamic change of service characteristics or QoS parameter sets on the Uu interface. Specifically, for the 5G RAN system, at least one of the following operations is included:

[0272] An RLC entity is activated by a fourth activation indication corresponding to the radio link control RLC entity in a user plane message. Specifically, the activation or deactivation of an RLC entity can be indicated by sending a fourth activation indication included in a predefined SDAP Control PDU, PDCP Control PDU, RLC Control PDU, or MAC CE (Control Element). The activation or deactivation indication method includes at least one of the following methods:

[0273] 1. The message includes the logicalChannelIdentity corresponding to one or more RLC entities and the fourth activation indication (i.e., activation or deactivation indication information);

[0274] 2. Include a fourth activation indication in the message (a predefined bitmap corresponding to each RLC entity), where each bit is used to indicate activation or deactivation of an RLC entity. When the value of the bit is set to 1, it indicates activation of the corresponding RLC entity; when the value of the bit is set to 0, it indicates deactivation of the corresponding RLC entity. The predefined method includes: sequentially corresponding to each bit in the bitmap from high to low or from low to high in the order of the value of logicalChannelIdentity.

[0275] In one implementation, when an RLC entity is set to a deactivated state, the PDCP entity corresponding to its DRB will cancel its association with the RLC entity, i.e., it will not send PDCP PDUs to or receive PDCP PDUs from the RLC entity. Conversely, when an RLC entity is set to an activated state, the PDCP entity corresponding to its DRB will establish an association with the RLC entity, i.e., it will send PDCP PDUs to or receive PDCP PDUs from the RLC entity.

[0276] The user plane message is sent by the base station to the UE, and the user plane message is exchanged between the base station and the UE.

[0277] As shown in Figure 15, a mapping relationship is established between QoS flow 1 and RLC entity 1, and a mapping relationship is established between QoS flow 2 and RLC entity 2. When QoS flow 1 changes from an activated state to a deactivated state, and QoS flow 2 changes from a deactivated state to an activated state, before the change, RLC entity 1 is activated and RLC entity 2 is deactivated; after the change, RLC entity 2 is activated and RLC entity 1 is deactivated.

[0278] Within the RAN network, as shown in Figure 6, the protocol layers or functional entities corresponding to the Uu interface user plane protocol stack, including the SDAP protocol layer or entity, PDCP protocol layer or entity, RLC protocol layer or entity, and / or MAC protocol layer or entity, may be located in different RAN nodes or RAN subnodes. Taking the 5G system as an example, in dual-link technology, the SDAP protocol layer or entity and PDCP protocol layer or entity are located in one RAN node base station, while the RLC protocol layer or entity and MAC protocol layer or entity are located in another RAN node base station, and the base stations are connected via the Xn interface. In the split RAN architecture, a base station consists of a central unit (CU) and a distributed unit (DU). The SDAP protocol layer or entity and PDCP protocol layer or entity are located in the CU, while the RLC protocol layer or entity and MAC protocol layer or entity are located in the DU, and the CU and DU are connected via the F1 interface. Therefore, on the Xn interface and F1 interface, configuration management processes related to DRB and data transmission processes are involved.

[0279] Basic Principle: Based on the User Plane Part of General Packet Radio Service Tunneling Protocol Extension Header (GTP-UExtension Header), also known as the New Radio Access Network Container (NR RAN Container), a RAN node sends DRB-related configuration information to another RAN node, or an internal RAN sub-node sends DRB-related configuration information to another internal RAN sub-node. Between different network nodes, a User Plane Part of General Packet Radio Service Tunneling Protocol tunnel (GTP-U tunnel) is first established for the DRB through the control plane protocol. Then, the user plane data packets of the DRB are transmitted and carried through the Protocol Data Unit (PDU) of the User Plane Part of General Packet Radio Service Tunneling Protocol (GTP-U). While GTP-U PDUs carry user-plane data packets, the GTP-U Extension Header in the PDUs also carries dynamic DRB configuration information to support dynamic changes in DRB configuration. Furthermore, dynamic changes in DRB configuration can be categorized into two methods: dynamic and semi-static.

[0280] Example 10

[0281] In some embodiments, the first network node is a distribution unit of a base station, and the distribution unit of the base station receives a first message based on a user plane protocol, which is sent by a second network node and contains configuration parameters related to at least one of service characteristics, quality of service, and data radio bearer (DRB). The first message is a message based on the user plane protocol, and the message based on the user plane protocol includes a new radio access network container NR RAN Container, and the NR RAN Container includes at least one of the following: a third protocol data unit type, the DRB parameter, and a fifth activation indication corresponding to the DRB parameter, wherein the fifth activation indication is used to indicate whether the DRB parameter has changed, and the third protocol data unit type is used to indicate the type of control information in the NR RAN Container.

[0282] Specifically, changes in the configuration parameter set or QoS parameter set related to service characteristics, and the service flow QOS flow to the network side of the wireless access network RAN ​​will bring about changes in the DRB parameters. In this way, the central unit of the base station transmits the DRB parameters (including the ID of the DRB parameters) and / or the fifth activation indication corresponding to the DRB parameters to be changed (for example: activating the DRB parameters) through the user plane protocol to determine which DRB parameters need to be dynamically changed to reduce the delay of dynamically changing the parameter set. Furthermore, different configuration information or data transmission content can be distinguished by the protocol data unit type, so that the distributed units and the central unit of the base station can understand more fine-grained data information.

[0283] The following is a detailed description using a practical example. Taking the F1 interface as an example, to support dynamic adjustment of DRB parameters, the method of dynamically adjusting DRB parameters through the NR RAN Container may include at least one of the following:

[0284] 1. In some embodiments, based on the NR RAN Container and with reference to the New Radio NR user plane protocol (NR user plane protocol, see 3GPP standard protocol 38.425 for details), a PDU type (PDU type = 8) is predefined to transmit the parameters of the DRB that needs to be adjusted, wherein a predefined bitmap is used to indicate whether a certain DRB parameter has changed. If the ind bit is set to 1, it indicates that the value of the parameter has changed; if the ind bit is set to 0, it indicates that the value of the parameter has not changed. The length of the bitmap depends on the number of predefined parameters. If a parameter has changed, the changed value of the parameter, i.e. parameter1 / 2 / 3, is further included later. These parameter values ​​correspond to multiple parameters with the ind bit set to 1 in sequence. As shown in Table 10, this is a specific implementation scheme of the PDU format. When the DRB parameter is sent and changed, the base station-CU sends the new DRB parameter information to the base station-DU by including the NR RAN Container of this PDU Type in the PDU of the GTP-U.

[0285] The DRB QoS parameters or DRB-related parameters include at least but not limited to the following parameters:

[0286] 1. DRB QoS parameters include the following:

[0287] 1) Non-dynamic 5QI related parameters;

[0288] 2) Dynamic 5QI (Dynamic5QI) related parameters;

[0289] 3) Next Generation Radio Access Network (NG-RAN) Allocation and Retention Priority;

[0290] 4) Guaranteed Bit Rate Quality of Service Flow Information (GBR QoS Flow Information);

[0291] 5) Reflective QoS Attribute;

[0292] 2. QoS parameters of the QoS flow associated with the DRB

[0293] 1) Non-dynamic 5QI related parameters

[0294] 2) Dynamic 5QI related parameters

[0295] 3) Next Generation Radio Access Network (NG-RAN) Allocation and Retention Priority;

[0296] 4) Guaranteed Bit Rate Quality of Service Flow Information (GBR QoS Flow Information);

[0297] 5) Reflective QoS Attribute;

[0298] 6) Other parameters: further including at least one of the following parameters: Session Access and Mobility Management Bearer (Session-AMBR), Periodicity, Burst Arrival Time, Survival Time, Jitter Arrange, PSDB, PSER, PSIHI, default Priority level, Packet Delay Budget (PDB), Packet Error Rate (PER), default maximum data burst volume, default averaging window, Preamble Sequence Index (PSI), Current QoS Parameters Set Index;

[0299] 3. RLC mode;

[0300] 4. Duplication Activation;

[0301] 5. Duplication Activation

[0302] 6. Downlink PDCP sequence length (DL PDCP SN length);

[0303] 7. Uplink PDCP sequence length (UL PDCP SN length);

[0304] 8. PDCP sequence length (PDCP SN Length).

[0305] Table 10 Configuration parameter set or QOS parameter set related to service features transmitted based on user plane protocol (PDU Type (=8))

[0306] 2. In some other implementations, a predefined PDU type (PDU Type (=9)) is used to transmit DRB parameters. Table 11 shows a specific implementation of the PDU format. When the corresponding DRB parameter transmission changes, the base station-CU sends the new DRB parameter information for the corresponding group to the base station-DU by including the NR RAN Container of this PDU Type in the GTP-U PDU.

[0307] Table 11 Configuration parameter set or QOS parameter set related to service features transmitted based on user plane protocol (PDU Type (=9))

[0308] In particular, the above parameters may be classified and grouped, and different PDU types may be predefined for parameters of different groups to transmit DRB parameters corresponding to the group that need to be adjusted.

[0309] In particular, based on the existing PDU type, the existing PDU type carrying capacity can be further expanded to transmit DRB parameters between the base station-CU and the base station-DU. For specific expansion methods, please refer to the solutions in Tables 10 / 11 above.

[0310] In particular, for a certain DRB, the base station-CU can also enable it to support dynamic changes of DRB parameters through control plane messages: if enabled, the above method can be used to dynamically adjust the DRB parameters for the DRB; otherwise, the above method cannot be used to dynamically adjust the DRB parameters.

[0311] In particular, the above method of sending service characteristics or QoS parameter information based on GTP-U Container is also applicable to the Xn interface, that is, one base station sends DRB parameters to another base station through the Xn interface based on NR RAN Container.

[0312] At the interface between network-side nodes of the RAN, or at the interface of a network-side internal sub-node of the RAN, to support dynamic adjustment of DRB configuration information, the service characteristics or quality of service parameters of the service are adjusted using the following method:

[0313] Establishing or modifying one or more DRBs through control plane procedures and / or messages, including at least one of the following information: DRB identification information, DRB status information (activated or deactivated), one or more third QoS flows associated with the DRB, status information (activated or deactivated) of the third QoS flows, multiple QoS parameter sets of the third QoS flows, and parameter set status information (activated or deactivated);

[0314] Dynamically activate or deactivate the DRB through user plane messages and / or processes, which include at least one of the following information: DRB identification information, DRB status information, DRB identification information, RLC entity identification information, RLC entity status information (activation state or deactivation state)

[0315] Example 11

[0316] In some embodiments, the first network node is a distribution unit of a base station, and the method for adjusting the service characteristics or service quality parameters of the service includes the distribution unit of the base station receiving a sixth message based on the control plane protocol, wherein the sixth message includes at least one of the following: the DRB ID, the fifth activation indication, one or more third QOS flow information associated with the DRB, status information of the third QoS flow, multiple QoS parameter sets corresponding to the third QoS flow, and status information of the QoS parameter set; wherein the fifth activation indication is used to indicate the activation or deactivation of the DRB; the distribution unit of the base station receives a first message based on the user plane protocol, which is sent by the second network node and contains configuration parameters related to at least one of service characteristics, service quality, and data radio bearer (DRB), the first message is a message based on the user plane protocol, and the message based on the user plane protocol includes at least one of the following: the fifth activation indication corresponding to the DRB parameter, and the data radio bearer identifier DRB ID.

[0317] Specifically, the distribution unit of the base station can receive the DRB ID, the fifth activation indication, one or more third QOS flow information associated with the DRB, the status information of the third QoS flow, multiple QoS parameter sets corresponding to the third QoS flow, and the status information of the QoS parameter set from the central unit of the base station based on the control plane protocol. The distribution unit of the base station can obtain the mapping relationship between the third QoS flow and the DRB. There are multiple QoS parameter sets in the third QoS flow information, and each QoS parameter set corresponds to an initial status information (activation state or deactivation state). In this way, the central unit of the base station only needs to perform one configuration of the control plane protocol. When the QoS parameter set corresponding to the third QoS flow information in the central unit of the base station changes, it is not necessary to re-configure the DRB ID, the fifth activation indication, the third QoS flow information, the status information of the third QoS flow, the multiple QoS parameter sets corresponding to the third QoS flow, and the status information of the QoS parameter set. It is only necessary to change the fifth activation indication corresponding to the DRB parameter and / or the data radio bearer identifier DRB ID to achieve the change of DRB, thereby saving transmission signaling and reducing the transmission delay between the internal sub-nodes of the RAN side.

[0318] The following is a detailed description using a practical example. Taking the 5G RAN system as an example, on the control plane, referring to the F1 interface control plane protocol (F1application protocol (F1AP), see 3GPP standard protocol 38.473 for details), based on the sixth message (UE Context Setup, UE Context Modification or UE Context Modification Required process and related messages), one or more DRBs are established, each DRB is configured to be activated or deactivated, which may also include at least one of the following operations and related information:

[0319] Of the multiple DRBs associated with the same third QoS flow, only one DRB is activated, and the others are deactivated.

[0320] For multiple DRBs associated with multiple QoS parameter sets for a third QoS flow, only the DRBs corresponding to the active parameter set are active, and the other DRBs are deactivated.

[0321] Specifically, the message of the above process is sent by the base station-CU to the base station-DU, and the operation is implemented by the base station-CU and / or the base station-DU. In the corresponding message of the above process, as shown in the modification made to the message format based on the F1 protocol in the table below, the fifth activation indication (DRB status) information element in the DRB configuration is used to configure the initial status of the DRB.

[0322] On the user plane, based on the NR RAN Container and with reference to the NR (New Radio) user plane protocol (see 3GPP standard protocol 38.425 for details), a PDU type (e.g., PDU type = 10) is predefined. The fifth activation indication of this PDU type is used to dynamically activate or deactivate one or more DRBs. Table 12 shows a specific implementation of the PDU format, in which the fifth activation indication (Status Ind) is used to indicate the status of a DRB, including activation or deactivation. The first Status Ind is used to indicate the status indication information of the DRB corresponding to this GTP-U tunnel. Each subsequent DRB identifier (DRB ID) corresponds to a fifth activation indication (status indication information).

[0323] Table 12 Configuration parameter set or QOS parameter set related to service features transmitted based on user plane protocol (PDU Type (=10))

[0324] In another embodiment, a PDU type is predefined (for example, PDU type (=11)), wherein the fifth activation indication is used to dynamically activate or deactivate one or more DRBs, including a fifth activation indication (predefined bitmap), wherein each indication bit (Ind bit) in the bitmap is used to indicate activation or deactivation of a DRB, and when the value of the bit is set to 1, it indicates activation of the corresponding DRB, and when the value of the bit is set to 0, it indicates deactivation of the corresponding DRB. The predefined method includes: in order of the size of the DRB identifier, corresponding to each bit in the bitmap from high to low or from low to high, respectively, and the length of the bitmap depends on the number of DRBs. Table 13 shows a specific implementation scheme of a PDU format.

[0325] Table 13 Configuration parameter set or QOS parameter set related to service features transmitted based on user plane protocol (PDU Type (=11))

[0326] After completing the above-mentioned DRB configuration through the control plane, the base station-CU sends the fifth activation indication (status indication information) corresponding to the DRB to the base station-DU by including the NR RAN Container of the above-mentioned PDU Type in the PDU of the GTP-U, thereby dynamically activating or deactivating one or more DRBs.

[0327] In particular, based on the existing PDU type, the carrying capacity of the existing PDU type can be further expanded to transmit DRB parameters between the base station-CU and base station-DU. For specific expansion methods, please refer to the solutions in Tables 12 / 13 above.

[0328] In particular, the above method is also applicable to the Xn interface, supporting dynamic changes of DRB parameters between base stations, namely:

[0329] 1. Configure one or more pieces of DRB information through the control plane Xn Application Processor (XNAP) protocol of the Xn interface, including at least one of the following information: DRB identification information, DRB status information (activated or deactivated), one or more pieces of third QoS flow information associated with the DRB, QoS flow status information (activated or deactivated), multiple QoS parameter sets of the QoS flow, and parameter set status information (activated or deactivated);

[0330] 2. Based on the NR RAN Container, one base station sends DRB parameters to another base station; the information includes at least one of the following information: DRB identification information DRB ID and DRB status information.

[0331] In order to support dynamic adjustment of DRB configuration information at the interface between network-side nodes of the RAN, or at the interface of a network-side internal sub-node of the RAN, the present disclosure discloses the following method:

[0332] A DRB is established or modified through a seventh message (control plane procedure and / or message), where the seventh message includes at least one of the following information:

[0333] DRB identification information;

[0334] DRB status information (activated or deactivated);

[0335] One or more types of DRB-related Data Radio Bearer Quality of Service (DRB QoS) information, such as DRB QoS list information, where the DRB QoS list information includes at least one of the following information: DRB QoS identification information, DRB QoS information, and status information (activated or deactivated).

[0336] One or more pieces of third QoS flow information associated with the DRB, wherein the third QoS flow information includes state information (activated state or deactivated state) of the QoS flow;

[0337] One or more QoS parameter sets associated with a QoS flow and the status information of their QoS flow parameter sets (activated or deactivated);

[0338] Information related to one or more RLC entities associated with the DRB, wherein each RLC entity includes at least one of the following information: identification information of the RLC entity, state information of the RLC entity (activated state or deactivated state);

[0339] 2. Dynamically activate or deactivate the RLC entity through a first message (user plane message and / or process), wherein the user plane message and / or process includes at least one of the following information: DRB identification information, RLC entity identification information, and a sixth activation indication (RLC entity status information (activated state or deactivated state)).

[0340] Example 12

[0341] In some embodiments, the distribution unit of the base station receives a seventh message based on the control plane protocol, wherein the seventh message includes a data radio bearer service quality list DRB QoS List information, wherein the DRB QoS List information includes at least one of the following: one or more data radio bearer service quality DRB QoS configuration information corresponding to the DRB, a data radio bearer service quality identifier DRB QoS Identity corresponding to the DRB QoS configuration information, and status information corresponding to the DRB QoS configuration information, wherein the DRB QoS configuration information corresponds to an RLC entity; the distribution unit of the base station receives a first message of configuration parameters related to at least one of service characteristics, service quality, and data radio bearer (DRB) sent by the central unit of the base station based on the user plane protocol, the first message is a message based on the user plane protocol, and the message based on the user plane protocol includes a new radio access network container NR RAN Container, and the NR RAN Container includes at least one of the following: a data radio bearer service quality identifier DRB QoS Identity, a logical channel identifier LCID, and a sixth activation indication corresponding to the radio link control RLC entity.

[0342] Specifically, the distribution unit of the base station can receive DRB QoS List information from the central unit of the base station based on the control plane protocol, that is, one or more data radio bearer service qualities DRB QoS configuration information corresponding to the DRB, the data radio bearer service quality identifier DRB QoS Identity corresponding to the DRB QoS configuration information, and the status information corresponding to the DRB QoS configuration information. Since the DRB QoS configuration information corresponds to an RLC entity; in this way, the distribution unit of the base station can obtain the correspondence between the DRB QoS configuration information and an RLC entity. The DRB QoS configuration information has initial status information (activated state or deactivated state). In this way, the central unit of the base station is only used for one-time configuration of the control plane protocol. When the status information of the DRB corresponding to the DRB QoS Identity in the central unit of the base station changes, it is not necessary to send one or more data radio bearer service qualities DRB QoS configuration information corresponding to the DRB, the data radio bearer service quality identifier DRB QoS Identity corresponding to the DRB QoS configuration information, and the status information corresponding to the DRB QoS configuration information (DRB The status information corresponding to the QoS list information) only needs to send at least one of the following information: data radio bearer service quality identifier DRB QoS Identity, logical channel identifier LCID, and the sixth activation indication corresponding to the radio link control RLC entity, thereby saving transmission signaling overhead and reducing the transmission delay between dynamically changing internal sub-nodes on the RAN side.

[0343] The following is a detailed explanation using a practical example. Taking the 5G RAN system as an example, on the control plane, referring to the F1 interface control plane protocol (F1application protocol (F1AP), see 3GPP standard protocol 38.473 for details), the distributed unit of the base station receives the seventh message sent by the central unit of the base station (based on the UE content establishment (UE Context Setup), UE content modification (UE Context Modification) or UE content modification request (UE Context Modification Required) process and related messages), and establishes or configures multiple RLC entities for one DRB, and each RLC entity is configured to be activated or deactivated. The operation (for example, establishing or configuring multiple RLC entities, and configuring status information for each RLC entity) is implemented by the base station-CU and / or the base station-DU. In the seventh message (corresponding message) of the above process, DRB QoS List information is added to the message sent by the base station-CU to the base station-DU. The DRB QoS List information is used to indicate that a DRB includes one or more DRB QoS configuration information (DRB QoS list information) and the DRB QoS Identity corresponding to the DRB QoS configuration information (DRB QoS list information) and the status information (activated state or deactivated state) corresponding to the DRB QoS configuration information (DRB QoS list information). Each type of DRB QoS configuration information (DRB QoS list information) may correspond to an RLC entity, and / or, in the response message sent by the base station distribution unit (gNB-DU) to the base station central unit (gNB-CU), RLC list (RLC list) information is carried. The RLC list information is used to indicate the identification information and status information of the corresponding established multiple RLC entities.

[0344] On the user plane, the distribution unit of the base station receives a first message from the central unit of the base station. The first message is a message based on the user plane protocol. In this implementation, the user plane protocol includes an NR RAN Container. Referring to the NR (New Radio) user plane protocol (NR user plane protocol, see 3GPP standard protocol 38.425 for details), a predefined PDU type PDU Type (=12) is used by the base station-CU to dynamically indicate the activated DRB QoS information to the base station-DU. Table 14 shows a specific implementation scheme of a PDU format, in which the sixth activation indication (DRB service quality identifier DRB QoS identity) is used to indicate an identifier of an activated DRB QoS configuration information (DRB QoS list information). At the same time, other DRB QoS configuration information (DRB QoS list information) corresponding to the DRB is indicated as deactivated.

[0345] Table 14 Configuration parameter set or QOS parameter set related to service features transmitted based on user plane protocol (PDU Type (=12))

[0346] Accordingly, a predefined PDU type (e.g., PDU Type (=13)) is used to dynamically indicate activated RLC entity information between the base station-DU and the base station-CU. Table 15 shows a specific implementation of a PDU format, in which the sixth activation indication (one or more LCIDs) is used to indicate one or more activated RLC entities in a DRB. At the same time, other RLC entities corresponding to the DRB are in a deactivated state.

[0347] Table 15 Configuration parameter set or QOS parameter set related to service features transmitted based on user plane protocol (PDU Type (=13))

[0348] In another implementation, a PDU type (e.g., PDU Type (=14)) is predefined to dynamically indicate the activated RLC entity information between the base station-DU and the base station-CU. This includes a sixth activation indication (predefined bitmap), wherein each Ind bit of the bitmap is used to indicate an activated or deactivated RLC entity. When the value of the bit is set to 1, it indicates that the RLC entity is activated; when the value of the bit is set to 0, it indicates that the RLC entity is deactivated. The predefined method includes: in order of the size of the RLC entity identifier, each bit in the bitmap from high to low or from low to high is sequentially corresponding, and the length of the bitmap depends on the number of RLC entities. Table 16 shows a specific implementation scheme of a PDU format.

[0349] Table 16 Configuration parameter set or QOS parameter set related to service features transmitted based on user plane protocol (PDU Type (=14))

[0350] After the above-mentioned DRB configuration is completed through the control plane, the base station-CU and the base station-DU dynamically indicate the DRB QoS configuration information (DRB QoS list information) of a DRB and the status information (activated state or deactivated state) of the corresponding one or more RLC entities by including the NR RAN Container of the above-mentioned PDU Type in the PDU of GTP-U.

[0351] In particular, based on the existing PDU type, the carrying capacity of the existing PDU type can be further expanded to transmit DRB parameters between the base station-CU and base station-DU. For specific expansion methods, please refer to the solutions in Tables 14 / 15 / 16 above.

[0352] In particular, the above method is also applicable to the Xn interface, supporting dynamic changes of DRB parameters between base stations, namely:

[0353] On the one hand, one or more DRB QoS information is configured through the control plane XNAP protocol of the Xn interface, wherein the DRB QoS information includes at least one of the following information: DRB identification information, DRB status information (activated state or deactivated state), DRB-related DRB QoS list information (further including at least one of the following information: DRB QoS identification information, DRB QoS information, DRB QoS status information), one or more third QoS flow information associated with the DRB, QoS flow status information (activated state or deactivated state), multiple QoS parameter sets of the third QoS flow and parameter set status information (activated state or deactivated state);

[0354] On the other hand, based on the NR RAN Container, one base station sends DRB parameters to another base station; wherein the DRB parameters include at least one of the following information: DRB QoS identification information, RLC entity identification information, and RLC entity status information.

[0355] This document describes methods for adjusting service characteristics or quality of service parameters, applicable to communications between a UE and a base station, and between a core network and a base station. However, these inventive concepts, methods, apparatuses, devices, computer-readable storage media, chips, and computer program products are not limited to 5G NR communications and can be extended to other communication scenarios to achieve the same technical benefits and effects.

[0356] In these scalable communication scenarios, the first network node and / or the first network node can be an entity such as a user equipment (UE), a base station (such as a base station, an eNodeB, a transmission reception point (TRP), a NodeB for next-generation communications, or a WIFI access point, etc.), or a network element. User equipment (UE) refers to a device used for communication at the user end, such as a mobile phone, and can also be called a terminal, a mobile station, or a mobile terminal. UE can be a variety of devices, including but not limited to mobile phones, tablet computers, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals for industrial control, wireless terminals for autonomous driving, wireless terminals for remote medical surgery, wireless terminals for smart grids, wireless terminals for environmental monitoring, wireless terminals for smart cities, and wireless terminals for smart homes, etc.

[0357] Furthermore, UEs and base stations can be deployed in different environments, including but not limited to indoors, outdoors, as handheld devices, in vehicles, or even on water, in the air, on airplanes, drones, or satellites.

[0358] Therefore, although this document describes methods and devices for 5G NR communications, the inventive concepts and technologies contained therein can be extended to other communication scenarios and are expected to achieve the same technical benefits and effects. It is easy to understand that these inventive concepts have broad applicability and scalability, whether in communications between different types of base stations and user equipment, or in different deployment environments.

[0359] It should be noted that the above steps are merely examples and do not limit the scope of the present invention. Various modifications and variations can be made to the steps without departing from the spirit and scope of the present invention.

[0360] The order of the described steps (signaling / boxes) is not intended to be construed as a limitation, and any number of the described steps (signaling / boxes) may be skipped or combined in any order to implement a method or an alternative method.

[0361] The present disclosure describes examples of communication between terminals and network element components in a network architecture in the above embodiments, which are mainly for illustrative purposes and not restrictive.

[0362] The order of the steps (signaling / boxes) described is not intended to be interpreted as limiting, and any number of the steps (signaling / boxes) described can be skipped or combined in any order to implement a method or alternative method. Typically, any of the components, modules, methods, and operations described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or any combination thereof. Some operations of the example methods can be described in the general context of executable instructions stored on a computer-readable memory locally and / or remotely on a computer processing system, and implementation methods can include software applications, programs, functions, and the like. Alternatively or in addition, any function described herein can be performed, at least in part, by one or more hardware logic components, such as, but not limited to, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), an application specific standard product (ASSP), a system on a chip (SoC), a complex programmable logic device (CPLD), and the like.

[0363] In addition, the signaling described in the embodiments of the present disclosure can be implemented in any manner known in the art. For example, the signaling can be explicit and / or implicit. In addition, the steps (signaling / frames) shown are for illustrative purposes only and are not intended to limit the present application.

[0364] FIG16 is a schematic structural diagram of a wireless communication device 900 provided by the present disclosure. The wireless communication device includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, and perform the following operations:

[0365] A first message of configuration parameters related to at least one of service characteristics, service quality, and data radio bearer (DRB) is received from a second network node, wherein the first message is a message based on a user plane protocol.

[0366] Or send a first message of configuration parameters related to at least one of service characteristics, service quality, and data radio bearer (DRB), wherein the first message is a message based on a user plane protocol.

[0367] The wireless communication device may be a user device, a base station, or a network element. The wireless communication device 900 shown in FIG16 includes a processor 910. The processor 910 may call and run a computer program from a memory to implement the method in an embodiment of the present application.

[0368] Optionally, as shown in FIG16 , the wireless communication device 900 may further include a memory 920. The processor 910 may call and execute a computer program from the memory 920 to implement the method in the embodiment of the present application. The memory 920 may be a separate device independent of the processor 910 or may be integrated into the processor 910.

[0369] Optionally, as shown in FIG16 , the wireless communication device 900 may further include a transceiver 930. The processor 910 may control the transceiver 930 to communicate with other devices. Specifically, the transceiver 930 may send information or data to other devices or receive information or data sent by other devices. The transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include one or more antennas.

[0370] Optionally, the wireless communication device 900 may specifically be a base station in an embodiment of the present application, and the wireless communication device 900 may implement the corresponding processes implemented by the base station in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0371] Optionally, the wireless communication device 900 may specifically be a mobile user device / user device in an embodiment of the present application, and the wireless communication device 900 may implement the corresponding processes implemented by the mobile user device / user device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0372] Optionally, the wireless communication device 900 may specifically be a network element in an embodiment of the present application, and the wireless communication device 900 may implement the corresponding processes implemented by the network element in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0373] According to an example embodiment, a chip is provided, comprising: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes a method according to any one of the above embodiments, examples, or exemplary embodiments.

[0374] According to an example embodiment, there is provided a computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute a method according to any one of the above-mentioned embodiments, examples, or exemplary embodiments.

[0375] According to an example embodiment, a computer program product is provided, comprising a computer program / instruction, which, when executed by a processor (e.g., by the processor or an apparatus, device, computer or machine including the processor), implements a method according to any one of the above-mentioned embodiments, examples, or example embodiments.

[0376] The embodiments of the present disclosure are a combination of techniques / processes that may be employed in 3GPP specifications to create a final product.

[0377] While the present disclosure has been described in connection with what is considered to be the most practical and preferred embodiment, it is to be understood that the disclosure is not limited to the disclosed embodiment, but is intended to cover various arrangements embodied within the broadest interpretation of the appended claims.

Claims

1. A method for adjusting service characteristics or service quality parameters of a service, executed by a first network node, the method comprising: A first message of configuration parameters related to at least one of service characteristics, service quality, and data radio bearer (DRB) is received from a second network node, wherein the first message is a message based on a user plane protocol.

2. The method according to claim 1, wherein The first network node is a base station, and the message based on the user plane protocol includes a General Packet Radio Service Tunneling Protocol user plane container GTP-U Container, where the GTP-U Container includes at least one of the following: A first protocol data unit type, a first quality of service flow identifier QOS flow ID, configuration parameters or QOS parameters related to service characteristics, a first activation indication corresponding to the first quality of service flow QOS flow, and a second activation indication corresponding to the QOS parameter, wherein the first protocol data unit type is used to indicate the type of control information in the GTP-U Container, the first activation indication is used to indicate activation or deactivation of the first QOS flow corresponding to the first QOS flow ID, and the second activation indication is used to indicate whether the QOS parameter has changed or to indicate activation or deactivation of the QOS parameter.

3. The method according to any one of claims 1 to 2, wherein: The QOS parameter is a QOS parameter set, and the method further includes: A second message is received based on a control plane protocol, wherein the second message includes at least one of the following: the first QOS flow ID, status information corresponding to the QOS parameter set, several QOS parameter sets corresponding to the first QOS flow, and an identifier corresponding to the QOS parameter set.

4. The method according to claim 1, wherein The method further comprises: A third message is received based on a control plane protocol, wherein the third message includes the first QOS flow ID and / or state information corresponding to the first QOS flow ID.

5. The method according to claim 1, wherein The first network node is a user equipment, and the message based on the user plane protocol includes a control protocol data unit (control PDU), where the control PDU includes at least one of the following: The second protocol data unit type, the DRB parameters, the logical channel identifier LCID, the length value, the protocol entity type, the entity identifier, the configuration information for adjusting the second QOS flow and the DRB, the third activation indication corresponding to the DRB or the DRB parameters, and the fourth activation indication corresponding to the radio link control RLC entity, wherein the second protocol data unit type is used to indicate the type of control information in the control PDU, the third activation indication is used to indicate whether the DRB parameters have changed or to indicate activation or deactivation of the DRB corresponding to the second QOS flow ID, and the fourth activation indication is used to indicate activation or deactivation of the RLC entity corresponding to the second QOS flow ID.

6. The method according to claim 5, wherein: When the control PDU is a Service Data Adaptation Protocol (SDAP) control PDU, a Packet Data Convergence Protocol (PDCP) control PDU, or an RLC control PDU, the control PDU includes at least one of the following: A second protocol data unit type, the DRB parameters, and a third activation indication corresponding to the DRB parameters.

7. The method according to claim 5, wherein: When the control PDU is a media access control element MAC CE, the control PDU includes at least one of the following: the DRB parameter, a logical channel identifier LCID, a length value, a protocol entity type, an entity identifier, and a third activation indication corresponding to the DRB parameter.

8. The method according to claim 5, wherein The adjusting the configuration information of the second QOS flow and the DRB includes at least one of the following operations: Indicate whether to activate a DRB through a user plane message; Adjust the mapping relationship between the second QoS flow and the DRB by sending a downlink SDAP PDU; When the relocation of the second QoS flow results in no QoS flow being mapped to a DRB, or only one or more deactivated second QoS flows are mapped to the DRB, the DRB is set to the deactivated state; Set a DRB to deactivated state through user plane messages; Cancel the mapping relationship between one or more second QoS flows and DRBs through a user plane message; Establishing a mapping relationship between multiple second QoS flows and a DRB through a user plane message; A mapping relationship between a second QoS flow and multiple DRBs is established through user plane messages, but only one DRB is active at a time. If there is no second QoS flow, or only a deactivated second QoS flow is mapped to a DRB, the DRB can be set to the deactivated state; If at least one active second QoS flow establishes a mapping relationship with a DRB, the DRB will be set to the active state.

9. The method according to any one of claims 5 to 8, wherein: The method further comprises: A fourth message is received based on a control plane protocol, wherein the fourth message includes at least one of the following: mapping relationship information between the second QoS flow and the DRB and status information corresponding to the DRB.

10. The method according to claims 5-8, wherein: The DRB is an RLC entity, and the method further includes: A fifth message is received based on the control plane protocol, and the fifth message includes at least one of the following: mapping relationship information between the second QoS flow and DRB, information about the DRB-associated PDCP entity, information about the DRB-configured RLC entity and status information corresponding to the RLC entity, and mapping relationship information between the PDCP entity and the RLC entity.

11. The method according to claim 1, wherein The first network node is a distributed unit of a base station, the message based on the user plane protocol includes a New Radio Access Network Container (NR RAN Container), and the NR RAN Container includes at least one of the following: The third protocol data unit type, the third quality of service flow identifier QOS flow ID, the DRB parameters, the fifth activation indication corresponding to the DRB parameters, the data radio bearer identifier DRB ID, the data radio bearer service quality identifier DRB QoS Identity, the logical channel identifier LCID, and the sixth activation indication corresponding to the radio link control RLC entity, wherein the fifth activation indication is used to indicate whether the DRB parameters have changed or to indicate activation or deactivation of the DRB, the third protocol data unit type is used to indicate the type of control information in the NR RAN Container, and the DRB ID is used to identify each DRB parameter.

12. The method according to claim 11, wherein The method further comprises: A sixth message is received based on the control plane protocol, wherein the sixth message includes at least one of the following: the DRB ID, status information corresponding to the DRB ID, one or more third QOS flow information associated with the DRB, status information of the third QoS flow, multiple QoS parameter sets corresponding to the third QoS flow, and status information of the QoS parameter set.

13. The method according to claim 11, wherein The method further comprises: A seventh message is received based on the control plane protocol, wherein the seventh message includes: data radio bearer service quality list DRB QoS List information, wherein the DRB QoS List information includes at least one of the following: one or more data radio bearer service quality DRB QoS configuration information corresponding to the DRB, a data radio bearer service quality identifier DRB QoS Identity corresponding to the DRB QoS configuration information, and status information corresponding to the DRB QoS configuration information, wherein the DRB QoS configuration information corresponds to an RLC entity.

14. A wireless communication device, wherein: The wireless communication device comprises: a processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 13.

15. A method for adjusting service characteristics or service quality parameters of a service, executed by a second network node, the method comprising: A first message of configuration parameters related to at least one of service characteristics, service quality, and data radio bearer (DRB) is sent, wherein the first message is a message based on a user plane protocol.

16. The method according to claim 15, wherein The second network node is a core network device, and the message based on the user plane protocol includes a General Packet Radio Tunneling Protocol user plane container GTP-U Container, where the GTP-U Container includes at least one of the following: A first protocol data unit type, a first quality of service flow identifier QOS flow ID, configuration parameters or QOS parameters related to service characteristics, a first activation indication corresponding to the first quality of service flow QOS flow, and a second activation indication corresponding to the QOS parameter, wherein the first protocol data unit type is used to indicate the type of control information in the GTP-U Container, the first activation indication is used to indicate activation or deactivation of the first QOS flow corresponding to the first QOS flow ID, and the second activation indication is used to indicate whether the QOS parameter has changed or to indicate activation or deactivation of the QOS parameter.

17. The method according to any one of claims 15 to 16, wherein: The QOS parameter is a QOS parameter set, and the method further includes: A second message is sent based on the control plane protocol, wherein the second message includes at least one of the following: the first QOS flow ID, status information corresponding to the QOS parameter set, several QOS parameter sets corresponding to the first QOS flow, and an identifier corresponding to the QOS parameter set.

18. The method according to claim 15, wherein The method further comprises: A third message is sent based on a control plane protocol, wherein the third message includes the first QOS flow ID and / or status information corresponding to the first QOS flow ID.

19. The method according to claim 15, wherein The second network node is a base station, and the message based on the user plane protocol includes a control protocol data unit (control PDU), and the control PDU includes at least one of the following: The second protocol data unit type, the DRB parameters, the logical channel identifier LCID, the length value, the protocol entity type, the entity identifier, the configuration information for adjusting the second QOS flow and the DRB, the third activation indication corresponding to the DRB or the DRB parameters, and the fourth activation indication corresponding to the radio link control RLC entity, wherein the second protocol data unit type is used to indicate the type of control information in the control PDU, the third activation indication is used to indicate whether the DRB parameters have changed or to indicate activation or deactivation of the DRB corresponding to the second QOS flow ID, and the fourth activation indication is used to indicate activation or deactivation of the RLC entity corresponding to the second QOS flow ID.

20. The method according to claim 19, wherein When the control PDU is a Service Data Adaptation Protocol (SDAP) control PDU, a Packet Data Convergence Protocol (PDCP) control PDU, or an RLC control PDU, the control PDU includes at least one of the following: A second protocol data unit type, the DRB parameters, and a third activation indication corresponding to the DRB parameters.

21. The method according to claim 19, wherein When the control PDU is a media access control element MAC CE, the control PDU includes at least one of the following: the DRB parameter, a logical channel identifier LCID, a length value, a protocol entity type, an entity identifier, and a third activation indication corresponding to the DRB parameter.

22. The method according to claim 19, wherein The adjusting the configuration information of the second QOS flow and the DRB includes at least one of the following operations: Indicate whether to activate a DRB through a user plane message; Adjust the mapping relationship between the second QoS flow and the DRB by sending a downlink SDAP PDU; When the relocation of the second QoS flow results in no QoS flow being mapped to a DRB, or only one or more deactivated second QoS flows are mapped to the DRB, the DRB is set to the deactivated state; Set a DRB to deactivated state through user plane messages; Cancel the mapping relationship between one or more second QoS flows and DRBs through a user plane message; Establishing a mapping relationship between multiple second QoS flows and a DRB through a user plane message; A mapping relationship between a second QoS flow and multiple DRBs is established through user plane messages, but only one DRB is active at a time. If there is no second QoS flow, or only a deactivated second QoS flow is mapped to a DRB, the DRB can be set to the deactivated state; If at least one active second QoS flow establishes a mapping relationship with a DRB, the DRB will be set to the active state.

23. The method according to any one of claims 19 to 22, wherein: The method further comprises: A fourth message is sent based on the control plane protocol, wherein the fourth message includes at least one of the following: mapping relationship information between the second QoS flow and the DRB and status information corresponding to the DRB.

24. The method according to claims 19-22, wherein: The DRB is an RLC entity, and the method further includes: A fifth message is sent based on the control plane protocol, and the fifth message includes at least one of the following: mapping relationship information between the second QoS flow and DRB, information about the DRB-associated PDCP entity, information about the DRB-configured RLC entity and status information corresponding to the RLC entity, and mapping relationship information between the PDCP entity and the RLC entity.

25. The method according to claim 15, wherein The second network node is a central unit of a base station, and the message based on the user plane protocol includes a New Radio Access Network Container (NR RAN Container), where the NR RAN Container includes at least one of the following: a third protocol data unit type, a third quality of service flow identifier (QOS flow ID), the DRB parameter, a fifth activation indication corresponding to the DRB parameter, the data radio bearer identifier (DRB ID), a data radio bearer quality of service identifier (DRB QoS Identity), a logical channel identifier (LCID), and a sixth activation indication corresponding to a radio link control (RLC) entity, wherein the fifth activation indication is used to indicate whether the DRB parameter has changed or to indicate activation or deactivation of the DRB, the third protocol data unit type is used to indicate the type of control information in the NR RAN Container, and the DRB ID is used to identify each DRB. parameter.

26. The method according to claim 25, wherein The method further comprises: A sixth message is sent based on the control plane protocol, wherein the sixth message includes at least one of the following: the DRB ID, status information corresponding to the DRB ID, one or more third QOS flow information associated with the DRB, status information of the third QoS flow, multiple QoS parameter sets corresponding to the third QoS flow, and status information of the QoS parameter set.

27. The method according to claim 25, wherein The method further comprises: A seventh message is sent based on the control plane protocol, wherein the seventh message includes: data radio bearer service quality list DRB QoS List information, wherein the DRB QoS List information includes at least one of the following: one or more data radio bearer service quality DRB QoS configuration information corresponding to the DRB, a data radio bearer service quality identifier DRB QoS Identity corresponding to the DRB QoS configuration information, and status information corresponding to the DRB QoS configuration information, wherein the DRB QoS configuration information corresponds to an RLC entity.

28. A wireless communication device, wherein: The wireless communication device includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the method according to any one of claims 15 to 27.

Images