WO2020042860A1 - 一种速率控制的方法、装置和系统 - Google Patents

一种速率控制的方法、装置和系统 Download PDF

Info

Publication number
WO2020042860A1
WO2020042860A1 PCT/CN2019/098644 CN2019098644W WO2020042860A1 WO 2020042860 A1 WO2020042860 A1 WO 2020042860A1 CN 2019098644 W CN2019098644 W CN 2019098644W WO 2020042860 A1 WO2020042860 A1 WO 2020042860A1
Authority
WO
WIPO (PCT)
Prior art keywords
rate control
data
time
information
network element
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2019/098644
Other languages
English (en)
French (fr)
Inventor
张成晨
舒林
李文强
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to JP2020572781A priority Critical patent/JP7083925B2/ja
Priority to EP19854148.4A priority patent/EP3799514B1/en
Priority to KR1020207036303A priority patent/KR102476193B1/ko
Publication of WO2020042860A1 publication Critical patent/WO2020042860A1/zh
Priority to US17/117,828 priority patent/US12035174B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0002—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0015—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/22—Negotiating communication rate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
    • G16Y30/00—IoT infrastructure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method, a device, and a system for rate control.
  • CIOT Cellular Internet of Things
  • NB-IoT narrowband Internet of Things
  • eMTC enhanced machine communication
  • CIOT is a cellular network that supports IoT devices with low complexity and low throughput.
  • UE User Equipment
  • Massive CIOT UE sending and receiving data generates a large amount of uplink and downlink data traffic, which has a huge impact on the management network element entity in the core network and the radio bearer in the radio access network.
  • 3GPP defines two rate control mechanisms, namely, Serving Public Land Mobile Network (Serving PLMN) rate control and Access point name (Access Point Name, APN) rate control.
  • Serving PLMN Serving Public Land Mobile Network
  • APN Access Point Name
  • PLMN rate control is used for Serving.
  • PLMN limits the number of user data packet data units (PDUs) transmitted by the UE through non-access stratum (NAS) messages.
  • APN rate control is used to belong to the public land mobile network. (Home, Public, Mobile, Network, HPLMN) The operator limits the amount of uplink user data sent by the UE.
  • Both of these rate control methods can effectively solve the problem of load pressure caused by massive connections.
  • the data sender sends a reasonable number of data PDUs within a time interval that it understands according to the rate control information.
  • the data receiver may be discarded or delayed, which increases the packet loss of user data transmission. Rate and transmission delay, affecting business characteristics and user experience.
  • the embodiments of the present application provide a method, a device, and a system for rate control, so as to solve the problem that the data sending device in the prior art still loses packets or delays processing when it uses the rate control information to send a reasonable amount of data.
  • a rate control method includes: a control device receiving a connection establishment request of a terminal, where the connection establishment request is used to establish a connection for data transmission by the terminal; the control device sends a rate-controlled Time management information, where the time management information is used by the data sending device to rate control data sent over the connection, wherein the time management information includes a start time indication of a rate control time unit for rate control Information, and the start time indication information is used to indicate a start time of the rate control time unit.
  • a rate control method includes: a data sending device receives rate management time management information; wherein the time management information includes rate control for rate control on a connection for data transmission by a terminal The start time indication information of the time unit, the start time indication information is used to indicate the start time of the rate control time unit; then, the data sending device rates the data sent on the connection according to the rate time management information control.
  • the data sending device can determine the same time point when the control device starts the rate control timing In this way, when the data sending device uses the time management information to send a reasonable number of data units to the control device, the control device will also treat these data as legitimate data, and will not perform packet loss or delay processing on these data.
  • the start time indication information may specifically be: a time point at which the connection is successfully established; or, a time point at which a first data unit is transmitted on the connection; Or, the starting point of the next charging cycle, etc.
  • the control device may be a mobile management network element or a session management network element; the data sending device For the terminal.
  • the control device is a mobile management network element or a session management network element, and the data sending device is a user plane network element; or, the The control device is a mobile management network element, and the data sending device is a session management network element.
  • the rate control is data network name rate control
  • the control device is a user plane network element; and the data sending device is a terminal.
  • the rate control is an access point name rate control
  • the control device is a user plane network element; and the data sending device is a terminal.
  • the time management information further includes timing indication information, where the timing indication information is specifically: when the terminal enters a connected state , Continue counting on the remaining value of the rate control time unit; or, when the terminal enters the connected state, restart timing of the rate control time unit; or, the next rate control time unit transmits after the rate control time unit ends Timing starts at the first data unit.
  • the time management information further includes timing indication information, and the timing indication information is specifically: The rate control time unit continuously counts after the start time; or, the next rate control time unit starts timing when the first data unit is transmitted after the rate control time unit ends.
  • the time management information further includes: a rate control value.
  • the rate control value is used to indicate the maximum value of the data unit sent by the data sending device within the rate control time unit.
  • the time management information further includes: rate control time unit information.
  • an embodiment of the present application provides a rate control device, which has a function of implementing the method provided in any one of the foregoing first aspects.
  • This function can be realized by hardware, and can also be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • an embodiment of the present application provides a data sending device, and the device has a function of implementing the method provided in any one of the foregoing second aspects.
  • This function can be realized by hardware, and also can be implemented by hardware by executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • an embodiment of the present application provides a rate control device, including: a processor and a memory; the memory is configured to store a computer executing instructions, and when the rate control device is running, the processor executes the computer stored in the memory An instruction is executed to cause the rate control device to execute the rate control method according to any one of the first aspects.
  • an embodiment of the present application provides a rate control device, including: a processor; the processor is configured to be coupled with a memory, and after reading an instruction in the memory, execute the instruction according to the instruction according to the first aspect.
  • an embodiment of the present application provides a data sending apparatus, including: a processor and a memory; the memory is configured to store a computer executing instructions, and when the data sending apparatus is running, the processor executes the computer stored in the memory An instruction is executed to cause the data transmitting device to execute the rate control method according to any one of the second aspects.
  • an embodiment of the present application provides a data sending device, including: a processor; the processor is configured to be coupled to a memory and read an instruction in the memory, and then execute the instruction as described in the second aspect according to the instruction.
  • an embodiment of the present application provides a rate control system, including the rate control device in any one of the third aspects, and the data sending device in any one of the fourth aspects; or, including the fifth aspect. Or the rate control device according to the sixth aspect, and the data transmission device according to the seventh or eighth aspect.
  • an embodiment of the present application provides a computer program product containing instructions, which when executed on a computer, causes the computer to execute the method according to any one of the first aspect or the second aspect.
  • an embodiment of the present application provides a computer storage medium including instructions that, when run on a computer, cause the computer to execute the method described in the first aspect or the second aspect above.
  • FIG. 1 is a schematic diagram of a possible system network according to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of another possible system network according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of another possible system network according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a computer device according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a rate selection method according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of another rate selection method according to an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of another rate selection method according to an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of another rate selection method according to an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of another rate selection method according to an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of another rate selection method according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a device according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of another device according to an embodiment of the present application.
  • the network architecture and service scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application.
  • Those of ordinary skill in the art know that with the network The evolution of the architecture and the emergence of new business scenarios.
  • the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • Serving PLMN rate control is used for Serving.
  • PLMN limits the number of PDUs transmitted through NAS messages in the uplink and downlink.
  • PDUs transmitted through NAS messages are also called NAS data PDUs. They are user data transmitted through NAS messages on the control plane.
  • Over-plane control Serving PLMN rate control can also be understood as limiting the number of NAS messages that carry user data in the uplink and downlink.
  • the uplink rate control is used to limit the number of NAS data PDUs sent by the UE.
  • the downlink rate control is used to limit the number of NAS data PDUs sent by the user plane network element or the session management network element. Can be different.
  • Serving PLMN rate control information is configured by the operator in the management network element or entity in the core network, and is generally set to "X NAS data PDUs every 6 minutes", where X is an integer and should not be less than 10; here NAS data PDUs can also be understood as NAS messages used to transmit user data.
  • EPS long-term evolved packet system
  • PDN gateway PDN Gateway
  • SMF Service Capability Open Function
  • NEF Network open function
  • APN rate control is used by the home operator to limit the number of uplink user data PDUs sent by the UE to the specified APN.
  • the restricted uplink user data PDUs can be user data transmitted through NAS messages on the control plane, or users transmitted through the user plane. data.
  • the APN rate control information is configured by the operator in the user plane network element or entity in the core network, and is generally set to the maximum number of user data messages (user data messages) sent by the UE within a specified time unit, for example: "X per day "User data message", where X is an integer and there is no minimum value limit; the user data message here can also be understood as a data unit (data unit), or a data packet (data packet), and the time unit here is also called time Unit (time unit), or time interval (time interval).
  • a UE that supports APN rate control can also support the limitation of abnormal report data packets, that is, the UE can continue to send a certain number of abnormal report data packets after exceeding the limit of sending a maximum of Y messages per day.
  • the APN rate control information is configured in PGW or SCEF.
  • the APN rate control information includes three pieces of information: the number of data packets (or data units) that can be sent per time unit; if the number of data packets reaches the limit, whether the UE allows to continue to send exception reports; if it allows In this case, the UE sends an exception report, and it includes the number of data packets that can send the exception report.
  • DNN rate control is similar to APN rate control and will not be repeated here.
  • APN rate control is applied to EPS, and DNN rate control is applied to 5GS.
  • the rate control information is based on a time interval, which can be understood as: the issued rate control information is valid within the time interval, and it is outside the time interval. Invalid.
  • the start time of the time interval is not coordinated between the control device and the data sending device, thereby causing the time of the two parties to perform rate control to be asynchronous.
  • Serving PLMN rate control information is "20 NAS data PDUs every 6 minutes". The data sending device understands the time interval as the start of the timing when the data is sent for the first time.
  • the device understands the time interval as the start of the timer when the PDN connection is established, for example, the PDN connection is established at 10:00.
  • 20 data can be received within 6 minutes of [10:00, 10:06), and 20 data can be received within 6 minutes of [10:06, 10:12).
  • 20 data can be sent during [10:02, 10:08), and 20 data can be sent during [10:08, 10:14).
  • the data sending device sends 15 data within 4 minutes of [10:02, 10:06), [10:06, 10:08) sends 5 data within 2 minutes. Then, 16 data were sent within 4 minutes of [10: 08,10: 12). In this way, the data sending device sends data in strict accordance with the PLMN rate control information, and does not exceed the rate control limit. But for the control device, the data received by [10: 06,10: 12) is 5 + 16, that is, 21 data, which exceeds the [10: 06,10: 11] stipulated by the Servo PLMN rate control information. Receiving no more than the upper limit of 20 data. Therefore, the control device will discard the 21st data.
  • embodiments of the present application provide a rate control method and system.
  • the following describes the rate control system and method provided by the embodiments of the present application.
  • an embodiment of the present application provides a rate control system 100.
  • the system 100 includes: a control device 10 and a data sending device 20.
  • the system architecture 100 described above may be used to execute the rate control method provided in this application.
  • the control device 10 is configured to receive a connection establishment request of the terminal, where the connection establishment request is used to establish a connection for data transmission by the terminal; and send rate-controlled time management information to the data sending device 20, where the time management information is used for The data transmitting device 20 performs rate control on data transmitted on the connection.
  • the time management information includes start time indication information of a rate control time unit that performs rate control, and the start time indication information is used to indicate a start time of the rate control time unit.
  • the data sending device 20 is configured to receive the time management information. Optionally, the data sending device 20 performs rate control on the data sent on the connection according to the time management information.
  • connection establishment request here may be a PDU session establishment request or a PDN connection establishment request, which is not limited in this application.
  • the connection establishment request is a PDU session establishment request
  • the established connection is a PDU session
  • the connection establishment request is a PDN connection establishment request
  • the established connection is a PDN connection.
  • the start time indication information may be any one of the following information: the time point when the connection is successfully established; the time point when the first data unit is transmitted on the connection; or, the next charging The starting point of the cycle.
  • the rate control may be a serving PLMN rate control, an APN rate control, or a DNN rate control.
  • the device or entity corresponding to the control device may be a mobile management network element or a session management network element, and the data sending device may be a terminal or a user plane network element.
  • the control device may be a mobile management network element, and the data sending device may be a session management network element.
  • the control device when the rate control is DNN rate control or APN rate control, the control device may be a user plane network element, and the data sending device may be a terminal; when the rate control is Serving or PLMN rate control, the The control device may be a mobile management network element, and the data sending device may be a user plane network element.
  • the time management information further includes timing indication information
  • the timing indication information is specifically any one of the following information: when the terminal enters the connected state, the remaining value of the rate control time unit Time counting continues on when the terminal enters the connected state and restarts timing of the rate control time unit; or, the next rate control time unit starts timing when the first data unit is transmitted after the rate control time unit ends.
  • the time management information further includes timing indication information, and the timing indication information is specifically any one of the following information: the time unit of rate control is at the beginning Continuous time counting after time; or, the next rate control time unit, that is, the next time unit of rate control, starts timing when the first data unit is transmitted after the rate control time unit ends.
  • the time management information may further include a rate control value, where the rate control value is used to indicate a maximum value of a data unit sent by the data sending device within the rate control time unit.
  • the data unit here may, in a specific implementation, be a message that sends a data unit, or a data unit that is sent, or may be in another form, which is not limited in this application.
  • the data unit can be encapsulated in a NAS message. In this way, the number of data units sent by the data sending device is the number of NAS messages sent with the data unit encapsulated.
  • the data sending device sends uplink user data messages.
  • a message contains a data unit (PDU), so the rate control value here can be expressed by the number of PDUs. It can also be expressed by the number of NAS messages containing PDUs.
  • PDU data unit
  • the data sending device is user data transmitted through a control plane NAS message.
  • a NAS message contains a data unit (PDU), so the rate control value here can be expressed by the number of PDUs. It can also be expressed by the number of NAS messages containing PDUs.
  • the data sending device sends downlink data PDUs (downlink data PDUs), which are not encapsulated with NAS messages. They are themselves PDUs, so the rate control value here can be expressed by the number of PDUs.
  • the time management information may further include: rate control time unit information.
  • the control device sends the start time indication information of the rate time unit. After receiving the start time indication information, the data sending device can determine the same time point as the control device to start the rate control timing. In this way, when the data sending device uses the time management information to send a reasonable number of data units to the control device, the control device will also treat these data as legitimate data, and will not perform packet loss or delay processing on these data. Therefore, in the prior art, when a data sender uses a rate control information to send a reasonable number of data PDUs, the problem of packet loss or delay in processing is solved.
  • the above-mentioned rate control system 100 may be applied to a 4th generation (4G) network, that is, an EPS, a 5G network, and other future networks, which are not specifically limited in this embodiment of the present application.
  • 4G 4th generation
  • EPS EPS
  • 5G 5th generation
  • future networks which are not specifically limited in this embodiment of the present application.
  • the 5G architecture diagram 200 shown in FIG. 2 is used.
  • the device or entity corresponding to the mobile management network element is access and mobility management function (AMF); the device or entity corresponding to the session management network element is SMF; the device or entity corresponding to the user plane network element
  • the entity is UPF or NEF.
  • the architecture can also include: the core network control plane includes authentication server function (AUSF), network slice selection function (NSSF), NEF, network function storage function (NFRF), unified Data management (unified data management, UDM), policy control function (PCF), or application function (AF).
  • AUSF authentication server function
  • NSSF network slice selection function
  • NFRF network function storage function
  • UDM unified data management
  • PCF policy control function
  • AF application function
  • the AMF may also be responsible for functions such as registration management, mobility management, or lawful interception, which are not specifically limited in this embodiment of the present application.
  • SMF can also be used for session management, including: session establishment, session modification, session release, terminal IP address allocation and management, selection and control of UPF, or legitimate interception, etc. Session-related controls.
  • UPF can also be used to perform user data packet forwarding based on SMF routing rules.
  • AUSF is used to perform security authentication of the terminal.
  • NSSF is used to select a network slice for the terminal.
  • NEF opens network functions to third parties in a Northbound Application Programming Interface (API) manner.
  • the NRF provides storage functions and selection functions of network function entity information for other network elements.
  • UDM is used to manage user subscription context.
  • PCF is used to manage user policies.
  • AF is used to manage user applications.
  • the N1 interface is the reference point between the UE and the AMF, and is used for NAS message transmission.
  • the N2 interface is the reference point for (R) AN and AMF.
  • the N3 interface is the (R) AN and UPF. The reference point between them is used to transmit user plane data.
  • the N4 interface is used as a reference point between SMF and UPF. It is used to transmit information such as tunnel identification information, data cache indication information, and downlink data notification messages for N3 connections.
  • N6 interface is the reference point between UPF and DN, used to transmit user plane data and so on.
  • the control plane network elements such as AMF network element, SMF network element, AUSF network element or UDM network element in the 5G network shown in FIG.
  • a service interface can be used for interaction.
  • the external service interface provided by AMF network elements can be Namf; the external service interface provided by SMF network elements can be Nsmf; the external service interface provided by AUSF network elements can be Nausf; and the external service interface provided by UDM network elements Can be Nudm, etc.
  • TSG 5G system architecture
  • interface names between the various network elements in FIG. 2 are only examples, and the interface names may be other names in the specific implementation, which is not specifically limited in this embodiment of the present application.
  • the terminal, AMF network element, SMF network element, UPF network element, NEF network element, and PCF network element in the above 5G network are only a name, and the name does not constitute a limitation on the device itself.
  • the network elements or entities or devices corresponding to the UE, AMF, SMF, UPF, NEF, and PCF may also have other names, which are not specifically limited in this embodiment of the present application.
  • the UDM entity may also be replaced with a user home server (HSS) or a user subscription database (USD) or a database entity, which will be described uniformly here, and will not be described in detail below.
  • the EPS architecture diagram 300 shown in FIG. 3 is shown.
  • the device or entity corresponding to the mobile management network element is a mobility management entity (MME); the device or entity corresponding to the user plane network element is a PGW or SCEF.
  • MME mobility management entity
  • PGW Packet Data Network
  • MME Control plane functions mainly responsible for user mobility management and session management, including non-access stratum NAS signaling and security, management of tracking area list, packet data network gateway PGW, and serving network element (serving) gateway, SGW).
  • PGW As the anchor point of the PDN connection, it is responsible for the Internet Protocol (IP) address allocation of the UE's network interconnection, the UE's data packet filtering, rate control, or generation of billing information.
  • IP Internet Protocol
  • system may also include SGW, evolved universal terrestrial radio access network (EUTRAN), serving GPRS support node (serving GPRS support node (SGSN), home subscriber server (HSS), Or policy and charging rules function (PCRF).
  • EUTRAN evolved universal terrestrial radio access network
  • serving GPRS support node serving GPRS support node (SGSN)
  • HSS home subscriber server
  • PCRF policy and charging rules function
  • the SGW is mainly responsible for data transmission, forwarding, and routing switching of the UE, and serves as a local mobility anchor point for the UE when switching between Evolved NodeBs (eNodeBs) (for each user equipment, each time only There is an SGW for it).
  • eNodeBs Evolved NodeBs
  • EUTRAN is a network of multiple eNodeBs that implements the functions of the wireless physical layer, resource scheduling and wireless resource management, wireless access control, and mobility management.
  • eNodeBs can be connected through an X2 interface, and can be used to transmit data during X2-based handover.
  • the eNodeB is connected to the SGW through the user plane interface S1-U, and uses the general packet radio system tunneling protocol user plane (general packet radio, system, general user protocol, GTP-U) to transmit user data; through the control plane interface S1-MME and mobile
  • the management entity is connected, and the S1-AP protocol is used to implement functions such as wireless access bearer control.
  • SGSN is 2G access network GSM / EDGE radio access network (GSM / EDGE radio access network, GERAN), 3G access network universal terrestrial radio access network (UTRAN) and 3GPP evolved packet core network
  • the access node (Evolved Packet Core, EPC) is responsible for the establishment and data forwarding of the EPC bearer from GERAN, UTRAN.
  • the HSS is mainly used to store subscription data for mobile users.
  • the PCRF is responsible for charging management and policy control, including policy and charging control (PCC) rules, and quality of service (QoS) rules.
  • PCC policy and charging control
  • QoS quality of service
  • SCEF (not shown in the figure) provides a secure way to expose the services and capabilities provided by the 3GPP network interface, while providing a method to discover the capabilities and services exposed.
  • MME can interact with HSS through SCEF.
  • the terminals involved in the embodiments of the present application may include various handheld devices, wireless devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication functions.
  • the terminal may also be referred to as a user equipment (UE), a mobile station (MS), and a terminal device (terminal device), and may further include a subscriber unit, a cellular phone, and a smart phone.
  • Smart phone wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem (modem), handheld device (laptop computer), cordless phone ( (cordless phone) or wireless local loop (wireless local loop (WLL)) stations, machine type communication (machine type communication (MTC) terminals, CIOT terminals, etc.).
  • PDA personal digital assistant
  • modem modem
  • handheld device laptop computer
  • cordless phone cordless phone
  • WLL wireless local loop
  • MTC machine type communication
  • CIOT terminals CIOT terminals, etc.
  • control device or the data sending device in FIG. 1 may be a single network element, or may be implemented by multiple network elements together, or may be used as a function module in a network element.
  • This is not specifically limited. It can be understood that the foregoing functions may be network elements in a hardware device, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform).
  • control device 10 in FIG. 1, or the AMF, SMF, and UE in FIG. 2, or the MME and UE in FIG. 3 may be implemented as a computer device (or system) in FIG. 4. .
  • FIG. 4 is a schematic diagram of a computer device according to an embodiment of the present application.
  • the computer device 400 includes at least one processor 41, a communication line 42, a memory 43, and at least one communication interface 44.
  • the processor 41 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the solution of the present application.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line 42 may include a path for transmitting information between the aforementioned components.
  • the communication interface 44 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), and the like.
  • RAN Radio Access Network
  • WLAN Wireless Local Area Networks
  • the memory 43 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions
  • the dynamic storage device can also be Electrically Erasable Programmable Read-Only Memory (EEPROM), Compact Disc (Read-Only Memory, CD-ROM) or other optical disk storage, optical disk 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 code in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.
  • the memory may exist independently and be connected to the processor through a communication line. The memory can also be integrated with the processor.
  • the memory 43 is configured to store application program code that executes the solution of the present application, and is controlled and executed by the processor 41.
  • the processor 41 is configured to execute application program code stored in the memory 43.
  • the processor 41 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 4.
  • the computer device 400 may include multiple processors, such as the processor 41 and the processor 48 in FIG. 4. Each of these processors may be a single-CPU processor or a multi-CPU processor.
  • a processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).
  • the computer device 400 may further include an output device 45 and an input device 46.
  • the output device 45 communicates with the processor 41 and can display information in a variety of ways.
  • the output device 45 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • the input device 46 is in communication with the processor 41 and can accept user input in a variety of ways.
  • the input device 46 may be a mouse, a keyboard, a touch screen device, or a sensing device.
  • the above-mentioned computer device 400 may be a general-purpose computer device or a special-purpose computer device.
  • the computer device 400 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, an embedded device, or the device shown in FIG. 4.
  • Equipment of similar structure The embodiment of the present application does not limit the type of the computer device 400.
  • control device 10 in FIG. 1 may be the device shown in FIG. 4, and one or more software modules are stored in a memory of the control device 10.
  • the control device 10 may implement software modules through a processor and program codes in a memory to implement rate control.
  • FIG. 5 provides a schematic flowchart of a method for performing rate control in the system shown in FIG. 1 or FIG. 2.
  • Figure 5 mainly introduces the PLMN rate control method.
  • a connection is taken by taking a session as an example, and a connection establishment request is described by taking a PDU session establishment request as an example.
  • the UE sends a PDU session establishment request to the AMF via the access node.
  • the AMF receives the PDU session establishment request.
  • a new PDU session needs to be established to transmit uplink and downlink user data.
  • the UE initiates a PDU session establishment procedure to the network side.
  • the UE sends a NAS message to the AMF, such as an uplink NAS transport (UL) message, which includes a PDU session identifier, a request type, and an N1 session management container.
  • the N1 session management container includes a PDU session establishment request.
  • AMF selects SMF.
  • a session context creation request is then sent to the selected SMF.
  • the SMF receives the session context creation request.
  • the session context creation request includes a PDU session establishment request in S501.
  • the method for selecting the SMF by the AMF can refer to the methods in the prior art.
  • the SMF can be selected according to the DNN or a single network slice provided by the UE. To repeat.
  • control device may be AMF or SMF.
  • control device is AMF for example.
  • the session context creation request includes Serving PLMN rate control time management information.
  • the user plane network element performs rate control on the data sent on the PDU session according to the serving PLMN rate control time management information.
  • the Serving PLMN rate control time management information may be transmitted through a specific information element (IE) in a specific implementation.
  • IE information element
  • Information elements here can also be called cells.
  • the serving PLMN rate control time management information includes starting time indication information of the serving PLMN rate control time unit that performs the serving PLMN rate control.
  • the starting time indication information is used to indicate a starting time of a serving PLMN rate control time unit.
  • the start time indication information has various forms, for example, it may be: a) the time point when the connection is successfully established; or b) the time point when the first data unit is transmitted on the connection; or : C) the starting point of the next charging cycle.
  • This application is not specifically limited. Among them, for b), since data can be transmitted on the connection, it is after the connection is successfully established.
  • the connection here specifically refers to a PDU session.
  • the time management information may further include timing indication information, and the timing indication information is specifically any one of the following information: the first type : The rate-controlled time unit continuously counts after the start time; or, the second type: the next rate-controlled time unit starts timing when the first data unit is transmitted after the rate-controlled time unit ends.
  • the timing indication may also be selected according to the operator's policy or configuration, which is not specifically limited in this application.
  • the serving PLMN rate control time management information may further include the serving PLMN rate control time unit.
  • the time unit can be 6 minutes, but it can also be other times.
  • the time unit may also be negotiated in advance by the AMF and the user plane network element. In this case, the session context creation request message may not carry the time unit.
  • the serving PLMN rate control time management information may further include: serving PLMN rate control value.
  • the Serving PLMN rate control value is used to indicate the maximum value of the data unit sent by the user plane network element within the Serving PLMN rate control time unit.
  • the SMF sends a session context creation response to the AMF.
  • the AMF receives the session context creation response.
  • the SMF sends a session establishment request to the user plane network element (here, the user plane network element may be UPF or NEF), where the session establishment request carries Serving PLMN time management information.
  • the user plane network element receives the session establishment request. Subsequently, after the session is successfully established, the user plane network element performs rate control on the data sent on the PDU session according to the serving PLMN time management information.
  • the SMF when executing S507, can also select the UPF, for example, when the request type is "initialization request".
  • the request type is "initialization request”.
  • the user plane network element sends a session establishment response to the SMF.
  • the SMF receives the session establishment response.
  • the SMF calls the N1N2 message transmission service operation of the mobile management network element, and performs message transmission with the AMF. By invoking the N1N2 message transmission service, the SMF sends the PDU session establishment acceptance message sent to the UE to the AMF as a response message to the PDU session establishment request received in step S503.
  • the AMF sends the PDU session establishment acceptance message received in S511 to the UE through the access node.
  • the UE accepts the PDU session establishment acceptance message.
  • the AMF sends a NAS message to the UE, such as a downlink NAS transport (DL NAS transport) message, which includes a PDU session establishment acceptance message sent by the SMF in S511.
  • a NAS message such as a downlink NAS transport (DL NAS transport) message, which includes a PDU session establishment acceptance message sent by the SMF in S511.
  • DL NAS transport downlink NAS transport
  • step 513 may also carry the time management information in the above S503, and the time management information is not described in this step. . Subsequently, after the PDU session is successfully established, the UE performs rate control on the data sent on the PDU session according to the time management information. After S513, the UE can learn that the PDU session is successfully established.
  • the AMF may be selected according to the frequency of data sent by the UE. For example, a UE sending data frequently may select a) or b) or c) described in S503 as the starting time indication information; a UE not sending data frequently may select b) or c) described in S503 as a start Time indication information.
  • AMF can also be selected according to the status of the UE.
  • a stationary UE is generally an energy-saving UE.
  • b) described in S503 may be selected as the start time indication.
  • the AMF can also be selected according to the duration of the UE communication. For a UE with a long communication duration, b) described in S503 may be selected as the start time indication. The AMF can also be selected based on whether the UE has an external power supply. For a UE with external power supply, a) or b) described in S503 may be selected as the start time indication. Of course, in specific implementation, appropriate start time indication information may also be selected according to the operator's policy or configuration, which is not specifically limited in this application.
  • the time management information may further include timing indication information, which is specifically any one of the following information: a1) when the UE enters a connected state, Continue counting on the remaining value of the Serving PLMN rate control time unit; or, b1) When the UE enters the connected state, restart the timing of the Serving PLMN rate control time unit; or c1) Serving the next time unit of the PLMN rate control, at Serving PLMN The rate control time unit starts to count when the first data unit is transmitted.
  • timing indication information is specifically any one of the following information: a1) when the UE enters a connected state, Continue counting on the remaining value of the Serving PLMN rate control time unit; or, b1) When the UE enters the connected state, restart the timing of the Serving PLMN rate control time unit; or c1) Serving the next time unit of the PLMN rate control, at Serving PLMN The rate control time unit starts to count when the first data unit is transmitted.
  • the AMF may be selected according to the frequency of the data sent by the UE. For example, a UE that sends data frequently may select a1) as a timing indication; a UE that does not send data frequently may select b1) or c1) as a timing indication.
  • the AMF can also be selected based on the interval of the UE's periodic communication. If the interval of cyclic communication is relatively long, it is more appropriate to choose b1).
  • the timing indication may also be selected according to the operator's policy or configuration, which is not specifically limited in this application.
  • the AMF controls both the sending rate of the uplink NAS data PDU and the sending rate of the downlink NAS data PDU.
  • the AMF's rate control of the uplink NAS data PDU and the downlink NAS data PDU's rate control are independent and decoupled.
  • the AMF can also control the sending rate of the uplink NAS data PDU.
  • S507 can not carry time management information;
  • AMF can also control the sending rate of downlink NAS data PDUs.
  • S513 can not carry time management information.
  • the time management information of the two may be the same or different, which is not limited in this application.
  • a user plane network element or a UE is described as a data sending device.
  • SMF can also be used as a data sending device.
  • a method similar to that in FIG. 5 may be adopted.
  • SMF obtains time management information through S503. Data for rate control.
  • S507 may not carry time management information. If the user plane network element also needs to be used as a data sending device, S507 can be the same as that in FIG. 5.
  • the AMF sends start time indication information of the serving PLMN rate control time unit.
  • the user plane network element, SMF, or UE can determine the same start time as the AMF. Time point for rate control timing.
  • the AMF will also treat these data as legitimate data and will not lose these data Packet or delay processing, thereby solving the problem of packet loss or delay processing in the prior art when a data sender sends a reasonable number of NAS data PDUs using rate control information.
  • step S507 when the SMF wishes to control the transmission rate of the downlink data, the session establishment request of S507 carries time management information. After the user plane network element receives the time management information, according to the time management information, after the PDU session is established, the downstream data sent on the PDU session is rate-controlled.
  • the time management information is carried in the PDU session establishment acceptance message, and sent to the AMF in S511, and then the AMF sends the PDU session establishment acceptance message with the time management information in S513 Send to the UE
  • the SMF can also directly carry the time management information to the AMF in S511, and directly send it to the UE in S513, that is, the time management information is not carried in the PDU session establishment acceptance message (not shown in the figure) ).
  • the UE after receiving the time management information, the UE performs rate control on the uplink data sent on the PDU session after the PDU session is established according to the time management information.
  • the SMF sends start time indication information of the serving PLMN rate control time unit.
  • the user plane network element or the UE can determine the same start rate control timing with the SMF.
  • the SMF will also treat these data as legitimate data, and will not perform packet loss or delay processing on these data. Therefore, in the prior art, when a data sender sends a reasonable number of NAS data PDUs using rate control information, the problem of packet loss or delay in processing is solved.
  • the actions of the AMF, SMF, user plane network element, or terminal may be performed by the AMF, SMF, user plane network element, or terminal according to the software module in the memory mentioned above. This embodiment of the application does not place any restrictions on this.
  • FIG. 6 provides a schematic flowchart of a method for performing rate control in the system shown in FIG. 1 or FIG. 2.
  • Figure 6 mainly introduces the DNN rate control method.
  • a connection is taken by taking a session as an example, and a connection establishment request is described by taking a PDU session establishment request as an example.
  • S601 is the same as S501.
  • the main difference between S603 and S503 is that the session context creation request does not carry DNN rate control time management information.
  • S605 is the same as S505.
  • the main difference between S607 and S507 is that the session establishment request does not carry DNN rate control time management information.
  • the user plane network element sends a session establishment response to the SMF.
  • the SMF receives the session establishment response.
  • the session establishment response message includes time management information for DNN rate control. Subsequently, after the PDU session is successfully established, the terminal performs rate control on the data sent on the PDU session according to the DNN rate control time management information.
  • the time management information of DNN rate control may be transmitted through Protocol Configuration Options (PCO) or Extended Protocol Configuration Options (ePCO) in specific implementation.
  • PCO Protocol Configuration Options
  • ePCO Extended Protocol Configuration Options
  • the DNN rate control time management information includes start time indication information of the DNN rate control time unit.
  • the start time indication information is used to indicate a start time of a DNN rate control time unit.
  • the start time indication information has various forms. In specific implementation, a), b), and c) in S503 may also be used. This application is not specifically limited.
  • the user plane network element may select the start time indication information by using the method of selecting the start time indication information by the AMF in S513. For example: select according to the frequency of data sent by the UE, or select the status of the UE; or select according to the duration of the UE communication. I won't repeat them here.
  • the time management information of DNN rate control may further include a timing indication, which is specifically any one of the following information: a1) When the UE enters the connected state, the DNN rate control time unit Or b1) when the UE enters the connected state, restart the timing of the DNN rate control time unit; or, c1) the next time unit of the DNN rate control is transmitted after the end of the DNN rate control time unit. One data unit starts timing.
  • the user plane network element may use the method of selecting timing indication information by the AMF in S513 to select the timing indication information. For example, it is selected according to the frequency of data sent by the UE, or according to the interval of the UE's periodic communication, which will not be repeated here.
  • the time management information of the DNN rate control may further include the DNN rate control time unit.
  • the time unit here is not specifically limited.
  • the time unit may also be negotiated in advance by the user plane network element and the terminal. In this case, the session establishment response may not carry the time unit.
  • the time management information of the DNN rate control may further include a DNN rate control value, and the DNN rate control value is used to indicate a maximum value of a data unit sent by the terminal within the DNN rate control time unit.
  • the SMF calls the N1N2 message transmission service operation of the mobile management network element, and performs message transmission with the AMF.
  • the SMF sends the PDU session establishment acceptance message sent to the UE to the AMF.
  • the SMF carries S609 in the PDU session establishment acceptance message.
  • Time management information may carry the time management information in S609 in the N1N2 message transmission, that is, the SMF does not carry the time management information in the PDU session establishment acceptance message (not shown in the figure).
  • the AMF sends a PDU session establishment acceptance message to the UE through the access node.
  • the UE accepts the PDU session establishment acceptance message.
  • the AMF sends a NAS message to the UE, such as a downlink NAS transport (DL NAS transport) message, which includes a PDU session establishment acceptance message sent by the SMF in S611.
  • DL NAS transport downlink NAS transport
  • the UE receives the time management information carried in the PDU session establishment acceptance message; if the SMF passes the time management information in the above S609 through the N1N2 message transmission To the AMF, the UE receives the time management information carried in the NAS message.
  • the user plane network element sends the start time indication information of the DNN rate control time unit.
  • the UE can determine the same start rate control timing with the user plane network element.
  • Time point when the UE uses the time management information to send a reasonable amount of data to the user plane network element, the user plane network element will also treat these data as legitimate data, and will not perform packet loss or delay processing on these data. Therefore, in the prior art, when a data sender uses a rate control information to send a reasonable amount of data, the problem of packet loss or delay in processing is solved.
  • the actions of the user plane network element or the terminal may be performed by the user plane network element or the terminal according to the software module in the memory mentioned above, respectively. This embodiment of the application does not place any restrictions on this.
  • FIG. 7 provides a schematic flowchart of a method for performing rate control in the system shown in FIG. 1 or FIG. 3.
  • Figure 7 mainly introduces the PLMN rate control method.
  • the UE sends an attach request to the MME via the access node.
  • the MME receives the attach request.
  • S703 The MME sends a connection establishment request to the user plane network element.
  • the user plane network element receives the connection establishment request.
  • the connection establishment request message includes time management information for serving PLMN rate control.
  • the user plane network element performs rate control on the data sent on the connection according to the time management information of the serving PLMN rate control.
  • the time management information of Serving PLMN rate control can be transmitted through specific IE in specific implementation.
  • the Serving PLMN rate control time management information includes start time indication information of the Serving PLMN rate control time unit.
  • start time indication information For a form of the start time indication information, refer to a related description in S503. I won't repeat them here.
  • the time management information for the serving PLMN rate control may further include the serving PLMN rate control time unit.
  • this time unit reference may be made to the related description in S503, which is not repeated here.
  • the time management information of the serving PLMN rate control may further include: the serving PLMN rate control value.
  • the rate control value reference may be made to the related description in S503, which is not repeated here.
  • the user plane network element sends a connection establishment response message to the MME.
  • the connection establishment response message may be sent to the MME via the SGW.
  • the MME sends an attach accept message to the UE.
  • the UE receives the attach accept message.
  • the attach accept message may also carry the time management information of the above-mentioned Serving PLMN rate control in S703.
  • About Serving PLMN Time management information for rate control is not detailed in this step.
  • the terminal performs rate control on the data to be sent on the connection according to the time management information of the serving PLMN rate control.
  • the MME may use the method of selecting start time indication information by the AMF in S513 to select the start time indication information, which is not described again here.
  • the time management information of the serving PLMN rate control may further include a timing indication, which is specifically any one of the following information: a1) the UE enters the connection In the state, continue counting on the remaining value of the Serving PLMN rate control time unit; or, b1) When the UE enters the connected state, restart the timing of the Serving PLMN rate control time unit; or c1) Serving the next time of the PLMN rate control The unit starts timing when the first data unit is transmitted after the end of the serving PLMN rate control time unit.
  • a timing indication which is specifically any one of the following information: a1) the UE enters the connection In the state, continue counting on the remaining value of the Serving PLMN rate control time unit; or, b1) When the UE enters the connected state, restart the timing of the Serving PLMN rate control time unit; or c1) Serving the next time of the PLMN rate control The unit starts timing when the first data unit is transmitted after the end of the serving PLMN rate control time unit.
  • the MME may use the method of selecting the timing indication by the AMF in S513 to select the timing indication, which is not repeated here.
  • the MME sends an initial context establishment message to the UE to request information such as the access layer security context.
  • the UE receives the initial context establishment message.
  • the initialization context establishment message may request a radio resource control connection reconfiguration.
  • the terminal After the establishment of the initialization context is completed, the terminal sends an attach completion message to the MME.
  • the MME receives the attach complete message.
  • the figure shows that the MME controls the sending rate of the uplink NAS data PDU and the sending rate of the downlink NAS data PDU.
  • the MME's rate control of the uplink NAS data PDU and the downlink NAS data PDU's rate control are independently decoupled, and the MME can also control the sending rate of the uplink NAS data PDU only.
  • S703 It does not need to carry the time management information for PLMN rate control in Serving; the MME may also only control the sending rate of downlink NAS data PDUs.
  • S707 does not need to carry the time management information for PLMN rate control.
  • the time management information of the two may be the same or different, which is not limited in this application.
  • the MME sends the starting time indication information of the serving PLMN rate time unit.
  • the user plane network element or the UE can determine the same starting rate control timing as the MME.
  • the MME will also treat these data as legitimate data, and will not perform packet loss or delay processing on these data. Therefore, in the prior art, when a data sender sends a reasonable number of NAS data PDUs using rate control information, the problem of packet loss or delay in processing is solved.
  • step S701 the terminal sends the PDN connection establishment. Request instead of attach request, S709 is bearer establishment, and S711 is connection completion.
  • step S701 the terminal sends the PDN connection establishment. Request instead of attach request, S709 is bearer establishment, and S711 is connection completion.
  • step S701 the terminal sends the PDN connection establishment. Request instead of attach request, S709 is bearer establishment, and S711 is connection completion.
  • S709 is bearer establishment, and S711 is connection completion.
  • S711 connection completion.
  • the other steps are similar to those of FIG. 7. I won't repeat them here.
  • the actions of the MME, the user plane network element, or the terminal may be performed by the MME, the user plane network element, or the terminal according to the software module in the memory mentioned above. This embodiment of the application does not place any restrictions on this.
  • FIG. 8 provides a schematic flowchart of a method for performing rate control in the system shown in FIG. 1 or FIG. 2.
  • Figure 8 mainly introduces the APN rate control method.
  • S801 is the same as S701.
  • connection establishment request message does not carry time management information for rate control.
  • the user plane network element sends a connection establishment response message to the MME.
  • the connection establishment response message may be sent to the MME via the SGW.
  • the connection establishment request message includes APN rate control time management information. Subsequently, after the connection is successfully established, the terminal performs rate control on the data to be sent on the connection according to the APN rate control time management information.
  • the APN rate control time management information can be transmitted through PCO / ePCO in specific implementation.
  • the APN rate control time management information includes start time indication information of an APN rate control time unit, where the start time indication information is used to indicate an APN rate control time for APN rate control The start time of the unit.
  • the start time indication information has various forms. In specific implementation, a), b) or c) in S703 may also be used. This application is not specifically limited.
  • the user plane network element may select the start time indication information by using the method of selecting the start time indication information by the AMF in S513. For example: select according to the frequency of data sent by the UE, or select the status of the UE; or select according to the duration of the UE communication. I won't repeat them here.
  • the time management information of the APN rate control may further include the serving APN rate control time unit.
  • the specific value of the time unit is not limited in this application.
  • the time unit may also be negotiated in advance by the user plane network element and the terminal. In this case, the connection establishment request response may not carry the time unit.
  • the time management information of the APN rate control may further include an APN rate control value, and the APN rate control value is used to indicate a maximum value of a data unit sent by the terminal within the APN rate control time unit.
  • the time management information of APN rate control may further include timing indication information, which is specifically any one of the following information: a1) When the UE enters the connected state, the APN rate control Continue counting on the remaining value of the time unit; or b1) When the UE enters the connected state, restart the timing of the APN rate control time unit; or c1) The next time unit of the APN rate control, after the APN rate control time unit ends Restart the timing when transmitting the first NAS data packet data unit carrying data.
  • timing indication information is specifically any one of the following information: a1) When the UE enters the connected state, the APN rate control Continue counting on the remaining value of the time unit; or b1) When the UE enters the connected state, restart the timing of the APN rate control time unit; or c1) The next time unit of the APN rate control, after the APN rate control time unit ends Restart the timing when transmitting the first NAS data packet data unit carrying data.
  • the user plane network element may use the method of selecting timing indication information by the AMF in S513 to select the timing indication information. For example, it is selected according to the frequency of data sent by the UE, or according to the interval of the UE's periodic communication, which will not be repeated here.
  • S807 The MME sends an attach accept message to the UE.
  • the UE receives the attach accept message.
  • the attach accept message carries the APN rate control time management information described in S805.
  • S809-S811 are the same as S709-S711, and are not repeated here.
  • the user plane network element sends the start time indication information of the APN rate time unit. After receiving the start time indication information, the UE can determine the same start rate control timing with the user plane network element. At the time point, when the UE uses the rate control information to send a reasonable number of NAS data PDUs to the user plane network element, the user plane network element will also treat these data as legitimate data, and will not perform packet loss or delay processing on these data. Therefore, in the prior art, when a data sender uses a rate control information to send a reasonable number of data PDUs, the problem of packet loss or delay in processing is solved.
  • step S801 the terminal sends the PDN connection establishment. Request instead of attach request, S809 is bearer establishment, and S811 is connection completion.
  • step S809 the terminal sends the PDN connection establishment.
  • step S809 bearer establishment
  • S811 connection completion.
  • the other steps are similar to those of FIG. 8. I won't repeat them here.
  • the actions of the user plane network element or the terminal may be performed by the user plane network element or the terminal according to the software module in the memory mentioned above, respectively. This embodiment of the application does not place any restrictions on this.
  • FIG. 9 provides a schematic flowchart of a method for performing rate control in the system shown in FIG. 2.
  • Figure 9 mainly introduces the PLMN rate control method.
  • a rate management device During mobile originating (MO) data transmission, the rate management device sends a Serving rate control status to the data sending device. After receiving the Serving rate control status information, the data sending device will adjust the data transmission rate accordingly.
  • a rate management device is a mobile management network element (corresponding to AMF in 5G), and a data sending device is a UE.
  • the UE Before the MO data is initiated, the UE is in an idle state.
  • the UE sends a radio resource control (Radio Resource Control, RRC) connection or sends an RRC early data request message to the access node.
  • RRC Radio Resource Control
  • the NAS PDU sent also contains the identifier of the connection or session and the encrypted uplink data.
  • the access node may query the UE context from the mobile management network element.
  • the access node forwards the NAS PDU from the UE to the mobile management network element through an application layer message.
  • the access node If an RRC early data request message is sent in step 901, the access node includes an "Early Data Transmission (EDT) Session" identifier in the application message.
  • EDT Error Data Transmission
  • the mobile management network element decrypts the data and performs an integrity check.
  • this step is optional. If the mobility management network element receives the "EDT session" identifier, the mobility management network element sends an application message to the access node.
  • the mobility management network element may add the serving PLMN rate control status to the application message according to the received uplink data and timing conditions. After receiving the serving PLMN rate control state, the UE adjusts the sending rate of the uplink data accordingly.
  • the serving PLMN rate control status includes two pieces of information.
  • the first part is: the remaining time of the validity period of the current serving PLMN rate control status period; the second part is: the amount of uplink data that is still allowed to be sent in the current rate control period.
  • the number of uplink data may be the number of data packets of the uplink data.
  • the mobile management management network element performs a connection with the session management and user plane network elements or Session modification process.
  • the NAS message in S905 is included in the application message, and the serving PLMN rate control status, if any, can be placed in the NAS message, and the NAS message here can also be said to be the NAS load.
  • S907 The mobility management network element forwards the uplink data to the user plane network element.
  • uplink data may be forwarded by the session management network element.
  • the user plane network element forwards the data to the mobility management network element.
  • the downlink data may be cached in the session management network element, and the data is forwarded from the session management network element to the mobile management network element.
  • the mobile management network element after receiving the downlink data, performs integrity protection and data encryption.
  • the mobile management network element forwards the downlink data to the access node through the application message, and the mobile management network element may send a connection establishment instruction message in the application message.
  • the mobility management network element may add the serving PLMN rate control status to the application message according to the received uplink data and timing conditions. After receiving the serving PLMN rate control state, the UE adjusts the sending rate of the uplink data accordingly.
  • the serving PLMN rate control status includes two pieces of information. For details, refer to S905.
  • the mobility management network element sends a UE context release command to the access node.
  • MT Mobile Terminated
  • the access node includes downlink data to be forwarded to the UE through an RRC downlink message.
  • step S917 will not be performed later. If early data transmission is used in S901, the access node sends an RRC early data completion message to the UE, which contains the NAS load from S905 and S911.
  • the access node If the mobile management network element requires feedback from the NAS, the access node sends a NAS delivery notification to the mobile management network element.
  • S919 Perform a connection release process between the UE and the mobility management network element. After that, the UE enters the leisure state again.
  • S921 Save the current serving PLMN rate control status, that is, the remaining time of the serving PLMN rate control validity period and the amount of uplink data that can be resent in the period.
  • the method shown in FIG. 9 can also be applied to a 4G system. If applied to a 4G system, the mobility management network element is an MME.
  • the rate control device sends the Serving PLMN rate control status information to the data sending device.
  • the data sending device receives the Serving PLMN rate control status information, it appropriately adjusts the transmission of data. Rate, so that the data sending device can adjust the rate of sending data in time, avoiding the possibility of packet loss caused by the rate control device when the rate exceeds the limit.
  • FIG. 10 provides a schematic flowchart of a method for performing rate control in the system shown in FIG. 2.
  • Figure 10 mainly describes the PLMN rate control method.
  • a rate management device is a mobile management network element
  • a data sending device is a user plane network element.
  • the UE Before initiating MO data, the UE is in an idle state.
  • the user plane network element After receiving the downlink data, the user plane network element sends it to the session management network element.
  • the session management network element buffers downlink data.
  • the session management network element After receiving the downlink data, the session management network element sends a downlink data arrival notification to the mobile management network element.
  • the mobility management network element may send a downlink data arrival notification confirmation message to the user plane network element according to the status or configuration of the UE.
  • the downlink data arrival notification confirmation message may include information such as the length of time that the session management network element needs to buffer data.
  • the mobility management network element adds a serving PLMN rate control status to the confirmation message according to the received downlink data condition and rate control timing condition.
  • the serving PLMN rate control status includes two pieces of information.
  • the first part is: the remaining duration of the validity period of the current PLMN rate control status period; the second part is: the amount of downlink data that is still allowed to be sent in the current rate control period.
  • the number of uplink data may be the number of data packets of the uplink data.
  • the mobility management network element determines that the UE is reachable, it sends paging information to the access node, the access node performs paging according to the information provided by the mobility management network element, and establishes an RRC connection.
  • the mobile management management network element performs a connection or session modification process with the session management and user plane network elements.
  • the session management network element sends the buffered downlink data to the mobility management network element.
  • the mobile management network element after receiving the downlink data, performs integrity protection and data encryption.
  • S1010 The mobility management network element forwards the downlink data to the access node through an application message.
  • S1011 The access node forwards the downlink data to the UE through an RRC downlink message.
  • NAS data PDUs can be sent to access nodes via RRC uplink messages.
  • the access node After receiving the uplink data, the access node forwards the uplink data to the mobile management network element through an application message.
  • the mobile management network element decrypts the data and performs an integrity check.
  • S1017 The mobility management network element forwards the downlink data to the user plane network element through the session management network element.
  • S1019 The access node waits for a period of time to detect whether there is NAS PDU activity.
  • S1021 Perform a connection release process between the UE and the mobility management network element. After this the UE enters the leisure state again.
  • S1023 Save the current serving PLMN rate control status, that is, the remaining time of the serving PLMN rate control cycle and the amount of uplink data that can be resent in the cycle.
  • the method shown in FIG. 10 can also be applied to a 4G system.
  • the mobility management network element is an MME.
  • the rate control device sends the Serving PLMN rate control status information to the data sending device.
  • the data sending device receives the Serving PLMN rate control status information, it appropriately adjusts the data transmission Rate, so that the data sending device can adjust the rate of sending data in time, avoiding the possibility of packet loss caused by the rate control device when the rate exceeds the limit.
  • the foregoing control device (or: device) or data sending device (or: device) for implementing rate control includes a hardware structure and / or software module corresponding to each function.
  • this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application of the technical solution and design constraints. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
  • control device or the data sending device may be divided into functional modules according to the foregoing method examples.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules may be implemented in the form of hardware or software functional modules. It should be noted that the division of the modules in the embodiments of the present application is schematic, and is only a logical function division. In actual implementation, there may be another division manner.
  • FIG. 11 shows a schematic structural diagram of a rate control device 110.
  • the rate control device 110 may be a mobile management network element, a session management network element, a user plane network element or a terminal, or a chip in these network elements or terminals, which is not specifically limited in this embodiment of the present application.
  • the rate control device 110 includes a receiving module 111 and a sending module 112.
  • the receiving module 111 is configured to receive a connection establishment request of a terminal, where the connection establishment request is used to establish a connection for data transmission by the terminal; the sending module 112 is configured to send rate-controlled time management information to a data sending device, Time management information is used by the data sending device to perform rate control on data sent over the connection, wherein the time management information includes start time indication information of a rate control time unit for rate control, and The start time indication information is used to indicate a start time of the rate control time unit.
  • the start time indication information is specifically any one of the following information: the time point when the connection is successfully established; the time point when the first data unit is transmitted on the connection; or, the next charging The starting point of the cycle.
  • the time management information further includes timing indication information
  • the timing indication information is specifically any one of the following information: when the terminal enters the connected state, Continue counting on the remaining value of the rate control time unit; when the terminal enters the connected state, restart timing of the rate control time unit; or, the next rate control time unit after the rate control time unit ends The timing starts when the first data unit is transmitted.
  • the time management information further includes timing indication information, and the timing indication information is specifically any one of the following information: the rate control time unit is at the beginning Continuous time counting after time; or the next rate control time unit starts timing when the first data unit is transmitted after the rate control time unit ends.
  • the device 110 is presented in the form of dividing each functional module in an integrated manner.
  • Module herein may refer to application-specific integrated circuits (ASICs), circuits, processors and memories that execute one or more software or firmware programs, integrated logic circuits, and / or other functions that may provide the above functions Device.
  • ASICs application-specific integrated circuits
  • processors and memories that execute one or more software or firmware programs, integrated logic circuits, and / or other functions that may provide the above functions Device.
  • the device 110 may take the form shown in FIG. 4.
  • the processor 41 in FIG. 4 may invoke a computer stored in the memory 43 to execute instructions, so that the device 110 executes the rate control method in the foregoing method embodiment.
  • the function / implementation process of the receiving module 111 and the sending module 112 in FIG. 11 may be implemented by the processor 41 in FIG. 4 calling a computer execution instruction stored in the memory 43.
  • the function / implementation process of the receiving module 111 and the sending module 112 in FIG. 11 may be implemented through the communication interface 44 in FIG. 4.
  • the function / implementation process of the receiving module 111 and the transmitting module 112 may also be implemented through pins or circuits.
  • the memory may be a storage unit in the chip, such as a register, a cache, and the like.
  • the storage unit may also be a storage unit located outside the chip, such as the memory shown in FIG. 4.
  • FIG. 12 shows a schematic structural diagram of a data sending device.
  • the data sending device may be a user plane network element, a session management network element, or a terminal, or may be a user plane network element, a session management network element, or a chip in the terminal, which is not specifically limited in this embodiment of the present application.
  • the data sending device 110 includes a receiving module 121 and a processing module 122.
  • the receiving module 121 is configured to receive rate control time management information.
  • the time management information includes start time indication information of a rate control time unit for performing rate control on a terminal for data transmission connection.
  • the start time indication information is used to indicate a start time of the rate control time unit; the processing module 122 is configured to perform rate control on data sent on the connection according to the rate time management information.
  • the start time indication information may be specifically the same as the start time indication information in FIG. 11. I won't repeat them here.
  • the time management information may specifically include timing indication information of FIG. 11. I won't repeat them here.
  • the time management information may specifically include the timing indication information of FIG. 11, and details are not described herein again.
  • 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 a control device or a data sending device to implement the foregoing rate control method.
  • the control device or data transmission device further includes a memory. This memory is used to store program instructions and data necessary for the control device or data transmission device. Of course, the memory may not be in the device.
  • the device When the device is a chip system, the device may be composed of a chip, and may also include a chip and other discrete devices, which are not specifically limited in the embodiments of the present application.
  • 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, for example, the computer instructions may be from a website site, a computer, a server, or a data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more servers, data centers, and the like that can be integrated with the medium.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (Solid State Disk) or the like).

