WO2019109298A1

WO2019109298A1 - Network capability configuration for rate control

Info

Publication number: WO2019109298A1
Application number: PCT/CN2017/114994
Authority: WO
Inventors: Zhiwei Qu; Jinyin Zhu; Jingrui TAO
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2017-12-07
Filing date: 2017-12-07
Publication date: 2019-06-13

Abstract

A method for communications is proposed. The method may comprise determining a first rate control parameter for a service. The method may further comprise transmitting a rate control request for the service from a server to a network exposure entity. The rate control request may comprise the first rate control parameter.

Description

NETWORK CAPABILITY CONFIGURATION FOR RATE CONTROL

FIELD OF THE INVENTION

The present disclosure generally relates to communication networks, and more specifically, to rate control in a communication network.

BACKGROUND

This section introduces aspects that may facilitate a better understanding of the disclosure. Accordingly, the statements of this section are to be read in this light and are not to be understood as admissions about what is in the prior art or what is not in the prior art.

Communication service providers and network operators have been continually facing challenges to deliver value and convenience to consumers by, for example, providing compelling network services and performance. With the rapid development of networking and radio technologies such as an Internet of things (IoT) or a cellular Internet of things (CIoT) , the optimized configuration of network capabilities may facilitate data delivery and enhance system performance. For IoT data transmission using a cellular network, a wireless device or user equipment (UE) such as a CIoT device may communicate with a server within or outside the cellular network. On the other hand, the server may support various services with different requirements for the UE. In some cases, there may occur message flooding and bandwidth overuse from CIoT devices, which may affect network performance and user experience. Thus, it may be desirable to improve rate control for different services to protect the network in a more efficient way.

SUMMARY

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

In a wireless communication network, rate control is a feature which may allow the network operator to control traffics of various services, such as the IoT traffic from a UE and/or an evolved packet core (EPC) network. For example, the serving public land mobile network (PLMN) rate control may allow the serving network to limit the traffic generated by the IoT in the serving network, while the access point name (APN) rate control may allow the operator to define the IoT traffic rate on the APN level. However, the rate control on the serving PLMN level controlled by a mobile management entity (MME) or on the APN level controlled by a packet data network gateway (PGW) may not satisfy the service requirements from a service capability server/application server (SCS/AS) .

The present disclosure proposes a mechanism to improve network capability configurations, which may enable a server such as a SCS/AS to configure the service specific rate control so that the server side may be aligned with the network side for the rate control of messages.

According to a first aspect of the present disclosure, there is provided a method implemented at a server. The method may comprise determining a first rate control parameter for a service. The method may further comprise transmitting a rate control request for the service to a network exposure entity. The rate control request may comprise the first rate control parameter.

Optionally, the method according to the first aspect of the present disclosure may further comprise receiving a response to the rate control request from the network exposure entity. The response may indicate whether the first rate control parameter is applicable to the service.

According to a second aspect of the present disclosure, there is provided an apparatus. The apparatus may comprise one or more processors and one or more memories comprising computer program codes. The one or more memories and the computer program codes may be configured to, with the one or more processors, cause the apparatus at least to perform any step of the method according to the first aspect of the present disclosure.

According to a third aspect of the present disclosure, there is provided a computer-readable medium having computer program codes embodied thereon for use with a computer. The computer program codes may comprise code for performing any step of the method according to the first aspect of the present disclosure.

According to a fourth aspect of the present disclosure, there is provided an apparatus. The apparatus may comprise a determining unit and a transmitting unit. In accordance with some exemplary embodiments, the determining unit may be operable to carry out at least the determining step of the method according to the first aspect of the present disclosure. The transmitting unit may be operable to carry out at least the transmitting step of the method according to the first aspect of the present disclosure.

In accordance with some exemplary embodiments, the response may indicate that the first rate control parameter is applicable to the service and the rate control request is acceptable.

In accordance with some exemplary embodiments, the response may indicate that the first rate control parameter is inapplicable to the service and the rate control request is rejected. Optionally, the response may comprise a cause of the rate control request being rejected.

In accordance with some exemplary embodiments, the response may indicate that the first rate control parameter is inapplicable to the service while the rate control request is acceptable with another rate control parameter applicable to the service. In accordance with some exemplary embodiments, the another rate control parameter may comprise a second rate control parameter selected by the network exposure entity or a third rate control parameter selected by a network policy entity.

According to a fifth aspect of the present disclosure, there is provided a method implemented at a network exposure entity. The method may comprise receiving a first rate control request for a service from a server. The first rate control request may comprise a first rate control parameter. The method may further comprise determining whether the first rate control parameter is applicable to the service.

Optionally, the method according to the fifth aspect of the present disclosure may further comprise transmitting a first response to the first rate control request to the server. The first response may indicate a result of the determination as to whether the first rate control parameter is applicable to the service.

According to a sixth aspect of the present disclosure, there is provided an apparatus. The apparatus may comprise one or more processors and one or more memories comprising computer program codes. The one or more memories and the computer program codes may be configured to, with the one or more processors, cause the apparatus at least to perform any step of the method according to the fifth aspect of the present disclosure.

According to a seventh aspect of the present disclosure, there is provided a computer-readable medium having computer program codes embodied thereon for use with a computer. The computer program codes may comprise code for performing any step of the method according to the fifth aspect of the present disclosure.

According to an eighth aspect of the present disclosure, there is provided an apparatus. The apparatus may comprise a receiving unit and a determining unit. In accordance with some exemplary embodiments, the receiving unit may be operable to carry out at least the receiving step of the method according to the fifth aspect of the present disclosure. The determining unit may be operable to carry out at least the determining step of the method according to the fifth aspect of the present disclosure.

In accordance with some exemplary embodiments, the determination as to whether the first rate control parameter is applicable to the service may be performed by transmitting a second rate control request to a network policy entity and receiving a second response to the second rate control request from the network policy entity. The second rate control request may comprise a candidate rate control parameter for the service. The second response may indicate whether the candidate rate control parameter is applicable to the service.

In accordance with some exemplary embodiments, the second rate control request may comprise an APN for the service.

In accordance with some exemplary embodiments where the candidate rate control parameter comprises the first rate control parameter, the second response may indicate that the candidate rate control parameter is applicable to the service.

In accordance with some exemplary embodiments, the first response may indicate that the first rate control parameter is applicable to the service and the first rate control request is acceptable.

In accordance with some exemplary embodiments where the candidate rate control parameter comprises a second rate control parameter selected by the network exposure entity for the service, the second response may indicate that the candidate rate control parameter is applicable to the service.

In accordance with some exemplary embodiments, the first response may indicate that the first rate control parameter is inapplicable to the service while the first rate control request is acceptable with a second rate control parameter selected by the network exposure entity for the service.

In accordance with some exemplary embodiments where the candidate rate control parameter comprises a second rate control parameter selected by the network exposure entity for the service or the first rate control parameter, the second response may indicate that the candidate rate control parameter is inapplicable to the service.

In accordance with some exemplary embodiments, the first response may indicate that the first rate control parameter is inapplicable to the service and the first rate control request is rejected. Optionally, the first response may comprise a cause of the first rate control request being rejected.

