WO2021238794A1 - 业务流的用户量统计方法、装置及系统 - Google Patents

业务流的用户量统计方法、装置及系统 Download PDF

Info

Publication number
WO2021238794A1
WO2021238794A1 PCT/CN2021/095161 CN2021095161W WO2021238794A1 WO 2021238794 A1 WO2021238794 A1 WO 2021238794A1 CN 2021095161 W CN2021095161 W CN 2021095161W WO 2021238794 A1 WO2021238794 A1 WO 2021238794A1
Authority
WO
WIPO (PCT)
Prior art keywords
service flow
user
user volume
network element
local
Prior art date
Application number
PCT/CN2021/095161
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 WO2021238794A1 publication Critical patent/WO2021238794A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer

Definitions

  • This application relates to the field of communications, and in particular to a method, device and system for counting the number of users of a service flow.
  • a shunt point may be inserted on the user plane path of a protocol data unit (PDU) session (session), and some service flows in the session may be shunted to a local route by the shunt point.
  • the branch point may be a branching point (BP) or an uplink classifier (ULCL).
  • a PDU session of the terminal can have a remote PDU session anchor (PSA) and a local PDU session anchor (L-PSA), and the remote PSA can communicate with central DN (central DN), and L-PSA can communicate with local DN (local DN).
  • PSA remote PDU session anchor
  • L-PSA local PDU session anchor
  • the offload point can offload the upstream service flow 1 to the remote PSA, and offload the upstream service flow 2 to the L-PSA; for the downlink service, the offload point can be from the remote PSA.
  • the downlink service flow 1 of the end PSA and the downlink service flow 2 from the L-PSA are aggregated into the tunnel between the offload point and the base station and sent to the base station, and then sent from the base station to the terminal.
  • Local business chain control refers to that the service flow is processed by a series of orderly service function (SF) network elements, and these SF network elements are located in the local DN.
  • SF orderly service function
  • the embodiments of the present application provide a method, device, and system for user volume statistics of service flows, which can realize user volume statistics of service flows that need to be controlled by a local service chain.
  • a method for counting the number of users of a service flow includes: the session management network element determines a user volume statistics rule, and sends the user volume statistics rule to the user plane network element.
  • the user volume statistics rule includes the user volume statistics rule of the first service flow and/or the user volume statistics rule of the second service flow.
  • the first service flow is an uplink service flow that needs to be controlled by the local service chain
  • the second service flow is Downstream service flow that needs to be controlled by the local service chain.
  • the user quantity statistics rule of the first service flow is used to instruct the user quantity statistics of the first service flow before the local service chain control, and/or the user quantity statistics of the first service flow after the local service chain control;
  • the user quantity statistics rule of the second service flow is used to instruct the user quantity statistics of the second service flow before the local service chain control, and/or the user quantity statistics of the second service flow after the local service chain control.
  • the session management network element obtains the user volume statistics rule of the uplink service flow and/or the downlink service flow, and sends the user volume statistics rule to the user plane network element, so that the user plane network element can make statistics based on the user volume
  • the rules perform user statistics on uplink or downlink service flows, realize user statistics on service flows that need to be controlled by the local service chain, and improve the accuracy of user statistics on this type of service flow.
  • the user volume statistics method of the service flow further includes: the session management network element obtains the first measurement strategy and the second measurement strategy, and the session management network element receives the first user volume statistics information and the second user
  • the first user amount statistics information is used to indicate the user amount of the first service flow before the local service chain control
  • the second user amount statistics information is used to indicate the user amount of the first service flow after the local service chain control.
  • the session management network element processes the first user volume statistical information according to the first measurement strategy, and processes the second user volume statistical information according to the second measurement strategy.
  • the CHF network element may perform charging and other operations based on the processed user volume statistical information. For example, the CHF network element generates a call ticket based on the processed user volume statistical information.
  • the user volume statistics method of the service flow further includes: the session management network element obtains the third measurement strategy and the fourth measurement strategy, and the session management network element receives the third user volume statistical information and the fourth user volume Statistical information, the third user volume statistical information is used to indicate the user volume of the second service flow before the local service chain control, and the fourth user volume statistical information is used to indicate the user volume of the second service flow after the local service chain control .
  • the session management network element processes the third user volume statistical information according to the third measurement strategy, and processes the fourth user volume statistical information according to the fourth measurement strategy.
  • the CHF network element may perform charging and other operations based on the processed user volume statistical information. For example, the CHF network element generates a call ticket based on the processed user volume statistical information.
  • the user volume statistics method of the service flow further includes: the session management network element receives the first indication information from the policy control function network element,
  • the session management network element determining the user volume statistics rule may include: the first indication information is used to indicate that the size of the first service flow after the local service chain control does not change, the session management network element determines the first service flow
  • the user volume statistics rule is used to instruct user volume statistics to be performed on the first service flow before the local service chain control, or to perform user volume statistics on the first service flow after the local service chain control.
  • the first indication information is used to indicate that when the size of the first service flow changes after the local service chain is controlled, the session management network element determines that the user volume statistics rule of the first service flow is used to indicate the first service flow before the control of the local service chain. Perform user volume statistics for a service flow, and perform user volume statistics for the first service flow after the local service chain is controlled.
  • the user volume statistics method of the service flow further includes: the session management network element receives the second indication information from the policy control function network element,
  • the session management network element determining the user volume statistics rule may include: the second indication information is used to indicate that the size of the second service flow after the local service chain control does not change, the session management network element determines the second service flow
  • the user volume statistics rule is used to instruct user volume statistics to be performed on the second service flow before the local service chain control, or to perform user volume statistics on the second service flow after the local service chain control; or, the second indication information is used to indicate
  • the session management network element determines the user quantity statistics rule of the second service flow to instruct the user quantity statistics of the second service flow before the local service chain control, and , Perform user statistics on the second service flow after the local service chain control.
  • the network can charge end users and third-party application providers more reasonably.
  • the network can charge end users according to the number of users of the service flow before the local service chain control, and according to the local service chain The third-party application provider is charged for the number of users of the service flow after control.
  • a method for counting the number of users of a service flow includes: a user plane network element receives a user amount statistics rule from a session management network element, the user amount statistics rule includes a user amount statistics rule of a first service flow and/or a user amount statistics rule of a second service flow, first
  • the service flow is an uplink service flow that needs to be controlled by the local service chain
  • the second service flow is a downlink service flow that needs to be controlled by the local service chain.
  • the user quantity statistics rule of the first service flow is used to instruct the user quantity statistics of the first service flow before the local service chain control, and/or the user quantity statistics of the first service flow after the local service chain control;
  • the user quantity statistics rule of the second service flow is used to instruct the user quantity statistics of the second service flow before the local service chain control, and/or the user quantity statistics of the second service flow after the local service chain control.
  • the user plane network element In the case where the user quantity statistics rule includes the user quantity statistics rule of the first service flow, the user plane network element counts the user quantity of the first service flow according to the user quantity statistics rule of the first service flow; where the user quantity statistics rule includes the first service flow In the case of the user amount statistics rule of the second service flow, the user plane network element counts the user amount of the second service flow according to the user amount statistics rule of the second service flow.
  • the user plane network element receives the user volume statistics rule from the session management network element, so that the user plane network element can perform user volume statistics on the uplink or downlink service flow according to the user volume statistics rule, and realize the need to pass the local service
  • the user volume statistics of the service flow controlled by the chain can improve the accuracy of the user volume statistics of this type of service flow.
  • the user amount statistics method of the service flow further includes: the user plane network element sends the first service flow to the session management network element.
  • the user plane network element sends the first service flow to the session management network element.
  • One user volume statistics information and/or second user volume statistics information the first user volume statistics information is used to indicate the user volume of the first service flow before the local service chain control, and the second user volume statistics information is used to indicate the local service chain Control the number of users in the first service stream afterwards.
  • the user amount statistics method of the service flow further includes: the user plane network element sends the first service flow to the session management network element. 3.
  • the third user volume statistical information is used to indicate the user volume of the second service flow before the local service chain is controlled, and the fourth user volume statistical information is used to indicate the local service chain Control the number of users of the second service stream afterwards.
  • the user plane network element can be used as a diversion point.
  • the user volume statistics point can be located at the diversion point.
  • the user volume statistics rule of the first service flow is used to instruct user volume statistics for the first service flow before the local service chain control, including: The user volume statistics rule of the service flow is used to instruct the user plane network element to perform user volume statistics on the first service flow from the access network device.
  • the user volume statistics rule of the first service flow is used to instruct the user volume statistics of the first service flow after the local service chain is controlled, including: the user volume statistics rule of the first service flow is used to instruct the user plane network element to The first service flow of the local anchor point performs user statistics. It is understandable that for the offload point, the uplink service flow from the access network device is the uplink service flow before the local service chain control, and the uplink service flow from the local anchor point is the uplink service flow after the local service chain control.
  • the user volume statistics rule of the second service flow is used to instruct the user volume statistics of the second service flow before the local service chain control, including: second The user volume statistics rule of the service flow is used to instruct the user plane network element to perform user volume statistics on the second service flow from the remote anchor point, or the user volume statistics rule of the second service flow is used to indicate the control of the local service chain
  • the second service flow of performing user volume statistics includes: the user volume statistics rule of the second service flow is used to instruct the user plane network element to perform user volume statistics on the second service flow from the local anchor. It is understandable that for the offload point, the downlink service flow from the remote anchor point is the downlink service flow before the local service chain control, and the downlink service flow from the local anchor point is the downlink service flow after the local service chain control.
  • the above user plane network element can be used as a remote anchor point.
  • the user volume statistics point can be located at the remote anchor point.
  • the user volume statistics rule of the first service flow is used to instruct the user volume statistics of the first service flow after the local service chain is controlled, including:
  • the user volume statistics rule of the service flow is used to instruct the user plane network element to perform user volume statistics on the first service flow. It is understandable that for the remote anchor point, if the upstream service flow needs to be controlled by the local service chain, the upstream service flow it receives must be the upstream service flow after the local service chain control.
  • the user volume statistics rule of the second service flow is used to instruct the user volume statistics of the second service flow before the local service chain control, including: second
  • the user volume statistics rule of the service flow is used to instruct the user plane network element to perform user volume statistics on the second service flow. It is understandable that, for the remote anchor point, if the downlink service flow needs to be controlled by the local service chain, the downlink service flow it receives must be the downlink service flow before the local service chain control.
  • the user plane network element may be used as a local anchor point.
  • the user volume statistics point can be located at the local anchor point.
  • the user volume statistics rule of the first service flow is used to instruct user volume statistics for the first service flow before the local service chain control, including: The user volume statistics rule of the service flow is used to instruct the user plane network element to perform user volume statistics on the first service flow from the shunt point.
  • the user volume statistics rule of the first service flow is used to instruct the user volume statistics of the first service flow after the local service chain is controlled, including: the user volume statistics rule of the first service flow is used to instruct the user plane network element to The first service flow of the local data network performs user statistics. It is understandable that for the local anchor point, the upstream service flow from the offload point is the upstream service flow before the local service chain control, and the upstream service flow from the local data network is the upstream service flow after the local service chain control.
  • the user volume statistics rule of the second service flow is used to instruct the user volume statistics of the second service flow before the local service chain control, including: second The user volume statistics rule of the service flow is used to instruct the user plane network element to perform user volume statistics on the second service flow from the offload point or the remote anchor point.
  • the user volume statistics rule of the second service flow is used to instruct the user volume statistics of the second service flow after the local service chain is controlled, including: the user volume statistics rule of the second service flow is used to instruct the user plane network element to The second service flow of the local data network performs user statistics.
  • the downlink service flow from the offload point or the remote anchor point is the downlink service flow before the local service chain control
  • the downlink service flow from the local data network is the downlink service flow after the local service chain control. business flow.
  • a session management network element in a third aspect, has the function of implementing the method described in the first aspect.
  • This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • a session management network element including: a processor and a memory; the memory is used to store computer execution instructions, and when the session management network element is running, the processor executes the computer execution instructions stored in the memory , So that the session management network element executes the method for counting the number of users of a service flow as described in any one of the foregoing first aspect.
  • a session management network element including: a processor; the processor is configured to couple with a memory, and after reading an instruction in the memory, execute any one of the above-mentioned first aspect according to the instruction The method for counting the number of users of the service flow.
  • a session management network element including: a processor and an interface circuit, the interface circuit may be a code/data read-write interface circuit, and the interface circuit is used to receive computer-executed instructions (the computer-executed instructions are stored in a memory) , May be directly read from the memory, or may be transmitted through other devices) and transmitted to the processor; the processor is used to run the computer to execute instructions to execute the user volume statistics of the service flow described in any one of the first aspects above method.
  • a computer-readable storage medium stores instructions that, when run on a computer, enable the computer to execute the service flow described in any one of the first aspects above.
  • the method of user statistics are provided.
  • a computer program product containing instructions which when running on a computer, enables the computer to execute the method for calculating the number of users of a service flow described in any one of the first aspects above.
  • an apparatus for example, the apparatus may be a chip system
  • the apparatus includes a processor for supporting the session management network element to implement the functions involved in the above-mentioned first aspect.
  • the device further includes a memory for storing necessary program instructions and data for the session management network element.
  • the device is a chip system, it can be composed of chips, or it can include chips and other discrete devices.
  • a user plane network element is provided, and the user plane network element has a function of implementing the method described in the second aspect.
  • This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • a user plane network element including: a processor and a memory; the memory is used to store computer execution instructions, and when the user plane network element is running, the processor executes the computer execution stored in the memory Instructions, so that the user plane network element executes the user volume statistics method of the service flow according to any one of the above second aspects.
  • a user plane network element including: a processor; the processor is configured to couple with a memory, and after reading an instruction in the memory, execute any one of the above-mentioned second aspect according to the instruction.
  • a user plane network element including: a processor and an interface circuit, the interface circuit may be a code/data read-write interface circuit, and the interface circuit is used to receive computer-executed instructions (computer-executed instructions are stored in a memory , May be directly read from the memory, or may be transmitted through other devices) and transmitted to the processor; the processor is used to run the computer to execute instructions to execute the number of users of the service flow described in any one of the above-mentioned second aspects statistical methods.
  • a computer-readable storage medium stores instructions that, when run on a computer, enable the computer to execute the business described in any one of the above-mentioned second aspects.
  • the flow of user statistics method is provided.
  • a computer program product containing instructions which when running on a computer, enables the computer to execute the method for calculating the number of users of a service flow described in any one of the second aspects above.
  • a device for example, the device may be a chip system
  • the device includes a processor for supporting user plane network elements to implement the functions involved in the second aspect.
  • the device further includes a memory for storing necessary program instructions and data for the user plane network element.
  • the device is a chip system, it can be composed of chips, or it can include chips and other discrete devices.
  • a communication system in a seventeenth aspect, includes a session management network element and a user plane network element.
  • the session management network element is used to perform the steps in the first aspect described above, or by the session management network element in the solution provided in the embodiments of this application; the user plane network element is used to perform the second aspect described above, or the steps implemented in this application.
  • the steps in the solution provided by the example are executed by the user plane network element.
  • the communication system may also include other devices that interact with the session management network element or the user plane network element in the solution provided in the embodiment of the present application, such as the policy control control function network element and the access network. Equipment, etc., which are not specifically limited in the embodiment of the present application.
  • Figure 1 is a schematic diagram of an existing business flow offloading scenario
  • FIG. 2 is a schematic structural diagram of a communication system provided by an embodiment of this application.
  • FIG. 3 is a schematic structural diagram of another communication system provided by an embodiment of this application.
  • FIG. 4a is a schematic diagram of an application of the communication system provided by an embodiment of this application in a 5G network;
  • FIG. 4b is a schematic diagram of another application of the communication system provided by an embodiment of this application in a 5G network;
  • FIG. 4c is a schematic diagram of another application of the communication system provided by an embodiment of this application in a 5G network;
  • FIG. 5 is a schematic diagram of the hardware structure of a communication device provided by an embodiment of the application.
  • FIG. 6 is a schematic flowchart of a method for counting the number of users of a service flow according to an embodiment of this application;
  • Figures 7 to 11 are schematic diagrams of the specific flow of a method for counting the number of users of a service flow provided by an embodiment of this application;
  • FIG. 12 is a schematic structural diagram of a session management network element provided by an embodiment of this application.
  • FIG. 13 is a schematic structural diagram of a user plane network element provided by an embodiment of this application.
  • words such as “first” and “second” are used to distinguish the same or similar items with basically the same function and effect.
  • words “first”, “second” and the like do not limit the quantity and order of execution, and the words “first” and “second” do not limit the difference.
  • At least one refers to one or more, and “multiple” refers to two or more.
  • “And/or” describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
  • the following at least one item (a)” or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
  • at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .
  • a service flow from a terminal or an access network device with a destination address as the central DN is referred to as an uplink service flow.
  • the destination address being the central DN means that the destination address is the address of the application server in the central DN, and the application server corresponds to the service flow and provides corresponding application services for the terminal.
  • the service flow from the center DN and whose destination address is the terminal is called a downlink service flow.
  • the Service chain refers to a series of orderly service function (SF) network elements.
  • the SF network element may be, for example, a network element with a video compression function, a network element with a firewall function, a network element with a video acceleration function, a network element with a deep packet inspection (DPI) function, and so on.
  • DPI deep packet inspection
  • Business chain control refers to the business flow being processed by the business chain, or in other words, refers to the business flow being processed by a series of orderly SF network elements.
  • This processing may be, for example, performing video compression on the service stream first, then going through deep packet inspection, and then going through enhanced processing such as a firewall.
  • This application does not limit the way the SF network element processes the service stream.
  • Local service chain control Refers to the service flow being processed by a series of orderly SF network elements located in the local DN.
  • service chain control in the embodiment of the present application can also be referred to as service chain processing, and the two can be replaced with each other.
  • FIG. 2 shows a communication system to which a method for calculating user volume of a service flow provided by an embodiment of the present application is applicable.
  • the communication system includes: a session management network element 10 and a user plane network element 20.
  • the session management network element 10 and the user plane network element 20 may communicate directly, or communicate through the forwarding of other devices, which is not specifically limited in the embodiment of the present application.
  • the embodiments of this application :
  • the session management network element 10 is used to determine user volume statistics rules.
  • the user volume statistics rules include the user volume statistics rules of the first service flow and/or the user volume statistics rules of the second service flow.
  • the upstream service flow controlled by the service chain, the second service flow is the downstream service flow that needs to be controlled by the local service chain
  • the user volume statistics rule of the first service flow is used to indicate the user volume of the first service flow before the local service chain control Statistics, and/or, perform user volume statistics on the first service flow after the local service chain control
  • the user volume statistics rules for the second service flow are used to instruct user volume statistics on the second service flow before the local service chain control, And/or, perform user statistics on the second service flow after the local service chain control.
  • the session management network element 10 is also used to send the user volume statistics rule to the user plane network element 20.
  • the user plane network element 20 is configured to receive the user amount statistics rule from the session management network element 10, and calculate the user amount of the first service flow according to the user amount statistics rule of the first service flow included in the user amount statistics rule, and according to the first service flow
  • the user volume statistics rule of the second service flow counts the user volume of the second service flow.
  • the session management network element obtains the user volume statistics rule of the uplink service flow and/or the downlink service flow, and sends the user volume statistics rule to the user plane network element, so that the user plane network element can According to the user quantity statistics rule, the user quantity statistics of the upstream or downstream service flows can be performed, so as to realize the user quantity statistics of the service flows that need to be controlled by the local service chain.
  • FIG. 3 it is a schematic structural diagram of another communication system provided by an embodiment of this application.
  • the communication system includes a session management network element 10, a shunt point 201, a remote anchor point 202, and a local anchor point 203.
  • the communication system may also include an access network device 30, a central DN communicating with the remote anchor point 202, and a local DN communicating with the local anchor point 203.
  • the user plane network element 20 in FIG. 2 can be used as the tap 201 in FIG. 3, or as the remote anchor point 202 in FIG. 3, or as the local anchor point 203 in FIG. 3. Or, it may include the remote anchor point 202 and the local anchor point 203 in FIG. 3.
  • the distribution point in the embodiment of the present application can divert the service flow to a local route, or divert the service flow to a remote route.
  • the so-called local routing refers to the diversion point 201 diverts the service flow to the local anchor point 203, and the local anchor point 203 transmits the service flow to the local DN that communicates with the local anchor point 203.
  • the so-called remote routing refers to the shunt point 201 shunting the service flow to the remote anchor point 202, and the remote anchor point 202 transmits the service flow to the central DN that communicates with the remote anchor point 202.
  • the session management network element 10 may insert a diversion point 201 as a diversion point in the user plane path of the session. That is, the offload point 201 may be a network element that has a function of offloading the service flow of the session.
  • the local DN in the embodiment of the present application may also be replaced with a local data center (DC) or a local mobile edge computing (mobile edge computing, MEC) platform.
  • DC local data center
  • MEC mobile edge computing
  • the local DN includes one or more SF network elements (for example, SF1 and SF2).
  • One or more SF network elements may be functional network elements deployed by an operator, or functional network elements deployed by a third party.
  • the SF network element can process the service flow, for example, perform enhancement processing or filtering processing.
  • the SF network element may be a network element with a firewall function, a network element with a video acceleration processing function, or a network element with a load balancing function, etc.
  • the central DN includes an application server (application server, AS) and one or more SF network elements (for example, SF3 and SF4).
  • the functions of different SFs may be the same or different, which is not limited in the embodiment of the present application.
  • the processing flow of the uplink service flow that needs to be controlled by the local service chain in the communication system shown in FIG. 3 can be described as: after the offload point 201 receives the uplink service flow from the access network device 30, The uplink service flow is sent to the local anchor point 203, and the local anchor point 203 sends the uplink service flow to the local DN for local service chain control, and sends the uplink service flow after the local service chain control to the central DN.
  • the uplink service after the local service chain control can be transmitted to the central DN through two different paths.
  • One of the paths is "local DN ⁇ local anchor 203 ⁇ distribution point 201 ⁇ remote anchor 202 ⁇ central DN", which is referred to as path 1 in the following embodiments; the other path is "local DN ⁇ local anchor” 203 ⁇ Remote Anchor Point 202 ⁇ Central DN", which is referred to as path 2 in the following embodiments.
  • the processing flow of the downlink service flow that needs to be controlled by the local service chain in the communication system shown in FIG. 3 can be described as: after the remote anchor 202 receives the downlink service flow from the central DN, the downlink service flow The service flow is transmitted to the local anchor point 203, and the local anchor point 203 sends it to the local DN for local service chain control. After the local DN performs local service chain control on the downlink service flow, the downlink service flow after the local service chain control is sent to the local anchor point 203, and then sent to the local anchor point 203 through the offload point 201 and the access network device 30 terminal.
  • the remote anchor point 202 may transmit the downlink service flow from the central DN to the local anchor point 203 through two paths.
  • One of the paths is "remote anchor point 202 ⁇ shunt point 201 ⁇ local anchor point 203", which is referred to as path 3 in the following embodiments; the other path is "remote anchor point 202 ⁇ local anchor point 203", This is referred to as path 4 in the following embodiments.
  • the local service chain control of the upstream service flow in the local DN passes through SF1 and SF2 as an example.
  • the process of local service chain control can be described as: the local anchor 203 sends the upstream service flow to SF1, SF1 is processed and then sent back to the local anchor point 203, the local anchor point 203 then sends the upstream traffic flow processed by SF1 to SF2, and SF2 is processed and then sent to the local anchor point 203; or after SF1 is processed, it is sent to SF2 and SF2 process the upstream service flow and then send it back to the local anchor point 203, and the local anchor point 203 sends the upstream service flow controlled by the local service chain to the central DN through the above-mentioned path 1.
  • the local anchor point 203 can also send the uplink service flow after the local service chain control to the central DN (not shown in FIG. 3) through the aforementioned path 2.
  • the local service chain control process of the downlink service flow is similar to the local service chain control process of the uplink service flow, and reference may be made to the above related description, which will not be repeated here.
  • a service chain protocol header is added to the message header of the service flow, and the local anchor 203 can identify the service chain protocol after receiving the service flow controlled by the local service chain Header, delete it and send it to the shunt point 201 or the remote anchor point 202.
  • the network element or entity corresponding to the offload point 201 may be an uplink classifier (ULCL) or branch point
  • the network element or entity corresponding to the session management network element 10 may be a session management function (SMF) network element.
  • the network element or entity corresponding to the local anchor 203 may be a first user plan function (UPF) network element, and may also be referred to as a local PDU session anchor (L-PSA).
  • the network element or entity corresponding to the remote anchor 202 may be a second user plan function (UPF) network element, and may also be called a remote PDU session anchor (remote PDU session anchor, which may be referred to as PSA for short) ).
  • the access network device 30 may be an access network (AN) device or a radio access network (RAN) device. In the embodiment of the present application, the access network device 30 is an RAN device as an example for description.
  • the 5G network architecture can also include: mobile management network elements, AF network elements, policy control function (PCF) network elements, unified data management (UDM) network elements, DN, authentication server function network Network elements, unified data management (UDM) network elements, etc., which are not specifically limited in the embodiment of the present application.
  • mobile management network elements AF network elements, policy control function (PCF) network elements, unified data management (UDM) network elements, DN, authentication server function network Network elements, unified data management (UDM) network elements, etc.
  • Terminals can include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to wireless modems; they can also include subscriber units, cellular Telephone (cellular phone), smart phone (smart phone), wireless data card, personal digital assistant (personal digital assistant, PDA) computer, tablet computer, wireless modem (modem), handheld device (handheld), laptop computer ( laptop computer), cordless phone or wireless local loop (WLL) station, machine type communication (MTC) terminal, user equipment (UE), mobile station (mobile station) , MS), terminal device (terminal device) or relay user equipment, etc.
  • the relay user equipment may be, for example, a 5G residential gateway (RG).
  • RG 5G residential gateway
  • the terminals in the embodiments of the present application may be terminals in various vertical industry application fields such as Internet of Things terminal equipment, ports, smart factories, railway transportation, logistics, drones, and unmanned vehicles.
  • Mobile Robot Mobile Robot
  • AGV Automated Guided Vehicle
  • driverless cars control equipment and sensors on trains
  • control equipment and sensors Sensors deployed in factories, etc.
  • the terminal may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which need to cooperate with other devices such as smart phones.
  • the terminal can also be a sensor device used in a factory.
  • the access network equipment is used to provide network access functions for authorized terminals in a specific area, and can use transmission tunnels of different quality according to the level of the terminal and service requirements.
  • the access network equipment can manage wireless resources, provide access services for the terminal equipment, and then complete the forwarding of control signals and terminal data between the terminal and the core network.
  • the access network equipment can also be understood as a base station in a traditional network. For example, it can be responsible for functions such as radio resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • QoS quality of service
  • the access network device may be a device in a wireless network.
  • Access network equipment may also be referred to as wireless access network equipment or network equipment.
  • some examples of access network equipment are: The Next Generation Node B (gNB), the transmission reception point (TRP), and the long term evolution (LTE) system in the 5G system
  • gNB Next Generation Node B
  • TRP transmission reception point
  • LTE long term evolution
  • eNB evolved Node B
  • RNC radio network controller
  • Node B Node B
  • base station controller base station controller
  • BSC base transceiver station
  • home base station for example, home evolved NodeB, or home Node B, HNB
  • BBU wireless fidelity
  • Wi wireless fidelity
  • a network device may include a centralized unit (CU) node, or a distributed unit (DU) node, or a RAN device including a CU node and a DU node.
  • the access device can also be a wireless backhaul device, a vehicle-mounted device, a wearable device, and a network device in a future 5G network or a network device in a future evolved PLMN network.
  • 3G 3rd generation
  • Node B Node B
  • Mobility management network element which belongs to the core network network element, is mainly responsible for the signaling processing part, such as: access control, mobility management, attachment and detachment, gateway selection and other functions.
  • the mobile management network element When the mobile management network element provides services for the session of the terminal, it will provide storage resources of the control plane for the session to store the session identifier, the SMF network element identifier associated with the session identifier, and so on.
  • the mobility management network element may be an access and mobility management function (AMF) network element.
  • AMF access and mobility management function
  • the mobility management network element may still be an AMF network element, or may also have other names, which is not limited in this application.
  • the session management network element is responsible for user plane network element selection, user plane network element redirection, Internet protocol (IP) address allocation, bearer establishment, modification and release, and QoS control. Session management, terminal IP address allocation and management, selection of end points that can manage user plane functions, policy control and charging function interfaces, and downlink data notifications.
  • IP Internet protocol
  • the session management network element may be an SMF network element.
  • the session management network element may still be an SMF network element, or may also have other names, which is not limited by this application.
  • the user plane network element is responsible for forwarding and receiving user data (for example, service flow) in the terminal.
  • User data can be received from the data network and transmitted to the terminal through the access device; the user plane network element can also receive user data from the terminal through the access network device and forwarded to the data network.
  • the transmission resources and scheduling functions in the user plane network element that provide services for the terminal are managed and controlled by the session management network element.
  • the user plane network element may be a UPF network element or a UPF module.
  • the user plane network element may still be a UPF network element or a UPF module, or may also have other names, which is not limited by this application.
  • the authentication server function network element mainly provides authentication functions and supports authentication of 3rd generation partnership project (3GPP) access and Non-3GPP access.
  • 3GPP 3rd generation partnership project
  • the authentication server function network element may be an authentication server function (authentication server function, AUSF) network element, or may also have other names, which are not limited by this application.
  • AUSF authentication server function
  • the UDR network element is mainly responsible for storing structured data.
  • the stored content includes contract data and policy data, structured data exposed to the outside, and application-related data.
  • the AF network element mainly supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side.
  • Data network refers to the operator network that provides data transmission services for the terminal, such as IMS (IP Multi-media Service, IP multimedia service), Internet, etc.
  • IMS IP Multi-media Service, IP multimedia service
  • Internet etc.
  • the terminal accesses the data network by establishing a PDD session from the terminal to the RAN to the UPF to the DN.
  • the network architecture further includes a terminal, an AMF network element, an AF network element, a PCF network element, a UDM network element, a central DN, and a local DN as an example for description.
  • the terminal communicates with the AMF network element through a Next Generation Network (N1) interface (N1 for short).
  • the access network device communicates with the AMF network element through the N2 interface (N2 for short).
  • the access network equipment communicates with ULCL/BP through the N3 interface (N3 for short).
  • the ULCL/BP communicates with the second UPF network element and the first UPF network element through the N9 interface.
  • the first UPF network element communicates with the local DN through the N6 interface (N6 for short).
  • the second UPF network element communicates with the central DN through an N6 interface (N6 for short), and any two UPF network elements communicate through an N9 interface (N9 for short).
  • ULCL/BP communicates with SMF network elements through the N4 interface (N4 for short).
  • the AMF network element communicates with the SMF network element through the N11 interface (N11 for short).
  • the AMF network element communicates with the UDM network element through the N8 interface (N8 for short).
  • the SMF network element communicates with the PCF network element through the N7 interface (N7 for short).
  • the SMF network element communicates with the UDM network element through the N10 interface (N10 for short).
  • the AUSF network element communicates with the UDM network element through the N13 interface (N13 for short).
  • the UDM network element communicates with the UDR network element.
  • the PCF network element communicates with the UDR network element.
  • ULCL/BP can be implemented through UPF.
  • Fig. 4b shows an architecture based on a service-oriented interface in a 5G network architecture.
  • the control plane network elements in the 5G core network in Fig. 4b can also interact with a service-oriented interface.
  • AMF network elements, AUSF network elements, SMF network elements, UDM network elements, UDR network elements, or PCF network elements interact with each other using a service-oriented interface.
  • the service-oriented interface provided by the AMF network element to the outside may be Namf.
  • the service-oriented interface provided by the SMF network element to the outside may be Nsmf.
  • the service-oriented interface provided by the UDM network element to the outside may be Nudm.
  • the service-oriented interface provided by the UDR network element to the outside may be Nudr.
  • the service-oriented interface provided by the PCF network element to the outside may be Npcf. It should be understood that the relevant description of the names of various service-oriented interfaces in FIG. 4b can refer to the 5G system architecture (5G system architecture) diagram in the 23501 standard, which will not be repeated here.
  • FIG. 4c it is a schematic diagram of another architecture in which the above-mentioned communication system is applied to a 5G network.
  • the difference between this architecture and Figure 4a is that ULCL/BP and the first UPF network element communicate with the first SMF network element, or managed by the first SMF network element; the second UPF network element communicates with the second SMF network element, or Said to be managed by the second SMF network element.
  • the first SMF network element and the second SMF network element can communicate with each other.
  • the name of the interface between the network elements in FIG. 4a or FIG. 4b or FIG. 4c is only an example, and the name of the interface may be other names in a specific implementation, which is not specifically limited in the embodiment of the present application.
  • the RAN device, AF network element, AMF network element, SMF network element, UDM network element, UPF network element, and PCF network element in Figure 4a or Figure 4b or Figure 4c is only a name, and the name refers to the device itself. Does not constitute a limitation.
  • the network elements corresponding to RAN equipment, AF network elements, AMF network elements, SMF network elements, UDM network elements, UPF network elements, and PCF network elements can also have other names. The application embodiment does not specifically limit this.
  • the UDM network element may also be replaced with a user home server (home subscriber server, HSS) or user subscription database (user subscription database, USD) or a database entity, etc., which will be uniformly explained here and will not be repeated in the following .
  • HSS home subscriber server
  • USD user subscription database
  • the terminal, RAN, UPF, and DN in Figure 4a or Figure 4b or Figure 4c are generally called user layer network functional entities.
  • the data traffic of the terminal can be transmitted through the PDU session established between the terminal and the DN.
  • the control layer network functions and entities After the two network functions (entities) of RAN and UPF; the other parts are called control layer network functions and entities, which are mainly responsible for functions such as authentication and authentication, registration management, session management, mobility management, and policy control. In this way, reliable and stable transmission of user-level traffic is realized.
  • the PDU session involved in the embodiments of this application refers to a connection (association between the UE and a Data Network that provides a PDU connectivity service) between the terminal and the data network to provide a PDU connection service.
  • the session management network element 10, the offload point 201, the remote anchor point 202, and the local anchor point 203 in the embodiment of the present application may also be referred to as communication devices, which may be a general-purpose device or a dedicated device.
  • the application embodiment does not specifically limit this.
  • the session management network element 10 may be implemented by the communication device (or communication device) 50 in FIG. 5.
  • FIG. 5 shows a schematic structural diagram of a communication device 50 provided by an embodiment of the application.
  • the communication device 50 includes one or more processors 501, and at least one communication interface (in FIG. 5, the communication interface 504 and one processor 501 are taken as an example for illustration), and optionally may also include Memory 503; optionally, a communication bus 502 may also be included.
  • the processor 501, the communication interface 504, or the memory 503 may be coupled together (not shown in FIG. 5), or, as shown in FIG. 5, they may also be connected together through a communication bus 502.
  • the processor 501 may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more programs for controlling the execution of the program of this application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication bus 502 may be a peripheral component interconnect standard (PCI) bus or an extended industry standard architecture (EISA) bus, etc.
  • PCI peripheral component interconnect standard
  • EISA extended industry standard architecture
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only a thick dashed line is used in FIG. 5 to represent it, but it does not mean that there is only one bus or one type of bus.
  • the communication bus 502 can be used to connect different components in the communication device 50 so that different components can communicate.
  • the communication interface 504 may be a transceiver module for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.
  • the transceiver module may be a device such as a transceiver or a transceiver.
  • the communication interface 504 may also be a transceiver circuit located in the processor 501 to implement signal input and signal output of the processor.
  • the memory 503 may be a device having a storage function.
  • it can be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types that can store information and instructions
  • Dynamic storage devices can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disc storage ( Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can be stored by a computer Any other media taken, but not limited to this.
  • the memory may exist independently, and is connected to the processor through the communication line 502. The memory can also be integrated with the processor.
  • the memory 503 is used to store computer instructions for executing the solution of the present application, and the processor 501 controls the execution.
  • the processor 501 is configured to execute computer instructions stored in the memory 503, so as to implement the method provided in the embodiment of the present application.
  • the processor 501 may also perform processing-related functions in the method provided in the following embodiments of the present application, and the communication interface 504 is responsible for communicating with other devices or communication networks.
  • the example does not make specific restrictions on this.
  • the computer instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.
  • the processor 501 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 5.
  • the communication device 50 may include multiple processors, such as the processor 501 and the processor 508 in FIG. 5. Each of these processors can be a single-CPU (single-CPU) processor or a multi-core (multi-CPU) processor.
  • the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).
  • the structure shown in FIG. 5 does not constitute a specific limitation on the communication device.
  • the communication device may include more or fewer components than those shown in the figure, or combine certain components, or split certain components, or arrange different components.
  • the illustrated components can be implemented in hardware, software, or a combination of software and hardware.
  • embodiments of the present application are not limited to the 5G network architecture shown in FIG. 4a to FIG. 4c, and can also be applied to other future communication systems, such as 6G network architecture.
  • the names of the various network elements used in the embodiments of the present application may remain the same in function in the future communication system, but the names will be changed.
  • a method for counting users of a service flow includes the following steps:
  • the session management network element determines a user volume statistics rule.
  • the user volume statistics rule includes the user volume statistics rule of the first service flow and/or the user volume statistics rule of the second service flow.
  • the first service flow is an uplink service flow that needs to be controlled by the local service chain
  • the second service flow It is a downstream service flow that needs to be controlled by the local service chain.
  • the user quantity statistics rule of the first service flow is used to instruct the user quantity statistics of the first service flow before the local service chain control, and/or the user quantity statistics of the first service flow after the local service chain control.
  • the user quantity statistics rule of the second service flow is used to instruct the user quantity statistics of the second service flow before the local service chain control, and/or the user quantity statistics of the second service flow in the local service chain control.
  • the user volume statistics rule in the embodiment of the present application is for the service flow in a certain session of the terminal, which is described here in a unified manner, and the following embodiments will not be repeated.
  • the user volume statistics of the service flow may be understood as user volume statistics based on traffic and/or duration.
  • user volume statistics may also be other forms of user volume statistics, such as user volume statistics based on service types.
  • the present invention does not limit the specific statistical form.
  • user volume statistics based on traffic refers to statistics on traffic used or occupied bandwidth resources for transmitting service streams, and its units are generally megabits (MB), kilobits (KB), and so on. For example, each time you transmit a service flow, you can count the traffic used to transmit the service flow this time, periodically calculate the sum of the traffic used for multiple transmissions of the service flow in the current cycle, and use the total traffic as the service in the current cycle. The number of users of the stream.
  • MB megabits
  • KB kilobits
  • user volume statistics based on time length refers to statistics on the time length of the transmission service flow, and the unit is generally minutes, hours, and so on.
  • the start time is counted.
  • the service flow is subsequently transmitted, it is judged whether the time interval between the current transmission of the service flow and the last transmission of the service flow is greater than or equal to the preset threshold.
  • the time when the service flow is transmitted for the second time is regarded as the end time, and the time length for transmitting the service flow is the time between the start time and the end time; if not, it is considered that the transmission of the service flow is not interrupted, and the next time the service flow is transmitted, it will continue. Make judgments.
  • the user volume statistics are performed on the service flow before the local service chain control, or the user volume statistics are performed on the service flow after the local service chain control, which may be called simple statistics; for the local service chain Performing user volume statistics on the service flow before control, and user volume statistics on the service flow after the local service chain control, can be called differentiated statistics.
  • the above-mentioned user volume statistics rule of the first service flow can also be understood as used to indicate simple statistics on the first service flow, or to indicate differentiated statistics on the first service flow; the user volume of the second service flow
  • the statistical rule may be understood as being used to indicate simple statistics on the second service flow, or used to indicate differentiated statistics on the second service flow.
  • the session management network element may determine the user volume statistics rule according to the policy control rule from the policy control function network element.
  • the method provided in the embodiment of the present application further includes: the policy control function network element sends the first policy control rule and/or the second policy control rule to the session management network element
  • the session management network element receives the first policy control rule and/or the second policy control rule from the policy control function network element.
  • the first policy control rule includes description information and first indication information of the first service flow.
  • the description information of the first service flow is used to identify or determine the first service flow, and the first indication information is used to indicate the local service. Whether the size of the first service flow after chain control changes.
  • the size of the business flow may refer to the flow size of the business flow.
  • the size of the business flow changes after the local business chain is controlled: before the local business chain is controlled, the size of the business flow is 10MB; after the local business chain is controlled, the size of the business flow becomes 5MB.
  • the description information of the service flow may include: quintuple information (for example, IP quintuple), triplet information (for example, IP triplet), tunnel information, application identification, and data network name (data network name). name, DNN), or one or more of single network slice selection assistance information (S-NSSAI).
  • the IP five-tuple may include, for example, a source IP address, a source port number, a destination IP address, a destination port number, and a transport layer protocol.
  • the size of the service stream will usually change after being processed by the service chain. For example, after the video service stream is rendered by the service chain, the size of the video service stream may become larger; or the video service stream may be changed by the service chain. After video compression, the size of the video service stream may become smaller.
  • the session management network element determining the user volume statistics rule may include: when the first indication information is used to indicate that the size of the first service flow does not change after the local service chain is controlled, the session management network element determines the first service
  • the flow user volume statistics rule is used to instruct user volume statistics to be performed on the first service flow before the local service chain control, or used to instruct user volume statistics to be performed on the first service flow after the local service chain control.
  • the session management network element determines that the user volume statistics rule of the first service flow is used to indicate the first service flow before the local service chain is controlled.
  • the service flow performs user volume statistics, and performs user volume statistics on the first service flow after the local service chain is controlled.
  • the network can more reasonably charge end users and third-party application providers.
  • the network can charge end users according to the number of users of the first service flow before the local service chain control.
  • the third-party application provider is charged according to the number of users of the first service flow after the local service chain control.
  • the second policy control rule includes description information of the second service flow and second indication information.
  • the description information of the second service flow is used to identify or determine the second service flow
  • the second indication information is used to indicate the local service. Whether the size of the second service flow after chain control changes.
  • the session management network element determining the user volume statistics rule may include: when the second indication information is used to indicate that the size of the second service flow after the local service chain control does not change, the session management network element determines the second service
  • the flow user volume statistics rule is used to instruct user volume statistics to be performed on the second service flow before the local service chain control, or used to instruct user volume statistics to be performed on the second service flow after the local service chain control.
  • the session management network element determines that the user volume statistics rule of the second service flow is used to indicate the second service flow before the local service chain is controlled.
  • the service flow performs user statistics, and performs user statistics on the second service flow after the local service chain is controlled.
  • the second service flow and the first service flow may be a downlink service flow and an uplink service flow of the same service, or may be a downlink service flow and an uplink service flow of different services.
  • the description information of the second service flow and the first service flow are different .
  • the session management network element sends a user volume statistics rule to the user plane network element.
  • the user plane network element receives the user quantity statistics rule from the session management network element.
  • step S602 it can be considered that the user plane network element has obtained the user volume statistics rule from the session management network element.
  • the user-plane network element may also obtain the user volume statistical rule through other methods, for example, the user-plane network element determines or generates the user volume statistical rule by itself, which is not specifically limited in the embodiment of the present application.
  • the user plane network element obtains the user volume statistics rule from the session management network element as an example for description.
  • the user plane network element performs user amount statistics according to the user amount statistics rule.
  • the user plane network element when the user amount statistics rule includes the user amount statistics rule of the first service flow, the user plane network element counts the user amount of the first service flow according to the user amount statistics rule of the first service flow; the user amount statistics rule includes the second service flow.
  • the user plane network element When the user quantity statistics rule of the service flow is used, the user plane network element counts the user quantity of the second service flow according to the user quantity statistics rule of the second service flow.
  • the session management network element obtains the user amount statistics rule of the uplink service flow and/or the downlink service flow, and sends the user amount statistics rule to the user plane network element.
  • User plane network elements can perform user statistics on uplink or downlink service flows according to the user statistics rules, realize user statistics on service flows that need to be controlled by the local service chain, and improve the accuracy of user statistics on this type of service flow Spend.
  • the above-mentioned user plane network elements can implement different functions in the communication system provided by the embodiment of this application (for example, the communication system shown in FIG. 3). Accordingly, the above-mentioned user volume statistics rule It may also be different.
  • the user plane network element can be used as a diversion point.
  • the user plane network element can be called a diversion point, and the two can be replaced with each other.
  • the user volume statistics rule of the first service flow is used to instruct the user volume statistics of the first service flow before the local service chain control, and may include: the user volume statistics rule of the first service flow is used to instruct the user plane network element to connect with each other.
  • the first service flow of the networked device performs user statistics.
  • the user volume statistics rule of the first service flow is used to instruct the user volume statistics of the first service flow after the local service chain is controlled, and may include: the user volume statistics rule of the first service flow is used to instruct the user plane network element pair
  • the first service flow from the local anchor point performs user statistics.
  • the user quantity statistics rule of the first service flow is used to instruct the user quantity statistics of the first service flow after the local service chain control, which may include: the first service flow after the local service chain control is transmitted to the branch point
  • the user volume statistics rule of the first service flow is used to instruct the user plane network element to perform user volume statistics on the first service flow from the local anchor point.
  • the offload point 201 after being transmitted from the access network device 30 to the offload point 201, the offload point 201 sends to the local anchor point 203 for local service chain control.
  • Uplink traffic flows through "local DN ⁇ local anchor 203 ⁇ distribution point 201 ⁇ remote anchor 202 ⁇ central DN” (referred to as path 1) to the central DN, or via "local DN ⁇ local anchor 203 ⁇ remote Anchor point 202 ⁇ central DN” (referred to as path 2) is transmitted to the central DN.
  • the upstream service flow from the access network device 30 is the upstream service flow before the local service chain control;
  • the uplink service flow after the local service chain control is transmitted through path 1
  • the uplink service flow from the local anchor point 203 is the uplink service flow after the local service chain control.
  • the user quantity statistics rule of the second service flow is used to instruct the user quantity statistics of the second service flow before the local service chain control, and may include: the user quantity statistics rule of the second service flow is used to instruct the user plane network element to communicate from the remote The second service flow of the end anchor point performs user statistics.
  • the user quantity statistics rule of the second service flow is used to instruct the user quantity statistics of the second service flow after the local service chain control may include: the user quantity statistics rule of the second service flow is used to instruct the user plane network element to The second service flow of the local anchor point performs user statistics.
  • the user volume statistics rule of the second service flow is used to instruct the user volume statistics of the second service flow before the local service chain control, which may include: the second service flow before the local service chain control is transmitted to the branch point
  • the user volume statistics rule of the second service flow is used to instruct the user plane network element to perform user volume statistics on the second service flow from the remote anchor point.
  • the remote anchor point 202 after being transmitted from the central DN to the remote anchor point 202, the remote anchor point 202 sends to the local anchor point 203 for local service chain control. It is understandable that the downlink The service flow can reach the local anchor point 203 through "remote anchor point 202 ⁇ distribution point 201 ⁇ local anchor point 203" (referred to as path 3) or "remote anchor point 202 ⁇ local anchor point 203" (referred to as path 4) .
  • the downlink service flow after the local service chain control is transmitted to the access network device 30 through the shunt point 201, and is sent to the terminal by the access network device 30.
  • the downlink service flow from the local anchor point 203 is the downlink service flow after the local service chain control; in the case that the downlink service flow before the local service chain control is transmitted through path 3, for the offload point
  • the downlink service flow from the remote anchor point 202 is the downlink service flow after the local service chain control.
  • the first service flow is represented by SDF (service data flow)1
  • the second service flow is represented by SDF2 as an example.
  • the user volume statistics rule can be any one of the following Table 1, for example, user The volume statistics rule can be: perform user volume statistics on the SDF1 from the access network device; or it can include any combination of any number in the following Table 1.
  • the user volume statistics rule can be: the SDF1 from the access network device , And SDF2 from the local anchor point for user statistics.
  • the user plane network element can identify whether the service flow is the service flow indicated in the user volume statistics rule, and if so, the user volume of the service flow is counted.
  • the user plane network element after the user plane network element receives the service flow, it can first identify whether the service flow is the first service flow, and if the service flow is determined If it is the first service flow, it is then identified whether the source of the first service flow is the same as the source indicated by the user volume statistics rule of the first service flow, and if they are the same, the user volume of the first service flow is counted.
  • the user plane network element may also first identify the source of the service flow and then identify whether the service flow is the first service flow or the second service flow, which is not specifically limited in this application.
  • the user plane network element can determine the source of the service flow through tunnel information (tunnel information, hereinafter referred to as tunnel info) in the header of the service flow.
  • tunnel info tunnel information
  • the user plane network element can judge whether the service flow has passed the local service chain control through the tunnel information in the header of the service flow.
  • SDF1 from access network equipment in Table 1 can be described as "SDF1 not controlled by local service chain” or “SDF1 before local service chain control”;
  • SDF1 from local anchor point can be described It is “SDF1 after local service chain control” or “SDF1 after local service chain control”;
  • SDF2 from remote anchor point can be described as "SDF2 not controlled by local service chain” or "local service chain control” The previous SDF2";
  • SDF2 from the local anchor point can be described as "SDF2 controlled by the local service chain” or "SDF2 controlled by the local service chain”.
  • the user plane network element can determine that the first service flow originates from the access network The device, in other words, the user plane network element can determine that the first service flow is not controlled by the local service chain; if the header of the first service flow carries the tunnel information of the branch point corresponding to the local anchor point, that is, I-UPF tunnel info for L-PSA, the user plane network element can determine that the first service flow originates from the local anchor point. In other words, the user plane network element can determine that the first service flow has passed the local service chain control.
  • the user plane network element can determine that the second service flow originated from the remote The anchor point, in other words, the user plane network element can determine that the second service flow is not controlled by the local service chain; if the packet header of the second service flow carries the tunnel information of the branch point corresponding to the local anchor point, that is, I- UPF tunnel info for L-PSA, the user plane network element can determine that the second service flow originates from the local anchor point. In other words, the user plane network element can determine that the second service flow has passed the local service chain control.
  • the user plane network element may also determine that the first service flow originates from the local anchor point, that is, the first service flow has been controlled by the local service chain.
  • the second dedicated tunnel is used to transmit the downstream service flow before the local service chain control, if the report of the second service flow
  • the header carries the tunnel information of the second dedicated tunnel, and the user plane network element can also determine that the second service flow originates from the remote anchor point, that is, the second service flow needs to be controlled by the local service chain.
  • the user plane network element may also determine whether the service flow has been controlled by the local service chain through the identification information carried in the packet of the service flow.
  • the first service flow after the local service chain control may be associated with the first identifier, and the first identifier is used to indicate that the service flow has passed the local service chain control.
  • the user plane network element may determine that the message is the message control of the first service flow after the local service chain control.
  • the second service flow after the local service chain control can be associated with the second identifier, and the second identifier is used to indicate that the service flow has passed the local service chain control.
  • the user plane network element may determine that the message is the message control of the second service flow after the local service chain control.
  • the user plane network element can be used as a remote anchor point.
  • the user plane network element can be called a remote anchor point, and the two can be replaced with each other.
  • the user volume statistics rule of the first service flow is used to instruct user volume statistics to be performed on the first service flow after the local service chain is controlled. It may include: the user volume statistics rule of the first service flow is used to instruct the user plane network element to perform user volume statistics on the first service flow, and the first service flow may come from a distribution point or a local anchor point.
  • the first service flow after the local service chain control is transmitted to the central DN through the offload point
  • the first service flow comes from the offload point.
  • the first service flow after the local service chain control is not transmitted to the central DN through the offload point
  • the first service flow comes from the local anchor point.
  • the upstream service flow from the offload point 201 is the local service chain
  • the first service flow it receives is the first service flow processed by the local service chain.
  • the user volume statistics rule of the second service flow is used to instruct user plane statistics to be performed on the second service flow before the local service chain control. It may include: the user volume statistics rule of the second service flow is used to instruct the user plane network element to perform user volume statistics on the second service flow, and the second service flow is from the central DN.
  • the downlink service flow from the central DN is the downlink service flow before the local service chain control.
  • the second service flow it receives is the second service flow before the local service chain processing.
  • the first service flow is represented by SDF1
  • the second service flow is represented by SDF2 as an example.
  • the user volume statistics rule can be any one of the following Table 2; or it can include any number of the following Table 2 Any combination of items.
  • the user volume statistics rule does not indicate the source of the service flow.
  • the user volume statistics rule includes the user volume statistics rule of the first service flow. In the case of receiving the first service flow, it performs user volume statistics, and when the user volume statistics rule includes the user volume statistics rule of the second service flow, it performs user volume statistics upon receiving the second service flow.
  • the user plane network element can be used as a local anchor point.
  • the user plane network element can be called a local anchor point, and the two can be replaced with each other.
  • the user quantity statistics rule of the first service flow is used to instruct the user quantity statistics of the first service flow before the local service chain control, and may include: the user quantity statistics rule of the first service flow is used to instruct the user plane network element to split the user Point’s first service flow performs user statistics.
  • the user volume statistics rule of the first service flow is used to instruct the user volume statistics of the first service flow after the local service chain is controlled, and may include: the user volume statistics rule of the first service flow is used to instruct the user plane network element pair The first service flow from the local data network performs user statistics.
  • the upstream service flow from the offload point 201 is the upstream service flow before the local service chain control; the upstream service flow from the local DN is after the local service chain control Upstream traffic flow.
  • the user quantity statistics rule of the second service flow is used to instruct the user quantity statistics of the second service flow before the local service chain control, and may include: the user quantity statistics rule of the second service flow is used to instruct the user plane network element to split the user The second service flow of the point or remote anchor point performs user statistics.
  • the user volume statistics rule of the second service flow is used to instruct the user volume statistics of the second service flow after the local service chain is controlled, and may include: the user volume statistics rule of the second service flow is used to instruct the user plane network element pair The second service flow from the local data network performs user statistics.
  • the user volume statistics rule of the second service flow is used to instruct the user volume statistics of the second service flow before the local service chain control, which may include: the second service flow before the local service chain control is transmitted to the branch point
  • the user volume statistics rule of the second service flow is used to instruct the user plane network element to perform user volume statistics on the second service flow from the branch point.
  • the user volume statistics rule of the second service flow is used to instruct the user plane network element to respond to the second service from the remote anchor point. Flow for user statistics.
  • the downstream service flow from the offload point 201 is before the local service chain control
  • the downlink service flow from the remote anchor point 202 is the downlink service flow before the local service chain control.
  • the first service flow is represented by SDF1
  • the second service flow is represented by SDF2 as an example.
  • the user volume statistics rule can be any one of the following Table 3; or it can include any number of the following Table 3 Any combination of items.
  • step S603 the manner in which the user plane network element performs user amount statistics according to the user amount statistics rule may refer to the related description in the foregoing first implementation scenario.
  • the user plane network element when the user plane network element judges the source of the first service flow, if the packet header of the first service flow includes the tunnel information of the local anchor point, that is, L-PSA tunnel info, the user plane network element can determine that the first service flow originates from the branch point; if the first service flow packet includes the service chain protocol header, the user plane network element can determine that the first service flow is processed by the local service chain , From the local data network.
  • the tunnel information of the local anchor point that is, L-PSA tunnel info
  • the user plane network element when the user plane network element judges the source of the second service flow, if the packet header of the second service flow includes the tunnel information of the local anchor point, that is, L-PSA tunnel info, the user plane network element can determine that the second service flow originates from the offload point or the remote anchor point; if the message of the second service flow includes the service chain protocol header, the user plane network element can determine that the second service flow is local After the business chain is processed, it comes from the local data network.
  • the tunnel information of the local anchor point that is, L-PSA tunnel info
  • L-PSA the second service flow will not come from the offload point and the remote anchor point at the same time.
  • L-PSA does not need to determine whether the second service flow comes from the offload point. It is also from a remote anchor point, and when the L-PSA tunnel info is included in the header of the second service flow, the L-PSA can determine that the second service flow is the second service flow before the local service chain control.
  • the user plane network element may include a remote anchor point and a local anchor point, that is, the remote anchor point and the local anchor point jointly count the number of users of the first service flow or the second service flow.
  • the user volume statistics of the first service flow and the second service flow may be simple statistics or differentiated statistics.
  • the statistical methods of the first service flow and the second service flow may be different.
  • the statistical method of the first service flow is simple statistics
  • the statistical method of the second service flow is differentiated statistics
  • the statistics of the first service flow and the second service flow The statistical methods can be the same, for example, both are simple statistics.
  • this implementation scenario can be understood as a combination of the foregoing second and third implementation scenarios.
  • the remote anchor point may count the number of users of the first service flow after the local service chain is controlled, and the local anchor point may count the number of users of the first service flow. The number of users of the second service flow after the local service chain control.
  • the remote anchor can count the number of users of the first service flow after the control of the local service chain, and the local service The number of users of the second service flow before chain control, while the local anchor points the number of users of the first service flow before the local service chain control and the number of users of the second service flow after the local service chain control.
  • the remote anchor point and the local anchor point do not perform repeated statistics. For example, if the remote anchor point counts the number of users of the first service flow after the local service chain is controlled, then the local anchor point does not count the local service chain. Control the number of users in the first service stream afterwards.
  • the communication system shown in Figure 3 is applied to the 5G network shown in Figure 4a or Figure 4b.
  • the UCLC/BP in Figure 4a or Figure 4b is I-UPF
  • the second UPF is the remote PSA (hereinafter referred to as PSA).
  • PSA remote PSA
  • the first UPF is L-PSA as an example, the method for counting the number of users of the service flow provided in the embodiment of the present application will be described.
  • a service flow user quantity statistics method provided by this embodiment of the application can be applied to a scenario where a tapping point (i.e., I-UPF) performs simple user quantity statistics.
  • the method includes:
  • the AF network element sends a message a to the PCF network element.
  • the PCF network element receives the message a from the AF network element.
  • the message a includes the description information of the first service flow and/or the description information of the second service flow.
  • the message a may also include the first indication information and/or the first service chain information, and the first indication information is used to indicate the operation after the local service chain control.
  • the first service chain information is used to indicate the first service chain, which is the service chain through which the first service flow passes, or is the service chain that processes the first service flow.
  • the first service chain information may include at least one of the following: the identification of one or more SF network elements, the order of the one or more SF network elements in the first service chain, or the information of the one or more SF network elements
  • the location information indicates that the SF network element is located at the central DN or the local DN.
  • the embodiment of the present application takes the SF network element located at the local DN, that is, the first service flow needs to be processed by the local service chain as an example for description.
  • message a may also include second indication information and/or second service chain information, and the second indication information is used to indicate the next step after the local service chain is controlled. Whether the size of the second service flow changes, the second service chain information is used to indicate the second service chain, and the second service chain is the service chain through which the second service flow passes, or is the service chain for processing the second service flow.
  • the second service chain information may include at least one of the following: the identification of one or more SF network elements, the order of the one or more SF network elements in the second service chain, or the information of the one or more SF network elements
  • the location information indicates that the SF network element is located at the central DN or the local DN.
  • the embodiment of the present application takes the SF network element located at the local DN, that is, the second service flow needs to be processed by the local service chain as an example for description.
  • first business chain and the second business chain can be the same or different. That is, the first business flow and the second business flow can be processed by the same business chain or by different business chains. This application is implemented The example does not make specific restrictions on this.
  • the message a may be an AF request (request).
  • the PCF network element sends a message b to the SMF network element, where the message b includes policy control rules.
  • the SMF network element receives the message b from the PCF network element.
  • the PCF may generate policy control rules according to message a.
  • the policy control rule may further include a first policy control rule, and the first policy rule includes the description information of the first service flow and the first indication information.
  • the policy control rule may also include the first service chain information.
  • the policy control rule may further include a second policy control rule, and the second policy control rule includes the description information of the second service flow and the second indication information, and the second policy control rule also May include second business chain information.
  • the message b may specifically be Npcf_SMPolicyControl_UpdateNotify request, which corresponds to the policy modification process triggered by AF; or, it may be Npcf_SMPolicyControl_Update response, which corresponds to the session modification process; or, it may be Npcf_SMPolicyControl_Create response, which corresponds to the session establishment process.
  • the session modification process corresponding to message b is taken as an example for description.
  • the terminal device has established a session, and the user plane transmission path corresponding to the session is: terminal ⁇ - ⁇ RAN ⁇ - ⁇ PSA ⁇ - ⁇ Central DN, that is, SMF network elements have obtained RAN tunnel information (RAN tunnel info) and PSA tunnel information (PSA tunnel info).
  • RAN tunnel info RAN tunnel info
  • PSA tunnel info PSA tunnel info
  • the SMF network element decides to insert I-UPF and L-PSA for the session.
  • the I-UPF acts as a shunt point, which can send part of the terminal's service flow to the L-PSA and the other part to the PSA.
  • the SMF network element may decide to insert I-UPF and L-PSA for the session when it detects that the terminal has a new service flow; or, when the terminal moves to the area served by the local DN, it may decide to insert the I-UPF and L-PSA for the session. -UPF and L-PSA.
  • step S703 can be performed first, and then steps S701 to S702; steps S701 to S702 can be performed first, and then step S703; or steps can be performed at the same time.
  • S704 SMF network element selects L-PSA.
  • the SMF network element sends an N4 session establishment request to the L-PSA.
  • L-PSA receives the N4 session establishment request.
  • the N4 session establishment request includes PSA tunnel info.
  • L-PSA can obtain PSA tunnel info, that is, a user plane connection between L-PSA ⁇ PSA can be established, so that L-PSA can send service flows to PSA.
  • establishing a user plane connection means transmitting the tunnel information of two end points (ie, network elements) on the user plane connection to the opposite end. For example, if endpoint A obtains the tunnel information of endpoint B, the user plane connection from endpoint A to endpoint B is successfully established; endpoint B obtains the tunnel information of endpoint A, then the user plane connection from endpoint B to endpoint A is established successfully.
  • the L-PSA sends an N4 session establishment response to the SMF network element.
  • the SMF network element receives the N4 session establishment response.
  • the N4 session establishment response carries L-PSAtunnel info.
  • the L-PSA tunnel info may also be allocated by the SMF network element.
  • the embodiment of this application only uses the L-PSA allocation L-PSA tunnel info as an example for description.
  • the SMF network element allocates the L-PSA tunnel info
  • the SMF network element sends the L-PSA tunnel info to the L-PSA in the N4 session establishment request.
  • tunnel info is allocated in the subsequent steps, it can be allocated by SMF network elements, or by L-PSA, or I-UPF or PSA.
  • the SMF network element sends an N4 session establishment request to the I-UPF network element.
  • the I-UPF network element receives the N4 session establishment request.
  • the N4 session establishment request carries RAN tunnel info, PSA tunnel info, L-PSA tunnel info, and user volume statistics rules.
  • RAN tunnel info is used to establish a downlink user plane connection between the I-UPF network element and the RAN, and then the RAN tunnel info can be carried in the header of the service flow sent by the I-UPF network element to the RAN. That is, when the I-UPF receives the service flow to be sent to the RAN, it can send it to the RAN.
  • PSA tunnel info is used to establish an uplink user plane connection between the I-UPF network element and the PSA.
  • the header of the service flow sent by the I-UPF network element to the PSA can carry PSA tunnel info. That is, when the I-UPF receives the service stream sent to the PSA, it can send it to the PSA.
  • L-PSA tunnel info is used to establish an uplink user plane connection between the I-UPF network element and the L-PSA, and then the I-UPF network element can carry the L-PSA in the header of the service flow sent to the L-PSA tunnel info. That is, when the I-UPF receives the service flow sent to the L-PSA, it can send it to the L-PSA.
  • the user quantity statistics rule may be determined by the SMF network element according to the policy control rule from the PCF. For related description, please refer to the above step S601, which will not be repeated here.
  • the user statistics rule may include the user statistics rule of the first service flow and/or the second service.
  • the user volume statistics rule of the flow the user volume statistics rule of the first service flow is used to indicate the user volume statistics of the first service flow before the local service chain control, or to indicate the user volume of the first service flow after the local service chain control Volume statistics
  • the user volume statistics rule of the second service flow is used to indicate the user volume statistics of the second service flow before the local service chain control, or indicate the user volume statistics of the second service flow after the local service chain control.
  • the user volume statistics rule may be one of the following:
  • Case 1 Perform user statistics on the first service flow from the RAN, that is, the first service flow carrying I-UPF tunnel info for RAN in the header;
  • the user volume statistics are performed.
  • Case 2 Perform user statistics on the first service flow from L-PSA, that is, the first service flow carrying I-UPF tunnel info for L-PSA in the header;
  • the user volume is counted.
  • Case3 Perform user statistics on the first service flow from the RAN, that is, the first service flow carrying I-UPF tunnel info for RAN in the header;
  • the user volume is counted.
  • Case4 Perform user statistics on the first service flow from L-PSA, that is, the first service flow carrying I-UPF tunnel info for L-PSA in the header;
  • the user volume statistics are performed.
  • Case5 Perform user statistics on the first service flow from the RAN, that is, the first service flow carrying I-UPF tunnel info for RAN in the header.
  • Case6 Perform user statistics on the first service flow from L-PSA, that is, the first service flow carrying I-UPF tunnel info for L-PSA in the header.
  • Case7 Perform user statistics on the second service flow from the PSA, that is, the second service flow carrying I-UPF tunnel info for PSA in the header.
  • Case 8 Perform user statistics on the second service flow from L-PSA, that is, the second service flow carrying I-UPF tunnel info for L-PSA in the header.
  • the user volume statistics rules in the above various situations can be represented as Table 4.
  • UL refers to the uplink service flow
  • DL refers to the downlink service flow
  • UL:before refers to the uplink service flow before the local service chain control
  • UL:after refers to the uplink service flow after the local service chain control.
  • DL:before refers to the downlink service flow before the local service chain control
  • DL:after refers to the downlink service flow after the local service chain control
  • the I-UPF network element returns an N4 session establishment response to the SMF network element.
  • the SMF network element receives the N4 session establishment response.
  • the N4 session establishment response carries I-UPF tunnel info for RAN, I-UPF tunnel info for PSA, and I-UPF tunnel info for L-PSA.
  • I-UPF tunnel info for RAN is the tunnel information corresponding to the RAN allocated by the I-UPF, which is used to establish the uplink user plane connection between the RAN and the I-UPF network element.
  • the SMF network element sends this information to the RAN
  • the header of the service flow sent by the RAN to the I-UPF network element can carry I-UPF tunnel information for RAN, that is, the I-UPF network element can carry the I-UPF according to the I-UPF carried in the header of the service flow.
  • tunnel information for RAN confirm that the service flow comes from PSA.
  • the I-UPF tunnel info for PSA is the tunnel information corresponding to the PSA allocated by the I-UPF, which is used to establish a downlink user plane connection between the PSA and the I-UPF network element.
  • the SMF network element sends this information to the PSA, that is, after the PSA obtains the I-UPF tunnel info for the PSA, the downlink user plane connection between the PSA and the I-UPF network element is successfully established.
  • the I-UPF tunnel info for PSA can be carried in the header of the service flow sent by the PSA to the I-UPF, that is, the I-UPF can be based on the I-UPF tunnel info for PSA carried in the header of the service flow. , Make sure that the service flow comes from PSA.
  • the I-UPF tunnel info for L-PSA is the tunnel information corresponding to the L-PSA allocated by the I-UPF, which is used to establish an uplink user plane connection between the L-PSA and the I-UPF network element.
  • the SMF network element sends the information to the L-PSA, that is, after the L-PSA obtains the I-UPF tunnel info for the L-PSA
  • the downlink user plane connection between the L-PSA and the I-UPF is successfully established.
  • the header of the service flow sent by L-PSA to I-UPF can carry I-UPF tunnel info for L-PSA, that is, the I-UPF can be based on the I-UPF carried in the header of the service flow.
  • tunnel info for L-PSA confirm that the service flow originates from L-PSA.
  • the N4 session establishment response may also include specific I-UPF tunnel info for L-PSA , Otherwise, specific I-UPF tunnel info for L-PSA may not be included.
  • the SMF network element sends an N4 session modification request to the PSA network element.
  • the PSA network element receives the N4 session modification request.
  • the N4 session modification request includes I-UPF tunnel info for PSA.
  • the PSA network element sends an N4 session modification response to the SMF network element.
  • the SMF network element receives the N4 session modification response from the PSA network element.
  • the N4 session modification response is used to indicate that the I-UPF tunnel info for PSA has been successfully received, or the N4 session modification response carries response indication information used to indicate the successful reception of the I-UPF tunnel info for PSA.
  • the SMF network element sends an N4 session modification request to the L-PSA network element.
  • the L-PSA network element receives the N4 session modification request.
  • the N4 session modification request includes I-UPF tunnel info for L-PSA, or includes I-UPF tunnel info for L-PSA and specific I-UPF tunnel info for L-PSA.
  • the L-PSA network element sends an N4 session modification response to the SMF network element.
  • the SMF network element receives the N4 session modification response from the L-PSA network element.
  • the N4 session modification response is used to indicate that the I-UPF tunnel info for L-PSA has been successfully received or the I-UPF tunnel info for L-PSA and specific I-UPF tunnel info for L-PSA have been successfully received; or the N4 session modification response It carries the response indication information used to indicate the successful reception of I-UPF tunnel info for L-PSA, or it carries the response indication information used to indicate the successful reception of I-UPF tunnel info for L-PSA and specific I-UPF tunnel info for L-PSA Instructions.
  • the I-UPF network element counts the user volume of the service flow according to the user volume statistics rule.
  • the user quantity statistics rule is received from the SMF network element in step S707.
  • the I-UPF network element when the user volume statistics rule includes the user volume statistics rule of the first service flow, the I-UPF network element counts the user volume of the first service flow according to the user volume statistics rule of the first service flow;
  • the statistical rule includes the user quantity statistical rule of the second service flow
  • the I-UPF network element counts the user quantity of the second service flow according to the user quantity statistical rule of the second service flow.
  • the I-UPF network element sends user statistics information to the SMF network element.
  • the SMF network element receives the user statistics information from the I-UPF network element.
  • the user amount statistics information may include the user amount statistics information of the first service flow, and the user amount statistics information of the first service flow indicates The local service chain controls the amount of users of the first service flow before, or indicates the amount of users of the first service flow before the local service chain controls.
  • the user amount statistics information may include the user amount statistics information of the second service flow, and the user amount statistics information of the second service flow indicates the local service chain control The number of users of the previous second service flow, or indicates the number of users of the second service flow before the local service chain control.
  • the SMF network element may report the user amount statistical information to a charging function (charging function, CHF) network element, so that the CHF network element can perform charging and other operations.
  • a charging function charging function, CHF
  • Another service flow user quantity statistics method provided in this embodiment of the present application can be applied to a scenario where L-PSA and/or PSA performs simple user quantity statistics.
  • the method includes:
  • S801 to S806 are the same as steps S701 to S706 in the embodiment shown in FIG.
  • the SMF network element sends an N4 session establishment request to the I-UPF network element.
  • the I-UPF network element receives the N4 session establishment request.
  • the N4 session establishment request carries RAN tunnel info, PSA tunnel info, and L-PSA tunnel info, and does not need to carry user volume statistics rules.
  • the N4 session establishment request carries RAN tunnel info, PSA tunnel info, and L-PSA tunnel info, and does not need to carry user volume statistics rules.
  • step S808 is the same as step S708 in the embodiment shown in FIG.
  • the SMF network element sends an N4 session modification request to the PSA network element.
  • the PSA network element receives the N4 session modification request.
  • the N4 session modification request includes I-UPF tunnel info for PSA.
  • the N4 session modification request may further include a first user volume statistics rule.
  • the first user volume statistics rule includes the user volume statistics rule of the first service flow, and/or the user volume statistics rule of the second service flow, and the user volume statistics rule of the first service flow is used to indicate the user volume statistics rule of the first service flow.
  • the first service flow after processing is subjected to user volume statistics, and the user volume statistics rule of the second service flow is used to instruct user volume statistics to be performed on the second service flow before the processing of the local service chain.
  • the first service flow may come from the I-UPF network element or from the L-PSA. It can be understood that when the first service flow after the local service chain control is transmitted to the central DN through the I-UPF network element (that is, path 1), the first service flow comes from the I-UPF network element. When the first service flow after the local service chain control is not transmitted to the central DN via the I-UPF network element (that is, path 2), the first service flow comes from the L-PSA.
  • the second service flow may come from the central DN.
  • the foregoing first user volume statistics rule may be represented as one item in Table 5.
  • UL refers to the uplink service flow
  • DL refers to the downlink service flow
  • UL:before refers to the uplink service flow before the local service chain control
  • UL:after refers to the uplink service flow after the local service chain control
  • DL:before refers to the local service chain control
  • the previous downlink service flow, DL:after refers to the downlink service flow after the local service chain control.
  • step S810 is the same as step S710 in the embodiment shown in FIG.
  • the SMF network element sends an N4 session modification request to the L-PSA network element.
  • the L-PSA network element receives the N4 session modification request.
  • the N4 session modification request includes I-UPF tunnel info for L-PSA, or includes I-UPF tunnel info for L-PSA and specific I-UPF tunnel info for L-PSA.
  • the N4 session modification request may further include a second user volume statistics rule.
  • the second user volume statistics rule includes the user volume statistics rule of the first service flow, and/or the user volume statistics rule of the second service flow, and the user volume statistics rule of the first service flow is used to indicate the user volume statistics rule of the first service flow.
  • the user volume statistics of the first service flow before or after processing are performed, and the user volume statistics rule of the second service flow is used to instruct the user volume statistics of the second service flow before or after the processing of the local service chain.
  • the user volume statistics rule of the first service flow is used to indicate the user volume statistics of the first service flow before the processing of the local service chain, which may be: the user volume of the first service flow from the I-UPF network element Statistics:
  • the user volume statistics rule of the first service flow is used to instruct user volume statistics to be performed on the first service flow processed by the local service chain, which may be: user volume statistics for the first service flow from the local DN.
  • the user volume statistics rule of the second service flow is used to instruct the user volume statistics of the second service flow before the processing of the local service chain, which can be: perform user volume statistics on the second service flow from the I-UPF network element or PSA User volume statistics; the user volume statistics rule of the second service flow is used to instruct user volume statistics to be performed on the second service flow processed by the local service chain, which may be: user volume statistics for the second service flow from the central DN.
  • the user volume statistics rule of the second service flow is used to indicate the processing of the local service chain
  • the previous second service flow for user volume statistics may be: user volume statistics for the first service flow from the I-UPF network element.
  • the user volume statistics rule of the second service flow is used to indicate the second service flow before the processing of the local service chain.
  • the second service flow for user volume statistics may be: user volume statistics for the second service flow from the PSA.
  • the foregoing second user volume statistics rule may be represented as one item in Table 6.
  • UL refers to the uplink service flow
  • DL refers to the downlink service flow
  • UL:before refers to the uplink service flow before the local service chain control
  • UL:after refers to the uplink service flow after the local service chain control
  • DL:before refers to the local service chain control
  • the previous downlink service flow, DL:after refers to the downlink service flow after the local service chain control.
  • step S809 when the SMF network element does not send the first user volume statistics rule to the PSA, in this step S811, the SMF network element sends the second user volume statistics rule to the L-PSA, that is, L-PSA conducts user statistics.
  • the SMF network element may not send the second user volume statistics rule to the L-PSA, that is, the PSA performs user volume statistics. statistics.
  • the SMF network element may also send the second user volume statistics rule to the L-PSA, that is, the PSA and L -PSA conducts joint statistics.
  • the first user volume statistics rule and the second user volume statistics rule do not have the same rules, or L-PSA and PSA do not perform repeated user volume statistics. For example, after PSA counts local business chain control If the number of users of the first service flow is determined, L-PSA no longer counts the number of users of the first service flow after the local service chain control.
  • a statistical method is: the L-PSA performs user statistics on the uplink service flow from the I-UPF.
  • Another statistical method is: L-PSA performs user statistics on the uplink service flows from the local DN, or the PSA performs user statistics on the uplink service flows from I-UPF or L-PSA.
  • L-PSA performs user statistics on the downlink service flow from the I-UPF or PSA, or the PSA performs statistics on the downlink service flow from the central DN.
  • Another statistical method is: L-PSA performs user statistics on the downlink service flow from the local DN.
  • step S812 is the same as step S712 in the embodiment shown in FIG.
  • the PSA performs user volume statistics according to the first user volume statistics rule, and/or the L-PSA performs user volume statistics according to the second user volume statistics rule.
  • step S813 if the SMF network element sends the first user volume statistics rule to the PSA, the PSA executes step S813; if the SMF network element sends the second user volume statistics rule to the L-PSA, the L-PSA executes step S813.
  • the PSA sends the statistical information of the user volume to the SMF network element, and/or the L-PSA sends the statistical information of the user volume to the SMF network element.
  • the SMF network element receives user statistics information from the PSA and/or L-PSA.
  • the PSA sends the user volume statistical information to the SMF network element.
  • the L-PSA sends the user amount statistical information to the SMF network element.
  • the user volume statistics information finally received by the SMF network element may include user volume statistics information of the first service flow and/or user volume statistics information of the second service flow, and user volume of the first service flow.
  • the statistical information indicates the number of users of the first service flow before the local service chain is controlled, or indicates the number of users of the first service flow before the local service chain is controlled, and the user statistics of the second service flow indicates the number of users of the first service flow before the local service chain is controlled. Second, the number of users of the service stream, or indicating the number of users of the second service stream before the local service chain control.
  • the SMF network element may report the user volume statistical information to the charging CHF network element, so that the CHF network element can perform charging and other operations.
  • the L-PSA and/or PSA can realize the user volume statistics of the uplink or downlink service flow that needs to be controlled by the local service chain.
  • Another service flow user quantity statistics method provided by this embodiment of the present application can be applied to a scenario where a split point (ie, I-UPF) performs differentiated statistics on the user quantity.
  • the method includes:
  • step S901 is the same as step S701 in the embodiment shown in FIG.
  • step S902 is similar to step S702 in the embodiment shown in FIG. 7, except that:
  • the message b may also include the first measurement policy and the second measurement policy, and the first measurement policy is used to control the local service chain before Processes (or measures) the first business flow of, and the second measure strategy is used to process (or measure) the first business flow after the local business chain is controlled.
  • the message b may also include a third measurement strategy and a fourth measurement strategy, and the third measurement strategy is used to control the previous first measurement strategy for the local service chain.
  • the second service flow is processed (or measured), and the fourth measurement strategy is used to process (or measure) the second service flow after the local service chain is controlled.
  • the "metric strategy” may also be referred to as the "metric standard", and the two can be replaced with each other.
  • the first measurement strategy, the second measurement strategy, the third measurement strategy, or the fourth measurement strategy may also be determined by the SMF network element according to the local configuration strategy.
  • This application implements the method steps for obtaining the measurement strategy for the SMF network element.
  • the limitation is only an example, taking the PCF network element to determine and send to the SMF network element as an example for description.
  • any plurality of measurement strategies in the first measurement strategy, the second measurement strategy, the third measurement strategy, or the fourth measurement may be the same or different, which is not specifically limited in the embodiment of the present application.
  • the above measurement strategy can be defined by the charging key (charging key), charging method (charging method), monitoring key (monitoring key), and session-level monitoring exclusion indication (indication of exclusion from session level monitoring).
  • the charging key is used to determine the service flow rate.
  • the charging method is used to indicate the charging method of the service flow, which can be online charging, offline charging, etc.
  • the monitoring key is used to indicate whether multiple service streams share the number of users.
  • the session-level monitoring exclusion indication is used to indicate that the service flow should not be included in the user volume statistics.
  • the charging key may be used as the metric policy.
  • the first measurement strategy, the second measurement strategy, the third measurement strategy, and the fourth measurement strategy respectively correspond to the same or different charging keys.
  • the way in which the measurement strategy is represented by the charging method, monitoring key, and session-level monitoring exclusion indication can refer to the way represented by the charging key, which will not be repeated here.
  • S903 to S906 are the same as steps S703 to S706 in the embodiment shown in FIG.
  • step S907 is similar to step S707 in the embodiment shown in FIG. 7, except that:
  • the user quantity statistics rule carried in the N4 session establishment request includes the user quantity statistics rule of the first service flow and/or the user quantity statistics rule of the second service flow.
  • the user quantity statistics rule of the first service flow is used to indicate the Perform user statistics on the first service flow before control and the first service flow after the local service chain control.
  • the user statistics rule of the second service flow is used to indicate the second service flow and the local service chain before the local service chain is controlled. The second service flow after the control performs user statistics.
  • the user volume statistics rule may be one of the following:
  • Case 1 Perform user statistics on the first service flow from the RAN, that is, the first service flow carrying I-UPF tunnel info for RAN in the header;
  • the user volume statistics are performed.
  • Case 2 Perform user statistics on the second service flow from L-PSA, that is, the second service flow carrying I-UPF tunnel info for L-PSA in the header;
  • the user volume statistics are performed.
  • Case3 Perform user statistics on the first service flow from the RAN, that is, the first service flow carrying I-UPF tunnel info for RAN in the header;
  • the user volume statistics rules in the above various situations can be represented as Table 7.
  • UL refers to the uplink service flow
  • DL refers to the downlink service flow
  • UL:before refers to the uplink service flow before the local service chain control
  • UL:after refers to the uplink service flow after the local service chain control.
  • DL:before refers to the downlink service flow before the local service chain control
  • DL:after refers to the downlink service flow after the local service chain control
  • S908 to S913 are the same as steps S708 to S713 in the embodiment shown in FIG.
  • the I-UPF network element sends user statistics information to the SMF network element.
  • the SMF network element receives the user statistics information from the I-UPF network element.
  • the user amount statistics information may include the first user amount statistics information and the second user amount statistics information, and the first user amount statistics information It is used to indicate the user volume of the first service flow before the local service chain control, and the second user volume statistical information is used to indicate the user volume of the first service flow after the local service chain control.
  • the user amount statistics information may include the third user amount statistics information and the fourth user amount statistics information, and the third user amount statistics information is used to indicate the local The user volume of the second service flow before the service chain control, and the fourth user volume statistical information is used to indicate the user volume of the second service flow after the local service chain control.
  • the SMF network element may process the first user volume statistical information according to the first measurement strategy, and process the second user volume statistical information according to the second measurement strategy. information. After that, the SMF network element may send the processed first user volume statistical information and the second user volume statistical information to the CHF network element.
  • processing the first user volume statistical information according to the first measurement strategy as an example:
  • processing the first user volume statistical information according to the first measurement policy may be: multiplying the fee rate determined according to the first measurement policy by the first user volume statistical information. The number of users indicated.
  • processing the first user volume statistical information according to the first metric policy may be: processing the first user volume statistical information using an online charging method The number of users indicated.
  • processing the first user amount statistical information according to the first measurement strategy may be: discarding the first user amount statistical information, or for the first user amount statistical information indicated The number of users is multiplied by 0.
  • the SMF network element may process the third user volume statistical information according to the third measurement strategy, and process the fourth user volume statistical information according to the fourth measurement strategy ,
  • the processing method may refer to the method of processing the first user amount statistical information according to the first metric information.
  • the SMF network element may also send the processed third user volume statistical information and the fourth user volume statistical information to the CHF network element.
  • the CHF network element can perform charging and other operations based on the processed user volume statistical information. For example, the CHF network element generates a call ticket based on the processed user volume statistical information.
  • the measurement strategy to process the user volume it is possible to realize the differential processing of the service flow controlled by the local service chain, that is, to realize the differential charging and the differential statistics.
  • the third-party application provider charges.
  • the network can charge terminal users according to the number of users of the service flow before the local service chain control, and charge the third-party application provider according to the number of users of the service flow after the local service chain control.
  • Another service flow user quantity statistics method provided by this embodiment of the present application can be applied to a scenario where L-PSA and/or PSA performs differentiated user quantity statistics.
  • the method includes:
  • step S1002 is the same as step S902 in the embodiment shown in FIG. 9
  • S1001 and S1003 to S1008 are the same as S801 and S803 to S808 in the embodiment shown in FIG. 8.
  • the N4 session modification request may also include the first user volume statistics rule.
  • the first user volume statistics rule includes the user volume statistics rule of the first service flow, and/or the user volume statistics rule of the second service flow, and the user volume statistics rule of the first service flow is used to indicate the user volume statistics rule of the first service flow.
  • the first service flow after processing is subjected to user volume statistics, and the user volume statistics rule of the second service flow is used to instruct user volume statistics to be performed on the second service flow before the processing of the local service chain.
  • step S1010 is the same as the above step S809.
  • step S1011 is similar to the above step S811, the difference lies in:
  • the second user volume statistics rule included in the N4 session modification request includes the user volume statistics rule of the first service flow, and/or the user volume statistics rule of the second service flow.
  • the first user volume statistics rule includes the first service flow user volume statistics rule for indicating that the user volume statistics of the first service flow after the local service chain control is performed
  • the second user volume statistics rule includes The user quantity statistics rule of the first service flow is used to instruct the user quantity statistics of the first service flow before the local service chain control.
  • the second user volume statistics rule may include the user volume statistics rule of the second service flow, or may not include the user volume statistics rule of the second service flow. If the second user volume statistics rule includes the user volume statistics rule of the second service flow, in the case that the first user volume statistics rule does not include the user volume statistics rule of the second service flow, the second user volume statistics rule includes the second user volume statistics rule.
  • the user volume statistics rule of the service flow is used to indicate the user volume statistics of the second service flow before the local service chain control and the second service flow after the local service chain control; the first user volume statistics rule includes the second service flow In the case of the user volume statistics rule, the user volume statistics rule of the second service flow included in the second user volume statistics rule is used to instruct user volume statistics to be performed on the second service flow after the local service chain is controlled.
  • the first user volume statistics rule includes the second service flow user volume statistics rule for indicating that the second service flow before the local service chain control is used to perform user volume statistics
  • the second user volume statistics rule includes The user volume statistics rule of the second service flow is used to instruct to perform user volume statistics on the second service flow after the local service chain is controlled.
  • the second user volume statistics rule may include the user volume statistics rule of the first service flow, or may not include the user volume statistics rule of the first service flow. If the second user volume statistics rule includes the user volume statistics rule of the first service flow, and in the case that the first user volume statistics rule does not include the user volume statistics rule of the first service flow, the second user volume statistics rule includes the first user volume statistics rule.
  • the user volume statistics rule of the service flow is used to indicate the user volume statistics of the first service flow before the local service chain control and the first service flow after the local service chain control; the first user volume statistics rule includes the first service flow
  • the user volume statistics rule of the first service flow included in the second user volume statistics rule is used to instruct user volume statistics to be performed on the first service flow before the local service chain control.
  • the user volume statistics rule of the first service flow included in the second user volume statistics rule is used to indicate the first service flow before processing the local service chain and After the local service chain is controlled, the first service flow performs user volume statistics, and the second user volume statistics rule includes the user volume statistics rule of the second service flow for indicating the second service flow and the local service chain before processing the local service chain The second service flow after the control performs user statistics.
  • the foregoing second user volume statistics rule may be represented as one item in Table 8.
  • UL refers to the uplink service flow
  • DL refers to the downlink service flow
  • UL:before refers to the uplink service flow before the local service chain control
  • UL:after refers to the uplink service flow after the local service chain control
  • DL:before refers to the local service chain control
  • the previous downlink service flow, DL:after refers to the downlink service flow after the local service chain control.
  • the first user volume statistics rule and the second user volume statistics rule do not have the same rules, or that L-PSA and PSA do not perform repeated user volume statistics.
  • PSA counts local users. The number of users of the first service flow after the service chain control, L-PSA no longer counts the number of users of the first service flow after the local service chain control.
  • a statistical method for the uplink service flow, a statistical method is: L-PSA performs user statistics on the uplink service flow from I-UPF, and L-PSA calculates the uplink service from the local DN. Flow for user statistics. Another statistical method is that the L-PSA performs user statistics on the uplink service flows from I-UPF, and the PSA performs user statistics on the uplink service flows from I-UPF or L-PSA.
  • L-PSA performs user statistics on the downlink service flow from I-UPF or PSA, and L-PSA performs user statistics on the downlink service flow from the local DN.
  • Another statistical method is: the PSA performs statistics on the downlink service flow from the central DN, and the L-PSA performs user statistics on the downlink service flow from the local DN.
  • S1012 is the same as S812 in the embodiment shown in FIG. 8.
  • the L-PSA counts the user volume of the service flow according to the second user volume statistical rule. Alternatively, L-PSA performs user volume statistics according to the second user volume statistics rule, and PSA performs user volume statistics according to the first user volume statistics rule.
  • this step S1013 is: L-PSA counts the user volume of the service flow according to the second user volume statistics rule.
  • this step S1013 is: L-PSA performs user volume statistics according to the second user volume statistics rule, and PSA performs user volume statistics according to the first user volume statistics rule .
  • L-PSA counts the number of users of the first service flow before the local service chain control
  • PSA counts the number of users of the first service flow after the local service chain control
  • the PSA counts the number of users of the second service flow before the local service chain control
  • the L-PSA counts the number of users of the second service flow after the local service chain control.
  • the L-PSA sends user statistics information to the SMF network element.
  • the SMF network element receives the user statistics information from the L-PSA.
  • L-PSA and PSA send user statistics information to the SMF network element.
  • the SMF network element receives user statistics information from L-PSA and PSA.
  • the user volume statistical information finally received by the SMF network element may include the first user volume statistical information and the second user volume statistical information, and/or the third user volume statistical information and the fourth user volume
  • the meaning of the four types of user volume statistical information and the processing of the SMF network element on it please refer to the relevant description in the above step S914, which will not be repeated here.
  • L-PSA, or L-PSA and PSA can perform differentiated statistics on the number of users of uplink or downlink service flows that need to be controlled by the local service chain, so as to improve the accuracy of user statistics of this type of service flow.
  • the network can charge end users according to the number of users of the service flow before the local service chain control, and users of the service flow after the local service chain control The amount is charged to third-party application providers.
  • the embodiment of the present application also provides a method for user volume statistics applicable to the service flow of the 5G network as shown in FIG. 4c.
  • the UCLC/BP in FIG. (Hereinafter referred to as PSA for short), the first UPF is L-PSA as an example, the method for counting the number of users of the service flow provided in the embodiment of the present application will be described. As shown in Figure 11, the method includes:
  • the terminal establishes a PDU session.
  • the user plane transmission path corresponding to the session is: terminal ⁇ - ⁇ RAN ⁇ - ⁇ PSA ⁇ - ⁇ center DN, that is, the SMF network element has obtained RAN tunnel information (RAN tunnel info) and PSA tunnel information (PSA tunnel info)
  • RAN tunnel info RAN tunnel info
  • PSA tunnel info PSA tunnel info
  • the first SMF network element decides to insert I-UPF and L-PSA for the session.
  • the I-UPF acts as a shunt point, which can send part of the terminal's service flow to the L-PSA and the other part to the PSA.
  • the I-UPF acts as a shunt point, which can send part of the terminal's service flow to the L-PSA and the other part to the PSA.
  • the first SMF network element selects L-PSA.
  • the first SMF network element sends an N4 session establishment request to the L-PSA.
  • L-PSA receives the N4 session establishment request.
  • the L-PSA sends an N4 session establishment response to the first SMF network element.
  • the first SMF network element receives the N4 session establishment response.
  • the N4 session establishment response carries L-PSA tunnel info.
  • the first SMF network element sends an N4 session establishment request to the I-UPF network element.
  • the I-UPF network element receives the N4 session establishment request.
  • the N4 session establishment request carries RAN tunnel info, PSA tunnel info, and L-PSA tunnel info.
  • the I-UPF network element returns an N4 session establishment response to the first SMF network element.
  • the first SMF network element receives the N4 session establishment response.
  • the N4 session establishment response carries I-UPF tunnel info, which may specifically include I-UPF tunnel info for RAN, I-UPF tunnel info for PSA, and I-UPF tunnel info for L-PSA.
  • the first SMF network element sends a session update request to the second SMF network element.
  • the second SMF network element receives the session update request from the first SMF network element.
  • the session update request includes I-UPF tunnel info for PSA. It may also include a shunt point insertion indication to indicate that the second SMF network element has inserted a shunt point for the session by the first SMF network element.
  • the second SMF network element sends a session update response to the first SMF network element.
  • the first SMF network element receives the session update response from the second SMF network element.
  • the second SMF network element sends an I-UPF tunnel info for PSA to the PSA.
  • the PSA receives the I-UPF tunnel info for PSA from the second SMF network element.
  • the second SMF network element sends a session update request to the first SMF network element.
  • the first SMF network element receives the session update request from the second SMF network element.
  • the session update request includes N4 information.
  • the N4 information includes service flow description information of one or more service flows and corresponding service chain information, and is used to indicate that the one or more service flows are controlled by the local service chain indicated by the corresponding service chain information.
  • the first SMF network element sends I-UPF tunnel info for L-PSA to L-PSA.
  • L-PSA receives I-UPF tunnel info for L-PSA from the first SMF network element.
  • the first SMF network element sends the N4 rule to the I-UPF.
  • the I-UPF network element receives the N4 rule from the first SMF network element.
  • the N4 rule includes service flow description information of one or more service flows in step S1111 and corresponding service chain information.
  • the first SMF network element sends a user volume statistics rule to the L-PSA.
  • the L-PSA receives the user quantity statistics rule from the first SMF network element.
  • the user quantity statistics rule includes the user quantity statistics rule of some or all of the one or more service flows in step S1111.
  • the user volume statistics rule may include the user volume statistics rule of service flow 1, which is used to indicate that the L-PSA counts the user volume of service flow 1.
  • the user amount statistics rule of the service flow can refer to the user amount statistics rule sent by the SMF network element to the L-PSA in the foregoing embodiment, which will not be repeated here.
  • the first SMF network element sends a session update response to the second SMF network element.
  • the second SMF network element receives the session update response from the first SMF network element.
  • step S1114 if the user amount statistics rule in step S1114 includes the user amount statistics rule of some of the above one or more service flows:
  • the session update response may include service flow description information and first indication information of the service flow for which user volume statistics are performed by L-PSA, which is used to indicate to the second SMF network element that the L-PSA is responsible for the service flow.
  • the service flow described by the description information is used for user statistics.
  • the second SMF network element may perform special processing on the user amount statistical information, for example, discard the user amount statistical information.
  • the policy information of the PCF network element indicates that the number of users of the service flow that needs to be processed by the local service chain is counted by L-PSA, that is, the one or more services are counted by L-PSA
  • the second SMF network element may determine, according to the policy information of the PCF network element, that the PSA does not need to perform user statistics on the one or more service flows, so as to send the service flow description information and the service flow description information of the one or more service flows to the PSA.
  • the third indication information instructs the PSA to stop counting the number of users of the one or more service flows.
  • the second SMF network element may perform special processing on the user volume statistical information, for example, discard the user volume statistical information.
  • the operator’s policy stipulates that the user volume statistics before the local service chain control is performed for the uplink service flow, or the user volume statistics after the local service chain control is performed for the downlink service flow.
  • PSA counts the number of users of the upstream service flow, it counts the number of users after the local service chain is controlled, and the PSA counts the number of users of the downstream service flow, which counts the number of users before the local service chain is controlled. Therefore, the first The SMF network element needs to instruct the PSA to stop counting the user volume of the uplink and/or downlink service flow, or perform special processing, such as discarding, on the user volume of the uplink and/or downlink service flow reported by the PSA.
  • the user quantity statistics rule in step S1114 is used to indicate the statistics of the user quantity of the service flow before the local service chain control, and/or the user quantity of the service flow after the local service chain control Make statistics.
  • each network element in the steps shown in FIG. 6 to FIG. 11 can be executed by the processor 501 in the communication device 50 shown in FIG. 5 calling the application program code stored in the memory 503. This does not make any restrictions.
  • each network element may perform some or all of the steps in the embodiments of the present application. These steps are only examples, and the embodiments of the present application may also perform other steps or variations of various steps. In addition, the various steps can be executed in a different order presented in the embodiments of the present application, and it is possible that not all the steps in the embodiments of the present application are to be performed.
  • the above-mentioned session management network element or user-plane 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 as going beyond the scope of this application.
  • the embodiments of the present application can divide the session management network element or the user plane network element into functional modules according to the foregoing method examples.
  • each functional module can be divided corresponding to each function, or two or more functions can be integrated into one.
  • Processing module 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. 12 shows a schematic structural diagram of a session management network element 120.
  • the session management network element 120 includes a processing module 1201 and a transceiver module 1202.
  • the processing module 1201 is used to control and manage the actions of the session management network element.
  • the processing module 1201 is used to support the session management network element to perform the process S601 in FIG. 6, the processes S703 and S704 in FIG. 7, and/or Other processes used in the techniques described herein.
  • the transceiver module 1202 is used to support communication between the session management network element and other network entities, for example, the communication with the user plane network element shown in FIG. 6.
  • the session management network element 120 may further include a storage module 1203 (not shown in FIG. 12) for storing program codes and data of the session management network element 120. Specifically, you can refer to the following description:
  • the processing module 1201 is configured to determine user volume statistics rules, the user volume statistics rules including the user volume statistics rules of the first service flow and/or the user volume statistics rules of the second service flow, and the first service flow is required to pass through the local service chain
  • the second service flow is a downstream service flow that needs to be controlled by the local service chain.
  • the user quantity statistics rule of the first service flow is used to instruct the user quantity statistics of the first service flow before the local service chain control, and/or the user quantity statistics of the first service flow after the local service chain control;
  • the user quantity statistics rule of the second service flow is used to instruct the user quantity statistics of the second service flow before the local service chain control, and/or the user quantity statistics of the second service flow after the local service chain control.
  • the transceiver module 1202 is configured to send the user volume statistics rule to the user plane network element.
  • the processing module 1201 is further configured to obtain the first measurement strategy and the second measurement strategy.
  • the transceiver module 1202 is further configured to receive first user volume statistical information and second user volume statistical information.
  • the first user volume statistical information is used to indicate the user volume of the first service flow before the local service chain control
  • the second user volume statistical information The information is used to indicate the number of users of the first service flow after the local service chain control.
  • the processing module 1201 is further configured to process the first user volume statistical information according to the first measurement strategy, and process the second user volume statistical information according to the second measurement strategy.
  • the processing module 1201 is further configured to obtain the third measurement strategy and the fourth measurement strategy.
  • the transceiver module 1202 is further configured to receive third user volume statistical information and fourth user volume statistical information.
  • the third user volume statistical information is used to indicate the user volume of the second service flow before the local service chain control, and the fourth user volume The statistical information is used to indicate the number of users of the second service flow after the local service chain control.
  • the processing module 1201 is further configured to process the third user volume statistical information according to the third measurement strategy, and process the fourth user volume statistical information according to the fourth measurement strategy.
  • the transceiver module 1202 is further configured to receive the first indication information from the policy control function network element.
  • the processing module 1201 is used to determine user volume statistics rules, and may include: a processing module 1201, used to determine the first service when the first indication information is used to indicate that the size of the first service flow after the local service chain control does not change
  • the flow user volume statistics rule is used to instruct user volume statistics to be performed on the first service flow before the local service chain control, or to perform user volume statistics on the first service flow after the local service chain control.
  • the processing module 1201 is configured to determine that the user volume statistics rule of the first service flow is used to indicate the control of the local service chain when the first indication information is used to indicate that the size of the first service flow after the local service chain control changes. Perform user volume statistics for the previous first service flow, and perform user volume statistics for the first service flow after the local service chain control.
  • the transceiver module 1202 is further configured to receive second indication information from the policy control function network element.
  • the processing module 1201 is configured to determine the user volume statistics rule, and may include: the processing module 1201, configured to determine the second service when the second indication information is used to indicate that the size of the second service flow after the local service chain control does not change
  • the flow user volume statistics rule is used to instruct user volume statistics to be performed on the second service flow before the local service chain control, or to perform user volume statistics on the second service flow after the local service chain control.
  • the processing module 1201 is configured to determine that the user volume statistics rule of the second service flow is used to indicate the control of the local service chain when the second indication information is used to indicate that the size of the second service flow after the local service chain control changes. Perform user volume statistics for the previous second service flow, and perform user volume statistics for the second service flow after the local service chain control.
  • the session management network element 120 is presented in the form of dividing various functional modules in an integrated manner.
  • the "module” here may refer to a specific ASIC, a circuit, a processor and memory that executes one or more software or firmware programs, an integrated logic circuit, and/or other devices that can provide the above-mentioned functions.
  • the session management network element 120 may adopt the form shown in FIG. 5.
  • the processor 501 in FIG. 5 may invoke the computer-executable instructions stored in the memory 503, so that the session management network element 120 executes the method for counting the number of users of the service flow in the foregoing method embodiment.
  • the functions/implementation process of the processing module 1201 and the transceiver module 1202 in FIG. 12 may be implemented by the processor 501 in FIG. 5 calling a computer execution instruction stored in the memory 503.
  • the function/implementation process of the processing module 1201 in FIG. 12 may be implemented by the processor 501 in FIG. 5 calling computer execution instructions stored in the memory 503, and the function/implementation process of the transceiver module 1202 in FIG.
  • the communication interface 504 in 5 is implemented.
  • the session management network element 120 provided in this embodiment can perform the above-mentioned method for counting the number of users of a service flow, the technical effects that can be obtained can refer to the above-mentioned method embodiment, which will not be repeated here.
  • an embodiment of the present application further provides a device (for example, the device may be a chip system), the device includes a processor, and is configured to support the session management network element to implement the user volume statistics method for the foregoing service flow.
  • the device also includes a memory.
  • the memory is used to store program instructions and data necessary for the session management network element. Of course, the memory may not be in the device.
  • the device also includes an interface circuit, the interface circuit is a code/data read and write interface circuit, the interface circuit is used to receive computer execution instructions (computer execution instructions are stored in the memory, and may be directly from the memory Read, or possibly through other devices) and transfer to the processor.
  • the device is a chip system, it may be composed of a chip, or may include a chip and other discrete devices, which is not specifically limited in the embodiment of the present application.
  • Fig. 13 shows a schematic structural diagram of a user plane network element 130.
  • the user plane network element 130 includes a processing module 1301 and a transceiver module 1302.
  • the processing module 1301 is used to control and manage the actions of the user plane network element.
  • the processing module 1301 is used to support the user plane network element to perform the process S603 in FIG. 6 and/or other technologies used in the technology described herein. process.
  • the transceiver module 1302 is used to support communication between user plane network elements and other network entities, for example, communication with the session management network element shown in FIG. 6.
  • the user plane network element 130 may further include a storage module 1303 (not shown in FIG. 13) for storing program codes and data of the user plane network element 130. Specifically, you can refer to the following description:
  • the transceiver module 1302 is configured to receive user volume statistics rules from the session management network element, the user volume statistics rules including the user volume statistics rules of the first service flow and/or the user volume statistics rules of the second service flow, and the first service flow It is an uplink service flow that needs to be controlled by the local service chain, and the second service flow is a downlink service flow that needs to be controlled by the local service chain.
  • the user quantity statistics rule of the first service flow is used to instruct the user quantity statistics of the first service flow before the local service chain control, and/or the user quantity statistics of the first service flow after the local service chain control;
  • the user quantity statistics rule of the second service flow is used to instruct the user quantity statistics of the second service flow before the local service chain control, and/or the user quantity statistics of the second service flow after the local service chain control.
  • the processing module 1301 is configured to count the user amount of the first service flow according to the user amount statistics rule of the first service flow when the user amount statistics rule includes the user amount statistics rule of the first service flow; or, the processing module 1301, It is used to count the user amount of the second service flow according to the user amount statistics rule of the second service flow when the user amount statistics rule includes the user amount statistics rule of the second service flow.
  • the transceiver module 1302 is further configured to send the first user volume statistical information and/or the second user volume statistical information to the session management network element, where the first user volume statistical information is used to indicate the first user volume before the local service chain control.
  • the user volume of the service flow, and the second user volume statistical information is used to indicate the user volume of the first service flow after the local service chain control.
  • the transceiver module 1302 is further configured to send third user volume statistical information and/or fourth user volume statistical information to the session management network element, and the third user volume statistical information is used to indicate the second user volume before the local service chain control.
  • the user volume of the service flow, and the fourth user volume statistical information is used to indicate the user volume of the second service flow after the local service chain control.
  • the user plane network element 130 is presented in the form of dividing various functional modules in an integrated manner.
  • the "module” here may refer to a specific ASIC, a circuit, a processor and memory that executes one or more software or firmware programs, an integrated logic circuit, and/or other devices that can provide the above-mentioned functions.
  • the user plane network element 130 may adopt the form shown in FIG. 5.
  • the processor 501 in FIG. 5 may invoke the computer-executable instructions stored in the memory 503, so that the user plane network element 130 executes the user volume statistics method of the service flow in the foregoing method embodiment.
  • the function/implementation process of the processing module 1301 and the transceiver module 1302 in FIG. 13 may be implemented by the processor 501 in FIG. 5 calling a computer execution instruction stored in the memory 503.
  • the function/implementation process of the processing module 1301 in FIG. 13 may be implemented by the processor 501 in FIG. 5 calling computer execution instructions stored in the memory 503, and the function/implementation process of the transceiver module 1302 in FIG.
  • the communication interface 504 in 5 is implemented.
  • the user plane network element 130 provided in this embodiment can perform the above-mentioned method for calculating the amount of users of a service flow, the technical effects that can be obtained can refer to the above-mentioned method embodiment, and will not be repeated here.
  • an embodiment of the present application further provides a device (for example, the device may be a chip system), the device includes a processor, and is configured to support the session management network element to implement the user volume statistics method for the foregoing service flow.
  • the device also includes a memory.
  • the memory is used to store program instructions and data necessary for the session management network element. Of course, the memory may not be in the device.
  • the device also includes an interface circuit, the interface circuit is a code/data read and write interface circuit, the interface circuit is used to receive computer execution instructions (computer execution instructions are stored in the memory, and may be directly from the memory Read, or possibly through other devices) and transfer to the processor.
  • the device is a chip system, it may be composed of a chip, or may include a chip and other discrete devices, which is not specifically limited in the embodiment of the present application.
  • the computer may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • a software program it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or include one or more data storage devices such as servers, data centers, etc. that can be integrated with the medium.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Landscapes

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

