(19)
(11)EP 3 238 400 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
10.06.2020 Bulletin 2020/24

(21)Application number: 14816333.0

(22)Date of filing:  23.12.2014
(51)International Patent Classification (IPC): 
H04L 29/06(2006.01)
(86)International application number:
PCT/EP2014/079228
(87)International publication number:
WO 2016/102016 (30.06.2016 Gazette  2016/26)

(54)

SERVICE AWARE OVERLOAD HANDLING IN A COMMUNICATION NETWORK

DIENSTBEWUSSTE ÜBERLASTUNGSHANDHABUNG IN EINEM KOMMUNIKATIONSNETZ

GESTION DE SURCHARGE EN FONCTION DU SERVICE DANS UN RÉSEAU DE COMMUNICATION


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(43)Date of publication of application:
01.11.2017 Bulletin 2017/44

(73)Proprietor: Telefonaktiebolaget LM Ericsson (publ)
164 83 Stockholm (SE)

(72)Inventors:
  • GONZALEZ DE LANGARICA, Ester
    S-116 29 Stockholm (SE)
  • HEGARTY, Cormac
    S-168 53 Bromma (SE)

(74)Representative: Brann AB 
P.O. Box 3690 Drottninggatan 27
103 59 Stockholm
103 59 Stockholm (SE)


(56)References cited: : 
US-A1- 2010 034 085
US-A1- 2014 006 630
US-A1- 2010 238 919
  
  • GURBANI V ET AL: "Session Initiation Protocol (SIP) Overload Control; draft-ietf-soc-overload-control-08.txt", SESSION INITIATION PROTOCOL (SIP) OVERLOAD CONTROL; DRAFT-IETF-SOC-OVERLOAD-CONTROL-08.TXT, INTERNET ENGINEERING TASK FORCE, IETF; STANDARDWORKINGDRAFT, INTERNET SOCIETY (ISOC) 4, RUE DES FALAISES CH- 1205 GENEVA, SWITZERLAND, 12 March 2012 (2012-03-12), pages 1-35, XP015081886, [retrieved on 2012-03-12]
  
Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


Description

Technical Field



[0001] The present invention relates to methods for providing an services in a communication network and to corresponding devices.

Background



[0002] In communication networks, such as cellular networks as specified by 3GPP (3rd Generation Partnership Project), it is known to provide various kinds of packet based services to a UE (user equipment), such as multimedia telephony services or messaging services. For example, in a 3GPP network such services may be provided by an architectural framework referred to as IMS (Internet Protocol Multimedia Subsystem). Details of the IMS are for example specified in 3GPP TS 23.228 V12.7.0 (2014-12). The IMS, but also various other kinds of packet based services, involve utilization of a control plane protocol referred to as SIP (Session Initiation Protocol), as for example specified in IETF RFC 3261 (June 2002), for establishing a session between a client utilizing the service and a server providing the service.

[0003] In many cases, the communication network may provide multiple application servers which provide multiple different services. Such application servers may have different capacities and the utilization of the provided service may vary individually for each application server. Accordingly, overload situations may occur in which one or more of the application servers is overloaded while one or more others of the application servers are not overloaded.

[0004] For addressing overload situations, the SIP provides a throttling mechanism based on a retry-after time window indicated in a header of a failure message. In the case of the IMS, the throttling mechanism may for example be implemented at a node acting as a proxy node for SIP messages between the IMS client and an IMS CN (IMS core network) and the application servers, such as a P-CSCF (Proxy Call Session Control Function) and IBCF (Interconnect Border Control Function). Further details concerning the handling of SIP messages by the P-CSCF and the IBCF can for example be found in 3GPP TS 24.229 V12.6.0 (2014-09).

[0005] Such proxy node typically operates on the basis of "windows" of SIP requests which are currently being handled. When the window is full, the proxy node does not forward the SIP request to the IMS CN but responds to it with an SIP failure response with response code 503 (Service Unavailable). This SIP failure response indicates that the server is undergoing maintenance or is temporarily overloaded and therefore cannot process the request. A "Retry-After" header field may specify when the client may reattempt its request. Upon receiving the SIP failure response, the client will not reattempt a new SIP request but will wait for the time period indicated in the Retry-After header field before sending a new SIP request. Such throttling mechanism may be implemented on an SIP method level, i.e., the windows and Retry-After time window may be provided individually for different SIP methods, such as REGISTER, SUBSCRIBE, or INVITE.

[0006] US patent application US 2014/0006630 A1 discloses systems and methods that use SIP for message throttling. A system includes a SIP client that communicates with a SIP server. When in operation, the SIP client sends a SIP request to the SIP server, such as a SIP INVITE. The SIP client then receives a SIP response from the SIP server answering the request. The SIP client parses the SIP response to identify an overload indicator which indicates that an overload condition exists in the SIP server, and limits additional SIP requests toward the SIP server based on the overload indicator.

[0007] However, in the above-mentioned situations where an overload occurs only for a part of the different application servers, the existing throttling mechanism may provide unsatisfactory results: It is quite common that different services use the same SIP method. For example, MMTel (Multimedia Telephony) and RCS (Rich Communication Suite) group chat both utilize the SIP INVITE method. Nonetheless, the corresponding application servers may have different capacity and may be subject to different traffic load. Accordingly, in an exemplary overload scenario the application server for RCS group chat may be overloaded while the application server for MMTel is not overloaded. If in this situation a UE tries to establish an RCS group chat session by sending an SIP INVITE request, the proxy node would respond with an SIP 503 failure response. If the UE then sends a further SIP INVITE request to establish an MMTel session, the proxy node may send an SIP 503 failure response as well, even though the corresponding application server is not overloaded. Further, 3GPP TS 24.229, section 5.1.3.1 specifies that upon receiving a SIP 503 failure response containing a Retry-After header field, the UE shall not automatically reattempt the request until after the time period indicated by the Retry-After header field has expired. Therefore, the UE may refrain from even sending the SIP INVITE request to establish the MMTel session. Accordingly, one service may be rejected due to an overload which is actually only present with respect to another service. This is undesirable from the perspective of service availability and user experience.

[0008] Accordingly, there is a need for techniques which allow for efficiently controlling multiple services in a communication network.

Summary



[0009] According to an embodiment of the invention, a method of controlling multiple services in a communication network is provided. According to the method, a node of the communication network receives a request relating to one of the multiple services, where the multiple services are provided by multiple application servers included in the communication network. Further, the node determines whether an overload with respect to the service is present. In response to determining absence of the overload with respect to the service, the node forwards the request for further processing by a corresponding application server. In response to determining presence of the overload with respect to the service, the node responds to the request with a failure message indicating that the request was not processed. The failure message comprises an indication of a time window after which the request may be retried and an identifier of the service to which the request relates.

[0010] According to a further embodiment of the invention, a method of controlling multiple services in a communication network is provided. According to the method, a communication device sends a request relating to one of the multiple services to the communication network, where the multiple services are provided by multiple application servers included in the communication network. In response to the request, the communication device receives a failure message from the communication network. The failure message indicating that the request was not processed and the failure message comprises an indication of a time window after which the request may be retried and an identifier of the service to which the request relates. Before expiry of the time window, the communication device determines a need to send a further request relating to one of the multiple services to the communication network. Depending on whether the further request relates to the service indicated in the failure message or to another one of the multiple services, the communication device controls sending of the further request to the communication network.