In accordance with some exemplary embodiments, the second response may comprise a third rate control parameter selected by the network policy entity for the service. In this case, the first response may indicate that the first rate control parameter is inapplicable to the service while the first rate control request is acceptable with the third rate control parameter.

According to a ninth aspect of the present disclosure, there is provided a method implemented at a network policy entity. The method may comprise receiving a rate control request for a service from a network exposure entity. The rate control request may comprise a candidate rate control parameter. The method may further comprise determining whether the candidate rate control parameter is applicable to the service.

Optionally, the method according to the ninth aspect of the present disclosure may further comprise transmitting a response to the rate control request to the network exposure entity. The response may indicate a result of the determination as to whether the candidate rate control parameter is applicable to the service.

Optionally, the method according to the ninth aspect of the present disclosure may further comprise transmitting another rate control request to a session management entity. The another rate control request may comprise a rate control parameter applicable to the service.

According to a tenth aspect of the present disclosure, there is provided an apparatus. The apparatus may comprise one or more processors and one or more memories comprising computer program codes. The one or more memories and the computer program codes may be configured to, with the one or more processors, cause the apparatus at least to perform any step of the method according to the ninth aspect of the present disclosure.

According to an eleventh aspect of the present disclosure, there is provided a computer-readable medium having computer program codes embodied thereon for use with a computer. The computer program codes may comprise code for performing any step of the method according to the ninth aspect of the present disclosure.

According to a twelfth aspect of the present disclosure, there is provided an apparatus. The apparatus may comprise a receiving unit and a determining unit. In accordance with some exemplary embodiments, the receiving unit may be operable to carry out at least the receiving step of the method according to the ninth aspect of the present disclosure. The determining unit may be operable to carry out at least the determining step of the method according to the ninth aspect of the present disclosure.

In accordance with some exemplary embodiments, the rate control request may comprise an APN for the service.

In accordance with some exemplary embodiments, the response may indicate that the candidate rate control parameter is applicable to the service and the rate control request is acceptable.

In accordance with some exemplary embodiments, the response may indicate that the candidate rate control parameter is inapplicable to the service and the rate control request is rejected. Optionally, the response may comprise a cause of the rate control request being rejected.

In accordance with some exemplary embodiments, the response may indicate that the candidate rate control parameter is inapplicable to the service while the rate control request is acceptable with a rate control parameter selected by the network policy entity for the service.

According to a thirteenth aspect of the present disclosure, there is provided a method implemented at a session management entity. The method may comprise receiving a rate control request for a service from a network policy entity. The method may further comprise obtaining a rate control parameter applicable to the service in the rate control request.

According to a fourteenth aspect of the present disclosure, there is provided an apparatus. The apparatus may comprise one or more processors and one or more memories comprising computer program codes. The one or more memories and the computer program codes may be configured to, with the one or more processors, cause the apparatus at least to perform any step of the method according to the thirteenth aspect of the present disclosure.

According to a fifteenth aspect of the present disclosure, there is provided a computer-readable medium having computer program codes embodied thereon for use with a computer. The computer program codes may comprise code for performing any step of the method according to the thirteenth aspect of the present disclosure.

According to a sixteenth aspect of the present disclosure, there is provided an apparatus. The apparatus may comprise a receiving unit and an obtaining unit. In accordance with some exemplary embodiments, the receiving unit may be operable to carry out at least the receiving step of the method according to the thirteenth aspect of the present disclosure. The obtaining unit may be operable to carry out at least the obtaining step of the method according to the thirteenth aspect of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure itself, the preferable mode of use and further objectives are best understood by reference to the following detailed description of the embodiments when read in conjunction with the accompanying drawings, in which:

Fig. 1 is a diagram illustrating an exemplary system architecture according to an embodiment of the present disclosure;

Fig. 2 is a flowchart illustrating a method according to some embodiments of the present disclosure;

Fig. 3 is a diagram illustrating an exemplary network capability configuration procedure according to an embodiment of the present disclosure;

Fig. 4 is a diagram illustrating an exemplary network capability configuration procedure according to another embodiment of the present disclosure;

Fig. 5 is a flowchart illustrating a method according to some embodiments of the present disclosure;

Fig. 6 is a flowchart illustrating a method according to some embodiments of the present disclosure;

Fig. 7 is a flowchart illustrating a method according to some embodiments of the present disclosure;

Fig. 8 is a block diagram illustrating an apparatus according to some embodiments of the present disclosure;

Fig. 9 is a block diagram illustrating an apparatus according to some embodiments of the present disclosure;

Fig. 10 is a block diagram illustrating an apparatus according to some embodiments of the present disclosure;

Fig. 11 is a block diagram illustrating an apparatus according to some embodiments of the present disclosure; and

Fig. 12 is a block diagram illustrating an apparatus according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

The embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed only for the purpose of enabling those skilled persons in the art to better understand and thus implement the present disclosure, rather than suggesting any limitations on the scope of the present disclosure. Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present disclosure should be or are in any single embodiment of the disclosure. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present disclosure. Furthermore, the described features, advantages, and characteristics of the disclosure may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the disclosure.

As used herein, the term “wireless communication network” may refer to a network following any suitable communication standards, such as long term evolution-advanced (LTE-A) , LTE, wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , and so on. Furthermore, the communications between a terminal device and a network node in the wireless communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the future fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.

The term “network node” may refer to a network device in a wireless communication network via which a terminal device accesses to the network and receives services therefrom. The network device may refer to a base station (BS) , an access point (AP) , a mobile management entity (MME) , a multi-cell/multicast coordination entity (MCE) , a gateway, a server, a controller or any other suitable device in the wireless communication network. The BS may be, for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNodeB or gNB) , a remote radio unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, a low power node such as a femto, a pico, and so forth.

Yet further examples of the network node may comprise multi-standard radio (MSR) radio equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs) , base transceiver stations (BTSs) , transmission points, transmission nodes, MCEs, core network nodes, positioning nodes and/or the like. More generally, however, the network node may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a terminal device access to the wireless communication network or to provide some service to a terminal device that has accessed to the wireless communication network.

The term “terminal device” may refer to any end device that can access a wireless communication network and receive services therefrom. By way of example and not limitation, the terminal device may refer to a mobile terminal, a UE, or other suitable devices. The UE may be, for example, a subscriber station, a portable subscriber station, a mobile station (MS) or an access terminal (AT) . The terminal device may include, but not limited to, portable computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, a mobile phone, a cellular phone, a smart phone, a tablet, a wearable device, a personal digital assistant (PDA) , a vehicle, and the like.

As yet another specific example, in an IoT scenario, a terminal device may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another terminal device and/or a network equipment. The terminal device may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as a machine-type communication (MTC) device.

As one particular example, the terminal device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances, e.g. refrigerators, televisions, personal wearables such as watches etc. In other scenarios, a terminal device may represent a vehicle or other equipment, for example, a medical instrument that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.

As used herein, the terms “first” , “second” and so forth may refer to different elements. The singular forms “a” and “an” are intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms “comprises” , “comprising” , “has” , “having” , “includes” and/or “including” as used herein, specify the presence of stated features, elements, and/or components and the like, but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof. The term “based on” is to be read as “based at least in part on” . The term “one embodiment” and “an embodiment” are to be read as “at least one embodiment” . The term “another embodiment” is to be read as “at least one other embodiment” . Other definitions, explicit and implicit, may be included below.

