User plane configuration method, system, base station and medium supporting low-latency services

Abstract

The present disclosure provides a user plane configuration method, system, base station and medium supporting low-latency services, and relates to the field of communication technology. The method includes: a base station control plane entity receives a session establishment or modification request message sent by a core network control plane entity; according to the session service feature information, determines the PDCP discard timer and / or EHC configuration required to be supported; when it is determined that the base station user plane entity supports the extended PDCP discard timer and / or EHC configuration of the low-latency service, the extended PDCP discard timer and / or EHC configuration is included in the PDCP configuration information and sent to the base station user plane entity through a bearer context establishment or modification request message; according to the bearer context establishment or modification response message returned by the base station user plane entity, an RRC reconfiguration message is generated and sent to the terminal; after receiving the RRC reconfiguration completion message returned by the terminal, a session establishment or modification response message is returned to the core network control plane entity. The present disclosure enables the base station user plane entity to support low-latency services.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a user plane configuration method, system, base station and medium that support low-latency services. Background Art

[0002] Compared with 4G (4th Generation) networks, 5G (5th Generation) networks introduce a design architecture that separates the control plane (Control Plane) from the user plane (User Plane).

[0003] There are differences in the support capabilities of the base station control plane entity and the base station user plane entity for the low-latency service discard timer, which may cause the failure of bearer establishment or modification between the base station control plane entity and the base station user plane entity, thereby making it impossible for low-latency services to be supported accordingly in the control plane and user plane separation architecture.

[0004] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0005] The present disclosure provides a user plane configuration method, system, base station and medium that support low-latency services, which at least to a certain extent overcome the technical problem in the related art that low-latency services cannot be supported accordingly in the control plane and user plane separation architecture.

[0006] Other features and advantages of the present disclosure will become apparent from the following detailed description, or may be learned in part by the practice of the present disclosure.

[0007] According to one aspect of the present disclosure, a user plane configuration method for supporting low-latency services is provided, the method comprising: a base station control plane entity receives a session establishment or modification request message sent by a core network control plane entity; the base station control plane entity determines the PDCP discard timer and / or Ethernet header compression EHC configuration required to be supported by the base station and terminal user plane PDCP configuration according to the service feature information of the established or modified session; the PDCP discard timer comprises a first discard timer or a second discard timer, the first discard timer is a PDCP discard timer supported by a radio resource control RRC layer, and the second discard timer is an extended PDCP discard timer supporting low-latency services; when When the base station control plane entity determines that the base station user plane entity supports the extended PDCP discard timer and / or Ethernet header compression EHC configuration, the base station control plane entity includes the corresponding extended PDCP discard timer and / or EHC configuration in the PDCP configuration information and sends it to the base station user plane entity through a bearer context establishment or modification request message; the base station control plane entity generates a radio resource control RRC reconfiguration message according to the bearer context establishment or modification response message returned by the base station user plane entity, and sends it to the terminal; after receiving the RRC reconfiguration completion message returned by the terminal, the base station control plane entity returns a session establishment or modification response message to the core network control plane entity.

[0008] In some embodiments, the method also includes any one of the following: the base station control plane entity determines whether the base station user plane entity supports the extended PDCP discard timer based on the protocol version information supported by the base station user plane entity carried in the first network management configuration information; the base station control plane entity determines whether the base station user plane entity supports the extended PDCP discard timer based on the protocol version indication information carried by the base station user plane entity in the E1 interface establishment or update message; the base station control plane entity determines that the base station user plane entity does not support the extended discard timer set based on the bearer establishment or modification failure reason received by the E1 interface.

[0009] In some embodiments, the protocol version indication information uses an enumeration type to represent the protocol version supported by the base station user plane entity.

[0010] In some embodiments, the protocol version supported by the base station user plane entity includes any one of the following: 3GPP Rel-15 version, 3GPP Rel-16-v80 and earlier versions, and 3GPP Rel-16-v90 and later versions.

[0011] In some embodiments, after the base station control plane entity receives a session establishment or modification request message sent by the core network control plane entity, the method also includes: the base station control plane entity determines the PDCP discard timer and / or EHC configuration sent to the base station user plane entity based on the second network management configuration information and the quality service QOS level of the data bearer carried in the session establishment or modification request message, wherein the second network management configuration information includes at least: a mapping relationship between the QOS level and the service data transmission interval; whether the QOS level activates the EHC configuration and the type of the activated EHC configuration, and the type of the EHC configuration includes any one of the following: uplink compression only, downlink compression only, and bidirectional compression.

[0012] In some embodiments, the method also includes: the base station control plane entity determines to configure the PDCP discard timer using a timer value in a first discard timer set or a second discard timer set based on a service data transmission interval, wherein the timer value in the first discard timer set is greater than or equal to 10ms; the timer value in the second discard timer set is less than 10ms, and the timer value in the second discard timer set is used to configure an extended PDCP discard timer supported by the base station user plane entity.

[0013] In some embodiments, the first discard timer set includes at least the following timer values: 10ms, 20ms, 30ms, 40ms, 50ms, 60ms, 75ms, 100ms, 150ms, 200ms, 250ms, 300ms, 500ms, 750ms, 1500ms; the second discard timer set includes at least the following timer values: 0.5ms, 1ms, 2ms, 4ms, 8ms, and the second discard timer set indicates an extended PDCP discard timer.

[0014] In some embodiments, after the base station control plane entity receives the session establishment or modification request message sent by the core network control plane entity, the method further includes: when the base station control plane entity does not know the protocol version information supported by the base station user plane entity, the base station control plane entity sends the first PDCP configuration information to the base station user plane entity through an E1 interface message carrying a context establishment or modification request message, wherein the first PDCP configuration information includes a PDCP discard timer and / or an EHC configuration;

[0015] The PDCP discard timer configuration includes: a timer value in the first discard timer set or the second discard timer set; and the EHC configuration includes:

[0016] Header compression context identifier, including 7-bit and 15-bit;

[0017] For downstream header compression, at least the following information is included:

[0018] Continuity indication information of downstream header compression, enumeration type, including at least True;

[0019] For upstream header compression, at least the following information is included:

[0020] Continuity indication information of upstream header compression, enumeration type, including at least True;

[0021] The maximum uplink header compression context identifier is MAX_CID_EHC_UL, and its value shall not exceed maxNumberEHC-Contexts.

[0022] In some embodiments, the method also includes: when the base station control plane entity supports the robust header compression ROHC function, the ROHC configuration parameters and the EHC configuration are included in the PDCP configuration and sent to the base station user plane entity through a bearer context establishment or modification request message, so that the base station user plane entity configures the header compression operation of the corresponding bearer.

[0023] In some embodiments, after the base station control plane entity sends the first PDCP configuration information to the base station user plane entity through an E1 interface message bearer context establishment or modification request message, the method also includes: the base station user plane entity checks whether it supports the timer value in the first PDCP configuration information of the established or modified bearer; when the base station user plane entity does not support the discard timer value in the first PDCP configuration information of the bearer, the base station user plane entity returns a bearer context establishment or modification failure message and a first failure cause to the base station control plane entity, the first failure cause being used to indicate that the base station user plane entity does not support the timer value included in the first PDCP configuration information; the base station user plane entity does not delete the user context configuration information and keeps receiving the original PDCP configuration information; when the base station user plane entity supports the timer value in the first PDCP configuration information, the timer value in the first PDCP configuration information is saved; the base station user plane entity For each data bearer requested by the base station control plane entity, the user plane entity uses the EHC configuration included in the PDCP configuration of the bearer context establishment or modification request message to perform the header compression operation process of the corresponding data bearer, and when the uplink header compression configuration is included in the first PDCP configuration information, checks whether the maximum uplink header compression context identifier MAX_CID_EHC_UL in the first PDCP configuration information exceeds maxNumberEHC-Contexts; when the maximum uplink header compression context identifier MAX_CID_EHC_UL in the first PDCP configuration information exceeds maxNumberEHC-Contexts, the base station user plane entity returns a bearer context establishment or modification failure message and a second failure cause to the base station control plane entity, and the second failure cause is used to indicate that the maximum uplink header compression context identifier in the first PDCP configuration information is greater than maxNumberEHC-Contexts.

[0024] In some embodiments, after the base station user plane entity checks whether it supports the discard timer value in the first PDCP configuration information, the method further includes: when the base station user plane entity supports the discard timer value in the first PDCP configuration information and other configurations can support the configuration, the base station user plane entity returns a bearer context establishment or modification response message to the base station control plane entity.

[0025] In some embodiments, after the base station user plane entity returns a bearer context establishment or modification response message to the base station control plane entity, the method further includes: the base station control plane entity generates a first RRC reconfiguration message sent to the terminal according to the bearer context establishment or modification response message returned by the base station user plane entity, wherein the discard timer value and / or EHC configuration in the first RRC reconfiguration message are the same as the discard timer value and / or EHC configuration of the first PDCP configuration information.

[0026] In some embodiments, the method also includes: the base station control plane entity sends a first RRC reconfiguration message to the terminal through the base station separation entity; the base station control plane entity receives a first RRC reconfiguration completion message returned by the terminal according to the first RRC reconfiguration message through the base station separation entity; the base station control plane entity sends a session establishment or modification response message to the core network control plane entity according to the first RRC reconfiguration completion message returned by the terminal to confirm that the bearer configuration in the wireless network is completed.

