METHOD AND APPARATUS FOR TRANSMITTING DATA WITH QUALITY OF SERVICE IN A WIRELESS COMMUNICATION SYSTEM - Patent application
The method optimizes 5G networks by managing PDU sessions with different QoS settings for multiple groups, addressing redundant transmissions and improving resource utilization in 5G mobile communication systems.
Patent Information
- Application Number
- JP2024527668
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-11-12
- Filing Date
- 2022-11-07
- Publication Date
- 2024-11-21
- Estimated Expiration
- 2042-11-07
AI Technical Summary
5G mobile communication systems face challenges in efficiently supporting multiple groups with different Quality of Service (QoS) requirements, leading to redundant data transmissions and inefficient resource utilization.
A method and apparatus that utilize session management functions to manage PDU sessions, allowing data to be divided and transmitted with different QoS settings based on group information, using UPFs to forward traffic according to specific QoS requirements of individual groups within a 5GS network.
Enables simultaneous support for multiple groups with varying QoS requirements, reducing redundant transmissions and optimizing resource allocation in 5G networks.
Smart Images

Figure 2024543438000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a method and apparatus for transmitting data based on Quality of Service (QoS) in a wireless communication network, and particularly to a method and apparatus for transmitting data simultaneously from one application of a terminal to multiple groups having different Quality of Service (QoS) requirements when group communication is supported in 3GPP (registered trademark, the same applies hereinafter) 5GS (5G System). [Background technology]
[0002] 5G mobile communication technology defines a wide frequency band to enable faster transmission speeds and new services, and can be implemented in frequencies below 6GHz ("Sub 6GHz") such as 3.5 gigahertz (3.5GHz), as well as ultra-high frequency bands ("Above 6GHz") called millimeter wave (mmWave) such as 28GHz and 39GHz. In addition, in the case of 6G mobile communication technology, known as the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, 3THz band at 95GHz) is being considered to achieve transmission speeds 50 times faster than 5G mobile communication technology and ultra-low latency time reduced to one-tenth of that of 5G mobile communication technology.
[0003] In the early stages of 5G mobile communications technology, in order to meet the service support and performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (ULLC), and massive Machine-Type Communications (mMTC), the following technologies have been proposed: Beamforming and Massive MIMO to mitigate path loss in ultra-high frequency bands and increase the propagation distance, various numerology support (multiple subcarrier spacing operation, etc.) and dynamic operation of slot formats to efficiently utilize ultra-high frequency resources, initial connection technology to support multiple beam transmission and wideband, definition and operation of Band-Width Part (BWP), new channel coding methods such as Low Density Parity Check (LDPC) code for large-volume data transmission and Polar Code for reliable transmission of control information, L2 pre-processing, and Network Slicing to provide a dedicated network specialized for specific services. Standardization of the 3D slicing process was also underway.
[0004] Discussions are currently underway to improve and enhance the initial 5G mobile communications technology in consideration of the services that 5G mobile communications technology is intended to support. Physical layer standardization is underway for technologies such as Vehicle-to-Everything (V2X), which aims to increase user convenience by helping autonomous vehicles make driving decisions based on the location and status information transmitted by the vehicle itself, New Radio Unlicensed (NR-U), which aims to operate systems in unlicensed bands in accordance with various regulatory requirements, low power consumption technology for NR terminals (UE Power Saving), Non-Terrestrial Network (NTN), which is direct communication between terminals and satellites to ensure coverage in areas where communication with terrestrial networks is not possible, and positioning.
[0005] In addition, standardization is underway in the areas of radio interface architecture / protocol for technologies such as the Industrial Internet of Things (IIoT) to support new services through linkage and integration with other industries, Integrated Access and Backhaul (IAB) to provide nodes for expanding network service areas by integrating wireless backhaul links and access links, mobility enhancement technologies including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) to simplify random access procedures. Standardization is also underway in the areas of system architecture / service for 5G baseline architecture (e.g., Service based Architecture, Service based Interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) in which services are provided based on the location of the terminal.
[0006] When such 5G mobile communication systems are put into practical use, connected devices, which are increasing explosively, will be connected to communication networks, which will require the enhancement of the functions and performance of 5G mobile communication systems and the integrated operation of connected devices.To this end, new research will be conducted on eXtended Reality (XR) to efficiently support Augmented Reality (AR), Virtual Reality (VR), Mixed Reality (MR), etc., 5G performance improvement and complexity reduction using Artificial Intelligence (AI) and Machine Learning (ML), AI service support, Metabus service support, drone communication, etc.
[0007] In addition, the development of the 5G mobile communication system will be the basis for the development of multiple antenna transmission technologies such as new waveforms, full dimensional multiple input / output (FD-MIMO), array antennas, and large scale antennas to ensure coverage in the terahertz band of 6G mobile communication technology, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using orbital angular momentum (OAM), and reconfigurable intelligent surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, AI-based communication technology that utilizes satellites and artificial intelligence (AI) from the design stage to internalize end-to-end AI support functions to optimize the system, and next-generation distributed computing technology that utilizes ultra-high performance communication and computing resources to realize services with a level of complexity that exceeds the limits of terminal computing capabilities.
[0008] The fifth generation system (5GS), a new communication method led by 3GPP, is used in smart energy infrastructure and allows multiple applications to be transmitted through one terminal. In this case, 5GS must support a method of communication using group communication, each with different QoS requirements. Also, one terminal must support multiple groups simultaneously. Each of the multiple groups must meet different QoS requirements. In order for one application in one terminal performing group communication to send data to multiple groups, the same data must be sent multiple times. Also, as the number of groups to which data must be transmitted simultaneously increases, there is a problem that unnecessary redundant transmissions also increase.
[0009] The above information is provided only as background information to aid in the understanding of the present disclosure. No determination or assertion is made as to whether any of the above content is applicable as prior art with respect to the present disclosure. Summary of the Invention [Problem to be solved by the invention]
[0010] Therefore, the present disclosure provides methods and apparatus for efficiently supporting communication with multiple groups having different QoS requirements in 5GS.
[0011] The present disclosure also provides a method and apparatus for preventing redundant transmissions when one terminal supports communication with multiple groups, each of which has different QoS requirements.
[0012] The present disclosure also provides a method and apparatus for performing communication according to the requested QoS when one terminal supports group communication and different terminals in the group request different QoS. [Means for solving the problem]
[0013] According to an embodiment of the present disclosure, a method for controlling a session management function (SMF) device of a wireless communication system to transmit data with different quality of service (QoS) within the same service group may include the steps of receiving a protocol data unit (PDU) session request requested by a first user equipment (UE) from an access and mobility management function (AMF) device, obtaining group information corresponding to the requested PDU Session from a user data repository (UDR) device based on the PDU Session request, the group information including at least two or more group information, determining at least one UPF for transmitting data transmitted from the first UE to at least one other UE based on information corresponding to each of the obtained groups, and requesting traffic forwarding and QoS setting corresponding to a group of the at least one UE in the determined UPF, and transmitting traffic according to different QoS between the first UE and the at least one UE. Effect of the Invention
[0014] According to the present disclosure, it is possible to simultaneously support multiple group communications having different QoS requirements in 5GS. Also, according to the present disclosure, it is possible to efficiently support communications with multiple groups having different QoS requirements in 5GS. In particular, according to the present disclosure, when one terminal supports communications to multiple groups, each of which has different QoS requirements, it is possible to prevent redundant transmission. Also, according to the present disclosure, when one terminal supports group communications, if different terminals in the group request different QoS, communication can be performed according to the QoS requested by each terminal.
[0015] The above and other aspects, features and advantages of particular embodiments of the present invention will become more apparent from the following description taken in conjunction with the accompanying drawings. [Brief description of the drawings]
[0016] [Figure 1] A network configuration diagram for explaining a 5G VN group management method. [Diagram 2] 1 is a diagram illustrating an example of a network and UE configuration to explain a 5G VN group communication method. [Diagram 3] FIG. 1 is an exemplary diagram illustrating multiple group communications supporting different QoS requirements. [Figure 4] A network configuration diagram for explaining a PDU session configuration method for multiple groups supporting different QoS requirements according to the present disclosure. [Diagram 5] 1 is a signal flowchart of a PDU session establishment method using pre-configured subgroups when multiple UPFs are used according to an embodiment of the present disclosure. [Figure 6] 13 is a signal flowchart of a PDU session establishment method using a pre-configured subgroup when using a single UPF according to another embodiment of the present disclosure. [Figure 7]13 is a signal flowchart of a PDU session establishment method using multiple groups when multiple UPFs are used according to yet another embodiment of the present disclosure. [Figure 8] 13 is a signal flowchart of a PDU session establishment method using multiple groups when using a single UPF according to yet another embodiment of the present disclosure. [Figure 9] FIG. 2 is a diagram illustrating a configuration of a UE according to an embodiment of the present disclosure. [Figure 10] FIG. 2 is a diagram illustrating a configuration of a network function according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0017] Throughout the drawings, like reference numbers are used to denote the same or similar elements, features and structures.
[0018] The following description with reference to the accompanying drawings is provided to aid in a comprehensive understanding of various embodiments of the present invention defined by the claims and their equivalents. Although various specific details are included herein to aid in understanding, they should be considered merely as examples. Therefore, those skilled in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of known functions and configurations may be omitted for clarity and conciseness.
[0019] The terms and words used in the following description and claims are not limited to their bibliographical meanings, but are merely used by the inventor to make the disclosure clear and consistent. Therefore, it will be apparent to those skilled in the art that the following description of various embodiments of the present invention is provided for illustrative purposes only, and not for the purpose of limiting the present invention, as defined by the appended claims and their equivalents.
[0020] The singular forms "a," "an," and "the" should be understood to include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to a "component surface" includes reference to one or more of those surfaces.
[0021] In describing the embodiments, technical content that is well known to those skilled in the art and is not directly related to the present disclosure will be omitted in order to clarify and more clearly convey the gist of the present invention by omitting unnecessary explanations.
[0022] For the same reason, some components are exaggerated, omitted, or illustrated diagrammatically in the accompanying drawings, and the size of each component does not entirely reflect the actual size. The same or corresponding components in each drawing are denoted by the same reference numerals.
[0023] The advantages and features of the present disclosure, and methods for achieving them, will become clear with reference to the embodiments described below in detail with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below, but may be embodied in various different forms, and the present embodiments are provided to complete the disclosure and fully inform those skilled in the art to which the disclosure pertains, and the disclosure is only defined by the scope of the claims. Throughout the specification, the same or similar reference numbers refer to the same or similar elements.
[0024] It will be understood herein that each block of the flowchart drawings and combinations of blocks in the flowchart drawings are embodied by computer program instructions. Such computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing device to produce a machine, and the instructions executed by the processor of the computer or other programmable data processing device produce means for implementing the functions specified in the flowchart blocks. Such computer program instructions can be stored in a computer usable or computer readable memory that can direct the computer or other programmable data processing device to operate in a particular manner, and the instructions stored in the computer usable or computer readable memory produce an article of manufacture that includes instruction means for implementing the functions specified in the flowchart blocks. The computer program instructions can further be loaded into a computer or other programmable data processing device to cause the computer or other programmable device to perform a series of operational steps, generating a computer-implemented process such that the instructions executed by the computer or other programmable device provide steps for implementing the functions specified in the flowchart blocks.
[0025] Moreover, each block in the flowchart may represent a module, segment, or portion of code, which may include one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions shown in the blocks may be performed out of order. For example, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may be executed in reverse order depending on the related functionality.
[0026] A "unit" as used in this document refers to a software element or a hardware element such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC) that performs a predetermined function. However, a "unit" is not necessarily limited to software or hardware. A "unit" may be stored in an addressable storage medium or configured to execute multiple processors. Thus, a "unit" includes, for example, a software element, an object-oriented software element, a class element or a work element, a process, a function, an attribute, a procedure, a subroutine, a segment of program code, a driver, firmware, microcode, a circuit, data, a database, a data structure, a table, an array, and a parameter. The elements and functions provided by a "unit" may be combined into fewer elements or "units" or divided into more elements or "units". Additionally, the elements and "units" may be embodied to emulate one or more CPUs within a device or a security multimedia card.
[0027] Specific terms used in the following description are provided to aid in understanding the present invention, and different types of terms may be used within the scope of the technical concept of the present invention.
[0028] In the following description, terms for identifying an access node, terms for indicating a network entity, terms for indicating a message, terms for indicating an interface between network entities, terms for indicating various identification information, etc. are used for convenience as examples. Therefore, the present disclosure is not limited to the terms used below, and other terms for indicating other subjects having equivalent technical meanings are used.
[0029] In the following description, a node may correspond to an AMF, SMF, UPF, UDM, UDR, PCF, NEF, AF, or other network function. For example, a first node may correspond to a UPF, a second node may correspond to an AMF, a third node may correspond to a UDM or UDR, a fourth node may correspond to a PCF or NEF, a fifth node may correspond to a UPF, and a sixth node may correspond to an AF. Each node, referred to as an ordinal number, is not limited to this example.
[0030] For the convenience of the following description, the present disclosure uses terms and names defined in the 5GS and NR standards, which are the latest standards defined by the 3GPP (The 3rd Generation Partnership Project) among currently existing communication standards. However, the present disclosure is not limited to the terms and names, and can be applied to wireless communication networks conforming to other standards as well. In particular, the present disclosure can be applied to 3GPP 5GS / NR (5th generation mobile communication standard).
[0031] In the Smart Energy Infrastructure, various applications distributed in each region send state / event information to a central server, and the central server sends overall / partial group / individual setting information and adjustment information to various applications distributed in each region.
[0032] FIG. 1 is a network configuration diagram for explaining a 5G VN group management method.
[0033] Referring to FIG. 1, a user equipment (UE) 101, which is an electronic device capable of 5G wireless communication, can be connected to a base station, NG-RAN 111, through a 5G wireless communication method. In FIG. 1, it should be noted that, among the configurations connected by solid lines, the UE 101 and the NG-RAN 111 are connected at least through wireless communication. In addition, in this disclosure, the 5G wireless communication method is used for the sake of convenience of understanding, but the connection can also be made through other wireless communication methods. For example, the connection can be made through a WiFi method or a 4G wireless communication network, or through a 6G wireless communication network that follows the 5G wireless communication network.
[0034] The UE 101 may be an electronic device capable of wireless communication, such as a mobile terminal (MT), a mobile station (MS), etc. The UE 101 may also be a hand held phone (HHP), a smart phone, a tablet computer, or an internet of things device.
[0035] The NG-RAN 111 operating as a base station can communicate with the UE 101 in a wireless communication scheme conforming to the 5G protocol, and can communicate with the UE 101 within a certain base station boundary. The NG-RAN 111 may be embodied as one base station, or as a central unit and one or more remote units. The NG-RAN 111 may be called a base station (BS), a Node B (Node B) which is a base station of a 3G mobile communication scheme, an eNode B (enode-B) which is a base station of a 4G mobile communication scheme, or a gNode B (gnode-B) which is a base station of a 5G mobile communication scheme.
[0036] A network function (NF) device constituting 5GC may be included above the NG-RAN 111. Such an NF device may be embodied as a plurality of NF devices in one server, or one NF device may be embodied in a plurality of servers. Furthermore, when the NF device is embodied in a server, it may be embodied as software, and in this case, a program for driving the NF device may be installed in the memory.
[0037] Also, one NF may be implemented as one instance. When one NF is implemented as one instance, multiple instances performing the same operation may be run within one server.
[0038] Furthermore, one or more NF devices may be implemented in the form of a network slice and may operate to meet the specifications required for a particular service. In the following description, each NF device will be described by itself as an NF with a specific name for convenience of description.
[0039] Next, we will explain each NF device that makes up 5GC.
[0040] The access and mobility management function (AMF) 121 provides functionality for UE-based connection and mobility management, and one UE can basically be connected to one AMF. Specifically, the AMF 112 provides signaling between CN nodes for mobility between 3GPP access networks, termination of the radio access network (RAN) CP interface (i.e., the 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 execution of paging retransmissions), mobility management control (subscription and policy), intra-system and inter-system mobility support, support for network slicing, SMF selection, lawful intercept (for AMF events and interface to the LI system), delivery of session management (SM) messages between the UE and the SMF, transparent proxy for SM message routing, access authentication, and so on. It may support functions such as authentication, access authorization including roaming permission check, provision for delivery of SMS messages between the UE and the SMF, security anchor function (SAF) and / or security context management (SCM). Some or all of the functions of the AMF 131 may be supported within a single instance of one AMF.
[0041] The User Plane Function (UPF) 113 can transmit downlink protocol data units (PDUs) received from a data network (DN) to the UE 101 via the NG-RAN 111, and transmit uplink PDUs received from the UE 101 via the NG-RAN 111 to the DN. Specifically, the UPF 113 supports functions such as an anchor point for intra / inter-RAT mobility, an external PDU Session point for interconnection to a DN, packet routing and forwarding, packet inspection, and user plane portion of policy rule execution, lawful intercept, traffic usage reporting, an uplink classifier for supporting routing of traffic flows to a data network, a branching point for supporting a multi-homed PDU Session, QoS handling for the user plane (e.g., packet filtering, gating, uplink / downlink rate execution, uplink traffic validation (SDF mapping between service data flow (SDF) and QoS flow), transport level in uplink and downlink) packet marking, downlink packet buffering, and downlink data notification trigger function. Some or all of the functions of the UPF 113 may be supported within a single instance of one UPF.
[0042] The session management function (SMF) 114 provides a session management function, and when a UE has multiple sessions, each session can be managed by a different SMF. Specifically, the SMF 114 can support functions such as session management (e.g., session establishment, modification, and cancellation, including maintenance of a tunnel between the UPF 113 and the NG-RAN 111 node), UE IP address allocation and management (optionally including authentication), UP function selection and control, traffic steering configuration for routing traffic to an appropriate destination in the UPF 113, termination of an interface to policy control functions, enforcement of policy and quality of service (QoS) control parts, lawful intercept (for SM events and interfaces to the LI system), termination of the SM part of NAS messages, downlink data notification, initiator of AN-specific SM information (transmitted to the NG-RAN 111 through the N2 via the AMF 112), SSC mode determination of a session, and roaming functions. Some or all of the functionality of SMF 114 may be supported within a single instance of one SMF.
[0043] The policy control function (PCF) 115 may provide a function of receiving information on packet flows from an application server and determining policies for mobility management, session management, etc. Specifically, the PCF 115 may support functions such as unified policy framework support for controlling network operations, provision of policy rules so that control plane functions (e.g., AMF, SMF, etc.) can execute policy rules, and front end implementation for accessing related subscription information for policy decisions in a user data repository (UDR).
[0044] The network exposure function (NEF) 116 can provide a means to securely expose services and capabilities provided by 3GPP network functions, e.g., for 3rd party, internal exposure / re-exposure, application functions, Edge Computing. The NEF 116 can receive information from other NFs (based on the exposed capabilities of the other NFs). The NEF 116 can store the received information as structured data using a standardized interface to a data storage network function. The stored information can be re-exposed by the NEF 116 to other NFs and AFs and used for other purposes, such as analysis.
[0045] Unified data management (UDM) 117 can store user subscription data, policy data, etc. UDM 155 can include two parts: an application front end (FE) (not shown) and a user data repository (UDR).
[0046] The FE may include a UDM FE responsible for location management, subscription management, credential processing, etc., and a PCF responsible for policy control.
[0047] A user data repository (UDR) 118 can store data required for functions provided by the UDM-FE and policy profiles required by the PCF. Data stored in the UDR can include 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 can access the subscription information stored in the UDR to support functions such as authentication credential processing, user identification handling, access authentication, registration / mobility management, subscription management, SMS management, etc.
[0048] The application function (AF) 121 may transmit a group request related to an application to the 5G network and, conversely, receive information usable by the application from the 5G network. For example, the AF 121 may request the 5G network to create / modify / delete a group for a group management application and may receive a result of the creation / modification / deletion request processing from the 5G network.
[0049] The VN Group Data Network 131 is a data network (DN) supporting a 5G Virtual Network (VN) and is connected to the UPF 113 in the same manner as a general DN. The DN may refer to a network connected to the UPF 113 allocated for each service. A form in which a plurality of UEs form one group and each UE that is a member of the group is mapped to one data network name (DNN) that can be broadcast / multicast / unicast among each other within one 5G LAN can be expressed as a 5G VN Data Network or a 5G VN group Data Network. Here, since 5G is the case of a UE connected to 5GC, a general-purpose network including other forms other than 5G can be expressed as a VN Data Network or a VN group Data Network. A form in which two different groups are mapped to different DNNs can be expressed as, for example, a Data Network mapped to VN1 as a VN1 DN and a Data Network mapped to VN2 as a VN2 DN.
[0050] In the above-described configuration, the AF 121 can be a device that exists outside the 5GC. Therefore, the AF 121 can set a group in the UDR 118 through the NEF 116. More specifically, the AF 121 can create / modify / delete a group in the UDR 118, add / delete members for each group, and set attributes for each group.
[0051] FIG. 2 illustrates an example of a network and UE configuration for explaining a 5G VN group communication method.
[0052] In Figure 2, different reference numbers are used than in Figure 1. However, the NFs illustrated in Figure 2 and Figure 1 may perform the same operations. Additionally, a particular NF may perform additional operations depending on its function, as will be described in more detail below.
[0053] 2, the (R)ANs 204, 214, and 224 may be base stations corresponding to the NG-RAN 111 in FIG. 1. Thus, each of the (R)ANs 204, 214, and 224 may have its own communication area or boundary.
[0054] 2 illustrates an example in which a first UE 201, a second UE 202, and a third UE 203 are located within the area of a first (R)AN 204. An example in which a fourth UE 211, a fifth UE 212, and a sixth UE 213 are located within the area of a second (R)AN 214, and an example in which a seventh UE 221, an eighth UE 222, and a ninth UE 223 are located within the area of a third (R)AN 224.
[0055] Also, in FIG. 2, the first (R)AN 204 is connected to the first I-UPF 205, the second (R)AN 214 is connected to the second I-UPF 215, and the third (R)AN 224 is connected to the third I-UPF 215. The first I-UPF 205, the second I-UPF 215, and the third I-UPF 215 are connected to the same SMF 251. I-UPF is an abbreviation of Intermediate-UPF, and is responsible for connecting the PSA (PDU Session Anchor) UPF having the final routing function with the DN and the (R)AN. There may be multiple I-UPFs between the PSA UPF and the (R)AN.
[0056] Meanwhile, the first I-UPF 205 and the second I-UPF 215 are connected to a first PSA-UPF 231 operating as a PDU Session Anchor (PSA) connected to the VN group DN 214 through an N9 interface, and the third I-UPF 215 is connected to a second PSA-UPF 232 connected to the VN group DN 214 through an N9 interface. The first PSA-UPF 231 and the second PSA-UPF 232 may be connected to the VN group DN 214 through an N19 interface, and the first PSA-UPF 231 and the second PSA-UPF 232 may be connected to the VN group DN 214 through an N6 interface.
[0057] Referring to FIG. 2, the 5G VN group DN241 illustrates a case where the first UE 201, which has established a PDU session using a data network name (DNN) for each group, transmits / receives data to other UEs in the group, for example, the fourth UE 211 located in the second (R)AN 214 and the seventh UE 221 located in the third (R)AN 224. For convenience of explanation, the following will describe a case where the first UE 201 transmits data to other UEs 202, 203, 211, 212, 213, 221, 222, and 223. In addition, since data can be received in the reverse direction of the data transmission path described below, reception can be performed through a reverse process described below. Furthermore, when other UEs in the group other than the first UE 201 transmit or receive data, it can be understood by replacing the first UE 201 with other UEs, so to avoid redundant explanation, only a case where the first UE 201 transmits data to other UEs will be described.
[0058] As in the above assumption, data for the first UE 201 to transmit to other UEs in the group can be transmitted to the first PSA-UPF 231 through the first (R)AN 204 and the first I-UPF 205. Therefore, when the data received from the first UE 201 must be provided to the second I-UPF 215, which is another UPF in the first PSA-UPF 231 (e.g., data to the fourth UE 211), the first PSA-UPF 231 can forward the data to the fourth UE 211 through the second I-UPF 215 and the second (R)AN 214. Also, when the first PSA-UPF 231 must provide the same data received from the first UE 201 to the seventh UE 221, the first PSA-UPF 231 can forward the data to the second PSA-UPF 232 using the N19 interface. Then, the second PSA-UPF 232 can forward the data to the third I-UPF 225 connected to itself through the N9 interface. As a result, the third I-UPF 225 can forward the signal to the seventh UE 221 via the third (R)AN 224.
[0059] FIG. 3 is an exemplary diagram illustrating multiple group communications supporting different QoS requirements.
[0060] In FIG. 3, the contents of FIG. 2 may be simplified and illustrated, and different reference symbols are used for convenience of explanation, but it will be obvious to those skilled in the art that the same configuration as described in FIG. 1 and FIG. 2 can perform the same operation.
[0061] 3, a case is illustrated in which a first UE 301, a second UE 302, and a third UE 303 are located within an area of a first (R)AN 304, and a case is illustrated in which a fourth UE 311, a fifth UE 312, and a sixth UE 313 are located within an area of a second (R)AN 314. In addition, a case is illustrated in which the first (R)AN 304 is connected to a first UPF 305, and the second (R)AN 314 is connected to a second UPF 315. The first UPF 305 and the second UPF 315 may be connected to each other via an N9 interface and / or an N19 interface.
[0062] 3, it can be assumed that the first UE 301, the second UE 302, the third UE 303, the fourth UE 311, the fifth UE 312, and the sixth UE 313 all require the same single QoS (Single QoS). For example, the following description will be given assuming that the single QoS has a latency requirement of 10 ms or less.
[0063] When the first UE 301, the second UE 302, the third UE 303, the fourth UE 311, the fifth UE 312, and the sixth UE 313 all require the same QoS, one DNN may be used for each PDU session assigned to each UE, and one DNN may be mapped to one group. In this case, data transmitted by the first UE 301 is provided to the first UPF 305 via the first (R)AN 304. At this time, when the data transmitted by the first UE 301 needs to be received by all other UEs in the same group, the transmission can be performed as follows.
[0064] When the data received from the first UE 301 is to be transmitted to the second UE 302 and the third UE 303, the first UPF 305 may transmit the data again through the first (R)AN 304. Meanwhile, when the data received from the first UE 301 must be provided to the fourth UE 311, the fifth UE 312, and the sixth UE 313, the first UPF 305 must first find the second UPR 315, which is another UPF where each UE is located. Then, the first UPF 305 may forward the data received from the first UE 301 to the second UPF 315. Then, the second UPF 315 may forward the data received from the first UE 301 to the fourth UE 311, the fifth UE 312, and the sixth UE 313 through the second (R)AN 314.
[0065] At this time, the second UE 302 and the third UE 303 are present within the area of the first UPF 305 which is at least the same UPF as the first UE 301. Note that, in FIG. 3, a case where they are located within the same (R)AN 304 is illustrated.
[0066] On the other hand, the fourth UE 311, the fifth UE 312, and the sixth UE 313 are located in at least a different UPF region from the first UE 301. Therefore, if the latency requirement is the same and is 10 ms or less, it may be difficult for the fourth UE 311, the fifth UE 312, and the sixth UE 313 to adjust the latency requirement. In addition, even if the latency requirement is 10 ms depending on the data traffic, it may be possible to delay within a certain range. However, currently, the same QoS is required for all UEs grouped in one group.
[0067] Therefore, the present disclosure provides a solution to this problem. For example, a method is proposed that allows different QoS to be applied within one group, so that the UE 301 can be provided with a required QoS when it is located at least in the same UPF area as the first UE 301 or in the same (R)AN, and the UE 301 can be provided with a slightly lower QoS than the UPF to which the first UE 301 is connected and the UEs connected to other UPFs.
[0068] When the UE is present within at least the same UPF area as the first UE 301, the distance (physical or logical distance) between the UE and the first UE 301 may not be large. In this way, among the UEs present in the same group, the UE close to the UE transmitting data can be provided with high QoS or the required QoS. According to the above example, when the required latency requirement is within 10 ms, the data can be provided within 10 ms.
[0069] On the other hand, when the UE is located in a different UPF region from the first UE 301 that transmits data, the UE may be far away from the first UE 301 in distance (physical or logical distance). In this way, among UEs in the same group, a QoS lower than the required QoS can be provided to a UE far away from the UE that transmits data. According to the above example, if the required latency requirement is within 10 ms, data can be provided within 20 ms, which is lower than the required latency requirement.
[0070] FIG. 4 is a network configuration diagram for explaining a PDU session setting method for multiple groups supporting different QoS requirements according to the present disclosure.
[0071] Each component in FIG. 4 can perform the same operation if it has the same name as each component described in FIG. 1 to FIG. 3. For example, AMF 112 in FIG. 1 can perform the same operation as AMF 451 in FIG. 4. Therefore, it should be noted that FIG. 4 further describes additional operations in addition to the contents described in FIG. 1 to FIG. 3.
[0072] In FIG. 4, three different UEs 401, 402, and 403 are illustrated. The first UE 401 is indicated by G1 and G2 in the drawing to indicate that it is a UE to which the first group service and the second group service are provided. Furthermore, the second UE 402 is indicated by G1 in the drawing to indicate that it is a UE to which the first group service is provided, and the third UE 403 is indicated by G2 to indicate that it is a UE to which the second group service is provided. Here, the first group and the second group may be lower groups belonging to one upper group.
[0073] The first UE 401 and the second UE 402 may be connected to the first PDN 432 that provides the first service through the first RAN 412 and the second UPF 422. Also, the third UE 403 may be connected to the second PDN 431 that provides the second service through the second RAN 411 and the second UPF 421. Among other configurations, a part different from FIG. 1 is the UDM / UDR 453. The UDM / UDR 453 may be a case where the UDM 117 and the UDR 118 mentioned in FIG. 1 are embodied as one, and may be understood as a simplified form for convenience of the drawing. This disclosure is not particularly limited.
[0074] Next, the method according to the present disclosure will be described below. The method for setting one group to provide a specific service can use one of the following methods.
[0075] First, a method can be considered in which multiple subgroups are pre-defined for one upper group, and a DNN indicating the upper group is used when setting up a PDU session.
[0076] Secondly, there is a method of using multiple DNNs corresponding to multiple groups to set up different PDU Sessions for each subgroup.
[0077] First, the first method will be described. A plurality of subgroups are set in advance in a higher-level group, and a DNN representing the higher-level group is used during a PDU session. The procedure is as follows.
[0078] First, the AF456 may set at least one upper group having a plurality of lower groups in the 5GS. Each lower group may be set to have different QoS requirements for each lower group. The AF456 may transmit different QoS requirements or requirement information for each lower group to the NF of the 5GC through the NEF455. For example, the AF456 may transmit different QoS requirements for each lower group to the UDM / UDR453 through the NEF455. Thus, a specific NF of the 5GC may determine a QoS policy to be actually supported by mapping the QoS requirements for each lower group to a policy in the 5GC network by the AF456. Thus, the UDM / UDR453 may provide different QoS requirement information required for each lower group to the PCF454 that manages the policy. The type of QoS requirement requested by the AF456 and the number of QoS policies that the PCF454 has determined to actually support may differ. For example, even if the AF 456 requests five different QoS requirements for five different subgroups, the PCF 454 may map and actually support four types of QoS policies. In this case, the number of QoS policies that the PCF 454 actually supports may be smaller than or equal to the number of QoS requirements that the AF 456 requests for each subgroup.
[0079] A case where the first UE 401 of a plurality of UEs requests a PDU session setup will be described. The first UE 401 may request a PDU session setup to a DNN corresponding to a representative group. The PDU session setup request transmitted by the first UE 401 may be provided to the AMF 451 through the second RAN 412 in which the first UE 401 is located. Thus, the AMF 451 may select an SMF based on the DNN included in the PDU session setup request. Although only one SMF 452 is illustrated in the example of FIG. 4, there may be multiple SMFs in the actual 5GC, and the AMF 451 selects one SMF from the multiple SMFs based on the DNN. However, it should be noted that only one SMF is illustrated in FIG. 4 for the sake of simplicity and ease of understanding. In addition, the AMF 451 may transmit the PDU session setup request transmitted by the first UE 401 to the selected SMF 452. Here, the SMF 452 selected by the AMF 451 is an SMF that can perform the PDU Session setup request sent by the first UE 401, and can be determined based on the DNN.
[0080] When the SMF 452 receives a PDU Session setting request transmitted by the first UE 401 from the AMF 451, it can obtain lower group information from the upper group information from the UDR 453. That is, the SMF 452 can provide the upper group information of the first UE 401 to the UDR 453 and request lower group information, and can receive the lower group information of the first UE 401 from the UDR 453 as a response. The SMF 452 can check member information included in the lower group from the lower group information received from the UDR 453. In addition, the SMF 452 can request QoS Policy information for each lower group for the lower group corresponding to the first UE 401 from the PCF 454 and receive QoS Policy information for each lower group from the PCF 454. As another example, the SMF 452 may receive and store QoS Policy for each lower group from the PCF 454 in advance.
[0081] The SMF 452 can select a UPF based on the lower group information received from the UDR 453, and can request the setting of a forwarding table in the selected UPF. The SMF 452 can also proceed with QoS setting according to the QoS policy of the lower group received from the PCF 454. In the first embodiment, it is assumed that a service is provided to two groups having different QoS policies in one upper group. Therefore, the QoS policy of the lower group provided by the SMF 452 as the second UPF 422 can set a forwarding table so that each group has a different QoS. That is, one upper group is used to provide different QoS to the first group G1 and the second group G2, which are two lower groups having different QoS.
[0082] The second UPF 412 can set a forwarding table in response to a request from the SMF 452. For example, one upper service that allows the first UE 401 to receive data from another UE can be assumed. In this case, the data can be transmitted from the first UE 401, or the first UE 401 can request that the data be transmitted from a specific DNN. It can be assumed that such a service has two different lower groups, i.e., a first group G1 and a second group G2, depending on QoS.
[0083] In this case, a first group G1, which is one of the lower groups included in the upper group, may have a first level of QoS, and a second group G2, which is the remaining lower group included in the upper group, may have a second level of QoS. In this case, it is assumed that the first level of QoS has a higher priority than the second level of QoS. Therefore, the second UPF 422 can set a forwarding table for a member corresponding to the first group G1 (e.g., the second UE 402) to transmit data at the first level of QoS, and can set a forwarding table for a member corresponding to the second group G2 (e.g., the third UE 403) to transmit data at the second level of QoS.
[0084] In this way, when the forwarding table is set, it can be set so that forwarding to a lower group with a higher QoS has a higher priority than forwarding to a group with a lower QoS. This is because the forwarding priority for each group is determined based on the QoS policy level mapped by the PCF 454 at the request of the AF 456. Therefore, even if there are five lower groups, there may be four levels of forwarding with different priorities based on the QoS policy level mapped by the PCF 454. Therefore, it is assumed that the first and second groups illustrated in FIG. 4 are both mapped by the PCF 454 with different QoS policies.
[0085] The first UE 401 may transmit data with the highest QoS among the QoS of the subgroups. For example, if the first group G1 has the highest QoS, the first UE 401 may transmit data with the QoS of the first group G1 to the second PDN 432 through the first RAN 412 and the second UPF 422. Therefore, the second UPF 422 may provide data received from the first PDN 432 to the second UE 402 through the second RAN 412 as a member having the highest priority based on the forwarding table received from the SMF 452, i.e., the second UE 402 belonging to the first group G1.
[0086] Also, the second UPF 422 can identify that there are remaining members after transmitting data to the second UE 402. In the example of FIG. 4, it can be identified that data is not transmitted to the third UE 403 belonging to the second group G2. Therefore, the second UPF 422 can select a lower group having the highest priority among the remaining members. In FIG. 4, since only two groups are assumed, the second group G2 can be selected. However, if a third group having a priority lower than the second group G2 exists, the second UPF 422 can select the second group G2 according to the priority among the second group G2 and the third group.
[0087] In addition, the second UPF 422 may set the destination as the third UE 403 while transmitting data to the first UPF 421 to transmit the data to the third UE 403, which is a member of the second group. This allows the first UPF 421 to transmit the data received from the second UPF 422 to the third UE 403 through the first RAN 411.
[0088] In the above description, it is assumed that one upper group includes two lower groups. However, even if one upper group includes three or more lower groups, the same operation can be performed according to the above-mentioned method. In other words, if there is a destination (e.g., UE) of a lower lower group among the members of the upper group, the above-mentioned operation is repeated for data through the UPF that is set so that data is transmitted to the corresponding destination.
[0089] Next, a method for setting up different PDU Sessions for each subgroup using multiple DNNs corresponding to each subgroup will be described.
[0090] First, the AF456 can set a plurality of groups in the 5GS. Here, the plurality of groups can be understood to correspond to a plurality of lower groups belonging to one upper group described above. However, in this disclosure, for ease of understanding, each will be described in the form of one group. Such a plurality of groups can be set to have different QoS requirements. The AF456 can transmit different QoS requirements or requirement information for each group to the NF of the 5GC through the NEF455. For example, the AF456 can transmit different QoS requirements for each group to the UDM / UDR453 through the NEF455. As a result, a specific NF of the 5GC can determine a QoS policy to be actually supported by mapping the QoS requirements for each group to a policy in the 5GC network by the AF456. Therefore, the UDM / UDR453 can provide different QoS requirement information required for each group to the PCF454 that manages the policy. The type of QoS requirement requested by the AF456 and the number of QoS policies that the PCF454 has determined to actually support may differ. For example, even if the AF 456 requests five different groups and five different QoS requirements for the groups, the PCF 454 maps them and the number of QoS policies that it actually supports can be four. In this case, the number of QoS policies that the PCF 454 actually supports can be less than or equal to the number of QoS requirements that the AF 456 requests for each group.
[0091] A case will be described in which the first UE 401 among a plurality of UEs requests PDU session setup for each group divided into each DNN. The first UE 401 may request PDU session setup for a plurality of DNNs corresponding to a plurality of groups. The PDU session setup request transmitted by the first UE 401 may be provided to the AMF 451 through the second RAN 412 in which the first UE 401 is located. The AMF 451 that receives the PDU session setup request may select an SMF based on a DNN with the highest priority, or may select an SMF that supports all of a plurality of DNNs. The DNN with the highest priority may be preset. As another example, the AMF 451 may read QoS information set for each DNN in the PCF 454 and determine it as a DNN having the highest QoS Policy. As yet another example, the AMF 451 may determine it in the order of DNNs included in the PDU session setup request received from the first UE 401. As described in the previous embodiment, there may be a plurality of SMFs in 5GC. However, in the example of Fig. 4, for the sake of simplicity and ease of understanding, only one SMF is illustrated, and therefore, the second embodiment of Fig. 4 will be described on the assumption that SMF452 is selected.
[0092] When the selected SMF 452 receives the PDU Session setup request transmitted by the first UE 401 from the AMF 451, it can obtain multiple group information from the UDR 453. That is, the SMF 452 can provide the UDR 453 with information on each group for which the first UE 401 has requested a service, and receive information for each group. The SMF 452 can check member information for each group from the information for each group received from the UDR 453. More specifically, the SMF 452 can request QoS Policy information for each group from the PCF 454 corresponding to each DNN group for which the first UE 401 has requested a PDU Session, and receive QoS Policy information for each group from the PCF 454.
[0093] The SMF 452 may select a UPF according to the group information received from the UDR 453, and may request the setting of a forwarding table in the selected UPF. The SMF 452 may also proceed with QoS setting according to the QoS Policy of the group received from the PCF 454. In FIG. 4, two different UPFs are illustrated. The first UPF 421 is a UPF connected to the first PDN 431, and the second UPF 422 is a UPF connected to the second PDN 432. That is, the first PDN 431 may correspond to one DNN, and the second PDN 432 may correspond to another DNN. Each of these DNNs may be a DNN having a different QoS.
[0094] As described above, the first UE 410 can transmit service data for the first group G1 and the second group G2, which are two groups having different QoS for each group. Therefore, the SMF 452 can select the second UPF 422 to provide a service corresponding to the first group G1. Also, the SMF 452 can select the first UPF 421 to provide a service corresponding to the second group G2.
[0095] Each UPF can set a forwarding table according to a request from the SMF 452. For example, a service based on data (or a request) transmitted by the first UE 410 can be assumed to be provided to other UEs. At this time, the SMF 452 can select the second UPF 422 for the first group G1 corresponding to the first DNN, and set the second PDN 432 and the forwarding table for providing the first group G1 service to the selected second UPF 422. As a result, the second UPF 422 can set a route based on the second PDN 432 and the forwarding table to provide the service of the first group G1.
[0096] Also, the SMF 452 may select the first UPF 421 for the second group G2 corresponding to the second DNN, and may set the first PDN 431 and a forwarding table that provide the service of the second group G2 in the selected first UPF 421. As a result, the first UPF 421 may set a route based on the first PDN 431 and the forwarding table to provide the service of the second group G2. Therefore, the forwarding tables provided by the first UPF 421 and the second UPF 422 may be different from each other.
[0097] When setting up a forwarding table, each UPF can set up forwarding to a lower group with high QoS to have a higher priority than forwarding to a lower group with low QoS. This is because the forwarding priority for each group is determined based on the QoS policy level mapped by the PCF 454 at the request of the AF 456. Therefore, even if there are five lower groups, there may be four levels of forwarding with different priorities based on the QoS policy level mapped by the PCF 454.
[0098] The first UE 401 may transmit data with the highest QoS among the QoS of the multiple groups. For example, if the first group has the highest QoS, the first UE 401 may transmit data to the second PDN 432 through the first RAN 412 and the second UPF 422. Thus, the second UPF 422 may provide data received from the first PDN 432 to the second UE 402 through the second RAN 412 for the member having the highest priority based on the forwarding table received from the SMF 452, i.e., the second UE 402 belonging to the first group G1.
[0099] Also, the first UPF 421 can transmit data received from the first PDN 431 to the third UE 403 through the first PDN RAN 411 based on a forwarding table set based on the QoS information received from the SMF 452. At this time, if the QoS level of the first group G1 is higher than the QoS level of the second group G2, the QoS for the first group G1 can be set higher. For example, assuming that the latency requirement of the first group G1 is 10 ms, the latency requirement of the second group can be 20 ms.
[0100] The above description assumes that two groups are included, but the above method can be carried out in the same manner even if three or more groups are included.
[0101] FIG. 5 is a signal flowchart of a PDU session establishment method using pre-configured subgroups when multiple UPFs are used according to an embodiment of the present disclosure.
[0102] Before referring to FIG. 5, each component illustrated in FIG. 5 will be described using each NF described in FIG. 4. However, please note that components not shown in FIG. 4 use different reference numerals. In addition, in FIG. 5, PCF / NEF may not mean that the two components can be embodied as one server. In order to reduce the complexity of the drawing, it is illustrated in one form, and the operation of each function will be described separately.
[0103] In step 0, the AF 456 can set group information in the UDR 468 via the NEF 454. At this time, as described in the first embodiment of FIG. 4, group A can be set to have subgroup1 and subgroup2. For each of subgroup1 and subgroup2, QoS requirements can be requested to be set by QoS1 req and QoS2 req. When this QoS request is stored in the PCF 454, it can be mapped to a network policy and set as QoS1 and QoS2 policies. The type of QoS requirement requested by the AF 456 and the number of QoS policies that the PCF 454 decides to actually support may be different. For example, QoS1 req and QoS2 req may be different, but QoS1 and QoS2 may be the same. In the following description, it is assumed that QoS1 and QoS2 are different from each other.
[0104] In step 1, UE1 (401), which belongs to both subgroup 1 and subgroup 2, can send a PDU Session request to AMF 451 using a DNN corresponding to group A. In step 1a, AMF 451 can select SMF 452 using a DNN corresponding to group A. In step 1b, AMF 451 can transmit the PDU Session request to the selected SMF 452.
[0105] In step 2, the SMF 452 obtains information on subgroup1 and subgroup2 related to group A to which UE1 (401) has joined from the UDR / UDM 458, and in step 2a, the SMF 452 can obtain policies for QoS1 related to subgroup1 and QoS2 related to subgroup2 from the PCF 454.
[0106] In steps 3 and 3a, the SMF 452 can request traffic forwarding and QoS configuration related to subgroup1 and subgroup2 from UPF1 (421) and UPF2 (422), respectively.
[0107] In step 4, traffic forwarding paths related to subgroup1 and subgroup2 can be set in UPF1 (421) and UPF2 (422), respectively. The traffic forwarding path setting can be understood in the same sense as the Forwarding Table setting described in FIG. 4. When setting the Forwarding Table, it can be set so that forwarding for subgroup1 with high QoS has a higher priority than forwarding for subgroup2 with low QoS. Since the forwarding priority for each group is determined according to the QoS Policy level mapped in step 0, if the QoS1 and QoS2 assigned to subgroup1 and subgroup2 are the same, the same priority can be set for forwarding.
[0108] In step 5, the SMF 452 can set the QoS to the higher QoS 1 between the QoS 1 assigned to the subgroup 1 and the QoS 2 assigned to the subgroup 2 while transmitting a PDU Session setup response to the UE 1 (401).
[0109] In step 5a, UE2 (402) belonging only to subgroup1 can transmit a PDU Session setup request to AMF 451 using the DNN for group A while setting up a PDU Session. AMF 451 can select SMF 452 using the DNN corresponding to group A. As the selection of SMF has been described above in FIG. 4, the same description will not be repeated. AMF 451 can transmit a PDU Session request to the selected SMF 452. SMF 452 can obtain subgroup1 information related to group A to which UE2 (402) has joined from UDR / UDM 453 and obtain QoS1 policy related to subgroup1 from PCF 454. SMF 452 can request traffic forwarding and QoS setup related to subgroup1 to UPF1 (421) and UPF2 (422). Each of UPF1 (421) and UPF2 (422) sets the traffic forwarding path related to subgroup1 as QoS1. The SMF 452 can set the QoS to QoS1 assigned to subgroup1 while transmitting a PDU Session setup response to the UE2 (402).
[0110] In step 5b, UE3 (403) belonging only to subgroup2 can transmit a PDU Session setup request to the AMF 451 for the DNN for group A while setting up a PDU Session. The AMF 451 can select the SMF 452 using the DNN corresponding to group A. The AMF 451 can transmit the PDU Session request to the selected SMF 452. The SMF 452 can obtain information on subgroup2 related to group A to which the UE3 (403) has joined from the UDR / UDM 453 and obtain a policy of QoS2 related to subgroup2 from the PCF 454. The SMF 452 can request traffic forwarding and QoS setup related to subgroup2 from the UPF1 (421) and UPF2 (422). Each of the UPF1 (421) and UPF2 (422) can set the traffic forwarding path related to subgroup2 as QoS2. The SMF 452 can set the QoS with QoS2 assigned to subgroup2 while sending a PDU Session setup response to the UE3 (403).
[0111] In step 6, UE1 (401) can transmit data destined for group A to UPF1 (421) with QoS1.
[0112] In step 7, the UPF1 (421) can determine a packet forwarding rule so that data transmitted from the UE1 (401) to group A is first transmitted to subgroup1.
[0113] In step 8, UPF1 (421) can deliver data transmitted from UE1 to group A to UE2 (402) belonging to subgroup1 with QoS1.
[0114] In step 8a, UPF1 (421) can transmit data transmitted from UE1 (401) to group A via UPE2 (422). In this case, transmission between UPF1 (421) and UPF2 (422) can be transmitted with QoS1, which is the higher QoS between subgroup1 and subgroup2.
[0115] In step 8b, the UPF1 (421) can deliver the data transmitted from the UE1 (401) to the group A to the station 441 belonging to the subgroup 1 located in the data network with QoS 1.
[0116] In step 9, the UPF2 (422) can determine a packet forwarding rule to forward data transmitted from the UE1 (401) to group A to subgroup 2, which does not belong to subgroup 1. This determination can be made based on the above-mentioned step 5b.
[0117] In step 10, the UPF2 (422) can deliver the data transmitted from the UE1 (401) to the group A to the UE3 (403) belonging to the subgroup2 with QoS2.
[0118] In step 10a, the UPF2 (422) can deliver data transmitted from the UE1 (401) to the group A to the station 422 belonging to the subgroup 2 located in the data network with QoS 2.
[0119] According to Fig. 5 described above, it is possible to operate in a case where a plurality of subgroups are set in advance for one upper group described in Fig. 4, and a DNN indicating the upper group is used during a PDU session. When the embodiment of Fig. 5 is used in this way, data can be transmitted in response to different QoS to lower groups having different QoS levels within one group.
[0120] FIG. 6 is a signal flowchart of a PDU session establishment method using a pre-configured subgroup when a single UPF is used according to another embodiment of the present disclosure.
[0121] In Fig. 6, the same reference numerals as those in Fig. 5 will be used for the description. Therefore, the contents described for each NF in Fig. 5 can be similarly applied to Fig. 6.
[0122] In step 0, the AF 456 can set group information in the UDR 468 via the NEF 454. At this time, as described in the first embodiment of FIG. 4, it is assumed that the group A is set to have subgroup1 and subgroup2. The QoS requirements can be requested to be set as QoS1 req and QoS2 req for each of the subgroup1 and subgroup2. When this QoS request is stored in the PCF 454, it can be mapped to the network policy and set as the QoS1 and QoS2 policies. Also, as described above, the type of QoS requirement requested by the AF 456 and the number of QoS policies that the PCF 454 decides to actually support may be different. For example, the QoS1 req and the QoS2 req may be different, but the QoS1 and QoS2 may be the same. In the following description, it is assumed that the QoS1 and QoS2 are different from each other.
[0123] In step 1, UE1 (401) belonging to both subgroup1 and subgroup2 can send a PDU Session request to AMF 451 using a DNN corresponding to group A. In step 1a, AMF 451 can select SMF 452 using a DNN corresponding to group A. In step 1b, AMF 451 can transmit the PDU Session request to the selected SMF 452.
[0124] In step 2, the SMF 452 obtains information on subgroup1 and subgroup2 related to group A to which UE1 (401) has joined from the UDR / UDM 458, and in step 2a, the SMF 452 can obtain policies for QoS1 related to subgroup1 and QoS2 related to subgroup2 from the PCF 454.
[0125] In step 3, the SMF 452 can request the UPF1 (421) to configure traffic forwarding and QoS settings related to subgroup1 and subgroup2.
[0126] In step 4, the UPF1 (421) can set a traffic forwarding path related to subgroup1 and subgroup2. As described in FIG. 5, the traffic forwarding path setting can be understood in the same sense as the Forwarding Table setting described in FIG. 4. When setting the Forwarding Table, it can be set so that the Forwarding for subgroup1 with high QoS has a higher priority than the Forwarding for subgroup2 with low QoS. In addition, since the forwarding priority for each group is determined according to the QoS Policy level mapped in step 0, if the QoS1 and QoS2 assigned to subgroup1 and subgroup2 are the same, the Forwarding can be set to the same priority.
[0127] In step 5, the SMF 452 can set the QoS to the higher QoS 1 between the QoS 1 assigned to the subgroup 1 and the QoS 2 assigned to the subgroup 2 while transmitting a PDU Session setup response to the UE 1 (401).
[0128] In step 5a, UE2 (402) belonging only to subgroup1 can transmit a PDU Session setup request to AMF451 using the DNN for group A while setting up a PDU Session. AMF451 can select SMF452 using the DNN corresponding to group A. The selection of SMF has been described above in FIG. 4, so the duplicated description will be omitted. AMF451 can transmit the PDU Session request to the selected SMF452. SMF452 can obtain subgroup1 information related to group A to which UE2 (402) has joined from UDR / UDM453 and obtain QoS1 policy related to subgroup1 from PCF454. SMF452 can request UPF1 (421) to set traffic forwarding and QoS related to subgroup1. SMF452 can set the traffic forwarding path related to subgroup1 as QoS1 in UPF1 (421). In addition, the SMF 452 can set the QoS to QoS1 assigned to subgroup1 while transmitting a PDU session setting response to the UE2 (402).
[0129] In step 5b, the UE3 (403) belonging only to subgroup2 can transmit a PDU Session setup request to the AMF 451 using the DNN for group A while setting up a PDU Session. The AMF 451 can select the SMF 452 using the DNN corresponding to group A. The AMF 451 can transmit the PDU Session request to the selected SMF 452. The SMF 452 can obtain information on the subgroup2 related to the group A to which the UE3 (403) has joined from the UDR / UDM 453, and obtain a policy of QoS2 related to the subgroup2 from the PCF 454. The SMF 452 can request traffic forwarding and QoS setup related to the subgroup2 from the UPF1 (421). The UPF1 (421) can set the traffic forwarding path related to the subgroup2 as QoS2. The SMF 452 can set the QoS with the QoS2 assigned to the subgroup2 while transmitting a PDU Session setup response to the UE3 (403).
[0130] In step 6, UE1 (401) can transmit data destined for group A to UPF1 (421) with QoS1.
[0131] In step 7, the UPF1 (421) can determine a packet forwarding rule by first transmitting data transmitted from the UE1 (401) to group A to subgroup1.
[0132] In step 8, the UPF1 (421) can deliver the data transmitted from the UE1 (401) to the group A to the UE2 (402) belonging to the subgroup1 with QoS1.
[0133] In step 8a, UPF1 (421) can deliver data transmitted from UE1 (401) to group A to station 441 belonging to subgroup 1 located in the data network with QoS1. Here, steps 8 and 8a may be performed in different orders or simultaneously depending on the required QoS. For example, if there is little difference in the latency interval required between QoS2 and QoS1, they may be performed simultaneously or step 8a may be performed first and then step 8 may be performed.
[0134] In step 9, the UPF1 (421) can determine a packet forwarding rule by transmitting data transmitted from the UE1 (401) to group A to subgroup 2, which does not belong to subgroup 1.
[0135] In step 10, the UPF1 (421) can deliver the data transmitted from the UE1 (401) to the group A to the UE3 (403) belonging to the subgroup2 with QoS2.
[0136] In step 10a, the UPF1 (421) can deliver data transmitted from the UE1 (401) to the group A to the station 422 belonging to the subgroup 2 located in the data network with QoS 2.
[0137] According to Figure 6 described above, even if there is only one UPF rather than two UPFs as in Figure 5, it is possible to pre-configure multiple subgroups in one upper group and perform operations using a DNN indicating the upper group during a PDU session.
[0138] FIG. 7 is a signal flowchart of a PDU session establishment method using multiple groups when multiple UPFs are used according to yet another embodiment of the present disclosure.
[0139] The same reference numerals as those in FIG. 5 will be used in the description of FIG. 7. Therefore, the contents of each NF in FIG. 5 can be similarly applied to FIG. 7. The embodiment of FIG. 7 can correspond to the second example in the description of FIG. 4.
[0140] In step 0, the AF 456 can set a plurality of group information in the UDR 468 via the NEF 454. In this case, it is assumed that a first group (Group 1) and a second group (Group 2) are set as the plurality of groups. For each of Group 1 and Group 2, the QoS requirements can be requested to be set by QoS1 req and QoS2 req. When this QoS request is stored in the PCF 454, it can be mapped to a network policy and set as QoS1 and QoS2 policies. Also, as described above, the type of QoS requirements requested by the AF 456 and the number of QoS policies that the PCF 454 decides to actually support may be different. For example, QoS1 req and QoS2 req may be different, but QoS1 and QoS2 may be the same. In the following description, it is assumed that QoS1 and QoS2 are different from each other.
[0141] In step 1, UE1 (401) belonging to both Group 1 and Group 2 can transmit a PDU Session request to AMF 451 using the first DNN corresponding to Group 1 and the second DNN corresponding to Group 2 at the same time. The AMF 451 that receives the PDU Session request using the first DNN and the second DNN at the same time can select the SMF 452 based on the DNN with the highest priority. As another example, the AMF 451 can select an SMF that supports all of the multiple DNNs. The DNN with the highest priority may be preset. In this case, if preset, the DNN can be determined as the DNN with the highest QoS Policy by reading the set QoS information. If the information on the DNN with the highest priority is not preset, the DNN for selecting the SMF can also be determined according to the order of the DNNs included in the PDU Session setting request. FIG. 7 illustrates a case where an SMF is selected based on Group 1. Therefore, the AMF 451 can select an SMF based on Group 1 in step 1a. In a subsequent step 1b, the AMF 451 can transmit the PDU Session request to the selected SMF 452.
[0142] In step 2, the SMF 452 can obtain information on Group 1 and Group 2 that the UE 1 (401) joined based on the DNN sent by the UE 1 (401) in the PDU Session Setup Request from the UDR / UDM 453. In the subsequent step 2b, the SMF 452 can obtain the policies of QoS 1 related to Group 1 and QoS 2 related to Group 2 from the PCF 454.
[0143] In steps 3 and 3a, the SMF 452 can request traffic forwarding and QoS configuration related to Group 1 and Group 2 from UPF1 (421) and UPF2 (422).
[0144] In steps 4 and 4a, UPF1 (421) and UPF2 (422) can set traffic forwarding paths related to Group1 and Group2, respectively. Here again, as described above in FIG. 5 and FIG. 6, the setting of the traffic forwarding path can be understood in the same sense as the setting of the Forwarding Table described in FIG. 4. When setting the Forwarding Table, Group1 Forwarding with high QoS can be set to have a higher priority than Group2 Forwarding with low QoS. In addition, since the forwarding priority for each group is determined according to the QoS Policy level mapped in the above-mentioned step 0, if QoS1 and QoS2 assigned to Group1 and Group2 are the same, Forwarding can be set with the same priority.
[0145] In step 5, the SMF 452 can set the QoS to the higher QoS 1 between the QoS 1 assigned to Group 1 and the QoS 2 assigned to Group 2 while transmitting a PDU Session setup response to the UE 1 (401).
[0146] In step 5a, the UE2 (402) belonging only to group 1 can transmit a PDU Session setup request to the AMF 451 for the first DNN corresponding to group 1 while setting up a PDU Session. The AMF 451 can select the SMF 452 using the first DNN corresponding to group 1. Here, the selection of the SMF has been described above in FIG. 4, so the duplicated description will be omitted. The AMF 451 can transmit the PDU Session request to the selected SMF 452. The SMF 452 can obtain Group 1 information subscribed based on the first DNN included in the PDU Session setup request transmitted by the UE2 (402) from the UDR / UDM 453, and can obtain a QoS1 policy related to Group 1 from the PCF 454. The SMF 452 can request traffic forwarding and QoS setup related to Group 1 from the UPF1 (421) and UPF2 (422). The SMF 452 can set the traffic forwarding path related to Group 1 to QoS 1 in UPF1 (421) and UPF2 (422). The SMF 452 also sets the QoS to QoS 1 assigned to Group 1 while transmitting a PDU Session Setup Response to the UE 2 (402).
[0147] In step 5b, the UE3 (403) belonging only to Group 2 can transmit a PDU Session setup request to the AMF 451 for the secondary DNN corresponding to Group 2 while setting up a PDU Session. The AMF 451 can select the SMF 452 using the secondary DNN corresponding to Group 2. The AMF 452 can transmit the PDU Session request to the selected SMF 452. The SMF 452 can obtain information on Group 2 to which the UE3 (403) has joined based on the secondary DNN included in the PDU Session setup request from the UDR / UDM 453, and can obtain a QoS2 policy related to Group 2 from the PCF 454. The SMF 452 can request traffic forwarding and QoS setup related to Group 2 from the UPF1 (421) and UPF2 (422). The traffic forwarding path related to Group 2 can be set as QoS2 in the UPF1 (421) and UPF2 (422). The SMF 452 can set the QoS to QoS2 assigned to group 2 while transmitting a PDU Session setup response to the UE 3 (403).
[0148] In step 6, UE1 (401) can transmit data destined for Group1 and Group2 to UPF1 (421) with QoS1.
[0149] In step 7, the UPF1 (421) can determine a packet forwarding rule by first transmitting data transmitted from the UE1 (401) to Group1 and Group2 to Group1.
[0150] In step 8, the UPF1 (421) can deliver data transmitted from the UE1 (401) to Group1 and Group2 to the UE2 (402) belonging to Group1 with QoS1.
[0151] In step 8a, UPF1 (421) can deliver data transmitted from UE1 (401) to Group1 and Group2 to UPE2 (422) with QoS1, which is a higher QoS for Group1 and Group2. Here, steps 8 and 8a may be performed in different orders or simultaneously depending on the required QoS. For example, if there is little difference in the latency interval required between QoS2 and QoS1, they may be performed simultaneously, or step 8a may be performed first and then step 8 may be performed.
[0152] In step 8b, the UPF1 (421) can deliver the data transmitted from the UE1 (401) to Group1 and Group2 to the Station 441 belonging to Group1 located in the data network with QoS1.
[0153] In step 9, the UPF2 (422) can determine a packet forwarding rule by transmitting data transmitted from the UE1 (401) to Group1 and Group2 to Group2, which does not belong to Group1.
[0154] In step 10, the UPF2 (421) can deliver data transmitted from the UE1 (401) to Group1 and Group2 to the UE3 (403) belonging to Group2 with QoS2.
[0155] In step 10a, the UPF2 (421) can deliver data transmitted from the UE1 (401) to Group1 and Group2 to a station 442 belonging to Group2 located in the data network with QoS2.
[0156] According to Fig. 7 described above, it is possible to use different DNNs corresponding to different groups. That is, it is possible to perform the operation corresponding to the second embodiment described in Fig. 4. In this way, even if each group is not divided into one upper group and one lower group, and multiple groups are set in advance and a DNN indicating each group is used during a PDU session, it is possible to provide services according to different QoS.
[0157] FIG. 8 is a signal flowchart of a PDU session establishment method using multiple groups when using a single UPF according to yet another embodiment of the present disclosure.
[0158] The same reference numerals as those in FIG. 5 are used in the description of FIG. 8. Therefore, the contents of each NF in FIG. 5 can be similarly applied to FIG. 8. In addition, the embodiment of FIG. 8 can correspond to the case where one UPF in the second example in the description of FIG. 4 is used.
[0159] In step 0, the AF 456 can set group information in the UDR 468 via the NEF 454. In this case, it is assumed that a first group (Group 1) and a second group (Group 2) are set as in FIG. 7. The QoS requirements for Group 1 and Group 2 can be requested to be set by QoS1 req and QoS2 req, respectively. When this QoS request is stored in the PCF 454, it can be mapped to a network policy and set as QoS1 and QoS2 policies. Also, as described above, the type of QoS requirements requested by the AF 456 and the number of QoS policies that the PCF 454 decides to actually support may be different. For example, QoS1 req and QoS2 req may be different, but QoS1 and QoS2 may be the same. In the following description, it is assumed that QoS1 and QoS2 are different from each other.
[0160] In step 1, UE1 (401) belonging to both Group1 and Group2 can transmit a PDU Session request to AMF451 using the first DNN corresponding to Group1 and the second DNN corresponding to Group2 at the same time. The AMF451 that receives the PDU Session request using the first DNN and the second DNN at the same time can select the SMF452 based on the DNN with the highest priority. As another example, the AMF451 can select an SMF that supports all of the multiple DNNs. The DNN with the highest priority may be preset. In this way, if the DNN with the highest priority is preset, the set QoS information can be read and the DNN with the highest QoS Policy can be determined. If the information on the DNN with the highest priority is not preset, the DNN for selecting the SMF can also be determined according to the order of the DNNs included in the PDU Session setting request. FIG. 8 illustrates a case where an SMF is selected based on Group1, as in FIG. 7 described above. Therefore, the AMF451 can select the SMF452 based on Group1 in step 1a. In a subsequent step 1b, the AMF 451 can transmit the PDU Session request to the selected SMF 452.
[0161] In step 2, the SMF 452 can obtain information on Group 1 and Group 2 that the UE 1 (401) has joined based on the DNN that the UE 1 (401) has sent in the PDU Session Setup Request from the UDR / UDM 453. In the subsequent step 2b, the SMF 452 can obtain the policies of QoS 1 related to Group 1 and QoS 2 related to Group 2 from the PCF 454.
[0162] In three steps, the SMF 452 can request traffic forwarding and QoS settings related to Group 1 and Group 2 from UPF1 (421) and UPF2 (422).
[0163] In step 4, the UPF1 (421) can set a traffic forwarding path related to Group1 and Group2. Here again, as described above in FIG. 5 and FIG. 6, the setting of the traffic forwarding path can be understood in the same sense as the setting of the Forwarding Table described in FIG. 4. When setting the Forwarding Table, it can be set so that the Forwarding for Group1 with high QoS has a higher priority than the Forwarding for Group2 with low QoS. In addition, since the forwarding priority for each group is determined according to the QoS Policy level mapped in step 0, if the QoS1 and QoS2 assigned to Group1 and Group2 are the same, the Forwarding can also be set to the same priority.
[0164] In step 5, the SMF 452 can set the QoS to the higher QoS 1 between QoS 1 assigned to Group 11 and QoS 2 assigned to Group 2 while transmitting a PDU Session Setup response to the UE 1 (401).
[0165] In step 5a, UE2 (402) belonging only to Group1 can transmit a PDU Session setup request to the AMF 451 for the first DNN corresponding to Group1 while setting up a PDU Session. The AMF 451 can select an SMF 452 using the first DNN corresponding to Group1. Here, the selection of an SMF has been described above in FIG. 4, so a duplicated description will be omitted. The AMF 451 can transmit the PDU Session request to the selected SMF 452. The SMF 452 can obtain Group1 information to which the UE2 (402) has joined based on the first DNN included in the PDU Session setup request from the UDR / UDM 453, and can obtain a QoS1 policy related to Group1 from the PCF 454. The SMF 452 can request traffic forwarding and QoS setup related to Group1 from the UPF1 (421). The UPF1 (421) can set the traffic forwarding path related to Group1 as QoS1. The SMF 452 can set the QoS to QoS1 assigned to Group1 while transmitting a PDU Session setup response to the UE2 (402).
[0166] In step 5b, the UE3 (403) belonging only to Group2 can transmit a PDU Session setup request to the AMF 451 for the secondary DNN corresponding to Group2 while setting up a PDU Session. The AMF 451 can select the SMF 452 using the secondary DNN corresponding to Group2. The AMF 451 can transmit the PDU Session request to the selected SMF 452. The SMF 452 can obtain information on the Group 2 to which the UE3 (403) has joined based on the secondary DNN included in the PDU Session setup request from the UDR / UDM 453, and can obtain a policy of QoS2 related to Group2 from the PCF 454. The SMF 452 can request traffic forwarding and QoS setup related to Group2 from the UPF1 (421). The UPF1 (421) can set the traffic forwarding path related to Group2 as QoS2. The SMF 452 can set the QoS to QoS2 assigned to Group 2 while transmitting a PDU Session setup response to the UE 3 (403).
[0167] In step 6, UE1 (401) can transmit data destined for group 1 and group 2 to UPF1 (421) with QoS1.
[0168] In step 7, the UPF1 (421) can determine a packet forwarding rule by first transmitting data transmitted from the UE1 (401) to Group1 and Group2 to Group1.
[0169] In step 8, the UPF1 (421) can deliver data transmitted from the UE1 (401) to Group1 and Group2 to the UE2 (402) belonging to Group1 with QoS1.
[0170] In step 8b, the UPF1 (421) can deliver the data transmitted from the UE1 (401) to Group1 and Group2 to the Station 441 belonging to Group1 located in the data network with QoS1.
[0171] In step 9, the UPF2 (422) can determine a packet forwarding rule by transmitting data transmitted from the UE1 (401) to Group1 and Group2 to Group2, which does not belong to Group1.
[0172] In step 10, the UPF2 (421) can deliver data transmitted from the UE1 (401) to Group1 and Group2 to the UE3 (403) belonging to Group2 with QoS2.
[0173] In step 10a, the UPF2 (421) can deliver data transmitted from the UE1 (401) to Group1 and Group2 to the Station 442 belonging to Group2 located in the data network with QoS2.
[0174] According to Fig. 8 described above, different DNNs may be used corresponding to different groups, and one UPF may be used in this case. That is, the operation corresponds to the second embodiment described in Fig. 4, and only one UPF may be used at the same time. In this way, by setting a plurality of groups in advance and using DNNs indicating each group during a PDU session, services can be provided according to different QoS even if only one UPF is used.
[0175] FIG. 9 is a diagram illustrating a configuration of a UE according to one embodiment of the present disclosure.
[0176] As shown in FIG. 9, the UE of the present disclosure may include a communication unit 912, a memory 913, and a control unit 911. The control unit 911, the communication unit 912, and the memory 913 of the UE may operate according to the UE communication method described in FIG. 1 to FIG. 8. However, the components of the UE are not limited to only the components illustrated in FIG. 9. For example, the UE may include more components or fewer components than the components illustrated in FIG. 9. In addition, the control unit 911, the communication unit 912, and the memory 913 may be embodied in the form of a single chip.
[0177] The communication unit 912, which is a generic name for a receiver for wireless communication of the UE and a transmitter for wireless communication of the UE, can transmit and receive signals to and from a base station or a network entity. Signals transmitted and received from a base station may include control information and data. To this end, the communication unit 912 may be composed of an RF transmitter that up-converts and amplifies the frequency of a signal to be transmitted, an RF receiver that low-noise amplifies a received signal and down-converts the frequency, and the like. However, this is merely one embodiment of the communication unit 912, and the components of the communication unit 912 are not limited to an RF transmitter and an RF receiver.
[0178] Also, the communication unit 912 may include a wired / wireless transceiver and may include various configurations for transmitting and receiving signals. Also, the communication unit 912 may receive a signal through a wireless channel and output it to the control unit 911, and transmit the signal output from the control unit 911 through a wireless channel. The communication unit 912 may receive a communication signal and output it to the control unit 911, and transmit the signal output from the control unit 911 to a network entity through a wired / wireless network.
[0179] The memory 913 can store programs and data necessary for the operation of the UE. In addition, the memory 913 can store control information or data included in a signal (or message) acquired by the UE. The memory 913 can be composed of a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, a DVD, or a combination of storage media.
[0180] The control unit 911 may control a series of processes for the operation of the UE according to the embodiment of the present disclosure described above with reference to Figs. 1 to 8. The control unit 911 may include at least one or more processors. For example, the control unit 911 may include a communication processor (CP) for controlling modulation / demodulation and encoding / decoding of signals / messages / data required during communication, and an application processor (AP) for processing (or controlling) data / signals / messages processed by the communication processor in a higher layer such as an application program.
[0181] Additionally, the UE may include input / output devices for interfacing with a user and devices such as a speaker and microphone for processing voice calls over VoNR and / or existing wireless networks. The input devices may include, for example, at least one of a touch screen, a touch pad, a stylus, keys, a voice recognition device, and a gesture recognition device. The output devices may include, for example, at least one of a display, a vibration motor, a speaker, and a lamp.
[0182] FIG. 10 is a diagram illustrating a configuration of a network function according to an embodiment of the present disclosure.
[0183] The network entity shown in Fig. 10 may be at least one of the network functions NF. Referring to Fig. 10, the configuration of the network entity may include a controller 1011, a network interface 1012, and a memory 1013. The network entity according to the present disclosure may be at least one of the NFs described in Figs. 1 to 8 above.
[0184] In addition, the components of the NF are not limited to the configuration exemplified in FIG. 10. For example, the NF may include more components than the above-mentioned components or may include fewer components. Furthermore, the controller 1011, the network interface 1012, and the memory 1013 may be embodied in the form of a single chip, or may be embodied in the form of an instance in a specific server. The NF may be any one of the above-mentioned RAN, AMF, SMF, PCF, UDM / UDR, UPF, and NEF.
[0185] The network interface 1012, which is a common name for a receiver of an NF and a transmitter of an NF, can transmit and receive signals to and from the UE 101 or other NFs. In this case, the transmitted and received signals / messages can include control information and data. If the NF is, for example, a base station, the network interface 1012 can be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is merely one embodiment of the network interface 1012, and the components of the network interface 1012 are not limited to an RF transmitter and an RF receiver. Furthermore, if the NF is an AMF, the network interface 1012 may be a device for providing an interface with another NF.
[0186] The memory 1013 can store programs and data necessary for the operation of the NF. The memory 1013 can also store control information or data contained in a signal acquired by the NF. The memory 1013 can be configured from a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, a DVD, or a combination of storage media.
[0187] The control unit 1011 can control a series of processes so that the NF operates according to the above-mentioned embodiment of the present disclosure. The control unit 1011 can include at least one processor. The method according to the embodiment described in the claims or specification of the present disclosure can be implemented in the form of hardware, software, or a combination of hardware and software.
[0188] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
[0189] In the case of a software implementation, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors in an electronic device. The one or more programs include instructions for causing the electronic device to execute a method according to an embodiment of the present invention as claimed or described in the specification.
[0190] Such programs (software modules, software) can be stored in random access memory, non-volatile memory including flash memory, Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disc storage device, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or in a memory consisting of a combination of some or all of them. Also, each component memory may be included in a plurality of pieces.
[0191] The program may be stored in an attachable storage device accessible through a communication network such as the Internet, an Intranet, a Local Area Network (LAN), a Wide LAN (WLAN), a Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to an apparatus that performs an embodiment of the present invention through an external port. Furthermore, a separate storage device on the communication network may be connected to an apparatus that performs an embodiment of the present invention.
[0192] While the present disclosure has been shown and described with reference to various embodiments, those skilled in the art will recognize that various changes in form and detail can be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims and corresponding claims. [Explanation of symbols]
[0193] 911 Control Unit 912 Communications Department 913 Memory 1011 Control section 1012 Network Interface 1013 Memory
Claims
1. 1. A method performed by a first node in a wireless communication system, comprising: receiving a protocol data unit (PDU) session setup request message from a first terminal through a second node; obtaining group information from a third node, the group information including a plurality of subordinate group lists; obtaining subgroup information from a fourth node, the subgroup information including quality of service (QoS) information for each subgroup; sending a traffic forwarding configuration request message to a fifth node, the traffic forwarding configuration request message including the group information and the subgroup information; and sending a PDU Session setup response message including group information and subgroup information to the first terminal.
2. The method of claim 1 , wherein the PDU Session setup request message indicates the highest QoS among the QoS of each of the subgroups.
3. The plurality of subgroups included in the group information and QoS information for each of the subgroups are predefined by a sixth node; The third node obtains the group information from the sixth node, The method of claim 1 , wherein the fourth node obtains the subgroup information from the sixth node.
4. 1. A method performed by a fifth node in a wireless communication system, comprising: receiving a traffic forwarding configuration request message from a first node, the traffic forwarding configuration request message including group information and subgroup information, where the group information includes a list of a plurality of subgroups, and the subgroup information includes Quality of Service (QoS) information for each subgroup; generating a traffic forwarding rule based on the group information and the subgroup information; receiving traffic from a first terminal, the traffic including an indication of a group to be transmitted, the traffic being received with a first QoS; transmitting the traffic to a second terminal based on the indication, the group information and the subgroup information.
5. The method of claim 4 , wherein if the second terminal belongs to a subgroup having the highest QoS among the plurality of subgroups, traffic transmission to the second terminal is performed with a first QoS.
6. transmitting the traffic to a third terminal based on the instruction, the group information, and the subgroup information; The method of claim 4 , wherein the second terminal and the third terminal belong to different subgroups, and a QoS of the subgroup to which the second terminal belongs is higher than a QoS of the subgroup to which the third terminal belongs.
7. The method of claim 4 , wherein the traffic forwarding rules include priority information for each of the subgroups based on QoS information for each of the subgroups.
8. transmitting the traffic to a third terminal based on the instruction, the group information, and the subgroup information; The method of claim 4, wherein the third terminal is not included in a subgroup that includes the second terminal.
9. As a first node in a wireless communication system, A transceiver unit, and A control unit, The control unit is receiving a protocol data unit (PDU) session setup request message from the first terminal through the second node; obtaining group information including a plurality of subordinate group lists from a third node; obtaining subgroup information from the fourth node, the subgroup information including quality of service (QoS) information for each subgroup; sending a traffic forwarding configuration request message to a fifth node, the traffic forwarding configuration request message including the group information and the subgroup information; The first node is configured to send a PDU Session Setup Response message including group information and subgroup information to the first terminal.
10. The first node of claim 9, wherein the PDU Session setup request message indicates the highest QoS among the QoS of each of the subgroups.
11. the plurality of subgroups and QoS information for each of the subgroups included in the group information are predefined by a sixth node; The third node obtains the group information from the sixth node, The first node of claim 9 , wherein the fourth node obtains the subgroup information from the sixth node.
12. As a fifth node in the wireless communication system, A transceiver unit, and A control unit, The control unit is receiving a traffic forwarding configuration request message from a first node, the traffic forwarding configuration request message including group information and subgroup information, where the group information includes a list of a plurality of subgroups, and the subgroup information includes quality of service (QoS) information for each subgroup; generating traffic forwarding rules based on the group information and the subgroup information; receiving traffic from a first terminal including an indication of a group to be transmitted, the traffic being received with a first QoS; A fifth node configured to transmit the traffic to a second terminal based on the indication, the group information and the subgroup information.
13. 13. The fifth node of claim 12, wherein if the second terminal belongs to a subgroup having the highest QoS among a plurality of the subgroups, the traffic to the second terminal is transmitted based on a first QoS.
14. The control unit is further configured to transmit the traffic to a third terminal based on the instruction, the group information, and the subgroup information; The second terminal and the third terminal belong to different subgroups, and a QoS of the subgroup to which the second terminal belongs is higher than a QoS of the subgroup to which the third terminal belongs; The fifth node of claim 12, wherein the traffic forwarding rules include priority information for each of the subgroups based on QoS information for each of the subgroups.
15. The control unit is further configured to transmit the traffic to a third terminal based on the instruction, the group information, and the subgroup information; The fifth node according to claim 12, wherein the third terminal is not included in a subgroup that includes the second terminal.
Citation Information
Patent Citations
Control of network slice
WO2021119627A1
Method and apparatus for providing plurality of virtual networks for single application in mobile communication network
WO2021141348A1
Cited By
Communication resource management method, device, system, and storage medium
JP2025530225A
Communication resource management method, device, system, and storage medium
JP7903937B2
