WO2017205116A1 - Procédés, systèmes, et supports lisibles par un ordinateur pour la prestation de service de priorité de point à point dans des réseaux d'évolution à long terme (lte) ou de génération ultérieure - Google Patents

Procédés, systèmes, et supports lisibles par un ordinateur pour la prestation de service de priorité de point à point dans des réseaux d'évolution à long terme (lte) ou de génération ultérieure Download PDF

Info

Publication number
WO2017205116A1
WO2017205116A1 PCT/US2017/032919 US2017032919W WO2017205116A1 WO 2017205116 A1 WO2017205116 A1 WO 2017205116A1 US 2017032919 W US2017032919 W US 2017032919W WO 2017205116 A1 WO2017205116 A1 WO 2017205116A1
Authority
WO
WIPO (PCT)
Prior art keywords
priority
message
user indicator
priority user
session
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/US2017/032919
Other languages
English (en)
Inventor
Rohit JUNEJA
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Oracle International Corp
Original Assignee
Oracle International Corp
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
Priority claimed from US15/217,899 external-priority patent/US10321300B2/en
Application filed by Oracle International Corp filed Critical Oracle International Corp
Priority to CN201780042397.2A priority Critical patent/CN110140368A/zh
Priority to JP2018561997A priority patent/JP7148408B2/ja
Priority to EP17726775.4A priority patent/EP3466129B1/fr
Publication of WO2017205116A1 publication Critical patent/WO2017205116A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • 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/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels

Definitions

  • the subject matter described herein relates to providing priority service in communications networks. More particularly, the subject matter described herein relates to methods, systems, and computer readable media for providing end-to-end priority service in long term evolution (LTE) or subsequent generation networks.
  • LTE long term evolution
  • mobile communications networks can become overwhelmed with high volumes of user traffic.
  • network resources may be unavailable for important personnel, such as public safety officials, government officials, etc. Because it is desirable for communications from such high priority users to be given precedence in emergency situations, the mobile communications network needs to provide a mechanism for prioritizing communications associated with these users.
  • Third generation and landline networks include mechanisms for prioritizing communications involving priority users.
  • 4G LTE networks do not currently provide a suitable solution for prioritizing communications on an end-to-end basis for high priority users.
  • the subject matter described herein includes methods, systems, and computer readable media for supporting end-to-end priority service in LTE or subsequent generation networks.
  • One method for supporting such priority occurs at a network node configured to operate in an LTE or subsequent generation network.
  • the method includes receiving an incoming message associated with a communications session or transaction in the network.
  • the message includes an end-to-end priority user indicator identifying a user associated the session or transaction as a priority user.
  • the method optionally includes storing an association between the end-to-end priority user indicator and the session or transaction.
  • the method further includes treating the session with a priority corresponding to the end-to-end priority user indicator.
  • the method further includes including the end-to-end priority user indicator in subsequent messages transmitted by the node that are associated with the same session or transaction.
  • the subject matter described herein may be implemented in hardware, software, firmware, or any combination thereof.
  • the terms “function” “node” or “module” as used herein refer to hardware, which may also include software and/or firmware components, for implementing the feature being described.
  • the subject matter described herein may be implemented using a non-transitory computer readable medium having stored thereon computer executable instructions that when executed by the processor of a computer control the computer to perform steps.
  • Exemplary computer readable media suitable for implementing the subject matter described herein include non-transitory computer-readable media, such as disk memory devices, chip memory devices, programmable logic devices, and application specific integrated circuits.
  • a computer readable medium that implements the subject matter described herein may be located on a single device or computing platform or may be distributed across multiple devices or computing platforms.
  • Figure 1 is a message flow illustrating a message flow for providing end-to-end priority service in LTE or subsequent generation networks according to an embodiment of the subject matter described herein;
  • FIG. 2 is a block diagram illustrating an LTE or subsequent generation network node for supporting end-to-end priority service according to an embodiment of the subject matter described herein;
  • Figure 3 is a flow chart illustrating an exemplary process performed by a network node for providing or supporting end-to-end priority service for LTE or subsequent generation networks according to an embodiment of the subject matter described herein.
  • the subject matter described herein includes methods, systems, and computer readable media for providing end-to-end priority service for LTE or subsequent generation networks.
  • a message priority parameter such as the ARP or QCI
  • the subject matter described herein utilizes an end-to-end priority user indicator that identifies a user as a high priority user and that is recognized as a priority user indicator by each node in the network that receives messages including the indicator.
  • Some nodes that receive a message including the end-to-end priority user indicator may store an association between the end-to-end priority user indicator and the session or transaction with which the end-to-end priority user is associated.
  • the end-to-end priority user indicator may also be stored at a location in a message that does not require deep parsing to access the indicator.
  • the end-to-end priority user indicator may be stored in a message header or in an AVP or IE with level 1 depth.
  • messages may optionally carry an end-to-end priority level indicator.
  • the end-to-end priority level indicator may be used to determine priority among session messages associated with different sessions or transactions that have the same end-to-end priority user indicator. Providing multiple levels of end-to-end priority indicators is intended to be within the scope of the subject matter described herein.
  • subject matter described herein includes an end-to-end priority user indicator that is distinct from the IMSI or MSISDN and that is universally recognized in the network as a priority user indicator.
  • the end-to-end priority user indicator is dedicated to identifying a user as a priority user. Different nodes may map such a parameter to message priority, but the end-to-end priority user indicator has at least one value that is universally recognized as denoting a priority user and at least another value different from the first value that is universally recognized as designating a non-priority user.
  • An end-to-end priority user indicator having plural possible values that respectively denote multiple different levels of priority users are also within the scope of the subject matter described herein.
  • FIG. 1 is a message flow diagram illustrating exemplary messages exchanged between LTE network nodes for supporting end-to-end priority service according to an embodiment of the subject matter described herein.
  • a user equipment UE
  • USIM universal subscriber identity module
  • the UE sends its PS_Marking information to the eNode B an in RRC connection request message.
  • the RRC message may also include an establishment cause parameter indicating priority access.
  • the eNode B Upon receipt of this message, in line 2, the eNode B generates an RRC connection setup message.
  • the eNode B may optionally include the end-to-end priority user indicator in the RRC connection setup message.
  • the UE sends an RRC connection setup complete message that includes the end-to-end priority user indicator.
  • the eNode B sends an S1 -AP initial attach request message to the MME.
  • the initial attach request message includes the end-to-end priority user indicator and the priority level information received in the RRC connection request message.
  • the MME stores the association between the end-to-end priority user indicator and the transaction and formulates and sends update location request (ULR) message to the HSS (line 5).
  • the ULR message includes the end-to-end priority user indicator and the priority level information.
  • the update location request message in Figure 1 includes the end-to- end priority user indicator.
  • the HSS and nodes between the MME and the HSS may treat the ULR with the indicated priority.
  • a Diameter signaling router may be located between the MME and the HSS.
  • the Diameter signaling router may receive the ULR message and route the ULR message with a priority corresponding to the priority associated with the end-to-end priority user indicator.
  • the DSR may also store an association between the ULR transaction and the end-to-end priority user indicator so that subsequent messages originated by the DSR associated with the same transaction can also include that parameter.
  • the DSR may then forward the ULR message with the end-to-end priority user indicator to the HSS.
  • the HSS in response to receiving the ULR message with the end-to- end priority user indicator, performs a lookup in its subscriber database and locates a record corresponding to the subscriber. The HSS determines that the subscriber should be afforded the priority indicated by the end-to-end priority user indicator based on the priority associated with the user's subscription stored in the record. If the HSS determines that the subscriber should be given the indicated priority, the HSS responds with a ULA message (line 6) with the same end-to-end priority user indicator received in the ULR message. If the HSS determines that the user is not entitled to the indicated priority, the HSS may override the priority in the message and respond with a ULA message with a lower priority than the received priority. The HSS may also override the message priority to give the user a higher priority if the HSS determines that a higher priority is specified by the user's subscription. The HSS sends the ULA message with the indicated priority to the MME.
  • the ULA message may be received by a DSR between the HSS and the MME.
  • the DSR may route the message with a priority corresponding to the end-to-end priority user indicator in the message.
  • the MME In line 7 of the message flow diagram, the MME generates a create session request message.
  • the create session request message includes the end-to-end priority user indicator and the priority level information.
  • the MME transmits the create session request message to the serving gateway (SGW).
  • SGW serving gateway
  • the serving gateway sends a Create Session Request message including the end-to-end priority user indicator and the priority level information to the packet gateway (PGW).
  • PGW packet gateway
  • the serving gateway may also store an indication between the session or transaction and the priority user and priority level information.
  • the packet gateway or policy and charging enforcement function generates a create connection request-initial (CCR-I) message in response to the received create session request message.
  • the packet gateway includes the end-to-end priority user indicator and the priority level information in the CCR-I message.
  • the packet gateway sends the CCR-I message to a policy and charging rules function (PCRF).
  • PCRF policy and charging rules function
  • a DSR located between the packet gateway and the PCRF may receive the CCR-I message, recognize the end-to-end priority user indicator in the message, and treat the message according to the indicated priority. For example, the DSR may route the message with a priority corresponding to the end-to-end priority user indicator.
  • the DSR may also store an association between the CCR-I transaction and the end-to-end priority user indicator so that the DSR can include the end-to-end priority user indicator in subsequent messages associated with the same transaction that are originated by the DSR. In the illustrated example, the DSR routes the CCR-I message to the PCRF.
  • the PCRF stores an association between the priority user indicator and the priority level information and a Gx session, so that further messages generated by the PCRF can include the same priority information.
  • the PCRF sends a user data request (UDR) message to the subscription profile repository (SPR) communicating the end-to-end priority user indicator and the priority level information to the SPR.
  • UDR user data request
  • SPR subscription profile repository
  • the SPR may determine whether a different priority than indicated by the priority user indicator and/or the priority level information as the SPR may include more real time traffic information than known by other nodes in the network.
  • the SPR sends a user data answer (UDA) message with the priority user indicator and the priority level information to the PCRF. If the SPR decides to override priority information, then the SPR could send new priority values in the UDA message to the PCRF. The PCRF may then decide whether to accept or override the new priority values received from the SPR.
  • the reason that the PCRF may have the authority/capability to override the priority set by the SPR is that the PCRF may have more real time traffic information than the SPR.
  • the priority override feature of the PCRF end may be a pre-enabled feature to avoid any dynamic behavior without the network operator's consent.
  • the PCRF sends a create connection answer initial (CCA-I) message with the priority user indicator and priority level information that it received from the SPR. If the SPR does not send any new priority information then the PCRF may continue to use the received priority information. The PCRF sends this message to the packet gateway. As with the CCR message, the CCA-I message will be received by the DSR and routed with a priority corresponding to the end-to-end priority user indicator.
  • CCA-I create connection answer initial
  • the packet gateway sends a Create Session Response message with the end-to-end priority user indicator and the priority level information that the packet gateway received from the PCRF.
  • the packet gateway sends this message to the serving gateway.
  • the serving gateway sends the Create Session Response including the end-to-end priority user indicator and the priority level information to the MME.
  • the MME triggers an S1 -AP initial context setup request with the end-to-end priority user indicator and the priority level information to eNode B.
  • the eNode B sends an RRC connection reconfiguration attach accept message to the UE confirming establishment of the session.
  • each node in the network can identify the user as a priority user and provide supporting end-to-end priority service.
  • FIG. 2 is a block diagram illustrating an exemplary LTE or subsequent generation network node for supporting end-to-end priority service.
  • network node 200 may be any of the nodes illustrated in Figure 1 or other Diameter, IMS, LTE, or subsequent generation network node.
  • network node 200 may be an eNode B, an MME, a DSR, an HSS, an SGW, a PGW, a PCRF, an SPR, a session border controller (SBC), a proxy call session control function (P-CSCF), an equipment identity register (EIR) or a user data repository (UDR).
  • network node 200 includes a processor 202 and memory 204.
  • Network node 200 also includes a network interface 206.
  • Network node 200 further includes an end-to-end priority service support module 208 that performs the functions described herein for supporting end- to-end priority service.
  • end-to-end priority service support module 208 may receive messages via network interface 206, determine the priority user indicator and priority level information in the messages and store an association between a session or transaction and the end-to-end priority user indicator and the priority level indicator in memory 204.
  • End-to- end priority service support module 208 may also ensure that subsequent messages associated with the same session contain the same priority user indicator and priority service indicator. If network node 200 is an HSS or an SPR, end-to-end priority service support module 208 may override the priority user indicator and/or priority level information as described above. End-to-end priority service support module may also ensure that subsequent messages originated by network node 200 associated with the same session or transaction are treated with the priority indicated by the user indicator and/or the priority level information.
  • FIG. 3 is a flow chart illustrating an exemplary process for supporting end-to-end priority service in LTE or subsequent generation networks according to an embodiment of the subject matter described herein.
  • a message is received at a node in a LTE or subsequent generation network.
  • the message may include an end-to-end priority user indicator and optional priority level information.
  • the node may be any of the nodes described with respect to Figures 1 or 2.
  • the node stores an association in between the priority user indicator and a session or transaction with which the message is associated.
  • network node 200 may store the end-to-end priority user indicator and/or priority level information in memory 204 along with an identifier for the transaction or session with which the message is associated.
  • step 304 it is determined whether the priority associated with the end-to-end priority user indicator should be overruled.
  • Step 304 may be implemented if the receiving node is an HSS, an SPR, or a PCRF. If the node is one of the other nodes without priority override capabilities, step 304 may be omitted, and control proceeds to step 306 where an association between the end-to-end priority user indicator and a session or transaction with which the received message is associate is stored. In step 304, if it is determined that the priority in the message should be overridden, control proceeds to step 308 where an association between the new priority and/or priority level in the session or transaction with which the message is associated is stored.
  • steps 306 and 308 may be omitted for nodes that do not originate any messaging related to the transaction or session. Such nodes may simply copy the priority user indicator and priority service indicator from inbound messages into outbound messages.
  • the session or transaction is treated with the priority corresponding to the end-to- end priority user indicator in the message.
  • the node that receives the message is a DSR
  • the message may be routed with a priority corresponding to the end-to-end priority user indicator.
  • end-to- end priority user indicator is included in subsequent messages associated with the same session or transaction.
  • LTE or subsequent generation network node 200 may include the end-to-end priority user indicator in messages that it formulates relating to the same session or transaction as the message in which the priority user indicator or priority level indicator is subsequently received.
  • the USIM must be modified to support priority service.
  • the USIM is a real or virtual card that is stored in a mobile device or UE. Because a USIM contains information for authenticating a user to the network during the user's initial attachment to the network, the USIM is the first device in the chain of devices that may be modified to support end-to-end priority service.
  • Option #1 Define a new elementary file (E F) for priority service (PS) marking and priority Level Info.
  • E F elementary file
  • PS priority service
  • Supplemental files are files that carry information and that are stored on the USIM in a UE.
  • the new EF for this option is referred to as EF PS _MARKING, which will carry information regarding a priority subscription from a UE.
  • the E F PS _MARKING file may carry the end-to-end priority user indicator described herein.
  • Option #1 may also include a second EF called EFps_priority_Levei_info that is used to convey priority level information. If PS_Marking is enabled and priority level information is not defined then network defined priority can be used. The priority information carried in the new elementary files to support priority services would be verified in network. For example, as described above with respect to Figure 1 , the HSS may verify that the user's subscription supports priority service. Also, PS_Marking may be mandatory for PS users but priority level can be optional.
  • option #2 instead of defining an EF with new parameters to support priority service, a new EF that re-uses existing parameters for priority services may be used. This option is referred to below as option #2.
  • Option #2 Define an EF for PS marking and reuse EF e Mi_pp for priority level information.
  • a new elementary file, E F PS _MARKING may be used to carry the end-to-end priority user indicator, and an existing E F, enhanced multi-level precedence and preemption (E F e Mi_pp) may be used to carry the optional priority level information.
  • Table 1 shown below illustrates the structure of the EF e Mi_pp elementary file and the portion that may be used to carry priority level information.
  • Table 1 EF e Mi_pp Structure Used to Carry Priority Level Information for USIM
  • byte 2 of the EF e Mi_pp elementary file may carry the priority level information.
  • the priority user and priority level information carried in the EFs for option #2 may be verified by the network as well.
  • the HSS may confirm whether or not the user is entitled to the priority carried in USIM EFs and may override the priority if the user is not entitled to the priority specified in the EFs.
  • the EF e Mi_pp elementary file may be modified to carry priority user information and priority level information.
  • Table 2 shown below illustrates exemplary modifications to the EF e Mi_pp elementary file for option #3.
  • Option #3 In Table 2, it can be seen that the size of the EF e Mi_pp elementary file has been increase to three bytes with the third byte carrying the end-to-end priority user information.
  • the priority level information can be carried in the existing priority level parameter (byte 1 ).
  • the priority user and priority level information in option #3 may be verified by the network to ensure that the user is entitled to the USIM-specified priority.
  • option #1 is preferred because it does not impact existing EFs.
  • eMLPP Third Generation Partnership Project Technical Standard
  • PS marking is enabled then network configured priority can be used.
  • the structure of the EF e Mi_pp is described in Third Generation Partnership Project Technical Standard (3GPP TS) 31.102 V13.1 .0 , the disclosure of which is incorporated herein by reference in its entirety.
  • the RRC interface is the interface between the eNode B and the MME.
  • Messages in the RRC information include lEs that carry information for radio interface resource control.
  • option #1 a new IE is added in RRC messaging to carry end-to-end priority user and priority level information.
  • PS_Marking may be mandatory and priority level information may be optional. If the priority level is not present then a system configured default priority can be used at the eNode B and the MME until the HSS communicates the subscriber priority to the eNode B and the MME.
  • end-to-end priority user and priority level information may be communicated in a NAS message (e.g. an Attach Request request)
  • a NAS message e.g. an Attach Request request
  • the eNode B does not process the NAS message, the eNode B will not be able to learn of the priority information.
  • the RRC Attach Type IE (carried in an attach request message) may be modified to carry end-to-end priority user and priority level information as well as evolved packet services (EPS) as the requested attachment type. Carrying priority service information as part of the attach type IE would require more effort from different nodes to process same type of calls with different priorities.
  • EPS evolved packet services
  • Option 1 Add PS marking and PS priority level info to an existing S1 - AP protocol message.
  • the S1 -AP protocol is used on the interface between the eNode B and the MME.
  • the end-to-end priority user indicator and the priority level information may be added to an existing message, such as an initial UE message transmitted from the eNode B to the MME.
  • PS marking end-to- end priority user indicator
  • the priority level may be optional.
  • Option 2 Carry forward the PS info from a non-access stratum (NAS) message.
  • NAS messaging is used between the eNode B and the MME to carry UE-MME signaling over the S1 interface.
  • Such signaling may be used to carry end-to-end priority user and priority level information received from the UE from the eNode B to the MME.
  • the MME may then transport the received priority information to other network nodes, such as the HSS.
  • PS marking in Diameter messaging can be implemented in at least the following two ways:
  • Option #1 Set reserved bit in command flag in Diameter header. Currently there are 4 reserved bits in the command flag as shown below:
  • the last 4 bits are reserved (r).
  • r the last 4 bits are reserved (r).
  • One of these reserved bits can be used to store the end-to-end priority user indicator.
  • One advantage of using a bit in the Diameter command flag in the Diameter header to store the end-to-end priority user indicator is that the command flag can be parsed quickly and used to either prioritize or discard messages during congestion.
  • One disadvantage of this approach is that a reserved bit is used. Additional details of the Diameter header and the command flag can be found in IETF RFC 6733, the disclosure of which is incorporated herein by reference in its entirety.
  • a new priority service AVP may be used.
  • the new AVP may indicate whether a message is associated with a priority user or not.
  • the AVP may be close to the header to reduce parsing time.
  • PS_Priority_Level can carry the PS priority user information.
  • a disadvantage to this approach is that a new AVP support may be required.
  • An advantage of tis approach is that PS priority level information can be segregated from Diameter message priority and can be taken in to account while setting the message priority.
  • the PS_Priority_Level AVP should be read to determine the message priority level so that it should be higher than public priority level.
  • an existing AVP can be used.
  • the existing AVP that is reused is the Diameter routing message priority (DRMP) AVP.
  • DRMP Diameter routing message priority
  • An advantage to this approach is that support for a new AVP does not need to be implemented.
  • a disadvantage of this approach is that PS users have different priority level (1 to n) and each network and vendor may have different interpretation of priority levels. So it would require a recommendation to use a fixed range for PS users which should be higher that public users.
  • a new Default_PS_Priority_LEVEL AVP can be sent in capabilities exchange request/capabilities exchange answer (CER/CEA) message and communicating nodes can use a max of CER and CEA. If only one node sends it than that priority can be used as default for other node as well.
  • CER/CEA capabilities exchange request/capabilities exchange answer
  • Node A sends priority info to node B. If node B has default priority, then ignore this AVP. Else the node B shall pick up node A priority received in CEx message.
  • Max is the maximum priority level used by the Diameter node.
  • GTPv2 General Packet Radio Service Tunneling Protocol Version 2
  • Option #1 Set spare bit in header to carry the end-to-end priority user indicator.
  • Table 4 shown below illustrates an exemplary structure of a GTPv2 header. Bits
  • T flag is set to 1 , then TEID shall be placed into octets k(m+3) 5-8. Otherwise TEID filed is not present at all.
  • octets n+3 in the header contain spare bits.
  • One of the spare bits can be used for PS marking.
  • An advantage of using a header bit for PS marking is that header bits can be quickly processed to identify messages associated with priority and non-priority users during periods of congestion.
  • a disadvantage of using a spare or reserved bit is that these bits are supposed to remain reserved according to the GTPv2 specification. Further details about the GTPv2 header can be found in 3GPP TS 29.274, the disclosure of which is incorporated herein by reference in its entirety.
  • a new IE may be used to carry the information to indicate whether a GTPv2 message is associated with a priority user or not. This IE may be kept close to the GTPv2 header. An advantage of this approach is that a reserved bit is saved. A disadvantage of utilizing a new IE is that additional parsing time in locating and parsing the IE may result.
  • the priority level information may also be carried and a GTPv2 IE separate from the GTPv2 header.
  • a new IE referred to as PS_Priority_Level can carry the priority level information.
  • PS_Priority_Level can carry the priority level information.
  • a disadvantage to this approach is that support for yet another new IE may be required.
  • An advantage to this approach is that priority level information can be segregated from the end-to- end user priority and can be taken in to account while setting the message priority.
  • the PS_Priority_Level IE may be read to determine the message priority level so that it should be higher than the priority level for public (non-emergency) messages.
  • the PS_Priority Level IE can be grouped with the new IE to support end-to-end user priority. Defining a new IE to carry the priority level information is cleaner than using an existing IE, such as the enhanced multi-level precedence and preemption (ML) IE, to carry such information because doing so keeps eMLPP and PS level lEs separate.
  • ML enhanced multi-level precedence and preemption
  • an existing IE can be reused to carry such information.
  • the existing IE that is reused may be the message priority service evolved packet system (MPS EPS) IE.
  • MPS EPS message priority service evolved packet system
  • An advantage of this approach is that support for a new IE is not required.
  • a disadvantage is that there is no segregation on e ELMPP and PS lEs, although only one will be in use.
  • network nodes may also be modified to support end-to-end priority service.
  • the following sections specify modifications that may be made to each node in the network to support end-to-end priority service as described herein.
  • the MME may implement the following:
  • the HSS may be modified to include support to save PS_Marking and PS_Priority_Level Info in the subscription profile for a UE.
  • the HSS may determine whether priority specified in a user's subscription matches the end-to-end priority user indicator and priority level information in a received message and may override the priority in the message if the priority in a user's subscription does not match.
  • the SPR may save PS marking and PS priority level information in the subscription information and communicate the same to the PCRF.
  • the SPR may also communicate priority information associated with a user's subscription to the PCRF to allow the PCRF to make priority override decisions.
  • the PCRF may use the PS marking and priority level information received from SPR and apply the received information in overriding the HSS values received from PGW. Additionally, the PCRF may communicate the PS marking and priority level information back to the network during IP CAN session establishment. Other nodes can use the PS marking and priority level information received from the PCRF to overwrite/disable message priority values in the network. DSR or Diameter Routing Agent (DRA)
  • a DSR or DRA may be modified to recognize end-to-end priority user indicators and priority level information, either stored in a Diameter header or a Diameter AVP.
  • the DSR may also be configured to include this information in outbound messages generated by the DSR that are associated with the same session or transaction as a received message that included the end-to-end priority user indicator and priority level information.
  • the DSR may also be configured to treat messages with the priority indicated by the priority user indicator and/or the priority level information. For example, messages with a priority user indicator may be routed with higher priority than messages without such an indicator.
  • the SGW and PGW may each be modified to recognize priority user indicators and priority level information in received messages, to store associations between the indicators and the corresponding session or transaction, and to include the end-to-end priority user indicator and priority level information in outbound messages transmitted by the SGW or PGW that are associated with the same session as message that communicated such information to the SGW or PGW.
  • end-to-end priority service may also be extended to other networks that communicate with such networks.
  • end-to-end priority service may be extended to IP multimedia subsystem (IMS) networks, using the same priority user indicator and priority level information described herein.
  • IMS IP multimedia subsystem
  • network node 300 illustrated in Figure 2 may be an IMS network node that performs the steps described herein for supporting end-to-end priority service.
  • the INVITE message from the UE may carry PS_MARKING and PS_PRIORITY_Level configured and may be communicated to IMS network from that point.
  • the HSS in the IMS network may verify and can override information sent from the UE. This behavior is similar to that described above for the LTE network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Emergency Management (AREA)
  • Environmental & Geological Engineering (AREA)
  • Public Health (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Le sujet de la présente invention inclut des procédés, des systèmes, et des supports lisibles par un ordinateur pour la prise en charge d'un service de priorité de point à point dans des réseaux LTE ou de génération ultérieure. Un procédé de prise en charge d'une telle priorité est mis en œuvre à un nœud de réseau configuré pour fonctionner dans un réseau LTE ou de génération ultérieure. Le procédé consiste à recevoir un message entrant associé à une session de communications ou à une transaction dans le réseau. Le message inclut un indicateur d'utilisateur de priorité de point à point identifiant un utilisateur associé à la session ou à la transaction en tant qu'utilisateur de priorité. Le procédé consiste optionnellement à enregistrer une association entre l'indicateur d'utilisateur de priorité de point à point et la session ou la transaction. Le procédé consiste en outre à traiter la session avec une priorité correspondant à l'indicateur d'utilisateur de priorité de point à point. Le procédé consiste en outre à inclure l'indicateur de priorité de point à point dans des messages suivants transmis par le nœud de réseau qui sont associés à la même session ou transaction que le message reçu.
PCT/US2017/032919 2016-05-26 2017-05-16 Procédés, systèmes, et supports lisibles par un ordinateur pour la prestation de service de priorité de point à point dans des réseaux d'évolution à long terme (lte) ou de génération ultérieure Ceased WO2017205116A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201780042397.2A CN110140368A (zh) 2016-05-26 2017-05-16 在长期演进(lte)或后代网络中提供端到端优先级服务的方法、系统和计算机可读介质
JP2018561997A JP7148408B2 (ja) 2016-05-26 2017-05-16 ロング・ターム・エボリューション（ｌｔｅ）または後続世代のネットワークにおけるエンドツーエンド優先サービスを提供するための方法、システム、およびコンピュータ読取可能な媒体
EP17726775.4A EP3466129B1 (fr) 2016-05-26 2017-05-16 Procédé, système, et support lisibles par un ordinateur pour la prestation de service de priorité de point à point dans des réseaux d'évolution à long terme (lte) ou de génération ultérieure

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
IN201641018071 2016-05-26
IN201641018071 2016-05-26
US15/217,899 US10321300B2 (en) 2016-05-26 2016-07-22 Methods, systems, and computer readable media for providing end-to-end priority service in long term evolution (LTE) or subsequent generation networks
US15/217,899 2016-07-22

Publications (1)

Publication Number Publication Date
WO2017205116A1 true WO2017205116A1 (fr) 2017-11-30

Family

ID=58800927

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/032919 Ceased WO2017205116A1 (fr) 2016-05-26 2017-05-16 Procédés, systèmes, et supports lisibles par un ordinateur pour la prestation de service de priorité de point à point dans des réseaux d'évolution à long terme (lte) ou de génération ultérieure

Country Status (1)

Country Link
WO (1) WO2017205116A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10425342B2 (en) 2016-12-16 2019-09-24 Oracle International Corporation Methods, systems, and computer readable media for priority routing of diameter messages
US12034570B2 (en) 2022-03-14 2024-07-09 T-Mobile Usa, Inc. Multi-element routing system for mobile communications

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090296688A1 (en) * 2008-06-02 2009-12-03 Research In Motion Limited Coding and Behavior when Receiving an IMS Emergency Session Indicator from Authorized Source

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090296688A1 (en) * 2008-06-02 2009-12-03 Research In Motion Limited Coding and Behavior when Receiving an IMS Emergency Session Indicator from Authorized Source

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS); Stage 2 (Release 13)", 3GPP STANDARD; 3GPP TS 23.228, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V13.5.0, 15 March 2016 (2016-03-15), pages 1 - 314, XP051087935 *
ACS ET AL: "Support of the Session-Priority AVP over S6a Interface", vol. CT WG4, no. Vancouver, Canada; 20150817 - 20150821, 10 August 2015 (2015-08-10), XP050991109, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ct/WG4_protocollars_ex-CN4/TSGCT4_70_Vancouver/Docs/> [retrieved on 20150810] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10425342B2 (en) 2016-12-16 2019-09-24 Oracle International Corporation Methods, systems, and computer readable media for priority routing of diameter messages
US12034570B2 (en) 2022-03-14 2024-07-09 T-Mobile Usa, Inc. Multi-element routing system for mobile communications