[0027] In some embodiments, after the base station user plane entity returns a bearer context establishment or modification failure message and a first failure cause to the base station control plane entity, the method further includes: the base station control plane entity determines that the base station user plane entity does not support the extended discard timer, and reselects a timer value with the smallest value in the first discard timer set, updates the first PDCP configuration information of the corresponding bearer to the second PDCP configuration information, and sends the second PDCP configuration information to the base station user plane entity via an E1 interface message bearer context establishment or modification request message.

[0028] In some embodiments, the method also includes: the base station user plane entity returns a bearer context establishment or modification response message to the base station control plane entity based on the received second PDCP configuration information; the base station control plane entity generates a second RRC reconfiguration message sent to the terminal based on the bearer context establishment or modification response message returned by the base station user plane entity, wherein the discard timer value and / or EHC configuration in the second RRC reconfiguration message are the same as the discard timer value and / or EHC configuration of the second PDCP configuration information.

[0029] In some embodiments, the method also includes: the base station control plane entity sends a second RRC reconfiguration message to the terminal through the base station separation entity; the base station control plane entity receives a second RRC reconfiguration completion message returned by the terminal according to the second RRC reconfiguration message through the base station separation entity; the base station control plane entity returns a session establishment or modification response message to the core network control plane entity according to the second RRC reconfiguration completion message returned by the terminal to confirm that the bearer configuration in the wireless network is completed.

[0030] According to another aspect of the present disclosure, a communication system is also provided, including: a core network control plane entity, a base station control plane entity and a base station user plane entity; wherein the core network control plane entity is used to send a session establishment or modification request message; the base station control plane entity is used to determine the PDCP discard timer and / or Ethernet header compression EHC configuration required to be supported by the base station and terminal user plane PDCP configuration according to the service feature information of the established or modified session; when it is determined that the base station user plane entity supports the extended PDCP discard timer and / or Ethernet header compression EHC configuration, the corresponding extended PDCP discard timer and / or EHC configuration is included in the PDCP configuration information and sent to the base station via a bearer context establishment or modification request message. Base station user plane entity; the PDCP discard timer includes a first discard timer and / or a second discard timer, the first discard timer is a PDCP discard timer supported by the radio resource control RRC layer, and the second discard timer is an extended PDCP discard timer supporting low-latency services; the base station user plane entity is used to return a bearer context establishment or modification response message to the base station control plane entity; the base station control plane entity is also used to generate a radio resource control RRC reconfiguration message according to the bearer context establishment or modification response message returned by the base station user plane entity, send it to the terminal, and after receiving the RRC reconfiguration completion message returned by the terminal, return a session establishment or modification response message to the core network control plane entity.

[0031] In some embodiments, the communication system further includes: a base station separation entity, which is used for the base station control plane entity to send an RRC reconfiguration message to the terminal or receive an RRC reconfiguration completion message returned by the terminal.

[0032] According to another aspect of the present disclosure, a base station is also provided, characterized in that it includes: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any one of the above-mentioned user plane configuration methods for supporting low-latency services by executing the executable instructions.

[0033] According to another aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the user plane configuration method for supporting low-latency services described in any one of the above is implemented.

[0034] The user plane configuration method, system, base station and medium for supporting low-latency services provided in the embodiments of the present disclosure, when the base station control plane entity receives a session establishment or modification request message sent by the core network control plane entity, the base station control plane entity determines the PDCP discard timer (the first discard timer supported by the radio resource control RRC layer or the extended second discard timer supporting low-latency services) and / or Ethernet header compression EHC configuration required to be supported by the base station and terminal user plane PDCP configuration according to the service feature information of the established or modified session; when the base station control plane entity determines that the base station user plane entity supports the extended PDCP discard timer and / or Ethernet header compression EHC configuration, the base station control plane entity includes the corresponding extended PDCP discard timer and / or EHC configuration in the PDCP configuration information through a bearer context establishment or modification request message and sends it to the base station user plane entity; the base station control plane entity generates a radio resource control RRC reconfiguration message according to the bearer context establishment or modification response message returned by the base station user plane entity and sends it to the terminal; after the terminal returns an RRC reconfiguration completion message to the base station control plane entity, the base station control plane entity returns a session establishment or modification response message to the core network control plane entity.

[0035] Through the embodiments of the present disclosure, low-latency services can be supported accordingly in base stations with a separate control plane and user plane design, thereby avoiding the problem of failure in bearer establishment or modification between the base station control plane entity and the base station user plane entity due to differences in their support capabilities for low-latency service discard timers.

[0036] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.

[0038] Figure 1 A schematic diagram of a control plane and user plane separation architecture in the related art is shown;

[0039] Figure 2A schematic diagram of a process of establishing an E1 interface between a control plane and a user plane in the related art is shown;

[0040] Figure 3 A schematic diagram of a process of establishing a bearer context between a base station control plane entity and a base station user plane entity in an embodiment of the present disclosure is shown;

[0041] Figure 4 A schematic diagram of a communication system in an embodiment of the present disclosure is shown;

[0042] Figure 5 A flow chart of a user plane configuration method for supporting low-latency services in an embodiment of the present disclosure is shown;

[0043] Figure 6 A schematic diagram of the interaction process of a user plane configuration system supporting low-latency services in an embodiment of the present disclosure is shown;

[0044] Figure 7 A schematic diagram showing a process of establishing an E1 interface between a control plane and a user plane in an embodiment of the present disclosure is shown;

[0045] Figure 8 A schematic diagram of a base station in an embodiment of the present disclosure is shown;

[0046] Fig. 9 A schematic diagram of a computer-readable storage medium in an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0047] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that the disclosure will be more comprehensive and complete and to fully convey the concepts of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0048] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0049] For ease of understanding, before introducing the embodiments of the present disclosure, several terms involved in the embodiments of the present disclosure are first explained as follows:

[0050] UE: User Equipment, also known as user terminal, or terminal for short;

[0051] gNB: base station of 5G network;

[0052] CU: Centralized Unit, centralized unit;

[0053] DU:Distributed Unit,distributed unit;

[0054] UP: User Plane, user plane;

[0055] CP:Control Plane,control surface;

[0056] PDCP: Packet Data Convergence Protocol, packet data convergence protocol;

[0057] EHC: Ethernet Header Compression, Ethernet header compression;

[0058] QOS: Quality of Service, service quality;

[0059] RRC: Radio Resource Control, radio resource control;

[0060] MAC: Medium Access Control, media access control;

[0061] PDCP: Packet Data Convergence Protocol, packet data convergence protocol;

[0062] RLC: Radio Link Control, wireless link layer control protocol;

[0063] PDU: Protocol Data Unit, protocol data unit;

[0064] SDU: Service Data Unit, service data unit;

[0065] RRC: Radio Resource Control.

[0066] The specific implementation of the embodiment of the present disclosure is described in detail below with reference to the accompanying drawings.

[0067] In order to support low-latency industrial Internet services, 3GPP has introduced relevant air interface enhancement technologies, but the support for low-latency services in the separation architecture of base station virtualization is still not perfect.

[0068] Figure 1 A schematic diagram of a control plane and user plane separation architecture in the related art is shown as follows Figure 1 As shown, the base station user plane (e.g., gNB-CU-UP) entity supports the protocol functions of the SDAP (Service Data Adaptation Protocol) and PDCP (Packet Data Convergence Protocol) layers, while the base station control plane (e.g., gNB-CU-CP) entity supports the protocol functions of the RRC (Radio Resource Control) layer, and the base station separation (e.g., gNB-DU) entity supports the protocol functions of the physical layer, MAC (Media Access Control) layer, and RLC (Radio Link Control) layer.

[0069] like Figure 2 As shown, the base station control plane entity (gNB-CU-CP) and the base station user plane entity (gNB-CU-UP) communicate using the E1 interface. During the establishment of the E1 interface, the base station control plane entity needs to obtain information such as the service support capability of the base station user plane entity before performing relevant configuration on the base station user plane entity. Figure 3 A schematic diagram of a process of establishing a bearer context between a base station control plane entity and a base station user plane entity in an embodiment of the present disclosure is shown. Figure 3 As shown, in the current E1 interface protocol, the base station control plane entity cannot understand the base station user plane entity's support capabilities for the protocol version or some business functions, and can only obtain the base station user plane entity's business function support capabilities through network management configuration. The difference in business support capabilities between the base station control plane entity and the base station user plane entity may cause the bearer establishment or modification between the base station control plane entity and the base station user plane entity to fail.

[0070] The PDU (Protocol Data Unit) of PDCP is divided into two types: data PDU and control PDU. The data PDU is the data transmitted between N-layer protocol entities, and the control PDU is the data transmitted between N-layer users and N-layer protocols.

[0071] The encapsulation / decapsulation process of PDU is as follows: at the sender, the SDU submitted by the user is added with the protocol control information PCI and encapsulated into PDU; at the receiver, the received PDU is decapsulated, the PCI is removed, and it is restored to SDU for transmission to the receiving user.

[0072] The process of SDU segmentation / assembly is as follows: if the bandwidth of the lower-layer channel cannot meet the needs of transmitting SDU, one SDU needs to be divided into multiple segments, each of which is encapsulated into PDU and sent out (segmentation); at the receiving end, these PDUs are decapsulated and reassembled into SDUs.

[0073] The process of SDU splicing / separation is as follows: splicing means that the sender encapsulates multiple shorter SDUs into one PDU and sends it, and then decapsulates the received PDU at the receiver to separate multiple SDUs. The splicing function can improve the utilization rate of the channel.

[0074] PDCP does not assign SN (Serial Number) to control PDUs, but assigns SN to all data PDUs and ensures that SN will not be repeated within a period of time. The sender will start a discard timer (also called discard timer) for each SDU, and discard the SDU after the timeout to prevent transmission buffer congestion.

