Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/70—Admission control; Resource allocation
  • H04L47/82—Miscellaneous aspects
  • H04L47/824—Applicable to portable or mobile terminals
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/70—Admission control; Resource allocation
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/70—Admission control; Resource allocation
  • H04L47/74—Admission control; Resource allocation measures in reaction to resource unavailability
  • H04L47/745—Reaction in network
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/70—Admission control; Resource allocation
  • H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
  • H04L47/762—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the network
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/70—Admission control; Resource allocation
  • H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
  • H04L47/765—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the end-points
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/70—Admission control; Resource allocation
  • H04L47/78—Architectures of resource allocation
  • H04L47/781—Centralised allocation of resources
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/70—Admission control; Resource allocation
  • H04L47/80—Actions related to the user profile or the type of traffic
  • H04L47/805—QOS or priority aware
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W28/00—Network traffic management; Network resource management
  • H04W28/02—Traffic management, e.g. flow control or congestion control
  • H04W28/10—Flow control between communication endpoints
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W28/00—Network traffic management; Network resource management
  • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
  • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W92/00—Interfaces specially adapted for wireless communication networks
  • H04W92/04—Interfaces between hierarchically different network devices
  • H04W92/14—Interfaces between hierarchically different network devices between access point controllers and backbone network device

Definitions