Similar Documents

Publication Publication Date Title
EP3466129B1 (fr) Procédé, système, et support lisibles par un ordinateur pour la prestation de service de priorité de point à point dans des réseaux d&#39;évolution à long terme (lte) ou de génération ultérieure
CN114902714B (zh) 使用diameter代理和信号传输点(stp)来实现间接的通用分组无线电服务(gprs)隧道协议(gtp)防火墙过滤的方法、系统和计算机可读介质
CN103444148B (zh) 控制部署的业务检测功能节点的路由选择或绕过的网络节点和方法
ES2778869T3 (es) Procedimientos y aparatos para controlar un servicio específico en estado de congestión de red en un sistema de comunicación inalámbrico
ES2686670T3 (es) Procedimiento de gestión de suscripciones de usuarios en una red de telecomunicaciones móviles
US9686116B2 (en) Dynamic service information for the access network
JP5463418B2 (ja) 拡張されたアロケーション／リテンションポリシーの解決策
CN107204938B (zh) 发送低优先级数据的方法和装置及处理其的方法和装置
CN107889255A (zh) 通信方法、装置、系统、终端和接入网设备
US12261821B2 (en) Reuse of IP addresses
US10645230B1 (en) Roaming cellular traffic policy and charging negotiation and enforcement entity
CN111278080B (zh) 在5g网络中路由移动数据业务的方法和系统
KR100666235B1 (ko) Ｐｄｐ 콘텍스트 에러 처리 방법
EP2903220A1 (fr) Procédé et appareil pour le traitement d&#39;un paquet
US10939484B2 (en) Establishing a bearer service in a telecommunications network
CN106471830A (zh) 策略和计费规则功能（pcrf）选择
US20240306237A1 (en) Dynamic pcrf/pcf selection
US9647935B2 (en) Inter-layer quality of service preservation
WO2017205116A1 (fr) Procédés, systèmes, et supports lisibles par un ordinateur pour la prestation de service de priorité de point à point dans des réseaux d&#39;évolution à long terme (lte) ou de génération ultérieure
JP6271719B2 (ja) データ接続のためのオンデマンドＱｏＳ
WO2013117221A1 (fr) Procédés, appareils, système et produit de programme informatique associé destinés à définir, fournir et activer des filtres de paquets
US20160191382A1 (en) Method for transmitting small data packet, and device
GB2637773A (en) Access traffic steering, switching, splitting (ATSSS) between access paths
US20150237669A1 (en) Diameter based communication session discovery and recovery
CN103874240A (zh) 一种信令发起方法、装置及网关设备

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2018561997

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 17726775

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017726775

Country of ref document: EP

Effective date: 20190102