Fig. 1 is a diagram illustrating an exemplary system architecture according to an embodiment of the present disclosure. Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless communication system complied with the exemplary system architecture illustrated in Fig. 1. For simplicity, the system architecture of Fig. 1 only depicts some exemplary elements such as a UE 101, an eNB 102, a serving general packet radio service support node/mobile management entity (SGSN/MME) 103, a service capability exposure function (SCEF) 104, an AS 105, a PGW 106, and a serving gateway (SGW) 107. In practice, a wireless communication system may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or terminal device. The wireless communication system may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’access to and/or use of the services provided by, or via, the wireless communication system.

As illustrated in Fig. 1, the UE 101 may be attached to the SGSN/MME 103 via the eNB 102. The SGSN/MME 103 may handle bearer and packet data network (PDN) connection setups for the UE 101. A control plane (CP) data transfer such as data over non-access stratum (DoNAS) , and/or a user plane (UP) data transfer (for example, via a radio resource control (RRC) resume) may be used for a PDN connection, such as a “Non-IP” type of PDN connection or a “IPv4/IPv6” type of PDN connection as shown in Fig. 1.

The SGSN/MME 103 can communicate with the SCEF 104 via the T6a/T6b interface. For each PDN connection, the UE 101 may be attached to the SGW 107 and the PGW 106. The S11-U interface between the SGSN/MME 103 and the SGW 107 and the S5/S8 interface between the SGW 107 and the PGW 106 may be used for session management messages such as a create session request or a create session response. The S1-U interface may be used to establish a connection between the eNB 102 and the SGW 107. As further illustrated in Fig. 1, the SCEF 104 may be connected to the AS 105 through the hypertext transfer protocol (HTTP) restful interface, and the PGW 106 may communicate with the AS 105 through an IP or point-to-point (PtP) tunnel or other suitable tunnel.

As mentioned previously, the rate control may be used to protect the network from message flooding and bandwidth overuse from some wireless devices. In accordance with an exemplary embodiment, the serving PLMN rate control may allow the serving PLMN to protect its MME and the signaling radio bearers in the evolved-universal terrestrial radio access network (E-UTRAN) from the load generated by NAS data packet data units (PDUs) . During PDN connection establishment, the MME may inform the UE and the PGW/SCEF of any local serving PLMN rate control that the serving PLMN intends to enforce for NAS data PDUs. The MME may only indicate the serving PLMN rate control to the PGW if the PDN connection is using S11-U and set to control plane only. Alternatively, the MME may only indicate the serving PLMN rate control to the SCEF if the PDN connection is using the SCEF. This rate control may be configurable for the operator and expressed as “X NAS data PDUs per deci hour” , where X is an integer which may not be less than 10. There may be separate limit for uplink and downlink NAS data PDUs. The UE may have to limit the rate at which it generates uplink NAS data PDUs to comply with the serving PLMN policy. The serving PLMN may enforce this policy by discarding or delaying packets that exceed the limit of the serving PLMN policy. The PGW/SCEF may have to limit the rate at which it generates downlink data PDUs to avoid that the serving PLMN may discard or delay packets that exceed the limit of the serving PLMN policy.

In accordance with an exemplary embodiment, the APN rate control may allow home public land mobile network (HPLMN) operators to offer customer services such as “maximum of Y messages per day” . Existing aggregate maximum bit rate (AMBR) mechanisms are not suitable for such a service since, for radio efficiency and UE battery life reasons, an AMBR of e.g. > 100kbit/sis desirable and such an AMBR translates to a potentially large daily data volume. The PGW or the SCEF can send an APN uplink rate control command to the UE using the protocol configuration options (PCO) information element (IE) . The APN uplink rate control may be applied to data PDUs sent on that APN by either data radio bearers (S1-U) or signaling radio bearers (NAS data PDUs) . The rate control information may be separate for uplink and downlink and in the form of a positive integer number of packets per time unit. The UE may have to comply with the uplink rate control instruction. For example, the UE may consider this rate control instruction as valid until it receives a new one from the PGW or the SCEF. The PGW or the SCEF may enforce the uplink rate control by discarding or delaying packets that exceed the rate limit which is indicated to the UE.

However, the serving PLMN rate control is on the serving PLMN level controlled by the MME and the APN rate control is on the APN level controlled by the PGW. There is no way for the SCS/AS to configure the service specific rate control based on service requirements and thus no differentiated traffic management could be provided by the SCS/AS for different services.

According to some exemplary embodiments, the present disclosure provides a mechanism to enable a server to configure the rate control to a wireless communication network. In accordance with some exemplary embodiments, the server such as an IoT AS may apply different rate control for diverse services and configure the rate control to the network side. In this way, the server side can be aligned with the network side (for example, the EPC network) for the message rate control and the traffics of different services can be scheduled to a UE correspondingly.

Fig. 2 is a flowchart illustrating a method 200 according to some embodiments of the present disclosure. The method 200 illustrated in Fig. 2 may be performed by an apparatus implemented at a server or communicatively coupled to a server. In accordance with the exemplary embodiment, the server may comprise a SCS, an AS, a host computer or any other service device being capable of participating in communication of a wireless network. By applying the method 200, the server can perform a network capability configuration or reconfiguration for a rate control of a terminal device such as an IoT UE.

According to the exemplary method 200 illustrated in Fig. 2, the server (such as the AS 105) may determine a first rate control parameter for a service, as shown in block 202. The first rate control parameter may comprises a specific rate control value or an indication of a rate control value. Optionally, distinctive rate control policies and the corresponding rate control parameters may be applied to different services based at least in part on the service requirements. The server can generate service specific rate control information. In this way, rate control differentiation may be achieved for multiple services.

In accordance with an exemplary embodiment, the server may transmit a rate control request for the service to a network exposure entity (such as the SCEF 104) , as shown in block 204. The rate control request may comprise the first rate control parameter. According to an exemplary embodiment, the rate control request may comprise a system configuration request such as a T8 set suggested network configuration request or a non-IP data delivery (NIDD) configuration request. As such, the network exposure entity may be informed of any rate control rule and/or rate control parameter that the server intends to enforce for the service.

Optionally, the server may receive a response to the rate control request from the network exposure entity. The response may indicate whether the first rate control parameter is applicable to the service. According to the indication of the response, the server can know whether the rate control request is acceptable for the network exposure entity and which rate control parameter is applicable to the service in case that the rate control request is accepted by the network exposure entity.

In accordance with an exemplary embodiment, the response to the rate control request may indicate that the first rate control parameter is applicable to the service and the rate control request is acceptable. In this case, the first rate control parameter may be comprised in the response to inform the server that the requested rate control for the service may be performed with the first rate control parameter. Alternatively, the response to the rate control request may comprise an indication of the acceptance of the first rate control parameter, instead of the first rate control parameter itself.

In accordance with an exemplary embodiment, the response to the rate control request may indicate that the first rate control parameter is inapplicable to the service and the rate control request is rejected. Optionally, the response may comprise a cause of the rate control request being rejected. As an example, the rate control request may be rejected because the first rate control parameter does not meet a rate control policy of the network exposure entity and/or other entities such as a network policy entity which may participate in the rate control for the service.