Landscapes

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

Abstract

本申请公开了一种速率控制方法。在该方法中，控制设备接收终端的连接建立请求，该连接建立请求用于建立所述终端进行数据传输的连接；该控制设备向数据发送设备发送速率控制的时间管理信息，该时间管理信息用于该数据发送设备对在该连接上发送的数据进行速率控制，其中，时间管理信息包括用于进行速率控制的速率控制时间单元的起始时间指示信息，该起始时间指示信息用于指示该速率控制时间单元的起始时间。通过上述方案，解决了现有技术中数据发送设备在使用速率控制信息发送合理数量的数据时，依然被丢包或延迟处理的问题。

Description

一种速率控制的方法、装置和系统
本申请要求于2018年8月25日提交中国国家知识产权局、申请号为201810976506.4、发明名称为“一种速率控制的方法、装置和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种速率控制的方法、装置及系统。
背景技术
蜂窝物联网(cellular internet of things，CIOT)是一种通过窄带物联网(narrowband internet of things，NB-IoT)接入技术或增强机器通信(enhanced machine type communication,eMTC)的接入技术实现CIOT终端接入到移动通信网络的物联网。CIOT是一种支持低复杂度和低吞吐量的物联网设备的蜂窝网络。随着物联网技术的发展和普及，接入CIOT的用户设备(User Equipment，UE)越来越多。海量的CIOT UE发送和接收数据产生了大量的上行和下行数据流量，对于核心网中的管理网元实体和无线接入网中的无线承载造成了巨大的影响。为了解决这个问题，第三代合作伙伴项目(3rd generation partnership project，3GPP)定义了两种速率控制(rate control)机制，即服务公共陆地移动网络(Serving Public Land Mobile Network，Serving PLMN)速率控制和接入点名称(Access Point Name，APN)速率控制。
Serving PLMN速率控制用于Serving PLMN限制UE通过非接入层(Non-access stratum，NAS)消息传输用户数据分组数据单元(Packet Data Unit，PDU)的数量，APN速率控制用于归属公共陆地移动网络(Home Public Land Mobile Network，HPLMN)运营商限制UE发送上行用户数据的数量。这两种速率控制方法都可以有效的解决海量的连接带来的负载压力问题。但是在这两种速率控制方法中，数据发送方按照速率控制信息在自身理解的时间间隔内发送合理数量的数据PDU，在数据接收方可能被丢弃或延迟发送，增加了用户数据传输的丢包率与传输时延，影响业务特性与用户体验。
发明内容
本申请实施例提供一种速率控制的方法、装置及系统，以解决现有技术中数据发送设备在使用速率控制信息发送合理数量的数据时，依然被丢包或延迟处理的问题。
为达到上述目的，本申请实施例提供如下技术方案：
第一方面，提供一种速率控制方法，该方法包括：控制设备接收终端的连接建立请求，该连接建立请求用于建立该终端进行数据传输的连接；该控制设备向数据发送设备发送速率控制的时间管理信息，该时间管理信息用于所述数据发送设备对在所述连接上发送的数据进行速率控制，其中，该时间管理信息包括用于进行速率控制的速率控制时间单元的起始时间指示信息，该起始时间指示信息用于指示该速率控制时间单元的起始时间。
第二方面，提供了一种速率控制方法，该方法包括：数据发送设备接收速率控制的时 间管理信息；其中，该时间管理信息包括用于在终端进行数据传输的连接上进行速率控制的速率控制时间单元的起始时间指示信息，该起始时间指示信息用于指示该速率控制时间单元的起始时间；接着，该数据发送设备根据该速率时间管理信息对在该连接上发送的数据进行速率控制。
基于本申请实施例第一方面或第二方面提供的速率控制方法，数据发送设备收到包括起始时间指示信息的时间管理信息后，就可以和控制设备确定相同的开始速率控制计时的时间点，这样数据发送设备在使用时间管理信息发送合理数量的数据单元给控制设备时，控制设备就会将这些数据也作为合法数据，不会对这些数据进行丢包或延迟处理。
在第一方面或第二方面的一种可能的设计中，该起始时间指示信息具体可以为：该连接建立成功的时间点；或，在该连接上传输第一个数据单元的时间点；或，下一个计费周期的起始时间点等。
在第一方面或第二方面的一种可能的设计中，若该速率控制为服务公共陆地移动网络速率控制，则该控制设备可以为移动管理网元、或会话管理网元；该数据发送设备为终端。
在一种可能的设计中，若该速率控制为服务公共陆地移动网络速率控制，则该控制设备为移动管理网元、或会话管理网元，该数据发送设备为用户面网元；或者，该控制设备为移动管理网元，该数据发送设备为会话管理网元。
在第一方面或第二方面的一种可能的设计中，若该速率控制为数据网络名速率控制，则该控制设备为用户面网元；该数据发送设备为终端。
在第一方面或第二方面的一种可能的设计中，若该速率控制为接入点名称速率控制，则该控制设备为用户面网元；该数据发送设备为终端。
在第一方面或第二方面的一种可能的设计中，若该数据发送设备为该终端，则时间管理信息还包括计时指示信息，其中，该计时指示信息具体为：该终端进入连接态时，在该速率控制时间单元的剩余值上继续计时；或，该终端进入连接态时，对该速率控制时间单元重新开始计时；或，下一个速率控制时间单元在该速率控制时间单元结束后传输第一个数据单元时开始计时。
在第一方面或第二方面的一种可能的设计中，若该数据发送设备为会话管理网元或用户面网元，则该时间管理信息还包括计时指示信息，该计时指示信息具体为：速率控制时间单元在起始时间后连续计时；或者，下一个速率控制时间单元在所述速率控制时间单元结束后传输第一个数据单元时开始计时。
在第一方面或第二方面的一种可能的设计中，该时间管理信息还包括：速率控制值。该速率控制值用于指示数据发送设备在该速率控制时间单元内发送的数据单元的最大值。
在第一方面或第二方面的一种可能的设计中，该时间管理信息还包括：速率控制时间单元信息。
第三方面，本申请的实施例提供一种速率控制装置，该装置具有实现上述第一方面任意一项提供的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第四方面，本申请的实施例提供一种数据发送装置，该装置具有实现上述第二方面任意一项提供的方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实 现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第五方面，本申请的实施例提供一种速率控制装置，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该速率控制装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该速率控制装置执行如上述第一方面任意一项的速率控制方法。
第六方面，本申请的实施例提供一种速率控制装置，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述第一方面中任一项所述的速率控制方法。
第七方面，本申请的实施例提供一种数据发送装置，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该数据发送装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该数据发送装置执行如上述第二方面任意一项的速率控制方法。
第八方面，本申请的实施例提供一种数据发送装置，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述第二方面中任一项所述的速率控制方法。
第九方面，本申请的实施例提供一种速率控制系统，包括上述第三方面中任一项的速率控制装置，和第四方面中任一项的数据发送装置；或，包括上述第五方面或第六方面所述的速率控制装置，和上述第七方面或第八方面所述的数据发送装置。
第十方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面或第二方面中任一所述的方法。
第十一方面，本申请实施例提供了一种计算机存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述第一方面或第二方面中所述的方法。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1所示为本申请实施例的一种可能的系统网络示意图；
图2所示为本申请实施例的另一种可能的系统网络示意图；
图3所示为本申请实施例的另一种可能的系统网络示意图；
图4所示为本申请实施例提供的计算机设备示意图；
图5所示为本申请实施例提供的一种速率选择的方法流程示意图；
图6所示为本申请实施例提供的另一种速率选择的方法流程示意图；
图7所示为本申请实施例提供的另一种速率选择的方法流程示意图；
图8所示为本申请实施例提供的另一种速率选择的方法流程示意图；
图9所示为本申请实施例提供的另一种速率选择的方法流程示意图；
图10所示为本申请实施例提供的另一种速率选择的方法流程示意图；
图11所示为本申请实施例提供的一种的装置结构示意图；
图12所示为本申请实施例提供的另一种的装置结构示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步 地详细描述。方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。
其中，在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
在描述本申请实施例之前，先对Serving PLMN速率控制、APN速率控制和数据网络名(Data Network Name，DNN)速率控制进行简单的介绍。Serving PLMN速率控制用于Serving PLMN限制上下行通过NAS消息传输PDU的数量，通过NAS消息传输的PDU也称为NAS数据PDU，是一种通过控制面NAS消息传输的用户数据(NAS messages with user data over control plane)，Serving PLMN速率控制也可以理解为限制上下行携带有用户数据的NAS消息的数量。上行速率控制用于限制UE发送的NAS数据PDU的数量，下行速率控制用于限制用户面网元或会话管理网元发送的NAS数据PDU数量，上行速率控制和下行速率控制对于NAS数据PDU的限制可以是不同的。Serving PLMN速率控制信息由运营商配置在核心网中的管理网元或实体中，一般设置为“每6分钟X个NAS数据PDU”，这里的X是一个整数，且不应该小于10；这里的NAS数据PDU也可以理解为是用来传输用户数据的NAS消息。比如：对于长期演进的分组系统(Evolved Packet System，下文简称EPS)，在分组数据网络(Packet Data Network，下文简称PDN)连接建立过程中，管理网元可能向UE、PDN网关(PDN Gateway，PGW)或服务能力开放网元(Service Capability Exposure Function，SCEF)发送本地的Serving PLMN速率控制信息。对于第五代(5rd generation，5G)系统，管理网元可能向UE、会话管理功能(session management function，SMF)、用户面功能(user plane function，UPF)或网络开放功能(Network Exposure Function，NEF)发送本地的Serving PLMN速率控制信息。
APN速率控制用于归属运营商限制UE发送到指定APN的上行用户数据PDU的数量，所限制的上行用户数据PDU可以是通过控制面NAS消息传输的用户数据，也可以是通过用户面传输的用户数据。APN速率控制信息由运营商配置在核心网中的用户面网元或实体中，一般设置为指定时间单元内UE发送的用户数据消息(user data message)的最大个数，比如：“每天X个用户数据消息”，这里的X是一个整数，没有最小值的限制；这里的用户数据消息也可以理解为数据单元(data unit)，或数据包(data packet)，这里的时间单元也称为时间单位(time unit)，或时间间隔(time interval)等。支持APN速率控制的UE也可以支持异常报告数据包的限制，即UE在超过每天最多发送Y条信息的限制后，仍然可以继续发送一定数量的异常报告数据包。对于EPS，APN速率控制信息配置在PGW或SCEF 中。一般的，APN速率控制信息包含三个信息：每个时间单元可发送数据包(或者说是：数据单元)的数目；如果数据包数量达到限制值后，UE是否允许继续发送异常报告；如果允许UE在这种情况下发送异常报告，则包含一个可发送异常报告的数据包的数目。DNN速率控制，与APN速率控制类似，这里不予赘述。一般地，APN速率控制应用于EPS，DNN速率控制应用于5GS。
在Serving PLMN速率控制方法、APN速率控制和DNN速率控制方法中，速率控制信息都是基于一个时间间隔的，可以理解为是：下发的速率控制信息在时间间隔内有效，在时间间隔外就是无效的。发明人在研究过程中，发现这三种速率控制方法中，对于控制设备和数据发送设备之间，并没有协调时间间隔的开始时间，从而导致双方执行速率控制的时间不同步。比如：Serving PLMN速率控制信息为“每6分钟20个NAS数据PDU”，数据发送设备将时间间隔理解为第一次发送数据时启动计时，比如：10:02分第一次发送数据，而控制设备将时间间隔理解为PDN连接建立时启动计时，比如：10:00分PDN连接建立。这样，按照控制设备的理解，在[10:00,10:06)这6分钟内可以接收20个数据，在[10:06,10:12)这6分钟内可以接收20个数据。按照数据发送设备的理解，在[10:02，10:08)这段时间可以发送20个数据，在[10:08，10:14)这段时间可以发送20个数据。
假如数据发送设备在[10:02,10:06)这4分钟内发了15个数据，[10:06,10:08)这2分钟内发了5个数据。然后，在[10:08,10:12)这4分钟内发了16个数据。这样，数据发送设备方是严格按照Serving PLMN速率控制信息来发送数据的，并没有超过速率控制限额。但是对于控制设备来说，[10:06,10:12)接收的数据为5+16，即21个数据，就超出了Serving PLMN速率控制信息规定的[10:06,10:11]只能接收不超过20个数据的上限。所以，控制设备会将第21个数据丢弃。也就是说，在现有技术中，由于双方没有协调时间间隔的开始时间，从而导致了双方执行速率控制的时间不同步，也增加了数据(比如：用户数据)传输的丢包率与传输时延，影响了业务特性与用户体验。
为了解决上述问题，本申请实施例提供了一种速率控制方法和系统。下面对本申请实施例提供的速率控制系统和方法一一进行介绍。
如图1所示，本申请实施例提供了一种速率控制系统100，该系统100包括：控制设备10和数据发送设备20。上述系统架构100可以用于执行本申请提供的速率控制方法。
控制设备10，用于接收终端的连接建立请求，所述连接建立请求用于建立所述终端进行数据传输的连接；向数据发送设备20发送速率控制的时间管理信息，所述时间管理信息用于数据发送设备20对在所述连接上发送的数据进行速率控制。其中，该时间管理信息包括进行速率控制的速率控制时间单元的起始时间指示信息，起始时间指示信息用于指示速率控制时间单元的起始时间。
数据发送设备20，用于接收该时间管理信息。可选的，数据发送设备20根据时间管理信息对在该连接上发送的数据进行速率控制。
其中，这里的连接建立请求可以为PDU会话建立请求，也可以为PDN连接建立请求，本申请不做限定。具体实现中，若连接建立请求为PDU会话建立请求，则建立的连接为PDU会话；若连接建立请求为PDN连接建立请求，则建立的连接为PDN连接。
在具体实现中，该起始时间指示信息可以为如下信息中的任意一个：所述连接建立成 功的时间点；在所述连接上传输第一个数据单元的时间点；或，下一个计费周期的起始时间点。
在具体实现中，该速率控制可以为Serving PLMN速率控制，也可以为APN速率控制，也可以为DNN速率控制。
在具体实现中，在速率控制为Serving PLMN速率控制的情况下，该控制设备对应的设备或实体可以为移动管理网元、或会话管理网元，该数据发送设备可以为终端或用户面网元；或者，该控制设备可以为移动管理网元，数据发送设备可以为会话管理网元。
在具体实现中，在速率控制为DNN速率控制或APN速率控制的情况下，该控制设备可以为用户面网元，数据发送设备可以为终端；在速率控制为Serving PLMN速率控制的情况下，该控制设备可以为移动管理网元，数据发送设备可以为用户面网元。
在具体实现中，若数据发送设备可以为终端，则，时间管理信息还包括计时指示信息，计时指示信息具体为如下信息中的任意一个：终端进入连接态时，在速率控制时间单元的剩余值上继续计时；终端进入连接态时，对速率控制时间单元重新开始计时；或，下一个速率控制时间单元在所述速率控制时间单元结束后传输第一个数据单元时开始计时。
在具体实现中，若数据发送设备为会话管理网元或用户面网元，则时间管理信息还包括计时指示信息，计时指示信息具体为如下信息中的任意一个：速率控制的时间单元在起始时间后连续计时；或，下一个速率控制时间单元，即速率控制的下一个时间单元，在所述速率控制时间单元结束后传输第一个数据单元时开始计时。
进一步的，时间管理信息还可以包括速率控制值，该速率控制值用于指示数据发送设备在速率控制时间单元内发送的数据单元的最大值。这里的数据单元，在具体实现中，可以是发送数据单元的消息，也可以是发送的数据单元，也可以是其他形式，本申请不做限定。比如：数据单元可以封装在一个NAS消息中，这样，数据发送设备发送的数据单元的个数，就是发送的封装有该数据单元的NAS消息的个数。
比如，对于APN或DNN速率控制，数据发送设备发送的是上行用户数据消息(uplink user data messages)，一个消息中包含了一个数据单元(PDU)，因此这里的速率控制值可以用PDU个数表示，也可以用包含PDU的NAS消息个数来表示。再比如，对于上行Serving PLMN速率控制，数据发送设备是通过控制面NAS消息传输的用户数据，一个NAS消息中包含了一个数据单元(PDU)，因此这里的速率控制值可以用PDU个数表示，也可以用包含PDU的NAS消息个数来表示。再比如，对于下行Serving PLMN速率控制，数据发送设备发送的是下行数据PDU(downlink Data PDUs)，没有用NAS消息进行封装，其本身就是PDU，因此这里的速率控制值可以用PDU个数表示。
可选的，时间管理信息还可以包括：速率控制时间单元的信息。
通过本实施例提供的系统，控制设备发送速率时间单元的起始时间指示信息，数据发送设备收到该起始时间指示信息后，就可以和控制设备确定相同的开始速率控制计时的时间点，这样数据发送设备在使用时间管理信息发送合理数量的数据单元给控制设备时，控制设备就会将这些数据也作为合法数据，不会对这些数据进行丢包或延迟处理。从而解决了现有技术中，数据发送方在使用速率控制信息发送合理数量的数据PDU时，被丢包或延迟处理的问题。
可选的，上述速率控制系统100可以应用于第四代(4th generation，4G)网络，也即EPS，5G网络以及未来其它的网络，本申请实施例对此不作具体限定。
其中，若上述数据传输系统10应用于5G网络，则如图2所示的5G架构图200。移动管理网元所对应的设备或者实体为接入和移动性管理功能(access and mobility management function，AMF)；会话管理网元所对应的设备或者实体为SMF；用户面网元所对应的设备或者实体为UPF、或NEF。
该架构还可以包括：核心网控制面包括认证服务器功能(authentication server function，AUSF)，网络切片选择功能(network slice selection function，NSSF)，NEF，网络功能仓储功能(NF repository function，NRF)，统一数据管理(unified data management，UDM)，策略控制功能(policy control function，PCF)，或应用功能(application function，AF)。
AMF还可以负责注册管理，移动性管理，或合法监听等功能，本申请实施例对此不作具体限定。
SMF还可以用于进行会话管理，包括：会话建立，会话修改，会话释放，终端的网络之间互连的协议(internet protocol，IP)地址分配和管理，UPF的选择和控制，或合法监听等与会话相关的控制功能。
UPF还可以用于根据SMF的路由规则执行用户数据包转发。AUSF用于执行终端的安全认证。NSSF用于为终端选择网络切片。NEF以北向应用程序接口(Application Programming Interface，API)的方式向第三方开放网络功能。NRF为其他网元提供网络功能实体信息的存储功能和选择功能。UDM用来管理用户签约上下文。PCF用来管理用户策略。AF用于管理用户应用。
在图2所示架构中，N1接口为UE与AMF之间的参考点，用于NAS消息的传递等；N2接口为(R)AN和AMF的参考点；N3接口为(R)AN和UPF之间的参考点，用于传输用户面的数据等；N4接口为SMF和UPF之间的参考点，用于传输例如N3连接的隧道标识信息，数据缓存指示信息，以及下行数据通知消息等信息；N6接口为UPF和DN之间的参考点，用于传输用户面的数据等。图2所示的5G网络中的AMF网元、SMF网元、AUSF网元或者UDM网元等控制面网元之间可以直接或间接通信，比如可以采用服务化接口进行交互。比如，AMF网元对外提供的服务化接口可以为Namf；SMF网元对外提供的服务化接口可以为Nsmf；AUSF网元对外提供的服务化接口可以为Nausf；UDM网元对外提供的服务化接口可以为Nudm，等。相关描述可以参考TS 23.501标准中的5G系统架构(5G system architecture)图，在此不予赘述。
需要说明的是，图2中的各个网元之间的接口名字只是一个示例，具体实现中接口名字可能为其他名字，本申请实施例对此不作具体限定。
需要说明的是，上述5G网络中的终端、AMF网元、SMF网元、UPF网元、NEF网元和PCF网元等仅是一个名字，名字对设备本身不构成限定。在5G网络以及未来其它的网络中，UE、AMF、SMF、UPF、NEF和PCF所对应的网元或实体或设备也可以是其他的名字，本申请实施例对此不作具体限定。例如，该UDM实体还有可能被替换为用户归属服务器(home subscriber server，HSS)或者用户签约数据库(user subscription database，USD)或者数据库实体，在此进行统一说明，以下不再赘述。
其中，若上述数据传输系统10应用于4G网络，则如图3所示的EPS架构图300。移动管理网元所对应的设备或者实体为移动性管理实体(mobility management entity，MME)；用户面网元所对应的设备或者实体为PGW或SCEF。
MME：主要负责用户移动管理和会话管理的控制平面功能，包括非接入层NAS信令及安全，跟踪区列表的管理(tracking area List)的管理，分组数据网络网关PGW与服务网元(serving gateway，SGW)的选择等。
PGW：作为PDN连接的锚定点，负责UE的网络之间互连的协议(Internet Protocol，IP)地址分配，UE的数据报文过滤、速率控制、或生成计费信息等。
此外，该系统还可以包括SGW，演进的通用陆地无线网(evolved universal terrestrial radio access network，EUTRAN)，服务GPRS支持节点(serving GPRS supporting node，SGSN)，归属用户服务器(home subscriber server，HSS)，或策略和计费规则功能(policy and charging rules function，PCRF)。
其中，SGW主要负责UE的数据传输、转发以及路由切换等，并作为UE在演进型基站(Evolved NodeB，eNodeB)之间切换时的本地移动性锚定点(对于每一个用户设备，每个时刻仅有一个SGW为之服务)。
EUTRAN由多个eNodeB组成的网络，实现无线物理层功能、资源调度和无线资源管理、无线接入控制以及移动性管理功能。eNodeB之间可以通过X2接口相连，可以在基于X2的切换过程中用来传输数据。eNodeB通过用户面接口S1-U和SGW相连，使用通用分组无线系统隧道协议用户面(general packet radio system general tunneling protocol user plane，GTP-U)来传送用户数据；通过控制面接口S1-MME和移动性管理实体相连，采用S1-AP协议实现无线接入承载控制等功能。
SGSN为2G接入网GSM/EDGE无线接入网(GSM/EDGE radio access network，GERAN)，3G接入网通用陆地无线接入网(universal terrestrial radio access network，UTRAN)与3GPP的演进分组核心网(Evolved Packet Core，EPC)的接入节点，负责从GERAN，UTRAN到EPC承载的建立和数据的转发。
HSS主要用于存储移动用户的签约数据。PCRF负责计费管理和策略控制，包括策略与计费控制(policy and charging control，PCC)规则，服务质量(quality of service，QoS)规则。
SCEF(在图中未示出)，提供了一种安全的方式暴露3GPP网络接口提供的服务和能力，同时提供一种发现暴露的能力和服务的方法。MME可以通过SCEF和HSS进行交互。
其中，本申请实施例中所涉及到的终端(terminal)可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备。所述终端也可以称为用户设备(user equipment，UE)，移动台(mobile station，MS)，终端设备(terminal device)，还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication,MTC)终端、CIOT终端等。
可选的，图1中的控制设备或数据发送设备可以是一个单独的网元，也可以是由多个网元共同实现，也可以作为一个网元内的一个功能模块，本申请实施例对此不作具体限定。可以理解的是，上述功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。
如图4所示，图1中的控制设备10，或者图2中的AMF、SMF和UE，或者图3中的MME和UE，可以以图4中的计算机设备(或系统)的方式来实现。
图4所示为本申请实施例提供的计算机设备示意图。计算机设备400包括至少一个处理器41，通信线路42，存储器43以及至少一个通信接口44。
处理器41可以是一个通用中央处理器(CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路42可包括一通路，在上述组件之间传送信息。所述通信接口44，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(RAN)，无线局域网(Wireless Local Area Networks，WLAN)等。
存储器43可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路与处理器相连接。存储器也可以和处理器集成在一起。
其中，所述存储器43用于存储执行本申请方案的应用程序代码，并由处理器41来控制执行。所述处理器41用于执行所述存储器43中存储的应用程序代码。
在具体实现中，作为一种实施例，处理器41可以包括一个或多个CPU，例如图4中的CPU0和CPU1。
在具体实现中，作为一种实施例，计算机设备400可以包括多个处理器，例如图4中的处理器41和处理器48。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，计算机设备400还可以包括输出设备45和输入设备46。输出设备45和处理器41通信，可以以多种方式来显示信息。例如，输出设备45可以是液晶显示器(liquid crystal display，LCD),发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备46和处理器41通信，可以以多种方式接受用户的输入。例如，输入设备46可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的计算机设备400可以是一个通用计算机设备或者是一个专用计算机设备。在具 体实现中，计算机设备400可以是台式机、便携式电脑、网络服务器、掌上电脑(Personal Digital Assistant，PDA)、移动手机、平板电脑、无线终端设备、通信设备、嵌入式设备或有图4中类似结构的设备。本申请实施例不限定计算机设备400的类型。
示例性的，图1中的控制设备10可以为图4所示的设备，控制设备10的存储器中存储了一个或多个软件模块。控制设备10可以通过处理器以及存储器中的程序代码来实现软件模块，实现速率控制。
下面结合流程图来介绍本申请实施例提供的速率控制的方法。
图5提供了一种可以在图1或图2所示的系统中执行速率控制的方法流程示意图。图5主要介绍的是Serving PLMN速率控制方法。本实施例中，是将连接以会话为例，连接建立请求以PDU会话建立请求为例来进行说明的。
S501，UE经由接入节点发送PDU会话建立请求给AMF。AMF接收该PDU会话建立请求。
具体的，UE成功注册到网络后，根据上层(upper layers)的请求，需要建立一个新的PDU会话来进行上下行用户数据的传输。UE发起到网络侧的PDU会话建立流程。具体地，UE向AMF发送NAS消息，例如上行NAS传输(UL NAS transport)消息，其中包含PDU会话标识符、请求类型和N1会话管理容器等，N1会话管理容器中包含有PDU会话建立请求。
S503，AMF选择SMF。然后向选择的SMF发送会话上下文创建请求。SMF接收该会话上下文创建请求。该会话上下文创建请求中包括S501中的PDU会话建立请求。
其中，AMF选择SMF的方法可以参考现有技术中的方法，比如，可以根据UE提供的DNN或单个网络切片选择辅助信息(Single Network Slice Selection Assistance Information，S-NSSAI)来选择SMF，这里不予赘述。
在实际实现中，控制设备可以是AMF，也可以是SMF。这里首先以控制设备为AMF为例来说明。
在AMF希望控制下行NAS数据PDU的发送速率的情况下，该会话上下文创建请求中包括Serving PLMN速率控制时间管理信息。后续，待PDU会话建立成功后，用户面网元根据Serving PLMN速率控制时间管理信息对在该PDU会话上发送的数据进行速率控制。
其中，Serving PLMN速率控制时间管理信息在具体实现中可以通过特定的信息元素(Information Element，IE)来传递。这里的信息元素也可以称为信元。
在具体实现中，作为一种实现方式，该Serving PLMN速率控制时间管理信息包括进行Serving PLMN速率控制的Serving PLMN速率控制时间单元的起始时间指示信息。所述起始时间指示信息用于指示Serving PLMN速率控制时间单元的起始时间。
其中，该起始时间指示信息形式多样，比如可以为：a)所述连接建立成功的时间点；也可以为：b)在所述连接上传输第一个数据单元的时间点；也可以为：c)下一个计费周期的起始时间点。本申请具体不做限定。其中，对于b)，由于连接上可以传输数据了，所以是在连接建立成功后的。在本实施例中，这里的连接具体是指PDU会话。
在具体实现中，作为一种实现方式，若数据发送设备为SMF或用户面网元，则时间管理信息还可以包括计时指示信息，该计时指示信息具体为如下信息中的任意一个：第一 种：速率控制的时间单元在起始时间后连续计时；或者，第二种：下一个速率控制时间单元在所述速率控制时间单元结束后传输第一个数据单元时开始计时。
在具体实现中，也可以根据运营商的策略或配置来选择计时指示，本申请不做具体限定。
在具体实现中，作为一种实现方式，该Serving PLMN速率控制时间管理信息还可以包括该Serving PLMN速率控制时间单元。该时间单元可以为6分钟，当然也可以为其他时间。在具体实现中，该时间单元也可以是AMF和用户面网元事先协商好了，在这种情况下，会话上下文创建请求消息中就可以不携带时间单元。
在具体实现中，作为一种实现方式，Serving PLMN速率控制时间管理信息还可以包括：Serving PLMN速率控制值。Serving PLMN速率控制值用于指示用户面网元在Serving PLMN速率控制时间单元内发送的数据单元的最大值。
S505，SMF发送会话上下文创建响应给AMF。AMF接收该会话上下文创建响应。
S507，SMF发送会话建立请求给用户面网元(这里用户面网元可以是UPF或NEF)，其中会话建立请求携带Serving PLMN时间管理信息。用户面网元接收该会话建立请求。后续，待会话建立成功后，用户面网元根据Serving PLMN时间管理信息对在该PDU会话上发送的数据进行速率控制。
在具体实现中，执行S507时，SMF还可以进行UPF的选择，比如请求类型为“初始化请求”的情况下。具体选择UPF的方法可以参考现有技术，这里不再赘述。
S509，用户面网元发送会话建立响应给SMF。SMF接收该会话建立响应。
S511，SMF调用移动管理网元的N1N2消息传输服务操作，和AMF进行消息传输。通过调用该N1N2消息传输服务，SMF将发送给UE的PDU会话建立接受消息发送给AMF，作为在步骤S503中收到的PDU会话建立请求的响应消息。
S513，AMF通过接入节点将S511中收到的PDU会话建立接受消息发送给UE，作为步骤S501的响应消息，UE接受该PDU会话建立接受消息。
具体地，AMF向UE发送NAS消息，例如下行NAS传输(DL NAS transport)消息，其中包括SMF在S511中发送的PDU会话建立接受消息。
在具体实现中，作为一种实现方式，在AMF希望控制上行NAS数据PDU的发送速率的情况下，步骤513中还可以携带上述S503中的时间管理信息，关于时间管理信息本步骤不再详述。后续，待PDU会话建立成功后，UE根据时间管理信息对在该PDU会话上发送的数据进行速率控制。在S513后，UE可以获知PDU会话建立成功。
其中，关于起始时间指示信息的选择：AMF可以根据UE发送数据的频率来选择。比如，频发数据的UE可以选择上述S503中描述的a)或b)或c)作为起始时间指示信息；不频发数据的UE可以选择上述S503中描述的b)或c)作为起始时间指示信息。
AMF也可以根据UE的状态来选择。比如，静止的UE一般是节能的UE，对于静止的UE可以选择上述S503中描述的b)作为起始时间指示。
AMF还可以根据UE通信的持续时长来选择。对于通信持续时间长的UE，可以选择上述S503中描述的b)作为起始时间指示。AMF还可以根据UE是否有外部电源供给来选择。对于有外部电源供给的UE，可以选择上述S503中描述的a)或b)作为起始时间指示。当 然，在具体实现中，也可以根据运营商的策略或配置来选择合适的起始时间指示信息，本申请不做具体限定。
在具体实现中，作为一种实现方式，若数据发送设备为UE，则时间管理信息还可以包括计时指示信息，该计时指示信息具体为如下信息中的任意一个：a1)UE进入连接态时，在Serving PLMN速率控制时间单元的剩余值上继续计时；或者，b1)UE进入连接态时，对Serving PLMN速率控制时间单元重新开始计时；或者，c1)Serving PLMN速率控制的下一个时间单元，在Serving PLMN速率控制时间单元结束后传输第一个数据单元时开始计时。
其中，关于计时指示信息的选择，AMF可以根据UE发送数据的频率来选择。比如，频发数据的UE可以选择a1)作为计时指示；不频发数据的UE可以选择b1)或c1)作为计时指示。AMF还可以根据UE周期通信的间隔时间来选择。如果周期通信的间隔时间比较长，则选择b1)比较合适。当然，在具体实现中，也可以根据运营商的策略或配置来选择计时指示，本申请不做具体限定。
可以理解的是，在本实施例中，图中示出的是AMF对上行NAS数据PDU的发送速率和下行NAS数据PDU的发送速率都进行了控制。但在具体实现中，AMF对上行NAS数据PDU的速率控制和下行NAS数据PDU的速率控制是独立解耦的，AMF也可以只对上行NAS数据PDU的发送速率进行控制，这种情况下，S503和S507中就可以不携带时间管理信息；AMF也可以只对下行NAS数据PDU的发送速率进行控制，这种情况下，S513中就可以不携带时间管理信息。AMF在同时执行上行NAS数据PDU的速率控制和下行NAS数据PDU的速率控制时，二者的时间管理信息可以相同，也可以不同，本申请对此不做限定。
在图5中是以用户面网元或UE作为数据发送设备来描述的。在实际实现中，SMF也可以作为数据发送设备。在SMF作为数据发送设备的方案中，可以采用图5相似的方法，和图5所不同的是：SMF通过S503获得时间管理信息，根据时间管理信息，在PDU会话建立后对在PDU会话上发送的数据进行速率控制。然后，如果用户面网元不需要作为数据发送设备，那么S507中就可以不携带时间管理信息。如果用户面网元也需要作为数据发送设备，那么S507可以和图5中一样。
通过本实施例提供的方法，AMF发送Serving PLMN速率控制时间单元的起始时间指示信息，用户面网元、SMF或UE在收到该起始时间指示信息后，就可以和AMF确定相同的开始速率控制计时的时间点，这样用户面网元、SMF或UE在使用速率控制信息发送合理数量的NAS数据PDU给AMF时，AMF就会将这些数据也作为合法数据，不会对这些数据进行丢包或延迟处理，从而解决了现有技术中，数据发送方在使用速率控制信息发送合理数量的NAS数据PDU时，被丢包或延迟处理的问题。
在图5中是以AMF作为速率控制设备来描述的。在实际实现中，SMF也可以取代AMF作为速率控制设备。在SMF作为速率控制设备的方案中，可以采用图5相似的方法，和图5所不同的是，S503中不携带时间管理信息。在S507步骤中，在SMF希望控制下行数据的发送速率的情况下，在S507的会话建立请求中携带时间管理信息。以使用户面网元收到该时间管理信息后，根据时间管理信息，在PDU会话建立后对在该PDU会话上发送的下 行数据进行速率控制。在SMF希望控制上行数据的发送速率的情况下，在PDU会话建立接受消息中携带时间管理信息，并在S511中发送给AMF，然后AMF在S513中将携带有时间管理信息的PDU会话建立接受消息发送给UE，可选地，SMF也可以直接在S511中携带时间管理信息给AMF，并在S513中直接发送给UE，也即不在PDU会话建立接受消息中携带时间管理信息(图中未示出)。这样UE在收到该时间管理信息后，根据时间管理信息，在PDU会话建立后对在该PDU会话上发送的上行数据进行速率控制。
通过本实施例提供的方法，SMF发送Serving PLMN速率控制时间单元的起始时间指示信息，用户面网元或UE收到该起始时间指示信息后，就可以和SMF确定相同的开始速率控制计时的时间点，这样用户面网元或UE在使用时间管理信息发送合理数量的数据给SMF时，SMF就会将这些数据也作为合法数据，不会对这些数据进行丢包或延迟处理。从而解决了现有技术中，数据发送方在使用速率控制信息发送合理数量的NAS数据PDU时，被丢包或延迟处理的问题。
在图5所示的实施例中，AMF、SMF、用户面网元或终端的动作可以分别由AMF、SMF、用户面网元或终端根据上述提及的存储器中的软件模块来执行。本申请实施例对此不作任何限制。
图6提供了一种可以在图1或图2所示的系统中执行速率控制的方法流程示意图。图6主要介绍的是DNN速率控制方法。本实施例中，是将连接以会话为例，连接建立请求以PDU会话建立请求为例来进行说明的。
S601，同S501。
S603，和S503的主要不同是，会话上下文创建请求中不携带DNN速率控制的时间管理信息。
S605，同S505。
S607，和S507的主要不同是，会话建立请求中不携带DNN速率控制的时间管理信息。
S609，用户面网元发送会话建立响应给SMF。SMF接收该会话建立响应。
在用户面网元希望控制UE发送到该PDU会话所关联的DNN的上行数据的发送速率的情况下，该会话建立响应消息中包括DNN速率控制的时间管理信息。后续，待PDU会话建立成功后，终端根据DNN速率控制的时间管理信息对在该PDU会话上发送的数据进行速率控制。
其中，DNN速率控制的时间管理信息在具体实现中可以通过协议配置选项(Protocol Configuration Options，PCO)或扩展型协议配置选项(extended Protocol Configuration Options，ePCO)来传递。
在具体实现中，作为一种实现方式，该DNN速率控制的时间管理信息中包括DNN速率控制时间单元的起始时间指示信息。所述起始时间指示信息用于指示DNN速率控制时间单元的起始时间。
其中，该起始时间指示信息形式多样，具体实现中，也可以采用S503中的a)、b)和c)三种形式。本申请具体不做限定。
其中，关于起始时间指示信息的选择：用户面网元可以采用S513中AMF选择起始时间指示信息的方法来选择起始时间指示信息。比如：根据UE发送数据的频率来选择，或根 据UE的状态来选择；或根据UE通信的持续时长来选择。这里不再赘述。
在具体实现中，作为一种实现方式，DNN速率控制的时间管理信息还可以包括计时指示，该计时指示具体为如下信息中的任意一个：a1)UE进入连接态时，在DNN速率控制时间单元的剩余值上继续计时；或者，b1)UE进入连接态时，对DNN速率控制时间单元重新开始计时；或者，c1)DNN速率控制的下一个时间单元，在DNN速率控制时间单元结束后传输第一个数据单元时开始计时。
其中，关于计时指示信息的选择，用户面网元可以采用S513中AMF选择计时指示信息的方法来选择计时指示信息。比如：根据UE发送数据的频率来选择，或根据UE周期通信的间隔时间来选择，这里不再赘述。
在具体实现中，作为一种实现方式，该DNN速率控制的时间管理信息还可以包括该DNN速率控制时间单元。这里的时间单元不做具体限定。在具体实现中，该时间单元也可以是用户面网元和终端事先协商好了，在这种情况下，会话建立响应中就可以不携带时间单元。
在具体实现中，作为一种实现方式，DNN速率控制的时间管理信息还可以包括：DNN速率控制值，DNN速率控制值用于指示终端在DNN速率控制时间单元内发送的数据单元的最大值。
S611，SMF调用移动管理网元的N1N2消息传输服务操作，和AMF进行消息传输。通过调用该N1N2消息传输服务，SMF将发送给UE的PDU会话建立接受消息发送给AMF，作为在步骤S603中收到的PDU会话建立请求的响应消息，SMF在PDU会话建立接受消息中携带S609中的时间管理信息。可选地，SMF可以在N1N2消息传输中携带S609中的时间管理信息，也即不在PDU会话建立接受消息中携带时间管理信息(图中未示出)。
S613，AMF通过接入节点向UE发送PDU会话建立接受消息，作为步骤S501的响应消息，UE接受该PDU会话建立接受消息。
具体地，AMF向UE发送NAS消息，例如下行NAS传输(DL NAS transport)消息，其中包括SMF在S611中发送的PDU会话建立接受消息。若SMF将上述S609中的时间管理信息携带在PDU会话建立接受消息中，则UE接收到PDU会话建立接受消息中携带的时间管理信息；若SMF将上述S609中的时间管理信息通过N1N2消息传输传递给AMF，则UE接收到NAS消息中携带的时间管理信息。
通过本实施例提供的方法，用户面网元发送DNN速率控制时间单元的起始时间指示信息，UE收到该起始时间指示信息后，就可以和用户面网元确定相同的开始速率控制计时的时间点，这样UE在使用时间管理信息发送合理数量的数据给用户面网元时，用户面网元就会将这些数据也作为合法数据，不会对这些数据进行丢包或延迟处理。从而解决了现有技术中，数据发送方在使用速率控制信息发送合理数量的数据时，被丢包或延迟处理的问题。
在图6所示的实施例中，用户面网元或终端的动作可以分别由用户面网元或终端根据上述提及的存储器中的软件模块来执行。本申请实施例对此不作任何限制。
图7提供了一种可以在图1或图3所示的系统中执行速率控制的方法流程示意图。图7主要介绍的是Serving PLMN速率控制方法。
S701，UE经由接入节点发送附着请求到MME。MME接收该附着请求。
S703，MME发送连接建立请求到用户面网元。用户面网元接收该连接建立请求。
在MME希望控制下行NAS数据PDU的发送速率的情况下，该连接建立请求消息中包括Serving PLMN速率控制的时间管理信息。后续，待连接建立成功后，用户面网元根据Serving PLMN速率控制的时间管理信息对在该连接上发送的数据进行速率控制。
其中，Serving PLMN速率控制的时间管理信息在具体实现中可以通过特定的IE来传递。
在具体实现中，作为一种实现方式，该Serving PLMN速率控制时间管理信息包括Serving PLMN速率控制时间单元的起始时间指示信息，关于该起始时间指示信息的形式可以参考S503中的相关描述，这里不再赘述。
在具体实现中，作为一种实现方式，该Serving PLMN速率控制的时间管理信息还可以包括该Serving PLMN速率控制时间单元。关于该时间单元，可以参考S503中的相关描述，这里不再赘述。
在具体实现中，作为一种实现方式，Serving PLMN速率控制的时间管理信息还可以包括：Serving PLMN速率控制值。关于该速率控制值，可以参考S503中的相关描述，这里不再赘述。
S705，用户面网元发送连接建立响应消息给MME。该连接建立响应消息可以经由SGW发送给MME。
S707，MME发送附着接受消息给UE。UE接收该附着接受消息。
在具体实现中，作为一种实现方式，在MME希望控制上行NAS数据PDU的发送速率的情况下，该附着接受消息中还可以携带上述S703中的Serving PLMN速率控制的时间管理信息，关于Serving PLMN速率控制的时间管理信息本步骤不再详述。后续，待连接建立成功后，终端根据Serving PLMN速率控制的时间管理信息对该连接上待发送的数据进行速率控制。
其中，关于起始时间指示信息的选择：MME可以采用S513中AMF选择起始时间指示信息的方法来选择起始时间指示信息，这里不再赘述。
在具体实现中，作为一种实现方式，若数据发送设备为UE，则Serving PLMN速率控制的时间管理信息还可以包括计时指示，该计时指示具体为如下信息中的任意一个：a1)UE进入连接态时，在Serving PLMN速率控制时间单元的剩余值上继续计时；或者，b1)UE进入连接态时，对Serving PLMN速率控制时间单元重新开始计时；或者，c1)Serving PLMN速率控制的下一个时间单元，在Serving PLMN速率控制时间单元结束后传输第一个数据单元时开始计时。
其中，关于计时指示的选择，MME可以采用S513中AMF选择计时指示的方法来选择计时指示，这里不再赘述。
S709，MME发送初始上下文建立消息给UE，以请求接入层安全上下文等信息。UE接收该初始上下文建立消息。其中，该初始化上下文建立消息可能请求进行无线资源控制连接重配置。
S711，完成初始化上下文建立后，终端向MME发送附着完成消息。MME接收该附着完成消息。
可以理解的是，在本实施例中，图中示出的是MME对上行NAS数据PDU的发送速率 和下行NAS数据PDU的发送速率都进行了控制。但在具体实现中，MME对上行NAS数据PDU的速率控制和下行NAS数据PDU的速率控制是独立解耦的，MME也可以只对上行NAS数据PDU的发送速率进行控制，这种情况下，S703中就可以不携带Serving PLMN速率控制的时间管理信息；MME也可以只对下行NAS数据PDU的发送速率进行控制，这种情况下，S707中就可以不携带Serving PLMN速率控制的时间管理信息。MME在同时执行上行NAS数据PDU的速率控制和下行NAS数据PDU的速率控制时，二者的时间管理信息可以相同，也可以不同，本申请对此不做限定。
通过本实施例提供的方法，MME发送Serving PLMN速率时间单元的起始时间指示信息，用户面网元或UE收到该起始时间指示信息后，就可以和MME确定相同的开始速率控制计时的时间点，这样用户面网元或UE在使用速率控制信息发送合理数量的NAS数据PDU给MME时，MME就会将这些数据也作为合法数据，不会对这些数据进行丢包或延迟处理。从而解决了现有技术中，数据发送方在使用速率控制信息发送合理数量的NAS数据PDU时，被丢包或延迟处理的问题。
在实际实现中，作为一种实现方式，图7所示的实施例也可以应用于PDN连接建立的场景中，执行流程和图7的主要差别为：步骤S701中，终端发送的是PDN连接建立请求，而非附着请求，S709是承载建立，S711是连接完成。其他步骤和图7类似。这里不再赘述。
在图7所示的实施例中，MME、用户面网元或终端的动作可以分别由MME、用户面网元或终端根据上述提及的存储器中的软件模块来执行。本申请实施例对此不作任何限制。
图8提供了一种可以在图1或图2所示的系统中执行速率控制的方法流程示意图。图8主要介绍的是APN速率控制方法。
S801，同S701。
S803，和S703的主要不同是，连接建立请求消息中不携带速率控制的时间管理信息。
S805，用户面网元发送连接建立响应消息给MME。该连接建立响应消息可以经由SGW发送给MME。
在用户面网元希望控制上行NAS数据PDU的发送速率的情况下，该连接建立请求消息中包括APN速率控制时间管理信息。后续，待连接建立成功后，终端根据APN速率控制时间管理信息对该连接上待发送的数据进行速率控制。
其中，APN速率控制时间管理信息在具体实现中可以通过PCO/ePCO来传递。
在具体实现中，作为一种实现方式，该APN速率控制时间管理信息包括APN速率控制时间单元的起始时间指示信息，所述起始时间指示信息用于指示进行APN速率控制的APN速率控制时间单元的起始时间。
其中，该起始时间指示信息形式多样，具体实现中，也可以采用S703中的a)、b)或c)三种形式。本申请具体不做限定。
其中，关于起始时间指示信息的选择：用户面网元可以采用S513中AMF选择起始时间指示信息的方法来选择起始时间指示信息。比如：根据UE发送数据的频率来选择，或根据UE的状态来选择；或根据UE通信的持续时长来选择。这里不再赘述。
在具体实现中，作为一种实现方式，该APN速率控制的时间管理信息还可以包括该Serving APN速率控制时间单元。该时间单元的具体值本申请不做限定。在具体实现中，该 时间单元也可以是用户面网元和终端事先协商好了，在这种情况下，连接建立请求响应中就可以不携带时间单元。
在具体实现中，作为一种实现方式，APN速率控制的时间管理信息还可以包括：APN速率控制值，APN速率控制值用于指示终端在APN速率控制时间单元内发送的数据单元的最大值。
在具体实现中，作为一种实现方式，APN速率控制的时间管理信息还可以包括计时指示信息，该计时指示信息具体为如下信息中的任意一个：a1)UE进入连接态时，在APN速率控制时间单元的剩余值上继续计时；或者，b1)UE进入连接态时，对APN速率控制时间单元重新开始计时；或者，c1)APN速率控制的下一个时间单元，在APN速率控制时间单元结束后传输第一个携带数据的NAS数据分组数据单元时进行重新开始计时。
其中，关于计时指示信息的选择，用户面网元可以采用S513中AMF选择计时指示信息的方法来选择计时指示信息。比如：根据UE发送数据的频率来选择，或根据UE周期通信的间隔时间来选择，这里不再赘述。
S807，MME发送附着接受消息给UE。UE接收该附着接受消息。该附着接受消息中携带S805中所述的APN速率控制时间管理信息。
S809-S811，同S709-S711，这里不再赘述。
通过本实施例提供的方法，用户面网元发送APN速率时间单元的起始时间指示信息，UE收到该起始时间指示信息后，就可以和用户面网元确定相同的开始速率控制计时的时间点，这样UE在使用速率控制信息发送合理数量的NAS数据PDU给用户面网元时，用户面网元就会将这些数据也作为合法数据，不会对这些数据进行丢包或延迟处理。从而解决了现有技术中，数据发送方在使用速率控制信息发送合理数量的数据PDU时，被丢包或延迟处理的问题。
在实际实现中，作为一种实现方式，图8所示的实施例也可以应用于PDN连接建立的场景中，执行流程和图8的主要差别为：步骤S801中，终端发送的是PDN连接建立请求，而非附着请求，S809是承载建立，S811是连接完成。其他步骤和图8类似。这里不再赘述。
在图8所示的实施例中，用户面网元或终端的动作可以分别由用户面网元或终端根据上述提及的存储器中的软件模块来执行。本申请实施例对此不作任何限制。
图9提供了一种提供了一种可以在图2所示的系统中执行速率控制的方法流程示意图。图9主要介绍的是Serving PLMN速率控制方法。
在移动始发(Mobile Originated,MO)数据传输过程中，速率管理设备向数据发送设备发送Serving速率控制状态，数据发送设备收到Serving速率控制状态信息后会据此调节数据传输速率。图9中，以速率管理设备为移动管理网元(对应5G中的AMF)，数据发送设备为UE为例。
S900，发起MO数据前，UE处于空闲态。
S901，UE发送无线资源控制(Radio Resource Control，RRC)连接或发送RRC早期数据请求消息给接入节点。
可选的，在发送的NAS PDU中还包含了连接或会话的标识符以及加密的上行数据。
S903，对于IoT的场景，基于配置，如果之前没有查询用户设备上下文，则接入节点 可能从移动管理网元查询UE上下文。接入节点通过应用层消息将来自UE的NAS PDU转发到移动管理网元。
如果步骤901中发送了RRC早期数据请求消息，则接入节点在应用消息中包含“早期数据传输(Early Data Transmission，EDT)会话”标识。
可选的，移动管理网元在收到NAS PDU后，对其进行数据解密并进行完整性检查。
S905，该步骤是可选的。如果移动管理网元收到“EDT会话”标识，则移动管理网元向接入节点发送应用消息。
如果在之前的连接或会话建立流程中，已经启动了速率控制，则移动管理网元可以根据接收到的上行数据情况以及计时情况，在应用消息中添加Serving PLMN速率控制状态。UE在收到Serving PLMN速率控制状态后，据此调节上行数据的发送速率。
其中，Serving PLMN速率控制状态包括两部分信息。第一部分为：当前Serving PLMN速率控制状态周期有效期的剩余时间；第二部分为：当前速率控制周期依然允许发送的上行数据的数量。这里，上行数据的数量可以为上行数据的数据包的个数等。
可选的，S905之后，如果移动管理网元和会话管理网元(图中未示出)之间的用户面连接没有激活，则移动管理管理网元与会话管理及用户面网元执行连接或会话修改流程。
其中，S905中NAS消息都包含在应用消息中，Serving PLMN速率控制状态如果有，都可以放在NAS消息中，这里的NAS消息也可以说成是NAS负载。
S907，移动管理网元将上行数据转发到用户面网元。
其中，上行数据可能通过会话管理网元转发。
S909，如果有下行数据，则用户面网元将数据转发到移动管理网元。
下行数据有可能缓存在会话管理网元，则从会话管理网元将数据转发到移动管理网元。
可选的，移动管理网元收到下行数据后，进行完整性保护和数据加密。
S911，移动管理网元通过应用消息将下行数据转发到接入节点，移动管理网元可以在应用消息中发送连接建立指示消息。
如果在之前的连接或会话建立流程中，已经启动了速率控制，则移动管理网元可以根据接收到的上行数据情况以及计时情况，在应用消息中添加Serving PLMN速率控制状态。UE在收到Serving PLMN速率控制状态后，据此调节上行数据的发送速率。
其中，Serving PLMN速率控制状态包含两部分信息，具体可以参考S905。
如果之前收到释放辅助信息且移动管理网元不期望再发送更多的移动终接(Mobile Terminated，MT)数据，则移动管理网元向接入节点发送UE上下文释放命令。
S913，接入节点包含下行数据通过RRC下行消息转发给UE。
如果在S911中接收到UE上下文释放命令，则后面不再执行步骤S917。如果S901中使用了早期数据传输，接入节点向UE发送RRC早期数据完成消息，其中包含来自S905和S911的NAS负载。
S915，如果移动管理网元要求NAS送达的反馈，则接入节点向移动管理网元发送NAS送达通知。
S917，等待一段时间，检测是否有NAS PDU活动。该步骤是可选的。
S919，执行UE与移动管理网元之间的连接释放流程。在此之后UE再次进入休闲状 态。
S921，保存当前的Serving PLMN速率控制状态，即Serving PLMN速率控制有效期的剩余时间和周期内可以再发送的上行数据的数量等信息。
图9所示的方法也可以应用于4G系统中，如果应用于4G系统中，则移动管理网元为MME。
通过本实施例提供的方法，在MO数据传输过程中，速率控制设备将Serving PLMN速率控制状态信息发送给数据发送设备，数据发送设备收到Serving PLMN速率控制状态信息后，适当的调节数据的发送速率，从而使得数据发送设备能够及时的调整发送数据的速率，避免了速率超限被速率控制设备丢包的可能。
图10提供了一种提供了一种可以在图2所示的系统中执行速率控制的方法流程示意图。图10主要介绍的是Serving PLMN速率控制方法。
在移动终接(Mobile Terminated,MT)数据传输过程中，速率管理设备向数据发送设备发送Serving速率控制状态，数据发送设备收到Serving速率控制状态信息后会据此调节数据传输速率。图10中，以速率管理设备为移动管理网元，数据发送设备为用户面网元为例。
S1000，发起MO数据前，UE处于空闲态。
S1001，用户面网元收到下行数据后，将其发送到会话管理网元。
可选的，会话管理网元会缓存下行数据。
S1003，会话管理网元在收到下行数据后，向移动管理网元发送下行数据到达通知。
S1005，移动管理网元在收到下行数据到达通知后，可能根据UE的状态或者配置等向用户面网元发送下行数据到达通知确认消息。
其中，下行数据到达通知确认消息中可能包含会话管理网元需要缓存数据的时长等信息。并且，移动管理网元根据接收到的下行数据情况以及速率控制计时情况，在该确认消息中添加Serving PLMN速率控制状态。
其中，Serving PLMN速率控制状态包括两部分信息。第一部分为：当前Serving PLMN速率控制状态周期有效期的剩余时长；第二部分为：当前速率控制周期依然允许发送的下行数据的数量。这里，上行数据的数量可以为上行数据的数据包的个数等。用户面网元在收到Serving PLMN速率控制状态后，据此调节下行数据的发送速率。
S1007，移动管理网元判断UE可达的情况下，向接入节点发送寻呼信息，接入节点根据移动管理网元提供的信息进行寻呼，并建立RRC连接。
可选的，如果移动管理网元和会话管理网元之间的用户面连接没有激活，则移动管理管理网元与会话管理及用户面网元执行连接或会话修改流程。
S1009，会话管理网元将缓存的下行数据发送到移动管理网元。
可选的，移动管理网元收到下行数据后，进行完整性保护和数据加密。
S1010，移动管理网元通过应用消息将下行数据转发到接入节点。
S1011，接入节点将下行数据通过RRC下行消息转发给UE。
S1013，如果RRC连接依然存在，则UE可能通过NAS信令发送数据。可以将NAS数据PDU通过RRC上行消息发送给接入节点。
S1015，接入节点收到上行数据后，通过应用消息将上行数据转发到移动管理网元。
可选的，移动管理网元在收到NAS PDU后，对其进行数据解密并进行完整性检查。
S1017，移动管理网元将下行数据通过会话管理网元转发到用户面网元。
S1019，接入节点等待一段时间，检测是否有NAS PDU活动。
S1021，执行UE与移动管理网元之间的连接释放流程。在此之后UE再次进入休闲状态。
S1023，保存当前的Serving PLMN速率控制状态，即Serving PLMN速率控制周期的剩余时长和周期内可以再发送的上行数据的数量等信息。
图10所示的方法也可以应用于4G系统中，如果应用于4G系统中，则移动管理网元为MME。
通过本实施例提供的方法，在MT数据传输过程中，速率控制设备将Serving PLMN速率控制状态信息发送给数据发送设备，数据发送设备收到Serving PLMN速率控制状态信息后，适当的调节数据的发送速率，从而使得数据发送设备能够及时的调整发送数据的速率，避免了速率超限被速率控制设备丢包的可能。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，上述实现速率控制的控制设备(或：装置)或数据发送设备(或：装置)为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对控制设备或数据发送设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，以采用集成的方式划分各个功能模块的情况下，图11示出了一种速率控制装置110的结构示意图。该速率控制装置110可以是移动管理网元、会话管理网元、用户面网元或终端，也可以是这些网元或终端内的芯片，本申请实施例对此不作具体限定。其中，该速率控制装置110包括接收模块111和发送模块112。接收模块111，用于接收终端的连接建立请求，所述连接建立请求用于建立所述终端进行数据传输的连接；发送模块112，用于向数据发送设备发送速率控制的时间管理信息，所述时间管理信息用于所述数据发送设备对在所述连接上发送的数据进行速率控制，其中，所述时间管理信息包括用于进行速率控制的速率控制时间单元的起始时间指示信息，所述起始时间指示信息用于指示所述速率控制时间单元的起始时间。
可选的，所述起始时间指示信息具体为如下信息中的任意一个：所述连接建立成功的时间点；在所述连接上传输第一个数据单元的时间点；或，下一个计费周期的起始时间点。
可选的，若数据发送装置为所述终端或终端内的芯片，则时间管理信息还包括计时指 示信息，所述计时指示信息具体为如下信息中的任意一个：所述终端进入连接态时，在所述速率控制时间单元的剩余值上继续计时；所述终端进入连接态时，对所述速率控制时间单元重新开始计时；或，下一个速率控制时间单元在所述速率控制时间单元结束后传输第一个数据单元时开始计时。
可选的，若数据发送装置为会话管理网元或用户面网元，则时间管理信息还包括计时指示信息，所述计时指示信息具体为如下信息中的任意一个：速率控制时间单元在起始时间后连续计时；或者下一个速率控制时间单元在所述速率控制时间单元结束后传输第一个数据单元时开始计时。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该装置110以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
在一个简单的实施例中，本领域的技术人员可以想到装置110可以采用图4所示的形式。
比如，图4中的处理器41可以通过调用存储器43中存储的计算机执行指令，使得装置110执行上述方法实施例中的速率控制方法。
具体的，图11中的接收模块111和发送模块112的功能/实现过程可以通过图4中的处理器41调用存储器43中存储的计算机执行指令来实现。或者，图11中的接收模块111和发送模块112的功能/实现过程可以通过图4中的通信接口44来实现。
可选的，当该装置110是芯片时，那么接收模块111和发送模块112的功能/实现过程还可以通过管脚或电路等来实现。可选地，当该装置110是芯片时，所述存储器可以为所述芯片内的存储单元，如寄存器、缓存等。当然，当该装置110是芯片时，所述存储单元还可以是位于所述芯片外部的存储单元，如图4所示的存储器。
比如，以采用集成的方式划分各个功能模块的情况下，图12示出了一种数据发送装置的结构示意图。该数据发送装置可以是用户面网元、会话管理网元或终端，也可以是这些用户面网元、会话管理网元或终端内的芯片，本申请实施例对此不作具体限定。其中，该数据发送装置110包括接收模块121和处理模块122。接收模块121，用于接收速率控制的时间管理信息；其中，所述时间管理信息包括用于在终端进行数据传输的连接上进行速率控制的速率控制时间单元的起始时间指示信息，所述起始时间指示信息用于指示所述速率控制时间单元的起始时间；处理模块122，用于根据所述速率时间管理信息对在所述连接上发送的数据进行速率控制。
可选的，所述起始时间指示信息具体可以同图11的起始时间指示信息。这里不再赘述。
可选的，若数据发送装置为所述终端或终端内的芯片，则所述时间管理信息具体可以包括图11的计时指示信息。这里不再赘述。
可选的，若数据发送装置为会话管理网元或用户面网元，则所述时间管理信息具体可以包括图11的计时指示信息，这里不再赘述。
由于本申请实施例提供的装置可用于执行上述速率控制方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
可选的，本申请实施例还提供了一种装置(例如，该装置可以是芯片系统)，该装置包括处理器，用于支持控制装置或数据发送装置实现上述速率控制方法。在一种可能的设计中，该控制装置或数据发送装置还包括存储器。该存储器，用于保存控制装置或数据发送装置必要的程序指令和数据。当然，存储器也可以不在该装置中。该装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (30)

  1. 一种速率控制方法，其特征在于，包括：
    控制设备接收终端的连接建立请求，所述连接建立请求用于建立所述终端进行数据传输的连接；
    所述控制设备向数据发送设备发送速率控制的时间管理信息，所述时间管理信息用于所述数据发送设备对在所述连接上发送的数据进行速率控制，其中，所述时间管理信息包括用于进行速率控制的速率控制时间单元的起始时间指示信息，所述起始时间指示信息用于指示所述速率控制时间单元的起始时间。
  2. 如权利要求1所述的速率控制方法，其特征在于，所述起始时间指示信息具体为如下信息中的任意一个：
    所述连接建立成功的时间点；
    在所述连接上传输第一个数据单元的时间点；或，
    下一个计费周期的起始时间点。
  3. 如权利要求1或2所述的速率控制方法，其特征在于，所述速率控制为服务公共陆地移动网络速率控制，所述控制设备为移动管理网元、或会话管理网元；所述数据发送设备为所述终端。
  4. 如权利要求1或2所述的速率控制方法，其特征在于，所述速率控制为服务公共陆地移动网络速率控制，所述控制设备为移动管理网元、或会话管理网元，所述数据发送设备为用户面网元；或者，所述控制设备为移动管理网元，所述数据发送设备为会话管理网元。
  5. 如权利要求1或2所述的速率控制方法，其特征在于，所述速率控制为数据网络名速率控制，所述控制设备为用户面网元；所述数据发送设备为所述终端。
  6. 如权利要求1或2所述的速率控制方法，其特征在于，所述速率控制为接入点名称速率控制，所述控制设备为用户面网元；所述数据发送设备为所述终端。
  7. 如权利要求1-3，5或6中任一所述的速率控制方法，其特征在于，所述数据发送设备为所述终端，则所述时间管理信息还包括计时指示信息，所述计时指示信息具体为如下信息中的任意一个：
    所述终端进入连接态时，在所述速率控制时间单元的剩余值上继续计时；
    所述终端进入连接态时，对所述速率控制时间单元重新开始计时；或，
    下一个速率控制时间单元在所述速率控制时间单元结束后传输第一个数据单元时开始计时。
  8. 如权利要求1-2或4中任一所述的速率控制方法，其特征在于，所述数据发送设备为会话管理网元或用户面网元，则所述时间管理信息还包括计时指示信息，所述计时指示信息具体为如下信息中的任意一个：
    速率控制时间单元在起始时间后连续计时；或者
    下一个速率控制时间单元在所述速率控制时间单元结束后传输第一个数据单元时开始计时。
  9. 如权利要求1-8任一所述的速率控制方法，其特征在于，所述时间管理信息还包括：速率控制值，所述速率控制值用于指示所述数据发送设备在所述速率控制时间单元内发送的数据单元的最大值。
  10. 如权利要求1-9任一所述的速率控制方法，其特征在于，所述时间管理信息还包括：所述速率控制时间单元信息。
  11. 一种速率控制方法，其特征在于，包括：
    数据发送设备接收速率控制的时间管理信息；其中，所述时间管理信息包括用于在终端进行数据传输的连接上进行速率控制的速率控制时间单元的起始时间指示信息，所述起始时间指示信息用于指示所述速率控制时间单元的起始时间；
    所述数据发送设备根据所述速率时间管理信息对在所述连接上发送的数据进行速率控制。
  12. 如权利要求11所述的速率控制方法，其特征在于，包括：所述起始时间指示信息具体为如下信息中的任意一个：
    所述连接建立成功的时间点；
    在所述连接上传输第一个数据单元的时间点；或，
    下一个计费周期的起始时间点。
  13. 如权利要求11或12所述的速率控制方法，其特征在于，所述数据发送设备为所述终端，则所述时间管理信息还包括计时指示信息，所述计时指示信息具体为如下信息中的任意一个：
    所述终端进入连接态时，在所述速率控制时间单元的剩余值上继续计时；
    所述终端进入连接态时，对所述速率控制时间单元重新开始计时；或，
    下一个速率控制时间单元在所述速率控制时间单元结束后传输第一个数据单元时开始计时。
  14. 如权利要求11或12所述的速率控制方法，其特征在于，所述数据发送设备为会话管理网元或用户面网元，则所述时间管理信息还包括计时指示信息，所述计时指示信息具体为如下信息中的任意一个：
    速率控制的时间单元在起始时间后连续计时；或者
    下一个速率控制时间单元在所述速率控制时间单元结束后传输第一个数据单元时开始计时。
  15. 一种速率控制装置，其特征在于，包括：
    接收模块，用于接收终端的连接建立请求，所述连接建立请求用于建立所述终端进行数据传输的连接；
    发送模块，用于向数据发送设备发送速率控制的时间管理信息，所述时间管理信息用于所述数据发送设备对在所述连接上发送的数据进行速率控制，其中，所述时间管理信息包括用于进行速率控制的速率控制时间单元的起始时间指示信息，所述起始时间指示信息用于指示所述速率控制时间单元的起始时间。
  16. 如权利要求15所述的速率控制装置，其特征在于，所述起始时间指示信息具体为如下信息中的任意一个：
    所述连接建立成功的时间点；
    在所述连接上传输第一个数据单元的时间点；或，
    下一个计费周期的起始时间点。
  17. 如权利要求15或16所述的速率控制装置，其特征在于，所述时间管理信息还包括计时指示信息，所述计时指示信息具体为如下信息中的任意一个：
    所述终端进入连接态时，在所述速率控制时间单元的剩余值上继续计时；
    所述终端进入连接态时，对所述速率控制时间单元重新开始计时；或，
    下一个速率控制时间单元在所述速率控制时间单元结束后传输第一个数据单元时开始计时。
  18. 如权利要求15或16所述的速率控制装置，其特征在于，所述时间管理信息还包括计时指示信息，所述计时指示信息具体为如下信息中的任意一个：
    速率控制时间单元在起始时间后连续计时；或者
    下一个速率控制时间单元在所述速率控制时间单元结束后传输第一个数据单元时开始计时。
  19. 一种数据发送装置，其特征在于，包括：
    接收模块，用于接收速率控制的时间管理信息；其中，所述时间管理信息包括用于在终端进行数据传输的连接上进行速率控制的速率控制时间单元的起始时间指示信息，所述起始时间指示信息用于指示所述速率控制时间单元的起始时间；
    处理模块，用于根据所述速率时间管理信息对在所述连接上发送的数据进行速率控制。
  20. 如权利要求19所述的数据发送装置，其特征在于，所述起始时间指示信息具体为如下信息中的任意一个：
    所述连接建立成功的时间点；
    在所述连接上传输第一个数据单元的时间点；或，
    下一个计费周期的起始时间点。
  21. 如权利要求19或20所述的数据发送装置，其特征在于，所述时间管理信息还包括计时指示信息，所述计时指示信息具体为如下信息中的任意一个：
    所述终端进入连接态时，在所述速率控制时间单元的剩余值上继续计时；
    所述终端进入连接态时，对所述速率控制时间单元重新开始计时；或，
    下一个速率控制时间单元在所述速率控制时间单元结束后传输第一个数据单元时开始计时。
  22. 如权利要求19或20所述的数据发送装置，其特征在于，所述时间管理信息还包括计时指示信息，所述计时指示信息具体为如下信息中的任意一个：
    速率控制时间单元在起始时间后连续计时；或者
    下一个速率控制时间单元在所述速率控制时间单元结束后传输第一个数据单元时开始计时。
  23. 一种速率控制系统，其特征在于，包括控制设备和数据发送设备，
    所述控制设备，用于接收终端的连接建立请求，所述连接建立请求用于建立所述终端进行数据传输的连接；所述控制设备向数据发送设备发送速率控制的时间管理信息，其中， 所述时间管理信息包括用于进行速率控制的速率控制时间单元的起始时间指示信息，所述起始时间指示信息用于指示所述速率控制时间单元的起始时间；
    所述数据发送设备，用于接收所述时间管理信息，所述时间管理信息用于所述数据发送设备对在所述连接上发送的数据进行速率控制。
  24. 一种速率控制装置，其特征在于，包括：处理器和通信接口，所述通信接口，用于接收代码指令并传输至所述处理器，所述处理器用于运行所述代码指令以执行如权利要求1-10任一项所述的速率控制方法。
  25. 一种数据发送装置，其特征在于，包括：处理器和通信接口，所述通信接口，用于接收代码指令并传输至所述处理器，所述处理器用于运行所述代码指令以执行如权利要求11-14任一项所述的速率控制方法。
  26. 一种处理器，其特征在于，用于执行如权利要求1-10任一项，或权利要求11-14任一项所述的速率控制方法。
  27. 一种计算机可读存储介质，包括计算机程序，当其在计算机上运行时，使得所述计算机执行如权利要求1-10任一项，或权利要求11-14任一项所述的速率控制方法。
  28. 一种计算机程序产品，所述计算机程序产品包括计算机程序，当所述计算机程序在计算机上运行时，使得计算机执行如权利要求1-10任一项，或权利要求11-14任一项所述的速率控制方法。
  29. 一种用来执行权利要求1-10任一项所述的速率控制方法的装置。
  30. 一种用来执行权利要求11-14任一项所述的速率控制方法的装置。