[0011] According to a further embodiment of the invention, a node for a communication network is provided. The node at least one interface for transmitting control plane messages relating to multiple services supported by the communication network. Further, the node comprises at least one processor. The at least one processor is configured to receive a request relating to one of the multiple services, where the multiple services are provided by multiple application servers included in the communication network. Further, the at least one processor is configured to determine whether an overload with respect to the service is present. Further, the at least one processor is configured to, in response to determining absence of the overload with respect to the service, forward the request for further processing. Further, the at least one processor is configured to, in response to determining presence of the overload with respect to the service, respond to the request with a failure message. The failure message indicates that the request was not processed and the failure message comprises an indication of a time window after which the request may be retried and an identifier of the service to which the request relates.

[0012] According to a further embodiment of the invention, a communication device is provided. The communication device comprises at least one interface for utilizing multiple services supported by a communication network. Further, the communication device comprises at least one processor. The at least one processor is configured to send a request relating to one of the multiple services to the communication network, where the multiple services are provided by multiple application servers included in the communication network. Further, the at least one processor is configured to receive, in response to the request, a failure message from the communication network. The failure message indicates that the request was not processed and the failure message comprises an indication of a time window after which the request may be retried and an identifier of the service to which the request relates. Further, the at least one processor is configured to determine, before expiry of the time window, a need to send a further request relating to one of the multiple services to the communication network. Further, the at least one processor is configured to control sending of the further request to the communication network depending on whether the further request relates to the service indicated in the failure message or to another one of the multiple services.

[0013] According to a further embodiment of the invention, a computer program or computer program product is provided, e.g., in the form of a non-transitory storage medium, which comprises program code to be executed by at least one processor of a node of a communication network. Execution of the program code causes the at least one processor to receive a request relating to one of multiple services supported by the communication network, where the multiple services are provided by multiple application servers included in the communication network. Further, execution of the program code causes the at least one processor to determine whether an overload with respect to the service is present. Further, execution of the program code causes the at least one processor to, in response to determining absence of the overload with respect to the service, forward the request for further processing. Further, execution of the program code causes the at least one processor to, in response to determining presence of the overload with respect to the service, respond to the request with a failure message. The failure message indicates that the request was not processed and the failure message comprises an indication of a time window after which the request may be retried and an identifier of the service to which the request relates.

[0014] According to a further embodiment of the invention, a computer program or computer program product is provided, e.g., in the form of a non-transitory storage medium, which comprises program code to be executed by at least one processor of a communication device for operation in a communication network. Execution of the program code causes the at least one processor to send to the communication network a request relating to one of multiple services supported by the communication network, where the multiple services are provided by multiple application servers included in the communication network. Further, execution of the program code causes the at least one processor to receive, in response to the request, a failure message from the communication network. The failure message indicates that the request was not processed and the failure message comprises an indication of a time window after which the request may be retried and an identifier of the service to which the request relates. Further, execution of the program code causes the at least one processor to determine, before expiry of the time window, a need to send a further request relating to one of the services to the communication network. Further, execution of the program code causes the at least one processor to control sending of the further request to the communication network depending on whether the further request relates to the service indicated in the failure message or to another one of the services.

[0015] Details of such embodiments and further embodiments will be apparent from the following detailed description of embodiments.

Brief Description of the Drawings



[0016] 

Fig. 1 schematically illustrates an architecture as applied according to an embodiment of the invention for providing multiple services in a communication network.

Fig. 2 shows an exemplary signaling flow of processes according to an embodiment of the invention.

Fig. 3 shows a flowchart for illustrating a method according to an embodiment of the invention, which may be performed by a node of a communication network.

Fig. 4 shows a flowchart for illustrating a further method according to an embodiment of the invention, which may be performed by a communication device connected to the communication network.

Fig. 5 schematically illustrates a network node according to an embodiment of the invention.

Fig. 6 schematically illustrates a communication device according to an embodiment of the invention.


Detailed Description of Embodiments



[0017] In the following, concepts in accordance with exemplary embodiments of the invention will be explained in more detail and with reference to the accompanying drawings. The illustrated embodiments relate to providing multiple services in a communication network. In the illustrated examples, it is assumed that the communication network is a cellular network as specified by 3GPP, and that the cellular network implements an IMS architecture for providing the services. However, it is to be understood that other network technologies, e.g., non-3GPP cellular network technologies, non-cellular wireless network technologies, or even wire-based network technologies could be applied as well. Further, the illustrated concepts may also be applied with respect to services not based on the IMS.

[0018] In the illustrated concepts, a throttling mechanism for control plane traffic associated with establishing sessions of the services is implemented in a service aware manner. For this purpose, a node of the network which receives a request related to one of the services first determines whether an overload with respect to the service is present or not. The request may be an SIP request for establishing a session of the service, e.g., an SIP INVITE request. In the case of absence of an overload with respect to the service, the node may forward the request for further processing, e.g., by a corresponding application server. Accordingly, the node may act as a proxy node for requests relating to the services. In the case of presence of an overload with respect to the service, the node responds to the request with a failure message, e.g., a SIP failure response of the server failure response category (identified by a response code of the form 5xx). The failure response may also indicate that the failure is due to an overload of an individual server. For this purpose, a corresponding message type could be defined, e.g., in the server failure response category. Alternatively, an existing failure response could be provided with a corresponding additional indication, e.g., in the form of an information field in the message header. Similar to the existing SIP throttling mechanism, the failure message indicates a time window after which the sender of the request may retry sending the request, e.g., in the form of the Retry After field. Further, the failure message indicates the service to which the request relates, e.g., in the form of a service identifier.

[0019] In the case of the assumed example of IMS services, the identifier may for example correspond to an ICSI (IMS Common Service Identifier). For some IMS services, the ICSI is typically included in a PAS (P-Asserted Service) header of the SIP INVITE request. Details of the PAS header can be found in IETF RFC 6050 (2010-11). Accordingly, in some implementations, a service identifier indicated in the request received by the node may be utilized to determine the service and also be included in the failure message. In cases where no ICSI or similar service identifier is included in the request, other ways may be utilized for deducing the service and determining the service identifier too be included in the failure message. For example, the service may be determined from other information in the header of the request, e.g., from information fields referred to as "Contact", "Accept-Contact", "Content-Type", or the like. For example, in the case of an OMA IM (Open Mobile Alliance) chat/group chat service, the SIP INVITE request includes a tag "+g./oma.sip-im" in the Accept-Contact and Contact information fields, which may be used as a basis for identifying the service.