Alternatively, even if the first rate control parameter is inapplicable to the service because it fails to satisfy the rate control policy of the network exposure entity and/or other network entity, the rate control request also may be accepted. In accordance with an exemplary embodiment, the response to the rate control request may indicate that the first rate control parameter is inapplicable to the service while the rate control request is acceptable with another rate control parameter applicable to the service. In this regard, the rate control for the service may be performed with the another rate control parameter indicated in the response to the rate control request.

In accordance with an exemplary embodiment, the another rate control parameter may comprise a second rate control parameter selected by the network exposure entity or a third rate control parameter selected by a network policy entity such as a PCRF. For example, the network exposure entity may select, based at least in part on its rate control policy, the second rate control parameter to replace the first rate control parameter which is determined as inapplicable to the service by the network exposure entity. Similarly, if the network policy entity considers that the first rate control parameter or the second rate control parameter is inapplicable to the service, it is also possible for the network policy entity to select, based at least in part on its rate control policy, the third rate control parameter for the rate control of the service.

Fig. 3 is a diagram illustrating an exemplary network capability configuration procedure according to an embodiment of the present disclosure. For simplicity, Fig. 3 only depicts some exemplary network elements such as a UE 301, a SGSN/MME 302, a SCEF 303 and a SCS/AS 304. It will be appreciated that signaling messages and network elements shown in Fig. 3 are just as examples, and more or less alternative signaling messages and network elements may be involved in the network capability configuration procedure.

According to the exemplary network capability configuration procedure illustrated in Fig. 3, a rate control configuration or reconfiguration may be performed for a SCEF based PDN connection. As shown in Fig. 3, the SCS/AS 304 may send 311 a T8 set suggested network configuration request message to the SCEF 303. In accordance with an exemplary embodiment, the T8 set suggested network configuration request message may comprise a rate control value determined or configured by the SCS/AS 304 for a service. It is noted that a rate control value contained in a signaling message herein is denoted as “Rate Control” in Fig. 3. Optionally, the T8 set suggested network configuration request message may further comprise one or more optional fields, such as a T8 transaction reference identifier (TTRI) , a T8 long term transaction reference identifier (TLTRI) , one or more external identifiers or mobile station integrated services digital network numbers (MSISDNs) or external group identifiers, a SCS/AS identifier, the maximum latency, the maximum response time and the suggested number of downlink packets, group reporting guard time, etc. This message can inform the SCEF 303 that the network may need to consider setting network configurations for the rate control, the maximum latency, the maximum response time and/or the suggested number of downlink packets according to the requested value (s) .

Alternatively or additionally, for a non-IP PDN which is served by the SCEF 303, a NIDD configuration procedure may be performed by the SCS/AS 304 prior to the UE 301 establishing a PDN connection. As shown in Fig. 3, the SCS/AS 304 may send 312 a NIDD configuration request message to the SCEF 303. In accordance with an exemplary embodiment, the NIDD configuration request message may comprise a rate control value determined or configured by the SCS/AS 304 for a service. Optionally, the NIDD configuration request message may further comprise one or more optional fields, such as an external identifier or a MSISDN, a SCS/AS identifier, a TTRI, a NIDD duration, a T8 destination address, a TLTRI, a requested action, a PDN connection establishment option, a reliable data service configuration, etc.

In accordance with an exemplary embodiment, the SCEF 303 may handle 313 the request message from the SCS/AS 304, for example, by checking whether the rate control value provided by the SCS/AS 304 is within a rate control range defined by operator policies for the SCEF 303. According to the operator policies, if the rate control value provided by the SCS/AS 304 is within the rate control range, then the SCEF 303 may accept the request with the rate control value from the SCS/AS 304. For example, the SCEF 303 may indicate the acceptance of the request and/or the rate control value provided by the SCS/AS 304 in the response to the SCS/AS 304. If the rate control value provided by the SCS/AS 304 is beyond the rate control range, then the SCEF 303 may reject the request by skipping operations 314-319 as shown in Fig. 3 and optionally providing a cause value indicating the rejection in a response to the SCS/AS 304.

Alternatively, even if the rate control value provided by the SCS/AS 304 is not within the rate control range, the SCEF 303 may accept the request from the SCS/AS 304 by selecting a different rate control value which is in the rate control range and proceed with the procedure as shown in Fig. 3. Optionally, the rate control value selected by the SCEF 303 may be contained in the response to the SCS/AS 304, which implies that the rate control value provided by the SCS/AS 304 is not applicable to the rate control for the service.

In the case that the IP-connectivity access network (IP-CAN) is already activated, the SCEF 303 may trigger 314 a connection management/update request to the SGSN/MME 302. In accordance with an exemplary embodiment, the connection management/update request may comprise the rate control value configured by the SCS/AS 304, or the rate control value selected or recommended by the SCEF 303. The connection management/update request may further comprise an APN for the service to which the rate control may be applied. Correspondingly, the SGSN/MME 302 may trigger 315 an IP-CAN modification procedure to update the rate control value (and optionally the APN) towards the UE 301. Then the SGSN/MME 302 may send 316 a connection management/update response to the SCEF 303.

In the case that the IP-CAN has not been activated yet and may be activated later, for example by the operation 317 as shown in Fig. 3, the SCEF 303 may receive 318 a connection management/update request from the SGSN/MME 302 and set 319 the rate control value and the APN as the updated parameters in the connection management/update response to the SGSN/MME 302. Then the SGSN/MME 302 can assign and transfer this rate control value to the UE 301.

Fig. 4 is a diagram illustrating an exemplary network capability configuration procedure according to another embodiment of the present disclosure. For simplicity, Fig. 4 only depicts some exemplary network elements such as a UE 401, a PCEF/PGW 402, a PCRF 403, a SCEF 404 and a SCS/AS 405. It will be appreciated that signaling messages and network elements shown in Fig. 4 are just as examples, and more or less alternative signaling messages and network elements may be involved in the network capability configuration procedure.

According to the exemplary network capability configuration procedure illustrated in Fig. 4, a rate control configuration or reconfiguration may be performed for a SGi based PDN connection via a PCRF. As an example, the SGi interface may connect a PGW to the operator’s IP services. As shown in Fig. 4, the SCS/AS 405 may send 411 a T8 set suggested network configuration request message to the SCEF 404. In accordance with an exemplary embodiment, the T8 set suggested network configuration request message may comprise a rate control value determined or configured by the SCS/AS 405 for a service. It is noted that a rate control value contained in a signaling message herein is denoted as “Rate Control” in Fig. 4. Optionally, the T8 set suggested network configuration request message may further comprise one or more optional fields, such as a TTRI, a TLTRI, one or more external identifiers or MSISDNs or external group identifiers, a SCS/AS identifier, group reporting guard time, etc. This message can inform the SCEF 404 that the network may need to consider setting network configurations for the rate control according to the requested value (s) .

In accordance with an exemplary embodiment, the SCEF 404 may handle 412 the T8 set suggested network configuration request message, for example, storing the received TLTRI and assigning it to an SCEF reference identifier (ID) . Based at least in part on operator policies for the SCEF 404, if the SCS/AS 405 is not authorized to perform this request (for example, if the service level agreement (SLA) does not allow for it) or the T8 set suggested network configuration request is malformed, the SCEF 404 may skip operations 413-421 as shown in Fig. 4 and provide a cause value appropriately indicating the error to the SCS/AS 405.

