Method and apparatus for controlling STP of UPF in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. This method performed by a UPF entity in a wireless communication system comprises the steps of: receiving STP-related information from an SMF entity; generating a BPDU on the basis of the STP-related information; and identifying an Ethernet path on the basis of the BPDU.

Description

Method and device for controlling STP of UPF in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for supporting an Ethernet path setup process by expanding a function for supporting Ethernet communication in a wireless communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz (THz) band (for example, 3 THz band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] The disclosed embodiment is intended to provide a device and method capable of effectively providing a service in a wireless communication system.

[0009] Based on the discussion as described above, the present disclosure may include a method performed by a user plane function (UPF) entity of a wireless communication system, the method including the steps of receiving information related to a spanning tree protocol (STP) from a session management function (SMF) entity, generating a bridge protocol data unit (BPDU) based on the information related to the STP, and identifying an Ethernet path based on the BPDU.

[0010] The disclosed embodiment provides a device and method for preventing an Ethernet path from forming a loop when supporting an Ethernet PDU (protocol data unit) session in a wireless communication system.

[0011] The effects that can be obtained from the present disclosure are not limited to the effects mentioned in the various embodiments, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

[0012] FIG. 1 is a diagram illustrating an example of an Ethernet PDU (protocol data unit) Session, a 5G (5th generation) VN (virtual network) PDU Session, and Loop generation according to various embodiments of the present disclosure.

[0013] FIG. 2 is a diagram illustrating an example of an Ethernet PDU Session, a 5G VN PDU Session, and a Loop resolution according to various embodiments of the present disclosure.

[0014] FIG. 3 is a diagram illustrating an example of a spanning tree protocol (STP) / rapid spanning tree protocol (RSTP) / multiple spanning tree protocol (MSTP) configuration of a 5GS (5G system) according to various embodiments of the present disclosure.

[0015] FIG. 4 is a diagram illustrating an example of PDU Session with STP / RSTP / MSTP Control according to various embodiments of the present disclosure.

[0016] FIG. 5 is a diagram illustrating an example configuration of a network entity in a wireless communication system according to various embodiments of the present disclosure.

[0017] FIG. 6 is a diagram showing an example configuration of a base station in a wireless communication system according to various embodiments of the present disclosure.

[0018] FIG. 7 is a diagram showing an example configuration of a terminal in a wireless communication system according to various embodiments of the present disclosure.

[0019] The operating principles of the present invention will be described in detail below with reference to the attached drawings. In the following description of the present invention, detailed descriptions of known functions or components will be omitted if they are deemed to unnecessarily obscure the gist of the invention. Furthermore, the terms described below are defined based on their functions in the present invention and may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the overall content of this specification.

[0020] For the same reason, some components in the attached drawings are omitted or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0021] The advantages and features of the present disclosure, and methods for achieving them, will become clearer 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 and may be implemented in various different forms. The various embodiments are provided to ensure that the disclosure is complete and to fully convey the scope of the disclosure to those skilled in the art, and the disclosure is defined solely by the scope of the claims. Like reference numerals designate like elements throughout the specification.

[0022] At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flow diagram block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flow diagram block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0023] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0024] The term "~unit" used in various embodiments of the present disclosure refers to a software or hardware component, and the "~unit" performs certain roles. However, the "~unit" is not limited to software or hardware. The "~unit" may be configured to reside on an addressable storage medium and may be configured to regenerate one or more processors. Thus, as an example, the "~unit" includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided within the components and "~units" may be combined into a smaller number of components and "~units" or further separated into additional components and "~units." In addition, the components and "~units" may be implemented to regenerate one or more CPUs within a device or a secure multimedia card. Additionally, in various embodiments of the present disclosure, '~bu' may include one or more processors.

[0025] In various embodiments of the present disclosure, a terminal may be referred to as a user equipment (UE), a terminal, a mobile station (MS), a cellular phone, a smartphone, a computer, or any other electronic device capable of performing a communication function.

[0026] Furthermore, the various embodiments of the present disclosure described below may be applied to other communication systems with similar technical backgrounds or channel configurations. Furthermore, the various embodiments of the present disclosure may be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.

[0027] The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, and terms referring to various identification information are provided for convenience of explanation. Therefore, the present invention is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.

[0028] In specifically describing various embodiments of the present disclosure, the communication system may utilize a wireless communication system, for example, the 3rd Generation Partnership Project (3GPP), a wireless communication standard standardization organization, may utilize NR (New RAN), a wireless access network, and Packet Core (5G System, or 5G Core Network, or NG Core (Next Generation Core)), a core network, in the 5G communication standard. In addition, it may be applied to other communication systems with similar technical backgrounds with slight modifications within a range that does not significantly deviate from the scope of the present disclosure, and this will be possible at the discretion of a person skilled in the art of the present disclosure.