[0075] In the 3GPP R15 protocol, the discard timer granularity supported by the RRC layer is: 10ms, 20ms, 30ms, 40ms, 50ms, 60ms, 75ms, 100ms, 150ms, 200ms, 250ms, 300ms, 500ms, 750ms, 1500ms and other extended values; since low-latency services have a lower transmission interval, in order to support the matching of the transmission interval and the discard timer, a lower discard timer granularity is introduced in the air interface, namely: 0.5ms, 1ms, 2ms, 4ms, 8ms and other extended values.

[0076] Since the E1 interface protocol (ie, TS38.463 protocol) does not yet support lower discard timer values, this will result in low-latency services not being supported in the control plane and user plane separation architecture, and there will also be interoperability issues with the core network and terminals.

[0077] In addition, for industrial Internet scenarios, the 3GPP standard introduced Ethernet Header Compression (EHC) technology in the Rel-15 stage to reduce the amount of data transmitted by data packets. The relevant configuration of uplink and downlink header compression is defined in the air interface RRC message. The uplink part includes the following:

[0078] ehc-Uplink-r16 SEQUENCE{

[0079] maxCID-EHC-UL-r16 INTEGER(1..32767),

[0080] drb-ContinueEHC-UL-r16 ENUMERATED{true}OPTIONAL,--Need R

[0081] }

[0082] Among them, maxCID-EHC-UL is used to define the EHC context identifier for uplink. According to the TS38.331 protocol, this value is not allowed to be greater than maxNumberEHC-Contexts; and drb-ContinueEHC-UL-r16 is used to define the continuity of uplink compression. The current E1 interface protocol (i.e., TS38.463 protocol) does not define the maximum value of the context identifier of the uplink EHC, but defines: the sum of maxCID-EHC-UL (maximum value of the context identifier of the uplink EHC) and maxCID-EHC-DL (maximum value of the context identifier of the downlink EHC) should be less than or equal to maxNumberEHC-Contexts (maximum value of the context identifier) ​​indicated by the UE.

[0083] It can be seen that for wireless networks using a CP / UP separation architecture, for example, existing 5G networks or subsequent network designs still have the following defects:

[0084] ① Leading to bearer configuration or modification failure: The base station control plane entity does not know the support of the base station user plane entity for the discard timer, and when the user plane entity does not support the enhanced discard timer extension, the processing behavior of the base station control plane entity, the terminal and the core network is undefined.

[0085] ② Does not support low-latency Industrial Internet services: The corresponding discard timer cannot be configured in the separation architecture, and the performance of Industrial Internet services cannot be guaranteed accordingly, resulting in performance degradation.

[0086] ③ Unable to distinguish the cause of failure: Since the failure cause supported by the protocol can only be "PDCP configuration not supported", which means that the corresponding PDCP configuration cannot be supported, the base station control plane entity cannot know whether it is caused by the unsupported extended information.

[0087] ④ Failures may occur during compression of the uplink Ethernet header: According to the definition in the current E1 interface protocol (i.e., TS38.463 protocol), the value of maxCID-EHC-UL (maximum value of the context identifier of the uplink EHC) can be inferred by calculating the difference between maxNumberEHC-Contexts (maximum value of the context identifier) ​​and maxCID-EHC-DL (maximum value of the context identifier of the downlink EHC). This method differs from the definition in the RRC protocol (i.e., TS38.331 protocol) during the calculation process, resulting in differences in the contexts of the E1 interface and the RRC air interface, which may lead to failures in bearer establishment and modification.

[0088] Based on the above requirements and reason analysis, the current 3GPP Rel-17 5G separation architecture protocol still has defects for low-latency services. In order to ensure that the base station user plane entity supports the relevant characteristics of low latency and reduce configuration errors caused by incomplete protocols, the user's transmission delay can be effectively improved and the user experience can be improved.

[0089] In an embodiment of the present disclosure, a user plane configuration method for supporting low-latency services is provided. When a base station control plane entity receives a session establishment or modification request message sent by a core network control plane entity, the base station control plane entity determines the PDCP discard timer (a first discard timer supported by the radio resource control RRC layer or an extended second discard timer supporting low-latency services) and / or Ethernet header compression EHC configuration required to be supported by the base station and terminal user plane PDCP configuration according to the service feature information of the established or modified session; when the base station control plane entity determines that the base station user plane entity supports the extended PDCP discard timer and / or Ethernet header compression EHC configuration, the base station control plane entity includes the corresponding extended PDCP discard timer and / or EHC configuration in the PDCP configuration information through a bearer context establishment or modification request message and sends it to the base station user plane entity; the base station control plane entity generates a radio resource control RRC reconfiguration message according to the bearer context establishment or modification response message returned by the base station user plane entity and sends it to the terminal; after the terminal returns an RRC reconfiguration completion message to the base station control plane entity, the base station control plane entity returns a session establishment or modification response message to the core network control plane entity.

[0090] Through the user plane configuration method for supporting low-latency services provided in the embodiments of the present invention, low-latency services can be supported accordingly in base stations with a separate control plane and user plane design, thereby avoiding the problem of failure in bearer establishment or modification between the base station control plane entity and the base station user plane entity due to differences in the support capabilities of the base station control plane entity and the base station user plane entity for the low-latency service discard timer.

[0091] The user plane configuration method for supporting low-latency services provided in the embodiments of the present disclosure can be applied but not limited to Figure 4 The communication system shown in Figure 4 As shown, the communication system includes: a core network control plane entity 41, a base station control plane entity 42 and a base station user plane entity 43;

[0092] Among them, the core network control plane entity 41 is used to send a session establishment or modification request message;

[0093] The base station control plane entity 42 is used to determine the PDCP discard timer and / or Ethernet header compression EHC configuration required to be supported by the base station and terminal user plane PDCP configuration according to the service feature information of the established or modified session; when it is determined that the base station user plane entity supports the extended PDCP discard timer and / or Ethernet header compression EHC configuration, the corresponding extended PDCP discard timer and / or EHC configuration is included in the PDCP configuration information and sent to the base station user plane entity 3 through a bearer context establishment or modification request message; wherein the PDCP discard timer includes a first discard timer and / or a second discard timer, the first discard timer is a PDCP discard timer supported by the radio resource control RRC layer, and the second discard timer is an extended PDCP discard timer supporting low-latency services;

[0094] The base station user plane entity 43 is used to return a bearer context establishment or modification response message to the base station control plane entity 42;

[0095] The base station control plane entity 42 is also used to generate a wireless resource control RRC reconfiguration message according to the bearer context establishment or modification response message returned by the base station user plane entity 43, send it to the terminal 44, and return a session establishment or modification response message to the core network control plane entity 41 after receiving the RRC reconfiguration completion message returned by the terminal 44.

[0096] It should be noted that the terminal 44 in the embodiment of the present disclosure can be various electronic devices, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, wearable devices, augmented reality devices, virtual reality devices, etc.

[0097] Optionally, the client of the application installed in different terminal devices 44 is the same, or the client of the same type of application based on different operating systems. Based on the different terminal platforms, the specific form of the client of the application can also be different, for example, the application client can be a mobile client, a PC client, etc.

[0098] In some embodiments, Figure 4As shown, the above-mentioned communication system provided in the embodiment of the present disclosure may also include: a base station separation entity 45, which is used for the base station control plane entity 42 to send an RRC reconfiguration message to the terminal 44 or receive an RRC reconfiguration completion message returned by the terminal.

[0099] Those skilled in the art will know that Figure 4 The number of core network control plane entity 41, base station control plane entity 42, base station user plane entity 43, terminal 44 and base station separation entity 45 is only illustrative, and any number of terminal devices, networks and servers may be provided according to actual needs. This disclosure embodiment does not limit this.

[0100] Under the above system architecture, the present disclosure provides a method for configuring a user plane that supports low-latency services. The method can be applied but not limited to Figure 4 The base station control plane entity is shown.

[0101] Figure 5 A flow chart of a method for configuring a user plane supporting low-latency services in an embodiment of the present disclosure is shown as follows: Figure 5 As shown, the method comprises the following steps:

[0102] S502: The base station control plane entity receives a session establishment or modification request message sent by the core network control plane entity.

[0103] It should be noted that the above-mentioned session establishment or modification request message may include service feature information of the service data transmitted by the established or modified session, such as the service data transmission interval requirement and whether to enable Ethernet header compression, etc.; when the base station control plane entity receives the session establishment request message or session modification request message sent by the core network control plane entity, it can determine the PDCP discard timer and / or Ethernet header compression EHC configuration required to be supported by the base station and terminal user plane PDCP configuration based on the service feature information of the session established or modified by the session establishment request message or the session modification request message.

[0104] In some embodiments, after the base station control plane entity receives a session establishment or modification request message sent by the core network control plane entity, the method also includes: the base station control plane entity determines the PDCP discard timer and / or EHC configuration sent to the base station user plane entity based on the second network management configuration information and the quality service QOS level of the data bearer carried in the session establishment or modification request message, wherein the second network management configuration information includes at least: a mapping relationship between the QOS level and the service data transmission interval; whether the QOS level starts the EHC configuration and the type of the started EHC configuration, and the type of EHC configuration includes any one of the following: uplink compression only, downlink compression only, and bidirectional compression.

[0105] S504, the base station control plane entity determines the PDCP discard timer and / or Ethernet header compression EHC configuration required to be supported by the base station and terminal user plane PDCP configuration according to the service feature information of the established or modified session.