[0020] Fig. 1 illustrates an exemplary architecture which may be utilized to implement the concepts as outlined above. In particular, Fig. 1 shows a UE 10 connected to the communication network, which includes a P-CSCF 100, an IMS CN 110, a first application server (AS 1) 120, and a second application server (AS 2) 130. The first application server 120 and the second application server 130 are assumed to provide different services. For example, the first application server 120 may provide a messaging service, such as OMA IM Chat/Group Chat CPM (Converged IP messaging) service, and the second application server 130 may provide a multimedia telephony service, such as MMTel. Due to the different nature of the services, the first application server 120 and the second application server 130 may have different capacities, further the load on the application servers 120, 130 may vary in an individually different way. Accordingly, situations may occur in which for one of the application servers 120 there is an overload situation, while of the other of the application servers there is no such overload situation.

[0021] The P-CSCF 100 of Fig. 1 acts as a common proxy node for control plane messages concerning sessions of the services provided by the application servers 120, 130. These proxy node functionalities involve forwarding SIP requests from service clients implemented at the UE 10 towards the IMS CN 110 and forwarding SIP responses to these SIP requests from the IMS CN 110 to the service clients. Further, the P-CSCF is also assumed to implement a throttling mechanism 105 for protecting the IMS CN 110 and the application servers 120, 130 from congestions which may arise in overload situations, such as simultaneous mass registrations or session establishment by a plurality of UEs.

[0022] The throttling mechanism 105 operates by detecting overload situations in a service specific manner and also sending failure responses for such overload situations in a service specific manner. In Fig. 1 this is illustrated for an exemplary scenario assuming that the first application server 120 is overloaded, while the second application server 130 is not overloaded.

[0023] As illustrated, the UE 10 sends a first SIP request 101, e.g., an SIP INVITE request, to the network for establishing a session of the service provided by the first application server 120. Upon receiving the first SIP request 101, the P-CSCF 100 detects that there is an overload with respect to the service provided by the first application server 120. Accordingly, the P-CSCF 100 does not forward the first SIP request 101 to the IMS CN 110, but rather sends a failure message 102. As mentioned above, the failure message 102 indicates the service to which the SIP request 101 relates. Further, the failure message 102 indicates a Retry-After time window. Further, the failure message 102 may also indicate a type of the failure, i.e., that the failure is due to an overload with respect to the specific service. For example, a server failure response type may be defined for situations in which there is an overload with respect to a specific service, and the failure message 102 may correspond to this failure response type.

[0024] As further illustrated by Fig. 1, the UE 10 then sends a second SIP request 103 to the network. The further SIP request 103 is assumed to relate to the same SIP method as the first SIP request 101. For example, if the first SIP request 101 is an SIP INVITE request, also the second SIP request 103 would be an SIP INVITE request. Further, the second SIP request 103 is assumed to be sent before expiry of the Retry-After time window indicated in the failure message 102. The second SIP request 103 has the purpose of establishing a session of the service provided by the second application server 130. Because the second SIP request relates to another service than the service indicated in the failure message 102, the UE 10 sends the second SIP request 103 irrespectively of the Retry-After time window not having expired. Upon receiving the second SIP request 103, the P-CSCF 100 detects that there is no overload with respect to the service provided by the second application server 130. Accordingly, the P-CSCF 100 forwards the second SIP request 103 to the IMS CN 110, and after the acceptance of the second SIP request 103 by the second application server 130, sends a SIP OK response 104 to the UE 10 to confirm successful establishment of the session.

[0025] Figs. 2 shows a signaling flow of exemplary processes for controlling session establishment. The processes of Fig. 2 involve the UE 10, the P-CSCF 100, an S-CSCF (Serving Call State Control Function) 100', the first application server 120, which in the illustrated example is assumed to be a MMTel application server (MTAS), the second application server 130, which in the illustrated example is assumed to be a messaging application server (MAS) providing a chat service, a BGCF (Breakout Gateway Control Function) 150, an IBCF 160, and a gateway 170. The S-CSCF 100', the BGCF 150, and the IBCF 160 may be regarded as components of the IMS CN.

[0026] As illustrated, the UE 10 may initially send an SIP INVITE request 201 for establishing a chat session controlled by the MAS 120. The SIP INVITE request 201 includes a PAS field or PPS (P-Preferred Service) field as specified by IETF RFC 6050. which indicates an ICSI corresponding to the chat service provided by the MAS 120.

[0027] Upon receiving the SIP INVITE request 201, the P-CSCF 100 recognizes the service to which the SIP INVITE request 201 relates, as indicated by step 202. In the illustrated example, the P-CSCF 100 would recognize that the SIP INVITE request 201 relates to the chat service.

[0028] As indicated by step 203, the P-CSCF 100 then detects whether there is an overload with respect to the service recognized at step 202. As illustrated, this may be accomplished by providing a corresponding bucket list for each of the supported services, and checking the bucket list for the service recognized at step 202, i.e., for the chat service. The bucket lists are assumed to include as those SIP INVITE requests relating to the respective service for which processing is not yet completed, i.e., no response has been sent by the P-CSCF 100.

[0029] In the illustrated example, an overload with respect to the chat service provided by the MAS 120 is assumed, resulting in the number of elements in the bucket list for the chat service exceeding a threshold. Accordingly, the P-CSCF 100 determines that an overload with respect to the chat service is present.

[0030] In response to detecting the overload with respect to the service at step 203, the P-CSCF 100 sends a failure message 204 to the UE 10. The failure message may be an SIP failure response of the server failure response category, e.g., a SIP server failure response of a type defined as indicating an overload with respect to a specific service. As further illustrated, the failure message 204 also indicates a Retry-After time window (in the illustrated example assumed to be 30 s) and includes a field indicating the overloaded service, i.e., the chat service in terms of the corresponding ICSI.

[0031] From the failure message 204, the UE 10 learns that the specific service of the SIP INVITE request 204 is overloaded, but that this overload may not pertain to other services, such as the MMTel service provided by the MTAS 130. If the UE 10 now needs to send a further SIP INVITE request, it first checks if the Retry-After time window has expired, and if this is not the case, if the further SIP INVITE request corresponds to the service indicated in the failure message 204 or to another service. Before expiry of the Retry-After time window, the UE 10 sends the further SIP INVITE request only if relates to another service than the service indicated in the failure message 204. If the further SIP INVITE request relates to the same service as indicated in the failure message 204, the UE 10 may or delay sending the further SIP INVITE message until the Retry-After time window has expired or may refrain from sending the further SIP INVITE message.

[0032] In the illustrated example, it is assumed that before expiry of the Retry-After time window indicated in the failure message 204, the UE 10 needs to send a further SIP INVITE request 205 for establishing a session of the MMTel service provided by the MTAS 130. Because the service is different from the service indicated in the failure message 204, the UE 10 sends the request 205 before expiry of the Retry-After time window. The further SIP INVITE request 205 includes a PAS field or PPS field which indicates an ICSI corresponding to the MMTel service provided by the MAS 120.

[0033] Upon receiving the further SIP INVITE request 205, the P-CSCF 100 recognizes the service to which the further SIP INVITE request 205 relates, as indicated by step 206. In the illustrated example, the P-CSCF 100 would recognize that the further SIP INVITE request 206 relates to the MMTel service.

