PATENTSCOPE sera indisponible durant quelques heures pour des raisons de maintenance le lundi 03.02.2020 à 10:00 AM CET
Recherche dans les collections de brevets nationales et internationales
Une partie du contenu de cette demande n'est pas disponible pour le moment.
Si cette situation persiste, contactez-nous auObservations et contact
1. (WO2015176743) RÉGULATION DE SURCHARGE DE BOUT EN BOUT BASÉE SUR UN PROTOCOLE D'INITIALISATION DE SESSION DANS UN SOUS-SYSTÈME MULTIMÉDIA SOUS IP
Note: Texte fondé sur des processus automatiques de reconnaissance optique de caractères. Seule la version PDF a une valeur juridique

What is claimed is:

1 . A method, comprising

determining usage of a resource at session setup with a signaling protocol;

counting the determined used resources during the session setup;

increasing a value of a progress counter for overload control based on the counted used resources, wherein the progress counter for overload control is carried in a Session Initiation Protocol messaging; and

prohibiting, in case of an overload, rejection of messages in the Session Initiation Protocol messaging with a progress counter value higher than a set threshold value.

2. The method according to claim 1 , wherein the threshold is set dependent on an overload level of the occurring overload.

3. The method according to claim 1 or 2, wherein usage of resources of a single network element is counted.

4. The method according to claim 1 or 2, wherein usage of resources in the network is counted, and the progress counter is increased by an application server.

5. The method according to claim 1 or 2, wherein, in case an application server does not support the progress counter, the received progress counter is sent transparently through the application server, whereas the originating and the terminating Call Session Control Functions add their resource use.

6. The method according to claim 5, wherein an indication of the progress counter is transmitted across another node through an application server in a parameter in the route header of a Call Session Control Function.

7. The method according to any of claims 1 to 6, wherein the progress counter is increased by one by each entity handling the session setup request.

8. The method according to any of claims 1 to 7, wherein the progress counter is increased by each Session Initiating Protocol resource with a value dependent on the logic it applies.

9. The method according to any of claims 1 to 7, wherein the value a resource adds depends on its overload level.

10. The method according to any of claims 1 to 9, wherein the progress counter is used and added by network elements only in case of an overload.

1 1. The method according to any of claims 1 to 10, wherein the progress counter is a dedicated Session Initiating Protocol header field and/or carried as an Uniform Resource Identifier parameter in existing header fields.

12. The method according to any of claims 1 to 1 1 , wherein the Session Initiation Protocol messaging method is one of INVITE, SUBSCRIBE, UPDATE and PRACK.

13. The method according to any of claims 1 to 12, wherein the progress counter is removed when the Session Initiation Protocol leaves a validity area.

14. An apparatus, comprising

a determination unit configured to determine usage of a resource at session setup with a signaling protocol;

a counting unit configured to count the determined used resources during the session setup;

a processing unit configured to increase a value of a progress counter for overload control based on the counted used resources, wherein the progress counter for overload control is carried in a Session Initiation Protocol messaging; and

a prohibiting unit configured to prohibit, in case of an overload, rejection of messages in the Session Initiation Protocol messaging with a progress counter value higher than a set threshold value.

15. The apparatus according to claim 14, wherein the threshold is set dependent on an overload level of the occurring overload.

16. The apparatus according to claim 14 or 15, wherein usage of resources of a single network element is counted.

17. The apparatus according to claim 14 or 15, wherein the processing unit is configured to count usage of resources in the network, and the progress counter is increased by an application server.

18. The apparatus according to claim 14 or 15, wherein, in case an application server does not support the progress counter, the received progress counter is sent transparently through the application server, whereas the originating and the terminating Call Session Control Functions add their resource use.

19. The apparatus according to claim 18, wherein an indication of the progress counter is transmitted across another node through an application server in a parameter in the route header of a Call Session Control Function.

20. The apparatus according to any of claims 14 to 19, wherein the progress counter is increased by one by each entity handling the session setup request.

21. The apparatus according to any of claims 14 to 20, wherein the progress counter is increased by each Session Initiating Protocol resource with a value dependent on the logic it applies.

22. The apparatus according to any of claims 14 to 20, wherein the value a resource adds depends on its overload level.

23. The apparatus according to any of claims 14 to 22, wherein the progress counter is used and added by network elements only in case of an overload.

24. The method according to any of claims 14 to 21 , wherein the progress counter is a dedicated Session Initiating Protocol header field and/or carried as an Uniform Resource Identifier parameter in existing header fields.

25. The apparatus according to any of claims 14 to 24, wherein the Session Initiation Protocol messaging method is one of INVITE, SUBSCRIBE, UPDATE and PRACK.

26. The apparatus according to any of claims 1 to 25, wherein the progress counter is removed when the Session Initiation Protocol leaves a validity area.

27. A computer program product for a computer, comprising software code portions for performing the steps of any of claims 1 to 13 when said product is run on the computer.

28. The computer program product according to claim 27, wherein

the computer program product comprises a computer-readable medium on which said software code portions are stored, and/or

the computer program product is directly loadable into the internal memory of the computer and/or transmittable via a network by means of at least one of upload, download and push procedures.