IP Library › Granted Patent US 12,739,901
Granted Patent B2
US 12,739,901 · App. 17/757,142 · Granted Sep 15, 2026

UE based pair ID for redundant PDU sessions

Inventors: Juan Zhang (Beijing, CN); Haris Zisimopoulos (London, GB)
Assignee: QUALCOMM Incorproated
H04W76/11H04W76/12
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,739,901
App. No.
17/757,142
Granted
Sep 15, 2026
Kind
B2
Abstract

In one aspect, a method includes determining, by a user equipment (UE), a pair identifier (ID); and transmitting, by the UE, a protocol data unit (PDU) session establishment message and the pair ID. In another aspect, a method include receiving, by a first network entity from a second network entity, a PDU session request message including a pair ID; and associating, by the network entity, a PDU session indicated by the PDU session request message with the pair ID. In yet another aspect, a method includes receiving, by a network entity from a UE, a PDU session establishment message and a pair ID; and transmitting, by the network entity, a PDU session request message responsive to the PDU session establishment message and including the pair ID.

Claims (60)

1 . A user equipment (UE) for wireless communication, comprising:

a memory; and

at least one processor coupled to the memory, wherein the at least one processor is configured to cause the UE to:

transmit a first protocol data unit (PDU) session establishment message;

generate a pair identifier (ID), wherein a value of the pair ID is an indication shared by redundant PDU sessions and configured to associate PDU sessions together as redundant; and

transmit a second PDU session establishment message and the pair ID.

2 . The UE of claim 1 , wherein the first PDU session establishment message includes the pair ID.

3 . The UE of claim 1 , wherein, to transmit the pair ID, the at least one processor is configured to:

transmit a message including the pair ID, wherein the message including the pair ID is separate from the first PDU session establishment message.

4 . The UE of claim 1 , wherein, to transmit the first PDU session establishment message, the at least one processor is configured to transmit the first PDU session establishment message to a first network entity, and wherein the first PDU session establishment message is configured to cause the first network entity to send a PDU session request message to a second network entity.

5 . The UE of claim 4 , wherein the PDU session request message includes the pair ID.

6 . The UE of claim 1 , wherein the second PDU session establishment message includes the pair ID and is configured to establish the redundant PDU sessions for the first and second PDU session establishment messages.

7 . The UE of claim 1 , wherein, to generate the pair ID, the at least one processor is configured to allocate the value of the pair ID based on a service associated with a PDU session corresponding to the first PDU session establishment message.

8 . The UE of claim 1 , wherein, to transmit the first PDU session establishment message, the at least one processor is configured to transmit the first PDU session establishment message to a first network entity and wherein the first PDU session establishment message includes the pair ID, and wherein, to transmit the second PDU session establishment message, the at least one processor is configured to:

transmit the second PDU session establishment message to a third network entity, wherein the second PDU session establishment message is configured to cause the third network entity to send a second PDU session request message to a second network entity.

9 . The UE of claim 8 , wherein the second network entity comprise a radio access network (RAN); or the first and third network entities comprise Session Management Functions (SMFs).

10 . The UE of claim 1 , wherein, to generate the pair ID, the at least one processor is configured to determine a PDU session ID from a prior PDU session as the pair ID.

11 . The UE of claim 1 , wherein, to generate the pair ID, the at least one processor is configured to determine the pair ID from a services table based on a corresponding service of a PDU session associated with the first PDU session establishment message.

12 . The UE of claim 1 , wherein, to transmit the first PDU session establishment message, the at least one processor is configured to transmit the first PDU session establishment message to a first network entity and wherein the first PDU session establishment message excludes the pair ID and is transmitted prior to determination of the pair ID, and wherein, to transmit the second PDU session establishment message, the at least one processor is configured to:

transmit, after the determination of the pair ID, the second PDU session establishment message to a third network entity, and wherein the second PDU session establishment message is configured to cause the third network entity to send a second PDU session request message to a second network entity.

13 . The UE of claim 12 , wherein the at least one processor is configured to:

transmit, after transmission of the first PDU session establishment message, a third PDU session establishment message to a fourth network entity, wherein the third PDU session establishment message includes the pair ID, and wherein the third PDU session establishment message is configured to cause the fourth network entity to send a third PDU session request message to the second network entity.

14 . The UE of claim 1 , wherein the at least one processor is configured to assign the pair ID to a particular service, wherein, to assign the pair ID to the particular service, the at least one processor is configured to edit a service table to correlate the pair ID with the particular service.

15 . The UE of claim 14 , wherein the services table is a URLLC service table.

16 . The UE of claim 1 , wherein the at least one processor is configured to perform a PDU session modification operation, wherein the PDU session modification operation includes transmitting a modification request to a service providing device including remove information corresponding to the pair ID.

17 . The UE of claim 1 , wherein the at least one processor is configured to:

receive first data via a first PDU session established by the first PDU session establishment message; and

receive second data via a second PDU session established by the second PDU session establishment message, the second data the same as the first data.

18 . The UE of claim 17 , wherein:

to receive the first data, the at least one processor is configured to receive the first data from a particular servicing device via a first base station; and

to receive the second data, the at least one processor is configured to receive the second data from the particular servicing device via a second base station.

19 . The UE of claim 1 , wherein the at least one processor is configured with a redundancy handling function (RHF) that is configured to generate the pair ID.