• the invention relates to a method for ensuring quality of service in packet-switched mobile radio networks, and in particular includes an alternative method to the quality of service concept used in today's second and third generation (GSM / UMTS) mobile digital networks.
• GSM second and third generation
• a user equipment is located in a radio cell of a packet-switched mobile radio network and is - after successful registration in the network - reachable for data to be transmitted.
• a packet-oriented connection to a data transmission device located in the core network ("CN") of the mobile radio network.
• the UE signals a request for establishing a connection to the network and also provides the data for the network connection
• CN core network
• the UE signals a request for establishing a connection to the network and also provides the data for the network connection
• These are: - explicitly a quality of service profile, which describes in the form of a parameter set, the technical characteristics of the packet flow (eg data throughput, delay in the transmission, prioritization) on the connection, or - implicitly to the specification of a in the network (eg per subscriber profile) stored basic profile, which is also in the form of the above parameter set.
• connection establishment request is forwarded via the radio access network ("RAN") to the core network CN, where first a check is made with regard to the admissibility of the requested quality of service or the selection of the basic profile with the aid of parameters of the subscriber profile of Subscriber profile, if necessary adjusted quality of service to the
• RAN radio access network
• Data transmission device was forwarded, there is a renewed review and possibly reduction of the quality of service, with internal criteria and optionally also additional external criteria, the further signaling of the data transmission device with external decision or
• Service nodes are taken into account. If the quality of service is finally determined, an acknowledgment of the connection establishment request is sent back to the requesting UE via the participating nodes of the core and radio network. Further signaling takes place in the RAN in order to set up the required radio channel to the UE. In this case, a further reduction of the quality of service by the RAN (for example due to lack of resources) is possible so that renewed signaling via it to the data transmission device takes place. Finally, if the connection establishment is accepted by all participating nodes, data transmission to and from the UE can be started, whereby both sequentially and simultaneously several and different services can be handled via this connection. All nodes involved in the data transfer must handle the data stream according to the quality of service profile specified by the technical transfer parameters.
• UMTS 3G radio network
• SGSN Server GPRS Support Node
• GGSN Gateway GPRS Support Node
• RNC Radio Network Controller
• NodeB base station
• Nodes are not meaningful or meaningless.
• the signaling between the affected nodes is very complex, partly because of the facts described in point c).
• e) Although the UE is registered in the network, additional data must still be signaled to start the data communication.
• f) Usually, the components of the CN shown in FIG. 1 are interconnected with a transport network (backbone) based on the Intern et protocol (IP). However, a comparison of the quality of service of the bearer set up in the mobile network with the transport network nodes is not possible.
• a subsequent change in the quality of service of an existing connection - for example, in the use of other applications / services by the UE - in principle requires the same signaling as described above.
• h) To differentiate the quality of service for parallel use with regard to the quality of service of services to be differentiated, the establishment of further connections is necessary (see also point a). The necessary Signaling is similar in process and effort to that shown above.
• the proposal eliminates procedural defects in today's concept, which make it difficult or prevent reaching the quality of service required for the offered telecommunications services. Due to the simplifications included in the proposal, the amount of processing steps and resources needed to ensure quality of service is much smaller. Furthermore, by minimizing the required signaling, a faster connection establishment and a higher efficiency in the network is achieved.
• FIG. 1 shows the sequence for a connection setup according to the prior art.
• Figure 2 shows the procedure for a connection establishment according to the invention.
• the initial state is initially identical to that of the known solution.
• a user equipment (UE) is located in a cell and - after successful registration in the network - can be reached for data to be transmitted.
• a connection to the data transmission is established, including the quality of service to be used. This can be done using the method described here or else in the context of other (previously occurring) signaling between the UE and the network, whereby a separate signaling (see point e) in the disadvantages of today practiced solution) for the connection setup is omitted.
• the connection can be established during the registration of the UE on the network, or during the configuration of the UE for the IP protocol. At most, the scope of service quality signaling is substantially reduced by the method described herein.
• a connection can be divided into a radio connection and a core network connection.
• the radio connection is managed by the RAN and is characterized by the following parameters:
• Radio Flow Identifier RFI
• TCL Transport Class Label
• RAN controls the radio connection for the provision of the quality of service.
• CFI 7 a transport class identifier TCL, a kernel-specific description of the parameters of the core network connection given by the TCL value, by means of which the CN controls the core network connection with regard to the provision of the quality of service.
• the respective radio- or core-network-specific parameters can be derived indirectly from the TCL, or can be explicitly or partially explicitly specified in the TCL.
• the derivation is based on configurable node-specific rules.
• An essential feature of the method is that RAN and CN can independently and without corresponding signaling change specific parameters of the RAN / CN connection managed by them, as long as this is permitted within the limits of the given TCL and the associated derivation rules ,
• Each connection is further characterized by a packet filter which determines the properties of the IP control information (IP header) for the connection so that only packets corresponding to that packet filter are passed on to the UE on that connection.
• IP header IP control information
• the rule "all packets for this UE" may apply to a connection
• the setup / changes of this packet filter for new / ongoing connections may be agreed between UE and CN or otherwise determined by the CN eg based on the participant profile. However, the required procedures are not part of this quality of service procedure.
• Packets that are downlinked over this connection (after being assigned to the connection by the CN using the Packet Filter) are tagged with the CFI and TCL valid for the connection
• the CFI is used by the RAN to forward the packet via the appropriately established RAN connection, ie the RAN maps the CFI to the RFI
• the TCL indicates that the packet with the quality of service set up for the connection should be forwarded via the air interface, the transmission of the TCL itself is not required over the air interface.
• Packets transmitted over the connection from the UE (uplink) (after being assigned to the connection by the UE using internal means) are identified by the UE with the RFI assigned to this connection Packet via the appropriately established CN connection, ie the RAN maps the RFI to the CFI, and adds the TCL valid for this connection, indicating that the packet with the quality of service established for the connection should be routed through the core network ,
• a variant of the o.g. Method is the intermittent or complete omission of the TCL, since this has not changed with the same quality of service over the previous packages.
• Packets sent / received over this connection to and from the UE may be encrypted beforehand on the RAN or CN connection or continuously from the CN to the UE. Encryption from the UE to external destination is also possible. Furthermore, optimizations of the transport volume, such as IP Header Compression, are possible.
• FIG. 2 schematically shows the above-described sequence of data transmission over the existing connection.
• the agreed quality of service is not adequate (too high / too low) for the service / purpose being handled by the connection or that previously assigned / requested resources are no longer available.
• the change of the quality of service of the connection is then initiated by the node (UE, RAN, CN) which has the above-mentioned. Reason for the change.
• the UE determines that it no longer needs the previously agreed quality of service or that a service with higher quality of service should expire. Accordingly, it requests a corresponding reduction or increase in the quality of service.
• the procedure is as follows.
• UE requests from the RAN a change in the radio connection specific parameters of the connection in such a way that this is incompatible with the existing TCL. In order to transmit this requirement, the prior establishment of a radio signaling connection may be required.
• RAN determines the TCL matching the change in the radio link.
• RAN sends the (uplink) packets of this connection, marked with the new TCL, to the CN. Unless the omission of the TCL, as under A) is used, at least one packet must be sent with the changed TCL. To ensure that the new TCL is received at the CN, several packets can be applied one after the other or at intervals with the new TCL. If there are no user data at this time, you can alternatively send empty packets marked with the new TCL on the connection. 4. In the CN, the core network specifics required for the new TCL are
• Connection parameter determined. 5 The availability of the required resources will be checked: a) if the result of the o.g. Check is assigned to the new TCL of the connection (identified by the CFI); b) otherwise the quality of service is reduced on the basis of the resources actually available and a TCL corresponding to that quality of service is assigned to the connection (this may be the "old" TCL!).
• This check can be omitted if the quality of service is to be lowered.
• the permissibility of the new TCL for the connection to the UE may be based on other information, e.g. the participant profile. For this purpose, if necessary, external decision or
• This step can be omitted if the quality of service is to be lowered.
• the CN now acts on the downlink packets of this connection with the TCL determined above. If the TCL omission technique described in A) is used, at least one packet containing the modified TCL should be sent. To ensure that the new TCL is received at the RAN, several packets can be applied to the new TCL in succession or at intervals. If there are no user data at this time, you can alternatively send empty packets marked with the new TCL on the connection. 8.
• the parameters of the radio connection are adjusted as necessary or not yet done according to the actual TCL 1 specified in step 7: a) if RAN and UE have not yet changed the radio connection (see step 1), this now becomes appropriate the actual TCL performed, b) changes already made to the radio connection, if necessary, adjusted according to the actual TCL.
• This change occurs, for example, when in RAN insufficient
• the RAN causes a reduction or increase in the quality of service.
• the procedure is identical to that described under B1 except for the exception that the change in the radio link in step 1 does not originate from the UE as in B1 but from the RAN.
• This change takes place, for example, if the CN no longer has sufficient resources available to maintain the agreed quality of connection service, or if resources withdrawn after previous use become available again. It can also be caused by the fact that CN determines that the previously agreed quality of service is no longer needed, or that a service with higher quality of service is expected to expire. It is also possible to change the existing connection by communicating with the CN with external decision or service nodes.
• the CN causes a reduction or increase in the quality of service.
• the process is basically identical to that described under B1 except for the fact that the individual steps proceed in a correspondingly reverse order, starting from the CN. Accordingly, it is possible that the requested resources are not available in the RAN - in that regard, the RAN may return a TCL in the uplink other than the TC specified by the CN.
• a UE or UPE determines the need to establish a (new) connection with a given quality of service. This can be done at the first connection e.g. in the course of registering on the network or other signaling, as shown at the beginning - ie with a procedure independent of our proposal.
• the UE may separately initiate the establishment of a connection to allow communication at all.
• the UE then has the necessary authentication,
• the procedure for establishing a connection is then as follows. 1.
• the UE requests from the RAN, in accordance with the behavior described under B1, point 1, resources for a radio network connection.
• point 1 resources for a radio network connection.
• the prior establishment of a radio signaling connection may be required.
• UE and RAN agree on the radio connection specific parameters of the connection in accordance with RAN established guidelines for establishing new connections.
• RAN determines the appropriate TCL for this radio connection and sets an RFI for the connection.
• RAN sends one or more uplink packet (s) to the CN, marked with the new TCL and a) a special CFI that the CN interprets as a request for a new connection, b) the UE identification parameters assigned at registration to the extent required.
• a) and b) can also be combined, e.g. if, as already described initially, the CFI is made unique by the UE identity. In this case, this already sets a valid CFI for the connection.
• the CN generates the CFI to use for the new connection, or uses the already unique CFI and sets the actual TCL as described under B. In doing so, it may lower the RL requested TCL (for example, due to resource bottlenecks, local policies, or subscriber profile restrictions).
• the CN sends one or more downlink packets with the specified TCL, the CFI valid for the connection and, if separately required, the UE identification parameters to the RAN.
• the packet filter valid for this first connection can be implicitly set up as "all packets.” If another packet filter is desired - so that only specific packets corresponding to that packet filter are sent over this connection - it is set up as described in step C2, step 6.
• the UE requests resources for the new radio link from the RAN via the known route, determining the radio link parameters, the corresponding TCL and a new RFI.
• the RAN adds the desired TCL and the CFI specified in C1, step 3 into one or more Packages. If there are no user data for the connection at this time, it is alternatively possible to send empty packets marked with the new TCL on the connection.
• the UE can use the same IP address as on another connection or also another address.
• the mechanism used to set the address to use is not part of this Quality of Service procedure.
• the quality of service of the new connection can be changed at any time using the procedures described under B.
• a change could also be caused by the fact that the connection is not used according to the agreed quality of service or that after a certain time still no packet filter has been set up.
• the CN may initiate this procedure, eg if the IP address of the UE has been established or if a packet destined to the IP address of the UE arrives and has not yet been connected.
• the procedure for this is analogous to C1 in accordance with the reverse order.
• the CN may also initiate the establishment of a new connection as described herein when a packet arrives for a UE for which the existing connections to that UE do not have a matching packet filter. Alternatively, it is also possible to change the packet filter of an existing connection to this UE. In contrast to the connection setup, the negotiation of the packet filter between CN and UE is not part of the quality of service method presented here.
• the CN can initiate this procedure, e.g. when packets arrive for a UE and there is no good quality connection to the UE. Instead of modifying an existing connection, it may make sense to set up a new connection here, especially if the packets to be transmitted via it are meaningfully separable from the other packets by means of a packet filter. Also, a cause for establishing the new connection is possible by communication of the CN with external decision or service nodes.
• the radio link is cleared by signaling between the RAN and the UE; the depletion of the core network connection is done by the mechanism described in B, setting the TCL to a special value that RAN and CN interpret as "end of connection".
• RAN and CN then disable all resources and settings assigned to the connection. Possibly. must be previously signaling between UE and CN, e.g. for logging out / resetting the packet filter valid for the connection.
• the radio access network RAN and the core network CN use the in this
• GSM 2nd generation mobile networks
• UMTS 3rd generation mobile networks
• Node SGSN and GGSN and the RAN consists of nodes NodeB and RNC; Mobile networks of the third generation development, which run in the standardization in 3GPP under the working titles "SAE” and "LTE".
• the core network consists of the nodes MME and UPE and the RAN consists of the nodes eNodeB and possibly central signaling nodes.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Quality & Reliability (AREA)
• Mobile Radio Communication Systems (AREA)
• Data Exchanges In Wide-Area Networks (AREA)