Abstract

本申请实施例提供一种业务流的用户量统计方法、装置及系统。该方法中，会话管理网元确定并向用户面网元发送用户量统计规则，用户面网元根据该用户量统计规则统计用户量。该用户量统计规则，可以指示对本地业务链控制之前的上行业务流和/或本地业务链控制之后的上行业务流进行用户量统计；或者还可以指示对本地业务链控制之前的下行业务流和/或本地业务链控制之后的下行业务流进行用户量统计。对本地业务链控制之前或之后的业务流的用户量进行统计，可以避免重复统计该业务流的用户量；对本地业务链控制之前和之后的业务流的用户量进行统计，可以实现该业务流的精确统计，进而可以基于该精确统计进行更合理地处理。

Description

业务流的用户量统计方法、装置及系统
本申请要求于2020年05月29日提交国家知识产权局、申请号为202010479207.7、申请名称为“业务流的用户量统计方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及业务流的用户量统计方法、装置及系统。
背景技术
移动通信系统中，可以通过在协议数据单元(protocol data unit，PDU)会话(session)的用户面路径上插入分流点，由该分流点将会话中的某些业务流分流到本地路由。该分流点可以是分支点(branching point，BP)或上行分类器(uplink classifier，ULCL)。
在该场景下，如图1所示，终端的一个PDU会话可以具有远端PDU会话锚点(PDU session anchor，PSA)和本地PDU会话锚点(local PDU session anchor，L-PSA)，远端PSA可以与中心DN(central DN)通信，L-PSA可以与本地DN(local DN)通信。
示例性的，如图1所示，对于上行业务流，分流点可以将上行业务流1分流至远端PSA，将上行业务流2分流至L-PSA；对于下行业务，分流点可以将来自远端PSA的下行业务流1和来自L-PSA的下行业务流2聚合到分流点与基站之间的隧道上发送至基站，再由基站发送至终端。
此外，为了给用户提供更好的增值服务，引入了本地业务链控制(traffic steering control)。本地业务链控制指的是，业务流由一系列有序的服务功能(service function，SF)网元作处理，这些SF网元位于本地DN中。
在实际应用中，通常存在业务流经过本地业务链控制后，需要将处理后的业务流发送至中心DN(上行业务流)或发送至终端(下行业务流)的场景。在该场景下，如何进行业务流的用户量统计是目前亟待解决的问题。
发明内容
本申请实施例提供一种业务流的用户量统计方法、装置及系统，可以实现对需经过本地业务链控制的业务流的用户量统计。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，提供了一种业务流的用户量统计方法。该方法包括：会话管理网元确定用户量统计规则，并向用户面网元发送该用户量统计规则。该用户量统计规则包括第一业务流的用户量统计规则和/或第二业务流的用户量统计规则，第一业务流为需经过本地业务链控制的上行业务流，该第二业务流为需经过本地业务链控制的下行业务流。第一业务流的用户量统计规则用于指示对本地业务链控制之前的该第一业务流进行用户量统计，和/或，对本地业务链控制之后的该第一业务流进行用户量统计；第二业务流的用户量统计规则用于指示对本地业务链控制之前的该第二业务流进行用户量统计，和/或，对本地业务链控制之后的该第二业务流进行用户量统计。
基于该方案，会话管理网元获取上行业务流和/或下行业务流的用户量统计规则，并将该用户量统计规则发送给用户面网元，这样用户面网元便可根据该用户量统计规则对上行或下行业务流进行用户量统计，实现对需经过本地业务链控制的业务流的用户量统计，提升该类业务流的用户量统计的精确度。
一种可能的设计中，该业务流的用户量统计方法还包括：会话管理网元获取第一度量策略和第二度量策略，以及会话管理网元接收第一用户量统计信息和第二用户量统计信息，第一用户量统计信息用于指示本地业务链控制之前的第一业务流的用户量，第二用户量统计信息用于指示本地业务链控制之后的第一业务流的用户量。会话管理网元根据该第一度量策略处理该第一用户量统计信息，以及根据该第二度量策略处理该第二用户量统计信息。
基于该方案，通过使用度量策略处理用户量的方式，可以实现对本地业务链控制之前的上行业务流的用户量和本地业务链控制之后的上行业务流的用户量进行差别处理，例如实现差别计费、差别统计等。示例性的，CHF网元可以根据处理后的用户量统计信息进行计费等操作，例如，CHF网元根据处理后的用户量统计信息生成话单。
一种可能的设计中，该业务流的用户量统计方法还包括：会话管理网元获取第三度量策略和第四度量策略，以及会话管理网元接收第三用户量统计信息和第四用户量统计信息，第三用户量统计信息用于指示本地业务链控制之前的该第二业务流的用户量，第四用户量统计信息用于指示本地业务链控制之后的该第二业务流的用户量。会话管理网元根据第三度量策略处理第三用户量统计信息，以及根据第四度量策略处理第四用户量统计信息。
基于该方案，通过使用度量策略处理用户量的方式，可以实现对本地业务链控制之前的下行业务流的用户量和本地业务链控制之后的下行业务流的用户量进行差别处理，例如实现差别计费、差别统计等。示例性的，CHF网元可以根据处理后的用户量统计信息进行计费等操作，例如，CHF网元根据处理后的用户量统计信息生成话单。
一种可能的设计中，在会话管理网元确定业务流的用户量统计规则之前，该业务流的用户量统计方法还包括：会话管理网元接收来自策略控制功能网元的第一指示信息，相应的，会话管理网元确定用户量统计规则，可以包括：第一指示信息用于指示本地业务链控制之后的第一业务流的大小不发生变化时，会话管理网元确定第一业务流的用户量统计规则用于指示对本地业务链控制之前的第一业务流进行用户量统计，或者，对本地业务链控制之后的第一业务流进行用户量统计。或者，第一指示信息用于指示本地业务链控制之后的第一业务流的大小发生变化时，会话管理网元确定第一业务流的用户量统计规则用于指示对本地业务链控制之前的第一业务流进行用户量统计，以及，对本地业务链控制之后的第一业务流进行用户量统计。
一种可能的设计中，在会话管理网元确定业务流的用户量统计规则之前，该业务流的用户量统计方法还包括：会话管理网元接收来自策略控制功能网元的第二指示信息，相应的，会话管理网元确定用户量统计规则，可以包括：第二指示信息用于指示本地业务链控制之后的第二业务流的大小不发生变化时，会话管理网元确定第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计，或者，对本地业务链控制之后的第二业务流进行用户量统计；或者，第二指示信息用于指示本地业务链控制之后的第二业务流的大小发生变化时，会话管理网元确定第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计，以及，对本地业务链控制之后的第二业务流进行用户量统计。
基于该方案，在本地业务链控制之后的业务流的大小不发生变化时，仅需对本地业务链控制之前或之后的业务流的用户量进行统计，从而可以避免重复统计该业务流的用户量。在本地业务链控制之后的业务流的大小发生变化时，对本地业务链控制之前和之后的该业务流的用户量进行统计，从而可以实现该业务流的精确统计，进而可以基于该精确统计进行更合理地处理，例如网络可以更合理地向终端用户和第三方应用提供商收 费，例如，网络可以按照本地业务链控制之前的该业务流的用户量对终端用户进行收费，而按照本地业务链控制之后的该业务流的用户量对第三方应用提供商收费。
第二方面，提供了一种业务流的用户量统计方法。该方法包括：用户面网元接收来自会话管理网元的用户量统计规则，该用户量统计规则包括第一业务流的用户量统计规则和/或第二业务流的用户量统计规则，第一业务流为需经过本地业务链控制的上行业务流，该第二业务流为需经过本地业务链控制的下行业务流。第一业务流的用户量统计规则用于指示对本地业务链控制之前的该第一业务流进行用户量统计，和/或，对本地业务链控制之后的该第一业务流进行用户量统计；第二业务流的用户量统计规则用于指示对本地业务链控制之前的该第二业务流进行用户量统计，和/或，对本地业务链控制之后的该第二业务流进行用户量统计。在用户量统计规则包括第一业务流的用户量统计规则的情况下，用户面网元根据第一业务流的用户量统计规则统计第一业务流的用户量；在该用户量统计规则包括第二业务流的用户量统计规则的情况下，用户面网元根据第二业务流的用户量统计规则统计第二业务流的用户量。
基于该方案，用户面网元接收来自会话管理网元的用户量统计规则，这样用户面网元便可根据该用户量统计规则对上行或下行业务流进行用户量统计，实现对需经过本地业务链控制的业务流的用户量统计，提升该类业务流的用户量统计的精确度。
在一种可能的设计中，在该用户量统计规则包括第一业务流的用户量统计规则的情况下，该业务流的用户量统计方法还包括：用户面网元向会话管理网元发送第一用户量统计信息和/或第二用户量统计信息，第一用户量统计信息用于指示本地业务链控制之前的第一业务流的用户量，第二用户量统计信息用于指示本地业务链控制之后的第一业务流的用户量。
在一种可能的设计中，在该用户量统计规则包括第一业务流的用户量统计规则的情况下，该业务流的用户量统计方法还包括：用户面网元向会话管理网元发送第三用户量统计信息和/或第四用户量统计信息，第三用户量统计信息用于指示本地业务链控制之前的第二业务流的用户量，第四用户量统计信息用于指示本地业务链控制之后的第二业务流的用户量。
结合上述第一方面和第二方面，在一种可能的设计中，该用户面网元可以作为分流点。也就是说，用户量统计点可以位于分流点。
结合上述第一方面和第二方面，在一种可能的设计中，第一业务流的用户量统计规则用于指示对本地业务链控制之前的第一业务流进行用户量统计，包括：第一业务流的用户量统计规则用于指示用户面网元对来自接入网设备的第一业务流进行用户量统计。或者，第一业务流的用户量统计规则用于指示对本地业务链控制之后的第一业务流进行用户量统计，包括：第一业务流的用户量统计规则用于指示用户面网元对来自本地锚点的第一业务流进行用户量统计。可以理解的，对于分流点来说，来自接入网设备的上行业务流为本地业务链控制之前的上行业务流，来自本地锚点的上行业务流为本地业务链控制之后的上行业务流。
结合上述第一方面和第二方面，在一种可能的设计中，第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计，包括：第二业务流的用户量统计规则用于指示用户面网元对来自远端锚点的第二业务流进行用户量统计，或者，第二业务流的用户量统计规则用于指示对本地业务链控制之后的第二业务流进行用户量统计，包括：第二业务流的用户量统计规则用于指示用户面网元对来自本地锚点的第二业务流进行用户量统计。可以理解的，对于分流点来说，来自远端锚点的下行业务流为本地业务链控制之前的下行业务流，来自本地锚点的下行业务流为本地业务链控制之后的下行业务流。
结合上述第一方面和第二方面，在一种可能的设计中，上述用户面网元可以作为远端锚 点。也就是说，用户量统计点可以位于远端锚点。
结合上述第一方面和第二方面，在一种可能的设计中，第一业务流的用户量统计规则用于指示对本地业务链控制之后的第一业务流进行用户量统计，包括：第一业务流的用户量统计规则用于指示用户面网元对第一业务流进行用户量统计。可以理解的，对于远端锚点来说，若上行业务流需经过本地业务链控制，其收到的上行业务流必然为本地业务链控制之后的上行业务流。
结合上述第一方面和第二方面，在一种可能的设计中，第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计，包括：第二业务流的用户量统计规则用于指示用户面网元对第二业务流进行用户量统计。可以理解的，对于远端锚点来说，若下行业务流需经过本地业务链控制，其收到的下行业务流必然为本地业务链控制之前的下行业务流。
结合上述第一方面和第二方面，在一种可能的设计中，上述用户面网元可以作为本地锚点。也就是说，用户量统计点可以位于本地锚点。
结合上述第一方面和第二方面，在一种可能的设计中，第一业务流的用户量统计规则用于指示对本地业务链控制之前的第一业务流进行用户量统计，包括：第一业务流的用户量统计规则用于指示用户面网元对来自分流点的第一业务流进行用户量统计。或者，第一业务流的用户量统计规则用于指示对本地业务链控制之后的第一业务流进行用户量统计，包括：第一业务流的用户量统计规则用于指示用户面网元对来自本地数据网络的第一业务流进行用户量统计。可以理解的，对于本地锚点来说，来自分流点的上行业务流为本地业务链控制之前的上行业务流，来自本地数据网络的上行业务流为本地业务链控制之后的上行业务流。
结合上述第一方面和第二方面，在一种可能的设计中，第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计，包括：第二业务流的用户量统计规则用于指示用户面网元对来自分流点或远端锚点的第二业务流进行用户量统计。或者，第二业务流的用户量统计规则用于指示对本地业务链控制之后的第二业务流进行用户量统计，包括：第二业务流的用户量统计规则用于指示用户面网元对来自本地数据网络的第二业务流进行用户量统计。可以理解的，对于本地锚点来说，来自分流点或远端锚点的下行业务流为本地业务链控制之前的下行业务流，来自本地数据网络的下行业务流为本地业务链控制之后的下行业务流。
第三方面，提供了一种会话管理网元，该会话管理网元具有实现上述第一方面所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第四方面，提供了一种会话管理网元，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该会话管理网元运行时，该处理器执行该存储器存储的该计算机执行指令，以使该会话管理网元执行如上述第一方面中任一项所述的业务流的用户量统计方法。
第五方面，提供了一种会话管理网元，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述第一方面中任一项所述的业务流的用户量统计方法。
第六方面，提供一种会话管理网元，包括：处理器和接口电路，该接口电路可以为代码/数据读写接口电路，该接口电路用于接收计算机执行指令(计算机执行指令存储在存储器中，可能直接从存储器读取，或可能经过其他器件)并传输至该处理器；该处理 器用于运行所述计算机执行指令以执行上述第一方面中任一项所述的业务流的用户量统计方法。
第七方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第一方面中任一项所述的业务流的用户量统计方法。
第八方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面中任一项所述的业务流的用户量统计方法。
第九方面，提供了一种装置(例如，该装置可以是芯片系统)，该装置包括处理器，用于支持会话管理网元实现上述第一方面中所涉及的功能。在一种可能的设计中，该装置还包括存储器，该存储器，用于保存会话管理网元必要的程序指令和数据。该装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第三方面至第九方面中任一种设计方式所带来的技术效果可参见第一方面中不同设计方式所带来的技术效果，此处不再赘述。
第十方面，提供了一种用户面网元，该用户面网元具有实现上述第二方面所述的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十一方面，提供了一种用户面网元，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该用户面网元运行时，该处理器执行该存储器存储的该计算机执行指令，以使该用户面网元执行如上述第二方面中任一项所述的业务流的用户量统计方法。
第十二方面，提供了一种用户面网元，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述第二方面中任一项所述的业务流的用户量统计方法。
第十三方面，提供一种用户面网元，包括：处理器和接口电路，该接口电路可以为代码/数据读写接口电路，该接口电路用于接收计算机执行指令(计算机执行指令存储在存储器中，可能直接从存储器读取，或可能经过其他器件)并传输至该处理器；该处理器用于运行所述计算机执行指令以执行上述第二方面中任一项所述的业务流的用户量统计方法。
第十四方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第二方面中任一项所述的业务流的用户量统计方法。
第十五方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第二方面中任一项所述的业务流的用户量统计方法。
第十六方面，提供了一种装置(例如，该装置可以是芯片系统)，该装置包括处理器，用于支持用户面网元实现上述第二方面中所涉及的功能。在一种可能的设计中，该装置还包括存储器，该存储器，用于保存用户面网元必要的程序指令和数据。该装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第十方面至第十六方面中任一种设计方式所带来的技术效果可参见第二方面中不同设计方式所带来的技术效果，此处不再赘述。
第十七方面，提供了一种通信系统，该通信系统包括会话管理网元和用户面网元。该会话管理网元用于执行上述第一方面中，或者本申请实施例提供的方案中由会话管理网元执行的步骤；该用户面网元用于执行上述第二方面中，或者本申请实施例提供的方 案中由用户面网元执行的步骤。
在一种可能的设计中，该通信系统还可以包括本申请实施例提供的方案中与会话管理网元、或用户面网元进行交互的其他设备，例如策略控制控制功能网元和接入网设备等，本申请实施例对此不作具体限定。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为现有的一种业务流分流的场景示意图；
图2为本申请实施例提供的一种通信系统的结构示意图；
图3为本申请实施例提供的另一种通信系统的结构示意图；
图4a为本申请实施例提供的通信系统在5G网络中的一种应用示意图；
图4b为本申请实施例提供的通信系统在5G网络中的另一种应用示意图；
图4c为本申请实施例提供的通信系统在5G网络中的又一种应用示意图；
图5为本申请实施例提供的一种通信设备的硬件结构示意图；
图6为本申请实施例提供的一种业务流的用户量统计方法的流程示意图；
图7～图11为本申请实施例提供的一种业务流的用户量统计方法的具体流程示意图；
图12为本申请实施例提供的会话管理网元的结构示意图；
图13为本申请实施例提供的用户面网元的结构示意图。
具体实施方式
本申请中“的(英文：of)”，相应的“(英文corresponding，relevant)”和“对应的(英文：corresponding)”有时可以混用，应当指出的是，在不强调其区别时，其所要表达的含义是一致的。
为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
需要说明的是，本申请中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。
本申请实施例描述的系统架构以及业务场景是为了更加清楚的说明本申请实施例的 技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。本申请实施例中以提供的方法应用于新无线(new radio，NR)系统或第五代(5th generation，5G)网络中为例进行说明。
为了方便理解本申请实施例的技术方案，首先给出本申请相关技术的简要介绍如下。
第一、上行业务流、下行业务流：
本申请实施例中，将来自终端或接入网设备，且目的地址为中心DN的业务流，称为上行业务流。需要说明的是，目的地址为中心DN指的是目的地址为中心DN中的应用服务器的地址，该应用服务器与该业务流对应，为终端提供相应的应用业务。将来自中心DN，且目的地址为终端的业务流称为下行业务流。
第二、业务链、业务链控制：
业务链：指一系列有序的服务功能(service function，SF)网元。SF网元例如可以是具有视频压缩功能的网元、具有防火墙功能的网元、具有视频加速功能的网元、具有深度报文检测(deep packet inspection，DPI)功能的网元等。
业务链控制：指业务流由业务链进行处理，或者说，指业务流由一系列有序的SF网元进行处理。该处理例如可以是对业务流先进行视频压缩、再经过深度报文检测、然后经过防火墙等增强处理，本申请不限定SF网元处理业务流的方式。
本地业务链控制：指业务流由一系列有序的位于本地DN的SF网元进行处理。
需要说明的是，本申请实施例中的业务链控制也可以称为业务链处理，二者可以相互替换。
图2示出了本申请实施例提供的一种业务流的用户量统计方法适用的通信系统，该通信系统包括：会话管理网元10和用户面网元20。
其中，会话管理网元10和用户面网元20之间可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不做具体限定。本申请实施例中：
会话管理网元10，用于确定用户量统计规则，该用户量统计规则包括第一业务流的用户量统计规则和/或第二业务流的用户量统计规则，第一业务流为需经过本地业务链控制的上行业务流，第二业务流为需经过本地业务链控制的下行业务流，第一业务流的用户量统计规则用于指示对本地业务链控制之前的第一业务流进行用户量统计，和/或，对本地业务链控制之后的第一业务流进行用户量统计，第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计，和/或，对本地业务链控制之后的第二业务流进行用户量统计。
会话管理网元10，还用于向用户面网元20发送该用户量统计规则。
用户面网元20，用于接收来自会话管理网元10的用户量统计规则，并根据该用户量统计规则包括的第一业务流的用户量统计规则统计第一业务流的用户量，根据第二业务流的用户量统计规则统计第二业务流的用户量。
本申请实施例提供的通信系统中，会话管理网元获取上行业务流和/或下行业务流的用户量统计规则，并将该用户量统计规则发送给用户面网元，这样用户面网元便可根据该用户量统计规则对上向或下行业务流进行用户量统计，实现对需经过本地业务链控制的业务流的用户量统计。
如图3所示，为本申请实施例提供的另一种通信系统的结构示意图，该通信系统包括会话管理网元10、分流点201、远端锚点202、本地锚点203。可选的，该通信系统还可以包括 接入网设备30、与远端锚点202通信的中心DN、以及与本地锚点203通信的本地DN。
其中，在该场景下，上述图2中的用户面网元20可以作为图3中的分流点201，或者作为图3中的远端锚点202，或者作为图3中的本地锚点203，或者可以包括图3中的远端锚点202和本地锚点203。
其中，本申请实施例中分流点可以将业务流分流到本地路由，或者将业务流分流到远端路由。
所谓的本地路由指分流点201将业务流分流至本地锚点203，由本地锚点203将业务流传输至与本地锚点203通信的本地DN。
所谓的远端路由指分流点201将业务流分流至远端锚点202，由远端锚点202将业务流传输至与远端锚点202通信的中心DN。
为了实现上述业务流的分流，会话管理网元10可以在会话的用户面路径上插入分流点201作为分流点实现。也即分流点201可以为具有对会话的业务流进行分流功能的网元。
可选的，本申请实施例中的本地DN也可以替换为本地数据中心(data center，DC)或本地移动边缘计算(mobile edge computing，MEC)平台。
其中，本地DN包括一个或多个SF网元(例如，SF1和SF2)。一个或多个SF网元可以是运营商部署的功能网元，也可以是第三方部署的功能网元。SF网元可以对业务流处理，例如做增强处理或者过滤处理。例如：SF网元可以是具有防火墙功能的网元、具有视频加速处理功能的网元、或者具有负载均衡功能的网元等。中心DN包括应用服务器(application server，AS)，以及一个或多个SF网元(比如，SF3和SF4)。不同的SF具有的功能可以相同，也可以不相同，本申请实施例对此不作限定。
本申请实施例中，需经过本地业务链控制的上行业务流在图3所示的通信系统中的处理流程可以描述为：分流点201接收来自接入网设备30的上行业务流后，将该上行业务流发送至本地锚点203，由本地锚点203将该上行业务流发送至本地DN进行本地业务链控制，并将本地业务链控制之后的该上行业务流发送至中心DN。
可选的，本地业务链控制之后的该上行业务可以通过两条不同的路径传输至中心DN。其中一条路径为“本地DN→本地锚点203→分流点201→远端锚点202→中心DN”，下述实施例中将其称为路径1；另一条路径为“本地DN→本地锚点203→远端锚点202→中心DN”，下述实施例中将其称为路径2。
本申请实施例中，需经过本地业务链控制的下行业务流在图3所示的通信系统中的处理流程可以描述为：远端锚点202接收来自中心DN的下行业务流后，将该下行业务流传输至本地锚点203，由本地锚点203将其发送至本地DN进行本地业务链控制。本地DN对该下行业务流进行本地业务链控制之后，将本地业务链控制之后的该下行业务流发送至本地锚点203，再由本地锚点203通过分流点201和接入网设备30发送至终端。
可选的，远端锚点202可以通过两条路径将来自中心DN的下行业务流传输至本地锚点203。其中一条路径为“远端锚点202→分流点201→本地锚点203”，下述实施例中将其称为路径3；另一条路径为“远端锚点202→本地锚点203”，下述实施例中将其称为路径4。
示例性的，如图3所示，以上行业务流在本地DN中的本地业务链控制经过SF1和SF2为例，本地业务链控制的过程可以描述为：本地锚点203将上行业务流发送至SF1，SF1处理完之后再发回本地锚点203，本地锚点203再将由SF1处理后的上行业务流发送 至SF2，SF2处理之后再发送至本地锚点203；或者SF1处理完之后再发送至SF2，SF2对上行业务流处理之后再发回本地锚点203，由本地锚点203通过上述路径1将本地业务链控制之后的上行业务流发送至中心DN。当然，本地锚点203也可以通过上述路径2将本地业务链控制之后的上行业务流发送至中心DN(图3中未示出)。
可选的，下行业务流的本地业务链控制与上行业务流的本地业务链控制过程类似，可参考上述相关描述，在此不再赘述。
可选的，在本地DN进行业务链控制时，会在业务流的报文头中添加业务链协议头，本地锚点203收到本地业务链控制后的业务流后，可以识别该业务链协议头，将其删除后发送至分流点201或远端锚点202。
示例性的，若上述通信系统应用于5G网络，则如图4a或图4b或图4c所示，分流点201所对应的网元或者实体可以为上行分类器(uplink classifier，ULCL)或分支点
(branching Point，BP)，ULCL/BP可以通过用户面功能(user plan function，UPF)网元实现，实现ULCL/BP的UPF网元可以称为I-UPF网元。会话管理网元10对应的网元或者实体可以为会话功能管理(session management function，SMF)网元。本地锚点203所对应的网元或者实体可以为第一用户面功能(user plan function，UPF)网元，也可以称为本地PDU会话锚点(Local PDU session anchor，L-PSA)。远端锚点202所对应的网元或者实体可以为第二用户面功能(user plan function，UPF)网元，也可以称为远端PDU会话锚点(remote PDU session anchor，其可以简称为PSA)。接入网设备30可以为接入网络(access network，AN)设备或者无线接入网络(radio access network，RAN)设备，本申请实施例中以接入网设备30为RAN设备为例进行说明。
此外，5G网络架构还可以包括：移动管理网元、AF网元、策略控制功能(policy control function，PCF)网元、统一数据管理(Unified Data Management，UDM)网元、DN、认证服务器功能网元、统一数据库(Unified Data Management，UDM)网元等，本申请实施例对此不作具体限定。
下面对上述网络架构中涉及的各个部分或网元在5G网络中的功能示例性的分别进行说明。
(1)、终端(terminal)可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备；还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication，MTC)终端、用户设备(user equipment，UE)，移动台(mobile station，MS)，终端设备(terminal device)或者中继用户设备等。其中，中继用户设备例如可以是5G家庭网关(residential gateway，RG)。为方便描述，本申请中，上面提到的设备统称为终端。
应理解，本申请实施例中的终端可以为物联网终端设备、港口、智能工厂、铁路交通、物流、无人机、无人驾驶汽车等多种垂直行业应用领域中的终端。例如：移动机器人(Mobile Robot)、自动导引车(Automated Guided Vehicle，AGV)，无人驾驶汽车，列车上的控制设备和传感器、工厂中部署的控制设备和传感器(Sensor)等。
作为示例，在本申请实施例中，该终端还可以是可穿戴设备。可穿戴设备也可以称 为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。该终端还可以为应用于工厂的传感器设备。
(2)、接入网设备用于为特定区域的授权终端提供入网功能，并能够根据终端的级别，业务的需求等使用不同质量的传输隧道。接入网设备能够管理无线资源，为终端设备提供接入服务，进而完成控制信号和终端数据在终端和核心网之间的转发，接入网设备也可以理解为传统网络中的基站。例如，可以负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。
接入网设备可以是无线网络中的设备。接入网设备也可以称为无线接入网设备或者网络设备。目前，一些接入网设备的举例为：5G系统中的下一代节点B(The Next Generation Node B，gNB)、传输接收点(transmission reception point，TRP)、长期演进(long term evolution，LTE)系统中的演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)，或无线保真(wireless fidelity，Wifi)接入点(access point，AP)等。在一种网络结构中，网络设备可以包括集中单元(centralized unit，CU)节点、或分布单元(distributed unit，DU)节点、或包括CU节点和DU节点的RAN设备。接入设备还可以是无线回传设备，车载设备，可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等。在第三代(3rd generation，3G)系统中，称为节点B(Node B)等。
(3)、移动管理网元，属于核心网网元，主要负责信令处理部分，例如：接入控制、移动性管理、附着与去附着以及网关选择等功能。移动管理网元为终端的会话提供服务的情况下，会为该会话提供控制面的存储资源，以存储会话标识、与会话标识关联的SMF网元标识等。
在5G通信系统中，该移动管理网元可以是接入和移动性管理功能(access and mobility management function，AMF)网元。在未来通信系统中，移动管理网元仍可以是AMF网元，或者，还可以有其它的名称，本申请不做限定。
(4)、会话管理网元，负责用户面网元选择，用户面网元重定向，因特网协议(internet protocol，IP)地址分配，承载的建立、修改和释放以及QoS控制。会话管理、终端的IP地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
在5G通信系统中，该会话管理网元可以是SMF网元。在未来通信系统中，会话管理网元仍可以是SMF网元，或者，还可以有其它的名称，本申请不做限定。
(5)、用户面网元，负责终端中用户数据(例如，业务流)的转发和接收。可以从数据网络接收用户数据，通过接入设备传输给终端；用户面网元还可以通过接入网设备从终端接收用户数据，转发到数据网络。用户面网元中为终端提供服务的传输资源和调度功能由会话管理网元管理控制的。
在5G通信系统中，该用户面网元可以是UPF网元或UPF模块。在未来通信系统中，用户面网元仍可以是UPF网元或UPF模块，或者，还可以有其它的名称，本申请不做限定。
(6)、认证服务器功能网元，主要提供认证功能，支持第三代合作伙伴计划(3rd generation partnership project，3GPP)接入和Non-3GPP接入的认证，具体可参考3GPP TS 33.501。
在未来通信系统中，认证服务器功能网元可以是认证服务器功能(authentication server function，AUSF)网元，或者，还可以有其它的名称，本申请不做限定。
(7)、UDR网元，主要负责存储结构化数据，存储的内容包括签约数据和策略数据、对外暴露的结构化数据和应用相关的数据。
(8)、AF网元，主要支持与3GPP核心网交互来提供服务，例如影响数据路由决策，策略控制功能或者向网络侧提供第三方的一些服务。
(9)、数据网络，指的是为终端提供数据传输服务的运营商网络，如IMS(IP Multi-media Service，IP多媒体业务)、Internet等。
终端通过建立终端到RAN到UPF到DN之间的PDD会话，来访问数据网络。
图4a或图4b中示例性的以该网络架构还包括终端、AMF网元、AF网元、PCF网元、UDM网元、中心DN、本地DN为例进行说明等。
其中，如图4a所示，终端通过下一代网络(Next generation，N1)接口(简称N1)与AMF网元通信。接入网设备通过N2接口(简称N2)与AMF网元通信。接入网设备通过N3接口(简称N3)与ULCL/BP通信。ULCL/BP通过N9接口与第二UPF网元和第一UPF网元通信。第一UPF网元通过N6接口(简称N6)与本地DN通信。第二UPF网元通过N6接口(简称N6)与中心DN通信，任意两个UPF网元之间通过N9接口(简称N9)通信。ULCL/BP通过N4接口(简称N4)与SMF网元通信。AMF网元通过N11接口(简称N11)与SMF网元通信。AMF网元通过N8接口(简称N8)与UDM网元通信。SMF网元通过N7接口(简称N7)与PCF网元通信。SMF网元通过N10接口(简称N10)与UDM网元通信。AUSF网元通过N13接口(简称N13)与UDM网元通信。UDM网元与UDR网元通信。PCF网元与UDR网元通信。ULCL/BP可以通过UPF来实现。
如图4b示出了5G网络架构中基于服务化接口的架构，该架构与图4a的区别在于，在图4b中5G核心网中的控制面网元也可以采用服务化接口进行交互。例如，AMF网元、AUSF网元、SMF网元、UDM网元、UDR网元或者PCF网元采用服务化接口进行交互。比如，AMF网元对外提供的服务化接口可以为Namf。SMF网元对外提供的服务化接口可以为Nsmf。UDM网元对外提供的服务化接口可以为Nudm。UDR网元对外提供的服务化接口可以为Nudr。PCF网元对外提供的服务化接口可以为Npcf。应理解，图4b中各种服务化接口的名称的相关描述可以参考23501标准中的5G系统架构(5G system architecture)图，在此不予赘述。
如图4c所示，为上述通信系统应用于5G网络的另一种架构示意图。该架构与图4a的区别在于，ULCL/BP以及第一UPF网元与第一SMF网元通信，或者说由第一SMF网元管理；第二UPF网元与第二SMF网元通信，或者说由第二SMF网元管理。第一SMF网元和第二SMF网元之间可以相互通信。
需要说明的是，图4a或图4b或图4c中的各个网元之间的接口名字只是一个示例， 具体实现中接口名字可能为其他名字，本申请实施例对此不作具体限定。
需要说明的是，图4a或图4b或图4c的RAN设备、AF网元、AMF网元、SMF网元、UDM网元、UPF网元和PCF网元等仅是一个名字，名字对设备本身不构成限定。在5G网络以及未来其它的网络中，RAN设备设备、AF网元、AMF网元、SMF网元、UDM网元、UPF网元和PCF网元所对应的网元也可以是其他的名字，本申请实施例对此不作具体限定。例如，该UDM网元还有可能被替换为用户归属服务器(home subscriber server，HSS)或者用户签约数据库(user subscription database，USD)或者数据库实体，等等，在此进行统一说明，后续不再赘述。
图4a或图4b或图4c中的终端、RAN、UPF和DN一般被称为用户层网络功能实体，终端的数据流量可以通过终端和DN之间建立的PDU会话(Session)进行传输，传输会经过RAN和UPF这两个网络功能(实体)；而其他的部分则被称为控制层网络功能和实体，主要负责认证和鉴权、注册管理、会话管理、移动性管理以及策略控制等功能，从而实现用户层流量可靠稳定的传输。本申请实施例中涉及到的PDU会话指在终端与数据网络之间提供PDU连接服务的一种连接(association between the UE and a Data Network that provides a PDU connectivity service)。
可选的，本申请实施例中会话管理网元10、分流点201、远端锚点202、本地锚点203也可以称之为通信装置，其可以是一个通用设备或者是一个专用设备，本申请实施例对此不作具体限定。
可选的，本申请实施例中，会话管理网元10、分流点201、远端锚点202、本地锚点203可以通过图5中的通信设备(或通信装置)50来实现。
图5所示为本申请实施例提供的通信设备50的结构示意图。该通信设备50包括一个或多个处理器501，以及至少一个通信接口(图5中仅是示例性的以包括通信接口504，以及一个处理器501为例进行说明)，可选的还可以包括存储器503；可选的还可以包括通信总线502。
可选的，处理器501、通信接口504、或者存储器503可以是耦合在一起的(图5中未示出)，或者，如图5所示，也可以是通过通信总线502连接在一起的。
处理器501可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信总线502可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。该总线可以分为地址总线、数据总线、控制总线等。为便于表示，图5中仅用一条粗虚线表示，但并不表示仅有一根总线或一种类型的总线。该通信总线502可以用于连接通信设备50中的不同组件，使得不同组件可以通信。
通信接口504，可以是收发模块用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。例如，所述收发模块可以是收发器、收发机一类的装置。可选的，所述通信接口504也可以是位于处理器501内的收发电路，用以实现处理器的信号输入和信号输出。
存储器503可以是具有存储功能的装置。例如可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电 可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路502与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器503用于存储执行本申请方案的计算机指令，并由处理器501来控制执行。处理器501用于执行存储器503中存储的计算机指令，从而实现本申请实施例中提供的方法。
或者，可选的，本申请实施例中，也可以是处理器501执行本申请下述实施例提供的方法中的处理相关的功能，通信接口504负责与其他设备或通信网络通信，本申请实施例对此不作具体限定。
可选的，本申请实施例中的计算机指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器501可以包括一个或多个CPU，例如图5中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信设备50可以包括多个处理器，例如图5中的处理器501和处理器508。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
可以理解的是，图5所示的结构并不构成对通信装置的具体限定。比如，在本申请另一些实施例中，通信装置可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
下面将结合图1至图5对本申请实施例提供的业务流的用户量统计方法进行具体阐述。
需要说明的是，本申请实施例并不限定于图4a至图4c所示的5G网络架构，还可以应用于未来其它的通信系统，例如6G网络架构等。并且，本申请实施例所使用的各个网元的名称，在未来通信系统中，可能保持功能相同，但名称会改变。
需要说明的是，本申请下述实施例中消息(或信息)的名字以及消息(或信息)中参数的名字等只是一个示例，具体实现中也可以是其他的名字，本申请实施例对此不作具体限定。
结合图3所示的网络架构，如图6所示，为本申请实施例提供的一种业务流的用户量统计方法，该业务流的用户量统计方法包括如下步骤：
S601、会话管理网元确定用户量统计规则。
其中，该用户量统计规则包括第一业务流的用户量统计规则和/或第二业务流的用户量统计规则，第一业务流为需经过本地业务链控制的上行业务流，第二业务流为需经过本地业务链控制的下行业务流。
其中，第一业务流的用户量统计规则用于指示对本地业务链控制之前的第一业务流进行用户量统计，和/或，对本地业务链控制之后的第一业务流进行用户量统计。第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计， 和/或，对本地业务链控制中的第二业务流进行用户量统计。
可以理解的是，本申请实施例中的用户量统计规则是针对终端的某个会话中的业务流而言的，在此统一说明，下述实施例不再赘述。可选的，本申请实施例中，业务流的用户量统计可以理解为基于流量和/或时长进行的用户量统计。当然也可以有其他形式的用户量统计，例如基于业务类型进行的用户量统计，对于具体的统计形式，本发明不做限定。
示例性的，基于流量进行的用户量统计指的是统计传输业务流所使用的流量，或占用的带宽资源，其单位一般为兆比特(MB)、千比特(KB)等。例如，每次传输业务流时可以统计本次传输该业务流所使用的流量，周期性地计算本周期内多次传输该业务流所使用的流量总和，将该流量总和作为本周期内该业务流的用户量。
示例性的，基于时长进行的用户量统计指的是统计传输业务流的时长，其单位一般为分钟、小时等。例如，初始传输业务流时统计起始时刻，后续传输该业务流时判断本次传输该业务流与上次传输该业务流之间的时间间隔是否大于或等于预设阈值，若是，认为将上次传输该业务流的时间作为结束时刻，传输该业务流的时长即为起始时刻和结束时刻之间的时长；若否，认为该业务流的传输未中断，下次传输该业务流时继续进行判断。
可选的，本申请实施例中，对本地业务链控制之前的业务流进行用户量统计，或者，对本地业务链控制之后的业务流进行用户量统计，可以称为简单统计；对本地业务链控制之前的业务流进行用户量统计，以及，对本地业务链控制之后的业务流进行用户量统计，可以称为区分统计。也就是说，上述第一业务流的用户量统计规则也可以理解为用于指示对第一业务流进行简单统计，或者用于指示对第一业务流进行区分统计；第二业务流的用户量统计规则可以理解为用于指示对第二业务流进行简单统计，或者用于指示对第二业务流进行区分统计。
本申请实施例的一种实施场景下，会话管理网元可以根据来自策略控制功能网元的策略控制规则，确定该用户量统计规则。示例性的，在会话管理网元确定用户量统计规则之前，本申请实施例提供的方法还包括：策略控制功能网元向会话管理网元发送第一策略控制规则和/或第二策略控制规则，相应的，会话管理网元接收来自策略控制功能网元的第一策略控制规则和/或第二策略控制规则。
对于第一策略控制规则：
可选的，第一策略控制规则包括第一业务流的描述信息和第一指示信息，该第一业务流的描述信息用于标识或确定第一业务流，第一指示信息用于指示本地业务链控制之后的第一业务流的大小是否发生变化。
可选的，业务流的大小可以指业务流的流量大小。例如，在本地业务链控制后业务流的大小发生变化的场景下：本地业务链控制之前，业务流的大小为10MB；本地业务链控制之后，业务流的大小变为5MB。
示例性的，业务流的描述信息可以包括：五元组信息(例如，IP五元组)、三元组信息(例如，IP三元组)、隧道信息、应用标识、数据网络名称(data network name，DNN)、或单网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)中的一个或多个。其中，IP五元组例如可以包括源IP地址，源端口号，目的IP地址，目的端口号，传输层协议。
可以理解的，业务流经过业务链处理之后，其大小通常会发生变化，例如，视频业 务流由业务链进行视频渲染后，该视频业务流的大小可能变大；或者，视频业务流由业务链进行视频压缩后，该视频业务流的大小可能变小。
该场景下，会话管理网元确定用户量统计规则，可以包括：在第一指示信息用于指示本地业务链控制之后的第一业务流的大小不发生变化时，会话管理网元确定第一业务流的用户量统计规则用于指示对本地业务链控制之前的第一业务流进行用户量统计，或者，用于指示对本地业务链控制之后的第一业务流进行用户量统计。在第一指示信息用于指示本地业务链控制之后的第一业务流的大小发生变化时，会话管理网元确定第一业务流的用户量统计规则用于指示对本地业务链控制之前的第一业务流进行用户量统计，以及对本地业务链控制之后的第一业务流进行用户量统计。
也就是说，在本地业务链控制之后的第一业务流的大小不发生变化时，仅需对本地业务链控制之前或之后的第一业务流的用户量进行统计，从而可以避免重复统计第一业务流的用户量。在本地业务链控制之后的第一业务流的大小发生变化时，对本地业务链控制之前和之后的第一业务流的用户量进行统计，从而可以实现第一业务流的精确统计，进而可以基于该精确统计进行更合理地处理，例如网络可以更合理地向终端用户和第三方应用提供商收费，例如，网络可以按照本地业务链控制之前的第一业务流的用户量对终端用户进行收费，而按照本地业务链控制之后的第一业务流的用户量对第三方应用提供商收费。
对于第二策略控制规则：
可选的，第二策略控制规则包括第二业务流的描述信息和第二指示信息，该第二业务流的描述信息用于标识或确定第二业务流，第二指示信息用于指示本地业务链控制之后的第二业务流的大小是否发生变化。
该场景下，会话管理网元确定用户量统计规则，可以包括：在第二指示信息用于指示本地业务链控制之后的第二业务流的大小不发生变化时，会话管理网元确定第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计，或者，用于指示对本地业务链控制之后的第二业务流进行用户量统计。在第二指示信息用于指示本地业务链控制之后的第二业务流的大小发生变化时，会话管理网元确定第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计，以及对本地业务链控制之后的第二业务流进行用户量统计。关于第二策略控制规则的其他相关描述可参考上述对第一策略控制规则的说明，在此不再赘述。
可以理解的，第二业务流和第一业务流可以是相同业务的下行业务流和上行业务流，也可以是不同业务的下行业务流和上行业务流。
可选的，在第二业务流和第一业务流为相同业务的下行业务流和上行业务流，业务流的描述信息为五元组时，第二业务流和第一业务流的描述信息不同。例如，假设第一业务流的描述信息包括IP五元组1，对应源IP地址＝IP1，源端口号＝port1，目的IP地址＝IP2，目的端口号＝port2，传输层协议＝UDP，则第二业务流的描述信息可以包括IP五元组2，对应源IP地址＝IP2，源端口号＝port2，目的IP地址＝IP1，目的端口号＝port1，传输层协议＝UDP。
S602、会话管理网元向用户面网元发送用户量统计规则。相应的，用户面网元接收来自会话管理网元的用户量统计规则。
可以理解的，在步骤S602中，可以认为用户面网元从会话管理网元处获取了用户量统计规则。
当然，用户面网元还可以通过其他方法获取该用户量统计规则，例如用户面网元自行确定或生成该用户量统计规则，本申请实施例对此不做具体限定。本申请下述实施例中以用户面网元从会话管理网元处获取用户量统计规则为例进行说明。
S603、用户面网元根据用户量统计规则进行用户量统计。
其中，该用户量统计规则包括第一业务流的用户量统计规则时，用户面网元根据第一业务流的用户量统计规则统计第一业务流的用户量；该用户量统计规则包括第二业务流的用户量统计规则时，用户面网元根据第二业务流的用户量统计规则统计第二业务流的用户量。
本申请实施例提供的业务流的用户量统计方法中，会话管理网元获取上行业务流和/或下行业务流的用户量统计规则，并将该用户量统计规则发送给用户面网元，这样用户面网元便可根据该用户量统计规则对上行或下行业务流进行用户量统计，实现对需经过本地业务链控制的业务流的用户量统计，提升该类业务流的用户量统计的精确度。
在本申请实施例的不同实施场景下，上述用户面网元在本申请实施例提供的通信系统(例如图3所示的通信系统)中可以实现不同的功能，相应的，上述用户量统计规则也可能随之不同。
第一种实施场景下，用户面网元可以作为分流点，此时，用户面网元可以称为分流点，二者可以相互替换。
在该场景下，对于第一业务流的用户量统计规则：
第一业务流的用户量统计规则用于指示对本地业务链控制之前的第一业务流进行用户量统计，可以包括：第一业务流的用户量统计规则用于指示用户面网元对来自接入网设备的第一业务流进行用户量统计。或者，第一业务流的用户量统计规则用于指示对本地业务链控制之后的第一业务流进行用户量统计，可以包括：第一业务流的用户量统计规则用于指示用户面网元对来自本地锚点的第一业务流进行用户量统计。
进一步的，第一业务流的用户量统计规则用于指示对本地业务链控制之后的第一业务流进行用户量统计，可以包括：在本地业务链控制之后的第一业务流经过分流点传输至中心DN的情况下，第一业务流的用户量统计规则用于指示用户面网元对来自本地锚点的第一业务流进行用户量统计。
示例性的，如图3所示，对于上行业务流，从接入网设备30传输至分流点201后，由分流点201发送至本地锚点203进行本地业务链控制，本地业务链控制之后的上行业务流经“本地DN→本地锚点203→分流点201→远端锚点202→中心DN”(称为路径1)传输至中心DN，或者经“本地DN→本地锚点203→远端锚点202→中心DN”(称为路径2)传输至中心DN，因此，对于分流点201来说，来自于接入网设备30的上行业务流为本地业务链控制之前的上行业务流；在本地业务链控制之后的上行业务流通过路径1传输的情况下，对于分流点201来说，来自本地锚点203的上行业务流为本地业务链控制之后的上行业务流。
在该场景下，对于第二业务流的用户量统计规则：
第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计，可以包括：第二业务流的用户量统计规则用于指示用户面网元对来自远端锚点的第二业务流进行用户量统计。或者，第二业务流的用户量统计规则用于指示对本地业务链控制之后的第二业务流进行用户量统计可以包括：第二业务流的用户量统计规则用于指示用户面网元对来自本地锚点的第二业务流进行用户量统计。
进一步的，第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计，可以包括：在本地业务链控制之前的第二业务流经过分流点传输至本地锚点的情况下，第二业务流的用户量统计规则用于指示用户面网元对来自远端锚点的第二业务流进行用户量统计。
示例性的，如图3所示，对于下行业务流，从中心DN传输至远端锚点202后，由远端锚点202发送至本地锚点203进行本地业务链控制，可以理解的，下行业务流可以经过“远端锚点202→分流点201→本地锚点203”(称为路径3)或“远端锚点202→本地锚点203”(称为路径4)到达本地锚点203。本地业务链控制之后的下行业务流经过分流点201传输至接入网设备30，由接入网设备30发送至终端。因此，对于分流点201来说，来自本地锚点203的下行业务流为本地业务链控制之后的下行业务流；在本地业务链控制之前的下行业务流通过路径3传输的情况下，对于分流点201来说，来自远端锚点202的下行业务流为本地业务链控制之后的下行业务流。
示例性的，以第一业务流用SDF(service data flow)1表示，第二业务流用SDF2表示为例，在该场景下，用户量统计规则可以为如下表1中的任意一项，例如，用户量统计规则可以为：对来自接入网设备的SDF1进行用户量统计；或者可以包括如下表1中任意多项的任意组合，例如，用户量统计规则可以为：对来自接入网设备的SDF1，以及来自本地锚点的SDF2进行用户量统计。
表1
Figure PCTCN2021095161-appb-000001
该场景下，步骤S603中，用户面网元收到业务流后，可以识别该业务流是否为用户量统计规则中所指示的业务流，若是，则统计该业务流的用户量。
可选的，以用户量统计规则包括第一业务流的用户量统计规则为例，用户面网元收到业务流后，可以先识别该业务流是否为第一业务流，若确定该业务流为第一业务流，再识别该第一业务流的来源是否与第一业务流的用户量统计规则指示的来源相同，若相同，则统计第一业务流的用户量。当然，用户面网元也可以先识别业务流的来源再识别业务流是否为第一业务流或第二业务流，本申请对此不做具体限定。
可选的，用户面网元可以根据第一业务流的描述信息识别该业务流是否为第一业务流。例如，以第一业务流的描述信息包括IP五元组1，对应源IP地址＝IP1，源端口号＝port1，目的IP地址＝IP2，目的端口号＝port2，传输层协议＝UDP为例，用户面网元接收到业务流后，可以将该业务流中的IP五元组与IP五元组1进行比较，若相同，可以确定该业务流为第一业务流。第二业务流的识别方式与第一业务流的识别方式类型，在此不再赘述。
可选的，用户面网元可以通过业务流的报文头中的隧道信息(tunnel information，以下简称为tunnel info)判断业务流的来源。换句话说，用户面网元可以通过业务流的报文头中的隧道信息判断业务流是否经过了本地业务链控制。也就是说，表1中“来自接入网设备的SDF1”可以描述为“没有经过本地业务链控制的SDF1”或“本地业务链控制 之前的SDF1”；“来自本地锚点的SDF1”可以描述为“经过了本地业务链控制的SDF1”或“本地业务链控制之后的SDF1”；“来自远端锚点的SDF2”可以描述为“没有经过本地业务链控制的SDF2”或“本地业务链控制之前的SDF2”；“来自本地锚点的SDF2”可以描述为“经过本地业务链控制的SDF2”或“本地业务链控制之后的SDF2”。
例如，若第一业务流的报文头中携带与接入网设备对应的分流点的隧道信息，即I-UPF tunnel info for RAN，用户面网元可以确定第一业务流来源于接入网设备，换句话说，用户面网元可以确定第一业务流没有经过本地业务链控制；若第一业务流的报文头中携带与本地锚点对应的分流点的隧道信息，即I-UPF tunnel info for L-PSA，用户面网元可以确定第一业务流来源于本地锚点，换句话说，用户面网元可以确定第一业务流经过了本地业务链控制。同理，若第二业务流的报文头中携带与远端锚点对应的分流点的隧道信息，即I-UPF tunnel info for PSA，用户面网元可以确定第二业务流来源于远端锚点，换句话说，用户面网元可以确定第二业务流没有经过本地业务链控制；若第二业务流的报文头中携带与本地锚点对应的分流点的隧道信息，即I-UPF tunnel info for L-PSA，用户面网元可以确定第二业务流来源于本地锚点，换句话说，用户面网元可以确定第二业务流经过了本地业务链控制。
或者，在用户面网元与本地锚点之间存在第一专用隧道，且该第一专用隧道用于传输本地业务链控制之后的上行业务流的情况下，若第一业务流的报文头中携带该第一专用隧道的隧道信息，用户面网元也可以确定第一业务流来源于本地锚点，即第一业务流经过了本地业务链控制。同理，在用户面网元与远端锚点之间存在第二专用隧道，且该第二专用隧道用于传输本地业务链控制之前的下行业务流的情况下，若第二业务流的报文头中携带该第二专用隧道的隧道信息，用户面网元也可以确定第二业务流来源于远端锚点，即第二业务流需要经过本地业务链控制。
可选的，用户面网元也可以通过业务流的报文中携带的标识信息来确定业务流是否经过了本地业务链控制。
例如，在用户面网元与本地锚点之间不存在第一专用隧道，即无论是本地业务链控制之前的第一业务流，还是本地业务链控制之后的第一业务流，都通过相同的隧道传输的情况下，本地业务链控制之后的第一业务流可以与第一标识关联，该第一标识用于表示该业务流经过了本地业务链控制。该情况下，用户面网元接收的第一业务流的报文中携带第一标识时，用户面网元可以确定该报文为经过本地业务链控制后的第一业务流的报文控制。同理，对于本地业务链控制之后的第二业务流可以与第二标识关联，该第二标识用于表示该业务流经过了本地业务链控制。该情况下，用户面网元接收的第二业务流的报文携带第二标识时，用户面网元可以确定该报文为经过本地业务链控制后的第二业务流的报文控制。
第二种实施场景下，用户面网元可以作为远端锚点，此时，用户面网元可以称为远端锚点，二者可以相互替换。
在该场景下，对于第一业务流的用户量统计规则：
第一业务流的用户量统计规则用于指示对本地业务链控制之后的第一业务流进行用户量统计。其可以包括：第一业务流的用户量统计规则用于指示用户面网元对第一业务流进行用户量统计，该第一业务流可以是来自分流点或本地锚点的。
可以理解的，在本地业务链控制之后的第一业务流经过分流点传输至中心DN的情况下，该第一业务流来自分流点。在本地业务链控制之后的第一业务流不经过分流点传 输至中心DN的情况下，该第一业务流来自本地锚点。
示例性的，如图3所示，对于远端锚点202来说，在本地业务链控制之后的上行业务流通过路径1传输的情况下，来自于分流点201的上行业务流为本地业务链控制之后的上行业务流；在本地业务链控制之后的上行业务流通过路径2传输的情况下，来自本地锚点203的上行业务流为本地业务链控制之后的上行业务流。
也就是说，对于远端锚点，其收到的第一业务流均为本地业务链处理之后的第一业务流。
在该场景下，对于第二业务流的用户量统计规则：
第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户面统计。其可以包括：第二业务流的用户量统计规则用于指示用户面网元对第二业务流进行用户量统计，该第二业务流是来自中心DN的。
示例性的，如图3所示，对于远端锚点202来说，来自中心DN的下行业务流为本地业务链控制之前的下行业务流。
也就是说，对于远端锚点，其收到的第二业务流均为本地业务链处理之前的第二业务流。
示例性的，以第一业务流用SDF1表示，第二业务流用SDF2表示为例，在该场景下，用户量统计规则可以为如下表2中的任意一项；或者可以包括如下表2中任意多项的任意组合。
表2
Figure PCTCN2021095161-appb-000002
也就是说，在用户面网元作为远端锚点的场景下，用户量统计规则不指示业务流的来源，对于远端锚点，在用户量统计规则包括第一业务流的用户量统计规则的情况下，其收到第一业务流即进行用户量统计，在用户量统计规则包括第二业务流的用户量统计规则的情况下，其收到第二业务流即进行用户量统计。
第三种实施场景下，用户面网元可以作为本地锚点，此时，用户面网元可以称为本地锚点，二者可以相互替换。
在该场景下，对于第一业务流的用户量统计规则：
第一业务流的用户量统计规则用于指示对本地业务链控制之前的第一业务流进行用户量统计，可以包括：第一业务流的用户量统计规则用于指示用户面网元对来自分流点的第一业务流进行用户量统计。或者，第一业务流的用户量统计规则用于指示对本地业务链控制之后的第一业务流进行用户量统计，可以包括：第一业务流的用户量统计规则用于指示用户面网元对来自本地数据网络的第一业务流进行用户量统计。
示例性的，如图3所示，对于本地锚点203来说，来自分流点201的上行业务流为本地业务链控制之前的上行业务流；来自本地DN的上行业务流为本地业务链控制之后的上行业务流。
在该场景下，对于第二业务流的用户量统计规则：
第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计，可以包括：第二业务流的用户量统计规则用于指示用户面网元对来自分流点 或远端锚点的第二业务流进行用户量统计。或者，第二业务流的用户量统计规则用于指示对本地业务链控制之后的第二业务流进行用户量统计，可以包括：第二业务流的用户量统计规则用于指示用户面网元对来自本地数据网络的第二业务流进行用户量统计。
进一步的，第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计，可以包括：在本地业务链控制之前的第二业务流经过分流点传输至本地锚点的情况下，第二业务流的用户量统计规则用于指示用户面网元对来自分流点的第二业务流进行用户量统计。在本地业务链控制之前的第二业务流不经过分流点传输至本地锚点的情况下，第二业务流的用户量统计规则用于指示用户面网元对来自远端锚点的第二业务流进行用户量统计。
示例性的，如图3所示，对于本地锚点203来说，在本地业务链控制之前的下行业务流通过路径3传输的情况下，来自分流点201的下行业务流为本地业务链控制之前的下行业务流；在本地业务链控制之前的下行业务流通过路径4传输的情况下，来自远端锚点202的下行业务流为本地业务链控制之前的下行业务流。
示例性的，以第一业务流用SDF1表示，第二业务流用SDF2表示为例，在该场景下，用户量统计规则可以为如下表3中的任意一项；或者可以包括如下表3中任意多项的任意组合。
表3
Figure PCTCN2021095161-appb-000003
该场景下，步骤S603中，用户面网元根据用户量统计规则进行用户量统计的方式可参考上述第一种实施场景中的相关描述。
可选的，该场景下，对于第一业务流，用户面网元在判断第一业务流的来源时，若第一业务流的报文头中包括本地锚点的隧道信息，即L-PSA tunnel info，用户面网元可以确定第一业务流来源于分流点；若第一业务流的报文中包括业务链协议头，用户面网元可以确定第一业务流是本地业务链处理后的，来源于本地数据网络的。
可选的，该场景下，对于第二业务流，用户面网元在判断第二业务流的来源时，若第二业务流的报文头中包括本地锚点的隧道信息，即L-PSA tunnel info，用户面网元可以确定第二业务流来源于分流点或远端锚点；若第二业务流的报文中包括业务链协议头，用户面网元可以确定第二业务流是本地业务链处理后的，来源于本地数据网络的。
可以理解的是，对于L-PSA来说，第二业务流不会同时来自分流点和远端锚点，在进行用户量统计时，L-PSA无需确定该第二业务流究竟是来自分流点还是来自远端锚点，在第二业务流的报文头中包括L-PSA tunnel info时，L-PSA即可确定该第二业务流为本地业务链控制之前的第二业务流。
第四种实施场景下，用户面网元可以包括远端锚点和本地锚点，即由远端锚点和本地锚点联合统计第一业务流或第二业务流的用户量。
可以理解的是，第一业务流和第二业务流的用户量统计可以为简单统计，也可以为区分统计。第一业务流和第二业务流的统计方式可以不同，例如第一业务流的统计方式 为简单统计，第二业务流的统计方式为区分统计；或者，第一业务流和第二业务流的统计方式可以相同，例如均为简单统计。也就是说，该实施场景可以理解为上述第二种和第三种实施场景的结合。
示例性的，以第一业务流和第二业务流的统计方式均为简单统计为例，可以由远端锚点统计本地业务链控制之后的第一业务流的用户量，由本地锚点统计本地业务链控制之后的第二业务流的用户量。
或者，示例性的，以第一业务流和第二业务流的统计方式均为区分统计为例，可以由远端锚点统计本地业务链控制之后的第一业务流的用户量，以及本地业务链控制之前的第二业务流的用户量，同时由本地锚点统计本地业务链控制之前的第一业务流的用户量，以及本地业务链控制之后的第二业务流的用户量。
可选的，远端锚点和本地锚点不进行重复的统计，例如，远端锚点统计了本地业务链控制之后的第一业务流的用户量，那么本地锚点不会统计本地业务链控制之后的第一业务流的用户量。
下面以图3所示的通信系统应用于如图4a或图4b所示的5G网络，图4a或图4b中的UCLC/BP为I-UPF，第二UPF为远端PSA(下文简称为PSA)、第一UPF为L-PSA为例，对本申请实施例提供的业务流的用户量统计方法进行说明。
如图7所示，为本申请实施例提供的一种业务流的用户量统计方法，该方法可以适用于由分流点(即I-UPF)进行用户量的简单统计的场景。该方法包括：
S701、AF网元向PCF网元发送消息a。相应的，PCF网元接收来自AF网元的消息a。
其中，该消息a中包括第一业务流的描述信息和/或第二业务流的描述信息。
可选的，在消息a包括第一业务流的描述信息的情况下，消息a还可以包括第一指示信息和/或第一业务链信息，第一指示信息用于指示本地业务链控制之后的第一业务流的大小是否发生变化，第一业务链信息用于指示第一业务链，第一业务链为第一业务流所要经过的业务链，或者说为处理第一业务流的业务链。第一业务链信息例如可以包括一下至少一项：一个或多个SF网元的标识、该一个或多个SF网元在第一业务链中的顺序、或者该一个或多个SF网元的位置信息，例如，指示SF网元位于中心DN或本地DN，本申请实施例以SF网元位于本地DN，即第一业务流需经过本地业务链处理为例进行说明。
可选的，在消息a包括第二业务流的描述信息的情况下，消息a还可以包括第二指示信息和/或第二业务链信息，第二指示信息用于指示本地业务链控制之后的第二业务流的大小是否发生变化，第二业务链信息用于指示第二业务链，第二业务链为第二业务流所要经过的业务链，或者说为处理第二业务流的业务链。第二业务链信息例如可以包括一下至少一项：一个或多个SF网元的标识、该一个或多个SF网元在第二业务链中的顺序、或者该一个或多个SF网元的位置信息，例如，指示SF网元位于中心DN或本地DN，本申请实施例以SF网元位于本地DN，即第二业务流需经过本地业务链处理为例进行说明。
可以理解的是，第一业务链和第二业务链可以相同，也可以不同，即第一业务流和第二业务流可以由相同的业务链处理也可以由不同的业务链处理，本申请实施例对此不做具体限定。
可选的，作为一种具体实现，该消息a可以为AF请求(request)。
S702、PCF网元向SMF网元发送消息b，该消息b中包括策略控制规则。相应的，SMF网元接收来自PCF网元的消息b。
可选的，PCF收到消息a后，可以根据消息a生成策略控制规则。
可选的，在消息a包括第一指示信息的情况下，该策略控制规则还可以包括第一策略控制规则，该第一策略规则包括第一业务流的描述信息和第一指示信息，第一策略控制规则还可以包括第一业务链信息。在消息a包括第二指示信息的情况下，该策略控制规则还可以包括第二策略控制规则，该第二策略控制包括第二业务流的描述信息和第二指示信息，第二策略控制规则还可以包括第二业务链信息。
可选的，该消息b，具体可以是Npcf_SMPolicyControl_UpdateNotify request，对应AF触发的策略修改过程；或者，可以是Npcf_SMPolicyControl_Update response，对应会话修改流程；或者，可以是Npcf_SMPolicyControl_Create response，对应会话建立流程。本申请实施例中以消息b对应会话修改流程为例进行说明，即在步骤S701之前，终端设备已经建立了会话，该会话对应的用户面传输路径为：终端<-→RAN<-→PSA<-→中心DN，即SMF网元已经获取到RAN的隧道信息(RAN tunnel info)和PSA的隧道信息(PSA tunnel info)。
S703、SMF网元决定为会话插入I-UPF和L-PSA。
其中，I-UPF充当分流点，可以将终端的部分业务流发送至L-PSA，另一部分发送至PSA。
可选的，SMF网元可以在检测到终端有新的业务流时决定为会话插入I-UPF和L-PSA；或者，可以在终端移动到本地DN所服务的区域时，决定为会话插入I-UPF和L-PSA。
需要说明的是，步骤S703与步骤S701～S702没有必然的执行顺序，可以先执行步骤S703，再执行步骤S701～S702；也可以先执行步骤S701～S702，再执行步骤S703；或者可以同时执行步骤S701～S702、以及S703。
S704、SMF网元选择L-PSA。
该步骤的具体实现可以参考现有技术，本申请实施例对此不作赘述。
S705、SMF网元向L-PSA发送N4会话建立请求。相应的，L-PSA接收N4会话建立请求。
其中，该N4会话建立请求中包括PSA tunnel info。
可以理解的是，通过步骤S705，L-PSA可以获取PSA tunnel info，即可以建立L-PSA→PSA之间的用户面连接，使得L-PSA能够向PSA发送业务流。
本申请实施例中，建立用户面连接，即将用户面连接上的两个端点(即网元)的隧道信息传达到对端。例如，A端点获取了B端点的隧道信息，则A端点至B端点的用户面连接建立成功；B端点获取了A端点的隧道信息，则B端点至A端点的用户面连接建立成功。
S706、L-PSA向SMF网元发送N4会话建立响应。相应的，SMF网元接收N4会话建立响应。
其中，N4会话建立响应中携带L-PSAtunnel info。
需要说明的是，L-PSA tunnel info也可以由SMF网元分配，本申请实施例仅以L-PSA分配L-PSA tunnel info为例进行说明。当由SMF网元分配L-PSA tunnel info时，SMF网元在N4会话建立请求中，将L-PSA tunnel info发送至L-PSA。同理，后续步骤中涉及tunnel info分配时，都是既可以由SMF网元分配，也可以由L-PSA、或I-UPF或PSA分配。
S707、SMF网元向I-UPF网元发送N4会话建立请求。相应的，I-UPF网元接收N4会话建立请求。
其中，N4会话建立请求携带RAN tunnel info、PSA tunnel info、L-PSA tunnel info、以及用户量统计规则。
其中，RAN tunnel info用于建立I-UPF网元到RAN之间的下行用户面连接，之后I-UPF网元向RAN发送的业务流的报文头中便可以携带RAN tunnel info。即，I-UPF收到要发往RAN的业务流时，可以将其发送至RAN。
PSA tunnel info用于建立I-UPF网元至PSA之间的上行用户面连接，之后I-UPF网元向PSA发送的业务流的报文头中便可以携带PSA tunnel info。即，I-UPF收到发往PSA的业务流时，可以将其发送至PSA了。
L-PSA tunnel info用于建立I-UPF网元至L-PSA之间的上行用户面连接，之后I-UPF网元向L-PSA发送的业务流的报文头中便可以携带L-PSA tunnel info。即，I-UPF收到发往L-PSA的业务流时，可以将其发送至L-PSA了。
用户量统计规则可以是SMF网元根据来自PCF的策略控制规则确定的，相关描述可参考上述步骤S601，在此不再赘述。
可选的，由于本实施例适用于由分流点(即I-UPF)进行用户量的简单统计的场景，该用户量统计规则可以包括第一业务流的用户量统计规则和/或第二业务流的用户量统计规则，第一业务流的用户量统计规则用于指示对本地业务链控制之前的第一业务流进行用户量统计，或者指示对本地业务链控制之后的第一业务流进行用户量统计，第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计，或者指示对本地业务链控制之后的第二业务流进行用户量统计。
也就是说，示例性的，用户量统计规则可以为以下一种：
Case1、对来自RAN的第一业务流，即报文头中携带I-UPF tunnel info for RAN的第一业务流，进行用户量统计；
以及对来自PSA的第二业务流，即报文头中携带I-UPF tunnel info for PSA的第二业务流，进行用户量统计。
Case2、对来自L-PSA的第一业务流，即报文头中携带I-UPF tunnel info for L-PSA的第一业务流，进行用户量统计；
以及对来自L-PSA的第二业务流，即报文头中携带I-UPF tunnel info for L-PSA的第二业务流，进行用户量统计。
Case3、对来自RAN的第一业务流，即报文头中携带I-UPF tunnel info forRAN的第一业务流，进行用户量统计；
以及对来自L-PSA的第二业务流，即报文头中携带I-UPF tunnel info for L-PSA的第二业务流，进行用户量统计。
Case4、对来自L-PSA的第一业务流，即报文头中携带I-UPF tunnel info forL-PSA的第一业务流，进行用户量统计；
以及对来自PSA的第二业务流，即报文头中携带I-UPF tunnel info for PSA的第二业务流，进行用户量统计。
Case5、对来自RAN的第一业务流，即报文头中携带I-UPF tunnel info for RAN的第一业务流，进行用户量统计。
Case6、对来自L-PSA的第一业务流，即报文头中携带I-UPF tunnel info forL-PSA的 第一业务流，进行用户量统计。
Case7、对来自PSA的第二业务流，即报文头中携带I-UPF tunnel info for PSA的第二业务流，进行用户量统计。
Case8、对来自L-PSA的第二业务流，即报文头中携带I-UPF tunnel info for L-PSA的第二业务流，进行用户量统计。
示例性的，以第一业务流由SDF1表示，第二业务流由SDF2表示，上述各种情况下的用户量统计规则可以表示为表4。其中，UL指上行业务流，DL指下行业务流，UL:before指本地业务链控制之前的上行业务流，UL:after指本地业务链控制之后的上行业务流，
DL:before指本地业务链控制之前的下行业务流，DL:after指本地业务链控制之后的下行业务流。
表4
Figure PCTCN2021095161-appb-000004
S708、I-UPF网元向SMF网元返回N4会话建立响应。相应的，SMF网元接收N4会话建立响应。
其中，N4会话建立响应中携带I-UPF tunnel info for RAN、I-UPF tunnel info for PSA，I-UPF tunnel info for L-PSA。
其中，I-UPF tunnel info for RAN为I-UPF分配的与RAN对应的隧道信息，用于建立RAN到I-UPF网元之间的上行用户面连接，当SMF网元将该信息发送到RAN后，即RAN获取到I-UPF tunnel info for RAN后，RAN到I-UPF网元之间的上行用户面连接建立成功。之后，RAN向I-UPF网元发送的业务流的报文头中便可以携带I-UPF tunnel information for RAN，也即I-UPF网元可以根据业务流的报文头中携带的I-UPF tunnel information for RAN，确定业务流来源于PSA。
其中，I-UPF tunnel infofor PSA为I-UPF分配的与PSA对应的隧道信息，用于建立PSA至I-UPF网元之间的下行用户面连接。当SMF网元将该信息发送到PSA后，即PSA获取到I-UPF tunnel infofor PSA后，PSA到I-UPF网元之间的下行用户面连接建立成功。 之后，PSA向I-UPF发送的业务流的报文头中便可以携带I-UPF tunnel info for PSA，也即I-UPF可以根据业务流的报文头中携带的I-UPF tunnel info for PSA，确定业务流来源于PSA。
其中，I-UPF tunnel infofor L-PSA为I-UPF分配的与L-PSA对应的隧道信息，用于建立L-PSA至I-UPF网元之间的上行用户面连接。当SMF网元将该信息发送至L-PSA后，即L-PSA获取到该I-UPF tunnel info for L-PSA后，L-PSA至I-UPF之间的下行用户面连接建立成功。之后，L-PSA向I-UPF发送的业务流的报文头中便可以携带I-UPF tunnel info for L-PSA，也即I-UPF可以根据业务流的报文头中携带的I-UPF tunnel info for L-PSA，确定业务流来源于L-PSA。
可选的，在I-UPF网元与PSA网元之间通过专用隧道传输经过本地业务链处理的上行业务流时，该N4会话建立响应中还可以包括specific I-UPF tunnel info for L-PSA，否则，可以不包括specific I-UPF tunnel info for L-PSA。
S709、SMF网元向PSA网元发送N4会话修改请求。相应的，PSA网元接收N4会话修改请求。
其中，该N4会话修改请求包括I-UPF tunnel info for PSA。
S710、PSA网元向SMF网元发送N4会话修改响应。相应的，SMF网元接收来自PSA网元的N4会话修改响应。
其中，N4会话修改响应用于表示已成功接收I-UPF tunnel info for PSA，或者N4会话修改响应中携带用于指示成功接收I-UPF tunnel info for PSA的响应指示信息。
S711、SMF网元向L-PSA网元发送N4会话修改请求。相应的，L-PSA网元接收N4会话修改请求。
其中，该N4会话修改请求包括I-UPF tunnel info for L-PSA，或者包括I-UPF tunnel info for L-PSA和specific I-UPF tunnel info for L-PSA。
S712、L-PSA网元向SMF网元发送N4会话修改响应。相应的，SMF网元接收来自L-PSA网元的N4会话修改响应。
其中，N4会话修改响应用于表示已成功接收I-UPF tunnel info for L-PSA或成功接收I-UPF tunnel info for L-PSA和specific I-UPF tunnel info for L-PSA；或者N4会话修改响应中携带用于指示成功接收I-UPF tunnel info for L-PSA的响应指示信息，或携带用于指示成功接收I-UPF tunnel info for L-PSA和specific I-UPF tunnel info for L-PSA的响应指示信息。
S713、I-UPF网元根据用户量统计规则统计业务流的用户量。
其中，该用户量统计规则为步骤S707中从SMF网元处接收的。
可选的，在用户量统计规则包括第一业务流的用户量统计规则的情况下，I-UPF网元根据第一业务流的用户量统计规则统计第一业务流的用户量；在用户量统计规则包括第二业务流的用户量统计规则的情况下，I-UPF网元根据第二业务流的用户量统计规则统计第二业务流的用户量，详细说明可参考上述图6所示的实施例中的相关描述。
S714、I-UPF网元向SMF网元发送用户量统计信息。相应的，SMF网元接收来自I-UPF网元的用户量统计信息。
可选的，在用户量统计规则包括第一业务流的用户量统计规则的情况下，该用户量统计信息可以包括第一业务流的用户量统计信息，第一业务流的用户量统计信息指示本地业务链控制之前的第一业务流的用户量，或指示本地业务链控制之前的第一业务流的 用户量。
在用户量统计规则包括第二业务流的用户量统计规则的情况下，该用户量统计信息可以包括第二业务流的用户量统计信息，第二业务流的用户量统计信息指示本地业务链控制之前的第二业务流的用户量，或指示本地业务链控制之前的第二业务流的用户量。
可选的，SMF网元接收该用户量统计信息后，可以将该用户量统计信息上报至计费功能(charging function，CHF)网元，以使该CHF网元进行计费等操作。
至此，可以实现由分流点对需经过本地业务链控制的上行或下行业务流的用户量统计。
如图8所示，为本申请实施例提供的另一种业务流的用户量统计方法，该方法可以适用于由L-PSA和/或PSA进行用户量的简单统计的场景。该方法包括：
S801～S806、同图7所示的实施例中的步骤S701～S706，可参考上述说明，在此不再赘述。
S807、SMF网元向I-UPF网元发送N4会话建立请求。相应的，I-UPF网元接收N4会话建立请求。
其中，N4会话建立请求携带RAN tunnel info、PSA tunnel info、L-PSA tunnel info，无需携带用户量统计规则，相关描述可参考上述步骤S707，在此不再赘述。
S808、同图7所示的实施例中的步骤S708，可参考上述说明，在此不再赘述。
S809、SMF网元向PSA网元发送N4会话修改请求。相应的，PSA网元接收N4会话修改请求。
其中，该N4会话修改请求包括I-UPF tunnel info for PSA。
可选的，该N4会话修改请求还可以包括第一用户量统计规则。其中，第一用户量统计规则包括第一业务流的用户量统计规则，和/或，第二业务流的用户量统计规则，且第一业务流的用户量统计规则用于指示对本地业务链处理之后的第一业务流进行用户量统计，第二业务流的用户量统计规则用于指示对本地业务链处理之前的第二业务流进行用户量统计。
可选的，第一业务流可以来自I-UPF网元或来自L-PSA。可以理解的，在本地业务链控制之后的第一业务流经I-UPF网元(即路径1)传输至中心DN时，第一业务流来自I-UPF网元。在本地业务链控制之后的第一业务流不经I-UPF网元(即路径2)传输至中心DN时，第一业务流来自L-PSA。可选的，第二业务流可以来自中心DN。
示例性的，以第一业务流由SDF1表示，第二业务流由SDF2表示，上述第一用户量统计规则可以表示为表5中的一项。其中，UL指上行业务流，DL指下行业务流，UL:before指本地业务链控制之前的上行业务流，UL:after指本地业务链控制之后的上行业务流，DL:before指本地业务链控制之前的下行业务流，DL:after指本地业务链控制之后的下行业务流。
表5
Figure PCTCN2021095161-appb-000005
Figure PCTCN2021095161-appb-000006
S810、同图7所示的实施例中的步骤S710，可参考上述说明，在此不再赘述。
S811、SMF网元向L-PSA网元发送N4会话修改请求。相应的，L-PSA网元接收N4会话修改请求。
其中，该N4会话修改请求包括I-UPF tunnel info for L-PSA，或者包括I-UPF tunnel info for L-PSA和specific I-UPF tunnel info for L-PSA。
可选的，该N4会话修改请求还可以包括第二用户量统计规则。其中，第二用户量统计规则包括第一业务流的用户量统计规则，和/或，第二业务流的用户量统计规则，且第一业务流的用户量统计规则用于指示对本地业务链处理之前或之后的第一业务流进行用户量统计，第二业务流的用户量统计规则用于指示对本地业务链处理之前或之后的第二业务流进行用户量统计。
可选的，第一业务流的用户量统计规则用于指示对本地业务链处理之前的第一业务流进行用户量统计，可以为：对来自I-UPF网元的第一业务流进行用户量统计；第一业务流的用户量统计规则用于指示对本地业务链处理之后的第一业务流进行用户量统计，可以为：对来自本地DN的第一业务流进行用户量统计。
可选的，第二业务流的用户量统计规则用于指示对本地业务链处理之前的第二业务流进行用户量统计，可以为：对来自I-UPF网元或PSA的第二业务流进行用户量统计；第二业务流的用户量统计规则用于指示对本地业务链处理之后的第二业务流进行用户量统计，可以为：对来自中心DN的第二业务流进行用户量统计。
可以理解的，在本地业务链控制之前的第二业务流经I-UPF网元(即路径3)传输至L-PSA时，第二业务流的用户量统计规则用于指示对本地业务链处理之前的第二业务流进行用户量统计，可以为：对来自I-UPF网元的第一业务流进行用户量统计。在本地业务链控制之前的第二业务流不经I-UPF网元(即路径4)传输至L-PSA时，第二业务流的用户量统计规则用于指示对本地业务链处理之前的第二业务流进行用户量统计，可以为：对来自PSA的第二业务流进行用户量统计。
示例性的，以第一业务流由SDF1表示，第二业务流由SDF2表示，上述第二用户量统计规则可以表示为表6中的一项。其中，UL指上行业务流，DL指下行业务流，UL:before指本地业务链控制之前的上行业务流，UL:after指本地业务链控制之后的上行业务流，DL:before指本地业务链控制之前的下行业务流，DL:after指本地业务链控制之后的下行业务流。
表6
Figure PCTCN2021095161-appb-000007
Figure PCTCN2021095161-appb-000008
可以理解的是，在上述步骤S809中，SMF网元不向PSA发送第一用户量统计规则的情况下，该步骤S811中，SMF网元向L-PSA发送第二用户量统计规则，即由L-PSA进行用户量统计。在上述步骤S809中，SMF网元向PSA发送第一用户量统计规则的情况下，该步骤S811中，SMF网元可以不向L-PSA发送第二用户量统计规则，即由PSA进行用户量统计。
当然，在步骤S809中，SMF网元向PSA发送第一用户量统计规则的情况下，该步骤S811中，SMF网元也可以向L-PSA发送第二用户量统计规则，即由PSA和L-PSA进行联合统计。在该场景下，第一用户量统计规则和第二用户量统计规则中不存在相同的规则，或者说L-PSA和PSA不进行重复的用户量统计，例如，PSA统计了本地业务链控制之后的第一业务流的用户量，则L-PSA不再统计本地业务链控制之后的第一业务流的用户量。
也就是说，本实施例中，对于上行业务流，一种统计方式为：由L-PSA对来自I-UPF的上行业务流进行用户量统计。另一种统计方式为：L-PSA对来自本地DN的上行业务流进行用户量统计，或者，由PSA对来自I-UPF或L-PSA的上行业务流进行用户量统计。
对于下行业务流，一种统计方式为：由L-PSA对来自I-UPF或PSA的下行业务流进行用户量统计，或者，由PSA对来自中心DN的下行业务流进行统计。另一种统计方式为：由L-PSA对来自本地DN的下行业务流进行用户量统计。
S812、同图7所示的实施例中的步骤S712，可参考上述说明，在此不再赘述。
S813、PSA根据第一用户量统计规则进行用户量统计，和/或，L-PSA根据第二用户量统计规则进行用户量统计。
可以理解的，若SMF网元向PSA发送了第一用户量统计规则，PSA执行步骤S813,；若SMF网元向L-PSA发送了第二用户量统计规则，L-PSA执行步骤S813。
S814、PSA向SMF网元发送用户量统计信息，和/或，L-PSA向SMF网元发送用户量统计信息。相应的，SMF网元接收来自PSA和/或L-PSA的用户量统计信息。
可以理解的是，在PSA执行了步骤S813的情况下，该步骤S814中，PSA向SMF网元发送用户量统计信息。在L-PSA执行了步骤S813的情况下，该步骤S814中，L-PSA向SMF网元发送用户量统计信息。
可以理解的，步骤S814后，SMF网元最终收到的用户量统计信息可以包括第一业务流的用户量统计信息和/或第二业务流的用户量统计信息，第一业务流的用户量统计信息指示本地业务链控制之前的第一业务流的用户量，或指示本地业务链控制之前的第一业务流的用户量，第二业务流的用户量统计信息指示本地业务链控制之前的第二业务流的用户量，或指示本地业务链控制之前的第二业务流的用户量。
可选的，SMF网元收到用户量统计信息后，可以将该用户量统计信息上报至计费CHF 网元，以使该CHF网元进行计费等操作。
至此，可以实现由L-PSA和/或PSA对需经过本地业务链控制的上行或下行业务流的用户量统计。
如图9所示，为本申请实施例提供的又一种业务流的用户量统计方法，该方法可以适用于由分流点(即I-UPF)进行用户量的区分统计的场景。该方法包括：
S901、同图7所示的实施例中的步骤S701，可参考上述说明，在此不再赘述。
S902、与图7所示的实施例中的步骤S702类似，区别在于：
在PCF网元发送的策略控制规则包括第一策略控制规则的情况下，消息b中还可以包括第一度量策略和第二度量策略，该第一度量策略用于对本地业务链控制之前的第一业务流进行处理(或度量)，该第二度量策略用于对本地业务链控制之后的第一业务流进行处理(或度量)。
在PCF网元发送的策略控制规则包括第二策略控制规则的情况下，消息b中还可以包括第三度量策略和第四度量策略，该第三度量策略用于对本地业务链控制之前的第二业务流进行处理(或度量)，该第四度量策略用于对本地业务链控制之后的第二业务流进行处理(或度量)。
需要说明的是，本申请实施例中，“度量策略”也可以称为“度量标准”，二者可以相互替换。上述第一度量策略、第二度量策略、第三度量策略、或者第四度量策略也可以是SMF网元根据本地配置策略确定的，本申请实施对SMF网元获取上述度量策略的方法步骤具体限定，仅是示例性的以PCF网元确定并发送给SMF网元为例进行说明。
可选的，第一度量策略、第二度量策略、第三度量策略、或者第四度量中的任意多个度量策略可以相同，也可以不同，本申请实施例对此不做具体限定。
可选的，上述度量策略可以由计费密钥(charging key)、计费方法(charging method)、监控密钥(monitoring key)、会话级监控排除指示(indication of exclusion from session level monitoring)中的一种或多种表示。其中，计费密钥用于确定业务流的费率。计费方法用于表明业务流的计费方法，可以是在线计费、离线计费等。监控密钥用于表明多个业务流是否共享用户量。会话级监控排除指示用于表明业务流不应该计入用户量统计中。
示例性的，当度量策略由计费密钥表示时，可以将计费密钥作为度量策略。第一度量策略、第二度量策略、第三度量策略、第四度量策略分别对应相同或不同的计费密钥。度量策略由计费方法、监控密钥、会话级监控排除指示表示的实现方式可参考由计费密钥表示的方式，在此不再赘述。
S903～S906、同图7所示的实施例中的步骤S703～S706，可参考上述说明，在此不再赘述。
S907、与图7所示的实施例中的步骤S707类似，区别在于：
N4会话建立请求中携带的用户量统计规则包括第一业务流的用户量统计规则和/或第二业务流的用户量统计规则，第一业务流的用户量统计规则用于指示对本地业务链控制之前的第一业务流以及本地业务链控制之后的第一业务流进行用户量统计，第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流以及本地业务链控制之后的第二业务流进行用户量统计。
也就是说，示例性的，用户量统计规则可以为以下一种：
Case1、对来自RAN的第一业务流，即报文头中携带I-UPF tunnel info for RAN的第一业务流，进行用户量统计；
以及对来自L-PSA的第一业务流，即报文头中携带I-UPF tunnel info for L-PSA的第一业务流，进行用户量统计。
Case2、对来自L-PSA的第二业务流，即报文头中携带I-UPF tunnel info for L-PSA的第二业务流，进行用户量统计；
以及对来自PSA的第二业务流，即报文头中携带I-UPF tunnel info for PSA的第二业务流，进行用户量统计。
Case3、对来自RAN的第一业务流，即报文头中携带I-UPF tunnel info for RAN的第一业务流，进行用户量统计；
以及，对来自L-PSA的第一业务流，即报文头中携带I-UPF tunnel info for L-PSA的第一业务流，进行用户量统计。
以及，对来自L-PSA的第二业务流，即报文头中携带I-UPF tunnel info for L-PSA的第二业务流，进行用户量统计；
以及，对来自PSA的第二业务流，即报文头中携带I-UPF tunnel info for PSA的第二业务流，进行用户量统计。
示例性的，以第一业务流由SDF1表示，第二业务流由SDF2表示，上述各种情况下的用户量统计规则可以表示为表7。其中，UL指上行业务流，DL指下行业务流，UL:before指本地业务链控制之前的上行业务流，UL:after指本地业务链控制之后的上行业务流，
DL:before指本地业务链控制之前的下行业务流，DL:after指本地业务链控制之后的下行业务流。
表7
Figure PCTCN2021095161-appb-000009
S908～S913、同图7所示的实施例中的步骤S708～S713，可参考上述说明，在此不再赘述。
S914、I-UPF网元向SMF网元发送用户量统计信息。相应的，SMF网元接收来自I-UPF网元的用户量统计信息。
可选的，在用户量统计规则包括第一业务流的用户量统计规则的情况下，该用户量统计信息可以包括第一用户量统计信息和第二用户量统计信息，第一用户量统计信息用于指示本地业务链控制之前的第一业务流的用户量，第二用户量统计信息用于指示本地业务链控制之后的第一业务流的用户量。
在用户量统计规则包括第二业务流的用户量统计规则的情况下，该用户量统计信息可以包括第三用户量统计信息和第四用户量统计信息，第三用户量统计信息用于指示本地业务链控制之前的第二业务流的用户量，第四用户量统计信息用于指示本地业务链控制之后的第二业务流的用户量。
可选的，SMF网元接收第一用户量统计信息和第二用户量统计信息后，可以根据第 一度量策略处理第一用户量统计信息，以及根据第二度量策略处理第二用户量统计信息。之后，SMF网元可以将处理后的第一用户量统计信息和第二用户量统计信息发送至CHF网元。
示例性的，以根据第一度量策略处理第一用户量统计信息为例：
当第一度量策略由计费密钥表示时，根据第一度量策略处理第一用户量统计信息可以为：使用根据第一度量策略确定的费率乘以第一用户量统计信息所指示的用户量。
当第一度量策略由计费方法表示，计费方法为在线计费时，根据第一度量策略处理第一用户量统计信息可以为：使用在线计费的方法处理第一用户量统计信息所指示的用户量。
当第一度量策略由会话级监控排除指示表示时，根据第一度量策略处理第一用户量统计信息可以为：丢弃第一用户量统计信息，或对第一用户量统计信息所指示的用户量乘以0。
可选的，SMF网元接收第三用户量统计信息和第四用户量统计信息后，可以根据第三度量策略处理第三用户量统计信息，以及根据第四度量策略处理第四用户量统计信息，处理方法可参考根据第一度量信息对第一用户量统计信息进行处理的方法。之后，SMF网元也可以将处理后的第三用户量统计信息和第四用户量统计信息发送至CHF网元。
基于该方案，CHF网元可以根据处理后的用户量统计信息进行计费等操作，例如，CHF网元根据处理后的用户量统计信息生成话单。通过使用度量策略处理用户量的方式，可以实现对经过本地业务链控制的业务流的差别处理，即实现差别计费、差别统计等。
至此，可以实现由分流点对需经过本地业务链控制的上行或下行业务流的用户量进行区分统计，以提升该类业务流的用户量统计的精确度，使得网络更合理地向终端用户和第三方应用提供商收费，例如，网络可以按照本地业务链控制之前的业务流的用户量对终端用户进行收费，而按照本地业务链控制之后的业务流的用户量对第三方应用提供商收费。
如图10所示，为本申请实施例提供的又一种业务流的用户量统计方法，该方法可以适用于由L-PSA和/或PSA进行用户量的区分统计的场景。该方法包括：
S1001～S1008、其中，步骤S1002同图9所述的实施例中的步骤S902，S1001、S1003～S1008同图8所示的实施例中的S801、S803～S808。
S1009、与上述步骤S809相同，即可选的，在N4会话修改请求中还可以包括第一用户量统计规则。其中，第一用户量统计规则包括第一业务流的用户量统计规则，和/或，第二业务流的用户量统计规则，且第一业务流的用户量统计规则用于指示对本地业务链处理之后的第一业务流进行用户量统计，第二业务流的用户量统计规则用于指示对本地业务链处理之前的第二业务流进行用户量统计。
S1010、与上述步骤S809相同。
S1011、与上述步骤S811类似，区别在于：
N4会话修改请求包括的第二用户量统计规则包括第一业务流的用户量统计规则，和/或，第二业务流的用户量统计规则。
在S1009中第一用户量统计规则包括的第一业务流的用户量统计规则用于指示对本地业务链控制之后的第一业务流进行用户量统计的情况下，第二用户量统计规则包括的第一业务流的用户量统计规则用于指示对本地业务链控制之前的第一业务流进行用户量统计。第二用户量统计规则可以包括第二业务流的用户量统计规则，也可以不包括第二 业务流的用户量统计规则。若第二用户量统计规则包括第二业务流的用户量统计规则，在第一用户量统计规则不包括第二业务流的用户量统计规则的情况下，第二用户量统计规则包括的第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流以及本地业务链控制之后的第二业务流进行用户量统计；在第一用户量统计规则包括第二业务流的用户量统计规则的情况下，第二用户量统计规则包括的第二业务流的用户量统计规则用于指示对本地业务链控制之后的第二业务流进行用户量统计。
在S1009中第一用户量统计规则包括的第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计的情况下，第二用户量统计规则包括的第二业务流的用户量统计规则用于指示对本地业务链控制之后的第二业务流进行用户量统计。第二用户量统计规则可以包括第一业务流的用户量统计规则，也可以不包括第一业务流的用户量统计规则。若第二用户量统计规则包括第一业务流的用户量统计规则，在第一用户量统计规则不包括第一业务流的用户量统计规则的情况下，第二用户量统计规则包括的第一业务流的用户量统计规则用于指示对本地业务链控制之前的第一业务流以及本地业务链控制之后的第一业务流进行用户量统计；在第一用户量统计规则包括第一业务流的用户量统计规则的情况下，第二用户量统计规则包括的第一业务流的用户量统计规则用于指示对本地业务链控制之前的第一业务流进行用户量统计。
在S1009中SMF网元不发送第一用户量统计规则的情况下，第二用户量统计规则包括的第一业务流的用户量统计规则用于指示对本地业务链处理之前的第一业务流以及本地业务链控制之后的第一业务流进行用户量统计，第二用户量统计规则包括的第二业务流的用户量统计规则用于指示对本地业务链处理之前的第二业务流以及本地业务链控制之后的第二业务流进行用户量统计。
示例性的，以第一业务流由SDF1表示，第二业务流由SDF2表示，上述第二用户量统计规则可以表示为表8中的一项。其中，UL指上行业务流，DL指下行业务流，UL:before指本地业务链控制之前的上行业务流，UL:after指本地业务链控制之后的上行业务流，DL:before指本地业务链控制之前的下行业务流，DL:after指本地业务链控制之后的下行业务流。
表8
Figure PCTCN2021095161-appb-000010
类似于图8所示的实施例，第一用户量统计规则和第二用户量统计规则不存在相同的规则，或者说L-PSA和PSA不进行重复的用户量统计，例如，PSA统计了本地业务链控制之后的第一业务流的用户量，则L-PSA不再统计本地业务链控制之后的第一业务流的用户量。
也就是说，本实施例中，对于上行业务流，一种统计方式为：由L-PSA对来自I-UPF的上行业务流进行用户量统计，以及由L-PSA对来自本地DN的上行业务流进行用户量统计。另一种统计方式为，由L-PSA对来自I-UPF的上行业务流进行用户量统计，以及由PSA对来自I-UPF或L-PSA的上行业务流进行用户量统计。
对于下行业务流，一种统计方式为：由L-PSA对来自I-UPF或PSA的下行业务流进行用户量统计，以及由L-PSA对来自本地DN的下行业务流进行用户量统计。另一种统计方式为：由PSA对来自中心DN的下行业务流进行统计，以及由L-PSA对来自本地DN的下行业务流进行用户量统计。
S1012、同图8所示的实施例中的S812。
S1013、L-PSA根据第二用户量统计规则统计业务流的用户量。或者，L-PSA根据第二用户量统计规则进行用户量统计，PSA根据第一用户量统计规则进行用户量统计。
可以理解的，在S1009中SMF网元不发送第一用户量统计规则的情况下，该步骤S1013为：L-PSA根据第二用户量统计规则统计业务流的用户量。
在S1009中SMF网元发送了第一用户量统计规则的情况下，该步骤S1013为：L-PSA根据第二用户量统计规则进行用户量统计，PSA根据第一用户量统计规则进行用户量统计。在该场景下，对于第一业务流：由L-PSA统计本地业务链控制之前的第一业务流的用户量，以及由PSA统计本地业务链控制之后的第一业务流的用户量；对于第二业务流，由PSA统计本地业务链控制之前的第二业务流的用户量，由L-PSA统计本地业务链控制之后的第二业务流的用户量。
S1014、L-PSA向SMF网元发送用户量统计信息。相应的，SMF网元接收来自L-PSA的用户量统计信息。
或者，L-PSA和PSA向SMF网元发送用户量统计信息。相应的，SMF网元接收来自L-PSA和PSA的用户量统计信息。
可以理解的，步骤S1014后，SMF网元最终收到的用户量统计信息可以包括第一用户量统计信息以及第二用户量统计信息，和/或，第三用户量统计信息以及第四用户量统计信息，该四种用户量统计信息的含义以及SMF网元对其的处理可参考上述步骤S914中的相关说明，在此不再赘述。
至此，可以实现由L-PSA，或者由L-PSA以及PSA对需经过本地业务链控制的上行或下行业务流的用户量进行区分统计，以提升该类业务流的用户量统计的精确度，使得网络更合理地向终端用户和第三方应用提供商收费，例如，网络可以按照本地业务链控制之前的业务流的用户量对终端用户进行收费，而按照本地业务链控制之后的业务流的用户量对第三方应用提供商收费。
此外，本申请实施例还提供一种适用于如图4c所示的5G网络的业务流的用户量统计方法，下面以图4c中的UCLC/BP为I-UPF，第二UPF为远端PSA(下文简称为PSA)、第一UPF为L-PSA为例，对本申请实施例提供的业务流的用户量统计方法进行说明。如图11所示，该方法包括：
S1101、终端建立PDU会话。
其中，该会话对应的用户面传输路径为：终端<-→RAN<-→PSA<-→中心DN，即SMF网元已经获取到RAN的隧道信息(RAN tunnel info)和PSA的隧道信息(PSA tunnel info)
S1102、第一SMF网元决定为会话插入I-UPF和L-PSA。
其中，I-UPF充当分流点，可以将终端的部分业务流发送至L-PSA，另一部分发送至PSA。其他说明可参考上述步骤S703中的相关描述。
S1103、第一SMF网元选择L-PSA。
该步骤的具体实现可以参考现有技术，本申请实施例对此不作赘述。
S1104、第一SMF网元向L-PSA发送N4会话建立请求。相应的，L-PSA接收N4会话建立请求。
S1105、L-PSA向第一SMF网元发送N4会话建立响应。相应的，第一SMF网元接收N4会话建立响应。
其中，N4会话建立响应中携带L-PSA tunnel info。
S1106、第一SMF网元向I-UPF网元发送N4会话建立请求。相应的，I-UPF网元接收N4会话建立请求。
其中，N4会话建立请求携带RAN tunnel info、PSA tunnel info、L-PSA tunnel info。
S1107、I-UPF网元向第一SMF网元返回N4会话建立响应。相应的，第一SMF网元接收N4会话建立响应。
其中，N4会话建立响应中携带I-UPF tunnel info，具体可以包括I-UPF tunnel info for RAN、I-UPF tunnel info for PSA，I-UPF tunnel info for L-PSA。
S1108、第一SMF网元向第二SMF网元发送会话更新请求。相应的，第二SMF网元接收来自第一SMF网元的会话更新请求。
其中，该会话更新请求包括I-UPF tunnel info for PSA。还可以包括分流点插入指示，以指示第二SMF网元由第一SMF网元为会话插入了分流点。
S1109、第二SMF网元向第一SMF网元发送会话更新响应。相应的，第一SMF网元接收来自第二SMF网元的会话更新响应。
S1110、第二SMF网元向PSA发送I-UPF tunnel info for PSA。相应的，PSA接收来自第二SMF网元的I-UPF tunnel info for PSA。
S1111、第二SMF网元向第一SMF网元发送会话更新请求。相应的，第一SMF网元接收来自第二SMF网元的会话更新请求。
其中，该会话更新请求包括N4信息。N4信息包括一个或多个业务流的业务流描述信息和相应的业务链信息，用于指示对该一个或多个业务流由其相应的业务链信息指示的本地业务链进行本地业务链控制。
S1112、第一SMF网元向L-PSA发送I-UPF tunnel info for L-PSA。相应的，L-PSA接收来自第一SMF网元的I-UPF tunnel info for L-PSA。
S1113、第一SMF网元向I-UPF发送N4规则。相应的，I-UPF网元接收来自第一SMF网元的N4规则。
其中，该N4规则包括步骤S1111中的一个或多个业务流的业务流描述信息和相应的业务链信息。
S1114、第一SMF网元向L-PSA发送用户量统计规则。相应的，L-PSA接收来自第一SMF网元的用户量统计规则。
其中，该用户量统计规则包括步骤S1111中的一个或多个业务流中部分或全部业务流的用户量统计规则。例如，步骤S1111中有业务流1、业务流2、以及业务流3，该用户量统计规则可以包括业务流1的用户量统计规则，用于表示由L-PSA统计业务流1的用户量。业务流的用户量统计规则可以参考前述实施例中SMF网元发送给L-PSA的用户量统计规则，在此不再赘述。
S1115、第一SMF网元向第二SMF网元发送会话更新响应。相应的，第二SMF网元接收来自第一SMF网元的会话更新响应。
在本实施例的一种实施场景下，若步骤S1114中的用户量统计规则包括上述一个或多个业务流中部分业务流的用户量统计规则：
可选的，该会话更新响应中可以包括由L-PSA进行用户量统计的业务流的业务流描述信息和第一指示信息，用于向第二SMF网元指示由L-PSA对该业务流描述信息所描述的业务流进行用户量统计。
可选的，第二SMF网元收到该业务流描述信息和第一指示信息后，为了避免重复统计业务流描述信息所描述的业务流的用户量，可以确定PSA无需对该业务流进行用户量统计，从而向PSA发送该业务流描述信息和第二指示信息，以指示PSA停止统计该业务流的用户量。或者，若第二SMF网元收到PSA上报的该业务流的用户量统计信息，第二SMF网元可以对该用户量统计信息进行特殊处理，例如丢弃该用户量统计信息。
在本实施例的另一种实施场景下，若PCF网元的策略信息指示需经本地业务链处理的业务流的用户量由L-PSA统计，即由L-PSA统计该一个或多个业务流中的全部业务流的用户量：
可选的，第二SMF网元可以根据PCF网元的策略信息确定PSA无需对该一个或多个业务流进行用户量统计，从而向PSA发送该一个或多个业务流的业务流描述信息和第三指示信息，以指示PSA停止统计该一个或多个业务流的用户量。或者，若第二SMF网元收到PSA上报的该一个或多个业务流的用户量统计信息，第二SMF网元可以对该用户量统计信息进行特殊处理，例如丢弃该用户量统计信息。
在本申请实施例的再一种实施场景下，若运营商策略规定，对于上行业务流进行本地业务链控制之前的用户量统计，或者对于下行业务流进行本地业务链控制之后的用户量统计，由于PSA对上行业务流的用户量统计，统计的是经过本地业务链控制之后的用户量，PSA对下行业务流的用户量统计，统计的是经过本地业务链控制之前的用户量，因此第一SMF网元需指示PSA停止统计上行和/或下行业务流的用户量，或者，对PSA上报的上行和/或下行业务流的用户量进行特殊处理，例如丢弃。可以理解的，在该场景下，步骤S1114中的用户量统计规则用于指示对本地业务链控制之前的业务流的用户量进行统计，和/或对本地业务链控制之后的业务流的用户量进行统计。
基于该方案，在分流点和本地锚点由第一SMF网元管理，远端锚点由第二SMF网元管理的情况下，可以避免本地锚点和远端锚点重复统计业务流的用户量，提高用户量统计的精确性。
其中，上述图6至图11所示的各个步骤中各个网元的动作可以由图5所示的通信设备50中的处理器501调用存储器503中存储的应用程序代码来执行，本实施例对此不作任何限制。
可以理解的是，本申请实施例中，各个网元可以执行本申请实施例中的部分或全部步骤，这些步骤仅是示例，本申请实施例还可以执行其它步骤或者各种步骤的变形。此 外，各个步骤可以按照本申请实施例呈现的不同的顺序来执行，并且有可能并非要执行本申请实施例中的全部步骤。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，上述会话管理网元或用户面网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对会话管理网元或用户面网元进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，以采用集成的方式划分各个功能模块的情况下，图12示出了一种会话管理网元120的结构示意图。该会话管理网元120包括处理模块1201和收发模块1202。
其中，处理模块1201用于对会话管理网元的动作进行控制管理，例如，处理模块1201用于支持会话管理网元执行图6中的过程S601、图7中的过程S703和S704，和/或用于本文所描述的技术的其它过程。收发模块1202用于支持会话管理网元与其他网络实体的通信，例如与图6所示的用户面网元之间的通信。
可选的，会话管理网元120还可以包括存储模块1203(图12中未示出)，用于存储会话管理网元120的程序代码和数据。具体的，可以参考如下描述：
处理模块1201，用于确定用户量统计规则，该用户量统计规则包括第一业务流的用户量统计规则和/或第二业务流的用户量统计规则，第一业务流为需经过本地业务链控制的上行业务流，该第二业务流为需经过本地业务链控制的下行业务流。第一业务流的用户量统计规则用于指示对本地业务链控制之前的该第一业务流进行用户量统计，和/或，对本地业务链控制之后的该第一业务流进行用户量统计；第二业务流的用户量统计规则用于指示对本地业务链控制之前的该第二业务流进行用户量统计，和/或，对本地业务链控制之后的该第二业务流进行用户量统计。收发模块1202，用于向用户面网元发送该用户量统计规则。
可选的，处理模块1201，还用于获取第一度量策略和第二度量策略。收发模块1202，还用于接收第一用户量统计信息和第二用户量统计信息，第一用户量统计信息用于指示本地业务链控制之前的第一业务流的用户量，第二用户量统计信息用于指示本地业务链控制之后的第一业务流的用户量。处理模块1201，还用于根据该第一度量策略处理该第一用户量统计信息，以及根据该第二度量策略处理该第二用户量统计信息。
可选的，处理模块1201，还用于获取第三度量策略和第四度量策略。收发模块1202，还用于接收第三用户量统计信息和第四用户量统计信息，第三用户量统计信息用于指示本地业务链控制之前的该第二业务流的用户量，第四用户量统计信息用于指示本地业务链控制之后的该第二业务流的用户量。处理模块1201，还用于根据第三度量策略处理第三用户量统计信 息，以及根据第四度量策略处理第四用户量统计信息。
可选的，收发模块1202，还用于接收来自策略控制功能网元的第一指示信息。处理模块1201，用于确定用户量统计规则，可以包括：处理模块1201，用于在第一指示信息用于指示本地业务链控制之后的第一业务流的大小不发生变化时，确定第一业务流的用户量统计规则用于指示对本地业务链控制之前的第一业务流进行用户量统计，或者，对本地业务链控制之后的第一业务流进行用户量统计。或者，处理模块1201，用于在第一指示信息用于指示本地业务链控制之后的第一业务流的大小发生变化时，确定第一业务流的用户量统计规则用于指示对本地业务链控制之前的第一业务流进行用户量统计，以及，对本地业务链控制之后的第一业务流进行用户量统计。
可选的，收发模块1202，还用于接收来自策略控制功能网元的第二指示信息。处理模块1201，用于确定用户量统计规则，可以包括：处理模块1201，用于在第二指示信息用于指示本地业务链控制之后的第二业务流的大小不发生变化时，确定第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计，或者，对本地业务链控制之后的第二业务流进行用户量统计。或者，处理模块1201，用于在第二指示信息用于指示本地业务链控制之后的第二业务流的大小发生变化时，确定第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计，以及，对本地业务链控制之后的第二业务流进行用户量统计。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该会话管理网元120以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该会话管理网元120可以采用图5所示的形式。
比如，图5中的处理器501可以通过调用存储器503中存储的计算机执行指令，使得会话管理网元120执行上述方法实施例中的业务流的用户量统计方法。
具体的，图12中的处理模块1201和收发模块1202的功能/实现过程可以通过图5中的处理器501调用存储器503中存储的计算机执行指令来实现。或者，图12中的处理模块1201的功能/实现过程可以通过图5中的处理器501调用存储器503中存储的计算机执行指令来实现，图12中的收发模块1202的功能/实现过程可以通过图5中的通信接口504来实现。
由于本实施例提供的会话管理网元120可执行上述的业务流的用户量统计方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
可选的，本申请实施例还提供了一种装置(例如，该装置可以是芯片系统)，该装置包括处理器，用于支持会话管理网元实现上述业务流的用户量统计方法。在一种可能的设计中，该装置还包括存储器。该存储器，用于保存会话管理网元必要的程序指令和数据。当然，存储器也可以不在该装置中。在另一种可能的设计中，该装置还包括接口电路，该接口电路为代码/数据读写接口电路，该接口电路用于接收计算机执行指令(计算机执行指令存储在存储器中，可能直接从存储器读取，或可能经过其他器件)并传输至该处理器。该装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
或者，比如，以采用集成的方式划分各个功能模块的情况下，图13示出了一种用户 面网元130的结构示意图。该用户面网元130包括处理模块1301和收发模块1302。
其中，处理模块1301用于对用户面网元的动作进行控制管理，例如，处理模块1301用于支持用户面网元执行图6中的过程S603，和/或用于本文所描述的技术的其它过程。收发模块1302用于支持用户面网元与其他网络实体的通信，例如与图6所示的会话管理网元之间的通信。
可选的，用户面网元130还可以包括存储模块1303(图13中未示出)，用于存储用户面网元130的程序代码和数据。具体的，可以参考如下描述：
收发模块1302，用于接收来自会话管理网元的用户量统计规则，该用户量统计规则包括第一业务流的用户量统计规则和/或第二业务流的用户量统计规则，第一业务流为需经过本地业务链控制的上行业务流，该第二业务流为需经过本地业务链控制的下行业务流。第一业务流的用户量统计规则用于指示对本地业务链控制之前的该第一业务流进行用户量统计，和/或，对本地业务链控制之后的该第一业务流进行用户量统计；第二业务流的用户量统计规则用于指示对本地业务链控制之前的该第二业务流进行用户量统计，和/或，对本地业务链控制之后的该第二业务流进行用户量统计。处理模块1301，用于在用户量统计规则包括第一业务流的用户量统计规则的情况下，根据第一业务流的用户量统计规则统计第一业务流的用户量；或者，处理模块1301，用于在该用户量统计规则包括第二业务流的用户量统计规则的情况下，根据第二业务流的用户量统计规则统计第二业务流的用户量。
可选的，收发模块1302，还用于向会话管理网元发送第一用户量统计信息和/或第二用户量统计信息，第一用户量统计信息用于指示本地业务链控制之前的第一业务流的用户量，第二用户量统计信息用于指示本地业务链控制之后的第一业务流的用户量。
可选的，收发模块1302，还用于向会话管理网元发送第三用户量统计信息和/或第四用户量统计信息，第三用户量统计信息用于指示本地业务链控制之前的第二业务流的用户量，第四用户量统计信息用于指示本地业务链控制之后的第二业务流的用户量。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该用户面网元130以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该用户面网元130可以采用图5所示的形式。
比如，图5中的处理器501可以通过调用存储器503中存储的计算机执行指令，使得用户面网元130执行上述方法实施例中的业务流的用户量统计方法。
具体的，图13中的处理模块1301和收发模块1302的功能/实现过程可以通过图5中的处理器501调用存储器503中存储的计算机执行指令来实现。或者，图13中的处理模块1301的功能/实现过程可以通过图5中的处理器501调用存储器503中存储的计算机执行指令来实现，图13中的收发模块1302的功能/实现过程可以通过图5中的通信接口504来实现。
由于本实施例提供的用户面网元130可执行上述的业务流的用户量统计方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
可选的，本申请实施例还提供了一种装置(例如，该装置可以是芯片系统)，该装置包括处理器，用于支持会话管理网元实现上述业务流的用户量统计方法。在一种可能的设计中，该装置还包括存储器。该存储器，用于保存会话管理网元必要的程序指令和 数据。当然，存储器也可以不在该装置中。在另一种可能的设计中，该装置还包括接口电路，该接口电路为代码/数据读写接口电路，该接口电路用于接收计算机执行指令(计算机执行指令存储在存储器中，可能直接从存储器读取，或可能经过其他器件)并传输至该处理器。该装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (31)

  1. 一种业务流的用户量统计方法，其特征在于，所述方法包括：
    会话管理网元确定用户量统计规则，所述用户量统计规则包括第一业务流的用户量统计规则和/或第二业务流的用户量统计规则，所述第一业务流为需经过本地业务链控制的上行业务流，所述第二业务流为需经过本地业务链控制的下行业务流，所述第一业务流的用户量统计规则用于指示对本地业务链控制之前的所述第一业务流进行用户量统计，和/或，对本地业务链控制之后的所述第一业务流进行用户量统计，所述第二业务流的用户量统计规则用于指示对本地业务链控制之前的所述第二业务流进行用户量统计，和/或，对本地业务链控制之后的所述第二业务流进行用户量统计；
    所述会话管理网元向用户面网元发送所述用户量统计规则。
  2. 根据权利要求1所述的方法，其特征在于，所述用户面网元作为分流点。
  3. 根据权利要求2所述的方法，其特征在于，所述第一业务流的用户量统计规则用于指示对本地业务链控制之前的所述第一业务流进行用户量统计，包括：
    所述第一业务流的用户量统计规则用于指示所述用户面网元对来自接入网设备的所述第一业务流进行用户量统计；
    或者，所述第一业务流的用户量统计规则用于指示对本地业务链控制之后的所述第一业务流进行用户量统计，包括：
    所述第一业务流的用户量统计规则用于指示所述用户面网元对来自本地锚点的所述第一业务流进行用户量统计。
  4. 根据权利要求2或3所述的方法，其特征在于，所述第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计，包括：
    所述第二业务流的用户量统计规则用于指示所述用户面网元对来自远端锚点的所述第二业务流进行用户量统计；
    或者，所述第二业务流的用户量统计规则用于指示对本地业务链控制之后的所述第二业务流进行用户量统计，包括：
    所述第二业务流的用户量统计规则用于指示所述用户面网元对来自本地锚点的所述第二业务流进行用户量统计。
  5. 根据权利要求1所述的方法，其特征在于，所述用户面网元作为远端锚点。
  6. 根据权利要求5所述的方法，其特征在于，所述第一业务流的用户量统计规则用于指示对本地业务链控制之后的所述第一业务流进行用户量统计，包括：
    所述第一业务流的用户量统计规则用于指示所述用户面网元对所述第一业务流进行用户量统计。
  7. 根据权利要求5或6所述的方法，其特征在于，所述第二业务流的用户量统计规则用于指示对本地业务链控制之前的所述第二业务流进行用户量统计，包括：
    所述第二业务流的用户量统计规则用于指示所述用户面网元对所述第二业务流进行用户量统计。
  8. 根据权利要求根据权利要求1所述的方法，其特征在于，所述用户面网元作为本地锚点。
  9. 根据权利要求8所述的方法，其特征在于，所述第一业务流的用户量统计规则用于指示对本地业务链控制之前的所述第一业务流进行用户量统计，包括：
    所述第一业务流的用户量统计规则用于指示所述用户面网元对来自分流点的所述第一业 务流进行用户量统计；
    或者，所述第一业务流的用户量统计规则用于指示对本地业务链控制之后的所述第一业务流进行用户量统计，包括：
    所述第一业务流的用户量统计规则用于指示所述用户面网元对来自本地数据网络的所述第一业务流进行用户量统计。
  10. 根据权利要求8或9所述的方法，其特征在于，所述第二业务流的用户量统计规则用于指示对本地业务链控制之前的所述第二业务流进行用户量统计，包括：
    所述第二业务流的用户量统计规则用于指示所述用户面网元对来自分流点或远端锚点的所述第二业务流进行用户量统计；
    或者，所述第二业务流的用户量统计规则用于指示对本地业务链控制之后的所述第二业务流进行用户量统计，包括：
    所述第二业务流的用户量统计规则用于指示所述用户面网元对来自本地数据网络的所述第二业务流进行用户量统计。
  11. 根据权利要求1-10任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元获取第一度量策略和第二度量策略；
    所述会话管理网元接收第一用户量统计信息和第二用户量统计信息，所述第一用户量统计信息用于指示本地业务链控制之前的所述第一业务流的用户量，所述第二用户量统计信息用于指示本地业务链控制之后的所述第一业务流的用户量；
    所述会话管理网元根据所述第一度量策略处理所述第一用户量统计信息，以及根据所述第二度量策略处理所述第二用户量统计信息。
  12. 根据权利要求1-11任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元获取第三度量策略和第四度量策略；
    所述会话管理网元接收第三用户量统计信息和第四用户量统计信息，所述第三用户量统计信息用于指示本地业务链控制之前的所述第二业务流的用户量，所述第四用户量统计信息用于指示本地业务链控制之后的所述第二业务流的用户量；
    所述会话管理网元根据所述第三度量策略处理所述第三用户量统计信息，以及根据所述第四度量策略处理所述第四用户量统计信息。
  13. 根据权利要求1-12任一项所述的方法，其特征在于，在所述会话管理网元确定用户量统计规则之前，所述方法还包括：
    所述会话管理网元接收来自策略控制功能网元的第一指示信息；
    所述会话管理网元确定用户量统计规则，包括：
    所述第一指示信息用于指示本地业务链控制之后的第一业务流的大小不发生变化时，所述会话管理网元确定所述第一业务流的用户量统计规则用于指示对本地业务链控制之前的所述第一业务流进行用户量统计，或者，对本地业务链控制之后的所述第一业务流进行用户量统计；
    或者，所述第一指示信息用于指示本地业务链控制之后的第一业务流的大小发生变化时，所述会话管理网元确定所述第一业务流的用户量统计规则用于指示对本地业务链控制之前的所述第一业务流进行用户量统计，以及，对本地业务链控制之后的所述第一业务流进行用户量统计。
  14. 根据权利要求1-13任一项所述的方法，其特征在于，在所述会话管理网元确定用户量统计规则之前，所述方法还包括：
    所述会话管理网元接收来自策略控制功能网元的第二指示信息；
    所述会话管理网元确定用户量统计规则，包括：
    所述第二指示信息用于指示本地业务链控制之后的第二业务流的大小不发生变化时，所述会话管理网元确定所述第二业务流的用户量统计规则用于指示对本地业务链控制之前的所述第二业务流进行用户量统计，或者，对本地业务链控制之后的所述第二业务流进行用户量统计；或者，
    所述第二指示信息用于指示本地业务链控制之后的第二业务流的大小发生变化时，所述会话管理网元确定所述第二业务流的用户量统计规则用于指示对本地业务链控制之前的所述第二业务流进行用户量统计，以及，对本地业务链控制之后的所述第二业务流进行用户量统计。
  15. 一种业务流的用户量统计方法，其特征在于，所述方法包括：
    用户面网元接收来自会话管理网元的用户量统计规则，所述用户量统计规则包括第一业务流的用户量统计规则和/或第二业务流的用户量统计规则，所述第一业务流为需经过本地业务链控制的上行业务流，所述第二业务流为需经过本地业务链控制的下行业务流，所述第一业务流的用户量统计规则用于指示对本地业务链控制之前的所述第一业务流进行用户量统计，和/或，对本地业务链控制之后的所述第一业务流进行用户量统计，所述第二业务流的用户量统计规则用于指示对本地业务链控制之前的所述第二业务流进行用户量统计，和/或，对本地业务链控制之后的所述第二业务流进行用户量统计；
    在所述用户量统计规则包括第一业务流的用户量统计规则的情况下，所述用户面网元根据所述第一业务流的用户量统计规则统计所述第一业务流的用户量；在所述用户量统计规则包括第二业务流的用户量统计规则的情况下，所述用户面网元根据所述第二业务流的用户量统计规则统计所述第二业务流的用户量。
  16. 根据权利要求15所述的方法，其特征在于，所述用户面网元作为分流点。
  17. 根据权利要求15或16所述的方法，其特征在于，所述第一业务流的用户量统计规则用于指示对本地业务链控制之前的所述第一业务流进行用户量统计，包括：
    所述第一业务流的用户量统计规则用于指示所述用户面网元对来自接入网设备的所述第一业务流进行用户量统计；
    或者，所述第一业务流的用户量统计规则用于指示对本地业务链控制之后的所述第一业务流进行用户量统计，包括：
    所述第一业务流的用户量统计规则用于指示所述用户面网元对来自本地锚点的所述第一业务流进行用户量统计。
  18. 根据权利要求16或17所述的方法，其特征在于，所述第二业务流的用户量统计规则用于指示对本地业务链控制之前的第二业务流进行用户量统计，包括：
    所述第二业务流的用户量统计规则用于指示所述用户面网元对来自远端锚点的所述第二业务流进行用户量统计；
    或者，所述第二业务流的用户量统计规则用于指示对本地业务链控制之后的所述第二业务流进行用户量统计，包括：
    所述第二业务流的用户量统计规则用于指示所述用户面网元对来自本地锚点的所述第二业务流进行用户量统计。
  19. 根据权利要求15所述的方法，其特征在于，所述用户面网元作为远端锚点。
  20. 根据权利要求19所述的方法，其特征在于，所述第一业务流的用户量统计规则用于 指示对本地业务链控制之后的所述第一业务流进行用户量统计，包括：
    所述第一业务流的用户量统计规则用于指示所述用户面网元对所述第一业务流进行用户量统计。
  21. 根据权利要求19或20所述的方法，其特征在于，所述第二业务流的用户量统计规则用于指示对本地业务链控制之前的所述第二业务流进行用户量统计，包括：
    所述第二业务流的用户量统计规则用于指示所述用户面网元对所述第二业务流进行用户量统计。
  22. 根据权利要求根据权利要求15所述的方法，其特征在于，所述用户面网元作为本地锚点。
  23. 根据权利要求22所述的方法，其特征在于，所述第一业务流的用户量统计规则用于指示对本地业务链控制之前的所述第一业务流进行用户量统计，包括：
    所述第一业务流的用户量统计规则用于指示所述用户面网元对来自分流点的所述第一业务流进行用户量统计；
    或者，所述第一业务流的用户量统计规则用于指示对本地业务链控制之后的所述第一业务流进行用户量统计，包括：
    所述第一业务流的用户量统计规则用于指示所述用户面网元对来自本地数据网络的所述第一业务流进行用户量统计。
  24. 根据权利要求22或23所述的方法，其特征在于，所述第二业务流的用户量统计规则用于指示对本地业务链控制之前的所述第二业务流进行用户量统计，包括：
    所述第二业务流的用户量统计规则用于指示所述用户面网元对来自分流点或远端锚点的所述第二业务流进行用户量统计；
    或者，所述第二业务流的用户量统计规则用于指示对本地业务链控制之后的所述第二业务流进行用户量统计，包括：
    所述第二业务流的用户量统计规则用于指示所述用户面网元对来自本地数据网络的所述第二业务流进行用户量统计。
  25. 根据权利要求15-24任一项所述的方法，其特征在于，在所述用户量统计规则包括第一业务流的用户量统计规则的情况下，所述方法还包括：
    所述用户面网元向所述会话管理网元发送第一用户量统计信息和/或第二用户量统计信息，所述第一用户量统计信息用于指示本地业务链控制之前的所述第一业务流的用户量，所述第二用户量统计信息用于指示本地业务链控制之后的所述第一业务流的用户量。
  26. 根据权利要求15-25任一项所述的方法，其特征在于，在所述用户量统计规则包括第二业务流的用户量统计规则的情况下，所述方法还包括：
    所述用户面网元向所述会话管理网元发送第三用户量统计信息和/或第四用户量统计信息，所述第三用户量统计信息用于指示本地业务链控制之前的所述第二业务流的用户量，所述第四用户量统计信息用于指示本地业务链控制之后的所述第二业务流的用户量。
  27. 一种通信装置，其特征在于，所述通信装置包括：处理器；
    所述处理器用于读取存储器中的计算机执行指令，并执行所述计算机执行指令，以使所述通信装置执行如权利要求1-14中任一项所述的方法，或者以使所述通信装置执行如权利要求15-26中任一项所述的方法。
  28. 一种通信装置，其特征在于，所述通信装置包括：处理器和存储器；
    所述存储器用于存储计算机执行指令，当所述处理器执行所述计算机执行指令时， 以使所述通信装置执行如权利要求1-14中任一项所述的方法，或者以使所述通信装置执行如权利要求15-26中任一项所述的方法。
  29. 一种通信装置，其特征在于，所述通信装置包括：处理器和接口电路；
    所述接口电路，用于接收计算机执行指令并传输至所述处理器；
    所述处理器用于执行所述计算机执行指令，以使所述通信装置执行如权利要求1-14中任一项所述的方法，或者以使所述通信装置执行如权利要求15-26中任一项所述的方法。
  30. 一种计算机可读存储介质，其特征在于，包括指令，当所述指令在通信装置上运行时，以使所述通信装置执行如权利要求1-14中任一项所述的方法，或者以使所述通信装置执行如权利要求15-26中任一项所述的方法。
  31. 一种计算机程序产品，其特征在于，当所述计算机程序产品在通信装置上运行时，以使所述通信装置执行如权利要求1-14中任一项所述的方法，或者，以使所述通信装置执行如权利要求15-26中任一项所述的方法。
