WO2019242578A1 - 一种性能数据统计方法及相关设备 - Google Patents

一种性能数据统计方法及相关设备 Download PDF

Info

Publication number
WO2019242578A1
WO2019242578A1 PCT/CN2019/091517 CN2019091517W WO2019242578A1 WO 2019242578 A1 WO2019242578 A1 WO 2019242578A1 CN 2019091517 W CN2019091517 W CN 2019091517W WO 2019242578 A1 WO2019242578 A1 WO 2019242578A1
Authority
WO
WIPO (PCT)
Prior art keywords
functional entity
control plane
performance data
plane functional
user plane
Prior art date
Application number
PCT/CN2019/091517
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 华为技术有限公司
Publication of WO2019242578A1 publication Critical patent/WO2019242578A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • 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

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a performance data statistics method and related equipment.
  • the core network equipment of the fourth generation mobile communication system includes a serving gateway (SGW), a packet data network gateway (PDN-GW or PGW), and a traffic detection function. TDF) entity.
  • SGW serving gateway
  • PDN-GW packet data network gateway
  • TDF traffic detection function
  • the main functions of the SGW include: as a local anchor point during eNodeB handover and assisting in completing the reordering function of eNodeB; as a mobility anchor point when switching between 3GPP different access systems; performing legal interception Function; routing and forwarding of data packets; marking packets in the uplink and downlink transport layers; used for billing between operators, etc.
  • TDF belongs to the position of the SGI interface connected between the PGW and the Internet. It is used to identify and detect the type of service and trigger an event to be reported to the policy and charging rules function unit (PCRF) in order to implement the policy update of the PGW. .
  • PCRF policy and charging rules function unit
  • SGW, PGW, and TDF are divided into control plane functional entities SGW-C, PGW-C, TDF-C, and user plane functional entities.
  • the control plane functional entity is used to manage the user plane functional entity or implement other non-session level management functions.
  • the user plane functional entity is used to provide services for the control plane functional entity. For example, the user plane functional entity may establish a session bearer according to a control instruction issued by the control plane to complete the forwarding of user data.
  • One control plane functional entity can manage multiple user plane functional entities, and one user plane functional entity can provide services for multiple control plane functional entities.
  • Figure 2 takes the control plane functional entity as SGW-C and the user plane functional entity as SGW-U as an example.
  • SGW-C1 manages SGW-U1 and SGW-U2
  • SGW-C2 manages SGW-U2 and SGW-U3
  • SGW-C3 manages SGW-U3 and SGW-U4.
  • one PGW-C can also manage multiple PGW-Us, and one PGW-U can provide services for multiple PGW-Cs.
  • One TDF-C can also manage multiple TDF-Us, and one TDF-U can provide services for multiple TDF-Cs.
  • the fifth generation mobile communication system has readjusted the network architecture of the next generation core network equipment.
  • the network architecture of the 5G core network device includes a session management function (SMF) and a user plane function (UPF).
  • SMF is the control plane functional entity.
  • SMF is used to manage UPF.
  • SMF needs to be responsible for managing UPF selection, policy release, event reporting, UPF heartbeat check, UPF load reporting and other non-session level management functions.
  • the UPF is used to provide services to the SMF.
  • the UPF can establish a session bearer according to control instructions issued by the SMF, and complete the forwarding of user data.
  • one SMF can manage multiple UPFs.
  • One UPF can serve multiple SMFs at the same time.
  • the existing operations support system (operations support system, OSS) needs to connect to all control plane function entities to observe the performance indicators of the system, to obtain control plane performance data, and to connect to all user plane functions.
  • OSS operations support system
  • the user plane performance data collected by a user plane functional entity is obtained by statistics of all packets on the user plane functional entity. For example, as shown in Figure 4, UPF2 counts the message kilobytes based on all the messages on UPF2. This causes the OSS to be unable to distinguish the user plane performance data corresponding to SMF1 and SMF2 in UPF2, which makes it impossible for each
  • the user plane performance data corresponding to the SMF is analyzed. Therefore, how to perform statistics on the user plane performance data corresponding to the control plane functional entities is an urgent problem to be solved.
  • This application provides a performance data statistics method and related equipment, which can perform statistics on user plane performance data corresponding to a control plane functional entity.
  • the present application provides a performance data statistics method.
  • the method is applied to a user plane functional entity.
  • the method includes receiving first information, where the first information is used to indicate a user corresponding to the first control plane functional entity.
  • the surface performance data is counted, and the first information carries the identifier of the first control plane functional entity; when it is determined that the session belongs to the first control plane functional entity according to the identifier of the control plane functional entity to which the session belongs, according to the session information
  • the performance statistics of the packets are collected; the performance data obtained by the statistics is used as the user plane performance data corresponding to the first control plane functional entity.
  • the user plane functional entity can perform statistics on the user plane performance data corresponding to the control plane functional entity.
  • the user plane function entity when it receives the first message, it determines the session in which the first message is located, and the first message is any message received; according to the control plane function entity that the session carries, Identification, when determining that the session belongs to the first control plane functional entity, the specific implementation of the statistical performance data according to the message under the session is: when determining according to the identification of the belonging control plane functional entity carried in the session in which the first message belongs When the session where the first message belongs belongs to the first control plane functional entity, the performance data is counted according to the first message.
  • the user plane functional entity can accurately determine a message belonging to the session of the first control plane functional entity, and statistics on the user plane performance data corresponding to the first control plane functional entity according to the message.
  • the first information is used to indicate that the user plane performance data corresponding to the first control plane functional entity and the first instance is counted, and the first information also carries an identifier of the first instance; when according to the belonging control carried in the session,
  • the specific implementation of the identification of the surface function entity to determine that the session belongs to the first control surface function entity according to the message under the session is as follows: According to the identification of the control surface function entity and the instance Identification, when determining that the session belongs to the first control plane functional entity and the first instance, the performance data is counted according to the message under the session; the performance data obtained as statistics is used as the specific implementation of the user plane performance data corresponding to the first control plane functional entity
  • the method is as follows: the statistical performance data is used as the user plane performance data corresponding to the first control plane functional entity and the first instance.
  • the user plane functional entity cannot distinguish the sessions corresponding to some instances, so that the user plane functional entity cannot collect statistics on the user plane performance data corresponding to some instances. It can be seen that by implementing this optional manner, the user plane functional entity can perform statistics on the user plane performance data corresponding to the control plane functional entity and the designated instance.
  • the user plane functional entity may further perform the following steps: receiving a request message for requesting establishment of a first session sent by the first control plane functional entity, the request message carrying an identifier of the instance; establishing the first session, and The identifier of the first control plane functional entity and the instance identifier in the request message are written in one session.
  • control plane functional entity and instance to which the first session belongs can be marked, thereby facilitating the finding of the session corresponding to the surface function entity and the instance.
  • the user plane functional entity may use the first time as a period to collect the performance data in the first time according to the statistical performance data of the packets in the session.
  • the first information comes from the first control function entity or the operation support system OSS, and the user plane function entity may also report the user plane performance data counted in the first time to the first control plane function entity for the first time as a cycle.
  • the first control plane functional entity may aggregate the user plane performance data and report it to the OSS, so that the OSS does not need to receive the user plane functional entities on its own.
  • the user plane performance data is aggregated to obtain the total user plane performance data of the first control plane functional entity, which can share the load for the OSS.
  • the user plane functional entity may also perform the following steps: buffering the user plane performance data reported to the first control plane functional entity; receiving the feedback from the first control plane functional entity within the second time to indicate that it has been received When the user plane performance data is indicated, the cached user plane performance data is deleted.
  • the user-plane performance data After uploading the user-plane performance data, the user-plane performance data is not deleted immediately, but the user-plane performance data is cached. This can avoid the loss of the user-plane performance data when the first control-plane functional entity does not receive the user-plane performance data.
  • the cached user plane performance data is re-uploaded to the first control plane function entity. . This can ensure that the first control plane functional entity can successfully receive user plane performance data.
  • the first information also carries a first time.
  • the first information also carries an identifier of a performance statistical item.
  • the present application provides a performance data statistics method.
  • the method is applied to a control plane functional entity.
  • the method includes: counting the control plane performance data within a first time using a first time as a cycle;
  • the managed one or more user plane functional entities send first information, the first information is used to instruct statistics on user plane performance data corresponding to the control plane functional entity, and the first information carries an identifier of the control plane functional entity.
  • the control plane functional entity may send the first to the one or more user plane functional entities managed by the control plane functional entity for instructing to perform statistics on the user plane performance data corresponding to the control plane functional entity.
  • Information so that the user plane functional entity can perform statistics on the user plane performance data corresponding to the control plane functional entity.
  • the first control plane functional entity sends the first information to the user plane functional entity.
  • the OSS does not need to send each control plane functional entity and each user plane functional entity to indicate the user plane corresponding to the first control plane functional entity.
  • the performance data is statistical information, which can share the load of OSS.
  • the first information is used to instruct statistics on the user plane performance data corresponding to the control plane functional entity and the first instance, and the first information also carries an identifier of the first instance; and the first time is used to count the first time.
  • the specific implementation of the control plane performance data within the first embodiment is: Counting the control plane performance data corresponding to the first instance within the first time using the first time as a cycle.
  • the first information that is used to indicate the statistics of the user plane performance data corresponding to the control plane functional entity and the first instance may be sent to the user plane functional entity, so that the user plane functional entity may Perform statistics on the user plane performance data corresponding to the functional entity and the first instance.
  • control plane functional entity may also send a request message for requesting establishment of the first session to any user plane functional entity managed by the control plane functional entity, and the request message carries the identifier of the instance.
  • the user plane functional entity can mark the control plane functional entity and instance to which the first session belongs when establishing the first session, thereby facilitating subsequent search of the control plane.
  • the session corresponding to the functional entity and instance.
  • control plane functional entity may also perform the following steps: receiving the user plane performance data reported by the one or more user plane functional entities managed by the control plane functional entity in the first time in a first time cycle; The user plane performance data reported by the one or more user plane functional entities within the first time; the control plane performance data and the aggregated user plane performance data are reported to the operation support system OSS.
  • the user plane performance data is aggregated and reported to the OSS through the first control plane functional entity, so that the OSS does not need to receive the user plane performance data on each user plane functional entity to obtain the total user plane performance data of the first control plane functional entity.
  • OSS shares the load.
  • the first information also carries a first time.
  • the first information also carries an identifier of a performance statistical item.
  • a user plane functional entity is provided, and the user plane functional entity can execute the foregoing first aspect or a method in a possible implementation manner of the first aspect.
  • This function can be realized by hardware, and can also be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • the unit may be software and / or hardware.
  • a user plane functional entity in a fourth aspect, includes: a processor, a memory, and a communication interface; the processor, the communication interface, and the memory are connected.
  • the communication interface is used to implement communication with the service server.
  • one or more programs are stored in a memory, and the processor calls the programs stored in the memory to implement the above-mentioned first aspect or a solution in a possible implementation manner of the first aspect, and the user plane functional entity solves the problem.
  • a control plane functional entity is provided, and the control plane functional entity may execute the method in the second aspect or a possible implementation manner of the second aspect.
  • This function can be realized by hardware, and can also be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • the unit may be software and / or hardware. Based on the same inventive concept, the principle and beneficial effects of the control plane functional entity's problem solving can be found in the above-mentioned second aspect or possible implementation manners of the second aspect and beneficial effects, and duplicates are not repeated.
  • a control plane functional entity includes: a processor, a memory, and a communication interface; the processor, the communication interface, and the memory are connected.
  • the communication interface is used to implement communication with the service server.
  • one or more programs are stored in a memory, and the processor calls the programs stored in the memory to implement the above-mentioned second aspect or the solution in a possible implementation manner of the second aspect.
  • the control plane functional entity solves the problem. For implementation manners and beneficial effects, reference may be made to the foregoing second aspect or possible implementation manners and beneficial effects of the second aspect, and repeated descriptions are not repeated.
  • a computer program product that, when run on a computer, causes the computer to execute the foregoing first aspect, the second aspect, or a possible implementation manner of the first aspect, or a possible implementation manner of the second aspect.
  • a chip product of a user-plane functional entity is provided to execute the method of the first aspect or the method in a possible implementation manner of the first aspect.
  • a chip product for a control plane functional entity which executes the method in the second aspect or a method in a possible implementation manner of the second aspect.
  • a computer-readable storage medium has instructions stored thereon, and when the computer-readable storage medium is run on a computer, the computer executes the first aspect, the second aspect, or the possibility of the first aspect.
  • the method in the embodiment or possible embodiment of the second aspect.
  • 1 to 4 are schematic diagrams of an existing system architecture
  • FIG. 5 is a schematic diagram of a system architecture according to an embodiment of the present application.
  • 6 to 11 are schematic flowcharts of a performance data statistics method according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a user plane functional entity according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a control plane functional entity according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of another user plane functional entity according to an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of another control plane functional entity provided by an embodiment of the present application.
  • the embodiments of the present application provide a performance data statistics method and related equipment, which can perform statistics on user plane performance data corresponding to a control plane functional entity.
  • FIG. 5 is a schematic diagram of a communication system according to an embodiment of the present application.
  • the communication system in the embodiment of the present application includes one or more control plane functional entities and one or more user plane functional entities.
  • FIG. 5 takes the communication system including two control plane functional entities and three user plane functional entities as an example.
  • the communication system may further include an operations support system (operations support system, OSS).
  • the control plane functional entity may be SMF, SGW-C, PGW-C, or TDF-C.
  • the user plane functional entities may be UPF, SGW-U, PGW-U, or TDF-U.
  • the control plane functional entity is SMF
  • the user plane functional entity is UPF.
  • control plane functional entity When the control plane functional entity is SGW-C, the user plane functional entity is SGW-U. When the control plane functional entity is PGW-C, the user plane functional entity is PGW-U. When the control plane functional entity is TDF-C, the user plane functional entity is TDF-U.
  • One control plane functional entity can manage multiple user plane functional entities, and one user plane functional entity can provide services for multiple control plane functional entities. For example, the control plane function entity 1 in FIG. 5 manages the user plane function entity 1 and the user plane function entity 2, and the control plane function entity 2 manages the user plane function entity 2 and the user plane function entity 3.
  • FIG. 6 is a schematic flowchart of a performance data statistics method according to an embodiment of the present application.
  • the performance data statistics method includes the following parts 601 to 603, of which:
  • a user plane function entity receives first information.
  • the first information is used to instruct statistics of user plane performance data corresponding to the first control plane functional entity, and the first information carries an identifier of the first control plane functional entity.
  • the first control plane functional entity is any one of the control plane functional entities. For example, it may be the control plane functional entity 1 or the control plane functional entity 2 in FIG. 5.
  • the identification of the first control plane functional entity is information used to determine the identity of the first control plane functional entity.
  • the user plane functional entity in step 601 is a user plane functional entity managed by the first control plane functional entity. For example, when the first control plane functional entity is the control plane functional entity 1, the user plane functional entity in step 601 may be the user plane functional entity 1 or the user plane functional entity 2. When the first control plane functional entity is the control plane functional entity 2, the user plane functional entity in step 601 may be the user plane functional entity 2 or the user plane functional entity 3.
  • the first information may come from the OSS or the first control plane functional entity, or from another device, which is not limited in the embodiment of the present application.
  • the first information may carry a first time, so that after receiving the first information, the user plane functional entity may count the first time based on the packets under the session belonging to the first control plane functional entity for the first time.
  • User plane performance data may not carry the first time.
  • the user plane function entity may use the time set by default as the first time, and use the first time as a period to count the user plane performance data within the first time.
  • the first information may also carry an identifier of a user plane performance statistical item, such as an ID or a name of the user plane performance statistical item.
  • the user plane functional entity may collect the user plane performance data of the user plane performance statistical item according to the message under the session belonging to the first control plane functional entity. That is, the user plane function entity only counts and reports the performance statistics items that it subscribes to based on the packets under the session belonging to the first control plane function entity, and does not need to count and report all the performance statistics items.
  • the user plane function entity may perform statistics on the performance statistics item set by default for a message belonging to a session belonging to the control plane function entity.
  • the OSS may also send instruction information to the first control plane functional entity for instructing to perform statistics of control plane performance data.
  • the first control plane function entity counts the control plane performance data within the first time period. That is, in this optional manner, the OSS sends information for instructing performance statistics to the first control plane functional entity and the user plane functional entity, respectively.
  • the indication information may carry a first time, or the first time may be set by a first control plane function entity by default.
  • the indication information may also carry an identification of a control plane performance statistics item to be counted, such as an ID or a name of the control plane performance statistics item.
  • the user plane performance statistics can be any one or more of the following data: SGW-U, the number of S1-U uplink user plane packets, and SGW- U1-S1-U uplink user plane packet kilobytes, SGW-U S1-U uplink user plane packet peak packet rate, SGW-U S1-U uplink user plane packet peak kilobyte rate, SGW-U Number of S1-U downlink user plane packets, SGW-U, S1-U downlink user plane message kilobytes, SGW-U, S1-U downlink user plane packet peak packet rate, SGW-U, S1-U downlink users Peak message face kilobyte rate, SGW-U GTP based S5 / S8 downlink user face message packets, SGW-U GTP based S5 / S8 downlink user face message kilobytes, SGW-U GTP based S5 / S8 downlink user face message kilobytes, SGW-U GTP
  • the user plane performance statistics item can be any one or more of the following data: PGW-U GTP based S5 / S8 / S2a / S2b uplink user plane message packets, PGW-U GTP based S5 / S8 / S2a / S2b uplink user plane message kilobytes, PGW-U GTP based S5 / S8 / S2a / S2b uplink user plane message peak packet rate, PGW-U GTP based based S5 / S8 / S2a / S2b uplink user plane packet peak kilobyte rate, PGW-U GTP based S5 / S8 / S2a / S2b downlink user plane packet number, PGW-U GTP based S5 / S8 / S2a / S2b downlink user Facet message kilobytes, PGW-U GTP based S5 / S8 / S2a / S2b downlink user Facet
  • the user plane performance statistics item can be any one or more of the following data: UPF N3 interface uplink user plane packet number, UPF N3 interface uplink user plane packet kilobyte Number, peak packet rate of uplink user plane packets on the UPF N3 interface, peak kilobyte rate of uplink user plane packets on the UPF N3 interface, number of downlink user plane packets on the UPF N3 interface, and kilobytes of downlink user plane packets on the UPF N3 interface Number, peak packet rate of downlink user plane packets on the UPF N3 interface, peak kilobyte rate of downlink user plane packets on the UPF N3 interface, number of downlink user plane packets on the UPF N6 interface, and kilobytes on the user plane of the UPF N6 Number, peak packet rate of downlink user plane packets on the UPF N6 interface, peak kilobyte rate of downlink user plane packets on the UPF N6 interface, number of uplink
  • the user plane function entity determines that the session belongs to the first control plane function entity according to the identifier of the control plane function entity to which the user belongs, collect performance data according to the message under the session.
  • the user plane functional entity may use the first time as a period to collect performance data in the first time based on the packets in the session.
  • a session belonging to a control plane functional entity is a session created by the control plane functional entity.
  • the control plane functional entity 1 sends a request message for establishing a session 1 to the user plane functional entity 2.
  • the user plane functional entity 2 After receiving the request message, the user plane functional entity 2 creates a session 1 and writes the identifier of the control plane functional entity 1 in the session 1.
  • the session 1 belongs to the control plane functional entity 1.
  • the user plane functional entity may first determine the session belonging to the first control plane functional entity according to the identifier of the control plane functional entity to which the user belongs, and then according to the session Packet statistics performance data.
  • the user plane functional entity 2 After receiving the first information, the user plane functional entity 2 detects that the sessions 1 to 3 carry the identity of the control plane functional entity 1 and the user plane functional entity 2 determines session 1 ⁇ 3 belongs to control plane functional entity 1. After the user plane functional entity 2 determines that the sessions 1 to 3 belong to the control plane functional entity 1, it detects the packets of the sessions 1 to 3, and collects performance data according to the packets of the sessions 1 to 3. The user plane functional entity may use the first time as a period to collect performance data in the first time based on the packets under the packets of sessions 1 to 3.
  • the counter that counts the number of packets on the uplink user plane is increased by 1, and when a packet exists on the session 2, it is counted as an uplink user plane.
  • the counter of the number of packets is increased by 1, and when the packets belonging to sessions 1 to 3 are detected, the counter of the number of packets of the uplink user plane is counted by 1, and so on. If it is finally counted that the number of uplink user plane message packets is 10 within 0 to 5 seconds, the number of uplink user plane message packets 10 is the user plane performance data of the control plane function entity 1.
  • the session in which the first message is located is determined, and the first message is any message received; and according to the control plane function entity to which the session carries.
  • the specific implementation of the statistical performance data according to the message under the session is: when according to the identifier of the control plane functional entity that the first message carries in the session,
  • the performance data is calculated according to the first packet. That is, in this embodiment, each time a message is received, it is determined whether the session in which the message belongs belongs to the first control plane functional entity, and if so, the performance data is counted according to the message.
  • the user plane function entity 2 when the user plane function entity 2 receives the message 1, it detects the session 1 where the message 1 is located. If the user plane functional entity 2 detects that the identity of the control plane functional entity 1 is carried in the session 1, the user plane functional entity 2 collects performance data according to the message 1. For example, when the performance data is the number of uplink user plane packet, the user plane function entity 2 adds 1 to the number of uplink user plane packet. Similarly, when the user plane functional entity 2 receives the message 2 again, it detects the session 1 where the message 2 is located.
  • the user plane functional entity 2 detects that the identity of the control plane functional entity 1 is carried in the session 1, the user plane functional entity 2 counts performance data according to the message 2, and the user plane functional entity 2 adds 1 to the number of uplink user plane message packets. .
  • the user plane functional entity may use the first time as a period to collect performance data in the first time. If the first time is 5 seconds, and if it is counted that the number of uplink user plane message packets is 10 within 0 to 5 seconds, the number of uplink user plane message packets 10 is the user plane performance data of the control plane functional entity 1.
  • the user plane functional entity can accurately determine a message belonging to the session of the first control plane functional entity, and statistics on the user plane performance data corresponding to the first control plane functional entity according to the message.
  • the user plane functional entity uses the statistically obtained performance data as the user plane performance data corresponding to the first control plane functional entity.
  • the user plane functional entity can perform statistics on the user plane performance data corresponding to the control plane functional entity.
  • the user plane performance data counted in the first time may be reported to the first time period Control plane functional entities.
  • the user plane functional entity 1 sends the uplink user plane packet number 100 counted within 5 seconds to the control plane functional entity 1 in a period of 5 seconds, and the user plane functional entity 2 sends 5 seconds in a period of 5 seconds.
  • the number of uplink user plane packet 200 obtained from the internal statistics is sent to the control plane functional entity 1.
  • the first control plane functional entity may aggregate the user plane performance data and report it to the OSS, so that the OSS does not need to receive the user plane functional entities on its own.
  • the user plane performance data is aggregated to obtain the total user plane performance data of the first control plane functional entity, which can share the load for the OSS.
  • the user plane functional entity may buffer the user plane performance data reported to the first control plane functional entity; and receive the feedback from the first control plane functional entity within the second time to indicate that the user plane performance data has been received.
  • cached user plane performance data is deleted. For example, after the user plane functional entity 1 and the user plane functional entity 2 report the number of uplink user plane packets to the control plane functional entity 1, they may buffer the number of reported uplink user plane packets and receive the control plane within 5 seconds.
  • the cached user plane performance data is deleted. After uploading the user-plane performance data, the user-plane performance data is not deleted immediately, but the user-plane performance data is cached.
  • the cached user plane performance data is re-uploaded to the first control plane function entity. . This can ensure that the first control plane functional entity can successfully receive user plane performance data.
  • the user plane functional entity uses the statistically obtained performance data as the user plane performance data corresponding to the first control plane functional entity, it may also directly report the user plane performance data to the OSS.
  • FIG. 7 is a schematic flowchart of another performance data statistics method according to an embodiment of the present application.
  • the performance data statistics method includes the following parts 701 to 704, of which:
  • the first control plane functional entity counts the control plane performance data in the first time by using the first time as a cycle.
  • the first control plane functional entity may be any control plane functional entity.
  • it may be the control plane functional entity 1 or the control plane functional entity 2 in FIG. 5.
  • the first control plane functional entity may count the control plane performance data within 5 seconds in a period of 5 seconds. For example, after statistics of control plane performance data within 0 to 5 seconds, statistics of control plane performance data within 5 to 10 seconds, statistics of control plane performance data within 10 to 15 seconds, and so on.
  • the control plane performance data may be any one or more of the following data: S5 / S8 (SGW-C) sends the number of default bearer creation request messages, S5 / S8 (SGW-C) receives the default bearer creation response number, S5 / S8 (SGW-C) receives the default bearer creation response number, and S5 / S8 (SGW-C) receives a dedicated bearer creation request Number of messages, S5 / S8 (SGW-C) sends the number of successful private bearer response messages, S5 / S8 (SGW-C) sends the number of failed private bearer response messages, S5 / S8 (SGW-C) sends the updated bearer Number of request messages, S5 / S8 (SGW-C) received update bearer successful response messages, S5 / S8 (SGW-C) received update bearer failed response messages, S5 / S8 (SGW-C) received update bearer request messages
  • the control plane performance data may be any one or more of the following data: S5 / S8 / S2a / S2b (PGW-C) receives the number of default bearer creation request messages, S5 / S8 / S2a / S2b (PGW-C) sends the default bearer creation response number, S5 / S8 / S2a / S2b (PGW-C) sends the default bearer creation response number, S5 / S8 / S2a / S2b (PGW-C) sends the number of private bearer creation request messages, S5 / S8 / S2a / S2b (PGW-C) receives the number of successful private bearer creation response messages, S5 / S8 / S2a / S2b (PGW-C) receives Number of private bearer failure response messages, S5 / S8 / S2a / S2b (PGW-C) send update bearer
  • the control plane performance data can be any one or more of the following data: MF received PDU session creation request messages, SMF sent N4 session creation request messages, SMF received N4 session creation Number of successful response messages, SMF receiving N4 session creation failure response messages, SMF sending PDU session creation success response messages, SMF sending PDU session creation failure response messages, SMF receiving PDU session modification request messages, SMF sending N4 session modification requests Number of messages, SMF received N4 session modification successful response messages, SMF received N4 session modification failed response messages, SMF sent PDU session modification successful response messages, SMF sent PDU session modification failed response messages, SMF received PDU session deletion request messages Number, SMF sends N4 session deletion request messages, SMF receives N4 session deletion success response messages, SMF receives N4 session deletion failure response messages, SMF sends PDU session deletion success response messages, SMF sends PDU session deletion failure response messages .
  • the first control plane functional entity sends the first information to one or more user plane functional entities managed by the first control plane functional entity.
  • the first information is used to instruct statistics of user plane performance data corresponding to the first control plane functional entity, and the first information carries an identifier of the first control plane functional entity.
  • the identification of the first control plane functional entity is information used to determine the identity of the first control plane functional entity.
  • the user plane functional entity in step 702 is a user plane functional entity managed by the first control plane functional entity.
  • the first control plane functional entity manages two user plane functional entities as an example.
  • the first control plane functional entity can also manage more than two user plane functional entities. Accordingly, the user plane functional entities in FIG. 7 For more than two.
  • the first control plane functional entity may also manage one user plane functional entity. Accordingly, there is only one user plane functional entity in FIG. 7.
  • the first control plane functional entity when the first control plane functional entity is the control plane functional entity 1, the first control plane functional entity sends the first information to the user plane functional entity 1 and the user plane functional entity 2.
  • the first control plane functional entity When the first control plane functional entity is the control plane functional entity 2, the first control plane functional entity sends the first information to the user plane functional entity 2 and the user plane functional entity 3.
  • the first control plane functional entity sends the first information to the user plane functional entity to indicate the statistics of the user plane performance data corresponding to the first control plane functional entity.
  • the OSS does not need to send to each control plane functional entity and each user.
  • the surface function entity sends first information for instructing statistics on user plane performance data corresponding to the first control surface function entity, so that the load of the OSS can be shared.
  • the first control plane functional entity may perform step 701 at a preset time point and send the first information to one or more user plane functional entities managed by the first control plane functional entity.
  • the first control plane functional entity can automatically count the control plane performance data at a preset time point, and the first control plane functional entity automatically sends the user plane function entity to instruct the user plane function entity at the preset time point.
  • First information for performing statistics on user plane performance data corresponding to the first control plane functional entity Therefore, it is not necessary for the OSS to send information for indicating performance statistics to each control plane functional entity and each user plane functional entity, so that the load of the OSS can be shared.
  • the first control plane functional entity may receive the instruction information sent by the operation support system OSS, and the instruction information is used to instruct the first control plane functional entity to perform statistics on the control plane performance data and the user corresponding to the first control plane functional entity. Surface performance data for statistics.
  • the first control plane functional entity executes step 701 and sends the first information to one or more user plane functional entities managed by the first control plane functional entity.
  • the OSS can only send information for performance statistics to the control plane functional entities, and the OSS does not need to send information for performance statistics to each control plane functional entity and each user plane functional entity, so it can be shared Load of OSS.
  • the indication information may carry the first time, or the indication information may further carry an identifier of a control plane performance statistical item and an identifier of a user plane performance statistical item to be counted.
  • the user plane function entity determines that the session belongs to the first control plane function entity according to the identifier of the control plane function entity to which the user belongs, collect performance data according to the message under the session.
  • the user plane functional entity uses the statistically obtained performance data as the user plane performance data corresponding to the first control plane functional entity.
  • steps 703 and 704 reference may be made to the descriptions of 602 and 603, and details are not described herein.
  • the user plane functional entity can perform statistics on the user plane performance data corresponding to the control plane functional entity.
  • the user plane functional entity uses the statistical performance data as the user plane performance data corresponding to the first control plane functional entity
  • the user plane that is counted in the first time may be cycled for the first time.
  • the performance data is reported to the first control plane functional entity.
  • the first control plane functional entity may perform the following steps: receiving the user plane performance data reported by the one or more user plane functional entities managed by the control plane functional entity in the first time in a first time period; summarizing one or more User plane performance data reported by each user plane functional entity within the first time; report control plane performance data and aggregated user plane performance data to the operation support system OSS.
  • the first control plane functional entity may not perform the user plane performance data. Summarized, you can directly upload the received user-side performance data to OSS. In this way, after the OSS observes the performance statistics, the operator can modify the UPF selection strategy to achieve load sharing among multiple UPFs.
  • the user plane functional entity 1 sends the uplink user plane packet number 100 counted within 5 seconds to the control plane functional entity 1 in a period of 5 seconds, and the user plane functional entity 2 sends 5 seconds in a period of 5 seconds.
  • the number of uplink user plane packet 200 obtained from the internal statistics is sent to the control plane functional entity 1.
  • the control plane functional entity 1 receives the number of uplink user plane packets 100 and the number of uplink user plane packets 200 sent by the user plane functional entity 1 and the user plane functional entity 2 and then summarizes the number of uplink user plane packets. Add the number of uplink user plane packets to get 300.
  • the number of uplink user plane packet 300 is the total user plane performance data of control plane functional entity 1.
  • Control plane functional entity 1 reports the number of uplink user plane packet 300 and the control plane performance data detected by itself to OSS for OSS. Analyze performance data.
  • the first control plane functional entity After the first control plane functional entity receives the user plane performance data of the first control plane functional entity on each of the user plane functional entities, it aggregates the user plane performance data and reports it to the OSS, thereby eliminating the need for the OSS to receive users on each user plane functional entity.
  • the surface performance data is aggregated to obtain the total user-plane performance data of the first control plane functional entity, which can share the load for the OSS.
  • the user plane functional entity may buffer the user plane performance data reported to the first control plane functional entity; and receive the feedback from the first control plane functional entity within the second time to indicate that the user plane performance data has been received.
  • cached user plane performance data is deleted. After uploading the user-plane performance data, the user-plane performance data is not deleted immediately, but the user-plane performance data is cached. This can avoid the loss of the user-plane performance data when the first control-plane functional entity does not receive the user-plane performance data.
  • the cached user plane performance data is re-uploaded to the first control plane function entity. . This can ensure that the first control plane functional entity can successfully receive user plane performance data.
  • the user plane functional entity uses the statistically obtained performance data as the user plane performance data corresponding to the first control plane functional entity, it may also directly report the user plane performance data to the OSS.
  • FIG. 9 is a schematic flowchart of another performance data statistics method according to an embodiment of the present application.
  • the performance data statistics method includes the following 901-905 sections, of which:
  • the user plane functional entity receives the first information.
  • the first information is used to instruct statistics on the user plane performance data corresponding to the control plane functional entity and the first instance, and the first information carries the identifier of the first control plane functional entity and the identifier of the first instance.
  • the identification of the first control plane functional entity is information used to determine the identity of the first control plane functional entity.
  • the identification of the first instance is information used to determine the identity of the first instance.
  • the user plane functional entity in step 901 is a user plane functional entity managed by the first control plane functional entity.
  • the first example may be any one of APN, OCS, CS, DRA, HPLMN, SGSN, and PCRF.
  • the first information may carry a first time, so that after receiving the first information, the user plane functional entity may periodically collect user plane performance data for the first time as a period.
  • the first information may also carry the identifier of the user plane performance statistics item corresponding to the first instance, such as the ID or name of the user plane performance statistics item.
  • the user plane function entity may The identifier of the user plane performance statistics item counts user plane performance data.
  • the first information may come from the OSS or the first control plane functional entity, or from another device, which is not limited in the embodiment of the present application.
  • the OSS may also send indication information to the first control plane functional entity to indicate statistics on control plane performance data corresponding to the first instance.
  • the first control plane function entity uses the first time as a period to count the control plane performance data corresponding to the first instance in the first time. That is, in this optional manner, the OSS sends information for instructing performance statistics to the first control plane functional entity and the user plane functional entity, respectively.
  • the indication information may carry a first time, or the first time may be set by a first control plane function entity by default.
  • the indication information may also carry an identifier of a control plane performance statistical item corresponding to the first instance to be counted, such as an ID or a name of the control plane performance statistical item.
  • the user plane performance statistics corresponding to the first instance may be: user plane L2TP performance measurement (designated APN), SGW-U and PGW-U combined form forwarding performance measurement (designated APN), user plane user basic session Service measurement (designated VPLMN), user plane forwarding performance measurement (designated VPLMN), user plane basic session service measurement (designated APN), user plane service instance performance measurement (designated service instance), user plane forwarding performance measurement (designated TAC), User plane forwarding performance measurement (specify TAC group).
  • APN user plane L2TP performance measurement
  • VPLMN user plane user basic session Service measurement
  • VPLMN user plane forwarding performance measurement
  • user plane basic session service measurement designated APN
  • user plane service instance performance measurement designated service instance
  • user plane forwarding performance measurement designated TAC
  • User plane forwarding performance measurement specify TAC group.
  • the first control plane functional entity sends a request message for requesting establishment of a first session to any user plane functional entity under management, where the request message carries an identifier of the instance.
  • the identity of the instance is information that can determine the identity of the instance.
  • the user plane functional entity establishes a first session, and writes the identifier of the first control plane functional entity and the identifier of the instance in the request message in the first session.
  • the first session is an arbitrary session. If the first information comes from the OSS, the OSS needs to send the identity of the instance to the first control plane functional entity. If the first control plane functional entity receives a request from a user terminal for establishing a first session corresponding to an instance, the first control plane functional entity sends a request for establishing a first session to any managed user plane functional entity. Request message, which carries the identity of the instance. After receiving the request message, the user plane function entity establishes a first session, and writes the identifier of the first control plane function entity and the identifier of the instance in the request message in the first session.
  • the first control plane functional entity may assign an identifier to the instance. If the first control plane functional entity receives a request from a user terminal for establishing a first session corresponding to an instance, the first control plane functional entity sends a request for establishing a first session to any managed user plane functional entity. A request message that carries the identifier of the instance allocated by the first control plane functional entity. After receiving the request message, the user plane function entity establishes a first session, and writes the identifier of the first control plane function entity and the identifier of the instance in the request message in the first session.
  • control plane functional entity and instance to which the first session belongs can be marked, which is beneficial to finding the session corresponding to the surface control functional entity and instance.
  • the identifier of the first control plane functional entity and the instance identifier may not be recorded in the first session through the methods of 902 and 903.
  • the identifier of the first control plane functional entity and the instance identifier may be recorded in the first session by other methods.
  • the user plane function entity determines that the session belongs to the first control plane function entity and the first instance according to the identifier of the control plane function entity and the instance identifier carried in the session, collect performance data according to the message under the session. .
  • the user plane functional entity receives the first information
  • the user plane functional entity determines that the session belongs to the first control plane functional entity and the first instance according to the identifier of the control plane functional entity and the identifier of the first instance carried by the session.
  • performance data is collected based on the packets in the session.
  • the user plane functional entity may perform statistics on the performance data of the first instance in the first time based on the packets in the session using the first time as a period.
  • the user-plane functional entity may first determine that the user belongs to the first control-plane functional entity and the identifier of the first control-plane functional entity and the identifier of the first instance carried in the session. In the session of the first instance, performance data is collected according to the packets in the session.
  • the session in which the first message is located is determined, and the first message is any message received; and according to the control plane function entity to which the session carries.
  • the specific implementation of statistical performance data based on the message under the session is as follows: When it is determined that the session where the first packet belongs belongs to the first control plane functional entity and the first instance, the performance data is counted according to the first packet. That is, in this embodiment, each time a message is received, it is determined whether the session in which the message belongs belongs to the first control plane functional entity and the first instance, and if so, the performance data is counted according to the message.
  • the user plane functional entity can accurately determine a message belonging to the session of the first control plane functional entity and the first instance, and count the first control plane functional entity and the first instance according to the message.
  • User plane performance data corresponding to the instance can accurately determine a message belonging to the session of the first control plane functional entity and the first instance, and count the first control plane functional entity and the first instance according to the message.
  • the user plane functional entity uses the statistically obtained performance data as user plane performance data corresponding to the first control plane functional entity and the first instance.
  • the user plane functional entity cannot distinguish the sessions corresponding to some instances, so that the user plane functional entity cannot collect statistics on the user plane performance data corresponding to some instances. It can be seen that by implementing the method described in FIG. 9, the user plane functional entity can perform statistics on the user plane performance data corresponding to the control plane functional entity and the designated instance.
  • the user plane function entity uses the statistical performance data as the user plane performance data corresponding to the first control plane function entity and the first instance
  • the user plane performance data that is counted in the first time may be cycled for the first time Report to the first control plane functional entity.
  • the user plane performance data reported to the first control plane functional entity is cached; when an instruction message indicating that the user plane performance data has been received is received within the second time, the user plane performance data is deleted. Cached user plane performance data. After uploading the user-plane performance data, the user-plane performance data is not deleted immediately, but the user-plane performance data is cached. This can avoid the loss of the user-plane performance data when the first control-plane functional entity does not receive the user-plane performance data.
  • the cached user plane performance data is re-uploaded to the first control plane function entity. . This can ensure that the first control plane functional entity can successfully receive user plane performance data.
  • the user plane performance data may also be directly reported to the OSS.
  • FIG. 10 is a schematic flowchart of another performance data statistics method according to an embodiment of the present application.
  • the performance data statistics method includes the following parts 1001 to 1006, of which:
  • a first control plane functional entity counts the control plane performance data corresponding to the first instance in the first time using the first time as a cycle.
  • the first control plane functional entity may be any control plane functional entity.
  • it may be the control plane functional entity 1 or the control plane functional entity 2 in FIG. 5.
  • the first control plane functional entity may count the control plane performance data corresponding to the first instance in a period of 5 seconds. For example, after counting the control plane performance data corresponding to the first instance within 0 to 5 seconds, then to count the control plane performance data corresponding to the first instance within 5 to 10 seconds, and then counting the control plane corresponding to the first instance within 10 to 15 seconds. Performance data, and so on.
  • the first example may be any one of APN, OCS, CS, DRA, HPLMN, SGSN, and PCRF.
  • the control plane performance statistics corresponding to the first instance may be: SGW-C basic session service measurement (designated APN), PGW-C basic session service measurement (designated APN), control plane basic session service measurement (designated APN), Control plane online charging service performance measurement (designated OCS), control plane Ga interface performance measurement (designated CG), PGW-C 3G session performance measurement (designated APN), PGW-C 2G session performance measurement (designated APN), control plane Session state statistics (designated APN), control plane Diameter performance statistics (designated DRA), control plane AAA performance measurement (designated APN), PGW-C 2 / 3G session performance measurement (designated APN, service type), GW control plane Basic session performance measurement (designated HPLMN), PGW-C 2 / 3G measurement basic session performance (designated SGSN), control plane Gx interface performance measurement (designated APN), control plane PCC session measurement
  • the first control plane functional entity sends the first information to one or more user plane functional entities managed by the first control plane functional entity.
  • the first information is used to instruct statistics on the user plane performance data corresponding to the control plane functional entity and the first instance, and the first information carries the identifier of the first control plane functional entity and the identifier of the first instance.
  • the identification of the first control plane functional entity is information used to determine the identity of the first control plane functional entity.
  • the identification of the first instance is information used to determine the identity of the first instance.
  • the user plane functional entity in step 1002 is a user plane functional entity managed by the first control plane functional entity.
  • the first information may carry a first time, so that after receiving the first information, the user plane functional entity may use the first time as a period to count according to the packet statistics in the session belonging to the first control plane functional entity and the first instance. User plane performance data in the first time.
  • the first information may not carry the first time.
  • the user plane function entity may use the time set by default as the first time, and use the first time as a period to count the user plane performance data within the first time.
  • the first information may also carry an identifier of a user plane performance statistical item, such as an ID or a name of the user plane performance statistical item.
  • the user plane function entity can calculate the user plane performance of the user plane performance statistics item according to the packets belonging to the session between the first control plane function entity and the first instance. data. That is, the user plane function entity only counts and reports the performance statistics items that it subscribes to according to the packets in the session belonging to the first control plane function entity and the first instance, and does not need to count and report all the performance statistics items.
  • the user plane function entity may perform statistics on the performance statistics item set by default for the packets belonging to the session of the control plane function entity and the first instance.
  • the first control plane functional entity sends the first information to the user plane functional entity to indicate the statistics of the user plane performance data corresponding to the first control plane functional entity and the first instance.
  • the OSS does not need to send to each control plane functional entity. Send first information to each user plane functional entity for instructing to perform statistics on user plane performance data corresponding to the first control plane functional entity and the first instance, so that the load of the OSS can be shared.
  • the first control plane functional entity may execute step 1001 at a preset time point and send the first information to one or more user plane functional entities managed by the first control plane functional entity.
  • the first control plane functional entity may receive the instruction information sent by the operation support system OSS, and the instruction information is used to instruct the first control plane functional entity to perform statistics on the control plane performance data, as well as to the first control plane functional entity and the first Perform statistics on user plane performance data corresponding to the instance.
  • the first control plane functional entity executes step 1001 and sends the first information to one or more user plane functional entities managed by the first control plane functional entity.
  • the OSS can only send information for performance statistics to the control plane functional entities, and the OSS does not need to send information for performance statistics to each control plane functional entity and each user plane functional entity, so it can be shared Load of OSS.
  • the indication information may carry a first time, or the indication information may further carry an identifier of a control plane performance statistics item and a user plane performance statistics item corresponding to the first instance to be counted.
  • the first control plane functional entity sends a request message for requesting establishment of a first session to any user plane functional entity under management, where the request message carries an identifier of the instance.
  • the identity of the instance is information that can determine the identity of the instance.
  • the user plane functional entity establishes a first session, and writes the identifier of the first control plane functional entity and the identifier of the instance in the request message in the first session.
  • the first control plane functional entity may assign an identifier to the instance. If the first control plane functional entity receives a request from a user terminal for establishing a first session corresponding to an instance, the first control plane functional entity sends a request for establishing a first session to any managed user plane functional entity. A request message that carries the identifier of the instance allocated by the first control plane functional entity. After receiving the request message, the user plane function entity establishes a first session, and writes the identifier of the first control plane function entity and the identifier of the instance in the request message in the first session.
  • control plane functional entity and instance to which the first session belongs can be marked, thereby facilitating the finding of the session corresponding to the surface functional entity and instance.
  • the identifier of the first control plane functional entity and the instance identifier may not be recorded in the first session through the methods of 1003 and 1004, and the identifier of the first control plane functional entity and the instance identifier may be recorded in the first session by other methods.
  • the performance data is counted according to the message under the session.
  • steps 1005 and 1006 reference may be made to the descriptions of 904 and 905, and details are not described herein.
  • the user plane functional entity cannot distinguish the sessions corresponding to some instances, so that the user plane functional entity cannot collect statistics on the user plane performance data corresponding to some instances. It can be seen that by implementing the method described in FIG. 10, the user plane functional entity can perform statistics on the user plane performance data corresponding to the control plane functional entity and the designated instance.
  • the first time period may be The statistical user plane performance data is reported to the first control plane functional entity.
  • the first control plane functional entity may perform the following steps: receiving the user plane performance data reported by the one or more user plane functional entities managed by the control plane functional entity within a first time period and reporting the first time; The user plane performance data reported by the one or more user plane functional entities within the first time; the control plane performance data and the aggregated user plane performance data are reported to the operation support system OSS.
  • the user plane performance data reported to the first control plane functional entity is cached; when an instruction message indicating that the user plane performance data has been received is received within the second time, the user plane performance data is deleted. Cached user plane performance data. After uploading the user-plane performance data, the user-plane performance data is not deleted immediately, but the user-plane performance data is cached. This can avoid the loss of the user-plane performance data when the first control-plane functional entity does not receive the user-plane performance data.
  • the cached user plane performance data is re-uploaded to the first control plane function entity. . This can ensure that the first control plane functional entity can successfully receive user plane performance data.
  • the user plane performance data may also be directly reported to the OSS.
  • the device may be divided into functional modules according to the foregoing method example.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of the modules in the embodiment of the present invention is schematic, and is only a logical function division. In actual implementation, there may be another division manner.
  • FIG. 12 is a user plane functional entity provided by the implementation of the present invention.
  • the user plane functional entity may execute the method performed by the user plane functional entity in the foregoing method embodiment.
  • the user plane functional entity includes a communication module 1201 and a processing module 1202. among them:
  • the communication module 1201 is configured to receive first information, and the first information is used to instruct statistics on user plane performance data corresponding to the first control plane functional entity, and the first information carries an identifier of the first control plane functional entity; the processing module 1202, When determining that the session belongs to the first control plane functional entity according to the identity of the control plane functional entity that the session carries, the performance data is calculated according to the message under the session; the processing module 1202 is further configured to collect the statistically obtained The performance data is used as user plane performance data corresponding to the first control plane functional entity.
  • the processing module 1202 is further configured to determine, when the first message is received, the session in which the first message is located, and the first message is any message received; when the processing module 1202 is based on the ownership carried in the session, The identification of the control plane functional entity determines that the session belongs to the first control plane functional entity.
  • the manner in which the processing module 1202 counts performance data according to the message under the session is specifically: when the processing module 1202 carries the When the identifier of the control plane functional entity to which the first control plane belongs is determined to belong to the first control plane functional entity, the processing module 1202 collects performance data according to the first packet.
  • the first information is used to indicate that the user plane performance data corresponding to the first control plane functional entity and the first instance is counted, and the first information also carries an identifier of the first instance; when the processing module 1202 carries When the identity of the belonging control plane functional entity determines that the session belongs to the first control plane functional entity, the manner in which the processing module 1202 counts performance data according to the message under the session is specifically: when the control plane functional entity carried by the session is included And the instance ID, when determining that the session belongs to the first control plane functional entity and the first instance, statistics are performed on the performance data according to the messages under the session; the processing module 1202 uses the statistical performance data as the first control plane functional entity corresponding
  • the method of the user plane performance data is specifically: using the statistically obtained performance data as the user plane performance data corresponding to the first control plane functional entity and the first instance.
  • the communication module 1201 is further configured to receive a request message sent by the first control plane functional entity for establishing a first session, where the request message carries an identifier of the instance; the processing module 1202 is further configured to establish a first session, The identifier of the first control plane functional entity and the identifier of the instance in the request message are written in the first session.
  • the first information comes from the first control function entity or the operation support system OSS, and the communication module 1201 is further configured to report the user plane performance data counted in the first time to the first control plane function using the first time as a cycle. entity.
  • the processing module 1202 is further configured to cache user plane performance data reported to the first control plane functional entity; the processing module 1202 is further configured to receive feedback from the first control plane functional entity in the second time for When an indication message indicating that the user plane performance data has been received, the cached user plane performance data is deleted.
  • the first information also carries a first time.
  • the first information also carries an identifier of a performance statistical item.
  • FIG. 13 is a control plane functional entity provided by the implementation of the present invention.
  • the control plane functional entity may execute the method executed by the control plane functional entity in the foregoing method embodiment.
  • the control plane functional entity includes a communication module 1301 and a processing module 1302. among them:
  • the processing module 1302 is configured to count the control plane performance data in the first time using the first time as a cycle; the communication module 1301 is configured to send the first information to one or more user plane functional entities managed by the control plane functional entity.
  • a piece of information is used to indicate that user plane performance data corresponding to the control plane functional entity is counted, and the first information carries an identifier of the control plane functional entity.
  • the first information is used to instruct statistics on user plane performance data corresponding to the control plane functional entity and the first instance, and the first information also carries an identifier of the first instance; the processing module 1302 counts the first time period as the first time.
  • the method of the control plane performance data within one time is specifically: using the first time as a cycle to count the control plane performance data corresponding to the first instance within the first time.
  • the communication module 1301 is further configured to send a request message for requesting establishment of the first session to any user plane function entity managed by the control plane function entity, where the request message carries an identifier of the instance.
  • the communication module 1301 is further configured to receive the user-plane performance data reported by the one or more user-plane function entities managed by the control-plane function entity and counted in the first time by the first-time cycle; the processing module 1302, It is also used to summarize the user plane performance data reported by one or more user plane functional entities in the first time; the communication module 1301 is also used to report the control plane performance data and the aggregated user plane performance data to the operation support system OSS. .
  • the first information also carries a first time.
  • the first information also carries an identifier of a performance statistical item.
  • FIG. 14 is a schematic structural diagram of a user plane functional entity disclosed in an embodiment of the present application.
  • the user plane functional entity 1400 includes a processor 1401, a memory 1402, and a communication interface 1403.
  • the processor 1401, the memory 1402, and the communication interface 1403 are connected.
  • the processor 1401 may be a central processing unit (CPU), a general-purpose processor, a coprocessor, a digital signal processor (DSP), and an application-specific integrated circuit (ASIC). Field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • the processor 1401 may also be a combination that implements computing functions, such as a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication interface 1403 is used to implement communication with a control plane functional entity.
  • the processor 1401 calls the program code stored in the memory 1402 to execute the steps performed by the user plane functional entity in the foregoing method embodiment.
  • FIG. 15 is a schematic structural diagram of a control plane functional entity disclosed in an embodiment of the present application.
  • the control plane functional entity 1500 includes a processor 1501, a memory 1502, and a communication interface 1503.
  • the processor 1501, the memory 1502, and the communication interface 1503 are connected.
  • the processor 1501 may be a central processing unit (CPU), a general-purpose processor, a coprocessor, a digital signal processor (DSP), and an application-specific integrated circuit (ASIC). Field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • the processor 1501 may also be a combination that implements computing functions, such as a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication interface 1503 is used to implement communication with a control plane functional entity.
  • the processor 1501 calls the program code stored in the memory 1502 to execute the steps performed by the first control plane functional entity in the foregoing method embodiment.

