WO2017054183A1 - 业务承载拥塞控制的方法及设备 - Google Patents

业务承载拥塞控制的方法及设备 Download PDF

Info

Publication number
WO2017054183A1
WO2017054183A1 PCT/CN2015/091256 CN2015091256W WO2017054183A1 WO 2017054183 A1 WO2017054183 A1 WO 2017054183A1 CN 2015091256 W CN2015091256 W CN 2015091256W WO 2017054183 A1 WO2017054183 A1 WO 2017054183A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
terminal
bearer
network device
target service
Prior art date
Application number
PCT/CN2015/091256
Other languages
English (en)
French (fr)
Inventor
曾元清
Original Assignee
广东欧珀移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to RU2018113474A priority Critical patent/RU2702267C1/ru
Priority to MX2018003712A priority patent/MX2018003712A/es
Priority to CA2996178A priority patent/CA2996178C/en
Priority to KR1020187004246A priority patent/KR102338670B1/ko
Priority to PCT/CN2015/091256 priority patent/WO2017054183A1/zh
Priority to CN201580081247.3A priority patent/CN107736055B/zh
Priority to BR112018005512-3A priority patent/BR112018005512A2/zh
Priority to EP15905095.4A priority patent/EP3319371B1/en
Priority to CN202011454615.3A priority patent/CN112601253A/zh
Priority to US15/745,936 priority patent/US11166187B2/en
Application filed by 广东欧珀移动通信有限公司 filed Critical 广东欧珀移动通信有限公司
Priority to SG11201801165UA priority patent/SG11201801165UA/en
Priority to EP21155285.6A priority patent/EP3836629A1/en
Priority to CN202011455059.1A priority patent/CN112566215A/zh
Priority to AU2015411026A priority patent/AU2015411026B2/en
Priority to JP2018507583A priority patent/JP2018537874A/ja
Publication of WO2017054183A1 publication Critical patent/WO2017054183A1/zh
Priority to IL257427A priority patent/IL257427B/en
Priority to ZA2018/00911A priority patent/ZA201800911B/en
Priority to PH12018500307A priority patent/PH12018500307A1/en
Priority to HK18104611.1A priority patent/HK1245559A1/zh
Priority to US17/501,762 priority patent/US20220038939A1/en

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/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • 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/0289—Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions

Definitions

  • Embodiments of the present invention relate to the field of communications, and, more particularly, to a method and an apparatus for traffic bearer congestion control.
  • the service class may include a mobile terminal originating data (MO-data) service, a mobile terminal originating signaling (MO-signaling) service, a mobile terminal called data (MT-data) service, and a high priority (High Priority).
  • MO-data mobile terminal originating data
  • MT-data mobile terminal originating signaling
  • High Priority high priority
  • An access network device (for example, a base station, etc.), in the system message of the broadcast, notifies the terminal of the service type of the access control and the corresponding access control parameter when initiating the random access from the idle state.
  • different types of services may be set according to different priorities, and different access control parameters may be set.
  • the terminal in the idle state needs to initiate a service request, it is determined whether the service request is prohibited according to the service category and the corresponding access control parameter.
  • the service request is forbidden, the random access and the subsequent service establishment process are not performed, so that the congestion of the access network or the core network can be alleviated.
  • the foregoing access control mechanism is for a terminal that is in an idle state, that is, when the terminal first initiates a service request.
  • the terminal may access the network through a high priority service request and subsequently initiate a low priority service request. Because the terminal is already in the connected state in the network at this time, it is not necessary to initiate a random access, service establishment request, and the like, and directly apply for adding a new bearer. This may result in a low priority service request initiated by the terminal in the connected state. Unfairness of low priority service requests is initiated directly with other terminals in idle state.
  • the embodiments of the present invention provide a method and a device for congestion control of a service category, which can perform bearer establishment control on a terminal in a connected state, thereby implementing a fair congestion control mechanism for each terminal.
  • a method for traffic category congestion control including:
  • the service bearer request information includes information corresponding to the request that the terminal in the connected state requests to establish the bearer initiated by the target service, where the service bearer request information includes the service category to which the target service belongs.
  • the service category prohibition information includes a prohibition parameter corresponding to the service category to which the target service belongs in the connected state;
  • a method for traffic category congestion control including:
  • the service bearer request information includes information corresponding to a request initiated by a terminal in a connected state for requesting to establish a target service, where the service bearer request information includes a service category to which the target service belongs ;
  • a method for traffic category congestion control including:
  • the request information includes a service category to which the target service belongs.
  • a method for traffic category congestion control including:
  • the core network device receives the indication information that is sent by the access network device to indicate that the bearer of the target service is allowed to be established.
  • a method for traffic category congestion control including:
  • the access network device sends the service category prohibition information to the core network device, where the service category prohibition information includes a prohibition parameter corresponding to the service category to which the target service belongs in the connected state;
  • the access network device receives the indication information that is sent by the core network device to indicate that the bearer of the target service is allowed to be established.
  • a device for congestion control of a service category including:
  • An obtaining module configured to obtain service bearer request information, where the service bearer request information includes information corresponding to a request initiated by a terminal in a connected state to request to establish a target service, where the service bearer request information includes the target The business category to which the business belongs;
  • the obtaining module is further configured to obtain the service category prohibition information, where the service category prohibition information includes a prohibition parameter corresponding to the service category to which the target service belongs in the connected state;
  • the determining module is configured to determine, according to the forbidden parameter, whether the terminal is prohibited from establishing a bearer belonging to the target service of the service category.
  • a terminal for congestion control of a service category including:
  • a sending module configured to send a service bearer request information, where the service bearer request information includes information corresponding to a request initiated by a terminal in a connected state to request to establish a target service, where the service bearer request information includes the target The business category to which the business belongs;
  • a receiving module configured to receive indication information that prohibits or allows the terminal to establish a bearer of a target service that belongs to the service category.
  • a core network device for traffic category congestion control including:
  • the receiving module is configured to receive a service bearer request sent by the non-access stratum sent by the terminal, where the service bearer request is used by the terminal in the connected state to request to establish a bearer initiated by the target service, where the service bearer request includes The business category to which the target business belongs;
  • a sending module configured to send a service bearer request information to the access network device, where the service bearer request information is used to notify the access network device that the non-access stratum of the terminal sends a service bearer request to the core network device
  • the service bearer request information includes a service category to which the target service belongs.
  • a core network device for traffic category congestion control including:
  • the receiving module is configured to: when the access network device determines that the terminal is allowed to establish a bearer of the target service, receive the indication information that is sent by the access network device to indicate that the bearer of the target service is allowed to be established.
  • the tenth aspect provides an access network device for traffic category congestion control, including:
  • a sending module configured to send the service category prohibition information to the core network device, where the service category prohibition information includes a prohibition parameter corresponding to the service category to which the target service belongs in the connected state;
  • a receiving module configured to: when the core network device determines that the terminal is allowed to establish the bearer of the target service, receive the indication information that is sent by the core network device to indicate that the bearer of the target service is allowed to be established.
  • the method and the device for the service category congestion control in the embodiment of the present invention can effectively prevent the terminal from accessing the network through the high priority service request by controlling the bearer establishment of the terminal in the connected state according to the forbidden parameter.
  • a low-priority service request is initiated to initiate a low-priority service request directly with other idle terminals, thereby achieving a fair congestion control mechanism for each terminal.
  • FIG. 1 is a schematic flowchart of a method for congestion control of a service class according to an embodiment of the present invention.
  • FIG. 2 is a schematic flowchart of a method for congestion control of a service class according to another embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a method for traffic category congestion control according to another embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a method for congestion control of a service class according to another embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a method for traffic category congestion control according to another embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of a method for traffic category congestion control according to another embodiment of the present invention.
  • FIG. 7 is a schematic flowchart of a method for traffic category congestion control according to another embodiment of the present invention.
  • FIG. 8 is a schematic flowchart of a method for traffic category congestion control according to another embodiment of the present invention.
  • FIG. 9 is a schematic flowchart of a method for traffic category congestion control according to another embodiment of the present invention.
  • FIG. 10 is a schematic block diagram of an apparatus for traffic class congestion control according to an embodiment of the present invention.
  • FIG. 11 is a schematic block diagram of an apparatus for traffic class congestion control according to another embodiment of the present invention.
  • Figure 12 is a schematic block diagram of a terminal in accordance with one embodiment of the present invention.
  • Figure 13 is a schematic block diagram of a terminal in accordance with another embodiment of the present invention.
  • Figure 14 is a schematic block diagram of a core network device in accordance with one embodiment of the present invention.
  • Figure 15 is a schematic block diagram of a core network device in accordance with another embodiment of the present invention.
  • Figure 16 is a schematic block diagram of a core network device in accordance with one embodiment of the present invention.
  • Figure 17 is a schematic block diagram of a core network device in accordance with another embodiment of the present invention.
  • FIG. 18 is a schematic block diagram of an access network device according to an embodiment of the present invention.
  • FIG. 19 is a schematic block diagram of an access network device according to another embodiment of the present invention.
  • a component can be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer.
  • an application running on a computing device and a computing device can be a component.
  • One or more components can reside within a process and/or execution thread, and the components can be located on one computer and/or distributed between two or more computers.
  • these components can execute from various computer readable media having various data structures stored thereon.
  • a component may, for example, be based on signals having one or more data packets (eg, data from two components interacting with another component between the local system, the distributed system, and/or the network, such as the Internet interacting with other systems) Communicate through local and/or remote processes.
  • data packets eg, data from two components interacting with another component between the local system, the distributed system, and/or the network, such as the Internet interacting with other systems
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD frequency division duplex
  • TDD LTE time division duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the present invention describes various embodiments in connection with a terminal.
  • the terminal can communicate with one or more core networks via a radio access network (RAN), and the terminal can refer to a user equipment (User Equipment, referred to as "UE"), an access terminal, a subscriber unit, a subscriber station, Mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.
  • RAN radio access network
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol ("SSIP") phone, a Wireless Local Loop (WLL) station, and a personal digital processing (Personal Digital) Assistant, referred to as "PDA” for short, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in future 5G networks, and the like.
  • SSIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Processing
  • the access network device may be a device in the access network for communicating with the terminal, for example, may be a base station (Base Transceiver Station, abbreviated as "BTS”) in the GSM system or CDMA, or may be a base station in the WCDMA system.
  • BTS Base Transceiver Station
  • NodeB referred to as "NB”
  • eNB evolved base station
  • the network device may be a relay station, an access point, or an in-vehicle device. , wearable devices, and access network devices in future 5G networks.
  • the present invention describes various embodiments in connection with a core network device.
  • the core network device is mainly used to provide user connection, management of the user, and completion of the service, as an interface provided by the bearer network to the external network, and the like.
  • it may be a Mobility Management Entity (MME) or other network element in the core network.
  • MME Mobility Management Entity
  • FIG. 1 is a schematic flowchart of a method 100 for service class congestion control according to an embodiment of the present invention. It should be understood that the method 100 may be performed by a terminal, by an access network device, such as a base station, or by a core network device, such as an MME. Method 100 includes:
  • the service bearer request information is obtained, where the service bearer request information includes information corresponding to the request that the terminal in the connected state requests to establish a bearer initiated by the target service, where the service bearer request information includes a service category to which the target service belongs.
  • S120 Obtain a service category prohibition information, where the service category prohibition information includes a prohibition parameter corresponding to a service category to which the target service belongs in a connected state;
  • the method for controlling the congestion of the traffic class in the embodiment of the present invention can effectively prevent the terminal from accessing the network through the high-priority service request and then initiate the low-priority service request by controlling the bearer establishment of the terminal in the connected state according to the forbidden parameter.
  • the service bearer request information in the S110 may be sent by the non-access stratum (NAS) of the terminal to the Access Stratum (AS) of the terminal, according to the executor of the method 100.
  • the core network device may notify the access network device after the NAS of the terminal sends the service bearer request to the core network device; or may be sent by the AS of the terminal to the access network device; or may be the NAS direction of the terminal. Sent by the core network device.
  • the service bearer request is a request for the bearer initiated by the terminal in the connected state to request the establishment of the target service, where the service bearer request includes the service category of the target service. It should be understood that multiple services may belong to the same service category.
  • the terminal When the terminal is in the idle state, the terminal does not establish a connection with the network side (including the access network and the core network), and the terminal does not carry any service.
  • the terminal When the terminal is in the connected state, the terminal establishes a connection with the network side (including the access network and the core network) through the signaling process.
  • the service category prohibition information in S120 is generally determined and generated by the access network device according to the data service carried by the current network, and generally includes multiple service categories in the connected state and prohibition parameters corresponding to each service category. And sent by the access network device to the terminal and/or the core network device in the form of broadcast or unicast.
  • S130 it is determined whether the terminal is prohibited from establishing a bearer of the target service according to the forbidden parameter corresponding to the service type of the target service.
  • the method for determining whether to prohibit the establishment of the bearer of the target service may be various.
  • the forbidden parameter is a forbidden probability
  • the method 100 may further include:
  • the S130 determines, according to the forbidden parameter, whether the terminal is prohibited from establishing a bearer that belongs to the target service of the service category, and may include:
  • the terminal When the random number is less than the forbidden probability, the terminal is prohibited from establishing a bearer of the target service; when the random number is greater than the forbidden probability, the terminal is allowed to establish a bearer of the target service.
  • the access network device may set different prohibition probabilities for different service categories (for example, S 1 , S 2 , . . . , S n ) according to the data service carried by the current network (for example, P 1 , P). 2 ,...,P n ).
  • the prohibition probability (P 1 , P 2 , . . . , P n ) is used to determine whether to prohibit the terminal in the connected state from establishing a service bearer.
  • a random number between 0 and 1 is generated for the target service.
  • the random number is sent to the executive body of method 100.
  • the random number may be sent in the service bearer request information, or may be sent separately, which is not limited in this embodiment of the present invention.
  • the executor of the method 100 finds the prohibition probability P i corresponding thereto according to the service class (for example, S i ) of the target service requested by the terminal in the connected state.
  • the random number is compared with the forbidden probability P i , and when the random number is less than the forbidden probability P i , the terminal is prohibited from establishing the bearer of the target service; when the random number is greater than the forbidden probability P i , the terminal is allowed to establish the bearer of the target service. .
  • the case where the random number is equal to the prohibition probability P i may be consistent with the processing when the random number is smaller than the prohibition probability P i , or may be consistent with the processing when the random number is greater than the prohibition probability P i .
  • the terminal when the random number is less than or equal to the prohibition probability P i (random number ⁇ P i ), the terminal is prohibited from establishing the bearer of the target service; when the random number is greater than the prohibition probability P i (random number > P i ), the The terminal establishes a bearer of the target service.
  • the terminal when the random number is less than the prohibition probability P i (random number ⁇ P i ), the terminal is prohibited from establishing a bearer of the target service; when the random number is greater than or equal to the prohibition probability P i (random number ⁇ P i ), the The terminal establishes a bearer of the target service.
  • This embodiment of the present invention does not limit this.
  • the terminal may select a random number between 0 and 1 again after a period of time to perform a service bearer request.
  • the time can be referred to as a service category prohibition time.
  • the calculation method of the business category prohibition time can be calculated according to the following formula (1).
  • the ac-BarringTime is an access prohibition time configured by the access network device.
  • the prohibition probability may be smaller than the access prohibition probability corresponding to the service category to which the target service belongs in the idle state.
  • the idle state terminal initiates the service category requested bearer service S j and S j under the business category corresponding to the idle state for the access barring probability p j. Then the terminal in a connected state, the terminal initiates the service type is connected state S i bearer service request, the service class S i corresponding to the idle state for the access barring probability p i. Since the terminal before initiating service class is requested bearer service S j has been established through multiple interactions with the access network device is connected, a terminal in a connected state at this time, when establishment of the signaling bearer service consumption much less than in the idle state, Therefore, the access network device can set the prohibition probability P i in the connected state, and P i is less than p i .
  • the P i is equal to the p i , and the specific parameters may be configured by the operator, which is not limited by the embodiment of the present invention.
  • the access network device may use the access service class probability used by the terminal when the idle state is multiplied by the access prohibition probability of the service class in the idle state to generate the prohibition probability of the service class in the connected state; or may be greater than 0.
  • the access prohibition probability of the service class When the coefficient of 1 is multiplied by the idle state, the access prohibition probability of the service class generates the prohibition probability of the service class in the connected state; or the access prohibition probability of the service class when the idle state is directly reused is used as the prohibition of the service class in the connected state.
  • Probability; or the prohibition probability of the service class in the connected state is separately defined by the access network device, which is not limited in this embodiment of the present invention.
  • the forbidden parameter is a forbidden bit mapping
  • the method 100 may further include:
  • the S130 determines, according to the forbidden parameter, whether the terminal is prohibited from establishing a bearer that belongs to the target service of the service category, and may include:
  • the terminal When the access level of the terminal is set to 1 in the forbidden bit mapping, the terminal is prohibited from establishing the bearer of the target service; when the access level of the terminal is not set to 1 in the forbidden bit mapping The terminal is allowed to establish a bearer of the target service.
  • each terminal is randomly assigned an access level when accessing the access network.
  • the access level can be set to a total of 10 levels, respectively 0-9, and the access level of a certain terminal is randomly assigned to 5.
  • the access network device can set different barbit maps (Bitmaps) for different service classes according to the data service carried by the current network.
  • the prohibition bit map includes 10 levels, and the bit indication is used to indicate which of each level needs to be prohibited and which is not. Since the access level of the terminal is randomly assigned to the access network device, a certain probability of prohibition can also be achieved. For example, when the network needs to prohibit 20% of the terminals from establishing service bearers, then two levels are randomly selected to be set to 1, and in a specific example, levels 3 and 5 are set to 1. The terminal corresponding to the access levels 3 and 5 is forbidden to establish a service bearer even if there is a service bearer request.
  • the number of bits set in the prohibited bit map may be less than the bit corresponding to the service class to which the target service belongs in the idle state. The number of bits set in the bit map.
  • the access network device can set more according to the bit bitmap used by the terminal in the idle state. Set a bit of 1 to generate a forbidden bit map of the service class in the connected state; or directly reuse the bit map of the service class as a forbidden bit map of the service class in the connected state; or The network access device separately defines the forbidden bit mapping of the service class in the connected state, which is not limited in this embodiment of the present invention.
  • the mechanism of traffic class congestion control of the embodiment of the present invention is described in detail above.
  • the signaling flow of the traffic class congestion control in the embodiment of the present invention is described in detail below with reference to four specific examples.
  • the method 100 is performed by an access layer (AS) of the terminal, that is, the executive body of the method 100 is an AS of the terminal,
  • S110 obtains service bearer request information, including:
  • NAS non-access stratum
  • S120 obtains service category prohibition information, including:
  • the access network device And receiving, by the access network device, the service category prohibition information, where the service category prohibition information includes multiple service categories and prohibition parameters corresponding to the multiple service categories respectively.
  • the method 100 may further include:
  • the AS When it is determined that the terminal is prohibited from establishing the bearer of the target service according to the forbidden parameter, the AS sends the first indication information for indicating that the bearer of the target service is prohibited from being established.
  • the method 100 may further include:
  • the AS When determining, according to the forbidden parameter, the bearer that allows the terminal to establish the target service, the AS sends, to the NAS, second indication information for indicating a bearer that is allowed to establish the target service, and the AS initiates the access network device. Establish the process of hosting the target business.
  • FIG. 2 shows a schematic flow chart of a method 200 of traffic class congestion control in accordance with an embodiment of the present invention.
  • Method 200 includes:
  • the AS of the terminal receives the service category prohibition information broadcasted by the access network device, where the service category prohibition information includes a plurality of service categories and a prohibition parameter corresponding to each service category in the connected state, for example, a prohibition probability or a prohibition bit mapping.
  • the access network device can also broadcast the access prohibition information (such as the access prohibition probability or the access level bit mapping) in the idle state to the terminal, and perform congestion control on the terminal in the idle state.
  • the embodiment of the invention is not limited.
  • the NAS of the terminal in the connected state sends the service bearer request information to the AS of the terminal, where the service bearer request information includes the service type of the service bearer that the terminal requests to establish.
  • the AS of the terminal acquires a random number generated by the terminal for the target service, or acquires the terminal. Access level.
  • S240 The AS of the terminal finds the prohibition probability or the forbidden bit mapping corresponding to the service category in the forbidden parameter according to the service type of the target service in the service bearer request information, and determines whether the random number or the access level obtained in S230 is determined according to the random number or the access level acquired in S230.
  • the terminal is forbidden to establish the bearer of the target service.
  • the AS of the terminal sends the first indication information of the bearer for indicating that the target service is prohibited from being established.
  • the AS performing the S261 terminal sends the second indication information indicating the bearer that is allowed to establish the target service to the NAS of the terminal, and the AS performing the S262 terminal initiates the establishment of the target to the access network device. The process of carrying the business.
  • the method 100 is performed by an access network device, that is, the execution entity of the method 100 is an access network device.
  • S110 obtains service bearer request information, including:
  • the service bearer request information is used to notify the access network device that the non-access stratum (NAS) of the terminal sends a service bearer request to the core network device, where the service bearer request information Including the business category of the target business;
  • NAS non-access stratum
  • S120 obtains service category prohibition information, including:
  • the service category prohibition information is generated, and the service category prohibition information includes a plurality of service categories and prohibition parameters corresponding to the plurality of service categories respectively.
  • the method 100 may further include:
  • the access network device When it is determined that the terminal is prohibited from establishing the bearer of the target service according to the forbidden parameter, the access network device sends, to the core network device, third indication information for indicating that the bearer of the target service is prohibited from being established, so as to facilitate the core network.
  • the device notifies the non-access stratum of the terminal to prohibit the establishment of the bearer of the target service.
  • the method 100 may further include:
  • the access network device When determining, according to the forbidden parameter, the bearer that allows the terminal to establish the target service, the access network device sends, to the access layer of the terminal, fourth indication information indicating that the bearer of the target service is allowed to be established.
  • FIG. 3 shows a schematic flow diagram of a method 300 of traffic class congestion control in accordance with an embodiment of the present invention.
  • Method 300 includes:
  • the access network device sets the service category prohibition information according to the data service carried by the current network.
  • the business category prohibition information includes multiple service categories and each service category in the connected state.
  • Corresponding prohibition parameters for example, prohibition probability or prohibition bit map.
  • the access network device may also generate access prohibition information (for example, an access prohibition probability or an access level bit mapping) in an idle state, and is used to perform congestion control on the terminal in an idle state.
  • the embodiment of the invention is not limited.
  • the NAS of the terminal in the connected state sends a service bearer request to the core network device, where the service class of the service bearer that the terminal requests to establish is included.
  • the core network device notifies the access network device terminal to request to establish a service bearer by using the service bearer request information.
  • the service bearer request information includes the service category of the service bearer that the terminal requests to establish.
  • the access network device acquires a random number generated by the terminal for the target service (preferably, the terminal generates a random number for the target service and sends the random number to the access network device), or the access network device acquires the access level of the terminal. It should be understood that the random number or the access level may be sent to the core network device in the service bearer request, and notified by the core network device to the access network device; the random number or the access level may also be separately sent to the access network device.
  • the manner in which the access network device obtains the random number or the access level is not limited in this embodiment of the present invention.
  • the access network device finds the prohibition probability or the prohibition bit mapping corresponding to the service category in the forbidden parameter according to the service type of the target service in the service bearer request information, and determines according to the random number or the access level acquired in S340. Whether to prohibit the terminal from establishing the bearer of the target service.
  • the S361 access network device When it is determined that the terminal is prohibited from establishing the bearer of the target service, the S361 access network device sends the third indication information indicating that the bearer of the target service is prohibited from being established to the core network device, and the S362 core network device notifies the terminal of the NAS to prohibit the establishment of the target.
  • the bearer of the business When it is determined that the terminal is prohibited from establishing the bearer of the target service, the S361 access network device sends the third indication information indicating that the bearer of the target service is prohibited from being established to the core network device, and the S362 core network device notifies the terminal of the NAS to prohibit the establishment of the target.
  • the bearer of the business When it is determined that the terminal is prohibited from establishing the bearer of the target service, the S361 access network device sends the third indication information indicating that the bearer of the target service is prohibited from being established to the core network device, and the S362 core network device notifies the terminal of the NAS to prohibit the establishment of
  • the S370 access network device When it is determined that the terminal is allowed to establish the bearer of the target service, the S370 access network device sends the fourth indication information for indicating the bearer that is allowed to establish the target service to the AS of the terminal.
  • the method 100 is performed by an access network device, that is, the execution entity of the method 100 is an access network device.
  • S110 obtains service bearer request information, including:
  • S120 obtains service category prohibition information, including:
  • the service category prohibition information is generated, and the service category prohibition information includes a plurality of service categories and prohibition parameters corresponding to the plurality of service categories respectively.
  • the method 100 may further include:
  • the access network device When it is determined that the terminal is prohibited from establishing the bearer of the target service according to the forbidden parameter, the access network device sends, to the access layer of the terminal, fifth indication information indicating that the bearer of the target service is prohibited from being established.
  • the method 100 may further include:
  • the access network device When determining, according to the forbidden parameter, the bearer that allows the terminal to establish the target service, the access network device sends, to the core network device, sixth indication information that is used to indicate that the bearer of the target service is allowed to be established.
  • FIG. 4 shows a schematic flow diagram of a method 400 of traffic class congestion control in accordance with an embodiment of the present invention.
  • Method 400 includes:
  • the access network device sets the service category prohibition information according to the data service carried by the current network.
  • the service category prohibition information includes a plurality of service categories and a prohibition parameter corresponding to each service category in the connected state, for example, a prohibition probability or a prohibition bit map.
  • the access network device may also generate access prohibition information (such as an access prohibition probability or an access level bit mapping) in an idle state, and perform congestion control on the terminal in an idle state.
  • the embodiment of the invention is not limited.
  • S420 The AS in the connected state sends the service bearer request information to the access network device, where the service class of the service bearer that the terminal requests to establish is included.
  • the access network device acquires a random number generated by the terminal for the target service (preferably, the terminal generates a random number for the target service and sends the random number to the access network device), or the access network device acquires the access level of the terminal. It should be understood that the random number or the access level may be sent to the core network device in the service bearer request, and notified by the core network device to the access network device; the random number or the access level may also be separately sent to the access network device.
  • the manner in which the access network device obtains the random number or the access level is not limited in this embodiment of the present invention.
  • the access network device finds a prohibition probability or a forbidden bit mapping corresponding to the service category in the forbidden parameter according to the service type of the target service in the service bearer request information, and determines according to the random number or the access level acquired in S430. Whether to prohibit the terminal from establishing the bearer of the target service.
  • the S450 access network device When it is determined that the terminal is prohibited from establishing the bearer of the target service, the S450 access network device sends, to the AS of the terminal, fifth indication information indicating that the bearer of the target service is prohibited from being established.
  • the S460 access network device sends, to the core network device, sixth indication information, which is used to indicate that the bearer is allowed to establish the target service, where the sixth indication information includes the service bearer that the terminal requests to establish. Information.
  • the method 100 is performed by a core network device, that is, the execution entity of the method 100 is a core network device.
  • S110 obtains service bearer request information, including:
  • NAS non-access stratum
  • S120 obtains service category prohibition information, including:
  • the access network device And receiving, by the access network device, the service category prohibition information, where the service category prohibition information includes multiple service categories and prohibition parameters corresponding to the multiple service categories respectively.
  • the method 100 may further include:
  • the core network device When it is determined that the terminal is prohibited from establishing the bearer of the target service according to the forbidden parameter, the core network device sends, to the non-access stratum of the terminal, seventh indication information for indicating that the bearer of the target service is prohibited from being established.
  • the method 100 may further include:
  • the core network device When determining, according to the forbidden parameter, that the terminal is allowed to establish the bearer of the target service, the core network device sends, to the access network device, eighth indication information that is used to indicate that the bearer of the target service is allowed to be established. .
  • FIG. 5 shows a schematic flow diagram of a method 500 of traffic class congestion control in accordance with an embodiment of the present invention.
  • Method 500 includes:
  • the core network device receives the service category prohibition information sent by the access network device.
  • the service category prohibition information is set by the access network device according to the data service carried by the current network.
  • the service category prohibition information includes a plurality of service categories and a prohibition parameter corresponding to each service category in the connected state, for example, a prohibition probability or a prohibition bit map.
  • the access network device may also generate access prohibition information (for example, an access prohibition probability or an access level bit mapping) in an idle state, and send the information to the terminal (not shown in FIG. 5) for The congestion control is performed on the terminal in the idle state, which is not limited in the embodiment of the present invention.
  • S520 The NAS of the terminal in the connected state sends the service bearer request information to the core network device, where the service class of the service bearer that the terminal requests to establish is included.
  • the core network device acquiring terminal generates a random number for the target service (preferably, the terminal generates a random number for the target service and sends the random number to the access network device), or the core network device acquires the access level of the terminal.
  • the random number or the access level may be sent to the core network device in the service bearer request information; the random number or the access level may also be separately sent to the core network device, and the embodiment of the present invention obtains the random number or the core network device.
  • the access level is not limited.
  • the core network device finds the prohibition probability or the forbidden bit mapping corresponding to the service category in the forbidden parameter according to the service type of the target service in the service bearer request information, and determines whether the random number or the access level obtained in S530 is determined according to the random number or the access level obtained in S530.
  • the terminal is forbidden to establish the bearer of the target service.
  • the S550 core network device When it is determined that the terminal is prohibited from establishing the bearer of the target service, the S550 core network device sends the seventh indication information indicating that the bearer of the target service is prohibited from being established to the NAS of the terminal.
  • the S560 core network device is configured to send, to the access network device, eighth indication information indicating that the bearer of the target service is allowed to be established.
  • the method for controlling traffic category congestion control in the embodiment of the present invention is described in detail above from the perspective of determining whether to prohibit the execution of the bearer of the target service.
  • the method for congestion control of the service category is described from the perspective of the terminal.
  • FIG. 6 shows a schematic flow diagram of a method 600 of traffic class congestion control in accordance with an embodiment of the present invention.
  • Method 600 is performed by a terminal in a connected state, including:
  • the service bearer request information is sent, where the service bearer request information includes information corresponding to the request that the terminal in the connected state requests to establish the bearer initiated by the target service, where the service bearer request information includes the service category to which the target service belongs.
  • S620 Receive indication information that prohibits or allows the terminal to establish a bearer of a target service that belongs to the service category.
  • the method for controlling the traffic congestion of the service in the embodiment of the present invention can effectively prevent the terminal from accessing the network through the high-priority service request, and then initiate the low-priority service request, and the other
  • the problem that the idle terminal directly initiates the low-priority service request causes unfairness, thereby implementing a fair congestion control mechanism for each terminal.
  • the S610 sends the service bearer request information, including:
  • the terminal sends the service bearer request information to the access layer by using a non-access stratum
  • the S620 receives the indication information that prohibits or allows the terminal to establish a bearer of the target service that belongs to the service category, and includes:
  • the non-access stratum of the terminal receives the indication information sent by the access layer of the terminal.
  • the S610 sends the service bearer request information, including:
  • the terminal sends the service bearer request information to the core network device by using a non-access stratum
  • the S620 receives the indication information that prohibits or allows the terminal to establish a bearer of the target service that belongs to the service category, and includes:
  • the indication information that is sent by the core network device to prohibit the terminal from establishing the target service, or the terminal receiving, by the access layer, the access network device to allow the terminal to establish the target service.
  • the indication information carried.
  • the S610 sends the service bearer request information, including:
  • the terminal sends the service bearer request information to the access network device by using an access layer
  • the S620 receives the indication information that prohibits or allows the terminal to establish a bearer of the target service that belongs to the service category, and includes:
  • the terminal receives, by using an access layer, indication information that is sent by the access network device and prohibits the terminal from establishing a bearer of the target service.
  • the S610 sends the service bearer request information, including:
  • the terminal sends the service bearer request information to the core network device by using a non-access stratum
  • the S620 receives the indication information that prohibits or allows the terminal to establish a bearer of the target service that belongs to the service category, and includes:
  • the terminal receives, by the non-access stratum, indication information that is sent by the core network device to prohibit the terminal from establishing the bearer of the target service.
  • the method of traffic class congestion control is described below from the perspective of a core network device.
  • FIG. 7 shows a schematic flow chart of a method 700 of traffic class congestion control in accordance with an embodiment of the present invention.
  • Method 700 is performed by a core network device, including:
  • S710 The service bearer request sent by the non-access stratum sent by the terminal, where the service bearer request is used by the terminal in the connected state to request to establish a bearer initiated by the target service, where the service bearer request includes the service to which the target service belongs. category;
  • S720 Send service bearer request information to the access network device, where the service bearer request information is used to notify the access network device that the non-access stratum of the terminal sends a service bearer request to the core network device, where the service bearer request information is Includes the business category to which the target business belongs.
  • the method 700 may further include:
  • the terminal is notified to prohibit the establishment of bearers belonging to the target service of the service category.
  • FIG. 8 shows a schematic flow diagram of a method 800 of traffic class congestion control in accordance with an embodiment of the present invention.
  • Method 800 is performed by a core network device, including:
  • the core network device receives the indication information that is sent by the access network device to indicate that the bearer of the target service is allowed to be established.
  • the method of traffic class congestion control is described below from the perspective of an access network device.
  • FIG. 9 shows a schematic flow diagram of a method 900 of traffic class congestion control in accordance with an embodiment of the present invention.
  • the method 900 is performed by an access network device, including:
  • the access network device sends a service category prohibition information to the core network device, where the service category prohibition information includes a prohibition parameter corresponding to the service category to which the target service belongs in the connected state.
  • the access network device receives the indication information that is sent by the core network device to indicate that the bearer of the target service is allowed to be established.
  • the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be directed to the embodiments of the present invention.
  • the implementation process constitutes any limitation.
  • the method for traffic class congestion control of the embodiment of the present invention is described in detail.
  • the device for traffic class congestion control of the embodiment of the present invention is described below.
  • FIG. 10 shows a schematic block diagram of an apparatus 1000 for traffic class congestion control in accordance with an embodiment of the present invention.
  • the device 1000 includes:
  • the obtaining module 1010 is configured to obtain the service bearer request information, where the service bearer request information includes information corresponding to the request that the terminal in the connected state requests to establish a bearer initiated by the target service, where the service bearer request information includes the The business category to which the target business belongs;
  • the obtaining module 1010 is further configured to obtain the service category prohibition information, where the service category prohibition information includes a prohibition parameter corresponding to the service category to which the target service belongs in the connected state;
  • the determining module 1020 is configured to determine, according to the forbidden parameter, whether the terminal is prohibited from establishing a bearer belonging to the target service of the service category.
  • the device of the service category congestion control in the embodiment of the present invention can effectively prevent the terminal from passing the high priority service request by performing bearer establishment control on the terminal in the connected state according to the forbidden parameter. Accessing the network, and subsequently initiating low-priority service requests, and indirectly launching low-priority service requests directly with other idle terminals, thereby achieving a fair congestion control mechanism for each terminal.
  • the forbidden parameter is a forbidden probability
  • the acquiring module 1010 is further configured to:
  • the determining module 1020 is specifically configured to:
  • the terminal When the random number is less than the forbidden probability, the terminal is prohibited from establishing a bearer of the target service; when the random number is greater than the forbidden probability, the terminal is allowed to establish a bearer of the target service.
  • the prohibition probability is smaller than an access prohibition probability corresponding to the service category to which the target service belongs in the idle state.
  • the forbidden parameter is a forbidden bit mapping
  • the obtaining module 1010 is further configured to:
  • the determining module 1020 is specifically configured to:
  • the terminal When the access level of the terminal is set to 1 in the forbidden bit mapping, the terminal is prohibited from establishing a bearer of the target service; when the access level of the terminal is not in the forbidden bit mapping When the middle is set to 1, the terminal is allowed to establish a bearer of the target service.
  • the number of bits set in the forbidden bit map may be less than the number of bits set in the bit map corresponding to the service class to which the target service belongs in the idle state.
  • the device 1000 is an access layer of the terminal
  • the obtaining module 1010 obtains service bearer request information, including:
  • the obtaining module 1010 obtains service category prohibition information, including:
  • the access network device And receiving, by the access network device, the service category prohibition information, where the service category prohibition information includes multiple service categories and prohibition parameters respectively corresponding to the multiple service categories.
  • the device 1000 further includes:
  • a sending module configured to send, to the non-access stratum, a bearer for indicating that the target service is prohibited from being established, when it is determined that the terminal is prohibited from establishing the bearer of the target service according to the forbidden parameter.
  • the device 1000 further includes:
  • a sending module configured to send, according to the forbidden parameter, a second indication information that is used to indicate that a bearer that is allowed to establish the target service is sent to the non-access stratum when determining that the terminal is allowed to establish the bearer of the target service.
  • the access layer initiates, to the access network device, a process of establishing a bearer of the target service.
  • the device 1000 is an access network device
  • the obtaining module 1010 obtains service bearer request information, including:
  • the request information includes a service category to which the target service belongs;
  • the obtaining module 1010 obtains service category prohibition information, including:
  • the service category prohibition information is generated, and the service category prohibition information includes a plurality of service categories and prohibition parameters respectively corresponding to the plurality of service categories.
  • the device 1000 further includes:
  • a sending module configured to send, to the core network device, third indication information that is used to indicate that the bearer of the target service is prohibited from being established, when determining that the terminal is not allowed to establish the bearer of the target service according to the forbidden parameter, So that the core network device notifies the non-access stratum of the terminal to prohibit the establishment of the bearer of the target service.
  • the device 1000 further includes:
  • a sending module configured to: when determining, according to the forbidden parameter, that the terminal is allowed to establish the bearer of the target service, send a fourth indication to the access layer of the terminal to indicate that the bearer of the target service is allowed to be established information.
  • the device 1000 is an access network device
  • the obtaining module 1010 obtains service bearer request information, including:
  • the obtaining module 1010 obtains service category prohibition information, including:
  • the service category prohibition information is generated, and the service category prohibition information includes a plurality of service categories and prohibition parameters respectively corresponding to the plurality of service categories.
  • the device 1000 further includes:
  • a sending module configured to, when determining, prohibiting the terminal from establishing the target according to the prohibition parameter
  • the fifth indication information for indicating that the bearer of the target service is prohibited from being established is sent to the access layer of the terminal.
  • the device 1000 further includes:
  • a sending module configured to: when determining, according to the forbidden parameter, that the terminal is allowed to establish the bearer of the target service, send, to the core network device, sixth indication information that is used to indicate that the bearer of the target service is allowed to be established.
  • the device 1000 is a core network device
  • the obtaining module 1010 obtains service bearer request information, including:
  • the obtaining module 1010 obtains service category prohibition information, including:
  • the service category prohibition information includes multiple service categories and prohibition parameters respectively corresponding to the multiple service categories.
  • the device 1000 further includes:
  • a sending module configured to send, to the non-access stratum of the terminal, a seventh bearer for indicating that the target service is prohibited from being established, when it is determined that the terminal is prohibited from establishing the bearer of the target service according to the forbidden parameter.
  • the device 1000 further includes:
  • a sending module configured to: when determining, according to the forbidden parameter, that the terminal is allowed to establish a bearer of the target service, send, to the access network device, an eighth indication information that is used to indicate that a bearer of the target service is allowed to be established.
  • the obtaining module may be implemented by a receiver or a processor
  • the sending module may be implemented by a transmitter
  • the determining module 1020 may be implemented by a processor.
  • device 1100 can include a processor 1110, a receiver 1120, a transmitter 1130, and a memory 1140.
  • the memory 1140 can be used to store code and the like executed by the processor 1110.
  • bus system 1150 which in addition to the data bus includes a power bus, a control bus, and a status signal bus.
  • the device 1000 shown in FIG. 10 or the device 1100 shown in FIG. 11 can implement the various processes implemented in the foregoing embodiments of FIG. 1 to FIG. 9. To avoid repetition, details are not described herein again.
  • the processor may be an integrated circuit chip with signal processing capabilities.
  • the steps of the foregoing method embodiments may be through an integrated logic circuit or hardware of hardware in the processor.
  • the instructions in the form of pieces are completed.
  • the processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), or the like. Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method.
  • the memory in the embodiments of the present invention may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (Programmable ROM (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), and an electrically erasable memory.
  • ROM read-only memory
  • PROM programmable read only memory
  • EPROM erasable programmable read only memory
  • EEPROM erasable programmable read only memory
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • Synchronous DRAM synchronous dynamic random access memory
  • SDRAM Double Data Rate SDRAM
  • DDR SDRAM Double Data Rate SDRAM
  • ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • SLDRAM Synchronous Connection Dynamic Random Access Memory
  • DR RAM direct memory bus random access memory
  • FIG. 12 is a schematic block diagram of a terminal 1200 for traffic class congestion control according to an embodiment of the present invention.
  • the terminal 1200 includes:
  • the sending module 1210 is configured to send the service bearer request information, where the service bearer request information includes information corresponding to the request that the terminal in the connected state requests to establish a bearer initiated by the target service, where the service bearer request information includes the The business category to which the target business belongs;
  • the receiving module 1220 is configured to receive indication information that prohibits or allows the terminal to establish a bearer of a target service that belongs to the service category.
  • the sending module 1210 is specifically configured to:
  • the receiving module 1220 is specifically configured to:
  • the non-access stratum receives the indication information sent by the access layer of the terminal.
  • the sending module 1210 is specifically configured to:
  • the receiving module 1220 is specifically configured to:
  • the sending module 1210 is specifically configured to:
  • the receiving module 1220 is specifically configured to:
  • the sending module 1210 is specifically configured to:
  • the receiving module 1220 is specifically configured to:
  • the sending module 1210 may be implemented by a transmitter
  • the receiving module 1220 may be implemented by a receiver
  • the terminal 1300 may include a processor 1310, a receiver 1320, a transmitter 1330, and a memory 1340.
  • the memory 1340 can be used to store code and the like executed by the processor 1310.
  • bus system 1350 that includes, in addition to the data bus, a power bus, a control bus, and a status signal bus.
  • the terminal 1200 shown in FIG. 12 or the terminal 1300 shown in FIG. 13 can implement the various processes implemented in the foregoing embodiments of FIG. 1 to FIG. 9. To avoid repetition, details are not described herein again.
  • FIG. 14 shows a core network device 1400 for traffic class congestion control according to an embodiment of the present invention. Schematic block diagram.
  • the core network device 1400 includes:
  • the receiving module 1410 is configured to receive a service bearer request sent by the non-access stratum sent by the terminal, where the service bearer request is used by the terminal in the connected state to request to establish a bearer initiated request of the target service, where the service bearer request includes The service category to which the target service belongs;
  • the sending module 1420 is configured to send the service bearer request information to the access network device, where the service bearer request information is used to notify the access network device that the non-access stratum of the terminal sends the service bearer to the core network device.
  • the service includes: the service bearer request information includes a service category to which the target service belongs.
  • the receiving module 1410 is further configured to:
  • the sending module 1420 is further configured to:
  • the sending module 1420 may be implemented by a transmitter
  • the receiving module 1410 may be implemented by a receiver
  • the core network device 1500 can include a processor 1510, a receiver 1520, a transmitter 1530, and a memory 1540.
  • the memory 1540 can be used to store code and the like executed by the processor 1510.
  • a bus system 1550 that includes, in addition to the data bus, a power bus, a control bus, and a status signal bus.
  • the core network device 1400 shown in FIG. 14 or the core network device 1500 shown in FIG. 15 can implement the various processes implemented in the foregoing embodiments of FIG. 1 to FIG. 9. To avoid repetition, details are not described herein again.
  • FIG. 16 shows a schematic block diagram of a core network device 1600 for traffic class congestion control in accordance with one embodiment of the present invention.
  • the core network device 1600 includes:
  • the receiving module 1610 is configured to: when the access network device determines that the terminal is allowed to establish a bearer of the target service, receive the indication information that is sent by the access network device to indicate that the bearer of the target service is allowed to be established.
  • the receiving module 1610 may be implemented by a receiver.
  • core network device 1700 can include a processor 1710, a receiver 1720, and a memory 1730.
  • the memory 1730 can be used to store code and the like executed by the processor 1710.
  • bus system 1740 includes a power bus, a control bus, and a status signal bus.
  • the core network device 1600 shown in FIG. 16 or the core network device 1700 shown in FIG. 17 can implement the various processes implemented in the foregoing embodiments of FIG. 1 to FIG. 9. To avoid repetition, details are not described herein again.
  • FIG. 18 is a schematic block diagram of an access network device 1800 for traffic class congestion control in accordance with one embodiment of the present invention.
  • the access network device 1800 includes:
  • the sending module 1810 is configured to send the service category prohibition information to the core network device, where the service category prohibition information includes a prohibition parameter corresponding to the service category to which the target service belongs in the connected state;
  • the receiving module 1820 is configured to: when the core network device determines that the terminal is allowed to establish the bearer of the target service, receive the indication information that is sent by the core network device to indicate that the bearer of the target service is allowed to be established.
  • the sending module 1810 may be implemented by a transmitter
  • the receiving module 1820 may be implemented by a receiver.
  • the access network device 1900 can include a processor 1910, a receiver 1920, a transmitter 1930, and a memory 1940.
  • the memory 1940 can be used to store code and the like executed by the processor 1910.
  • a bus system 1950 that includes, in addition to the data bus, a power bus, a control bus, and a status signal bus.
  • the access network device 1800 shown in FIG. 18 or the access network device 1900 shown in FIG. 19 can implement the various processes implemented in the foregoing embodiments of FIG. 1 to FIG. 9. To avoid repetition, details are not described herein again.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division, and may be implemented in actual implementation.
  • multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Landscapes

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

Abstract

本发明公开了一种业务类别拥塞控制的方法和设备，该方法包括：获取业务承载请求信息，该业务承载请求信息包括处于连接态的终端用于请求建立目标业务的承载发起的请求所对应的信息，该业务承载请求信息中包括该目标业务所属的业务类别；获取业务类别禁止信息，该业务类别禁止信息中包括连接态下该目标业务所属的业务类别对应的禁止参数；根据该禁止参数，判断是否禁止该终端建立属于该业务类别的目标业务的承载。本发明实施例的方法能够有效避免终端通过高优先级业务请求接入网络，随后发起低优先级业务请求，与其他处于空闲态的终端直接发起低优先级业务请求而引发的不公平性的问题，从而实现对各终端的公平的拥塞控制机制。

Description

业务承载拥塞控制的方法及设备 技术领域
本发明实施例涉及通信领域，并且更具体地，涉及一种业务承载拥塞控制的方法及设备。
背景技术
当前，随着无线通信技术的飞速发展，数据业务呈现爆发式增长。数据业务的快速增长使得无线通信的接入网和核心网可能会出现拥塞。为解决拥塞问题，目前无线通信中正在讨论通过***预先针对终端的部分数据业务设置随机接入优先级，从而使处于空闲态的终端在发起业务建立流程时进行自动判断，在判断可以接入的条件下再发起随机接入以及之后的业务建立流程。
例如，在长期演进(Long Term Evolution，LTE)***中，从版本8(Release 8，R8)开始就引入了接入控制机制，例如接入等级禁止(Access Class Barring，ACB)等。在R8***中，业务类别可以包括移动终端发起数据(MO-data)业务、移动终端发起信令(MO-signaling)业务、移动终端被叫数据(MT-data)业务、高优先级(High Priority，通常指运营商预留的)业务以及紧急(Emergency)业务等。不同类别的业务对应的优先级不同。
接入网设备(例如基站等)，在广播的***消息中通知终端从空闲态发起随机接入时，需要进行接入控制的业务类别以及相应的接入控制参数。这里，可以不同类别的业务可以根据其优先级的不同，设置不同的接入控制参数。当处于空闲态的终端需要发起业务请求时，根据业务类别以及相应的接入控制参数确定该业务请求是否被禁止掉。当该业务请求被禁止掉时，不进行随机接入以及之后的业务建立流程，从而可以缓解接入网或者核心网的拥塞情况。
但是上述接入控制机制是针对处于空闲态的终端的，即是针对终端首次发起业务请求时的。在当前的机制下，终端可能通过高优先级的业务请求接入网络，并在随后发起低优先级业务请求。因为此时终端已经在网络中处于连接态，不需要发起随机接入、业务建立请求等流程，直接申请增加新的承载即可。这样有可能会造成处于连接态的该终端所发起的低优先级业务请求 和其他处于空闲态的终端直接发起低优先级业务请求的不公平性。
发明内容
本发明实施例提供一种业务类别拥塞控制的方法及设备，可以对处于连接态的终端进行承载建立的控制，从而实现对各终端的公平的拥塞控制机制。
第一方面，提供了一种业务类别拥塞控制的方法，包括：
获取业务承载请求信息，所述业务承载请求信息包括处于连接态的终端用于请求建立目标业务的承载发起的请求所对应的信息，所述业务承载请求信息中包括所述目标业务所属的业务类别；
获取业务类别禁止信息，所述业务类别禁止信息中包括连接态下所述目标业务所属的业务类别对应的禁止参数；
根据所述禁止参数，判断是否禁止所述终端建立属于所述业务类别的目标业务的承载。
第二方面，提供了一种业务类别拥塞控制的方法，包括：
发送业务承载请求信息，所述业务承载请求信息包括处于连接态的终端用于请求建立目标业务的承载发起的请求所对应的信息，所述业务承载请求信息中包括所述目标业务所属的业务类别；
接收禁止或允许所述终端建立属于所述业务类别的目标业务的承载的指示信息。
第三方面，提供了一种业务类别拥塞控制的方法，包括：
接收终端的非接入层发送的业务承载请求，所述业务承载请求为处于连接态的终端用于请求建立目标业务的承载发起的请求，所述业务承载请求中包括所述目标业务所属的业务类别；
向接入网设备发送业务承载请求信息，所述业务承载请求信息用于通知所述接入网设备所述终端的非接入层向所述核心网设备发送了业务承载请求，所述业务承载请求信息中包括所述目标业务所属的业务类别。
第四方面，提供了一种业务类别拥塞控制的方法，包括：
当接入网设备确定允许终端建立目标业务的承载时，核心网设备接收所述接入网设备发送的用于指示允许建立所述目标业务的承载的指示信息。
第五方面，提供了一种业务类别拥塞控制的方法，包括：
接入网设备向核心网设备发送业务类别禁止信息，所述业务类别禁止信息中包括连接态下所述目标业务所属的业务类别对应的禁止参数；
当所述核心网设备确定允许终端建立所述目标业务的承载时，所述接入网设备接收所述核心网设备向发送的用于指示允许建立所述目标业务的承载的指示信息。
第六方面，提供了一种业务类别拥塞控制的设备，包括：
获取模块，用于获取业务承载请求信息，所述业务承载请求信息包括处于连接态的终端用于请求建立目标业务的承载发起的请求所对应的信息，所述业务承载请求信息中包括所述目标业务所属的业务类别；
所述获取模块还用于获取业务类别禁止信息，所述业务类别禁止信息中包括连接态下所述目标业务所属的业务类别对应的禁止参数；
判断模块，用于根据所述禁止参数，判断是否禁止所述终端建立属于所述业务类别的目标业务的承载。
第七方面，提供了一种业务类别拥塞控制的终端，包括：
发送模块，用于发送业务承载请求信息，所述业务承载请求信息包括处于连接态的终端用于请求建立目标业务的承载发起的请求所对应的信息，所述业务承载请求信息中包括所述目标业务所属的业务类别；
接收模块，用于接收禁止或允许所述终端建立属于所述业务类别的目标业务的承载的指示信息。
第八方面，提供了一种业务类别拥塞控制的核心网设备，包括：
接收模块，用于接收终端发送的非接入层发送的业务承载请求，所述业务承载请求为处于连接态的终端用于请求建立目标业务的承载发起的请求，所述业务承载请求中包括所述目标业务所属的业务类别；
发送模块，用于向接入网设备发送业务承载请求信息，所述业务承载请求信息用于通知所述接入网设备所述终端的非接入层向所述核心网设备发送了业务承载请求，所述业务承载请求信息中包括所述目标业务所属的业务类别。
第九方面，提供了一种业务类别拥塞控制的核心网设备，包括：
接收模块，用于当接入网设备确定允许终端建立目标业务的承载时，接收所述接入网设备发送的用于指示允许建立所述目标业务的承载的指示信息。
第十方面，提供了一种业务类别拥塞控制的接入网设备，包括：
发送模块，用于向核心网设备发送业务类别禁止信息，所述业务类别禁止信息中包括连接态下所述目标业务所属的业务类别对应的禁止参数；
接收模块，用于当所述核心网设备确定允许终端建立所述目标业务的承载时，接收所述核心网设备向发送的用于指示允许建立所述目标业务的承载的指示信息。
基于上述技术方案，本发明实施例的业务类别拥塞控制的方法及设备，通过根据禁止参数对处于连接态的终端进行承载建立的控制，能够有效避免终端通过高优先级业务请求接入网络，随后发起低优先级业务请求，与其他处于空闲态的终端直接发起低优先级业务请求而引发的不公平性的问题，从而实现对各终端的公平的拥塞控制机制。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明一个实施例业务类别拥塞控制的方法的示意性流程图。
图2是本发明另一个实施例业务类别拥塞控制的方法的示意性流程图。
图3是本发明另一个实施例业务类别拥塞控制的方法的示意性流程图。
图4是本发明另一个实施例业务类别拥塞控制的方法的示意性流程图。
图5是本发明另一个实施例业务类别拥塞控制的方法的示意性流程图。
图6是本发明另一个实施例业务类别拥塞控制的方法的示意性流程图。
图7是本发明另一个实施例业务类别拥塞控制的方法的示意性流程图。
图8是本发明另一个实施例业务类别拥塞控制的方法的示意性流程图。
图9是本发明另一个实施例业务类别拥塞控制的方法的示意性流程图。
图10是本发明一个实施例业务类别拥塞控制的设备的示意性框图。
图11是本发明另一个实施例业务类别拥塞控制的设备的示意性框图。
图12是本发明一个实施例的终端的示意性框图。
图13是本发明另一个实施例的终端的示意性框图。
图14是本发明一个实施例的核心网设备的示意性框图。
图15是本发明另一个实施例的核心网设备的示意性框图。
图16是本发明一个实施例的核心网设备的示意性框图。
图17是本发明另一个实施例的核心网设备的示意性框图。
图18是本发明一个实施例的接入网设备的示意性框图。
图19是本发明另一个实施例的接入网设备的示意性框图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
在本说明书中使用的术语“部件”、“模块”、“***”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在2个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地***、分布式***和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它***交互的互联网)的信号通过本地和/或远程进程来通信。
应理解，本发明实施例的技术方案可以应用于各种通信***，例如：全球移动通讯(Global System of Mobile Communication，简称为“GSM”)***、码分多址(Code Division Multiple Access，简称为“CDMA”)***、宽带码分多址(Wideband Code Division Multiple Access，简称为“WCDMA”)通用分组无线业务(General Packet Radio Service，简称为“GPRS”)***、长期演进(Long Term Evolution，简称为“LTE”)***、LTE频分双工(Frequency Division Duplex，简称为“FDD”)***、LTE时分双工(Time Division Duplex，简称为“TDD”)、通用移动通信***(Universal Mobile Telecommunication System，简称为“UMTS”)、全球互联微波接入(Worldwide Interoperability for Microwave Access，简称为“WiMAX”)通信***，以及未来的5G通信*** 等。
本发明结合终端描述了各个实施例。终端可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，终端可以指用户设备(User Equipment，简称为“UE”)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，简称为“SIP”)电话、无线本地环路(Wireless Local Loop，简称为“WLL”)站、个人数字处理(Personal Digital Assistant，简称为“PDA”)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端等。
本发明结合接入网设备描述了各个实施例。接入网设备可以是接入网中用于与终端进行通信的设备，例如，可以是GSM***或CDMA中的基站(Base Transceiver Station，简称为“BTS”)，也可以是WCDMA***中的基站(NodeB，简称为“NB”)，还可以是LTE***中的演进型基站(Evolutional Node B，简称为“eNB”或“eNodeB”)，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的接入网设备等。
本发明结合核心网设备描述了各个实施例。核心网设备主要用于提供用户连接、对用户的管理以及对业务完成承载，作为承载网络提供到外部网络的接口等等。例如，可以是移动管理实体(Mobility Management Entity，MME)，或者核心网中的其它网元。
图1是本发明一个实施例的业务类别拥塞控制的方法100的示意性流程图。应理解，方法100可以由终端执行，也可以由接入网设备，例如基站执行，还可以由核心网设备，例如MME执行。方法100包括：
S110，获取业务承载请求信息，该业务承载请求信息包括处于连接态的终端用于请求建立目标业务的承载发起的请求所对应的信息，该业务承载请求信息中包括该目标业务所属的业务类别；
S120，获取业务类别禁止信息，该业务类别禁止信息中包括连接态下该目标业务所属的业务类别对应的禁止参数；
S130，根据该禁止参数，判断是否禁止该终端建立属于该业务类别的目标业务的承载。
本发明实施例的业务类别拥塞控制的方法，通过根据禁止参数对处于连接态的终端进行承载建立的控制，能够有效避免终端通过高优先级业务请求接入网络，随后发起低优先级业务请求，与其他处于空闲态的终端直接发起低优先级业务请求而引发的不公平性的问题，从而实现对各终端的公平的拥塞控制机制。
其中，根据方法100的执行主体不同，S110中的业务承载请求信息可以是由终端的非接入层(Non-access Stratum，NAS)向终端的接入层(Access Stratum，AS)发送的；也可以是由终端的NAS向核心网设备发送业务承载请求后，核心网设备向接入网设备通知的；还可以是由终端的AS向接入网设备发送的；还可以是由终端的NAS向核心网设备发送的。业务承载请求是处于连接态的终端用于请求建立目标业务的承载发起的请求，该业务承载请求中包括目标业务的业务类别。应理解，多个业务可以同属于一种业务类别。
终端处于空闲态是指终端未与网络侧(包括接入网和核心网)建立连接，并且终端未承载任何业务。终端处于连接态是指终端通过信令流程已与网络侧(包括接入网和核心网)建立连接。
S120中的业务类别禁止信息一般是由接入网设备根据当前网络承载的数据业务的情况确定并生成的，通常包括连接态下多个业务类别以及各业务类别分别对应的禁止参数。并由接入网设备通过广播或单播的形式发送给终端和/或核心网设备。
S130中根据目标业务的业务类别对应的禁止参数，判断是否禁止终端建立目标业务的承载。其中，判断是否禁止建立目标业务的承载的方式可以有多种。
可选地，作为一个实施例，该禁止参数为禁止概率，该方法100还可以包括：
获取该终端针对该目标业务生成的随机数；
S130根据该禁止参数，判断是否禁止该终端建立属于该业务类别的目标业务的承载，可以包括：
当该随机数小于该禁止概率时，禁止该终端建立该目标业务的承载；当该随机数大于该禁止概率时，允许该终端建立该目标业务的承载。
具体而言，接入网设备根据当前网络承载的数据业务的情况，可以对不 同的业务类别(例如，S1，S2，…，Sn)设置不同的禁止概率(例如，P1，P2，…，Pn)。禁止概率(P1，P2，…，Pn)用于判断是否禁止处于连接态的终端建立业务承载。
当处于连接态的终端请求建立业务承载时，针对目标业务生成一个0和1之间的随机数。并将该随机数发送给方法100的执行主体。其中，该随机数可以携带于业务承载请求信息中发送，也可以单独发送，本发明实施例对此不作限定。
方法100的执行主体根据处于连接态的终端所请求的目标业务的业务类别(例如为Si)，找对其对应的禁止概率Pi。将随机数与禁止概率Pi相比较，当随机数小于禁止概率Pi时，禁止该终端建立该目标业务的承载；当随机数大于禁止概率Pi时，允许该终端建立该目标业务的承载。
应理解，随机数等于禁止概率Pi的情况可以与随机数小于禁止概率Pi时处理相一致，也可以与随机数大于禁止概率Pi时处理相一致。例如，当随机数小于或等于禁止概率Pi(随机数≤Pi)时，禁止该终端建立该目标业务的承载；当随机数大于禁止概率Pi(随机数＞Pi)时，允许该终端建立该目标业务的承载。或者，当随机数小于禁止概率Pi(随机数＜Pi)时，禁止该终端建立该目标业务的承载；当随机数大于或等于禁止概率Pi(随机数≥Pi)时，允许该终端建立该目标业务的承载。本发明实施例对此不作限定。
如果该次业务承载请求被禁止，则终端可以在间隔一段时间之后，再次在0和1之间选择一个随机数，进行业务承载请求。其中，该时间可以称为业务类别禁止时间。业务类别禁止时间的计算方式可以按照下列公式(1)计算，
Tbarring＝(0.7+0.6×随机数)×ac-BarringTime……(1)
其中，ac-BarringTime为由接入网设备配置的接入禁止时间。
本发明实施例中，禁止概率可以小于空闲态下目标业务所属的业务类别对应的接入禁止概率。
例如，终端在空闲态发起业务类别为Sj的业务承载请求，业务类别Sj对应的空闲态下接入禁止概率的为pj。继而终端处于连接态，终端在连接态发起业务类别为Si的业务承载请求，业务类别Si对应的空闲态下接入禁止概率的为pi。由于终端在之前发起业务类别为Sj的业务承载请求时，已经通过多次交互与接入网设备建立了连接，此时终端处于连接态，建立业务承载时 信令的消耗远小于空闲态，因此接入网设备可以设置连接态下禁止概率为Pi，Pi小于pi。当然，本发明实施例中也可以设置Pi等于pi，具体参数可以由运营商配置完成，本发明实施例对此不作限定。
应理解，接入网设备可以采用空闲态时终端使用的接入业务类别概率乘以空闲态时该业务类别的接入禁止概率产生连接态下该业务类别的禁止概率；或者可以采用大于0小于1的系数乘以空闲态时该业务类别的接入禁止概率产生连接态下该业务类别的禁止概率；或者直接重用空闲态时该业务类别的接入禁止概率作为连接态下该业务类别的禁止概率；或者由接入网设备单独定义连接态下该业务类别的禁止概率，本发明实施例对此不作限定。
可选地，作为另一个实施例，该禁止参数为禁止比特位映射，该方法100还可以包括：
获取该终端的接入级别(Access Class，AC)；
S130根据禁止参数，判断是否禁止该终端建立属于该业务类别的目标业务的承载，可以包括：
当该终端的接入级别在该禁止比特位映射中被置为1时，禁止该终端建立该目标业务的承载；当该终端的接入级别未在该禁止比特位映射中被置为1时，允许该终端建立该目标业务的承载。
具体而言，每个终端在接入接入网时，均会被随机分配一个接入级别。例如，接入级别可以设置为共10个级别，分别0-9，某一终端的接入级别被随机分配为5。
接入网设备根据当前网络承载的数据业务的情况，可以对不同的业务类别设置不同的禁止比特位映射(Bitmap)。例如，禁止比特位映射中包括10个级别，采用比特指示的方式标明每个级别中哪个需要禁止，哪个不需要。由于终端的接入级别为接入网设备为其随机分配的，因此同样可以实现一定概率的禁止。例如，当网络需要禁止20％的终端建立业务承载时，则随机选择两个级别设置为1，在一个具体的例子中，设置级别3和5为1。则接入级别为3和5对应的终端即使有业务承载请求，也会被禁止建立业务承载。
优选地，基于上文中描述的Pi可以小于pi的同样的原因，所述禁止比特位映射中置1的比特位的数目可以少于空闲态下所述目标业务所属的业务类别对应的比特位映射中置1的比特位的数目。
应理解，接入网设备可以根据空闲态时终端使用的比特位映射设置更多 的置1的比特位，而产生连接态下该业务类别的禁止比特位映射；或者直接重用空闲态时该业务类别的比特位映射作为连接态下该业务类别的禁止比特位映射；或者由接入网设备单独定义连接态下该业务类别的禁止比特位映射，本发明实施例对此不作限定。
上文中详细描述了本发明实施例的业务类别拥塞控制的机制。下面结合四个具体的例子详细描述本发明实施例的业务类别拥塞控制的信令流程。
在一个例子中，方法100由终端的接入层(AS)执行即方法100的执行主体为该终端的AS，
S110获取业务承载请求信息，包括：
接收该终端的非接入层(NAS)发送的业务承载请求信息；
S120获取业务类别禁止信息，包括：
接收接入网设备广播的该业务类别禁止信息，该业务类别禁止信息包括多个业务类别以及该多个业务类别分别对应的禁止参数。
在本发明实施例中，方法100还可以包括：
当根据该禁止参数，确定禁止该终端建立该目标业务的承载时，该AS向该NAS发送用于指示禁止建立该目标业务的承载的第一指示信息。
或者，在本发明实施例中，方法100还可以包括：
当根据该禁止参数，确定允许该终端建立该目标业务的承载时，该AS向该NAS发送用于指示允许建立该目标业务的承载的第二指示信息，并且该AS向该接入网设备发起建立该目标业务的承载的流程。
图2示出了本发明一个实施例的业务类别拥塞控制的方法200的示意性流程图。方法200包括：
S210，终端的AS接收接入网设备广播的业务类别禁止信息，该业务类别禁止信息包括多个业务类别以及连接态下各业务类别分别对应的禁止参数，例如，禁止概率或禁止比特位映射。当然，在S210中接入网设备也可以一并向终端广播空闲态下的接入禁止信息(例如接入禁止概率或接入级别比特位映射)，用于对空闲态下的终端执行拥塞控制，本发明实施例不作限定。
S220，处于连接态的终端的NAS向终端的AS发送业务承载请求信息，该业务承载请求信息中包括终端请求建立的业务承载的业务类别。
S230，终端的AS获取终端针对目标业务生成的随机数，或获取终端的 接入级别。
S240，终端的AS根据业务承载请求信息中目标业务的业务类别，在禁止参数中找到与该业务类别对应的禁止概率或禁止比特位映射，根据S230中获取的随机数或接入级别，判断是否禁止终端建立目标业务的承载。
S250，当确定禁止终端建立目标业务的承载时，终端的AS向终端的NAS发送用于指示禁止建立目标业务的承载的第一指示信息。
当确定允许终端建立目标业务的承载时，执行S261终端的AS向终端的NAS发送用于指示允许建立目标业务的承载的第二指示信息，并且执行S262终端的AS向接入网设备发起建立目标业务的承载的流程。
在另一个例子中，方法100由接入网设备执行，即方法100的执行主体为接入网设备，
S110获取业务承载请求信息，包括：
接收核心网设备发送的业务承载请求信息，该业务承载请求信息用于通知该接入网设备该终端的非接入层(NAS)向该核心网设备发送了业务承载请求，该业务承载请求信息中包括该目标业务的所属业务类别；
S120获取业务类别禁止信息，包括：
生成该业务类别禁止信息，该业务类别禁止信息包括多个业务类别以及该多个业务类别分别对应的禁止参数。
在本发明实施例中，方法100还可以包括：
当根据该禁止参数，确定禁止该终端建立该目标业务的承载时，该接入网设备向该核心网设备发送用于指示禁止建立该目标业务的承载的第三指示信息，以便于该核心网设备通知该终端的非接入层禁止建立该目标业务的承载。
或者，在本发明实施例中，方法100还可以包括：
当根据该禁止参数，确定允许该终端建立该目标业务的承载时，该接入网设备向该终端的接入层发送用于指示允许建立该目标业务的承载的第四指示信息。
图3示出了本发明一个实施例的业务类别拥塞控制的方法300的示意性流程图。方法300包括：
S310，接入网设备根据当前网络承载的数据业务的情况，设置业务类别禁止信息。该业务类别禁止信息包括多个业务类别以及连接态下各业务类别 分别对应的禁止参数，例如，禁止概率或禁止比特位映射。当然，在S310中接入网设备也可以一并生成空闲态下的接入禁止信息(例如接入禁止概率或接入级别比特位映射)，用于对空闲态下的终端执行拥塞控制，本发明实施例不作限定。
S320，处于连接态的终端的NAS向核心网设备发送业务承载请求，其中，包括终端请求建立的业务承载的业务类别。
S330，核心网设备通过业务承载请求信息，通知接入网设备终端向核心网设备请求建立业务承载。该业务承载请求信息中包括终端请求建立的业务承载的业务类别。
S340，接入网设备获取终端针对目标业务生成随机数(优选地，终端针对目标业务生成随机数并发送给接入网设备)，或接入网设备获取终端的接入级别。应理解，随机数或接入级别可以包括在业务承载请求中发送给核心网设备，并由核心网设备通知给接入网设备；随机数或接入级别也可以单独发送给接入网设备，本发明实施例对接入网设备获取随机数或接入级别的方式不作限定。
S350，接入网设备根据业务承载请求信息中目标业务的业务类别，在禁止参数中找到与该业务类别对应的禁止概率或禁止比特位映射，根据S340中获取的随机数或接入级别，判断是否禁止终端建立目标业务的承载。
当确定禁止终端建立目标业务的承载时，执行S361接入网设备向核心网设备发送用于指示禁止建立目标业务的承载的第三指示信息，并且执行S362核心网设备通知终端的NAS禁止建立目标业务的承载。
当确定允许终端建立目标业务的承载时，执行S370接入网设备向终端的AS发送用于指示允许建立目标业务的承载的第四指示信息。
在另一个例子中，方法100由接入网设备执行，即方法100的执行主体为接入网设备，
S110获取业务承载请求信息，包括：
接收该终端的接入层(AS)发送的业务承载请求信息；
S120获取业务类别禁止信息，包括：
生成该业务类别禁止信息，该业务类别禁止信息包括多个业务类别以及该多个业务类别分别对应的禁止参数。
在本发明实施例中，方法100还可以包括：
当根据该禁止参数，确定禁止该终端建立该目标业务的承载时，该接入网设备向该终端的接入层发送用于指示禁止建立该目标业务的承载的第五指示信息。
或者，在本发明实施例中，方法100还可以包括：
当根据该禁止参数，确定允许该终端建立该目标业务的承载时，该接入网设备向该核心网设备发送用于指示允许建立该目标业务的承载的第六指示信息。
图4示出了本发明一个实施例的业务类别拥塞控制的方法400的示意性流程图。方法400包括：
S410，接入网设备根据当前网络承载的数据业务的情况，设置业务类别禁止信息。该业务类别禁止信息包括多个业务类别以及连接态下各业务类别分别对应的禁止参数，例如，禁止概率或禁止比特位映射。当然，在S410中接入网设备也可以一并生成空闲态下的接入禁止信息(例如接入禁止概率或接入级别比特位映射)，用于对空闲态下的终端执行拥塞控制，本发明实施例不作限定。
S420，处于连接态的终端的AS向接入网设备发送业务承载请求信息，其中，包括终端请求建立的业务承载的业务类别。
S430，接入网设备获取终端针对目标业务生成随机数(优选地，终端针对目标业务生成随机数并发送给接入网设备)，或接入网设备获取终端的接入级别。应理解，随机数或接入级别可以包括在业务承载请求中发送给核心网设备，并由核心网设备通知给接入网设备；随机数或接入级别也可以单独发送给接入网设备，本发明实施例对接入网设备获取随机数或接入级别的方式不作限定。
S440，接入网设备根据业务承载请求信息中目标业务的业务类别，在禁止参数中找到与该业务类别对应的禁止概率或禁止比特位映射，根据S430中获取的随机数或接入级别，判断是否禁止终端建立目标业务的承载。
当确定禁止终端建立目标业务的承载时，执行S450接入网设备向终端的AS发送用于指示禁止建立目标业务的承载的第五指示信息。
当确定允许终端建立目标业务的承载时，执行S460接入网设备向核心网设备发送用于指示允许建立目标业务的承载的第六指示信息，该第六指示信息中包括终端请求建立的业务承载的信息。
在另一个例子中，方法100由核心网设备执行，即方法100的执行主体为核心网设备，
S110获取业务承载请求信息，包括：
接收该终端的非接入层(NAS)发送的业务承载请求信息；
S120获取业务类别禁止信息，包括：
接收接入网设备发送的该业务类别禁止信息，该业务类别禁止信息包括多个业务类别以及该多个业务类别分别对应的禁止参数。
在本发明实施例中，方法100还可以包括：
当根据该禁止参数，确定禁止该终端建立该目标业务的承载时，该核心网设备向该终端的非接入层发送用于指示禁止建立该目标业务的承载的第七指示信息。
或者，在本发明实施例中，方法100还可以包括：
当根据所述禁止参数，确定允许所述终端建立所述目标业务的承载时，所述核心网设备向所述接入网设备发送用于指示允许建立所述目标业务的承载的第八指示信息。
图5示出了本发明一个实施例的业务类别拥塞控制的方法500的示意性流程图。方法500包括：
S510，核心网设备接收接入网设备发送的业务类别禁止信息。该业务类别禁止信息是接入网设备根据当前网络承载的数据业务的情况设置的。该业务类别禁止信息包括多个业务类别以及连接态下各业务类别分别对应的禁止参数，例如，禁止概率或禁止比特位映射。当然，在S510中接入网设备也可以一并生成空闲态下的接入禁止信息(例如接入禁止概率或接入级别比特位映射)发送给终端(图5中未示出)，用于对空闲态下的终端执行拥塞控制，本发明实施例不作限定。
S520，处于连接态的终端的NAS向核心网设备发送业务承载请求信息，其中，包括终端请求建立的业务承载的业务类别。
S530，核心网设备获取终端针对目标业务生成随机数(优选地，终端针对目标业务生成随机数并发送给接入网设备)，或核心网设备获取终端的接入级别。应理解，随机数或接入级别可以包括在业务承载请求信息中发送给核心网设备；随机数或接入级别也可以单独发送给核心网设备，本发明实施例对核心网设备获取随机数或接入级别的方式不作限定。
S540，核心网设备根据业务承载请求信息中目标业务的业务类别，在禁止参数中找到与该业务类别对应的禁止概率或禁止比特位映射，根据S530中获取的随机数或接入级别，判断是否禁止终端建立目标业务的承载。
当确定禁止终端建立目标业务的承载时，执行S550核心网设备向终端的NAS发送用于指示禁止建立目标业务的承载的第七指示信息。
当确定允许终端建立目标业务的承载时，执行S560核心网设备向接入网设备发送用于指示允许建立目标业务的承载的第八指示信息。
以上分别从判断是否禁止建立目标业务的承载的执行主体的角度详细描述了本发明实施例的业务类别拥塞控制的方法，下面从终端的角度描述业务类别拥塞控制的方法。
图6示出了本发明一个实施例的业务类别拥塞控制的方法600的示意性流程图。方法600由处于连接态的终端执行，包括：
S610，发送业务承载请求信息，该业务承载请求信息包括处于连接态的终端用于请求建立目标业务的承载发起的请求所对应的信息，该业务承载请求信息中包括该目标业务所属的业务类别；
S620，接收禁止或允许该终端建立属于该业务类别的目标业务的承载的指示信息。
本发明实施例的业务类别拥塞控制的方法，通过对处于连接态的终端进行承载建立的控制，能够有效避免终端通过高优先级业务请求接入网络，随后发起低优先级业务请求，与其他处于空闲态的终端直接发起低优先级业务请求而引发的不公平性的问题，从而实现对各终端的公平的拥塞控制机制。
可选地，作为一个实施例，S610发送业务承载请求信息，包括：
该终端通过非接入层向接入层发送该业务承载请求信息；
S620接收禁止或允许该终端建立属于该业务类别的目标业务的承载的指示信息，包括：
该终端的非接入层接收该终端的接入层发送的该指示信息。
应理解，该实施例与方法200的信令流程相对应。
可选地，作为另一个实施例，S610发送业务承载请求信息，包括：
该终端通过非接入层向核心网设备发送该业务承载请求信息；
S620接收禁止或允许该终端建立属于该业务类别的目标业务的承载的指示信息，包括：
该终端通过该非接入层接收该核心网设备发送的禁止该终端建立该目标业务的承载的指示信息，或该终端通过接入层接收接入网设备发送的允许该终端建立该目标业务的承载的指示信息。
应理解，该实施例与方法300的信令流程相对应。
可选地，作为另一个实施例，S610发送业务承载请求信息，包括：
该终端通过接入层向接入网设备发送该业务承载请求信息；
S620接收禁止或允许该终端建立属于该业务类别的目标业务的承载的指示信息，包括：
该终端通过接入层接收该接入网设备发送的禁止该终端建立该目标业务的承载的指示信息。
应理解，该实施例与方法400的信令流程相对应。
可选地，作为另一个实施例，S610发送业务承载请求信息，包括：
该终端通过非接入层向核心网设备发送该业务承载请求信息；
S620接收禁止或允许该终端建立属于该业务类别的目标业务的承载的指示信息，包括：
该终端通过该非接入层接收该核心网设备发送的禁止该终端建立该目标业务的承载的指示信息。
应理解，该实施例与方法500的信令流程相对应。
下面从核心网设备的角度描述业务类别拥塞控制的方法。
图7示出了本发明一个实施例的业务类别拥塞控制的方法700的示意性流程图。方法700由核心网设备执行，包括：
S710，接收终端发送的非接入层发送的业务承载请求，该业务承载请求为处于连接态的终端用于请求建立目标业务的承载发起的请求，该业务承载请求中包括该目标业务所属的业务类别；
S720，向接入网设备发送业务承载请求信息，该业务承载请求信息用于通知该接入网设备该终端的非接入层向该核心网设备发送了业务承载请求，该业务承载请求信息中包括该目标业务所属的业务类别。
可选地，作为一个实施例，方法700还可以包括：
接收该接入网设备发送的用于指示禁止该终端建立属于该业务类别的目标业务的承载的指示信息；
通知该终端禁止建立属于该业务类别的目标业务的承载。
应理解，该实施例与方法300的信令流程相对应。
图8示出了本发明一个实施例的业务类别拥塞控制的方法800的示意性流程图。方法800由核心网设备执行，包括：
S810，当接入网设备确定允许终端建立目标业务的承载时，核心网设备接收该接入网设备发送的用于指示允许建立该目标业务的承载的指示信息。
应理解，该实施例与方法400的信令流程相对应。
下面从接入网设备的角度描述业务类别拥塞控制的方法。
图9示出了本发明一个实施例的业务类别拥塞控制的方法900的示意性流程图。方法900由接入网设备执行，包括：
S910，接入网设备向核心网设备发送业务类别禁止信息，该业务类别禁止信息中包括连接态下该目标业务所属的业务类别对应的禁止参数；
S920，当该核心网设备确定允许终端建立该目标业务的承载时，该接入网设备接收该核心网设备向发送的用于指示允许建立该目标业务的承载的指示信息。
应理解，该实施例与方法500的信令流程相对应。
应理解，在本发明的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
以详细描述了本发明实施例的业务类别拥塞控制的方法，下面描述本发明实施例的业务类别拥塞控制的设备。
图10示出了本发明一个实施例的业务类别拥塞控制的设备1000的示意性框图。该设备1000包括：
获取模块1010，用于获取业务承载请求信息，所述业务承载请求信息包括处于连接态的终端用于请求建立目标业务的承载发起的请求所对应的信息，所述业务承载请求信息中包括所述目标业务所属的业务类别；
所述获取模块1010还用于获取业务类别禁止信息，所述业务类别禁止信息中包括连接态下所述目标业务所属的业务类别对应的禁止参数；
判断模块1020，用于根据所述禁止参数，判断是否禁止所述终端建立属于所述业务类别的目标业务的承载。
本发明实施例的业务类别拥塞控制的设备，通过根据禁止参数对处于连接态的终端进行承载建立的控制，能够有效避免终端通过高优先级业务请求 接入网络，随后发起低优先级业务请求，与其他处于空闲态的终端直接发起低优先级业务请求而引发的不公平性的问题，从而实现对各终端的公平的拥塞控制机制。
可选地，作为一个实施例，所述禁止参数为禁止概率，所述获取模块1010还用于：
获取所述终端针对所述目标业务生成的随机数；
所述判断模块1020具体用于：
当所述随机数小于所述禁止概率时，禁止所述终端建立所述目标业务的承载；当所述随机数大于所述禁止概率时，允许所述终端建立所述目标业务的承载。
可选地，在本发明实施例中，所述禁止概率小于空闲态下所述目标业务所属的业务类别对应的接入禁止概率。
可选地，作为另一个实施例，所述禁止参数为禁止比特位映射，所述获取模块1010还用于：
获取所述终端的接入级别；
所述判断模块1020具体用于：
当所述终端的接入级别在所述禁止比特位映射中被置为1时，禁止所述终端建立所述目标业务的承载；当所述终端的接入级别未在所述禁止比特位映射中被置为1时，允许所述终端建立所述目标业务的承载。
在本发明实施例中，所述禁止比特位映射中置1的比特位的数目可以少于空闲态下所述目标业务所属的业务类别对应的比特位映射中置1的比特位的数目。
可选地，在本发明实施例中，所述设备1000为所述终端的接入层，
所述获取模块1010获取业务承载请求信息，包括：
接收所述终端的非接入层发送的业务承载请求信息；
所述获取模块1010获取业务类别禁止信息，包括：
接收接入网设备广播的所述业务类别禁止信息，所述业务类别禁止信息包括多个业务类别以及所述多个业务类别分别对应的禁止参数。
可选地，作为一个实施例，所述设备1000还包括：
发送模块，用于当根据所述禁止参数，确定禁止所述终端建立所述目标业务的承载时，向所述非接入层发送用于指示禁止建立所述目标业务的承载 的第一指示信息。
可选地，作为另一个实施例，所述设备1000还包括：
发送模块，用于当根据所述禁止参数，确定允许所述终端建立所述目标业务的承载时，向所述非接入层发送用于指示允许建立所述目标业务的承载的第二指示信息，并且所述接入层向所述接入网设备发起建立所述目标业务的承载的流程。
可选地，在本发明实施例中，所述设备1000为接入网设备，
所述获取模块1010获取业务承载请求信息，包括：
接收核心网设备发送的业务承载请求信息，所述业务承载请求信息用于通知所述接入网设备所述终端的非接入层向所述核心网设备发送了业务承载请求，所述业务承载请求信息中包括所述目标业务所属的业务类别；
所述获取模块1010获取业务类别禁止信息，包括：
生成所述业务类别禁止信息，所述业务类别禁止信息包括多个业务类别以及所述多个业务类别分别对应的禁止参数。
可选地，作为一个实施例，所述设备1000还包括：
发送模块，用于当根据所述禁止参数，确定禁止所述终端建立所述目标业务的承载时，向所述核心网设备发送用于指示禁止建立所述目标业务的承载的第三指示信息，以便于所述核心网设备通知所述终端的非接入层禁止建立所述目标业务的承载。
可选地，作为另一个实施例，所述设备1000还包括：
发送模块，用于当根据所述禁止参数，确定允许所述终端建立所述目标业务的承载时，向所述终端的接入层发送用于指示允许建立所述目标业务的承载的第四指示信息。
可选地，在本发明实施例中，所述设备1000为接入网设备，
所述获取模块1010获取业务承载请求信息，包括：
接收所述终端的接入层发送的业务承载请求信息；
所述获取模块1010获取业务类别禁止信息，包括：
生成所述业务类别禁止信息，所述业务类别禁止信息包括多个业务类别以及所述多个业务类别分别对应的禁止参数。
可选地，作为一个实施例，所述设备1000还包括：
发送模块，用于当根据所述禁止参数，确定禁止所述终端建立所述目标 业务的承载时，向所述终端的接入层发送用于指示禁止建立所述目标业务的承载的第五指示信息。
可选地，作为一个实施例，所述设备1000还包括：
发送模块，用于当根据所述禁止参数，确定允许所述终端建立所述目标业务的承载时，向所述核心网设备发送用于指示允许建立所述目标业务的承载的第六指示信息。
可选地，在本发明实施例中，所述设备1000为核心网设备，
所述获取模块1010获取业务承载请求信息，包括：
接收所述终端的非接入层发送的业务承载请求信息；
所述获取模块1010获取业务类别禁止信息，包括：
接收接入网设备发送的所述业务类别禁止信息，所述业务类别禁止信息包括多个业务类别以及所述多个业务类别分别对应的禁止参数。
可选地，作为一个实施例，所述设备1000还包括：
发送模块，用于当根据所述禁止参数，确定禁止所述终端建立所述目标业务的承载时，向所述终端的非接入层发送用于指示禁止建立所述目标业务的承载的第七指示信息。
可选地，作为另一个实施例，所述设备1000还包括：
发送模块，用于当根据所述禁止参数，确定允许所述终端建立所述目标业务的承载时，向所述接入网设备发送用于指示允许建立所述目标业务的承载的第八指示信息。
应注意，本发明实施例中，获取模块可以由接收器或处理器实现，发送模块可以由发送器实现，判断模块1020可以由处理器实现。如图11所示，设备1100可以包括处理器1110、接收器1120、发送器1130和存储器1140。其中，存储器1140可以用于存储处理器1110执行的代码等。
设备1100中的各个组件通过总线***1150耦合在一起，其中总线***1150除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。
图10所示的设备1000或图11所示的设备1100能够实现前述图1至图9的实施例中所实现的各个过程，为避免重复，这里不再赘述。
应注意，本发明上述方法实施例可以应用于处理器中，或者由处理器实现。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软 件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本发明实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(ProgrammableROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的***和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
图12示出了本发明一个实施例的业务类别拥塞控制的终端1200的示意性框图。该终端1200包括：
发送模块1210，用于发送业务承载请求信息，所述业务承载请求信息包括处于连接态的终端用于请求建立目标业务的承载发起的请求所对应的信息，所述业务承载请求信息中包括所述目标业务所属的业务类别；
接收模块1220，用于接收禁止或允许所述终端建立属于所述业务类别的目标业务的承载的指示信息。
可选地，作为一个实施例，所述发送模块1210具体用于：
通过非接入层向接入层发送所述业务承载请求信息；
所述接收模块1220具体用于：
非接入层接收所述终端的接入层发送的所述指示信息。
可选地，作为另一个实施例，所述发送模块1210具体用于：
通过非接入层向核心网设备发送所述业务承载请求信息；
所述接收模块1220具体用于：
通过所述非接入层接收所述核心网设备发送的禁止所述终端建立所述目标业务的承载的指示信息，或所述终端通过接入层接收接入网设备发送的允许所述终端建立所述目标业务的承载的指示信息。
可选地，作为另一个实施例，所述发送模块1210具体用于：
通过接入层向接入网设备发送所述业务承载请求信息；
所述接收模块1220具体用于：
通过接入层接收所述接入网设备发送的禁止所述终端建立所述目标业务的承载的指示信息。
可选地，作为另一个实施例，所述发送模块1210具体用于：
通过非接入层向核心网设备发送所述业务承载请求信息；
所述接收模块1220具体用于：
通过所述非接入层接收所述核心网设备发送的禁止所述终端建立所述目标业务的承载的指示信息。
应注意，本发明实施例中，发送模块1210可以由发送器实现，接收模块1220可以由接收器实现。如图13所示，终端1300可以包括处理器1310、接收器1320、发送器1330和存储器1340。其中，存储器1340可以用于存储处理器1310执行的代码等。
终端1300中的各个组件通过总线***1350耦合在一起，其中总线***1350除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。
图12所示的终端1200或图13所示的终端1300能够实现前述图1至图9的实施例中所实现的各个过程，为避免重复，这里不再赘述。
图14示出了本发明一个实施例的业务类别拥塞控制的核心网设备1400 的示意性框图。该核心网设备1400包括：
接收模块1410，用于接收终端发送的非接入层发送的业务承载请求，所述业务承载请求为处于连接态的终端用于请求建立目标业务的承载发起的请求，所述业务承载请求中包括所述目标业务所属的业务类别；
发送模块1420，用于向接入网设备发送业务承载请求信息，所述业务承载请求信息用于通知所述接入网设备所述终端的非接入层向所述核心网设备发送了业务承载请求，所述业务承载请求信息中包括所述目标业务所属的业务类别。
可选地，作为一个实施例，所述接收模块1410还用于：
接收所述接入网设备发送的用于指示禁止所述终端建立属于所述业务类别的目标业务的承载的指示信息；
所述发送模块1420还用于：
通知所述终端禁止建立属于所述业务类别的目标业务的承载。
应注意，本发明实施例中，发送模块1420可以由发送器实现，接收模块1410可以由接收器实现。如图15所示，核心网设备1500可以包括处理器1510、接收器1520、发送器1530和存储器1540。其中，存储器1540可以用于存储处理器1510执行的代码等。
核心网设备1500中的各个组件通过总线***1550耦合在一起，其中总线***1550除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。
图14所示的核心网设备1400或图15所示的核心网设备1500能够实现前述图1至图9的实施例中所实现的各个过程，为避免重复，这里不再赘述。
图16示出了本发明一个实施例的业务类别拥塞控制的核心网设备1600的示意性框图。该核心网设备1600包括：
接收模块1610，用于当接入网设备确定允许终端建立目标业务的承载时，接收所述接入网设备发送的用于指示允许建立所述目标业务的承载的指示信息。
应注意，本发明实施例中，接收模块1610可以由接收器实现。如图17所示，核心网设备1700可以包括处理器1710、接收器1720和存储器1730。其中，存储器1730可以用于存储处理器1710执行的代码等。
核心网设备1700中的各个组件通过总线***1740耦合在一起，其中总 线***1740除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。
图16所示的核心网设备1600或图17所示的核心网设备1700能够实现前述图1至图9的实施例中所实现的各个过程，为避免重复，这里不再赘述。
图18示出了本发明一个实施例的业务类别拥塞控制的接入网设备1800的示意性框图。该接入网设备1800包括：
发送模块1810，用于向核心网设备发送业务类别禁止信息，所述业务类别禁止信息中包括连接态下所述目标业务所属的业务类别对应的禁止参数；
接收模块1820，用于当所述核心网设备确定允许终端建立所述目标业务的承载时，接收所述核心网设备向发送的用于指示允许建立所述目标业务的承载的指示信息。
应注意，本发明实施例中，发送模块1810可以由发送器实现，接收模块1820可以由接收器实现。如图19所示，接入网设备1900可以包括处理器1910、接收器1920、发送器1930和存储器1940。其中，存储器1940可以用于存储处理器1910执行的代码等。
接入网设备1900中的各个组件通过总线***1950耦合在一起，其中总线***1950除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。
图18所示的接入网设备1800或图19所示的接入网设备1900能够实现前述图1至图9的实施例中所实现的各个过程，为避免重复，这里不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可 以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以权利要求的保护范围为准。

Claims (52)

  1. 一种业务类别拥塞控制的方法，其特征在于，包括：
    获取业务承载请求信息，所述业务承载请求信息包括处于连接态的终端用于请求建立目标业务的承载发起的请求所对应的信息，所述业务承载请求信息中包括所述目标业务所属的业务类别；
    获取业务类别禁止信息，所述业务类别禁止信息中包括连接态下所述目标业务所属的业务类别对应的禁止参数；
    根据所述禁止参数，判断是否禁止所述终端建立属于所述业务类别的目标业务的承载。
  2. 根据权利要求1所述的方法，其特征在于，所述禁止参数为禁止概率，所述方法还包括：
    获取所述终端针对所述目标业务生成的随机数；
    所述根据所述禁止参数，判断是否禁止所述终端建立属于所述业务类别的目标业务的承载，包括：
    当所述随机数小于所述禁止概率时，禁止所述终端建立所述目标业务的承载；当所述随机数大于所述禁止概率时，允许所述终端建立所述目标业务的承载。
  3. 根据权利要求2所述的方法，其特征在于，所述禁止概率小于空闲态下所述目标业务所属的业务类别对应的接入禁止概率。
  4. 根据权利要求1所述的方法，其特征在于，所述禁止参数为禁止比特位映射，所述方法还包括：
    获取所述终端的接入级别；
    所述根据所述禁止参数，判断是否禁止所述终端建立属于所述业务类别的目标业务的承载，包括：
    当所述终端的接入级别在所述禁止比特位映射中被置为1时，禁止所述终端建立所述目标业务的承载；当所述终端的接入级别未在所述禁止比特位映射中被置为1时，允许所述终端建立所述目标业务的承载。
  5. 根据权利要求4所述的方法，其特征在于，所述禁止比特位映射中置1的比特位的数目少于空闲态下所述目标业务所属的业务类别对应的比特位映射中置1的比特位的数目。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法由 所述终端的接入层执行，
    所述获取业务承载请求信息，包括：
    接收所述终端的非接入层发送的业务承载请求信息；
    所述获取业务类别禁止信息，包括：
    接收接入网设备广播的所述业务类别禁止信息，所述业务类别禁止信息包括多个业务类别以及所述多个业务类别分别对应的禁止参数。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    当根据所述禁止参数，确定禁止所述终端建立所述目标业务的承载时，所述接入层向所述非接入层发送用于指示禁止建立所述目标业务的承载的第一指示信息。
  8. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    当根据所述禁止参数，确定允许所述终端建立所述目标业务的承载时，所述接入层向所述非接入层发送用于指示允许建立所述目标业务的承载的第二指示信息，并且所述接入层向所述接入网设备发起建立所述目标业务的承载的流程。
  9. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法由接入网设备执行，
    所述获取业务承载请求信息，包括：
    接收核心网设备发送的业务承载请求信息，所述业务承载请求信息用于通知所述接入网设备所述终端的非接入层向所述核心网设备发送了业务承载请求，所述业务承载请求信息中包括所述目标业务所属的业务类别；
    所述获取业务类别禁止信息，包括：
    生成所述业务类别禁止信息，所述业务类别禁止信息包括多个业务类别以及所述多个业务类别分别对应的禁止参数。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    当根据所述禁止参数，确定禁止所述终端建立所述目标业务的承载时，所述接入网设备向所述核心网设备发送用于指示禁止建立所述目标业务的承载的第三指示信息，以便于所述核心网设备通知所述终端的非接入层禁止建立所述目标业务的承载。
  11. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    当根据所述禁止参数，确定允许所述终端建立所述目标业务的承载时， 所述接入网设备向所述终端的接入层发送用于指示允许建立所述目标业务的承载的第四指示信息。
  12. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法由接入网设备执行，
    所述获取业务承载请求信息，包括：
    接收所述终端的接入层发送的业务承载请求信息；
    所述获取业务类别禁止信息，包括：
    生成所述业务类别禁止信息，所述业务类别禁止信息包括多个业务类别以及所述多个业务类别分别对应的禁止参数。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    当根据所述禁止参数，确定禁止所述终端建立所述目标业务的承载时，所述接入网设备向所述终端的接入层发送用于指示禁止建立所述目标业务的承载的第五指示信息。
  14. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    当根据所述禁止参数，确定允许所述终端建立所述目标业务的承载时，所述接入网设备向所述核心网设备发送用于指示允许建立所述目标业务的承载的第六指示信息。
  15. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法由核心网设备执行，
    所述获取业务承载请求信息，包括：
    接收所述终端的非接入层发送的业务承载请求信息；
    所述获取业务类别禁止信息，包括：
    接收接入网设备发送的所述业务类别禁止信息，所述业务类别禁止信息包括多个业务类别以及所述多个业务类别分别对应的禁止参数。
  16. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    当根据所述禁止参数，确定禁止所述终端建立所述目标业务的承载时，所述核心网设备向所述终端的非接入层发送用于指示禁止建立所述目标业务的承载的第七指示信息。
  17. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    当根据所述禁止参数，确定允许所述终端建立所述目标业务的承载时，所述核心网设备向所述接入网设备发送用于指示允许建立所述目标业务的 承载的第八指示信息。
  18. 一种业务类别拥塞控制的方法，其特征在于，包括：
    发送业务承载请求信息，所述业务承载请求信息包括处于连接态的终端用于请求建立目标业务的承载发起的请求所对应的信息，所述业务承载请求信息中包括所述目标业务所属的业务类别；
    接收禁止或允许所述终端建立属于所述业务类别的目标业务的承载的指示信息。
  19. 根据权利要求18所述的方法，其特征在于，所述发送业务承载请求信息，包括：
    所述终端通过非接入层向接入层发送所述业务承载请求信息；
    所述接收禁止或允许所述终端建立属于所述业务类别的目标业务的承载的指示信息，包括：
    所述终端的非接入层接收所述终端的接入层发送的所述指示信息。
  20. 根据权利要求18所述的方法，其特征在于，所述发送业务承载请求信息，包括：
    所述终端通过非接入层向核心网设备发送所述业务承载请求信息；
    所述接收禁止或允许所述终端建立属于所述业务类别的目标业务的承载的指示信息，包括：
    所述终端通过所述非接入层接收所述核心网设备发送的禁止所述终端建立所述目标业务的承载的指示信息，或所述终端通过接入层接收接入网设备发送的允许所述终端建立所述目标业务的承载的指示信息。
  21. 根据权利要求18所述的方法，其特征在于，所述发送业务承载请求信息，包括：
    所述终端通过接入层向接入网设备发送所述业务承载请求信息；
    所述接收禁止或允许所述终端建立属于所述业务类别的目标业务的承载的指示信息，包括：
    所述终端通过接入层接收所述接入网设备发送的禁止所述终端建立所述目标业务的承载的指示信息。
  22. 根据权利要求18所述的方法，其特征在于，所述发送业务承载请求信息，包括：
    所述终端通过非接入层向核心网设备发送所述业务承载请求信息；
    所述接收禁止或允许所述终端建立属于所述业务类别的目标业务的承载的指示信息，包括：
    所述终端通过所述非接入层接收所述核心网设备发送的禁止所述终端建立所述目标业务的承载的指示信息。
  23. 一种业务类别拥塞控制的方法，其特征在于，包括：
    接收终端发送的非接入层发送的业务承载请求，所述业务承载请求为处于连接态的终端用于请求建立目标业务的承载发起的请求，所述业务承载请求中包括所述目标业务所属的业务类别；
    向接入网设备发送业务承载请求信息，所述业务承载请求信息用于通知所述接入网设备所述终端的非接入层向所述核心网设备发送了业务承载请求，所述业务承载请求信息中包括所述目标业务所属的业务类别。
  24. 根据权利要求23所述的方法，其特征在于，所述方法还包括：
    接收所述接入网设备发送的用于指示禁止所述终端建立属于所述业务类别的目标业务的承载的指示信息；
    通知所述终端禁止建立属于所述业务类别的目标业务的承载。
  25. 一种业务类别拥塞控制的方法，其特征在于，包括：
    当接入网设备确定允许终端建立目标业务的承载时，核心网设备接收所述接入网设备发送的用于指示允许建立所述目标业务的承载的指示信息。
  26. 一种业务类别拥塞控制的方法，其特征在于，包括：
    接入网设备向核心网设备发送业务类别禁止信息，所述业务类别禁止信息中包括连接态下所述目标业务所属的业务类别对应的禁止参数；
    当所述核心网设备确定允许终端建立所述目标业务的承载时，所述接入网设备接收所述核心网设备向发送的用于指示允许建立所述目标业务的承载的指示信息。
  27. 一种业务类别拥塞控制的设备，其特征在于，包括：
    获取模块，用于获取业务承载请求信息，所述业务承载请求信息包括处于连接态的终端用于请求建立目标业务的承载发起的请求所对应的信息，所述业务承载请求信息中包括所述目标业务所属的业务类别；
    所述获取模块还用于获取业务类别禁止信息，所述业务类别禁止信息中包括连接态下所述目标业务所属的业务类别对应的禁止参数；
    判断模块，用于根据所述禁止参数，判断是否禁止所述终端建立属于所 述业务类别的目标业务的承载。
  28. 根据权利要求27所述的设备，其特征在于，所述禁止参数为禁止概率，所述获取模块还用于：
    获取所述终端针对所述目标业务生成的随机数；
    所述判断模块具体用于：
    当所述随机数小于所述禁止概率时，禁止所述终端建立所述目标业务的承载；当所述随机数大于所述禁止概率时，允许所述终端建立所述目标业务的承载。
  29. 根据权利要求28所述的设备，其特征在于，所述禁止概率小于空闲态下所述目标业务所属的业务类别对应的接入禁止概率。
  30. 根据权利要求27所述的设备，其特征在于，所述禁止参数为禁止比特位映射，所述获取模块还用于：
    获取所述终端的接入级别；
    所述判断模块具体用于：
    当所述终端的接入级别在所述禁止比特位映射中被置为1时，禁止所述终端建立所述目标业务的承载；当所述终端的接入级别未在所述禁止比特位映射中被置为1时，允许所述终端建立所述目标业务的承载。
  31. 根据权利要求30所述的设备，其特征在于，所述禁止比特位映射中置1的比特位的数目少于空闲态下所述目标业务所属的业务类别对应的比特位映射中置1的比特位的数目。
  32. 根据权利要求27至31中任一项所述的设备，其特征在于，所述设备为所述终端的接入层，
    所述获取模块获取业务承载请求信息，包括：
    接收所述终端的非接入层发送的业务承载请求信息；
    所述获取模块获取业务类别禁止信息，包括：
    接收接入网设备广播的所述业务类别禁止信息，所述业务类别禁止信息包括多个业务类别以及所述多个业务类别分别对应的禁止参数。
  33. 根据权利要求32所述的设备，其特征在于，所述设备还包括：
    发送模块，用于当根据所述禁止参数，确定禁止所述终端建立所述目标业务的承载时，向所述非接入层发送用于指示禁止建立所述目标业务的承载的第一指示信息。
  34. 根据权利要求32所述的设备，其特征在于，所述设备还包括：
    发送模块，用于当根据所述禁止参数，确定允许所述终端建立所述目标业务的承载时，向所述非接入层发送用于指示允许建立所述目标业务的承载的第二指示信息，并且所述接入层向所述接入网设备发起建立所述目标业务的承载的流程。
  35. 根据权利要求27至31中任一项所述的设备，其特征在于，所述设备为接入网设备，
    所述获取模块获取业务承载请求信息，包括：
    接收核心网设备发送的业务承载请求信息，所述业务承载请求信息用于通知所述接入网设备所述终端的非接入层向所述核心网设备发送了业务承载请求，所述业务承载请求信息中包括所述目标业务所属的业务类别；
    所述获取模块获取业务类别禁止信息，包括：
    生成所述业务类别禁止信息，所述业务类别禁止信息包括多个业务类别以及所述多个业务类别分别对应的禁止参数。
  36. 根据权利要求35所述的设备，其特征在于，所述设备还包括：
    发送模块，用于当根据所述禁止参数，确定禁止所述终端建立所述目标业务的承载时，向所述核心网设备发送用于指示禁止建立所述目标业务的承载的第三指示信息，以便于所述核心网设备通知所述终端的非接入层禁止建立所述目标业务的承载。
  37. 根据权利要求35所述的设备，其特征在于，所述设备还包括：
    发送模块，用于当根据所述禁止参数，确定允许所述终端建立所述目标业务的承载时，向所述终端的接入层发送用于指示允许建立所述目标业务的承载的第四指示信息。
  38. 根据权利要求27至31中任一项所述的设备，其特征在于，所述设备为接入网设备，
    所述获取模块获取业务承载请求信息，包括：
    接收所述终端的接入层发送的业务承载请求信息；
    所述获取模块获取业务类别禁止信息，包括：
    生成所述业务类别禁止信息，所述业务类别禁止信息包括多个业务类别以及所述多个业务类别分别对应的禁止参数。
  39. 根据权利要求38所述的设备，其特征在于，所述设备还包括：
    发送模块，用于当根据所述禁止参数，确定禁止所述终端建立所述目标业务的承载时，向所述终端的接入层发送用于指示禁止建立所述目标业务的承载的第五指示信息。
  40. 根据权利要求38所述的设备，其特征在于，所述设备还包括：
    发送模块，用于当根据所述禁止参数，确定允许所述终端建立所述目标业务的承载时，向所述核心网设备发送用于指示允许建立所述目标业务的承载的第六指示信息。
  41. 根据权利要求27至31中任一项所述的设备，其特征在于，所述设备为核心网设备，
    所述获取模块获取业务承载请求信息，包括：
    接收所述终端的非接入层发送的业务承载请求信息；
    所述获取模块获取业务类别禁止信息，包括：
    接收接入网设备发送的所述业务类别禁止信息，所述业务类别禁止信息包括多个业务类别以及所述多个业务类别分别对应的禁止参数。
  42. 根据权利要求41所述的设备，其特征在于，所述设备还包括：
    发送模块，用于当根据所述禁止参数，确定禁止所述终端建立所述目标业务的承载时，向所述终端的非接入层发送用于指示禁止建立所述目标业务的承载的第七指示信息。
  43. 根据权利要求41所述的设备，其特征在于，所述设备还包括：
    发送模块，用于当根据所述禁止参数，确定允许所述终端建立所述目标业务的承载时，向所述接入网设备发送用于指示允许建立所述目标业务的承载的第八指示信息。
  44. 一种业务类别拥塞控制的终端，其特征在于，包括：
    发送模块，用于发送业务承载请求信息，所述业务承载请求信息包括处于连接态的终端用于请求建立目标业务的承载发起的请求所对应的信息，所述业务承载请求信息中包括所述目标业务所属的业务类别；
    接收模块，用于接收禁止或允许所述终端建立属于所述业务类别的目标业务的承载的指示信息。
  45. 根据权利要求44所述的终端，其特征在于，所述发送模块具体用于：
    通过非接入层向接入层发送所述业务承载请求信息；
    所述接收模块具体用于：
    非接入层接收所述终端的接入层发送的所述指示信息。
  46. 根据权利要求44所述的终端，其特征在于，所述发送模块具体用于：
    通过非接入层向核心网设备发送所述业务承载请求信息；
    所述接收模块具体用于：
    通过所述非接入层接收所述核心网设备发送的禁止所述终端建立所述目标业务的承载的指示信息，或所述终端通过接入层接收接入网设备发送的允许所述终端建立所述目标业务的承载的指示信息。
  47. 根据权利要求44所述的终端，其特征在于，所述发送模块具体用于：
    通过接入层向接入网设备发送所述业务承载请求信息；
    所述接收模块具体用于：
    通过接入层接收所述接入网设备发送的禁止所述终端建立所述目标业务的承载的指示信息。
  48. 根据权利要求44所述的终端，其特征在于，所述发送模块具体用于：
    通过非接入层向核心网设备发送所述业务承载请求信息；
    所述接收模块具体用于：
    通过所述非接入层接收所述核心网设备发送的禁止所述终端建立所述目标业务的承载的指示信息。
  49. 一种业务类别拥塞控制的核心网设备，其特征在于，包括：
    接收模块，用于接收终端发送的非接入层发送的业务承载请求，所述业务承载请求为处于连接态的终端用于请求建立目标业务的承载发起的请求，所述业务承载请求中包括所述目标业务所属的业务类别；
    发送模块，用于向接入网设备发送业务承载请求信息，所述业务承载请求信息用于通知所述接入网设备所述终端的非接入层向所述核心网设备发送了业务承载请求，所述业务承载请求信息中包括所述目标业务所属的业务类别。
  50. 根据权利要求49所述的核心网设备，其特征在于，所述接收模块还用于：
    接收所述接入网设备发送的用于指示禁止所述终端建立属于所述业务类别的目标业务的承载的指示信息；
    所述发送模块还用于：
    通知所述终端禁止建立属于所述业务类别的目标业务的承载。
  51. 一种业务类别拥塞控制的核心网设备，其特征在于，包括：
    接收模块，用于当接入网设备确定允许终端建立目标业务的承载时，接收所述接入网设备发送的用于指示允许建立所述目标业务的承载的指示信息。
  52. 一种业务类别拥塞控制的接入网设备，其特征在于，包括：
    发送模块，用于向核心网设备发送业务类别禁止信息，所述业务类别禁止信息中包括连接态下所述目标业务所属的业务类别对应的禁止参数；
    接收模块，用于当所述核心网设备确定允许终端建立所述目标业务的承载时，接收所述核心网设备向发送的用于指示允许建立所述目标业务的承载的指示信息。
PCT/CN2015/091256 2015-09-30 2015-09-30 业务承载拥塞控制的方法及设备 WO2017054183A1 (zh)

Priority Applications (20)

Application Number Priority Date Filing Date Title
SG11201801165UA SG11201801165UA (en) 2015-09-30 2015-09-30 Service bearer congestion control method and device
MX2018003712A MX2018003712A (es) 2015-09-30 2015-09-30 Metodo y aparato de control de congestion de portacion de servicio.
KR1020187004246A KR102338670B1 (ko) 2015-09-30 2015-09-30 서비스 베어링 혼잡 제어 방법 및 장치
PCT/CN2015/091256 WO2017054183A1 (zh) 2015-09-30 2015-09-30 业务承载拥塞控制的方法及设备
CN201580081247.3A CN107736055B (zh) 2015-09-30 2015-09-30 业务承载拥塞控制的方法及设备
BR112018005512-3A BR112018005512A2 (zh) 2015-09-30 2015-09-30 Traffic carrying congestion control method and equipment
EP15905095.4A EP3319371B1 (en) 2015-09-30 2015-09-30 Service bearing congestion control method and apparatus
EP21155285.6A EP3836629A1 (en) 2015-09-30 2015-09-30 Service bearer congestion control method and apparatus
US15/745,936 US11166187B2 (en) 2015-09-30 2015-09-30 Service bearer congestion control method and device
RU2018113474A RU2702267C1 (ru) 2015-09-30 2015-09-30 Способ и устройство для предотвращения перегрузки канала передачи данных услуги
CA2996178A CA2996178C (en) 2015-09-30 2015-09-30 Service bearer congestion control method and device
CN202011454615.3A CN112601253A (zh) 2015-09-30 2015-09-30 业务承载拥塞控制的方法及装置
CN202011455059.1A CN112566215A (zh) 2015-09-30 2015-09-30 业务承载拥塞控制的方法及装置
AU2015411026A AU2015411026B2 (en) 2015-09-30 2015-09-30 Service bearing congestion control method and apparatus
JP2018507583A JP2018537874A (ja) 2015-09-30 2015-09-30 サービスベアリング輻輳制御方法及び装置
IL257427A IL257427B (en) 2015-09-30 2018-02-08 A method for controlling a service subject in a load and a device
ZA2018/00911A ZA201800911B (en) 2015-09-30 2018-02-12 Service bearer congestion control method and device
PH12018500307A PH12018500307A1 (en) 2015-09-30 2018-02-12 Service bearer congestion control method and device
HK18104611.1A HK1245559A1 (zh) 2015-09-30 2018-04-09 業務承載擁塞控制的方法及設備
US17/501,762 US20220038939A1 (en) 2015-09-30 2021-10-14 Service bearer congestion control method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/091256 WO2017054183A1 (zh) 2015-09-30 2015-09-30 业务承载拥塞控制的方法及设备

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US15/745,936 A-371-Of-International US11166187B2 (en) 2015-09-30 2015-09-30 Service bearer congestion control method and device
US17/501,762 Continuation US20220038939A1 (en) 2015-09-30 2021-10-14 Service bearer congestion control method and device

Publications (1)

Publication Number Publication Date
WO2017054183A1 true WO2017054183A1 (zh) 2017-04-06

Family

ID=58422537

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/091256 WO2017054183A1 (zh) 2015-09-30 2015-09-30 业务承载拥塞控制的方法及设备

Country Status (16)

Country Link
US (2) US11166187B2 (zh)
EP (2) EP3319371B1 (zh)
JP (1) JP2018537874A (zh)
KR (1) KR102338670B1 (zh)
CN (3) CN112601253A (zh)
AU (1) AU2015411026B2 (zh)
BR (1) BR112018005512A2 (zh)
CA (1) CA2996178C (zh)
HK (1) HK1245559A1 (zh)
IL (1) IL257427B (zh)
MX (1) MX2018003712A (zh)
PH (1) PH12018500307A1 (zh)
RU (1) RU2702267C1 (zh)
SG (1) SG11201801165UA (zh)
WO (1) WO2017054183A1 (zh)
ZA (1) ZA201800911B (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018231114A1 (en) * 2017-06-16 2018-12-20 Telefonaktiebolaget Lm Ericsson (Publ) User equipment, computer program, carrier and method for controlling a data transmisson over a bearer in a wireless communications network
WO2019218126A1 (zh) * 2018-05-14 2019-11-21 Oppo广东移动通信有限公司 控制网络拥塞的方法、终端设备和网络设备
EP3624536B1 (en) * 2017-06-15 2024-06-19 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Uplink access request process according to an access category self-determined by an access stratum entity of a user equipment

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
MX2019008683A (es) * 2017-01-23 2019-09-18 Guangdong Oppo Mobile Telecommunications Corp Ltd Metodo de acceso y terminal.
KR102222830B1 (ko) * 2017-03-21 2021-03-04 삼성전자 주식회사 이동통신에서 연결 모드의 비연속 수신 모드를 지원하는 방법 및 장치
KR102176301B1 (ko) * 2018-10-31 2020-11-09 에스케이텔레콤 주식회사 호 접속 제어장치 및 호 접속 제어방법
CN114339616B (zh) * 2020-09-30 2023-03-10 维沃移动通信有限公司 广播多播业务的拥塞控制方法、装置和设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140010180A1 (en) * 2012-07-06 2014-01-09 Lg Electronics Inc. Method and apparatus for service access barring
CN104427574A (zh) * 2013-09-11 2015-03-18 华为技术有限公司 一种接入控制的方法及装置
CN104811909A (zh) * 2014-01-27 2015-07-29 中兴通讯股份有限公司 设备到设备广播信息的发送、接收方法及装置、传输***
WO2015131851A1 (en) * 2014-03-06 2015-09-11 Mediatek Inc. Smart congestion control for rrc idle mode in lte advanced systems

Family Cites Families (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100512171C (zh) 2004-03-26 2009-07-08 华为技术有限公司 一种控制接入的实现方法
US8072948B2 (en) * 2005-07-14 2011-12-06 Interdigital Technology Corporation Wireless communication system and method of implementing an evolved system attachment procedure
US8688129B2 (en) * 2007-09-17 2014-04-01 Qualcomm Incorporated Grade of service (GoS) differentiation in a wireless communication network
CN101742555A (zh) 2008-11-17 2010-06-16 华为技术有限公司 一种位置更新时拥塞控制的方法、装置及***
US9357568B2 (en) * 2009-06-16 2016-05-31 Futurewei Technologies, Inc. System and method for adapting an application source rate to a load condition
CN101932123B (zh) * 2009-06-23 2013-05-08 财团法人资讯工业策进会 中继台及其后端连线方法
CN102893668B (zh) 2010-06-07 2016-08-10 交互数字专利控股公司 用于在拥塞网络中传送服务请求消息的方法和装置
US8837443B2 (en) * 2010-08-13 2014-09-16 Sharp Kabushiki Kaisha Reducing congestion in wireless communication networks
CN102469520B (zh) 2010-11-09 2015-09-09 大唐移动通信设备有限公司 一种拥塞控制方法和设备
CN102638848B (zh) 2011-02-14 2016-05-11 中兴通讯股份有限公司 一种机器类型通信设备的拥塞控制方法及***
JP5388234B2 (ja) * 2011-02-21 2014-01-15 株式会社Ｎｔｔドコモ ネットワークアクセス規制方法及び該方法のための移動機並びに移動機に用いられるプロセッサ
CN102761933B (zh) 2011-04-29 2018-04-10 中兴通讯股份有限公司 Eab处理方法及装置、接入处理方法、装置及***
CN102170659B (zh) 2011-05-11 2015-06-17 电信科学技术研究院 一种网络拥塞控制方法和设备
CN102857969B (zh) 2011-06-28 2017-09-29 中兴通讯股份有限公司 一种拥塞控制方法及***
CN102892177B (zh) * 2011-07-20 2018-01-02 中兴通讯股份有限公司 一种终端接入控制处理方法及装置
KR101967721B1 (ko) 2011-08-10 2019-04-10 삼성전자 주식회사 무선 통신 시스템에서 확장 접속 차단 적용 방법 및 장치
CN103220750A (zh) 2012-01-19 2013-07-24 电信科学技术研究院 一种eab机制的管理方法和设备
WO2013133738A1 (en) 2012-03-06 2013-09-12 Telefonaktiebolaget Lm Ericsson (Publ) Method and network node for determining admittance based on reason for not achieving quality of service
EP2829121B1 (en) 2012-03-21 2020-12-30 Samsung Electronics Co., Ltd. Granular network access control and methods thereof
US9125137B2 (en) * 2012-07-26 2015-09-01 Lg Electronics Inc. Method and terminal for applying an extended access barring
KR20140035785A (ko) 2012-09-14 2014-03-24 삼성전자주식회사 무선 통신 시스템에서 망 혼잡상황에서 특정 서비스를 제어하는 방법 및 장치
WO2014063360A1 (zh) * 2012-10-26 2014-05-01 华为技术有限公司 业务接入的控制方法及设备
KR20150087838A (ko) * 2012-11-06 2015-07-30 엘지전자 주식회사 무선 통신 시스템에서 접근 제어 방법 및 이를 지원하는 장치
US20140269279A1 (en) * 2013-03-15 2014-09-18 Seven Networks, Inc. Triggering congestion control for radio aware applications
CN103857005A (zh) 2012-12-03 2014-06-11 电信科学技术研究院 接入控制方法和设备
US9743341B2 (en) 2013-03-29 2017-08-22 Intel IP Corporation Provisioning of application categories at a user equipment during network congestion
WO2014183254A1 (zh) 2013-05-13 2014-11-20 华为技术有限公司 一种进行接入控制的方法及设备
US9332968B2 (en) 2013-05-24 2016-05-10 Reflex Medical Corp. Saliva container with optical volume indicator
KR20200123278A (ko) * 2013-08-30 2020-10-28 인터디지탈 패튼 홀딩스, 인크 애플리케이션 특정 액세스 제어 방법
CN104769999B (zh) * 2013-10-25 2019-06-14 华为技术有限公司 拥塞控制方法、装置及***
CN111586596B (zh) * 2013-10-30 2022-11-04 交互数字专利控股公司 用于处理优先级服务拥塞的***和方法
US9723466B2 (en) * 2013-11-01 2017-08-01 Nokia Technologies Oy Enhanced control of services
CN104811900A (zh) 2014-01-24 2015-07-29 ***通信集团江西有限公司 Lbs定位***下显示移动终端历史轨迹的方法及***
US9775011B2 (en) * 2014-01-31 2017-09-26 Intel Corporation Implementations of application specific access class barring skip functionality in a wireless network
WO2015142048A1 (ko) * 2014-03-19 2015-09-24 엘지전자 주식회사 서비스 요청 절차 수행 방법 및 사용자 장치
CN105612788B (zh) * 2014-06-30 2019-05-28 Lg 电子株式会社 对每个应用限制网络接入的方法和用户设备
US10264514B2 (en) * 2014-07-28 2019-04-16 Lg Electronics Inc. Method for access control in wireless communication system and apparatus supporting same
JP6321832B2 (ja) * 2014-08-13 2018-05-09 エルジー エレクトロニクス インコーポレイティド アプリケーション別ネットワークアクセス遮断方法及びユーザ装置
CN107211345B (zh) * 2015-01-30 2020-07-24 交互数字专利控股公司 用于高优先级应用的接入控制
CN106211261B (zh) * 2015-04-10 2020-10-16 中兴通讯股份有限公司 信息处理方法及通信节点
CN108141812B (zh) * 2015-08-14 2020-12-01 瑞典爱立信有限公司 用于提供用于数据通信的应用特定拥塞控制的控制信息的***和方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140010180A1 (en) * 2012-07-06 2014-01-09 Lg Electronics Inc. Method and apparatus for service access barring
CN104427574A (zh) * 2013-09-11 2015-03-18 华为技术有限公司 一种接入控制的方法及装置
CN104811909A (zh) * 2014-01-27 2015-07-29 中兴通讯股份有限公司 设备到设备广播信息的发送、接收方法及装置、传输***
WO2015131851A1 (en) * 2014-03-06 2015-09-11 Mediatek Inc. Smart congestion control for rrc idle mode in lte advanced systems

Non-Patent Citations (1)

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

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3624536B1 (en) * 2017-06-15 2024-06-19 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Uplink access request process according to an access category self-determined by an access stratum entity of a user equipment
US12041659B2 (en) 2017-06-15 2024-07-16 Guangdong Oppo Telecommunications Corp., Ltd. Access control method and related product
WO2018231114A1 (en) * 2017-06-16 2018-12-20 Telefonaktiebolaget Lm Ericsson (Publ) User equipment, computer program, carrier and method for controlling a data transmisson over a bearer in a wireless communications network
WO2019218126A1 (zh) * 2018-05-14 2019-11-21 Oppo广东移动通信有限公司 控制网络拥塞的方法、终端设备和网络设备
US11146983B2 (en) 2018-05-14 2021-10-12 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for controlling network congestion, terminal device and network device

Also Published As

Publication number Publication date
US20180295539A1 (en) 2018-10-11
CA2996178A1 (en) 2017-04-06
KR20180059750A (ko) 2018-06-05
AU2015411026B2 (en) 2020-09-17
IL257427A (en) 2018-04-30
KR102338670B1 (ko) 2021-12-13
CN107736055B (zh) 2021-01-01
EP3836629A1 (en) 2021-06-16
CN112601253A (zh) 2021-04-02
RU2702267C1 (ru) 2019-10-07
AU2015411026A1 (en) 2018-03-08
SG11201801165UA (en) 2018-03-28
PH12018500307A1 (en) 2018-08-20
CN112566215A (zh) 2021-03-26
US11166187B2 (en) 2021-11-02
MX2018003712A (es) 2018-04-30
HK1245559A1 (zh) 2018-08-24
EP3319371B1 (en) 2021-03-24
EP3319371A1 (en) 2018-05-09
CN107736055A (zh) 2018-02-23
US20220038939A1 (en) 2022-02-03
IL257427B (en) 2021-07-29
JP2018537874A (ja) 2018-12-20
BR112018005512A2 (zh) 2018-10-09
ZA201800911B (en) 2018-12-19
EP3319371A4 (en) 2019-01-16
CA2996178C (en) 2019-12-31

Similar Documents

Publication Publication Date Title
WO2017054183A1 (zh) 业务承载拥塞控制的方法及设备
US11457331B2 (en) Positioning method and related device
WO2019140629A1 (zh) 一种接入控制的方法、设备及计算机存储介质
JP6910445B2 (ja) 通信方法、アクセスネットワークデバイス、及び端末
WO2017166221A1 (zh) 无线接入控制方法、装置及***
US20200084613A1 (en) Status switching method and apparatus
CN108293259B (zh) 一种nas消息处理、小区列表更新方法及设备
WO2022206007A1 (zh) 中继通信方法及装置、存储介质、中继设备
JP7128896B6 (ja) システム情報の取得方法、端末デバイス及びネットワークデバイス
US11588860B2 (en) Flexible selection of security features in mobile networks
WO2019148404A1 (zh) 用于寻呼的方法、终端设备和网络设备
WO2018195971A1 (zh) 获取上下文配置信息的方法、终端设备和接入网设备
CN111641482A (zh) 管理定时器、传输信息的方法、终端设备和网络设备
WO2020233496A1 (zh) 安全会话方法和装置
WO2018170892A1 (zh) 用于终端设备接入网络的方法、终端设备和网络设备
WO2018059397A1 (zh) 接入控制方法、终端设备和无线接入网设备
CN113709763A (zh) 接入控制方法及装置、存储介质、终端
JP2021073815A (ja) サービスベアリング輻輳制御方法及び装置
WO2022021004A1 (zh) 无线通信方法和设备
CN115767630A (zh) 传输链路选择方法及装置、计算机可读存储介质
CN118055457A (zh) 通信方法、计算机可读存储介质及通信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15905095

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15745936

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2015905095

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 257427

Country of ref document: IL

ENP Entry into the national phase

Ref document number: 20187004246

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 12018500307

Country of ref document: PH

WWE Wipo information: entry into national phase

Ref document number: 2018507583

Country of ref document: JP

ENP Entry into the national phase

Ref document number: 2996178

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2015411026

Country of ref document: AU

Date of ref document: 20150930

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: MX/A/2018/003712

Country of ref document: MX

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112018005512

Country of ref document: BR

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2018113474

Country of ref document: RU

ENP Entry into the national phase

Ref document number: 112018005512

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20180320