[0034] As indicated by step 207, the P-CSCF 100 then detects whether there is an overload with respect to the service recognized at step 206. This may be accomplished checking the bucket list for the service recognized at step 206, i.e., the bucket list for the MMTel service.

[0035] In the illustrated example, no overload with respect to the MMTel service provided by the MTAS 130 is assumed, which means that in the number of elements in the bucket list for the MMTel service does not exceed a threshold defining an overload. Accordingly, the P-CSCF 100 determines that no overload with respect to the MMTel service is present.

[0036] Since no overload is present, the P-CSCF 100 forwards the further SIP INVITE request 205 for further processing. As illustrated in Fig. 2 this involves transmission of a cascade of SIP INVITE requests 208, 209, 210, 211, 212, 213 via the S-CSCF 100', the MTAS 130, the BGCF 150, and the IBCF 160 towards the gateway 170, transmission of a cascade of SIP OK responses 214, 215, 216, 217, 218, 219 from the gateway 170 to the P-CSCF 100, and transmission of an SIP OK response 220 from the P-CSCF 100 to the UE 10. The session is then successfully established and media 221 relating to the service may be transmitted between the UE 10 and the gateway 170.

[0037] It should be noted that the functionalities as explained in connection with Fig. 2 for the P-CSCF 100 may also be implemented in other nodes with proxy node functionalities, such as the S-CSCF 100' or the IBCF 160.

[0038] As can be seen, the service-aware handling of the overload situation allows for successfully establishing a session relating to a non-overloaded other service, even if the Retry-After time window in the failure message 204 indicating the overload has not yet expired.

[0039] Fig. 3 shows a flowchart for illustrating a method which may be utilized for implementing the illustrated concepts. The method may be applied for providing multiple services in a communication network. These services may in particular be packet-based services, such as IMS services, utilizing SIP based methods for session establishment. The method is performed by a node of the communication network, e.g., a node acting as a proxy node for control plane messages relating to the services. Examples of such nodes are a CSCF (Call State Control Function) of the IMS, such as the above-mentioned P-CSCF 100 or S-CSCF 100', a IBCF of the IMS, such as the above-mentioned IBCF 160. If a processor-based implementation of the node is used, the steps of the method may be performed by one or more processors of the node.

[0040] At step 310, the node receives a request relating to one of the services. The request may for example have the purpose of establishing or otherwise controlling a session of this service. The session may be established by a communication device connected to the communication network, such as the UE 10. The request may for example be an SIP request, such as an SIP INVITE request. The request may also include a service identifier of the service, e.g., in the form of an ICSI.

[0041] At step 320, the node determines the service to which the request relates. If the request includes a service identifier, this may be accomplished on the basis of this service identifier. Alternatively, the service may be deduced from other information fields of the request which allow for distinguishing between the different services.

[0042] At step 330, the node determines whether an overload with respect to the service is present. For this purpose, the node may determine a list of pending requests relating to the service and then perform the determination depending on a number of elements in the list of pending requests. The bucket lists mentioned in connection with steps 203 and 207 of Fig. 2 are examples of such list of pending requests. If the number of elements in the list for the service determined at step 320 exceeds a threshold, the node may determine that an overload with respect to the service is present. Otherwise, the node may determine that there is no overload with respect to the service. Such thresholds for detecting the presence of an overload may be defined individually for each of the service.

[0043] In response to determining absence of an overload with respect to the service, the node proceeds to step 340, as indicated by branch "N". At step 340, the node forwards the request for further processing. This may involve sending the request or a subsequent request to another node. However, in some scenarios the further processing of the request could also be internal within the node.

[0044] In response to determining presence of an overload with respect to the service, the node proceeds to step 350, as indicated by branch "Y". At step 350, the node responds with a failure message to the request of step 310. The failure message indicates that the request was not processed. In some scenarios, the failure message may indicate that the request was not processed due to the overload with respect to the service, i.e., indicate a failure type. This may be accomplished implicitly by selecting a corresponding message type for the failure message or explicitly by indicating a failure reason in the failure message. Further, the failure message includes an indication of a time window after which the request may be retried, i.e., in the form of the above-mentioned Retry-After time window, and an identifier of the service to which the request relates (in other words, an identifier of the service for which the overload was found to be present). If a service identifier was included in the request of step 310, e.g., an ICSI, the same identifier may also be included in the failure message.

[0045] Fig. 4 shows a flowchart for illustrating a further method which may be utilized for implementing the illustrated concepts. The method may be applied for providing multiple services in a communication network. These services may in particular be packet-based services, such as IMS services, utilizing SIP based methods for session establishment. The method is performed by a communication device connected to the communication network, such as the UE 10. If a processor-based implementation of the communication device is used, the steps of the method may be performed by one or more processors of the communication device.

[0046] At step 410, the communication device sends a request relating to one of the services to the communication network. The request may for example have the purpose of establishing or otherwise controlling a session of this service. The request may for example be an SIP request, such as an SIP INVITE request. The request may also include a service identifier of the service, e.g., in the form of an ICSI. The request may be sent to a node acting as a proxy node for control plane messages related to the service. For example, this node may correspond to a CSCF, such as the above-mentioned P-CSCF 100 or S-CSCF 100', or to an IBCF, such as the above-mentioned IBCF 160.

[0047] At step 420, the communication device receives a failure message from the communication network. The failure message indicates that the request was not processed. In some scenarios, the failure message may indicate that the request was not processed due to an overload with respect to the service, i.e., indicate a failure type. This may be accomplished implicitly by a corresponding message type for the failure message or explicitly by indicating a failure reason in the failure message. Further, the failure message includes an indication of a time window after which the request may be retried, i.e., in the form of the above-mentioned Retry-After time window, and an identifier of the service to which the request relates (in other words, an identifier of the service for which the overload was found to be present). The failure message may include a service identifier, e.g., an ICSI, which may be the same as included in the request of step 410.

[0048] At step 430, before expiry of the time window indicated in the failure message, the communication device determines a need to send a further request relating to one of the services to the communication network. For example, if the request of step 410 was an SIP INVITE request, the communication device may determine a need to send a further SIP INVITE request. This further request may relate to the same service as the request of step 410 and as indicated in the failure message of step 420, or may relate to another one of the services.

[0049] At step 440, the communication device controls sending of the further request to the communication network. This is accomplished depending on whether the further request relates to the service indicated in the failure message or to another one of the services.

[0050] For example, in response to the further request relating to the service indicated in the failure message, the communication device may send the further request after expiry of the time window indicated in the failure message. Further, in response to the further request relating to the service indicated in the failure message, the communication device may refrain from sending the further request. Further, in response to the further request relating to another one of the services, the communication device may send the further request before expiry of the time window.

[0051] It is to be understood that the methods of Figs. 3 and 4 may be combined with each other in a system which includes a node of a communication network operating according to the method of Fig. 3 and a communication device operating according to the method of Fig. 4. Fig. 5 illustrates exemplary structures which may be used for implementing the above concepts in a node for a communication network, e.g., a node implementing a CSCF, such as the above-mentioned P-CSCF 100 or S-CSCF 100', or a node implementing an IBCF, such as the above-mentioned IBCF 160.