Priority Applications (12)

Applications Claiming Priority (2)

Related Child Applications (1)

Publications (1)

Family

ID=38016991

Family Applications (1)

Country Status (15)

Cited By (1)

Families Citing this family (4)

Citations (2)

Family Cites Families (8)

• 2006
  • 2006-02-14 DE DE102006006953A patent/DE102006006953A1/de not_active Withdrawn
• 2007
  • 2007-02-12 KR KR1020087022513A patent/KR101230031B1/ko active Active
  • 2007-02-12 ES ES07703391T patent/ES2348120T3/es active Active
  • 2007-02-12 EP EP07703391A patent/EP1985144B1/de active Active
  • 2007-02-12 PT PT07703391T patent/PT1985144E/pt unknown
  • 2007-02-12 JP JP2008554639A patent/JP5352242B2/ja active Active
  • 2007-02-12 BR BRPI0707798A patent/BRPI0707798B1/pt active IP Right Grant
  • 2007-02-12 SI SI200730363T patent/SI1985144T1/sl unknown
  • 2007-02-12 CN CN2007800055036A patent/CN101385380B/zh active Active
  • 2007-02-12 CA CA2642413A patent/CA2642413C/en active Active
  • 2007-02-12 PL PL07703391T patent/PL1985144T3/pl unknown
  • 2007-02-12 DK DK07703391.8T patent/DK1985144T3/da active
  • 2007-02-12 AT AT07703391T patent/ATE472912T1/de active
  • 2007-02-12 DE DE502007004247T patent/DE502007004247D1/de active Active
  • 2007-02-12 WO PCT/EP2007/001154 patent/WO2007093335A1/de not_active Ceased
• 2008
  • 2008-08-14 US US12/191,903 patent/US8699496B2/en active Active

Patent Citations (2)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events