[0029] For convenience of explanation, the present invention may use terms and names defined in the 5GS and NR standards, which are the most recent standards defined by the 3GPP organization among the existing communication standards. However, the present invention is not limited to the above terms and names and can be equally applied to wireless communication networks conforming to other standards. In particular, the present invention can be applied to the 3GPP 5GS / NR (5th generation mobile communication standard).

[0030] The 5G mobile communication network is composed of 5G UE (terminal), 5G RAN (radio access network), base station, gNB (5g nodeB), eNB (evolved nodeB, etc.), and 5G core network. The 5G core network can be composed of network functions such as AMF (access and mobility management function) that provides UE mobility management function, SMF (session management function) that provides session management function, UPF (user plane function) that performs data transfer role, PCF (policy control function) that provides policy control function, UDM (unified data management) that provides data management function such as subscriber data and policy control data, and UDR (unified data repository) that stores data of various network functions such as UDM.

[0031] Hereinafter, methods for a 3GPP network (e.g., 5GS) to support an Ethernet PDU (protocol data unit) Session in embodiments of the present disclosure may be described. In one embodiment, when a single user plane function (UPF) supports multiple PDU Sessions for multiple UEs, an Ethernet path may form a Loop depending on the configuration of an Ethernet Device connected to each UE. In addition, when a 3GPP network (e.g., 5GS) supports an Ethernet PDU Session among the methods for supporting a 5G VN in embodiments of the present disclosure, one or multiple UPFs may support multiple PDU Sessions for multiple UEs, and in this case, an Ethernet path may form a Loop depending on the configuration of an Ethernet Device connected to each UE or the configuration of Ethernet Stations connected to the UPF. To this end, the UPF of the 5GS must be able to participate in the Ethernet path setup process.

[0032] FIG. 1 is a diagram illustrating an example of an Ethernet PDU Session, a 5G VN (virtual network) PDU Session, and Loop creation according to various embodiments of the present disclosure.

[0033] Referring to FIG. 1a, FIG. 1a illustrates an example in which an Ethernet path forms a loop depending on the configuration of an Ethernet device connected to each UE when a 3GPP network (e.g., 5GS) supports multiple PDU Sessions for multiple UEs (e.g., UE1 and UE2) in one UPF among methods for supporting Ethernet PDU Sessions.

[0034] UE1 can be connected to the UPF via an Ethernet PDU Session, and UE2 can also be connected to the UPF via an Ethernet PDU Session. Station1 (e.g., ST1) and Station2 (e.g., ST2) can be connected to a DNN (Data Network Name) connected to the UPF via Ethernet. Device1 (e.g., D1) and Device2 (e.g., D2) can be connected to UE1 via Ethernet. Device3 (e.g., D3) can be connected to UE2 via Ethernet. In addition, UE1 and UE2 can also be connected to each other via Ethernet. When there are two or more Ethernet links, a node (e.g., UE or DNN) or network entity participating in Ethernet transmission can be represented as a Switch. In this case, a loop, which is a path from the UPF to UE2 and UE1 and back to the UPF, can be created. If a loop is formed on the Ethernet path, Ethernet may not work. Of course, it is not limited to the above example.

[0035] Referring to FIG. 1b, FIG. 1b is a diagram showing an example of a method in which a 3GPP network (e.g., 5GS) supports a 5G VN, in which case, when supporting Ethernet PDU Sessions, multiple PDU Sessions for multiple UEs can be supported in one or multiple UPFs (e.g., UPF1 and UPF2), and in this case, an Ethernet path forms a loop depending on the configuration of an Ethernet device connected to each UE or the configuration of Ethernet stations connected to the UPF.

[0036] UE1 can be connected to UPF1 via an Ethernet PDU Session, and UE2 can also be connected to UPF1 via an Ethernet PDU Session. Station1 (e.g., ST1) and Station2 (e.g., ST2) can be connected to a DNN connected to UPF1 via Ethernet. Device1 (e.g., D1) and Device2 (e.g., D2) can be connected to UE1 via Ethernet. Device3 (e.g., D3) can be connected to UE2 via Ethernet. Additionally, UE1 and UE2 can also be connected via Ethernet. When there are two or more Ethernet links, a node (e.g., UE or DNN) or network entity participating in Ethernet transmission can be represented as a Switch. In this case, a loop, which is a path from UPF to UE2 and UE1 and back to UPF, can be created. If a loop is formed on the Ethernet path, Ethernet communication may not work.

