Method and apparatus for enhancing reliability in a wireless communication system

Abstract

A method and apparatus for enhancing reliability in a wireless communication system are provided. An operation method of a user plane function (UPF) in a wireless communication system includes receiving NF set related information changed through an association procedure with a network function (NF), changing a profile of the NF based on the received NF set related information, and performing an operation related to the NF based on the changed profile.

Description

Technical Field

[0001] This disclosure relates to a method and apparatus for enhancing reliability in a wireless communication system. Background Technology

[0002] To meet the increasing demand for wireless data services following the commercialization of fourth-generation (4G) communication systems, considerable efforts have been made to develop improved fifth-generation (5G) communication systems, or near-5G communication systems. Therefore, 5G or near-5G communication systems are referred to as super-4G network communication systems or post-Long Term Evolution (LTE) systems.

[0003] To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency bands (millimeter wave (mmWave)) (e.g., the 60 GHz band). To reduce radio wave propagation loss and increase the transmission range of radio waves in ultra-high frequency bands, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are being discussed.

[0004] In addition, technologies such as evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receive interference cancellation are being developed to improve the system network used in 5G communication systems.

[0005] In addition, advanced coding and modulation (ACM) technologies such as hybrid FSK and QAM modulation (FQAM), sliding window superposition coding (SWSC), and advanced access technologies such as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) are being developed in 5G systems.

[0006] Meanwhile, the internet has evolved from a human-centric connectivity network (through which humans generate and consume information) to an Internet of Things (IoT) network, which exchanges and processes information between distributed elements such as objects. The Internet of Everything (IoE) technology has emerged, where IoT technology is combined with technologies such as those that process big data by connecting to cloud servers. To realize IoT, various technological components are needed, such as sensing technologies, wired / wireless communication and network infrastructure, service interface technologies, and security technologies. In recent years, technologies including sensor networks for connecting objects, machine-to-machine (M2M) communication, and machine-type communication (MTC) have been researched. In the IoT environment, intelligent internet technology (IT) services can be provided to collect and interpret data obtained from interconnected objects and create new value in human life. With the convergence and integration of existing information technology (IT) technologies and various industries, IoT can be applied to various fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and high-quality medical services.

[0007] Various attempts are underway to apply 5G communication systems to IoT networks. For example, technologies related to sensor networks, M2M communication, and MTC are being implemented using 5G communication technologies, such as beamforming, MIMO, and array antenna schemes. The application of cloud RAN, as a big data processing technology, can serve as an example of the convergence of 5G communication and IoT technologies.

[0008] With the development of various information technologies (IT), network devices have evolved into virtualized network functions (NFs) (hereinafter referred to as "network elements") by applying virtualization technology. This allows virtualized NFs to be implemented in software form, exceeding physical limitations, and to be launched / operated in various types of clouds or data centers (DCs). Specifically, NFs can be freely scaled up or down, launched or terminated according to service demands, system capacity, and network load. Even when these NFs are implemented in software, it should be noted that physical configuration is not excluded, as NFs must essentially run on physical configurations (e.g., devices). Furthermore, NFs can be implemented with simple physical configurations, i.e., simply as hardware.

[0009] To support various services across these different network architectures, network slicing technology was introduced. Network slicing is a technique used to logically structure a network as a set of Network Functions (NFs) supporting specific services and separating it from other slices. When a terminal receives various services, it can access two or more slices. Summary of the Invention

[0010] Technical solutions

[0011] According to embodiments of this disclosure, an operation method of a user plane function (UPF) in a wireless communication system includes receiving NF set-related information that has been modified through an association process with a network function (NF), modifying the profile of an NF based on the received NF set-related information, and performing NF-related operations based on the modified profile.

[0012] Beneficial effects

[0013] According to embodiments of this disclosure, the reliability of wireless communication systems can be improved. Attached Figure Description

[0014] The above and other aspects, features, and advantages of certain embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings, wherein:

[0015] Figure 1 This is a diagram illustrating a wireless communication system according to various embodiments of the present disclosure;

[0016] Figure 2 This is a diagram illustrating the relationship between the Session Management Function (SMF) and the User Plane Function (UPF) according to embodiments of the present disclosure;

[0017] Figure 3 This is a diagram illustrating network operation when the set information of the SMF is changed according to an embodiment of the present disclosure;

[0018] Figure 4 This is a diagram illustrating network operations using SMF sets according to embodiments of the present disclosure;

[0019] Figure 5 This is a diagram illustrating network operation using an SMF set according to another embodiment of the present disclosure;

[0020] Figure 6 This is a diagram illustrating network operation using an SMF set according to another embodiment of the present disclosure;

[0021] Figure 7 This is a flowchart of the operation of the UPF according to embodiments of the present disclosure;

[0022] Figure 8 This is a flowchart illustrating the operation of a network function (NF) according to embodiments of the present disclosure; and

