IP Library › Granted Patent US 12,250,738
Granted Patent B2
US 12,250,738 · App. 18/194,234 · Granted Mar 11, 2025

Method for allocating bearer identifier, apparatus, and system

Inventors: Yang Xin (Shanghai, CN); Xiaobo Wu (Shenzhen, CN); Weiwei Chong (Shenzhen, CN); Runze Zhou (Shanghai, CN)
Assignee: HUAWEI TECHNOLOGIES CO., LTD.
H04W76/11H04W8/08H04W28/0268H04W36/08H04W36/144H04W36/324H04W80/10
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,250,738
App. No.
18/194,234
Granted
Mar 11, 2025
Kind
B2
Abstract

A session management method, an access management function device, and a session management device, where the method is carried out by an access and mobility management network element and includes: obtaining first subscription data of a terminal in a first communications network and second subscription data of the terminal in a second communications network, where the first subscription data includes a data network name (DNN), and the second subscription data includes an access point name (APN) corresponding to the DNN; allocating a bearer identifier to a bearer in a packet data network (PDN) connection corresponding to the APN; receiving a flow identifier that is of a flow in a protocol data unit (PDU) session corresponding to the DNN and that is sent by a session management network element; and sending the bearer identifier and the flow identifier to the terminal.

Claims (54)

1. A method comprising:

receiving, by a first communication network and from a terminal, a request for modifying a protocol data unit (PDU) session related to a service; and

providing, by the first communication network to the terminal, in response to the request, and based on terminal capability information, a bearer identifier and a flow identifier,

wherein the terminal capability information indicates that the terminal supports communication between the terminal and a second communication network,

wherein the bearer identifier identifies a bearer in the second communication network,

wherein the bearer corresponds to a flow that is of the PDU session and that is in the first communication network, and

wherein the flow identifier identifies the flow.

2. The method of claim 1 , further comprising providing, by the second communication network, the service to the terminal.

3. The method of claim 1 , wherein the first communication network is a fifth-generation (5G) communication network, and wherein the second communication network is a Long-Term Evolution Advanced Pro (4.5G) communication network or a fourth-generation (4G) communication network.

4. The method of claim 1 , wherein the bearer is a dedicated bearer.

5. The method of claim 4 , wherein the flow is a dedicated flow.

6. The method of claim 1 , further comprising:

receiving, by an access and mobility management network element in the first communication network, from a session management network element in the first communication network, and during a procedure for establishing the flow, a bearer identifier assignment request message;

allocating, by the access and mobility management network element, the bearer identifier to the bearer; and

sending, by the access and mobility management network element and to the session management network element, a bearer identifier assignment response message comprising the bearer identifier.

7. The method of claim 6 , further comprising:

receiving, by the access and mobility management network element and from an access network device in the first communication network, a handover request requesting to hand over the terminal from the first communication network to the second communication network;

sending, by the access and mobility management network element, to the session management network element, and in response to the handover request, a session context request message; and

receiving, by the access and mobility management network element and from the session management network element, a session context response message comprising the bearer identifier.

8. The method of claim 7 , further comprising providing, by the second communication network and to the terminal, the service by using the access and mobility management network element to send, to a mobility management entity in the second communication network, a relocation request comprising indication information, wherein the indication information instructs the mobility management entity to reselect a serving gateway in the second communication network.

9. The method of claim 6 , further comprising receiving, by the access and mobility management network element and from the terminal, a registration request message comprising indication information indicating that the terminal supports communication between the terminal and the second communication network.

10. The method of claim 6 , wherein receiving, by the first communication network and from the terminal, the request comprises receiving, by the access and mobility management network element, from the terminal, and before receiving the bearer identifier assignment request message, the request, wherein the request is a PDU session modification request message, wherein the method further comprises:

sending, by the access and mobility management network element and to the session management network element, the PDU session modification request message; and

receiving, by the access and mobility management network element, from the session management network element, and after sending the bearer identifier assignment response message, a PDU session modification accept message comprising the bearer identifier and the flow identifier, and

wherein providing the bearer identifier and the flow identifier comprises sending, by the access and mobility management network element and to the terminal, the PDU session modification accept message.