When handling the T8 set suggested network configuration request message, the SCEF 404 may check whether the rate control value provided by the SCS/AS 405 is within a rate control range defined by operator policies for the SCEF 404. According to the operator policies, if the rate control value provided by the SCS/AS 405 is within the rate control range, the SCEF 404 may accept the request and confirm that the rate control value provided by the SCS/AS 405 may be applicable to the rate control of the service. Otherwise, the SCEF 404 may reject the request from the SCS/AS 405 by skipping operations 413-421 as shown in Fig. 4 and optionally providing a cause value indicating the rejection in a response to the SCS/AS 405.

Alternatively, even if the rate control value in the request message is not within the rate control range acceptable for the SCEF 404, the request from the SCS/AS 405 may be accepted by the SCEF 404. For example, the SCEF 404 may select a different rate control value which is within the rate control range defined by the operator policies and proceed with the procedure as shown in Fig. 4. Optionally, the SCS/AS 405 may be informed of the different rate control value in a T8 set suggested network configuration response as shown in the operation 416 for the single UE processing or the operation 421 for the group based processing, which implies that the rate control value provided by the SCS/AS 405 is inapplicable to the rate control for the service.

For the single UE processing as illustrated in operations 413-416, the SCEF 404 may act as an application function (AF) and send 413 an authentication and authorization request (AAR) to the PCRF 403. In accordance with an exemplary embodiment, the AAR may comprise a rate control value which is within the rate control range for the SCEF 404, for example, the rate control value provided by the SCA/AS 405, or the rate control value selected by the SCEF 404 in case that the rate control value provided by the SCA/AS 405 in not within the rate control range for the SCEF 404.

The PCRF 403 can handle 414 the request message received from the SCEF 404, for example, by checking whether the rate control value in the request message is acceptable for the operator. If it is acceptable, the PCRF 403 may accept the request from the SCEF 404. Otherwise, the PCRF 403 may reject the request by skipping operations 415-421 as shown in Fig. 4 and optionally providing a cause value indicating the rejection in a response to the SCEF 404.

Alternatively, the PCRF 403 may accept the request from the SCEF 404, even if the rate control value in the request message is not acceptable for the PCRF 403. For example, the PCRF 403 may select a different rate control value which is within a rate control range defined by operator policies for the PCRF 403 and proceed with the procedure as shown in Fig. 4.

Optionally, the PCRF 403 may send 415 an authentication and authorization answer (AAA) to the SCEF 404. In accordance with an exemplary embodiment, the AAA may comprise a rate control value which is within the rate control range for the PCRF 403, for example, the rate control value received from the SCEF 404 or selected by the PCRF 403. In this way, the SCEF 404 may be informed of the rate control value applicable to the rate control for the service. Alternatively, the AAA may comprise a cause value indicating the rejection of the rate control value from the SCEF 404.

Then, the SCEF 404 may send 416 a T8 set suggested network configuration response message to the SCS/AS 405. In accordance with an exemplary embodiment, the T8 set suggested network configuration response message may comprise the rate control value which is acceptable for the PCRF 403 and the SCEF 404 and thus applicable to the rate control of the service. Optionally, the T8 set suggested network configuration response message may further comprise one or more optional fields, such as a TTRI, a TLTRI, etc. Alternatively, the T8 set suggested network configuration response message may comprise a cause value indicating the rejection of the rate control value from the SCS/AS 405.

For the group based processing as illustrated in operations 413, 414, 417, 418, 420 and 421, for each PCRF in the operator network, the SCEF 404 may send 413 a set suggested network configuration request message to the PCRF 403. In accordance with an exemplary embodiment, the set suggested network configuration request message may comprise the rate control value provided by the SCA/AS 405 or selected by the SCEF 404. According to an exemplary embodiment, the set suggested network configuration request message may comprise an APN for the service to which the rate control may be applied. The SCEF 404 can decide the APN based at least in part on an SCS/AS identifier and external group identifier information. Optionally, the set suggested network configuration request message may further comprise one or more optional fields such as an external group identifier, a SCEF ID, a SCEF reference ID, group reporting guard time, etc.

The PCRF 403 can handle 414 the received request message, for example, by checking whether the rate control value in the request message is acceptable for the operator. If it is acceptable, the PCRF 403 may accept the request from the SCEF 404. Otherwise, the PCRF 403 may reject the request by skipping operations 417-421 as shown in Fig. 4 and optionally providing a cause value indicating the rejection in a response to the SCEF 404.

Optionally, the PCRF 403 may send 417 a set suggested network configuration response message to the SCEF 404 to acknowledge acceptance of the set suggested network configuration request before beginning the processing of individual UEs, indicating that the group based processing is in progress. As an example, the set suggested network configuration response message may comprise a SCEF reference ID, a cause value, etc. Correspondingly, the SCEF 404 may send 418 a T8 set suggested network configuration response message comprising a TTRI, a TLTRI, and a cause value to the SCS/AS 405. The cause value may indicate the progress of the group based processing.

In accordance with an exemplary embodiment, the PCRF 403 may initiate 419 an IP-CAN session modification procedure to update a rate control value towards a UE. For the single UE processing, only one IP-CAN session may be impacted. For the group based processing, the PCRF 403 may find each UE which has the associated external group identifier, and then find the respective IP-CAN sessions for the UEs based at least in part on the APN provided in the operation 413.

The PCRF initiated IP-CAN session modification procedure may be triggered 419 for each impacted IP-CAN session. In accordance with an exemplary embodiment, the PCRF 403 may send a re-authentication request (RAR) message sent to the PCEF/PGW 402. Optionally, the RAR message may comprise a rate control value applicable to the rate control for the service of the UE 401. As described previously, the rate control value in the RAR message may be configured or provisioned by the SCS/AS 405, the SCEF 404 or the PCRF 403. Then the PCEF/PGW 402 may send the rate control value to the UE 401, for example, by using APN rate control parameters container in a PCO IE or an extended PCO IE carried in the IP-CAN bearer message and NAS session message.

For the group based processing, if the group reporting guard time was provided, for example, in the set suggested network configuration request, the PCRF 403 may accumulate multiple responses for the UEs of the group within the group reporting guard time. After the group reporting guard time expiration, the PCRF 403 may send 420 a set suggested network configuration response with the accumulated responses for the group members to the SCEF 404. In accordance with an exemplary embodiment, the set suggested network configuration response may comprise a SCEF reference ID, a cause value, a list of (an external identifier or MSISDN, a rate control value, a cause value) , etc. Optionally, the PCRF 403 may include an UE identity (or UE identities) and a cause value indicating the reason for the failure in the message if the configuration of a group member failed. As such, the SCEF 404 may be informed of whether the requested rate control is acceptable and which rate control value is applicable to the service.

Correspondingly, the SCEF 404 may send 421 a T8 set suggested network configuration response with the accumulated responses received from the PCRF 403 in the operation 420. As an example, the T8 set suggested network configuration response may comprise a TTRI, a TLTRI, a rate control value, a cause value, a list of (an external identifier or MSISDN, a cause value) , etc. In this way, the SCS/AS 405 may be informed of whether the requested rate control is acceptable and which rate control value is applicable to the service.