Landscapes

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

Abstract

本申请公开了一种性能数据统计方法及相关设备，其中，该方法应用于用户面功能实体，该方法包括：接收第一信息，该第一信息用于指示对第一控制面功能实体对应的用户面性能数据进行统计，该第一信息携带第一控制面功能实体的标识；当根据会话携带的所归属的控制面功能实体的标识，确定会话归属于第一控制面功能实体时，根据会话下的报文统计性能数据；将统计得到的性能数据作为第一控制面功能实体对应的用户面性能数据。可见，通过实施本申请所提供的方法，用户面功能实体能够对控制面功能实体对应的用户面性能数据进行统计。

Description

一种性能数据统计方法及相关设备
本申请要求于2018年6月21日提交中国国家知识产权局、申请号为201810642853.3、发明名称为“一种性能数据统计方法及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种性能数据统计方法及相关设备。
背景技术
第四代移动通信系统(即4G)的核心网设备包括服务网关(serving gateway，SGW)、分组数据网络网关(packet data network gateway，PDN-GW或PGW)和数据流探测功能(traffic detection function，TDF)实体。其中，SGW的主要功能包括：进行eNode B间切换时，作为本地锚定点，并协助完成eNode B的重排序功能；在3GPP不同接入系统间切换时，作为移动性锚点；执行合法侦听功能；进行数据包的路由和前转；在上行和下行传输层进行分组标记；用于运营商间的计费等。PGW的主要功能包括：基于用户的包过滤功能、合法侦听功能、用户终端设备(user equipment，UE)的IP地址分配功能、在上行链路中进行数据包传送级标记、进行上下行服务等级计费以及服务水平门限的控制、进行基于业务的上下行速率的控制等。TDF属于连接在PGW与Internet之间的SGI接口的位置，用于识别和探测业务类型，触发事件上报到策略与计费规则功能单元(policy and charging rules function，PCRF)以便于实现PGW的策略更新。
在4G的核心网控制面与用户面分离的系统架构中，如图1所示，SGW、PGW、TDF被划分为控制面功能实体SGW-C、PGW-C、TDF-C和用户面功能实体SGW-U、PGW-U、TDF-U。控制面功能实体用于对用户面功能实体进行管理，或实现其他非会话级的管理功能。用户面功能实体用于为控制面功能实体提供服务，例如用户面功能实体可根据控制平面下发的控制指令建立会话承载，完成用户数据的转发。一个控制面功能实体可以管理多个用户面功能实体，一个用户面功能实体可以为多个控制面功能实体提供服务。图2以控制面功能实体为SGW-C，用户面功能实体为SGW-U为例。如图2所示，SGW-C1管理SGW-U1和SGW-U2，SGW-C2管理SGW-U2和SGW-U3，SGW-C3管理SGW-U3和SGW-U4。同理，一个PGW-C也可以管理多个PGW-U，一个PGW-U可以为多个PGW-C提供服务。一个TDF-C也可以管理多个TDF-U，一个TDF-U可以为多个TDF-C提供服务。
第五代移动通信系统(即5G)对下一代核心网设备的网络架构进行了重新调整。如图3所示，5G核心网设备的网络架构中包括会话管理功能实体(session management function，SMF)和用户面功能实体(user plane function，UPF)。SMF即为控制面功能实体。SMF用于对UPF进行管理，例如，SMF需要负责管理UPF的选择，策略下发，事件上报，UPF心跳检查，UPF负荷上报等非会话级的管理功能。UPF用于为SMF提供服务，例如，UPF可根据SMF下发的控制指令建立会话承载，完成用户数据的转发。同理，如图4所示，一个SMF可以管理多个UPF。一个UPF可以同时为多个SMF提供服务。
如图2和图4所示，现有运营支撑系统(operations support system，OSS)要观察系统的性能指标需要连接到所有的控制面功能实体获取控制面性能数据，以及需要连接到所有用户面功能实体上获取用户面性能数据。然而在现有技术中，一个用户面功能实体统计的用户面性能数据都是根据用户面功能实体上的所有报文统计得到的。例如，如图4所示的UPF2根据UPF2上面的所有报文统计报文千字节数，这就导致OSS无法区分SMF1和SMF2在UPF2分别对应的用户面性能数据，从而导致了无法对每个SMF对应的用户面性能数据进行分析。因此，如何对控制面功能实体对应的用户面性能数据进行统计是目前亟待解决的问题。
发明内容
本申请提供了一种性能数据统计方法及相关设备，能够对控制面功能实体对应的用户面性能数据进行统计。
第一方面，本申请提供了一种性能数据统计方法，该方法应用于用户面功能实体，该方法包括：接收第一信息，该第一信息用于指示对第一控制面功能实体对应的用户面性能数据进行统计，该第一信息携带第一控制面功能实体的标识；当根据会话携带的所归属的控制面功能实体的标识，确定会话归属于第一控制面功能实体时，根据会话下的报文统计性能数据；将统计得到的性能数据作为第一控制面功能实体对应的用户面性能数据。
可见，通过实施第一方面所描述的方法，用户面功能实体能够对控制面功能实体对应的用户面性能数据进行统计。
可选的，当用户面功能实体接收到第一报文时，确定第一报文所在会话，第一报文为接收的任一报文；当根据会话携带的所归属的控制面功能实体的标识，确定会话归属于第一控制面功能实体时，根据会话下的报文统计性能数据的具体实施方式为：当根据第一报文所在会话携带的所归属的控制面功能实体的标识，确定第一报文所在会话归属于第一控制面功能实体时，根据第一报文统计性能数据。
通过实施该可选的实施方式，用户面功能实体能够准确地确定归属于第一控制面功能实体的会话的报文，并根据该报文统计第一控制面功能实体对应的用户面性能数据。
可选的，第一信息用于指示对第一控制面功能实体和第一实例对应的用户面性能数据进行统计，第一信息还携带第一实例的标识；当根据会话携带的所归属的控制面功能实体的标识，确定会话归属于第一控制面功能实体时，根据会话下的报文统计性能数据的具体实施方式为：当根据会话携带的所归属的控制面功能实体的标识和实例的标识，确定会话归属于第一控制面功能实体和第一实例时，根据会话下的报文统计性能数据；将统计得到的性能数据作为第一控制面功能实体对应的用户面性能数据的具体实施方式为：将统计得到的性能数据作为第一控制面功能实体和第一实例对应的用户面性能数据。
现有技术中用户面功能实体无法区分某些实例对应的会话，从而导致用户面功能实体无法对某些实例对应的用户面性能数据进行统计。可见，通过实施该可选的方式，用户面功能实体能够对控制面功能实体和指定实例对应的用户面性能数据进行统计。
可选的，用户面功能实体还可执行以下步骤：接收第一控制面功能实体发送的用于请求建立第一会话的请求消息，该请求消息携带实例的标识；建立第一会话，并在第一会话 中写入第一控制面功能实体的标识和请求消息中的实例的标识。
通过实施该可选的方式，可以对第一会话所归属的控制面功能实体和实例进行标记，从而有利于查找到制面功能实体和实例对应的会话。
可选的，用户面功能实体可以以第一时间为周期根据所述会话下的报文统计性能数据统计第一时间内的性能数据。
可选的，第一信息来自第一控制功能实体或运营支撑系统OSS，用户面功能实体还可以第一时间为周期将第一时间内统计的用户面性能数据上报至第一控制面功能实体。
第一控制面功能实体接收第一控制面功能实体在各个用户面功能实体上的用户面性能数据之后，可汇总用户面性能数据上报给OSS，从而不需要OSS自己接收各个用户面功能实体上的用户面性能数据汇总得到第一控制面功能实体总的用户面性能数据，可为OSS分担负荷。
可选的，用户面功能实体还可执行以下步骤：缓存上报至第一控制面功能实体的用户面性能数据；在第二时间内接收到第一控制面功能实体反馈的用于指示已收到用户面性能数据的指示消息时，删除缓存的用户面性能数据。
在上传用户面性能数据之后不马上删除用户面性能数据，而是将用户面性能数据缓存下来，这样可以避免第一控制面功能实体未接收到用户面性能数据时，造成用户面性能数据丢失。相应地，若在第二时间内未接收到第一控制面功能实体反馈的用于指示已收到用户面性能数据的指示消息时，重新上传缓存的用户面性能数据至第一控制面功能实体。这样可以确保第一控制面功能实体能够成功接收到用户面性能数据。
可选的，第一信息中还携带第一时间。
可选的，第一信息中还携带性能统计项的标识。
第二方面，本申请提供了一种性能数据统计方法，该方法应用于控制面功能实体，该方法包括：以第一时间为周期统计第一时间内的控制面性能数据；向控制面功能实体管理的一个或多个用户面功能实体发送第一信息，该第一信息用于指示对控制面功能实体对应的用户面性能数据进行统计，第一信息携带控制面功能实体的标识。
通过实施第二方面所描述的方法，控制面功能实体可向控制面功能实体管理的一个或多个用户面功能实体发送用于指示对控制面功能实体对应的用户面性能数据进行统计的第一信息，从而用户面功能实体可对控制面功能实体对应的用户面性能数据进行统计。并且通过第一控制面功能实体向用户面功能实体发送第一信息，OSS不需要向每个控制面功能实体和每个用户面功能实体发送用于指示对第一控制面功能实体对应的用户面性能数据进行统计的信息，从而可分担OSS的负荷。
可选的，第一信息用于指示对控制面功能实体和第一实例对应的用户面性能数据进行统计，该第一信息还携带第一实例的标识；以第一时间为周期统计第一时间内的控制面性能数据的具体实施方式为：以第一时间为周期统计第一时间内第一实例对应的控制面性能数据。
通过实施该可选的实施方式，可向用户面功能实体发送用于指示对控制面功能实体和第一实例对应的用户面性能数据进行统计的第一信息，从而用户面功能实体可对控制面功能实体和第一实例对应的用户面性能数据进行统计。
可选的，控制面功能实体还可向控制面功能实体管理的任意一个用户面功能实体发送用于请求建立第一会话的请求消息，请求消息携带实例的标识。
通过在用于请求第一会话的请求消息中携带实例的标识，从而用户面功能实体可在建立第一会话时，标记第一会话所属的控制面功能实体和实例，从而有利于后续查找控制面功能实体和实例对应的会话。
可选的，控制面功能实体还可执行以下步骤：以第一时间为周期接收控制面功能实体管理的一个或多个用户面功能实体上报的在第一时间内统计的用户面性能数据；汇总一个或多个用户面功能实体上报的在第一时间内统计的用户面性能数据；向运营支撑系统OSS上报控制面性能数据和汇总的用户面性能数据。
通过第一控制面功能实体汇总用户面性能数据上报给OSS，从而不需要OSS自己接收各个用户面功能实体上的用户面性能数据汇总得到第一控制面功能实体总的用户面性能数据，可为OSS分担负荷。
可选的，第一信息中还携带第一时间。
可选的，第一信息中还携带性能统计项的标识。
第三方面，提供了一种用户面功能实体，该用户面功能实体可执行上述第一方面或第一方面可能的实施方式中的方法。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元。该单元可以是软件和/或硬件。基于同一发明构思，该用户面功能实体解决问题的原理以及有益效果可以参见上述第一方面或第一方面可能的实施方式中以及有益效果，重复之处不再赘述。
第四方面，提供了一种用户面功能实体，该用户面功能实体包括：处理器、存储器、通信接口；处理器、通信接口和存储器相连。通信接口用于实现与业务服务器之间的通信。其中，一个或多个程序被存储在存储器中，该处理器调用存储在该存储器中的程序以实现上述第一方面或第一方面可能的实施方式中的方案，该用户面功能实体解决问题的实施方式以及有益效果可以参见上述第一方面或第一方面可能的实施方式以及有益效果，重复之处不再赘述。
第五方面，提供了一种控制面功能实体，该控制面功能实体可执行上述第二方面或第二方面可能的实施方式中的方法。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元。该单元可以是软件和/或硬件。基于同一发明构思，该控制面功能实体解决问题的原理以及有益效果可以参见上述第二方面或第二方面可能的实施方式中以及有益效果，重复之处不再赘述。
第六方面，提供了一种控制面功能实体，该控制面功能实体包括：处理器、存储器、通信接口；处理器、通信接口和存储器相连。通信接口用于实现与业务服务器之间的通信。其中，一个或多个程序被存储在存储器中，该处理器调用存储在该存储器中的程序以实现上述第二方面或第二方面可能的实施方式中的方案，该控制面功能实体解决问题的实施方式以及有益效果可以参见上述第二方面或第二方面可能的实施方式以及有益效果，重复之处不再赘述。
第七方面，提供了一种计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面、第二方面或第一方面的可能的实施方式或第二方面的可能的实施方式中的方 法。
第八方面，提供了一种用户面功能实体的芯片产品，执行上述第一方面的方法或第一方面的可能的实施方式中的方法。
第九方面，提供了一种控制面功能实体的芯片产品，执行上述第二方面的方法或第二方面的可能的实施方式中的方法。
第十方面，提了供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第一方面、第二方面或第一方面的可能的实施方式或第二方面的可能的实施方式中的方法。
附图说明
图1～图4是现有的系统架构的示意图；
图5是本申请实施例提供的一种系统架构的示意图；
图6～11是本申请实施例提供的性能数据统计方法的流程示意图；
图12是本申请实施例提供的一种用户面功能实体的结构示意图；
图13是本申请实施例提供的一种控制面功能实体的结构示意图；
图14是本申请实施例提供的另一种用户面功能实体的结构示意图；
图15是本申请实施例提供的另一种控制面功能实体的结构示意图。
具体实施方式
下面结合附图对本申请具体实施例作进一步的详细描述。
本申请实施例提供了一种性能数据统计方法及相关设备，能够对控制面功能实体对应的用户面性能数据进行统计。
为了能够更好地理解本申请实施例，下面对本申请实施例的通信系统进行说明。
图5是本申请实施例提供的一种通信系统的示意图。如图5所示，本申请实施例的通信系统中包括一个或多个控制面功能实体和一个或多个用户面功能实体。图5以通信系统包括两个控制面功能实体和3个用户面功能实体为例。可选的，该通信系统中还可包括运营支撑系统(operations support system，OSS)。其中，控制面功能实体可以为SMF、SGW-C、PGW-C或TDF-C等。用户面功能实体可以为UPF、SGW-U、PGW-U或TDF-U等。当控制面功能实体为SMF时，用户面功能实体为UPF。当控制面功能实体为SGW-C时，用户面功能实体为SGW-U。当控制面功能实体为PGW-C时，用户面功能实体为PGW-U。当控制面功能实体为TDF-C时，用户面功能实体为TDF-U。一个控制面功能实体可以管理多个用户面功能实体，一个用户面功能实体可以为多个控制面功能实体提供服务。例如，图5中的控制面功能实体1管理用户面功能实体1和用户面功能实体2，控制面功能实体2管理用户面功能实体2和用户面功能实体3。
以下对本申请所提供的性能数据统计方法及相关设备进行详细地介绍。
请参见图6，图6是本申请实施例提供的一种性能数据统计方法的流程示意图。如图6所示，该性能数据统计方法包括如下601～603部分，其中：
601、用户面功能实体接收第一信息。
其中，该第一信息用于指示对第一控制面功能实体对应的用户面性能数据进行统计，该第一信息携带第一控制面功能实体的标识。第一控制面功能实体为任意一个控制面功能实体。例如，可以是图5中的控制面功能实体1或控制面功能实体2。第一控制面功能实体的标识为用于确定第一控制面功能实体的身份的信息。其中，步骤601中的用户面功能实体为第一控制面功能实体管理的用户面功能实体。例如，第一控制面功能实体为控制面功能实体1时，步骤601中的用户面功能实体可以为用户面功能实体1或用户面功能实体2。第一控制面功能实体为控制面功能实体2时，步骤601中的用户面功能实体可以为用户面功能实体2或用户面功能实体3。
可选的，第一信息可来自OSS或第一控制面功能实体，或来自其他设备，本申请实施例不做限定。
可选的，第一信息中可携带第一时间，这样用户面功能实体接收第一信息之后，可以第一时间为周期根据属于第一控制面功能实体的会话下的报文统计第一时间内的用户面性能数据。当然第一信息中也可不携带第一时间，用户面功能实体可以以默认设置的时间为第一时间，并以第一时间为周期统计第一时间内的用户面性能数据。
第一信息中也可携带用户面性能统计项的标识，如用户面性能统计项的ID或名称等。这样用户面功能实体接收携带用户面性能统计项的标识的第一信息之后，可以根据属于第一控制面功能实体的会话下的报文统计该用户面性能统计项的用户面性能数据。即用户面功能实体根据属于第一控制面功能实体的会话下的报文仅统计和上报其订阅的性能统计项，不用对所有的性能统计项进行统计和上报。当然，若第一信息中不携带用户面性能统计项的标识，用户面功能实体针对属于该控制面功能实体的会话的报文可以对默认设置的性能统计项进行统计。
可选的，若第一信息来自OSS，则OSS还可向第一控制面功能实体发送用于指示进行控制面性能数据统计的指示信息。第一控制面功能实体接收该指示信息之后，就以第一时间为周期统计所述第一时间内的控制面性能数据。也就是说，在该可选的方式中，由OSS向第一控制面功能实体和用户面功能实体分别发送用于指示进行性能统计的信息。其中，该指示信息可携带第一时间，或第一时间可以是第一控制面功能实体默认设置的。该指示信息中还可携带需要统计的控制面性能统计项的标识，如控制面性能统计项的ID或名称等。
第一信息来自第一控制面功能实体的具体实施方式可参见图8所对应的描述。
举例来说，第一用户面功能实体为SGW-U时，用户面性能统计项可以为以下数据中的任意一种或多种：SGW-U S1-U上行用户面报文包数、SGW-U S1-U上行用户面报文千字节数、SGW-U S1-U上行收用户面报文峰值包速率、SGW-U S1-U上行用户面报文峰值千字节速率、SGW-U S1-U下行用户面报文包数、SGW-U S1-U下行用户面报文千字节数、SGW-U S1-U下行用户面报文峰值包速率、SGW-U S1-U下行用户面报文峰值千字节速率、SGW-U GTP based S5/S8下行用户面报文包数、SGW-U GTP based S5/S8下行用户面报文千字节数、SGW-U GTP based S5/S8下行用户面报文峰值包速率、SGW-U GTP based S5/S8下行用户面报文峰值千字节速率、SGW-U GTP based S5/S8上行用户面报文包数、SGW-U GTP based S5/S8上行用户面报文千字节数、SGW-U GTP based S5/S8上行用户面报文峰值包速率、SGW-U GTP based S5/S8上行用户面报文峰值千字节速率。
第一用户面功能实体为PGW-U时，用户面性能统计项可以为以下数据中的任意一种或多种：PGW-U GTP based S5/S8/S2a/S2b上行用户面报文包数、PGW-U GTP based S5/S8/S2a/S2b上行用户面报文千字节数、PGW-U GTP based S5/S8/S2a/S2b上行用户面报文峰值包速率、PGW-U GTP based S5/S8/S2a/S2b上行用户面报文峰值千字节速率、PGW-U GTP based S5/S8/S2a/S2b下行用户面报文包数、PGW-U GTP based S5/S8/S2a/S2b下行用户面报文千字节数、PGW-U GTP based S5/S8/S2a/S2b下行用户面报文峰值包速率、PGW-U GTP based S5/S8/S2a/S2b下行用户面报文峰值千字节速率、PGW-U SGi下行用户面报文包数、PGW-U SGi下行用户面报文千字节数、PGW-U SGi下行用户面报文峰值包速率、PGW-U SGi下行用户面报文峰值千字节速率、PGW-U SGi上行用户面报文包数、PGW-U SGi上行用户面报文千字节数、PGW-U SGi上行用户面报文峰值包速率、PGW-U SGi上行用户面报文峰值千字节速率、PGW-U SGi下行超过1500字节的用户面报文包数、PGW-U SGi口出错丢弃的IP包数量。
第一用户面功能实体为UPF时，用户面性能统计项可以为以下数据中的任意一种或多种：UPF N3接口上行用户面报文包数、UPF N3接口上行用户面报文千字节数、UPF N3接口上行用户面报文峰值包速率、UPF N3接口上行用户面报文峰值千字节速率、UPF N3接口下行用户面报文包数、UPF N3接口下行用户面报文千字节数、UPF N3接口下行用户面报文峰值包速率、UPF N3接口下行用户面报文峰值千字节速率、UPF N6接口下行用户面报文包数、UPF N6接口下行用户面报文千字节数、UPF N6接口下行用户面报文峰值包速率、UPF N6接口下行用户面报文峰值千字节速率、UPF N6接口上行用户面报文包数、UPF N6接口上行用户面报文千字节数、UPF N6接口上行用户面报文峰值包速率、UPF N6接口上行用户面报文峰值千字节速率。
602、当用户面功能实体根据会话携带的所归属的控制面功能实体的标识，确定会话归属于第一控制面功能实体时，根据会话下的报文统计性能数据。
具体地，用户面功能实体接收第一信息之后，当用户面功能实体根据会话携带的所归属的控制面功能实体的标识，确定会话归属于第一控制面功能实体时，根据会话下的报文统计性能数据。可选的，用户面功能实体可以以第一时间为周期根据会话下的报文统计第一时间内的性能数据。
其中，所有会话中都携带有所归属的控制面功能实体的标识。归属于控制面功能实体的会话为通过该控制面功能实体创建的会话。例如，控制面功能实体1向用户面功能实体2发送用于建立会话1的请求消息。用户面功能实体2接收该请求消息之后，创建会话1，并在会话1中写入控制面功能实体1的标识。其中，会话1归属于控制面功能实体1。
作为一种可选的实施方式，用户面功能实体接收第一信息之后，可先根据会话携带的所归属的控制面功能实体的标识，确定属于第一控制面功能实体的会话，再根据会话下的报文统计性能数据。
例如，用户面功能实体2具有会话1～5，则用户面功能实体2接收第一信息之后，若检测到会话1～3携带控制面功能实体1的标识，则用户面功能实体2确定会话1～3归属于控制面功能实体1。用户面功能实体2确定会话1～3归属于控制面功能实体1之后，检测会话1～3的报文，并根据会话1～3的报文统计性能数据。用户面功能实体可以以第一时间为周期 根据会话1～3的报文下的报文统计第一时间内的性能数据。例如，在0～5秒内检测到存在会话1的报文，则将统计上行用户面报文包数的计数器加1，又检测到存在会话2的报文时，又将统计上行用户面报文包数的计数器加1，又检测到属于会话1～3的报文时，又将统计上行用户面报文包数的计数器加1，依次类推。若最后在0～5秒内统计出统计上行用户面报文包数为10，则上行用户面报文包数10为控制面功能实体1的用户面性能数据。
作为一种可选的实施方式，当接收到第一报文时，确定第一报文所在会话，第一报文为接收的任一报文；当根据会话携带的所归属的控制面功能实体的标识，确定会话归属于第一控制面功能实体时，根据会话下的报文统计性能数据的具体实施方式为：当根据第一报文所在会话携带的所归属的控制面功能实体的标识，确定第一报文所在会话归属于第一控制面功能实体时，根据第一报文统计性能数据。也就是说，在该实施方式中，每接收到一个报文，就判断该报文所在会话是否归属于第一控制面功能实体，若是，则根据该报文统计性能数据。
例如，用户面功能实体2接收到报文1时，检测报文1所在会话1。若用户面功能实体2检测到会话1中携带控制面功能实体1的标识时，用户面功能实体2根据报文1统计性能数据。例如，性能数据为上行用户面报文包数时，用户面功能实体2将上行用户面报文包数加1。同理，在用户面功能实体2又接收到报文2时，检测报文2所在会话1。若用户面功能实体2检测到会话1中携带控制面功能实体1的标识时，用户面功能实体2根据报文2统计性能数据，用户面功能实体2将上行用户面报文包数又加1。用户面功能实体可以以第一时间为周期统计第一时间内的性能数据。若第一时间为5秒，若在0～5秒内统计出统计上行用户面报文包数为10，则上行用户面报文包数10为控制面功能实体1的用户面性能数据。
通过实施该可选的实施方式，用户面功能实体能够准确地确定归属于第一控制面功能实体的会话的报文，并根据该报文统计第一控制面功能实体对应的用户面性能数据。
603、用户面功能实体将统计得到的性能数据作为第一控制面功能实体对应的用户面性能数据。
可见，通过实施图6所描述的方法，用户面功能实体能够对控制面功能实体对应的用户面性能数据进行统计。
可选的，用户面功能实体将统计得到的性能数据作为第一控制面功能实体对应的用户面性能数据之后，可以第一时间为周期将第一时间内统计的用户面性能数据上报至第一控制面功能实体。
举例来说，用户面功能实体1以5秒为周期将5秒内统计得到的上行用户面报文包数100发送至控制面功能实体1，用户面功能实体2以5秒为周期将5秒内统计得到的上行用户面报文包数200发送至控制面功能实体1。
第一控制面功能实体接收第一控制面功能实体在各个用户面功能实体上的用户面性能数据之后，可汇总用户面性能数据上报给OSS，从而不需要OSS自己接收各个用户面功能实体上的用户面性能数据汇总得到第一控制面功能实体总的用户面性能数据，可为OSS分担负荷。
可选的，用户面功能实体可缓存上报至第一控制面功能实体的用户面性能数据；在第 二时间内接收到第一控制面功能实体反馈的用于指示已收到用户面性能数据的指示消息时，删除缓存的用户面性能数据。例如，用户面功能实体1和用户面功能实体2在上报上行用户面报文包数至控制面功能实体1之后，可缓存上报的上行用户面报文包数，在5秒以内接收到控制面功能实体1反馈的用于指示已收到用户面性能数据的指示消息时，删除缓存的用户面性能数据。在上传用户面性能数据之后不马上删除用户面性能数据，而是将用户面性能数据缓存下来，这样可以避免第一控制面功能实体未接收到用户面性能数据时，造成用户面性能数据丢失。相应地，若在第二时间内未接收到第一控制面功能实体反馈的用于指示已收到用户面性能数据的指示消息时，重新上传缓存的用户面性能数据至第一控制面功能实体。这样可以确保第一控制面功能实体能够成功接收到用户面性能数据。
当然，用户面功能实体将统计得到的性能数据作为第一控制面功能实体对应的用户面性能数据之后，也可直接用户面性能数据上报给OSS。
请参见图7，图7是本申请实施例提供的另一种性能数据统计方法的流程示意图。如图7所示，该性能数据统计方法包括如下701～704部分，其中：
701、第一控制面功能实体以第一时间为周期统计第一时间内的控制面性能数据。
其中，第一控制面功能实体可以是任意一个控制面功能实体。例如，可以是图5中的控制面功能实体1或控制面功能实体2。
例如，第一控制面功能实体可以以5秒为周期统计5秒内控制面性能数据。例如，统计0～5秒内的控制面性能数据之后，再统计5～10秒内的控制面性能数据，再统计10～15秒内的控制面性能数据，依次类推。
举例来说，第一控制面功能实体为SGW-C时，控制面性能数据可以为以下数据中的任意一种或多种：S5/S8(SGW-C)发送创建缺省承载请求消息数、S5/S8(SGW-C)接收创建缺省承载成功响应消息数、S5/S8(SGW-C)接收创建缺省承载失败响应消息数、S5/S8(SGW-C)接收创建专有承载请求消息数、S5/S8(SGW-C)发送创建专有承载成功响应消息数、S5/S8(SGW-C)发送创建专有承载失败响应消息数、S5/S8(SGW-C)发送更新承载请求消息数、S5/S8(SGW-C)接收更新承载成功响应消息数、S5/S8(SGW-C)接收更新承载失败响应消息数、S5/S8(SGW-C)接收更新承载请求消息数、S5/S8(SGW-C)发送更新承载成功响应消息数、S5/S8(SGW-C)发送更新承载失败响应消息数、S5/S8(SGW-C)发送删除承载请求消息数、S5/S8(SGW-C)接收删除承载成功响应消息数、S5/S8(SGW-C)接收删除承载失败响应消息数、S5/S8(SGW-C)接收删除承载请求消息数、S5/S8(SGW-C)发送删除承载成功响应消息数、S5/S8(SGW-C)发送删除承载失败响应消息数、S5/S8(SGW-C)发送承载资源变更消息数。
第一控制面功能实体为PGW-C时，控制面性能数据可以为以下数据中的任意一种或多种：S5/S8/S2a/S2b(PGW-C)接收创建缺省承载请求消息数、S5/S8/S2a/S2b(PGW-C)发送创建缺省承载成功响应消息数、S5/S8/S2a/S2b(PGW-C)发送创建缺省承载失败响应消息数、S5/S8/S2a/S2b(PGW-C)发送创建专有承载请求消息数、S5/S8/S2a/S2b(PGW-C)接收创建专有承载成功响应消息数、S5/S8/S2a/S2b(PGW-C)接收创建专有承载失败响应消息数、S5/S8/S2a/S2b(PGW-C)发送更新承载请求消息数、S5/S8/S2a/S2b(PGW-C)接收更新承载成功响应消息数、S5/S8/S2a/S2b(PGW-C)接收更新承载失败响应消息数、S5/S8/S2a/S2b (PGW-C)接收更新承载请求消息数、S5/S8/S2a/S2b(PGW-C)发送更新承载成功响应消息数、S5/S8/S2a/S2b(PGW-C)发送更新承载失败响应消息数、S5/S8/S2a/S2b(PGW-C)发送删除承载请求消息数、S5/S8/S2a/S2b(PGW-C)接收删除承载成功响应消息数、S5/S8/S2a/S2b(PGW-C)接收删除承载失败响应消息数、S5/S8/S2a/S2b(PGW-C)接收删除承载请求消息数、S5/S8/S2a/S2b(PGW-C)发送删除承载成功响应消息数、S5/S8/S2a/S2b(PGW-C)发送删除承载失败响应消息数、S5/S8/S2a/S2b(PGW-C)接收承载资源变更消息数。
第一控制面功能实体为SMF时，控制面性能数据可以为以下数据中的任意一种或多种：MF接收PDU会话创建请求消息数、SMF发送N4会话创建请求消息数、SMF接收N4会话创建成功响应消息数、SMF接收N4会话创建失败响应消息数、SMF发送PDU会话创建成功响应消息数、SMF发送PDU会话创建失败响应消息数、SMF接收PDU会话修改请求消息数、SMF发送N4会话修改请求消息数、SMF接收N4会话修改成功响应消息数、SMF接收N4会话修改失败响应消息数、SMF发送PDU会话修改成功响应消息数、SMF发送PDU会话修改失败响应消息数、SMF接收PDU会话删除请求消息数、SMF发送N4会话删除请求消息数、SMF接收N4会话删除成功响应消息数、SMF接收N4会话删除失败响应消息数、SMF发送PDU会话删除成功响应消息数、SMF发送PDU会话删除失败响应消息数。
702、第一控制面功能实体向第一控制面功能实体管理的一个或多个用户面功能实体发送第一信息。
其中，该第一信息用于指示对第一控制面功能实体对应的用户面性能数据进行统计，该第一信息携带第一控制面功能实体的标识。第一控制面功能实体的标识为用于确定第一控制面功能实体的身份的信息。其中，步骤702中的用户面功能实体为第一控制面功能实体管理的用户面功能实体。图7中以第一控制面功能实体管理两个用户面功能实体为例，当然第一控制面功能实体还可管理两个以上的用户面功能实体，相应地，图7中的用户面功能实体为两个以上。或者第一控制面功能实体还可管理一个用户面功能实体，相应地，图7中的用户面功能实体为一个。
例如，第一控制面功能实体为控制面功能实体1时，第一控制面功能实体向用户面功能实体1和用户面功能实体2发送第一信息。第一控制面功能实体为控制面功能实体2时，第一控制面功能实体向用户面功能实体2和用户面功能实体3发送第一信息。通过第一控制面功能实体向用户面功能实体发送用于指示对第一控制面功能实体对应的用户面性能数据进行统计的第一信息，OSS不需要向每个控制面功能实体和每个用户面功能实体发送用于指示对第一控制面功能实体对应的用户面性能数据进行统计的第一信息，从而可分担OSS的负荷。
可选的，第一控制面功能实体可以在预设时间点执行步骤701以及向其管理的一个或多个用户面功能实体发送第一信息。通过实施该实施方式，第一控制面功能实体可以在预设时间点开始自动统计控制面性能数据，并由第一控制面功能实体在预设时间点自动向用户面功能实体发送用于指示对第一控制面功能实体对应的用户面性能数据进行统计的第一信息。从而不需要OSS向每个控制面功能实体和每个用户面功能实体发送用于指示对性能数据进行统计的信息，从而可分担OSS的负荷。
或者，第一控制面功能实体可接收运营支撑系统OSS发送的指示信息，该指示信息用于指示第一控制面功能实体对控制面性能数据进行统计，以及对第一控制面功能实体对应的用户面性能数据进行统计。第一控制面功能实体接收该指示信息之后，执行步骤701以及向其管理的一个或多个用户面功能实体发送第一信息。通过实施该实施方式，OSS可只向控制面功能实体发送用于性能统计的信息，OSS不需要向每个控制面功能实体和每个用户面功能实体发送用于性能统计的信息，从而可分担OSS的负荷。其中，该指示信息可携带第一时间，或者该指示信息中还可携带需要统计的控制面性能统计项的标识和用户面性能统计项的标识。
703、当用户面功能实体根据会话携带的所归属的控制面功能实体的标识，确定会话归属于第一控制面功能实体时，根据会话下的报文统计性能数据。
704、用户面功能实体将统计得到的性能数据作为第一控制面功能实体对应的用户面性能数据。
步骤703和704可参见602和603的描述，在此不赘述。
可见，通过实施图7所描述的方法，用户面功能实体能够对控制面功能实体对应的用户面性能数据进行统计。
可选的，如图8所示，用户面功能实体将统计得到的性能数据作为第一控制面功能实体对应的用户面性能数据之后，可以第一时间为周期将第一时间内统计的用户面性能数据上报至第一控制面功能实体。第一控制面功能实体可执行以下步骤：以第一时间为周期接收控制面功能实体管理的一个或多个用户面功能实体上报的在第一时间内统计的用户面性能数据；汇总一个或多个用户面功能实体上报的在第一时间内统计的用户面性能数据；向运营支撑系统OSS上报控制面性能数据和汇总的用户面性能数据。或者，第一控制面功能实体以第一时间为周期接收控制面功能实体管理的一个或多个用户面功能实体上报的在第一时间内统计的用户面性能数据之后，可不对用户面性能数据进行汇总，可直接上传接收的用户面性能数据至OSS。这样运营商在OSS观察性能统计数据之后，可修改UPF选择策略，以实现多个UPF之间的负荷分担。
举例来说，用户面功能实体1以5秒为周期将5秒内统计得到的上行用户面报文包数100发送至控制面功能实体1，用户面功能实体2以5秒为周期将5秒内统计得到的上行用户面报文包数200发送至控制面功能实体1。控制面功能实体1接收用户面功能实体1和用户面功能实体2发送的上行用户面报文包数100和上行用户面报文包数200之后，将上行用户面报文包数进行汇总，即将上行用户面报文包数进行相加得到300。上行用户面报文包数300为控制面功能实体1总的用户面性能数据，控制面功能实体1将上行用户面报文包数300和自身检测到的控制面性能数据上报给OSS，以便OSS对性能数据进行分析。
第一控制面功能实体接收第一控制面功能实体在各个用户面功能实体上的用户面性能数据之后，汇总用户面性能数据上报给OSS，从而不需要OSS自己接收各个用户面功能实体上的用户面性能数据汇总得到第一控制面功能实体总的用户面性能数据，可为OSS分担负荷。
可选的，用户面功能实体可缓存上报至第一控制面功能实体的用户面性能数据；在第二时间内接收到第一控制面功能实体反馈的用于指示已收到用户面性能数据的指示消息时， 删除缓存的用户面性能数据。在上传用户面性能数据之后不马上删除用户面性能数据，而是将用户面性能数据缓存下来，这样可以避免第一控制面功能实体未接收到用户面性能数据时，造成用户面性能数据丢失。相应地，若在第二时间内未接收到第一控制面功能实体反馈的用于指示已收到用户面性能数据的指示消息时，重新上传缓存的用户面性能数据至第一控制面功能实体。这样可以确保第一控制面功能实体能够成功接收到用户面性能数据。
当然，用户面功能实体将统计得到的性能数据作为第一控制面功能实体对应的用户面性能数据之后，也可直接用户面性能数据上报给OSS。
请参见图9，图9是本申请实施例提供的另一种性能数据统计方法的流程示意图。如图9所示，该性能数据统计方法包括如下901～905部分，其中：
901、用户面功能实体接收第一信息。
其中，第一信息用于指示对控制面功能实体和第一实例对应的用户面性能数据进行统计，第一信息携带第一控制面功能实体的标识和第一实例的标识。第一控制面功能实体的标识为用于确定第一控制面功能实体的身份的信息。第一实例的标识为用于确定第一实例的身份的信息。其中，步骤901中的用户面功能实体为第一控制面功能实体管理的用户面功能实体。其中，第一实例可以是APN、OCS、CS、DRA、HPLMN、SGSN、PCRF中的任意一种。
可选的，第一信息中可携带第一时间，这样用户面功能实体接收第一信息之后，可以第一时间为周期统计第一时间内的用户面性能数据。第一信息中也可携带第一实例对应的用户面性能统计项的标识，如用户面性能统计项的ID或名称等，这样用户面功能实体接收第一信息之后，可以根据第一实例对应的用户面性能统计项的标识统计用户面性能数据。
可选的，第一信息可来自OSS或第一控制面功能实体，或来自其他设备，本申请实施例不做限定。
可选的，若第一信息来自OSS，则OSS还可向第一控制面功能实体发送用于指示统计第一实例对应的控制面性能数据的指示信息。第一控制面功能实体接收该指示信息之后，就以第一时间为周期统计所述第一时间内第一实例对应的控制面性能数据。也就是说，在该可选的方式中，由OSS向第一控制面功能实体和用户面功能实体分别发送用于指示进行性能统计的信息。其中，该指示信息可携带第一时间，或第一时间可以是第一控制面功能实体默认设置的。该指示信息中还可携带需要统计的第一实例对应的控制面性能统计项的标识，如控制面性能统计项的ID或名称等。
第一信息来自第一控制面功能实体的具体实施方式可参见图10所对应的描述。
举例来说，第一实例对应的用户面性能统计项可以为：用户平面L2TP性能测量(指定APN)、SGW-U和PGW-U合一形态转发性能测量(指定APN)、用户平面用户基本会话业务测量(指定VPLMN)、用户平面转发性能测量(指定VPLMN)、用户平面基本会话业务测量(指定APN)、用户平面业务实例性能测量(指定业务实例)、用户平面转发性能测量(指定TAC)、用户平面转发性能测量(指定TAC Group)。
902、第一控制面功能实体向管理的任意一个用户面功能实体发送用于请求建立第一会话的请求消息，该请求消息携带实例的标识。
其中，实例的标识为能够确定实例身份的信息。
903、用户面功能实体建立第一会话，并在第一会话中写入第一控制面功能实体的标识和请求消息中的实例的标识。
其中，第一会话为任意一个会话。若第一信息来自OSS，则OSS需要将实例的标识发送至第一控制面功能实体。若第一控制面功能实体接收到用户终端发送的用于建立实例对应的第一会话的请求，则第一控制面功能实体向管理的任意一个用户面功能实体发送用于请求建立第一会话的请求消息，该请求消息携带实例的标识。用户面功能实体接收该请求消息之后，建立第一会话，并在第一会话中写入第一控制面功能实体的标识和请求消息中的实例的标识。
若第一信息来自第一控制面功能实体，第一控制面功能实体可以为实例分配标识。若第一控制面功能实体接收到用户终端发送的用于建立实例对应的第一会话的请求，则第一控制面功能实体向管理的任意一个用户面功能实体发送用于请求建立第一会话的请求消息，该请求消息携带第一控制面功能实体分配的实例的标识。用户面功能实体接收该请求消息之后，建立第一会话，并在第一会话中写入第一控制面功能实体的标识和请求消息中的实例的标识。
通过执行步骤902和903，可以对第一会话所归属的控制面功能实体和实例进行标记，从而有利于查找到制面功能实体和实例对应的会话。
当然也可以不通过902和903的方式在第一会话中记录第一控制面功能实体的标识和实例的标识，可通过其他方式在第一会话中记录第一控制面功能实体的标识和实例的标识。
904、当用户面功能实体根据会话携带的所归属的控制面功能实体的标识和实例的标识，确定会话归属于第一控制面功能实体和第一实例时，根据会话下的报文统计性能数据。
具体地，用户面功能实体接收第一信息之后，当用户面功能实体根据会话携带的所归属的控制面功能实体的标识和第一实例的标识，确定会话归属于第一控制面功能实体和第一实例时，根据会话下的报文统计性能数据。用户面功能实体可以以第一时间为周期根据会话下的报文对第一时间内第一实例的性能数据进行统计。
作为一种可选的实施方式，用户面功能实体接收第一信息之后，可先根据会话携带的所归属的控制面功能实体的标识和第一实例的标识，确定属于第一控制面功能实体和第一实例的会话，再根据会话下的报文统计性能数据。
作为一种可选的实施方式，当接收到第一报文时，确定第一报文所在会话，第一报文为接收的任一报文；当根据会话携带的所归属的控制面功能实体的标识和实例的标识，确定会话归属于第一控制面功能实体和第一实例时，根据会话下的报文统计性能数据的具体实施方式为：当根据第一报文所在会话携带的所归属的控制面功能实体的标识和实例的标识，确定第一报文所在会话归属于第一控制面功能实体和第一实例时，根据第一报文统计性能数据。也就是说，在该实施方式中，每接收到一个报文，就判断该报文所在会话是否归属于第一控制面功能实体和第一实例，若是，则根据该报文统计性能数据。
通过实施该可选的实施方式，用户面功能实体能够准确地确定归属于第一控制面功能实体和第一实例的会话的报文，并根据该报文统计第一控制面功能实体和第一实例对应的用户面性能数据。
905、用户面功能实体将统计得到的性能数据作为第一控制面功能实体和第一实例对应的用户面性能数据。
现有技术中用户面功能实体无法区分某些实例对应的会话，从而导致用户面功能实体无法对某些实例对应的用户面性能数据进行统计。可见，通过实施图9所描述的方法，用户面功能实体能够对控制面功能实体和指定实例对应的用户面性能数据进行统计。
可选的，用户面功能实体将统计得到的性能数据作为第一控制面功能实体和第一实例对应的用户面性能数据之后，可以第一时间为周期将第一时间内统计的用户面性能数据上报至第一控制面功能实体。
可选的，缓存上报至第一控制面功能实体的用户面性能数据；在第二时间内接收到第一控制面功能实体反馈的用于指示已收到用户面性能数据的指示消息时，删除缓存的用户面性能数据。在上传用户面性能数据之后不马上删除用户面性能数据，而是将用户面性能数据缓存下来，这样可以避免第一控制面功能实体未接收到用户面性能数据时，造成用户面性能数据丢失。相应地，若在第二时间内未接收到第一控制面功能实体反馈的用于指示已收到用户面性能数据的指示消息时，重新上传缓存的用户面性能数据至第一控制面功能实体。这样可以确保第一控制面功能实体能够成功接收到用户面性能数据。
当然，用户面功能实体将统计得到的性能数据作为第一控制面功能实体和第一实例对应的用户面性能数据之后，也可直接将用户面性能数据上报给OSS。
请参见图10，图10是本申请实施例提供的另一种性能数据统计方法的流程示意图。如图10所示，该性能数据统计方法包括如下1001～1006部分，其中：
1001、第一控制面功能实体以第一时间为周期统计第一时间内第一实例对应的控制面性能数据。
其中，第一控制面功能实体可以是任意一个控制面功能实体。例如，可以是图5中的控制面功能实体1或控制面功能实体2。
例如，第一控制面功能实体可以以5秒为周期统计5秒内第一实例对应的控制面性能数据。例如，统计0～5秒内第一实例对应的控制面性能数据之后，再统计5～10秒内第一实例对应的控制面性能数据，再统计10～15秒内第一实例对应的控制面性能数据，依次类推。
其中，第一实例可以是APN、OCS、CS、DRA、HPLMN、SGSN、PCRF中的任意一种。例如，第一实例对应的控制面性能统计项可以为：SGW-C基本会话业务测量(指定APN)、PGW-C基本会话业务测量(指定APN)、控制平面基本会话业务测量(指定APN)、控制平面在线计费业务性能测量(指定OCS)、控制平面Ga接口性能测量(指定CG)、PGW-C 3G会话性能测量(指定APN)、PGW-C 2G会话性能测量(指定APN)、控制平面会话状态统计(指定APN)、控制平面Diameter性能统计项(指定DRA)、控制平面AAA性能测量(指定APN)、PGW-C 2/3G会话性能测量(指定APN、分业务类型)、GW控制平面基本会话性能测量(指定HPLMN)、PGW-C 2/3G测量基本会话性能(指定SGSN)、控制平面Gx接口性能测量(指定APN)、控制平面PCC会话测量(指定APN)、SGW-C和PGW-C合一形态基本会话业务测量(指定APN)、控制平面Gx接口性能测量(指定PCRF主机)、控制平面PCC会话测量(指定PCRF主机)、控制平面在线计费命令层返回码测量(指定OCS)、控制平面在线计费业务层 返回码测量(指定OCS)、控制平面GW用户基本会话业务测量(指定VPLMN)。
1002、第一控制面功能实体向第一控制面功能实体管理的一个或多个用户面功能实体发送第一信息。
其中，第一信息用于指示对控制面功能实体和第一实例对应的用户面性能数据进行统计，第一信息携带第一控制面功能实体的标识和第一实例的标识。第一控制面功能实体的标识为用于确定第一控制面功能实体的身份的信息。第一实例的标识为用于确定第一实例的身份的信息。其中，步骤1002中的用户面功能实体为第一控制面功能实体管理的用户面功能实体。
可选的，第一信息中可携带第一时间，这样用户面功能实体接收第一信息之后，可以第一时间为周期根据属于第一控制面功能实体和第一实例的会话下的报文统计第一时间内的用户面性能数据。当然第一信息中也可不携带第一时间，用户面功能实体可以以默认设置的时间为第一时间，并以第一时间为周期统计第一时间内的用户面性能数据。
第一信息中也可携带用户面性能统计项的标识，如用户面性能统计项的ID或名称等。这样用户面功能实体接收携带用户面性能统计项的标识的第一信息之后，可以根据属于第一控制面功能实体和第一实例的会话下的报文统计该用户面性能统计项的用户面性能数据。即用户面功能实体根据属于第一控制面功能实体和第一实例的会话下的报文仅统计和上报其订阅的性能统计项，不用对所有的性能统计项进行统计和上报。当然，若第一信息中不携带用户面性能统计项的标识，用户面功能实体针对属于该控制面功能实体和第一实例的会话的报文可以对默认设置的性能统计项进行统计。
通过第一控制面功能实体向用户面功能实体发送用于指示对第一控制面功能实体和第一实例对应的用户面性能数据进行统计的第一信息，OSS不需要向每个控制面功能实体和每个用户面功能实体发送用于指示对第一控制面功能实体和第一实例对应的用户面性能数据进行统计的第一信息，从而可分担OSS的负荷。
可选的，第一控制面功能实体可以在预设时间点执行步骤1001以及向其管理的一个或多个用户面功能实体发送第一信息。或者，第一控制面功能实体可接收运营支撑系统OSS发送的指示信息，该指示信息用于指示第一控制面功能实体对控制面性能数据进行统计，以及对第一控制面功能实体和第一实例对应的用户面性能数据进行统计。第一控制面功能实体接收该指示信息之后，执行步骤1001以及向其管理的一个或多个用户面功能实体发送第一信息。通过实施该实施方式，OSS可只向控制面功能实体发送用于性能统计的信息，OSS不需要向每个控制面功能实体和每个用户面功能实体发送用于性能统计的信息，从而可分担OSS的负荷。其中，该指示信息可携带第一时间，或者该指示信息中还可携带需要统计的第一实例对应的控制面性能统计项的标识和用户面性能统计项的标识。
1003、第一控制面功能实体向管理的任意一个用户面功能实体发送用于请求建立第一会话的请求消息，该请求消息携带实例的标识。
其中，实例的标识为能够确定实例身份的信息。
1004、用户面功能实体建立第一会话，并在第一会话中写入第一控制面功能实体的标识和请求消息中的实例的标识。
第一控制面功能实体可以为实例分配标识。若第一控制面功能实体接收到用户终端发 送的用于建立实例对应的第一会话的请求，则第一控制面功能实体向管理的任意一个用户面功能实体发送用于请求建立第一会话的请求消息，该请求消息携带第一控制面功能实体分配的实例的标识。用户面功能实体接收该请求消息之后，建立第一会话，并在第一会话中写入第一控制面功能实体的标识和请求消息中的实例的标识。
通过执行步骤1003和1004，可以对第一会话所归属的控制面功能实体和实例进行标记，从而有利于查找到制面功能实体和实例对应的会话。
当然也可以不通过1003和1004的方式在第一会话中记录第一控制面功能实体的标识和实例的标识，可通过其他方式在第一会话中记录第一控制面功能实体的标识和实例的标识。
1005、当根据会话携带的所归属的控制面功能实体的标识和实例的标识，确定会话归属于第一控制面功能实体和第一实例时，根据会话下的报文统计性能数据。
1006、将统计得到的性能数据作为第一控制面功能实体和第一实例对应的用户面性能数据。
步骤1005和1006可参见904和905的描述，在此不赘述。
现有技术中用户面功能实体无法区分某些实例对应的会话，从而导致用户面功能实体无法对某些实例对应的用户面性能数据进行统计。可见，通过实施图10所描述的方法，用户面功能实体能够对控制面功能实体和指定实例对应的用户面性能数据进行统计。
可选的，如图11所示，用户面功能实体将统计得到的性能数据作为第一控制面功能实体和第一实例对应的用户面性能数据之后，可以第一时间为周期将第一时间内统计的用户面性能数据上报至第一控制面功能实体。相应地，第一控制面功能实体可执行以下步骤：以第一时间为周期接收控制面功能实体管理的一个或多个用户面功能实体上报的在第一时间内统计的用户面性能数据；汇总一个或多个用户面功能实体上报的在第一时间内统计的用户面性能数据；向运营支撑系统OSS上报控制面性能数据和汇总的用户面性能数据。
可选的，缓存上报至第一控制面功能实体的用户面性能数据；在第二时间内接收到第一控制面功能实体反馈的用于指示已收到用户面性能数据的指示消息时，删除缓存的用户面性能数据。在上传用户面性能数据之后不马上删除用户面性能数据，而是将用户面性能数据缓存下来，这样可以避免第一控制面功能实体未接收到用户面性能数据时，造成用户面性能数据丢失。相应地，若在第二时间内未接收到第一控制面功能实体反馈的用于指示已收到用户面性能数据的指示消息时，重新上传缓存的用户面性能数据至第一控制面功能实体。这样可以确保第一控制面功能实体能够成功接收到用户面性能数据。
当然，用户面功能实体将统计得到的性能数据作为第一控制面功能实体和第一实例对应的用户面性能数据之后，也可直接将用户面性能数据上报给OSS。
本发明实施例可以根据上述方法示例对设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
请参见图12，图12是本发明实施提供的一种用户面功能实体。用户面功能实体可以执行上述方法实施例中用户面功能实体所执行的方法。该用户面功能实体包括通信模块1201和处理模块1202。其中：
通信模块1201，用于接收第一信息，第一信息用于指示对第一控制面功能实体对应的用户面性能数据进行统计，第一信息携带第一控制面功能实体的标识；处理模块1202，用于当根据会话携带的所归属的控制面功能实体的标识，确定会话归属于第一控制面功能实体时，根据会话下的报文统计性能数据；处理模块1202，还用于将统计得到的性能数据作为第一控制面功能实体对应的用户面性能数据。
可选的，处理模块1202，还用于当接收到第一报文时，确定第一报文所在会话，第一报文为接收的任一报文；当处理模块1202根据会话携带的所归属的控制面功能实体的标识，确定会话归属于第一控制面功能实体时，处理模块1202根据会话下的报文统计性能数据的方式具体为：当处理模块1202根据第一报文所在会话携带的所归属的控制面功能实体的标识，确定第一报文所在会话归属于第一控制面功能实体时，处理模块1202根据第一报文统计性能数据。
可选的，第一信息用于指示对第一控制面功能实体和第一实例对应的用户面性能数据进行统计，第一信息还携带第一实例的标识；当处理模块1202根据会话携带的所归属的控制面功能实体的标识，确定会话归属于第一控制面功能实体时，处理模块1202根据会话下的报文统计性能数据的方式具体为：当根据会话携带的所归属的控制面功能实体的标识和实例的标识，确定会话归属于第一控制面功能实体和第一实例时，根据会话下的报文统计性能数据；处理模块1202将统计得到的性能数据作为第一控制面功能实体对应的用户面性能数据的方式具体为：将统计得到的性能数据作为第一控制面功能实体和第一实例对应的用户面性能数据。
可选的，通信模块1201，还用于接收第一控制面功能实体发送的用于请求建立第一会话的请求消息，请求消息携带实例的标识；处理模块1202，还用于建立第一会话，并在第一会话中写入第一控制面功能实体的标识和请求消息中的实例的标识。
可选的，第一信息来自第一控制功能实体或运营支撑系统OSS，通信模块1201，还用于以第一时间为周期将第一时间内统计的用户面性能数据上报至第一控制面功能实体。
可选的，处理模块1202，还用于缓存上报至第一控制面功能实体的用户面性能数据；处理模块1202，还用于在第二时间内接收到第一控制面功能实体反馈的用于指示已收到用户面性能数据的指示消息时，删除缓存的用户面性能数据。
可选的，第一信息中还携带第一时间。
可选的，第一信息中还携带性能统计项的标识。
请参见图13，图13是本发明实施提供的一种控制面功能实体。控制面功能实体可以执行上述方法实施例中控制面功能实体所执行的方法。该控制面功能实体包括通信模块1301和处理模块1302。其中：
处理模块1302，用于以第一时间为周期统计第一时间内的控制面性能数据；通信模块1301，用于向控制面功能实体管理的一个或多个用户面功能实体发送第一信息，第一信息 用于指示对控制面功能实体对应的用户面性能数据进行统计，第一信息携带控制面功能实体的标识。
可选的，第一信息用于指示对控制面功能实体和第一实例对应的用户面性能数据进行统计，第一信息还携带第一实例的标识；处理模块1302以第一时间为周期统计第一时间内的控制面性能数据的方式具体为：以第一时间为周期统计第一时间内第一实例对应的控制面性能数据。
可选的，通信模块1301，还用于向控制面功能实体管理的任意一个用户面功能实体发送用于请求建立第一会话的请求消息，请求消息携带实例的标识。
可选的，通信模块1301，还用于以第一时间为周期接收控制面功能实体管理的一个或多个用户面功能实体上报的在第一时间内统计的用户面性能数据；处理模块1302，还用于汇总一个或多个用户面功能实体上报的在第一时间内统计的用户面性能数据；通信模块1301，还用于向运营支撑系统OSS上报控制面性能数据和汇总的用户面性能数据。
可选的，第一信息中还携带第一时间。
可选的，第一信息中还携带性能统计项的标识。
请参见图14，图14是本申请实施例公开的一种用户面功能实体的结构示意图。如图14所示，该用户面功能实体1400包括处理器1401、存储器1402和通信接口1403。其中，处理器1401、存储器1402和通信接口1403相连。
其中，处理器1401可以是中央处理器(central processing unit，CPU)，通用处理器，协处理器，数字信号处理器(digital signal processor，DSP)，专用集成电路(application-specific integrated circuit，ASIC)，现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。该处理器1401也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
其中，通信接口1403用于实现与控制面功能实体之间的通信。
其中，处理器1401调用存储器1402中存储的程序代码，可执行上述方法实施例中用户面功能实体所执行的步骤。
基于同一发明构思，本申请实施例中提供的各装置解决问题的原理与本申请方法实施例相似，因此各装置的实施可以参见方法的实施，为简洁描述，在这里不再赘述。
请参见图15，图15是本申请实施例公开的一种控制面功能实体的结构示意图。如图15所示，该控制面功能实体1500包括处理器1501、存储器1502和通信接口1503。其中，处理器1501、存储器1502和通信接口1503相连。
其中，处理器1501可以是中央处理器(central processing unit，CPU)，通用处理器，协处理器，数字信号处理器(digital signal processor，DSP)，专用集成电路(application-specific integrated circuit，ASIC)，现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。该处理器1501也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
其中，通信接口1503用于实现与控制面功能实体之间的通信。
其中，处理器1501调用存储器1502中存储的程序代码，可执行上述方法实施例中第一控制面功能实体所执行的步骤。
基于同一发明构思，本申请实施例中提供的各装置解决问题的原理与本申请方法实施例相似，因此各装置的实施可以参见方法的实施，为简洁描述，在这里不再赘述。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
最后应说明的是：以上各实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述各实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (28)

  1. 一种性能数据统计方法，其特征在于，应用于用户面功能实体，所述方法包括：
    接收第一信息，所述第一信息用于指示对第一控制面功能实体对应的用户面性能数据进行统计，所述第一信息携带所述第一控制面功能实体的标识；
    当根据会话携带的所归属的控制面功能实体的标识，确定所述会话归属于所述第一控制面功能实体时，根据所述会话下的报文统计性能数据；
    将统计得到的性能数据作为所述第一控制面功能实体对应的用户面性能数据。
  2. 根据权利要求1所述的方法，其特征在于，所述当根据会话携带的所归属的控制面功能实体的标识，确定所述会话归属于所述第一控制面功能实体时，根据所述会话下的报文统计性能数据之前，所述方法还包括：
    当接收到第一报文时，确定所述第一报文所在会话，所述第一报文为接收的任一报文；
    当根据会话携带的所归属的控制面功能实体的标识，确定所述会话归属于所述第一控制面功能实体时，根据所述会话下的报文统计性能数据，包括：
    当根据所述第一报文所在会话携带的所归属的控制面功能实体的标识，确定所述第一报文所在会话归属于所述第一控制面功能实体时，根据所述第一报文统计性能数据。
  3. 根据权利要求1所述的方法，其特征在于，所述第一信息用于指示对第一控制面功能实体和第一实例对应的用户面性能数据进行统计，所述第一信息还携带所述第一实例的标识；
    所述当根据会话携带的所归属的控制面功能实体的标识，确定所述会话归属于所述第一控制面功能实体时，根据所述会话下的报文统计性能数据，包括：
    当根据会话携带的所归属的控制面功能实体的标识和实例的标识，确定所述会话归属于所述第一控制面功能实体和所述第一实例时，根据所述会话下的报文统计性能数据；
    所述将统计得到的性能数据作为所述第一控制面功能实体对应的用户面性能数据，包括：
    将统计得到的性能数据作为所述第一控制面功能实体和所述第一实例对应的用户面性能数据。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    接收所述第一控制面功能实体发送的用于请求建立第一会话的请求消息，所述请求消息携带实例的标识；
    建立所述第一会话，并在所述第一会话中写入所述第一控制面功能实体的标识和所述请求消息中的实例的标识。
  5. 根据权利要求1-4任意一项所述的方法，其特征在于，所述第一信息来自所述第一控制功能实体或运营支撑系统OSS，所述方法还包括：
    以第一时间为周期将所述第一时间内统计的所述用户面性能数据上报至所述第一控制面功能实体。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    缓存上报至所述第一控制面功能实体的用户面性能数据；
    在第二时间内接收到所述第一控制面功能实体反馈的用于指示已收到用户面性能数据的指示消息时，删除缓存的用户面性能数据。
  7. 根据权利要求5或6所述的方法，其特征在于，所述第一信息中还携带所述第一时间。
  8. 根据权利要求1-7任意一项所述的方法，其特征在于，所述第一信息中还携带性能统计项的标识。
  9. 一种性能数据统计方法，其特征在于，应用于控制面功能实体，所述方法包括：
    以第一时间为周期统计所述第一时间内的控制面性能数据；
    向所述控制面功能实体管理的一个或多个用户面功能实体发送第一信息，所述第一信息用于指示对所述控制面功能实体对应的用户面性能数据进行统计，所述第一信息携带所述控制面功能实体的标识。
  10. 根据权利要求9所述的方法，其特征在于，所述第一信息用于指示对所述控制面功能实体和所述第一实例对应的用户面性能数据进行统计，所述第一信息还携带所述第一实例的标识；
    以第一时间为周期统计所述第一时间内的控制面性能数据，包括：
    以第一时间为周期统计所述第一时间内所述第一实例对应的控制面性能数据。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    向所述控制面功能实体管理的任意一个用户面功能实体发送用于请求建立所述第一会话的请求消息，所述请求消息携带实例的标识。
  12. 根据权利要求9-11任意一项所述的方法，其特征在于，所述方法还包括：
    以所述第一时间为周期接收所述控制面功能实体管理的一个或多个用户面功能实体上报的在所述第一时间内统计的用户面性能数据；
    汇总所述一个或多个用户面功能实体上报的在所述第一时间内统计的用户面性能数据；
    向运营支撑系统OSS上报所述控制面性能数据和汇总的用户面性能数据。
  13. 根据权利要求12所述的方法，其特征在于，所述第一信息中还携带所述第一时间。
  14. 根据权利要求9-12任意一项所述的方法，其特征在于，所述第一信息中还携带性能统计项的标识。
  15. 一种用户面功能实体，其特征在于，所述用户面功能实体包括：
    通信模块，用于接收第一信息，所述第一信息用于指示对第一控制面功能实体对应的用户面性能数据进行统计，所述第一信息携带所述第一控制面功能实体的标识；
    处理模块，用于当根据会话携带的所归属的控制面功能实体的标识，确定所述会话归属于所述第一控制面功能实体时，根据所述会话下的报文统计性能数据；
    所述处理模块，还用于将统计得到的性能数据作为所述第一控制面功能实体对应的用户面性能数据。
  16. 根据权利要求15所述的用户面功能实体，其特征在于，
    所述处理模块，还用于当接收到第一报文时，确定所述第一报文所在会话，所述第一报文为接收的任一报文；
    当所述处理模块根据会话携带的所归属的控制面功能实体的标识，确定所述会话归属于所述第一控制面功能实体时，所述处理模块根据所述会话下的报文统计性能数据的方式具体为：
    当所述处理模块根据所述第一报文所在会话携带的所归属的控制面功能实体的标识，确定所述第一报文所在会话归属于所述第一控制面功能实体时，所述处理模块根据所述第一报 文统计性能数据。
  17. 根据权利要求15所述的用户面功能实体，其特征在于，所述第一信息用于指示对第一控制面功能实体和第一实例对应的用户面性能数据进行统计，所述第一信息还携带所述第一实例的标识；
    当所述处理模块根据会话携带的所归属的控制面功能实体的标识，确定所述会话归属于所述第一控制面功能实体时，所述处理模块根据所述会话下的报文统计性能数据的方式具体为：
    当根据会话携带的所归属的控制面功能实体的标识和实例的标识，确定所述会话归属于所述第一控制面功能实体和所述第一实例时，根据所述会话下的报文统计性能数据；
    所述处理模块将统计得到的性能数据作为所述第一控制面功能实体对应的用户面性能数据的方式具体为：
    将统计得到的性能数据作为所述第一控制面功能实体和所述第一实例对应的用户面性能数据。
  18. 根据权利要求17所述的用户面功能实体，其特征在于，
    所述通信模块，还用于接收所述第一控制面功能实体发送的用于请求建立第一会话的请求消息，所述请求消息携带实例的标识；
    所述处理模块，还用于建立所述第一会话，并在所述第一会话中写入所述第一控制面功能实体的标识和所述请求消息中的实例的标识。
  19. 根据权利要求15-18任意一项所述的用户面功能实体，其特征在于，所述第一信息来自所述第一控制功能实体或运营支撑系统OSS，
    所述通信模块，还用于以第一时间为周期将所述第一时间内统计的所述用户面性能数据上报至所述第一控制面功能实体。
  20. 根据权利要求19所述的用户面功能实体，其特征在于，
    所述处理模块，还用于缓存上报至所述第一控制面功能实体的用户面性能数据；
    所述处理模块，还用于在第二时间内接收到所述第一控制面功能实体反馈的用于指示已收到用户面性能数据的指示消息时，删除缓存的用户面性能数据。
  21. 根据权利要求19或20所述的用户面功能实体，其特征在于，所述第一信息中还携带所述第一时间。
  22. 根据权利要求15-21任意一项所述的用户面功能实体，其特征在于，所述第一信息中还携带性能统计项的标识。
  23. 一种控制面功能实体，其特征在于，所述控制面功能实体包括：
    处理模块，用于以第一时间为周期统计所述第一时间内的控制面性能数据；
    通信模块，用于向所述控制面功能实体管理的一个或多个用户面功能实体发送第一信息，所述第一信息用于指示对所述控制面功能实体对应的用户面性能数据进行统计，所述第一信息携带所述控制面功能实体的标识。
  24. 根据权利要求23所述的控制面功能实体，其特征在于，所述第一信息用于指示对所述控制面功能实体和所述第一实例对应的用户面性能数据进行统计，所述第一信息还携带所述第一实例的标识；
    所述处理模块以第一时间为周期统计所述第一时间内的控制面性能数据的方式具体为：
    以第一时间为周期统计所述第一时间内所述第一实例对应的控制面性能数据。
  25. 根据权利要求24所述的控制面功能实体，其特征在于，
    所述通信模块，还用于向所述控制面功能实体管理的任意一个用户面功能实体发送用于请求建立所述第一会话的请求消息，所述请求消息携带实例的标识。
  26. 根据权利要求23-25任意一项所述的控制面功能实体，其特征在于，
    所述通信模块，还用于以所述第一时间为周期接收所述控制面功能实体管理的一个或多个用户面功能实体上报的在所述第一时间内统计的用户面性能数据；
    所述处理模块，还用于汇总所述一个或多个用户面功能实体上报的在所述第一时间内统计的用户面性能数据；
    所述通信模块，还用于向运营支撑系统OSS上报所述控制面性能数据和汇总的用户面性能数据。
  27. 根据权利要求26所述的控制面功能实体，其特征在于，所述第一信息中还携带所述第一时间。
  28. 根据权利要求23-27所述的控制面功能实体，其特征在于，所述第一信息中还携带性能统计项的标识。