PCT/CN2019/098644 2018-08-25 2019-07-31 一种速率控制的方法、装置和系统 Ceased WO2020042860A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2020572781A JP7083925B2 (ja) 2018-08-25 2019-07-31 レート制御方法、装置、およびシステム
EP19854148.4A EP3799514B1 (en) 2018-08-25 2019-07-31 Rate control methods, devices, computer program and system
KR1020207036303A KR102476193B1 (ko) 2018-08-25 2019-07-31 레이트 제어 방법, 장치, 및 시스템
US17/117,828 US12035174B2 (en) 2018-08-25 2020-12-10 Rate control method, apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810976506.4 2018-08-25
CN201810976506.4A CN110859012B (zh) 2018-08-25 2018-08-25 一种速率控制的方法、装置和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/117,828 Continuation US12035174B2 (en) 2018-08-25 2020-12-10 Rate control method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2020042860A1 true WO2020042860A1 (zh) 2020-03-05

Family

ID=69635638

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/098644 Ceased WO2020042860A1 (zh) 2018-08-25 2019-07-31 一种速率控制的方法、装置和系统

Country Status (6)

Country Link
US (1) US12035174B2 (zh)
EP (1) EP3799514B1 (zh)
JP (1) JP7083925B2 (zh)
KR (1) KR102476193B1 (zh)
CN (1) CN110859012B (zh)
WO (1) WO2020042860A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7240503B2 (ja) * 2019-03-11 2023-03-15 テレフオンアクチーボラゲット エルエム エリクソン（パブル） Ｐｌｍｎレート制御のための方法及び装置
KR102238699B1 (ko) * 2019-10-14 2021-04-09 에스케이텔레콤 주식회사 단말의 연결 시간을 제어하는 방법 및 그 방법을 수행하는 amf 노드
WO2021074859A1 (en) * 2019-10-16 2021-04-22 Telefonaktiebolaget Lm Ericsson (Publ) Configuration of downlink data measurement at mobile terminating early data transmission (mt-edt)
CN112740583B (zh) * 2020-12-25 2022-03-04 华为技术有限公司 数据处理方法、装置和系统
KR20230004006A (ko) * 2021-06-30 2023-01-06 삼성전자주식회사 서비스 파라미터를 전송하기 위한 장치 및 방법
CN113766570B (zh) * 2021-09-27 2025-03-18 展讯通信（上海）有限公司 基于速率控制的数据发送方法及装置、通信装置
CN116056153A (zh) * 2021-10-28 2023-05-02 华为技术有限公司 一种通信方法及装置
CN115022931B (zh) * 2022-05-27 2024-02-06 中国电信股份有限公司 速率控制方法及装置、计算机可读存储介质及电子设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106648904A (zh) * 2017-01-09 2017-05-10 大连理工大学 一种流式数据处理自适应速率控制方法
WO2018008977A1 (en) * 2016-07-05 2018-01-11 Samsung Electronics Co., Ltd. A method of handling control plane data in a wireless network
WO2018063462A1 (en) * 2016-09-29 2018-04-05 Intel IP Corporation At commands for cellular internet of things rate control

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7706403B2 (en) * 2003-11-25 2010-04-27 Telefonaktiebolaget Lm Ericsson (Publ) Queuing delay based rate control
KR20160131413A (ko) 2015-05-07 2016-11-16 삼성전자주식회사 무선 통신 시스템에서 데이터 레이트 제어 장치 및 방법
CN107925631A (zh) * 2016-02-17 2018-04-17 日本电气株式会社 基于服务开放功能实施非ip数据监管的方法
US10805036B2 (en) * 2016-02-18 2020-10-13 Telefonaktiebolaget Lm Ericsson (Publ) System, methods, and apparatuses for managing data rate for control plane optimization
JPWO2018084115A1 (ja) * 2016-11-01 2019-09-19 株式会社Ｎｔｔドコモ 無線端末装置及び通信方法
US10805983B2 (en) * 2017-10-17 2020-10-13 Ofinno, Llc Control plane data transmission
US10834266B2 (en) * 2018-07-23 2020-11-10 Cisco Technology, Inc. Process-efficient generation of data records for data communications involving groups or aggregates of IoT devices

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018008977A1 (en) * 2016-07-05 2018-01-11 Samsung Electronics Co., Ltd. A method of handling control plane data in a wireless network
WO2018063462A1 (en) * 2016-09-29 2018-04-05 Intel IP Corporation At commands for cellular internet of things rate control
CN106648904A (zh) * 2017-01-09 2017-05-10 大连理工大学 一种流式数据处理自适应速率控制方法

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
KR102476193B1 (ko) 2022-12-08
JP7083925B2 (ja) 2022-06-13
US20210099912A1 (en) 2021-04-01
EP3799514A4 (en) 2021-09-29
EP3799514A1 (en) 2021-03-31
EP3799514B1 (en) 2024-09-11
CN110859012B (zh) 2023-07-18
US12035174B2 (en) 2024-07-09
CN110859012A (zh) 2020-03-03
JP2021528918A (ja) 2021-10-21
KR20210010562A (ko) 2021-01-27