In accordance with some exemplary embodiments, an information element comprising a rate control value may be added into some signaling messages associated with the rate control configuration, such as T8 set suggested network configuration request/response and NIDD configuration request/response messages in the T8 interface between a SCS/AS and a SCEF, AAR and AAA messages in the Rx interface between a SCEF and a PCRF, and a RAR message in the Gx interface between a PCRF and a PGW. Optionally, an information element indicating a rate control value and an APN may be added into set suggested network configuration request and response messages in the Nt interface between a SCEF and a PCRF.

Fig. 5 is a flowchart illustrating a method 500 according to some embodiments of the present disclosure. The method 500 illustrated in Fig. 5 may be performed by an apparatus implemented at a network exposure entity or communicatively coupled to a network exposure entity. In accordance with the exemplary embodiment, the network exposure entity may comprise a SCEF or any other network device being capable of interacting with third-party service providers. By applying the method 500, the network exposure entity can obtain a network capability configuration for a rate control of a terminal device from a server such as a SCS/AS.

Corresponding to operations of the exemplary method 200 as illustrated in Fig. 2, the network exposure entity (such as the SCEF 104) in the exemplary method 500 as illustrated in Fig. 5 may receive a first rate control request for a service from a server, as shown in block 502. The first rate control request may comprise a first rate control parameter, for example, which may be configured or determined by the server for the service. As described in connection with Figs. 2-4, the first rate control request may comprise a system configuration request such as a T8 set suggested network configuration request or a NIDD configuration request.

In accordance with an exemplary embodiment, the network exposure entity can determine whether the first rate control parameter is applicable to the service, as shown in block 504. For example, if the first rate control parameter is within a first range defined by the rate control policy of the network exposure entity, the network exposure entity may consider that the first rate control parameter is applicable to the service. Otherwise, the network exposure entity may determine that the first rate control parameter is inapplicable to the service, and then reject the first rate control request or select a second rate control parameter for the service within the first range.

Alternatively or additionally, the network exposure entity can made the determination as to whether the first rate control parameter is applicable to the service by transmitting a second rate control request to a network policy entity such as a PCRF and receiving a second response to the second rate control request from the network policy entity. The second rate control request may comprise a candidate rate control parameter for the service, and the second response may indicate whether the candidate rate control parameter is applicable to the service. The candidate control parameter may comprise the first rate control parameter provided from the server or the second rate control parameter selected by the network exposure entity. Optionally, the second rate control request may comprise an APN for the service.

Optionally, the network policy entity may reject the second rate control request, or accept the second rate control request by selecting a third rate control parameter for the service within a second range defined by the rate control policy of the network policy entity, in case that the candidate rate control parameter from the network exposure entity is beyond the second range and thus unacceptable for the network policy entity. In general, the third rate control parameter may be acceptable for both of the network exposure entity and the network policy entity.

In accordance with an exemplary embodiment, the network exposure entity may transmit a first response to the first rate control request to the server. The first response may indicate a result of the determination as to whether the first rate control parameter is applicable to the service. For example, in the case that the first rate control parameter is acceptable for the network exposure entity (as illustrated in Fig. 3) , or that the first rate control parameter is acceptable for both of the network exposure entity and the network policy entity (as illustrated in Fig. 4) , the first response may indicate that the first rate control parameter is applicable to the service and the first rate control request is acceptable. For the case where the first rate control parameter is acceptable for both of the network exposure entity and the network policy entity, the second response from the network policy entity may indicate that the first rate control parameter is applicable to the service.

Alternatively, the first response may indicate that the first rate control parameter is inapplicable to the service while the first rate control request is acceptable with the second rate control parameter selected by the network exposure entity for the service. For example, the network exposure entity may independently configure the second rate control parameter for the service as illustrated in Fig. 3. Optionally, the network exposure entity may provide the second rate control parameter as the candidate rate control parameter for the service to the network policy entity, as illustrated in Fig. 4. Optionally, if the second response from the network policy entity indicates that the second rate control parameter is applicable to the service, the network exposure entity may signal the second rate control parameter to the server.

In accordance with an exemplary embodiment, the second response from the network policy entity may indicate that the candidate rate control parameter (for example, the first rate control parameter or the second rate control parameter) is inapplicable to the service since it is unacceptable for the network policy entity. Optionally, the second response from the network policy entity may comprise the third rate control parameter selected by the network policy entity for the service. In this case, the first response may indicate that the first rate control parameter is inapplicable to the service while the first rate control request is acceptable with the third rate control parameter.

Alternatively, the first response may indicate that the first rate control parameter is inapplicable to the service and the first rate control request is rejected. Optionally, the first response may comprise a cause of the first rate control request being rejected. For example, the first rate control request may be rejected because the first rate control parameter configured by the server is unacceptable for the network exposure entity or the network policy entity. It is also possible that the first rate control request may be rejected because the second rate control parameter configured by the network exposure entity is unacceptable for the network policy entity.

Fig. 6 is a flowchart illustrating a method 600 according to some embodiments of the present disclosure. The method 600 illustrated in Fig. 6 may be performed by an apparatus implemented at a network policy entity or communicatively coupled to a network policy entity. In accordance with the exemplary embodiment, the network policy entity may comprise a PCRF or any other network device being capable of participating in choosing and/or providing available policies and/or rules to a wireless communication network. By applying the method 600, the network policy entity can get a network capability configuration for a rate control of a terminal device from a server (such as a SCS/AS) through a network exposure entity (such as a SCEF) .

According to the exemplary method illustrated in Fig. 6, the network policy entity (such as the PCRF 403) may receive a rate control request for a service from a network exposure entity (such as the SCEF 404) , as shown in block 602. The rate control request (such as an AAR or a set suggested network configuration request) may comprise a candidate rate control parameter, for example, a rate control parameter configured by a server (such as the SCS/AS 405) or the network exposure entity (such as the SCEF 404) . Optionally, the rate control request may comprise an APN for the service.

In accordance with an exemplary embodiment, the network policy entity can determine whether the candidate rate control parameter is applicable to the service, as shown in block 604. For example, the candidate rate control parameter may be determined to be applicable to the service if it is within a rate control range defined for the network policy entity. Otherwise, the network policy entity may determine that the candidate rate control parameter is inapplicable to the service. In this case, the network policy entity may reject the rate control request from the network exposure entity, or accept the rate control request by selecting a rate control parameter for the service within the rate control range defined for the network policy entity.

In accordance with an exemplary embodiment, the network policy entity may transmit a response to the rate control request to the network exposure entity. The response may indicate a result of the determination as to whether the candidate rate control parameter is applicable to the service. According to an exemplary embodiment, the response may indicate that the candidate rate control parameter is applicable to the service and thus the rate control request is acceptable.

Alternatively, the response may indicate that the candidate rate control parameter is inapplicable to the service while the rate control request is acceptable with the rate control parameter selected by the network policy entity for the service. In another exemplary embodiment, the response may indicate that the candidate rate control parameter is inapplicable to the service and the rate control request is rejected. Optionally, the response may comprise a cause of the rate control request being rejected.