[0023] Figure 9 This is an apparatus diagram illustrating the configuration of an NF according to an embodiment of the present disclosure. Detailed Implementation

[0024] A method and apparatus for enhancing reliability in a wireless communication system are provided.

[0025] Additional aspects will be set forth in part in the description which follows, and in part will be apparent from the description, or may be learned by practice of the embodiments presented in this disclosure.

[0026] According to embodiments of this disclosure, an operation method of a user plane function (UPF) in a wireless communication system includes receiving NF set-related information that has been modified through an association process with a network function (NF), modifying the profile of an NF based on the received NF set-related information, and performing NF-related operations based on the modified profile.

[0027] According to another embodiment of this disclosure, a user plane function (UPF) of a wireless communication system includes: a transceiver; a memory; and a processor configured to control such that NF set-related information, which is modified through an association process with respect to network functions (NFs), is received, an NF profile is modified based on the received NF set-related information, and NF-related operations are performed based on the modified profile to be performed.

[0028] Inventive Method

[0029] Before proceeding with the detailed description below, it may be advantageous to define certain words and phrases used in this patent document: the terms “comprising” and “including” and their derivatives mean including but not limited to; the term “or” includes, and its meaning and / or; the phrases “associated with” and “associated with” and their derivatives may mean including, including in, interconnected with, containing, contained within, connected to or coupled with, communicating with, cooperating with, interleaving, juxtaposed, proximate, bound to or having its attributes, etc.; the term “controller” means any device, system or part thereof that controls at least one operation, such device may be implemented in hardware, firmware or software or some combination of at least two of these. It should be noted that the functionality associated with any particular controller can be centralized or distributed, whether local or remote.

[0030] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit temporary electrical or other signals. Non-transitory computer-readable media includes media that can permanently store data and media that can store data and subsequently rewrite it, such as rewritable optical discs or erasable storage devices.

[0031] This patent document provides definitions for certain words and phrases, and those skilled in the art will understand that, in many, if not most, cases, such definitions apply to the words and phrases defined therebefore and in the future.

[0032] The following discussion Figures 1 to 9 The various embodiments used to describe the principles of this disclosure in this patent document are merely examples and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or device.

[0033] Throughout the disclosure, the expression "at least one of a, b or c" means only a, only b, only c, both a and b, both a and c, both b and c, all of a, b and c, or variations thereof.

[0034] Examples of terminals may include user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, multimedia system capable of performing communication functions, etc.

[0035] In this disclosure, the controller may be referred to as a processor.

[0036] In this disclosure, a layer (or layer device) may also be referred to as an entity.

[0037] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of other embodiments. Singular expressions may include plural expressions unless the context clearly specifies otherwise. The terminology used herein, including technical or scientific terms, may have the same meaning as commonly understood by one of ordinary skill in the art as described in this disclosure. Among the terminology used in this disclosure, terms defined in general dictionaries may be interpreted as having the same or similar meaning as in the relevant technical context, and should not be construed as having an ideal or overly formal meaning unless expressly defined in this disclosure. In some cases, even terms defined in this disclosure should not be construed as excluding embodiments of this disclosure.

[0038] In the various embodiments of this disclosure described below, hardware access methods will be described as examples. However, because the various embodiments of this disclosure include techniques using both hardware and software, software-based methods are not excluded from the various embodiments of this disclosure.

[0039] In the following, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that, in this context, the same components are indicated by the same reference numerals wherever possible. Furthermore, detailed descriptions of well-known functions and configurations that may obscure the spirit of the present disclosure will be omitted.

[0040] In describing embodiments of this disclosure, descriptions of technical content that is well-known in the art to which this disclosure pertains and is not directly related to this disclosure will be omitted. This is to more clearly convey the essential points of this disclosure by omitting unnecessary descriptions.

[0041] For the same reason, some components are exaggerated, omitted, or shown schematically in the accompanying drawings. Furthermore, the size of each component does not perfectly reflect its actual size. In each drawing, the same or corresponding elements are given the same reference numerals.

[0042] The advantages and features of one or more embodiments of this disclosure, as well as methods of implementing them, can be more readily understood by referring to the following detailed description and accompanying drawings of embodiments of this disclosure. However, this disclosure may be embodied in many different forms and should not be construed as limiting itself to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey to those skilled in the art the scope of this disclosure as defined only by the claims. Throughout this disclosure, the same reference numerals refer to the same elements.

[0043] In this context, it should be understood that each block of the flowchart and combinations thereof can be executed by computer program instructions. Because these computer program instructions can be embedded in the processor of a general-purpose computer, special-purpose computer, or other programmable data processing device, the instructions executed by the processor of the computer or other programmable data processing device generate modules for performing the functions described in one or more flowchart blocks. Because these computer program instructions can also be stored in a computer-executable or computer-readable storage device, and can instruct the computer or other programmable data processing device to implement functions in a particular manner, the instructions stored in the computer-executable or computer-readable storage device can also produce an article of art containing instruction modules for performing the functions described in one or more flowchart blocks. Because the computer program instructions can also be embedded in a computer or other programmable data processing device to generate computer-implemented processing by performing a series of operations on the computer or other programmable data processing device, the instructions of the computer or other data processing device can provide operations for performing the functions described in one or more flowchart blocks.

[0044] Furthermore, each block may represent a portion of a module, segment, or code that includes one or more executable instructions for performing one or more specified logical functions. It should also be noted that in some alternative implementations, the functions described in a block may not appear in the order shown in the figures. For example, two blocks shown consecutively may actually be executed substantially simultaneously, or these blocks may sometimes be executed in reverse order, depending on the functions involved.

[0045] As used in this embodiment of the disclosure, the term "-unit" refers to a software or hardware component that performs certain tasks, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC). However, the terms "module" or "-device / machine" are not limited to software or hardware. The terms "module" or "-device / machine" can be configured in addressable storage media or configured to reproduce one or more processors. Thus, for example, the terms "module" or "-device / machine" include elements such as software elements, object-oriented software elements, class elements and task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided in elements and "modules" or "-devices / machines" can be combined with fewer elements and "modules" or "-devices / machines," or can be decoupled from additional elements and "modules" or "-devices / machines." Furthermore, elements and "modules" or "-devices / machines" can be implemented to reproduce one or more central processing units (CPUs) in a device or secure multimedia card.

[0046] This disclosure relates to a method and apparatus for supporting various services in a wireless communication system. For example, this disclosure describes a technique in a wireless communication system for supporting various services by supporting the mobility of a UE.

[0047] Here, terms used to identify access nodes, terms used to refer to network entities or network functions (NFs), terms used to refer to messages, terms used to refer to interfaces between network entities, and terms used to refer to various types of identification information are examples for ease of explanation. Therefore, this disclosure is not limited to the terms described later, and other terms may be used to refer to entities with equivalent technical meanings.

[0048] For ease of explanation, this disclosure will use terms and definitions defined by the 3GPP LTE and 5G standards. However, this disclosure is not limited to terms and names and can be equally applied to systems conforming to other standards.

[0049] For ease of explanation, entities that exchange information for access control and state management will now be collectively referred to as "NFs". For example, an NF may be at least one of an Access and Mobility Management Function (hereinafter referred to as AMF) device, a Session Management Function (hereinafter referred to as SMF) device, or a Network Slice Selection Function (hereinafter referred to as NSSF) device. However, embodiments of this disclosure can be equally applied when an NF is implemented as an instance (e.g., an AMF instance, an SMF instance, an NSSF instance, etc.).

[0050] In this disclosure, in an instance, an NF can exist in the form of software code and can be executed by receiving physical and / or logical resources from a physical computing system (e.g., a computing system existing on the core network) to perform the NF's functions within the computing system. All NF instances (such as AMF instances, SMF instances, etc.) can refer to instances that can be used by receiving physical and / or logical resources for NF operation from a computing system existing on the core network. As a result, NF instances in the presence of physical NF devices such as AMFs, SMFs, etc., and NF instances that receive and use physical and / or logical resources for NF operation from a computing system existing on the network, can perform the same operations.

[0051] Figure 1 Wireless communication systems according to various embodiments of the present disclosure are shown.

[0052] refer to Figure 1 Radio access node (RAN) 110 and user equipment (UE) 120 are shown as part of a node using a radio channel in a wireless communication system. Although Figure 1The diagram shows a RAN 110 and a UE 120, but may also include another RAN that is the same as or similar to RAN 110. Furthermore, Figure 1 This focuses on the scenario where a single UE 120 performs communication with a single RAN 110. However, it is clear that in reality, multiple UEs may communicate with a single RAN 110.

[0053] RAN 110 includes the network infrastructure that provides radio access to UE 120. RAN 110 may have coverage defined as a geographical area based on the range from which signals can be transmitted from RAN 110. In addition to base stations, RAN 110 may be referred to as an access point (AP), eNodeB (eNB), gNodeB (gNB), fifth-generation (5G) node, radio point, transmit / receive point (TRP), or other terms with equivalent technical meanings.

[0054] UE 120 is a device used by the user and performs communication with RAN 110 via a radio channel. In some cases, UE 120 can operate without user intervention. For example, UE 120 is a device for performing machine-type communication (MTC) and may not be carried by the user. Figure 1 The UE 120 shown may include at least one user portable device, and may also include at least one MTC. The UE 120 may be referred to as a terminal, mobile station, subscriber station, remote terminal, wireless terminal, user equipment, user device, or other terms with the same technical meaning.

[0055] AMF 131 may include a network entity for managing wireless network access and mobility. SMF 132 may include a network entity for managing access to a packet data network for providing packet data to UE 120. UE 120 and SMF 132 can connect to each other via packet data unit (PDU) sessions.

[0056] User plane function (UPF) 133 may include, or may function as, a gateway for delivering packets sent and received by UE 120. UPF 133 may be connected to data network (DN) 140 via the Internet to provide a path for data transmission or reception between UE 120 and DN 140. Therefore, UPF 133 can route data in packets sent by UE 120 destined for the Internet to the Internet data network.

[0057] The Network Slice Selection Function (NSSF) 134 may include a network entity that performs the network selection operation described herein (e.g., the operation of selecting a network slice). The operation of NSSF 134 will be described in detail later with reference to the accompanying drawings.

[0058] The Authentication Server Function (AUSF) 151 can provide services for the subscriber authentication process.

[0059] Network Exposure Function (NEF) 152 can access information used to manage UE 120 in a 5G network, subscribe to UE 120's mobility management events, subscribe to UE 120's session management events, request session-related information, set UE 120's billing information, request changes to UE 120's PDU session policy, and send small amounts of data from UE 120.

[0060] The Network Repository Function (NRF) 153 can store the state information of NFs and handle requests for finding NFs that can be accessed by other NFs.

[0061] The Policy and Charging Function (PCF) 154 can apply the mobile network operator's service policies, charging policies, and policies for the PDU sessions of UE 120.

[0062] Unified Data Management (UDM) 155 can store information about subscribers and / or UEs 120.

[0063] Application Function (AF) 156 can provide services to users by interoperating with mobile communication networks.

[0064] Service Communication Agent (SCP) 157 can provide functions such as discovering NFs for communication between NFs and sending messages between NFs. SCP 157 may operate in an integrated form with NRF 153, depending on the operator's choice, in which case SCP 157 may include the functionality of NRF 153, or conversely, NRF 153 may include the functionality of SCP 157.

[0065] For ease of explanation, entities that exchange information for access control and state management will now be collectively referred to as "NFs". For example, an NF may include one of AMF, SMF, NSSF, etc. Embodiments of this disclosure can be equally applied to situations where an NF is implemented as an instance (e.g., an AMF instance, an SMF instance, an NSSF instance, etc.).

[0066] In a network, it is essential to handle various situations that may arise during the actual operation of an NF (Network Function) and to recover from problems without affecting services. In this disclosure, a group of NFs providing the same functionality / service is defined as an NF set, and a method is provided for adaptively responding to changes in network conditions (the creation of new NFs, the termination of existing NFs, NF failures, etc.). Although this disclosure does not specify a set of NF services that bundles the NF services provided by an NF and equivalent NF services, the main points of this disclosure can be applied not only to NF sets but also to NF service sets.

[0067] In an embodiment, the NF set can be mapped to UPFs on the network at a ratio of N:M (N≥1, M≥1). Furthermore, the NF can include control plane entities, including AMFs, SMFs, etc.

[0068] Figure 2 This is a diagram illustrating the relationship between the SMF and UPF according to an embodiment of the present disclosure.

[0069] exist Figure 2 In this context, SMF is described as an example of NF. Figure 2 The diagram shows two SMF sets, such as set #1 210 and set #2 220, where N SMF instances 212, 212, and 21N are included in SMF set #1 210, and M SMF instances 221, 222, and 22N are included in SMF set #2 220. Figure 2 In this context, each of the two UPFs (e.g., UPF#A 230 and UPF#B 240) is interlocked with the SMF sets #1 210, #2 220, and the SMF instances of #1 210. In other words, the SMF sets and UPFs can freely have associations with each other.

[0070] The configuration of an SMF set, the instances included in the SMF set, and its association with a UPF can all be dynamically changed according to network conditions and operational needs. When an SMF set changes within the network, it can be broadly categorized into two types. The first type involves the creation of a new SMF set itself, the set disappearing, or changes to the set's information (set ID, etc.). The second type occurs when the set information of an SMF instance is modified. Changes to set information can include all additions, deletions, and updates to SMF instances.

[0071] Figure 3 This is a diagram illustrating network operation when the collection information of the SMF is changed according to an embodiment of the present disclosure.

[0072] When the set configuration of SMF 310 is changed, in embodiments of this disclosure, SMF 310 can transmit the changed information to another NF (e.g., AMF 330) via NRF 320. In other words, SMF 310 can notify NRF 320 of its changed set information. This process is performed by registering a new NF profile including the set information of SMF 310 or by changing / updating an existing NF profile. NRF 320 can notify another NF of the changed SMF information. In embodiments, UPF 340 can receive notifications when it is interlocked with NRF 320. However, when UPF 340 is not interlocked with NRF 320, UPF 340 may have difficulty receiving notifications.

[0073] Figure 4 This is a diagram illustrating network operations using SMF sets according to embodiments of the present disclosure.

[0074] In operation 410, SMF 402 can modify set information (including set ID) via instructions from Operation, Administration and Maintenance (OAM) 401. This instruction from OAM 401 can be executed automatically when an operator command is entered or conditions are met. When OAM 401 and SMF 402 are separated, OAM 401 can send a message to SMF 402 containing configuration information including instructions from OAM 401, and receive a response to it.

[0075] In operation 420, configure the new SMF set information (including set ID) in SMF 402.

[0076] In operation 430, SMF 402 sends an association establishment request message to UPF 403 to generate an N4 (Packet Forwarding Control Protocol (PFCP)) association with UPF 403, thereby sending SMF set information to UPF 403. When SMF 402 needs to restrict or select the target UPF 403 to be operated on based on the SMF set configured by SMF 402, SMF 402 can perform operations to select the target UPF 403. For this purpose, SMF 402 can use information such as SMF set ID, slice ID (Single Network Slice Selection Auxiliary Information (S-NSSAI)), and data network name (DNN). When there is an existing N4 (PCFP) association that SMF 402 has already established with the target UPF 403, and the existing association becomes invalid due to a change in the SMF set, SMF 402 can send a request to UPF 403 to release the existing association before sending an association establishment request message to create a new association, and receive a release response to it. The new SMF set information, specifically the set ID, can be included in the association establishment request message used to create the new association. Additionally, the information sent from SMF 402 may include a timer value, which can be used to notify the requesting SMF 402 when to begin operations with the new SMF set ID.

[0077] In operation 440, UPF 403 can obtain SMF set information, specifically the SMF set ID, from the message received from SMF 402, and store the obtained SMF set information as information for the corresponding SMF 402. UPF 403 can store and use the obtained information on an SMF-by-SMF basis (i.e., on an SMF instance basis), or it can store and use information on the currently processed N4 (PFCP) association basis. When a timer value is included in the received message, UPF 403 starts a timer based on the timer value and determines that the corresponding SMF 402 will begin operating on a new set when the timer has expired.

[0078] In operation 450, UPF 403 generates an N4 (PCFP) association through the message received from SMF 402 and sends an association establishment response message in response to this.

[0079] In operation 460, UPF 403 performs operations using the stored SMF set information. In other words, when the SMF set includes two or more SMF instances, UPF 403 can use them to perform computational operations, session processing requests / notifications, or fault recovery procedures. For example, when a transaction requiring an SMF set is needed, UPF 403 can select and process an available SMF instance from the SMF instances included in the SMF set. Alternatively, regarding transactions to be processed for an SMF instance, if the corresponding SMF instance is unresponsive or unable to receive requests due to failure and / or overload, and another SMF instance needs to be selected, UPF 403 can select another SMF instance using the SMF set ID of the corresponding SMF instance.

[0080] Figure 5 This is a diagram illustrating network operations using an SMF set according to another embodiment of the present disclosure.

[0081] In operation 510, SMF 502 can modify set information (including set ID) via an instruction from OAM 501. This instruction from OAM 501 can be executed by a function configured to automatically execute upon input of an operator command or when conditions are met. When OAM 501 and SMF 502 are separated from each other, OAM 501 can send a message to SMF 502 containing configuration information including the instruction from OAM 501 and receive a response to it.

[0082] In operation 520, configure the new SMF collection information (including the collection ID) in SMF 502.

[0083] In operation 530, UPF 503 sends an association establishment request message to SMF 502 to create an N4 (PFCP) association based on certain conditions. These conditions may include the recognition that a new UPF has been created, UPF 503 has been restarted, the SMF configuration has been changed, or the SMF instance and existing N4 (PCFP) associations have been released and a new association is needed. UPF 503 may include service information supported by UPF 503 (slice identifier, DNN, etc.) in the association establishment request message.

[0084] In operation 540, SMF 502 sends an association establishment response message to UPF 503, and SMF set information (including the SMF set ID) is included in the association establishment response message. In this case, when SMF 502 can select the SMF set to be included in the association establishment response message (i.e., when the SMM instance supports at least two sets), SMF 502 can use information such as slice ID (S-NSSAI), DNN, etc. When SMF 502 has previously established an N4 (PCFP) association with the target UPF, and the existing association becomes invalid due to the change in the SMF set, SMF 502 can send a request to UPF 503 to release the existing association before sending an association establishment response message for creating a new association, and receive a release response in response. New SMF set information, specifically the set ID, can be included in the association establishment response message for creating a new association. In addition, the set information of the response message sent from SMF 502 may include a timer value, and the timer value may be used to notify UPF 503 when the SMF 502 that sent the response will begin to operate with the new SMF set ID.

[0085] Table 1 shows the message format for sending an N4 (PFCP) association establishment response message that includes the SMF set ID. This information can be included in the message and sent along with the ID of the NF sending the message and information indicating the reason for sending.

[0086] [Table 1]

[0087]

[0088]

[0089] In operation 550, UPF 503 can obtain the set information of SMF 502, specifically the SMF set ID, from the message received from SMF 502, and store the obtained set information as information for the corresponding SMF. UPF 503 can store and use the obtained information on an SMF-by-SMF basis (i.e., on an SMF instance basis) or on a currently processed N4 (PFCP) association basis. When a timer value is included in the received message, UPF 503 starts a timer based on the timer value and determines that SMF 502 will operate with a new set after the timer expires.

[0090] In operation 560, UPF 503 performs operations using stored SMF set information. In other words, when the SMF set includes two or more SMF instances, UPF 503 can use them to perform computational operations, session handling requests / notifications, and fault recovery procedures. For example, when a transaction concerning the SMF set is needed, UPF 503 can select and process one available SMF instance from those belonging to the SMF set. Alternatively, regarding a transaction to be processed for an SMF instance, if the corresponding SMF instance is unresponsive or has not received a request due to failure and / or overload, another SMF instance can be selected using the SMF set ID of the corresponding SMF instance.

[0091] Figure 6 This is a diagram illustrating network operations using an SMF set according to another embodiment of the present disclosure.

[0092] In operation 610, SMF 602 and UPF 603 are operated by creating an N4 (PFCP) association between them.

[0093] In operation 620, SMF 602 can modify set information (including set ID) via an instruction from OAM 601. This instruction from OAM 601 can be executed by a function configured to automatically execute upon input of an operator command or when conditions are met. When OAM 601 and SMF 602 are separated from each other, OAM 601 can send a message to SMF 602 including configuration information for changing the set ID and receive a response to it.

[0094] In operation 630, SMF 602 is configured with new SMF set information (including set ID). For this purpose, SMF 602 determines that the N4 (PCFP) association established with the existing UPF 603 needs to be updated. When SMF 602 needs to restrict or select the target UPF 603 to be operated on based on the SMF set configured by SMF 602, SMF 602 can perform operations for selecting the target UPF 602. For this purpose, SMF 602 can use information such as SMF set ID, slice ID (S-NSSAI), DNN, etc.

[0095] In operation 640, SMF 602 sends an N4 (PFCP) association update request message to UPF 603 to update the SMF set information with UPF 603. The new SMF set information, specifically the set ID, can be included in the association update request message. Furthermore, the information sent from SMF 602 may include a time value, and this timer value can be used to notify the requesting SMF 602 of the time to begin operating with the new SMF set ID.

[0096] Table 2 shows the message format for sending an N4 (PFCP) association update request message that includes the SMF set ID. This information can be included in the message and sent along with the ID of the NF sending the message and information indicating the reason for sending.

[0097] [Table 2]

[0098]

[0099] In operation 650, UPF 603 obtains the set information of SMF 602 and updates the obtained set information to the corresponding SMF 602 information through messages received from SMF 602. Specifically, it can obtain and store the SMF set ID. UPF 603 can store and use the obtained information on an SMF-by-SMF basis (i.e., on an SMF instance basis) or on a currently processed N4 (PFCP) association basis. When a timer value is included in the received message, UPF 603 starts the timer and determines that the corresponding SMF 602 will operate on a new set after the timer expires.

[0100] In operation 660, UPF 603 can update the N4 (PCFP) association by receiving a message from SMF 602 and send a response to it.

[0101] In operation 670, UPF 603 performs operations using the stored SMF set information. In other words, when the SMF set includes two or more SMF instances, UPF 603 can use them to perform computational operations, session processing requests / notifications, and fault recovery procedures. For example, when a transaction involving an SMF set is required, UPF 603 can select and process one available SMF instance from those belonging to the SMF set. Alternatively, regarding transactions to be processed for an SMF instance, if the corresponding SMF instance is unresponsive or has not received a request due to failure and / or overload, another SMF instance can be selected using the SMF set ID of the corresponding SMF instance.

[0102] Although the above description illustrates SMF 602 triggering the N4 (PFCP) association update process, this embodiment can be applied similarly when UPF 603 begins the N4 (PFCP) association update process. In this case, UPF 603 sends an update request to SMF 602, and when SMF 602 determines that the set information corresponding to UPF 603 needs to be updated, SMF 602 can insert the changed set information (including the set ID) into the update response message and send that message. The operation of the UPF described above is as follows.

[0103] Figure 7 This is a flowchart of the operation of the UPF according to an embodiment of the present disclosure.

[0104] refer to Figure 7 In operation 710, the UPF can receive information related to the NF set that has been changed through the association process with the NF.

[0105] In an embodiment, the UPF can receive an association request from the NF, including information about the NF set to be modified, and send an association response to the association request to the NF, thereby receiving the information about the NF set to be modified. Furthermore, the UPF can send an association request to the NF and receive an association response from the NF, including information about the NF set to be modified, thereby receiving the information about the NF set to be modified. Additionally, when the association process with the NF has already been performed, the UPF can receive an association update request from the NF, including information about the NF set to be modified, and send an association update response to the association update request to the NF, thereby receiving the information about the NF set to be modified.

[0106] In an embodiment, the indication information used to indicate a change in the NF set may include the NF set ID. Furthermore, NF set-related information may also include a timer value for operating the NF with the changed NF set.

[0107] In the embodiments, NF may include SMF, AMF, etc.

[0108] In operation 720, the UPF can modify the profile of an NF based on the received NF set information. The UPF can obtain NF set information from an NF and store the obtained NF set information as information for the corresponding NF. For example, the NF set ID can be obtained and stored. The UPF can store and use the obtained information on a per-NF basis (i.e., per-NF instance) or on a per-N4 (PFCP) basis currently being processed.

[0109] In operation 730, the UPF can perform NF-related operations based on the modified profile. In embodiments, the UPF can perform operations such as session processing, notification, or fault recovery. Furthermore, when NF set-related information includes timer values ​​for operating NFs with modified NF sets, the UPF can start a timer based on the timer values, and when the timer expires, it can perform NF-related operations.

[0110] Figure 8 This is a flowchart of the operation of NF according to an embodiment of the present disclosure.

[0111] refer to Figure 8 In operation 810, an NF can be changed to a new NF set. In an embodiment, the NF set information can be changed according to configuration or instructions from OAM.

[0112] In operation 820, the NF can send information related to the NF set to be modified through an association process with the UPF. In an embodiment, the NF can send an association request including information related to the NF set to be modified to the UPF, and send an association response to the association request from the UPF, thereby sending the information related to the NF set to be modified. Alternatively, the NF can receive an association request from the UPF and send an association response to the association request including information related to the NF set to be modified to the UPF, thereby sending the information related to the NF set to be modified. Furthermore, when an association process with the UPF has been performed, the NF can send an association update request including information related to the NF set to be modified to the UPF, and receive an association update response to the association update request from the UPF, thereby sending the information related to the NF set to be modified.

[0113] In an embodiment, the indication information used to indicate a change in the NF set may include the NF set ID. Furthermore, NF set-related information may also include a timer value for operating the NF with the changed NF set.

[0114] In operation 830, the NF can perform UPF-related operations based on the modified profile. In an embodiment, the NF can perform operations such as session processing, notification, or fault recovery.

[0115] Figure 9This is a diagram illustrating the configuration of a network entity according to an embodiment of the present disclosure.

[0116] like Figure 9 As shown, the network entity in this disclosure may include a transceiver 910, a memory 920, and a processor 930. The processor 930, transceiver 910, and memory 920 of the network entity can operate according to the communication method described above. However, the components of the network entity are not limited thereto. For example, the network entity may include more or fewer elements than described above. Furthermore, the processor 930, transceiver 910, and memory 920 may be implemented in the form of a chip. The processor 930 may include at least one processor.

[0117] In this embodiment, the network entity may include a reference. Figure 1 The descriptions include AMF 131, UPF 133, NSSF 134, AUSF 151, NEF 152, PCF 154, UDM 155, AF 156, SCP 157, etc. However, these are just examples, and network entities can include a wide variety of entities.

[0118] Transceiver 910 is a collective term for network entity receivers and network entity transmitters, capable of transmitting signals to or receiving signals from the RAN. Signals transmitted to and received from the RAN can include control information and data. For this purpose, transceiver 910 may include an RF transmitter for up-converting the frequency of the signal to be transmitted and amplifying the signal, and an RF receiver for low-noise amplification of the received signal and down-converting the frequency of the received signal. This is merely an example, and the components of transceiver 910 are not limited to RF transmitters and RF receivers.

[0119] In addition, transceiver 910 can receive signals on a wireless channel and output signals to processor 930, or transmit signals output from processor 930 on a radio channel.

[0120] The memory 920 can store programs and data required for the operation of the network entity. Furthermore, the memory 920 can store control information or data included in signals received by the network entity. The memory 920 may include storage media such as read-only memory (ROM), random access memory (RAM), hard disk, optical disc ROM (CD-ROM), and digital versatile disc (DVD), or a combination of storage media.

[0121] According to embodiments of this disclosure, processor 930 can control a series of processes of a network entity to be operated. For example, processor 930 can receive control signals and data signals through transceiver 910, and process the received control signals and data signals. Furthermore, processor 930 can transmit the processed control signals and processed data signals through transceiver 910.

[0122] The methods described in the claims or specification according to embodiments of this disclosure can be implemented as hardware, software, or a combination of hardware and software.

[0123] When implemented as software, a computer-readable storage medium may be provided for storing one or more programs (software modules). The one or more programs stored in the computer-readable storage medium are configured to be executable by one or more processors in an electronic device. The one or more programs include instructions to cause the electronic device to perform methods according to embodiments of this disclosure, methods described in the claims or specification of this disclosure.

[0124] Programs (e.g., software modules or software) can be stored in non-volatile memory, including RAM or flash memory, ROM, electrically erasable programmable read-only memory (EEPROM), disk storage devices, CD-ROMs, DVDs, other optical storage devices, or magnetic tape. Optionally, one or more programs can be stored in memory provided by a combination of all or some of these devices. Furthermore, each memory can include multiple configured memories.

[0125] Furthermore, the program can be stored in an attachable storage device, which can be accessed via any or a combination of communication networks such as the Internet, intranet, local area network (LAN), wide area network (WAN), and storage area network (SAN). These storage devices can be connected to the device executing embodiments of this disclosure via external ports. Additionally, a separate memory on the communication network can access the device executing embodiments of this disclosure.

[0126] In the specific embodiments described above, components included in this disclosure are represented in a singular or plural form according to the specific embodiments presented in this disclosure. However, for ease of explanation, the singular or plural forms are appropriately chosen as suggested, and this disclosure is not intended to be limited to a single or plural element. Even when an element is represented in a plural form, it may be provided as a single element, and even when an element is represented in a singular form, it may be provided as a plurality of elements.

[0127] Although specific embodiments have been described in the detailed description of this disclosure, various modifications may be made without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the embodiments described above, but should be determined by the appended claims and their equivalents.

[0128] According to embodiments of this disclosure, the reliability of wireless communication systems can be improved.

[0129] Although this disclosure has been described with reference to various embodiments, those skilled in the art can suggest various changes and modifications. This disclosure includes such changes and modifications that fall within the scope of the appended claims.

Claims

1. A method for a user plane function (UPF) in a wireless communication system, the method comprising: Send a Packet Forwarding Control Protocol (PFCP) association establishment request to the Session Management Function (SMF); Receive a PFCP association establishment response from the SMF, including the SMF set identifier ID corresponding to the PFCP association establishment request; as well as To perform operations related to requests for SMF PFCP sessions based on the SMF set ID.

2. The method according to claim 1, wherein, Sending a PFCP association establishment request to SMF includes: Identify the conditions used to send the PFCP association establishment request, and The conditions include at least one of the following: creation of a UPF, restart of a UPF, change of configuration related to an SMF, and release of an existing PFCP association.

3. The method according to claim 1, further comprising: Send a PFCP association update request to the SMF; as well as Receive the PFCP association update response corresponding to the PFCP association update request from the SMF.

4. The method according to claim 1, further comprising: Receive a PFCP association update request from the SMF, including the changed SMF set ID; as well as Send the PFCP association update response corresponding to the PFCP association update request to the SMF.

5. The method according to claim 1, further comprising: Before receiving the PFCP association establishment response Receive a PFCP association release request from the SMF to release the existing PFCP association with the SMF; as well as Send a PFCP associated release response to SMF.

6. The method according to claim 1, further comprising: Select SMF instances included in the SMF set based on the SMF set ID.

7. The method according to claim 1, wherein, The SMF set corresponding to the SMF set ID is selected based on at least one of slice information or data network name.

8. A user plane function (UPF) in a wireless communication system, the UPF comprising: transceiver; Memory; and A processor, operatively connected to the transceiver and the memory, is configured to: Send a Packet Forwarding Control Protocol (PFCP) association establishment request to the Session Management Function (SMF). Receive from SMF a PFCP association establishment response including the SMF set identifier ID corresponding to the PFCP association establishment request, and To perform operations related to requests for SMF PFCP sessions based on the SMF set ID.

9. The UPF according to claim 8, wherein, The processor is also configured to: Identify the conditions used to send the PFCP association establishment request, and The conditions include at least one of the following: creation of a UPF, restart of a UPF, change of configuration related to an SMF, and release of an existing PFCP association.

10. The UPF according to claim 8, wherein, The transceiver is also configured to: Send a PFCP association update request to the SMF, and Receive the PFCP association update response corresponding to the PFCP association update request from the SMF.

11. The UPF according to claim 8, wherein, The transceiver is also configured to: Receive PFCP association update requests from SMF, including the changed SMF set ID, and Send the PFCP association update response corresponding to the PFCP association update request to the SMF.

12. The UPF according to claim 8, wherein, The processor is also configured to: Before receiving the PFCP association establishment response Receive a PFCP association release request from the SMF to release the existing PFCP association with the SMF, and Send a PFCP associated release response to SMF.

13. The UPF according to claim 8, wherein, The processor is also configured to: Select SMF instances included in the SMF set based on the SMF set ID.

14. The UPF according to claim 8, wherein, The SMF set corresponding to the SMF set ID is selected based on at least one of slice information or data network name.

Images