WO2010121645A1 - Invocation et révocation de services de priorité - Google Patents

Invocation et révocation de services de priorité Download PDF

Info

Publication number
WO2010121645A1
WO2010121645A1 PCT/EP2009/054708 EP2009054708W WO2010121645A1 WO 2010121645 A1 WO2010121645 A1 WO 2010121645A1 EP 2009054708 W EP2009054708 W EP 2009054708W WO 2010121645 A1 WO2010121645 A1 WO 2010121645A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
priority
user
modification
service flow
Prior art date
Application number
PCT/EP2009/054708
Other languages
English (en)
Inventor
Wei Hua Zhou
Shun Liang Zhang
Yi Zhang
Original Assignee
Nokia Siemens Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Siemens Networks Oy filed Critical Nokia Siemens Networks Oy
Priority to PCT/EP2009/054708 priority Critical patent/WO2010121645A1/fr
Publication of WO2010121645A1 publication Critical patent/WO2010121645A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • 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/80—Actions related to the user profile or the type of traffic
    • H04L47/808—User-type aware
    • 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
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102—Entity profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/61—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources taking into account QoS or priority requirements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H04W12/082—Access security using revocation of authorisation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/50—Connection management for emergency connections

Definitions

  • the present invention generally relates to priority service invocation and revocation. Specifically, the present invention for example relates to the invocation and/or revocation of priority services in public communication networks.
  • emergency services are only a non-limiting example for a priority service.
  • the subject-matter of the present specification is related to priority services of any kind.
  • Emergency Telecommunication Services are currently defined for fixed/mobile communication systems (like for example PSTN (Public Switched Telephone Network) , GSM (Global System for Mobile Communication) , GPRS (General Packet Radio Service) , UMTS (Universal Mobile Telecommunication System) or the like) .
  • PSTN Public Switched Telephone Network
  • GSM Global System for Mobile Communication
  • GPRS General Packet Radio Service
  • UMTS Universal Mobile Telecommunication System
  • An Emergency Telecommunication Service enables National Security/Emergency Preparedness (NS/EP) users (e.g., commander in chief, federal emergency management, national security staff, CEOs of key financial institution, and first responders leadership) to make priority calls/sessions using the public networks during a network congestion or partial network outage condition, which may be caused by natural disasters (e.g., hurricanes) or man-made disasters (e.g., terrorist attacks) . Namely, due to such natural or man-made disasters, network equipment could be destroyed so that available resources are reduced and/or the amount of traffic could rise, thus leading to a network congestion or partial network outage condition.
  • natural disasters e.g., hurricanes
  • man-made disasters e.g., terrorist attacks
  • ETS representing a priority
  • NS/EP users' calls/sessions are treated in a prioritized manner so as to ensure such priority calls/sessions be established in spite of the general shortage of available resources.
  • SIP Session Initiation Protocol
  • public networks having no standardized means for implementing such emergency services or other priority services, there is no way for prioritizing specific users and/or specific calls, sessions, or the like as compared with other users, calls, sessions, or the like.
  • networks include WiMAX (Worldwide Interoperability for Microwave Access) according to IEEE 802.16 standards and LTE/SAE (LTE: Long Term Evolution, SAE: Service Architecture Evolution) according to 3GPP (Third Generation Partnership Project) standards .
  • WiMAX Worldwide Interoperability for Microwave Access
  • LTE/SAE Long Term Evolution
  • SAE Service Architecture Evolution
  • a web portal may be provided dedicated for emergency data applications, said web portal acting as sort of access point for NS/EP users and being accessible for example via submitting a specific message via HTTP/HTTPS (HTTP: Hypertext Transfer Protocol, HTTPS: Hypertext Transfer Protocol Secure) .
  • HTTP/HTTPS Hypertext Transfer Protocol
  • HTTPS Hypertext Transfer Protocol Secure
  • the present invention and its embodiments are made to provide for a feasible solution for invoking and/or revoking priority services in public communication networks .
  • a method comprising receiving, from a priority user, a request for invoking or revoking a priority data service for a data application in a public communication network, and invoking or revoking the requested priority data service on the basis of a priority status and a service profile of the priority user in accordance with an applicable service flow procedure.
  • said invoking the requested priority data service comprises initiating an authentication of the priority user at an authentication entity, and acquiring the priority status and the service profile of the priority user and an indication on the applicable service flow procedure from the authentication entity,
  • said invoking the requested priority data service comprises requesting a service flow creation or modification for the priority data service to be invoked in accordance with the applicable service flow procedure at an authentication or policy control entity,
  • said requesting comprises sending, to the authentication entity, a dynamic quality-of-service service creation request including an identity of the priority user,
  • said requesting comprises sending, to the policy control entity, an application and/or service information including the priority status and the service profile of the priority user,
  • said revoking the requested priority data service comprises requesting a service flow deletion or modification for the priority data service to be revoked in accordance with the applicable service flow procedure at an authentication or policy control entity,
  • said requesting comprises sending, to the authentication entity, a dynamic quality-of-service service deletion request including an identity of the priority user,
  • said requesting comprises sending, to the policy control entity, an application and/or service information including the priority status and the service profile of the priority user, - said method is operable at a priority service authentication server,
  • the priority data service is one of an emergency telecommunication service and a multimedia priority service, and/or
  • the public communication network is one of a network complying with IEEE 802.16 standards and a network complying with 3GPP LTE/SAE standards.
  • an apparatus comprising a priority service processor configured to receive, from a priority user, a request for invoking or revoking a priority data service for a data application in a public communication network, and invoke or revoke the requested priority data service on the basis of a priority status and a service profile of the priority user in accordance with an applicable service flow procedure.
  • said priority service processor for invoking the requested priority data service, is configured to initiate an authentication of the priority user at an authentication entity, and acquire the priority status and the service profile of the priority user and an indication on the applicable service flow procedure from the authentication entity,
  • said priority service processor for invoking the requested priority data service, is configured to request a service flow creation or modification for the priority data service to be invoked in accordance with the applicable service flow procedure at an authentication or policy control entity, - said priority service processor, for requesting said service flow creation or modification, is configured to send, to the authentication entity, a dynamic quality-of- service service creation request including an identity of the priority user,
  • said priority service processor for requesting said service flow creation or modification, is configured to send, to the policy control entity, an application and/or service information including the priority status and the service profile of the priority use,
  • said priority service processor for revoking the requested priority data service, is configured to request a service flow deletion or modification for the priority data service to be revoked in accordance with the applicable service flow procedure at an authentication or policy control entity,
  • said priority service processor for requesting said service flow deletion or modification, is configured to send, to the authentication entity, a dynamic quality-of- service service deletion request including an identity of the priority user,
  • said priority service processor for requesting said service flow deletion or modification, is configured to send, to the policy control entity, an application and/or service information including the priority status and the service profile of the priority user,
  • said apparatus is operable as a priority service authentication server
  • the priority data service is one of an emergency telecommunication service and a multimedia priority service, and/or
  • the public communication network is one of a network complying with IEEE 802.16 standards and a network complying with 3GPP LTE/SAE standards.
  • a computer program product comprising program code means being arranged, when run on a processor of an apparatus, to perform the method according to the first aspect and/or any one of the further developments or modifications thereof.
  • a method comprising authenticating a priority user requesting an invocation or revocation of a priority data service for a data application in a public communication network upon initiation from a priority service authentication server, and providing a priority status and a service profile of the priority user and an indication on an applicable service flow procedure to the priority service authentication server.
  • the method comprises triggering a service flow creation or modification for an invocation of the requested priority data service in accordance with the applicable service flow procedure, - said triggering comprises receiving, from the priority service authentication server, a dynamic quality-of-service service creation request including an identity of the priority user, and sending, to an access service node, a dynamic service flow creation or modification request including the priority status and the service profile of the priority user,
  • the method comprises triggering a service flow deletion or modification for a revocation of the requested priority data service in accordance with the applicable service flow procedure, - said triggering comprises receiving, from the priority service authentication server, a dynamic quality-of-service service deletion request including an identity of the priority user, and sending, to an access service node, a dynamic service flow deletion or modification request including the priority status and the service profile of the priority user,
  • the method is operable at an authentication, authorization and accounting server, - the priority data service is one of an emergency telecommunication service and a multimedia priority service, and/or
  • the public communication network is one of a network complying with IEEE 802.16 standards and a network complying with 3GPP LTE/SAE standards.
  • an apparatus comprising: an authenticating unit configured to authenticate a priority user requesting an invocation or revocation of a priority data service for a data application in a public communication network upon initiation from a priority service authentication server, and a data processor configured to provide a priority status and a service profile of the priority user and an indication on an applicable service flow procedure to the priority service authentication server.
  • the apparatus comprises a priority service flow processor being configured to trigger a service flow creation or modification for an invocation of the requested priority data service in accordance with the applicable service flow procedure, - said priority service flow processor, for triggering, is configured to receive, from the priority service authentication server, a dynamic quality-of-service service creation request including an identity of the priority user, and send, to an access service node, a dynamic service flow creation or modification request including the priority status and the service profile of the priority user,
  • the apparatus comprises a priority service flow processor being configured to trigger a service flow deletion or modification for a revocation of the requested priority data service in accordance with the applicable service flow procedure,
  • said priority service flow processor for triggering, is configured to receive, from the priority service authentication server, a dynamic quality-of-service service deletion request including an identity of the priority user, and send, to an access service node, a dynamic service flow deletion or modification request including the priority status and the service profile of the priority user,
  • said apparatus is operable as an authentication, authorization and accounting server
  • the priority data service is one of an emergency telecommunication service and a multimedia priority service, and/or
  • the public communication network is one of a network complying with IEEE 802.16 standards and a network complying with 3GPP LTE/SAE standards.
  • a computer program product comprising program code means being arranged, when run on a processor of an apparatus, to perform the method according to the fourth aspect and/or any one of the further developments or modifications thereof.
  • a method comprising: triggering at least one of a service flow creation, deletion and modification for an invocation or revocation of a priority data service for a data application of a requesting priority user in a public communication network upon initiation from a priority service authentication server, said triggering being based on a priority status and a service profile of the priority user and an applicable service flow procedure.
  • said service flow creation or modification comprises receiving, from the priority service authentication server, an application and/or service information including the priority status and the service profile of the priority user, and sending, to an access service node, a policy and charging rule provision message including the priority status and the service profile of the priority user for requesting creation or modification of an appropriate service flow,
  • said service flow deletion or modification comprises receiving, from the priority service authentication server, an application and/or service information including the priority status and the service profile of the priority user, and sending, to an access service node, a policy and charging rule provision message including the priority status and the service profile of the priority user for requesting deletion or modification of an appropriate service flow, - said method is operable at a policy distribution function and/or a policy and charging rule function,
  • the priority data service is one of an emergency telecommunication service and a multimedia priority service, and/or
  • the public communication network is one of a network complying with IEEE 802.16 standards and a network complying with 3GPP LTE/SAE standards.
  • an apparatus comprising a priority service flow processor configured to trigger at least one of a service flow creation, deletion and modification for an invocation or revocation of a priority data service for a data application of a requesting priority user in a public communication network upon initiation from a priority service authentication server, said triggering being based on a priority status and a service profile of the priority user and an applicable service flow procedure.
  • said priority service flow processor for service flow creation or modification, is configured to receive, from the priority service authentication server, an application and/or service information including the priority status and the service profile of the priority user, and send, to an access service node, a policy and charging rule provision message including the priority status and the service profile of the priority user for requesting creation or modification of an appropriate service flow,
  • said service flow priority processor for service flow deletion or modification, is configured to receive, from the priority service authentication server, an application and/or service information including the priority status and the service profile of the priority user, and send, to an access service node, a policy and charging rule provision message including the priority status and the service profile of the priority user for requesting deletion or modification of an appropriate service flow,
  • said apparatus is operable as a policy distribution function and/or a policy and charging rule function
  • the priority data service is one of an emergency telecommunication service and a multimedia priority service, and/or
  • the public communication network is one of a network complying with IEEE 802.16 standards and a network complying with 3GPP LTE/SAE standards.
  • a computer program product comprising program code means being arranged, when run on a processor of an apparatus, to perform the method according to the seventh aspect and/or any one of the further developments or modifications thereof.
  • exemplary embodiments of the present invention there is provided support for priority services (e.g. Emergency Telecommunication Service ETS, Multimedia Priority Service MPS, or the like) in public communication networks, such as for example WiMAX or LTE/SAE access and/or core networks.
  • priority services e.g. Emergency Telecommunication Service ETS, Multimedia Priority Service MPS, or the like
  • public communication networks such as for example WiMAX or LTE/SAE access and/or core networks.
  • exemplary embodiments of the present invention may provide a priority access for a priority service (e.g. ETS, MPS, etc.) in public communication networks, such as for example WiMAX or LTE/SAE access and/or core networks.
  • an appropriate invocation and/or revocation of a priority data service for a data application in public communication networks such as for example WiMAX or LTE/SAE access and/or core networks
  • data services may be invoked and/or revoked for all data applications (e.g. web access, email, short message service SMS, Internet Protocol based multimedia IM, file transfer, or the like) of a prioritized user, such as a NS/EP user, in a prioritized manner.
  • the architecture, structures and operations of the underlying network environment e.g. WiMAX, LTE/SAE, etc.
  • the underlying network environment e.g. WiMAX, LTE/SAE, etc.
  • Figure 1 shows a schematic block diagram of an arrangement of a first implementation example according to exemplary embodiments of the present invention
  • Figure 2 shows a signaling diagram of an exemplary priority service invocation procedure for the arrangement of Figure 1 according to exemplary embodiments of the present invention
  • Figure 3 shows a signaling diagram of an exemplary priority service revocation procedure for the arrangement of Figure 1 according to exemplary embodiments of the present invention
  • Figure 4 shows a schematic block diagram of an arrangement of a second implementation example according to exemplary embodiments of the present invention
  • Figure 5 shows a signaling diagram of an exemplary priority service invocation procedure for the arrangement of Figure 4 according to exemplary embodiments of the present invention
  • Figure 6 shows a signaling diagram of an exemplary priority service revocation procedure for the arrangement of Figure 4 according to exemplary embodiments of the present invention
  • Figure 7 shows a flowchart of an exemplary method of a priority service authentication server according to exemplary embodiments of the present invention
  • Figure 8 shows a flowchart of an exemplary method of an authentication entity according to exemplary embodiments of the present invention
  • Figure 9 shows a flowchart of an exemplary method of a policy control entity according to exemplary embodiments of the present invention
  • Figure 10 shows a schematic block diagram of an exemplary configuration of a priority service authentication server according to exemplary embodiments of the present invention
  • Figure 11 shows a schematic block diagram of an exemplary configuration of an authentication entity according to exemplary embodiments of the present invention
  • Figure 12 shows a schematic block diagram of an exemplary configuration of a policy control entity according to exemplary embodiments of the present invention.
  • the present invention and its embodiments are mainly described in relation to IEEE specifications being used as non-limiting examples for certain exemplary network configurations.
  • a WiMAX network according to IEEE 802.16 standards is used as a non- limiting example in this regard.
  • 3GPP specifications and for example a LTE/SAE network could be equally used as well.
  • an emergency service in particular an emergency telecommunication service ETS, is used as a non-limiting example for a priority service, while for example a multimedia priority service MPS could be equally used as well.
  • ETS emergency telecommunication service
  • MPS multimedia priority service
  • the description of the exemplary embodiments given herein specifically refers to terminology which is directly related thereto. Such terminology is only used in the context of the presented non-limiting examples, and does naturally not limit the invention in any way. Rather, any other network configuration or access implementation may also be utilized as long as compliant with the features described herein .
  • AAA authentication, authorization and accounting
  • Figure 1 shows a schematic block diagram of an arrangement of a first implementation example according to exemplary embodiments of the present invention.
  • a mobile station MS representing a priority user is connected with an access service node ASN via a Rl interface and with an ETS authentication server representing a priority service authentication server via an Internet interface
  • the access service node ASN is connected with an AAA server representing an authentication entity via a R3 interface
  • the AAA server is connected with the ETS authentication server via a Re interface.
  • Figure 1 may have the one or more of the following properties. Details are set out below in connection with Figures 2, 3, and 7 to 12.
  • the Re interface i.e. the AAA server and the ETS authentication server, shall be able to support ETS user authentication.
  • the ETS authentication server may access the AAA server to get necessary information for ETS user authentication.
  • the Re interface i.e. the AAA server and the ETS authentication server, shall be able to support to return an appropriate ETS SF (service flow) creation, deletion or modification method from the AAA server to the ETS authentication server, which will be used by the ETS authentication server to decide how to and to initiate ETS SF creation or modification for a current ETS user.
  • ETS SF service flow
  • the Re interface i.e. the AAA server and the ETS authentication server, shall be able to support a dynamic QoS (quality-of-service) service creation/ deletion/ modification.
  • the ETS authentication server may initiate a SF creation, deletion or modification by a dynamic QoS service request to the AAA server for an ETS data (transport) service.
  • the AAA server may trigger the ASN to create, delete or modify at least one dynamic SF with the ETS-specific priority by way of a network-initiated SF creation, deletion or modification procedure, i.e. the appropriate service flow procedure.
  • the R3 interface i.e. the AAA server and the ETS authentication server, is enhanced to support an ETS service, i.e. an ETS data (transport) service.
  • Both the Re and R3 interfaces shall support "ETS user priority” representing a user' s priority status and "ETS QoS profile” representing a user' s service profile on related messages on the respective interface.
  • Figure 2 shows a signaling diagram of an exemplary priority service invocation procedure for the arrangement of Figure 1, i.e. an AAA-based implementation, according to exemplary embodiments of the present invention.
  • ETS emergency telecommunication service
  • An ETS service user represented by his/her user equipment or mobile station MS submits an invocation request for an ETS data application towards an ETS authentication server via an anchor access service node ASN.
  • the ETS authentication server upon receipt of the invocation request, sends an access request to an AAA server to authenticate whether the requesting user has an ETS subscription, i.e. whether the user is authenticated for ETS application invocation.
  • the ETS user authentication is done.
  • the AAA server sends an access response to the ETS authentication server to notify the authentication results of this ETS user, which includes ETS user priority, ETS QoS (quality-of- service) profile and ETS SF (service flow) creation method to be used. Otherwise, i.e. if authentication yields a negative result, the AAA server sends an access reject to the ETS authentication server to reject this user to access to the requested ETS service.
  • the ETS authentication server notifies the ETS user that it is rejected, and terminates the present invocation procedure.
  • the ETS authentication server decides (not shown) how to initiate ETS SF creation based on the applicability indication received from the AAA server. Accordingly, the ETS authentication server sends a dynamic QoS service creation request to the AAA server, which includes ETS user identity (and not ETS user priority and ETS QoS profile) , since the AAA server itself knows ETS priority and ETS QoS profile already.
  • the AAA server then triggers the anchor ASN for SF creation for the requested ETS by sending a dynamic SF creation request message, which shall also include ETS priority and ETS QoS profile.
  • the ASN acknowledges to the AAA server the result of the SF creation.
  • the AAA server acknowledges to the ETS authentication server the result of the dynamic QoS service creation.
  • the ETS authentication server notifies the ETS user whether its ETS data application invocation is success or not.
  • operation 2 represents an initiation of a user authentication
  • operation 6 represents a request for service flow creation.
  • ETS priority and ETS QoS profile represent non-limiting examples for user priority status and user service profile.
  • SF creation is mentioned above, SF modification is equally applicable.
  • Figure 3 shows a signaling diagram of an exemplary priority service revocation procedure for the arrangement of Figure 1, i.e. an AAA-based implementation, according to exemplary embodiments of the present invention
  • ETS emergency telecommunication service
  • An ETS service user represented by his/her user equipment or mobile station MS submits a revocation request for an ETS data application towards an ETS authentication server via an anchor access service node ASN.
  • the ETS authentication server sends a dynamic QoS service delete message to the AAA server.
  • the AAA server sends also a dynamic SF delete message to the ASN to ask it to delete or modify a corresponding ETS-specific SF.
  • the ASN deletes the corresponding ETS SF or modifies it (when modification instead of deletion is requested, which is equally applicable) by removing or altering its ETS indicator to preserve it for further usage.
  • the ASN acknowledges to the AAA server that the ETS SF is deleted or modified.
  • the AAA server acknowledges to the ETS authentication server that the ETS data application revocation is done.
  • the ETS authentication server responds to the ETS user that its ETS data application revocation is done.
  • the parameters in the individual messages exchanged are evident from the illustration of Figure 3.
  • an exemplary priority service revocation procedure may also comprise user authentication and information provisioning operations between the ETS authentication server and the AAA server (similar to those illustrated in steps 2 to 4 of Figure 2) .
  • PCC policy and charging control
  • Figure 4 shows a schematic block diagram of an arrangement of a second implementation example according to exemplary embodiments of the present invention.
  • a mobile station MS representing a priority user is connected with an access service node ASN via a Rl interface and with an ETS authentication server representing a priority service authentication server via an Internet interface
  • the access service node ASN is connected with a PDF/PCRF element (PDF: policy distribution function, PCRF: policy and charging rule function) representing a policy control entity via a PCC-R3-P interface
  • the PDF/PCRF element is connected with the ETS authentication server via a Rx interface.
  • the ETS authentication server is also connected with an AAA server.
  • Figure 4 may have the one or more of the following properties. Details are set out below in connection with Figures 5 to 12.
  • the interface between the AAA server and the ETS authentication server shall be able to support ETS user authentication.
  • the ETS authentication server may access the AAA server to get necessary information for ETS user authentication. It shall be able to support to return an appropriate ETS SF (service flow) creation, deletion or modification method from the AAA server to the ETS authentication server, which will be used by the ETS authentication server to decide how to and to initiate ETS SF creation or modification for a current ETS user.
  • ETS SF service flow
  • the Rx interface i.e. the PDF/PCRF element and the ETS authentication server, shall be able to support a service creation/ deletion/ modification.
  • the ETS authentication server may initiate a SF creation, deletion or modification by application and/or service information transmittal to the PDF/PCRF element for an ETS data (transport) service.
  • the PDF/PCRF element may trigger the ASN to create, delete or modify at least one dynamic SF with the ETS-specific priority by way of a network- initiated SF creation, deletion or modification procedure, i.e. the appropriate service flow procedure.
  • the Rx interface i.e. the PDF/PCRF element and the ETS authentication server, is enhanced to support an ETS service, i.e. an ETS data (transport) service.
  • Both the Rx and PCC-R3-P interfaces shall support "ETS user priority” representing a user' s priority status and "ETS QoS profile” representing a user' s service profile on related messages on the respective interface.
  • Figure 5 shows a signaling diagram of an exemplary priority service invocation procedure for the arrangement of Figure 4, i.e. a PCC-based implementation, according to exemplary embodiments of the present invention
  • An ETS service user represented by his/her user equipment or mobile station MS submits an invocation request for an ETS data application towards an ETS authentication server via an anchor access service node ASN.
  • the ETS authentication server upon receipt of the invocation request, sends an access request to an AAA server to authenticate whether the requesting user has an ETS subscription, i.e. whether the user is authenticated for ETS application invocation.
  • the AAA server sends an access response to the ETS authentication server to notify the authentication results of this ETS user, which includes ETS user priority, ETS QoS (quality-of- service) profile and ETS SF (service flow) creation method to be used. Otherwise, i.e. if authentication yields a negative result, the AAA server sends an access reject to the ETS authentication server to reject this user to access to the requested ETS service.
  • the ETS authentication server notifies the ETS user that it is rejected, and terminates the present invocation procedure.
  • the ETS authentication server decides (not shown) how to initiate ETS SF creation based on the applicability indication received from the AAA server. Accordingly, the sends application and/or service Information to the
  • PDF/PCRF which shall include ETS priority and ETS QoS profile .
  • the PDF/PCRF then triggers the anchor ASN for SF creation or modification for the requested ETS by sending a policy and charging rule provision message, which shall include ETS priority and ETS QoS profile.
  • One new SF is created or one existing SF is modified at/by the ASN to support the requested ETS service.
  • the ETS authentication server notifies the ETS user whether its ETS data application invocation is success or not .
  • operation 2 represents an initiation of a user authentication
  • operation 6 represents a request for service flow creation or modification.
  • the above-mentioned information ETS priority and ETS QoS profile represent non-limiting examples for user priority status and user service profile .
  • Figure 6 shows a signaling diagram of an exemplary priority service revocation procedure for the arrangement of Figure 4, i.e. a PCC-based implementation, according to exemplary embodiments of the present invention.
  • ETS emergency telecommunication service
  • An ETS service user represented by his/her user equipment or mobile station MS submits a revocation request for ETS data application towards an ETS authentication server via an anchor access service node ASN.
  • the ETS authentication server sends application and/or service information to the PDF/PCRF to notify which dynamic QoS service is to be deleted or modified.
  • the PDF/PCRF sends a policy and charging rule provision message to the ASN to ask the ASN to delete or modify a corresponding ETS-specific SF.
  • the ASN deletes the corresponding ETS SF or modifies it (when modification instead of deletion is requested, which is equally applicable) by removing or altering its ETS indicator to preserve it for further usage.
  • the PDF/PCRF acknowledges to the ETS authentication server that the ETS data application revocation is done.
  • the ETS authentication server responds to the ETS user that its ETS data application revocation is done.
  • an exemplary priority service revocation procedure may also comprise user authentication and information provisioning operations between the ETS authentication server and the AAA server (similar to those illustrated in steps 2 to 4 of Figure 5) .
  • FIG 7 shows a flowchart of an exemplary method of a priority service authentication server according to exemplary embodiments of the present invention. The thus depicted and described method may for example be carried out by the ETS authentication server according to any one of Figures 1 to 3 or 4 to 6.
  • a method comprises the operations of receiving, from a priority user, a request for invoking or revoking a priority data service (e.g. a priority data transport service) for a data application in a public communication network, and invoking or revoking the requested priority data service on the basis of a priority status and a service profile of the priority user in accordance with an applicable service flow procedure.
  • a priority data service e.g. a priority data transport service
  • the receiving operation may be accomplished by a transceiver of the executing apparatus
  • the invoking/revoking operation may be accomplished by a dedicated means or device, for example by a priority service processor.
  • a priority service authentication server may carry out the following operations.
  • the priority service authentication server may receive, from a priority user, such as e.g. an ETS user, a request for invoking or revoking a priority data transport service (e.g. a priority data transport service) for a data application in a public communication network, such as e.g. an ETS data application invocation/revocation request (like in operation 1 of Figures 2, 3, 5 and 6) .
  • a priority user such as e.g. an ETS user
  • a request for invoking or revoking a priority data transport service e.g. a priority data transport service
  • a data application invocation/revocation request like in operation 1 of Figures 2, 3, 5 and 6 .
  • the requested priority data service is invoked (or activated) on the basis of a priority status, such as e.g. ETS priority, and a service profile, such as e.g. ETS QoS profile, of the priority user in accordance with an applicable service flow procedure.
  • a priority status such as e.g. ETS priority
  • a service profile such as e.g. ETS QoS profile
  • the invocation operation may comprise one or more of a user authentication, an information acquisition and a service flow creation or modification request.
  • the priority service authentication server may initiate an authentication of the priority user at an authentication entity, such as the AAA server of Figure 1 or 3. Such initiation may for example comprise the sending of an access request to the AAA server (like in operation 2 of Figures 2 and 5) .
  • it is determined whether the initiated user authentication has been successful which may be accomplished by determining whether an access response or an access reject is received from the AAA server (like in operations 3 and 4 of Figures 2 and 5) .
  • the priority service authentication server may in step S713 acquire information necessary for the further invocation procedure, such as priority status and service profile of the priority user and an indication on the applicable service flow procedure.
  • Such information acquisition may for example comprise the receiving of a message including respective information from the authentication entity, such as the AAA server (like in operation 4 of Figures 2 and 5) .
  • the priority service authentication server may decide on the SF procedure to be used, and may in step S714 request a service flow creation or modification for the priority data service to be invoked accordingly.
  • Such requesting may for example comprise a sending of a corresponding message or corresponding information to an authentication entity, such as the AAA server of Figures 1 and 2 (like in operation 6 of Figure 2), or a policy control entity, such the PDF/PCRF element of Figures 4 and 5 (like in operation 6 of Figure 5) .
  • the priority service authentication server may notify the requesting priority user about the success or non-success of the requested priority service invocation (like in operations 5 and 11 of Figures 2 and 5) , wherein a non-success may be due to a failed authentication, i.e. NO in step S712, or a failed service flow creation or modification, or the like.
  • the requested priority data service is revoked (or deactivated) on the basis of a priority status, such as e.g. ETS priority, and a service profile, such as e.g. ETS QoS profile, of the priority user in accordance with an applicable service flow procedure.
  • a priority status such as e.g. ETS priority
  • a service profile such as e.g. ETS QoS profile
  • the revocation operation may comprise a service flow deletion or modification request.
  • the priority service authentication server may request a service flow deletion or modification for the priority data service to be revoked accordingly.
  • requesting may for example comprise a sending of a corresponding message or corresponding information to an authentication entity, such as the AAA server of Figures 1 and 3 (like in operation 2 of Figure 3) , or a policy control entity, such the PDF/PCRF element of Figures 4 and 6 (like in operation 2 of Figure 6) .
  • the priority service authentication server may notify the requesting priority user about the success or non-success of the requested priority service revocation (like in operation 7 of Figures 3 and 6) , wherein a non-success may be due to a failed service flow deletion or modification, or the like.
  • FIG 8 shows a flowchart of an exemplary method of an authentication entity according to exemplary embodiments of the present invention.
  • the thus depicted and described method may for example be carried out by the AAA server according to any one of Figures 1 to 3 or 4 to 6.
  • a method comprises the operations of authenticating a priority user requesting an invocation or revocation of a priority data transport service (e.g. a priority data transport service) for a data application in a public communication network upon initiation from a priority service authentication server, and providing a priority status and a service profile of the priority user and an indication on an applicable service flow procedure to the priority service authentication server.
  • a priority data transport service e.g. a priority data transport service
  • the authenticating operation may be accomplished by an authenticating unit or authenticator of the executing apparatus, and the information providing operation may be accomplished by a dedicated means or device, for example by a data processor and/or database or memory means.
  • an authentication entity may carry out the following operations .
  • the authentication entity may authenticate a priority user, such as e.g. an ETS user, requesting an invocation or revocation of a priority data service (e.g. a priority data transport service) for a data application in a public communication network, such as e.g. an ETS data application invocation/revocation request, upon initiation from a priority service authentication server, such as e.g. the ETS authentication server, and may respond to the priority service authentication server by way of an authentication success indication (like in operations 3 and 4 of Figures 2 and 5) .
  • the authentication entity may provide the priority service authentication server with information necessary for the further invocation/revocation procedure, such as priority status and service profile of the priority user and an indication on the applicable service flow procedure (like in operation 4 of Figures 2 and 5) .
  • the above operations are common to authentication entities of various implementations according to exemplary embodiments of the present invention.
  • the below operations may be carried out by authentication entities of certain implementations according to exemplary embodiments of the present invention, which is why they are illustrated as being optional by way of dashed lines.
  • an authentication entity according to exemplary embodiments of the present invention may carry out the below operations in an AAA-based implementation.
  • the authentication entity may trigger a service flow creation or modification for an invocation of the requested priority data service in accordance with the applicable service flow procedure.
  • triggering may for example comprise the sending of a corresponding message or corresponding information (like in operation 7 of Figure 2), which may for example be induced by a receiving of a corresponding request from the priority service authentication server, such as the ETS authentication server (like in operation 6 of Figure 2) .
  • the authentication entity may acknowledge the successful or non-successful completion of the requested service flow creation or modification to the requesting priority service authentication server (like in operation 10 of Figure 2) .
  • the authentication entity may trigger a service flow deletion or modification for a revocation of the requested priority data service in accordance with the applicable service flow procedure.
  • triggering may for example comprise the sending of a corresponding message or corresponding information (like in operation 3 of Figure 3), which may for example be induced by a receiving of a corresponding request from the priority service authentication server, such as the ETS authentication server (like in operation 2 of Figure 3) .
  • the authentication entity may acknowledge the successful or non-successful completion of the requested service flow deletion or modification to the requesting priority service authentication server (like in operation 6 of Figure 3) .
  • the above triggering operation (s) may be accomplished by a dedicated means or device, for example by a priority service flow processor.
  • Figure 9 shows a flowchart of an exemplary method of a policy control entity according to exemplary embodiments of the present invention. The thus depicted and described method may for example be carried out by the PDF/PCRF element according to any one of Figures 4 to 6.
  • a method comprises the operations of triggering at least one of a service flow creation, deletion and modification for an invocation or revocation of a priority data service (e.g. a priority data transport service) for a data application of a requesting priority user in a public communication network upon initiation from a priority service authentication server, said triggering being based on a priority status and a service profile of the priority user and an applicable service flow procedure.
  • a priority data service e.g. a priority data transport service
  • the triggering operation may be accomplished by a dedicated means or device, for example by a priority service flow processor.
  • a policy control entity may carry out the following operations.
  • a policy control entity may carry out the below operations in a PCC- based implementation.
  • the operations carried out by a policy control entity in a PCC-based implementation are comparable to those carried out by an authentication entity in an AAA-based implementation, as depicted in the bottom part with dashed lines in Figure 8.
  • the policy control entity may trigger a service flow creation or modification for an invocation of the requested priority data service in accordance with the applicable service flow procedure.
  • triggering may for example comprise the sending of a corresponding message or corresponding information (like in operation 7 of Figure 5) , which may for example be induced by a receiving of a corresponding request from the priority service authentication server, such as the ETS authentication server (like in operation 6 of Figure 5) .
  • the policy control entity may acknowledge the successful or non-successful completion of the requested service flow creation or modification to the requesting priority service authentication server (like in operation 10 of Figure 5) .
  • the policy control entity may trigger a service flow deletion or modification for an invocation of the requested priority data service in accordance with the applicable service flow procedure.
  • triggering may for example comprise the sending of a corresponding message or corresponding information (like in operation 3 of Figure 6) , which may for example be induced by a receiving of a corresponding request from the priority service authentication server, such as the ETS authentication server (like in operation 2 of Figure 6) .
  • the policy control entity may acknowledge the successful or non-successful completion of the requested service flow deletion or modification to the requesting priority service authentication server (like in operation 6 of Figure 6) .
  • an access entity such as e.g. an (anchor) access service node
  • an access entity is configured to be enabled for cooperating in the above- outlined procedures performed by the other entities in an appropriate manner.
  • an access entity according to exemplary embodiments of the present invention may be adapted for supporting a Rl interface as well as an accordingly enhanced R3 and/or PCC-R3-P interface, as depicted in Figures 1 and 4.
  • an access entity may properly participate in and contribute to any kind of message or information transfer in any stage of the above procedures, and particularly in/to service flow creation, deletion and/or modification, as triggered by an authentication entity or a policy control entity (like in operations 7 to 9 of Figures 2 and 5 or in operations 3 to 5 of Figures 3 and 6) .
  • An access entity according to exemplary embodiments of the present invention thus comprises accordingly configured means, devices, processors, or the like for achieving the above effects.
  • the solid line blocks are basically configured to perform the basic operations.
  • the entirety of solid/dashed line blocks are basically configured to perform the methods and operations as described above, respectively.
  • the individual blocks are meant to illustrate respective functional blocks implementing a respective function, process or procedure, respectively.
  • Such functional blocks are implementation- independent, i.e. may be implemented by means of any kind of hardware or software, respectively.
  • the lines interconnecting individual blocks are meant to illustrate an operational coupling there-between, which on the one hand is implementation-independent (e.g. wired or wireless) and on the other hand may also comprise an arbitrary number of intermediary functional entities not shown .
  • Figure 10 shows a schematic block diagram of an exemplary configuration of a priority service authentication server according to exemplary embodiments of the present invention.
  • the thus depicted and described apparatus may for example be (a part of) the ETS authentication server according to any one of Figures 1 to 3 or 4 to 6.
  • an apparatus comprises a priority service processor.
  • the priority service processor may be configured to carry out or to control a procedure according to Figure 7. Namely, the priority service processor may be configured to receive, from a priority user, a request for invoking or revoking a priority data service (e.g. a priority data transport service) for a data application in a public communication network, and to invoke or revoke the requested priority data service on the basis of a priority status and a service profile of the priority user in accordance with an applicable service flow procedure, as well as to carry out any one of associated operations described above.
  • a priority data service e.g. a priority data transport service
  • the priority service processor may represent means for receiving, from a priority user, a request for invoking or revoking a priority data service (e.g. a priority data transport service) for a data application in a public communication network, and for invoking or revoking the requested priority data service on the basis of a priority status and a service profile of the priority user in accordance with an applicable service flow procedure, as well as for carrying out any one of associated operations described above.
  • the priority service processor may be connected with a transceiver and/or a database or memory storing priority service information, i.e. information needed for an invocation and/or revocation of a priority service.
  • the transceiver i.e. a combined transmitter and receiver
  • the present apparatus may be connected via respective interfaces with a priority user represented by its user equipment or mobile station MS and an AAA server, thus leading to an arrangement according to an AAA-based implementation as explained above.
  • the present apparatus may be connected via respective interfaces with a priority user represented by its user equipment or mobile station MS, an AAA server and a policy control element such as e.g. PDF/PCRF, thus leading to an arrangement according to a PCC-based implementation as explained above.
  • a system according to exemplary embodiments of the present invention may comprise an apparatus according to Figure 10 and one or more of MS, AAA and PDF/PCRF.
  • FIG 11 shows a schematic block diagram of an exemplary configuration of an authentication entity according to exemplary embodiments of the present invention.
  • the thus depicted and described apparatus may for example be (a part of) the AAA server according to any one of Figures 1 to 3 or 4 to 6.
  • an apparatus comprises an authenticating unit and a data processor.
  • the authenticating unit may be configured to carry out or to control a procedure according to step S801 of Figure 8.
  • the authenticating unit may be configured to authenticate a priority user requesting an invocation or revocation of a priority data service (e.g. a priority data transport service) for a data application in a public communication network upon initiation from a priority service authentication server, as well as to carry out any one of associated operations described above.
  • a priority data service e.g. a priority data transport service
  • the authenticating unit may represent means for authenticating a priority user requesting an invocation or revocation of a priority data service (e.g.
  • the data processor may be configured to carry out or to control a procedure according to step S802 of Figure 8. Namely, the data processor may be configured to provide a priority status and a service profile of the priority user and an indication on an applicable service flow procedure to the priority service authentication server, as well as to carry out any one of associated operations described above. Stated in other terms, the data processor may represent means for providing a priority status and a service profile of the priority user and an indication on an applicable service flow procedure to the priority service authentication server, as well as for carrying out any one of associated operations described above.
  • the data processor may be connected with a database or memory storing priority service information, i.e. information needed for an invocation and/or revocation of a priority service, and the authenticating unit may be connected with a transceiver.
  • the present apparatus may additionally comprise a priority service flow processor.
  • the priority service flow processor may be configured to carry out or to control a procedure according to steps S803 to S806 of Figure 8.
  • the priority service flow processor may be configured to trigger a service flow creation, deletion or modification for an invocation or revocation of a requested priority data service (e.g. a priority data transport service) in accordance with the applicable service flow procedure, as well as associated operations described above.
  • the priority service flow processor may represent means for triggering a service flow creation or modification for an invocation of a requested priority data service (e.g. a priority data transport service) in accordance with the applicable service flow procedure, as well as for carrying out associated operations described above.
  • the priority service flow processor may be connected with the information database or memory and the transceiver.
  • the transceiver i.e. a combined transmitter and receiver
  • the transceiver may be connected with one or more interfaces to other apparatuses, entities, devices, or network nodes.
  • the present apparatus may be connected via respective interfaces with a priority authentication server denoted e.g. as ETS authentication server.
  • the present apparatus may be connected via respective interfaces with a priority authentication server denoted e.g. as ETS authentication server and an (anchor) access entity such as an access service node ASN being connected with a priority user represented by its user equipment or mobile station MS.
  • a system according to exemplary embodiments of the present invention may comprise an apparatus according to Figure 11 and one or more of ETS authentication server, ASN and MS.
  • Figure 12 shows a schematic block diagram of an exemplary configuration of a policy control entity according to exemplary embodiments of the present invention.
  • the thus depicted and described apparatus may for example be (a part of) the PDF/PCRF element according to any one of Figures 4 to 6.
  • an apparatus comprises a priority service flow processor.
  • the priority service flow processor may be configured to carry out or to control a procedure according to Figure 9.
  • the priority service flow processor may be configured to trigger at least one of a service flow creation, deletion and modification for an invocation or revocation of a priority data service (e.g. a priority data transport service) for a data application of a requesting priority user in a public communication network upon initiation from a priority service authentication server, said triggering being based on a priority status and a service profile of the priority user and an applicable service flow procedure, as well as to carry out any one of associated operations described above.
  • a priority data service e.g. a priority data transport service
  • the priority service flow processor may represent means for triggering at least one of a service flow creation, deletion and modification for an invocation or revocation of a priority data service (e.g. a priority data transport service) for a data application of a requesting priority user in a public communication network upon initiation from a priority service authentication server, said triggering being based on a priority status and a service profile of the priority user and an applicable service flow procedure, as well as for carrying out any one of associated operations described above.
  • the priority service flow processor may be connected with a transceiver.
  • the transceiver i.e. a combined transmitter and receiver
  • the transceiver may be connected with one or more interfaces to other apparatuses, entities, devices, or network nodes.
  • the present apparatus may be connected via respective interfaces with a priority authentication server denoted e.g. as ETS authentication server and an (anchor) access entity such as an access service node ASN being connected with a priority user represented by its user equipment or mobile station MS.
  • a system according to exemplary embodiments of the present invention may comprise an apparatus according to Figure 12 and one or more of ETS authentication server, ASN and MS.
  • Any one of the above-outlined apparatuses represents an autonomous entity according to respective embodiments of the present invention, while their interworking entirety or any conceivable combination thereof represents a system according to respective embodiments of the present invention.
  • a system may for example be a (transport) network complying with IEEE 802.16 standards and/or a (transport) network complying with 3GPP LTE/SAE standards .
  • respective functional blocks or elements according to above-described aspects can be implemented by any known means, either in hardware and/or software, respectively, if it is only adapted to perform the described functions of the respective parts.
  • the mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the present invention.
  • Devices and means can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to those skilled in the art.
  • Software in the sense of the present description comprises software code as such comprising code means for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable storage medium having stored thereon a respective data structure or code portions or embodied in a signal or in a chip, potentially during processing thereof.
  • an access technology may be any technology by means of which a user equipment or terminal device can access an access network (e.g. via a base station or generally an access device) .
  • any present or future technology such as WLAN (Wireless Local Access Network) , WiMAX (Worldwide Interoperability for Microwave Access), BlueTooth, Infrared, and the like may be applicable; access technologies may be distinguishable in at least two categories or access domains such as packet switched and circuit switched, but the existence of more than two access domains does not impede the invention being applied thereto, - an access network may be any device, apparatus, unit or means by which a station, entity or other user equipment may connect to and/or utilize services offered by the access network; such services include, among others, data and/or (audio-) visual communication, data download etc .
  • a user equipment or terminal device may be any device, apparatus, unit or means by which a system user may experience services from an access network such as a mobile phone, personal digital assistant PDA, or computer;
  • - method steps and functions likely to be implemented as software code portions and being run using a processor at one of the entities, a network element, or a terminal are software code independent and can be specified using any known or future developed programming language, such as e.g. Java, C++, C, and Assembler, as long as the functionality defined by the method steps is preserved;
  • any method step is suitable to be implemented as software or by hardware without changing the idea of the invention in terms of the functionality implemented;
  • CMOS Complementary MOS
  • BiMOS Bipolar MOS
  • BiCMOS Bipolar CMOS
  • ECL emitter Coupled Logic
  • TTL Transistor-Transistor Logic
  • any method steps and/or devices, units or means likely to be implemented as software components may for example be based on any security architecture capable e.g. of authentication, authorization, keying and/or traffic protection;
  • devices, apparatuses, units or means can be implemented as individual devices, apparatuses, units or means, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device, apparatus, unit or means is preserved,
  • an apparatus may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution/being run on a processor;
  • a device may be regarded as an apparatus or as an assembly of more than one apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.
  • the present invention also covers any conceivable combination of method steps and operations described above, and any conceivable combination of nodes, apparatuses, modules or elements described above, as long as the above-described concepts of methodology and structural arrangement are applicable.
  • An exemplary measure may comprise receiving, from a priority user, a request for invoking or revoking a priority data service (e.g. a priority data transport service) for a data application in a public communication network (e.g. a transport network) , and invoking or revoking the requested priority data service (e.g. a priority data transport service) on the basis of a priority status and a service profile of the priority user in accordance with an applicable service flow procedure.
  • a priority data service e.g. a priority data transport service
  • non-limiting examples for such priority services may include ETS in WiMAX network environments, MPS in 3GPP (LTE/SAE) network environments, or any other present or future service in any network environment, which requires a prioritization for calls, sessions or the like of certain prioritized users.
  • ETS in WiMAX network environments
  • MPS in 3GPP (LTE/SAE) network environments
  • SAE 3GPP network environments
  • any other present or future service in any network environment which requires a prioritization for calls, sessions or the like of certain prioritized users.

Abstract

L'invention porte sur des mesures pour une invocation et une révocation de services de priorité. Plus précisément, la présente invention concerne par exemple l'invocation et/ou la révocation de services, de priorité dans des réseaux de communication publics. Une mesure donnée à titre d'exemple peut comporter la réception, à partir d'un utilisateur de priorité, d'une demande pour invoquer ou révoquer un service de données de priorité pour une application de données dans un réseau de communication public, et l'invocation ou la révocation du service de données de priorité demandé sur la base d'un état de priorité et d'un profil de service de l'utilisateur de priorité, conformément à une opération de flux de service applicable.
PCT/EP2009/054708 2009-04-21 2009-04-21 Invocation et révocation de services de priorité WO2010121645A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2009/054708 WO2010121645A1 (fr) 2009-04-21 2009-04-21 Invocation et révocation de services de priorité

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2009/054708 WO2010121645A1 (fr) 2009-04-21 2009-04-21 Invocation et révocation de services de priorité

Publications (1)

Publication Number Publication Date
WO2010121645A1 true WO2010121645A1 (fr) 2010-10-28

Family

ID=41210577

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2009/054708 WO2010121645A1 (fr) 2009-04-21 2009-04-21 Invocation et révocation de services de priorité

Country Status (1)

Country Link
WO (1) WO2010121645A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013083003A1 (fr) * 2011-12-08 2013-06-13 中兴通讯股份有限公司 Procédé et système pour acquérir un attribut de priorité d'utilisateur dans un système à accès multiples
US9667582B2 (en) 2013-11-04 2017-05-30 At&T Intellectual Property I, L.P. Per-session invocation of priority services based upon network available information
US10880836B2 (en) 2019-03-28 2020-12-29 At&T Intellectual Property I, L.P. Beam provisioning for sensory data collection for 5G or other next generation networks
US11026095B2 (en) 2019-07-31 2021-06-01 At&T Intellectual Property I, L.P. Real-time network provisioning for distributed virtual zones of collaborative mobile devices for 5G or other next generation network
US11064337B2 (en) 2019-03-28 2021-07-13 At&T Intellectual Property I, L.P. Beam as a service for 5G or other next generation network
US11297554B2 (en) 2019-03-28 2022-04-05 At&T Intellectual Property I, L.P. Candidate beam selection and control for 5G or other next generation network

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080175263A1 (en) * 2007-01-22 2008-07-24 Qualcomm Incorporated Assured packet data services associated with communication networks

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080175263A1 (en) * 2007-01-22 2008-07-24 Qualcomm Incorporated Assured packet data services associated with communication networks

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NPSTC BROADBAND WORKING GROUP: "Public Saftey 700MHz Broadband Statement of Requirements Version 0.6", INTERNET CITATION, 8 November 2007 (2007-11-08), pages 1 - 53, XP002551758 *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013083003A1 (fr) * 2011-12-08 2013-06-13 中兴通讯股份有限公司 Procédé et système pour acquérir un attribut de priorité d'utilisateur dans un système à accès multiples
US9667582B2 (en) 2013-11-04 2017-05-30 At&T Intellectual Property I, L.P. Per-session invocation of priority services based upon network available information
US10178064B2 (en) 2013-11-04 2019-01-08 At&T Intellectual Property I, L.P. Per-session invocation of priority services based upon network available information
US11178094B2 (en) 2013-11-04 2021-11-16 At&T Intellectual Property I, L.P. Per-session invocation of priority services based upon network available information
US11606324B2 (en) 2013-11-04 2023-03-14 At&T Intellectual Property I, L.P. Per-session invocation of priority services based upon network available information
US10880836B2 (en) 2019-03-28 2020-12-29 At&T Intellectual Property I, L.P. Beam provisioning for sensory data collection for 5G or other next generation networks
US11064337B2 (en) 2019-03-28 2021-07-13 At&T Intellectual Property I, L.P. Beam as a service for 5G or other next generation network
US11297554B2 (en) 2019-03-28 2022-04-05 At&T Intellectual Property I, L.P. Candidate beam selection and control for 5G or other next generation network
US11425652B2 (en) 2019-03-28 2022-08-23 At&T Intellectual Property I, L.P. Beam provisioning for sensory data collection for 5G or other next generation networks
US11026095B2 (en) 2019-07-31 2021-06-01 At&T Intellectual Property I, L.P. Real-time network provisioning for distributed virtual zones of collaborative mobile devices for 5G or other next generation network

Similar Documents

Publication Publication Date Title
JP6194024B2 (ja) Ｍ２ｍサービス設定変更方法及びこのための装置
JP5588017B2 (ja) 発展型パケットシステム及びその緊急呼出のアタッチメント処理方法
US20170332421A1 (en) Connecting to Virtualized Mobile Core Networks
US10474522B2 (en) Providing a network access failure cause value of a user equipment
CN110831243B (zh) 一种用户面安全策略实现方法、装置及系统
EP3745757A1 (fr) Procédé et appareil de communication
CN105103497A (zh) 应用业务配对
CN109691059B (zh) 用于ip版本的选择的方法、无线通信设备、以及网络节点
EP3742812B1 (fr) Dispositif, système et procédé de personnalisation de réseau mobile défini par l'utilisateur
CN112073919A (zh) 多播广播业务的通信方法及装置、电子设备、存储介质
WO2010121645A1 (fr) Invocation et révocation de services de priorité
US20220360670A1 (en) System and method to enable charging and policies for a ue with one or more user identities
US20230328805A1 (en) Policy control for redundant transmissions
CN113747479B (zh) 获取网络资源的方法、设备及系统
JP2020506629A (ja) ルーティング方法および装置
CN110933709B (zh) 协议数据单元会话管理方法及通信装置
WO2021037604A1 (fr) Solution de réattribution d'amf avec isolement de tranche de réseau
US20220248228A1 (en) Methods and Apparatus for Device Authentication and Authorisation
US10798253B2 (en) Methods, devices, and computer programs for enabling the sponsoring of data connectivity
EP2721859B1 (fr) Traitement d'offres de connexion d'opérateurs dans un réseau de télécommunication
CN111164951A (zh) 基于服务能力要求和偏好的服务注册
US20240137447A1 (en) Access and mobility policy control
WO2023274366A1 (fr) Procédé et appareil d'établissement de session avec une qualité de service requise
US20240137366A1 (en) Systems and methods for providing prioritization for data transport services
WO2024032226A1 (fr) Procédé de communication et appareil de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09779321

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09779321

Country of ref document: EP

Kind code of ref document: A1