[0052] As illustrated, the node may include a client interface 510 for connecting to one or more communication devices acting as clients for services provided by the communication network, such as the UE 10. Further, the node may include a server interface 520 for connecting to application servers providing the services, such as the application servers 120, 130. The interfaces 510 and 520 may be SIP based.

[0053] Further, the node includes one or more processors 550 coupled to the interfaces 510, 520, and 530, and a memory 560 coupled to the processor(s) 550. The memory 560 may include a Read Only Memory (ROM), e.g., a flash ROM, a Random Access Memory (RAM), e.g., a Dynamic RAM (DRAM) or Static RAM (SRAM), a mass storage, e.g., a hard disk or solid state disk, or the like. The memory 560 includes suitably configured program code to be executed by the processor(s) 850 so as to implement the above-described functionalities of the node. In particular, the memory 560 may include various program code modules for causing the node to perform processes as described above, e.g., corresponding to the method steps of Fig. 3.

[0054] As illustrated, the memory 560 may include a message proxy module 570 for implementing the above-described functionalities of receiving, sending and forwarding messages relating to different services. These functionalities may include the above-mentioned receiving and forwarding of requests relating to the services. Further, the memory 560 may include an overload detection module 580 for implementing the above-described functionalities of detecting an overload with respect to a service. Further, the memory 560 may include a throttling module 590 for implementing the above-mentioned functionalities of sending the service-specific failure response in response to detecting an overload with respect to one of the services.

[0055] It is to be understood that the structures as illustrated in Fig. 5 are merely schematic and that the node may actually include further components which, for the sake of clarity, have not been illustrated, e.g., further interfaces or processors. Also, it is to be understood that the memory 560 may include further types of program code modules, which have not been illustrated, e.g., program code modules for implementing known functionalities of a node implementing a P-CSCF. According to some embodiments, also a computer program may be provided for implementing functionalities of the node, e.g., in the form of a physical medium storing the program code and/or other data to be stored in the memory 560 or by making the program code available for download or by streaming.

[0056] Fig. 6 illustrates exemplary structures which may be used for implementing the above concepts in a communication device for operation in a communication network, such as the UE 10.

[0057] As illustrated, the communication device may include a network interface 610 for connecting to the communication network. The interface 610 may be SIP based.

[0058] Further, the communication device includes one or more processors 650 coupled to the interface 610, and a memory 660 coupled to the processor(s) 650. The memory 660 may include a ROM, e.g., a flash ROM, a RAM, e.g., a DRAM or SRAM, a mass storage, e.g., a hard disk or solid state disk, or the like. The memory 660 includes suitably configured program code to be executed by the processor(s) 650 so as to implement the above-described functionalities of the communication device. In particular, the memory 660 may include various program code modules for causing the communication device to perform processes as described above, e.g., corresponding to the method steps of Fig. 4.

[0059] As illustrated, the memory 660 may include a service control module 670 for implementing the above-described functionalities of sending and receiving control plane messages relating to different services. These functionalities may include the above-mentioned sending of requests relating to the services and receiving of responses to these requests. Further, the memory 560 may include a request processing module 680 for implementing the above-described functionalities of controlling the sending of requests depending on the service indicated in a failure message.

[0060] It is to be understood that the structures as illustrated in Fig. 6 are merely schematic and that the communication device may actually include further components which, for the sake of clarity, have not been illustrated, e.g., further interfaces or processors. Also, it is to be understood that the memory 660 may include further types of program code modules, which have not been illustrated, e.g., program code modules for implementing known functionalities of a UE as utilized in a 3GPP cellular network. According to some embodiments, also a computer program may be provided for implementing functionalities of the communication device, e.g., in the form of a physical medium storing the program code and/or other data to be stored in the memory 660 or by making the program code available for download or by streaming.

[0061] As can be seen, the concepts as described above may be used for controlling multiple services in a communication network. In particular, it can be avoided that an overload with respect to only a certain application service affects other services which are not overloaded. In this way, an improved service availability and user experience may be achieved. From the perspective of the operator of the communication network or the provider(s) of the services. this may also allow for increased service revenues. Further, network resources may be used more efficiently because blocking of requests to an application server which is not overloaded can be avoided.

[0062] It is to be understood that the examples and embodiments as explained above are merely illustrative and susceptible to various modifications. For example, the illustrated concepts may be applied in connection with various network technologies, without limitation to the above-mentioned example of 3GPP cellular network technology. Further, the illustrated concepts may be applied in connection with various kinds and numbers of services, without limitation to the above-mentioned IMS services. Moreover, it is to be understood that the above concepts may be implemented by using correspondingly designed software to be executed by one or more processors of an existing device, or by using dedicated device hardware. Further, it should be noted that the illustrated nodes may each be implemented as a single device or as a system of multiple interacting devices.


Claims

1. A method of controlling multiple services in a communication network, the method comprising:

a node (100), of the communication network, receiving a request (101; 201) relating to one of the multiple services, wherein the multiple services are provided by multiple application servers included in the communication network;

the node (100) determining whether an overload with respect to the service is present;

in response to determining absence of the overload with respect to the service, the node (100) forwarding the request (101; 201) for further processing by a corresponding application server; and

in response to determining presence of the overload with respect to the service, the node (100) responding to the request (101; 201) with a failure message (102; 204), the failure message (102; 204) indicating that the request (101; 201) was not processed, and the failure message (102; 204) comprising an indication of a time window after which the request (101; 201) may be retried and an identifier of the service to which the request (101; 201) relates.


 
2. The method according to claim 1,
wherein the failure message (102; 204) further comprises an indication that the request (101; 201) was not processed due to an overload with respect to the service.
 
3. The method according to claim 1 or 2, comprising:

the node (100) determining the service to which the request (101; 201) relates;

depending on the service to which the request (101; 201) relates, the node (100) determining a list of pending requests relating to the service; and

the node (100) performing said determining whether an overload with respect to the service is present depending on a number of elements in the list of pending requests.


 
4. The method according to any one of the preceding claims,
wherein the identifier of the service is also indicated in the request (101; 201).
 
5. A method of controlling multiple services in a communication network, the method comprising:

a communication device (10) sending a request (101; 201) relating to one of the multiple services to the communication network, wherein the multiple services are provided by multiple application servers included in the communication network;

in response to the request (101; 201), the communication device (10) receiving a failure message (102) from the communication network, the failure message (102; 204) indicating that the request (101; 201) was not processed, and the failure message (102; 204) comprising an indication of a time window after which the request (101; 201) may be retried and an identifier of the service to which the request (101; 201) relates;

before expiry of the time window, the communication device (10) determining a need to send a further request (103; 205) relating to one of the multiple services to the communication network; and

depending on whether the further request (103; 205) relates to the service indicated in the failure message (102; 204) or to another one of the multiple services, the communication device (10) controlling sending of the further request (103; 205) to the communication network.


 
6. The method according to claim 5, comprising:

- in response to the further request (103; 205) relating to the service indicated in the failure message (102; 204), the communication device (10) sending the further request (103; 205) after expiry of the time window.


 
7. The method according to claim 5 or 6, comprising:

- in response to the further request (103; 205) relating to the service indicated in the failure message (102; 204), the communication device (10) not sending the further request (103; 204).


 
8. The method according to any one of claims 5 to 7, comprising:

- in response to the further request (103; 205) relating to another one of the services, the communication device (10) sending the further request (103; 205) before expiry of the time window.


 
9. The method according to any one of the claims 5 to 8,
wherein the failure message (102; 204) further comprises an indication that the request (101; 201) was not processed due to an overload with respect to the service.
 
10. The method according to any one of claims 5 to 9,
wherein the identifier of the service is also indicated in the request (101; 201).
 
11. A node (100) for a communication network, the node (100) comprising:

at least one interface (510) for control plane messages (101, 102, 103, 104; 201, 204, 205, 208, 219, 220) relating to multiple services supported by the communication network, wherein the multiple services are provided by multiple application servers included in the communication network; and

at least one processor (550), the at least one processor (550) being configured to:

- receive a request (101; 201) relating to one of the multiple services;

- determine whether an overload with respect to the service is present;

- in response to determining absence of the overload with respect to the service, forward the request (101; 201) for further processing by a corresponding application server; and

- in response to determining presence of the overload with respect to the service, respond to the request (101; 201) with a failure message (102; 204), the failure message (102; 204) indicating that the request (101; 201) was not processed, and the failure message (102; 204) comprising an indication of a time window after which the request (101; 201) may be retried and an identifier of the service to which the request (101; 201) relates.


 
12. The node (100) according to claim 11,
wherein the at least one processor (550) is configured to perform the steps of a method according to any one of claims 2 to 4.
 
13. A communication device (10), comprising:

at least one interface (610) for utilizing multiple services supported by a communication network, wherein the multiple services are provided by multiple application servers included in the communication network; and

at least one processor (650), the at least one processor (650) being configured to:

- send a request (101; 201) relating to one of the multiple services to the communication network;

- in response to the request (101; 201), receive a failure message (102; 204) from the communication network, the failure message (102; 204) indicating that the request was not processed, and the failure message (102; 204) comprising an indication of a time window after which the request (101; 201) may be retried and an identifier of the service to which the request (101; 201) relates;

- before expiry of the time window, determine a need to send a further request (103; 205) relating to one of the multiple services to the communication network; and

- depending on whether the further request (103; 205) relates to the service indicated in the failure message (102; 204) or to another one of the multiple services, control sending of the further request (103; 205) to the communication network.


 
14. The communication device (10) according to claim 13,
wherein the at least one processor (650) is configured to perform the steps of a method according to any one of claims 6 to 10.
 
15. A computer program comprising program code to be executed by at least one processor (550) of a node (100) of a communication network, wherein execution of the program code causes the at least one processor (550) to perform steps of a method according to any one of claims 1 to 4.
 
16. A computer program comprising program code to be executed by at least one processor (650) of a communication device (10) operated in a communication network, wherein execution of the program code causes the at least one processor (650) to perform steps of a method according to any one of claims 5 to 10.
 


Ansprüche

1. Verfahren zum Steuern mehrerer Dienste in einem Kommunikationsnetzwerk, wobei das Verfahren Folgendes umfasst:

einen Knoten (100) des Kommunikationsnetzwerks, der eine Anfrage (101; 201) bezüglich eines der mehreren Dienste empfängt, wobei die mehreren Dienste durch mehrere in dem Kommunikationsnetzwerk beinhaltete Anwendungsserver bereitgestellt sind;

wobei der Knoten (100) bestimmt, ob eine Überlastung in Bezug auf den Dienst vorliegt;

wobei als Reaktion auf das Bestimmen eines Nichtvorhandenseins der Überlastung in Bezug auf den Dienst, der Knoten (100) die Anfrage (101; 201) zum Weiterverarbeiten durch einen entsprechenden Anwendungsserver weiterleitet; und

wobei als Reaktion auf das Bestimmen eines Vorhandenseins der Überlastung bezüglich des Dienstes, der Knoten (100) auf die Anfrage (101; 201) mit einer Fehlernachricht (102; 204) antwortet, wobei die Fehlernachricht (102; 204) angibt, dass die Anfrage (101; 201) nicht verarbeitet wurde, und wobei die Fehlernachricht (102; 204) eine Angabe eines Zeitfensters, nach dessen Ablauf die Anfrage (101; 201) erneut versucht werden kann, und eine Kennung des Dienstes, auf den sich die Anfrage (101; 201) bezieht, umfasst.


 
2. Verfahren nach Anspruch 1, wobei die Fehlernachricht (102; 204) ferner eine Angabe darüber umfasst, dass die Anfrage (101; 201) aufgrund einer Überlastung in Bezug auf den Dienst nicht verarbeitet wurde.
 
3. Verfahren nach Anspruch 1 oder 2, umfassend:

den Knoten (100), der den Dienst bestimmt, auf den sich die Anfrage (101; 201) bezieht;

wobei in Abhängigkeit von dem Dienst, auf den sich die Anfrage (101; 201) bezieht, der Knoten (100) eine Liste ausstehender Anfragen bezüglich des Dienstes bestimmt; und

den Knoten (100),der das Bestimmen, ob eine Überlastung in Bezug auf den Dienst vorliegt, an einer Anzahl von Elementen in der Liste ausstehender Anfragen durchführt.


 
4. Verfahren nach einem der vorstehenden Ansprüche, wobei die Kennung des Dienstes auch in der Anfrage (101; 201) angegeben ist.
 
5. Verfahren zum Steuern mehrerer Dienste in einem Kommunikationsnetzwerk, wobei das Verfahren Folgendes umfasst:

eine Kommunikationsvorrichtung (10), die eine Anfrage (101; 201) bezüglich eines der mehreren Dienste an das Kommunikationsnetzwerk sendet, wobei die mehreren Dienste durch mehrere in dem Kommunikationsnetzwerk beinhaltete Anwendungsserver bereitgestellt sind;

wobei als Reaktion auf die Anfrage (101; 201) die Kommunikationsvorrichtung (10) eine Fehlernachricht (102) von dem Kommunikationsnetzwerk empfängt, wobei die Fehlernachricht (102; 204) angibt, dass die Anfrage (101; 201) nicht verarbeitet wurde, und wobei die Fehlernachricht (102; 204) eine Angabe eines Zeitfensters, nach dessen Ablauf die Anfrage (101; 201) erneut versucht werden kann, und eine Kennung des Dienstes, auf den sich die Anfrage (101; 201) bezieht, umfasst;

wobei vor Ablauf des Zeitfensters die Kommunikationsvorrichtung (10) eine Notwendigkeit, eine weitere Anfrage (103; 205) bezüglich eines der mehreren Dienste an das Kommunikationsnetzwerk zu senden, bestimmt; und

wobei in Abhängigkeit davon, ob sich die weitere Anfrage (103; 205) auf den Dienst, der in der Fehlernachricht (102; 204) angegeben ist, oder auf einen anderen der mehreren Dienste bezieht, die Kommunikationsvorrichtung (10) das Senden der weiteren Anfrage (103; 205) an das Kommunikationsnetzwerk steuert.


 
6. Verfahren nach Anspruch 5, umfassend:

- als Reaktion auf die weitere Anfrage (103; 205) bezüglich des Dienstes, der in der Fehlernachricht (102; 204) angegeben ist, Senden der weiteren Anfrage (103; 205) nach Ablauf des Zeitfensters durch die Kommunikationsvorrichtung (10).


 
7. Verfahren nach Anspruch 5 oder 6, umfassend:

- als Reaktion auf die weitere Anfrage (103; 205) bezüglich des Dienstes, der in der Fehlernachricht (102; 204) angegeben ist, kein Senden der weiteren Anfrage (103; 204) durch die Kommunikationsvorrichtung (10).


 
8. Verfahren nach einem der Ansprüche 5 bis 7, umfassend:

- als Reaktion auf die weitere Anfrage (103; 205) bezüglich eines anderen der Dienstes, Senden der weiteren Anfrage (103; 205) vor Ablauf des Zeitfensters durch die Kommunikationsvorrichtung (10).


 
9. Verfahren nach einem der Ansprüche 5 bis 8,
wobei die Fehlernachricht (102; 204) ferner eine Angabe darüber umfasst, dass die Anfrage (101; 201) aufgrund einer Überlastung in Bezug auf den Dienst nicht verarbeitet wurde.
 
10. Verfahren nach einem der Ansprüche 5 bis 9,
wobei die Kennung des Dienstes auch in der Anfrage (101; 201) angegeben ist.
 
11. Knoten (100) für ein Kommunikationsnetzwerk, wobei der Knoten (100) Folgendes umfasst:

mindestens eine Schnittstelle (510) für Nachrichten (101, 102, 103, 104; 201, 204, 205, 208, 219, 220) der Steuerungsebene, die sich auf mehrere durch das Kommunikationsnetzwerk unterstützte Dienste beziehen, wobei die mehreren Dienste durch mehrere in dem Kommunikationsnetzwerk beinhaltete Anwendungsserver bereitgestellt sind; und

mindestens einen Prozessor (550), wobei der mindestens eine Prozessor (550) konfiguriert ist zum:

- Empfangen einer Anfrage (101; 201) bezüglich des einen der mehreren Dienste;

- Bestimmen, ob eine Überlastung in Bezug auf den Dienst vorliegt;

- als Reaktion auf das Bestimmen eines Nichtvorhandenseins der Überlastung in Bezug auf den Dienst, Weiterleiten der Anfrage (101; 201) zum Weiterverarbeiten durch einen entsprechenden Anwendungsserver; und

- als Reaktion auf das Bestimmen eines Vorhandenseins der Überlastung in Bezug auf den Dienst, Antworten auf die Anfrage (101; 201) mit einer Fehlernachricht (102; 204), wobei die Fehlernachricht (102; 204) angibt, dass die Anfrage (101; 201) nicht verarbeitet wurde, und wobei die Fehlernachricht (102; 204) eine Angabe eines Zeitfensters, nach dessen Ablauf die Anfrage (101; 201) erneut versucht werden kann, und eine Kennung des Dienstes, auf den sich die Anfrage (101; 201) bezieht, umfasst.


 
12. Knoten (100) nach Anspruch 11,
wobei der mindestens eine Prozessor (550) dazu konfiguriert ist, die Schritte eines Verfahrens nach einem der Ansprüche 2 bis 4 durchzuführen.
 
13. Kommunikationsvorrichtung (10), umfassend:
mindestens eine Schnittstelle (610) zum Verwenden mehrerer durch ein Kommunikationsnetzwerk unterstützte Dienste, wobei die mehreren Dienste durch mehrere in dem Kommunikationsnetzwerk beinhaltete Anwendungsserver bereitgestellt sind; und mindestens einen Prozessor (650), wobei der mindestens eine Prozessor (650) konfiguriert ist zum:

- Senden einer Anfrage (101; 201) bezüglich des einen der mehreren Dienste an das Kommunikationsnetzwerk;

- als Reaktion auf die Anfrage (101; 201) Empfangen einer Fehlernachricht (102; 204) von dem Kommunikationsnetzwerk, wobei die Fehlernachricht (102; 204) angibt, dass die Anfrage nicht verarbeitet wurde, und wobei die Fehlernachricht (102; 204) eine Angabe eines Zeitfensters, nach dessen Ablauf die Anfrage (101; 201) erneut versucht werden kann, und eine Kennung des Dienstes, auf den sich die Anfrage (101; 201) bezieht, umfasst;

- vor Ablauf des Zeitfensters Bestimmen einer Notwendigkeit, eine weitere Anfrage (103; 205) bezüglich eines der mehreren Dienste an das Kommunikationsnetzwerk zu senden; und

- in Abhängigkeit davon, ob sich die weitere Anfrage (103; 205) auf den Dienst, der in der Fehlernachricht (102; 204) angegeben ist, oder auf einen anderen der mehreren Dienste bezieht, Steuern des Sendens der weiteren Anfrage (103; 205) an das Kommunikationsnetzwerk.


 
14. Kommunikationsvorrichtung (10) nach Anspruch 13,
wobei der mindestens eine Prozessor (650) dazu konfiguriert ist, die Schritte eines Verfahrens nach einem der Ansprüche 6 bis 10 durchzuführen.
 
15. Computerprogramm, umfassend Programmcode, der durch den mindestens einen Prozessor (550) des Knotens (100) eines Kommunikationsnetzwerks ausgeführt werden soll, wobei die Ausführung des Programmcodes den mindestens einen Prozessor (550) dazu veranlasst, die Schritte eines Verfahrens nach einem der Ansprüche 1 bis 4 durchzuführen.
 
16. Computerprogramm, umfassend Programmcode, der durch den mindestens einen Prozessor (650) einer Kommunikationsvorrichtung (10), betrieben in einem Kommunikationsnetzwerk, ausgeführt werden soll, wobei die Ausführung des Programmcodes den mindestens einen Prozessor (650) dazu veranlasst, die Schritte eines Verfahrens nach einem der Ansprüche 5 bis 10 durchzuführen.
 


Revendications

1. Procédé de commande de multiples services dans un réseau de communication, le procédé comprenant :

un nœud (100), du réseau de communication, recevant une demande (101 ; 201) se rapportant à l'un des multiples services, dans lequel les multiples services sont fournis par de multiples serveurs d'application inclus dans le réseau de communication ;

le nœud (100) déterminant si une surcharge par rapport au service est présente ;

en réponse à la détermination de l'absence de la surcharge par rapport au service, le nœud (100) transférant la demande (101 ; 201) pour un traitement supplémentaire par un serveur d'application correspondant ; et

en réponse à la détermination de la présence de la surcharge par rapport au service, le nœud (100) répondant à la demande (101 ; 201) avec un message d'échec (102 ; 204), le message d'échec (102 ; 204) indiquant que la demande (101 ; 201) n'a pas été traitée, et le message d'échec (102 ; 204) comprenant une indication d'une fenêtre temporelle après laquelle la demande (101 ; 201) peut être réessayée et un identifiant du service auquel la demande (101 ; 201) se rapporte.


 
2. Procédé selon la revendication 1, dans lequel le message d'échec (102 ; 204) comprend en outre une indication que la demande (101 ; 201) n'a pas été traitée en raison d'une surcharge par rapport au service.
 