Similar Documents

Publication Publication Date Title
WO2020042860A1 (zh) 一种速率控制的方法、装置和系统
US12231946B2 (en) Communications method and apparatus
CN110049070B (zh) 事件通知方法及相关设备
CN110166407B (zh) QoS流处理方法、设备及系统
CN113473391B (zh) 会话建立方法、设备及系统
CN109673060B (zh) 一种通信方法及装置
WO2019062754A1 (zh) 一种通信方法、装置及系统
CN110519809B (zh) 管理pdu会话的方法、网元、设备、装置、系统和存储介质
WO2019129115A1 (zh) 一种系统切换的方法及通信实体
CN110324867A (zh) 一种通信方法及装置
JP7785853B2 (ja) インジケーション情報送信方法、装置およびシステム、および記憶媒体
WO2019157963A1 (zh) 用于数据传输的方法、移动管理设备、数据业务处理设备和终端
WO2022237505A1 (zh) 一种通信方法、设备及系统
WO2019096306A1 (zh) 一种处理请求的方法以及相应实体
CN111491370A (zh) 一种通信方法、网元、系统及存储介质
WO2020135536A1 (zh) 一种通信方法及装置
WO2022160861A1 (zh) 通信方法及装置
CN110830928A (zh) 通信方法和装置
CN110933709B (zh) 协议数据单元会话管理方法及通信装置
WO2021160096A1 (zh) 一种私网签约信息更新方法及装置
CN109863784B (zh) 控制网络拥塞的方法、终端设备和网络设备
WO2018191867A1 (zh) 终端监控信息的同步方法、设备及系统
WO2020011173A1 (zh) 搬迁管理方法及装置
CN112104464A (zh) 一种传输背景流量传输信息的方法、装置及系统
US20240163735A1 (en) Cellular communication session management for user equipment (ues) in idle mode

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20207036303

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019854148

Country of ref document: EP

Effective date: 20201202

ENP Entry into the national phase

Ref document number: 2020572781

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE