WO2011106940A1

WO2011106940A1 - Network entity and method for providing a user entity-based service in a communication network

Info

Publication number: WO2011106940A1
Application number: PCT/CN2010/070894
Authority: WO
Inventors: Eric Villier; Olivier Piot
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2010-03-05
Filing date: 2010-03-05
Publication date: 2011-09-09

Abstract

The invention relates to a network entity (101) for providing a user entity-based service in a communication network. The network entity (101) comprises a provider (103) for providing a user entity indication indicating a type of a certain user entity communicating with the communication network and a controller (105) for controlling at least one management parameter adjusting said service for said certain user entity dependent on the provided user entity indication.

Description

Network entity and method for providing a user entity-based service in a communication network

BACKGROUND OF THE INVENTION

The present invention relates to mobile communications over communication networks.

Conventional radio communication systems, such as a 2^nd generation system, e.g. a Global System for Mobile Communications (GSM) or a 3^rd Generation

Partnership Project (3GPP) system, e.g. a Universal Mobile Telecommunications System (UMTS) or Long Term Evolution (LTE), provide a respective certain service, e.g. Quality of Service (QoS), to its connected mobile terminals or user entities.

For example, conventional wireless mobile networks offered and offer services, like voice services or data services, for which there was no necessity or use for differentiating the type of devices used by the end user. A reason for this is that there was not a big variety in applications run by these devices.

Moreover, in conventional communication networks, in particular in the core network, a device indication indicating a device may be used. An example is the use of the device indication to verify whether a particular device is allowed to access the network or not, i.e. typically to check whether it is a stolen device which has been barred or not.

In addition, there are other possible applications for the use of a device indication. These applications may include measuring a number of key performance indicators (KPI) for a specific type of devices. For example, an end-to-end call drop rate in a UMTS network may be measured readily by an operator using a protocol analyzer on the lu interface. Then, these measurements may be calculated for the devices of the same type, to assess the relative performance of these devices. SUMMARY OF THE INVENTION

A goal to be achieved by the present invention is to provide a user entity-based or device-based service differentiation in a communication network, in particular in a radio access network (RAN). In particular, the service, e.g. the quality of service (QoS), may be provided for a certain user entity in dependence on the type of said user entity. According to the present invention, different services may be provided for different types of user entities, the user entities differing e.g. in their capabilities, in their performances, such as radio sensitivity, in their behaviours according to certain algorithms embedded in the user entity, like power control in 3G systems, and/or in their degree of compliance with respect to certain standards. I.e., some specific types of user entities may not behave according to the expectation in some areas. Here, examples may include Compressed Mode and Wide-Band Adaptive Multi- rate (WB-AMR).

E.g., with the availability and the fast growing of mobile broadband systems, an increasing number of applications is available on a greater range of user entities or user devices. In particular, with the adoption of "always-on" experience, such user entities or devices, like smart phones, may behave quite differently compared to their previous generations. For example, if a device supplier releases a particular model of a user entity which shall be only available by a particular operator, at least for a definite introduction period, an exclusivity and promotional operation may be possible. Thus, in such cases, it may be possible that such a particular operator wants his network infrastructure to serve these particular user entities in a certain way. In this regard, the present invention gives a technical opportunity to provide such a certain way by providing a user entity-based service differentiation. The suggested user entity-based service differentiation may be done in many aspects. For example, the throughput may be increased for certain user entities by providing them more resources. Further, certain user entities may be given a higher priority in assessing the communication network so that they have the ability to pre-empt other entities. Another example may be to use different values of parameters for user entities to improve their user experience. In particular, the present user entity-based service differentiation is supported if the network entity. In this regard, the network entity, e.g. a RAN entity, may be aware of the types of the user entities being used for the communication with the communication network.

In sum, the differentiation of the service experience offered to the end user may be not dependent on his or her subscription, but on the specific type of the user entity the user is using. This information may be made available in the network entity, e.g. the RAN entity.

According to a first aspect, a network entity for providing a user entity-based service in a communication network is provided. The network entity comprises a provider for providing a user entity indication indicating a type of a certain user entity communicating with the communication network and a controller for controlling at least one management parameter adjusting said user entity-based service for said certain user entity dependent on the provided user entity indication.

The network entity may be a Radio Network Controller (RNC) or a Radio Access Network (RAN) entity. The communication network may be a mobile

communication network, in particular comprising a core network (CN).

The respective means, in particular the provider and the controller, may be implemented in hardware or in software. If said means are implemented in hardware, it may be embodied as a device, e.g. as a computer or as a processor, or as a part of a system, e.g. a computer system. If said means are implemented in software, it may be embodied as a computer program product, as a function, as a routine, as a program code or as an executable object. The respective user entity may be embodied as user device, a mobile device or mobile terminal, in particular as a smart phone. According to an implementation form, the network entity may comprise a monitor being configured to monitor messages for extracting a transferred International Mobile station Equipment Identity (IMEI). E.g., the messages may be transferred between the communication network and a certain user entity. In particular, the monitored messages may be signaling messages transferred between the communication network and the certain user entity.

The IMEI may be an identifier identifying a user entity or user device. In addition, the IMEI may be a number with 15 digits. Moreover, it may be allocated by a centralized body to equipment manufacturers. The IMEI may be structured as follows:

TAC (8-digits) + SNR (6-digits) + Spare (1 -digit) wherein TAC may designate a Type Allocation Code, e.g. allocated by a central body, SNR may designate a Serial Number, e.g. allocated by a manufacturer, and Spare may designate a key to check integrity of the TAC and the SNR.

According to an implementation form, the network entity may comprise a monitor, a monitoring unit or a monitoring device. Said monitor may be configured to decode signaling messages transferred over a communication channel, to identify an IMEI check procedure in dependence on said decoding and to extract the IMEI transferred in said identified IMEI check procedure. Said signaling messages, e.g. direct transfer messages, may be transferred between the communication network and the certain user entity. Further, the communication channel may comprise the communication network, e.g. a core network, and a number of base stations coupling user entities. Furthermore, said monitor, e.g. located in the RNC, may detect messages normally destined to the core network and may decode a particular type of such messages, but without interfering with the delivery of such message to the core network.

According to an implementation form, the network entity may comprise a

determiner, a determining unit or a determining device. Said determiner may be configured to determine the type of the certain user entity communicating with the communication network dependent on an IMEI extracted from messages, in particular signaling messages, transferred between the communication network and the certain user entity.

According to an implementation form, the network entity may comprise a monitor and a determiner. Said monitor may be configured to snoop direct transfer messages transferred between the communication network and the certain user entity. Furthermore, said monitor may be configured to identify an IMEI check procedure in dependence on said snooping and to extract the IMEI transferred in said identified IMEI check procedure. In addition, said determiner may be

configured to interrogate a local or a remote database for determining the type of the certain user entity communicating with said communication network dependent on the extracted IMEI.

For example, in UMTS, the communication network, in particular the core network, may send an IMEI check message to the user entity which may respond with some information including its IMEI and optionally its software version. Said information including the IMEI may be snooped by the monitor. As mentioned, said monitor may provide the IMEI to the determiner. Once the determiner has the IMEI, it may send a request to an Equipment Identity Register (EIR). The equipment identity register (EIR) may be a database keeping a record of stolen user entities. Moreover, the EIR may maintain different lists of IMEIs, e.g. a white list, a grey list and a black list. The black-listed user entities may be forbidden to access the communication network.

According to an implementation form, said controller may be configured to adjust at least one Quality of Service (QoS) parameter defining the provided QoS for the certain user entity, at least one channel allocation parameter for allocating channels to the certain user entity, and/or at least one radio resources

management parameter for controlling co-channel interference and/or radio transmission characteristics.

According to an implementation form, the network entity may comprise a measuring entity, measuring unit or measuring device. Said measuring entity may be adapted to measure certain key performance indicators (KPI). Moreover, said network entity may comprise a storing entity for storing the KPIs and a transfer entity for transferring the KPIs towards a certain remote server.

According to an implementation form, said controller may be configured to adjust stored KPIs to be transferred towards a certain remote server.

According to an implementation form, the network entity may comprise a transfer entity configured to transfer stored KPIs towards a certain remote server in particular periodically or on demand. The mentioned remote servers may be identical.

According to an implementation form, the communication network belongs at least to one of the communication network technologies: Universal Mobile

Telecommunication System (UMTS), Global System for Mobile Communications (GSM), Long-Term Evolution (LTE), and Code-Division Multiple Access 2000 (CDMA 2000). According to an implementation form, the controller may be configured to adjust at least one RAN-specific QoS parameter. In particular, the controller may be configured to give at least one certain user entity a higher throughput.

According to an implementation form, the controller may be configured to adjust at least one management parameter for a HSDPA scheduler of a NodeB base station in a UMTS system. In particular, the controller may be configured to alter a throughput or a delay for a certain user entity. According to an implementation form, the controller may be configured to handle network trouble-shooting in dependence on a plurality of provided user entity indications of a plurality of user entities communicating with the communication network.

According to another aspect, the invention relates to a communication system having a plurality of above mentioned network entities for providing a user entity- based service.

According to another aspect, the invention relates to a method for providing a user entity-based service in a communication network. The method comprises providing a user entity indication indicating a type of a certain user entity communication with the communication network, and controlling at least one management parameter adjusting said user entity-based service for said certain user entity dependent on the provided user entity indication.

According to another aspect, the invention relates to a computer program comprising a program code for executing the method for providing a user entity- based service in a communication network when run in a computer.

BRIEF DESCRIPTION OF THE DRAWINGS

Further embodiments of the invention will be described with respect to the following figures, in which:

Fig. 1 shows a first embodiment of a network entity for providing a user entity- based service in a communication network,

Fig. 2 shows an embodiment of a communication system having a network entity, a user entity and a communication network, Fig. 3 shows a second embodiment of a network entity for providing a user entity- based service in a communication network, and

Fig. 4 shows an embodiment of a method for providing a user entity-based service in a communication network.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

In Fig. 1 , a first embodiment of a network entity 101 for providing a user entity- based service in a communication network is shown.

The network entity 101 may have a provider 103 and a controller 105. The provider 103 may be configured to provide a user entity indication to the controller 105. The user entity indication may be adapted to indicate the type of a certain user entity communicating, in particular actually communicating, with the communication network.

The controller 105 may be adapted to control at least one management parameter adjusting said user entity-based service for said certain user entity dependent on the provided user entity indication. Thus, the provider 103 and the controller 105 provide a user entity-based service differentiation in the communication network.

Fig. 2 shows, by way of example, an embodiment of communication system 200 having a network entity 201 , a user entity 203 and a communication network 205.

The network entity 201 may be embodied as the network entity 101 of Fig. 1. Further, the network entity 201 may be embodied as a Radio Network Controller (RNC) or as a RAN entity. In addition, said communication network 205 may be embodied as a core network (CN). Said CN 205 may have a 3G Serving GPRS Support Node (3G SGSN) 207, a 3G Mobile Switching Center (MSC) 209, and a Home Location Register (HLR) 211. The 3G SGSN 207 and the network entity 201 may be coupled by an I U PS (Packet Switched) Interface 213. Moreover, said 3G MSC 209 may be coupled with said network entity 201 via an lu CS (Circuit Switched) Interface 215.

Furthermore, said network entity 201 and said user entity 203 may be coupled by a base station 217.

As shown in Fig. 2, the network entity 201 may be adapted to snoop a

communication 219 between the core network 205 and the user entity 203, said communication 219 may include an IMEI check.

Fig. 3 shows a second embodiment of network entity 301 for providing a user entity-based service in a communication network.

The network entity 301 may have a provider 303 and a controller 305.

The provider 303 may have a monitor 307 and a determiner 309.

In particular, the monitor 307 may be adapted to monitor messages for extracting a transferred IMEI. Particularly, the messages may be signaling messages being transferred between the communication network and a certain user entity.

In particular, said monitor 307 may be configured to snoop direct transfer messages. Moreover, said monitor 307 may be adapted to identify an IMEI check procedure based upon the snooped direct transfer messages and to further extract the IMEI transferred in said identified IMEI check procedure.

Furthermore, said determiner 309 of said provider 303 may be adapted to determine the type of the certain user entity communicating with the

communication network. This determining may be done dependent on the IMEI extracted from the snooped direct transfer messages. Further, said determiner 309 may be configured to interrogate a local database 311 for determining the type of the certain user entity. As an alternative, the determiner 309 may interrogate a remote database, not depicted in Fig. 3. Dependent on the provided type of the certain user entity, the controller 305 of the network entity 301 may be adapted to adjust at least one quality of service (QoS) parameter, said QoS parameter defining the provided QoS for a certain user entity Moreover, said controller 309 may adjust at least one channel allocation

parameter, said channel allocation parameter adapted to allocate channels to the certain user entity communicating with the communication network. Moreover, said controller 305 may be adapted to adjust at least one radio resources management parameter for controlling co-channel interference and/or radio transmission characteristics. With respect to Fig. 3, said controller 305 may comprise a measuring entity 313, a storing entity 315 and a transfer entity 317.

Said measuring entity 313 may be adapted to measure certain key performance indicators (KPI). In addition, said storing entity 315 may be adapted to store the measured KPIs. Furthermore, said transfer entity 317 may transfer the stored KPIs towards a certain remote server 319.

In this regard, the controller 305 may be configured to adjust the stored KPIs to be transferred towards the remote server 319. In addition, said transfer entity 318 may transfer the stored KPIs towards the remote server 319 periodically or on demand.

In Fig. 4, an embodiment of the method for providing a user entity-based service in a communication network is depicted.

As shown in Fig. 4, the method comprises a step of providing 401 a user entity indication. Said user entity indication is eligible to indicate a type of a certain user entity communicating with the communication network. Said user entity indication may be bijective.