3. Procédé selon la revendication 1 ou 2, comprenant :

le nœud (100) déterminant le service auquel la demande (101 ; 201) se rapporte ;

en fonction du service auquel la demande (101 ; 201) se rapporte, le nœud (100) déterminant une liste de demandes en attente se rapportant au service ; et

le nœud (100) réalisant ladite détermination permettant de savoir si une surcharge par rapport au service est présente en fonction d'un nombre d'éléments dans la liste de demandes en attente.


 
4. Procédé selon l'une quelconque des revendications précédentes, dans lequel l'identifiant du service est également indiqué dans la demande (101 ; 201).
 
5. Procédé de commande de multiples services dans un réseau de communication, le procédé comprenant :

un dispositif de communication (10) envoyant une demande (101 ; 201) se rapportant à l'un des multiples services au réseau de communication, dans lequel les multiples services sont fournis par de multiples serveurs d'application inclus dans le réseau de communication ;

en réponse à la demande (101 ; 201), le dispositif de communication (10) recevant un message d'échec (102) à partir du réseau de communication, le message d'échec (102 ; 204) indiquant que la demande (101 ; 201) n'a pas été traitée, et le message d'échec (102 ; 204) comprenant une indication d'une fenêtre temporelle après laquelle la demande (101 ; 201) peut être réessayée et un identifiant du service auquel la demande (101 ; 201) se rapporte ;

avant l'expiration de la fenêtre temporelle, le dispositif de communication (10) déterminant un besoin d'envoyer une demande supplémentaire (103 ; 205) se rapportant à l'un des multiples services au réseau de communication ; et

en fonction de si la demande supplémentaire (103 ; 205) se rapporte au service indiqué dans le message d'échec (102 ; 204) ou à un autre des multiples services, le dispositif de communication (10) commandant l'envoi de la demande supplémentaire (103 ; 205) au réseau de communication.


 
6. Procédé selon la revendication 5, comprenant :

- en réponse à la demande supplémentaire (103 ; 205) se rapportant au service indiqué dans le message d'échec (102 ; 204), le dispositif de communication (10) envoyant la demande supplémentaire (103 ; 205) après l'expiration de la fenêtre temporelle.


 
7. Procédé selon la revendication 5 ou 6, comprenant :

- en réponse à la demande supplémentaire (103 ; 205) se rapportant au service indiqué dans le message d'échec (102 ; 204), le dispositif de communication (10) n'envoyant pas la demande supplémentaire (103 ; 204).


 
8. Procédé selon l'une quelconque des revendications 5 à 7, comprenant :

- en réponse à la demande supplémentaire (103 ; 205) se rapportant à un autre des services, le dispositif de communication (10) envoyant la demande supplémentaire (103 ; 205) avant l'expiration de la fenêtre temporelle.


 
9. Procédé selon l'une quelconque des revendications 5 à 8, dans lequel le message d'échec (102 ; 204) comprend en outre une indication que la demande (101 ; 201) n'a pas été traitée en raison d'une surcharge par rapport au service.
 
10. Procédé selon l'une quelconque des revendications 5 à 9, dans lequel l'identifiant du service est également indiqué dans la demande (101 ; 201).
 
11. Nœud (100) pour un réseau de communication, le nœud (100) comprenant :

au moins une interface (510) pour des messages de plan de commande (101, 102, 103, 104 ; 201, 204, 205, 208, 219, 220) se rapportant à de multiples services pris en charge par le réseau de communication, dans lequel les multiples services sont fournis par de multiples serveurs d'application inclus dans le réseau de communication ; et

au moins un processeur (550), l'au moins un processeur (550) étant configuré pour :

- recevoir une demande (101 ; 201) se rapportant à l'un des multiples services ;

- déterminer si une surcharge par rapport au service est présente ;

- en réponse à la détermination de l'absence de la surcharge par rapport au service, transférer la demande (101 ; 201) pour un traitement supplémentaire par un serveur d'application correspondant ; et

- en réponse à la détermination de la présence de la surcharge par rapport au service, répondre à la demande (101 ; 201) avec un message d'échec (102 ; 204), le message d'échec (102 ; 204) indiquant que la demande (101 ; 201) n'a pas été traitée, et le message d'échec (102 ; 204) comprenant une indication d'une fenêtre temporelle après laquelle la demande (101 ; 201) peut être réessayée et un identifiant du service auquel la demande (101 ; 201) se rapporte.


 
12. Nœud (100) selon la revendication 11,
dans lequel l'au moins un processeur (550) est configuré pour réaliser les étapes d'un procédé selon l'une quelconque des revendications 2 à 4.
 
13. Dispositif de communication (10), comprenant :

au moins une interface (610) pour utiliser de multiples services pris en charge par un réseau de communication, dans lequel les multiples services sont fournis par de multiples serveurs d'application inclus dans le réseau de communication ; et

au moins un processeur (650), l'au moins un processeur (650) étant configuré pour :

- envoyer une demande (101 ; 201) se rapportant à l'un des multiples services au réseau de communication ;

- en réponse à la demande (101 ; 201), recevoir un message d'échec (102 ; 204) à partir du réseau de communication, le message d'échec (102 ; 204) indiquant que la demande n'a pas été traitée, et le message d'échec (102 ; 204) comprenant une indication d'une fenêtre temporelle après laquelle la demande (101 ; 201) peut être réessayée et un identifiant du service auquel la demande (101 ; 201) se rapporte ;

- avant l'expiration de la fenêtre temporelle, déterminer un besoin d'envoyer une demande supplémentaire (103 ; 205) se rapportant à l'un des multiples services au réseau de communication ; et

- en fonction de si la demande supplémentaire (103 ; 205) se rapporte au service indiqué dans le message d'échec (102 ; 204) ou à un autre des multiples services, commander l'envoi de la demande supplémentaire (103 ; 205) au réseau de communication.


 
14. Dispositif de communication (10) selon la revendication 13, dans lequel l'au moins un processeur (650) est configuré pour réaliser les étapes d'un procédé selon l'une quelconque des revendications 6 à 10.
 
15. Programme informatique comprenant un code de programme qui doit être exécuté par au moins un processeur (550) d'un nœud (100) d'un réseau de communication, dans lequel l'exécution du code de programme amène l'au moins un processeur (550) à réaliser des étapes d'un procédé selon l'une quelconque des revendications 1 à 4.
 
16. Programme informatique comprenant un code de programme qui doit être exécuté par au moins un processeur (650) d'un dispositif de communication (10) exploité dans un réseau de communication, dans lequel l'exécution du code de programme amène l'au moins un processeur (650) à réaliser des étapes d'un procédé selon l'une quelconque des revendications 5 à 10.
 




Drawing























Cited references

REFERENCES CITED IN THE DESCRIPTION



This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

Patent documents cited in the description




Non-patent literature cited in the description