IP Library Granted Patent US 12,207,325
Granted Patent B2
US 12,207,325 · App. 17/571,785 · Granted Jan 21, 2025

Method and apparatus for operating wireless communication system having separated mobility management and session management

Inventors: Jinsung Lee (Suwon-si, KR); Kisuk Kweon (Suwon-si, KR); Jungshin Park (Seoul, KR); Daegyun Kim (Seongnam-si, KR); Sangjun Moon (Seoul, KR); Beomsik Bae (Suwon-si, KR); Joohyung Lee (Gwacheon-si, KR); Jicheol Lee (Suwon-si, KR); Hyungho Lee (Seoul, KR)
Assignee: Samsung Electronics Co., Ltd.
H04W76/12H04W76/11H04W76/32H04W92/045
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,207,325
App. No.
17/571,785
Filed
Jan 10, 2022
Granted
Jan 21, 2025
Kind
B2
Art Unit
2477
USPC
370/329
Abstract

The present invention defines signaling required for separating a network entity (NE) responsible for mobility management (MM) and session management (SM), which are main function of a control plane (CP) in a next generation (NextGen) mobile communication system, and presents a basic procedure for providing mobile communication services including the signaling. Therefore, complexity of core equipment responsible for the CP is reduced in order to implement a network slice function and provide various levels of mobility, and an effect of minimizing a signaling load therebetween can be obtain. In addition, it is possible to efficiently manage the resources of a base station (radio access network (RAN)) and a user plane network entity (UP NF).

Claims (53)

1. A method performed by an access and mobility management function (AMF) in a communication system, the method comprising:

receiving, from a terminal via a base station, a service request message including information for identifying a protocol data unit (PDU) session for which a user plane (UP) connection is to be activated, the PDU session being included in at least one PDU session established for the terminal, wherein the terminal is in an idle state and the UP connection is in a deactivated state;

transmitting, to a session management function (SMF) associated with the PDU session, a first message to activate the UP connection for the PDU session;

receiving, from the SMF, a second message including the information for identifying the PDU session and information on a user plane function (UPF) associated with the PDU session, as a response to the first message;

transmitting, to the base station, a third message including the information for identifying the PDU session and the information on the UPF associated with the PDU session;

receiving, from the base station, a fourth message including tunnel information associated with the base station, as a response to the third message: and

transmitting, to the SMF, a fifth message including the tunnel information associated with the base station,

wherein the UP connection includes a data radio bearer (DRB) between the terminal and the base station and an N 3 tunnel between the base station and the UPF associated with the PDU session, and

wherein downlink data is transmitted from the UPF to the terminal, after the fifth message is transmitted.

2. The method of claim 1 ,

wherein the information for identifying the PDU session includes a PDU session identifier (ID), and

wherein the information on the UPF includes tunnel information associated with the UPF.

3. The method of claim 1 , wherein the DRB is setup based on quality of service (QOS) information of the PDU session.

4. The method of claim 1 , wherein only the UP connection of the PDU session is activated for uplink data among at least one UP connection of the at least one PDU session.

5. A method performed by a terminal in a communication system, the method comprising:

identifying uplink data to be transmitted in an idle state;

transmitting, to an access and mobility management function (AMF) via a base station, a service request message including information for identifying a protocol data unit (PDU) session for which a user plane (UP) connection is to be activated, the PDU session being included in at least one PDU session established for the terminal, wherein the UP connection is in a deactivated state, wherein a message to activate the UP connection for the PDU session is transmitted from the AMF to a session management function (SMF) associated with the PDU session, and wherein the information for identifying the PDU session and information on a user plane function (UPF) associated with the PDU session are transmitted from the SMF to the base station via the AMF;

receiving, from the base station, a radio resource control (RRC) message for setting up a data radio bearer (DRB) for the PDU session; and

forwarding, to the UPF, the uplink data via the DRB, wherein the UP connection includes the DRB between the terminal and the base station and an N 3 tunnel between the base station and the UPF associated with the PDU session, and

wherein downlink data is received from the UPF, after tunnel information associated with the base station is transmitted from the base station to the SMF via the AMF.