PCT/CN2019/091517 2018-06-21 2019-06-17 一种性能数据统计方法及相关设备 WO2019242578A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810642853.3A CN110636518B (zh) 2018-06-21 2018-06-21 一种性能数据统计方法及相关设备
CN201810642853.3 2018-06-21

Publications (1)

Publication Number Publication Date
WO2019242578A1 true WO2019242578A1 (zh) 2019-12-26

Family

ID=68966473

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/091517 WO2019242578A1 (zh) 2018-06-21 2019-06-17 一种性能数据统计方法及相关设备

Country Status (2)

Country Link
CN (1) CN110636518B (zh)
WO (1) WO2019242578A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105208575A (zh) * 2014-06-30 2015-12-30 中兴通讯股份有限公司 一种网络接口信令监测的信息处理方法及装置
US20170339609A1 (en) * 2016-05-17 2017-11-23 Lg Electronics Inc. Method and apparatus for determining pdu session identity in wireless communication system
WO2018006017A1 (en) * 2016-07-01 2018-01-04 Idac Holdings, Inc. Methods for supporting session continuity on per-session basis
CN107547212A (zh) * 2016-06-24 2018-01-05 中兴通讯股份有限公司 一种基于分离架构的计费方法、装置和系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101197737B (zh) * 2008-01-09 2010-07-14 中兴通讯股份有限公司 一种iptv接入网的测量装置及测量方法
CN106559868B (zh) * 2015-09-25 2019-05-10 电信科学技术研究院 一种跟踪区更新方法及装置
US10142427B2 (en) * 2016-03-31 2018-11-27 Huawei Technologies Co., Ltd. Systems and methods for service and session continuity in software defined topology management
CN107580324B (zh) * 2017-09-22 2020-05-08 中国电子科技集团公司第三十研究所 一种用于移动通信系统imsi隐私保护的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105208575A (zh) * 2014-06-30 2015-12-30 中兴通讯股份有限公司 一种网络接口信令监测的信息处理方法及装置
US20170339609A1 (en) * 2016-05-17 2017-11-23 Lg Electronics Inc. Method and apparatus for determining pdu session identity in wireless communication system
CN107547212A (zh) * 2016-06-24 2018-01-05 中兴通讯股份有限公司 一种基于分离架构的计费方法、装置和系统
WO2018006017A1 (en) * 2016-07-01 2018-01-04 Idac Holdings, Inc. Methods for supporting session continuity on per-session basis

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
3GPP GROUP: "3rd Generation Partnership Project Technical Specification Group Services and System Aspects Study on Architecture for Next Generation System (Release 14)", 3GPP TR 23.799 V1.0.0, 17 September 2016 (2016-09-17), pages 1 - 423, XP055622137 *