11. The method of claim 10 , wherein the PDU session modification accept message further comprises first quality of service (QoS) parameters corresponding to the flow and second QoS parameters corresponding to the bearer.

12. The method of claim 11 , further comprising obtaining, by the session management network element, the first QoS parameters and the second QoS parameters.

13. A system comprising:

a first communication network configured to:

receive, from a terminal, a request for modifying a protocol data unit (PDU) session related to a service; and

provide, to the terminal, in response to the request, and based on terminal capability information, a bearer identifier and a flow identifier,

wherein the terminal capability information indicates that the terminal supports communication between the terminal and a second communication network,

wherein the bearer identifier identifies a bearer in the second communication network,

wherein the bearer corresponds to a flow that is of the PDU session and that is in the first communication network, and

wherein the flow identifier identifies the flow.

14. The system of claim 13 , further comprising the second communication network, wherein the second communication network is configured to provide the service to the terminal.

15. The system of claim 13 , wherein the first communication network is a fifth-generation (5G) communication network, and wherein the second communication network is a Long-Term Evolution Advanced Pro (4.5G) communication network or a fourth-generation (4G) communication network.

16. The system of claim 13 , wherein the bearer is a dedicated bearer.

17. The system of claim 16 , wherein the flow is a dedicated flow.

18. The system of claim 13 , wherein the first communication network comprises an access and mobility management network element and a session management network element, and wherein the access and mobility management network element is configured to:

receive, from the session management network element and during a procedure for establishing the flow, a bearer identifier assignment request message;

allocate the bearer identifier to the bearer; and

send, to the session management network element, a bearer identifier assignment response message comprising the bearer identifier.

19. The system of claim 18 , wherein the first communication network further comprises an access network device, and wherein the access and mobility management network element is further configured to:

receive, from the access network device, a handover request requesting to hand over the terminal from the first communication network to the second communication network;

send, to the session management network element and in response to the handover request, a session context request message; and

receive, from the session management network element, a session context response message comprising the bearer identifier.

20. A computer program product comprising instructions that are stored on a non-transitory computer-readable medium and that, when executed by one or more processors, cause an access and mobility management network element in a first communication network to:

receive, from a terminal, a request for modifying a protocol data unit (PDU) session related to a service; and

provide, to the terminal, in response to the request, and based on terminal capability information, a bearer identifier and a flow identifier,

wherein the terminal capability information indicates that the terminal supports communication between the terminal and a second communication network,

wherein the bearer identifier identifies a bearer in the second communication network,

wherein the bearer corresponds to a flow that is of the PDU session and that is in the first communication network, and