[0106] It should be noted that the PDCP discard timer required to be supported by the PDCP configuration of the base station and the terminal user plane includes a first discard timer or a second discard timer. The first discard timer is a PDCP discard timer supported by the radio resource control RRC layer, and the second discard timer is an extended PDCP discard timer supporting low-latency services.

[0107] In some embodiments, the value of the first discard timer may be: 10ms, 20ms, 30ms, 40ms, 50ms, 60ms, 75ms, 100ms, 150ms, 200ms, 250ms, 300ms, 500ms, 750ms, 1500ms and other extended values; the value of the second discard timer may be: 0.5ms, 1ms, 2ms, 4ms, 8ms and other extended values.

[0108] S506, when the base station control plane entity determines that the base station user plane entity supports the extended PDCP discard timer and / or Ethernet header compression EHC configuration, the base station control plane entity includes the corresponding extended PDCP discard timer and / or EHC configuration in the PDCP configuration information and sends it to the base station user plane entity through a bearer context establishment or modification request message.

[0109] Since there are differences in the support capabilities of the base station control plane entity and the base station user plane entity for the PDCP discard timer and / or EHC configuration, in the above S506, the base station control plane entity can determine the support capabilities of the base station user plane entity for the PDCP discard timer and / or EHC configuration based on the protocol version supported by the base station user plane entity.

[0110] In some embodiments, the user plane configuration method for supporting low-latency services provided in the embodiments of the present disclosure may also determine whether the base station user plane entity supports the extended PDCP discard timer in any of the following ways:

[0111] Mode 1: The base station control plane entity determines whether the base station user plane entity supports the extended PDCP discard timer according to the protocol version information supported by the base station user plane entity carried in the first network management configuration information;

[0112] Mode 2: The base station control plane entity determines whether the base station user plane entity supports the extended PDCP discard timer according to the protocol version indication information carried by the base station user plane entity in the E1 interface establishment or update message, wherein the E1 interface is a communication interface between the base station control plane entity and the base station user plane entity;

[0113] Mode 3: The base station control plane entity determines that the base station user plane entity does not support the extended discard timer set according to the bearer establishment or modification failure reason received on the E1 interface.

[0114] Optionally, the protocol version indication information carried by the base station user plane entity may include, but is not limited to: a protocol version number, which may be represented by enumerated data, for example, v15, v16, and the like.

[0115] In some embodiments, the user plane configuration method for supporting low-latency services provided in the embodiments of the present disclosure may also include the following steps: the base station control plane entity determines to use the timer value in the first discard timer set or the second discard timer set to configure the PDCP discard timer according to the service data transmission interval, wherein the timer value in the first discard timer set is greater than or equal to 10ms; the timer value in the second discard timer set is less than 10ms, and the timer value in the second discard timer set is used to configure the extended PDCP discard timer supported by the base station user plane entity.

[0116] In specific implementation, the size of the discard timer to be used can be determined based on the transmission interval of the low-latency service. If a range of 10ms or above is required, the discard timer is determined to use a value in the first discard timer set, and the discard timer uses a Rel-15 applicable signaling unit; if a range of 0.5ms to 8ms is required, the discard timer is determined to use a value in the second discard timer set, and the discard timer uses a Rel-16 applicable signaling unit.

[0117] In some embodiments, the first discard timer set may include the following timer values: 10ms, 20ms, 30ms, 40ms, 50ms, 60ms, 75ms, 100ms, 150ms, 200ms, 250ms, 300ms, 500ms, 750ms, 1500ms and other extended values; the second discard timer set may include the following timer values: 0.5ms, 1ms, 2ms, 4ms, 8ms and other extended values. The second discard timer set indicates an extended PDCP discard timer.

[0118] Furthermore, in some embodiments, after the base station control plane entity receives the session establishment or modification request message sent by the core network control plane entity, the user plane configuration method for supporting low-latency services provided in the embodiment of the present disclosure may also include the following steps: when the base station control plane entity does not know the protocol version information supported by the base station user plane entity, the base station control plane entity sends the first PDCP configuration information to the base station user plane entity through an E1 interface message carrying a context establishment or modification request message, wherein the first PDCP configuration information includes a PDCP discard timer and / or an EHC configuration;

[0119] The PDCP discard timer configuration includes: a timer value in the first discard timer set or the second discard timer set; the EHC configuration includes: a header compression context identifier, including two types of 7 bits and 15 bits;

[0120] For downstream header compression, at least the following information is included:

[0121] Continuity indication information of downstream header compression, enumeration type, including at least True;

[0122] For upstream header compression, at least the following information is included:

[0123] Continuity indication information of upstream header compression, enumeration type, including at least True;

[0124] The maximum uplink header compression context identifier is MAX_CID_EHC_UL, and its value shall not exceed maxNumberEHC-Contexts.

[0125] In some embodiments, the user plane configuration method for supporting low-latency services provided in the embodiments of the present disclosure may also include the following steps: when the base station control plane entity supports the robust header compression ROHC function, the ROHC configuration parameters and the EHC configuration are included in the PDCP configuration and sent to the base station user plane entity through a bearer context establishment or modification request message, so that the base station user plane entity configures the header compression operation of the corresponding bearer.

[0126] In some embodiments, after the base station control plane entity sends the first PDCP configuration information to the base station user plane entity through an E1 interface message bearer context establishment or modification request message, the user plane configuration method for supporting low-latency services provided in the embodiments of the present disclosure may also include the following steps: the base station user plane entity checks whether it supports the timer value in the first PDCP configuration information of the established or modified bearer; when the base station user plane entity does not support the discard timer value in the first PDCP configuration information of the bearer, the base station user plane entity returns a bearer context establishment or modification failure message and a first failure cause to the base station control plane entity, and the first failure cause is used to indicate that the base station user plane entity does not support the timer value included in the first PDCP configuration information; the base station user plane entity does not delete the user context configuration information and keeps receiving the original PDCP configuration information; when the base station user plane entity supports the timer value in the first PDCP configuration information, it saves the timer value in the first PDCP configuration information. timer value; for each data bearer requested by the base station control plane entity, the base station user plane entity uses the EHC configuration included in the PDCP configuration of the bearer context establishment or modification request message to perform the header compression operation process of the corresponding data bearer, and when the uplink header compression configuration is included in the first PDCP configuration information, checks whether the maximum uplink header compression context identifier MAX_CID_EHC_UL in the first PDCP configuration information exceeds maxNumberEHC-Contexts; when the maximum uplink header compression context identifier MAX_CID_EHC_UL in the first PDCP configuration information exceeds maxNumberEHC-Contexts, the base station user plane entity returns a bearer context establishment or modification failure message and a second failure cause to the base station control plane entity, and the second failure cause is used to indicate that the maximum uplink header compression context identifier in the first PDCP configuration information is greater than maxNumberEHC-Contexts.

[0127] In some embodiments, after the base station user plane entity checks whether it supports the discard timer value in the first PDCP configuration information, the user plane configuration method for supporting low-latency services provided in the embodiments of the present disclosure may also include the following steps: when the base station user plane entity supports the discard timer value in the first PDCP configuration information and other configurations can support the configuration, the base station user plane entity returns a bearer context establishment or modification response message to the base station control plane entity.

[0128] S508, the base station control plane entity generates a radio resource control RRC reconfiguration message according to the bearer context establishment or modification response message returned by the base station user plane entity, and sends it to the terminal;

[0129] It should be noted that the functions of a base station (for example, a 5G base station) can be reconstructed into two functional entities, CU and DU, where the division of CU and DU functions is distinguished by the real-time nature of the processing content. Therefore, in some embodiments, in the user plane configuration method for supporting low-latency services provided in the embodiments of the present disclosure, the base station control plane entity (CU) can send an RRC reconfiguration message to the terminal through the base station separation entity (DU); the terminal can also return an RRC reconfiguration completion message to the base station control plane entity (CU) through the base station separation entity (DU).

[0130] S510, after receiving the RRC reconfiguration completion message returned by the terminal, the base station control plane entity returns a session establishment or modification response message to the core network control plane entity.

[0131] It should be noted that the RRC reconfiguration value message sent by the base station control plane entity to the terminal includes the bearer configuration information successfully established or modified by the base station control plane entity based on the bearer context between the base station control plane entity and the base station user plane entity. Therefore, the terminal can establish an RRC connection according to the bearer configuration information contained in the RRC reconfiguration value message, and after establishing the RRC connection, return an RRC reconfiguration completion message to the base station control plane entity, so that the base station control plane entity returns a session establishment or modification response message to the core network control plane entity.

[0132] In some embodiments, after the base station user plane entity returns a bearer context establishment or modification response message to the base station control plane entity, the user plane configuration method for supporting low-latency services provided in the embodiments of the present disclosure may also include the following steps: the base station control plane entity generates a first RRC reconfiguration message sent to the terminal based on the bearer context establishment or modification response message returned by the base station user plane entity, wherein the discard timer value and / or EHC configuration in the first RRC reconfiguration message are the same as the discard timer value and / or EHC configuration of the first PDCP configuration information.

[0133] Furthermore, in some embodiments, the user plane configuration method for supporting low-latency services provided in the embodiments of the present disclosure may also include the following steps: the base station control plane entity sends a first RRC reconfiguration message to the terminal through the base station separation entity; the base station control plane entity receives a first RRC reconfiguration completion message returned by the terminal according to the first RRC reconfiguration message through the base station separation entity; the base station control plane entity sends a session establishment or modification response message to the core network control plane entity according to the first RRC reconfiguration completion message returned by the terminal to confirm that the bearer configuration in the wireless network is completed.

