Priority data transport service
Abstract
Techniques, devices, and systems for implementing a Priority Data Transport Service (PDTS) are disclosed. The PDTS provides authorized devices and/or authorized users with on-demand, priority data transport (e.g., priority Internet access). For example, the PDTS allows authorized devices and/or authorized users to access the Internet, use mobile applications, and/or send and receive image data, video data, and text data in a prioritized manner, as compared to the regular (non-priority) Internet access that is provided to non-subscribers of the PDTS over commercial telecommunications networks. An authorized user may activate and deactivate the PDTS on demand. For instance, the PDTS may be activated during an emergency or crisis situation when networks may be congested, thereby providing the user with priority data transport (e.g., priority Internet access) in an emergency or crisis situation when a telecommunications network may be overloaded.
Claims
exact text as granted — not AI-modifiedWe claim:
1 . (canceled)
2 . A user equipment (UE) comprising:
a processor; and memory storing a set of UE route selection policy (URSP) rules and computer-executable instructions that, when executed by the processor, cause the UE to:
register for a first network slice and a second network slice, wherein the second network slice is configured to provide higher priority transport of data packets during protocol data unit (PDU) sessions than the first network slice; and
based on the set of URSP rules:
when using a priority data transport service (PDTS), send data packets via the second network slice, and
when not using the PDTS, send data packets via the first network slice.
3 . The UE of claim 2 , wherein the computer-executable instructions, when executed by the processor, further cause the UE to:
receive user input to activate the PDTS, wherein the user input corresponds to at least one of navigating a browser to a site or launching an application; and determine that a URSP rule of the set of URSP rules specifies an identifier (ID) of at least one of the site or the application.
4 . The UE of claim 2 , wherein the computer-executable instructions, when executed by the processor, further cause the UE to:
receive a second set of URSP rules, wherein the set of URSP rules is a first set of URSP rules; delete the first set of URSP rules from the memory at a time of receiving the second set of URSP rules; receive user input to deactivate the PDTS; send a PDU session establishment request; receive, based at least in part on the PDU session establishment request, the first set of URSP rules to replace the second set of URSP rules in the memory; and send, based at least in part on a URSP rule of the first set of URSP rules, one or more second data packets during a second PDU session via the first network slice.
5 . The UE of claim 2 , wherein a URSP rule of the set of URSP rules prevents one or more data packets from being sent over Wi-Fi during a PDU session.
6 . The UE of claim 2 , wherein:
the UE is subscribed to the PDTS; the second network slice is usable by UEs that are subscribed to the PDTS to activate and use the PDTS; and one or more data packets are sent during a PDU session via the second network slice.
7 . The UE of claim 6 , wherein the computer-executable instructions, when executed by the processor, further cause the UE to, prior to receiving a second set of URSP rules, send credentials for authenticating with the PDTS.
8 . The UE of claim 2 , wherein:
the UE is not subscribed to the PDTS; the second network slice is usable by UEs that are not subscribed to the PDTS to activate the PDTS; the computer-executable instructions, when executed by the processor, further cause the UE to, prior to receiving a second set of URSP rules:
receive user input to activate the PDTS, wherein the user input corresponds to navigating a browser to a site
send, based at least in part on a URSP rule of the set of URSP rules, a PDU session establishment request via the second network slice; and
receive, during an intermediate PDU session, second user input corresponding to credentials entered by a user of the UE via the site; and
one or more data packets are sent during a PDU session via a third network slice that is configured to provide higher priority transport of data packets during PDU sessions than the first network slice.
9 . A method comprising:
registering, by a user equipment (UE), for a first network slice and a second network slice, wherein the second network slice is configured to provide higher priority transport of data packets during protocol data unit (PDU) sessions than the first network slice; based on a set of UE Route Selection Policy (URSP) rules:
when using a priority data transport service (PDTS), sending, by the UE, data packets via the second network slice, and
when not using the PDTS, sending, by the UE, data packets via the first network slice.
10 . The method of claim 9 , wherein:
the set of URSP rules comprises a second set of URSP rules; and the method further comprises:
receiving user input to activate the PDTS, wherein the user input corresponds to at least one of navigating a browser to a site or launching an application; and
prior to the receiving of the second set of URSP rules, determining that a URSP rule of a first set of URSP rules stored in memory of the UE specifies an identifier (ID) of at least one of the site or the application.
11 . The method of claim 9 , wherein the set of URSP rules comprises a second set of URSP rules, the method further comprising:
deleting a first set of URSP rules from memory of the UE at a time of receiving of the second set of URSP rules receiving user input to deactivate the PDTS; sending, by the UE, a PDU session establishment request; receiving, based at least in part on the PDU session establishment request, the first set of URSP rules to replace the second set of URSP rules in the memory; and sending, based at least in part on a URSP rule of the first set of URSP rules, one or more data packets during a PDU session via the first network slice.
12 . The method of claim 9 , wherein a URSP rule of the set of URSP rules prevents one or more data packets from being sent over Wi-Fi during a PDU session.
13 . The method of claim 9 , wherein:
the UE is subscribed to the PDTS; the second network slice is usable by UEs that are subscribed to the PDTS to activate and use the PDTS; and one or more data packets are sent during a PDU session via the second network slice.
14 . The method of claim 13 , further comprising, prior to receiving of the set of URSP rules, sending credentials for authenticating with the PDTS.
15 . The method of claim 9 , wherein:
the set of URSP rules comprises a second set of URSP rules; the UE is not subscribed to the PDTS; the second network slice is usable by UEs that are not subscribed to the PDTS to activate the PDTS; a user input received by the UE corresponds to navigating a browser to a site; the method further comprises, prior to the receiving of the second set of URSP rules:
sending, based at least in part on a URSP rule of a first set of URSP rules stored in memory of the UE, a PDU session establishment request via the second network slice; and
receiving, during an intermediate PDU session, second user input corresponding to credentials entered by a user of the UE via the site; and one or more data packets are sent during a PDU session via a third network slice.
16 . A non-transitory computer storage medium having a plurality of programming instructions stored thereon that, when executed by a user equipment (UE), cause the UE to perform operations comprising:
registering for a first network slice and a second network slice, wherein the second network slice is configured to provide higher priority transport of data packets during protocol data unit (PDU) sessions than the first network slice; based on a set of UE Route Selection Policy (URSP) rules:
when using a priority data transport service (PDTS), sending data packets via the second network slice, and
when not using the PDTS, sending data packets via the first network slice.
17 . The non-transitory computer storage medium of claim 16 , wherein:
the set of URSP rules comprises a second set of URSP rules; and the operations further comprise:
receiving user input to activate the PDTS, wherein the user input corresponds to at least one of navigating a browser to a site or launching an application; and
prior to the receiving of the second set of URSP rules, determining that a URSP rule of a first set of URSP rules stored in memory of the UE specifies an identifier (ID) of at least one of the site or the application.
18 . The non-transitory computer storage medium of claim 16 , wherein the set of URSP rules comprises a second set of URSP rules, the operations further comprising:
deleting a first set of URSP rules from memory of the UE at a time of receiving of the second set of URSP rules receiving user input to deactivate the PDTS; sending, by the UE, a PDU session establishment request; receiving, based at least in part on the PDU session establishment request, the first set of URSP rules to replace the second set of URSP rules in the memory; and sending, based at least in part on a URSP rule of the first set of URSP rules, one or more data packets during a PDU session via the first network slice.
19 . The non-transitory computer storage medium of claim 16 , wherein a URSP rule of the set of URSP rules prevents one or more data packets from being sent over Wi-Fi during a PDU session.
20 . The non-transitory computer storage medium of claim 16 , wherein:
the UE is subscribed to the PDTS; the second network slice is usable by UEs that are subscribed to the PDTS to activate and use the PDTS; and one or more data packets are sent during a PDU session via the second network slice.
21 . The non-transitory computer storage medium of claim 20 , wherein the operations further comprise, prior to receiving of the set of URSP rules, sending credentials for authenticating with the PDTS.Join the waitlist — get patent alerts
Track US2023337105A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.