[0037] UE3 can be connected to UPF2 via an Ethernet PDU Session, and UE4 can also be connected to UPF2 via an Ethernet PDU Session. Station3 (e.g., ST3) and Station4 (e.g., ST4) can be connected to a DNN connected to UPF2 via Ethernet. Device4 (e.g., D4) and an Ethernet switch can be connected to UE3 via Ethernet. Device5 (e.g., D5) and UE4 can be connected to the Ethernet switch via Ethernet. Device6 (e.g., D6) can be connected to UE4 via Ethernet. Additionally, UE1 and UE2 can also be connected via Ethernet. With two or more Ethernet links, a node (e.g., UE or DNN) or network entity participating in Ethernet forwarding can be represented as a Switch. In this case, a loop can be created, which is a path from UPF to UE3 and UE4 and back to UPF2. If a loop is formed on the Ethernet path, operation will not be possible.

[0038] The Ethernet switch connecting ST1 and ST2, and the Ethernet switch connecting ST3 and ST4, can be connected through another Ethernet switch. Therefore, a loop can be created, which is a path that starts from UPF1, passes through the Ethernet switch connected to UPF1, and the Ethernet switch connected to UPF2, and then returns to UPF1 via UPF2. If a loop is formed in the Ethernet path, Ethernet communication may not function. Of course, this is not limited to the above example.

[0039] Since Ethernet cannot operate if a loop is formed on the Ethernet path, a method is needed to set up the Ethernet path to prevent loop formation. A representative method may be to use the Spanning Tree Protocol (STP).

[0040] STP (Spanning Tree Protocol) can be a method in which switches supporting the protocol exchange BPDUs (Bridge Protocol Data Units) in a broadcast manner to select a root switch. Then, switches supporting the protocol can use the method of exchanging BPDUs in a broadcast manner to find the Designated Port (DP) that reaches the next switch based on the root switch. This method can also be used to add paths that pass through the fewest number of switches without forming a loop.

[0041] Rapid Spanning Tree Protocol (RSTP) may be a solution to the drawback of STP, which can take up to 50 seconds to discover an alternate path in the event of a failure. For example, it can shorten the stabilization time by exchanging Bridge Protocol Data Units (BPDUs) periodically (e.g., every two seconds).

[0042] MSTP (Multiple Spanning Tree Protocol) can be used to reduce the total number of BPDUs when the network has a large number of VLANs, as RSTP operates on a per-VLAN (Virtual Local Area Network) basis. For example, MSTP can group multiple VLANs and apply RSTP to each group, with each group able to set a route by designating a representative port.

[0043] FIG. 2 is a diagram illustrating an example of an Ethernet PDU Session, a 5G VN PDU Session, and a Loop resolution according to various embodiments of the present disclosure.

[0044] Referring to FIG. 2a, FIG. 2a illustrates an example of preventing a loop from forming in an Ethernet path according to an Ethernet device configuration connected to each UE when supporting multiple PDU sessions for multiple UEs (e.g., UE1 and UE2) in one UPF, among the methods for supporting an Ethernet PDU Session in a 3GPP network (e.g., 5GS). In order to prevent a loop from forming in the example of FIG. 2a, 5GS may need to support STP / RSTP / MSTP. Hereinafter, in embodiments of the present disclosure, 5GS may include a case where it supports at least one of STP, RSTP, or MSTP, and does not necessarily mean a case where it must support all of STP, RSTP, and MSTP.

[0045] As an example, FIG. 2A illustrates a case where UPF, UE1, and UE2 of 5GS support STP / RSTP / MSTP to establish a path that prevents loop formation. UPF may be connected via an Ethernet PDU Session with UE2, but STP / RSTP / MSTP may be configured so that UPF does not use the path via the Ethernet PDU Session with UE2. Of course, the present invention is not limited to the example of FIG. 2A.

[0046] Referring to FIG. 2b, FIG. 2b illustrates a method in which a 3GPP network (e.g., 5GS) supports 5G VN, and when supporting Ethernet PDU Sessions, multiple PDU Sessions for multiple UEs can be supported in one or more UPFs (e.g., UPF1 and UPF2). At this time, the formation of a loop in the Ethernet path can be prevented depending on the configuration of the Ethernet Device connected to each UE or the configuration of the Ethernet Stations connected to the UPF. In the example of FIG. 2b, to prevent the formation of a loop, 5GS may need to support STP / RSTP / MSTP.

[0047] As an example, FIG. 2b may illustrate a case where UPF1, UE1, and UE2 of 5GS support STP / RSTP / MSTP to establish a path that prevents loop formation. UPF1 may be connected via an Ethernet PDU Session with UE2, but UPF1 may be configured not to use the path via the Ethernet PDU Session with UE2 via STP / RSTP / MSTP.

[0048] As an example, FIG. 2b illustrates a case where UPF2, UE3, and UE4 of 5GS can support STP / RSTP / MSTP and set up a path that prevents loop formation. UPF2 can be connected to UE4 via an Ethernet PDU Session, but UPF2 can be set up not to use the path through UE4's Ethernet PDU Session via STP / RSTP / MSTP.

[0049] As an example, FIG. 2b illustrates a case where UPF1, UPF2 of 5GS and external Ethernet switches all support STP / RSTP / MSTP, thereby establishing a path that prevents loop formation. While a switch in the DNN directly connected to UPF2 can be directly connected via Ethernet, STP / RSTP / MSTP can be configured so that UPF2 does not use a direct path to the switch in the DNN. Of course, this is not limited to the example of FIG. 2b.

[0050] To prevent loop formation in a 5GS supporting Ethernet communication, the UPF of the 5GS may need to support STP / RSTP / MSTP. However, if the UPF of the 5GS supports STP / RSTP / MSTP, it may need to support periodic BPDU broadcast and perform protocol-dependent path configuration operations. For example, in environments with simple configurations where there is no concern about loop formation, such as when only one PDU session exists, or in cases where loop formation can be completely prevented through the configuration of external switches, stations, and devices, the UPF of the 5GS may not support STP / RSTP / MSTP. Therefore, a method may be needed to configure whether the UPF of the 5GS supports STP / RSTP / MSTP.

[0051] For example, the way UPF of 5GS configures STP / RSTP / MSTP can be as follows. Of course, the following examples are not limited to this.

[0052] 1. DNN / S-NSSAI (Single Network Slice Selection Assistance Information) Configuration

[0053] - STP / RSTP / MSTP Supported / not-supported

[0054] 2. UDM Subscription per UE

[0055] - STP / RSTP / MSTP Subscribed / not-subscribed

[0056] 3. PDU Session Indication per UE per PDU Session (PDU Session indication for each UE per PDU)

[0057] - STP / RSTP / MSTP Requested / not-requested

[0058] 4. 5G VN Configuration per External Group ID

[0059] - STP / RSTP / MSTP Supported / not-supported

[0060] - External Group ID mapped to Internal Group ID (Subscription per Internal Group ID)

[0061] - Internal Group ID to DNN / S-NSSAI (DNN / S-NSSAI Configuration)

[0062] - Internal Group ID can derive a list of UEs (Subscription per UE)

[0063] 5GS operations based on the above-described configuration may require additional actions, primarily in the PDU Session establishment or modification procedures. For example, the following actions may be required, although these are not limited to the examples below.

[0064] 1. PDU Session Setup Request

[0065] - UE Send Establish / Modify Request with STP-requested / not-requested Indication, based on UE configuration (Whether Tethering or not), PDU Session Configuration, DNN / S-NSSAI configuration (5G VN or not)

[0066] 2. SMF checks UDM subscription data (SMF checks UDM subscription data)

[0067] - PDU Session STP / RSTP / MSTP subscribed / not-subscribed

[0068] - RSTP BPDU timeout needs to consider PDB for the PDU Session(RSTP BPDU timeout needs to consider PDB for the PDU Session)

[0069] 3. PCF Policy Check

[0070] - STP / RSTP / MSTP Supported / not-supported

[0071] 4. SMF Local Configuration Check

[0072] - STP / RSTP / MSTP Supported / not-supported

[0073] 5. UPF Parameter Update

[0074] - STP / RSTP / MSTP Enabled / Disabled

[0075] FIG. 3 is a diagram illustrating an example of STP / RSTP / MSTP Configuration of 5GS according to various embodiments of the present disclosure.

[0076] Referring to Fig. 3, a preset may be made to the UDM in step 0a. At this time, the preset may include at least one of Group Data, DNN / S-NSSAI, Internal Group ID, STP / RSTP / MSTP Enabled / Disabled, SUPI, or STP / RSTP / MSTP Subscribed / not-subscribed. For example, at least one of STP / RSTP / MSTP Supported / not-supported per DNN / S-NSSAI, STP / RSTP / MSTP Subscribed / not-subscribed per UE, Mapping of DNN / S-NSSAI and Internal Group ID, or Mapping of UE ID and Internal Group ID may be preset to the UDM.

[0077] In step 0b, PCF can proactively send a Subscribe request to UDR to be notified when a change occurs based on at least one of DNN / S-NSSAI or Internal Group ID.

[0078] In step 1, AF / NEF (Application Function / Network Exposure Function) can send Parameter Create / Update / Delete Request to UDM. At this time, Parameter Create / Update / Delete Request can include at least one of DNN / S-NSSAI, External Group ID, UE, list of UEs, or STP / RSTP / MSTP Enabled / Disabled.

[0079] In step 2, the UDM can request Group Data from the UDR. The UDM can receive at least one of the DNN / S-NSSAI or the Internel Group ID from the UDR through the Group Data request.

[0080] In Step 3, the UDM can update UDR information. The updated information may include at least one of the following: External Group ID, Internal Group ID, STP / RSTP / MSTP supported / not-supported, or STP / RSTP / MSTP subscribed / not-subscribed. The UDM can also update its own data.

[0081] In step 4, UDM can send Parameter Create / Update / Delete Response to AF / NEF. At this time, Parameter Create / Update / Delete Response can include at least one of DNN / S-NSSAI, External Group ID, UE, list of UEs, or STP / RSTP / MSTP Enabled / Disabled.

[0082] In step 5, the UDR can notify the PCF of changed parameters. The changed parameters may include at least one of DNN / S-NSSAI, Internal Group ID, or STP / RSTP / MSTP Enabled / Disabled. Of course, this is not limited to the above examples.

[0083] FIG. 4 is a diagram illustrating an example of PDU Session with STP / RSTP / MSTP Control according to various embodiments of the present disclosure.

[0084] Referring to FIG. 4, in step 1, a UE (e.g., UE1) may send a PDU Session Establishment / Modification Request to an AMF via a RAN. At this time, the PDU Session Establishment / Modification Request may include at least one of DNN / S-NSSAI, SUPI, or STP / RSTP / MSTP Indication. The PDU Type may be set to Ethernet. The UE may utilize DNN / S-NSSAI using Ethernet, and may add an STP-requested / not-requested Indication to the Establishment / Modification Request to indicate whether it wants a loop prevention function. Information included in the PDU Session Establishment / Modification Request may vary based on at least one of UE configuration / selection (selection, determining), PDU Session Configuration, and DNN / S-NSSAI configuration. For example, if the information included in the PDU Session Establishment / Modification Request varies depending on the UE configuration or UE selection, and if the UE is using the Tethering function, the information included in the PDU Session Establishment / Modification Request may include STP / RSTP / MSTP Indication. For example, the PDU Session Configuration may be set so that the Ethernet PDU Session always includes STP / RSTP / MSTP Indication.For example, the DNN / S-NSSAI Configuration can be set to always include MSTP Indication since it can be a large-scale network if it is a DNN / S-NSSAI for a 5G VN.

[0085] In step 2, AMF can perform SMF Selection. At this time, AMF can refer to at least one of PDU Session Type, DNN / S-NSSAI, or STP / RSTP / MSTP Indication.

[0086] In step 3, AMF may send a PDU Session CreateSMContext Request to SMF. At this time, the PDU Session CreateSMContext Request may include at least one of DNN / S-NSSAI, SUPI, or STP / RSTP / MSTP Indication.

[0087] In step 4, the SMF can send a Subscription Retrieval / Subscription for Update request to the UDM. The Subscription Retrieval / Subscription for Update request can include at least one of DNN / S-NSSAI or SUPI.

[0088] In step 5, the UDM can receive detailed data from the UDR by sending a Subscription Data Query to the UDR. The detailed data may include at least one of Group Data and information about the Internal Group to which the UE (e.g., UE1) belongs. Therefore, the UDM can verify information about the Internal Group to which the UE (e.g., UE1) belongs.

[0089] In Step 6, the UDM can receive information from the UDR and may also update it. The information received from the UDR may include at least one of the Internal Group ID, STP / RSTP / MSTP Supported / not-supported, or STP / RSTP / MSTP Subscribed / not-subscribed.

[0090] In step 7, SMF can retrieve subscription information. At this time, the subscription information can include at least one of DNN / S-NSSAI, SUPI, Internal Group ID, STP / RSTP / MSTP Supported / not-supported, or STP / RSTP / MSTP Subscribed / not-subscribed.

[0091] In step 8, the SMF can check the subscription information and determine whether the PDU Session information needs to be additionally updated. At this time, the SMF can compare the STP / RSTP / MSTP Requested / not-requested Indication included in the PDU Session Request with the STP / RSTP / MSTP Subscribed / not-subscribed and DNN / S-NSSAI supported / not-supported information received from the UDM. If the STP / RSTP / MSTP Indication is STP / RSTP / MSTP Requested, the setting for DNN / S-NSSAI is STP / RSTP / MSTP Supported based on the information received from the UDM, and the subscription information for the UE is STP / RSTP / MSTP Subscribed, the corresponding PDU Session can be updated to STP / RSTP / MSTP Enabled. If the PDU Session is a PDU Session of DNN / S-NSSAI of 5G VN, and the setting of DNN / S-NSSAI is STP / RSTP / MSTP Supported, and RSTP can have a BPDU timeout smaller than STP to shorten the stabilization time compared to STP of UE, SMF can check the PDB (Packet Delay Budget) of the Default QoS of PDU Session to support RSTP. If the BPDU timeout value for RSTP support is smaller than twice the PDB, SMF can trigger a QoS setting with a PDB smaller than 0.5 times the BPDU Timeout. For example, if the PDB Timeout is 200ms, SMF can perform a QoS setting with a PDB less than 100ms. If QoS setting is not possible, RTSP support is not possible, so SMF may reject the PDU Session.In the case of MSTP, since RSTP usage is assumed for each VLAN, SMF can compare BPDU Timeout and PDB in the same way as when RSTP is supported, and can attempt QoS change if necessary, or request PDU Session termination if QoS change fails.

[0092] In step 9, the SMF can perform N4 Setup for the UPF. At this time, the N4 Setup can include STP / RSTP / MSTP Enabled / Disabled information. A UPF with one or more Ethernet PDU Sessions set to STP / RSTP / MSTP Enabled can participate in Ethernet-based path configuration as a Bridge with the corresponding Ethernet PDU Sessions and N6 and N19 Interfaces as Ports by periodically generating, transmitting, receiving, and interpreting BPDUs. In addition, the UPF can prevent loop creation by participating in Ethernet-based path configuration. If there is no Ethernet PDU Session set to STP / RSTP / MSTP Enabled among the PDU Sessions connected to the UPF, the UPF may not perform the operation to prevent loop creation by periodically generating, transmitting, receiving, and interpreting BPDUs to participate in Ethernet-based path configuration.

[0093] In step 10, the SMF can select a PCF. At this time, the SMF can refer to at least one of the PDU Session Type, DNN / S-NSSAI, and STP / RSTP / MSTP Indication.

[0094] In step 11, the SMF may send an SM Policy Association Establishment / Modification request to the PCF. At this time, the SM Policy Association Establishment / Modification request may include at least one of DNN / S-NSSAI, SUPI, Internal Group ID, PDU Session ID, or QoS configuration information.

[0095] In step 12, the PCF can send a Subscribe request to the UDR. The Subscribe request can include at least one of the DNN / S-NSSAI or the Internal Group ID.

[0096] In step 13, the UDR can send a Notification to the PCF. The Notification can include at least one of DNN / S-NSSAI, Internal Group ID, or STP / RSTP / MSTP Supported / not-supported.

[0097] In step 14, the PCF can check the Policy and / or information. The PCF can then determine whether additional PDU Session information needs to be updated. At this time, the PCF can compare the STP / RSTP / MSTP Supported / not-supported configured in the PCF, the STP / RSTP / MSTP Subscribed / not-subscribed configured in the UDM, and the STP / RSTP / MSTP Requested / not-requested included in the PDU Session Request. If the Policy is STP / RSTP / MSTP Supported, the UE Subscription information from the UDM is STP / RSTP / MSTP Subscribed, the configuration information of the DNN / S-NSSAI is STP / RSTP / MSTP Supported, and the Indication of the PDU Session is STP / RSTP / MSTP Requested, the PCF can confirm the SM Policy value of the corresponding PDU Session as STP / RSTP / MSTP Supported. If additional QoS settings are required to support STP / RSTP / MSTP, PCF can update the QoS information by selecting a Policy from the parameter sets that satisfies the required QoS.

[0098] In step 15, the PCF may send an SM Policy Association Establishment / Modification response to the SMF. The SM Policy Association Establishment / Modification response may include at least one of DNN / S-NSSAI, Internal Group ID, STP / RSTP / MSTP Supported / not-supported, STP / RSTP / MSTP Subscribed / not-subscribed, or QoS Parameters.

[0099] In step 16, the SMF can check the SMF Local Configuration and Policy. In addition, the SMF can update the SMF Local Configuration and Policy by DNN / S-NSSAI if necessary. If the SMF receives the Local Configuration and Policy information from the PCF and STP / RSTP / MSTP Supported, the SMF can set the corresponding PDU Session to STP / RSTP / MSTP Enabled. If the SMF requires additional QoS settings for STP / RSTP / MSTP support, the SMF can receive parameters from the PCF in step 15 that allow the Policy for the QoS change request in step 8. If the SMF satisfies the required QoS, the SMF can proceed with the subsequent PDU Session Establishment / Modification process according to the QoS settings with the received parameters. At this time, if the required QoS is not satisfied, the SMF can trigger the termination of the PDU Session.

[0100] In step 17, the SMF can perform N4 Setup for the UPF. At this time, the N4 Setup can include STP / RSTP / MSTP Enabled / Disabled information. A UPF with one or more Ethernet PDU Sessions set to STP / RSTP / MSTP Enabled can participate in Ethernet-based path configuration as a Bridge with the corresponding Ethernet PDU Sessions and N6 and N19 Interfaces as Ports by periodically generating, transmitting, receiving, and interpreting BPDUs. In addition, the UPF can prevent loop creation by participating in Ethernet-based path configuration. If there is no Ethernet PDU Session set to STP / RSTP / MSTP Enabled among the PDU Sessions connected to the UPF, the UPF may not perform the operation of preventing loop creation by periodically generating, transmitting, receiving, and interpreting BPDUs to participate in Ethernet-based path configuration. Additional QoS settings (e.g., QoS settings in step 8 or additional QoS settings in step 16) can also be applied to the UPF in step 17.

[0101] In step 18, the SMF may transmit a PDU Session Establishment / Modification response to the UE via the AMF and RAN. The PDU Session Establishment / Modification response may include at least one of DNN / S-NSSAI, SUPI, or STP / RSTP / MSTP Indication. Additionally, QoS parameters for the RAN and UE may also be transmitted and configured in step 18. Of course, the present invention is not limited to the above examples.

[0102] FIG. 5 is a diagram illustrating an example configuration of a network entity in a wireless communication system according to various embodiments of the present disclosure.

[0103] The network entity of FIG. 5 may be one of the network entities described in the embodiments of FIGS. 1 to 4.

[0104] A network entity according to one embodiment of the present disclosure may include a processor (510) that controls the overall operation of the network entity, a transceiver (520) including a transmitter and a receiver, and a memory (530). Of course, the present invention is not limited to the above example, and the network entity may include more or fewer components than those illustrated in FIG. 5.

[0105] According to one embodiment of the present disclosure, the transceiver (520) can transmit and receive signals with at least one of other network entities or terminals. The transmitted and received signals may include at least one of control information and data. If the network entity of FIG. 5 is a core network entity (NF), the signals transmitted and received between the network entity and the terminal may be transmitted and received via the RAN.

[0106] According to one embodiment of the present disclosure, the processor (510) may control the overall operation of the corresponding network entity to perform an operation according to one or a combination of two or more of the embodiments of FIGS. 1 to 4 described above. Meanwhile, the processor (510), the transceiver (520), and the memory (530) do not necessarily have to be implemented as separate modules, and may of course be implemented as a single component in the form of a single chip. In addition, the processor (510) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor. The transceiver (520) may include at least one communication interface for transmitting and receiving signals with another network entity via wired / wireless.

[0107] According to one embodiment of the present disclosure, the memory (530) can store data such as basic programs, application programs, and setting information for the operation of the corresponding network entity. In addition, the memory (530) provides the stored data upon request of the processor (510). The memory (530) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (530). In addition, the processor (510) can perform at least one of the above-described embodiments based on a program for performing an operation according to at least one of the above-described embodiments of the present disclosure stored in the memory (530).

[0108] FIG. 6 is a diagram illustrating an example configuration of a base station in a wireless communication system according to various embodiments of the present disclosure. The base station of FIG. 6 may refer to the RAN node described in the embodiments of FIGS. 1 to 4.

[0109] A base station according to one embodiment of the present disclosure may include a processor (610) that controls the overall operation of the base station, a transceiver (620) including a transmitter and a receiver, and a memory (630). Of course, the present invention is not limited to the above example, and the base station may include more or fewer components than those illustrated in FIG. 6.

[0110] According to one embodiment of the present disclosure, a transceiver (620) can transmit and receive signals with at least one of a terminal, another base station, or a network entity. The transmitted and received signals can include at least one of control information and data.

[0111] According to one embodiment of the present disclosure, the processor (610) may control the overall operation of the base station to perform operations according to one or a combination of two or more of the embodiments of FIGS. 1 to 4 described above. Meanwhile, the processor (610), the transceiver (620), and the memory (630) do not necessarily have to be implemented as separate modules, and may of course be implemented as a single component in the form of a single chip. In addition, the processor (610) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor. The transceiver (620) may include at least one communication interface for transmitting and receiving signals wired / wirelessly to and from a terminal, another base station, or a network entity.

[0112] According to one embodiment of the present disclosure, the memory (630) can store data such as basic programs, application programs, and setting information for the operation of the corresponding base station. In addition, the memory (630) provides the stored data upon request of the processor (610). The memory (630) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (630). In addition, the processor (610) can perform at least one of the above-described embodiments based on a program for performing an operation according to at least one of the above-described embodiments of the present disclosure stored in the memory (630).

[0113] FIG. 7 is a diagram showing an example configuration of a terminal in a wireless communication system according to various embodiments of the present disclosure.

[0114] A terminal according to one embodiment of the present disclosure may include a processor (710) that controls the overall operation of the terminal, a transceiver (720) including a transmitter and a receiver, and a memory (730). Of course, the terminal is not limited to the above example, and the terminal may include more or fewer components than those illustrated in FIG. 7.

[0115] According to one embodiment of the present disclosure, a transceiver (720) can transmit and receive signals with at least one other terminal, base station, or network entity. The transmitted and received signals can include at least one of control information and data.

