# US 12,010,644 B2 · Method and system for handling service request procedure in communication network > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,010,644 B2 - Document ID: US12010644B2 - Status: Granted - Kind: B2 - Application number: 18/158,120 - Filed: 2023-01-23 - Published: 2023-05-25 - Granted: 2024-06-11 - Earliest claimed: 2018-03-23 - Assignees: Samsung Electronics Co., Ltd. - Applicants: Samsung Electronics Co., Ltd. - Inventors: Lalith Kumar; Kailash Kumar Jha; Nitesh Pushpak Shah; Ricky Kumar Kaura; Shweta M; Ajay Kumawat; Vikrant Bajaj - Web page: https://patentgrep.com/patent/US12010644B2 ## CPC - H04W 60/04: using triggered events - H04W 76/12: Setup of transport tunnels - H04W 8/08: Mobility data transfer - H04W 68/005: {Transmission of information for alerting of incoming communication} - H04W 76/11: Allocation or use of connection identifiers - H04W 80/08: Upper layer protocols {(network arrangements or communication protocols for networked applications H04L67/00)} - H04W 60/00: Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration - H04W 76/25: Maintenance of established connections - H04W 76/27: Transitions between radio resource control [RRC] states - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract The present disclosure relates to a communication method and system for converging a 5th-Generation (5G) communication system for supporting higher data rates beyond a 4th-Generation (4G) system with a technology for Internet of Things (IoT). The present disclosure may be applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. The method includes configuring, by a User Equipment (UE) (100), a Protocol Data Unit (PDU) session type as an always-ON type or a normal PDU type. Further, the method includes sending, by the UE (100), a PDU session establishment request message including the PDU session type to be the always-ON type or the normal PDU type to a network (200) during an initial PDU session establishment procedure. ## Claims ### Claim 1 A method performed by a terminal in a communication system, the method comprising: identifying a protocol data unit (PDU) session to be established as an always-on PDU session based on an indication from an upper layer; transmitting, to a network entity, a PDU session establishment request message including first information for requesting to establish the PDU session as the always-on PDU session; identifying whether a user-plane resource for the always-on PDU session is established, the always-on PDU session being established based on the PDU session establishment request message; and transmitting, to the network entity, a service request message associated with a change of a 5G system (5GS) mobility management (5GMM) mode, in case that the user-plane resource for the always-on PDU session is not established, wherein the service request message includes uplink data status information indicating the always-on PDU session for which data is pending. ### Claim 2 (depends on 1) The method of claim 1, further comprising: receiving, from the network entity, a PDU session establishment accept message as a response to the PDU session establishment request message, the PDU session establishment accept message including second information indicating whether the PDU session is to be established as the always-on PDU session. ### Claim 3 (depends on 2) The method of claim 2, further comprising: determining that the established PDU session is considered as the always-on PDU session, in case that the second information indicates that the PDU session is required as the always-on PDU session; and determining that the established PDU session is not considered as the always-on PDU session, in case that the second information indicates that the PDU session is not allowed as the always-on PDU session. ### Claim 4 (depends on 1) The method of claim 1, further comprising: receiving, from the network entity, a PDU session modification command message including third information on an always-on PDU session indication; determining that the PDU session is considered as the always-on PDU session, in case that the third information indicates that the PDU session is required as the always-on PDU session; and determining that the PDU session is not considered as the always-on PDU session, in case that the third information indicates that the PDU session is not allowed as the always-on PDU session. ### Claim 5 A method performed by a network entity in a communication system, the method comprising: receiving, from a terminal, a protocol data unit (PDU) session establishment request message including first information for requesting to establish the PDU session as an always-on PDU session; and receiving, from the terminal, a service request message associated with a change of a 5G system (5GS) mobility management (5GMM) mode, in case that a user-plane resource for the always-on PDU session is not established, the always-on PDU session being established based on the PDU session establishment request message, wherein the service request message includes uplink data status information indicating the always-on PDU session for which data is pending. ### Claim 6 (depends on 5) The method of claim 5, further comprising: transmitting, to the terminal, a PDU session establishment accept message as a response to the PDU session establishment request message, the PDU session establishment accept message including second information indicating whether the PDU session is to be established as the always-on PDU session. ### Claim 7 (depends on 6) The method of claim 6, wherein the established PDU session is considered as the always-on PDU session, in case that the second information indicates that the PDU session is required as the always-on PDU session, and wherein the established PDU session is not considered as the always-on PDU session, in case that the second information indicates that the PDU session is not allowed as the always-on PDU session. ### Claim 8 (depends on 5) The method of claim 5, further comprising: transmitting, to the terminal, a PDU session modification command message including third information on an always-on PDU session indication, wherein the PDU session is considered as the always-on PDU session, in case that the third information indicates that the PDU session is required as the always-on PDU session, and wherein the PDU session is not considered as the always-on PDU session, in case that the third information indicates that the PDU session is not allowed as the always-on PDU session. ### Claim 9 A terminal in a communication system, the terminal comprising: a transceiver; and at least one processor coupled with the transceiver and configured to: identify a protocol data unit (PDU) session to be established as an always-on PDU session based on an indication from an upper layer, transmit, to a network entity, a PDU session establishment request message including first information for requesting to establish the PDU session as the always-on PDU session, identify whether a user-plane resource for the always-on PDU session is established, the always-on PDU session being established based on the PDU session establishment request message, and transmit, to the network entity, a service request message associated with a change of a 5G system (5GS) mobility management (5GMM) mode, in case that the user-plane resource for the always-on PDU session is not established, wherein the service request message includes uplink data status information indicating the always-on PDU session for which data is pending. ### Claim 10 (depends on 9) The terminal of claim 9, wherein the at least one processor is further configured to: receive, from the network entity, a PDU session establishment accept message as a response to the PDU session establishment request message, the PDU session establishment accept message including second information indicating whether the PDU session is to be established as the always-on PDU session. ### Claim 11 (depends on 10) The terminal of claim 10, wherein the at least one processor is further configured to: determine that the established PDU session is considered as the always-on PDU session, in case that the second information indicates that the PDU session is required as the always-on PDU session, and determine that the established PDU session is not considered as the always-on PDU session, in case that the second information indicates that the PDU session is not allowed as the always-on PDU session. ### Claim 12 (depends on 9) The terminal of claim 9, wherein the at least one processor is further configured to: receive, from the network entity, a PDU session modification command message including third information on an always-on PDU session indication, determine that the PDU session is considered as the always-on PDU session, in case that the third information indicates that the PDU session is required as the always-on PDU session, and determine that the PDU session is not considered as the always-on PDU session, in case that the third information indicates that the PDU session is not allowed as the always-on PDU session. ### Claim 13 A network entity in a communication system, the network entity comprising: a transceiver; and at least one processor coupled with the transceiver and configured to: receive, from a terminal, a protocol data unit (PDU) session establishment request message including first information for requesting to establish the PDU session as an always-on PDU session, and receive, from the terminal, a service request message associated with a change of a 5G system (5GS) mobility management (5GMM) mode, in case that a user-plane resource for the always-on PDU session is not established, the always-on PDU session being established based on the PDU session establishment request message, wherein the service request message includes uplink data status information indicating the always-on PDU session for which data is pending. ### Claim 14 (depends on 13) The network entity of claim 13, wherein the at least one processor is further configured to: transmit, to the terminal, a PDU session establishment accept message as a response to the PDU session establishment request message, the PDU session establishment accept message including second information indicating whether the PDU session is to be established as the always-on PDU session. ### Claim 15 (depends on 14) The network entity of claim 14, wherein the established PDU session is considered as the always-on PDU session, in case that the second information indicates that the PDU session is required as the always-on PDU session, and wherein the established PDU session is not considered as the always-on PDU session, in case that the second information indicates that the PDU session is not allowed as the always-on PDU session. ### Claim 16 (depends on 13) The network entity of claim 13, wherein the at least one processor is further configured to: transmit, to the terminal, a PDU session modification command message including third information on an always-on PDU session indication, wherein the PDU session is considered as the always-on PDU session, in case that the third information indicates that the PDU session is required as the always-on PDU session, and wherein the PDU session is not considered as the always-on PDU session, in case that the third information indicates that the PDU session is not allowed as the always-on PDU session.