WO2019141171A1 - 一种业务数据流处理方法及其相关设备 - Google Patents

一种业务数据流处理方法及其相关设备 Download PDF

Info

Publication number
WO2019141171A1
WO2019141171A1 PCT/CN2019/071851 CN2019071851W WO2019141171A1 WO 2019141171 A1 WO2019141171 A1 WO 2019141171A1 CN 2019071851 W CN2019071851 W CN 2019071851W WO 2019141171 A1 WO2019141171 A1 WO 2019141171A1
Authority
WO
WIPO (PCT)
Prior art keywords
service data
pcef device
server
data flow
determining
Prior art date
Application number
PCT/CN2019/071851
Other languages
English (en)
French (fr)
Inventor
郭建成
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to JP2020538915A priority Critical patent/JP7207764B2/ja
Priority to EP19741183.8A priority patent/EP3734905B1/en
Publication of WO2019141171A1 publication Critical patent/WO2019141171A1/zh
Priority to US16/931,146 priority patent/US11303761B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8214—Data or packet based

Definitions

  • the present application relates to the field of communications, and in particular, to a service data stream processing method and related devices.
  • UE user equipment
  • 3GPP 3rd Generation Partnership Project
  • UE user equipment
  • PDN public data network
  • EPC evolved core packet network
  • IP internet Protocol
  • the UE and the network establish a connection to the default bearer, which reduces the delay caused by the UE establishing a connection with the network when transmitting and receiving data.
  • the UE When the service request does not require high data packet delay, the UE generally transmits the data packet on the default bearer. If the user initiates a request for a voice call, the default bearer cannot guarantee the transmission delay and packet loss rate. At this time, a dedicated bearer needs to be established. After the voice call ends, the dedicated bearer will be deleted, and the default bearer will remain during the UE connection with the network.
  • the user equipment After the user equipment turns off the cellular mobile data switch, the user equipment cannot actively initiate uplink data transmission, and therefore cannot actively send data to other devices. At this time, some user equipment 4G switches may be in the on mode. In this case, the user context of the unified packet gateway (UCG) device is still active, and the network and the UE are still connected, so the default bearer of the connected user is It can still be used. In this case, if the UCG receives the downlink packet, it will forward it to the UE. The policy and charging enforcement function (PCEF) will perform normal traffic accounting for the transmitted downlink packet. .
  • PCEF policy and charging enforcement function
  • the embodiment of the present application provides a service data stream processing method and a related device thereof, which are used to process a service data flow generated on a default bearer when an uplink network connection is in a disconnected state, so as to reduce data traffic corresponding to the service data flow. cost.
  • a first aspect of the embodiments of the present application provides a service data stream processing method, including:
  • the PCEF device obtains a service data stream, which is sent by the server to the data stream of the default bearer and transmitted through the default bearer.
  • the default bearer is a bearer established when the PDN connection between the server and the UE is in a connected state, and the default bearer exists as long as the PDN connection is not disconnected.
  • the PCEF device When the PCEF device determines that the uplink network connection between the UE and the server is in the disconnected state, the PCEF device processes the service data flow by blocking the transmission of the service data flow or according to presets of the service data flow.
  • the charging method performs charging, wherein blocking the transmission of the service data stream does not perform charging for the service data stream, and charging the service data stream according to a preset charging manner may reduce the data traffic cost of the service data stream. .
  • the PCEF device obtains the service data flow transmitted by the default bearer, and the default bearer is the bearer established when the PDN connection between the server and the UE is in a connected state, and the PCEF device determines the uplink network of the UE and the server.
  • the PCEF device blocks the sending of the service data flow, or the PCEF device charges the service data flow according to a preset charging manner.
  • the PCEF determines the connection state between the UE and the server, so that when the PDN connection between the UE and the server is in a connected state but the uplink network connection is in the closed state, the service data flow is processed to reduce data traffic. The purpose of the fee.
  • the PCEF device determines that the uplink network connection between the UE and the server is in a disconnected state, The method also includes:
  • the PCEF device After the PCEF device determines that the UE generates an abnormal response, it performs a step of determining that the uplink network connection is in an open state.
  • the manner in which the UE determines that the uplink network connection is in the disconnected state is introduced, and the implementability of the solution is increased.
  • the determining, by the PCEF device, whether the UE generates an abnormal response includes:
  • the PCEF device determines whether the UE initiates a request to disconnect the PDN from the server, or the PCEF device determines whether the UE does not respond to the service data flow within a preset duration;
  • the PCEF device determines that the UE initiates a request to disconnect the PDN from the server, or the PCEF device determines that the UE has no
  • the service data flow generates a response, and the PCEF device determines that the UE generates an abnormal response.
  • the method further includes: before the determining, by the PCEF device, that the UE generates an abnormal response, the method further includes: :
  • the PCEF device may determine the preset duration according to at least one of an Internet Protocol IP address, port information, domain name information, and a communication protocol followed by the UE.
  • the manner in which the PCEF device determines the preset duration is introduced, which increases the practicability of the solution.
  • the determining, by the PCEF device, whether the UE generates an abnormal response includes:
  • the service data stream can transmit the packet, and the PCEF device determines whether the number of the packets in the service data stream is greater than a threshold.
  • the threshold value can be set in advance by the PCEF device.
  • the PCEF device determines that the number of packets in the service data flow is greater than a threshold, and the UE does not respond to the service data flow or the UE initiates a request to disconnect the PDN from the server, The PCEF device determines that the UE generates an abnormal response.
  • the PCEF device determines whether the number of packets in the service data flow is greater than Before the threshold, the method further includes:
  • the PCEF device may determine the threshold according to at least one of an Internet Protocol IP address, port information, domain name information, and a communication protocol followed by the UE.
  • the manner in which the PCEF device determines the threshold value is introduced, which increases the practicability of the solution.
  • the data traffic fee corresponding to the preset charging mode is less than the The data traffic charge when the PDN connection and the uplink network connection are in a connected state, the purpose of which is to reduce the data traffic cost of the service data flow.
  • the preset charging mode is described, and the implementability of the solution is increased.
  • the second aspect of the present application provides a policy and charging execution function PCEF device, which includes:
  • the obtaining module may be configured to obtain a service data stream, where the service data stream is a data stream that is sent by the server to the user equipment UE by using a default bearer, where the default bearer is connected to the PDN connection of the public data network of the UE.
  • the default bearer is a bearer established when the PDN connection between the server and the UE is in a connected state, and the default bearer exists as long as the PDN connection is not disconnected.
  • a determining module configured to determine that an uplink network connection between the UE and the server is in an disconnected state
  • the charging module may be configured to block the sending of the service data flow, or charge the service data flow according to a preset charging manner.
  • the sending of the service data stream is not performed, that is, the service data stream is not charged, and the service data stream is charged according to the preset charging manner, so that the data traffic fee of the service data stream can be reduced.
  • the PCEF determines the connection state between the UE and the server, so that when the PDN connection between the UE and the server is in a connected state but the uplink network connection is in the closed state, the service data flow is processed to reduce data traffic.
  • the purpose of the fee is the reason of the fee.
  • the PCEF device further includes:
  • a determining module configured to determine whether the UE generates an abnormal response
  • the executing module may be configured to perform the step of determining that the uplink network connection between the UE and the server is in an disconnected state, if the UE generates an abnormal response.
  • the manner in which the UE determines that the uplink network connection is in the disconnected state is introduced, and the implementability of the solution is increased.
  • the determining module includes:
  • the first determining sub-module may be configured to determine whether the UE initiates a request to disconnect the PDN from the server or determine whether the UE does not respond to the service data flow within a preset duration;
  • a first determining sub-module if the first determining sub-module determines that the UE initiates a request to disconnect the PDN connection with the server, or the UE does not respond to the service data flow, It is used to determine that the UE generates an abnormal response.
  • the determining module further includes:
  • the second determining submodule may be configured to determine the preset duration according to at least one of an internet protocol IP address, port information, domain name information, and a communication protocol followed by the UE.
  • the manner in which the PCEF device determines the preset duration is introduced, which increases the practicability of the solution.
  • the determining module includes:
  • the second determining sub-module may be configured to determine whether the number of the packets in the service data flow is greater than a threshold
  • a third determining submodule if the second determining submodule determines that the number of the packets in the service data flow is greater than a threshold, and the UE does not respond to the service data flow or the UE initiates
  • the request that the server disconnects the PDN connection may be used to determine that the UE generates an abnormal response.
  • the threshold value can be set in advance by the PCEF device.
  • the determining module further includes:
  • the fourth determining submodule may be configured to determine the threshold according to at least one of an Internet Protocol IP address, port information, domain name information, and a communication protocol followed by the UE.
  • the manner in which the PCEF device determines the threshold value is introduced, which increases the practicability of the solution.
  • a third aspect of the present application provides a PCEF device, including: a memory, a transceiver, a processor, and a bus system;
  • the memory is used to store programs and instructions
  • the transceiver is configured to receive or transmit information under control of the processor
  • the processor is configured to execute a program in the memory
  • the bus system is configured to connect the memory, the transceiver, and the processor to cause the memory, the transceiver, and the processor to communicate;
  • the processor is configured to invoke a program instruction in the memory, and execute the method according to any one of the first to sixth implementation manners of the first aspect of the first aspect and the first aspect.
  • a fourth aspect of the present application provides a computer readable storage medium having instructions stored therein that, when executed on a computer, cause the computer to perform the methods described in the above aspects.
  • a fifth aspect of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the various aspects above.
  • 1 is a structural diagram of an EPC core network of an existing LTE system
  • FIG. 2 is a method for processing a service data stream according to an embodiment of the present application
  • FIG. 3 is another method for processing a service data stream according to an embodiment of the present application
  • FIG. 4 is another method for processing a service data stream according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of an embodiment of a PCEF device according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of another embodiment of a PCEF device according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of another embodiment of a PCEF device according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a PCEF device according to an embodiment of the present application.
  • the circuit switched (CS) is mainly used for voice services and video services.
  • the circuit switched domain exclusive channel is used for voice. The channel is released until the end of the call for other users.
  • the switch, CS) domain is also a data exchange domain, which is mainly responsible for data services (such as Internet access), and uses a packet forwarding mechanism. Multiple users share channel resources, which greatly improves resource utilization.
  • the default bearer is also set up in the LTE system.
  • the default bearer is the default data established by the UE after the initial PDP context is established after the UE establishes a radio resource control (RRC) connection.
  • RRC radio resource control
  • the data radio bearer (DRB) if only connected to the data switching domain, has only one default bearer. If it is also connected to an IP multimedia subsystem (IMS), a dedicated bearer of the voice domain is also established.
  • IMS IP multimedia subsystem
  • a situation related to the user's behavior is that when the data transmission requirement is high, the default bearer cannot guarantee the transmission delay, packet loss rate, etc., and a dedicated bearer needs to be established at this time.
  • Mobility management device MME mobility management, session management, user authentication access, and the like.
  • Serving gateway SGW function terminates the interface of the radio access part, is used for bearer and charging of the user, and reorders the base station when the base station switches.
  • PGW terminates the SGi interface for PDN, based on service-based charging, connects to external gateways, and can also perform IP address allocation. Whether the UE is 3GPP or non-3GPP, it needs to pass PGW. The NE can access the PDN. After the default bearer is established, the PGW allocates an IP address to the UE, thereby providing the UE with a "permanent online" function.
  • the PGW can be used as a PCEF device to perform service data flow detection, policy enforcement, and flow-based charging functions.
  • PCRF Policy and charging rules function
  • Home Subscriber Server HSS Supports the primary user database of the IMS network entity used to process the call/session. It contains user profiles, performs user authentication and authorization, and provides information about the user's physical location.
  • SGSN Used for signaling interaction when the 2G/3G and E-UTRAN3GPP access networks move, including the selection of the PGW and the SGW, and the MME selection for the user switching to the E-UTRAN3GPP access network.
  • the access network E-UTRAN consists of a base station.
  • the signaling interaction process is as follows: the UE is connected to the evolved packet core (EPC) through the base station, and the signaling is connected to the MME through the S1-MME interface to perform user registration and authentication, and is determined by the HSS. User validity.
  • the MME sends the default bearer message to the SGW through the S11.
  • the SGW parses the PGW carried on the Domain Name System (DNS) through the access point name (APN).
  • the SGW sends the message through the S5 interface.
  • the PGW is connected to the PGW, and the PGW is connected to the PCRF through the Gx interface, and the user is requested to authorize and charge the policy.
  • the PCRF allocates the charging policy to the PCEF for charging.
  • the UE connects to the SGW through the S1u interface, and is used for user bearer and charging.
  • the PGW accesses the carrier network through the SGi. Through this connection mode, the charging of the service data flow between the UE and the server can be completed.
  • the default bearer is not established in the 2G and 3G systems. Therefore, there is no defect in the embodiment of the present application.
  • the present application is mainly directed to the LTE system.
  • the disadvantages of the embodiments of the present application are not only in the 4G network, but also in the 5G network. Same as it exists. It should be noted that, in any network system, as long as the default bearer is established between the UE and the server, even if the uplink network connection network of the UE is closed, the server can use the default bearer for data transmission.
  • the embodiment of the present application provides a service data stream processing method, where the PCEF device processes the service data stream when the uplink network connection between the UE and the server is disconnected.
  • the PCEF device is a unit on the network device, and mainly includes detection of service data flow, policy execution, and charging function based on the service data flow.
  • the PCEF device obtains a service data stream.
  • the service data stream is forwarded to the UE through the PCEF device, and the PCEF device can charge the service data stream.
  • the PCEF is connected between the UE and the server to forward the service data stream.
  • the service data stream is sent by using a default bearer, and the default bearer is a bearer established when the PDN connection between the server and the UE is in a connected state.
  • the default bearer is a bearer established when the PDN connection between the server and the UE is in a connected state.
  • the 4G switch of the UE is turned on, as described above, the UE and the UE are The server will establish a PDN connection, and then establish a default bearer.
  • the server can still send data to the UE.
  • the service data stream generated at this time will also be acquired by the PCEF device and billed.
  • the UE establishes a PDN connection before establishing a default bearer with the server.
  • the purpose of establishing a PDN connection is to establish a default bearer for a PDN.
  • the UE sends a PDN connection request message to the server, and the message may be included in the attach message.
  • the first default bearer it may not be included in the attached message, but is sent as a separate message, which is not limited herein.
  • the default bearer establishment process is specifically as follows: 1.
  • the default bearer setup process is part of the attach process: the MME sends an actvate default EPS bearen context request and an attach accept message to the UE. If the attach process fails, the UE is invisible. The default bearer activation process is also considered to have failed. 2. If the establishment process of the default bearer is not part of the attach procedure, but is a separate response to the PDN connection request, the MME sends an actvate default EPS bearen context request message to the UE.
  • the UE sends a request to disconnect the PDN connection message.
  • the purpose of the UE is to release the PDN connection, and all the EPS bearer contexts established by the UE are to be released.
  • the specific process is: the UE sends a request to disconnect the PDN connection to the MME.
  • the message includes the EPS bearer identifier of the default bearer of the PDN.
  • the MME sends a disconnected EPS bearer connection request message (including the default bearer identifier of the PDN) to the UE to start the EPS bearer context deactivation process.
  • the default bearer is disconnected only when the PDN connection is released, otherwise it will always exist. If one UE connects multiple PDNs, a default bearer is established for each PDN.
  • EPS bearer (including default bearer) context deactivation process is to deactivate the EPS context bearer or disconnect the PDN connection (the way to disconnect the PDN connection is by deactivating all EPS bearer contexts under the PDN), initiated by the base station, but It may be requested or triggered by the UE through certain processes, such as the UE requesting the bearer modification procedure or the UE requesting the PDN disconnection procedure.
  • the UE also needs to obtain the default bearer resource allocated by the base station, and the base station may allocate a default bearer to the UE by using signaling, such as RRC signaling, physical layer signaling, and MAC layer signaling.
  • signaling such as RRC signaling, physical layer signaling, and MAC layer signaling.
  • the manner in which the base station can allocate the default bearer to the UE by using the signaling may be: the signaling carries the parameter information, where the parameter indicates the frequency domain resource information occupied by the channel resource corresponding to the default bearer.
  • the PCEF performs a charging execution policy sent by the PCRF, and performs charging on the service data flow according to the policy.
  • the network architecture of the core network is similar to the prior art described above, and details are not described herein again.
  • the service data stream sent by the server to the UE through the default bearer may also be received by the UE, but the UE does not generate a normal response to the service data stream.
  • the PCEF device determines that the uplink network connection between the UE and the server is in an disconnected state.
  • the UE may still receive the service data stream sent by the server, but in this state, the UE does not actively send data to the server, nor does it A normal response is sent to the service data stream sent by the server. For example, the UE does not send a data packet to the server based on the handshake protocol, and the data packet is used to notify the server that the UE receives the service data stream successfully.
  • the uplink network connection may be a mobile network connection
  • the mobile network connection may have different names on different user equipments, for example, it is called cellular mobile data on an Apple mobile phone, and is called on Huawei and Samsung mobile phones.
  • the mobile network connection in this embodiment has different names on different devices, but the functions implemented in the embodiment of the present application are similar to the mobile network connection, and more examples are not listed here.
  • the PCEF device blocks the sending of the service data flow, or the PCEF device performs charging according to the preset charging mode.
  • the processing of the service data flow by the PCEF device includes blocking the transmission of the service data flow or performing special charging on the service data flow, wherein blocking the transmission of the service data flow means that the PCEF device does not serve the service.
  • Data is billed.
  • special charging is performed on the service data stream, the data traffic cost generated by the special charging is smaller than the data traffic cost when the PDN connection and the uplink network connection are connected. For example, the data traffic cost when the 4G switch is turned on is less than the cellular. Data traffic charges when both mobile data and 4G switches are turned on.
  • the service data stream sent by the server to the UE is processed when the PDN connection is in the connected state and the uplink network connection is in the closed state, so as to reduce the data traffic cost corresponding to the service data flow, thereby enabling Reduce the traffic charge when the user's upstream network connection is closed.
  • the PCEF device determines whether the uplink network connection of the UE is in the disconnected state, and can determine whether the UE generates an abnormal response to the service data flow. Referring to FIG. 3, description will be made below.
  • the PCEF device obtains a service data stream.
  • the step 301 of the embodiment is similar to the step 201 of the embodiment, and details are not described herein again.
  • the PCEF device determines whether the UE generates an abnormal response.
  • the UE initiates a request to disconnect the PDN from the server. 2. Whether the UE does not respond to the service data flow within the preset duration;
  • the PCEF device determines that the UE has generated an abnormal response.
  • the determination of the preset duration may be determined according to at least one of a UE's Internet Protocol IP address, port information, domain name information, and a communication protocol followed by the UE.
  • the PCEF device determines the cell information and the channel condition of the UE according to the IP address of the UE, distinguishes different UEs, and allocates different preset durations according to different IP addresses.
  • the server allocates different ports and domain names to different UEs
  • the PCEF device allocates different preset durations to the UE according to different ports and domain names.
  • the PCEF device can also allocate different preset durations to the UE according to different communication protocols that the UE follows.
  • the communication protocol in this embodiment may be the L34 protocol.
  • the PCEF device determines whether the number of packets in the service data flow is greater than the first threshold. If yes, and the UE does not respond to the service data flow or the UE initiates a request to disconnect the PDN from the server, the PCEF device determines that the UE generates. Abnormal response.
  • the determining of the first threshold may be determined according to at least one of a UE's Internet Protocol IP address, port information, domain name information, and a communication protocol followed by the UE.
  • the PCEF device determines the cell information and the channel condition of the UE according to the IP address of the UE, distinguishes different UEs, and allocates different first threshold values according to different IP addresses.
  • the server allocates different ports and domain names to different UEs
  • the PCEF device allocates different first thresholds to the UE according to different ports and domain names.
  • the PCEF device may also allocate different first thresholds to the UE according to different communication protocols that the UE follows.
  • the communication protocol in this embodiment may be the L34 protocol.
  • the PCEF device may limit the number of the service data flows before the determination result is generated, so as to reduce the data traffic corresponding to the service data flow as much as possible. Tariff.
  • the PCEF device may save the sever IP list of the service data flow, and if the service data flow initiated by the subsequent server matches the list, directly determine It is an abnormal service data flow, and processes the service data flow to reduce the data traffic cost corresponding to the service data flow, without judging whether the UE generates an abnormal response.
  • the PCEF device determines that the uplink network connection between the UE and the server is in an disconnected state.
  • the uplink network connection in this embodiment is similar to the uplink network connection in step 202 of the embodiment, and details are not described herein again.
  • the PCEF device blocks the transmission of the service data flow, or the PCEF device performs the charging on the service data flow according to the preset charging mode.
  • the step 304 of the embodiment is similar to the step 202 of the embodiment, and details are not described herein again.
  • the UE when the UE is in an abnormal response, it is determined that the uplink network connection between the server and the UE is in an disconnected state, and several cases of abnormal response are analyzed, which increases the implementability of the solution.
  • the embodiment of the present application for the service data flow initiated by the service server, continuously changing the output port of the service data flow may evade the judgment of the abnormal response status of the UE. Therefore, the embodiment of the present application further proposes another service data stream processing method, which does not judge whether the UE generates an abnormal response, and only increases the restriction on the service data stream. Please refer to FIG. 4, which will be described below.
  • the PCEF device obtains a service data flow.
  • the PCEF device determines whether the number of service data flows exceeds a second threshold.
  • the PCEF device determines whether the number of service data flows exceeds the second threshold.
  • the PCEF device blocks the sending of the service data flow, or the PCEF device performs the charging according to the preset charging mode.
  • the PCEF device processes the service data stream whose number of service data flows exceeds the second threshold value, and the processing manner is similar to the step 202 of the embodiment, which may be to prevent the service data stream from being sent. Or special charging for the service data flow, which will not be described here.
  • the service data flow initiated by the server is restricted, and the malicious tool traffic is prevented from generating huge bills.
  • the embodiment of the present application is described in the following with reference to FIG. 5 from the perspective of a service data stream processing method.
  • the following describes the embodiment of the present application from the perspective of a PCEF device.
  • the obtaining module 501 is configured to obtain a service data stream, where the service data stream is a data stream that is sent by the server to the user equipment UE by using a default bearer, where the default bearer is connected to the PDN connection of the public data network of the UE.
  • a determining module 502 configured to determine that an uplink network connection between the UE and the server is in an disconnected state
  • the charging module 503 is configured to block the sending of the service data flow, or perform charging on the service data flow according to a preset charging manner.
  • the service data stream sent by the server to the UE is processed when the PDN connection is in the connected state and the uplink network connection is in the closed state, so as to reduce the data traffic cost corresponding to the service data flow, thereby enabling Reduce the traffic charge when the user's upstream network connection is closed.
  • the manner in which the PCEF device determines that the uplink network connection between the UE and the server is in the disconnected state is to determine whether the UE has generated an abnormal response. Referring to FIG. 6, description will be made below.
  • the obtaining module 601 is configured to obtain a service data stream, where the service data stream is a data stream that is sent by the server to the user equipment UE by using a default bearer, where the default bearer is connected to the PDN connection of the public data network of the UE.
  • the determining module 602 is configured to determine whether the UE generates an abnormal response.
  • the executing module 603 is configured to perform the step of determining that the uplink network connection between the UE and the server is in an disconnected state, if the UE generates an abnormal response.
  • a determining module 604 configured to determine that an uplink network connection between the UE and the server is in an disconnected state
  • the charging module 605 is configured to block the sending of the service data flow, or charge the service data flow according to a preset charging manner.
  • determining whether the uplink network connection is in an off state by determining whether the UE generates an abnormal response increases the implementability of the solution.
  • the obtaining module 701 is configured to obtain a service data stream, where the service data stream is a data stream that is sent by the server to the user equipment UE by using a default bearer, where the default bearer is connected to the PDN connection of the public data network of the UE.
  • the determining module 702 is configured to determine whether the UE generates an abnormal response.
  • the executing module 703 is configured to perform the step of determining that the uplink network connection between the UE and the server is in an disconnected state, if the UE generates an abnormal response.
  • a determining module 704 configured to determine that an uplink network connection between the UE and the server is in an disconnected state
  • the charging module 705 is configured to block the sending of the service data flow, or charge the service data flow according to a preset charging manner.
  • the UE initiates a request to disconnect the PDN from the server. 2. Whether the UE does not respond to the service data flow within the preset duration;
  • the determining module 702 includes:
  • the first determining sub-module 7022 is configured to determine whether the UE initiates a request to disconnect the PDN from the server, or determine whether the UE does not respond to the service data flow within a preset duration;
  • a first determining sub-module 7023 if the first determining sub-module 7021 determines that the UE initiates a request to disconnect the PDN connection with the server, or the UE does not respond to the service data flow, Then, it is used to determine that the UE generates an abnormal response.
  • the judgment module further includes:
  • the second determining sub-module 7021 is configured to determine the preset duration according to at least one of an Internet Protocol IP address, port information, domain name information, and a communication protocol followed by the UE.
  • the PCEF device determines whether the number of packets in the service data flow is greater than the first threshold. If yes, and the UE does not respond to the service data flow or the UE initiates a request to disconnect the PDN from the server, the PCEF device determines that the UE generates. Abnormal response.
  • the determining module 702 includes:
  • the second determining sub-module 7025 is configured to determine whether the number of the packets in the service data flow is greater than a threshold
  • a third determining sub-module 7026 if the second determining sub-module 7023 determines that the number of the packets in the service data flow is greater than a threshold, and the UE does not respond to the service data flow or the UE initiates A request to disconnect the PDN connection from the server is used to determine that the UE generates an abnormal response.
  • the judgment module further includes:
  • the fourth determining sub-module 7024 is configured to determine the threshold according to at least one of an Internet Protocol IP address, port information, domain name information, and a communication protocol followed by the UE.
  • FIG. 8 is a schematic diagram of a PCEF device according to an embodiment of the present disclosure.
  • the PCEF device 800 includes a browser, and the PCEF device 800 may generate a large difference due to different configurations or performances, and may include one or more central processing units (Central processing units (CPU) 822 (eg, one or more processors) and memory 832, one or more storage media 830 storing application 842 or data 844 (eg, one or one storage device in Shanghai).
  • the memory 832 and the storage medium 830 may be short-term storage or persistent storage.
  • Programs stored on storage medium 830 may include one or more modules (not shown), each of which may include a series of instruction operations in a PCEF device.
  • central processor 822 can be configured to communicate with storage medium 830, executing a series of instruction operations in storage medium 830 on PCEF device 800.
  • the central processing unit 822 can perform the following steps according to the instruction operation:
  • the service data stream is a data stream that is sent by the server to the user equipment UE by using a default bearer, where the default bearer is a bearer established when the server is connected to the public data network PDN of the UE;
  • the sending of the service data flow is blocked, or the PCEF device charges the service data flow according to a preset charging manner.
  • PCEF device 800 may also include one or more power supplies 826, one or more wired or wireless network interfaces 850, one or more input and output interfaces 858, and/or one or more operating systems 841, such as Windows ServerTM, Mac. OS XTM, UnixTM, LinuxTM, FreeBSDTM and more.
  • operating systems 841 such as Windows ServerTM, Mac. OS XTM, UnixTM, LinuxTM, FreeBSDTM and more.
  • the steps performed by the PCEF device in the above embodiment may be based on the PCEF device structure shown in FIG.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of cells is only a logical function division. In actual implementation, there may be another division manner. For example, multiple units or components may be combined or integrated. Go to another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • An integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, can be stored in a computer readable storage medium.
  • the instructions include a plurality of instructions for causing a computer device (which may be a personal computer, a local client, or a network device, etc.) to perform all or part of the steps of the various embodiments of Figures 2 through 4 of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program code. .

Abstract

本申请实施例提供了一种业务数据流处理方法及其相关设备，用于对上行网络连接处于断开状态时默认承载上产生的业务数据流进行处理，以降低该业务数据流对应的数据流量费用。本申请实施例方法包括：策略及计费执行功能PCEF设备获取业务数据流，所述业务数据流为服务器利用默认承载发送至用户设备UE的数据流，所述默认承载为所述服务器与所述UE的公共数据网PDN连接处于连接状态时建立的承载；所述PCEF设备确定所述UE与所述服务器的上行网络连接处于断开状态；所述PCEF设备阻止所述业务数据流的发送，或，所述PCEF设备对所述业务数据流按照预置计费方式进行计费。

Description

一种业务数据流处理方法及其相关设备
本申请要求于2018年1月17日提交中国国家知识产权局、申请号为201810046643.8、发明名称为“一种业务数据流处理方法及其相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种业务数据流处理方法及其相关设备。
背景技术
第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)标准协议中，用户设备(user equipment，UE)与服务器间通过数据传输进行通信，用户发送上行数据至服务器，服务器通过发送下行数据进行响应。在LTE系统中，从UE附着网络的过程中会建立公共数据网(public data network，PDN)连接，PDN连接指UE与演进的核心分组网(evolved packet core，EPC)之间的互联网协议(internet protocol，IP)连接，PDN连接会触发UE与网络间建立默认承载，只要默认承载存在，IP连接也不会中断。UE与网络通过给默认承载建立连接，降低了UE在收发数据时再与网络建立连接而导致的时延。当业务请求对数据包时延要求不高时，UE一般会在默认承载上进行数据包的传输，如果用户发起了语音呼叫等请求，由于默认承载无法保证传输时延、丢包率等要求，此时需要建立专有承载，在语音通话结束后，专有承载将会被删除，而默认承载会在UE与网络连接期间一直保留。
用户设备在关闭蜂窝移动数据开关后，无法主动发起上行数据的传输，因此无法主动向其它设备发送数据。此时一些用户设备4G开关可能处于开启模式，这种情况下，统一分组网关(unified packet gateway，UCG)设备上用户上下文仍处于激活状态，网络与UE仍然处于连接状态，因此连接用户的默认承载仍可以使用，此时，若UCG收到下行报文，会正常转发给UE，策略及计费执行功能(policy and charging enforcement function，PCEF)会对传输的该下行报文进行正常的流量计费。
可见，3GPP标准协议中只要UE附着网络，就会建立默认承载，因此会导致某些用户在关闭蜂窝移动数据开关但未关闭4G开关时，服务器仍然会通过默认承载发送下行报文至UE，PCEF对该报文进行正常计费导致这些用户的流量计费金额增加。
发明内容
本申请实施例提供了一种业务数据流处理方法及其相关设备，用于对上行网络连接处于断开状态时默认承载上产生的业务数据流进行处理，以降低该业务数据流对应的数据流量费用。
本申请实施例的第一方面提供了一种业务数据流处理方法，其特征在于，包括：
PCEF设备获取业务数据流，该业务数据流为服务器发送至默认承载的数据流且通过 默认承载进行传输。
在本实施例中，默认承载为服务器与UE的PDN连接处于连接状态时建立的承载，只要PDN连接没有断开，默认承载就一直存在。
当PCEF设备确定UE与服务器的上行网络连接处于断开状态时，PCEF设备对该业务数据流进行处理，处理的方式可以是阻止该业务数据流的发送或者对该业务数据流按照预置的计费方式进行计费，其中，阻止该业务数据流的发送即不对该业务数据流进行计费，对该业务数据流按照预置的计费方式进行计费可以降低该业务数据流的数据流量费用。
本申请实施例具有以下优点：PCEF设备获取通过默认承载传输的业务数据流，该默认承载为服务器与UE的PDN连接处于连接状态时建立的承载，当所述PCEF设备确定UE与服务器的上行网络连接处于断开状态时，所述PCEF设备阻止所述业务数据流的发送，或，所述PCEF设备对所述业务数据流按照预置计费方式进行计费。在本实施例中，PCEF通过对UE与服务器连接状态的判断，从而达到在UE与服务器的PDN连接处于连接状态但是上行网络连接处于关闭状态时，对上述业务数据流进行处理以达到减少数据流量费用的目的。
基于第一方面，在本申请实施例的第一方面的第一种实现方式中，其特征在于，所述PCEF设备确定所述UE与所述服务器的上行网络连接处于断开状态之前，所述方法还包括：
所述PCEF设备判断所述UE是否产生异常响应；
当PCEF设备确定UE产生异常响应后，则执行确定该上行网络连接处于断开状态的步骤。
在本实施例中，介绍了UE确定上行网络连接处于断开状态的方式，增加了方案的可实施性。
基于第一方面的第一种实现方式，在本申请实施例的第一方面的第二种实现方式中，其特征在于，所述PCEF设备判断所述UE是否产生异常响应包括：
所述PCEF设备判断所述UE是否发起与所述服务器断开所述PDN连接的请求，或，所述PCEF设备判断预置时长内所述UE是否没有对所述业务数据流产生响应；
若满足上述两种情况中的任一种，即PCEF设备确定所述UE发起与所述服务器断开所述PDN连接的请求，或，所述PCEF设备确定预置时长内所述UE没有对所述业务数据流产生响应，则所述PCEF设备确定所述UE产生异常响应。
在本实施例中，对PCEF设备确定UE产生异常响应的一种方式进行了说明，增加了方案的灵活性。
基于第一方面的第二种实现方式，在本申请实施例的第一方面的第三种实现方式中，其特征在于，所述PCEF设备确定所述UE产生异常响应之前，所述方法还包括：
所述PCEF设备可以根据所述UE的互联网协议IP地址、端口信息、域名信息和所述UE所遵循的通信协议中的至少一个确定所述预置时长。
在本实施例中，介绍了PCEF设备确定预置时长的方式，增加了方案的实用性。
基于第一方面的第一种实现方式，在本申请实施例的第一方面的第四种实现方式中， 其特征在于，所述PCEF设备判断所述UE是否产生异常响应包括：
业务数据流可以传输报文，PCEF设备判断业务数据流中的报文个数是否大于门限值；
在本实施例中，门限值可以由PCEF设备事先设置。
若PCEF设备判断业务数据流中的报文个数大于门限值，且所述UE没有对所述业务数据流产生响应或所述UE发起与所述服务器断开所述PDN连接的请求，所述PCEF设备确定所述UE产生异常响应。
在本实施例中，对PCEF设备确定UE产生异常响应的另一种方式进行了说明，增加了方案的灵活性。
基于第一方面的第四种实现方式，在本申请实施例的第一方面的第五种实现方式中，其特征在于，所述PCEF设备判断所述业务数据流中的报文个数是否大于门限值之前，所述方法还包括：
所述PCEF设备可以根据所述UE的互联网协议IP地址、端口信息、域名信息和所述UE遵循的通信协议中的至少一个确定所述门限值。
在本实施例中，介绍了PCEF设备确定门限值的方式，增加了方案的实用性。
基于第一方面及其第一方面的第一种至第五种实现方式，在本申请实施例的第一方面的第六种实现方式中，预置计费方式对应的数据流量费用小于所述PDN连接和所述上行网络连接处于连接状态时的数据流量费用，其目的是减少业务数据流的数据流量费用。
在本实施例，对预置计费方式进行了说明，增加了方案的可实施性。
本申请的第二方面提供了一种策略及计费执行功能PCEF设备，其特征在于，包括：
获取模块，可以用于获取业务数据流，所述业务数据流为服务器利用默认承载发送至用户设备UE的数据流，所述默认承载为所述服务器与所述UE的公共数据网PDN连接处于连接状态时建立的承载；
在本实施例中，默认承载为服务器与UE的PDN连接处于连接状态时建立的承载，只要PDN连接没有断开，默认承载就一直存在。
确定模块，可以用于确定所述UE与所述服务器的上行网络连接处于断开状态；
计费模块，可以用于阻止所述业务数据流的发送，或，对所述业务数据流按照预置计费方式进行计费。其中，阻止该业务数据流的发送即不对该业务数据流进行计费，对该业务数据流按照预置的计费方式进行计费可以降低该业务数据流的数据流量费用。
在本实施例中，PCEF通过对UE与服务器连接状态的判断，从而达到在UE与服务器的PDN连接处于连接状态但是上行网络连接处于关闭状态时，对上述业务数据流进行处理以达到减少数据流量费用的目的。
基于第二方面，在第二方面的第一种实现方式中，其特征在于，所述PCEF设备还包括：
判断模块，可以用于判断所述UE是否产生异常响应；
执行模块，若所述UE产生异常响应，则可以用于执行确定所述UE与所述服务器的上行网络连接处于断开状态的步骤。
在本实施例中，介绍了UE确定上行网络连接处于断开状态的方式，增加了方案的可实施性。
基于第二方面的第一种实现方式，在第二方面的第二种实现方式中，其特征在于，所述判断模块包括：
第一判断子模块，可以用于判断所述UE是否发起与所述服务器断开所述PDN连接的请求或判断预置时长内所述UE是否没有对所述业务数据流产生响应；
第一确定子模块，若第一判断子模块判断得到所述UE发起与所述服务器断开所述PDN连接的请求或预置时长内所述UE没有对所述业务数据流产生响应，则可以用于确定所述UE产生异常响应。
在本实施例中，对PCEF设备确定UE产生异常响应的一种方式进行了说明，增加了方案的灵活性。
基于第二方面的第二种实现方式，在本申请实施例的第二方面的第三种实现方式中，其特征在于，所述判断模块还包括：
第二确定子模块，可以用于根据所述UE的互联网协议IP地址、端口信息、域名信息和所述UE所遵循的通信协议中的至少一个确定所述预置时长。
在本实施例中，介绍了PCEF设备确定预置时长的方式，增加了方案的实用性。
基于第二方面，在第二方面的第四种实现方式中，其特征在于，所述判断模块包括：
第二判断子模块，可以用于判断所述业务数据流中的报文个数是否大于门限值；
第三确定子模块，若第二判断子模块判断得到所述业务数据流中的报文个数大于门限值，且所述UE没有对所述业务数据流产生响应或所述UE发起与所述服务器断开所述PDN连接的请求，则可以用于确定所述UE产生异常响应。
在本实施例中，门限值可以由PCEF设备事先设置。
在本实施例中，对PCEF设备确定UE产生异常响应的另一种方式进行了说明，增加了方案的灵活性。
基于第二方面的第四种实现方式，在第二方面的第五种实现方式中，其特征在于，所述判断模块还包括：
第四确定子模块，可以用于根据所述UE的互联网协议IP地址、端口信息、域名信息和所述UE遵循的通信协议中的至少一个确定所述门限值。
在本实施例中，介绍了PCEF设备确定门限值的方式，增加了方案的实用性。
本申请的第三方面提供了一种PCEF设备，其特征在于，包括：存储器、收发器、处理器以及总线系统；
其中，所述存储器用于存储程序和指令；
所述收发器用于在所述处理器的控制下接收或发送信息；
所述处理器用于执行所述存储器中的程序；
所述总线系统用于连接所述存储器、所述收发器以及所述处理器，以使所述存储器、所述收发器以及所述处理器进行通信；
其中，所述处理器用于调用所述存储器中的程序指令，执行如权利要求第一方面及其第一方面的第一种至第六种实现方式中任一种实现方式所述的方法。
本申请的第四方面提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
本申请的第五方面提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
附图说明
图1为现有LTE系统EPC核心网组成结构图；
图2为本申请实施例的一种业务数据流处理方法；
图3为本申请实施例的另一种业务数据流处理方法；
图4为本申请实施例的另一种业务数据流处理方法；
图5为本申请实施例PCEF设备的一种实施例示意图；
图6为本申请实施例PCEF设备的另一种实施例示意图；
图7为本申请实施例PCEF设备的另一种实施例示意图；
图8为本申请实施例PCEF设备的一种实体结构图。
具体实施方式
在2G、3G系统中，电路交换域(circuit switched，CS)主要用于语音业务、视频业务，电路交换域独占信道用于语音，直到通话结束才释放信道，供其他用户使用；分组交换(packet switch，CS)域也是数据交换域，主要负责数据业务(例如上网)，采用分组转发机制，多个用户共用信道资源，使得资源利用率大大提高。
4G系统，也就是长期演进(Long Term Evolution，LTE)系统中没有CS域，只有PS域。LTE中所有的语音业务将以VoIP(voice over internet protocol)的方式进行的，即以数据封包的形式在IP网络上做实时传递。与2G、3G不同，在LTE系统中还会建立默认承载，默认承载就是UE与无线资源控制(radio resource control，RRC)连接建立后，初始PDP上下文建立时，核心网为UE缺省建立的数据无线承载(data radio bearer DRB)，如果只连接到数据交换域，那么只有一个默认承载，如果还连接到IP多媒体系统(IP multimedia subsystem，IMS)，那么还会建立语音域的专用承载。与用户的行为(比如发起语音通话)相关的一种情况为，当数据传输的要求较高时，由于默认承载无法保证传输时延、丢包率等要求，此时还需要建立专用承载。
现有LTE系统EPC核心网的介绍如图1所示，首先对各个网元进行简单介绍：
1、移动管理设备MME的功能：移动性管理、会话管理、用户鉴权接入等。
2、服务网关SGW功能：终结无线接入部分的接口，用于用户的承载与计费，基站切换时对基站进行重新排序。
3、PGW(PDN-GW)：终结面向PDN的SGi接口，基于业务的计费，连接外部的网关，还可以进行IP地址分配，无论UE是3GPP接入还是非3GPP接入，都需要经过PGW网元才能接入到PDN。默认承载建立后PGW为UE分配IP地址，从而为UE提供“永久在线”的功能。PGW可以作为PCEF设备，进行业务数据流的检测、策略执行和基于流的计费功能等。
4、策略与计费规则功能(policy and charging rules function，PCRF)设备：业务数据流和IP承载资源的策略与计费控制策略决策点，它为PCEF选择及提供可用的策略 和计费控制决策。
5、归属用户服务器HSS：支持用于处理调用/会话的IMS网络实体的主要用户数据库。它包含用户配置文件，执行用户的身份验证和授权，并可以提供有关用户物理位置的信息。
6、SGSN：用于2G/3G和E-UTRAN3GPP接入网间移动时进行信令交互，包括对PGW和SGW的选择，同时为切换到E-UTRAN3GPP接入网的用户进行MME选择。
接入网E-UTRAN由基站构成。
如图所示的信令交互过程为：UE通过基站连接到演进分组核心网((evolved packet core，EPC)，信令通过S1-MME接口与MME连接，进行用户注册、鉴权，在HSS判断用户合法性。MME通过S11发送默认承载的消息给SGW，SGW通过接入点(access point name，APN)在域名系统(Domain Name System，DNS)上解析出所承载的PGW，SGW通过S5接口把消息发送给PGW，PGW通过Gx接口与PCRF连接，对用户请求授权、计费策略分配，PCRF分配计费策略给PCEF进行计费，UE通过S1u接口与SGW连接，用于用户的承载与计费，PGW通过SGi接入运营商网络。通过这种连接方式，可以完成UE与服务器间业务数据流的计费。
在2G、3G系统中不会建立默认承载，因此不存在本申请实施例的缺陷，本申请主要针对LTE系统而言，本申请实施例的缺点不止在4G网络中存在，同样在5G网络中也一样存在。需要说明的是，不管在哪一种网络系统中，只要UE与服务器间建立默认承载，即使UE的上行网络连接网络关闭，服务器也可利用默认承载进行数据传输。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本申请实施例提供了一种业务数据流处理方法，用于当UE与服务器的上行网络连接处于断开状态时，PCEF设备对业务数据流进行处理。
在本实施例中，PCEF设备是网络设备上的一个单元，主要包含业务数据流的检测、策略执行和基于业务数据流的计费功能。
201、策略及执行计费功能PCEF设备获取业务数据流。
服务器与UE进行业务数据流的传输的过程中，该业务数据流会经过PCEF设备再转发至UE，PCEF设备可以对该业务数据流进行计费。
PCEF连接在UE与服务器之间，进行业务数据流的转发。
在本实施例中，该业务数据流通过默认承载进行发送，默认承载是在服务器与UE的PDN连接处于连接状态时建立的承载，在UE的4G开关打开时，如前面所描述的，UE与服务器建会建立PDN连接，随后建立默认承载，服务器仍然可以向UE发送数据，此时产生的业务数据流也会被PCEF设备获取并执行计费。
在本实施例中，UE与服务器建立默认承载之前要建立PDN连接，建立PDN连接的目的是为一个PDN建立一个默认承载，首先UE发送PDN连接请求消息至服务器，该消息可以包含在附着消息中以便建立第一个默认承载，也可以不包含在附着消息中，而是作为一条单独的消息发送，具体此处不作限定。
在本实施例中，默认承载的建立过程具体为：1、默认承载的建立过程是附着流程的一部分：MME发送actvate default EPS bearen context request和attach accept消息给UE，如果附着流程失败，那么UE隐形的认为默认承载激活流程也是失败的。2、如果默认承载的建立过程不是附着流程的一部分，而是单独的作为PDN连接请求的响应，那么MME发送actvate default EPS bearen context request消息给UE。
UE发送请求断开PDN连接消息的目的是UE为了断开一个PDN连接，那么这个UE所建立的所有EPS承载上下文都要被释放，具体过程为：UE发送断开PDN连接的请求至MME，该消息包含了PDN的默认承载的EPS承载标识，MME收到消息后，发送断开EPS承载连接请求消息(包含PDN的默认承载标识)给UE，以启动EPS承载上下文去激活过程。
在本申请实施例中，默认承载只有PDN连接被释放时才会断开，否则将一直存在，一个UE如果连接了多个PDN，就要给每个PDN建立一个默认承载。EPS承载(包括默认承载)上下文去激活的过程是为了去激活EPS上下文承载或断开PDN连接(断开PDN连接的方式是通过去激活该PDN下的所有EPS承载上下文)，由基站发起，但可以被UE通过某些流程请求或触发，比如UE请求承载修改流程或UE请求PDN断开连接流程。
在本实施例中，UE还需要获取基站分配的默认承载资源，基站可以通过信令为UE分配默认承载，例如RRC信令、物理层信令、MAC层信令。
在本实施例中，基站可以通过信令为UE分配默认承载的方式可以是，该信令中携带参数信息，该参数指示了默认承载对应的信道资源占用的频域资源信息。
在本实施例中，PCEF执行PCRF发送的计费执行策略，并按照此策略对业务数据流进行计费。
在本实施例中，核心网的网络架构与上述所述的现有技术类似，具体此处不再赘述。
在本实施例中，服务器通过默认承载发送给UE的业务数据流也可以被UE接收到，但UE不会对该业务数据流产生正常响应。
202、PCEF设备确定UE与服务器的上行网络连接处于断开状态；
在本实施例中，当UE与服务器的上行网络连接处于断开状态时，UE仍然可以收到服务器发送的该业务数据流，但是这种状态下UE不会主动向服务器发送数据，也不会对服务器发送的该业务数据流产生正常响应，例如UE不会基于握手协议，给服务器发送数据报文，该数据报文用于告知服务器UE接收业务数据流成功。
在本实施例中，上行网络连接可以为移动网络连接，移动网络连接在不同的用户设备上可能有不同的名称，例如在苹果手机上被称为蜂窝移动数据，在华为、三星手机上被称为移动数据，因此本实施例中的移动网络连接在不同的设备上名称不同，但在本申请实施例中实现的功能与移动网络连接类似，更多的例子具体此处不再列举。
203、PCEF设备阻止业务数据流的发送，或，PCEF设备对业务数据流按照预置计费方式进行计费。
在本申请实施例中，PCEF设备对业务数据流的处理包括阻止该业务数据流的发送或对该业务数据流进行特殊计费，其中，阻止该业务数据流的发送意味着PCEF设备不对该业务数据进行计费。而对该业务数据流进行特殊计费时，特殊计费产生的数据流量费用小于PDN连接和上行网络连接都处于连接状态时的数据流量费用，例如：只有4G开关打开时的数据流量费用小于蜂窝移动数据和4G开关都打开时的数据流量费用。
在本申请实施例中，通过对PDN连接处于连接状态而上行网络连接处于关闭状态时的由服务器发送给UE的业务数据流进行处理，以达到降低该业务数据流对应的数据流量费用，从而能减免用户的上行网络连接处于关闭状态时的流量资费。
在本实施例中PCEF设备判断UE的上行网络连接是否处于断开状态可以通过判断UE是否对该业务数据流产生异常响应，请参照图3，下面将进行说明。
301、策略及执行计费功能PCEF设备获取业务数据流。
在本申请实施例中，实施例步骤301与实施例步骤201类似，具体此处不再赘述。
302、PCEF设备判断UE是否产生异常响应；
在本实施例中，PCEF设备判断UE是否产生异常响应的方式有两种，下面将进行说明。
一、PCEF设备对UE与服务器的数据交互进行监控的过程中1、检测到UE发起与服务器断开PDN连接的请求。2、预置时长内UE是否没有对业务数据流产生响应；
当满足上述两种情况中的任一种时，PCEF设备确定UE产生了异常响应。
可以理解的是，除了上述两种情况，可能还存在其他情况也可以被认为是UE产生了异常响应，具体此处不作限定。
在本方式中，预置时长的确定可以根据UE的互联网协议IP地址、端口信息、域名信息和UE所遵循的通信协议中的至少一个确定。
具体为，不同的IP地址(或应用)的行为特征可能不一样，需要区分处理。PCEF设备根据UE的IP地址判断该UE所处于小区信息及其信道情况，区分不同的UE，并根据不同IP地址的分配不同的预置时长。
同样的，服务器分配不同的端口、域名给不同的UE，PCEF设备根据端口和域名的不同为UE分配不同的预置时长。
同样的，PCEF设备也可以根据UE所遵循的通信协议不同为UE分配不同的预置时长，在本实施例中的通信协议可以为L34协议。
二、PCEF设备判断业务数据流中的报文个数是否大于第一门限值，若是，且UE没有对业务数据流产生响应或UE发起与服务器断开PDN连接的请求，PCEF设备确定UE产生异常响应。
在本方式中，第一门限值的确定可以根据UE的互联网协议IP地址、端口信息、域名信息和UE所遵循的通信协议中的至少一个确定。
具体为，不同的IP地址(或应用)的行为特征可能不一样，需要区分处理。PCEF设备根据UE的IP地址判断该UE所处于小区信息及其信道情况，区分不同的UE，并根据IP地址不同分配不同的第一门限值。
同样的，服务器分配不同的端口、域名给不同的UE，PCEF设备根据端口和域名的不 同为UE分配不同的第一门限值。
同样的，PCEF设备也可以根据UE所遵循的通信协议不同为UE分配不同的第一门限值，在本实施例中的通信协议可以为L34协议。
在本实施例中，在PCEF设备判断UE是否产生正常响应的过程中，在判断结果产生之前，PCEF设备可以限制该业务数据流的个数，以便尽可能的减少该业务数据流对应的数据流量资费。
在本实施例中，PCEF设备判断UE对该业务数据流产生异常响应后，可以保存该业务数据流的sever IP名单，后续服务器再发起的业务数据流，如果与该名单相匹配，则直接判断为异常业务数据流，并对业务数据流进行处理，以降低该业务数据流对应的数据流量费用，而不用再对UE是否产生异常响应进行判断。
303、若UE产生异常响应，PCEF设备确定UE与服务器的上行网络连接处于断开状态。
在本实施例中的上行网络连接与实施例步骤202中的上行网络连接类似，具体此处不再赘述。
304、PCEF设备阻止业务数据流的发送，或，PCEF设备对业务数据流按照预置计费方式进行计费。
在本申请实施例中，实施例步骤304与实施例步骤202类似，具体此处不再赘述。
在本实施例中，当UE处于异常响应时，确定服务器与UE的上行网络连接处于断开状态，并对异常响应的几种情况进行了分析，增加了方案的可实施性。
在本申请实施例中，对于业务服务器主动发起的业务数据流，不断变化业务数据流的输出端口，可能规避掉对UE异常响应状况的判断。因此，本申请实施例还提出了另一种业务数据流处理方法，不对UE是否产生异常响应进行判断，仅增加对该业务数据流的限制，请参照图4，下面将进行说明。
401、PCEF设备获取业务数据流。
实施例401所执行的步骤与实施例步骤201类似，具体此处不再赘述。
402、PCEF设备判断业务数据流的个数是否超过第二门限值；
在本实施例中当有多条业务数据流时，即服务器向UE进行发起了多条业务数据流，PCEF设备判断业务数据流的个数是否超过第二门限值。
403、PCEF设备阻止业务数据流的发送，或，PCEF设备对业务数据流按照预置计费方式进行计费。
在本实施例中，对业务数据流的个数超过第二门限值的业务数据流，PCEF设备对其进行处理，处理的方式与实施例步骤202类似，可以是阻止该业务数据流的发送或对该业务数据流进行特殊计费，具体此处不再赘述。
在本实施例中，通过限制服务器并行发起的业务数据流的个数，从而实现对服务器主动发起的业务数据流进行限制，避免恶意工具流量产生巨额话单。
上面图2至图4从一种业务数据流处理方法的角度对本申请实施例进行了叙述，请参照图5，下面将从PCEF设备的角度对本申请实施例进行说明。
获取模块501，用于获取业务数据流，所述业务数据流为服务器利用默认承载发送 至用户设备UE的数据流，所述默认承载为所述服务器与所述UE的公共数据网PDN连接处于连接状态时建立的承载；
确定模块502，用于确定所述UE与所述服务器的上行网络连接处于断开状态；
计费模块503，用于阻止所述业务数据流的发送，或，对所述业务数据流按照预置计费方式进行计费。
在本申请实施例中，通过对PDN连接处于连接状态而上行网络连接处于关闭状态时的由服务器发送给UE的业务数据流进行处理，以达到降低该业务数据流对应的数据流量费用，从而能减免用户的上行网络连接处于关闭状态时的流量资费。
在本实施例中，PCEF设备确定UE与服务器的上行网络连接处于断开状态的方式是判断UE是否产生了异常响应，请参照图6，下面将进行说明。
获取模块601，用于获取业务数据流，所述业务数据流为服务器利用默认承载发送至用户设备UE的数据流，所述默认承载为所述服务器与所述UE的公共数据网PDN连接处于连接状态时建立的承载；
判断模块602，用于判断所述UE是否产生异常响应；
执行模块603，若所述UE产生异常响应，则用于执行确定所述UE与所述服务器的上行网络连接处于断开状态的步骤。
确定模块604，用于确定所述UE与所述服务器的上行网络连接处于断开状态；
计费模块605，用于阻止所述业务数据流的发送，或，对所述业务数据流按照预置计费方式进行计费。
在本实施例中，介绍了通过判断UE是否产生异常响应从而判断上行网络连接是否处于断开状态，增加了方案的可实施性。
在本实施例中，具体怎么判断UE是否产生了异常响应的方式有多种，下面请参照图7，对其中两种情况进行叙述。
获取模块701，用于获取业务数据流，所述业务数据流为服务器利用默认承载发送至用户设备UE的数据流，所述默认承载为所述服务器与所述UE的公共数据网PDN连接处于连接状态时建立的承载；
判断模块702，用于判断所述UE是否产生异常响应；
执行模块703，若所述UE产生异常响应，则用于执行确定所述UE与所述服务器的上行网络连接处于断开状态的步骤。
确定模块704，用于确定所述UE与所述服务器的上行网络连接处于断开状态；
计费模块705，用于阻止所述业务数据流的发送，或，对所述业务数据流按照预置计费方式进行计费。
一、PCEF设备对UE与服务器的数据交互进行监控的过程中1、检测到UE发起与服务器断开PDN连接的请求。2、预置时长内UE是否没有对业务数据流产生响应；
其中，判断模块702包括：
第一判断子模块7022，用于判断所述UE是否发起与所述服务器断开所述PDN连接的请求或判断预置时长内所述UE是否没有对所述业务数据流产生响应；
第一确定子模块7023，若第一判断子模块7021判断得到所述UE发起与所述服务器 断开所述PDN连接的请求或预置时长内所述UE没有对所述业务数据流产生响应，则用于确定所述UE产生异常响应。
判断模块还包括：
第二确定子模块7021，用于根据所述UE的互联网协议IP地址、端口信息、域名信息和所述UE所遵循的通信协议中的至少一个确定所述预置时长。
二、PCEF设备判断业务数据流中的报文个数是否大于第一门限值，若是，且UE没有对业务数据流产生响应或UE发起与服务器断开PDN连接的请求，PCEF设备确定UE产生异常响应。
其中，判断模块702包括：
第二判断子模块7025，用于判断所述业务数据流中的报文个数是否大于门限值；
第三确定子模块7026，若第二判断子模块7023判断得到所述业务数据流中的报文个数大于门限值，且所述UE没有对所述业务数据流产生响应或所述UE发起与所述服务器断开所述PDN连接的请求，则用于确定所述UE产生异常响应。
判断模块还包括：
第四确定子模块7024，用于根据所述UE的互联网协议IP地址、端口信息、域名信息和所述UE遵循的通信协议中的至少一个确定所述门限值。
图8是本申请实施例提供的一种PCEF设备示意图，该PCEF设备800包括浏览器，该PCEF设备800可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上中央处理器(central processing units，CPU)822(例如，一个或一个以上处理器)和存储器832，一个或一个以上存储应用程序842或数据844的存储介质830(例如一个或一个以上海量存储设备)。其中，存储器832和存储介质830可以是短暂存储或持久存储。存储在存储介质830的程序可以包括一个或一个以上模块(图示没标出)，每个模块可以包括对PCEF设备中的一系列指令操作。更进一步地，中央处理器822可以设置为与存储介质830通信，在PCEF设备800上执行存储介质830中的一系列指令操作。
该中央处理器822可以根据指令操作执行如下步骤：
获取业务数据流，所述业务数据流为服务器利用默认承载发送至用户设备UE的数据流，所述默认承载为所述服务器与所述UE的公共数据网PDN连接处于连接状态时建立的承载；
确定所述UE与所述服务器的上行网络连接处于断开状态；
阻止所述业务数据流的发送，或，所述PCEF设备对所述业务数据流按照预置计费方式进行计费。
PCEF设备800还可以包括一个或一个以上电源826，一个或一个以上有线或无线网络接口850，一个或一个以上输入输出接口858，和/或，一个或一个以上操作系统841，例如Windows ServerTM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM等等。
上述实施例中由PCEF设备所执行的步骤可以基于该图8所示的PCEF设备结构。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以 通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，本地客户端，或者网络设备等)执行本申请图2至图4各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上，以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (16)

  1. 一种业务数据流处理方法，其特征在于，包括：
    策略及计费执行功能PCEF设备获取业务数据流，所述业务数据流为服务器利用默认承载发送至用户设备UE的数据流，所述默认承载为所述服务器与所述UE的公共数据网PDN连接处于连接状态时建立的承载；
    所述PCEF设备确定所述UE与所述服务器的上行网络连接处于断开状态；
    所述PCEF设备阻止所述业务数据流的发送，或，所述PCEF设备对所述业务数据流按照预置计费方式进行计费。
  2. 根据权利要求1所述的方法，其特征在于，所述PCEF设备确定所述UE与所述服务器的上行网络连接处于断开状态之前，所述方法还包括：
    所述PCEF设备判断所述UE是否产生异常响应；
    若是，则执行后续步骤。
  3. 根据权利要求2所述的方法，其特征在于，所述PCEF设备判断所述UE是否产生异常响应包括：
    所述PCEF设备判断所述UE是否发起与所述服务器断开所述PDN连接的请求或判断预置时长内所述UE是否没有对所述业务数据流产生响应；
    若是，所述PCEF设备确定所述UE产生异常响应。
  4. 根据权利要求3所述的方法，其特征在于，所述PCEF设备确定所述UE产生异常响应之前，所述方法还包括：
    所述PCEF设备根据所述UE的互联网协议IP地址、端口信息、域名信息和所述UE所遵循的通信协议中的至少一个确定所述预置时长。
  5. 根据权利要求2所述的方法，其特征在于，所述PCEF设备判断所述UE是否产生异常响应包括：
    所述PCEF设备判断所述业务数据流中的报文个数是否大于门限值；
    若是，且所述UE没有对所述业务数据流产生响应或所述UE发起与所述服务器断开所述PDN连接的请求，所述PCEF设备确定所述UE产生异常响应。
  6. 根据权利要求5所述的方法，其特征在于，所述PCEF设备判断所述业务数据流中的报文个数是否大于门限值之前，所述方法还包括：
    所述PCEF设备根据所述UE的互联网协议IP地址、端口信息、域名信息和所述UE遵循的通信协议中的至少一个确定所述门限值。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述预置计费方式对应的数据流量费用小于所述PDN连接和所述上行网络连接处于连接状态时的数据流量费用。
  8. 一种策略及计费执行功能PCEF设备，其特征在于，包括：
    获取模块，用于获取业务数据流，所述业务数据流为服务器利用默认承载发送至用户设备UE的数据流，所述默认承载为所述服务器与所述UE的公共数据网PDN连接处于连接状态时建立的承载；
    确定模块，用于确定所述UE与所述服务器的上行网络连接处于断开状态；
    计费模块，用于阻止所述业务数据流的发送，或，对所述业务数据流按照预置计费方式进行计费。
  9. 根据权利要求8所述的PCEF设备，其特征在于，所述PCEF设备还包括：
    判断模块，用于判断所述UE是否产生异常响应；
    执行模块，若所述UE产生异常响应，则用于执行确定所述UE与所述服务器的上行网络连接处于断开状态的步骤。
  10. 根据权利要求9所述的PCEF设备，其特征在于，所述判断模块包括：
    第一判断子模块，用于判断所述UE是否发起与所述服务器断开所述PDN连接的请求或判断预置时长内所述UE是否没有对所述业务数据流产生响应；
    第一确定子模块，若第一判断子模块判断得到所述UE发起与所述服务器断开所述PDN连接的请求或预置时长内所述UE没有对所述业务数据流产生响应，则用于确定所述UE产生异常响应。
  11. 根据权利要求10所述的PCEF设备，其特征在于，所述判断模块还包括：
    第二确定子模块，用于根据所述UE的互联网协议IP地址、端口信息、域名信息和所述UE所遵循的通信协议中的至少一个确定所述预置时长。
  12. 根据权利要求9所述的PCEF设备，其特征在于，所述判断模块包括：
    第二判断子模块，用于判断所述业务数据流中的报文个数是否大于门限值；
    第三确定子模块，若第二判断子模块判断得到所述业务数据流中的报文个数大于门限值，且所述UE没有对所述业务数据流产生响应或所述UE发起与所述服务器断开所述PDN连接的请求，则用于确定所述UE产生异常响应。
  13. 根据权利要求12所述的PCEF设备，其特征在于，所述判断模块还包括：
    第四确定子模块，用于根据所述UE的互联网协议IP地址、端口信息、域名信息和所述UE遵循的通信协议中的至少一个确定所述门限值。
  14. 一种PCEF设备，其特征在于，包括：存储器、收发器、处理器以及总线系统；
    其中，所述存储器用于存储程序和指令；
    所述收发器用于在所述处理器的控制下接收或发送信息；
    所述处理器用于执行所述存储器中的程序；
    所述总线系统用于连接所述存储器、所述收发器以及所述处理器，以使所述存储器、所述收发器以及所述处理器进行通信；
    其中，所述处理器用于调用所述存储器中的程序指令，执行如权利要求1至7中任一项所述的方法。
  15. 一种计算机可读存储介质，包括指令，当所述指令在计算机上运行时，使得计算机执行如权利要求1至7中任意一项所述的方法。
  16. 一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如权利要求1至7中任意一项所述的方法。