[0116] According to one embodiment of the present disclosure, the processor (710) may control the overall operation of the terminal to perform an operation according to one or a combination of two or more of the embodiments of FIGS. 1 to 4 described above. Meanwhile, the processor (710), the transceiver (720), and the memory (730) do not necessarily have to be implemented as separate modules, and may of course be implemented as a single component in the form of a single chip. In addition, the processor (710) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor. The transceiver (720) may include at least one communication interface for transmitting and receiving signals with another terminal, a base station, or a network entity via wired / wireless.

[0117] According to one embodiment of the present disclosure, the memory (730) can store data such as basic programs, application programs, and setting information for the operation of the terminal. In addition, the memory (730) provides the stored data upon request of the processor (710). The memory (730) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (730). In addition, the processor (710) can perform at least one of the above-described embodiments based on a program for performing an operation according to at least one of the above-described embodiments of the present disclosure stored in the memory (730).

[0118] 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.

[0119] When implemented in software, 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 within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present disclosure.

[0120] These programs (software modules, software) may be stored in a non-volatile memory including random access memory, flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0121] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.

[0122] In the specific embodiments of the present disclosure described above, components included in the present disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0123] Meanwhile, a part or all of one or more embodiments proposed in the present disclosure may be applied in combination with a part or all of one or more other embodiments, and such combination forms are also included within the scope of the present disclosure.

[0124] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below but also by equivalents thereof. Furthermore, the above-described embodiments may be combined and operated as needed, as long as there is no technical contradiction.

Claims

1. A method performed by a user plane function (UPF) entity of a wireless communication system, A step of receiving information related to STP (spanning tree protocol) from an SMF (session management function) entity; A step of generating a BPDU (bridge protocol data unit) based on information related to the above STP; and A step of identifying an Ethernet path based on the above BPDU is included. A method wherein the above Ethernet path is a path that does not include a loop.

2. In paragraph 1, A method wherein the above STP includes RSTP (rapid spanning tree protocol) or MSTP (multiple spanning tree protocol).

3. In paragraph 1, A method, wherein the information related to the STP includes at least one of information regarding whether the STP is supported or the type of the STP.

4. In paragraph 1, A method wherein the information related to the above STP is included in a terminal's PDU (protocol data unit) session setup request or PDU session change request.

5. In paragraph 4, The above PDU session setup request or the above PDU session change request includes information for instructing the STP, A method, wherein the information for indicating the STP includes an instruction regarding the STP or an instruction based on DNN / S-NSSAI (data network name / single network slice selection assistance information).

6. In paragraph 1, Information related to the above STP is included in the subscription information of the UDR (unified data repository) entity or the policy information of the SMF entity. A method, wherein the information related to the STP includes at least one of whether the STP is supported or whether the STP is subscribed to.

7. In paragraph 1, Information related to the above STP is included in the configuration information of the UDM (unified data management) entity. A method, wherein the information related to the STP includes at least one of information regarding whether the STP is supported for each DNN / S-NSSAI or whether the STP is subscribed to for each terminal.

8. In paragraph 1, A method wherein whether or not to apply the above STP is based on QoS (quality of service) settings.

9. In the UPF (user plane function) entity of a wireless communication system, Transmitter and receiver; and At least one control unit connected to the above transceiver unit, At least one of the above control units: Receive information related to STP (spanning tree protocol) from SMF (session management function) entity, Generates a BPDU (bridge protocol data unit) based on the information related to the above STP, and It is set to identify the Ethernet path based on the above BPDU, A UPF entity in which the above Ethernet path is a path that does not contain a loop.

10. In paragraph 9, The above STP is a UPF entity that includes RSTP (rapid spanning tree protocol) or MSTP (multiple spanning tree protocol).

11. In paragraph 9, A UPF entity, wherein the information related to the STP includes at least one of information regarding whether the STP is supported or the type of the STP.

12. In paragraph 9, The UPF entity, which is information related to the above STP, is included in the terminal's PDU (protocol data unit) session setup request or PDU session change request.

13. In paragraph 12, The above PDU session setup request or the above PDU session change request includes information for instructing the STP, A UPF entity, wherein the information for indicating the above STP includes an instruction regarding the above STP or an instruction based on DNN / S-NSSAI (data network name / single network slice selection assistance information).

14. In paragraph 9, Information related to the above STP is included in the subscription information of the UDR (unified data repository) entity or the policy information of the SMF entity. A UPF entity, wherein information related to said STP includes at least one of whether said STP is supported or whether said STP is subscribed to.

15. In paragraph 9, Information related to the above STP is included in the configuration information of the UDM (unified data management) entity. A UPF entity, wherein the information related to the above STP includes at least one of information regarding whether the STP is supported for each DNN / S-NSSAI or whether the STP is subscribed to for each terminal.

Images