PCT/CN2021/095161 2020-05-29 2021-05-21 业务流的用户量统计方法、装置及系统 WO2021238794A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010479207.7A CN113747483B (zh) 2020-05-29 2020-05-29 业务流的用户量统计方法、装置及系统
CN202010479207.7 2020-05-29

Publications (1)

Publication Number Publication Date
WO2021238794A1 true WO2021238794A1 (zh) 2021-12-02

Family

ID=78725028

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/095161 WO2021238794A1 (zh) 2020-05-29 2021-05-21 业务流的用户量统计方法、装置及系统

Country Status (2)

Country Link
CN (1) CN113747483B (zh)
WO (1) WO2021238794A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109462488A (zh) * 2017-09-06 2019-03-12 中兴通讯股份有限公司 获取用户设备数据流量的方法、会话管理功能及存储介质
WO2019223852A1 (en) * 2018-05-22 2019-11-28 Lenovo (Singapore) Pte. Ltd. Measuring access network performance for a multi-access data connection
CN110703817A (zh) * 2016-03-29 2020-01-17 华为技术有限公司 一种统计流量的控制方法、装置和系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10951427B2 (en) * 2017-10-09 2021-03-16 Comcast Cable Communications, Llc Ethernet type packet data unit session communications
CN110149603B (zh) * 2018-02-13 2020-07-07 华为技术有限公司 一种策略控制方法、设备及系统
WO2020034911A1 (zh) * 2018-08-13 2020-02-20 华为技术有限公司 通信方法和通信装置
CN110933061B (zh) * 2019-11-22 2022-02-18 中国联合网络通信集团有限公司 一种通信方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110703817A (zh) * 2016-03-29 2020-01-17 华为技术有限公司 一种统计流量的控制方法、装置和系统
CN109462488A (zh) * 2017-09-06 2019-03-12 中兴通讯股份有限公司 获取用户设备数据流量的方法、会话管理功能及存储介质
WO2019223852A1 (en) * 2018-05-22 2019-11-28 Lenovo (Singapore) Pte. Ltd. Measuring access network performance for a multi-access data connection

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "Introduction of ATSSS triggers", 3GPP DRAFT; S5-202007, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG5, no. Online Meeting ;20200420 - 20200428, 10 April 2020 (2020-04-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051874695 *

Also Published As

Publication number Publication date
CN113747483B (zh) 2023-07-07
CN113747483A (zh) 2021-12-03

Similar Documents

Publication Publication Date Title
WO2020200066A1 (zh) 获取数据包延迟参数的方法、系统和装置
KR102581335B1 (ko) 서비스 품질 모니터링 방법 및 시스템, 및 디바이스
WO2021227559A1 (zh) 通信方法、装置及系统
WO2021212439A1 (zh) 一种通信方法及装置
WO2019201322A1 (zh) 一种通信方法及相关设备
WO2020169039A1 (zh) 一种策略管理的方法及装置
WO2022007847A1 (zh) 一种通信方法及装置
US11824783B2 (en) Maximum data burst volume (MDBV) determining method, apparatus, and system
WO2021058029A1 (zh) 一种控制业务流传输的方法、装置及系统
CN114586321A (zh) 在通信系统中启用用户面业务分类的节点和方法
US20240236755A1 (en) Traffic routing method, apparatus, and system
US12075283B2 (en) Method and apparatus for providing traffic steering in mobile communication system
WO2021238794A1 (zh) 业务流的用户量统计方法、装置及系统
CN116436862A (zh) 一种通信方法及通信装置
CN114079944A (zh) 通信方法、装置及系统
CN113596909A (zh) 通信方法、装置及系统
JP7534029B2 (ja) データ伝送方法、リンク品質検出方法、通信装置、及び記憶媒体
WO2022267683A1 (zh) 一种通信方法及装置
EP4210381A1 (en) Communication method and apparatus
WO2023185598A1 (zh) 通信方法及装置
WO2024037256A1 (zh) 一种业务流路由方法及装置
WO2022067699A1 (zh) 业务数据流的传输方法、通信装置及通信系统
CN117461382A (zh) 应用于通信系统的方法及通信装置
CN115942362A (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: 21812539

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

Country of ref document: EP

Kind code of ref document: A1