6. The method of claim 5 , wherein the information for identifying the PDU session includes a PDU session identifier (ID), and wherein the information on the UPF includes tunnel information associated with the UPF.

7. The method of claim 5 , wherein the data radie bearer between the terminal and the base station-DRB_is setup based on quality of service (QOS) information of the PDU session.

8. The method of claim 5 , wherein only the UP connection of the PDU session is activated for uplink data among at least one UP connection of the at least one PDU session.

9. An access and mobility management function (AMF) in a communication system, the AMF comprising:

a transceiver; and

a controller configured to:

control the transceiver to receive, from a terminal via a base station, a service request message including information for identifying a protocol data unit (PDU) session for which a user plane (UP) connection is to be activated, the PDU session being included in at least one PDU session established for the terminal, wherein the terminal is in an idle state and the UP connection is in a deactivated state,

control the transceiver to transmit, to a session management function (SMF) associated with the PDU session, a first message to activate the UP connection for the PDU session,

control the transceiver to receive, from the SMF, a second message including the information for identifying the PDU session and information on a user plane function (UPF) associated with the PDU session, as a response to the first message,

control the transceiver to transmit, to the base station, a third message including the information for identifying the PDU session and the information on the UPF associated with the PDU session,

control the transceiver to receive, from the base station, a fourth message including tunnel information associated with the base station, as a response to the third message, and

control the transceiver to transmit, to the SMF, a fifth message including the tunnel information associated with the base station,

wherein the UP connection includes a data radio bearer (DRB) between the terminal and the base station and an N 3 tunnel between the base station and the UPF associated with the PDU session, and

wherein downlink data is transmitted from the UPF to the terminal, after the fifth message is transmitted.

10. The AMF of claim 9 ,

wherein the information for identifying the PDU session includes a PDU session identifier (ID), and

wherein the information on the UPF includes tunnel information associated with the UPF.

11. The AMF of claim 9 , wherein the DRB is setup based on quality of service (QOS) information of the PDU session.

12. The AMF of claim 9 , wherein only the UP connection of the PDU session is activated for uplink data among at least one UP connection of the at least one PDU session.

13. A terminal in a communication system, the terminal comprising:

a transceiver; and

a controller configured to:

identify uplink data to be transmitted in an idle state,

control the transceiver to transmit, to an access and mobility management function (AMF) via a base station, a service request message including information for identifying a protocol data unit (PDU) session for which a user plane (UP) connection is to be activated, the PDU session being included in at least one PDU session established for the terminal, wherein the UP connection is in a deactivated state, wherein a message to activate the UP connection for the PDU session is transmitted from the AMF to a session management function (SMF) associated with the PDU session, and wherein the information for identifying the PDU session and information on a user plane function (UPF) associated with the PDU session are transmitted from the SMF to the base station via the AMF,

control the transceiver to receive, from the base station, a radio resource control (RRC) message for setting up a data radio bearer (DRB) for the PDU session, and

control the transceiver to forward, to the UPF, the uplink data via the DRB,

wherein the UP connection includes the DRB between the terminal and the base station and an N3 tunnel between the base station and the UPF associated with the PDU session, and

wherein downlink data is received from the UPF, after tunnel information asociated with the base station is transmitted from the base station to the SMF via the AMF.

14. The terminal of claim 13 ,

wherein the information for identifying the PDU session includes a PDU session identifier (ID), and

wherein the information on the UPF includes tunnel information associated with the UPF.

15. The terminal of claim 13 , wherein the data radio bearer between the terminal and the base station is setup based on quality of service (QOS) information of the PDU session.

16. The terminal of claim 13 , wherein only the UP connection of the PDU session is activated for uplink data among at least one UP connection of the at least one PDU session.