Further, the method comprises a step of controlling 402 at least one management parameter adjusting said user entity-based service for said certain user entity dependent on the provided user entity indication.

According to some implementations, a user entity-based service in a

communication network, e.g. in GSM, in UMTS or in LTE technologies, is enabled.

According to some implementations, the present network entity may adjust at least one RAN-specific QoS parameter. In particular, such an adjusting may enable at least one certain user entity to communicate with a higher throughput. Further, according to some implementations, at least one management parameter for a HSDPA scheduler of a NodeB base station in a UMTS system may be adjusted, in particular to alter a throughput or a delay for certain user entities.

According to some implementations, the network entity, in particular the controller of the network entity, may handle network trouble-shooting in dependence on a plurality of provided user entity indications of a plurality of user entities

communicating with the communication network.

Claims

CLAIMS:

1. Network entity (101 , 201 , 301 ) for providing a user entity-based service in a communication network (205), the network entity (101 , 201 , 301) comprising: a provider (103, 303) for providing a user entity indication indicating a type of a certain user entity (203) communicating with the communication network (205), and a controller (105, 305) for controlling at least one management parameter adjusting said user entity-based service for said certain user entity (203) dependent on the provided user entity indication.

2. Network entity of claim 1 , comprising a monitor (307) being configured to monitor messages for extracting a transferred International Mobile station

Equipment Identity (IMEI), the messages, in particular signaling messages, being transferred between the communication network (205) and a certain user entity (203).

3. Network entity of one of the preceding claims, comprising a monitor (307) being configured to snoop direct transfer messages, to identify an IMEI check procedure in dependence on said snooping and to extract the IMEI transferred in said identified IMEI check procedure, the messages, in particular signaling messages, being transferred between the communication network (205) and a certain user entity (203).

4. Network entity of one of the preceding claims, comprising a determiner (309) being configured to determine the type of the certain user entity (203)

communicating with the communication network (205) dependent on an IMEI extracted from messages, in particular signaling messages, transferred between the communication network (205) and the certain user entity (203).

5. Network entity of one of the preceding claims, comprising a monitor (307) and a determiner (309), said monitor (307) being configured to snoop direct transfer messages transferred between the communication network (205) and the certain user entity (203), to identify an IMEI check procedure in dependence on said snooping, said monitor (307) being further configured to extract the IMEI transferred in said identified IMEI check procedure, and said determiner (309) being configured to interrogate a local or a remote database (311 ) for determining the type of the certain user entity (203) communicating with said communication network (205) dependent on the extracted IMEI.

6. Network entity of one of the preceding claims, wherein said controller (105, 305) is configured to adjust at least one Quality of Service (QoS) parameter defining the provided QoS for the certain user entity (203), to adjust at least one channel allocation parameter for allocating channels to the certain user entity (203), or to adjust at least one radio resources management parameter for controlling co-channel interference or radio transmission characteristics.

7. Network entity of one of the preceding claims, comprising a measuring entity (313) for measuring certain key performance indicators (KPI), a storing entity (315) for storing the KPIs and a transfer entity (317) for transferring the KPIs towards a certain remote server (319).

8. Network entity of one of the preceding claims, wherein the controller (105, 305) is configured to adjust stored KPIs to be transferred towards a certain remote server (319).

9. Network entity of one of the preceding claims, comprising a transfer entity (317) configured to transfer stored KPIs towards a certain remote server (319) in particular periodically or on demand.

10. Network entity of one of the preceding claims, wherein the communication network (205) belongs at least to one of the communication network technologies:

Universal Mobile Telecommunication System (UMTS),

Global System for Mobile Communications (GSM), Long-Term Evolution (LTE), and

Code-Division Multiple Access 2000 (CDMA 2000).

11. Network entity of one of the preceding claims, wherein the controller (105, 305) is configured to adjust at least one RAN-specific QoS parameter, in particular to enable at least one certain user entity (203) to communicate with a higher throughput.

12. Network entity of one of the preceding claims, wherein the controller (105, 305) is configured to adjust at least one management parameter for a HSDPA scheduler of a NodeB base station in a UMTS system, in particular to alter a throughput or a delay for a certain user entity (203).

13. Network entity of one of the preceding claims, wherein the controller (105, 305) is configured to handle network trouble-shooting in dependence on a plurality of provided user entity indications of a plurality of user entities (203) communicating with the communication network (205).

14. Method for providing a user entity-based service in a communication network (205), the method comprising: providing (401 ) a user entity indication indicating a type of a certain user entity (203) communication with the communication network (205), and controlling (402) at least one management parameter adjusting said user entity- based service for said certain user entity (203) dependent on the provided user entity indication.

15. Computer program comprising a program code for executing the method of claim 14 when run on a computer.