wherein the flow identifier identifies the flow.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 31, 2023
From: XIN, YANG; WU, XIAOBO; CHONG, WEIWEI; ZHOU, RUNZE
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 063193/0834 →
Continuity (4)
Continuation 17226398 · Apr 9, 2021
Continuation 16575585 · Sep 19, 2019
Continuation PCTCN2017077371 · Mar 20, 2017
Related Publication 20230328813A1 · Oct 12, 2023
References Cited (36)
US 10548046B2 · Cho et al. · 2020 [cited by applicant]
US 10681607B2 · Shah et al. · 2020 [cited by applicant]
US 10841933B2 · Hapsari et al. · 2020 [cited by applicant]
US 10980071B2 · Xin · 2021 [cited by examiner]
US 11622395B2 · Xin · 2023 [cited by examiner]
US 20160072930A1 · Shi et al. · 2016 [cited by applicant]
US 20190021043A1 · Myungjune et al. · 2019 [cited by applicant]
CN 101588548A · 2009 [cited by applicant]
CN 102986271A · 2013 [cited by applicant]
CN 103109553A · 2013 [cited by applicant]
KR 20160065168A · 2016 [cited by applicant]
WO 2011120235A1 · 2011 [cited by applicant]
WO 2016175926A1 · 2016 [cited by applicant]
WO 2017034352A1 · 2017 [cited by applicant]
113rd Generation Partnership Project; technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2; (Release 15), 3GPP Draft; 23.502-020, Feb. 24, 2017, 71 pages. [cited by applicant]
3GPP TS 23.003 V14.3.0; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification; (Release 14), Mar. 2017, 106 pages. [cited by applicant]
3GPP TS 23.401 V14.3.0, Mar. 2017, 3rd Generation Partnership Project; Technical Specification Group Services and System aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio … [cited by applicant]
3GPP TS 23.501 V0.3.0 (Feb. 2017); 3rd Generation Partnership Project; Technical Specification Group Services and System aspects; system architecture for the 5G System; Stage 2 (Release 15); 19 pages. [cited by applicant]
3GPP TS 23.501 V0.3.1 (Mar. 2017); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System; Stage 2 (Release 15), 97 pages. [cited by applicant]
3GPP TS 23.502 V0.2.0 (Feb. 2017), 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15), 71 pages. [cited by applicant]
3GPP TS 29.274 V14.3.0; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunelling Protocol for … [cited by applicant]
Ericsson, “23.502: 5G-EPC interworking,” SA WG2 Meeting #119, S2-170805, Feb. 13-17, 2017, Dubrovnik; Croatia, 6 pages. [cited by applicant]
Ericsson, Allocation of EPS bearer ID in 5GS, SA WG2 meeting #121, May 15-19, 2017, Hangzhou, China, s2-173322, 8 pages. [cited by applicant]
Ericsson, Correlation between EBI and QFI, 3GPP TSG-SA WG2 Meeting #127bis, May 28-Jun. 1, S2-184890, 5 pages. [cited by applicant]
Ericsson; 23.501: 5GC-EPC interworking, Sa WG2 meeting #11913, Feb. 17, 2017, Dubrovnik, Croatia, S2-170804; Interworking and Migration, 7 pages. [cited by applicant]
Huawei, et al., TS 23.501: Description of DNN SA WG2; S2-171064; Meeting #119; Feb. 13-17, 2017, Dubrovnik, Croatia, 3 pages. [cited by applicant]
Huawei, et al., TS 23.502: Addition of AMF service for EPS Bearer ID Allocation, SA WG2 Meeting #123, Oct. 23-27, 2017, Ljubjana, Slovenia, S2-177561, 5 pages. [cited by applicant]
Nokia, et al., 23.501 5.9.3: DNN Versus APN; SA WG2; S2-170888; Meeting #119; Feb. 13-17, 2017, Dubrovnik, Croatia; 2 pages. [cited by applicant]
Nokia; TS 23.502: P-CR for Single Registration-based Interworking from EPS to 5GS procedure; SA WG2 Meeting #119; S2-171013; Feb. 13-17, 2017, Dubrovnik, Croatia, 5 pages. [cited by applicant]
NTT DOCOMO “TS 23.502: Nx-Based Handover procedure,” 3GPP Draft, S2-171503, Feb. 17, 2017, 4 pages. [cited by applicant]
NTT DOCOMO, “Nx-based interworking procedures from QoS point of view,” SA WG2 meeting #119, S2-17xxxx, (S2-170936), Feb. 13-17, 2017, Dubrovnik, Croatia, 4pages. [cited by applicant]
NTT DOCOMO, et al., “TS 23.502: Nx-based Handover procedure,” 3GPP Draft; S2-171590, Feb. 18, 2017, 3 pages. [cited by applicant]
NTT Docomo, Intel; TS 23.502: Nx-based Handover procedure; S2-171608; SA WG2 Meeting #119, Feb. 2017, Dubrovnik, Croatia, 4 pages. [cited by applicant]
NTT DOCOMO: “TS 23.502: Nx-based Handover procedure,” 3GPP Draft; S2-170937, Feb. 13, 2017, 8 pages. [cited by applicant]
Qualcomm Incorporated, UE Capability related to integrity protection of DRBs for signaling of the maximum supported data rate per UE for integrity protection. 3GPP TSG-WG2 Meeting #127, Sanya, China, Apr. 16-20, 2018, S… [cited by applicant]
3GPP TS 23.203 V14.3.0; 3rd Generation Partnership Project; technical Specification Group Services and System Aspects; Policy and charging control architecture (Release 14); Mar. 2017, 256 pages. [cited by applicant]