PCT/CN2019/071851 2018-01-17 2019-01-16 一种业务数据流处理方法及其相关设备 WO2019141171A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2020538915A JP7207764B2 (ja) 2018-01-17 2019-01-16 サービスデータフロー処理方法および関連デバイス
EP19741183.8A EP3734905B1 (en) 2018-01-17 2019-01-16 Service data flow processing method and related device thereof
US16/931,146 US11303761B2 (en) 2018-01-17 2020-07-16 Service data flow processing method and related device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810046643.8 2018-01-17
CN201810046643.8A CN110048861B (zh) 2018-01-17 2018-01-17 一种业务数据流处理方法及其相关设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/931,146 Continuation US11303761B2 (en) 2018-01-17 2020-07-16 Service data flow processing method and related device

Publications (1)

Publication Number Publication Date
WO2019141171A1 true WO2019141171A1 (zh) 2019-07-25

Family

ID=67273536

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/071851 WO2019141171A1 (zh) 2018-01-17 2019-01-16 一种业务数据流处理方法及其相关设备

Country Status (5)

Country Link
US (1) US11303761B2 (zh)
EP (1) EP3734905B1 (zh)
JP (1) JP7207764B2 (zh)
CN (1) CN110048861B (zh)
WO (1) WO2019141171A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107295575B (zh) * 2016-04-01 2020-02-28 中兴通讯股份有限公司 一种服务质量的控制方法和装置
US11206515B2 (en) * 2018-06-01 2021-12-21 Microsoft Technology Licensing, Llc Method and system for enhancing charging for co-located SGW and PGW

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103582171A (zh) * 2012-07-27 2014-02-12 阿尔卡特朗讯 一种用于确定终止计费会话的设备与系统
US20160219644A1 (en) * 2015-01-23 2016-07-28 Apple Inc. Apparatus, System and Method for VoLTE Call Continuity
CN106900022A (zh) * 2015-12-21 2017-06-27 华为技术有限公司 长期演进lte网络数据关闭方法及装置
CN107197482A (zh) * 2017-05-10 2017-09-22 努比亚技术有限公司 数据传输方法、终端、网络设备和计算机可读存储介质
CN107453917A (zh) * 2012-07-18 2017-12-08 华为技术有限公司 一种数据连接管理的方法、装置及系统

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4485432B2 (ja) * 2005-08-23 2010-06-23 日本電信電話株式会社 無線通信システムおよび無線通信方法
US8086216B2 (en) * 2007-01-31 2011-12-27 Alcatel Lucent Mobility aware policy and charging control in a wireless communication network
EP2273731B1 (en) * 2008-04-03 2013-06-12 NTT DoCoMo, Inc. Data relay device and data relay method
US8743684B2 (en) * 2011-02-24 2014-06-03 Alcatel Lucent GPRS default bearer tracking
JP2012222378A (ja) * 2011-04-04 2012-11-12 Hitachi Ltd 端末キープアライブ方式、及びキープアライブ間隔決定方法
CN110062422A (zh) * 2011-10-21 2019-07-26 弗劳恩霍夫应用研究促进协会 无线资源管理设备及方法
EP3078224B1 (en) * 2013-12-03 2017-10-25 Telefonaktiebolaget LM Ericsson (publ) Bandwidth limitation of non-gbr bearers
CN110971419B (zh) * 2014-03-04 2021-10-26 华为技术有限公司 一种计费会话管理方法、装置
CN105379402B (zh) * 2014-04-21 2019-06-11 华为技术有限公司 承载控制方法及系统
CN105519150B (zh) * 2014-08-11 2019-05-03 华为技术有限公司 一种数据业务实现设备及方法
EP3485696B1 (en) * 2017-08-10 2022-09-07 Telefonaktiebolaget LM Ericsson (publ) Service gap control for a wireless device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107453917A (zh) * 2012-07-18 2017-12-08 华为技术有限公司 一种数据连接管理的方法、装置及系统
CN103582171A (zh) * 2012-07-27 2014-02-12 阿尔卡特朗讯 一种用于确定终止计费会话的设备与系统
US20160219644A1 (en) * 2015-01-23 2016-07-28 Apple Inc. Apparatus, System and Method for VoLTE Call Continuity
CN106900022A (zh) * 2015-12-21 2017-06-27 华为技术有限公司 长期演进lte网络数据关闭方法及装置
CN107197482A (zh) * 2017-05-10 2017-09-22 努比亚技术有限公司 数据传输方法、终端、网络设备和计算机可读存储介质