Continuity (3)
Continuation 16327139
Provisional Application 62377889 · Aug 22, 2016
Related Publication 20220174759A1 · Jun 2, 2022
References Cited (38)
US 10098042B2 · Lee et al. · 2018 [cited by applicant]
US 10356689B2 · Chan · 2019 [cited by applicant]
US 20070104116A1 · Olvera-Hernandez · 2007 [cited by applicant]
US 20080233947A1 · Herrero-Veron · 2008 [cited by applicant]
US 20090016258A1 · Zhang et al. · 2009 [cited by applicant]
US 20170127471A1 · Yu et al. · 2017 [cited by applicant]
US 20170290082A1 · Salkintzis · 2017 [cited by applicant]
US 20170374542A1 · Ryu et al. · 2017 [cited by applicant]
US 20180227807A1 · Youn et al. · 2018 [cited by applicant]
US 20190208465A1 · Mihaly et al. · 2019 [cited by applicant]
US 20190208573A1 · Yang · 2019 [cited by examiner]
US 20190274178A1 · Salkintzis · 2019 [cited by examiner]
US 20190313473A1 · Kim · 2019 [cited by examiner]
US 20190335330A1 · Salkintzis · 2019 [cited by examiner]
US 20190357130A1 · Garcia Azorero · 2019 [cited by examiner]
US 20190364541A1 · Ryu · 2019 [cited by examiner]
US 20200008052A1 · Bas Sanchez · 2020 [cited by examiner]
US 20200059989A1 · Velev · 2020 [cited by examiner]
US 20200068587A1 · Garcia Azorero · 2020 [cited by examiner]
US 20200099742A1 · Puente Pestaña · 2020 [cited by examiner]
US 20200170055A1 · Dou · 2020 [cited by examiner]
EP 2214451B1 · 2012 [cited by applicant]
KR 1020080063844A · 2008 [cited by applicant]
KR 1020100037601A · 2010 [cited by applicant]
WO 2016114611A1 · 2016 [cited by applicant]
Siwar Ben Hadj Said, 'New Control Plane in 3GPP Lte/Epc Architecture for On-Demand Connectivity Service, In: Cloud Networking(CloudNet) 2013: 2nd IEEE International Conference on Cloud Networking, San Francisco, United … [cited by applicant]
Hailan Peng, ‘Extended User/Control Plane Architectures for Tightly Coupled LTE/WiGig Interworking in Millimeter-wave Heterogeneous Networks’, In: 2015 IEEE Wireless Communications and Networking Conference (WCNC): Trac… [cited by applicant]
Extended European Search Report dated May 9, 2019, issued in a counterpart European application No. 17843923.8-1215 / 3490297. [cited by applicant]
Samsung: “Update to Solution 5.3: Re-selection of user-plane path based on UE traffic pattern”, 3GPP Draft; 62-163984_WAS_S2-163298, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Route Des Lu… [cited by applicant]
Qualcomm Incorporated: “Solution X for Key Issue 4 on Session Management”, 3GPP Draft; S2-162264_E-MAIL_REV1 0_S2-162159-WAS-162091-WAS-162087-WAS-161494-NEXTGEN-SM, 3rd Generation Partnership Project (3GPP), Mobile Com… [cited by applicant]
China Mobile: “Work Task Description on Session Management”, 3GPP Draft; S2-162931 WAS 2419-WTS#4-SM-V5, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Route Des Lucioles ; F-06921 Sophia-Anti… [cited by applicant]
European Office Action dated May 13, 2020, issued in a counterpart European application No. 17 843 923.8-1215. [cited by applicant]
Huawei, HiSilicon, CATT; 3GPP TSG SA WG2 Meeting #116; Solution to 4.x: The interaction between MM and SM; Discussion and approval; S2-164107; Jul. 17, 2016, Vienna, Austria. [cited by applicant]
Motorola Mobility, Lenovo; SA WG2 Meeting #120; Corrections to PDU session establishment procedure; Approval; S2-171948; Mar. 21, 2017, Busan, South Korea. [cited by applicant]
Indian Office Action dated Sep. 15, 2021, issued in a counterpart an Indian Application No. 201937006961. [cited by applicant]
European Office Action dated Nov. 5, 2021, issued in a counterpart an Indian Application No. 17 843 923.8-1215. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System (Release 14)”, 3GPP Standard; 3GPP TR23.799, 3rd Generation Partnership Pr… [cited by applicant]
European Notification of Allowance dated Oct. 4, 2023, issued in European Patent Application No. 17843923.8. [cited by applicant]