[0134] In some embodiments, after the base station user plane entity returns a bearer context establishment or modification failure message and a first failure cause to the base station control plane entity, the user plane configuration method for supporting low-latency services provided in the embodiments of the present disclosure may also include the following steps: the base station control plane entity determines that the base station user plane entity does not support the extended discard timer, and reselects a timer value with the smallest value in the first discard timer set, updates the first PDCP configuration information of the corresponding bearer to the second PDCP configuration information, and sends the second PDCP configuration information to the base station user plane entity via an E1 interface message bearer context establishment or modification request message.

[0135] In some embodiments, the user plane configuration method for supporting low-latency services provided in the embodiments of the present disclosure may also include the following steps: the base station user plane entity returns a bearer context establishment or modification response message to the base station control plane entity based on the received second PDCP configuration information; the base station control plane entity generates a second RRC reconfiguration message sent to the terminal based on the bearer context establishment or modification response message returned by the base station user plane entity, wherein the discard timer value and / or EHC configuration in the second RRC reconfiguration message are the same as the discard timer value and / or EHC configuration of the second PDCP configuration information.

[0136] In some embodiments, the user plane configuration method for supporting low-latency services provided in the embodiments of the present disclosure may also include the following steps: the base station control plane entity sends a second RRC reconfiguration message to the terminal through the base station separation entity; the base station control plane entity receives a second RRC reconfiguration completion message returned by the terminal according to the second RRC reconfiguration message through the base station separation entity; the base station control plane entity returns a session establishment or modification response message to the core network control plane entity based on the second RRC reconfiguration completion message returned by the terminal to confirm that the bearer configuration in the wireless network is completed.

[0137] Figure 6 A schematic diagram of the user plane configuration system interaction process supporting low-latency services in an embodiment of the present disclosure is shown. Figure 6 As shown, the specific steps include:

[0138] S602: The base station control plane entity obtains protocol version information of the base station user plane entity.

[0139] In this step, the base station control plane entity can determine the protocol version information supported by the base station user plane entity according to the network management configuration or the protocol version indication information carried by the first base station user plane entity in the E1 interface establishment or update message, and then obtain the service function support capability of the base station user plane entity.

[0140] S604, the core network control plane entity and the base station control plane entity send a PDU session establishment request message or a modification request message to the base station control plane entity.

[0141] In this step, the base station control plane entity receives the session establishment request message or modification request message sent by the core network control plane entity, determines the transmission interval requirement of the service data and whether to enable Ethernet header compression and other information according to the QOS level of the data bearer carried in the message combined with the network management configuration information, and determines the discard timer size to be used according to the transmission interval of the service data. The network management configuration information here includes but is not limited to the following:

[0142] ① The mapping relationship between QOS level and GBR (Guaranteed Bit Rate) rate and transmission interval requirements;

[0143] ②Whether the QOS level enables Ethernet header compression;

[0144] ③ Types of Ethernet header compression (using enumeration type): upstream header compression only, downstream header compression only, and bidirectional header compression.

[0145] S606: The base station control plane entity determines PDCP configuration information for establishing or modifying a bearer context with the base station plane user entity.

[0146] In this step, the base station control plane entity modifies the value set used by the discard timer based on the obtained protocol version indication information of the base station user plane entity. When the protocol version supported by the base station user plane entity is lower than the protocol version supported by the base station control plane entity, only the value in the first discard timer set is used; when the protocol version supported by the base station user plane entity is higher than or equal to the protocol version supported by the base station control plane entity, the value of the discard timer is not modified. If the protocol version indication information of the base station user plane entity is not obtained or the network management has not configured relevant information, the value of the discard timer is not modified. The first PDCP configuration information is sent to the base station user plane entity via an E1 interface message carrying a context establishment request or a modification request message. The first PDCP configuration information includes but is not limited to the following information:

[0147] ① Discard timer: a value in the determined first or second discard timer set;

[0148] ②Ethernet header compression configuration includes but is not limited to:

[0149] Header compression context identifier: ehc-CID-Length-r16 defined in TS38.463 is adopted, which is an enumeration type and includes at least 7-bit and 15-bit types;

[0150] For downlink header compression, the following information is included but not limited to: continuity indication information of downlink header compression, which adopts drb-ContinueEHC-DL-r16 defined in TS38.463, enumeration type, and at least includes "True";

[0151] For uplink header compression, it includes but is not limited to the following information: continuity indication information of uplink header compression, which adopts drb-ContinueEHC-UL-r16 defined in TS38.463, enumeration type, including at least "True"; maximum uplink header compression context identifier: maxCID-EHC-UL-r16 defined in TS38.331 protocol, the value is not allowed to be greater than maxNumberEHC-Contexts.

[0152] S608: The base station control plane entity sends a bearer context establishment or modification request message (carrying a discard timer value and / or EHC configuration) to the base station user plane entity.

[0153] After receiving the first PDCP configuration information, the user plane entity of the base station processes it according to the following process:

[0154] Check whether the value in the discard timer is supported; if not, generate a bearer context failure message and a first failure reason, the first failure reason is that the configuration value version is not supported, indicating that the value is not within the support range of the current version; if supported, perform the following steps:

[0155] ① Save the value of the abandonment timer;

[0156] ② If header compression is configured and uplink header compression is configured, check whether the maximum uplink header compression context identifier exceeds the maximum maxNumberEHC-Contexts; if not, save the header compression context identifier, the continuity indication information of the uplink header compression and the maximum uplink header compression context identifier; if exceeded, generate a bearer context failure message and the second failure reason, the second failure reason indicates that the configuration maximum value is exceeded;

[0157] ③Generate a bearer context establishment / modification response message.

[0158] S610: The user plane entity of the base station returns a bearer context establishment or modification response message (carrying a failure reason) to the control plane entity of the base station.

[0159] In this step, the base station user plane entity carries the configuration result and sends a bearer context failure message or a bearer context establishment / modification response message containing the failure cause to the base station control plane entity. If the base station control plane entity receives a bearer context failure message, it further obtains the failure cause. If the failure cause is the first failure cause, it is determined that the base station user plane cannot receive the configured timer value, and then a minimum value is reselected from the first discard timer set as the new discard timer value. If the failure cause is the second failure cause, the maximum uplink header compression context identifier is updated to the maximum maxNumberEHC-Contexts, and the first PDCP configuration information is updated to the second PDCP configuration information.

[0160] S612: The base station control plane entity updates the PDCP configuration information for establishing or modifying the bearer context with the base station user entity.

[0161] In this step, if the PDCP configuration sent by the base station control plane entity to the base station user plane entity does not successfully establish or modify the bearer context between the base station control plane entity and the base station user plane entity, the PDCP configuration information is updated, and the updated PDCP configuration information is sent to the base station user plane entity through a bearer context establishment or modification request message, and the bearer context between the base station control plane entity and the base station user plane entity is re-established or modified.

[0162] S614: Establish or modify a bearer context based on the updated configuration.

[0163] In this step, if the updated configuration successfully establishes or modifies the bearer context, an RRC message is generated based on the confirmed PDCP configuration information (the first PDCP configuration information or the second PDCP configuration information), and the discard timer value and / or EHC configuration used in the RRC message are the same as the PDCP configuration information (the first PDCP configuration information or the second PDCP configuration information) in which the bearer is successfully established or modified.

[0164] S616: The base station control plane entity sends an RRC message to the terminal through the base station separation entity.

[0165] S618: The terminal returns an RRC configuration confirmation message to the base station control plane entity.

[0166] S620: The base station control plane entity returns a PDU session establishment success indication message to the core network control plane entity.

[0167] Figure 7 A schematic diagram of the process of establishing an E1 interface between a control plane and a user plane in an embodiment of the present disclosure is shown. Figure 7As shown, when the base station user plane entity establishes an E1 interface with the base station user plane entity, the E1 interface response message can carry the indication information of its protocol version so that the base station control plane entity can obtain the protocol version information supported by the base station user plane.

[0168] Two specific embodiments are listed below to illustrate the user plane configuration method for supporting low-latency services provided in the embodiments of the present disclosure:

[0169] Example 1: The user plane entity of the base station supports the value based on the second discard timer set, and the user plane entity of the base station notifies the control plane of the base station of the capability to acquire through the E1 interface.

[0170] 1) The base station control plane entity gNB-CU-CP determines the protocol version information supported by the base station user plane entity gNB-CU-UP entity by carrying the first version indication information in the E1 interface establishment message. The first version indication information includes the following: Version number: v16

[0171] 2) The base station control plane entity gNB-CU-CP receives the session establishment request message sent by the core network control plane entity AMF, and determines the transmission interval requirement and whether to enable Ethernet header compression in its service type characteristics based on the QOS level of the DRB carried therein and the second OMC configuration information, and determines the discard timer size used according to the transmission interval. If the range of 0.5ms to 8ms is required, the discard timer uses a value of 0.5ms in the second discard timer set. The second OMC configuration information includes but is not limited to the following:

[0172] ① The mapping relationship between QOS level, GBR rate and transmission interval requirements;

[0173] ②Whether the QOS level starts Ethernet header compression: QCI = 72;

[0174] ③Header compression type: Uplink header compression only;

[0175] 3) The base station control plane entity gNB-CU-CP, based on obtaining the first version indication information, does not modify the discard timer value in step 2, and sends the first PDCP configuration information to the base station user plane entity gNB-CU-UP entity through an E1 interface message carrying a context establishment request message. The first PDCP configuration information includes the following information: discard timer: 0.5ms.

[0176] 4) After receiving the first PDCP configuration information, the base station user plane entity gNB-CU-UP entity processes it according to the following process:

[0177] ① Check if the value in the discard timer is supported, and save the value of the discard timer;

[0178] ② Generate a bearer context establishment / modification response message.

[0179] 5) After receiving the bearer context establishment response message fed back by the base station user plane entity gNB-CU-UP entity, the base station control plane entity gNB-CU-CP generates an RRC message based on the confirmed first PDCP configuration, wherein the discard timer value used in the RRC message is the same as the first PDCP configuration.

[0180] 6) The base station control plane entity gNB-CU-CP generates an RRC message and sends it to the terminal through the first base station separation entity.

[0181] 7) After receiving the RRC configuration confirmation message sent by the terminal, the base station control plane entity gNB-CU-CP notifies the AMFPDU session establishment success indication message.

[0182] Example 2: The network management has not configured any user plane entity capabilities, so the base station control plane entity does not have any prior information about the base station user plane entity, and the base station user plane entity does not support the second discard timer set value. The base station control plane entity updates the discard timer configuration parameters through secondary reconfiguration.

[0183] 1) The base station control plane entity gNB-CU-CP receives the session establishment request message sent by AMF, and determines the transmission interval requirement and whether to enable Ethernet header compression in its service type characteristics based on the QOS level of the DRB carried therein and the second OMC configuration information, and determines the discard timer size used according to the transmission interval. If the range of 0.5ms to 8ms is required, the discard timer uses a value of 0.5ms in the second discard timer set. The second OMC configuration information includes but is not limited to the following:

[0184] ① The mapping relationship between QOS level, GBR rate and transmission interval requirements;

[0185] ②Whether the QOS level starts Ethernet header compression: QCI = 72;

[0186] ③Header compression type: Uplink header compression only.

[0187] 2) The base station control plane entity gNB-CU-CP corrects the set information used by the repair package timer based on the first version indication information. Since the OMC does not configure the relevant information, the discard timer value in step 1 is not modified. The first PDCP configuration information is sent to the base station user plane entity gNB-CU-UP entity through the E1 interface message carrying context establishment request message. The first PDCP configuration information includes the following information: discard timer: 0.5ms.

[0188] 3) After receiving the first PDCP configuration information, the base station user plane entity gNB-CU-UP entity processes it according to the following process:

[0189] ① Check that the value in the discard timer is not supported;

[0190] ② Generate a bearer context failure message and a first failure reason, where the first failure reason is that the configuration value version is not supported.

[0191] 4) The base station control plane entity gNB-CU-UP entity sends a bearer context failure message including the failure cause to the gNB-CU-CP based on the bearer configuration result.

[0192] 5) If the base station control plane entity gNB-CU-CP receives a bearer context failure message, and since the failure cause is the first failure cause, it is determined that the base station user plane entity gNB-CU-UP cannot receive the configured timer value, then a value of 10ms is reselected from the first discard timer set. And the first PDCP configuration information is updated to the second PDCP configuration information.

[0193] 6) The base station control plane entity gNB-CU-CP sends the second PDCP configuration information to the base station user plane entity gNB-CU-UP entity through the E1 interface message carrying context establishment request message for configuring the PDCP configuration.

[0194] 7) After the base station control plane entity gNB-CU-CP receives the bearer context establishment response or modification response message fed back by the base station user plane entity gNB-CU-UP entity, it generates an RRC message based on the confirmed second PDCP configuration, wherein the discard timer value used in the RRC message is the same as the second PDCP configuration.

[0195] 8) The base station control plane entity gNB-CU-CP generates an RRC message and sends it to the terminal through the first base station separation entity.

[0196] 9) After receiving the RRC configuration confirmation message sent by the terminal, the base station control plane entity gNB-CU-CP notifies the AMF of the PDU session establishment success indication message.

[0197] Example 3: The base station user plane entity correctly configures the uplink header compression related configuration parameters and completes the bearer configuration process with the base station user plane entity through the E1 interface.

[0198] 1) The base station control plane entity gNB-CU-CP receives the session establishment request message sent by the core network control plane entity AMF, and determines the transmission interval requirement and whether to enable Ethernet header compression in its service type characteristics based on the QOS level of the DRB carried therein and the second OMC configuration information, and determines the discard timer size to be used according to the transmission interval. If a range of more than 10ms is required, the discard timer uses a value of 20ms in the first discard timer set.

[0199] The second OMC configuration information includes but is not limited to the following:

[0200] ① The mapping relationship between QOS level, GBR rate and transmission interval requirements;

[0201] ②Whether the QOS level starts Ethernet header compression: QCI = 72;

[0202] ③Header compression type: Uplink only.

[0203] 2) The base station control plane entity gNB-CU-CP, after obtaining the first version indication information, does not modify the discard timer value in step 1 because the OMC has not configured relevant information. It then sends the first PDCP configuration information to the base station user plane entity gNB-CU-UP entity through an E1 interface message carrying a context establishment modification request message. The first PDCP configuration information includes the following information:

[0204] ①Discard timer: 20ms

[0205] ②Ethernet header compression configuration, including but not limited to the following:

[0206] Header compression context identifier: 15 bits;

[0207] "True" for downstream header compression;

[0208] For uplink header compression, the following information is included: uplink header compression continuity indication information: "True"; maximum uplink header compression context identifier: maxNumberEHC-Contexts-10.

[0209] 3) After receiving the first PDCP configuration information, the base station control plane entity gNB-CU-UP entity processes it according to the following process:

[0210] ① Check that the value in the discard timer can be supported and save the value of the discard timer; if header compression is configured and uplink header compression is configured, check that the maximum uplink header compression context identifier does not exceed the maximum maxNumberEHC-Contexts; if it does not exceed, save the header compression context identifier and the continuity indication information of the uplink header compression and the maximum uplink header compression context identifier;

[0211] ② Generate a bearer context establishment response message.

[0212] 4) After the base station control plane entity gNB-CU-CP receives the bearer context establishment response message fed back by the base station user plane entity gNB-CU-UP entity, it generates an RRC message based on the confirmed first PDCP configuration, wherein the discard timer value used in the RRC message is the same as the first PDCP configuration.

[0213] 5) The base station control plane entity gNB-CU-CP generates an RRC message and sends it to the terminal through the first base station separation entity.

[0214] 6) After receiving the RRC configuration confirmation message sent by the terminal, the base station control plane entity gNB-CU-CP notifies the AMFPDU session establishment success indication message.

[0215] Through the user plane configuration method for supporting low-latency services provided in the embodiments of the present disclosure, the following technical effects can be achieved but are not limited to: ① The problem that the bearer cannot be established or modified successfully when there is a difference in the support capabilities of the base station control plane entity and the base station user plane entity for the low-latency service discard timer is solved, thereby avoiding the bearer release problem caused by configuration failure; ② By defining new failure reasons, the base station control plane entity is supported to re-identify the error cause and reconfigure the PDCP parameters based on the cause value; ③ Overcoming the inconsistent understanding of the header compression context identifier between the base station control plane entity and the base station user plane entity, thereby reducing errors during air interface transmission and reducing the user call drop rate.

[0216] Based on the same inventive concept, a base station is also provided in an embodiment of the present disclosure. The base station may be a base station of 5G or later versions (for example, 5G NR NB), or a base station in other communication systems (for example, eNB base station). It should be noted that the specific type of network side equipment is not limited in the embodiment of the present disclosure.

[0217] Figure 8 A schematic diagram of a base station in an embodiment of the present disclosure is shown. Figure 8 As shown, the base station includes: a processor 801; and a memory 802, which is used to store executable instructions of the processor 801;

[0218] Among them, the processor 801 is configured to execute the following steps of the above-mentioned method embodiment by executing executable instructions: the base station control plane entity receives the session establishment or modification request message sent by the core network control plane entity; the base station control plane entity determines the PDCP discard timer and / or Ethernet header compression EHC configuration required to be supported by the base station and terminal user plane PDCP configuration based on the service feature information of the established or modified session; the PDCP discard timer includes a first discard timer or a second discard timer, the first discard timer is a PDCP discard timer supported by the radio resource control RRC layer, and the second discard timer is an extended PDCP discard timer supporting low-latency services. device; when the base station control plane entity determines that the base station user plane entity supports the extended PDCP discard timer and / or Ethernet header compression EHC configuration, the base station control plane entity includes the corresponding extended PDCP discard timer and / or EHC configuration in the PDCP configuration information and sends it to the base station user plane entity through a bearer context establishment or modification request message; the base station control plane entity generates a radio resource control RRC reconfiguration message according to the bearer context establishment or modification response message returned by the base station user plane entity, and sends it to the terminal; after receiving the RRC reconfiguration completion message returned by the terminal, the base station control plane entity returns a session establishment or modification response message to the core network control plane entity.

[0219] In some embodiments, the above-mentioned processor 801 is also used to execute the following steps of the above-mentioned method embodiment: the base station control plane entity determines whether the base station user plane entity supports the extended PDCP discard timer based on the protocol version information supported by the base station user plane entity carried in the first network management configuration information; the base station control plane entity determines whether the base station user plane entity supports the extended PDCP discard timer based on the protocol version indication information carried by the base station user plane entity in the E1 interface establishment or update message; the base station control plane entity determines that the base station user plane entity does not support the extended discard timer set based on the bearer establishment or modification failure reason received by the E1 interface.

[0220] In some embodiments, the protocol version indication information uses an enumeration type to indicate the protocol version supported by the user plane entity of the base station.

[0221] In some embodiments, the protocol version supported by the user plane entity of the base station includes any one of the following: 3GPP Rel-15 version, a version before 3GPP Rel-16-v80, and a version subsequent to 3GPP Rel-16-v90.

[0222] In some embodiments, the above-mentioned processor 801 is also used to execute the following steps of the above-mentioned method embodiment: the base station control plane entity determines the PDCP discard timer and / or EHC configuration sent to the base station user plane entity based on the second network management configuration information and the quality service QOS level of the data bearer carried in the session establishment or modification request message, wherein the second network management configuration information at least includes: a mapping relationship between the QOS level and the service data transmission interval; whether the QOS level starts the EHC configuration and the type of the started EHC configuration, and the type of EHC configuration includes any one of the following: uplink compression only, downlink compression only, and bidirectional compression.

[0223] In some embodiments, the above-mentioned processor 801 is also used to execute the following steps of the above-mentioned method embodiment: the base station control plane entity determines to configure the PDCP discard timer using the timer value in the first discard timer set or the second discard timer set according to the service data transmission interval, wherein the timer value in the first discard timer set is greater than or equal to 10ms; the timer value in the second discard timer set is less than 10ms, and the timer value in the second discard timer set is used to configure the extended PDCP discard timer supported by the base station user plane entity.

[0224] In some embodiments, the first discard timer set includes at least the following timer values: 10ms, 20ms, 30ms, 40ms, 50ms, 60ms, 75ms, 100ms, 150ms, 200ms, 250ms, 300ms, 500ms, 750ms, 1500ms; the second discard timer set includes at least the following timer values: 0.5ms, 1ms, 2ms, 4ms, 8ms, and the second discard timer set indicates an extended PDCP discard timer.

[0225] In some embodiments, the processor 801 is further used to execute the following steps of the method embodiment: when the base station control plane entity does not know the protocol version information supported by the base station user plane entity, the base station control plane entity sends the first PDCP configuration information to the base station user plane entity through an E1 interface message carrying a context establishment or modification request message, wherein the first PDCP configuration information includes a PDCP discard timer and / or an EHC configuration;

[0226] The PDCP discard timer configuration includes: a timer value in the first discard timer set or the second discard timer set; the EHC configuration includes: a header compression context identifier, including two types of 7 bits and 15 bits;

[0227] For downstream header compression, at least the following information is included:

[0228] Continuity indication information of downstream header compression, enumeration type, including at least True;

[0229] For upstream header compression, at least the following information is included:

[0230] Continuity indication information of upstream header compression, enumeration type, including at least True;

[0231] The maximum uplink header compression context identifier is MAX_CID_EHC_UL, and its value shall not exceed maxNumberEHC-Contexts.

[0232] In some embodiments, the above-mentioned processor 801 is also used to execute the following steps of the above-mentioned method embodiment: when the base station control plane entity supports the robust header compression ROHC function, the ROHC configuration parameters and the EHC configuration are included in the PDCP configuration and sent to the base station user plane entity through a bearer context establishment or modification request message, so that the base station user plane entity configures the header compression operation of the corresponding bearer.

[0233] In some embodiments, the processor 801 is further used to execute the following steps of the method embodiment: the base station user plane entity checks whether it supports the timer value in the first PDCP configuration information of the established or modified bearer; when the base station user plane entity does not support the discard timer value in the first PDCP configuration information of the bearer, the base station user plane entity returns a bearer context establishment or modification failure message and a first failure cause to the base station control plane entity, and the first failure cause is used to indicate that the base station user plane entity does not support the timer value contained in the first PDCP configuration information; the base station user plane entity does not delete the user context configuration information and keeps receiving the original PDCP configuration information; when the base station user plane entity supports the timer value in the first PDCP configuration information, the timer value in the first PDCP configuration information is saved; the base station user plane entity for each data bearer requested by the base station control plane entity , use the EHC configuration included in the PDCP configuration of the bearer context establishment or modification request message to perform the header compression operation process of the corresponding data bearer, and when the uplink header compression configuration is included in the first PDCP configuration information, check whether the maximum uplink header compression context identifier MAX_CID_EHC_UL in the first PDCP configuration information exceeds maxNumberEHC-Contexts; when the maximum uplink header compression context identifier MAX_CID_EHC_UL in the first PDCP configuration information exceeds maxNumberEHC-Contexts, the base station user plane entity returns a bearer context establishment or modification failure message and a second failure cause to the base station control plane entity, and the second failure cause is used to indicate that the maximum uplink header compression context identifier in the first PDCP configuration information is greater than maxNumberEHC-Contexts.

[0234] In some embodiments, the above-mentioned processor 801 is also used to execute the following steps of the above-mentioned method embodiment: when the base station user plane entity supports the discard timer value in the first PDCP configuration information and other configurations can support the configuration, the base station user plane entity returns a bearer context establishment or modification response message to the base station control plane entity.

[0235] In some embodiments, the above-mentioned processor 801 is also used to execute the following steps of the above-mentioned method embodiment: the base station control plane entity generates a first RRC reconfiguration message sent to the terminal according to the bearer context establishment or modification response message returned by the base station user plane entity, wherein the discard timer value and / or EHC configuration in the first RRC reconfiguration message are the same as the discard timer value and / or EHC configuration of the first PDCP configuration information.

[0236] In some embodiments, the above-mentioned processor 801 is also used to execute the following steps of the above-mentioned method embodiment: the base station control plane entity sends a first RRC reconfiguration message to the terminal through the base station separation entity; the base station control plane entity receives a first RRC reconfiguration completion message returned by the terminal according to the first RRC reconfiguration message through the base station separation entity; the base station control plane entity sends a session establishment or modification response message to the core network control plane entity according to the first RRC reconfiguration completion message returned by the terminal to confirm that the bearer configuration in the wireless network is completed.

[0237] In some embodiments, the above-mentioned processor 801 is also used to execute the following steps of the above-mentioned method embodiment: the base station control plane entity determines that the base station user plane entity does not support the extended discard timer, and reselects a timer value with the smallest value in the first discard timer set, updates the first PDCP configuration information of the corresponding bearer to the second PDCP configuration information, and sends the second PDCP configuration information to the base station user plane entity through the E1 interface message carrying context establishment or modification request message.

[0238] In some embodiments, the above-mentioned processor 801 is also used to execute the following steps of the above-mentioned method embodiment: the base station user plane entity returns a bearer context establishment or modification response message to the base station control plane entity based on the received second PDCP configuration information; the base station control plane entity generates a second RRC reconfiguration message sent to the terminal based on the bearer context establishment or modification response message returned by the base station user plane entity, wherein the discard timer value and / or EHC configuration in the second RRC reconfiguration message are the same as the discard timer value and / or EHC configuration of the second PDCP configuration information.

[0239] In some embodiments, the above-mentioned processor 801 is also used to execute the following steps of the above-mentioned method embodiment: the base station control plane entity sends a second RRC reconfiguration message to the terminal through the base station separation entity; the base station control plane entity receives a second RRC reconfiguration completion message returned by the terminal according to the second RRC reconfiguration message through the base station separation entity; the base station control plane entity returns a session establishment or modification response message to the core network control plane entity according to the second RRC reconfiguration completion message returned by the terminal to confirm that the bearer configuration in the wireless network is completed.

[0240] Based on the same inventive concept, a computer-readable storage medium is also provided in an embodiment of the present disclosure. The computer-readable storage medium may be a readable signal medium or a readable storage medium. Fig. 9 A schematic diagram of a computer-readable storage medium in an embodiment of the present disclosure is shown. Fig. 9 As shown, a program product capable of implementing the above method of the present disclosure is stored on the computer-readable storage medium 900. In some possible implementations, various aspects of the present disclosure may also be implemented in the form of a program product, which includes a program code. When the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps according to various exemplary implementations of the present disclosure described in the above “Exemplary Method” section of this specification.

[0241] More specific examples of computer-readable storage media in the present disclosure may include, but are not limited to, an electrical connection having one or more conductors, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0242] In the present disclosure, a computer readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, wherein a readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A readable signal medium may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0243] Alternatively, the program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0244] In a specific implementation, the program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).

[0245] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.

[0246] In addition, although the steps of the method in the present disclosure are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0247] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0248] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure, which follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the appended claims.

Claims

1. A user plane configuration method supporting low-latency services, characterized in that: include: The base station control plane entity receives a session establishment or modification request message sent by the core network control plane entity; The base station control plane entity determines the PDCP discard timer required to be supported by the base station and the terminal user plane PDCP configuration; the PDCP discard timer is determined according to the service feature information of the established or modified session, and the PDCP discard timer includes a second discard timer, and the second discard timer is an extended PDCP discard timer supporting low-latency services; When the base station control plane entity determines that the base station user plane entity supports the extended PDCP discard timer, the base station control plane entity includes the corresponding extended PDCP discard timer in the PDCP configuration information and sends it to the base station user plane entity through a bearer context establishment or modification request message; The base station control plane entity generates a radio resource control RRC reconfiguration message according to the bearer context establishment or modification response message returned by the base station user plane entity, and sends the message to the terminal; After receiving the RRC reconfiguration completion message returned by the terminal, the base station control plane entity returns a session establishment or modification response message to the core network control plane entity.

2. The user plane configuration method for supporting low-latency services according to claim 1, characterized in that: The method further includes any one of the following: The base station control plane entity determines, according to the protocol version information supported by the base station user plane entity carried in the first network management configuration information, whether the base station user plane entity supports the extended PDCP discard timer; The base station control plane entity determines, according to the protocol version indication information carried by the base station user plane entity in the E1 interface establishment or update message, whether the base station user plane entity supports the extended PDCP discard timer; The base station control plane entity determines, according to the bearer establishment or modification failure reason received via the E1 interface, that the base station user plane entity does not support the extended discard timer set.

3. The user plane configuration method for supporting low-latency services according to claim 2, characterized in that: The protocol version indication information uses an enumeration type to indicate the protocol version supported by the base station user plane entity.

4. The user plane configuration method for supporting low-latency services according to claim 3, characterized in that: The protocol version supported by the base station user plane entity includes any one of the following: 3GPP Rel-15 version, 3GPP Rel-16-v80 and earlier versions, and 3GPP Rel-16-v90 and later versions.

5. The method for configuring a user plane supporting low-latency services according to claim 1, characterized in that: After the base station control plane entity receives the session establishment or modification request message sent by the core network control plane entity, the method further includes: The base station control plane entity determines the PDCP discard timer and EHC configuration sent to the base station user plane entity according to the second network management configuration information and the quality service QOS level of the data bearer carried in the session establishment or modification request message, wherein the second network management configuration information at least includes: The mapping relationship between QOS level and service data transmission interval; Whether the QOS level activates the EHC configuration and the type of the activated EHC configuration, wherein the type of the EHC configuration includes any one of the following: uplink compression only, downlink compression only, and bidirectional compression.

6. The user plane configuration method for supporting low-latency services according to claim 5, characterized in that: The PDCP discard timer also includes: a first discard timer; the first discard timer is a PDCP discard timer supported by a radio resource control RRC layer; Wherein, the method further comprises: The base station control plane entity determines to configure the PDCP discard timer using a timer value in a first discard timer set or a second discard timer set according to a service data transmission interval, wherein the timer value in the first discard timer set is greater than or equal to 10ms; the timer value in the second discard timer set is less than 10ms, and the timer value in the second discard timer set is used to configure an extended PDCP discard timer supported by the base station user plane entity.

7. The method for configuring a user plane supporting low-latency services according to claim 6, characterized in that: The first discard timer set includes at least the following timer values: 10ms, 20ms, 30ms, 40ms, 50ms, 60ms, 75ms, 100ms, 150ms, 200ms, 250ms, 300ms, 500ms, 750ms, 1500ms; the second discard timer set includes at least the following timer values: 0.5ms, 1ms, 2ms, 4ms, 8ms, and the second discard timer set indicates an extended PDCP discard timer.

8. The method for configuring a user plane supporting low-latency services according to claim 7, characterized in that: After the base station control plane entity receives the session establishment or modification request message sent by the core network control plane entity, the method further includes: When the base station control plane entity does not know the protocol version information supported by the base station user plane entity, the base station control plane entity sends the first PDCP configuration information to the base station user plane entity through an E1 interface message carrying a context establishment or modification request message, wherein the first PDCP configuration information includes a PDCP discard timer and an EHC configuration; The PDCP discard timer configuration includes: A timer value in the first discard timer set or the second discard timer set; The EHC configuration includes: Header compression context identifier, including 7-bit and 15-bit; For downstream header compression, at least the following information is included: Continuity indication information of downstream header compression, enumeration type, including at least True; For upstream header compression, at least the following information is included: Continuity indication information of upstream header compression, enumeration type, including at least True; The maximum uplink header compression context identifier is MAX_CID_EHC_UL, and its value shall not exceed maxNumberEHC-Contexts.

9. The user plane configuration method for supporting low-latency services according to claim 8, characterized in that: The method further comprises: When the base station control plane entity supports the robust header compression ROHC function, the ROHC configuration parameters and the EHC configuration are included in the PDCP configuration and sent to the base station user plane entity through a bearer context establishment or modification request message, so that the base station user plane entity configures the header compression operation of the corresponding bearer.

10. The method for configuring a user plane supporting low-latency services according to claim 8, characterized in that: After the base station control plane entity sends the first PDCP configuration information to the base station user plane entity through an E1 interface message carrying a context establishment or modification request message, the method further includes: The base station user plane entity checks whether it supports the timer value in the first PDCP configuration information of the established or modified bearer; When the base station user plane entity does not support the discard timer value in the first PDCP configuration information of the bearer, the base station user plane entity returns a bearer context establishment or modification failure message and a first failure cause to the base station control plane entity, where the first failure cause is used to indicate that the base station user plane entity does not support the timer value included in the first PDCP configuration information; the base station user plane entity does not delete the user context configuration information, and keeps receiving the original PDCP configuration information; When the base station user plane entity supports the timer value in the first PDCP configuration information, save the timer value in the first PDCP configuration information; The base station user plane entity performs a header compression operation process of the corresponding data bearer for each data bearer requested by the base station control plane entity using the EHC configuration included in the bearer context establishment or modification request message PDCP configuration, and checks whether the maximum uplink header compression context identifier MAX_CID_EHC_UL in the first PDCP configuration information exceeds maxNumberEHC-Contexts when the first PDCP configuration information includes an uplink header compression configuration; When the maximum uplink header compression context identifier MAX_CID_EHC_UL in the first PDCP configuration information exceeds maxNumberEHC-Contexts, the base station user plane entity returns a bearer context establishment or modification failure message and a second failure cause to the base station control plane entity, and the second failure cause is used to indicate that the maximum uplink header compression context identifier in the first PDCP configuration information is greater than maxNumberEHC-Contexts.

11. The method for configuring a user plane supporting low-latency services according to claim 10, characterized in that: After the base station user plane entity checks whether it supports the discard timer value in the first PDCP configuration information, the method further includes: When the base station user plane entity supports the discard timer value in the first PDCP configuration information and other configurations can support configuration, the base station user plane entity returns a bearer context establishment or modification response message to the base station control plane entity.

12. The user plane configuration method for supporting low-latency services according to claim 11, characterized in that: After the base station user plane entity returns a bearer context establishment or modification response message to the base station control plane entity, the method further includes: The base station control plane entity generates a first RRC reconfiguration message sent to the terminal according to the bearer context establishment or modification response message returned by the base station user plane entity, wherein the discard timer value and EHC configuration in the first RRC reconfiguration message are the same as the discard timer value and EHC configuration of the first PDCP configuration information.

13. The method for configuring a user plane supporting low-latency services according to claim 12, characterized in that: The method further comprises: The base station control plane entity sends a first RRC reconfiguration message to the terminal through the base station separation entity; The base station control plane entity receives, through the base station separation entity, a first RRC reconfiguration completion message returned by the terminal according to the first RRC reconfiguration message; The base station control plane entity sends a session establishment or modification response message to the core network control plane entity according to the first RRC reconfiguration completion message returned by the terminal to confirm that the bearer configuration in the wireless network is completed.

14. The method for configuring a user plane supporting low-latency services according to claim 10, characterized in that: After the base station user plane entity returns a bearer context establishment or modification failure message and a first failure cause to the base station control plane entity, the method further includes: The base station control plane entity determines that the base station user plane entity does not support the extended discard timer, and reselects a timer value with the smallest value in the first discard timer set, updates the first PDCP configuration information of the corresponding bearer to the second PDCP configuration information, and sends the second PDCP configuration information to the base station user plane entity via an E1 interface message carrying a context establishment or modification request message.

15. The method for configuring a user plane supporting low-latency services according to claim 14, characterized in that: The method further comprises: The base station user plane entity returns a bearer context establishment or modification response message to the base station control plane entity according to the received second PDCP configuration information; The base station control plane entity generates a second RRC reconfiguration message sent to the terminal based on the bearer context establishment or modification response message returned by the base station user plane entity, wherein the discard timer value and EHC configuration in the second RRC reconfiguration message are the same as the discard timer value and EHC configuration of the second PDCP configuration information.

16. The method for configuring a user plane supporting low-latency services according to claim 15, characterized in that: The method further comprises: The base station control plane entity sends a second RRC reconfiguration message to the terminal through the base station separation entity; The base station control plane entity receives, through the base station separation entity, a second RRC reconfiguration completion message returned by the terminal according to the second RRC reconfiguration message; The base station control plane entity returns a session establishment or modification response message to the core network control plane entity according to the second RRC reconfiguration completion message returned by the terminal to confirm that the bearer configuration in the wireless network is completed.

17. A communication system, characterized in that: include: Core network control plane entity, base station control plane entity and base station user plane entity; The core network control plane entity is used to send a session establishment or modification request message; The base station control plane entity is used to determine the PDCP discard timer required to be supported by the base station and the terminal user plane PDCP configuration according to the service feature information of the established or modified session; when it is determined that the base station user plane entity supports the extended PDCP discard timer, the corresponding extended PDCP discard timer is included in the PDCP configuration information and sent to the base station user plane entity through a bearer context establishment or modification request message; the PDCP discard timer includes a second discard timer, and the second discard timer is an extended PDCP discard timer supporting low-latency services; The base station user plane entity is used to return a bearer context establishment or modification response message to the base station control plane entity; The base station control plane entity is also used to generate a radio resource control RRC reconfiguration message according to the bearer context establishment or modification response message returned by the base station user plane entity, send it to the terminal, and return a session establishment or modification response message to the core network control plane entity after receiving the RRC reconfiguration completion message returned by the terminal.

18. The communication system according to claim 17, characterized in that: The communication system further includes: a base station separation entity, which is used for the base station control plane entity to send an RRC reconfiguration message to the terminal or receive an RRC reconfiguration completion message returned by the terminal.

19. A base station, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to execute the user plane configuration method for supporting low-latency services as described in any one of claims 1 to 16 by executing the executable instructions.

20. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for configuring a user plane supporting low-latency services described in any one of claims 1 to 16 is implemented.

Images