Search

KR-20260066636-A - SESSION MANAGEMENT METHOD APPLYING NON-3GPP DEVICE RELATED INFORMATION TO SESSION OF MOBILE COMMUNICATION NETWORK AND COMMUNICATION SYSTEM PROVIDING THE SAME

KR20260066636AKR 20260066636 AKR20260066636 AKR 20260066636AKR-20260066636-A

Abstract

A session management method performed by a core network according to an embodiment of the present invention includes: receiving a packet data unit (PDU) session modification request with non-3GPP device connection information applied from a user device (User Equipment, UE) or a 5G residential gateway (5G-RG) using an access and mobility management function (AMF); and determining whether to reject the PDU session modification request using at least one of a session management function (SMF) or a policy control function (PCF).

Inventors

  • 이수환

Assignees

  • 한국전자통신연구원

Dates

Publication Date
20260512
Application Date
20251103
Priority Date
20241104

Claims (20)

  1. A core network receiving a packet data unit (PDU) session modification request from a User Equipment (UE) or a 5G Residential Gateway (5G-RG) that includes Non-3GPP Device Connection Information; and The core network determines whether to reject the PDU session modification request by using at least one of a session management function (SMF) or a policy control function (PCF); including, Session management method for mobile communication networks.
  2. In paragraph 1, The step of determining whether to reject the above PDU session modification request is, Determining whether to reject the PDU session modification request based on whether the non-3GPP device identifier included in the non-3GPP device connection information applied to the PDU session modification request is available according to information stored in the unified data repository (UDR) for the user device (UE) or 5G-RG. Session management method for mobile communication networks.
  3. In paragraph 1, The step of determining whether to reject the above PDU session modification request is, A step of determining whether a non-3GPP device identifier included in the non-3GPP device connection information applied to the PDU session modification request is available using a unified data repository (UDR); A step of determining whether to reject a Session Management Policy Association Modification request generated based on the PDU session modification request, based on whether the non-3GPP device identifier is available, using the PCF; and A step of rejecting the PDU session modification request when the session management policy association modification request is rejected by the PCF using the above SMF; including, Session management method for mobile communication networks.
  4. In paragraph 3, The step of determining whether to reject the above PDU session modification request is, If the above session management policy association modification request is rejected, a step of notifying the SMF of the rejection of the session management policy association modification request using the PCF, indicating that the non-3GPP device identifier is not available for the user device (UE) or 5G-RG; including, Session management method for mobile communication networks.
  5. In paragraph 3, If the above PDU session modification request is rejected, A step of notifying the user device (UE) or 5G-RG, via the access and mobility management function (AMF), of the rejection of the PDU session modification request, along with a cause code notifying that the non-3GPP device identifier is not available for the user device (UE) or 5G-RG, using the above SMF; including, Session management method for mobile communication networks.
  6. In paragraph 1, The above-mentioned core network receives a request to update the session management context of a PDU session generated from an access and mobility management function (AMF) based on a request to modify the PDU session, using a session management function (SMF); including, Session management method for mobile communication networks.
  7. In paragraph 1, The core network updates session management context information based on the PDU session modification request so that the non-3GPP device connection information is applied, using the SMF and the PCF; including, Session management method for mobile communication networks.
  8. A core network receiving a packet data unit (PDU) session modification request containing non-3GPP device connection information from a User Equipment (UE) or a 5G Residential Gateway (5G-RG) using an access and mobility management function (AMF); and The core network transmits the packet data unit (PDU) session context update result or PDU session modification result to the user device (UE) or 5G Residential Gateway (5G-RG) via the AMF, wherein the non-3GPP device connection information is applied; including, Session management method for mobile communication networks.
  9. In paragraph 8, The above core network receives a session management context update request generated from the above AMF based on the PDU session modification request using a session management function (SMF); and The core network performs a session management policy association modification procedure for differentiated QoS handling of traffic with the user device (UE) or 5G-RG based on a non-3GPP device identifier included in the non-3GPP device connection information, using the SMF and the policy control function (PCF); including, Session management method for mobile communication networks.
  10. In Paragraph 9, The step of executing the above session management policy association modification procedure is, The core network generates or updates Policy and Charging Control (PCC) rules based on the non-3GPP device identifier and the user plane address corresponding to the non-3GPP device identifier using the PCF; The core network determines Quality of Service (QoS) parameters within the PCC rules based on the non-3GPP device identifier or operator policy using the PCF; and The core network updates a session management context for differentiated QoS handling of traffic with the user device (UE) or 5G-RG based on the QoS parameters using the SMF; including Session management method for mobile communication networks.
  11. In Paragraph 10, The step of determining Quality of Service (QoS) parameters within the above PCC rule is: Determining QoS parameters within the PCC rule based on a QoS reference or individual QoS parameter associated with the non-3GPP device identifier obtained from the unified data repository (UDR) using the non-3GPP device identifier. Session management method for mobile communication networks.
  12. In Paragraph 9, The core network, after receiving the session management context update request, updates the session management information of the user plane function (UPF) using the SMF so that the non-3GPP device connection information is applied; including, Session management method for mobile communication networks.
  13. In paragraph 8, The step of transmitting the above PDU session context update result or PDU session modification result to the user device (UE) or 5G-RG via the above AMF is: The core network responds to an AMF with a PDU session context update result or a PDU session modification result to which the non-3GPP device connection information is applied, using an SMF; and The core network notifies the user device (UE) or 5G-RG of a PDU session context update result or a PDU session modification result to which the non-3GPP device connection information is applied, using an AMF; including, Session management method for mobile communication networks.
  14. At least one entity; Includes, and at least one of the entities, Memory for storing at least one computer-readable instruction; and A processor that executes at least one of the above instructions; Includes, The above at least one entity is, Using the access and mobility management function (AMF), receive a packet data unit (PDU) session modification request from a User Equipment (UE) or a 5G Residential Gateway (5G-RG) that includes non-3GPP device connection information, and Determining whether to reject the PDU session modification request by using at least one of a session management function (SMF) or a policy control function (PCF). Communication system.
  15. In Paragraph 14, The above at least one entity is, Determining whether to reject the PDU session modification request based on whether the non-3GPP device identifier included in the non-3GPP device connection information applied to the PDU session modification request is available according to information stored in the unified data repository (UDR) for the user device (UE) or 5G-RG. Communication system.
  16. In Paragraph 14, The above at least one entity is, Determining whether a non-3GPP device identifier included in the non-3GPP device connection information applied to the PDU session modification request is available using a unified data repository (UDR), and Using the above PCF, determine whether to reject a Session Management Policy Association Modification request generated based on the PDU session modification request based on whether the above non-3GPP device identifier is available, and Using the above SMF, if the session management policy association modification request is rejected by the above PCF, the above PDU session modification request is rejected, Communication system.
  17. In Paragraph 16, The above at least one entity is, If the above session management policy association modification request is rejected, the rejection of the session management policy association modification request is notified to the SMF using the PCF, indicating that the non-3GPP device identifier is not available for the user device (UE) or 5G-RG, and If the above PDU session modification request is rejected, the rejection of the PDU session modification request is notified to the user device (UE) or 5G-RG via the AMF, using the SMF, along with a cause code notifying that the non-3GPP device identifier is not available for the user device (UE) or 5G-RG. Communication system.
  18. In Paragraph 14, The above at least one entity is, Transmitting the result of a packet data unit (PDU) session context update or the result of modifying a PDU session to which the above non-3GPP device connection information is applied, to the user device (UE) or 5G Residential Gateway (5G-RG) access network via the above AMF. Communication system.
  19. In Paragraph 14, The above at least one entity is, Using the above PCF, generate or update Policy and Charging Control (PCC) rules based on the above non-3GPP device identifier and the user plane address corresponding to the above non-3GPP device identifier, and The core network determines Quality of Service (QoS) parameters within the PCC rules based on the non-3GPP device identifier or operator policy using the PCF, and The core network updates a session management context for differentiated QoS handling of traffic with the user device (UE) or 5G-RG based on the QoS parameters using the SMF, Communication system.
  20. In Paragraph 14, The above non-3GPP device connection information includes a device identifier and a user plane address bound to the non-3GPP device for QoS differentiation between PDU sessions involving the user device (UE), or for differentiation between QoS flows within a PDU session involving the user device (UE). Communication system.