Also Published As

Publication number Publication date
US11303761B2 (en) 2022-04-12
CN110048861A (zh) 2019-07-23
EP3734905A4 (en) 2020-11-11
JP7207764B2 (ja) 2023-01-18
CN110048861B (zh) 2021-01-29
US20200351410A1 (en) 2020-11-05
JP2021511718A (ja) 2021-05-06
EP3734905A1 (en) 2020-11-04
EP3734905B1 (en) 2023-10-25

Similar Documents

Publication Publication Date Title
USRE49636E1 (en) Method and apparatus of improving quality of calls in mobile communication system
US9544939B2 (en) Intelligent policy and charging rule function (PCRF) restoration
KR102092101B1 (ko) 무선 통신 시스템에서 망 혼잡상황에서 특정 서비스를 제어하는 방법 및 장치
US8780799B2 (en) Handling multiple voice over internet protocol (VoIP) calls via a single bearer
US10057805B2 (en) Use of traffic load reduction indicator for facilitating mobility management entity overload control function
US9591560B2 (en) Temporary credential assignment when connecting to roaming wireless networks
US11349765B2 (en) Policy control method for multipath transmission, and related device
JP2020527307A (ja) 通信ネットワークにおいてセッションタイムアウト情報を動的にプロビジョニングするための方法、システムおよびコンピュータ読取可能媒体
US11510267B2 (en) Efficient Evolved Packet System (EPS) fallback
EP2952056A1 (en) Mobile gateway selection using a direct connection between a pcrf node and a mobility management node
EP2892289B1 (en) Method, apparatus, entity and network device for controlling page
WO2009059532A1 (fr) Procédé et dispositif pour exploitation de support
US9544832B2 (en) Method, apparatus and system for policy control
JP7417719B2 (ja) 接続処理方法及び通信機器
WO2014086320A1 (zh) 分组数据连接的处理方法、终端设备、网络侧设备及系统
JP6446546B2 (ja) データ処理方法、装置、端末、モビリティ管理エンティティ、およびシステム
US11303761B2 (en) Service data flow processing method and related device
Taylor et al. Priority capabilities in LTE supporting national security and emergency preparedness next generation network priority services
WO2014090011A1 (zh) 一种信令发起方法、装置及网关设备
US20230126490A1 (en) Optimized security mode command procedure to reduce communication setup failures
WO2009146630A1 (zh) 实现本地传输的方法、系统和设备
WO2018036449A1 (zh) 一种数据转发方法及装置
WO2012152170A1 (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: 19741183

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020538915

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019741183

Country of ref document: EP

Effective date: 20200729