Also Published As

Publication number Publication date
CN110636518B (zh) 2020-12-25
CN110636518A (zh) 2019-12-31

Similar Documents

Publication Publication Date Title
US20220247868A1 (en) Charging Method and Device
US11272333B2 (en) Convergent charging method and device
US10772005B2 (en) Systems and methods for tracking and calculating network usage in a network with multiple user plane functions
US10945104B2 (en) Charging method and device
US20180262625A1 (en) System and method for account level maximum bit rate enforcement
US8897749B1 (en) Policy decisions based on subscriber spending limits
CN108024023B (zh) 用于在通信网络中在线计费的系统、方法和可读存储介质
US11233694B2 (en) Method and device for processing communication path
WO2020135848A1 (zh) 计费的方法、装置及系统
WO2021036441A1 (zh) 一种统计业务流量的方法和装置
US11337103B2 (en) Bearer processing method and system, and related apparatus
WO2020143502A1 (zh) 对网络切片实例进行计费处理的方法、系统及相关设备
WO2016107374A1 (zh) 一种带宽控制的方法、装置及系统
WO2019242578A1 (zh) 一种性能数据统计方法及相关设备
US10499213B2 (en) Charging method, control plane network element, forwarding plane network element, and charging system
WO2021027757A1 (zh) 保障数据业务的计费处理方法、系统及相关设备
US20170251355A1 (en) Method and apparatus for obtaining user equipment ue information
CN114554538A (zh) 流量统计方法、装置、电子设备及存储介质
US10771596B2 (en) Service data transmission method and apparatus
WO2022062778A1 (zh) 业务计费方法、通信设备及存储介质
WO2014141785A1 (ja) ネットワークの監視システム及び監視方法
WO2018153193A1 (zh) 一种计费方法及装置
CN106358232A (zh) 蜂窝网中业务速率监测方法、装置和系统

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19823277

Country of ref document: EP

Kind code of ref document: A1