Description

Session management method applying non-3GPP device-related information to a session of a mobile communication network and communication system providing the same The present invention belongs to the field of communication technology, and specifically relates to a technology for managing and updating packet data unit (PDU) sessions of a mobile communication network. The content described in this section merely provides background information regarding the present embodiment and does not constitute prior art. In wireless communication networks, electronic devices such as base stations (BS) and user equipment (UE) communicate wirelessly with each other to transmit or receive data. Sensing is the process of acquiring information about the surroundings of a device. Sensing can also be used to detect information about objects, such as their location, speed, distance, direction, shape, and texture. This information can be used to improve communication within the network and for other specific purposes. Sensing in communication networks has typically been limited to active sensing techniques involving devices that receive and process radio frequency (RF) sensing reference signals. Other sensing techniques, such as passive sensing (e.g., radar) and non-RF sensing (e.g., video imaging and other sensors), can address some of the limitations of active sensing; however, these other techniques are typically standalone systems implemented separately from the communication network. 5G communication systems are designed with a focus on communication functions, while sensing technology is performed in a separate, independent system. Sensing technology independent of the communication system leads to inefficient use of resources and acts as a major factor in degrading the reliability and quality of integrated sensing data. Therefore, solutions to these problems are required. FIG. 1 is a conceptual diagram illustrating a wireless signal-based sensing service including a wireless sensing UE that recognizes and utilizes a non-3GPP device according to an embodiment of the present invention, and a core network supporting the service. Figure 2 is a diagram conceptually illustrating the architecture of the core network of Figure 1. FIGS. 3 to 6 are operation flowcharts illustrating processes between a non-3GPP device associated UE (associated UE), (R)AN, and a plurality of network functions within a core network for a session management method according to an embodiment of the present invention. FIG. 7 is an operation flowchart illustrating a session management method for utilizing a non-3GPP device within a mobile communication network according to an embodiment of the present invention. FIG. 8 is an operation flowchart illustrating a session management method for utilizing a non-3GPP device within a mobile communication network according to another embodiment of the present invention. FIG. 9 is a conceptual diagram illustrating an example of a generalized computing system in which a user device (UE) associated with a non-3GPP device, (R)AN, an entity within a core network, a sensing entity that interacts with the core network and participates in the sensing process, or a part thereof, is implemented, capable of performing at least a part of the processes of FIG. 1 to 8. The present invention is capable of various modifications and may have various embodiments, and specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the invention to specific embodiments, and it should be understood that the invention includes all modifications, equivalents, and substitutions that fall within the spirit and scope of the invention. Terms such as "first," "second," etc., may be used to describe various components, but said components should not be limited by said terms. These terms are used solely for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be named the second component, and similarly, the second component may be named the first component. The term "and/or" includes a combination of a plurality of related described items or any of a plurality of related described items. In the embodiments of the present application, "at least one of A and B" may mean "at least one of A or B" or "at least one of one or more combinations of A and B". Additionally, in the embodiments of the present application, "at least one of A and B" may mean "at least one of A or B" or "at least one of one or more combinations of A and B". When it is stated that one component is "connected" or "connected" to another component, it should be understood that while it may be directly connected or connected to that other component, there may also be other components in between. On the other hand, when it is stated that one component is "directly connected" or "directly connected" to another component, it should b