WO2021036441A1 - Procédé et appareil de collecte de statistiques relatives à un trafic de service - Google Patents

Procédé et appareil de collecte de statistiques relatives à un trafic de service Download PDF

Info

Publication number
WO2021036441A1
WO2021036441A1 PCT/CN2020/097553 CN2020097553W WO2021036441A1 WO 2021036441 A1 WO2021036441 A1 WO 2021036441A1 CN 2020097553 W CN2020097553 W CN 2020097553W WO 2021036441 A1 WO2021036441 A1 WO 2021036441A1
Authority
WO
WIPO (PCT)
Prior art keywords
urr
session
flow
user plane
plane function
Prior art date
Application number
PCT/CN2020/097553
Other languages
English (en)
Chinese (zh)
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 WO2021036441A1 publication Critical patent/WO2021036441A1/fr

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/02Arrangements for optimising operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/08Testing, supervising or monitoring using real traffic

Definitions

  • This application relates to the field of communications, and in particular to a method and device for counting business traffic.
  • the 5th generation mobile networks (5G) network is committed to meeting the huge challenges of future diversification and differentiated services. It not only needs to continue to face the challenges brought by mobile Internet services, but also needs to meet the diversification of vertical industries Business requirements, such as ultra-high speed, ultra-low latency, and ultra-high traffic. Therefore, in the 5G network architecture, the uplink classifier (UL CL) or branching point (BP) function is defined to realize the flexible deployment of the application in the network, and the application and the network cooperate to select the optimal data path , To achieve the lowest transmission cost and the highest efficiency to provide bandwidth to reduce business delay.
  • UL CL uplink classifier
  • BP branching point
  • the 5G network allows a session to have multiple user plane functions (UPF) and multiple session anchors at the same time.
  • the 5G network can control different service flows through UL CL/BP to select different session anchor, so as to meet the needs of business diversity.
  • the charging function (CHF) can give all UPF traffic quota management.
  • the session management function (SMF) is required for secondary management of quotas, so as to Multiple UPFs are coordinated and allocated.
  • the SMF determines that the usage of the quota for this session in the multiple UPFs reaches the threshold, the traffic is reported to the CHF.
  • SMF when SMF performs secondary management of quotas, it needs to coordinate and allocate among multiple UPFs. There will be multiple queries and reports between SMF and UPF. This multiple query and report method makes it difficult to accurately control the quota threshold. In other words, the traffic finally aggregated by SMF may exceed the threshold before being reported to CHF, making traffic statistics and reporting inaccurate. Moreover, when two UPFs report traffic at different timings, if the SMF actively queries the UPF for traffic, time loss will occur. Especially in the scenario where the quota is exhausted, the signaling interaction between the SMF and the UPF is increased.
  • a method for counting service traffic including: a first user plane function receives a session establishment request sent by a session management function, the session establishment request includes at least one URR cell corresponding to the session flow, and each URR The cell includes the flow threshold; the first user plane function receives the first downlink data packet, and the first downlink data packet includes the identifier of the session flow, the first URR bit map, and the cumulative flow of the session flow; the URR bit map is used to indicate the accumulation The URR cell involved in the flow; the first user plane function counts the newly added flow of the URR cell indicated by the URR bit chart according to the first downlink data packet.
  • the first user plane function sends a URR notification to the session management function, and the URR notification is used to apply for a new flow threshold for URR cells that reach the flow threshold. Therefore, in the embodiment of the present application, the URR bit map can be carried in the downlink data packet sent by the session anchor (PSA) to the first user plane function to indicate the URR cell or service for which the traffic needs to be counted, which can be convenient for the first user
  • the plane function performs traffic statistics based on the URR bit chart to determine whether to send a URR notification to the SMF to apply for a new traffic threshold. In this way, by carrying the flow URR bit map in the downlink data packet and collecting it through the first user plane function, the power consumption caused by multiple signaling interactions between the session anchor and the SMF can be reduced, and the traffic Statistics are accurate in real time.
  • the first user plane function is the uplink classifier UL CL or branch point BP; the first user plane function receiving the first downlink data packet includes: the first user plane function receiving the second user plane function sending The first downlink data packet, the second user plane function is the protocol data unit PDU session anchor PSA.
  • each URR cell also includes a URR bitmap subscript; the URR bitmap includes at least one bit value, the bit value corresponds to the URR bitmap subscript, and the bit value is the first indicator value or the second Indicating value, the first indicating value is used to indicate that the URR cell corresponding to the URR bitmap subscript requires cumulative flow, and the second indicating value is used to indicate that the URR cell corresponding to the URR bitmap subscript does not require cumulative flow.
  • the first indicator value is 1, and the second indicator value is 0. Since the bits in the URR bitmap have two bit values, UL CL/BP can determine the URR bitmap subscript corresponding to the bit according to the first indicator value, and then can calculate the new URR cell corresponding to the URR bitmap subscript flow.
  • each URR cell also includes a URR identifier; in each URR cell, a URR identifies a URR bitmap subscript mapping.
  • this application may not use the URR bitmap subscript, and reuse the URR identifier to participate in traffic statistics.
  • the use of URR bitmap subscripts takes into account that the types of services that users subscribe to are less than URR identifiers, and the use of URR bitmap subscripts occupies smaller bits.
  • the first user plane function according to the first downlink data packet statistics indicates the newly added flow of the URR cell indicated by the first bit chart includes: the first user plane function obtains the first downlink data packet carried in the first downlink data packet The difference between the accumulated flow of and the accumulated flow carried in the second downlink data packet received last time, and the difference is the newly added flow corresponding to the URR cell indicated by the URR bit chart.
  • This method of carrying accumulated traffic in downlink data packets to obtain new traffic can avoid the signaling overhead caused by multiple signaling interactions for traffic statistics.
  • the first downlink data packet also includes a start marker of the session flow; the start marker is used to indicate that the first downlink data packet is the first downlink data packet of the session flow; or, the first downlink data packet
  • the line data packet also includes an end mark, which is used to indicate that the first downlink data packet is the last downlink data packet of the session flow; the method further includes: if the first downlink data packet includes the start mark, then the first user The plane function records the identifier of the session flow; if the first downlink data packet includes an end marker, the first user plane function deletes the identifier of the session flow. In this way, by carrying the start mark and the end mark, the first user plane function can record and delete relevant parameters of the session stream in time.
  • a method for counting service traffic including: a session management function sends a session establishment request to a first user plane function, the session establishment request includes at least one usage reporting rule URR cell corresponding to the session flow, each The URR cell includes the flow threshold; the session management function receives the URR notification sent by the first user plane function, and the URR notification is used to apply for a new flow threshold for the URR cell in the session flow that reaches the flow threshold; the session management function sends the policy control function PCF Send URR notifications to obtain new traffic thresholds.
  • the beneficial effects of the second aspect can be referred to the first aspect, which will not be repeated here.
  • the first user plane function is the uplink classifier UL CL or branch point BP; the session establishment request is used to instruct the first user plane function to determine when the newly added flow of URR cells reaches the corresponding flow threshold , To send URR notification to the session management function.
  • each URR cell also includes a URR bitmap subscript; the URR bitmap subscript corresponds to at least one bit included in the URR bitmap, and the bit value corresponding to the bit is the first indicator value or the second Indicating value, the first indicating value is used to indicate that the URR cell corresponding to the URR bitmap subscript requires cumulative flow, and the second indicating value is used to indicate that the URR cell corresponding to the URR bitmap subscript does not require cumulative flow.
  • each URR cell also includes a URR identifier; in each URR cell, a URR identifier is mapped to a URR bitmap subscript.
  • the method further includes: the session management function receives a URR response sent by the PCF, the URR response includes a new traffic threshold; the session management function sends a URR update notification to the first user plane function, and the URR update notification includes the new Traffic threshold.
  • the method further includes: when the session management function determines that the first user plane function is deleted, if the session management function needs to update the URR information element, the session management function sends a session update request to the second user plane function,
  • the second user plane function is a protocol data unit PDU session anchor PSA associated with the first user plane function, and the session update request is used to instruct the second user plane function to send a URR notification to the session management function. That is, when the first user plane function (UL CL/BP) is deleted, the second user plane function (PSA) can directly report the traffic to the session management function (SMF).
  • a user plane function is provided.
  • the user plane function is a first user plane function
  • the first user plane function includes: a receiving module for receiving a session establishment request sent by a session management function, and the session establishment request includes a session flow correspondence At least one of the URR cells using the reporting rule, each URR cell includes a flow threshold;
  • the receiving module is also used to receive the first downlink data packet, the first downlink data packet includes the session flow identifier, the first URR bit map And the cumulative flow of the session flow;
  • the URR bit chart is used to indicate the URR cells involved in the cumulative flow;
  • the processing module is used to count the newly added flow of URR cells indicated by the URR bit chart according to the first downlink data packet;
  • the sending module It is also used to send a URR notification to the session management function if the newly added flow reaches the flow threshold corresponding to the URR cell indicated by the URR bit chart.
  • the URR notification is used to apply for a new flow threshold for the URR cell that reaches
  • the first user plane function is the uplink classifier UL CL or branch point BP; the receiving module is used to: receive the first downlink data packet sent by the second user plane function, and the second user plane function is Protocol data unit PDU session anchor PSA.
  • each URR cell also includes a URR bitmap subscript; the URR bitmap includes at least one bit value, the bit value corresponds to the URR bitmap subscript, and the bit value is the first indicator value or the second Indicating value, the first indicating value is used to indicate that the URR cell corresponding to the URR bitmap subscript requires cumulative flow, and the second indicating value is used to indicate that the URR cell corresponding to the URR bitmap subscript does not require cumulative flow.
  • each URR cell also includes a URR identifier; in each URR cell, a URR identifies a URR bitmap subscript mapping.
  • the processing module is used to obtain the difference between the accumulated flow carried in the first downlink data packet and the accumulated flow carried in the second downlink data packet received previously, the difference being URR bits The newly added traffic corresponding to the URR cell indicated in the chart.
  • the first downlink data packet also includes a start marker of the session flow; the start marker is used to indicate that the first downlink data packet is the first downlink data packet of the session flow; or, the first downlink data packet
  • the line data packet also includes an end mark, which is used to indicate that the first downlink data packet is the last downlink data packet of the session flow; the processing module is also used to: if the first downlink data packet includes the start mark, record the session The identifier of the flow; if the first downlink data packet includes an end marker, the identifier of the flow of the second session is deleted.
  • a session management function including: a sending module for sending a session establishment request to a first user plane function, the session establishment request includes at least one usage reporting rule URR cell corresponding to the session flow, each The URR cell includes a flow threshold; the receiving module is used to receive the URR notification sent by the first user plane function, and the URR notification is used to apply for a new flow threshold for the URR cell that reaches the flow threshold in the session flow; the sending module is used to send The policy control function PCF sends URR notifications to obtain new traffic thresholds.
  • the first user plane function is the uplink classifier UL CL or branch point BP; the session establishment request is used to instruct the first user plane function to determine when the newly added flow of URR cells reaches the corresponding flow threshold , To send URR notification to the session management function.
  • each URR cell also includes a URR bitmap subscript; the URR bitmap subscript corresponds to at least one bit included in the URR bitmap, and the bit value corresponding to the bit is the first indicator value or the second Indicating value, the first indicating value is used to indicate that the URR cell corresponding to the URR bitmap subscript requires cumulative flow, and the second indicating value is used to indicate that the URR cell corresponding to the URR bitmap subscript does not require cumulative flow.
  • each URR cell also includes a URR identifier; in each URR cell, a URR identifier is mapped to a URR bitmap subscript.
  • the receiving module is also used to receive a URR response sent by the PCF, the URR response includes a new traffic threshold; the sending module is also used to send a URR update notification to the first user plane function, the URR update notification includes The new traffic threshold.
  • the sending module is also used for: when the session management function determines that the first user plane function is deleted, if the session management function needs to update the URR information element, it sends a session update request to the second user plane function.
  • the second user plane function is a protocol data unit PDU session anchor PSA associated with the first user plane function, and the session update request is used to instruct the second user plane function to send a URR notification to the session management function.
  • the embodiments of the present application provide a computer program product, which when the computer program product runs on an electronic device, causes the electronic device to execute the method of the first aspect and/or the second aspect described above.
  • Figure 1 is a signaling interaction diagram for coordinating and distributing traffic among multiple UPFs
  • FIG. 2 is a schematic diagram of a network architecture provided by an embodiment of this application.
  • FIG. 3 is a schematic diagram of a network architecture provided by an embodiment of this application.
  • FIG. 4 is a schematic flow chart of a method for counting service traffic provided by an embodiment of this application.
  • FIG. 5 is a schematic flowchart of a method for counting service traffic provided by an embodiment of this application.
  • Fig. 6 is a schematic flow chart of a method for counting service traffic when UL CL/BP is deleted according to an embodiment of the application;
  • FIG. 7 is a schematic structural diagram of an electronic device provided by an embodiment of the application.
  • FIG. 8 is a schematic structural diagram of an electronic device provided by an embodiment of the application.
  • FIG. 9 is a schematic structural diagram of an electronic device provided by an embodiment of this application.
  • FIG. 10 is a schematic structural diagram of an electronic device provided by an embodiment of this application.
  • FIG. 11 is a schematic structural diagram of an electronic device provided by an embodiment of this application.
  • FIG. 12 is a schematic structural diagram of an electronic device provided by an embodiment of this application.
  • the embodiments of the present application can be applied to a 5G network architecture.
  • a session has multiple UPFs, how to count and report service traffic in real time and accurately.
  • SMF sends a session management policy association (Npcf_smpolicyControl_Create) message to the policy control function (PCF) to the PCF, determines that policy control and charging (PCC) authorization is required, and requests to establish session management with the PCF ( session management, SM) policy association;
  • PCF policy control function
  • PDU session anchor point 1 PDU (Protocol Data Unit, protocol data unit) session anchor, PSA
  • PSA PDU session anchor point 1
  • PSA1 uses the Packet Forwarding Control Protocol (PFCP) session notification (PFCP session report) to report to the SMF that the traffic has reached the threshold;
  • PFCP Packet Forwarding Control Protocol
  • SMF sends a PFCP session modification Request message to PSA2, requesting PSA2 to report traffic usage immediately;
  • SMF re-allocates traffic quotas to PSA1 and PSA2 based on the remaining quota and other information, and sends the updated traffic threshold to PSA1;
  • the SMF delivers the updated traffic threshold to PSA2.
  • the design idea of this application is to use the convergence point characteristics of UL CL/BP to report URR.
  • the identification of URR is completed by PSA and the URR list corresponding to the session flow is carried in the downlink packet, so as to achieve the traffic control.
  • the network architecture of this application may be as shown in Figure 2, including terminal equipment, access network (AN), user plane functions, mobility management network elements, session management functions, policy control functions, charging functions, and data networks (data network, DN), etc.
  • AN access network
  • DN data network
  • the terminal equipment may be user equipment (UE), access terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal, mobile equipment, UE terminal, terminal, wireless Communication equipment, UE agent or UE device, etc.
  • the access terminal can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in 5G networks or terminals in evolved public land mobile network (PLMN) networks, etc.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • the access network AN may include equipment capable of communicating with terminal equipment.
  • the access network includes a base station, and the base station may be a relay station or an access point.
  • the base station can be a base transceiver station (BTS) in the global system for mobile communication (GSM) or code division multiple access (CDMA) network, or it can be a broadband code division
  • the NB (NodeB) in wideband code division multiple access (WCDMA) may also be the eNB or eNodeB (evolutional NodeB) in LTE.
  • the base station may also be a wireless controller in a cloud radio access network (cloud radio access network, CRAN) scenario.
  • the base station can also be a network device in a 5G network or an evolved PLMN network; it can also be a wearable device or a vehicle-mounted device.
  • the user plane function can be UPF, which can be used for: intra-RAT (radio access technology, RAT)/inter-RAT mobility anchor (when applicable); external PDU and data network interconnection Session point; packet routing and forwarding (for example, supporting uplink classifiers to route traffic to an instance of the data network, supporting branch points to support multi-homed PDU sessions); packet inspection (for example, based on service data flow templates) Application process detection and flow description of optional packets received from SMF (packet flow description, PFD); user plane part of the policy rule implementation, such as gating, redirection, traffic diversion); lawful interception; traffic usage report; user plane Quality of Service (QoS) processing, such as UL CL/DL rate implementation, reflection QoS marking in DL; uplink traffic verification service data flow (service data flow, SDF to QoS traffic mapping; uplink and downlink Transmission-level packet marking in the link; downlink packet buffering and downlink data notification triggering; sending and forwarding one or more "end marks
  • RAT radio access
  • mobility management network elements can be access and mobility management functions (AMF), which can be used to: terminate the non-access-stratum (NAS) (N1), NAS encryption and integrity protection; registration management; connection management; reachability management; liquidity management; lawful interception (applicable to the interface of AMF events and LI system; provides transmission for SM messages between UE and SMF; used for routing Transparent proxy of SM messages; access identity verification; access authorization; provide message transmission between UE and SMF; position service management of supervisory service; provide between UE and location management function (location management function, LMF) as well as between RAN and Location service messages between LMFs provide transmission and so on.
  • AMF access and mobility management functions
  • the session management function can be SMF, which can be used for: session management; UE Internet Protocol (IP) address allocation and management; selection and control of the UP function; configuration of the UPF transmission direction and routing of the transmission to Correct destination; part of controlling policy execution and QoS; downlink data notification; configuring UPF flow control to route traffic to the correct destination; terminating the interface to the policy control function, etc.
  • SMF Session Management Function
  • IP Internet Protocol
  • the policy control function can be PCF, and its functions can include: support a unified policy framework to manage network behavior; provide policy rules for control plane functions; access and unified data repository (UDR) User information related to strategic decisions.
  • PCF policy control function
  • its functions can include: support a unified policy framework to manage network behavior; provide policy rules for control plane functions; access and unified data repository (UDR) User information related to strategic decisions.
  • UDR unified data repository
  • the charging function can be CHF, which can be used for converged online and offline charging.
  • the CHF receives the charging information reported by the charging trigger function (charging trigger function, CTF) (SMF can be used as the CTF), generates a bill or issues a quota to the CTF, and provides a charging function to the UE.
  • CTF charging trigger function
  • the data network DN may include various devices, such as routers, servers, and so on.
  • UPF can be classified as UL CL or branch point BP.
  • UL CL can be an uplink traffic classifier that supports the offload of upstream traffic.
  • BP can be a branch point of a session, which can support downstream traffic. merge.
  • UPF can also be PSA, that is, PDU session anchor.
  • Figure 2 shows that there are two PSAs, PSA1 and PSA2.
  • the embodiment of the present application provides a method for counting service traffic, as shown in FIG. 4, including:
  • the session management function sends a session establishment request to a first user plane function.
  • the session establishment request includes at least one URR cell of a usage reporting rule, and each URR cell includes a flow threshold.
  • the session management function may be SMF; the user plane function may be UPF, and UPF may be used as UL CL or BP, or PSA.
  • SMF sends a session establishment request to UPF
  • the UPF is UC CL/BP. That is, the first user plane function is UC CL/BP, which is denoted as the first UPF.
  • the flow threshold carried in the URR cell may indicate that the first UPF reports to the SMF when the statistical flow reaches the flow threshold.
  • the first user plane function receives a session establishment request sent by the session management function.
  • the first user plane function receives the first downlink data packet.
  • the first downlink data packet includes the identifier of the session flow, the first URR bit map, and the cumulative traffic of the session flow; the URR bit map is used to indicate the cumulative traffic involved URR cell.
  • the first downlink data packet may be sent by the second user plane function (second UPF) to the first UPF (UL CL/BP), and the second UPF is PSA.
  • second UPF second user plane function
  • UL CL/BP first UPF
  • PSA PSA
  • the URR cell can correspond to different service types, and the bit in the URR bit table can correspond to one URR cell.
  • the value of the bit in the bitmap can indicate which URR cell corresponds to the business that needs to count traffic.
  • the mapping relationship between the bit and URR in the bitmap is issued by the SMF, so that the cumulative traffic in the downlink data packet can be adjusted Perform statistics on the services that need to be counted as indicated by the URR bit chart.
  • the first user plane function counts the newly added traffic of URR cells indicated by the URR bit chart according to the first downlink data packet.
  • the first UPF can obtain the difference between the accumulated flow carried in the first downlink data packet and the accumulated flow carried in the second downlink data packet received last time.
  • the difference is the URR cell indicated by the URR bit chart. Of new traffic.
  • the first user plane function sends a URR notification to the session management function, and the URR notification is used to apply for new traffic for the URR cell that reaches the traffic threshold. Threshold.
  • the session management function receives the URR notification sent by the first user plane function.
  • the session management function sends a URR notification to the policy control function PCF and the charging function CHF to obtain a new flow threshold.
  • the URR bit chart can be carried in the downlink data packet sent by the PSA to UL CL/BP to indicate the URR or service that needs to count traffic, which can facilitate UL CL/BP to perform traffic statistics based on the URR bit chart. To determine whether to send a URR notification to SMF to apply for a new traffic threshold. In this way, by carrying the flow URR bit chart in the downlink data packet and collecting it through UL CL/BP, the power consumption caused by the signaling interaction between PSA and SMF can be reduced, and the traffic statistics can be real-time and accurate.
  • the session management function is SMF
  • the policy control function is PCF
  • the charging function is CHF
  • the first user plane function is UL CL/BP
  • the second user plane function is PSA1
  • the third user plane function is PSA2, as an example, an embodiment of the present application provides a method for counting service traffic, as shown in FIG. 5, including:
  • the SMF calls the PCF to obtain the PCC policy.
  • the PCC strategy is used for policy control and stream charging such as QoS for packet network service data transmission, and aims to provide users with differentiated services.
  • SMF calls CHF to start charging.
  • SMF After the user establishes a session connection, SMF needs to perform traffic accounting services for the user, and SMF can call CHF to start traffic accounting for the session according to the PCC policy.
  • the SMF combines information such as the PCC policy issued by the PCF, the charging policy of the CHF, and the locally configured policy to generate URR information elements, and establishes the mapping relationship between the URR ID to the URR bitmap subscript and the URR bitmap.
  • URR cells There are two types of URR cells, one is the charging type, which is used when the SMF reports to the CHF for charging; the other is the policy type, which is used when the SMF reports the policy to the PCF.
  • URR cells can be divided into session-level URR and service-level URR.
  • the session-level URR can be understood as a session corresponding to a URR cell, and all flows in the session are associated with the URR cell; for its service-level URR, the service-level URR is under the PCF
  • the strategy issued by the PCF is associated with the URR cell, and multiple strategies can be associated with the same URR cell.
  • the service-level URR corresponds to the charging rate group/service ID (RG/SID)
  • the policy issued by the PCF is associated with the RG/SID
  • the CHF is for the RG /SID allocates quota
  • SMF can create URR cell corresponding to RG/SID.
  • each URR cell corresponds to a service.
  • Each URR cell includes a URR ID (URR identify, URR ID), and each URR cell also includes URR. Bitmap index (URR index).
  • the URR bitmap subscript can reuse the dynamically generated URR ID for traffic statistics; if the SMF is local If the URR is configured, the bit size occupied by the URR ID is relatively large.
  • the embodiment of the present application uses the URR bitmap subscript to perform traffic statistics, that is, converts the URR ID into a number in the session, so that the number range is reduced.
  • the URR information element includes the URR bitmap subscript
  • this application extends the Creat URR IE (information element) of the N4 interface between the SMF and the UPF, and expands the URR Index field, for example, Creat URR
  • the expanded format of IE can be as shown in Table 1.
  • This IE shall uniquely identify the URR among all the URRs configured for this PFCP session. It is expressed that the IE should be uniquely identified as the URR in all URRs configured for the PFCP session.
  • a URR cell contains a URR ID and a URR bitmap subscript, that is, a URR ID maps a URR bitmap subscript.
  • a session can have up to 128 URR Indexes.
  • the specific format of the URR Index field can be shown in Table 2.
  • URR Index can be represented by 8 bits, its type value is 50000, and its length can be n.
  • URR Index can be expressed as 10000000, 01000000, and so on.
  • the URR bitmap (bitmap) corresponding to multiple URR bitmap subscripts includes at least one bit value. For example, when a user subscribes to 32 types of services, there can be 32 bits to indicate Bitmap subscript. Taking user 2 as an example, the 0th bit in the bitmap actually represents URR ID 11, the 1st bit actually represents URR ID3, and so on. In the URR bit map, the initial bit value of each URR bit map subscript can be 0.
  • the SMF sends a first session establishment request to the PSA1.
  • the first session establishment request includes at least one URR cell, and each URR cell includes a URR bitmap subscript.
  • the SMF may send the first session establishment request to the PSA1 through the N4 interface.
  • the session establishment request may be a PFCP session establishment request.
  • the first session establishment request includes URR cells corresponding to these multiple services and is sent to PSA1.
  • the format of the URR cell can be seen in Table 1.
  • a session may have multiple session anchor points.
  • the established session anchor points are PSA1 and PSA2 as an example.
  • PSA1 sends a first session establishment response to the SMF.
  • PSA1 may send the first session establishment response to the SMF through the N4 interface.
  • the session establishment response may be PFCP session establishment response.
  • the SMF sends a second session establishment request to PSA2.
  • the second session establishment request includes at least one URR cell of a usage reporting rule, and each URR cell includes a URR bitmap subscript.
  • PSA2 sends a second session establishment response to the SMF.
  • the SMF sends a third session establishment request to the UL CL/BP.
  • the third session establishment request includes at least one URR cell corresponding to the session flow, and each URR cell includes a URR bitmap subscript and a flow threshold.
  • the SMF can send the third session establishment request to the UL CL/BP through the N4 interface.
  • each URR cell carries Traffic thresholds and URR bit graphs collect statistics on business traffic.
  • the format of the URR cell can be seen in Table 1.
  • the UL CL/BP sends a third session establishment response to the SMF.
  • PSA1 sends the first downlink data packet to UL CL/BP.
  • the first downlink data packet includes the identifier of the session flow, the URR bit map, and the cumulative flow of the session flow; the URR bit map is used to indicate the URR involved in the cumulative flow Letter yuan.
  • the session anchor PSA1 corresponding to the session receives the first downlink data packet sent by the data network DN, it can be sent to the terminal device through the session anchor PSA1 and the access network AN.
  • the first downlink data packet received by PSA1 carries the identifier of the session flow (LableId), the URR bit map, and the cumulative flow of the session flow (volume), and PSA1 can send the first data to UL CL/BP through the N9 interface Downlink data packet.
  • the downlink PDU session information (download PDU session information) (PDU type 0) in the first downlink data packet can be extended to carry the identifier of the session flow, the URR bit map, and the cumulative flow.
  • the specific format can be as shown in Table 3. Shown.
  • URR BITMAP LEN represents the length of bits occupied by the URR bitmap
  • LabelId represents the session flow ID, and the URR bitmap corresponding to a flow is fixed
  • URR BITMAP represents the URR bitmap
  • Volume represents the flow of the stream identified by LabelId Cumulative traffic
  • STA represents the start mark of the flow identified by the Label Id
  • STO represents the end mark of the flow identified by the Label Id.
  • the URR bit table includes at least one bit value, the bit value corresponds to the URR bitmap subscript, the bit value is the first indicator value or the second indicator value, and the first indicator value is used to indicate the URR signal corresponding to the URR bitmap subscript.
  • the second indicator value is used to indicate that the URR cell corresponding to the subscript of the URR bitmap does not need to accumulate the flow. For example, the first indicator value is 1, and the second indicator value is 0.
  • STA is used to indicate that the first downlink data packet is the first downlink data packet of the session flow; or, STO is used to indicate that the first downlink data packet is the last downlink data packet of the session flow. If the first downlink data packet includes STA, UL CL/BP records the identifier of the session flow, LableId; if the first downlink data packet includes STO, UL CL/BP deletes the identifier of the session flow.
  • the format of the downlink data packet received by PSA2 is similar to that of the first downlink data packet received by PSA1.
  • the UL CL/BP counts the newly added traffic of URR cells indicated by the URR bit chart according to the first downlink data packet.
  • UL CL/BP can determine the URR bitmap subscript corresponding to the bit according to the first indicator value, and then can calculate the new URR cell corresponding to the URR bitmap subscript flow.
  • UL CL/BP can obtain the difference between the accumulated flow carried in the first downlink data packet and the accumulated flow carried in the second downlink data packet received last time.
  • the difference is the first graph
  • the bit value of the URR bitmap is 01011000 (bit numbering from the left end to the right end)
  • the value of the 0, 2, 5, 6, and 7 bits is 0, and the corresponding URR bitmap subscripts are 0, 2, 5, 6 and 7, then URR cells corresponding to the subscripts of the URR bitmap of 0, 2, 5, 6, and 7 do not need to count the new traffic
  • the value of the first 1, 3, and 4 bits is 1, the corresponding URR bitmap
  • the subscripts are 1, 3, and 4, then the URR cells corresponding to the subscripts 1, 3, and 4 of the URR bitmap need to count the new traffic.
  • the service-level URR when the URR cell needs to count the traffic, it can also be considered that the traffic corresponding to the URR cell needs to be count the
  • UL CL/BP sends a URR notification to the SMF.
  • the URR notification is used to apply for a new flow threshold for the URR cell that reaches the flow threshold.
  • UL CL/BP can notify the SMF that the flow allocated by the URR cell has been allocated. After use, instruct SMF to apply for a new traffic threshold from PCF. For example, if the new traffic threshold is 200, then if UL CL/BP continues to count the new traffic and reaches 200, you can send URR notification to SMF again to apply for new traffic. Threshold.
  • the SMF sends a URR notification to the PCF to obtain a new flow threshold.
  • the SMF receives the URR response sent by the PCF, and the URR response includes the new flow threshold.
  • the SMF sends a URR update notification to the UL CL/BP, and the URR update notification includes the new traffic threshold.
  • PSA can report traffic to UL CL/BP along with data packets
  • UL CL/BP performs traffic statistics, and reports traffic to SMF.
  • This process of reporting traffic along with data packets can guarantee the traffic
  • the accuracy of reporting can also avoid the problem of high signaling overhead caused by multiple signaling interactions between SMF and UPF.
  • UL CL/BP realizes the functions of traffic accumulation and URR reporting.
  • the UL CL in the above embodiments may be deleted. After the UL CL is deleted, the traffic report of PSA1/PSA2 will no longer be able to report traffic to the SMF through the UL CL. At this time, the PSA You can report traffic directly to SMF.
  • Figure 3 As the network architecture, as shown in Figure 6:
  • the UE establishes a PDU session.
  • the session includes multiple sessions such as UL CL/BP, PSA1, and PSA2.
  • the UL CL/BP implements traffic statistics and traffic reporting (see the corresponding embodiment in FIG. 4).
  • the SMF informs the UE to stop using the IPv6 prefix corresponding to PSA1 through an Internet Protocol Version 6 routing advertisement ((Internet Protocol Version 6, IPv6) Router Advertisement), the UE can start to use the IPv6 prefix corresponding to PSA2 for all service traffic.
  • Internet Protocol Version 6 routing advertisement (Internet Protocol Version 6, IPv6) Router Advertisement)
  • the SMF interacts with the (R)AN to update the (R)AN tunnel information, so that the uplink traffic is sent from the (R)AN to the PSA2 without passing through the UL CL/BP.
  • the SMF interacts with the PSA2 through the N4 interface, updates the PSA2 tunnel information, and sends a session update request to the PSA2 at the same time.
  • the session update request is used to instruct the PSA2 to send a URR notification to the SMF.
  • PSA1 the protocol data associated with the session of PSA1 Unit PDU session anchor point PSA
  • session update request is used to instruct PSA2 to send URR notification to SMF.
  • downstream traffic will be directly sent from the PSA2 to the (R)AN, so that the entire upstream and downstream traffic path switching is completed. That is, after UL CL/BP is deleted, PSA2 reports statistical traffic to SMF.
  • the SMF sends a session (PFCP session) delete message to PSA1 to instruct PSA1 to release the session on PSA1.
  • PFCP session PFCP session
  • the SMF sends a session (PFCP session) delete message to the UL CL/BP to instruct the UL CL/BP to release the session on PSA1.
  • PFCP session a session delete message
  • PSA2 performs traffic statistics, and if the traffic threshold is reached, it reports the accumulated traffic to the SMF.
  • PSA2 performing traffic statistics
  • UL CL/BP performing traffic statistics
  • the embodiment of the present application can enable other UPFs to report URR traffic to the SMF according to the traffic accumulation in the data packet when the UL CL is deleted, so as to implement URR reporting across multiple UPFs and reduce the signaling interaction between the SMF and the UPF.
  • each network element such as a user plane function, a session management function, etc.
  • each network element includes a hardware structure and/or software module corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiments of the present application can divide the user plane functions, session management functions, etc. into functional modules based on the foregoing method examples.
  • each functional module can be divided corresponding to each function, or two or more functions can be integrated into one process.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 7 shows a schematic structural diagram of an electronic device 70.
  • the electronic device 70 may be the above-mentioned user plane function, or UL CL/BP, and the electronic device 70 includes: receiving Unit 701, processing unit 702, and sending unit 703.
  • the receiving unit 701 is used to support the electronic device 70 to execute the processes 302 and 303 in FIG. 4, the corresponding processes of the processes 408 and 410 in FIG. 5, and the corresponding process of the process 506 in FIG. 6;
  • the processing unit 702 is used to support the electronic device 70
  • the process 304 in FIG. 4 and the process 411 in FIG. 5 are executed, and the sending unit 703 is used to support the electronic device 70 to execute the process 305 in FIG. 4 and the processes 409 and 412 in FIG. 5.
  • all relevant content of the steps involved in the above method embodiments can be cited in the functional description of the corresponding functional module, and will not be repeated here.
  • FIG. 8 shows a schematic diagram of a possible structure of the electronic device involved in the foregoing embodiment.
  • the electronic device 80 includes a processing module 802 and a communication module 803.
  • the processing module 802 is used to control and manage the actions of the electronic device.
  • the processing module 802 is used to support the electronic device 80 to execute the process 304 in FIG. 3, the process 411 in FIG. 5, and/or the technology described herein.
  • Other processes are used to support communication between the electronic device and other network entities, for example, communication with the functional modules or network entities shown in FIG. 2 and FIG. 3.
  • the communication module 803 includes the functions of the receiving unit 701 and the sending unit 703 described above.
  • the electronic device 80 may also include a storage module 801 for storing program codes and data of the electronic device 80.
  • the processing module 802 may be a processor or a controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), and an application-specific integrated circuit (Application-Specific Integrated Circuit). Integrated Circuit, ASIC), Field Programmable Gate Array (FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination of computing functions, for example, a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication module 803 may be a transceiver, a transceiver circuit, or a communication interface.
  • the storage module 801 may be a memory.
  • the processing module 802 is a processor
  • the communication module 803 is a communication interface
  • the storage module 801 is a memory
  • the electronic device involved in the embodiment of the present application may be the electronic device 90 shown in FIG. 9.
  • the electronic device 90 includes: a processor 912, a communication interface 913, a memory 911, and a bus 914.
  • the communication interface 913, the processor 912, and the memory 911 are connected to each other through a bus 914;
  • the bus 914 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus Wait.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.
  • FIG. 10 shows a schematic structural diagram of an electronic device 10.
  • the electronic device 10 may be the session management function involved in the above-mentioned embodiment, or a possible SMF
  • the electronic device 10 includes a sending unit 1001, a receiving unit 1002, and a processing unit 1003.
  • the sending unit 1001 is used to support the electronic device 10 to execute the processes 301 and 307 in FIG. 4, the processes 404, 406, 408, and 413 in FIG. 5, and the processes 505, 506 in FIG. 6;
  • the receiving unit 1002 is used to support the electronic device 10
  • the process 306 in FIG. 3 is performed.
  • the processing unit 1003 is used to support the electronic device 10 to execute the processes 401, 402, and 403 in FIG. 5, and the processes 502, 503, and 504 in FIG.
  • the function description of the corresponding function module will not be repeated here.
  • FIG. 11 shows another possible structural schematic diagram of the electronic device 10 involved in the foregoing embodiment.
  • the electronic device 11 includes: a processing module 1102 and a communication module 1103.
  • the processing module 1102 is used to control and manage the actions of the electronic device 11.
  • the processing module 1102 is used to support the electronic device 11 to execute the processes 401, 402, and 403 in FIG. 5, the processes 502, 503, and 504 in FIG. 6, and / Or other processes used in the techniques described herein.
  • the communication module 1103 is used to support communication between the electronic device 11 and other network entities, for example, communication with the functional modules or network entities shown in FIG. 2 and FIG. 3.
  • the electronic device 11 may also include a storage module 1101 for storing program codes and data of the electronic device 11.
  • the processing module 1102 may be a processor or a controller, for example, a CPU, a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination of computing functions, for example, a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication module 1103 may be a transceiver, a transceiver circuit, or a communication interface.
  • the storage module 1101 may be a memory.
  • the processing module 1102 is a processor
  • the communication module 1103 is a communication interface
  • the storage module 1101 is a memory
  • the electronic device 11 involved in the embodiment of the present application may be the electronic device 12 shown in FIG. 12.
  • the electronic device 12 includes a processor 1212, a communication interface 1213, a memory 1211, and a bus 1214.
  • the communication interface 1213, the processor 1212, and the memory 1211 are connected to each other through a bus 1214;
  • the bus 1214 may be a PCI bus or an EISA bus.
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in FIG. 12 to represent it, but it does not mean that there is only one bus or one type of bus.
  • the steps of the method or algorithm described in combination with the disclosure of this application can be implemented in a hardware manner, or can be implemented in a manner in which a processor executes software instructions.
  • Software instructions can be composed of corresponding software modules, which can be stored in random access memory (Random Access Memory, RAM), flash memory, read-only memory (Read Only Memory, ROM), and erasable programmable read-only memory ( Erasable Programmable ROM (EPROM), Electrically Erasable Programmable Read-Only Memory (Electrically EPROM, EEPROM), registers, hard disk, mobile hard disk, CD-ROM or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the ASIC may be located in the core network interface device.
  • the processor and the storage medium may also exist as discrete components in the core network interface device.
  • Computer-readable media include computer storage media and communication media, where communication media includes any media that facilitates the transfer of computer programs from one place to another.
  • the storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention relève du domaine des communications. La présente invention concerne un procédé et un appareil de collecte de statistiques relatives à un trafic de service susceptibles d'accroître la précision d'une interrogation et d'un rapport de trafic entre une fonction de gestion de session (SMF) et une fonction de plan utilisateur (UPF) et de réduire les surdébits de signalisation. Le procédé comprend les étapes au cours desquelles : une première UPF reçoit une demande d'établissement de session envoyée par une SMF, la demande d'établissement de session contenant au moins une cellule d'une règle de rapport d'utilisation (URR) correspondant à un flux de session et chaque cellule URR comportant un seuil de trafic ; la première UPF reçoit un premier paquet de données de liaison descendante, le premier paquet de données de liaison descendante contenant l'identifiant du flux de session, une première table bitmap URR et un trafic accumulé du flux de session, et la table bitmap URR étant utilisée pour indiquer la cellule URR impliquée dans le trafic accumulé ; la première UPF collecte des statistiques relatives au trafic nouvellement ajouté de la cellule URR indiquée par la table bitmap URR en fonction du premier paquet de données de liaison descendante ; et, si le trafic nouvellement ajouté atteint le seuil de trafic correspondant à la cellule URR indiquée par la table bitmap URR, la première UPF envoie une notification URR à la SMF. Les modes de réalisation de la présente invention sont utilisés pour un rapport de trafic parmi une pluralité d'UPF.
PCT/CN2020/097553 2019-08-30 2020-06-22 Procédé et appareil de collecte de statistiques relatives à un trafic de service WO2021036441A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910818906.7A CN112449358B (zh) 2019-08-30 2019-08-30 一种统计业务流量的方法和装置
CN201910818906.7 2019-08-30

Publications (1)

Publication Number Publication Date
WO2021036441A1 true WO2021036441A1 (fr) 2021-03-04

Family

ID=74684073

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/097553 WO2021036441A1 (fr) 2019-08-30 2020-06-22 Procédé et appareil de collecte de statistiques relatives à un trafic de service

Country Status (2)

Country Link
CN (1) CN112449358B (fr)
WO (1) WO2021036441A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113747493A (zh) * 2021-09-17 2021-12-03 阿里巴巴达摩院(杭州)科技有限公司 数据传输方法、设备、系统及存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114125030A (zh) * 2021-11-30 2022-03-01 北京天融信网络安全技术有限公司 连接跟踪方法、装置、电子设备和计算机可读存储介质
CN114338930B (zh) * 2021-12-30 2022-10-11 广州爱浦路网络技术有限公司 话单信息处理方法、计算机装置和存储介质
CN115529566B (zh) * 2022-10-27 2023-10-31 广州爱浦路网络技术有限公司 基于预定义Urr的计费控制方法、装置及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105871602A (zh) * 2016-03-29 2016-08-17 华为技术有限公司 一种统计流量的控制方法、装置和系统
CN108282342A (zh) * 2017-01-05 2018-07-13 华为技术有限公司 计费管理方法、用户面功能实体以及控制面功能实体
CN110149602A (zh) * 2018-02-13 2019-08-20 华为技术有限公司 一种策略控制方法、设备及系统
CN110149603A (zh) * 2018-02-13 2019-08-20 华为技术有限公司 一种策略控制方法、设备及系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10805983B2 (en) * 2017-10-17 2020-10-13 Ofinno, Llc Control plane data transmission
CN109756430B (zh) * 2017-11-07 2021-08-03 华为技术有限公司 一种规则的处理方法及装置
CN110048873A (zh) * 2018-01-16 2019-07-23 华为技术有限公司 多锚点协议数据单元会话的策略控制的方法和通信装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105871602A (zh) * 2016-03-29 2016-08-17 华为技术有限公司 一种统计流量的控制方法、装置和系统
CN108282342A (zh) * 2017-01-05 2018-07-13 华为技术有限公司 计费管理方法、用户面功能实体以及控制面功能实体
CN110149602A (zh) * 2018-02-13 2019-08-20 华为技术有限公司 一种策略控制方法、设备及系统
CN110149603A (zh) * 2018-02-13 2019-08-20 华为技术有限公司 一种策略控制方法、设备及系统

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Interface between the Control Plane and the User Plane Nodes; Stage 3 (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 29.244, vol. CT WG4, no. V15.6.0, 13 June 2019 (2019-06-13), pages 1 - 198, XP051754042 *
ERICSSON: "The report and update of a URR", 3GPP DRAFT; C4-184032_REPORT AND UPDATE_REL15_PA2, vol. CT WG4, 11 May 2018 (2018-05-11), Osaka, Japan, pages 1 - 4, XP051460775 *
HUAWEI; HISILICON: "Proposal of QER, URR and FAR", 3GPP DRAFT; S2-182191 - PROPOSAL OF QER URR AND FAR_R5, vol. SA WG2, 20 February 2018 (2018-02-20), Montreal, Canada, pages 1 - 5, XP051408717 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113747493A (zh) * 2021-09-17 2021-12-03 阿里巴巴达摩院(杭州)科技有限公司 数据传输方法、设备、系统及存储介质
CN113747493B (zh) * 2021-09-17 2024-04-05 杭州阿里云飞天信息技术有限公司 数据传输方法、设备、系统及存储介质

Also Published As

Publication number Publication date
CN112449358B (zh) 2022-05-24
CN112449358A (zh) 2021-03-05

Similar Documents

Publication Publication Date Title
WO2021036441A1 (fr) Procédé et appareil de collecte de statistiques relatives à un trafic de service
US11558770B2 (en) Method for determining QoS description information and apparatus
WO2020108003A1 (fr) Procédé de contrôle d'accès d'utilisateur, procédé de transmission d'informations et appareils associés
CN109167847B (zh) 一种IPv6地址的生成方法及SMF、通信系统
US9178767B2 (en) Intelligent traffic quota management in split-architecture networks
US11272333B2 (en) Convergent charging method and device
US20090296613A1 (en) Method and apparatus for providing quality-of-service in radio access networks
US11042408B2 (en) Device, system, and resource allocation method
EP3685627B1 (fr) Mise en oeuvre de services de réseau edge au niveau d'éléments d'accès pour une informatique edge mobile
US20220393984A1 (en) Nodes and Methods for Enabling User Plane Traffic Classification in a Communications System
US10616119B2 (en) Policy determining method and apparatus
WO2020169039A1 (fr) Procédé et dispositif de gestion de politique
EP2863661A1 (fr) Procédé et passerelle de facturation de passerelle
CN104769978B (zh) 计费方法及设备
CN113169884A (zh) 移除应用标识符
WO2021179598A1 (fr) Procédé, appareil et système de communication
CN113727390A (zh) 一种数据传输方法、装置及通信系统
TWI821882B (zh) 丟包率的檢測方法、通信裝置及通信系統
CN112910662B (zh) 一种流量信息上报及接收上报方法、设备、介质
WO2024022136A1 (fr) Procédé et appareil de traitement de données de réseau, et support de stockage
RU2786413C2 (ru) Способ отчетности по объему данных при множественном подключении
WO2023143255A1 (fr) Procédé et appareil de communication
US20240048398A1 (en) Method and apparatus for charging management
WO2016029673A1 (fr) Procédé de rapport d'état de l'encombrement d'un réseau d'accès, procédé de traitement de mise à jour d'informations d'encombrement, et dispositif
WO2016029674A1 (fr) Procédé de rapport d'état d'encombrement d'un réseau d'accès, procédé de traitement de mise à jour d'informations d'encombrement, et dispositif

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

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

Country of ref document: EP

Kind code of ref document: A1