WO2019174386A1 - 无线接入网流量报告方法以及装置和系统、存储介质 - Google Patents

无线接入网流量报告方法以及装置和系统、存储介质 Download PDF

Info

Publication number
WO2019174386A1
WO2019174386A1 PCT/CN2019/070937 CN2019070937W WO2019174386A1 WO 2019174386 A1 WO2019174386 A1 WO 2019174386A1 CN 2019070937 W CN2019070937 W CN 2019070937W WO 2019174386 A1 WO2019174386 A1 WO 2019174386A1
Authority
WO
WIPO (PCT)
Prior art keywords
traffic
base station
pdcp
radio access
access network
Prior art date
Application number
PCT/CN2019/070937
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 EP19766744.7A priority Critical patent/EP3749010A4/en
Priority to US16/977,872 priority patent/US11223968B2/en
Publication of WO2019174386A1 publication Critical patent/WO2019174386A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/045—Interfaces between hierarchically different network devices between access point and backbone network device

Definitions

  • the present application relates to communication technologies, for example, to a radio access network data volume report method and apparatus and system, and a computer readable storage medium.
  • CA Carrier Aggregation
  • the UE can simultaneously send and receive data on multiple component carriers (CCs).
  • the user equipment User Equipment, UE
  • PCC primary component carrier
  • SCC secondary component carrier
  • the SCC is the base station after the UE enters the connected state. Configured.
  • the serving cell (Serving Cell) corresponding to the PCC is called a primary cell (PCell), and the serving cell corresponding to the SCC is called a secondary cell (SCell).
  • PCell primary cell
  • SCell secondary cell
  • Dual connectivity is supported in both 4G and 5G systems.
  • the dual-connected UE can maintain connection with two base stations at the same time.
  • One base station is called a primary base station (MN), and the other base station is called a secondary base station (SN).
  • MN primary base station
  • SN secondary base station
  • a Packet Data Convergence Protocol (PDCP) entity corresponds to two or more radio link control ( Radio Link Control (RLC) entity.
  • RLC Radio Link Control
  • Multiple RLC entities transmit the same data on different serving cells of the same base station (when CA is operating) or on different base stations (when DC is operating).
  • the embodiment of the present application provides a radio access network traffic reporting method, device, and system, and a computer readable storage medium, which implements a data volume report of a radio access network when the UE performs replication transmission, and meets the requirements of the operator.
  • An embodiment of the present application provides a radio access network traffic reporting method, including:
  • the base station acquires the traffic information of the data radio bearer, where the traffic information of the data radio bearer includes: a packet data convergence protocol protocol data unit PDCP PDU generated by the packet data convergence protocol PDCP or a packet data convergence protocol service data unit PDCP SDU traffic, PDCP The traffic sent to the PDCP PDU or PDCP SDU of the radio link control;
  • the traffic information of the data radio bearer includes: a packet data convergence protocol protocol data unit PDCP PDU generated by the packet data convergence protocol PDCP or a packet data convergence protocol service data unit PDCP SDU traffic, PDCP The traffic sent to the PDCP PDU or PDCP SDU of the radio link control;
  • the base station generates a radio access network traffic report according to the traffic information of the data radio bearer, where the radio access network traffic report includes at least one of the following: the radio access network traffic of the granularity unit that is not included in the repeated part, and the repetition Part of the radio access network traffic of the granularity unit and the radio access network traffic of the repeating part of the granularity unit;
  • the base station sends the radio access network traffic report to the core network.
  • An embodiment of the present application provides a radio access network traffic reporting apparatus, including a memory and a processor, where the memory stores a program, and the program implements the radio access network traffic when read and executed by the processor. Reporting method.
  • An embodiment of the present application provides a computer readable storage medium storing one or more programs, the one or more programs being executable by one or more processors to implement any The radio access network traffic reporting method described in the embodiment.
  • At least one embodiment of the present application provides a radio access network traffic reporting system, including a base station and a core network, where:
  • the base station is configured to acquire the traffic information of the data radio bearer, where the traffic information of the data radio bearer includes: the traffic of the PDCP PDU or the PDCP SDU generated by the PDCP, and the PDCP PDU or the PDCP SDU sent by the PDCP to the radio link control Generating a radio access network traffic report according to the traffic information of the data radio bearer, and transmitting the radio access network traffic report to the core network;
  • the radio access network traffic report includes at least one of the following: The radio access network traffic of the granularity unit, the radio access network traffic of the granularity unit when the repeated part is included, and the radio access network traffic of the repeated part of the granularity unit;
  • the core network is configured to receive the radio access network traffic report sent by the base station.
  • FIG. 1 is a flowchart of a radio access network traffic reporting method according to an embodiment of the present application
  • FIG. 2 is a flowchart of a radio access network traffic reporting method according to an embodiment of the present application
  • FIG. 3 is a flowchart of a radio access network traffic reporting method according to an embodiment of the present application.
  • FIG. 4 is a flowchart of a radio access network traffic reporting method according to an embodiment of the present application.
  • FIG. 5 is a flowchart of a radio access network traffic reporting method according to an embodiment of the present application.
  • FIG. 6 is a flowchart of a radio access network traffic reporting method according to an embodiment of the present application.
  • FIG. 7 is a flowchart of a radio access network traffic reporting method according to an embodiment of the present application.
  • FIG. 8 is a flowchart of a radio access network traffic reporting method according to an embodiment of the present application.
  • FIG. 9 is a flowchart of a radio access network traffic reporting method according to an embodiment of the present application.
  • FIG. 10 is a flowchart of a radio access network traffic reporting method according to an embodiment of the present application.
  • FIG. 11 is a flowchart of a radio access network traffic reporting method according to an embodiment of the present application.
  • FIG. 12 is a flowchart of a radio access network traffic reporting method according to an embodiment of the present application.
  • FIG. 13 is a flowchart of a radio access network traffic reporting method according to an embodiment of the present application.
  • FIG. 14 is a flowchart of a radio access network traffic reporting method according to an embodiment of the present application.
  • FIG. 15 is a flowchart of a radio access network traffic reporting method according to an embodiment of the present application.
  • 16 is a flowchart of a radio access network traffic reporting method according to an embodiment of the present application.
  • FIG. 17 is a flowchart of a radio access network traffic reporting method according to an embodiment of the present application.
  • FIG. 18 is a block diagram of a radio access network traffic reporting apparatus according to an embodiment of the present application.
  • the 4G base station is called an evolved Node B (eNB).
  • the interface between the eNB and the core network (CN) is called the S1 interface.
  • the 5G base station is called a new generation radio access network node (NG RAN Node or gNB).
  • the interface between the gNB is called an Xn interface, and the interface between the gNB and the CN is called an NG interface.
  • QoS Quality of Service
  • the bearers are one-to-one correspondence.
  • Protocol Data Unit Session PDU Session
  • QoS Flow Quality of Service Flow
  • a UE can have multiple PDU sessions.
  • a PDU session can contain multiple QoS flows.
  • Multiple QoS flows of the same PDU session can be mapped to the same DRB.
  • the QoS flows of different PDU sessions cannot be mapped to the same DRB.
  • QoS flow includes: guaranteed bit rate quality of service (GBR QoS flow) and non-guaranteed bit rate QoS flow (non-GBR QoS flow).
  • SDAP Service Data Adaptation Protocol
  • PDCP Packet Data Convergence Protocol
  • Each PDU Session corresponds to one SDAP entity (Entity), and each DRB corresponds to one PDCP entity.
  • a 5G base station can be divided into two parts: a central unit (CU) and a distributed unit (DU).
  • CU central unit
  • DU distributed unit
  • One base station has one CU, and one base station can have multiple DUs. This is called a centralized unit distribution unit separation (CU DU Split). ), the interface between the CU and the DU is called the F1 interface.
  • CU DU Split centralized unit distribution unit separation
  • the CU of the 5G base station can be divided into two parts: Control Plane (CP) and User Plane (UP), which is called CP UP Split.
  • CP Control Plane
  • UP User Plane
  • the interface between CP and UP is called E1 interface. .
  • the CN sends the configuration information to the base station (which is the MN when the dual connection is connected), including at least one of the following: the UE identifier, the E-RAB identifier (for the case of 4G CN), the PDU Session identifier (for the case of 5G CN), and the QoS Flow identifier ( In the case of 5G CN, whether the repeated part of the transmission is included in the indication of the RAN traffic report, and the RAT information calculated by the traffic during the replication transmission (required when the RATs of the MN and the SN are different and the repeated part is not included).
  • the configuration granularity of the CN may be UE, E-RAB (for example, when 4G CN), PDU Session (for 5G CN), and QoS Flow level (for 5G CN).
  • the configuration information may be carried by an existing interface message between the CN and the base station such as S1 or NG, or may be carried by a new interface message between the CN and the base station.
  • the MN sends the configuration information to the SN, including at least one of the following: the UE identifier, the E-RAB identifier (for example, when the 4G CN is used), the PDU Session identifier (for the case of 5G CN), and the QoS Flow identifier (for example, 5G).
  • CN time whether the repeated part of the duplicate transmission is included in the indication of the RAN traffic report, and the RAT information calculated by the traffic during the replication transmission (required when the RATs of the MN and the SN are different and the repeated part is not included).
  • the configuration information may be carried by an existing inter-base station interface message such as X2 or Xn, or may be carried by a new inter-base station interface message.
  • the SN When dual-connected, the SN performs statistics on the DRBs of the PDs on the SN side for each PDCP: the traffic of the PDCP PDUs generated by the PDCP (set to V), and the traffic of the PDCP PDUs sent by the PDCP to the RLCs of the SN side (set to Vs, which can be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RL on the MN side set to Vm, which can be 0)
  • the SN When dual-connected, the SN sends a RAN traffic report to the MN including at least one of the following DRBs of the PDCP on the SN side: the RAN traffic V1 when the repeated part is not counted, and the RAN traffic V2 when the repeated part is counted, the repeated part RAN traffic Vd, the flow rate VrS2 of the SN side RAT when the repeated part is counted, the flow rate VrM2 of the MN side RAT when the repeated part is counted, the flow rate VrS1 of the SN side RAT when the repeated part is not counted, and the MN side when the repeated part is not counted RAT traffic VrM1.
  • the RAN traffic report may be carried by an existing inter-base station interface message such as X2 or Xn, or may be carried by a new inter-base station interface message.
  • the base station (in the case of the dual-connection, the MN) performs statistics on the DRB of the MN side for each PDCP: the traffic of the PDCP PDU generated by the PDCP (set to V), and the traffic of the PDCP PDU that is sent by the PDCP to the RLC of the MN side (set to Vm)
  • the traffic of the PDCP PDU sent by the PDCP to the RLC of the SN side (set to Vs, which can be 0)
  • the RAN traffic of the repeated part is Vd.
  • VrM2 Vm.
  • the RAT counted by the traffic is the SN side RAT
  • VrM1 Vm
  • the base station (which is the MN when dual-connected) sends the RAN traffic report to the CN, including at least one of the following:
  • the RRC traffic of the UE when the UE identifier and the repeated part are not counted that is, the sum of V1s of all DRBs of the UE
  • the RAN traffic of the UE on the MN side RAT ie, the sum of VrM1 of all DRBs of the UE) when the UE identity and the repeated part are not counted;
  • the RAN traffic of the UE on the SN side RAT ie, the sum of VrS1 of all DRBs of the UE) when the UE identity and the repeated part are not counted;
  • the RAN traffic of the UE when the UE identifier and the repeated part are counted (that is, the sum of V2s of all DRBs of the UE);
  • the RAN traffic of the UE on the MN side RAT ie, the sum of VrM2 of all DRBs of the UE) when the UE identifier and the repeated part are counted;
  • the RAN traffic of the UE on the SN side RAT ie, the sum of VrS2 of all DRBs of the UE) when the UE identifier and the repeated part are counted;
  • the UE identifier, the RAN traffic of the repeated part of the UE (that is, the sum of the Vds of all DRBs of the UE);
  • E-RAB identifier the RAN traffic of the E-RAB when the repeated part is not counted (that is, the E-RAB corresponds to the V1 of the DRB);
  • E-RAB identifier the RAN traffic of the E-RAB on the MN side RAT when the repeated part is not counted (ie, the E-RAB corresponds to the VrM1 of the DRB);
  • E-RAB identifier the RAN traffic of the E-RAB on the SN side RAT when the repeated part is not counted (ie, the E-RAB corresponds to the VrS1 of the DRB);
  • E-RAB identifier the RAN traffic of the E-RAB when the repeated part is counted (that is, the E-RAB corresponds to the V2 of the DRB);
  • E-RAB identifier the RAN traffic of the E-RAB on the MN side RAT when the repeated part is counted (ie, the E-RAB corresponds to the VrM2 of the DRB);
  • E-RAB identifier the RAN traffic of the E-RAB on the SN side RAT when the repeated part is counted (ie, the E-RAB corresponds to the VrS2 of the DRB);
  • E-RAB identifier the RAN traffic of the E-RAB repeating part (ie, the E-RAB corresponds to the Vd of the DRB);
  • the RAN session identifier and the repeated part are not included in the RAN traffic of the PDU Session (that is, the sum of V1s of all DRBs of the PDU Session);
  • the PDU session identifier and the repeated part are not counted as the RAN traffic of the PDU Session on the MN side RAT (that is, the sum of VrM1 of all DRBs of the PDU Session);
  • the PDU session identifier and the repeated part are not counted as the RAN traffic of the PDU Session on the SN side RAT (that is, the sum of VrS1 of all DRBs of the PDU Session);
  • the PDU session identifier the RAN traffic of the PDU Session when the duplicate part is counted (that is, the sum of V2 of all DRBs of the PDU Session);
  • the PDU session identifier the RAN traffic of the PDU Session on the SN side RAT when the duplicate part is counted (that is, the sum of VrS2 of all DRBs of the PDU Session);
  • PDU session identifier RAN traffic of the PDU Session repeating part (that is, the sum of Vd of all DRBs of the PDU Session);
  • the QoS flow identifier and the repeated part are not counted as the RAN traffic of the QoS Flow (that is, the V1 of the DRB corresponding to the QoS Flow, when the QoS Flow and the DRB are one-to-one);
  • the QoS flow identifier and the repeated part are not counted as the RAN traffic of the QoS Flow on the MN side RAT (ie, the VrM1 of the DRB corresponding to the QoS Flow, when the QoS Flow and the DRB are one-to-one);
  • the QoS flow identifier and the repeated part are not counted as the RAN traffic of the QoS Flow on the SN side RAT (that is, the VrS1 of the DRB corresponding to the QoS Flow, when the QoS Flow and the DRB are one-to-one);
  • the QoS Flow identifier the RAN traffic of the QoS Flow when the repeated part is counted (that is, the V2 of the DRB corresponding to the QoS Flow, when the QoS Flow and the DRB are one-to-one);
  • the QoS Flow identifier the RAN traffic of the QoS Flow on the MN side RAT when the repeated part is counted (that is, the VrM2 of the DRB corresponding to the QoS Flow, when the QoS Flow and the DRB are one-to-one);
  • the QoS Flow identifier the RAN traffic of the QoS Flow on the SN side RAT when the QoS Flow is calculated (that is, the VrS2 of the DRB corresponding to the QoS Flow, when the QoS Flow and the DRB are one-to-one);
  • QoS Flow identifier RAN traffic of the QoS Flow repeating part (ie, Vd of the DRB corresponding to the QoS Flow, when QoS Flow and DRB are one-to-one);
  • the QoS flow identifier list and the repeated part are not counted as the RAN traffic of the QoS Flow group (that is, the V1 of the DRB corresponding to the QoS Flow group, when the QoS Flow and the DRB are many-to-one);
  • the QoS flow identifier list and the repeated part are not counted as the RAN traffic of the QoS Flow group in the MN side RAT (ie, the VrM1 of the DRB corresponding to the QoS Flow group, when the QoS Flow and the DRB are many-to-one);
  • the QoS flow identifier list and the repeated part are not counted as the RAN traffic of the QoS Flow group on the SN side RAT (that is, the VrS1 of the DRB corresponding to the QoS Flow group, when the QoS Flow and the DRB are many-to-one);
  • the QoS flow identifier list the RAN traffic of the QoS Flow group when the repeated part is counted (that is, the V2 of the DRB corresponding to the QoS Flow group, when the QoS Flow and the DRB are many-to-one);
  • the QoS Flow identifier list the RAN traffic of the QoS Flow group in the MN side RAT when the repeated part is counted (that is, the VrM2 of the DRB corresponding to the QoS Flow group, when the QoS Flow and the DRB are many-to-one);
  • the QoS Flow identifier list the RAN traffic of the QoS Flow group on the SN side RAT when the duplicate part is counted (that is, the VrS2 of the DRB corresponding to the QoS Flow group, when the QoS Flow and the DRB are many-to-one);
  • QoS Flow identification list RAN traffic of the QoS Flow group repeating part (ie, Vd of the DRB corresponding to the QoS Flow group, when QoS Flow and DRB are many-to-one).
  • the RAN traffic report may be carried by an existing interface message between the CN and the base station such as S1 or NG, or may be carried by a new interface message between the CN and the base station.
  • the embodiment provides a radio access network traffic reporting method, including: step 101, step 102, and step 103.
  • the base station acquires the traffic information of the data radio bearer, where the traffic information of the data radio bearer includes: the PDCP PDU generated by the PDCP or the traffic of the PDCP SDU (Service Data Unit), and the PDCP is sent to the RLC. Traffic of PDCP PDUs or PDCP SDUs.
  • the base station In step 102, the base station generates a radio access network traffic report according to the traffic information of the data radio bearer, where the radio access network traffic report includes at least one of the following: the RAN traffic of the granular unit is not included in the repeated part The RAN traffic of the granular unit when the repeated part is counted; the granular unit repeats the RAN traffic of the part.
  • step 103 the base station sends the radio access network traffic report to the core network.
  • the granularity unit refers to an object for performing traffic statistics, such as a UE (at this time, performing traffic statistics for the UE), and an E-UTRAN Radio Access Bearer (E-UTRAN Radio Access Bearer).
  • -RAB E-UTRAN Radio Access Bearer
  • traffic statistics are performed for E-RAB
  • PDU Session current traffic statistics for PDU Session
  • QoS Flow current traffic statistics for QoS Flow
  • QoS Flow group for this group QoS Flow for traffic statistics).
  • the information in the radio access network traffic report is: the identity information of the UE, the RAN traffic of the UE when the repeated part is not counted, and the RAN traffic of the UE when the repeated part is included; the repeated part of the UE RAN traffic.
  • the information in the radio access network traffic report is: the E-RAB identification information, and the RAN traffic of the E-RAB when the repeated part is not included, and the repeated part is included in the calculation.
  • RAN traffic of the E-RAB; the E-RAB repeats the RAN traffic.
  • the granularity is the corresponding granularity unit information.
  • the traffic of the PDCP SDU is the PDCP PDU traffic minus the PDCP header overhead.
  • the obtaining the traffic of the PDCP PDU or the PDCP SDU that is sent by the PDCP to the radio link control includes: when the PDCP and the RLC corresponding to the DRB are not in the same node (for example, when the dual connection and the CU DU are separated), When the traffic of the PDCP PDU or the PDCP SDU that is sent by the PDCP to the radio link control is obtained, the traffic of the lost data packet on the interface between the node where the PDCP is located and the node where the radio link is controlled is removed.
  • the obtaining the traffic of the PDCP PDU or the PDCP SDU that is sent by the PDCP to the radio link control includes: removing the PDCP PDU that is sent by the PDCP to the radio link control PDCP PDU or the PDCP SDU, Determine the traffic of dropped packets.
  • the base station at this time includes the MN and the SN.
  • the MN and SN may be the same RAT, or different RATs.
  • the MN receives the first configuration information sent by the CN or the OAM, where the first configuration information includes at least one of the following: an indication of whether the repeated part of the transmission transmission is included in the radio access network traffic report. And copy the radio access technology information and the granularity unit information that the traffic is calculated during transmission.
  • the MN sends the second configuration information to the SN, where the second configuration information includes at least one of the following: whether the repeated part of the replication transmission is included in the indication of the radio access network traffic report, and the traffic is included in the replication transmission.
  • Wireless access technology information and granular unit information.
  • the first configuration information may be carried by an existing interface message between the CN and the base station such as S1 or NG, or may be carried by a new interface message between the CN and the base station.
  • the second configuration information may be carried by an existing inter-base station interface message such as X2 or Xn, or may be carried by a new inter-base station interface message.
  • the first configuration information includes at least one of the following: a UE identifier, an E-UTRAN Radio Access Bearer (E-RAB) identifier (eg, 4G CN) Time), PDU Session identifier (if 5G CN), QoS Flow identifier (if 5G CN), whether the duplicate part of the replication transmission is included in the radio access network (RAN) traffic report indication, and The Radio Access Technology (RAT) information that is included in the traffic at the time of transmission (required when the RATs of the MN and the SN are different and the repeated part is not counted).
  • the configuration granularity of the CN may be UE, E-RAB (for example, when 4G CN), PDU Session (for 5G CN), and QoS Flow level (for 5G CN).
  • the second configuration information includes at least one of the following: a UE identifier, an E-RAB identifier (for example, when the 4G CN is used), a PDU Session identifier (for a 5G CN), and a QoS Flow identifier (if 5G CN), whether the repeated part of the duplicate transmission is included in the RAN traffic report indication, and the RAT information calculated by the traffic during the replication transmission (required when the RATs of the MN and the SN are different and the repeated part is not included).
  • a UE identifier for example, when the 4G CN is used
  • a PDU Session identifier for a 5G CN
  • QoS Flow identifier if 5G CN
  • the acquiring, by the base station, the traffic information of each data radio bearer includes:
  • the primary base station acquires the information of each PDCP on the primary base station side, where the information of each PDCP on the primary base station side includes: the traffic of the PDCP PDU or the PDCP SDU generated by the PDCP, and the PDCP sent by the PDCP to the primary base station side RLC.
  • the secondary base station acquires the information of each PDCP on the secondary base station side, where the information of each PDCP on the primary base station side includes: the traffic of the PDCP PDU or the PDCP SDU generated by the PDCP, and the PDCP sent by the PDCP to the primary base station side RLC.
  • Generating, by the base station, the radio access network traffic report according to the traffic information of the data radio bearer includes:
  • the secondary base station generates a first radio access network traffic report, and sends the first radio access network traffic report to the primary base station, where the first radio access network traffic report includes at least one of the following at the secondary base station side : when the RAN traffic of the granularity unit (the secondary base station side) is not included in the repetition part, and the traffic of the granularity unit in the primary base station side RAT when the repeated part is not counted, and the repeated part is not included, the granularity unit is on the secondary base station side RAT.
  • the RAN traffic of the granularity unit when the repeated part is counted the traffic of the granularity unit on the primary base station side RAT when the repeated part is counted, the traffic of the granularity unit on the secondary base station side RAT when the repeated part is counted, and the granularity
  • the RAN traffic of the unit repeating part
  • the primary base station generates a second radio access network traffic report, where the second radio access network traffic report includes the identifier information of the granular unit, and further includes at least one of the following:
  • the granularity unit is at least one of the primary base station side and the secondary base station side; if the granularity is UE, the primary base station side and the secondary base station side; At least one of the primary base station side and the secondary base station side, when the dual connection is performed, one PDU session may be on the primary base station side or the secondary base station side, or may be split on the primary base station side and the secondary base station side; if the granularity is QoS Flow, In the E-RAB, when the RAN traffic on the primary base station side or the secondary base station side is not counted, the traffic of the granularity unit on the primary base station side RAT is not counted, and the granularity unit is on the secondary base station side.
  • the traffic of the RAT The traffic of the RAT, the RAN traffic of the granularity unit when the repeated part is counted, the traffic of the granularity unit on the primary base station side RAT when the repeated part is counted, the traffic of the granularity unit on the secondary base station side RAT when the repeated part is counted, and the The RAN traffic of the granular part repeating part;
  • the sending, by the base station, the radio access network traffic report to the core network includes: sending, by the primary base station, the second radio access network traffic report to the core network.
  • the secondary base station generates a first radio access network traffic report according to the traffic information of the data radio bearer and the second configuration information; and the primary base station according to the data radio bearer traffic information and the first configuration information Generating a second radio access network traffic report.
  • the SN sends a RAN traffic report to the MN, where the RAN traffic report includes at least one of the following DRBs of the PDCP on the SN side: the RAN traffic V1 when the repeated part is not counted, and the RAN traffic V2 when the repeated part is counted, repeating Part of the RAN traffic Vd, the repeated part is included in the SN side RAT traffic VrS2, the repeated part is included in the MN side RAT traffic VrM2, the repeated part is not included in the SN side RAT traffic VrS1, and the repeated part is not included in the MN
  • the flow rate of the side RAT is VrM1.
  • the RAN traffic report may be carried by an existing inter-base station interface message such as X2 or Xn, or may be carried by a new inter-base station interface message.
  • the MN performs statistics on the DRBs of the PDCPs on the MN side for each PDCP: the traffic of the PDCP PDUs generated by the PDCP (set to V), and the traffic of the PDCP PDUs sent by the PDCP to the RLs of the MN side (set to Vm, which can be 0), under PDCP
  • the traffic sent to the PDCP PDU of the RLC on the SN side (set to Vs, which can be 0), then:
  • the MN sends a RAN traffic report to the CN, the RAN traffic report including at least one of the following:
  • the RRC traffic of the UE when the UE identifier and the repeated part are not counted that is, the sum of V1 of all the MN sides of the UE and the DRB of the SN side);
  • the RRC traffic of the UE on the MN side RAT ie, the sum of all the MN sides of the UE and the VrM1 of the DRBs on the SN side of the UE) when the UE identity and the repeated part are not counted;
  • the RAN traffic of the UE on the SN side RAT ie, the sum of the VrS1s of all the MN sides of the UE and the DRBs of the SN side) of the UE when the UE identifier and the repeated part are not counted;
  • the RRC traffic of the UE when the UE identifier and the repeated part are counted (that is, the sum of V2 of all the MN sides of the UE and the DRB of the SN side);
  • the RAN traffic of the UE on the MN side RAT (ie, the sum of all the MN sides of the UE and the VrM2 of the DRBs on the SN side) of the UE when the UE is identified and repeated;
  • the RAN traffic of the UE on the SN side RAT ie, the sum of all the MN sides of the UE and the VrS2 of the DRBs on the SN side of the UE) when the UE identifier and the repeated part are counted;
  • the UE identifier the RAN traffic of the repeated part of the UE (that is, the sum of the Vd of all the MN sides of the UE and the DRB of the SN side);
  • E-RAB identifier the RAN traffic of the E-RAB when the repeated part is not counted (that is, the V1 of the DRB corresponding to the MN side or the SN side corresponding to the E-RAB);
  • E-RAB identifier the RAN traffic of the E-RAB on the MN side RAT when the repeated part is not counted (that is, the VrM1 of the DRB corresponding to the MN side or the SN side corresponding to the E-RAB);
  • E-RAB identifier the RAN traffic of the E-RAB on the SN side RAT when the repeated part is not counted (that is, the VrS1 of the DRB corresponding to the MN side or the SN side corresponding to the E-RAB);
  • E-RAB identifier the RAN traffic of the E-RAB when the repeated part is counted (that is, the V2 of the DRB corresponding to the MN side or the SN side corresponding to the E-RAB);
  • E-RAB identifier the RAN traffic of the E-RAB on the MN side RAT when the repeated part is counted (that is, the VrM2 of the DRB corresponding to the MN side or the SN side corresponding to the E-RAB);
  • E-RAB identifier the RAN traffic of the E-RAB on the SN side RAT when the repeated part is counted (that is, the VrS2 of the DRB corresponding to the MN side or the SN side corresponding to the E-RAB);
  • the E-RAB identifies the RAN traffic of the E-RAB repeating part (ie, the Vd of the MN side corresponding to the E-RAB or the DRB of the SN side);
  • the PDU session identifier and the repeated part are not counted as the RAN traffic of the PDU Session (that is, the sum of V1s of the DRBs of at least one of the MN side and the SN side of the PDU Session);
  • the PDU session identifier and the repeated part are not counted as the RAN traffic of the PDU Session on the MN side RAT (ie, the sum of the VrM1s of the DRBs of at least one of the MN side and the SN side of the PDU Session);
  • the PDU session identifier and the repeated part are not counted as the RAN traffic of the PDU Session on the SN side RAT (ie, the sum of VrS1 of the DRB of at least one of the MN side and the SN side of the PDU Session);
  • the RAN traffic of the PDU Session when the repeated part is counted that is, the sum of V2 of the DRB of at least one of the MN side and the SN side of the PDU Session
  • PDU session identifier the RAN session of the PDU Session at the MN side RAT traffic (ie, the sum of VrM2 of the DRB of at least one of the MN side and the SN side of the PDU Session);
  • PDU session identifier the RAN session of the PDU Session at the SN side RAT traffic (ie, the sum of VrS2 of the DRB of at least one of the MN side and the SN side of the PDU Session);
  • PDU Session identifier RAN traffic of the PDU Session repeating part (ie, the sum of Vd of the DRB of at least one of the MN side and the SN side of the PDU Session);
  • the QoS flow identifier and the repeated part are not included in the RAN traffic of the QoS Flow (that is, the V1 of the MN side corresponding to the QoS Flow or the DRB of the SN side when the QoS Flow and the DRB are one-to-one);
  • the QoS flow identifier and the repeated part are not counted as the RAN traffic of the QoS Flow on the MN side RAT (that is, the VrM1 of the MN side corresponding to the QoS Flow or the DRB of the SN side when the QoS Flow and the DRB are one-to-one);
  • the QoS flow identifier and the repeated part are not counted as the RAN traffic of the QoS Flow on the SN side RAT (that is, the VrS1 of the MN side corresponding to the QoS Flow or the DRB of the SN side when the QoS Flow and the DRB are one-to-one);
  • the QoS Flow identifier the RAN traffic of the QoS Flow when the repeated part is included (that is, the V2 of the MN side corresponding to the QoS Flow or the DRB of the SN side, when the QoS Flow and the DRB are one-to-one);
  • the QoS Flow identifier the RAN traffic of the QoS Flow on the MN side RAT when the QoS Flow is calculated (that is, the VrM2 of the MN side corresponding to the QoS Flow or the DRB of the SN side when the QoS Flow and the DRB are one-to-one);
  • the QoS Flow identifier the RAN traffic of the QoS Flow on the SN side RAT when the QoS Flow is calculated (that is, the VrS2 of the MN side corresponding to the QoS Flow or the DRB of the SN side when the QoS Flow and the DRB are one-to-one);
  • QoS Flow identifier RAN traffic of the QoS Flow repeating part (ie, Vd of the MN side corresponding to the QoS Flow or the DRB of the SN side when the QoS Flow and the DRB are one-to-one);
  • the QoS flow identifier list and the repeated part are not counted as the RAN traffic of the QoS Flow group (that is, the QoS Flow group indicated by the QoS Flow identifier list) (that is, the V1 of the DRB corresponding to the MN side or the SN side corresponding to the QoS Flow group, When QoS Flow and DRB are many-to-one;
  • the QoS Flow identifier list and the repeated part are not counted as the RAN traffic of the QoS Flow group on the MN side RAT (that is, the MN side corresponding to the QoS Flow group or the RN side of the DRB VrM1, when the QoS Flow and the DRB are multiple pairs Temporarily)
  • the QoS flow identifier list and the repeated part are not counted as the RAN traffic of the QoS Flow group on the SN side RAT (that is, the VrS1 of the MN side or the RN side DRB corresponding to the QoS Flow group, when the QoS Flow and the DRB are multiple pairs Temporarily)
  • the QoS Flow identifier list the RAN traffic of the QoS Flow group when the repeated part is counted (that is, the V2 of the MN side corresponding to the QoS Flow group or the DRB of the SN side when the QoS Flow and the DRB are many-to-one);
  • the QoS Flow identifier list the RAN traffic of the QoS Flow group on the MN side RAT when the QoS Flow group is counted (that is, the VrM2 of the MN side corresponding to the QoS Flow group or the DRB of the SN side, when the QoS Flow and the DRB are many-to-one );
  • QoS Flow identifier list VR traffic of the QoS Flow group at the SN side RAT when the QoS Flow group is counted (ie, the MN side corresponding to the QoS Flow group or the VBS2 of the DRB of the SN side when the QoS Flow and the DRB are many-to-one) );
  • QoS Flow identification list RAN traffic of the QoS Flow group repeating part (that is, the Vd of the MN side corresponding to the QoS Flow group or the DRB of the SN side when the QoS Flow and the DRB are many-to-one).
  • the RAN traffic report includes at least one of the following:
  • the RRC traffic of the UE when the UE identifier and the repeated part are not counted that is, the sum of V1 of all the MN sides of the UE and the DRB of the SN side);
  • the RRC traffic of the UE when the UE identifier and the repeated part are counted (that is, the sum of V2 of all the MN sides of the UE and the DRB of the SN side);
  • the UE identifier the RAN traffic of the repeated part of the UE (that is, the sum of the Vd of all the MN sides of the UE and the DRB of the SN side);
  • E-RAB identifier the RAN traffic of the E-RAB when the repeated part is not counted (that is, the V1 of the DRB corresponding to the MN side or the SN side corresponding to the E-RAB);
  • E-RAB identifier the RAN traffic of the E-RAB when the repeated part is counted (that is, the V2 of the DRB corresponding to the MN side or the SN side corresponding to the E-RAB);
  • the E-RAB identifies the RAN traffic of the E-RAB repeating part (ie, the Vd of the MN side corresponding to the E-RAB or the DRB of the SN side);
  • the PDU session identifier and the repeated part are not counted as the RAN traffic of the PDU Session (that is, the sum of V1s of the DRBs of at least one of the MN side and the SN side of the PDU Session);
  • the RAN traffic of the PDU Session when the repeated part is counted that is, the sum of V2 of the DRB of at least one of the MN side and the SN side of the PDU Session
  • PDU Session identifier RAN traffic of the PDU Session repeating part (ie, the sum of Vd of the DRB of at least one of the MN side and the SN side of the PDU Session);
  • the QoS flow identifier and the repeated part are not included in the RAN traffic of the QoS Flow (that is, the V1 of the MN side corresponding to the QoS Flow or the DRB of the SN side when the QoS Flow and the DRB are one-to-one);
  • the QoS Flow identifier the RAN traffic of the QoS Flow when the repeated part is included (that is, the V2 of the MN side corresponding to the QoS Flow or the DRB of the SN side, when the QoS Flow and the DRB are one-to-one);
  • QoS Flow identifier RAN traffic of the QoS Flow repetition part (ie, Vd of the MN side corresponding to the QoS Flow or the DRB of the SN side when the QoS Flow and the DRB are one-to-one);
  • the QoS flow identifier list and the repeated part are not counted as the RAN traffic of the QoS Flow group (that is, the QoS Flow group indicated by the QoS Flow identifier list) (that is, the V1 of the DRB corresponding to the MN side or the SN side corresponding to the QoS Flow group, When QoS Flow and DRB are many-to-one;
  • the QoS Flow identifier list the RAN traffic of the QoS Flow group when the repeated part is counted (that is, the V2 of the MN side corresponding to the QoS Flow group or the DRB of the SN side when the QoS Flow and the DRB are many-to-one);
  • QoS Flow identification list RAN traffic of the QoS Flow group repeating part (that is, the Vd of the MN side corresponding to the QoS Flow group or the DRB of the SN side when the QoS Flow and the DRB are many-to-one).
  • the secondary base station when the secondary base station includes the secondary base station centralized unit control plane and the secondary base station centralized unit user plane:
  • the information that the secondary base station acquires each PDCP on the secondary base station side includes:
  • the secondary base station generates a first radio access network traffic report, and the sending the first radio access network traffic report to the primary base station includes:
  • the secondary base station central unit generates a first radio access network traffic report, and sends the first radio access network traffic report to the secondary base station centralized unit control plane; the secondary base station centralized unit control plane sends the The first radio access network traffic is reported to the primary base station.
  • the configuration information is sent by the CN or OAM to the MN, and the MN sends the base station centralized unit control plane, and the secondary base station centralized unit control plane Then, the configuration information is sent to the user plane of the central unit of the secondary base station.
  • the RAN traffic report may be carried by an existing interface message between the CN and the base station such as S1 or NG, or may be carried by a new interface message between the CN and the base station.
  • the base station further receives configuration information sent by the OAM or the CN, where the configuration information includes at least one of the following: whether the repeated part of the duplicate transmission is included in the indication of the radio access network traffic report, and the traffic during the replication transmission.
  • the configuration information further includes at least one of the following: a UE identifier, an E-RAB identifier, a PDU Session identifier, and a QoS Flow identifier.
  • the base station performs statistics for each DRB: the traffic of the PDCP PDU generated by the PDCP (set to V), and the sum of the traffic of the PDCP PDUs sent by the PDCP to all the RLCs (set to Vr), and the repeated part is not
  • the RAN traffic report includes at least one of the following:
  • the RRC traffic of the UE when the UE identifier and the repeated part are not counted that is, the sum of V1s of all DRBs of the UE
  • the RAN traffic of the UE when the UE identifier and the repeated part are counted (that is, the sum of V2s of all DRBs of the UE);
  • the UE identifier, the RAN traffic of the repeated part of the UE (that is, the sum of the Vds of all DRBs of the UE);
  • E-RAB identifier the RAN traffic of the E-RAB when the repeated part is not counted (that is, the E-RAB corresponds to the V1 of the DRB);
  • E-RAB identifier the RAN traffic of the E-RAB when the repeated part is counted (that is, the E-RAB corresponds to the V2 of the DRB);
  • E-RAB identifier the RAN traffic of the E-RAB repeating part (ie, the E-RAB corresponds to the Vd of the DRB);
  • the RAN session identifier and the repeated part are not included in the RAN traffic of the PDU Session (that is, the sum of V1s of all DRBs of the PDU Session);
  • the PDU session identifier the RAN traffic of the PDU Session when the duplicate part is counted (that is, the sum of V2 of all DRBs of the PDU Session);
  • PDU session identifier RAN traffic of the PDU Session repeating part (that is, the sum of Vd of all DRBs of the PDU Session);
  • the QoS flow identifier and the repeated part are not counted as the RAN traffic of the QoS Flow (that is, the V1 of the DRB corresponding to the QoS Flow, when the QoS Flow and the DRB are one-to-one);
  • the QoS Flow identifier the RAN traffic of the QoS Flow when the repeated part is counted (that is, the V2 of the DRB corresponding to the QoS Flow, when the QoS Flow and the DRB are one-to-one);
  • QoS Flow identifier RAN traffic of the QoS Flow repeating part (ie, Vd of the DRB corresponding to the QoS Flow, when QoS Flow and DRB are one-to-one);
  • the QoS flow identifier list and the repeated part are not counted as the RAN traffic of the QoS Flow group (that is, the V1 of the DRB corresponding to the QoS Flow group, when the QoS Flow and the DRB are many-to-one);
  • the QoS flow identifier list the RAN traffic of the QoS Flow group when the repeated part is counted (that is, the V2 of the DRB corresponding to the QoS Flow group, when the QoS Flow and the DRB are many-to-one);
  • QoS Flow identification list RAN traffic of the QoS Flow group repeating part (ie, Vd of the DRB corresponding to the QoS Flow group, when QoS Flow and DRB are many-to-one).
  • the RAN traffic report may be generated according to the indication in the configuration information. For example, when the configuration information carries the indication that the repeated part of the replication transmission is not included in the radio access network traffic report, and the granularity unit is the UE, the RAN traffic report includes the following information: the UE identifier, and the repeated part is not included in the UE. RAN traffic (ie the sum of V1 of all DRBs of the UE).
  • the base station includes a base station centralized unit control plane and a base station centralized unit user plane.
  • the obtaining, by the base station, the traffic information of the data radio bearer includes: acquiring, by the user unit of the base station, the following information of each PDCP: the traffic of the PDCP PDU or the PDCP SDU generated by the PDCP, and the PDCP PDU sent by the PDCP to the radio link control or The traffic of the PDCP SDU.
  • the base station centralized unit user plane Generating, by the base station, the radio access network traffic report according to the traffic information of the data radio bearer, the base station centralized unit user plane generates a radio access network traffic report, and sending the radio access network traffic report to the base station set Unit control surface.
  • the configuration information is sent by the CN or the OAM to the base station centralized unit control plane, and the base station centralized unit control plane is further sent to the base station centralized unit user plane.
  • At least one embodiment of the present application provides a report implementation scheme for radio access network traffic during replication transmission, which meets the requirements of the operator.
  • the dual connectivity scenario includes: Step 201 to Step 206.
  • the network management operation and maintenance sends configuration information to the MN, where the configuration information includes at least one of the following: an indication of whether the duplicate part is included in the RAN traffic report when copying the transmission (this example assumes Not counting), copying the RAT information that the traffic is calculated at the time of transmission (when the RATs of the MN and the SN are different and the repeated part is not included, this example assumes that the MN is a 4G RAT, the SN is a 5G RAT, and the traffic is copied during transmission. The RAT counted is 5G).
  • the OAM configuration granularity is a base station.
  • the OAM sends configuration information to the SN, where the configuration information includes at least one of the following: an indication of whether the duplicate part is included in the RAN traffic report when the transmission is duplicated (this example assumes not to be counted), and the traffic is copied during transmission.
  • RAT information to be counted when the RATs of the MN and the SN are different and the repeated part is not included, this example assumes that the MN is a 4G RAT, the SN is a 5G RAT, and the RAT counted by the traffic during the replication transmission is 5G).
  • the OAM configuration granularity is a base station.
  • the SN performs statistics on the DRB of the SN side for each PDCP: the traffic of the PDCP PDU generated by the PDCP (set to V), and the traffic of the PDCP PDU that is sent by the PDCP to the RLC of the SN side (set to Vs, which may be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RL on the MN side (set to Vm, which can be 0)
  • the SN sends a RAN traffic report to the MN, the RAN traffic report including at least one of the following DRBs of each PDCP on the SN side: V1, VrS, and VrM.
  • the MN performs statistics on the DRB of the MN side for each PDCP: the traffic of the PDCP PDU generated by the PDCP (set to V), and the traffic of the PDCP PDU that the PDCP sends to the RLC of the MN side (set to Vm, which may be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RLC on the SN side (set to Vs, which can be 0)
  • the MN sends a RAN traffic report to the CN, the RAN traffic report including at least one of the following: each DRB (PDCP on the MN side and PDCP on at least one of the SN sides):
  • the RAN traffic report includes a list including traffic information of E-RABs corresponding to all DRBs of the UE (PDCP on the MN side and PDCP on the SN side), and one of the lists indicates one of the E-
  • the traffic information of the RAB includes: an E-RAB identifier, a VrS, and a VrM.
  • This embodiment is implemented in a dual connectivity scenario. As shown in FIG. 3, the method includes: Step 301 to Step 306.
  • the OAM sends configuration information to the MN, where the configuration information includes at least one of the following: an indication of whether the duplicate part is included in the RAN traffic report when replicating the transmission (in this example, is assumed), wherein the example assumes that the MN For the 4G RAT, the SN is a 5G RAT.
  • the OAM configuration granularity is a base station.
  • the OAM sends configuration information to the SN, where the configuration information includes at least one of the following: an indication of whether the duplicate part is included in the RAN traffic report when replicating the transmission (this example assumes to be included) (this example assumes that the MN is 4G) RAT, SN is 5G RAT).
  • the OAM configuration granularity is a base station.
  • the SN performs statistics on the DRBs of the PDs on the SN side for each PDCP: the traffic of the PDCP PDUs generated by the PDCP (set to V), and the traffic of the PDCP PDUs sent by the PDCP to the RLCs of the SN side (set to Vs, which may be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RL on the MN side (set to Vm, which can be 0)
  • the SN sends a RAN traffic report to the MN, the RAN traffic report including at least one of the following DRBs of each PDCP on the SN side: V2, VrS, and VrM.
  • the MN performs statistics on the DRB of the MN side for each PDCP: the traffic of the PDCP PDU generated by the PDCP (set to V), and the traffic of the PDCP PDU that is sent by the PDCP to the RLC of the MN side (set to Vm, which may be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RLC on the SN side (set to Vs, which can be 0)
  • the MN sends a RAN traffic report to the CN, where the RAN traffic report includes at least one of each of the DRBs (the PDCP is on the MN side and the PDCP is in at least one of the SN sides): one-to-one correspondence with the DRB
  • the RAN traffic report includes at least one of each of the DRBs (the PDCP is on the MN side and the PDCP is in at least one of the SN sides): one-to-one correspondence with the DRB
  • the E-RAB logo, V2, VrS, and VrM The E-RAB logo, V2, VrS, and VrM.
  • the traffic statistics may also be performed for the PDCP SDU, that is, the overhead of the PDCP header is reduced when the traffic statistics are collected.
  • the dual connectivity scenario includes: Step 401 to Step 406.
  • step 401 the CN sends configuration information to the MN.
  • the configuration information includes at least one of the following: a UE identifier, an E-RAB identifier, an indication of whether a duplicate portion is included in the RAN traffic report during replication transmission (this example is assumed not to be included), and the traffic is included in the replication transmission.
  • RAT information when the RATs of the MN and the SN are different and the repeated part is not included, this example assumes that the MN is a 4G RAT, the SN is a 5G RAT, and the RAT counted by the traffic during the replication transmission is 5G).
  • the CN configuration granularity is UE, E-RAB (this example assumes that the configuration granularity is E-RAB, and all E-RABs are configured not to count).
  • the MN sends configuration information to the SN, where the configuration includes at least one of the following: a UE identifier, an E-RAB identifier, and an indication of whether the duplicate portion is included in the RAN traffic report during replication transmission (this example assumes not to count ), copying the RAT information that is included in the repetition part of the transmission (when the RATs of the MN and the SN are different and the repeated part is not included, this example assumes that the MN is a 4G RAT, and the SN is a 5G RAT, and the repetition part of the replication transmission is counted)
  • the incoming RAT is 5G).
  • the SN performs statistics on the DRBs of the PDs on the SN side for each PDCP: the traffic of the PDCP PDUs generated by the PDCP (set to V), and the traffic of the PDCP PDUs sent by the PDCP to the RLCs of the SN side (set to Vs, which may be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RL on the MN side (set to Vm, which can be 0)
  • the SN sends a RAN traffic report to the MN, the RAN traffic report including at least one of the following DRBs of each PDCP on the SN side: V1, VrS, and VrM.
  • the MN performs statistics on the DRB of the MN side for each PDCP: the traffic of the PDCP PDU generated by the PDCP (set to V), and the traffic of the PDCP PDU that the PDCP sends to the RLC of the MN side (set to Vm, which may be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RLC on the SN side (set to Vs, which can be 0)
  • the MN sends a RAN traffic report to the CN, the RAN traffic report including at least one of the following per DRB (PDCP on the MN side and at least one of the PDCP on the SN side): one-to-one correspondence with the DRB
  • the E-RAB logo, V1, VrS, and VrM are examples of the E-RAB logo, V1, VrS, and VrM.
  • the traffic statistics may also be performed for the PDCP SDU, that is, the overhead of the PDCP header is reduced when the traffic statistics are collected.
  • the MN is a 4G RAT and the SN is a 5G RAT.
  • the method includes: Step 501 to Step 506.
  • the CN sends configuration information to the MN, where the configuration information includes at least one of the following: a UE identifier, an E-RAB identifier, and an indication of whether the duplicate portion is included in the RAN traffic report during replication transmission (this example is assumed to be included) ).
  • the CN configuration granularity is UE, E-RAB (in this example, the configuration granularity is E-RAB, and all E-RABs are configured to be counted).
  • the MN sends configuration information to the SN, where the configuration information includes at least one of the following: a UE identifier, an E-RAB identifier, and an indication of whether the duplicate portion is included in the RAN traffic report when replicating the transmission (this example assumes In).
  • the SN performs statistics on the DRBs of the PDs on the SN side for each PDCP: the traffic of the PDCP PDUs generated by the PDCP (set to V), and the traffic of the PDCP PDUs sent by the PDCP to the RLCs of the SN side (set to Vs, which may be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RL on the MN side (set to Vm, which can be 0)
  • the SN sends a RAN traffic report to the MN, the RAN traffic report including at least one of the following DRBs of each PDCP on the SN side: V2, VrS, and VrM.
  • the MN performs statistics on the DRB of the MN side for each PDCP: the traffic of the PDCP PDU generated by the PDCP (set to V), and the traffic of the PDCP PDU sent by the PDCP to the RL of the MN side (set to Vm, which may be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RLC on the SN side (set to Vs, which can be 0)
  • the MN sends a RAN traffic report to the CN, the RNA traffic report including at least one of the following DRBs (at least one of the PDCP on the MN side and the PDCP on the SN side): one with the DRB Corresponding E-RAB identification, V2, VrS, and VrM.
  • the traffic statistics may also be performed for the PDCP SDU, that is, the overhead of the PDCP header is reduced when the traffic statistics are collected.
  • the MN is a 4G RAT
  • the SN is a 5G RAT.
  • the method includes: Step 601 to Step 604.
  • the SN performs statistics on the DRBs of the PDs on the SN side for each PDCP: the traffic of the PDCP PDUs generated by the PDCP (set to V), and the traffic of the PDCP PDUs sent by the PDCP to the RLCs of the SN side (set to Vs, which may be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RL on the MN side (set to Vm, which can be 0)
  • the SN sends a RAN traffic report to the MN including at least one of the following DRBs of each PDCP on the SN side: V1, V2, Vd, Vs, and Vm.
  • the MN performs statistics on the DRB of the MN side for each PDCP: the traffic of the PDCP PDU generated by the PDCP (set to V), and the traffic of the PDCP PDU that is sent by the PDCP to the RLC of the MN side (set to Vm, which may be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RLC on the SN side (set to Vs, which can be 0)
  • the MN sends a RAN traffic report to the CN, the RAN traffic report including at least one of the following DRBs (at least one of the PDCP on the MN side and the PDCP on the SN side): one with the DRB Corresponding E-RAB identifiers, V1, V2, Vd, Vs, and Vm.
  • the RAN traffic report includes a list of traffic information of all DRBs of the UE (PDCP on the MN side and PDCP on the SN side), and one of the lists indicates that the traffic information of one DRB includes: E -RAB logo, Vd, Vs, and Vm.
  • the traffic statistics may also be performed on the PDCP SDU, that is, the overhead of the PDCP header is subtracted during traffic statistics.
  • the dual connectivity scenario includes: Step 701 to Step 706.
  • the CN sends configuration information to the MN, where the configuration information includes at least one of the following: a UE identifier, a PDU Session identifier, a QoS Flow identifier, and an indication of whether the duplicate portion is included in the RAN traffic report during replication transmission (this example assumes For the purpose of not accounting for, and copying the RAT information that is included in the traffic during transmission (when the RATs of the MN and the SN are different and the repeated part is not included, this example assumes that the MN is a 5G RAT and the SN is a 4G RAT. The RAT counted by the traffic is 5G).
  • the CN configuration granularity is UE, PDU Session, and QoS Flow (in this example, the configuration granularity is PDU Session).
  • the MN sends configuration information to the SN, where the configuration information includes at least one of the following: a UE identifier, a PDU Session identifier, a QoS Flow identifier, and an indication of whether the duplicate portion is included in the RAN traffic report during replication transmission (this example assumes For the purpose of not accounting for, and copying the RAT information that is included in the traffic during transmission (when the RATs of the MN and the SN are different and the repeated part is not included, this example assumes that the MN is a 5G RAT and the SN is a 4G RAT. The RAT counted by the traffic is 5G).
  • the SN performs statistics on the DRB of the SN side for each PDCP: the traffic of the PDCP PDU generated by the PDCP (set to V), and the traffic of the PDCP PDU that the PDCP sends to the RL side of the RLC (set to Vs, which may be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RL on the MN side (set to Vm, which can be 0)
  • the SN sends a RAN traffic report to the MN, where the RAN traffic report includes at least one of the following PDU Sessions of the SN side: a PDU Session identifier, a sum of V1s of all DRBs of the PDU Session, and all DRBs of the PDU Session The sum of the VrS and the sum of the VrMs of all DRBs of the PDU Session.
  • the MN performs statistics on the DRB of the MN side for each PDCP: the traffic of the PDCP PDU generated by the PDCP (set to V), and the traffic of the PDCP PDU that the PDCP sends to the RLC of the MN side (set to Vm, which may be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RLC on the SN side (set to Vs, which can be 0)
  • the MN sends a RAN traffic report to the CN, the RAN traffic report including at least one of the following PDU Sessions (on the MN side and at least one of the SN sides): PDU Session Identity, the PDU The sum of V1 of all DRBs of the session, the sum of VrSs of all DRBs of the PDU Session, and the sum of VrMs of all DRBs of the PDU Session.
  • PDU Session Identity the PDU The sum of V1 of all DRBs of the session, the sum of VrSs of all DRBs of the PDU Session, and the sum of VrMs of all DRBs of the PDU Session.
  • the RAN traffic report includes a list including traffic information of all PDU sessions (on the MN side and on the SN side) of a certain UE, and one of the lists indicates that the traffic information of one of the PDU sessions includes: PDU
  • the session identifier is the sum of the 4G traffic of the PDU Session, that is, the sum of the VrSs of all DRBs of the PDU Session, and the sum of the 5G traffic of the PDU Session, that is, the sum of the VrMs of all DRBs of the PDU Session.
  • the traffic statistics may also be performed for the PDCP SDU, that is, the overhead of the PDCP header is reduced when the traffic statistics are collected.
  • the dual connectivity scenario includes: Step 801 to Step 806.
  • the CN sends configuration information to the MN, where the configuration information includes at least one of the following: a UE identifier, a PDU Session identifier, a QoS Flow identifier, and an indication of whether the duplicate portion is included in the RAN traffic report during replication transmission (in this example). Assume that it is counted).
  • the CN configuration granularity is UE, PDU Session, and QoS Flow (in this example, the configuration granularity is PDU Session).
  • the MN sends configuration information to the SN, where the configuration information includes at least one of the following: a UE identifier, a PDU Session identifier, a QoS Flow identifier, and an indication of whether the duplicate portion is included in the RAN traffic report during replication transmission (in this example). Assume that it is counted) (This example assumes that the MN is a 5G RAT and the SN is a 4G RAT).
  • the SN performs statistics on the DRBs of the PDs on the SN side for each PDCP: the traffic of the PDCP PDUs generated by the PDCP (set to V), and the traffic of the PDCP PDUs sent by the PDCP to the RLCs of the SN side (set to Vs, which may be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RL on the MN side (set to Vm, which can be 0)
  • the SN sends a RAN traffic report to the MN, where the RAN traffic report includes at least one of the following PDU Sessions of the SN side: a PDU Session identifier, a sum of V2s of all DRBs of the PDU Session, and all DRBs of the PDU Session The sum of the VrS and the sum of the VrMs of all DRBs of the PDU Session.
  • the MN performs statistics on the DRB of the MN side for each PDCP: the traffic of the PDCP PDU generated by the PDCP (set to V), and the traffic of the PDCP PDU that the PDCP sends to the RLC of the MN side (set to Vm, which may be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RLC on the SN side (set to Vs, which can be 0)
  • the MN sends a RAN traffic report to the CN, the RAN traffic report including at least one of the following PDU Session (at least one of the MN side and at the SN side): PDU Session Identity, the PDU The sum of V2 of all DRBs of the session, the sum of the VrSs of all DRBs of the PDU Session, and the sum of the VrMs of all DRBs of the PDU Session.
  • PDU Session at least one of the MN side and at the SN side
  • the RAN traffic report includes a list including traffic information of all PDU Sessions (on the MN side and on the SN side) of a certain UE, and an item of the list indicates that traffic information of one of the PDU sessions includes: PDU
  • the session identifier indicates that the 4G traffic of the PDU Session is the sum of the VrSs of all DRBs of the PDU Session when the repeated part is counted.
  • the 5G traffic of the PDU Session is the sum of the VrMs of all DRBs of the PDU Session.
  • the traffic statistics may also be performed for the PDCP SDU, that is, the overhead of the PDCP header is reduced when the traffic statistics are collected.
  • the MN is a 5G RAT
  • the SN is a 4G RAT.
  • the method includes: Step 901 to Step 904.
  • the SN performs statistics on the DRB of the SN side for each PDCP: the traffic of the PDCP PDU generated by the PDCP (set to V), and the traffic of the PDCP PDU that is sent by the PDCP to the RLC of the SN side (set to Vs, which may be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RL on the MN side (set to Vm, which can be 0)
  • the SN sends a RAN traffic report to the MN, the RAN traffic report including at least one of the following DRBs of each PDCP on the SN side: V1, V2, Vd, Vs, and Vm.
  • the MN performs statistics on the DRB of the MN side for each PDCP: the traffic of the PDCP PDU generated by the PDCP (set to V), and the traffic of the PDCP PDU that the PDCP sends to the RLC of the MN side (set to Vm, which may be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RLC on the SN side (set to Vs, which can be 0)
  • the MN sends a RAN traffic report to the CN, the RAN traffic report including at least one of the following:
  • the UE identifier the sum of V1 of all DRBs (on the MN side and the SN side) of the UE (the repeated part is not counted);
  • the UE identifier the sum of V2 of all DRBs (on the MN side and the SN side) of the UE (repeated part is included);
  • the UE identifies that the repeated part of the traffic of the UE is the sum of the Vds of all DRBs (on the MN side and the SN side) of the UE;
  • PDU Session identifier the sum of V1 of all DRBs (at least one of the MN side and the SN side) of the PDU Session (the repeated part is not counted);
  • PDU Session identifier the sum of V2 of all DRBs (at least one of the MN side and the SN side) of the PDU Session (repeated part is counted);
  • the PDU session identifier and the repeated traffic of the PDU Session are the sum of the Vds of all DRBs (at least one of the MN side and the SN side) of the PDU Session;
  • QoS Flow identifier list V1 of the DRB (on the MN side or the SN side) corresponding to the QoS Flow group (the repeated part is not counted, when QoS Flow and DRB are many-to-one);
  • QoS Flow identifier, V2 of the DRB (on the MN side or the SN side) corresponding to the QoS Flow (repeated part is counted when QoS Flow and DRB are one-to-one);
  • QoS Flow identifier list V2 of the DRB (on the MN side or the SN side) corresponding to the QoS Flow group (repeated part is counted when QoS Flow and DRB are many-to-one);
  • the QoS Flow identifier the repeated traffic of the QoS Flow, that is, the Vd of the DRB (on the MN side or the SN side) corresponding to the QoS Flow (when the QoS Flow and the DRB are one-to-one);
  • the QoS Flow identifier list and the repeated part traffic of the QoS Flow group are the Vd (on the MN side or the SN side) corresponding to the QoS Flow group (when the QoS Flow and the DRB are many-to-one).
  • the traffic statistics may also be performed on the PDCP SDU, that is, the overhead of the PDCP header is subtracted during traffic statistics.
  • This embodiment is implemented in a carrier aggregation scenario. As shown in FIG. 10, the method includes: step 1001, step 1002, and step 1003.
  • the OAM sends configuration information to the base station, where the configuration information includes at least one of the following: an indication of whether the repeated portion is included in the RAN traffic report and the granularity unit information when the transmission is replicated.
  • the granularity unit is a base station.
  • the base station performs statistics for each DRB: the traffic of the PDCP PDU generated by the PDCP (set to V), and the sum of the traffic of the PDCP PDUs sent by the PDCP to all the RLCs (set to Vr), and the repeated part is not counted.
  • the base station sends a RAN traffic report to the CN, where the RAN traffic report includes the following information of each DRB: an identifier of the E-RAB corresponding to the DRB, V1 (when the repeated part is not counted) Or the following information: the identifier of the E-RAB corresponding to the DRB one-to-one, V2 (when the repeated part is included). Vd may also be included in the RAN traffic report.
  • the traffic statistics may also be performed for the PDCP SDU, that is, the overhead of the PDCP header is reduced when the traffic statistics are collected.
  • This embodiment is implemented in a carrier aggregation scenario. As shown in FIG. 11, the method includes: step 1101, step 1102, and step 1103.
  • the CN sends configuration information to the base station, where the configuration information includes at least one of the following: a UE identifier, an E-RAB identifier, an indication of whether the duplicate portion is included in the RAN traffic report during replication transmission, and granularity unit information.
  • the configurable size of the CN is UE, E-RAB, and this example assumes that the granularity unit is E-RAB.
  • the base station performs statistics for each DRB: the traffic of the PDCP PDU generated by the PDCP (set to V), the sum of the traffic of the PDCP PDUs sent by the PDCP to all the RLCs (set to Vr), and the repetition part
  • the base station sends a RAN traffic report to the CN, where the RAN traffic report includes the following information of each DRB: an identifier of the E-RAB corresponding to the DRB, V1 (when configured as a duplicate part is not counted Time); or the following information: the identifier of the E-RAB corresponding to the DRB one-to-one, V2 (when configured as a duplicate part). Vd may also be included in the RAN traffic report.
  • the traffic statistics may also be performed for the PDCP SDU, that is, the overhead of the PDCP header is reduced when the traffic statistics are collected.
  • This embodiment is implemented in a carrier aggregation scenario. As shown in FIG. 12, the method includes: step 1201 and step 1202.
  • the base station performs statistics for each DRB: the traffic of the PDCP PDU generated by the PDCP (set to V), and the sum of the traffic of the PDCP PDUs sent by the PDCP to all the RLCs (set to Vr), and the repeated part is not counted.
  • the base station sends a RAN traffic report to the CN, where the RAN traffic report includes at least one of the following: an identifier of the E-RAB corresponding to the DRB, V1, V2, Vd.
  • the traffic statistics may also be performed for the PDCP SDU, that is, the overhead of the PDCP header is reduced when the traffic statistics are collected.
  • This embodiment is implemented in a carrier aggregation scenario. As shown in FIG. 13, the method includes: step 1301, step 1302, and step 1303.
  • the CN sends configuration information to the base station, where the configuration information includes at least one of the following: a UE identifier, a PDU Session identifier, a QoS Flow identifier, an indication of whether a duplicate portion is included in the RAN traffic report during replication transmission, and a granularity unit. information.
  • the CN configuration granularity is UE, PDU Session, and QoS Flow (this example assumes that the granularity unit is a PDU Session).
  • the base station performs statistics for each DRB: the traffic of the PDCP PDU generated by the PDCP (set to V), the sum of the traffic of the PDCP PDUs sent by the PDCP to all the RLCs (set to Vr), and the repetition part
  • the base station sends a RAN traffic report to the CN, where the RAN traffic report includes at least one of each of the PDU Sessions of the UE:
  • the traffic statistics may also be performed for the PDCP SDU, that is, the overhead of the PDCP header is reduced when the traffic statistics are collected.
  • This embodiment is implemented in a carrier aggregation scenario. As shown in FIG. 14, the method includes: step 1401 and step 1402.
  • the base station performs statistics for each DRB: the traffic of the PDCP PDU generated by the PDCP (set to V), and the sum of the traffic of the PDCP PDUs sent by the PDCP to all the RLCs (set to Vr), and the repeated part is not counted.
  • the base station sends a RAN traffic report to the CN, and the RAN traffic report includes at least one of the following:
  • the UE identifier the sum of V2 of all DRBs of the UE (when the repeated part is counted);
  • the UE identifies that the repeated part of the traffic of the UE is the sum of the Vds of all DRBs of the UE;
  • PDU Session ID the sum of V1 of all DRBs of the PDU Session (when the duplicate part is not counted);
  • PDU Session ID the sum of V2 of all DRBs of the PDU Session (when the duplicate part is counted);
  • the repeated traffic of the PDU Session is the sum of the Vds of all DRBs of the PDU Session;
  • QoS Flow identifier list V1 of the DRB corresponding to the QoS Flow group (the repeated part is not counted, when QoS Flow and DRB are many-to-one);
  • QoS Flow identifier V2 of the DRB corresponding to the QoS Flow (repeated part is counted, when QoS Flow and DRB are one-to-one);
  • QoS Flow identifier list V2 of the DRB corresponding to the QoS Flow group (repeated part is counted, when QoS Flow and DRB are many-to-one);
  • the QoS Flow identifier the repeated traffic of the QoS Flow, that is, the Vd of the DRB corresponding to the QoS Flow (when the QoS Flow and the DRB are one-to-one);
  • the QoS Flow identifier list and the repeated part traffic of the QoS Flow group are the Vd of the DRB corresponding to the QoS Flow group (when the QoS Flow and the DRB are many-to-one).
  • the traffic statistics may also be performed for the PDCP SDU, that is, the overhead of the PDCP header is reduced when the traffic statistics are collected.
  • This embodiment is implemented in a carrier aggregation scenario. As shown in FIG. 15, the method includes: Step 1501 to Step 1505.
  • the CN sends configuration information to the base station CU-CP (central unit control plane), and the configuration information includes at least one of the following: the UE identifier, the PDU Session identifier, the QoS Flow identifier, and whether the duplicate portion is included in the RAN traffic during the replication transmission.
  • Reported instructions as well as granular unit information.
  • the CN configuration granularity is UE, PDU Session, and QoS Flow (this example assumes that the granularity unit is a PDU Session).
  • the base station CU-CP sends configuration information to the base station CU-UP (central unit user plane), and the configuration information includes at least one of the following: UE identifier, PDU Session identifier, QoS Flow identifier, and whether the duplicate portion is duplicated during replication transmission. Indication of the RAN traffic report, and granularity unit information.
  • the CN configuration granularity is UE, PDU Session, and QoS Flow (this example assumes that the granularity unit is a PDU Session).
  • the base station CU-UP sends a RAN traffic report to the base station CU-CP, where the RAN traffic report includes at least one of each PDU Session of the UE:
  • the base station CU-CP sends a RAN traffic report to the CN, and the RAN traffic report includes at least one of each of the PDU Sessions of the UE:
  • the traffic statistics may also be performed for the PDCP SDU, that is, the overhead of the PDCP header is reduced when the traffic statistics are collected.
  • configuration information may also be sent by the OAM to the base station CU-CP.
  • the CN or OAM may also not send configuration information to the base station CU-CP.
  • the granularity unit may also be a UE, a QoS flow, or the like, and the implementation method is similar, and details are not described herein again.
  • the method includes: step 1601 to step 1608.
  • step 1601 the CN sends configuration information to the MN.
  • the configuration information includes at least one of the following: a UE identifier, an E-RAB identifier, an indication of whether a duplicate portion is included in the RAN traffic report during replication transmission (this example is assumed not to be included), and the traffic is included in the replication transmission.
  • RAT information when the RATs of the MN and the SN are different and the repeated part is not included, this example assumes that the MN is a 4G RAT, the SN is a 5G RAT, and the RAT counted by the traffic during the replication transmission is 5G).
  • the CN configuration granularity is UE, E-RAB (this example assumes that the configuration granularity is E-RAB, and all E-RABs are configured not to count).
  • the MN sends configuration information to the CU-CP (central unit control plane) of the SN, the configuration including at least one of the following: the UE identifier, the E-RAB identifier, and whether the duplicate portion is included in the RAN traffic report during replication transmission.
  • the indication (which is assumed not to be included in this example), and the RAT information counted in the duplicate part of the duplicate transmission (when the RATs of the MN and the SN are different and the repeated part is not included, this example assumes that the MN is a 4G RAT, SN For the 5G RAT, the RAT counted in the duplicate part of the replication transmission is 5G).
  • the CU-CP of the SN sends configuration information to the CU-UP (central unit user plane) of the SN, the configuration including at least one of the following: UE identifier, E-RAB identifier, and whether the duplicate portion is duplicated during replication transmission.
  • the indication of the incoming RAN traffic report (this example is assumed not to be included), and the RAT information counted in the duplicate part of the duplicate transmission (when the RATs of the MN and the SN are different and the repeated part is not included, this example assumes that the MN is 4G RAT, SN is 5G RAT, and the RAT counted in the duplicate part during replication transmission is 5G).
  • the CU-UP of the SN sends a RAN traffic report to the CU-CP of the SN, the RAN traffic report including at least one of the following DRBs of the PDCP on the SN side: V1, VrS, and VrM.
  • the CU-CP of the SN sends a RAN traffic report to the MN, the RAN traffic report including at least one of the following DRBs of each PDCP on the SN side: V1, VrS, and VrM.
  • the MN performs statistics on the DRB of the MN side for each PDCP: the traffic of the PDCP PDU generated by the PDCP (set to V), and the traffic of the PDCP PDU that the PDCP sends to the RLC of the MN side (set to Vm, which may be 0)
  • the traffic of the PDCP PDU sent by the PDCP to the RLC on the SN side (set to Vs, which can be 0)
  • the MN sends a RAN traffic report to the CN, the RAN traffic report including at least one of the following DRBs (at least one of the PDCP on the MN side and the PDCP on the SN side): one with the DRB Corresponding E-RAB identification, V1, VrS, and VrM.
  • the traffic statistics may also be performed for the PDCP SDU, that is, the overhead of the PDCP header is reduced when the traffic statistics are collected.
  • the configuration information may also be sent by the OAM to the MN.
  • the CN or OAM may also not send configuration information to the MN.
  • the granularity unit may also be other, such as UE, PDU Session, QoS Flow, QoS Flow group, and the like.
  • the method includes: step 1701 and step 1702.
  • the DRB corresponding node of the RLC sends a first interface data delivery status report to the node where the DRB corresponds to the PDCP, where the first interface data delivery status report includes information of the lost data packet on the first interface, when dual connectivity
  • the first interface is an X2 or Xn interface, and the first interface is an F1 interface when the CU DU is separated.
  • step 1702 the DRB corresponding to the PDCP node performs statistics on the DRB, and the traffic of the lost packet on the first interface is subtracted from the traffic of the PDCP PDU generated by the PDCP, and the PDCP PDU is sent to the RLC in the statistical PDCP. The traffic of the lost packet on the first interface is subtracted from the traffic.
  • the traffic statistics may also be performed for the PDCP SDU, that is, the overhead of the PDCP header is reduced when the traffic statistics are collected.
  • step 1801 the DRB corresponding to the PDCP node performs statistics on the DRB, and when the traffic of the PDCP PDU generated by the PDCP is counted, the traffic of the data packet that the PDCP has decided to discard is subtracted, and the traffic of the PDCP PDU that is sent to the RLC in the statistical PDCP is calculated. The traffic of the packet that PDCP has decided to discard is subtracted.
  • the traffic statistics may also be performed for the PDCP SDU, that is, the overhead of the PDCP header is reduced when the traffic statistics are collected.
  • the dual connectivity scenario and the carrier aggregation scenario are used as examples.
  • the present application is not limited thereto.
  • the traffic reporting method may also be used in other scenarios.
  • the repeated portion is 0.
  • an embodiment of the present application provides a radio access network traffic reporting apparatus 180, including a memory 1810 and a processor 1820.
  • the memory 1810 stores a program, and the program is read by the processor 1820.
  • the radio access network traffic report includes at least one of the following: the RAN traffic of the granularity unit when the repeated part is not counted, and the granularity when the repeated part is included The RAN traffic of the unit, and the RAN traffic of the repeating portion of the granular unit;
  • the program when read and executed by the processor 1820, further implements the radio access network traffic reporting method in any of the above embodiments.
  • An embodiment of the present application provides a computer readable storage medium storing one or more programs, the one or more programs being executable by one or more processors to implement the foregoing A radio access network traffic reporting method as described in an embodiment.
  • the computer readable storage medium includes: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk, and the like, and the program code can be stored. Medium.
  • An embodiment of the present application further provides a radio access network traffic reporting system, including a base station and a core network, where:
  • the base station is configured to acquire the traffic information of the data radio bearer, where the traffic information of the data radio bearer includes: the traffic of the PDCP PDU or the PDCP SDU generated by the PDCP, and the PDCP PDU or the PDCP SDU sent by the PDCP to the radio link control Generating a radio access network traffic report according to the traffic information of the data radio bearer, and transmitting the radio access network traffic report to the core network, where the radio access network traffic report includes at least one of the following: a repeating part Not counting the RAN traffic of the granularity unit, the RAN traffic of the granularity unit when the repeated part is included, and the RAN traffic of the repeated part of the granularity unit;
  • the core network is configured to receive the radio access network traffic report sent by the base station.
  • the core network is further configured to send configuration information to the base station, where the configuration information includes at least one of the following: an indication of whether a duplicate part is included in a radio access network traffic report during a replication transmission, and a granularity.
  • the unit information is configured to generate a radio access network traffic report according to the traffic information of the data radio bearer by: generating the radio access network according to the traffic information of the data radio bearer and the configuration information. Traffic report.
  • the base station includes a primary base station and a secondary base station
  • the secondary base station is configured to acquire the information of each PDCP on the secondary base station side, where the information of each PDCP on the secondary base station side includes: the traffic of the PDCP PDU or the PDCP SDU generated by the PDCP, and the PDCP is sent to the primary base station side wireless chain.
  • the primary base station is configured to acquire information of each PDCP on the primary base station side, where the information of each PDCP on the secondary base station side includes: the traffic of the PDCP PDU generated by the PDCP, and the PDCP is sent to the primary base station side for wireless link control.
  • the traffic of the PDCP PDU, the PDCP is sent to the traffic of the PDCP PDU controlled by the secondary base station side radio link; the second radio access network traffic report is generated, and the second radio access network traffic report is sent to the core network.
  • the second radio access network traffic report includes identification information of the granular unit, and further includes at least one of the following:
  • the granularity unit When the repeated part is not included in the radio access network traffic of the granularity unit, and the repeated part is not included, the granularity unit is not included in the traffic of the primary base station side radio access technology, and the repeated part is not included.
  • the traffic of the radio access technology of the base station side, the radio access network traffic of the granularity unit when the repeated part is counted, and the traffic of the radio access technology of the primary base station side when the repeated part is counted, and the repeated part is included
  • the granularity unit is in the traffic of the secondary base station side radio access technology, and the granularity unit repeating part of the radio access network traffic.
  • At least one embodiment of the present application provides a report implementation scheme for radio access network traffic during replication transmission, which meets the requirements of the operator.

Abstract

一种无线接入网流量报告方法、装置和系统，计算机可读存储介质，该无线接入网流量报告方法包括：基站获取数据无线承载的流量信息，其中所述数据无线承载的流量信息包括：分组数据会聚协议PDCP生成的分组数据会聚协议协议数据单元PDCP PDU或分组数据会聚协议服务数据单元PDCP SDU的流量、PDCP下发给无线链路控制的PDCP PDU或PDCP SDU的流量；基站生成无线接入网流量报告，所述无线接入网流量报告包括以下至少之一：重复部分不计入时粒度单元的无线接入网流量、重复部分计入时该粒度单元的无线接入网流量、该粒度单元重复部分的无线接入网流量；发送所述无线接入网流量报告给核心网。

Description

无线接入网流量报告方法以及装置和系统、存储介质
本申请要求在2018年03月16日提交中国专利局、申请号为201810219173.0的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术，例如涉及一种无线接入网流量报告(data volume report)方法以及装置和系统，计算机可读存储介质。
背景技术
第四代(4 Generation，4G)和第五代(5 Generation，5G)系统中，均支持载波聚合(Carrier Aggregation，CA)功能。CA下UE可以同时在多个分量载波(Component Carrier，CC)上收发数据。用户设备(User Equipment，UE)初始接入的CC为主分量载波(Primary Component Carrier，PCC)，其他的CC称为辅分量载波(Secondary Component Carrier，SCC)，SCC是UE进入连接态后由基站配置的。PCC对应的服务小区(Serving Cell)称为主小区(Primary Cell，PCell)，SCC对应的服务小区称为辅小区(Secondary Cell，SCell)。
4G和5G系统中，均支持双连接(Dual Connectivity，DC)功能。双连接下UE可以同时与两个基站保持连接，其中一个基站称为主基站(Master Node，MN)，另一个基站称为辅基站(Secondary Node，SN)。
5G系统中，在载波聚合操作、双连接操作时支持复制传输(Duplication Transmission)，此时，一个分组数据会聚协议(Packet Data Convergence Protocol，PDCP)实体对应两个或两个以上无线链路控制(Radio Link Control，RLC)实体，多个RLC实体分别在同一基站的不同服务小区上(CA操作时)或在不同的基站上(DC操作时)传输同样的数据。当UE进行复制传输时，缺乏无线接入网流量报告的解决方案，无法满足运营商需求。
发明内容
本申请实施例提供了一种无线接入网流量报告方法以及装置和系统、计算机可读存储介质，实现UE进行复制传输时无线接入网的流量(data volume)报告，满足运营商需求。
本申请一实施例提供了一种无线接入网流量报告方法，包括：
基站获取数据无线承载的流量信息，其中所述数据无线承载的流量信息包括：分组数据会聚协议PDCP生成的分组数据会聚协议协议数据单元PDCP PDU或分组数据会聚协议服务数据单元PDCP SDU的流量、PDCP下发给无线链路控制的PDCP PDU或PDCP SDU的流量；
所述基站根据所述数据无线承载的流量信息生成无线接入网流量报告，所述无线接入网流量报告包括以下至少之一：重复部分不计入时粒度单元的无线接入网流量、重复部分计入时该粒度单元的无线接入网流量、以及该粒度单元重复部分的无线接入网流量；
所述基站发送所述无线接入网流量报告给核心网。
本申请一实施例提供一种无线接入网流量报告装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现上述无线接入网流量报告方法。
本申请一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现任一实施例所述的无线接入网流量报告方法。
本申请至少一实施例提供一种无线接入网流量报告系统，包括基站和核心网，其中：
所述基站设置为，获取数据无线承载的流量信息，其中所述数据无线承载的流量信息包括：PDCP生成的PDCP PDU或PDCP SDU的流量、PDCP下发给无线链路控制的PDCP PDU或PDCP SDU的流量；根据所述数据无线承载的流量信息生成无线接入网流量报告，发送所述无线接入网流量报告给核心网；所述无线接入网流量报告包括以下至少之一：重复部分不计入时粒度单元的无线接入网流量、重复部分计入时该粒度单元的无线接入网流量、以及该粒度单元重复部分的无线接入网流量；
所述核心网设置为，接收所述基站发送的所述无线接入网流量报告。
附图概述
附图用来提供对本申请技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1是本申请一实施例提供的无线接入网流量报告方法流程图；
图2是本申请一实施例提供的无线接入网流量报告方法流程图；
图3是本申请一实施例提供的无线接入网流量报告方法流程图；
图4是本申请一实施例提供的无线接入网流量报告方法流程图；
图5是本申请一实施例提供的无线接入网流量报告方法流程图；
图6是本申请一实施例提供的无线接入网流量报告方法流程图；
图7是本申请一实施例提供的无线接入网流量报告方法流程图；
图8是本申请一实施例提供的无线接入网流量报告方法流程图；
图9是本申请一实施例提供的无线接入网流量报告方法流程图；
图10是本申请一实施例提供的无线接入网流量报告方法流程图；
图11是本申请一实施例提供的无线接入网流量报告方法流程图；
图12是本申请一实施例提供的无线接入网流量报告方法流程图；
图13是本申请一实施例提供的无线接入网流量报告方法流程图；
图14是本申请一实施例提供的无线接入网流量报告方法流程图；
图15是本申请一实施例提供的无线接入网流量报告方法流程图；
图16是本申请一实施例提供的无线接入网流量报告方法流程图；
图17是本申请一实施例提供的无线接入网流量报告方法流程图；
图18是本申请一实施例提供的无线接入网流量报告装置框图。
具体实施方式
下文中将结合附图对本申请的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
4G基站称为演进基站(evolved Node B，eNB)，eNB之间的接口称为X2接口，eNB与核心网(Core Network，CN)之间的接口称为S1接口。5G基站称为新一代无线接入网节点(New Generation Radio Access Network Node，NG RAN Node或gNB)，gNB之间的接口称为Xn接口，gNB与CN之间的接口称为NG接口。
4G系统中，将具有相同服务质量(Quality of Service，QoS)要求的数据流 聚合成承载，eNB与CN对QoS的处理都是按承载进行的，S1接口上的网络承载和Uu接口上的无线承载是一一对应的。
5G系统中，采用了新的QoS机制，Uu接口上的无线承载概念仍然保留即数据无线承载(Data Radio Bearer，DRB)，但NG接口上没有网络承载的概念，取而代之的是协议数据单元会话(Protocol Data Unit Session，PDU Session)和服务质量流(Quality of Service Flow，QoS Flow)。一个UE可以建有多个PDU Session，一个PDU Session可以包含多个QoS Flow，同一个PDU Session的多个QoS flow可以映射到同一个DRB，不同PDU Session的QoS flow不可以映射到同一个DRB。QoS flow包括：保证比特率服务质量流(GBR QoS flow)和非保证比特率服务质量流(non-GBR QoS flow)。
5G基站中，在分组数据会聚协议(Packet Data Convergence Protocol，PDCP)之上引入了新的业务数据适配协议(Service Data Adaptation Protocol，SDAP)用于QoS flow与DRB之间的映射(Mapping)等。每个PDU Session对应一个SDAP实体(Entity)，每个DRB对应一个PDCP实体。
5G基站可分为集中单元(Central Unit，CU)与分布单元(Distributed Unit，DU)两部分，一个基站有一个CU，一个基站可有多个DU，称为集中单元分布单元分离(CU DU Split)，CU与DU间的接口称为F1接口。
5G基站的CU可分为控制面(Control Plane，CP)与用户面(User Plane，UP)两部分，称为控制面用户面分离(CP UP Split)，CP与UP间的接口称为E1接口。
实施例0
CN向基站(当双连接时为MN)发送配置信息包括以下至少之一：UE标识、E-RAB标识(如为4G CN时)、PDU Session标识(如为5G CN时)、QoS Flow标识(如为5G CN时)、复制传输时重复部分是否计入RAN流量报告的指示、复制传输时流量所计入的RAT信息(当MN和SN的RAT不同且重复部分不计入时需要)。CN的配置粒度可为UE、E-RAB(如为4G CN时)、PDU Session(如为5G CN时)、QoS Flow级别(如为5G CN时)。所述配置信息可以由已有的S1或NG等CN与基站间接口消息携带，也可以由新的CN与基站间接口消息携带。
当双连接时，MN向SN发送配置信息包括以下至少之一：UE标识、E-RAB 标识(如为4G CN时)、PDU Session标识(如为5G CN时)、QoS Flow标识(如为5G CN时)、复制传输时重复部分是否计入RAN流量报告的指示、复制传输时流量所计入的RAT信息(当MN和SN的RAT不同且重复部分不计入时需要)。所述配置信息可以由已有的X2或Xn等基站间接口消息携带，也可以由新的基站间接口消息携带。
当双连接时，SN针对每个PDCP在SN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vs+Vm-V，重复部分计入时的RAN流量为V2＝Vs+Vm，重复部分计入时SN侧RAT的流量为VrS2＝Vs，重复部分计入时MN侧RAT的流量为VrM2＝Vm。当复制传输时流量所计入的RAT为SN侧RAT时，重复部分不计入时SN侧RAT的流量为VrS1＝Vs，重复部分不计入时MN侧RAT的流量为VrM1＝Vm-Vd。当复制传输时流量所计入的RAT为MN侧RAT时，重复部分不计入时SN侧RAT的流量为VrS1＝Vs-Vd，重复部分不计入时MN侧RAT的流量为VrM1＝Vm。
当双连接时，SN向MN发送RAN流量报告包括每个PDCP在SN侧的DRB的以下至少之一：重复部分不计入时的RAN流量V1，重复部分计入时的RAN流量V2，重复部分的RAN流量Vd，重复部分计入时SN侧RAT的流量VrS2，重复部分计入时MN侧RAT的流量VrM2，重复部分不计入时SN侧RAT的流量VrS1，重复部分不计入时MN侧RAT的流量VrM1。所述RAN流量报告可以由已有的X2或Xn等基站间接口消息携带，也可以由新的基站间接口消息携带。
基站(当双连接时为MN)针对每个PDCP在MN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vs+Vm-V，重复部分计入时的RAN流量为V2＝Vs+Vm，重复部分计入时SN侧RAT的流量为VrS2＝Vs，重复部分计入时MN侧RAT的流量为VrM2＝Vm。当复制传输时流量所计入的RAT为SN侧RAT时，重复部分不计入时SN侧RAT的流量为VrS1＝Vs，重复部分不计入时MN侧RAT 的流量为VrM1＝Vm-Vd。当复制传输时流量所计入的RAT为MN侧RAT时，重复部分不计入时SN侧RAT的流量为VrS1＝Vs-Vd，重复部分不计入时MN侧RAT的流量为VrM1＝Vm。
基站(当双连接时为MN)向CN发送RAN流量报告包括以下至少之一：
UE标识、重复部分不计入时该UE的RAN流量(即该UE所有DRB的V1之和)；
UE标识、重复部分不计入时该UE在MN侧RAT的RAN流量(即该UE所有DRB的VrM1之和)；
UE标识、重复部分不计入时该UE在SN侧RAT的RAN流量(即该UE所有DRB的VrS1之和)；
UE标识、重复部分计入时该UE的RAN流量(即该UE所有DRB的V2之和)；
UE标识、重复部分计入时该UE在MN侧RAT的RAN流量(即该UE所有DRB的VrM2之和)；
UE标识、重复部分计入时该UE在SN侧RAT的RAN流量(即该UE所有DRB的VrS2之和)；
UE标识、该UE重复部分的RAN流量(即该UE所有DRB的Vd之和)；
E-RAB标识，重复部分不计入时该E-RAB的RAN流量(即该E-RAB对应DRB的V1)；
E-RAB标识，重复部分不计入时该E-RAB在MN侧RAT的RAN流量(即该E-RAB对应DRB的VrM1)；
E-RAB标识，重复部分不计入时该E-RAB在SN侧RAT的RAN流量(即该E-RAB对应DRB的VrS1)；
E-RAB标识，重复部分计入时该E-RAB的RAN流量(即该E-RAB对应DRB的V2)；
E-RAB标识，重复部分计入时该E-RAB在MN侧RAT的RAN流量(即该E-RAB对应DRB的VrM2)；
E-RAB标识，重复部分计入时该E-RAB在SN侧RAT的RAN流量(即该E-RAB对应DRB的VrS2)；
E-RAB标识，该E-RAB重复部分的RAN流量(即该E-RAB对应DRB的Vd)；
PDU Session标识、重复部分不计入时该PDU Session的RAN流量(即该PDU Session所有DRB的V1之和)；
PDU Session标识、重复部分不计入时该PDU Session在MN侧RAT的RAN流量(即该PDU Session所有DRB的VrM1之和)；
PDU Session标识、重复部分不计入时该PDU Session在SN侧RAT的RAN流量(即该PDU Session所有DRB的VrS1之和)；
PDU Session标识、重复部分计入时该PDU Session的RAN流量(即该PDU Session所有DRB的V2之和)；
PDU Session标识、重复部分计入时该PDU Session在MN侧RAT的RAN流量(即该PDU Session所有DRB的VrM2之和)；
PDU Session标识、重复部分计入时该PDU Session在SN侧RAT的RAN流量(即该PDU Session所有DRB的VrS2之和)；
PDU Session标识、该PDU Session重复部分的RAN流量(即该PDU Session所有DRB的Vd之和)；
QoS Flow标识、重复部分不计入时该QoS Flow的RAN流量(即该QoS Flow所对应DRB的V1，当QoS Flow和DRB为一对一时)；
QoS Flow标识、重复部分不计入时该QoS Flow在MN侧RAT的RAN流量(即该QoS Flow所对应DRB的VrM1，当QoS Flow和DRB为一对一时)；
QoS Flow标识、重复部分不计入时该QoS Flow在SN侧RAT的RAN流量(即该QoS Flow所对应DRB的VrS1，当QoS Flow和DRB为一对一时)；
QoS Flow标识、重复部分计入时该QoS Flow的RAN流量(即该QoS Flow所对应DRB的V2，当QoS Flow和DRB为一对一时)；
QoS Flow标识、重复部分计入时该QoS Flow在MN侧RAT的RAN流量(即该QoS Flow所对应DRB的VrM2，当QoS Flow和DRB为一对一时)；
QoS Flow标识、重复部分计入时该QoS Flow在SN侧RAT的RAN流量(即该QoS Flow所对应DRB的VrS2，当QoS Flow和DRB为一对一时)；
QoS Flow标识、该QoS Flow重复部分的RAN流量(即该QoS Flow所对应DRB的Vd，当QoS Flow和DRB为一对一时)；
QoS Flow标识列表、重复部分不计入时该QoS Flow组的RAN流量(即该QoS Flow组所对应DRB的V1，当QoS Flow和DRB为多对一时)；
QoS Flow标识列表、重复部分不计入时该QoS Flow组在MN侧RAT的 RAN流量(即该QoS Flow组所对应DRB的VrM1，当QoS Flow和DRB为多对一时)；
QoS Flow标识列表、重复部分不计入时该QoS Flow组在SN侧RAT的RAN流量(即该QoS Flow组所对应DRB的VrS1，当QoS Flow和DRB为多对一时)；
QoS Flow标识列表、重复部分计入时该QoS Flow组的RAN流量(即该QoS Flow组所对应DRB的V2，当QoS Flow和DRB为多对一时)；
QoS Flow标识列表、重复部分计入时该QoS Flow组在MN侧RAT的RAN流量(即该QoS Flow组所对应DRB的VrM2，当QoS Flow和DRB为多对一时)；
QoS Flow标识列表、重复部分计入时该QoS Flow组在SN侧RAT的RAN流量(即该QoS Flow组所对应DRB的VrS2，当QoS Flow和DRB为多对一时)；
QoS Flow标识列表、该QoS Flow组重复部分的RAN流量(即该QoS Flow组所对应DRB的Vd，当QoS Flow和DRB为多对一时)。
所述RAN流量报告可以由已有的S1或NG等CN与基站间接口消息携带，也可以由新的CN与基站间接口消息携带。
实施例一
本实施例提供一种无线接入网流量报告方法，包括：步骤101、步骤102和步骤103。
在步骤101中，基站获取数据无线承载的流量信息，其中所述数据无线承载的流量信息包括：PDCP生成的PDCP PDU或PDCP SDU(Service Data Unit，服务数据单元)的流量、PDCP下发给RLC的PDCP PDU或PDCP SDU的流量。
在步骤102中，所述基站根据所述数据无线承载的流量信息生成无线接入网流量报告，所述无线接入网流量报告包括以下至少之一：重复部分不计入时粒度单元的RAN流量，重复部分计入时该粒度单元的RAN流量；该粒度单元重复部分的RAN流量。
在步骤103中，所述基站发送所述无线接入网流量报告给核心网。
其中，步骤102中，粒度单元是指进行流量统计针对的对象，比如为UE(此时针对UE进行流量统计)、演进通用陆地无线接入网无线接入承载(E-UTRAN Radio Access Bearer，E-RAB)(此时针对E-RAB进行流量统计)、PDU Session(此时针对PDU Session进行流量统计)、QoS Flow(此时针对QoS Flow进行 流量统计)、QoS Flow组(此时针对一组QoS Flow进行流量统计)。比如粒度单元为UE时，无线接入网流量报告中的信息为：UE的标识信息、重复部分不计入时该UE的RAN流量，重复部分计入时该UE的RAN流量；该UE重复部分的RAN流量。又比如，如果粒度单元为E-RAB时，无线接入网流量报告中的信息为：E-RAB的标识信息、重复部分不计入时该E-RAB的RAN流量，重复部分计入时该E-RAB的RAN流量；该E-RAB重复部分的RAN流量。后文中配置粒度即对应粒度单元信息。
其中，PDCP SDU的流量为PDCP PDU的流量减掉PDCP头开销。
在一实施例中，所述获取PDCP下发给无线链路控制的PDCP PDU或PDCP SDU的流量包括：当DRB对应的PDCP和RLC不在同一节点时(如双连接、CU DU分离的情况)，获取PDCP下发给无线链路控制的PDCP PDU或PDCP SDU的流量时，去除PDCP所在节点与无线链路控制所在节点间接口上丢失的数据包的流量。
在一实施例中，所述获取PDCP下发给无线链路控制的PDCP PDU或PDCP SDU的流量包括：获取PDCP下发给无线链路控制的PDCP PDU或PDCP SDU的流量时，去除该PDCP已决定丢弃的数据包的流量。
下面分两种情况进行说明。
1、双连接时，此时基站包括MN和SN。所述MN和SN可能为相同的RAT，或者不同的RAT。
在一实施例中，所述MN接收所述CN或者OAM发送的第一配置信息，所述第一配置信息包括以下至少之一：复制传输时重复部分是否计入无线接入网流量报告的指示、复制传输时流量所计入的无线接入技术信息、以及粒度单元信息。
所述MN发送第二配置信息给所述SN，所述第二配置信息包括以下至少之一：复制传输时重复部分是否计入无线接入网流量报告的指示、复制传输时流量所计入的无线接入技术信息、以及粒度单元信息。所述第一配置信息可以由已有的S1或NG等CN与基站间接口消息携带，也可以由新的CN与基站间接口消息携带。所述第二配置信息可以由已有的X2或Xn等基站间接口消息携带，也可以由新的基站间接口消息携带。
在一实施例中，所述第一配置信息包括以下至少之一：UE标识、演进通用陆地无线接入网无线接入承载(E-UTRAN Radio Access Bearer，E-RAB)标识 (如为4G CN时)、PDU Session标识(如为5G CN时)、QoS Flow标识(如为5G CN时)、复制传输时重复部分是否计入无线接入网(Radio Access Network，RAN)流量报告的指示、以及复制传输时流量所计入的无线接入技术(Radio Access Technology，RAT)信息(当MN和SN的RAT不同且重复部分不计入时需要)。CN的配置粒度可为UE、E-RAB(如为4G CN时)、PDU Session(如为5G CN时)、QoS Flow级别(如为5G CN时)。
在一实施例中，所述第二配置信息包括以下至少之一：UE标识、E-RAB标识(如为4G CN时)、PDU Session标识(如为5G CN时)、QoS Flow标识(如为5G CN时)、复制传输时重复部分是否计入RAN流量报告的指示、以及复制传输时流量所计入的RAT信息(当MN和SN的RAT不同且重复部分不计入时需要)。
在一实施例中，所述基站获取每个数据无线承载的流量信息包括：
所述主基站获取每个PDCP在主基站侧的信息，其中所述每个PDCP在主基站侧的信息包括：PDCP生成的PDCP PDU或PDCP SDU的流量、PDCP下发给主基站侧RLC的PDCP PDU或PDCP SDU的流量、以及PDCP下发给辅基站侧RLC的PDCP PDU或PDCP SDU的流量；
所述辅基站获取每个PDCP在辅基站侧的信息，其中所述每个PDCP在主基站侧的信息包括：PDCP生成的PDCP PDU或PDCP SDU的流量、PDCP下发给主基站侧RLC的PDCP PDU或PDCP SDU的流量、PDCP下发给辅基站侧RLC的PDCP PDU或PDCP SDU的流量。
所述基站根据所述数据无线承载的流量信息生成无线接入网流量报告包括：
所述辅基站生成第一无线接入网流量报告，发送所述第一无线接入网流量报告给所述主基站，所述第一无线接入网流量报告包括辅基站侧的以下至少之一：重复部分不计入时粒度单元(辅基站侧的)的RAN流量、重复部分不计入时该粒度单元在主基站侧RAT的流量、重复部分不计入时该粒度单元在辅基站侧RAT的流量、重复部分计入时该粒度单元的RAN流量、重复部分计入时该粒度单元在主基站侧RAT的流量、重复部分计入时该粒度单元在辅基站侧RAT的流量、以及该粒度单元重复部分的RAN流量；
所述主基站生成第二无线接入网流量报告，所述第二无线接入网流量报告包括粒度单元的标识信息，还包括以下至少之一：
重复部分不计入时该粒度单元(主基站侧的和辅基站侧中的至少之一的。 如粒度为UE时，为主基站侧的和辅基站侧的；如粒度为PDU Session时，为主基站侧的和辅基站侧中的至少之一的，双连接时一个PDU Session可以在主基站侧或辅基站侧，也可以分离split在主基站侧和辅基站侧；如粒度为QoS Flow、E-RAB时，为主基站侧的或辅基站侧的)的RAN流量、重复部分不计入时该粒度单元在主基站侧RAT的流量、重复部分不计入时该粒度单元在辅基站侧RAT的流量、重复部分计入时该粒度单元的RAN流量、重复部分计入时该粒度单元在主基站侧RAT的流量、重复部分计入时该粒度单元在辅基站侧RAT的流量、以及该粒度单元重复部分的RAN流量；
所述基站发送所述无线接入网流量报告给核心网包括：所述主基站发送所述第二无线接入网流量报告给所述核心网。
所述辅基站根据所述数据无线承载的流量信息和所述第二配置信息生成第一无线接入网流量报告；所述主基站根据所述数据无线承载的流量信息和所述第一配置信息生成第二无线接入网流量报告。
在一实施例中，SN针对每个PDCP在SN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vs+Vm-V，重复部分计入时的RAN流量为V2＝Vs+Vm，重复部分计入时SN侧RAT的流量为VrS2＝Vs，重复部分计入时MN侧RAT的流量为VrM2＝Vm。当复制传输时流量所计入的RAT为SN侧RAT时，重复部分不计入时SN侧RAT的流量为VrS1＝Vs，重复部分不计入时MN侧RAT的流量为VrM1＝Vm-Vd。当复制传输时流量所计入的RAT为MN侧RAT时，重复部分不计入时SN侧RAT的流量为VrS1＝Vs-Vd，重复部分不计入时MN侧RAT的流量为VrM1＝Vm。
SN向MN发送RAN流量报告，所述RAN流量报告包括每个PDCP在SN侧的DRB的以下至少之一：重复部分不计入时的RAN流量V1，重复部分计入时的RAN流量V2，重复部分的RAN流量Vd，重复部分计入时SN侧RAT的流量VrS2，重复部分计入时MN侧RAT的流量VrM2，重复部分不计入时SN侧RAT的流量VrS1，重复部分不计入时MN侧RAT的流量VrM1。所述RAN流量报告可以由已有的X2或Xn等基站间接口消息携带，也可以由新的基站间 接口消息携带。
MN针对每个PDCP在MN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)，则：
重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vs+Vm-V，重复部分计入时的RAN流量为V2＝Vs+Vm，重复部分计入时SN侧RAT的流量为VrS2＝Vs，重复部分计入时MN侧RAT的流量为VrM2＝Vm。当复制传输时流量所计入的RAT为SN侧RAT时，重复部分不计入时SN侧RAT的流量为VrS1＝Vs，重复部分不计入时MN侧RAT的流量为VrM1＝Vm-Vd。当复制传输时流量所计入的RAT为MN侧RAT时，重复部分不计入时SN侧RAT的流量为VrS1＝Vs-Vd，重复部分不计入时MN侧RAT的流量为VrM1＝Vm。
在一实施例中，MN向CN发送RAN流量报告，所述RAN流量报告包括以下至少之一：
UE标识、重复部分不计入时该UE的RAN流量(即该UE所有MN侧的和SN侧的DRB的V1之和)；
UE标识、重复部分不计入时该UE在MN侧RAT的RAN流量(即该UE所有MN侧的和SN侧的DRB的VrM1之和)；
UE标识、重复部分不计入时该UE在SN侧RAT的RAN流量(即该UE所有MN侧的和SN侧的DRB的VrS1之和)；
UE标识、重复部分计入时该UE的RAN流量(即该UE所有MN侧的和SN侧的DRB的V2之和)；
UE标识、重复部分计入时该UE在MN侧RAT的RAN流量(即该UE所有MN侧的和SN侧的DRB的VrM2之和)；
UE标识、重复部分计入时该UE在SN侧RAT的RAN流量(即该UE所有MN侧的和SN侧的DRB的VrS2之和)；
UE标识、该UE重复部分的RAN流量(即该UE所有MN侧的和SN侧的DRB的Vd之和)；
E-RAB标识，重复部分不计入时该E-RAB的RAN流量(即该E-RAB对应的MN侧的或SN侧的DRB的V1)；
E-RAB标识，重复部分不计入时该E-RAB在MN侧RAT的RAN流量(即该E-RAB对应的MN侧的或SN侧的DRB的VrM1)；
E-RAB标识，重复部分不计入时该E-RAB在SN侧RAT的RAN流量(即该E-RAB对应的MN侧的或SN侧的DRB的VrS1)；
E-RAB标识，重复部分计入时该E-RAB的RAN流量(即该E-RAB对应的MN侧的或SN侧的DRB的V2)；
E-RAB标识，重复部分计入时该E-RAB在MN侧RAT的RAN流量(即该E-RAB对应的MN侧的或SN侧的DRB的VrM2)；
E-RAB标识，重复部分计入时该E-RAB在SN侧RAT的RAN流量(即该E-RAB对应的MN侧的或SN侧的DRB的VrS2)；
E-RAB标识，该E-RAB重复部分的RAN流量(即该E-RAB对应的MN侧的或SN侧的DRB的Vd)；
PDU Session标识、重复部分不计入时该PDU Session的RAN流量(即该PDU Session所有MN侧的和SN侧中的至少之一的DRB的V1之和)；
PDU Session标识、重复部分不计入时该PDU Session在MN侧RAT的RAN流量(即该PDU Session所有MN侧的和SN侧中的至少之一的DRB的VrM1之和)；
PDU Session标识、重复部分不计入时该PDU Session在SN侧RAT的RAN流量(即该PDU Session所有MN侧的和SN侧中的至少之一的DRB的VrS1之和)；
PDU Session标识、重复部分计入时该PDU Session的RAN流量(即该PDU Session所有MN侧的和SN侧中的至少之一的DRB的V2之和)；
PDU Session标识、重复部分计入时该PDU Session在MN侧RAT的RAN流量(即该PDU Session所有MN侧的和SN侧中的至少之一的DRB的VrM2之和)；
PDU Session标识、重复部分计入时该PDU Session在SN侧RAT的RAN流量(即该PDU Session所有MN侧的和SN侧中的至少之一的DRB的VrS2之和)；
PDU Session标识、该PDU Session重复部分的RAN流量(即该PDU Session所有MN侧的和SN侧中的至少之一的DRB的Vd之和)；
QoS Flow标识、重复部分不计入时该QoS Flow的RAN流量(即该QoS Flow 所对应的MN侧的或SN侧的DRB的V1，当QoS Flow和DRB为一对一时)；
QoS Flow标识、重复部分不计入时该QoS Flow在MN侧RAT的RAN流量(即该QoS Flow所对应的MN侧的或SN侧的DRB的VrM1，当QoS Flow和DRB为一对一时)；
QoS Flow标识、重复部分不计入时该QoS Flow在SN侧RAT的RAN流量(即该QoS Flow所对应的MN侧的或SN侧的DRB的VrS1，当QoS Flow和DRB为一对一时)；
QoS Flow标识、重复部分计入时该QoS Flow的RAN流量(即该QoS Flow所对应的MN侧的或SN侧的DRB的V2，当QoS Flow和DRB为一对一时)；
QoS Flow标识、重复部分计入时该QoS Flow在MN侧RAT的RAN流量(即该QoS Flow所对应的MN侧的或SN侧的DRB的VrM2，当QoS Flow和DRB为一对一时)；
QoS Flow标识、重复部分计入时该QoS Flow在SN侧RAT的RAN流量(即该QoS Flow所对应的MN侧的或SN侧的DRB的VrS2，当QoS Flow和DRB为一对一时)；
QoS Flow标识、该QoS Flow重复部分的RAN流量(即该QoS Flow所对应的MN侧的或SN侧的DRB的Vd，当QoS Flow和DRB为一对一时)；
QoS Flow标识列表、重复部分不计入时该QoS Flow组(即QoS Flow标识列表指示的QoS Flow组)的RAN流量(即该QoS Flow组所对应的MN侧的或SN侧的DRB的V1，当QoS Flow和DRB为多对一时)；
QoS Flow标识列表、重复部分不计入时该QoS Flow组在MN侧RAT的RAN流量(即该QoS Flow组所对应的MN侧的或SN侧的DRB的VrM1，当QoS Flow和DRB为多对一时)；
QoS Flow标识列表、重复部分不计入时该QoS Flow组在SN侧RAT的RAN流量(即该QoS Flow组所对应的MN侧的或SN侧的DRB的VrS1，当QoS Flow和DRB为多对一时)；
QoS Flow标识列表、重复部分计入时该QoS Flow组的RAN流量(即该QoS Flow组所对应的MN侧的或SN侧的DRB的V2，当QoS Flow和DRB为多对一时)；
QoS Flow标识列表、重复部分计入时该QoS Flow组在MN侧RAT的RAN流量(即该QoS Flow组所对应的MN侧的或SN侧的DRB的VrM2，当QoS Flow 和DRB为多对一时)；
QoS Flow标识列表、重复部分计入时该QoS Flow组在SN侧RAT的RAN流量(即该QoS Flow组所对应的MN侧的或SN侧的DRB的VrS2，当QoS Flow和DRB为多对一时)；
QoS Flow标识列表、该QoS Flow组重复部分的RAN流量(即该QoS Flow组所对应的MN侧的或SN侧的DRB的Vd，当QoS Flow和DRB为多对一时)。
在另一实施例中，如果MN和SN同为4G或同为5G基站，则，所述RAN流量报告包括以下至少之一：
UE标识、重复部分不计入时该UE的RAN流量(即该UE所有MN侧的和SN侧的DRB的V1之和)；
UE标识、重复部分计入时该UE的RAN流量(即该UE所有MN侧的和SN侧的DRB的V2之和)；
UE标识、该UE重复部分的RAN流量(即该UE所有MN侧的和SN侧的DRB的Vd之和)；
E-RAB标识，重复部分不计入时该E-RAB的RAN流量(即该E-RAB对应的MN侧的或SN侧的DRB的V1)；
E-RAB标识，重复部分计入时该E-RAB的RAN流量(即该E-RAB对应的MN侧的或SN侧的DRB的V2)；
E-RAB标识，该E-RAB重复部分的RAN流量(即该E-RAB对应的MN侧的或SN侧的DRB的Vd)；
PDU Session标识、重复部分不计入时该PDU Session的RAN流量(即该PDU Session所有MN侧的和SN侧中的至少之一的DRB的V1之和)；
PDU Session标识、重复部分计入时该PDU Session的RAN流量(即该PDU Session所有MN侧的和SN侧中的至少之一的DRB的V2之和)；
PDU Session标识、该PDU Session重复部分的RAN流量(即该PDU Session所有MN侧的和SN侧中的至少之一的DRB的Vd之和)；
QoS Flow标识、重复部分不计入时该QoS Flow的RAN流量(即该QoS Flow所对应的MN侧的或SN侧的DRB的V1，当QoS Flow和DRB为一对一时)；
QoS Flow标识、重复部分计入时该QoS Flow的RAN流量(即该QoS Flow所对应的MN侧的或SN侧的DRB的V2，当QoS Flow和DRB为一对一时)；
QoS Flow标识、该QoS Flow重复部分的RAN流量(即该QoS Flow所对 应的MN侧的或SN侧的DRB的Vd，当QoS Flow和DRB为一对一时)；
QoS Flow标识列表、重复部分不计入时该QoS Flow组(即QoS Flow标识列表指示的QoS Flow组)的RAN流量(即该QoS Flow组所对应的MN侧的或SN侧的DRB的V1，当QoS Flow和DRB为多对一时)；
QoS Flow标识列表、重复部分计入时该QoS Flow组的RAN流量(即该QoS Flow组所对应的MN侧的或SN侧的DRB的V2，当QoS Flow和DRB为多对一时)；
QoS Flow标识列表、该QoS Flow组重复部分的RAN流量(即该QoS Flow组所对应的MN侧的或SN侧的DRB的Vd，当QoS Flow和DRB为多对一时)。
在一实施例中，当辅基站包括辅基站集中单元控制面和辅基站集中单元用户面时：
所述辅基站获取每个PDCP在辅基站侧的信息包括：
所述辅基站集中单元用户面获取所述每个PDCP在辅基站侧的信息：PDCP生成的PDCP PDU或PDCP SDU的流量、PDCP下发给主基站侧无线链路控制的PDCP PDU或PDCP SDU的流量、PDCP下发给辅基站侧无线链路控制的PDCP PDU或PDCP SDU的流量；
所述辅基站生成第一无线接入网流量报告，发送所述第一无线接入网流量报告给所述主基站包括：
所述辅基站集中单元用户面生成第一无线接入网流量报告，发送所述第一无线接入网流量报告给所述辅基站集中单元控制面；所述辅基站集中单元控制面发送所述第一无线接入网流量报告给所述主基站。
在一实施例中，当辅基站包括辅基站集中单元控制面和辅基站集中单元用户面时：配置信息由CN或OAM发送给MN，MN发送给基站集中单元控制面，辅基站集中单元控制面再将配置信息发送给辅基站集中单元用户面。
所述RAN流量报告可以由已有的S1或NG等CN与基站间接口消息携带，也可以由新的CN与基站间接口消息携带。
2、载波聚合时
在一实施例中，所述基站还接收OAM或CN发送的配置信息，所述配置信息包括以下至少之一：复制传输时重复部分是否计入无线接入网流量报告的指示、复制传输时流量所计入的无线接入技术信息、以及粒度单元信息。其中， 配置信息还包括以下至少之一：UE标识、E-RAB标识、PDU Session标识、以及QoS Flow标识。
在一实施例中，基站针对每个DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给所有RLC的PDCP PDU的流量之和(设为Vr)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vr-V，重复部分计入时的RAN流量为V2＝Vr。
在一实施例中，所述RAN流量报告包括以下至少之一：
UE标识、重复部分不计入时该UE的RAN流量(即该UE所有DRB的V1之和)；
UE标识、重复部分计入时该UE的RAN流量(即该UE所有DRB的V2之和)；
UE标识、该UE重复部分的RAN流量(即该UE所有DRB的Vd之和)；
E-RAB标识，重复部分不计入时该E-RAB的RAN流量(即该E-RAB对应DRB的V1)；
E-RAB标识，重复部分计入时该E-RAB的RAN流量(即该E-RAB对应DRB的V2)；
E-RAB标识，该E-RAB重复部分的RAN流量(即该E-RAB对应DRB的Vd)；
PDU Session标识、重复部分不计入时该PDU Session的RAN流量(即该PDU Session所有DRB的V1之和)；
PDU Session标识、重复部分计入时该PDU Session的RAN流量(即该PDU Session所有DRB的V2之和)；
PDU Session标识、该PDU Session重复部分的RAN流量(即该PDU Session所有DRB的Vd之和)；
QoS Flow标识、重复部分不计入时该QoS Flow的RAN流量(即该QoS Flow所对应DRB的V1，当QoS Flow和DRB为一对一时)；
QoS Flow标识、重复部分计入时该QoS Flow的RAN流量(即该QoS Flow所对应DRB的V2，当QoS Flow和DRB为一对一时)；
QoS Flow标识、该QoS Flow重复部分的RAN流量(即该QoS Flow所对应DRB的Vd，当QoS Flow和DRB为一对一时)；
QoS Flow标识列表、重复部分不计入时该QoS Flow组的RAN流量(即该 QoS Flow组所对应DRB的V1，当QoS Flow和DRB为多对一时)；
QoS Flow标识列表、重复部分计入时该QoS Flow组的RAN流量(即该QoS Flow组所对应DRB的V2，当QoS Flow和DRB为多对一时)；
QoS Flow标识列表、该QoS Flow组重复部分的RAN流量(即该QoS Flow组所对应DRB的Vd，当QoS Flow和DRB为多对一时)。
当基站接收了配置信息时，可以根据配置信息中的指示生成RAN流量报告。比如，配置信息中携带复制传输时重复部分不计入无线接入网流量报告的指示，且粒度单元为UE时，RAN流量报告中包括如下信息：UE标识、重复部分不计入时该UE的RAN流量(即该UE所有DRB的V1之和)。
在一实施例中，所述基站包括基站集中单元控制面和基站集中单元用户面。
所述基站获取数据无线承载的流量信息包括：所述基站集中单元用户面获取每个PDCP的如下信息：PDCP生成的PDCP PDU或PDCP SDU的流量、PDCP下发给无线链路控制的PDCP PDU或PDCP SDU的流量。
所述基站根据所述数据无线承载的流量信息生成无线接入网流量报告包括：所述基站集中单元用户面生成无线接入网流量报告，发送所述无线接入网流量报告给所述基站集中单元控制面。
所述基站发送所述无线接入网流量报告给核心网包括：所述基站集中单元控制面发送所述无线接入网流量报告给所述核心网。
另外，配置信息由CN或OAM发送给所述基站集中单元控制面，所述基站集中单元控制面再发送给基站集中单元用户面。
与相关技术相比，本申请至少一实施例提供了一种复制传输时，无线接入网流量的报告实现方案，满足运营商需求。
实施例二
本实施例为双连接场景下，如图2所示，包括：步骤201至步骤206。
在步骤201中，网络管理操作维护(Operating and Maintaining，OAM)向MN发送配置信息，所述配置信息包括以下至少之一：复制传输时重复部分是否计入RAN流量报告的指示(本例假设为不计入)，复制传输时流量所计入的RAT信息(当MN和SN的RAT不同且重复部分不计入时需要，本例假设MN为4G RAT，SN为5G RAT，复制传输时流量所计入的RAT为5G)。其中，OAM配置粒度为基站。
在步骤202中，OAM向SN发送配置信息，所述配置信息包括以下至少之一：复制传输时重复部分是否计入RAN流量报告的指示(本例假设为不计入)，复制传输时流量所计入的RAT信息(当MN和SN的RAT不同且重复部分不计入时需要，本例假设MN为4G RAT，SN为5G RAT，复制传输时流量所计入的RAT为5G)。OAM配置粒度为基站。
在步骤203中，SN针对每个PDCP在SN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vs+Vm-V，重复部分不计入时的5G流量为VrS＝Vs，重复部分不计入时的4G流量为VrM＝Vm-Vd。
在步骤204中，SN向MN发送RAN流量报告，所述RAN流量报告包括每个PDCP在SN侧的DRB的以下至少之一：V1，VrS，以及VrM。
在步骤205中，MN针对每个PDCP在MN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vm+Vs-V，重复部分不计入时的4G流量为VrM＝Vm-Vd，重复部分不计入时的5G流量为VrS＝Vs。
在步骤206中，MN向CN发送RAN流量报告，所述RAN流量报告包括每个DRB(PDCP在MN侧的和PDCP在SN侧中至少之一的)的以下至少之一：
与DRB一一对应的E-RAB的标识，V1，VrS，以及VrM。
即，所述RAN流量报告包括一个列表，该列表包括某UE所有DRB(PDCP在MN侧的和PDCP在SN侧的)对应的E-RAB的流量信息，该列表的一项表示其中一个E-RAB的流量信息包括：E-RAB标识、VrS、以及VrM。
另外，所述流量统计也可以针对PDCP SDU进行，即在流量统计的时候减掉PDCP头的开销得到PDCP SDU的流量，即PDCP SDU＝PDCP PDU-PDCP header(头)。
实施例三
本实施例为双连接场景下的实现，如图3所示，包括：步骤301至步骤306。
在步骤301中，OAM向MN发送配置信息，所述配置信息包括以下至少之一：复制传输时重复部分是否计入RAN流量报告的指示(本例假设为计入)，其中，本例假设MN为4G RAT，SN为5G RAT。OAM配置粒度为基站。
在步骤302中，OAM向SN发送配置信息，所述配置信息包括以下至少之一：复制传输时重复部分是否计入RAN流量报告的指示(本例假设为计入)(本例假设MN为4G RAT，SN为5G RAT)。OAM配置粒度为基站。
在步骤303中，SN针对每个PDCP在SN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)，则重复部分计入时的RAN流量为V2＝Vs+Vm，重复部分的RAN流量为Vd＝Vs+Vm-V，重复部分计入时的5G流量为VrS＝Vs，重复部分计入时的4G流量为VrM＝Vm。
在步骤304中，SN向MN发送RAN流量报告，所述RAN流量报告包括每个PDCP在SN侧的DRB的以下至少之一：V2，VrS，以及VrM。
在步骤305中，MN针对每个PDCP在MN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)，则重复部分计入时的RAN流量为V2＝Vm+Vs，重复部分的RAN流量为Vd＝Vm+Vs-V，重复部分计入时的4G流量为VrM＝Vm，重复部分计入时的5G流量为VrS＝Vs。
在步骤306中，MN向CN发送RAN流量报告，所述RAN流量报告包括每个DRB(PDCP在MN侧的和PDCP在SN侧中至少之一的)的以下至少之一：与DRB一一对应的E-RAB的标识，V2，VrS，以及VrM。
另外，所述流量统计也可以针对PDCP SDU进行，即在流量统计的时候减掉PDCP头的开销。
实施例四
本实施例为双连接场景下，如图4所示，包括：步骤401至步骤406。
在步骤401中，CN向MN发送配置信息。
所述配置信息包括以下至少之一：UE标识、E-RAB标识、复制传输时重复 部分是否计入RAN流量报告的指示(本例假设为不计入)，以及复制传输时流量所计入的RAT信息(当MN和SN的RAT不同且重复部分不计入时需要，本例假设MN为4G RAT，SN为5G RAT，复制传输时流量所计入的RAT为5G)。CN配置粒度为UE、E-RAB(本例假设配置粒度为E-RAB，且所有E-RAB都配置为不计入)。
在步骤402中，MN向SN发送配置信息，所述配置包括以下至少之一：UE标识、E-RAB标识、复制传输时重复部分是否计入RAN流量报告的指示(本例假设为不计入)，复制传输时重复部分所计入的RAT信息(当MN和SN的RAT不同且重复部分不计入时需要，本例假设MN为4G RAT，SN为5G RAT，复制传输时重复部分所计入的RAT为5G)。
在步骤403中，SN针对每个PDCP在SN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vs+Vm-V，重复部分不计入时的5G流量为VrS＝Vs，重复部分不计入时的4G流量为VrM＝Vm-Vd。
在步骤404中，SN向MN发送RAN流量报告，所述RAN流量报告包括每个PDCP在SN侧的DRB的以下至少之一：V1，VrS，以及VrM。
在步骤405中，MN针对每个PDCP在MN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vm+Vs-V，重复部分不计入时的4G流量为VrM＝Vm-Vd，重复部分不计入时的5G流量为VrS＝Vs。
在步骤406中，MN向CN发送RAN流量报告，所述RAN流量报告包括每DRB(PDCP在MN侧的和PDCP在SN侧中的至少之一的)的以下至少之一：与DRB一一对应的E-RAB的标识，V1，VrS，以及VrM。
另外，所述流量统计也可以针对PDCP SDU进行，即在流量统计的时候减掉PDCP头的开销。
实施例五
本实施例为双连接场景下，假设MN为4G RAT，SN为5G RAT，如图5所示，包括：步骤501至步骤506。
在步骤501中，CN向MN发送配置信息，所述配置信息包括以下至少之一：UE标识、E-RAB标识、复制传输时重复部分是否计入RAN流量报告的指示(本例假设为计入)。CN配置粒度为UE、E-RAB(本例假设配置粒度为E-RAB，且所有E-RAB都配置为计入)。
在步骤502中，MN向SN发送配置信息，所述配置信息包括以下至少之一：UE标识、E-RAB标识、以及复制传输时重复部分是否计入RAN流量报告的指示(本例假设为计入)。
在步骤503中，SN针对每个PDCP在SN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)，则重复部分计入时的RAN流量为V2＝Vs+Vm，重复部分的RAN流量为Vd＝Vs+Vm-V，重复部分计入时的5G流量为VrS＝Vs，重复部分计入时的4G流量为VrM＝Vm。
在步骤504中，SN向MN发送RAN流量报告，所述RAN流量报告包括每个PDCP在SN侧的DRB的以下至少之一：V2，VrS，以及VrM。
在步骤505中，MN针对每个PDCP在MN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)，则重复部分计入时的RAN流量为V2＝Vm+Vs，重复部分的RAN流量为Vd＝Vm+Vs-V，重复部分计入时的4G流量为VrM＝Vm，重复部分计入时的5G流量为VrS＝Vs。
在步骤506中，MN向CN发送RAN流量报告，所述RNA流量报告包括每个DRB(PDCP在MN侧的和PDCP在SN侧中的至少之一的)的以下至少之一：与DRB一一对应的E-RAB的标识，V2，VrS，以及VrM。
另外，所述流量统计也可以针对PDCP SDU进行，即在流量统计的时候减掉PDCP头的开销。
实施例六
本实施例为双连接场景下，假设MN为4G RAT，SN为5G RAT，如图6 所示，包括：步骤601至步骤604。
在步骤601中，SN针对每个PDCP在SN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vs+Vm-V，重复部分计入时的RAN流量为V2＝Vs+Vm。
在步骤602中，SN向MN发送RAN流量报告包括每个PDCP在SN侧的DRB的以下至少之一：V1，V2，Vd，Vs，以及Vm。
在步骤603中，MN针对每个PDCP在MN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vm+Vs-V，重复部分计入时的RAN流量为V2＝Vm+Vs。
在步骤604中，MN向CN发送RAN流量报告，所述RAN流量报告包括每个DRB(PDCP在MN侧的和PDCP在SN侧中的至少之一的)的以下至少之一：与DRB一一对应的E-RAB的标识，V1，V2，Vd，Vs，以及Vm。
即，所述RAN流量报告包括一个列表，该列表包括某UE所有DRB(PDCP在MN侧的和PDCP在SN侧的)的流量信息，该列表的一项表示其中一个DRB的流量信息包括：E-RAB标识，Vd，Vs，以及Vm。
另外、所述流量统计也可以针对PDCP SDU进行，即在流量统计的时候减掉PDCP头的开销。
实施例七
本实施例为双连接场景下，如图7所示，包括：步骤701至步骤706。
在步骤701中，CN向MN发送配置信息，所述配置信息包括以下至少之一：UE标识、PDU Session标识、QoS Flow标识、复制传输时重复部分是否计入RAN流量报告的指示(本例假设为不计入)，以及复制传输时流量所计入的RAT信息(当MN和SN的RAT不同且重复部分不计入时需要，本例假设MN为5G RAT，SN为4G RAT，复制传输时流量所计入的RAT为5G)。CN配置粒度为UE、PDU Session、QoS Flow(本例假设配置粒度为PDU Session)。
在步骤702中，MN向SN发送配置信息，所述配置信息包括以下至少之一： UE标识、PDU Session标识、QoS Flow标识、复制传输时重复部分是否计入RAN流量报告的指示(本例假设为不计入)，以及复制传输时流量所计入的RAT信息(当MN和SN的RAT不同且重复部分不计入时需要，本例假设MN为5G RAT，SN为4G RAT，复制传输时流量所计入的RAT为5G)。
在步骤703中，SN针对每个PDCP在SN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vs+Vm-V，重复部分不计入时的4G流量为VrS＝Vs-Vd，重复部分不计入时的5G流量为VrM＝Vm。
在步骤704中，SN向MN发送RAN流量报告，所述RAN流量报告包括SN侧每个PDU Session的以下至少之一：PDU Session标识、该PDU Session所有DRB的V1之和，该PDU Session所有DRB的VrS之和，以及该PDU Session所有DRB的VrM之和。
在步骤705中，MN针对每个PDCP在MN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)，则重复不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vm+Vs-V，重复部分不计入时的5G流量为VrM＝Vm，重复部分不计入时的4G流量为VrS＝Vs-Vd。
在步骤706中，MN向CN发送RAN流量报告，所述RAN流量报告包括每个PDU Session(在MN侧的和在SN侧中至少之一的)的以下至少之一：PDU Session标识、该PDU Session所有DRB的V1之和，该PDU Session所有DRB的VrS之和，以及该PDU Session所有DRB的VrM之和。
即，所述RAN流量报告包括一个列表，该列表包括某UE所有PDU Session(在MN侧的和在SN侧的)的流量信息，该列表的一项表示其中一个PDU Session的流量信息包括：PDU Session标识，重复部分不计入时该PDU Session的4G流量即该PDU Session所有DRB的VrS之和，以及重复部分不计入时该PDU Session的5G流量即该PDU Session所有DRB的VrM之和。
另外，所述流量统计也可以针对PDCP SDU进行，即在流量统计的时候减掉PDCP头的开销。
实施例八
本实施例为双连接场景下，如图8所示，包括：步骤801至步骤806。
在步骤801中，CN向MN发送配置信息，所述配置信息包括以下至少之一：UE标识、PDU Session标识、QoS Flow标识、以及复制传输时重复部分是否计入RAN流量报告的指示(本例假设为计入)。CN配置粒度为UE、PDU Session、QoS Flow(本例假设配置粒度为PDU Session)。
在步骤802中，MN向SN发送配置信息，所述配置信息包括以下至少之一：UE标识、PDU Session标识、QoS Flow标识、以及复制传输时重复部分是否计入RAN流量报告的指示(本例假设为计入)(本例假设MN为5G RAT，SN为4G RAT)。
在步骤803中，SN针对每个PDCP在SN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)，则重复部分计入时的RAN流量为V2＝Vs+Vm，重复部分的RAN流量为Vd＝Vs+Vm-V，重复部分计入时的4G流量为VrS＝Vs，重复部分计入时的5G流量为VrM＝Vm。
在步骤804中，SN向MN发送RAN流量报告，所述RAN流量报告包括SN侧每个PDU Session的以下至少之一：PDU Session标识、该PDU Session所有DRB的V2之和，该PDU Session所有DRB的VrS之和，以及该PDU Session所有DRB的VrM之和。
在步骤805中，MN针对每个PDCP在MN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)，则重复计入时的RAN流量为V2＝Vm+Vs，重复部分的RAN流量为Vd＝Vm+Vs-V，重复部分计入时的5G流量为VrM＝Vm，重复部分计入时的4G流量为VrS＝Vs。
在步骤806中，MN向CN发送RAN流量报告，所述RAN流量报告包括每个PDU Session(在MN侧的和在SN侧中至少之一的)的以下至少之一：PDU Session标识、该PDU Session所有DRB的V2之和，该PDU Session所有DRB的VrS之和，以及该PDU Session所有DRB的VrM之和。
即，所述RAN流量报告包括一个列表，该列表包括某UE所有PDU Session (在MN侧的和在SN侧的)的流量信息，该列表的一项表示其中一个PDU Session的流量信息包括：PDU Session标识，重复部分计入时该PDU Session的4G流量即该PDU Session所有DRB的VrS之和，重复部分计入时该PDU Session的5G流量即该PDU Session所有DRB的VrM之和。
另外，所述流量统计也可以针对PDCP SDU进行，即在流量统计的时候减掉PDCP头的开销。
实施例九
本实施例为双连接场景下，假设MN为5G RAT，SN为4G RAT，如图9所示，包括：步骤901至步骤904。
在步骤901中，SN针对每个PDCP在SN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vs+Vm-V，重复部分计入时的RAN流量为V2＝Vs+Vm。
在步骤902中，SN向MN发送RAN流量报告，所述RAN流量报告包括每个PDCP在SN侧的DRB的以下至少之一：V1，V2，Vd，Vs，以及Vm。
在步骤903中，MN针对每个PDCP在MN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vm+Vs-V，重复部分计入时的RAN流量为V2＝Vm+Vs。
在步骤904中，MN向CN发送RAN流量报告，所述RAN流量报告包括以下至少之一：
UE标识、该UE所有DRB(MN侧的和SN侧的)的V1之和(重复部分不计入)；
UE标识，该UE所有DRB(MN侧的和SN侧的)的V2之和(重复部分计入)；
UE标识，该UE的重复部分流量即该UE所有DRB(MN侧的和SN侧的)的Vd之和；
PDU Session标识、该PDU Session所有DRB(MN侧的和SN侧中的至少 之一的)的V1之和(重复部分不计入)；
PDU Session标识、该PDU Session所有DRB(MN侧的和SN侧中的至少之一的)的V2之和(重复部分计入)；
PDU Session标识、该PDU Session的重复部分流量即该PDU Session所有DRB(MN侧的和SN侧中的至少之一的)的Vd之和；
QoS Flow标识、该QoS Flow所对应DRB(MN侧的或SN侧的)的V1(重复部分不计入，当QoS Flow和DRB为一对一时)；
QoS Flow标识列表、该QoS Flow组所对应DRB(MN侧的或SN侧的)的V1(重复部分不计入，当QoS Flow和DRB为多对一时)；
QoS Flow标识、该QoS Flow所对应DRB(MN侧的或SN侧的)的V2(重复部分计入，当QoS Flow和DRB为一对一时)；
QoS Flow标识列表、该QoS Flow组所对应DRB(MN侧的或SN侧的)的V2(重复部分计入，当QoS Flow和DRB为多对一时)；
QoS Flow标识、该QoS Flow的重复部分流量即该QoS Flow所对应DRB(MN侧的或SN侧的)的Vd(当QoS Flow和DRB为一对一时)；
QoS Flow标识列表、该QoS Flow组的重复部分流量即该QoS Flow组所对应DRB(MN侧的或SN侧的)的Vd(当QoS Flow和DRB为多对一时)。
另外、所述流量统计也可以针对PDCP SDU进行，即在流量统计的时候减掉PDCP头的开销。
实施例十
本实施例为载波聚合场景下的实现，如图10所示，包括：步骤1001、步骤1002和步骤1003。
在步骤1001中，OAM向基站发送配置信息，所述配置信息包括以下至少之一：复制传输时重复部分是否计入RAN流量报告的指示和粒度单元信息。本实施例中，粒度单元为基站。
在步骤1002中，基站针对每个DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给所有RLC的PDCP PDU的流量之和(设为Vr)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vr-V，重复部分计入时的RAN流量为V2＝Vr。
在步骤1003中，所述基站向CN发送RAN流量报告，所述RAN流量报告 包括每个DRB的以下信息：与DRB一一对应的E-RAB的标识，V1(当重复部分不计入时)；或以下信息：与DRB一一对应的E-RAB的标识，V2(当重复部分计入时)。所述RAN流量报告中还可包括Vd。
另外，所述流量统计也可以针对PDCP SDU进行，即在流量统计的时候减掉PDCP头的开销。
实施例十一
本实施例为载波聚合场景下的实现，如图11所示，包括：步骤1101、步骤1102和步骤1103。
在步骤1101中，CN向基站发送配置信息，所述配置信息包括以下至少之一：UE标识、E-RAB标识、复制传输时重复部分是否计入RAN流量报告的指示、以及粒度单元信息。本实施例中，CN可配置的粒度为UE、E-RAB，本例假设粒度单元为E-RAB。
在步骤1102中，所述基站针对每个DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给所有RLC的PDCP PDU的流量之和(设为Vr)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vr-V，重复部分计入时的RAN流量为V2＝Vr。
在步骤1103中，所述基站向CN发送RAN流量报告，所述RAN流量报告包括每个DRB的以下信息：与DRB一一对应的E-RAB的标识，V1(当配置为重复部分不计入时)；或以下信息：与DRB一一对应的E-RAB的标识，V2(当配置为重复部分计入时)。所述RAN流量报告中还可包括Vd。
另外，所述流量统计也可以针对PDCP SDU进行，即在流量统计的时候减掉PDCP头的开销。
实施例十二
本实施例为载波聚合场景下的实现，如图12所示，包括：步骤1201和步骤1202。
在步骤1201中，基站针对每个DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给所有RLC的PDCP PDU的流量之和(设为Vr)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vr-V，重复部分计入时的RAN流量为V2＝Vr。
在步骤1202中，所述基站向CN发送RAN流量报告，所述RAN流量报告包括每个DRB的以下至少之一：与DRB一一对应的E-RAB的标识，V1，V2，Vd。
另外，所述流量统计也可以针对PDCP SDU进行，即在流量统计的时候减掉PDCP头的开销。
实施例十三
本实施例为载波聚合场景下的实现，如图13所示，包括：步骤1301、步骤1302和步骤1303。
在步骤1301中，CN向基站发送配置信息，所述配置信息包括以下至少之一：UE标识、PDU Session标识、QoS Flow标识、复制传输时重复部分是否计入RAN流量报告的指示、以及粒度单元信息。CN配置粒度为UE、PDU Session、QoS Flow(本例假设粒度单元为PDU Session)。
在步骤1302中，所述基站针对每个DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给所有RLC的PDCP PDU的流量之和(设为Vr)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vr-V，重复部分计入时的RAN流量为V2＝Vr。
在步骤1303中，所述基站向所述CN发送RAN流量报告，所述RAN流量报告包括UE每个PDU Session以下至少之一：
PDU Session标识、该PDU Session所有DRB的V1之和(当配置信息中携带重复部分不计入指示时)；
PDU Session标识、该PDU Session所有DRB的V2之和(当配置信息中携带重复部分计入指示时)。
另外，所述流量统计也可以针对PDCP SDU进行，即在流量统计的时候减掉PDCP头的开销。
实施例十四
本实施例为载波聚合场景下的实现，如图14所示，包括：步骤1401和步骤1402。
在步骤1401中，基站针对每个DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给所有RLC的PDCP PDU的流量之和(设为Vr)， 则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vr-V，重复部分计入时的RAN流量为V2＝Vr。
在步骤1402中，所述基站向CN发送RAN流量报告，所述RAN流量报告包括以下至少之一：
UE标识、该UE所有DRB的V1之和(重复部分不计入时)；
UE标识，该UE所有DRB的V2之和(重复部分计入时)；
UE标识，该UE的重复部分流量即该UE所有DRB的Vd之和；
PDU Session标识、该PDU Session所有DRB的V1之和(重复部分不计入时)；
PDU Session标识、该PDU Session所有DRB的V2之和(重复部分计入时)；
PDU Session标识，该PDU Session的重复部分流量即该PDU Session所有DRB的Vd之和；
QoS Flow标识、该QoS Flow所对应DRB的V1(重复部分不计入，当QoS Flow和DRB为一对一时)；
QoS Flow标识列表、该QoS Flow组所对应DRB的V1(重复部分不计入，当QoS Flow和DRB为多对一时)；
QoS Flow标识、该QoS Flow所对应DRB的V2(重复部分计入，当QoS Flow和DRB为一对一时)；
QoS Flow标识列表、该QoS Flow组所对应DRB的V2(重复部分计入，当QoS Flow和DRB为多对一时)；
QoS Flow标识、该QoS Flow的重复部分流量即该QoS Flow所对应DRB的Vd(当QoS Flow和DRB为一对一时)；
QoS Flow标识列表、该QoS Flow组的重复部分流量即该QoS Flow组所对应DRB的Vd(当QoS Flow和DRB为多对一时)。
另外，所述流量统计也可以针对PDCP SDU进行，即在流量统计的时候减掉PDCP头的开销。
实施例十五
本实施例为载波聚场景下的实现，如图15所示，包括：步骤1501至步骤1505。
在步骤1501中，CN向基站CU-CP(集中单元控制面)发送配置信息，配 置信息包括以下至少之一：UE标识、PDU Session标识、QoS Flow标识、复制传输时重复部分是否计入RAN流量报告的指示、以及粒度单元信息。CN配置粒度为UE、PDU Session、QoS Flow(本例假设粒度单元为PDU Session)。
在步骤1502中，基站CU-CP向基站CU-UP(集中单元用户面)发送配置信息，配置信息包括以下至少之一：UE标识、PDU Session标识、QoS Flow标识、复制传输时重复部分是否计入RAN流量报告的指示、以及粒度单元信息。CN配置粒度为UE、PDU Session、QoS Flow(本例假设粒度单元为PDU Session)。
在步骤1503中，所述基站CU-UP针对每个DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给所有RLC的PDCP PDU的流量之和(设为Vr)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vr-V，重复部分计入时的RAN流量为V2＝Vr。
在步骤1504中，所述基站CU-UP向所述基站CU-CP发送RAN流量报告，所述RAN流量报告包括UE每个PDU Session以下至少之一：
PDU Session标识、该PDU Session所有DRB的V1之和(当配置信息中携带重复部分不计入指示时)；
PDU Session标识、该PDU Session所有DRB的V2之和(当配置信息中携带重复部分计入指示时)。
在步骤1505中，所述基站CU-CP向所述CN发送RAN流量报告，所述RAN流量报告包括UE每个PDU Session以下至少之一：
PDU Session标识、该PDU Session所有DRB的V1之和(当配置信息中携带重复部分不计入指示时)；
PDU Session标识、该PDU Session所有DRB的V2之和(当配置信息中携带重复部分计入指示时)。
另外，所述流量统计也可以针对PDCP SDU进行，即在流量统计的时候减掉PDCP头的开销。
需要说明的是，在另一实施例中，也可由OAM向基站CU-CP发送配置信息。在另一实施例中，CN或OAM也可以不发送配置信息给基站CU-CP。
需要说明的是，其他实施例中，粒度单元也可以为UE、QoS Flow等，实现方法类似，此处不再赘述。
实施例十六
如图16所示，包括：步骤1601至步骤1608。
在步骤1601中，CN向MN发送配置信息。
所述配置信息包括以下至少之一：UE标识、E-RAB标识、复制传输时重复部分是否计入RAN流量报告的指示(本例假设为不计入)，以及复制传输时流量所计入的RAT信息(当MN和SN的RAT不同且重复部分不计入时需要，本例假设MN为4G RAT，SN为5G RAT，复制传输时流量所计入的RAT为5G)。CN配置粒度为UE、E-RAB(本例假设配置粒度为E-RAB，且所有E-RAB都配置为不计入)。
在步骤1602中，MN向SN的CU-CP(集中单元控制面)发送配置信息，所述配置包括以下至少之一：UE标识、E-RAB标识、复制传输时重复部分是否计入RAN流量报告的指示(本例假设为不计入)，以及复制传输时重复部分所计入的RAT信息(当MN和SN的RAT不同且重复部分不计入时需要，本例假设MN为4G RAT，SN为5G RAT，复制传输时重复部分所计入的RAT为5G)。
在步骤1603中，SN的CU-CP向SN的CU-UP(集中单元用户面)发送配置信息，所述配置包括以下至少之一：UE标识、E-RAB标识、复制传输时重复部分是否计入RAN流量报告的指示(本例假设为不计入)，以及复制传输时重复部分所计入的RAT信息(当MN和SN的RAT不同且重复部分不计入时需要，本例假设MN为4G RAT，SN为5G RAT，复制传输时重复部分所计入的RAT为5G)。
在步骤1604中，SN的CU-UP针对每个PDCP在SN侧的DRB进行统计：PDCP生成的PDCP PDU的流量(设为V)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vs+Vm-V，重复部分不计入时的5G流量为VrS＝Vs，重复部分不计入时的4G流量为VrM＝Vm-Vd。
在步骤1605中，SN的CU-UP向SN的CU-CP发送RAN流量报告，所述RAN流量报告包括每个PDCP在SN侧的DRB的以下至少之一：V1，VrS，以及VrM。
在步骤1606中，SN的CU-CP向MN发送RAN流量报告，所述RAN流量报告包括每个PDCP在SN侧的DRB的以下至少之一：V1，VrS，以及VrM。
在步骤1607中，MN针对每个PDCP在MN侧的DRB进行统计：PDCP生 成的PDCP PDU的流量(设为V)、PDCP下发给MN侧RLC的PDCP PDU的流量(设为Vm，可以为0)、PDCP下发给SN侧RLC的PDCP PDU的流量(设为Vs，可以为0)，则重复部分不计入时的RAN流量为V1＝V，重复部分的RAN流量为Vd＝Vm+Vs-V，重复部分不计入时的4G流量为VrM＝Vm-Vd，重复部分不计入时的5G流量为VrS＝Vs。
在步骤1608中，MN向CN发送RAN流量报告，所述RAN流量报告包括每个DRB(PDCP在MN侧的和PDCP在SN侧中的至少之一的)的以下至少之一：与DRB一一对应的E-RAB的标识，V1，VrS，以及VrM。
另外，所述流量统计也可以针对PDCP SDU进行，即在流量统计的时候减掉PDCP头的开销。
需要说明的是，在另一实施例中，也可由OAM向MN发送配置信息。在另一实施例中，CN或OAM也可以不发送配置信息给MN。
在另一实施例中，粒度单元也可以是其他，比如UE，PDU Session，QoS Flow，QoS Flow组等。
实施例十七
如图17所示，包括：步骤1701和步骤1702。
在步骤1701中，DRB对应RLC所在节点向DRB对应PDCP所在节点发送第一接口数据传递状态报告，所述第一接口数据传递状态报告包含第一接口上丢失的数据包的信息，当双连接时第一接口为X2或Xn接口，当CU DU分离时第一接口为F1接口。
在步骤1702中，DRB对应PDCP所在节点针对该DRB进行统计，在统计PDCP生成的PDCP PDU的流量时减去第一接口上丢失的数据包的流量，在统计PDCP下发给RLC的PDCP PDU的流量时减去第一接口上丢失的数据包的流量。
另外，所述流量统计也可以针对PDCP SDU进行，即在流量统计的时候减掉PDCP头的开销。
实施例十八
在步骤1801中，DRB对应PDCP所在节点针对该DRB进行统计，在统计PDCP生成的PDCP PDU的流量时减去PDCP已决定丢弃的数据包的流量，在 统计PDCP下发给RLC的PDCP PDU的流量时减去PDCP已决定丢弃的数据包的流量。
另外，所述流量统计也可以针对PDCP SDU进行，即在流量统计的时候减掉PDCP头的开销。
需要说明的是，上述实施例中用双连接场景和载波聚合场景进行举例，但本申请不限于此，其他场景也可使用上述流量报告方法，没有复制传输时，相当于重复部分为0。
如图18所示，本申请一实施例提供一种无线接入网流量报告装置180，包括存储器1810和处理器1820，所述存储器1810存储有程序，所述程序在被所述处理器1820读取执行时，执行以下操作：
获取数据无线承载的如下流量信息：PDCP生成的PDCP PDU或PDCP SDU的流量、PDCP下发给RLC的PDCP PDU或PDCP SDU的流量；
根据所述数据无线承载的流量信息生成无线接入网流量报告，所述无线接入网流量报告包括以下至少之一：重复部分不计入时粒度单元的RAN流量、重复部分计入时该粒度单元的RAN流量、以及该粒度单元重复部分的RAN流量；
发送所述无线接入网流量报告给核心网。
在另一实施例中，所述程序在被所述处理器1820读取执行时，还实现上述任一实施例中所述的无线接入网流量报告方法。
本申请一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现上述任一实施例中所述的无线接入网流量报告方法。
所述计算机可读存储介质包括：U盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、移动硬盘、磁碟或者光盘等多种可以存储程序代码的介质。
本申请一实施例还提供一种无线接入网流量报告系统，包括基站和核心网，其中：
所述基站设置为，获取数据无线承载的流量信息，其中所述数据无线承载的流量信息包括：PDCP生成的PDCP PDU或PDCP SDU的流量、PDCP下发给无线链路控制的PDCP PDU或PDCP SDU的流量；根据所述数据无线承载的流量信息生成无线接入网流量报告，发送所述无线接入网流量报告给核心网，其中所述无线接入网流量报告包括以下至少之一：重复部分不计入时粒度单元 的RAN流量、重复部分计入时该粒度单元的RAN流量、以及该粒度单元重复部分的RAN流量；
所述核心网设置为，接收所述基站发送的所述无线接入网流量报告。
在一实施例中，所述核心网还设置为，发送配置信息至所述基站，所述配置信息包括以下至少之一：复制传输时重复部分是否计入无线接入网流量报告的指示、粒度单元信息；所述基站设置为通过以下方式来根据所述数据无线承载的流量信息生成无线接入网流量报告：根据所述数据无线承载的流量信息和所述配置信息生成所述无线接入网流量报告。
在一实施例中，所述基站包括主基站和辅基站；
所述辅基站设置为，获取每个PDCP在辅基站侧的信息，其中每个PDCP在辅基站侧的信息包括：PDCP生成的PDCP PDU或PDCP SDU的流量、PDCP下发给主基站侧无线链路控制的PDCP PDU或PDCP SDU的流量、PDCP下发给辅基站侧无线链路控制的PDCP PDU或PDCP SDU的流量；生成第一无线接入网流量报告，发送所述第一无线接入网流量报告给所述主基站，所述第一无线接入网流量报告包括粒度单元的标识信息，还包括辅基站侧的以下至少之一：重复部分不计入时所述粒度单元的无线接入网流量、重复部分不计入时所述粒度单元在主基站侧无线接入技术的流量、重复部分不计入时所述粒度单元在辅基站侧无线接入技术的流量、重复部分计入时所述粒度单元的无线接入网流量、重复部分计入时所述粒度单元在主基站侧无线接入技术的流量、重复部分计入时所述粒度单元在辅基站侧无线接入技术的流量、以及所述粒度单元重复部分的无线接入网流量；
所述主基站设置为，获取每个PDCP在主基站侧的信息，其中每个PDCP在辅基站侧的信息包括：PDCP生成的PDCP PDU的流量、PDCP下发给主基站侧无线链路控制的PDCP PDU的流量、PDCP下发给辅基站侧无线链路控制的PDCP PDU的流量；生成第二无线接入网流量报告，发送所述第二无线接入网流量报告给所述核心网，所述第二无线接入网流量报告包括粒度单元的标识信息，还包括以下至少之一：
重复部分不计入时所述粒度单元的无线接入网流量、重复部分不计入时所述粒度单元在主基站侧无线接入技术的流量、重复部分不计入时所述粒度单元在辅基站侧无线接入技术的流量、重复部分计入时所述粒度单元的无线接入网流量、重复部分计入时所述粒度单元在主基站侧无线接入技术的流量、重复部 分计入时所述粒度单元在辅基站侧无线接入技术的流量、以及所述粒度单元重复部分的无线接入网流量。
所述基站和核心网的其他功能请参考前述实施例，此处不再赘述。
与相关技术相比，本申请至少一实施例提供了一种复制传输时，无线接入网流量的报告实现方案，满足运营商需求。

Claims (14)

  1. 一种无线接入网流量报告方法，包括：
    基站获取数据无线承载的流量信息，其中所述数据无线承载的流量信息包括：分组数据会聚协议PDCP生成的分组数据会聚协议协议数据单元PDCP PDU或分组数据会聚协议服务数据单元PDCP SDU的流量、PDCP下发给无线链路控制的PDCP PDU或PDCP SDU的流量；
    所述基站根据所述数据无线承载的流量信息生成无线接入网流量报告，其中所述无线接入网流量报告包括以下至少之一：重复部分不计入时粒度单元的无线接入网流量、重复部分计入时所述粒度单元的无线接入网流量、以及所述粒度单元重复部分的无线接入网流量；
    所述基站发送所述无线接入网流量报告给核心网。
  2. 如权利要求1所述的方法，其中，所述基站包括主基站和辅基站；
    所述基站获取数据无线承载的流量信息包括：
    所述主基站获取每个PDCP在主基站侧的信息，其中所述每个PDCP在主基站侧的信息包括：PDCP生成的PDCP PDU或PDCP SDU的流量、PDCP下发给主基站侧无线链路控制的PDCP PDU或PDCP SDU的流量、以及PDCP下发给辅基站侧无线链路控制的PDCP PDU或PDCP SDU的流量；
    所述辅基站获取每个PDCP在辅基站侧的信息，其中所述每个PDCP在辅基站侧的信息包括：PDCP生成的PDCP PDU或PDCP SDU的流量、PDCP下发给主基站侧无线链路控制的PDCP PDU或PDCP SDU的流量、以及PDCP下发给辅基站侧无线链路控制的PDCP PDU或PDCP SDU的流量；
    所述基站根据所述数据无线承载的流量信息生成无线接入网流量报告包括：
    所述辅基站生成第一无线接入网流量报告，发送所述第一无线接入网流量报告给所述主基站，所述第一无线接入网流量报告包括粒度单元的标识信息，还包括辅基站侧的以下至少之一：
    重复部分不计入时粒度单元的无线接入网流量、重复部分不计入时所述粒度单元在主基站侧无线接入技术的流量、重复部分不计入时所述粒度单元在辅基站侧无线接入技术的流量、重复部分计入时所述粒度单元的无线接入网流量、重复部分计入时所述粒度单元在主基站侧无线接入技术的流量、重复部分计入时所述粒度单元在辅基站侧无线接入技术的流量、以及所述粒度单元重复部分的无线接入网流量；
    所述主基站生成第二无线接入网流量报告，所述第二无线接入网流量报告 包括粒度单元的标识信息，还包括以下至少之一：
    重复部分不计入时所述粒度单元的无线接入网流量、重复部分不计入时所述粒度单元在主基站侧无线接入技术的流量、重复部分不计入时所述粒度单元在辅基站侧无线接入技术的流量、重复部分计入时所述粒度单元的无线接入网流量、重复部分计入时所述粒度单元在主基站侧无线接入技术的流量、重复部分计入时所述粒度单元在辅基站侧无线接入技术的流量、以及所述粒度单元重复部分的无线接入网流量；
    所述基站发送所述无线接入网流量报告给核心网包括：
    所述主基站发送所述第二无线接入网流量报告给所述核心网。
  3. 如权利要求2所述的方法，其中，所述辅基站包括辅基站集中单元控制面和辅基站集中单元用户面；
    所述辅基站获取每个PDCP在辅基站侧的信息包括：
    所述辅基站集中单元用户面获取所述每个PDCP在辅基站侧的信息；
    所述辅基站生成第一无线接入网流量报告，发送所述第一无线接入网流量报告给所述主基站包括：
    所述辅基站集中单元用户面生成第一无线接入网流量报告，发送所述第一无线接入网流量报告给所述辅基站集中单元控制面；所述辅基站集中单元控制面发送所述第一无线接入网流量报告给所述主基站。
  4. 如权利要求1所述的方法，其中，所述基站包括基站集中单元控制面和基站集中单元用户面；
    所述基站获取数据无线承载的流量信息包括：
    所述基站集中单元用户面获取每个PDCP的信息，其中所述每个PDCP的信息包括：PDCP生成的PDCP PDU或PDCP SDU的流量、PDCP下发给无线链路控制的PDCP PDU或PDCP SDU的流量；
    所述基站根据所述数据无线承载的流量信息生成无线接入网流量报告包括：
    所述基站集中单元用户面生成无线接入网流量报告，发送所述无线接入网流量报告给所述基站集中单元控制面；
    所述基站发送所述无线接入网流量报告给核心网包括：
    所述基站集中单元控制面发送所述无线接入网流量报告给所述核心网。
  5. 如权利要求1所述的方法，其中，所述粒度单元包括以下至少之一：
    用户设备、演进通用陆地无线接入网无线接入承载、协议数据单元会话、 服务质量流、以及服务质量流组。
  6. 如权利要求1至5任一项所述的方法，还包括，所述基站接收所述核心网或者网络管理操作维护发送的配置信息，所述配置信息包括以下至少之一：复制传输时重复部分是否计入无线接入网流量报告的指示和粒度单元信息；
    所述基站根据所述数据无线承载的流量信息生成无线接入网流量报告包括：
    所述基站根据所述数据无线承载的流量信息和所述配置信息生成所述无线接入网流量报告。
  7. 如权利要求1至5任一项所述的方法，其中，所述基站包括主基站和辅基站，所述方法还包括：
    所述主基站接收所述核心网或者网络管理操作维护发送的第一配置信息，所述第一配置信息包括以下至少之一：复制传输时重复部分是否计入无线接入网流量报告的指示、复制传输时流量所计入的无线接入技术信息、以及粒度单元信息；
    所述主基站发送第二配置信息给所述辅基站，所述第二配置信息包括以下至少之一：复制传输时重复部分是否计入无线接入网流量报告的指示、复制传输时流量所计入的无线接入技术信息、以及粒度单元信息；
    所述基站根据所述数据无线承载的流量信息生成无线接入网流量报告包括：
    所述辅基站根据所述数据无线承载的流量信息和所述第二配置信息生成第一无线接入网流量报告；所述主基站根据所述数据无线承载的流量信息和所述第一配置信息生成第二无线接入网流量报告。
  8. 如权利要求1至5任一项所述的方法，其中，所述获取PDCP下发给无线链路控制的PDCP PDU或PDCP SDU的流量包括：
    数据无线承载对应的PDCP和无线链路控制不在同一节点时，获取PDCP下发给无线链路控制的PDCP PDU或PDCP SDU的流量时，去除PDCP所在节点与无线链路控制所在节点间接口上丢失的数据包的流量。
  9. 如权利要求1至5任一项所述的方法，其中，
    所述获取PDCP下发给无线链路控制的PDCP PDU或PDCP SDU的流量包括：
    获取PDCP下发给无线链路控制的PDCP PDU或PDCP SDU的流量时，去除所述PDCP已决定丢弃的数据包的流量。
  10. 一种无线接入网流量报告装置，包括存储器和处理器，所述存储器存 储有程序，所述程序在被所述处理器读取执行时，实现如权利要求1至9任一项所述的无线接入网流量报告方法。
  11. 一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现如权利要求1至9任一项所述的无线接入网流量报告方法。
  12. 一种无线接入网流量报告系统，包括基站和核心网，其中：
    所述基站设置为，获取数据无线承载的流量信息，其中所述数据无线承载的流量信息包括：PDCP生成的PDCP PDU或PDCP SDU的流量、PDCP下发给无线链路控制的PDCP PDU或PDCP SDU的流量；根据所述数据无线承载的流量信息生成无线接入网流量报告，发送所述无线接入网流量报告给核心网，其中所述无线接入网流量报告包括以下至少之一：重复部分不计入时粒度单元的无线接入网流量、重复部分计入时所述粒度单元的无线接入网流量、以及所述粒度单元重复部分的无线接入网流量；
    所述核心网设置为，接收所述基站发送的所述无线接入网流量报告。
  13. 如权利要求12所述的系统，其中，
    所述核心网还设置为，发送配置信息至所述基站，其中所述配置信息包括以下至少之一：复制传输时重复部分是否计入无线接入网流量报告的指示和粒度单元信息；
    所述基站设置为通过以下方式来根据所述数据无线承载的流量信息生成无线接入网流量报告：根据所述数据无线承载的流量信息和所述配置信息生成所述无线接入网流量报告。
  14. 如权利要求12或13所述的系统，其中，
    所述基站包括主基站和辅基站；
    所述辅基站设置为，获取每个PDCP在辅基站侧的信息，其中每个PDCP在辅基站侧的信息包括：PDCP生成的PDCP PDU或PDCP SDU的流量、PDCP下发给主基站侧无线链路控制的PDCP PDU或PDCP SDU的流量、PDCP下发给辅基站侧无线链路控制的PDCP PDU或PDCP SDU的流量；生成第一无线接入网流量报告，发送所述第一无线接入网流量报告给所述主基站，其中所述第一无线接入网流量报告包括粒度单元的标识信息，还包括辅基站侧的以下至少之一：重复部分不计入时所述粒度单元的无线接入网流量、重复部分不计入时所述粒度单元在主基站侧无线接入技术的流量、重复部分不计入时所述粒度单 元在辅基站侧无线接入技术的流量、重复部分计入时所述粒度单元的无线接入网流量、重复部分计入时所述粒度单元在主基站侧无线接入技术的流量、重复部分计入时所述粒度单元在辅基站侧无线接入技术的流量、以及所述粒度单元重复部分的无线接入网流量；
    所述主基站设置为，获取每个PDCP在主基站侧的信息，其中每个PDCP在主基站侧的信息包括：PDCP生成的PDCP PDU的流量、PDCP下发给主基站侧无线链路控制的PDCP PDU的流量、PDCP下发给辅基站侧无线链路控制的PDCP PDU的流量；生成第二无线接入网流量报告，发送所述第二无线接入网流量报告给所述核心网，其中所述第二无线接入网流量报告包括粒度单元的标识信息，还包括以下至少之一：
    重复部分不计入时所述粒度单元的无线接入网流量、重复部分不计入时所述粒度单元在主基站侧无线接入技术的流量、重复部分不计入时所述粒度单元在辅基站侧无线接入技术的流量、重复部分计入时所述粒度单元的无线接入网流量、重复部分计入时所述粒度单元在主基站侧无线接入技术的流量、重复部分计入时所述粒度单元在辅基站侧无线接入技术的流量、以及所述粒度单元重复部分的无线接入网流量。
PCT/CN2019/070937 2018-03-16 2019-01-09 无线接入网流量报告方法以及装置和系统、存储介质 WO2019174386A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19766744.7A EP3749010A4 (en) 2018-03-16 2019-01-09 METHOD, APPARATUS AND SYSTEM FOR REPORTING RADIO ACCESS NETWORK TRAFFIC, AND MEMORY MEDIUM
US16/977,872 US11223968B2 (en) 2018-03-16 2019-01-09 Method, apparatus and system for reporting radio access network traffic

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810219173.0 2018-03-16
CN201810219173.0A CN110278581B (zh) 2018-03-16 2018-03-16 一种无线接入网流量报告方法、装置和系统、存储介质

Publications (1)

Publication Number Publication Date
WO2019174386A1 true WO2019174386A1 (zh) 2019-09-19

Family

ID=67907358

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/070937 WO2019174386A1 (zh) 2018-03-16 2019-01-09 无线接入网流量报告方法以及装置和系统、存储介质

Country Status (4)

Country Link
US (1) US11223968B2 (zh)
EP (1) EP3749010A4 (zh)
CN (1) CN110278581B (zh)
WO (1) WO2019174386A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4187942A4 (en) * 2020-08-04 2023-11-29 Huawei Technologies Co., Ltd. BILLING PROCESSING METHOD, SYSTEM, AND ASSOCIATED DEVICE

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247238A (zh) * 2007-02-14 2008-08-20 华为技术有限公司 数据流量统计的方法及系统
CN102300264A (zh) * 2011-08-22 2011-12-28 中国电信股份有限公司 无线网络的流量控制方法和系统
CN102638781A (zh) * 2012-03-09 2012-08-15 华为技术有限公司 分流数据的计费方法及无线接入设备、网关设备
US20160359695A1 (en) * 2015-06-04 2016-12-08 Cisco Technology, Inc. Network behavior data collection and analytics for anomaly detection
CN106686660A (zh) * 2015-11-06 2017-05-17 北京三星通信技术研究有限公司 一种流量控制方法及设备
CN107623611A (zh) * 2017-09-22 2018-01-23 国云科技股份有限公司 一种云平台虚拟机的流量监控系统

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7796505B2 (en) * 2005-01-26 2010-09-14 M-Stack Limited Method for processing traffic data in a wireless communications system
CN100550906C (zh) * 2005-11-24 2009-10-14 大唐移动通信设备有限公司 无线链路层的流量控制方法
FI20065859A0 (fi) * 2006-12-28 2006-12-28 Nokia Corp MBMS parannus
JP2012134829A (ja) * 2010-12-22 2012-07-12 Panasonic Mobile Communications Co Ltd 通信端末装置及びデータ量報告方法
EP2723134B1 (en) * 2012-10-18 2014-11-26 Fujitsu Limited Wireless communication in Multi-RAT System
US10142799B2 (en) * 2014-08-19 2018-11-27 Qualcomm Incorporated Multicasting traffic using multi-connectivity
JPWO2017022388A1 (ja) * 2015-07-31 2018-05-17 株式会社Ｎｔｔドコモ 基地局、データ通信量管理装置、データ通信量報告方法、及びデータ通信量取得方法
CN106230810B (zh) * 2016-07-29 2019-07-02 南京优速网络科技有限公司 动静态流量分析方法
CN112616161B (zh) * 2017-06-15 2022-08-26 华为技术有限公司 一种通信处理方法和通信装置
CN107342851B (zh) * 2017-06-15 2020-05-26 电信科学技术研究院 一种重复传输的配置及重复传输方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247238A (zh) * 2007-02-14 2008-08-20 华为技术有限公司 数据流量统计的方法及系统
CN102300264A (zh) * 2011-08-22 2011-12-28 中国电信股份有限公司 无线网络的流量控制方法和系统
CN102638781A (zh) * 2012-03-09 2012-08-15 华为技术有限公司 分流数据的计费方法及无线接入设备、网关设备
US20160359695A1 (en) * 2015-06-04 2016-12-08 Cisco Technology, Inc. Network behavior data collection and analytics for anomaly detection
CN106686660A (zh) * 2015-11-06 2017-05-17 北京三星通信技术研究有限公司 一种流量控制方法及设备
CN107623611A (zh) * 2017-09-22 2018-01-23 国云科技股份有限公司 一种云平台虚拟机的流量监控系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3749010A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4187942A4 (en) * 2020-08-04 2023-11-29 Huawei Technologies Co., Ltd. BILLING PROCESSING METHOD, SYSTEM, AND ASSOCIATED DEVICE

Also Published As

Publication number Publication date
EP3749010A1 (en) 2020-12-09
US20210029568A1 (en) 2021-01-28
US11223968B2 (en) 2022-01-11
CN110278581A (zh) 2019-09-24
CN110278581B (zh) 2021-09-28
EP3749010A4 (en) 2022-01-12

Similar Documents

Publication Publication Date Title
US11057797B2 (en) Method and device for processing information
CN108024294B (zh) 切换方法及装置
CN109548090B (zh) QoS控制方法及设备
CN107925905B (zh) 用于处理向wlan载波卸载drb的方法和无线通信系统
CN108306708B (zh) 一种数据包处理方法及装置
KR102380004B1 (ko) 이중 접속에서 데이터를 분할 베어러에 할당하기 위한 방법 및 장치
EP3761681B1 (en) Multi-connection data amount reporting method
CN103874128B (zh) 配置ue的聚合最大速率的方法
CN107484183B (zh) 一种分布式基站系统、cu、du及数据传输方法
WO2015176462A1 (zh) 双连接无线承载的迁移处理、迁移方法及装置
CN108337633B (zh) 数据分流配置方法、基站系统和用户终端
US11382052B2 (en) Synchronization method and apparatus, network element, and storage medium
CN104955109A (zh) 配置UE的聚合最大速率的方法、协调non-GBR业务的聚合速率及基站
KR20190017026A (ko) 다중연결 통신 방법 및 디바이스
CN104066133A (zh) 一种支持切换的方法
CN109246833B (zh) 承载配置确定、信息发送方法及装置、主基站和辅基站
WO2015123939A1 (zh) 一种信息交互方法、系统以及基站
WO2020063438A1 (zh) 一种协调重复传输的方法
CN109688631B (zh) 一种连接处理方法和设备
CN104685959B (zh) 具有统一接口的无源无线电链路控制实体
US9596620B2 (en) Congestion processing method, apparatus, and core network
WO2019174386A1 (zh) 无线接入网流量报告方法以及装置和系统、存储介质
WO2019062866A1 (zh) 数据传输方法和数据传输装置
CN113950079A (zh) 一种数据传输的方法和节点
EP3453205B1 (en) Security context escrowing

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: 19766744

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019766744

Country of ref document: EP

Effective date: 20200902

NENP Non-entry into the national phase

Ref country code: DE