Method and apparatus for reporting PDU session information
The method enables efficient management of diverse 5G services by transmitting URSP-related terminal capability information between V-PCF and H-PCF, addressing scalability issues in 5G Core networks by enforcing terminal routing policies and improving network management.
Patent Information
- Application Number
- PCT/KR2024/006321
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-12
- Filing Date
- 2024-05-10
- Publication Date
- 2024-11-21
AI Technical Summary
The 5G communication system faces challenges in managing diverse terminal types and services, such as eMBB, URLLC, and mMTC, which require different network characteristics, leading to scalability issues due to the reliance on a single Mobility Management Entity (MME) for signaling and session management in 4G LTE networks.
The proposed method involves the V-PCF in a VPLMN transmitting URSP-related terminal capability information to the H-PCF in an HPLMN, enabling the enforcement of terminal routing selection policies and checking compliance during slice replacement or DNN replacement, using a method that includes transmitting policy control request messages, receiving capability information, and converting S-NSSAI to HPLMN S-NSSAI.
This solution enhances scalability by allowing the 5G Core network to efficiently manage various services by separating mobility and session management functions, ensuring compliance with URSP rules and improving signaling load handling and functional complexity in the control plane.
Smart Images

Figure KR2024006321_21112024_PF_FP_ABST
Abstract
Description
Method and device for reporting PDU session information
[0001] The present invention relates to a wireless communication system, and more specifically, to a method for confirming compliance with a terminal routing selection policy (URSP) of a terminal in a cellular wireless communication system (5G System).
[0002] To meet the growing demand for wireless data traffic following the commercialization of 4G communication systems, efforts are being made to develop improved 5G or pre-5G communication systems. For this reason, 5G or pre-5G communication systems are also referred to as "Beyond 4G Network" or "Post-LTE" systems.
[0003] To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., the 60 GHz band). To mitigate radio path loss and increase the transmission range of radio waves in ultra-high frequency bands, beamforming, massive MIMO (massive MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antenna technologies are being discussed in 5G communication systems.
[0004] In addition, to improve the network of the system, technologies such as evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, moving networks, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation are being developed in 5G communication systems.
[0005] In addition, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access) are being developed in 5G systems.
[0006] Meanwhile, 3GPP, which is in charge of cellular mobile communication standards, is naming a new core network structure 5G Core (5GC) and proceeding with standardization to promote evolution from the existing 4G LTE system to a 5G system.
[0007] 5GC supports the following differentiated features compared to the Evolved Packet Core (EPC), the network core for existing 4G.
[0008] First, 5GC introduces the Network Slice feature. As a requirement of 5G, 5GC must support a variety of terminal types and services, such as enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine Type Communications (mMTC). These terminals and services each have different requirements for the core network. For example, eMBB services require high data rates, while URLLC services require high reliability and low latency. Network Slice is a proposed technology to meet these diverse service requirements.
[0009] Network slicing virtualizes a single physical network to create multiple logical networks. Each Network Slice Instance (NSI) can have distinct characteristics. Therefore, each NSI can have a network function (NF) tailored to its specific characteristics, enabling it to meet diverse service requirements. By assigning an NSI tailored to the service requirements of each terminal, various 5G services can be efficiently supported.
[0010] Second, 5GC can easily support the network virtualization paradigm by separating mobility management and session management functions. In existing 4G LTE, all terminals could receive network services through signaling exchanges with a single core device called the Mobility Management Entity (MME), which was responsible for registration, authentication, mobility management, and session management. However, in 5G, the number of terminals will explode, and the mobility and traffic / session characteristics that must be supported will become more specialized depending on the terminal type. Therefore, supporting all functions with a single device like the MME will inevitably reduce scalability by adding entities for each required function. Therefore, various functions are being developed based on a structure that separates mobility management and session management functions to improve scalability in terms of functional / implementation complexity and signaling load of the core device responsible for the control plane.
[0011] The present invention aims to provide a method for transmitting a report on a URSP enforcement rule of a terminal from a V-PCF of a VPLMN to an H-PCF of an HPLMN in an LBO roaming environment.
[0012] The present invention also seeks to enable the PCF to check whether URSP is complied with when a slice replacement or a DNN replacement occurs in a serving network.
[0013] According to one embodiment of the present invention, a method performed by a visited-policy control function (V-PCF) of a visited public land mobile network (VPLMN) in a local breakout (LBO) roaming situation may include the steps of: transmitting a terminal policy control request message to an H-PCF of a home PLMN (HPLMN); receiving, from the H-PCF, a policy control request trigger (PCRT) for capability information of a terminal related to a URSP (UE route selection policy); transmitting, to an SM-PCF managing a PDU (packet data unit) session, a subscription request for URSP-related terminal capability information; receiving, from the SM-PCF, URSP-related terminal capability information; and transmitting, to the H-PCF, the URSP-related terminal capability information.
[0014] The method performed by the above V-PCF may further include a step of transmitting a subscription request message for an SM policy connection between an SMF and an SM-PCF to a BSF (binding support function).
[0015] The above URSP-related terminal capability information may include a DNN (data network name) requested by the terminal and a DNN selected by a session management function (SMF).
[0016] The above URSP-related terminal capability information may include S-NSSAI and alternative S-NSSAI requested by the terminal.
[0017] The method performed by the above V-PCF may further include a step of changing the S-NSSAI (single-network slice selection assistance information) to HPLMN S-NSSAI when the URSP-related terminal capability information received from the SM-PCF includes the S-NSSAI.
[0018] According to another embodiment of the present invention, a method performed by a home-policy control function (H-PCF) of a home public land mobile network (HPLMN) in a local breakout (LBO) roaming situation may include the steps of: receiving a terminal policy control request message from a V-PCF of a visited PLMN (VPLMN); transmitting a policy control request trigger (PCRT) for capability information of a terminal related to a URSP (UE route selection policy) to the V-PCF; and receiving, from the V-PCF, terminal capability information related to the URSP.
[0019] According to another embodiment of the present invention, a visited-policy control function (V-PCF) of a visited public land mobile network (VPLMN) operating in a local breakout (LBO) roaming situation includes a transceiver; and a control unit, wherein the control unit may be configured to transmit a terminal policy control request message to an H-PCF of an HPLMN (Home PLMN), receive a PCRT (policy control request trigger) for capability information of a terminal related to URSP (UE route selection policy) from the H-PCF, transmit a subscription request for URSP-related terminal capability information to an SM-PCF managing a PDU (packet data unit) session, receive URSP-related terminal capability information from the SM-PCF, and transmit the URSP-related terminal capability information to the H-PCF.
[0020] According to the disclosure of the present invention, even when DNN replacement is performed, V-PCF can determine whether a terminal is executing URSP by checking PDU session information reported by SM-PCF.
[0021] According to the disclosure of the present invention, even if S-NSSAI replacement is performed, V-PCF can determine whether the terminal is executing URSP by checking PDU session information reported by SM-PCF.
[0022] According to the disclosure of the present invention, H-PCF (V-PCF) can determine whether a matched PDU session in an application of a terminal is a new match or matches an existing session.
[0023] Figure 1 is a diagram showing the 5G system network structure in a service-based format.
[0024] Figure 2 is a diagram illustrating the concept of a UE Route Selection Policy (hereinafter referred to as URSP).
[0025] Figures 3a and 3b are flowcharts of a method by which a V-PCF reports to an H-PCF about a terminal's URSP enforcement rules.
[0026] Figure 4 is a drawing showing the structure of a terminal according to one embodiment of the present invention.
[0027] FIG. 5 is a diagram illustrating the structure of a network entity according to one embodiment of the present invention.
[0028] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. In addition, when describing the present invention, if a detailed description of a related known function or configuration is judged to unnecessarily obscure the gist of the present invention, such detailed description will be omitted. In addition, the terms described below are terms defined in consideration of their functions in the present invention, and these may vary depending on the intention or custom of the user or operator. Therefore, their definitions should be made based on the contents throughout this specification. For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically illustrated. Furthermore, the size of each component does not entirely reflect the actual size. Identical or corresponding components in each drawing are assigned the same reference numerals. The advantages and features of the technical ideas according to the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described in detail below with reference to the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms, and these embodiments are provided only to make the present disclosure complete and to fully inform those skilled in the art of the scope of the invention, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification. In addition, when describing the present disclosure, if it is determined that a specific description of a related function or configuration may unnecessarily obscure the gist of the technical idea according to the present disclosure, the detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of the functions in the present disclosure, and this may vary depending on the intention or custom of the user or operator. Therefore, the definitions should be made based on the contents throughout the present specification.
[0029] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of an eNode B, a Node B, a BS (Base Station), a RAN (Radio Access Network), an AN (Access Network), a RAN node, a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present invention, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, although the embodiments of the present disclosure are described below using an LTE or LTE-A system as an example, the embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel type. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included in a system to which the embodiments of the present disclosure can be applied, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the embodiments of the present disclosure may be applied to other communication systems with some modifications within a scope that does not significantly deviate from the scope of the present invention, as judged by a person having skilled technical knowledge. In this case, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams can be performed by computer program instructions.
[0030] These computer program instructions may be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, so that the instructions executed by the processor of the computer or other programmable data processing apparatus create means for performing the functions described in the flowchart block(s). These computer program instructions may also be stored in a computer-available or computer-readable memory that can be directed to a computer or other programmable data processing apparatus to implement functions in a particular manner, so that the instructions stored in the computer-available or computer-readable memory can produce an article of manufacture that includes instruction means for performing the functions described in the flowchart block(s). The computer program instructions may also be installed on a computer or other programmable data processing apparatus, so that a series of operational steps are performed on the computer or other programmable data processing apparatus to create a computer-implemented process, so that the instructions executing on the computer or other programmable data processing apparatus can provide steps for performing the functions described in the flowchart block(s).
[0031] Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions mentioned in the blocks may occur out of order. For example, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order depending on the corresponding function. In this case, the term '~unit' used in the embodiments of the present disclosure means software or a hardware component such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC), and the '~unit' may perform certain roles. However, the '~unit' is not limited to software or hardware. The '~unit' may be configured to be on an addressable storage medium and may be configured to execute one or more processors. Thus, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, the components and '~ units' may be implemented to reproduce one or more CPUs within a device or a secure multimedia card. Also, in an embodiment, the '~ unit' may include one or more processors.
[0032] FIG. 1 is a diagram illustrating the network structure and interface of a 5G system according to one embodiment of the present disclosure. Network entities included in the network structure of the 5G system of FIG. 1 may include network functions (NFs) depending on the system implementation.
[0033] Referring to FIG. 1, the network structure of a 5G system may include various network entities. For example, a 5G system may include an authentication server function (AUSF), an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), an application function (AF), a unified data management (UDM), a data network (DN), a network exposure function (NEF), a network slicing selection function (NSSF), an edge application service domain repository (EDR), an edge application server (EAS, not shown), an EAS discovery function (EASDF, not shown), a user plane function (UPF), a (radio) access network (R)AN, and a terminal, i.e., a user equipment (UE) (101).
[0034] Each NF in the 5G system supports the following functions:
[0035] AUSF processes and stores data for UE authentication.
[0036] AMF provides functions for access and mobility management at the UE level, and one UE can be connected to one AMF by default. Specifically, the AMF provides CN inter-node signaling for mobility between 3GPP access networks, termination of the radio access network (RAN) CP interface (i.e., N2 interface), termination of non-access stratum (NAS) signaling (N1), NAS signaling security (NAS ciphering and integrity protection), AS security control, registration management (registration area management), connection management, idle mode UE reachability (including control and performance of paging retransmission), mobility management control (subscription and policy), intra-system mobility and inter-system mobility support, support for network slicing, SMF selection, lawful intercept (for AMF events and interfaces to the LI system), provision for forwarding of session management (SM) messages between the UE and the SMF, a transparent proxy for SM message routing, access authentication, access authorization including roaming authorization checks, and UE and SMSF. It supports functions such as providing delivery of SMS messages between AMF, security anchor function (SAF), and / or security context management (SCM). Some or all of the functions of AMF can be supported within a single instance of AMF.
[0037] DN stands for operator service, Internet access, or third-party service, for example. DN transmits downlink protocol data units (PDUs) to UPF or receives PDUs transmitted from UEs from UPF.
[0038] PCF receives information about packet flows from application servers and provides the ability to determine policies for mobility management, session management, and other aspects. Specifically, PCF supports a unified policy framework for controlling network behavior, provides policy rules so that control plane functions (e.g., AMF, SMF, etc.) can enforce them, and implements a front end for accessing relevant subscription information for policy decision-making within the user data repository (UDR).
[0039] The SMF provides session management functions, and when a UE has multiple sessions, each session can be managed by a different SMF. Specifically, the SMF supports functions such as session management (e.g., session establishment, modification, and termination, including tunnel maintenance between the UPF and (R)AN nodes), UE IP address allocation and management (optionally including authentication), selection and control of UP functions, traffic steering setup to route traffic to appropriate destinations in the UPF (104), termination of interfaces to policy control functions, enforcement of policy and quality of service (QoS) control portions, lawful intercept (for SM events and interfaces to the LI system), termination of the SM portion of NAS messages, downlink data notification, initiator of AN-specific SM information (forwarded to the (R)AN via N2 via the AMF), determination of the SSC mode of the session, and roaming functions. Some or all of the features of an SMF may be supported within a single instance of an SMF.
[0040] The UDM stores user subscription data, policy data, etc. The UDM includes two parts: the application front end (FE) (not shown) and the user data repository (UDR) (not shown).
[0041] The FE includes the UDM FE, which is responsible for location management, subscription management, and credential processing, and the PCF, which is responsible for policy control. The UDR stores the data required for the functions provided by the UDM-FE and the policy profiles required by the PCF. The data stored in the UDR includes user subscription data and policy data, including subscription identifiers, security credentials, access and mobility-related subscription data, and session-related subscription data. The UDM-FE accesses the subscription information stored in the UDR and supports functions such as authentication credential processing, user identification handling, access authentication, registration / mobility management, subscription management, and SMS management.
[0042] The UPF forwards the downlink PDU received from the DN to the UE via the (R)AN (102), and forwards the uplink PDU received from the UE to the DN via the (R)AN. Specifically, UPF supports functions such as anchor points for intra / inter RAT mobility, external PDU session points for interconnect to the Data Network, user plane portions of packet routing and forwarding, packet inspection and policy rule enforcement, uplink classifiers to support lawful intercept, traffic usage reporting and routing of traffic flows to the Data Network, branching points to support multi-homed PDU sessions, QoS handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement), uplink traffic validation (service data flows (SDFs) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering. Some or all of the functions of UPF may be supported within a single instance of a UPF.
[0043] AF interacts with the 3GPP core network to provide services (e.g., application influence on traffic routing, access to network capability exposure, and interaction with the policy framework for policy control).
[0044] (R)AN is a general term for new radio access networks that support both evolved E-UTRA, an evolved version of 4G radio access technology, and new radio (NR) technologies (e.g., gNB).
[0045] The gNB provides functions for radio resource management (i.e., radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to the UE in uplink / downlink (i.e., scheduling), IP (internet protocol) header compression, encryption and integrity protection of user data streams, selection of an AMF upon attachment of the UE if routing to the AMF is not determined from the information provided to the UE, routing of user plane data to UPF(s), routing of control plane information to the AMF, connection setup and teardown, scheduling and transmission of paging messages (originating from the AMF), scheduling and transmission of system broadcast information (originating from the AMF or operating and maintenance (O&M)), measurement and measurement reporting setup for mobility and scheduling, transport level packet marking in uplink, session management, support for network slicing, and QoS flows. It supports features such as mapping to management and data radio bearers, support for UEs in inactive mode, distribution of NAS messages, NAS node selection, radio access network sharing, dual connectivity, and tight interworking between NR and E-UTRA.
[0046] UE stands for User Equipment. A User Equipment may be referred to by terms such as terminal, mobile equipment (ME), or mobile station (MS). Furthermore, a User Equipment may be a portable device, such as a laptop, mobile phone, personal digital assistant (PDA), smartphone, or multimedia device, or a non-portable device, such as a personal computer (PC) or vehicle-mounted device.
[0047] The NEF provides a means to securely expose services and capabilities provided by 3GPP network functions, such as third-party, internal exposure / re-exposure, application functions, and edge computing. The NEF receives information from other NF(s) (based on the exposed capability(s) of other NF(s)). The NEF may store the received information as structured data using a standardized interface to a data storage network function. The stored information may be re-exposed by the NEF to other NF(s) and AF(s) and used for other purposes, such as analysis.
[0048] The NSSF may select a set of network slice instances serving the UE. Furthermore, the NSSF may determine the allowed network slice selection assistance information (NSSAI) and, if necessary, perform mapping to subscribed single-network slice selection assistance information (S-NSSAI). Furthermore, the NSSF may determine the configured NSSAI and, if necessary, perform mapping to subscribed S-NSSAIs. Furthermore, the NSSF may determine the set of AMFs to be used to serve the UE, or, depending on the configuration, may query the NRF to determine a list of candidate AMFs.
[0049] NRF supports service discovery. It receives NF discovery requests from NF instances and provides information about discovered NF instances to them. It also maintains a list of available NF instances and the services they support.
[0050] Figure 2 is a diagram illustrating the concept of a UE Route Selection Policy (hereinafter referred to as URSP).
[0051] The URSP rule consists of traffic descriptor information that can identify a terminal application or traffic generated by a terminal application, as briefly described in Table 1, and a route selection component that determines which PDU session to associate the terminal application or terminal application traffic with when the identified traffic descriptor is detected.
[0052] URSP RulesPSIPrecedenceTraffic Descriptor (TD)Route Selection Component (RSC)IP, FQDN, APPID, CC, DNNS-NSSAIDNNPDU-TypeSSC ModeAccess-TypePSI = 11IP (10.10.10.*)S-NSSAI#1DNN#1IPv42FQDN (www.svc1.com)S-NSSAI#2DNN#2IPv4 / v6SSC#23GPP3APPID (A-OS, com.go.tv),IP (20.20.*.*)S-NSSAI#3DNN#2IPv4PSI = 24Connection capability (IMS)S-NSSAI#4DNN#3IPv4SSC#13GPP5IP (30.30.*.*),FQDN (www.svc2.com)S-NSSAI#5DNN#2IPv4v6SSC#2 / 3PSI = 36DNN#3S-NSSAI#6DNN#4
[0053] A traffic descriptor contains information about the characteristics of a terminal application or traffic generated by an application, and may contain the following elements:
[0054] ■ Application descriptor: Information that can designate the terminal's application, including OSID and APPID.
[0055] ■ IP Descriptor: Displays the IP address that represents the destination address of the IP packet transmitted by the terminal. It can include IP 3-tuple, i.e., IP destination address, port number, and protocol.
[0056] ■ Non-IP descriptor: This is information that can specify the recipient of Non-IP data.
[0057] ■ Domain Descriptor: Expresses the destination address of the server to which the terminal connects in FQDN format.
[0058] ■ Connection Capability (CC): This corresponds to type information that can specify the characteristics of connected traffic, and can have values such as IMS, MMS, and Internet.
[0059] ■ DNN: Data Network Name
[0060] As described in Table 1, the Route Selection Component (RSC) includes the following elements that can specify the properties of a PDU session so that the application or application traffic detected by the traffic descriptor corresponds to a specific PDU session.
[0061] ■ DNN (Data Network Name): This is the data network name. When a terminal connects to the EPC network, it can be used in the same way as the APN (Access Point Name).
[0062] ■ S-NSSAI: Information that can specify a network slice.
[0063] ■ PDU Session Type: This is an element that can specify the type of PDU-Session, which can be IPv4, IPv6, or IPv4v6, or Ethernet, or Non-IP.
[0064] ■ SSC Mode: This is an element that indicates the continuity of sessions and services and can have values of SSC Mode 1, 2, and 3.
[0065] ■ Access-Type: This element indicates whether the PDU session is connected via 3GPP access or via Non-3GPP access.
[0066] Multiple URSP rules are divided and included in multiple Policy Sections within the UE Policy Container, and multiple URSP rules can be distributed and included in multiple Policy Sections so as not to exceed the maximum allowable transmission size of the NAS layer. A single URSP rule cannot be divided and included in two Policy Sections, and a single complete URSP rule must be included in a single Policy Section.
[0067] USRP rules can have priorities on a rule-by-rule basis.
[0068] The terminal receives a URSP from the NAS layer. The terminal then detects the occurrence of a terminal application or terminal application traffic.
[0069] Here are some ways to detect terminal applications:
[0070] ■ A terminal application can request a specific network through the API provided by the terminal's operating system. The API provided by the terminal's operating system may include direct information corresponding to the traffic descriptor received from the terminal's modem's NAS, or information that can be mapped to the traffic descriptor.
[0071] ■ Detection of terminal applications can be performed indirectly by the terminal operating system. For example, in the Android operating system of a terminal, when a terminal application is installed, the package manager that manages it can detect whether it is installed, and can also detect the status of the application by detecting the user's actions. Depending on the status of the application managed within the operating system, the terminal operating system can indirectly detect the application's network connection by detecting a change in status, such as an event in which the application occupies the user's screen (a transition event to foreground activity).
[0072] ■ The terminal operating system can detect the terminal application or traffic generated by the terminal application even when the terminal application calls an API that transmits packets through the terminal operating system.
[0073] ■ When a terminal application attempts to access a service running on the Internet or edge computing by providing an FQDN, the terminal operating system can detect the FQDN provided by the terminal application.
[0074] When the terminal's operating system detects such an application or traffic generated by an application in the URSP Handler, the URSP Handler checks the URSP rules received from the NAS to determine which URSP rule the detected application corresponds to.
[0075] When the URSP Handler encounters a traffic descriptor that matches a URSP rule, it checks whether a PDU session matching the RSC corresponding to the traffic descriptor is currently created. If a PDU session with an RSC matching the URSP rule already exists, the URSP Handler binds the corresponding terminal application to the corresponding PDU session. Future traffic generated from the bound application will be forwarded using the bound PDU session.
[0076] If the URSP Handler finds that there is no PDU session containing the RSC associated with the traffic descriptor, the URSP Handler may initiate a PDU session creation procedure to create the corresponding PDU session. When creating a PDU session, the terminal may initiate the creation of the PDU session by including the PDU session parameters corresponding to the RSC of the URSP rule.
[0077] In the present disclosure, when a URSP handler detects an application or traffic of an application, and a corresponding URSP rule exists, but a PDU session having a corresponding RSC has not been created, the terminal can initiate creation of a new PDU session and transmit information that can designate the discovered application together with a PDU session parameter corresponding to the RSC included in the URSP rule in a PDU session creation request message.
[0078] In this disclosure, for the sake of consistency of explanation, information that can indicate a discovered application is referred to as URSP Enforcement report information. URSP Enforcement report information may also include traffic descriptor values (e.g., application descriptor, DNN, IP address, FQDN, Connection Capability, etc.). URSP Enforcement report information may also include representative traffic descriptor values and associated path selection elements such as DNN, APN, and S-NSSAI values.
[0079] When a terminal receives Connection Capability information transmitted along with a URSP rule, if the detected application corresponds to Connection Capability, it can perform an action of reporting Connection Capability information in a PDU session creation request or change message.
[0080] Figures 3a and 3b are flowcharts of a method by which a V-PCF reports to an H-PCF about a terminal's URSP enforcement rules.
[0081] Step 1. The terminal may transmit its capability information to the AMF to indicate whether it provides the URSP enforcement reporting function. The capability information of the terminal may be a URSP enforcement reporting support indication (URSI). The URSI may be an indicator indicating the capability (capability) of the terminal to report a URSP enforcement report when an application corresponding to a URSP rule is detected. The terminal transmitting the URSI may include the URSP enforcement reporting information in a PDN connection creation request and transmit it to the PGW-C / SMF of the EPC when an application corresponding to the URSP rule is detected. In addition, the terminal transmitting the USRI may include the URSP enforcement reporting information in a PDU session creation / modification request and transmit it to the SMF of the 5GC when an application corresponding to the URSP rule is detected. The URSP enforcement reporting information may include the Connection Capability information in the Traffic Descriptor of the URSP. The EPC may transmit the S-NSSAI information together with the Connection Capability information.
[0082] Step 2. Upon receiving a registration request message from a terminal, the AMF can request a terminal policy association connection to the V-PCF, which is responsible for terminal policy. The AMF then forwards the terminal's capability information regarding the URSP enforcement report function received from the terminal to the V-PCF.
[0083] Step 3. In case of roaming, the V-PCF forwards a terminal policy control request message (policy control create request message) to the H-PCF of the HPLMN. This terminal policy control request message may include terminal capability information regarding the URSP enforcement report function received from the terminal. The V-PCF may forward RAT-Type information to the H-PCF. The H-PCF may determine whether the RAT-Type is 5GC based on the RAT-Type information received from the V-PCF.
[0084] The H-PCF determines whether the URSP uses URSP rule enforcement. If so, the H-PCF can configure a policy control request trigger (PCRT) for the UE reporting of URSP rule enforcement to the V-PCF, and a PCRT for the UE reporting of CC from the associated URSP rule. The PCRT information can be included in the UE policy control creation response message and passed to the V-PCF.
[0085] Step 4. V-PCF receives PCRT for “UE Reporting of CC from Associated URSP rule” from H-PCF.
[0086] Step 5. V-PCF can forward a Terminal Policy Control Creation Response message to AMF.
[0087] Step 6. The H-PCF may transmit a UE policy control update notification message containing the URSP policy for the UE to the V-PCF. In addition to the URSP policy, the H-PCF may transmit HPLMN S-NSSAI and Alternative HPLMN S-NSSAI information for the UE. The V-PCF may perform a procedure (not shown) to transmit the URSP information received from the H-PCF to the UE through Step 6. The V-PCF may store the HPLMN S-NSSAI and Alternative HPLMN S-NSSAI information received from the H-PCF.
[0088] Step 7. V-PCF can receive PCRT for UE Reporting CC from associated URSP rule from H-PCF through the message described in Step 4. Upon receiving this information, V-PCF can perform the subscription procedure for the reporting service of UE Reporting CC to SM-PCF (PCF for the PDU session) that manages PDU session associated with UE through the process from Step 8 to Step 15.
[0089] Step 8. V-PCF can forward a join request message to BSF to subscribe to the notification service for SM policy association (i.e., creation / termination notification of SM-related policy association between SMF and SM-PCF).
[0090] Step 10. The terminal creates a PDU session with the SMF, and the SMF creates an SM policy association with the SM-PCF. During the PDU session creation process, the SMF may send a session management policy control create request message to the SM-PCF. In Step 10A, the SMF may store USRP-related terminal reporting capability information.
[0091] Step 11. SM-PCF performs a registration request procedure with the BSF. The message for the registration request procedure may include the assigned terminal address / prefix, SUPI, DNN, S-NSSAI, and PCF address.
[0092] Step 12. Mgmt_Notify: If UE-PCF has joined BSF (in the previous step), BSF notifies V-PCF that SM-PCF (PCF for PDU Session) has registered with BSF. Notified information may include terminal address, PCF address, PCF Instance ID, PCF Set ID, and binding level information. If multiple PDU sessions exist for one terminal, BSF may send multiple notifications to PCF.
[0093] Step 13. PolicyAuthorization_Notify: If V-PCF has sent a notification request to AMF when SM-PCF becomes available, SM-PCF can send a notification message to V-PCF notifying that SM policy association has been created. The notification message can include terminal address, PCF address, PCF instance ID, PCF Set ID, and PCF binding information.
[0094] Step 14. Policy_Authorization_Subscribe: V-PCF can subscribe to the “UE reporting CC from associated URSP” event notification service by sending a PolicyAuthorization_Subscribe message to SM-PCF. V-PCF can set the Event ID of the notification message to “UE reporting CC from associated URSP rule” and the Event Filter to a list of CCs. V-PCF can also set a Flag to request immediate reporting. The response message can include a Notification Correlation ID, a list of CC values, and PDU session information.
[0095] Step 15. SMPolicyControl_UpdateNotify (SM-PCF to SMF): SM-PCF installs PCRT to detect “UE Reporting Connection Capabilities from associated URSP rule” if it is not already installed.
[0096] Step 16. The terminal provides a CC reporting function for URSP enforcement during the registration procedure, and if the received URSP rule includes a CC and a corresponding application is detected, or if the terminal detects an application corresponding to a URSP rule that includes a CC, it includes the URSP rule enforcement in a PDU session creation or update message and sends it to the AMF. The AMF can send the PDU session creation or update message to the H-PCF in step 16B.
[0097] Step 17. When the SMF receives the “UE report of URSP rule enforcement) during the PDU session creation or modification process and the PCRT is satisfied, the SMF reports the PDU session related information to the PCF by including it in the SMPolicyControl update message.
[0098] Step 18. PolicyAuthorization_Notify: V-PCF receives notification from SM-PCF regarding “UE reporting Connection Capabilities from associated URSP rule.” The Event ID is “UE Reporting Connection Capabilities from associate URSP rule,” and the Event information may include CC and PDU session information (UE requested PDU session information, authorized PDU session information, and Serving PLMN ID information).
[0099] Step 19. If Non-Roaming or HR, UE-PCF checks the operator policy and determines the policy for URSP rule enforcement reporting.
[0100] Step 20. In a Local Breakout (LBO) roaming scenario, if PCRT is received from H-PCF in Step 4 and event information for UE reporting CC from associated URSP rule is received from SM-PCF in Step 18, V-PCF forwards the received event information to H-PCF. The event information may include CC information and PDU session information received from SM-PCF. If S-NSSAI is included in the received information, V-PCF changes S-NSSAI information to HPLMN S-NSSAI and reports the received PDU session information to H-PCF.
[0101] ■ The PDU session information that V-PCF passes to H-PCF may include the following information (information included in steps 18 and 20):
[0102] - Connection Capabilities: list of CC value
[0103] - UE requested PDU Session Information (requested by the UE)
[0104] - PDU Session ID, Old PDU Session ID (for SSC mode 3)
[0105] - UE requested DNN,
[0106] - UE requested PDU Session Type,
[0107] - S-NSSAI (initially requested by UE),
[0108] - SSC Mode(s) supported by the UE,
[0109] - Request-Type: “Initial Request”, “Handover”, “Emergency”, “Emergency Existing Session”
[0110] - PDU Session Request Type: whether to indicate “Establishment Request” or “Modification Request”
[0111] - Access-Type: “Non-3GPP Access”
[0112] - RAT-Type
[0113] - Accepted PDU Session Information (determined by the SMF)
[0114] - DNN (Selected DNN)
[0115] - Alternative S-NSSAI (replaced by the AMF)
[0116] - PDU Session Type selected by the SMF
[0117] - SSC Mode selected by the SMF
[0118] - PDU Session Type, IP Address or prefix or both
[0119] - Associated Info
[0120] - Service Network ID (PLMN ID or PLMN ID and NID) when LBO roaming (to identify the VPLMN specific URSP rules are applied)
[0121] Figure 4 is a drawing showing the structure of a terminal according to one embodiment of the present invention.
[0122] Referring to FIG. 4, the terminal may include a transceiver (410), a control unit (420), and a storage unit (430). In the present invention, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.
[0123] The transceiver (410) can transmit and receive signals with other network entities. For example, the transceiver (410) can receive system information from a base station and receive synchronization signals or reference signals.
[0124] The control unit (420) can control the overall operation of the terminal according to the embodiment proposed in the present invention. For example, the control unit (420) can control the terminal to transmit information about its capability for the URSP enforcement reporting function to the AMF.
[0125] The storage unit (430) can store at least one of the information transmitted and received through the transmission and reception unit (410) and the information generated through the control unit (420). For example, the storage unit (430) can store information on URSP enforcement.
[0126] FIG. 5 is a diagram illustrating the structure of a network entity according to one embodiment of the present invention.
[0127] The network entity in FIG. 5 may mean one of the NFs, such as AMF, V-PCF, BSF, SM-PCF, SMF, and H-PCF, as described above.
[0128] Referring to FIG. 5, a network entity may be configured to include a transceiver (510), a control unit (520), and a storage unit (530). In the present invention, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.
[0129] The transceiver (510) can transmit and receive signals with other network entities. The transceiver (510) can receive signals from, for example, a terminal or another network entity.
[0130] The control unit (520) can control the overall operation of a network entity according to the embodiment presented in the present invention. Specifically, the control unit (620) can control the signal flow between each block to perform the operations in the flowchart of FIG. 3.
[0131] The storage unit (530) can store at least one of the information transmitted and received through the transmission and reception unit (510) and the information generated through the control unit (520). For example, the storage unit (530) can store various pieces of information included in PDU session information.
[0132] The embodiments of the present invention disclosed in this specification and drawings are merely specific examples intended to facilitate easy explanation of the technical content of the present invention and aid understanding thereof, and are not intended to limit the scope of the present invention. It will be apparent to those skilled in the art that other modifications based on the technical concepts of the present invention are possible in addition to the embodiments disclosed herein.
Claims
1. In a method performed by the V-PCF (visited-policy control function) of the VPLMN (visited public land mobile network) in a LBO (local breakout) roaming situation, Step of transmitting a terminal policy control request message to the H-PCF of the HPLMN (Home PLMN); A step of receiving a PCRT (policy control request trigger) for capability information of a terminal related to URSP (UE route selection policy) from the above H-PCF; A step for transmitting a subscription request for terminal capability information related to URSP to SM-PCF, which manages a PDU (packet data unit) session; A step of receiving URSP related terminal capability information from the above SM-PCF; and A method comprising the step of transmitting terminal capability information related to the URSP to the above H-PCF.
2. In paragraph 1, A method further comprising the step of transmitting a subscription request message for an SM policy connection between an SMF and an SM-PCF with a BSF (binding support function).
3. In paragraph 1, A method in which the above URSP related terminal capability information includes a DNN (data network name) requested by the terminal and a DNN selected by a session management function (SMF).
4. In paragraph 1, A method wherein the above URSP related terminal capability information includes S-NSSAI and alternative S-NSSAI requested by the terminal.
5. In paragraph 1, A method further comprising a step of changing S-NSSAI (single-network slice selection assistance information) to HPLMN S-NSSAI when the URSP-related terminal capability information received from the SM-PCF includes S-NSSAI.
6. In a method performed by the H-PCF (home-policy control function) of the HPLMN (home public land mobile network) in a LBO (local breakout) roaming situation, A step of receiving a terminal policy control request message from a V-PCF of a VPLMN (visited PLMN); A step of transmitting PCRT (policy control request trigger) for capability information of a terminal related to URSP (UE route selection policy) to the above V-PCF; and A method comprising the step of receiving URSP related terminal capability information from the above V-PCF.
7. In paragraph 6, A method in which the above URSP related terminal capability information includes a DNN (data network name) requested by the terminal and a DNN selected by a session management function (SMF).
8. In paragraph 6, A method wherein the above URSP related terminal capability information includes S-NSSAI and alternative S-NSSAI requested by the terminal.
9. In the V-PCF (visited-policy control function) of a VPLMN (visited public land mobile network) operating in a LBO (local breakout) roaming situation, Transmitter and receiver; and Includes a control unit, The above control unit, Send a terminal policy control request message to the H-PCF of HPLMN (Home PLMN), From the above H-PCF, PCRT (policy control request trigger) for terminal capability information related to URSP (UE route selection policy) is received, SM-PCF manages PDU (packet data unit) sessions and transmits subscription requests for URSP-related terminal capability information. Receive URSP related terminal capability information from the above SM-PCF, V-PCF, which is set to transmit terminal capability information related to the URSP to the above H-PCF.
10. In paragraph 9, The above control unit. V-PCF, which is further configured to send subscription request messages for SM policy connections between SMF and SM-PCF, with BSF (binding support function).
11. In paragraph 9, The above URSP related terminal capability information includes a V-PCF including a DNN (data network name) requested by the terminal and a DNN selected by a session management function (SMF).
12. In paragraph 9, The above URSP related terminal capability information includes V-PCF, including S-NSSAI and alternative S-NSSAI requested by the terminal.
13. In paragraph 9, The above control unit, V-PCF, which is further configured to change the S-NSSAI to HPLMN S-NSSAI when the URSP-related terminal capability information received from the SM-PCF includes S-NSSAI (single-network slice selection assistance information).
14. In the H-PCF (home-policy control function) of the HPLMN (home public land mobile network) operating in a LBO (local breakout) roaming situation, Transmitter and receiver; and Includes a control unit, The above control unit, Receive a terminal policy control request message from the V-PCF of the VPLMN (visited PLMN), With the above V-PCF, PCRT (policy control request trigger) for terminal capability information related to URSP (UE route selection policy) is transmitted, H-PCF, which is configured to receive URSP related terminal capability information from the above V-PCF.
15. In paragraph 14, The above USRP related terminal capability information includes H-PCF, which includes DNN (data network name) requested by the terminal, DNN selected by SMF (session management function), S-NSSAI requested by the terminal, and alternative S-NSSAI.
Citation Information
Patent Citations
Obtaining of UE policy
US20200304983A1
Session Establishment with a Local Serving Network
US20220312510A1
Method and apparatus for providing policy of user equipment in wireless communication system
US20220386100A1