20 . The UE of claim 1 , wherein the at least one processor is configured to receive an apparatus policy from a network entity, and wherein, to generate the pair ID, the at least one processor is configured to cause generation or determination of the pair ID based on the apparatus policy.

21 . The UE of claim 1 , wherein the at least one processor is configured to:

determine a first service associated with a first PDU session

determine a second service associated with a second PDU session;

compare the first service to the second service; and

determine to generate a redundant PDU session of the redundant PDU sessions based on the comparison.

22 . The UE of claim 1 , wherein the pair ID comprises an identifier of a PDU session.

23 . The UE of claim 22 , wherein the pair ID further identifies a service associated with the PDU session.

24 . The UE of claim 1 , wherein the pair ID is PDU session ID that identifies a first PDU session associated with the first PDU session establishment message.

25 . A first network entity for wireless communication, comprising:

a memory; and

at least one processor coupled to the memory, wherein the at least one processor is configured to:

receive, from a second network entity, a first protocol data unit (PDU) session request message;

receive, from a third network entity, a second PDU session request message including a pair identifier (ID) generated by a user equipment (UE); and

associate, a PDU session indicated by the first PDU session request message with the pair ID, wherein a value of the pair ID is an indication shared by redundant PDU sessions and configured to associate PDU sessions together as redundant.

26 . The first network entity of claim 25 , wherein the pair ID comprises a UE-generated pair ID and is included in a N2 session management (SM) container of the second PDU session request message, and wherein the second PDU session request message is responsive to a second PDU session establishment message which included the UE-generated pair ID.

27 . The first network entity of claim 26 , wherein, to associate the PDU session with the pair ID, the at least one processor is configured to modify one or more entries of a PDU table to indicate the pair ID.

28 . The first network entity of claim 25 , wherein the at least one processor is configured to:

receive the second PDU session request message responsive to a second PDU session establishment message; and

associate a second PDU session indicated by the second PDU session request message with the pair ID, wherein, to associate the second PDU session with the pair ID, the at least one processor is configured to associate the PDU session and the second PDU session as the redundant PDU sessions.

29 . A first network entity for wireless communication comprising:

a memory; and

at least one processor coupled to the memory, wherein the at least one processor is configured to:

receive, from a user equipment (UE), a protocol data unit (PDU) session establishment message and a pair identifier (ID) generated by the UE; and

transmit a PDU session request message for a second PDU session responsive to the PDU session establishment message, the PDU session request message including the pair ID, wherein a value of the pair ID is an indication shared by redundant PDU sessions and configured to associate the second PDU session and a prior, first PDU session together as redundant.

30 . The first network entity of claim 29 , wherein the at least one processor is configured to:

receive from the UE, a PDU session modification request message including remove information corresponding to the pair ID; and

transmit, to a second network entity, a PDU session modification message indicating removal of the pair ID.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 3, 2022
From: ZHANG, JUAN; ZISIMOPOULOS, HARIS
To: QUALCOMM INCORPORATED
Reel/Frame 061058/0546 →
Continuity (1)
Related Publication 20230156831A1 · May 18, 2023
References Cited (15)
US 20160212030A1 · Racz et al. · 2016 [cited by applicant]
US 20190364607A1 · Lai et al. · 2019 [cited by applicant]
US 20210250788A1 · Kim · 2021 [cited by examiner]
CN 110475381A · 2019 [cited by applicant]
CN 110536332A · 2019 [cited by applicant]
KR 1020190123065 · 2019 [cited by examiner]
WO WO2019130048A1 · 2019 [cited by applicant]
NEC: “URLLC KI-1 Solution 1—Updates Related to the URLLC Support by the Network”, SA WG2 Meeting #130, S2-1900342, Jan. 21, 2019-Jan. 25, 2019, Kochi, India, Jan. 15, 2019, 6 Pages, Section 6.1. [cited by applicant]
Ericsson: “Evaluation of Solution# 1: Redundant User Plane Paths Based on Dual Connectivity”, 3GPP TSG-SA WG2 Meeting #129, S2-1810109 Oct. 19, 2018 (Oct. 19, 2018), 8 pages, section 6.1. [cited by applicant]
International Search Report and Written Opinion—PCT/CN2019/124194—ISA/EPO—Aug. 27, 2020. [cited by applicant]
NEC: “URLLC KI-1 Solution 1—Updates Related to the URLLC Support by the Network”, SA WG2 Meeting #130, S2-1900342, Jan. 25, 2019 (Jan. 25, 2019), 6 pages, section 6.1.1. [cited by applicant]
LG Electronics: “Clarification on PDU Session Pair Information to NG-RAN”, 3GPP TSG-SA2 Meeting #136, S2-1911235, 3rd Generation Partnership Project, Mobile Competence Centre, 650, Route Des Lucioles, F-06921 Sophia-Ant… [cited by applicant]
LG Electronics: “Discussion on PDU Session Pair Information Between Two SMFs”, 3GPP TSG-SA2 Meeting #135, S2-1909850, 3rd Generation Partnership Project, Mobile Competence Centre, 650, Route Des Lucioles, F-06921 Sophia… [cited by applicant]
Supplementary European Search Report—EP19955591—Search Authority—Berlin—Aug. 3, 2023. [cited by applicant]
NEC: “URLLC KI-1 Solution 1—Updates Related to the URLLC Support by the Network”, SA WG2 Meeting #130, S2-1900342, Jan. 21, 2019-Jan. 25, 2019, Kochi, India, Jan. 15, 2019, 6 Pages. [cited by applicant]