According to an exemplary embodiment where the rate control request from the network exposure entity is acceptable for the network policy entity, another rate control request may be transmitted from the network policy entity to a session management entity (such as the PCEF/PGW 402) . The another rate control request may comprise a rate control parameter applicable to the service, for example, the rate control parameter obtained by the network policy entity from the network exposure entity, or the rate control parameter selected by the network policy entity.

Fig. 7 is a flowchart illustrating a method 700 according to some embodiments of the present disclosure. The method 700 illustrated in Fig. 7 may be performed by an apparatus implemented at a session management entity or communicatively coupled to a session management entity. In accordance with the exemplary embodiment, the session management entity may comprise a PCEF, a PGW or any other network device being capable of enforcing policies and/or rules for a wireless communication network.

Corresponding to operations of the exemplary method 600 as illustrated in Fig. 6, the session management entity (such as the PCEF/PGW 402) in the exemplary method 700 as illustrated in Fig. 7 may receive a rate control request for a service from a network policy entity (such as the PCRF 403) , as shown in block 702. The rate control request may comprise a RAR from the PCRF, in which a rate control parameter configured for the service from the server side may be indicated to the PCEF/PGW.

In accordance with an exemplary embodiment, the session management entity can obtain a rate control parameter applicable to the service in the rate control request, as shown in block 704. For example, the obtained rate control parameter may be used in a PCRF initiated IP-CAN session modification procedure to update a rate control parameter towards a UE, as described in connection with Fig. 4.

The proposed solutions as illustrated with respect to Figs. 1-7 can enable the server side to configure the rate control to the network side. According to some exemplary embodiments, a server can set a rate control configuration for a SCEF based PDN connection, or for a SGi based PDN connection via a PCRF. Rate control differentiation may be achieved by applying respective rate control parameters for different services. In this way, the server side may be aligned with the network side for the message rate control. On the other hand, the traffic transmission efficiency and the user service experience also may be improved.

The various blocks shown in Figs. 2-7 may be viewed as method steps, and/or as operations that result from operation of computer program code, and/or as a plurality of coupled logic circuit elements constructed to carry out the associated function (s) . The schematic flow chart diagrams described above are generally set forth as logical flow chart diagrams. As such, the depicted order and labeled steps are indicative of specific embodiments of the presented methods. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the illustrated methods. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown.

Fig. 8 is a block diagram illustrating an apparatus 800 according to some embodiments of the present disclosure. As shown in Fig. 8, the apparatus 800 may comprise one or more processors such as processor 801 and one or more memories such as memory 802 storing computer program codes 803. In accordance with some exemplary embodiments, the one or more memories 802 and the computer program codes 803 may be configured to, with the one or more processors 801, cause the apparatus 800 at least to perform any operation of the method as described in connection with any one of Fig. 2, Fig. 5, Fig. 6 and Fig. 7.

Alternatively or additionally, the one or more memories 802 and the computer program codes 803 may be configured to, with the one or more processors 801, cause the apparatus 800 at least to perform more or less operations to implement the proposed methods according to the exemplary embodiments of the present disclosure.

Fig. 9 is a block diagram illustrating an apparatus 900 according to some embodiments of the present disclosure. As shown in Fig. 9, the apparatus 900 may comprise a determining unit 901 and a transmitting unit 902. In an exemplary embodiment, the apparatus 900 may be implemented at a server such as a SCS, an AS or the like. The determining unit 901 may be operable to carry out the operation in block 202, and the transmitting unit 902 may be operable to carry out the operation in block 204. Optionally, the determining unit 901 and/or the transmitting unit 902 may be operable to carry out more or less operations to implement the proposed methods according to the exemplary embodiments of the present disclosure.

Fig. 10 is a block diagram illustrating an apparatus 1000 according to some embodiments of the present disclosure. As shown in Fig. 10, the apparatus 1000 may comprise a receiving unit 1001 and a determining unit 1002. In an exemplary embodiment, the apparatus 1000 may be implemented at a network exposure entity such as a SCEF or the like. The receiving unit 1001 may be operable to carry out the operation in block 502, and the determining unit 1002 may be operable to carry out the operation in block 504. Optionally, the receiving unit 1001 and/or the determining unit 1002 may be operable to carry out more or less operations to implement the proposed methods according to the exemplary embodiments of the present disclosure.

Fig. 11 is a block diagram illustrating an apparatus 1100 according to some embodiments of the present disclosure. As shown in Fig. 11, the apparatus 1100 may comprise a receiving unit 1101 and a determining unit 1102. In an exemplary embodiment, the apparatus 1100 may be implemented at a network policy entity such as a PCRF or the like. The receiving unit 1101 may be operable to carry out the operation in block 602, and the determining unit 1102 may be operable to carry out the operation in block 604. Optionally, the receiving unit 1101 and/or the determining unit 1102 may be operable to carry out more or less operations to implement the proposed methods according to the exemplary embodiments of the present disclosure.

Fig. 12 is a block diagram illustrating an apparatus 1200 according to some embodiments of the present disclosure. As shown in Fig. 12, the apparatus 1200 may comprise a receiving unit 1201 and an obtaining unit 1202. In an exemplary embodiment, the apparatus 1200 may be implemented at a session management entity such as a PCEF, a PGW or the like. The receiving unit 1201 may be operable to carry out the operation in block 702, and the obtaining unit 1202 may be operable to carry out the operation in block 704. Optionally, the receiving unit 1201 and/or the obtaining unit 1202 may be operable to carry out more or less operations to implement the proposed methods according to the exemplary embodiments of the present disclosure.

In general, the various exemplary embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto. While various aspects of the exemplary embodiments of this disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

As such, it should be appreciated that at least some aspects of the exemplary embodiments of the disclosure may be practiced in various components such as integrated circuit chips and modules. It should thus be appreciated that the exemplary embodiments of this disclosure may be realized in an apparatus that is embodied as an integrated circuit, where the integrated circuit may comprise circuitry (as well as possibly firmware) for embodying at least one or more of a data processor, a digital signal processor, baseband circuitry and radio frequency circuitry that are configurable so as to operate in accordance with the exemplary embodiments of this disclosure.

It should be appreciated that at least some aspects of the exemplary embodiments of the disclosure may be embodied in computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other device. The computer executable instructions may be stored on a computer readable medium such as a hard disk, optical disk, removable storage media, solid state memory, random access memory (RAM) , etc. As will be appreciated by one of skill in the art, the function of the program modules may be combined or distributed as desired in various embodiments. In addition, the function may be embodied in whole or partly in firmware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGA) , and the like.

The present disclosure includes any novel feature or combination of features disclosed herein either explicitly or any generalization thereof. Various modifications and adaptations to the foregoing exemplary embodiments of this disclosure may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings. However, any and all modifications will still fall within the scope of the non-Limiting and exemplary embodiments of this disclosure.

Claims

A method (200) implemented at a server, comprising:

determining (202) a first rate control parameter for a service; and

transmitting (204) a rate control request for the service to a network exposure entity, wherein the rate control request comprises the first rate control parameter.
The method according to claim 1, further comprising:

receiving a response to the rate control request from the network exposure entity, wherein the response indicates whether the first rate control parameter is applicable to the service.
The method according to claim 2, wherein the response indicates that the first rate control parameter is applicable to the service and the rate control request is acceptable.
The method according to claim 2, wherein the response indicates that the first rate control parameter is inapplicable to the service and the rate control request is rejected.
The method according to claim 4, wherein the response comprises a cause of the rate control request being rejected.
The method according to claim 2, wherein the response indicates that the first rate control parameter is inapplicable to the service while the rate control request is acceptable with another rate control parameter applicable to the service.
The method according to claim 6, wherein the another rate control parameter comprises a second rate control parameter selected by the network exposure entity or a third rate control parameter selected by a network policy entity.
An apparatus (800) , comprising:

one or more processors (801) ; and

one or more memories (802) comprising computer program codes (803) ,

the one or more memories (802) and the computer program codes (803) configured to, with the one or more processors (801) , cause the apparatus (800) at least to:

determine a first rate control parameter for a service; and

transmit a rate control request for the service to a network exposure entity, wherein the rate control request comprises the first rate control parameter.
The apparatus according to claim 8, wherein the one or more memories and the computer program codes are configured to, with the one or more processors, cause the apparatus at least to perform the method according to any of claims 2-7.
A method (500) implemented at a network exposure entity, comprising:

receiving (502) a first rate control request for a service from a server, wherein the first rate control request comprises a first rate control parameter; and

determining (504) whether the first rate control parameter is applicable to the service.
The method according to claim 10, further comprising:

transmitting a first response to the first rate control request to the server, wherein the first response indicates a result of the determination.
The method according to claim 10 or 11, wherein the determination as to whether the first rate control parameter is applicable to the service is performed by:

transmitting a second rate control request to a network policy entity, wherein the second rate control request comprises a candidate rate control parameter for the service; and

receiving a second response to the second rate control request from the network policy entity, wherein the second response indicates whether the candidate rate control parameter is applicable to the service.
The method according to claim 12, wherein the second response indicates that the candidate rate control parameter is applicable to the service, and wherein the candidate rate control parameter comprises the first rate control parameter.
The method according to claim 11 or 13, wherein the first response indicates that the first rate control parameter is applicable to the service and the first rate control request is acceptable.
The method according to claim 12, wherein the second response indicates that the candidate rate control parameter is applicable to the service, and wherein the candidate rate control parameter comprises a second rate control parameter selected by the network exposure entity for the service.
The method according to claim 11 or 15, wherein the first response indicates that the first rate control parameter is inapplicable to the service while the first rate control request is acceptable with a second rate control parameter selected by the network exposure entity for the service.
The method according to claim 12, wherein the second response indicates that the candidate rate control parameter is inapplicable to the service, and wherein the candidate rate control parameter comprises a second rate control parameter selected by the network exposure entity for the service or the first rate control parameter.
The method according to claim 11 or 17, wherein the first response indicates that the first rate control parameter is inapplicable to the service and the first rate control request is rejected.
The method according to claim 18, wherein the first response comprises a cause of the first rate control request being rejected.
The method according to claim 17, wherein the second response comprises a third rate control parameter selected by the network policy entity for the service.
The method according to claim 20, wherein the first response indicates that the first rate control parameter is inapplicable to the service while the first rate control request is acceptable with the third rate control parameter.
The method according to claim 12, wherein the second rate control request comprises an access point name for the service.
An apparatus (800) , comprising:

one or more processors (801) ; and

one or more memories (802) comprising computer program codes (803) ,

the one or more memories (802) and the computer program codes (803) configured to, with the one or more processors (801) , cause the apparatus (800) at least to:

receive a first rate control request for a service from a server, wherein the first rate control request comprises a first rate control parameter; and

determine whether the first rate control parameter is applicable to the service.
The apparatus according to claim 23, wherein the one or more memories and the computer program codes are configured to, with the one or more processors, cause the apparatus at least to perform the method according to any of claims 11-22.
A method (600) implemented at a network policy entity, comprising:

receiving (602) a rate control request for a service from a network exposure entity, wherein the rate control request comprises a candidate rate control parameter; and

determining (604) whether the candidate rate control parameter is applicable to the service.
The method according to claim 25, further comprising:

transmitting a response to the rate control request to the network exposure entity, wherein the response indicates a result of the determination.
The method according to claim 26, wherein the response indicates that the candidate rate control parameter is applicable to the service and the rate control request is acceptable.
The method according to claim 26, wherein the response indicates that the candidate rate control parameter is inapplicable to the service and the rate control request is rejected.
The method according to claim 28, wherein the response comprises a cause of the rate control request being rejected.
The method according to claim 26, wherein the response indicates that the candidate rate control parameter is inapplicable to the service while the rate control request is acceptable with a rate control parameter selected by the network policy entity for the service.
The method according to claim 27 or 30, further comprising:

transmitting another rate control request to a session management entity, wherein the another rate control request comprises a rate control parameter applicable to the service.
The method according to any of claims 25-31, wherein the rate control request comprises an access point name for the service.
An apparatus (800) , comprising:

one or more processors (801) ; and

one or more memories (802) comprising computer program codes (803) ,

the one or more memories (802) and the computer program codes (803) configured to, with the one or more processors (801) , cause the apparatus (800) at least to:

receive a rate control request for a service from a network exposure entity, wherein the rate control request comprises a candidate rate control parameter; and

determine whether the candidate rate control parameter is applicable to the service.
The apparatus according to claim 33, wherein the one or more memories and the computer program codes are configured to, with the one or more processors, cause the apparatus at least to perform the method according to any of claims 26-32.
A method (700) implemented at a session management entity, comprising:

receiving (702) a rate control request for a service from a network policy entity; and

obtaining (704) a rate control parameter applicable to the service in the rate control request.
An apparatus (800) , comprising:

one or more processors (801) ; and

one or more memories (802) comprising computer program codes (803) ,

the one or more memories (802) and the computer program codes (803) configured to, with the one or more processors (801) , cause the apparatus (800) at least to:

receive a rate control request for a service from a network policy entity; and

obtain a rate control parameter applicable to the service in the rate control request.
A computer-readable medium having computer program codes (803) embodied thereon for use with a computer, wherein the computer program codes (803) comprise codes for performing the method according to any of claims 1-7, claims 10-22, claims 25-32 and claim 35.
An apparatus (900) , comprising:

a determining unit (901) configured to determine a first rate control parameter for a service; and

a transmitting unit (902) configured to transmit a rate control request for the service to a network exposure entity, wherein the rate control request comprises the first rate control parameter.
An apparatus (1000) , comprising:

a receiving unit (1001) configured to receive a first rate control request for a service from a server, wherein the first rate control request comprises a first rate control parameter; and

a determining unit (1002) configured to determine whether the first rate control parameter is applicable to the service.
An apparatus (1100) , comprising:

a receiving unit (1101) configured to receive a rate control request for a service from a network exposure entity, wherein the rate control request comprises a candidate rate control parameter; and

a determining unit (1102) configured to determine whether the candidate rate control parameter is applicable to the service.
An apparatus (1200) , comprising:

a receiving unit (1201) configured to receive a rate control request for a service from a network policy entity; and

an obtaining unit (1202) configured to obtain a rate control parameter applicable to the service in the rate control request.