WO2019062244A1 - 一种同步方法和装置、网元及存储介质 - Google Patents

一种同步方法和装置、网元及存储介质 Download PDF

Info

Publication number
WO2019062244A1
WO2019062244A1 PCT/CN2018/093804 CN2018093804W WO2019062244A1 WO 2019062244 A1 WO2019062244 A1 WO 2019062244A1 CN 2018093804 W CN2018093804 W CN 2018093804W WO 2019062244 A1 WO2019062244 A1 WO 2019062244A1
Authority
WO
WIPO (PCT)
Prior art keywords
entity
request
synchronization operation
information
synchronization
Prior art date
Application number
PCT/CN2018/093804
Other languages
English (en)
French (fr)
Inventor
杨立
黄河
高媛
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US16/650,850 priority Critical patent/US11382052B2/en
Priority to EP18863335.8A priority patent/EP3691354B1/en
Publication of WO2019062244A1 publication Critical patent/WO2019062244A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/004—Synchronisation arrangements compensating for timing error of reception due to propagation delay
    • H04W56/0045—Synchronisation arrangements compensating for timing error of reception due to propagation delay compensating for timing error by altering transmission time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]

Definitions

  • the embodiments of the present disclosure relate to the field of communications technologies, but are not limited to the field of communications technologies, and particularly, to a synchronization method and apparatus, a network element, and a storage medium.
  • the BBU Baseband Unit
  • LTE Long Term Evolution
  • CPRI Common Public Radio Interface
  • RRU Remote Radio Unit
  • RRU Remote Radio Unit
  • RRU Remote Radio Unit
  • the air interface rate of the 5G base station (gNB) is increased to tens of Gbps, the transmission traffic demand of the CPRI interface will rise to at least the Tbps level, which brings huge cost and difficulty in deploying the front-end network interface (Fronthaul). pressure. Therefore, in 5G NR (New Radio, new radio system), it is necessary to redefine the division mode of the preamble network interface in the base station gNB.
  • 5G NR New Radio, new radio system
  • the delay-insensitive network function is placed on the first network element (for example, : CU (Centralized Unit), the delay-sensitive network function is placed in the second network element (for example, DU (Distributed Unit)).
  • CU Centralized Unit
  • DU Distributed Unit
  • a centralized deployment gNB may include a gNB-CU and multiple gNB-DUs under its jurisdiction, which are connected by a forward link logical interface F1, for example, an F1-C interface or an F1-U interface.
  • a gNB-DU can only be connected to and controlled by a gNB-CU. There is no direct interface between the gNB-DU and the adjacent gNB-DU. From the outside, the NG interface and the Xn interface are terminated on the gNB-CU unit, and the gNB-DU is not visible to the outside. To ensure reliability, a gNB-DU may also be connected to multiple gNB-CUs from the perspective of actual deployment.
  • Embodiments of the present disclosure provide a synchronization method and apparatus, a synchronization network element, and a storage medium.
  • Embodiments of the present disclosure provide a synchronization method, including:
  • a Control Plane (CP) entity determines a to-be-stated content, an object, and a reporting policy for performing a synchronization operation; wherein the synchronization operation includes at least one of: a working state synchronization operation, and a resource state synchronization operation;
  • the CP entity sends a request for a synchronization operation to a User Plane (UP) entity, where the request carries configuration information of the content to be statistic, the object, and the reporting policy of the synchronization operation.
  • UP User Plane
  • the embodiment of the present disclosure further provides a synchronization method, including:
  • the user plane UP entity receives a request for a synchronization operation sent by the CP entity, where the request carries configuration information of the to-be-stated content, the object, and the reporting policy of the synchronization operation, where the synchronization operation includes at least one of the following: Synchronous operation, resource status synchronization operation;
  • the embodiment of the present disclosure further provides a synchronization device, including:
  • a first determining module configured to determine a to-be-stated content, an object, and a reporting policy for performing a synchronization operation, where the synchronization operation includes at least one of: a working state synchronization operation, and a resource state synchronization operation;
  • the first sending module is configured to send a request for a synchronization operation to the user plane UP entity, where the request carries configuration information of the content to be statistic, the object, and the reporting policy of the synchronization operation.
  • the embodiment of the present disclosure further provides a synchronization device, including:
  • a second receiving module configured to receive a request for a synchronization operation sent by the CP entity, where the request carries configuration information of the to-be-stated content, the object, and the reporting policy of the synchronization operation, where the synchronization operation includes at least one of the following : work state synchronization operation, resource state synchronization operation;
  • a second determining module configured to determine to accept or reject configuration information in the request and the request
  • a second sending module configured to send, according to a decision of the determining module, a response to the synchronization operation to the CP entity, where the response carries feedback information that accepts or rejects the request, and when the request is accepted, Carrying feedback information that all of the configuration information carried in the request is accepted or partially accepted.
  • Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions for performing the synchronization method described above.
  • the embodiment of the present disclosure further provides a network element, including: a transceiver; a memory; a processor, respectively connected to the transceiver and the memory, configured to control the transceiver by execution of computer executable instructions Information transmission and reception and information storage of the memory, and the above synchronization method.
  • a network element including: a transceiver; a memory; a processor, respectively connected to the transceiver and the memory, configured to control the transceiver by execution of computer executable instructions Information transmission and reception and information storage of the memory, and the above synchronization method.
  • the embodiment of the present disclosure includes: the control plane CP entity determines the to-be-stated content, the object, and the reporting policy for performing the synchronization operation; wherein the synchronization operation includes at least one of: a working state synchronization operation, a resource state synchronization operation, and the CP entity Sending a request for a synchronization operation to the user plane UP entity, where the request carries configuration information of the content to be statistic, the object, and the reporting policy of the synchronization operation.
  • the control plane CP entity determines the to-be-stated content, the object, and the reporting policy for performing the synchronization operation
  • the synchronization operation includes at least one of: a working state synchronization operation, a resource state synchronization operation, and the CP entity Sending a request for a synchronization operation to the user plane UP entity, where the request carries configuration information of the content to be statistic, the object, and the reporting policy of the synchronization operation.
  • the corresponding control plane response operation may be performed according to the statistical result of the synchronization operation reported by the UP entity, so that the UP entity can work more efficiently and efficiently, for example, the UP resource is more rationally utilized, and the DRB ( The data transmission on the Data Radio Bearer (data radio bearer) is restored to normal in time, and the fault in the UP entity is cleared in time.
  • DRB The data transmission on the Data Radio Bearer (data radio bearer) is restored to normal in time, and the fault in the UP entity is cleared in time.
  • the CP entity may configure different objects of the synchronization operation at different levels of granularity, and different to-be-stated contents may be associated with different granular operation objects.
  • the CP entity may configure the UP entity to perform the synchronization operation in the manner of event definition triggering, time period triggering, event, and time period triggering, and may perform synchronous operation according to different real-time requirements of the information content to be synchronized. A balance between real-time and efficiency efficiency overhead costs.
  • FIG. 1 is a schematic diagram of a 5G NR CU-DU split deployment (gNB centralized deployment) architecture
  • FIG. 2 is a schematic diagram of a physical separation of CP and UP
  • FIG. 3 is a flowchart (CP entity) of a synchronization method according to an embodiment of the present disclosure
  • FIG. 4 is a flowchart (UP entity) of a synchronization method according to an embodiment of the present disclosure
  • FIG. 5 is a flowchart of a synchronization method (CP entity and UP entity) according to an embodiment of the present disclosure
  • FIG. 6 is a schematic structural diagram of a synchronization system according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a synchronization device according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a synchronization device according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic flowchart of application example 1 of an embodiment of the present disclosure.
  • FIG. 10 is a schematic flowchart of application example 2 of an embodiment of the present disclosure.
  • FIG. 11 is a schematic flowchart of Application Example 3 of an embodiment of the present disclosure.
  • FIG. 13 is a schematic flowchart of application example 5 of an embodiment of the present disclosure.
  • FIG. 1 it is a schematic diagram of a 5G NR CU-DU split deployment (gNB centralized deployment) architecture.
  • the 5G user service and the unbalanced user service physical distribution required by different QoS (Quality of Service) services have different requirements for network deployment and data transmission performance of 5G networks. These different types of data services are often interwoven. Coexisting, or hotspots in local areas, thus making the current relatively closed network architecture unable to support various 5G communication scenarios more efficiently.
  • QoS Quality of Service
  • Control plane referred to as ECU entity
  • User plane UP for physical segmentation
  • CP and UP function set which has been divided by logic level in the past, but physically integrated in a single base station network element
  • CP and UP can Deployed in different geographical locations, independently configured, resource extension and function upgrade, it can be deployed more flexibly and efficiently to meet the various business requirements of 5G.
  • the physical separation architecture of CP and UP is shown in Figure 2.
  • the CP entity can be deployed in a network central office such as a CU entity, and manage multiple UP entities in the jurisdiction to efficiently coordinate service load resources between multiple UP entities to achieve load balancing.
  • the CP can also be deployed at the edge of the network near the DU entity according to the requirements.
  • the UP entity can be deployed in the network database center such as the CU entity or the User Plane Function (UPF) of the core network.
  • UPF User Plane Function
  • it is controlled to be connected to multiple CP entities to implement shared multiplexing of baseband resource pools in the UP entity.
  • UP can also be deployed at the edge of the network near the DU entity according to requirements.
  • the above various flexible deployment modes can enable the baseband resources in the CP and the UP entity to be utilized efficiently, and can also greatly reduce RRC (Radio Resource Control) control plane signaling and user service data and DU.
  • RRC Radio Resource Control
  • the interaction delay between entities fully satisfies the QoS requirements of low-latency services.
  • the separation of CP and UP can construct a more flexible and efficient network deployment mode, which can further reduce the deployment cost while enhancing network performance and meeting various service requirements.
  • the CP entity includes the RRC and PDCP-C layers (PDCP (Packet Data Convergence Protocol) processing for control plane signaling), and the UP entity includes SDAP (Service Data Adaptation Protocol). , Service Data Adaptation Protocol), PDCP-U layer (for PDCP processing of user plane data).
  • PDCP Packet Data Convergence Protocol
  • SDAP Service Data Adaptation Protocol
  • PDCP-U layer for PDCP processing of user plane data.
  • a many-to-many mapping connection mode can be adopted between the CP entity and the UP entity.
  • the CP can manage multiple UPs at the same time, and the resources provided by the UP can also be shared by multiple CPs.
  • the embodiment of the present disclosure is applicable to a 5G NR or other all-bit wireless system, and relates to synchronization of state information between the CP and the UP in a scenario where the network radio access side CP and the UP network element entity are physically separated.
  • the logical interface between the CP and the UP network element is uniformly referred to as an E1 interface.
  • E1 interface the logical interface between the CP and the UP network element
  • it may be configured with one or more DRBs (Data Radio Bearers).
  • DRBs Data Radio Bearers
  • a user service data stream used to transmit various QoS requirements, including downlink and uplink data streams.
  • the embodiment of the present disclosure provides a method for synchronizing state information between a physically separated CP entity and a UP entity in a radio access network, so that the CP entity can obtain certain key state information in the UP entity in time, and thus can be triggered.
  • Various control operations on the CP entity side are possible.
  • the synchronization method of the embodiment of the present disclosure includes:
  • Step 101 The CP entity determines a to-be-stated content, an object, and a reporting policy for performing a synchronization operation, where the synchronization operation includes at least one of the following: a working state synchronization operation, and a resource state synchronization operation;
  • the object that performs the synchronization operation may include at least one of the following:
  • PDUs Protocol Data Units
  • Per DRB For each user service data flow in a specific UP entity processing unit, Per DRB (each DRB) may be used as a granularity object for tracking information collection and calculation reporting of state information; or a Per PDU Session (a PDU session, The PDU session may be mapped to multiple DRBs as a granular object, and the tracking information collection and analysis of the state information may be performed.
  • the single UE or multiple UE group sets may be used, and the UP entity processing unit is a granular object. Perform tracking and calculation of status information and report it.
  • the granularity object of the UE and the following relates to "UE Associated Signaling", and the granularity object above the UE refers to "Non UE Associated Signaling" or "Global Process (Global Procedures)".
  • the network side CP entity selects an object to be synchronized according to the needs of the control plane, for example, a plurality of DRBs, a plurality of PDU Sessions, a single UE, a plurality of UE group sets, and a processing unit of the specified UP entity.
  • the configuration information of the content to be counted includes at least one of: configuration parameter information for analyzing a working state of a user service data flow, configuration parameter work of the analysis statistical UP entity, and configuration parameter information of a resource state. .
  • the configuration parameter information for analyzing the working status of the user service data stream includes at least one of the following: the uplink and downlink transmission rate information of the service data stream, the uplink and downlink service quality information of the service data stream, and the grouping of the downlink service data stream.
  • Data aggregation protocol PDCP SN Serial Number
  • uplink service data flow security operation information uplink service data flow security operation information
  • PDCP data packet recovery information of the uplink service data stream.
  • the uplink and downlink transmission rate information of the service data flow may include: an uplink and downlink average transmission rate of the service data flow, and an maintenance situation of an aggregated maximum bit rate (AMBR).
  • AMBR aggregated maximum bit rate
  • the uplink and downlink QoS information of the service data flow may include: whether the uplink and downlink QoS of the service data flow is normally maintained, the QoS statistics time window parameter, and the QoS specific analysis object parameter.
  • the PDCP SN information of the downlink service data flow may include: whether the PDCP SN of the downlink service data flow has a maximum value flip, a current Count Value, and the like.
  • the uplink service data flow security operation information may include: whether the decryption failure of the uplink service data flow is detected, and the integrity protection check fails.
  • the PDCP packet recovery information of the uplink service data stream may include: whether a PDCP packet Recovery failure of the uplink service data stream is detected.
  • the configuration parameter information of the processing unit operation and the resource status of the statistical UP entity includes at least one of: a baseband resource duty ratio of the processing unit, a baseband resource busy/busy ratio, a fault information, and a
  • the number of data radio bearers of the service carries the number of DRBs and the number of protocol data unit PDU sessions.
  • control plane CP entity determines, in the step of performing the synchronization operation, the object to be counted, and the reporting policy, and determining the action type of the synchronization operation;
  • the action type of the synchronization operation includes one of the following: establishing Start, modify reconfiguration, and delete stop, respectively, corresponding to the initial configuration parameters to start the synchronization operation, modify the configuration parameters to continue the synchronization operation, delete the configuration parameters to stop the synchronization operation.
  • Step 102 The CP entity sends a request for a synchronization operation to the user plane UP entity, where the request carries configuration information of the to-be-stated content, the object, and the reporting policy of the synchronization operation.
  • the corresponding UP entity can be requested and configured through the E1 interface process, and the selected target object is tracked and analyzed and analyzed and reported (referred to as synchronous operation).
  • the request in the step of the CP entity sending a request for a synchronization operation to the user plane UP entity, the request further carries the configuration information of the action type.
  • the request of the synchronization operation is sent to the UP entity by the CP entity, and the state of the various information content to be synchronized in the UP entity may be tracked in real time.
  • the reporting policy includes one of the following: a specified event triggering report, a time period triggering report, and a periodic report event triggering.
  • the network-side CP entity can be configured with a specific reporting policy (for example, the event is triggered by the event, the time period is triggered, and the periodic event is triggered by the specified event), and the UP entity is configured to perform the corresponding synchronization operation.
  • a specific reporting policy for example, the event is triggered by the event, the time period is triggered, and the periodic event is triggered by the specified event
  • the UP entity is configured to perform the corresponding synchronization operation.
  • the CP entity may configure the UP entity to perform the synchronization operation in the manner of event definition triggering, time period triggering, event, and time period triggering, and may perform real-time synchronization operation according to different real-time requirements of the information content to be synchronized. A balance is struck between performance and efficiency overhead costs.
  • the CP entity may request to obtain the following information through the request of the synchronization operation:
  • Target DRB target PDU session or other granular traffic data uplink and downlink average transmission rate; optionally including: rate statistics time window parameter, rate event triggering reported threshold parameter, UP no data transmission silence Inactivity status indication, and the like.
  • the method includes: a QoS statistics time window parameter, and a QoS specific analysis object parameter, such as: an actual average rate of the GBR, an average delay of the data packet transmission, and an average packet loss rate of the data packet.
  • Whether the PDCP SN of the target DRB downlink service data flow has a maximum value rollover, and the current downlink Count Value may optionally include: the PDCP SN of the target DRB downlink service data flow has been flipped several times.
  • the UP entity detects at least one of a decryption failure and an integrity protection check failure of the uplink service data flow of the target DRB.
  • the baseband resource duty cycle or busy-to-air ratio in the target UP entity processing unit the total number of DRBs and PDU sessions being served, and the like.
  • the method may further include:
  • Step 103 The CP entity receives a response of a synchronization operation sent by the UP entity, where the response carries feedback information that is accepted or rejected by the request, and when the request is accepted, the request is also carried.
  • the feedback information carried in the configuration information is accepted or partially accepted.
  • the relevant state tracking statistics and analysis reporting operations are performed; if rejected, the synchronization operations are not performed for those objects.
  • the acceptance here refers to the acceptance of establishing a startup or modification reconfiguration, and if the deletion is stopped, the related state tracking statistics and analysis reporting operations are not performed.
  • the method further includes:
  • Step 104 The CP entity receives a statistical result of the synchronization operation reported by the UP entity.
  • the request, the response, and the statistics result of the synchronization operation are carried by the signaling of the E1 interface between the CP entity and the UP entity.
  • the method further includes:
  • Step 105 The CP entity performs a corresponding control plane response operation according to the received statistical result.
  • the CP response operation may include: performing reconfiguration adjustment on at least one of a working state and a resource state of the core network element, the base station network element, the user equipment UE, or the UP entity.
  • the CP entity takes the corresponding control plane response operation, such as triggering the process related to the core network, triggering the process related to the UP entity, triggering the process related to the UE, and the like.
  • the corresponding control plane response operation may be performed according to the statistical result of the synchronization operation reported by the UP entity, so that the UP entity can work more efficiently and efficiently, for example, the UP resource is more rationally utilized, and the DRB is used.
  • the data transmission returns to normal in time, and the faults in the UP entity are cleared in time.
  • the synchronization method of the embodiment of the present disclosure includes:
  • Step 201 The UP entity receives a request for a synchronization operation sent by the CP entity, where the request carries configuration information of the content to be statistic, the object, and the report policy of the synchronization operation, where the synchronization operation includes at least one of the following: State synchronization operation, resource state synchronization operation;
  • the request further carries configuration information of an action type of the synchronization operation
  • the action type of the synchronization operation includes one of: establishing startup, modifying reconfiguration, and deleting stop.
  • the configuration information of the content to be counted includes at least one of: configuration parameter information for analyzing a working state of a user service data flow, configuration parameter work of the analysis statistical UP entity, and configuration parameter information of a resource state. ;
  • the configuration parameter information for analyzing the working status of the user service data flow includes at least one of the following: the uplink and downlink transmission rate information of the service data flow, the uplink and downlink service quality information of the service data flow, and the packet data convergence protocol PDCP serial number of the downlink service data flow.
  • the configuration parameter information of the processing unit operation and the resource status of the analysis statistics UP entity includes at least one of: a baseband resource duty ratio of the processing unit, a baseband resource busy-to-air ratio, fault information, a data radio bearer DRB being served. Number, number of protocol data unit PDU sessions.
  • the object for performing the synchronization operation includes at least one of the following:
  • the request for the synchronization operation is one of: a setup request, a modification request, and a delete request.
  • Step 202 The UP entity determines to accept or reject the configuration information in the request and the request, and sends a response to the synchronization operation to the CP entity, where the response carries feedback information that accepts or rejects the request. And, when accepting the request, carrying feedback information that is all accepted or partially accepted by the configuration information carried in the request.
  • the UP entity may respectively use Per DRB, Per PDU Session, Per UE, Per UE set, and the Per UP entity processing unit as a granular object, and accept or reject the request for the synchronous operation.
  • the method further includes:
  • Step 203 The UP entity performs corresponding tracking analysis and statistics on the object according to the configuration information of the to-be-stated content, the object, and the reporting policy, and performs the synchronization operation reported to the CP entity according to the reporting policy. statistical results.
  • the UP entity rejects the request, it does not perform synchronization operations on those objects.
  • the acceptance refers to the acceptance of establishing the startup and modifying the reconfiguration, and if the acceptance of the deletion is stopped, the related state tracking statistics and the analysis reporting operation are not performed.
  • the reporting policy includes one of the following: a specified event triggering report, a time period triggering report, and a periodic report event triggering.
  • the network-side UP entity performs the tracking and statistics of the related content according to the synchronization operation request and configuration of the CP entity, and then reports the related result according to the reporting policy and related reporting parameters configured by the CP entity, and synchronizes the process through the E1 interface process.
  • the result of the operation is sent to the CP entity.
  • the request of the synchronization operation is sent to the UP entity by the CP entity, and the state of the various information content to be synchronized in the UP entity may be tracked in real time.
  • the CP entity performs the corresponding control plane response operation according to the statistical result of the synchronization operation reported by the UP entity, so that the UP entity can work more efficiently and efficiently, for example, the UP resource is more rationally utilized, and the data transmission on the DRB is restored in time. Normal, the fault in the UP entity is cleared in time.
  • the synchronization method of the embodiment of the present disclosure includes:
  • the CP entity determines the to-be-stated content, the object, and the reporting policy for performing the synchronization operation.
  • the synchronization operation includes at least one of the following: a working state synchronization operation and a resource state synchronization operation;
  • Step 302 The CP entity sends a request for a synchronization operation to the user plane UP entity, where the request carries configuration information of the content, object, and reporting policy of the synchronization operation.
  • Step 303 The UP entity determines to accept or reject the configuration information in the request and the request, and sends a response to the synchronization operation to the CP entity, where the response carries feedback information that accepts or rejects the request. And, when accepting the request, carrying feedback information that is all accepted or partially accepted by the configuration information carried in the request.
  • the method further includes:
  • Step 304 The UP entity performs corresponding tracking analysis and statistics on the object according to the information about the content to be counted, the object, and the report policy, and the statistical result of the synchronization operation reported to the CP entity according to the reporting policy. .
  • the method further includes:
  • Step 305 The CP entity performs a corresponding CP response operation according to the received statistical result.
  • the request of the synchronization operation is sent to the UP entity by the CP entity, and the state of the various information content to be synchronized in the UP entity may be tracked in real time.
  • the CP entity performs the corresponding control plane response operation according to the statistical result of the synchronization operation reported by the UP entity, so that the UP entity can work more efficiently and efficiently, for example, the UP resource is more rationally utilized, and the data transmission on the DRB is restored in time. Normal, the fault in the UP entity is cleared in time.
  • the synchronization system of the embodiment of the present disclosure includes a CP entity 41 and a UP entity 42.
  • the CP entity 41 of the embodiment of the present disclosure includes a memory, a processor, and a computer program stored on the memory and operable on the processor, and the processor implements the following steps when executing the program:
  • the processor further implements when executing the program:
  • the action type of the synchronous operation includes one of the following: establishing start, modifying reconfiguration, and deleting stop;
  • the request also carries configuration information of the action type.
  • the processor further implements when the program is executed:
  • the processor after receiving the response indicating the accepted synchronization operation, the processor also implements the program when:
  • the method after receiving the statistical result of the synchronization operation reported by the UP entity, when the processor executes the program, the method further implements:
  • the UP entity 42 of the embodiment of the present disclosure includes: a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor implementing the program to implement the following steps:
  • the synchronization operation includes at least one of the following: a working state synchronization operation, a resource State synchronization operation;
  • Determining that the request and the configuration information in the request are accepted or rejected sending a response to the synchronization operation to the CP entity, the response carrying feedback information that accepts or rejects the request, and the request When accepted, it also carries feedback information that accepts or partially accepts the configuration information carried in the request.
  • the request further carries configuration information of an action type of the synchronization operation
  • the action type of the synchronization operation includes one of: establishing startup, modifying reconfiguration, and deleting stop.
  • the processor further implements when the program is executed:
  • the statistical result of the synchronization operation reported to the CP entity according to the reporting policy is performed according to the configuration information of the content to be counted, the object, and the reporting policy.
  • the request of the synchronization operation is sent to the UP entity by the CP entity, and the state of the various information content to be synchronized in the UP entity may be tracked in real time.
  • the CP entity performs the corresponding control plane response operation according to the statistical result of the synchronization operation reported by the UP entity, so that the UP entity can work more efficiently and efficiently, for example, the UP resource is more rationally utilized, and the data transmission on the DRB is restored in time. Normal, the fault in the UP entity is cleared in time.
  • the synchronization device of the embodiment of the present disclosure includes:
  • the first determining module 51 is configured to determine a to-be-stated content, an object, and a reporting policy for performing a synchronization operation, where the synchronization operation includes at least one of: a working state synchronization operation, and a resource state synchronization operation;
  • the first sending module 52 is configured to send a request for a synchronization operation to the user plane UP entity, where the request carries configuration information of the content to be statistic, the object, and the reporting policy of the synchronization operation.
  • the first determining module 51 is further configured to determine an action type of the synchronous operation; the action type of the synchronous operation includes one of: establishing a start, modifying a reconfiguration, and deleting the stop;
  • the request also carries configuration information of the action type.
  • the method further includes:
  • the first receiving module 53 is configured to receive a response of the synchronization operation sent by the UP entity, where the response carries feedback information that is accepted or rejected by the request, and when the request is accepted, the The feedback information of all the configuration information carried in the request is accepted or partially accepted.
  • the first receiving module 53 is further configured to receive a statistical result of the synchronization operation reported by the UP entity.
  • the method further includes:
  • the first execution module 54 is configured to perform a corresponding control plane response operation according to the received statistical result.
  • the state of various information content to be synchronized within the UP entity can be tracked in real time.
  • the CP entity performs the corresponding control plane response operation according to the statistical result of the synchronization operation reported by the UP entity, so that the UP entity can work more efficiently and efficiently, for example, the UP resource is more rationally utilized, and the data transmission on the DRB is restored in time. Normal, the fault in the UP entity is cleared in time.
  • the synchronization device of the embodiment of the present disclosure includes:
  • the second receiving module 61 is configured to receive a request for a synchronization operation sent by the CP entity, where the request carries configuration information of the to-be-stated content, the object, and the reporting policy of the synchronization operation, where the synchronization operation includes at least the following One: work state synchronization operation, resource state synchronization operation;
  • a second determining module 62 configured to determine accepting or rejecting configuration information in the request and the request;
  • the second sending module 63 is configured to send, according to the decision of the determining module, a response to the synchronization operation to the CP entity, where the response carries feedback information that accepts or rejects the request, and when the request is accepted, It also carries feedback information that is fully accepted or partially accepted by the configuration information carried in the request.
  • the method further includes:
  • the second execution module 64 is configured to: after determining that the request is accepted, the UP entity performs corresponding tracking analysis and statistics on the object according to the configuration information of the to-be-stated content, the object, and the reporting policy that are determined to be accepted;
  • the second sending module 63 is further configured to report the statistical result of the synchronization operation to the CP entity according to the reporting policy.
  • the request of the synchronization operation is sent to the UP entity by the CP entity, and the state of the various information content to be synchronized in the UP entity may be tracked in real time.
  • the CP entity performs the corresponding control plane response operation according to the statistical result of the synchronization operation reported by the UP entity, so that the UP entity can work more efficiently and efficiently, for example, the UP resource is more rationally utilized, and the data transmission on the DRB is restored in time. Normal, the fault in the UP entity is cleared in time.
  • the UE1 is configured with two DRBs of the GBR service attributes: DRB1 and DRB2, which are respectively used to carry the voice and video data services, and the network side CP entity and the UP entity support the content of the embodiment of the present disclosure, which can be granular to the DRB. Perform a synchronization operation.
  • FIG. 9 is a schematic flowchart of Application Example 1.
  • Step 901 The network-side CP entity requests the synchronization operation to the UP entity through the E1 interface flow message UP Status Synchronization Request, and the operation object is the DRB1 and the DRB2 in the UE1, and the content to be synchronized is: the service data flow is uplink and downlink.
  • the QoS of the QoS is normally performed and maintained.
  • Step 902 The UP entity receives and accepts the synchronization operation request and related parameter configuration of the DR entity for the DRB1 and the DRB2 in the UE1, and replies to the CP entity by the E1 interface flow message UP Status Synchronization Response. And configuration parameters have been accepted.”
  • Step 903 The UP entity will calculate the time window length of the QoS in 10s units, periodically perform statistics and records of the actual average rate of the GBR, and compare the rates of the GBR subscription requirements to obtain the “QoS-damaged identifier string” of the DRB1 and the DRB2, respectively.
  • Step 904 According to the reporting policy and parameters configured by the previous CP entity, when the QoS impairment record occurs three times in succession, the UP entity reports the "CP" to the CP entity through the E1 interface flow message UP Status Synchronization Report.
  • the QoS impairment of the DRB event may optionally report the QoS Damaged Identification String information.
  • Step 905 The CP entity learns that the QoS of the DRB1 is continuously damaged by the content reported by the UP entity, and the QoS experience of the user's voice service is degraded, so that the AMF related situation is notified through the NGAP flow message PDU Session Resource Notify.
  • Step 906 The AMF, according to the content reported by the CP entity, triggers a PDU Session Resource Modify process to modify the content of the PDU Session attribute associated with the DRB1, for example, releasing the video service data stream.
  • UE2 is configured with three DRBs of Non GBR service attributes: DRB1, DRB2, and DRB3 are used to carry different file block objects, which belong to the same PDU Session.
  • DRB1, DRB2, and DRB3 are used to carry different file block objects, which belong to the same PDU Session.
  • Both the network side CP entity and the UP entity support the content of the embodiment of the present disclosure, and the synchronization operation can be performed with the PDU Session as the granularity.
  • FIG. 10 is a schematic flow chart of Application Example 2.
  • Step 1001 The network side CP entity requests a synchronization operation to the UP entity through the E1 interface flow message UP Status Synchronization Request, and the operation object is the PDU Session1 in UE1 (mapped to DRB1, DRB2, and DRB3), and the content to be synchronized is: PDU Whether the AMBR of the session level is normally executed and maintained.
  • Step 1002 The UP entity receives and accepts the synchronization operation request and related parameter configuration of the PDU Session1 of the UE2 in the UE2, and replies to the CP entity by the E1 interface flow message UP Status Synchronization Response that the synchronization operation request and the configuration parameters have been accepted. .
  • Step 1003 The UP entity will calculate the time window length of the AMBR in units of 20s, periodically perform statistics and records of the actual average rate of the AMBR, and compare with the rate of the AMBR subscription request, thereby obtaining a "history identification string" of the PDU Session1AMBR, such as ⁇ . . Normal, normal, normal, overrun ⁇ .
  • Step 1004 According to the reporting policy and parameters configured by the previous CP entity, when the first AMBR over-limit identifier occurs, the UP entity reports the PDU Session1 AMBR Overrun event to the CP entity through the E1 interface flow message UP Status Synchronization Report.
  • Step 1005 The CP entity learns that the PDU Session1 AMBR is exceeded by the content reported by the UP entity, and the QoS of the file download service of the user exceeds the limitation of the subscription, so the AMF related information is notified through the NGAP process message PDU Session Resource Notify.
  • Step 1006 The AMF triggers the PDU Session Resource Modify process according to the content reported by the CP entity, and modifies the content of the PDU Session1 attribute, for example, releasing some QoS Flow data streams in the PDU Session1.
  • UE3 is configured with two DRs of Non-GBR service attributes: DRB1, which are used to carry services for transmitting web browsing and online audio data, and they belong to the same PDU Session.
  • DRB1 Non-GBR service attributes
  • Both the network side CP entity and the UP entity support the content of the embodiment of the present disclosure, and the synchronization operation can be performed with the DRB as the granularity.
  • 11 is a schematic flow chart of Application Example 3.
  • Step 1101 The network-side CP entity requests the synchronization operation to the UP entity through the E1 interface flow message UP Status Synchronization Request, and the operation object is DRB1 and DRB2 in UE1, and the content to be synchronized is: when a DRB has a downlink PDCP SN maximum value When flipping, the UP entity reports the relevant result in an event manner.
  • Step 1102 The UP entity receives and accepts the synchronization operation request and related parameter configuration of the DR entity for the DRB1 and the DRB2 in the UE3, and replies to the CP entity through the E1 interface flow message UP Status Synchronization Response that the synchronization operation request and the configuration parameters have been accept".
  • Step 1103 As the downlink data blocks carried in the DRB1 and the DRB2 are continuously transmitted, the SN sequence number of each downlink PDCP entity is +1; at a certain moment, the downlink PDCP SN corresponding to the DRB2 reaches a maximum value, and the SN is about to be flipped. Reset back to 0, the UP entity suspends downlink data transmission on DRB2.
  • Step 1104 According to the reporting policy and parameters configured by the previous CP entity, when the maximum PDCP SN of a DRB is about to be reversed, the UP entity reports the DRD2 downlink PDCP SN to the CP entity through the E1 interface flow message UP Status Synchronization Report. The value is about to flip" event.
  • Step 1105 The CP entity learns that the maximum value of the downlink PDCP SN of the DRB2 is about to be reversed through the content reported by the UP entity, and the security subkey (including encryption and integrity protection) of the bearer needs to be updated (Key Refresh process). Then, a new security subkey is generated and configured for UE3 in the UP entity through the E1AP flow message Security Mode Update. The CP entity also needs to configure a new security subkey for the UE3 through the air interface message flow RRC Connection Reconfiguration, which is consistent with the configuration related to maintaining the security operation on the UP entity side.
  • Step 1106 The UP entity configures and applies a new security subkey to the DRB2 in the UE3 according to the new security parameter configuration sent by the CP entity, and returns a confirmation notification CP through the E1AP flow message Security Mode Update Acknowledge. entity. Afterwards, the UP entity restores the downlink data security transmission in the DRB2 based on the new security subkey, encrypts the downlink data packet with the new encryption key, and performs a integrity protection operation on the downlink data packet by the new integrity protection key.
  • the UE4 is configured with two DRBs of the GBR service attributes: DRB1, which are used to carry the services of the uplink file block and the local cloud disk backup respectively. They belong to different PDU sessions. Both the network side CP entity and the UP entity support the content of the embodiment of the present disclosure, and the synchronization operation can be performed with the DRB as the granularity.
  • FIG. 12 is a schematic flow chart of Application Example 4.
  • Step 1201 The network side CP entity requests a synchronization operation to the UP entity through the E1 interface flow message UP Status Synchronization Request, and the operation object is DRB1 and DRB2 in UE1, and the content to be synchronized is: when a DRB fails to perform an uplink security operation (decryption) When at least one of the failure and integrity protection check failures occurs, the UP entity reports the relevant result in an event manner.
  • Step 1202 The UP entity receives and accepts the synchronization operation request and related parameter configuration of the DR entity for the DRB1 and the DRB2 in the UE4, and replies to the CP entity through the E1 interface flow message UP Status Synchronization Response that the synchronization operation request and the configuration parameters have been accept".
  • Step 1203 During continuous transmission of uplink data blocks carried in DRB1 and DRB2,
  • the hacker maliciously attacks the uplink wireless link between the UE4 and the UP entity, and the uplink forcibly inserts consecutive "fake packets". After the UP entity receives these "fake packets",
  • Step 1204 According to the reporting policy and parameters configured by the previous CP entity, when the uplink security operation fails in a certain DRB, the UP entity reports to the CP entity through the E1 interface process message UP Status Synchronization Report that "the DRB2 integrity protection school is detected. The error of the test.
  • Step 1205 The CP entity learns that the DRB2 detects the integrity protection check error on the DRB2 through the content reported by the UP entity, and then generates and configures a new security subkey for the UE4 in the UP entity through the E1AP flow message Security Mode Update Request. And ask to try to recover the lost upstream true packets before.
  • the CP entity also needs to configure a new security subkey for the UE4 through the air interface message process RRC Connection Reconfiguration, which is consistent with the configuration related to maintaining the security operation on the UP entity side.
  • Step 1206 The UP entity configures and applies a new security subkey to the DRB2 in the UE4 according to the new security parameter configuration sent by the CP entity, and returns a notification to the CP entity through the E1AP flow message Security Mode Update Response, agreeing to try to recover before losing. Upstream packet. Afterwards, the UP entity recovers the uplink data transmission in DRB2 based on the new security subkey, and attempts to recover the previously lost uplink true data packet.
  • a UP entity processing unit is carrying a transmission service of different types of service data of a plurality of UEs. Both the network side CP entity and the UP entity support the content of the embodiment of the present disclosure, and the UP entity processing unit may perform the synchronization operation for the granularity.
  • FIG. 13 is a schematic flow chart of Application Example 5.
  • Step 1301 The network side CP entity requests a synchronization operation to the UP entity through the E1 interface flow message UP Status Synchronization Request, and the operation object is a specific UP entity processing unit, and the content to be synchronized is: statistically calculating its processing resource duty ratio (ie, : The ratio between the average occupied resource and the total resource.
  • the UP entity reports the related statistics in a periodic manner.
  • Step 1302 The UP entity receives and accepts the synchronization operation request and related parameter configuration of the CP entity for the specific UP entity processing unit, and replies to the CP entity through the E1 interface flow message UP Status Synchronization Response that the synchronization operation request and the configuration parameters have been accept".
  • Step 1303 In the service process of data transmission of different service types carrying a plurality of UEs, the UP entity period continuously calculates and calculates the duty ratio of the processing resources in the processing unit of the specific UP entity, and calculates the period of reporting by using 60s as a statistical calculation, thereby Obtain a history table on the timeline, such as ⁇ 60%, 70%, 80%, 75%, 78%, 82%... ⁇ , 60% means: in the UP entity processing unit in the last statistical observation window Processing resources consume an average of 60% of the total.
  • Step 1304 According to the reporting policy and parameters configured by the previous CP entity, the UP entity reports the statistical calculation result to the CP entity through the E1 interface process message UP Status Synchronization Report, and the CP entity can learn the UP entity side. Handle the real-time situation of resource overhead.
  • Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions for performing a synchronization method as shown in FIG.
  • Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions for performing a synchronization method as shown in FIG.
  • Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions for performing a synchronization method as shown in FIG. 5.
  • the foregoing storage medium may include, but not limited to, a U disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • mobile hard disk a magnetic disk
  • magnetic disk a magnetic disk
  • optical disk a variety of media that can store program code.
  • the computer readable storage medium described above is a non-transitory storage medium.
  • the embodiment further provides a network element, including:
  • the transceiver can be a communication interface of the network element, for example, an interface between the CP and the UP
  • a memory which may include various storage media
  • the processor is respectively connected to the transceiver and the memory, configured to control the information transceiving of the transceiver and the information storage of the memory by executing the executable instructions of the computer, and implement a synchronization method performed by the CP or the UP, For example, one or more of the synchronization methods shown in FIGS. 3 to 5 and 9 to 13.
  • the processor can be any type of processor, which can be a central processing unit, a microprocessor, a digital signal processor, a programmable array, or an application specific integrated circuit.
  • the processor can be respectively connected to the transceiver and the memory through a bus interface such as an integrated circuit bus.
  • modules or steps of the embodiments of the present disclosure may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed either separately as an integrated circuit module, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • embodiments of the present disclosure are not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例公开了一种同步方法和装置，所述方法包括：控制面CP实体确定进行同步操作的待统计内容、对象和上报策略；其中，所述同步操作包括如下至少之一：工作状态同步操作、资源状态同步操作；所述CP实体向用户面UP实体发送同步操作的请求，所述请求中携带所述同步操作的待统计内容、对象和上报策略的配置信息。在本公开实施例中，还公开了一种网元和计算机可读存储介质。

Description

一种同步方法和装置、网元及存储介质
相关申请的交叉引用
本公开基于申请号为201710901674.2、申请日为2017年09月28日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本公开作为参考。
技术领域
本公开实施例涉及通信技术领域但是不限于通信技术领域，尤指一种同步方法和装置、网元及存储介质。
背景技术
随着进入到5G(Fifth Generation，第五代移动通信)移动通信时代，海量连接以及用户更高的数据传输速率要求，对LTE(Long Term Evolution，长期演进)系统中BBU(Baseband Unit，基带单元)与RRU(Remote Radio Unit，远端射频单元)之间的前传接口CPRI(Common Public Radio Interface，通用公共无线电接口)的传输容量提出了极大的挑战。由于CPRI接口传输的是经过物理层编码调制等处理后的IQ(In-phase Quadrature，同相正交)信号，对应的数字比特串速率巨大，因此CPRI接口对传输时延和工作带宽都有较大的要求，否则BBU和RRU之间不能工作。如果当5G基站(gNB)的空口速率提升到数十Gbps后，CPRI接口的传输流量需求，将至少上升到Tbps级别，这对前传网络接口(Fronthaul)的部署成本和难度都带来了巨大的压力。因此，在5G NR(New Radio，新无线系统)中，需要重新定义基站gNB内前传网络接口的划分方式。
在前传接口的划分方式中，需要从传输容量、传输时延、方便部署等几方面综合考虑，比如：考虑到非理想前传传输，将时延不敏感的网络功能放在第一网元(比如：CU(Centralized Unit，集中处理单元)中)，将 时延敏感的网络功能放在第二网元(比如：DU(Distributed Unit，分布式处理单元)中)。
一个集中式部署gNB可以包含一个gNB-CU和所辖的多个gNB-DU，它们之间通过前传链路逻辑接口F1连接，例如，F1-C接口或F1-U接口。一个gNB-DU只能连接到一个gNB-CU并被其管理控制，gNB-DU和相邻gNB-DU之间没有直接接口。从外部看，NG接口和Xn接口都终结在gNB-CU单元上，gNB-DU对外不可见。为了保证可靠性，从实际部署的角度考虑，一个gNB-DU也可能会连接到多个gNB-CU。
发明内容
本公开实施例提供了一种同步方法和装置、同步网元及存储介质。
本公开实施例提供了一种同步方法，包括：
控制面(Control Plane，CP)实体确定进行同步操作的待统计内容、对象和上报策略；其中，所述同步操作包括如下至少之一：工作状态同步操作、资源状态同步操作；
所述CP实体向用户面(User Plane，UP)实体发送同步操作的请求，所述请求中携带所述同步操作的待统计内容、对象和上报策略的配置信息。
本公开实施例还提供了一种同步方法，包括：
用户面UP实体接收CP实体发送的同步操作的请求，所述请求中携带所述同步操作的待统计内容、对象和上报策略的配置信息；其中，所述同步操作包括如下至少之一：工作状态同步操作、资源状态同步操作；
所述UP实体确定对所述请求和所述请求中的配置信息接受或拒绝，向所述CP实体发送同步操作的响应，所述响应中携带对所述请求接受或拒绝的反馈信息，以及，对所述请求接受时，还携带对所述请求中携带的配置信息全部接受或部分接受的反馈信息。
本公开实施例还提供了一种同步装置，包括：
第一确定模块，配置为确定进行同步操作的待统计内容、对象和上报策略；其中，所述同步操作包括如下至少之一：工作状态同步操作、资源 状态同步操作；
第一发送模块，配置为向用户面UP实体发送同步操作的请求，所述请求中携带所述同步操作的待统计内容、对象和上报策略的配置信息。
本公开实施例还提供了一种同步装置，包括：
第二接收模块，配置为接收CP实体发送的同步操作的请求，所述请求中携带所述同步操作的待统计内容、对象和上报策略的配置信息；其中，所述同步操作包括如下至少之一：工作状态同步操作、资源状态同步操作；
第二确定模块，配置为确定对所述请求和所述请求中的配置信息接受或拒绝；
第二发送模块，配置为根据确定模块的决策，向所述CP实体发送同步操作的响应，所述响应中携带对所述请求接受或拒绝的反馈信息，以及，对所述请求接受时，还携带对所述请求中携带的配置信息全部接受或部分接受的反馈信息。
本公开实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述同步方法。
本公开实施例还提供了一种网元，其中，包括：收发器；存储器；处理器，分别与所述收发器及存储器连接，配置为通过计算机可执行指令的执行，控制所述收发器的信息收发及所述存储器的信息存储，并上述同步方法。
本公开实施例包括：控制面CP实体确定进行同步操作的待统计内容、对象和上报策略；其中，所述同步操作包括如下至少之一：工作状态同步操作、资源状态同步操作；所述CP实体向用户面UP实体发送同步操作的请求，所述请求中携带所述同步操作的待统计内容、对象和上报策略的配置信息。在本公开实施例中，通过CP实体向UP实体发送同步操作的请求，可以及时(例如，实时)地跟踪UP实体内的各种待同步信息内容的状态。
在一实施方式中，可以根据UP实体上报的同步操作的统计结果，执行相应的控制面响应操作，从而可以使得UP实体能够更有效和高效地工作， 比如：UP资源得到更合理利用，DRB(Data Radio Bearer，数据无线承载)上的数据传输及时恢复正常，UP实体内故障得到及时清除等。
在一实施方式中，CP实体可以以不同粒度等级，去配置同步操作的不同对象，不同的待统计内容可以关联到不同的粒度操作对象。
在一实施方式中，CP实体可以以事件定义触发、时间周期触发、事件和时间周期触发的方式，配置UP实体进行同步操作，可以根据不同的待同步信息内容的实时性要求，在同步操作的实时性和效果效率开销成本之间取得平衡。
附图说明
附图用来提供对本公开实施例技术方案的进一步理解，并且构成说明书的一部分，与本公开的实施例一起用于解释本公开实施例的技术方案，并不构成对本公开实施例技术方案的限制。
图1为5G NR CU-DU分离式部署(gNB集中式部署)架构示意图；
图2为CP和UP物理分离的架构示意图；
图3为本公开实施例的同步方法流程图(CP实体)；
图4为本公开实施例的同步方法流程图(UP实体)；
图5为本公开实施例的同步方法流程图(CP实体和UP实体)；
图6为本公开实施例的同步系统组成示意图；
图7为本公开实施例的同步装置组成示意图；
图8为本公开实施例的同步装置组成示意图；
图9为本公开实施例应用示例1的流程示意图；
图10为本公开实施例应用示例2的流程示意图；
图11为本公开实施例应用示例3的流程示意图；
图12为本公开实施例应用示例4的流程示意图；
图13为本公开实施例应用示例5的流程示意图。
具体实施方式
下文中将结合附图对本公开的实施例进行详细说明。需要说明的是，在不冲突的情况下，本公开中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
如图1所示，为5G NR CU-DU分离式部署(gNB集中式部署)架构示意图。不同QoS(Quality of Service，服务质量)业务要求的5G用户业务和不均衡的用户业务物理分布，对5G网络的组网部署和数据传输性能的需求都不同，这些不同类型的数据业务往往是交织并存的，或者在局部区域热点爆发，因此使得当前相对封闭的网络架构，不能更高效地支撑各类5G通讯场景。因此，在CU和DU划分的基础上，同时结合传输时延、负载均衡、多厂商设备互操作性以及部署成本等多个角度的综合考虑，对CU实体内的控制面实体(Control plane，简称CP)和用户面实体(User plane，简称UP)进行物理分割(注：CP和UP功能集，过去已经被逻辑层面分割，但是物理上还是集成在单个基站网元内)，使得CP和UP可以部署在不同的地理位置，独立地被配置，资源扩展和功能升级，因此可以更灵活高效地组网部署且去满足5G的各类业务需求。CP和UP物理分离的架构如图2所示。
参考图2，从部署位置看，CP实体既可以部署在网络中心机房如：CU实体内，同时管理辖区内多个UP实体，高效协调多个UP实体之间的业务负载资源，达到负载均衡的目的；CP也可以根据需求，部署在网络边缘靠近DU实体的位置；同理，UP实体既可以部署在网络数据库中心如：CU实体或者核心网UPF(User Plane Function，用户面功能)实体内，同时被控连接于多个CP实体，实现UP实体内基带资源池的共享复用；UP也可以根据需求，部署在网络边缘靠近DU实体的位置。上述各种灵活的部署方式，既可以使得CP和UP实体内的基带资源能够被高效地利用，也可以大大减小RRC(Radio Resource Control，无线资源控制)控制面信令和用 户业务数据和DU实体之间的交互时延，充分满足低延时业务的QoS需求。
从运营商角度看，CP和UP分离可以构造更加灵活和高效的网络部署方式，在增强网络性能，满足各类业务需求的同时，可以进一步降低部署成本。
从空口用户面划分的角度看，CP实体包含RRC和PDCP-C层(用于控制面信令的PDCP(Packet Data Convergence Protocol，分组数据汇聚协议)处理)，UP实体包含SDAP(Service Data Adaptation Protocol，业务数据适配协议)，PDCP-U层(用于用户面数据的PDCP处理)。CP实体和UP实体之间可采用多对多的映射连接方式，CP可以同时管理多个UP，而UP提供的资源也可以由多个CP共享。
本公开实施例适用于5G NR或者其他等位无线系统中，涉及网络无线接入侧CP和UP网元实体之间物理分离的场景下，CP和UP之间状态信息的同步。公开中，统一把CP和UP网元实体之间的逻辑接口称为E1接口，对于某个特定被服务的UE对象，它可以被配置一条或者多条DRB(Data Radio Bearer，数据无线承载)，用来传输各种不同QoS要求的用户业务数据流，包含下行和上行的数据流。
本公开实施例提出一种无线接入网内部物理分离的CP实体和UP实体之间，进行状态信息同步的方法，从而使得CP实体能及时获得UP实体内的某些关键状态信息，进而可以触发CP实体侧的各种管控操作。
如图3所示，本公开实施例的同步方法，包括：
步骤101，CP实体确定进行同步操作的待统计内容、对象和上报策略；其中，所述同步操作包括如下至少之一：工作状态同步操作、资源状态同步操作；
在一实施方式中，所述进行同步操作的对象可以包括如下至少之一：
一条或多条DRB、一个或多个PDU(Protocol Data Unit，协议数据单元)Session(会话)、一个UE、多个UE的群集合、指定的UP实体的处理单元。
针对特定UP实体处理单元内的各条用户业务数据流，可以以Per DRB (每条DRB)为粒度对象，进行状态信息的跟踪收集计算和分析上报；也可以以Per PDU Session(一个PDU会话，其中，一个PDU Session可被映射到多条DRB上)为粒度对象，进行状态信息的跟踪收集计算和分析上报；还可以以单个UE，或者多个UE群集合，UP实体处理单元为粒度对象，进行状态信息的跟踪收集计算和分析上报。通常，UE及其以下的粒度对象涉及到“UE专有流程(UE Associated Signaling)”，而UE以上的粒度对象涉及到“非UE专有流程(Non UE Associated Signaling)”或者“全局流程(Global Procedures)”。
网络侧CP实体根据控制面的需要，选择要进行同步操作的对象，比如：若干条DRB，若干个PDU Session，单个UE，若干个UE群集合，指定的UP实体的处理单元。
在一实施方式中，所述待统计内容的配置信息包括如下至少之一：分析统计用户业务数据流工作状态的配置参数信息、所述分析统计UP实体的处理单元工作和资源状态的配置参数信息。
在一实施方式中，所述分析统计用户业务数据流工作状态的配置参数信息包括如下至少之一：业务数据流上下行传输速率信息、业务数据流上下行服务质量信息、下行业务数据流的分组数据汇聚协议PDCP SN(Serial Number，序列号)信息、上行业务数据流安全操作信息、上行业务数据流的PDCP数据包恢复信息。
其中，业务数据流上下行传输速率信息可以包括：业务数据流上下行平均传输速率、AMBR(Aggregated Maximum Bit Rate，聚合的最大数据传输速率)的维护情况等。
业务数据流上下行QoS信息可以包括：业务数据流上下行QoS是否被正常维护、QoS统计时间窗参数，QoS具体的分析对象参数等。
下行业务数据流的PDCP SN信息可以包括：下行业务数据流的PDCP SN是否发生最大值翻转、当前的Count Value(计数值)等。
上行业务数据流安全操作信息可以包括：是否检测到上行业务数据流的解密失败、完整性保护校验失败。
上行业务数据流的PDCP数据包恢复信息可以包括：是否检测到上行业务数据流的PDCP数据包Recovery(恢复)失败。
在一实施方式中，所述分析统计UP实体的处理单元工作和资源状态的配置参数信息包括如下至少之一：所述处理单元的基带资源占空比、基带资源忙闲比、故障信息、正在服务的数据无线承载DRB个数、协议数据单元PDU会话个数。
在一实施方式中，所述控制面CP实体确定进行同步操作的待统计内容、对象和上报策略的步骤中，还确定同步操作的动作类型；所述同步操作的动作类型包括如下之一：建立启动、修改重配和删除停止，分别对应着初始配置参数开启同步操作，修改配置参数继续同步操作，删除配置参数停止同步操作。
步骤102，所述CP实体向用户面UP实体发送同步操作的请求，所述请求中携带所述同步操作的待统计内容、对象和上报策略的配置信息。
本步骤中，可以通过E1接口流程，请求和配置对应的UP实体，对选择出的目标对象，进行状态信息的跟踪统计和分析上报的操作(简称为同步操作)。
在一实施方式中，所述CP实体向用户面UP实体发送同步操作的请求的步骤中，所述请求中还携带所述动作类型的配置信息。
在本公开实施例实施例中，通过CP实体向UP实体发送同步操作的请求，可以实时地跟踪UP实体内的各种待同步信息内容的状态。
在一实施方式中，所述上报策略包括如下之一：指定事件触发上报、时间周期触发上报，指定事件触发的周期性上报。
其中，网络侧CP实体可配置特定的上报策略(比如：指定事件触发上报、时间周期触发上报，指定事件触发的周期性上报)，配置UP实体进行相应的同步操作相关结果上报。有的操作对象“事件”和“时间”两种方式都适用，有的操作对象只适用其中一种方式。
本实施例中，CP实体可以以事件定义触发、时间周期触发、事件和时间周期触发的方式，配置UP实体进行同步操作，可以根据不同的待同步信 息内容的实时性要求，在同步操作的实时性和效果效率开销成本之间取得平衡。
例如：CP实体可以通过所述同步操作的请求，请求获取如下信息：
目标DRB，目标PDU Session或者其他粒度的业务数据流上下行平均传输速率；可选地包含：速率统计时间窗参数，速率事件触发上报的门限参数，UP无数据传输静默Inactivity状态指示等。
目标DRB，目标PDU Session或者其他粒度的业务数据流上下行服务质量QoS是否被正常地执行维护，即用户签约的业务服务质量QoS要求没有受损或者超限。可选地包含：QoS统计时间窗参数，QoS具体的分析对象参数，如：GBR实际平均速率，数据包传输平均时延，数据包平均丢包率等。
目标DRB下行业务数据流的PDCP SN是否发生最大值翻转，当前下行的Count Value，可选地包含：目标DRB下行业务数据流的PDCP SN已发生了几次翻转。
UP实体是否检测到目标DRB的上行业务数据流的解密失败和完整性保护校验失败中至少之一。
UP实体是否检测到目标DRB的上行业务数据流的PDCP Recovery数据包恢复失败。
目标UP实体处理单元内的基带资源占空比或忙闲比，正在服务的DRB和PDU Session总个数等。
在一实施方式中，所述步骤102之后，还可以包括：
步骤103，所述CP实体接收所述UP实体发送的同步操作的响应，所述响应中携带对所述请求接受或拒绝的反馈信息，以及，对所述请求接受时，还携带对所述请求中携带的配置信息全部接受或部分接受的反馈信息。
其中，UP实体如果接受，随后就进行相关的状态跟踪统计和分析上报操作；如果拒绝，就不针对那些对象执行同步操作。
需要说明的是，此处接受指的是对建立启动或修改重配的接受，若是对删除停止接受则并不会执行相关的状态跟踪统计和分析上报操作。
在一实施方式中，所述CP实体接收到表示接受的同步操作的响应之后，所述方法还包括：
步骤104，所述CP实体接收所述UP实体上报的同步操作的统计结果。
其中，所述同步操作的请求、响应和统计结果通过CP实体和UP实体之间的E1接口的信令承载。
在一实施方式中，所述方法还包括：
步骤105，所述CP实体根据接收到的所述统计结果，执行相应的控制面响应操作。
其中，所述CP响应操作可包括：对核心网网元、基站网元、用户设备UE或UP实体的工作状态和资源状态中的至少之一进行重配置调整。
本步骤中，CP实体接收到UP实体的结果上报后，采取相应的控制面响应操作，如：触发和核心网相关的流程，触发和UP实体相关的流程，触发和UE相关的流程等。
本实施例中，可以根据UP实体上报的同步操作的统计结果，执行相应的控制面响应操作，从而可以使得UP实体能够更有效和高效地工作，比如：UP资源得到更合理利用，DRB上的数据传输及时恢复正常，UP实体内故障得到及时清除等。
如图4所示，本公开实施例的同步方法，包括：
步骤201，UP实体接收CP实体发送的同步操作的请求，所述请求中携带所述同步操作的待统计内容、对象和上报策略的配置信息；其中，所述同步操作包括如下至少之一：工作状态同步操作、资源状态同步操作；
在一实施方式中，所述请求中还携带所述同步操作的动作类型的配置信息，所述同步操作的动作类型包括如下之一：建立启动、修改重配和删除停止。
在一实施方式中，所述待统计内容的配置信息包括如下至少之一：分析统计用户业务数据流工作状态的配置参数信息、所述分析统计UP实体的处理单元工作和资源状态的配置参数信息；
所述分析统计用户业务数据流工作状态的配置参数信息包括如下至少之一：业务数据流上下行传输速率信息、业务数据流上下行服务质量信息、下行业务数据流的分组数据汇聚协议PDCP序列号信息、上行业务数据流安全操作信息、上行业务数据流的PDCP数据包恢复信息；
所述分析统计UP实体的处理单元工作和资源状态的配置参数信息包括如下至少之一：所述处理单元的基带资源占空比、基带资源忙闲比、故障信息、正在服务的数据无线承载DRB个数、协议数据单元PDU会话个数。
在一实施方式中，所述进行同步操作的对象包括如下至少之一：
一条或多条DRB、一个或多个PDU会话、一个UE、多个UE的群集合、指定的UP实体的处理单元。
在一实施方式中，所述同步操作的请求为如下之一：建立请求、修改请求和删除请求。
步骤202，所述UP实体确定对所述请求和所述请求中的配置信息接受或拒绝，向所述CP实体发送同步操作的响应，所述响应中携带对所述请求接受或拒绝的反馈信息，以及，对所述请求接受时，还携带对所述请求中携带的配置信息全部接受或部分接受的反馈信息。
UP实体接收到请求后，可以分别以Per DRB，Per PDU Session，Per UE，Per UE集合，Per UP实体处理单元为粒度对象，对同步操作的请求，进行接受或者拒绝。
在一实施方式中，所述UP实体确定对所述请求接受之后，所述方法还包括：
步骤203，所述UP实体根据确定接受的待统计内容、对象和上报策略的配置信息，对所述对象进行相应的跟踪分析统计，按照所述上报策略，向所述CP实体上报的同步操作的统计结果。
UP实体如果拒绝请求，就不针对那些对象执行同步操作。
其中，此处接受指的是对建立启动、修改重配的接受，若是对删除停止的接受则并不会执行相关的状态跟踪统计和分析上报操作。
在一实施方式中，所述上报策略包括如下之一：指定事件触发上报、时间周期触发上报，指定事件触发的周期性上报。
本步骤中，网络侧UP实体根据CP实体的同步操作请求和配置，进行相关内容的跟踪统计，之后根据CP实体配置的上报策略和相关上报参数，进行相关结果的上报，通过E1接口流程把同步操作的结果发给CP实体。
在本公开实施例中，通过CP实体向UP实体发送同步操作的请求，可以实时地跟踪UP实体内的各种待同步信息内容的状态。CP实体根据UP实体上报的同步操作的统计结果，执行相应的控制面响应操作，从而可以使得UP实体能够更有效和高效地工作，比如：UP资源得到更合理利用，DRB上的数据传输及时恢复正常，UP实体内故障得到及时清除等。
如图5所示，本公开实施例的同步方法，包括：
步骤301，CP实体确定进行同步操作的待统计内容、对象和上报策略；其中，所述同步操作包括如下至少之一：工作状态同步操作、资源状态同步操作；
步骤302，所述CP实体向用户面UP实体发送同步操作的请求，所述请求中携带所述同步操作的待统计内容、对象和上报策略的配置信息；
步骤303，所述UP实体确定对所述请求和所述请求中的配置信息接受或拒绝，向所述CP实体发送同步操作的响应，所述响应中携带对所述请求接受或拒绝的反馈信息，以及，对所述请求接受时，还携带对所述请求中携带的配置信息全部接受或部分接受的反馈信息。
在一实施方式中，所述UP实体确定对所述请求接受之后，所述方法还包括：
步骤304，所述UP实体根据确定接受的待统计内容、对象和上报策略的配置信息，对所述对象进行相应的跟踪分析统计，按照上报策略，向所述CP实体上报的同步操作的统计结果。
在一实施方式中，所述UP实体向所述CP实体上报的同步操作的统计结果之后，所述方法还包括：
步骤305，所述CP实体根据接收到的所述统计结果，执行相应的CP响应操作。
在本公开实施例中，通过CP实体向UP实体发送同步操作的请求，可以实时地跟踪UP实体内的各种待同步信息内容的状态。CP实体根据UP实体上报的同步操作的统计结果，执行相应的控制面响应操作，从而可以使得UP实体能够更有效和高效地工作，比如：UP资源得到更合理利用，DRB上的数据传输及时恢复正常，UP实体内故障得到及时清除等。
如图6所示，本公开实施例的同步系统，包括CP实体41和UP实体42。
本公开实施例的CP实体41，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现以下步骤：
确定进行同步操作的待统计内容、对象和上报策略；其中，所述同步操作包括如下至少之一：工作状态同步操作、资源状态同步操作；
向用户面UP实体发送同步操作的请求，所述请求中携带所述同步操作的待统计内容、对象和上报策略的配置信息。
在一实施方式中，所述处理器执行所述程序时还实现：
确定进行同步操作的待统计内容、对象和上报策略的步骤中，还确定同步操作的动作类型；所述同步操作的动作类型包括如下之一：建立启动、修改重配和删除停止；
所述请求中还携带所述动作类型的配置信息。
在一实施方式中，向UP实体发送同步操作的请求之后，所述处理器执行所述程序时还实现：
接收所述UP实体发送的同步操作的响应，所述响应中携带对所述请求接受或拒绝的反馈信息，以及，对所述请求接受时，还携带对所述请求中携带的配置信息全部接受或部分接受的反馈信息。
在一实施方式中，接收到表示接受的同步操作的响应之后，所述处理 器执行所述程序时还实现：
接收所述UP实体上报的同步操作的统计结果。
在一实施方式中，接收所述UP实体上报的同步操作的统计结果之后，所述处理器执行所述程序时还实现：
根据接收到的所述统计结果，执行相应的CP响应操作。
本公开实施例的UP实体42，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现以下步骤：
接收CP实体发送的同步操作的请求，所述请求中携带所述同步操作的待统计内容、对象和上报策略的配置信息；其中，所述同步操作包括如下至少之一：工作状态同步操作、资源状态同步操作；
确定对所述请求和所述请求中的配置信息接受或拒绝，向所述CP实体发送同步操作的响应，所述响应中携带对所述请求接受或拒绝的反馈信息，以及，对所述请求接受时，还携带对所述请求中携带的配置信息全部接受或部分接受的反馈信息。
在一实施方式中，所述请求中还携带所述同步操作的动作类型的配置信息，所述同步操作的动作类型包括如下之一：建立启动、修改重配和删除停止。
在一实施方式中，所述UP实体确定对所述请求接受之后，所述处理器执行所述程序时还实现：
根据确定接受的待统计内容、对象和上报策略的配置信息，对所述对象进行相应的跟踪分析统计，按照上报策略，向所述CP实体上报的同步操作的统计结果。
在本公开实施例中，通过CP实体向UP实体发送同步操作的请求，可以实时地跟踪UP实体内的各种待同步信息内容的状态。CP实体根据UP实体上报的同步操作的统计结果，执行相应的控制面响应操作，从而可以使得UP实体能够更有效和高效地工作，比如：UP资源得到更合理利用，DRB上的数据传输及时恢复正常，UP实体内故障得到及时清除等。
如图7所示，本公开实施例的同步装置，包括：
第一确定模块51，配置为确定进行同步操作的待统计内容、对象和上报策略；其中，所述同步操作包括如下至少之一：工作状态同步操作、资源状态同步操作；
第一发送模块52，配置为向用户面UP实体发送同步操作的请求，所述请求中携带所述同步操作的待统计内容、对象和上报策略的配置信息。
在一实施方式中，第一确定模块51，还配置为确定同步操作的动作类型；所述同步操作的动作类型包括如下之一：建立启动、修改重配和删除停止；
所述请求中还携带所述动作类型的配置信息。
在一实施方式中，还包括：
第一接收模块53，配置为接收所述UP实体发送的同步操作的响应，所述响应中携带对所述请求接受或拒绝的反馈信息，以及，对所述请求接受时，还携带对所述请求中携带的配置信息全部接受或部分接受的反馈信息。
在一实施方式中，所述第一接收模块53，还配置为接收所述UP实体上报的同步操作的统计结果。
在一实施方式中，还包括：
第一执行模块54，配置为根据接收到的所述统计结果，执行相应的控制面响应操作。
在本公开实施例中，通过向UP实体发送同步操作的请求，可以实时地跟踪UP实体内的各种待同步信息内容的状态。CP实体根据UP实体上报的同步操作的统计结果，执行相应的控制面响应操作，从而可以使得UP实体能够更有效和高效地工作，比如：UP资源得到更合理利用，DRB上的数据传输及时恢复正常，UP实体内故障得到及时清除等。
如图8所示，本公开实施例实施例的同步装置，包括：
第二接收模块61，配置为于接收CP实体发送的同步操作的请求，所述请求中携带所述同步操作的待统计内容、对象和上报策略的配置信息；其中，所述同步操作包括如下至少之一：工作状态同步操作、资源状态同步操作；
第二确定模块62，配置为确定对所述请求和所述请求中的配置信息接受或拒绝；
第二发送模块63，配置为根据确定模块的决策，向所述CP实体发送同步操作的响应，所述响应中携带对所述请求接受或拒绝的反馈信息，以及，对所述请求接受时，还携带对所述请求中携带的配置信息全部接受或部分接受的反馈信息。
在一实施方式中，还包括：
第二执行模块64，配置为在确定对所述请求接受之后，所述UP实体根据确定接受的待统计内容、对象和上报策略的配置信息，对所述对象进行相应的跟踪分析统计；
所述第二发送模块63，还配置为按照上报策略，向所述CP实体上报的同步操作的统计结果。
在本公开实施例中，通过CP实体向UP实体发送同步操作的请求，可以实时地跟踪UP实体内的各种待同步信息内容的状态。CP实体根据UP实体上报的同步操作的统计结果，执行相应的控制面响应操作，从而可以使得UP实体能够更有效和高效地工作，比如：UP资源得到更合理利用，DRB上的数据传输及时恢复正常，UP实体内故障得到及时清除等。
下面以应用示例进行说明，值得注意的是：以下对应用示例的编号，并不代表应用示例之间的优先关系，只是为了区分应用示例而已：
应用示例1
某时刻，UE1配置有两条GBR业务属性的DRB：DRB1和DRB2，分别用于承载传输语音和视频数据业务，网络侧CP实体和UP实体都支持本公开实施例的内容，可以以DRB为粒度进行同步操作。图9为应用示例1 的流程示意图。
步骤901：网络侧CP实体通过E1接口流程消息UP Status Synchronization Request(UP状态同步请求)向UP实体请求同步操作，操作对象为UE1中的DRB1和DRB2，需要同步的内容为：业务数据流上下行的服务质量QoS是否被正常地执行和维护，可选参数为：QoS统计时间窗＝10s，周期地统计GBR实际平均速率。当DRB1和DRB2各自的GBR实际平均速率<GBR签约要求速率的时候，记录该DRB的QoS受损标识；当连续出现3次QoS受损的时候，UP实体以事件方式上报相关的结果。
步骤902：UP实体接收且接受了CP实体针对UE1中的DRB1和DRB2的同步操作请求和相关参数配置，通过E1接口流程消息UP Status Synchronization Response(UP状态同步响应)向CP实体回复“同步操作请求和配置参数都已被接受”。
步骤903：UP实体将以10s单位为QoS统计时间窗长度，周期地进行GBR实际平均速率的统计和记录，和GBR签约要求速率进行比较，分别获得DRB1和DRB2的“QoS受损标识串”，如{。。正常，受损，正常，受损，受损，受损}。
步骤904：按照之前CP实体配置的上报策略和参数，当连续出现3次QoS受损记录的时候，UP实体通过E1接口流程消息UP Status Synchronization Report(UP状态同步报告)向CP实体上报“某某DRB的QoS受损”事件，可选地可以上报“QoS受损标识串”信息。
步骤905：CP实体通过UP实体上报的内容，得知DRB1的QoS连续受损，用户的语音业务QoS体验下降，于是通过NGAP流程消息PDU Session Resource Notify(PDU会话资源通知)，告知AMF相关情况。
步骤906：AMF根据CP实体的上报内容，触发PDU Session Resource Modify(PDU会话资源修改)流程，对DRB1所关联的PDU Session属性内容进行修改，比如：释放掉视频业务数据流。
应用示例2
某时刻，UE2配置有三条Non GBR业务属性的DRB：DRB1，DRB2，DRB3分别用于承载传输不同的文件块对象，它们属于同一个PDU Session。网络侧CP实体和UP实体都支持本公开实施例的内容，可以以PDU Session为粒度进行同步操作。图10为应用示例2的流程示意图。
步骤1001：网络侧CP实体通过E1接口流程消息UP Status Synchronization Request向UP实体请求同步操作，操作对象为UE1中的PDU Session1(被映射到DRB1，DRB2，DRB3上)，需要同步的内容为：PDU Session级别的AMBR是否被正常地执行和维护，可选参数为：AMBR统计时间窗＝20s，周期地统计AMBR实际平均速率。当DRB1，DRB2，DRB3聚合的AMBR实际平均速率>AMBR签约要求速率的时候，记录该PDU Session AMBR超限标识；当出现第一次AMBR超限标识的时候，UP实体以事件方式上报相关的结果。
步骤1002：UP实体接收且接受了CP实体针对UE2中PDU Session1的同步操作请求和相关参数配置，通过E1接口流程消息UP Status Synchronization Response向CP实体回复“同步操作请求和配置参数都已被接受”。
步骤1003：UP实体将以20s单位为AMBR统计时间窗长度，周期地进行AMBR实际平均速率的统计和记录，和AMBR签约要求速率进行比较，从而获得PDU Session1AMBR的“历史标识串”，如{。。正常，正常，正常，超限}。
步骤1004：按照之前CP实体配置的上报策略和参数，当出现第一次AMBR超限标识的时候，UP实体通过E1接口流程消息UP Status Synchronization Report向CP实体上报“PDU Session1 AMBR超限”事件。
步骤1005：CP实体通过UP实体上报的内容，得知PDU Session1 AMBR超限，用户的文件下载业务QoS超过了签约的限制，于是通过NGAP流程消息PDU Session Resource Notify，告知AMF相关情况。
步骤1006：AMF根据CP实体的上报内容，触发PDU Session Resource Modify流程，对PDU Session1属性内容进行修改，比如：释放掉PDU Session1中一些QoS Flow数据流。
应用示例3
某时刻，UE3配置有两条Non GBR业务属性的DRB：DRB1，DRB2分别用于承载传输网页浏览和在线音频数据的业务，它们属于同一个PDU Session。网络侧CP实体和UP实体都支持本公开实施例的内容，可以以DRB为粒度进行同步操作。图11为应用示例3的流程示意图。
步骤1101：网络侧CP实体通过E1接口流程消息UP Status Synchronization Request向UP实体请求同步操作，操作对象为UE1中的DRB1和DRB2，需要同步的内容为：当某个DRB出现下行PDCP SN最大值即将翻转的时候，UP实体以事件方式上报相关的结果。
步骤1102：UP实体接收且接受了CP实体针对UE3中的DRB1和DRB2的同步操作请求和相关参数配置，通过E1接口流程消息UP Status Synchronization Response向CP实体回复“同步操作请求和配置参数都已被接受”。
步骤1103：随着DRB1和DRB2中承载的下行数据块连续地传输，各自下行PDCP实体的SN序列号+1递加；到某时刻，DRB2对应的下行PDCP SN达到最大值，SN即将发生翻转被重置回到0，UP实体暂停DRB2上的下行数据传输。
步骤1104：按照之前CP实体配置的上报策略和参数，当某个DRB出现下行PDCP SN最大值即将翻转的时候，UP实体通过E1接口流程消息UP Status Synchronization Report向CP实体上报“DRB2下行PDCP SN最大值即将翻转”的事件。
步骤1105：CP实体通过UP实体上报的内容，得知DRB2的下行PDCP SN最大值即将翻转，于是该承载的安全子密钥(包括加密和完整性保护)都需要进行更新(Key Refresh过程)，于是通过E1AP流程消息Security Mode Update(安全模式更新)，为UP实体中UE3生成和配置新的安全子密钥。CP实体还需要通过空口消息流程RRC Connection Reconfiguration，为UE3配置新的安全子密钥，以和UP实体侧保持安全操作相关配置一致。
步骤1106：UP实体根据CP实体发来的新安全参数配置，对UE3中的DRB2配置和施加新的安全子密钥，并且通过E1AP流程消息Security Mode Update Acknowledge(安全模式更新确认)返回确认通知CP实体。之后UP实体基于新的安全子密钥，恢复DRB2中的下行数据安全传输，分别用新加密密钥对下行数据包进行加密操作，新完整性保护密钥对下行数据包进行完整性保护操作。
应用示例4
某时刻，UE4配置有两条GBR业务属性的DRB：DRB1，DRB2分别用于承载传输上行文件块和本地云盘备份的业务，它们属于不同的PDU Session。网络侧CP实体和UP实体都支持本公开实施例的内容，可以以DRB为粒度进行同步操作。图12为应用示例4的流程示意图。
步骤1201：网络侧CP实体通过E1接口流程消息UP Status Synchronization Request向UP实体请求同步操作，操作对象为UE1中的DRB1和DRB2，需要同步的内容为：当某个DRB出现上行安全操作失败(解密失败和完整性保护校验失败中至少之一)的时候，UP实体以事件方式上报相关的结果。
步骤1202：UP实体接收且接受了CP实体针对UE4中的DRB1和DRB2的同步操作请求和相关参数配置，通过E1接口流程消息UP Status Synchronization Response向CP实体回复“同步操作请求和配置参数都已被接受”。
步骤1203：在DRB1和DRB2中承载的上行数据块连续传输过程中，
到某段时间，黑客对UE4和UP实体之间的上行无线链路进行了恶意攻击，上行强行插入了连续地“假数据包”，UP实体接收到这些“假数据包”之后，
检测到DRB2上出现完整性保护校验错误；随后UP实体暂停DRB2上的上行数据接收，以免接收到更多的“假数据包”，但同时可能会错失来自UE4的一些“真数据包”。
步骤1204：按照之前CP实体配置的上报策略和参数，当某个DRB出现上行安全操作失败的时候，UP实体通过E1接口流程消息UP Status  Synchronization Report向CP实体上报“检测到DRB2上完整性保护校验错误”的事件。
步骤1205：CP实体通过UP实体上报的内容，得知DRB2检测到DRB2上完整性保护校验错误，于是通过E1AP流程消息Security Mode Update Request，为UP实体中UE4生成和配置新的安全子密钥，并且要求尝试恢复之前丢失的上行真数据包。CP实体还需要通过空口消息流程RRC Connection Reconfiguration，为UE4配置新的安全子密钥，以和UP实体侧保持安全操作相关配置一致。
步骤1206：UP实体根据CP实体发来的新安全参数配置，对UE4中的DRB2配置和施加新的安全子密钥，并且通过E1AP流程消息Security Mode Update Response返回通知CP实体，同意尝试恢复之前丢失的上行数据包。之后UP实体基于新的安全子密钥，恢复DRB2中的上行数据传输，尝试恢复之前丢失的上行真数据包。
应用示例5
某时刻，某UP实体处理单元正承载着众多UEs的不同类型业务数据的传输服务。网络侧CP实体和UP实体都支持本公开实施例的内容，可以以UP实体处理单元为粒度进行同步操作。图13为应用示例5的流程示意图。
步骤1301：网络侧CP实体通过E1接口流程消息UP Status Synchronization Request向UP实体请求同步操作，操作对象为特定的UP实体处理单元，需要同步的内容为：统计计算它的处理资源占空比(即：平均被占用使用的资源和总资源量之间的比例)，可选参数为：占空比统计时间窗＝60s，UP实体以周期的方式上报相关的统计结果。
步骤1302：UP实体接收且接受了CP实体针对特定的UP实体处理单元的同步操作请求和相关参数配置，通过E1接口流程消息UP Status Synchronization Response向CP实体回复“同步操作请求和配置参数都已被接受”。
步骤1303：在承载众多UEs的不同业务类型数据传输的服务过程中，UP实体周期连续地统计计算特定的UP实体处理单元中的处理资源占空比，以60s为一个统计计算上报的周期，从而获得时间轴上的历史记录表，比如{60％，70％，80％，75％，78％，82％……}，60％表示：在上一个统计观察窗内该UP实体处理单元中的处理资源平均被占用消耗了总量的60％。
步骤1304：按照之前CP实体配置的上报策略和参数，UP实体通过E1接口流程消息UP Status Synchronization Report向CP实体，以60s为周期进行统计计算结果的上报，从而CP实体能够获悉到UP实体侧的处理资源开销实时的状况。
本公开实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行如图3所示的同步方法。
本公开实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行如图4所示的同步方法。
本公开实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行如图5所示的同步方法。
在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
在一些实施例中，上述计算机可读存储介质均为非瞬间存储介质。
本实施例还提供一种网元，其中，包括：
收发器，可为网元的通信接口，例如，CP与UP之间的接口
存储器，可包括各种存储介质；
处理器，分别与所述收发器及存储器连接，配置为通过计算机可执行指令的执行，控制所述收发器的信息收发及所述存储器的信息存储，并实现由CP或UP执行的同步方法、例如，图3至图5以及图9至图13所示同步方法中的一个或多个。
该处理器可为各种类型的处理器，该处理器可为中央处理器、微处理器、数字信号处理器、可编程阵列或专用集成电路等。
所述处理器，可通过集成电路总线等总线接口，分别与所述收发器及存储器连接。
显然，本领域的技术人员应该明白，上述的本公开实施例的模块或步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开实施例不限制于任何特定的硬件和软件结合。
虽然本公开实施例所揭露的实施方式如上，但所述的内容仅为便于理解本公开实施例而采用的实施方式，并非用以限定本公开。任何本公开所属领域内的技术人员，在不脱离本公开所揭露的精神和范围的前提下，可以在实施的形式及细节上进行任何的修改与变化，但本公开的专利保护范围，仍须以所附的权利要求书所界定的范围为准。

Claims (23)

  1. 一种同步方法，包括：
    控制面CP实体确定进行同步操作的待统计内容、对象和上报策略；其中，所述同步操作包括如下至少之一：工作状态同步操作、资源状态同步操作；
    所述CP实体向用户面UP实体发送同步操作的请求，所述请求中携带所述同步操作的待统计内容、对象和上报策略的配置信息。
  2. 如权利要求1所述的方法，其中，
    所述控制面CP实体确定进行同步操作的待统计内容、对象和上报策略的步骤中，还确定同步操作的动作类型；所述同步操作的动作类型包括如下之一：建立启动、修改重配和删除停止；
    所述CP实体向用户面UP实体发送同步操作的请求的步骤中，所述请求中还携带所述动作类型的配置信息。
  3. 如权利要求1或2所述的方法，其中，所述CP实体向UP实体发送同步操作的请求之后，所述方法还包括：
    所述CP实体接收所述UP实体发送的同步操作的响应，所述响应中携带对所述请求接受或拒绝的反馈信息，以及，对所述请求接受时，还携带对所述请求中携带的配置信息全部接受或部分接受的反馈信息。
  4. 如权利要求3所述的方法，其中，所述CP实体接收到表示接受的同步操作的响应之后，所述方法还包括：
    所述CP实体接收所述UP实体上报的同步操作的统计结果。
  5. 如权利要求4所述的方法，其中，所述CP实体接收所述UP实体上报的同步操作的统计结果之后，所述方法还包括：
    所述CP实体根据接收到的所述统计结果，执行相应的CP响应操作。
  6. 如权利要求5所述的方法，其中，
    所述CP响应操作包括：对核心网网元、基站网元、用户设备UE或 UP实体的工作状态和资源状态中的至少之一进行重配置调整。
  7. 如权利要求1所述的方法，其中，
    所述待统计内容的配置信息包括如下至少之一：分析统计用户业务数据流工作状态的配置参数信息、分析统计UP实体的处理单元工作和资源状态的配置参数信息；
    所述分析统计用户业务数据流工作状态的配置参数信息包括如下至少之一：业务数据流上下行传输速率信息、业务数据流上下行服务质量信息、下行业务数据流的分组数据汇聚协议PDCP序列号信息、上行业务数据流安全操作信息、上行业务数据流的PDCP数据包恢复信息；
    所述分析统计UP实体的处理单元工作和资源状态的配置参数信息包括如下至少之一：所述处理单元的基带资源占空比、基带资源忙闲比、故障信息、正在服务的数据无线承载DRB个数、协议数据单元PDU会话个数。
  8. 如权利要求1所述的方法，其中，所述进行同步操作的对象包括如下至少之一：
    一条或多条DRB、一个或多个PDU会话、一个UE、多个UE的群集合、指定的UP实体的处理单元。
  9. 如权利要求1所述的方法，其中，所述上报策略包括如下之一：指定事件触发上报、时间周期触发上报，指定事件触发的周期性上报。
  10. 如权利要求4所述的方法，其中，
    所述同步操作的请求、响应和统计结果通过CP实体和UP实体之间的E1接口的信令承载。
  11. 一种同步方法，包括：
    用户面UP实体接收CP实体发送的同步操作的请求，所述请求中携带所述同步操作的待统计内容、对象和上报策略的配置信息；其中，所述同步操作包括如下至少之一：工作状态同步操作、资源状态同步操作；
    所述UP实体确定对所述请求和所述请求中的配置信息接受或拒绝，向所述CP实体发送同步操作的响应，所述响应中携带对所述请求接受或拒绝 的反馈信息，以及，对所述请求接受时，还携带对所述请求中携带的配置信息全部接受或部分接受的反馈信息。
  12. 如权利要求11所述的方法，其中，
    所述请求中还携带所述同步操作的动作类型的配置信息，所述同步操作的动作类型包括如下之一：建立启动、修改重配和删除停止。
  13. 如权利要求11或12所述的方法，其中，所述UP实体确定对所述请求接受之后，所述方法还包括：
    所述UP实体根据确定接受的待统计内容、对象和上报策略的配置信息，对所述对象进行相应的跟踪分析统计，按照上报策略，向所述CP实体上报的同步操作的统计结果。
  14. 如权利要求11所述的方法，其中，
    所述待统计内容的配置信息包括如下至少之一：分析统计用户业务数据流工作状态的配置参数信息、所述分析统计UP实体的处理单元工作和资源状态的配置参数信息；
    所述分析统计用户业务数据流工作状态的配置参数信息包括如下至少之一：业务数据流上下行传输速率信息、业务数据流上下行服务质量信息、下行业务数据流的分组数据汇聚协议PDCP序列号信息、上行业务数据流安全操作信息、上行业务数据流的PDCP数据包恢复信息；
    所述分析统计UP实体的处理单元工作和资源状态的配置参数信息包括如下至少之一：所述处理单元的基带资源占空比、基带资源忙闲比、故障信息、正在服务的数据无线承载DRB个数、协议数据单元PDU会话个数。
  15. 如权利要求11所述的方法，其中，所述同步操作的对象包括如下至少之一：
    一条或多条DRB、一个或多个PDU会话、一个UE、多个UE的群集合、指定的UP实体的处理单元。
  16. 如权利要求11所述的方法，其中，所述上报策略包括如下之一：指定事件触发上报、时间周期触发上报，指定事件触发的周期性上报。
  17. 如权利要求13所述的方法，其中，
    所述同步操作的请求、响应和统计结果通过CP实体和UP实体之间的E1接口的信令承载。
  18. 一种同步装置，其中，包括：
    第一确定模块，配置为确定进行同步操作的待统计内容、对象和上报策略；其中，所述同步操作包括如下至少之一：工作状态同步操作、资源状态同步操作；
    第一发送模块，配置为向用户面UP实体发送同步操作的请求，所述请求中携带所述同步操作的待统计内容、对象和上报策略的配置信息。
  19. 如权利要求18所述的装置，其中，还包括：
    第一接收模块，配置为接收所述UP实体发送的同步操作的响应，所述响应中携带对所述请求接受或拒绝的反馈信息，以及，对所述请求接受时，还携带对所述请求中携带的配置信息全部接受或部分接受的反馈信息。
  20. 一种同步装置，包括：
    第二接收模块，配置为接收CP实体发送的同步操作的请求，所述请求中携带所述同步操作的待统计内容、对象和上报策略的配置信息；其中，所述同步操作包括如下至少之一：工作状态同步操作、资源状态同步操作；
    第二确定模块，配置为确定对所述请求和所述请求中的配置信息接受或拒绝；
    第二发送模块，配置为根据确定模块的决策，向所述CP实体发送同步操作的响应，所述响应中携带对所述请求接受或拒绝的反馈信息，以及，对所述请求接受时，还携带对所述请求中携带的配置信息全部接受或部分接受的反馈信息。
  21. 如权利要求20所述的装置，其中，还包括：
    第二执行模块，配置为在确定对所述请求接受之后，根据确定接受的待统计内容、对象和上报策略的配置信息，对所述对象进行相应的跟踪分析统计；
    所述第二发送模块，还配置为按照上报策略，向所述CP实体上报的同 步操作的统计结果。
  22. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1-10或11-17任一项的同步方法。
  23. 一种网元，其中，包括：
    收发器，
    存储器；
    处理器，分别与所述收发器及存储器连接，配置为通过计算机可执行指令的执行，控制所述收发器的信息收发及所述存储器的信息存储，
    并实现权利要求1-10或11-17任一项的同步方法。
PCT/CN2018/093804 2017-09-28 2018-06-29 一种同步方法和装置、网元及存储介质 WO2019062244A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/650,850 US11382052B2 (en) 2017-09-28 2018-06-29 Synchronization method and apparatus, network element, and storage medium
EP18863335.8A EP3691354B1 (en) 2017-09-28 2018-06-29 Synchronisation method and apparatus, network element, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710901674.2A CN109587782B (zh) 2017-09-28 2017-09-28 一种同步方法和装置
CN201710901674.2 2017-09-28

Publications (1)

Publication Number Publication Date
WO2019062244A1 true WO2019062244A1 (zh) 2019-04-04

Family

ID=65900491

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/093804 WO2019062244A1 (zh) 2017-09-28 2018-06-29 一种同步方法和装置、网元及存储介质

Country Status (4)

Country Link
US (1) US11382052B2 (zh)
EP (1) EP3691354B1 (zh)
CN (1) CN109587782B (zh)
WO (1) WO2019062244A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019193553A1 (en) * 2018-04-06 2019-10-10 Telefonaktiebolaget Lm Ericsson (Publ) Qos flow management over e1
CN113412665B (zh) * 2019-07-12 2023-09-22 Oppo广东移动通信有限公司 一种会话设置方法、网络设备、用户设备
CN112333232A (zh) * 2020-09-18 2021-02-05 天地互联科技(广州)有限公司 Ifec机上数据同步方法及其系统
CN112579237B (zh) * 2020-12-17 2024-06-11 百果园技术(新加坡)有限公司 基于mvvm模式的事件响应方法、装置、设备和介质
CN116266812A (zh) * 2021-12-17 2023-06-20 华为技术有限公司 一种过载处理方法、网络设备及系统
CN114710394A (zh) * 2022-03-30 2022-07-05 亚信科技（中国）有限公司 告警同步方法、装置、电子设备及可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101547403A (zh) * 2008-03-24 2009-09-30 大唐移动通信设备有限公司 实现无线网络控制器间的同步的方法、系统和设备
CN101931876A (zh) * 2009-06-26 2010-12-29 华为技术有限公司 传递信息的方法、装置和系统
CN104094536A (zh) * 2013-02-01 2014-10-08 Lg电子株式会社 用于发送和接收mbsfn子帧的方法和装置
EP3011785A1 (en) * 2013-06-21 2016-04-27 Panasonic Intellectual Property Corporation of America Uplink switching of communication links for mobile stations in dual connectivity

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9392462B2 (en) * 2009-01-28 2016-07-12 Headwater Partners I Llc Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy
EP2854475B1 (en) * 2012-06-29 2018-10-31 Huawei Technologies Co., Ltd. Gateway system, device and communication method
WO2016105570A1 (en) * 2014-12-23 2016-06-30 Interdigital Patent Holdings, Inc. Latency reduction in lte systems
WO2017045708A1 (en) * 2015-09-16 2017-03-23 Nokia Solutions And Networks Oy Control and user plane decoupling in radio access network
US10630410B2 (en) * 2016-05-13 2020-04-21 Telefonaktiebolaget Lm Ericsson (Publ) Network architecture, methods, and devices for a wireless communications network
CN106102106B (zh) * 2016-06-20 2020-03-24 电信科学技术研究院 一种终端接入的方法、装置及网络架构
WO2018166607A1 (en) * 2017-03-16 2018-09-20 Huawei Technologies Co., Ltd. Communication techniques based on adaptive numerology
US11228991B2 (en) * 2019-02-01 2022-01-18 Cisco Technology, Inc. Link auto-negotiation between a radio equipment controller (REC) and radio equipment (RE) in an ethernet-based fronthaul network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101547403A (zh) * 2008-03-24 2009-09-30 大唐移动通信设备有限公司 实现无线网络控制器间的同步的方法、系统和设备
CN101931876A (zh) * 2009-06-26 2010-12-29 华为技术有限公司 传递信息的方法、装置和系统
CN104094536A (zh) * 2013-02-01 2014-10-08 Lg电子株式会社 用于发送和接收mbsfn子帧的方法和装置
EP3011785A1 (en) * 2013-06-21 2016-04-27 Panasonic Intellectual Property Corporation of America Uplink switching of communication links for mobile stations in dual connectivity

Also Published As

Publication number Publication date
CN109587782B (zh) 2021-04-30
EP3691354A4 (en) 2021-06-23
US20200280937A1 (en) 2020-09-03
CN109587782A (zh) 2019-04-05
EP3691354A1 (en) 2020-08-05
EP3691354B1 (en) 2023-11-08
US11382052B2 (en) 2022-07-05

Similar Documents

Publication Publication Date Title
CN109587782B (zh) 一种同步方法和装置
US10645618B2 (en) Link failure recovery method and apparatus
US20230180349A1 (en) Bearer configuration method and apparatus, context information management method and apparatus, releasing method and apparatus, and device
US10805849B2 (en) Handover method and apparatus
US11240699B2 (en) Insufficient resources in the UE during PDU session establishment procedure
WO2019096281A1 (zh) 一种通信方法，通信设备及其通信系统
WO2018045877A1 (zh) 网络切片控制方法及相关设备
US8934902B2 (en) Method of notifying switching information and base station
US11438739B2 (en) Multi-connectivity data volume reporting method
US9807626B2 (en) Processing method of wireless fidelity technology and user equipment
KR20190127846A (ko) 사용자 정보 관리를 위한 방법 및 시스템
US10257749B2 (en) Information interaction method, system and base station
EP3570582B1 (en) Entity configuration method, device and system, and cu-u
CN104955109A (zh) 配置UE的聚合最大速率的方法、协调non-GBR业务的聚合速率及基站
CN104685959B (zh) 具有统一接口的无源无线电链路控制实体
KR102480610B1 (ko) 주소 송신 방법, 장치 및 저장매체
WO2019033905A1 (zh) 数据流传输安全控制方法及装置
CN114788365A (zh) 在无线电接入网通信系统中经由e2接口进行服务订阅的设备和方法
CN104023376A (zh) 多个无线接入网聚合系统及其实现方法和接入网网元
US11223968B2 (en) Method, apparatus and system for reporting radio access network traffic
JP6208813B2 (ja) リンク障害復旧方法および装置
JP6478195B2 (ja) リンク障害復旧方法および装置
KR102277007B1 (ko) 단말 정보 전송 방법 및 장치
CN115942257A (zh) 一种流量控制的方法及设备
US20170230332A1 (en) Making International Mobile Subscriber Identity Available at Base Station

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18863335

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018863335

Country of ref document: EP

Effective date: 20200428