Apparatus and method for supporting upf event exposure service in wireless communication system

Abstract

The disclosure relates to a fifth-generation (5G) communication system or a pre-5G communication system for supporting a higher data transmission rate than a fourth-generation (4G) system such as long term evolution (LTE). According to various embodiments, there is provided an operation method of an application function (AF) in a wireless communication system, the method including transmitting, to a network exposure function (NEF), an Nnef_EventExposure_Subscribe message including a user equipment (UE) address to request subscription to a user plane function (UPF) event exposure service of the UE, and receiving, from the NEF, an Nnef_EventExposure_Notify message including information about the UPF event exposure service of the UE.

Description

TECHNICAL FIELD

[0001] The disclosure relates generally to a wireless communication system, and more particularly, to an apparatus and method for supporting a UPF event exposure service in a wireless communication system. BACKGROUND

[0002] To meet the demand for wireless data traffic having increased since deployment of 4G communication systems, efforts have been made to develop an improved 5G or pre-5G communication system. The 5G or pre-5G communication system is also called a 'beyond 4G network' or a 'post LTE system'.

[0003] The 5G communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 60GHz bands, so as to accomplish higher data rates. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques are discussed in 5G communication systems.

[0004] In addition, the developments for system network improvement are under way based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, a device-to-device (D2D) communication, wireless backhaul, moving networks, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancellation and the like in 5G communication systems.

[0005] In the 5G system, hybrid FSK and FQAM modulation and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), a non-orthogonal multiple access (NOMA), and a sparse code multiple access (SCMA) as an advanced access technology have also been developed.

[0006] The above information is presented as background information only to assist with an understanding of the disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the disclosure. SUMMARY

[0007] [TECHNICAL SOLUTION]

[0008] Based on the above discussion, the disclosure provides an apparatus and method for supporting a UPF event exposure service in a wireless communication system.

[0009] According to various embodiments, an operation method for an application function (AF) in a wireless communication system is provided. The method includes: sending an Nnef_EventExposure_Subscribe message including a user equipment (UE) address to a network open function (NEF) to request subscription to the UE's User Plane Function (UPF) event open service; and receiving an Nnef_EventExposure_Notify message from the NEF including information related to the UE's UPF event open service.

[0010] According to various embodiments, an operation method for a Network Open Function (NEF) in a wireless communication system is provided. The method includes: receiving an Nnef_EventExposure_Subscribe message from an Application Function (AF) requesting subscription to a User Plane Function (UPF) event open service for a User Equipment (UE), including the address of the User Equipment (UE); and sending an Nnef_EventExposure_Notify message to the AF including information related to the UE's UPF event open service.

[0011] According to various embodiments, an apparatus for application function (AF) in a wireless communication system is provided. The apparatus includes: a transceiver; and at least one processor operatively coupled to the transceiver and configured to: send an Nnef_EventExposure_Subscribe message including a user equipment (UE) address to a Network Open Function (NEF) to request subscription to the UE's User Plane Function (UPF) event open service; and receive an Nnef_EventExposure_Notify message from the NEF including information relating to the UE's UPF event open service.

[0012] Various embodiments provide apparatus and methods for supporting UPF event open services in wireless communication systems.

[0013] The beneficial effects that can be obtained from this disclosure may not be limited to the effects described above, and other effects not mentioned can be clearly understood by those skilled in the art to which this disclosure pertains through the following description.

[0014] Before proceeding with the following detailed description, it may be advantageous to define certain words and phrases used throughout the patent document. The terms “include” and “comprise” and their derivatives mean non-restrictive inclusion; the term “or” is inclusive, meaning and / or; the phrases “associated with,” “associated with,” and their derivatives can mean including, contained within, interconnected with, including, included in, connected to or linked with, coupled to or connected with, communicates with, collaborates with, intertwined, parallel, proximate, bound to or bound with, having, possessing the characteristics of, etc.; the term “controller” means any device, system, or part thereof that controls at least one operation, which may be implemented in hardware, software, or firmware, or at least some combination of both. It should be noted that the functionality associated with any particular controller, whether local or remote, can be centralized or distributed.

[0015] 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 implemented in a computer-readable medium. The terms "application program" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, examples, associated data, or portions thereof, implemented in suitable 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 media accessible 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 excludes wired, wireless, optical, or other communication links that transmit transient electrical signals or other transient signals. Non-transitory computer-readable media includes media capable of permanently storing data, as well as media capable of storing data and subsequently rewriting it, such as rewritable optical discs or erasable storage devices.

[0016] Throughout the patent document, definitions of certain words and phrases are provided, and those skilled in the art will understand that, in many (if not most) examples, such definitions apply to the prior and future use of the words and phrases defined in this way. Attached Figure Description

[0017] 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:

[0018] Figure 1 The structure of a 5G network wireless communication system according to various embodiments is shown;

[0019] Figure 2 The configuration of network entities in a wireless communication system according to various embodiments is shown;

[0020] Figure 3 The process of using UPF events to open services in an external AF or internal NF (including AF) in a wireless communication system is illustrated according to various embodiments.

[0021] Figure 4 The process of registering the UE IP address (IPv4 or IPv6), UE MAC address, and the UPF responsible for the PDU session in the UDM during the PDU session establishment process in a wireless communication system, according to various embodiments, is illustrated.

[0022] Figure 5 The process of updating the (PSA) UPF ID and UE IP address in the UDM when relocating the PSA UPF in a wireless communication system is illustrated according to various embodiments;

[0023] Figure 6 The process of subscribing to UPF event open services using PCF or BSF in an external AF or internal NF (including AF) in a wireless communication system according to various embodiments is illustrated.

[0024] Figure 7 The process of storing UPF IDs in the PCF and BSF of a wireless communication system to retrieve UPFs, according to various embodiments, is illustrated; and

[0025] Figure 8 The process of updating the (PSA) UPF ID in the PCF and BSF when relocating the PSA UPF in a wireless communication system is illustrated according to various embodiments. Detailed Implementation

[0026] The following discussion Figures 1 to 8 The various embodiments described in this patent document to illustrate the principles of this disclosure are for illustrative purposes only 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 suitable system or apparatus.

[0027] The terminology used in this disclosure is for descriptive purposes only and is not intended to limit the scope of the disclosure. Singular expressions may include plural expressions unless defined differently in the context. Unless otherwise specified, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. Unless clearly defined in this disclosure, the meaning of such terms, such as those defined in a general dictionary, may be interpreted as equivalent to their meaning in the context of the relevant field, and not as having an idealized or overly formal meaning. In some cases, even terms defined in this disclosure should not be construed as excluding embodiments of this disclosure.

[0028] In the following description, embodiments of the present disclosure will be based on hardware methods. However, embodiments of the present disclosure include techniques using both hardware and software, and therefore, software aspects are not excluded from embodiments of the present disclosure.

[0029] Furthermore, in this disclosure, terms used in some communication standards (e.g., the 3rd Generation Partnership Project (3GPP)) will be used to describe various embodiments; however, these terms are used only for ease of description. The embodiments of this disclosure can be modified and adapted to other communication systems.

[0030] Various embodiments relate to methods and apparatus for supporting User Plane Function (UPF) event open services in wireless communication systems.

[0031] Various implementations provide a method for a network function (NF) or external application function (AF) in a 5G core (5GC) to use a service-based interface (SBI) to access the event opening service of a user plane function.

[0032] With the development of mobile communication systems, various services can be provided, thus creating a particular need for an effective method of using non-public networks (NPNs).

[0033] This disclosure proposes a method for subscribing to a UPF event open service to use the UPF event open service inside / outside a network. To this end, a network function (NF) inside / outside the network requests a service subscription from the UPF via a User Data Management (UDM) or Session Management Function (SMF). A method for discovering the UPF is also proposed here, which stores the UE Internet Protocol (IP) address or UE Media Access Control (MAC) address and the UPF identifier (ID) in the UDM.

[0034] Figure 1 The structure of a 5G network wireless communication system according to various embodiments is shown. The network entities or network nodes included in the 5G network wireless communication system are described below.

[0035] An access network (AN) (or equivalently, a radio access network (RAN)) is an entity that performs radio resource allocation for terminals and can be at least one of an evolved Node B (eNode B), a Node B, a base station (BS), a next-generation radio access network (NG-RAN), a 5G access network (5G-AN), a radio access unit or radio unit (RU), a base station controller, or a node on a network. Terminals can include user equipment (UE) capable of performing communication functions, next-generation UE (NG UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system. Although the embodiments disclosed herein are described below with reference to a 5G system as an example, these embodiments can be applied to other communication systems with similar technical backgrounds. Furthermore, as will be determined by those skilled in the art, the embodiments disclosed herein can be applied to other communication systems with modifications without significantly departing from the scope of this disclosure.

[0036] As wireless communication systems evolve from 4G to 5G, new core networks, such as Next Generation (NG) cores or 5G cores (5GC), have been defined. These new core networks virtualize all existing network entities (NEs) into network functions (NFs). Depending on the implementation, a network function can refer to a network entity, network component, or network resource.

[0037] According to the implementation method, 5GC may include Figure 1 The NF shown is not limited to 5GC. Figure 1 Examples, and can include more than Figure 1 The number of NFs shown is either greater or less.

[0038] According to the implementation method, the Access and Mobility Management Function (AMF) can be a network function that manages terminal mobility.

[0039] According to the implementation method, the Session Management Function (SMF) can be a network function that manages the Packet Data Network (PDN) connection provided to the terminal. The PDN connection can be referred to as a PDU session.

[0040] According to the implementation method, the policy control function (PCF) can be a network function that applies the mobile network operator's service policies, billing policies, and policies for PDU sessions on the terminal.

[0041] According to the implementation method, unified data management (UDM) can be a network function that stores information about subscribers.

[0042] According to the implementation, the Network Open Function (NEF) can be a function that provides information about the terminal to a server outside the 5G network. Additionally, the NEF can provide the information required to provide services to the 5G network and store that information in a Unified Data Repository (UDR).

[0043] According to the implementation, the User Plane Function (UPF) can be a function that acts as a gateway to send user data (Protocol Data Units or "PDUs") to a Data Network (DN). In particular, in this disclosure, a Nupf (which is a Service-Based Interface (SBI)) is defined, and the UPF can provide event open services to another NF through the SBI.

[0044] According to the implementation, the Network Repository Function (NRF) can perform the function of discovering NFs.

[0045] According to the implementation method, the Authentication Server Function (AUSF) can perform terminal authentication in 3GPP access networks and non-3GPP (non-3GPP) access networks.

[0046] According to the implementation method, the Network Slice Selection Function (NSSF) can perform the function of selecting network slice instances provided to the terminal.

[0047] According to the implementation method, a data network (DN) can be a data network through which terminals send and receive data to use network operator services or third-party services.

[0048] Figure 2 The configuration of network entities in a wireless communication system according to various embodiments is shown.

[0049] The network entities disclosed herein are concepts that include network functions implemented according to the system. As used herein, the term "unit," terms ending with "-device," etc., refer to a unit used for processing and / or controlling at least one function or operation, which may be implemented in hardware, software, or a combination of hardware and software.

[0050] According to various embodiments, the network entity 200 may include a communication unit 210, a storage unit 220, and a controller 230 for controlling the overall operation of the network entity 200.

[0051] Communication unit 210 transmits signals to other network entities and receives signals from other network entities. Communication unit 210 in whole or in part may be referred to as transmitter 211, receiver 213, or transceiver unit / transceiver 210.

[0052] Storage unit 220 stores data used for the operation of network entity 200, such as basic programs, application programs, and configuration information. Storage unit 220 may include volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. Storage unit 220 provides the stored data according to requests from controller 230.

[0053] Controller 230 controls the overall operation of network entity 200. For example, controller 230 sends and receives signals via communication unit 210. Controller 230 writes and reads data from storage unit 220. Controller 230 can perform the functions of the protocol stack required by the communication standard. For this purpose, controller 230 may include circuitry, dedicated circuitry, at least one processor or microprocessor, or may be part of a processor. Communication unit 210 and part of controller 230 may be referred to as a communication processor (CP). According to various embodiments, controller 230 can control network entity 200 to perform any operation.

[0054] The communication unit 210 and the controller 230 do not need to be configured as separate modules, but can be configured as a single component such as a single chip or software block. The communication unit 210, the storage unit 220, and the controller 230 can be electrically connected. The operation of the network entity 200 can be achieved by including the storage unit 220 in the network entity 200 to store the corresponding program code.

[0055] Network entity 200 includes network nodes and can be any of the following: base station (RAN), AMF, SMF, UPF, NF, NEF, NRF, CF, NSSF, UDM, AF, AUSF, SCP, UDSF, context store, OAM, EMS configuration server, identifier (ID) management server, and user equipment (UE).

[0056] Figure 3 The process of using UPF event to open services in an external AF or internal NF (including AF) in a wireless communication system is illustrated according to various embodiments.

[0057] In operation 301, AF / NF 311 sends an Nnef_EventExposure_Subscribe / Unsubscribe request message to NEF 312 to subscribe to or unsubscribe from at least one UPF event exposure service identified by the AF event ID. To unsubscribe, AF / NF 311 also needs to send a subscription-related ID to identify the existing event service subscription. The subscription request message needs to include the following parameters. When AF / NF 311 is an internal NF, AF / NF 311 does not need to send this message to NEF 312, and therefore sends a subscription or unsubscribe request message to UDM 314 in operation 302, including the following parameters:

[0058] (1) Event ID: The ID used to identify the event open service to which the subscription is made;

[0059] (2) Objectives of the event report: The objective of the event to be observed;

[0060] (2-1) One of the terminal IDs, such as the General Public Subscription Identifier (GPSI) or the External Group Identifier (when the target to be observed is a terminal).

[0061] (2-2) One of the terminal IDs, such as GPSI, Subscription Permanent Identifier (SUPI), or Internal Group Identifier (when the target to be observed is an internal NF).

[0062] (2-3) Any combination of information used to specify a particular service data flow, such as UE IP address (IPv4 address or IPv6 prefix), UE MAC address, AF service identifier, or combination of Data Network Name (DNN) / Single Network Slice Selection Auxiliary Information (S-NSSAI) (when the target to be observed is a particular service data flow (SDF) or packet flow).

[0063] (3) Event reporting information: Define information related to event reporting, such as whether event reporting is performed periodically, the maximum number of times event reporting is performed, and until when event reporting is performed;

[0064] (4) Notification Target Address (+Notification Related ID): Defines the address of the NF that receives the notification when the event occurs and the subscription related ID. If the AF / NF sends a subscription request on behalf of another NF that receives the event, the AF / NF needs to send the address of the NF receiving the event and the address of the AF / NF together to change the subscription information;

[0065] (5) Event Filter Information: Defines the event parameter type and event parameter value, which defines the conditions and values ​​for notification subscription events. For example, the event parameter type can be "Region of Interest," and the event parameter value can be a list of Tracking Regions (TAs); and / or

[0066] (6) Expiry time: Defines the duration of the subscription.

[0067] AF / NF 311 specifies its address as the notification target address and also specifies values ​​in the target of the event report to identify the packet flow, such as UE IP address / IPv4 prefix, UE MAC address, AF service identifier or DNN / S-NSSAI combination, and GPSI / SUPI or external group identifier / internal group identifier, to open the service to the UPF subscription event through which the specific SDF or packet flow passes.

[0068] In operation 302, NEF 312 sends a Nudm_EventExposure_Subscribe / Unsubscribe request message to UDM 314 regarding service subscription or unsubscription requests, in order to open the service to subscribe or unsubscribe events of a specific SDF or packet stream passing through the UPF. To unsubscribe, NEF 312 also needs to send a subscription-related ID to identify the existing event service subscription. When NEF 312 receives the AF service identifier as the target value for event reporting, NEF 312 changes the AF service identifier to a DNN / S-NSSAI combination. NEF 312 sends the information received from AF 311 in operation 301 along with information about the notification target address, with the NEF 312 address added. Adding the NEF 312 address to the notification target address is for NEF 312 to receive notifications of subscription information changes when such changes occur in UDM 314. When a subscription to a service is authorized by UDM 314, UDM 314 stores the identity of the event trigger and the requester.

[0069] UDM 314 converts the GPSI or External Group Identifier received from NEF 312 into SUPI or a SUPI list, which is a terminal ID that can be used within the network. UDM 314 can perform two methods to subscribe to the event open service regarding the appropriate UPF 316. The first method is to find the appropriate UPF 316 and subscribe to the service directly, and the second method is to subscribe to the UPF service by managing the SMF 315 of the appropriate UPF 316.

[0070] Operations 303a and 303b involve methods for UDM 314 to immediately locate a suitable UPF 316 and directly subscribe to the UPF event exposure service. In operation 303a, UDM 314 sends a Nupf_EventExposure_Subscribe / Unsubscribe request message to UPF 316 regarding a service subscription or unsubscription request, in order to subscribe to or unsubscribe from the event exposure service on a specific SDF or UPF 316 through which a packet flow passes. To unsubscribe, UDM 314 also needs to send a subscription-related ID to identify the existing event service subscription. When multiple UEs, or even a single UE, receive event exposure service subscription requests for multiple packet flows, UDM 314 needs to send service subscription requests to all corresponding UPFs. UDM 314 sends the information received from NEF 312 in operation 302, along with a notification target address with UDM 314's address added. This notification target address is used by UDM 314 to receive notifications of subscription information changes when changes occur in the UPF 316. When a subscription to a service is authorized by UPF 316, UPF 316 stores the event trigger and the identity of the requester. In Operation 303b, UPF 316 sends a Nupf_EventExposure_Subscribe / Unsubscribe response message to UDM 314 in response to subscription or unsubscription to the service. This message may include the subscription-related ID and the expiration time.

[0071] Operations 303c through 303f involve a method by which UDM 314 subscribes to the UPF event exposure service by managing the SMF 315 of the appropriate UPF 316. In operation 303c, UDM 314 sends an Nnef_EventExposure_Subscribe / Unsubscribe request message to the SMF 315 regarding a service subscription or unsubscription request, in order to subscribe to or unsubscribe from the UPF event exposure service on a specific SDF or UPF 316 through which a packet flow passes. To unsubscribe, UDM 314 also needs to send a subscription-related ID to identify the existing event service subscription. When multiple UEs, or even a single UE, receive event exposure service subscription requests for multiple packet flows, UDM 314 needs to send the service subscription request to all the corresponding SMFs. In operation 302, UDM 314 sends information received from NEF 312 along with a notification target address that includes UDM 314's address, which is used by UDM 314 to receive notifications of subscription information changes when such changes occur in the SMF 315. When a subscription service is authorized by SMF 315, SMF 315 stores the event trigger and the identity of the requester.

[0072] In Operation 303d, the SMF 315 sends a Nupf_EventExposure_Subscribe / Unsubscribe request message to the UPF 316 regarding service subscription or unsubscription requests, in order to subscribe to or unsubscribe from the UPF event exposure service for a specific SDF or UPF 316 through which a packet flow passes. To unsubscribe, the SMF 315 also needs to send a subscription-related ID to identify the existing event service subscription. When multiple UEs, or even a single UE, receive event exposure service subscription requests for multiple packet flows, the SMF 315 needs to send service subscription requests to all corresponding UPFs managed by the SMF 315. The SMF 315 sends the information received from the UDM 314 in Operation 303c, along with a notification target address with the SMF 315 address appended. This notification target address is used by the SMF 315 to receive notifications of subscription changes when changes occur in the UPF 316. When the UPF 316 authorizes a subscription service, it stores the identity of the event trigger and the requester. In Operation 303e, UPF 316 sends a Nupf_EventExposure_Subscribe / Unsubscribe response message to SMF 315 in response to subscription or unsubscription to a service. This message may include the subscription-related ID and the expiration time.

[0073] In operation 303f, SMF 315, in response to subscribing to or unsubscribing from a service, sends an Nsmf_EventExposure_Subscribe / Unsubscribe response message to UDM 314. This message may include the subscription-related ID and the expiration time.

[0074] In operation 304, UDM 314, in response to subscribing to or unsubscribing from the service, sends a Nudm_EventExposure_Subscribe / Unsubscribe response message to NEF 312. This message may include the subscription-related ID and the expiration time.

[0075] In operation 305, NEF 312 sends an Nnef_EventExposure_Subscribe / Unsubscribe response message to AF 311 in response to subscribing to or unsubscribing from a service. This message may include the subscription-related ID and the expiration time.

[0076] In operations 306a / 306b, after an event is detected, the UPF 316 sends an event report along with a timestamp to the NEF 312 via the Nupf_EventExposure_Notify message to notify that an event has occurred. The NEF 312 can use the Nudr_DM_Create or Nudr_DM_Update messages to store the timestamped event report information in the UDR 313.

[0077] In operation 307, NEF 312 sends an Nnef_EventExposure_Notify message to AF 311, which includes information about the received event reports. When an internal NF subscribes to the UPF event exposure service, this notification is forwarded directly to the NF without going through NEF 312.

[0078] In operation 308a / 308b, when subscription information changes, UPF 316 can notify UDM 314 or SMF 315 of the change in subscription information along with the subscription-related ID via the Nupf_EventExposure_Notify message.

[0079] Figure 4 The process of registering the UE IP address (IPv4 or IPv6), UE MAC address, and the UPF responsible for the PDU session in the UDM during the PDU session establishment process in a wireless communication system, according to various embodiments, is illustrated.

[0080] In operations 401 to 416b, UE 431 requests the network to generate a PDU session in order to create a new PDU session and switch the existing PDU session.

[0081] In operation 401, UE 431 sends a PDU session establishment request message to AMF 433. AMF 433 and SMF 435 process the PDU session establishment request.

[0082] In operation 403, in order to generate a PDU session, AMF 433 selects the appropriate SMF 435 and sends an Nsmf_PDUSession_CreateSMContext request message to SMF 435.

[0083] In operation 404, SMF 435 obtains session management subscription data related to PDU session generation from UDM 437. That is, SMF 435 and UDM 437 perform subscription retrieval / update.

[0084] In operation 405, SMF 435 sends an Nsmf_PDUSession_CreateSMContext response message to AMF 433.

[0085] In Operation 406, perform PDU session authentication / authorization.

[0086] Subsequently, SMF 435 selects PCF 436 and obtains the default PCC rule for the PDU session.

[0087] In operation 407a, SMF 435 selects PCF 436.

[0088] In operation 407b, perform SM policy association establishment / SM policy association modification initiated by SMF.

[0089] SMF 435 selects the appropriate UPF 434 for the PDU session and generates an N4 session with the UPF 434.

[0090] In operation 408, SMF 435 selects UPF 434.

[0091] In operation 409, the SM policy association modification initiated by SMF is executed.

[0092] In operation 410a, SMF 435 sends an N4 session establishment / modification request message to UPF 434.

[0093] In operation 410b, UPF 434 sends an N4 session establishment / modification response message to SMF 435.

[0094] In order to generate a GTP-U tunnel for user data transmission between (R)AN 432 (e.g., NG-RAN) and UPF 434, (R)AN 432 and UPF 434 exchange separate CN tunnel information via SMF 435.

[0095] In operation 411, SMF 435 and AMF 433 exchange Namf_Communication_N1N2MessageTrasfer messages.

[0096] In addition, SMF 435 and AMF 433 notify UE 431 that a PDU session has been successfully generated by using a PDU session establishment accept message, and forward the UE IP address (IPv4 or IPv6) or UE MAC address assigned to the PDU session.

[0097] In operation 412, AMF 433 sends a NAS message to (R)AN 432 that includes an N2 PDU session request.

[0098] In operation 413, (R)AN 432 and UE 431 exchange PDU session establishment accept messages, including AN-specific resource establishment.

[0099] In operation 414a, (R)AN 432 sends an N2 PDU session response message to AMF 433.

[0100] In operation 414b, UE 431 sends the first uplink data to UPF 434.

[0101] In operation 415, AMF 433 sends an Nsmf_PDUSession_UpdateSMContext request message to SMF 415.

[0102] In operation 416a, SMF 435 sends an N4 session modification request message to UPF 434.

[0103] In operation 416b, UPF 434 sends an N4 session modification response message to SMF 435.

[0104] In operation 416c, the SMF 435 registers a PDU session with the UDM 437 via the Nudm_UECM_Registration operation. Here, the SMF sends the SUPI, DNN, S-NSSAI, PDU session ID, and SMF identifier, and also sends the UE IP address (IPv4 or IPv6), UE MAC address, and UPF identifier. The UDM 437 stores the following information for the PDU session: SUPI, SMF identifier, DNN, S-NSSAI, PDU session ID, UE IP address (IPv4 / IPv6), UE MAC address, and UPF identifier. The UDM 437 can use the Nudr_DM_Update operation to store the following information in the UDR: SUPI, UE context from subscription data, and SMF data.

[0105] The following information about the UE context from the SMF data, as listed in Table 1, is stored in UDM 437.

[0106] [Table 1]

[0107]

[0108] In operation 416d, UPF 434 sends the first downlink data to UE 431.

[0109] In operation 417, SMF 435 sends an Nsmf_PDUSession_UpdateSMContext response message to AMF 433.

[0110] In operation 418, SMF 435 sends an Nsmf_PDUSession_SMContextStatusNotify message to AMF 433.

[0111] In Operation 419, SMF 435 establishes an IPv6 address.

[0112] In operation 420, the SM policy association modification initiated by SMF is executed.

[0113] In operation 421, the subscription is canceled.

[0114] Figure 5 The process of updating the (PSA) UPF ID and UE IP address in the UDM when relocating the PSA UPF in a wireless communication system is illustrated according to various embodiments.

[0115] In Operation 501, relocate the PDU Session Anchor (PSA) User Plane Function (UPF).

[0116] In operation 502, SMF 511 sends a Nudm_UECM_Update request message to UDM 512 to update the UE context in the SMF data after PSA UPF relocation. Parameters in the Nudm_UECM_Update request message may include at least one of NFID, SUPI, and NF type. Specifically, the (PSA) UPF ID and UE IP address that changed due to the PSA UPF relocation are added and sent. Therefore, UDM 512 can store the UPF ID and UE IP address that changed due to the PSA UPF relocation.

[0117] In operation 503, UDM 512 sends a Nudm_UECM_Update response message to SMF 511.

[0118] Figure 6 The process of subscribing to UPF event open services using PCF or BSF in an external AF or internal NF (including AF) in a wireless communication system is illustrated according to various embodiments.

[0119] In addition to using Policy Control Function (PCF) or Binding Support Function (BSF) instead of UDM to retrieve UPF, Figure 6 The implementation methods shown are the same as Figure 3 The implementation method shown is the same.

[0120] In operation 601, AF / NF 611 sends an Nnef_EventExposure_Subscribe / Unsubscribe request message to NEF 612 to subscribe to or unsubscribe from at least one UPF event exposure service identified by an AF event ID. To unsubscribe, AF / NF 611 also needs to send a subscription-related ID to identify an existing event service subscription. The subscription request message needs to include the following parameters:

[0121] (1) Event ID: The ID used to identify the event open service to which the subscription is made;

[0122] (2) Objectives of the event report: The objective of the event to be observed;

[0123] (2-1) One of the terminal IDs, such as the General Public Subscription Identifier (GPSI) or the External Group Identifier (when the target to be observed is a terminal).

[0124] (2-2) One of the terminal IDs, such as GPSI, Subscription Permanent Identifier (SUPI), or Internal Group Identifier (when the target to be observed is an internal NF).

[0125] (2-3) Any combination of information used to specify a particular service data flow, such as UE IP address (IPv4 address or IPv6 prefix), UE MAC address, AF service identifier, or combination of Data Network Name (DNN) / Single Network Slice Selection Auxiliary Information (S-NSSAI) (when the target to be observed is a particular service data flow (SDF) or packet flow).

[0126] (3) Event reporting information: Define information related to event reporting, such as whether event reporting is performed periodically, the maximum number of times event reporting is performed, and until when event reporting is performed;

[0127] (4) Notification Target Address (+Notification Related ID): Defines the address of the NF that receives the notification when the event occurs and the subscription related ID. If the AF / NF sends a subscription request on behalf of another NF that receives the event, the AF / NF needs to send the address of the NF receiving the event and the address of the AF / NF together to change the subscription information;

[0128] (5) Event Filter Information: Defines the event parameter type and event parameter value, which defines the conditions and values ​​for notification subscription events. For example, the event parameter type can be "Region of Interest," and the event parameter value can be a list of Tracking Regions (TAs); and / or

[0129] (6) Expiry time: Defines the duration of the subscription.

[0130] When AF / NF 611 is an internal NF, AF / NF 611 does not need to send this message to NEF, and therefore sends a subscription or unsubscribe request message including the previous parameters to PCF / BSF 614 in operation 602a / 602b.

[0131] AF / NF 611 specifies its address as the notification target address and also specifies values ​​in the target of the event report to identify the packet flow, such as UE IP address / IPv4 prefix, UE MAC address, AF service identifier or DNN / S-NSSAI combination, and GPSI / SUPI or external group identifier / internal group identifier, to open the service to the UPF subscription event through which the specific SDF or packet flow passes.

[0132] In operations 602a / 602b, NEF 612 sends an Npcf_EventExposure_Subscribe / Unsubscribe request message or an Nbsf_EventExposure_Subscribe / Unsubscribe request message to PCF / BSF 614 regarding service subscription or unsubscription requests, in order to open the service to subscribe or unsubscribe events of a specific SDF or packet stream through which the UPF is traversed. To unsubscribe, NEF 612 also needs to send a subscription-related ID to identify the existing event service subscription. When NEF 612 receives the AF service identifier as the target value for event reporting, NEF 612 changes the AF service identifier to a DNN / S-NSSAI combination. NEF 612 sends the information received from AF 611 in operation 601 and information to the notification target address with the NEF 612 address added. Adding the NEF 612 address to the notification target address is for NEF 612 to receive notification of subscription information changes when changes occur in PCF / BSF 614. When a subscription service is authorized by PCF / BSF 614, PCF / BSF 614 stores the event trigger and the identity of the requester.

[0133] The PCF / BSF 614 converts the GPSI or External Group Identifier received from the NEF 612 into a SUPI or a SUPI list, which is a terminal ID that can be used within the network. The PCF / BSF 614 can perform two methods to subscribe to event open services regarding the appropriate UPF 615. The first method is to find the appropriate UPF 615 and subscribe to the service directly; the second method is to subscribe to the UPF service through the SMF that manages the appropriate UPF 615. The method of subscribing to the UPF service through the SMF is similar to... Figure 3 The same implementation method is described in the previous implementation method, so its description is omitted in this implementation method.

[0134] In operation 603, PCF / BSF 614 sends a Nupf_EventExposure_Subscribe / Unsubscribe request message to UPF 615 regarding service subscription or unsubscription requests, in order to subscribe to or unsubscribe from events for a specific SDF or packet flow passing through UPF 615. To unsubscribe, PCF / BSF 614 also needs to send a subscription-related ID to identify the existing event service subscription. When multiple UEs, or even a single UE, receive event-open service subscription requests for multiple packet flows, PCF / BSF 614 needs to send service subscription requests to all corresponding UPFs. PCF / BSF 614 sends the information received from NEF 612 in operations 602a / 602b, along with a notification target address with PCF / BSF 614's address added. This notification target address is used to receive notifications of subscription information changes when changes occur in UPF 615. When a subscription to a service is authorized by UPF 615, UPF 615 stores the event trigger and the identity of the requester. In Operation 604, UPF 615, in response to the subscription or unsubscription of the service, sends a Nupf_EventExposure_Subscribe / Unsubscribe response message to PCF / BSF 614. This message may include the subscription-related ID and the expiration time.

[0135] In Operations 605a / 605b, PCF / BSF 614 sends an Npcf_EventExposure_Subscribe / Unsubscribe response message or an Nbsf_EventExposure_Subscribe / Unsubscribe response message to NEF 612 in response to subscription or unsubscription to a service. This message may include the subscription-related ID and the expiration time.

[0136] In operation 606, NEF 612 sends an Nnef_EventExposure_Subscribe / Unsubscribe response message to AF 611 in response to subscribing to or unsubscribing from a service. This message may include the subscription-related ID and the expiration time.

[0137] In operation 607, after an event is detected, UPF 615 sends an event report along with a timestamp to NEF 612 via the Nupf_EventExposure_Notify message to notify that an event has occurred.

[0138] In operation 608, NEF 612 can use the Nudr_DM_Create or Nudr_DM_Update messages to store information of timestamped event reports in the UDR.

[0139] In operation 609, NEF 612 sends an Nnef_EventExposure_Notify message to AF 611, which includes information about the received event reports. When an internal NF subscribes to the UPF event exposure service, this notification is forwarded directly to the NF without going through NEF 612.

[0140] In operation 610, when subscription information changes, UPF 615 can notify PCF / BSF 614 of the change in subscription information along with the subscription-related ID via the Nupf_EventExposure_Notify message.

[0141] Figure 7 The process of storing UPF IDs in the PCF and BSF of a wireless communication system to retrieve UPFs is illustrated according to various embodiments.

[0142] Figure 7 The implementation shown is performed by the SM policy association modification process initiated by the SMF during the PDU session establishment process.

[0143] In Operation 701, the PDU session establishment process is executed.

[0144] In operation 702, SMF 711 sends an Npcf_SMPolicyControl_Update request message to PCF 712 to update the SM policy association information regarding the generated PDU session. The parameters included in the message in operation 702 may include at least one of the following: SM policy association ID, IPv4 address and / or IP6 network prefix, user location information, UE time zone, serving network, RAT type, session AMBR or default QoS information for subscription, DN authorization profile index, MAC address, port number of the manageable Ethernet port, UE-DS-TT dwell time and port management information container, MA PDU request indication, and MA PDU network upgrade permission indication. Specifically, the ID and address of the (PSA) UPF responsible for the PDU session are added and sent. Therefore, PCF 712 can store the ID and address of the UPF responsible for the generated PDU session.

[0145] In operation 703, PCF 712 sends an Npcf_SMPolicyControl_Update response message to SMF 711.

[0146] In operation 704, the PCF registers information about the PDU session in the BSF 713 via an Nbsf_Management_Register request message. The registration information may include at least one of the following: UE address, SUPI, GPSI, DNN, DN information (e.g., S-NSSAI), PCF address, PCF ID, and PCF set ID. To register UPF information in the BSF 713, the UPF address and ID are also provided. Therefore, the BSF 713 can store the ID and address of the UPF responsible for generating the PDU session.

[0147] In operation 705, BSF 713 sends an Nbsf_Management_Register response message to PCF 712.

[0148] Figure 8 The process of updating the (PSA) UPF ID in the PCF and BSF when relocating the PSA UPF in a wireless communication system is illustrated according to various embodiments.

[0149] In Operation 801, relocate the PSA UPF.

[0150] In operation 802, SMF 811 sends an Npcf_SMPolicyControl_Update request message to PCF 812 to update the SM policy association information for the PDU session after PSA UPF relocation. The parameters in the Npcf_SMPolicyControl_Update request message may include at least one of the following: SM policy association ID, IPv4 address and / or IP6 network prefix, user location information, UE time zone, serving network, RAT type, session AMBR or default QoS information for subscription, DN authorization profile index, MAC address, port number of the manageable Ethernet port, UE-DS-TT dwell time and port management information container, MA PDU request indication, and MA PDU network upgrade permission indication. Specifically, the (PSA)UPF ID and (PSA)UPF address that changed due to PSA UPF relocation are added and sent. Therefore, PCF 812 can store the UPF ID and UPF address that changed due to PSA UPF relocation.

[0151] In operation 803, PCF 812 sends an Npcf_SMPolicyControl_Update response message to SMF 811.

[0152] In operation 804, PCF 812 updates information about the PDU session to BSF 813 via an Nbsf_Management_Update request message. The parameters in the Nbsf_Management_Update request message include at least one of the following: the PDU session binding identifier, the UE address, and the PCF ID. To update UPF information to BSF 813, the UPF address and UPF ID can also be provided. Therefore, BSF 813 can store the UPF ID and UPF address that have changed due to PSA UPF relocation.

[0153] In operation 805, BSF 813 sends an Nbsf_Management_Register response message to PCF 812.

[0154] The methods disclosed in the claims and / or the methods of various embodiments described in this disclosure can be implemented in hardware, software, or a combination of hardware and software.

[0155] When the method is implemented in 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 may be configured to be executed by one or more processors within an electronic device. At least one program may include instructions to cause the electronic device to perform the method according to various embodiments of this disclosure as defined in the appended claims and / or disclosed herein.

[0156] The program (software module or software) can be stored in non-volatile memory, including random access memory and flash memory, read-only memory, electrically erasable programmable read-only memory, magnetic disk storage devices, compressed optical disc-ROM (CD-ROM), digital versatile discs (DVDs), or other types of optical storage devices or magnetic tape cassettes. Alternatively, any combination of some or all of the above-mentioned memories can form a memory storing the program. Furthermore, multiple such memories can be included in an electronic device.

[0157] Additionally, the program can be stored in an attachable storage device, which can be connected to the electronic device via a communication network such as the Internet, intranet, local area network (LAN), wide area network (WLAN), and storage area network (SAN), or a combination thereof. This storage device can be connected to the electronic device via an external port. Furthermore, a separate storage device on the communication network can be connected to a portable electronic device.

[0158] In the detailed embodiments described above, elements included in this disclosure are referred to as singular or plural, depending on the presented embodiments. However, for ease of description, the singular or plural form may be chosen as appropriate for the presented situation, and this disclosure is not limited to elements referred to as singular or plural. Thus, elements referred to as plural may also include a single element, or elements referred to as singular may include multiple elements.

[0159] Although specific embodiments have been described in detail in this disclosure, various modifications and changes can be made thereto without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the embodiments, but should be defined by the appended claims and their equivalents.

[0160] Although this disclosure has been described using various embodiments, various changes and modifications can be made by those skilled in the art. This disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims.

Claims

1. A method performed by a network exposure function (NEF) in a wireless communication system, the method comprising: receiving, from an application function (AF), an Nnef_EventExposure_Subscribe message including an Internet Protocol (IP) address of a user equipment (UE) to subscribe to events of a specific service flow of the UE from a user plane function (UPF); in response to the Nnef_EventExposure_Subscribe message, transmitting, to a binding support function (BSF), a request message including the IP address of the UE to find the UPF to subscribe to events of a specific service flow of the UE; receiving, from the UPF, an Nupf_EventExposure_Notify including information of the subscribed events; and in response to the Nupf_EventExposure_Notify message, transmitting, to the AF, an Nnef_EventExposure_Notify including the subscribed information. 2.The method of claim 1, wherein the Nupf_EventExposure_Subscribe message is transmitted to the UPF to subscribe to the events, and wherein the Nupf_EventExposure_Notify message is received in response to the Nupf_EventExposure_Subscribe message.

3. The method of claim 2, wherein, the Nupf_EventExposure_Subscribe message includes the IP address of the UE. 4.A network exposure function (NEF) in a wireless communication system, the NEF comprising: at least one processor; and at least one memory communicably coupled to the at least one processor and storing instructions executable by the at least one processor to, individually or in any combination: receive, from an application function (AF), an Nnef_EventExposure_Subscribe message including an Internet Protocol (IP) address of a user equipment (UE) to subscribe to events of a specific service flow of the UE from a user plane function (UPF); in response to the Nnef_EventExposure_Subscribe message, transmit, to a binding support function (BSF), a request message including the IP address of the UE to find the UPF to subscribe to events of a specific service flow of the UE; receive, from the UPF, an Nupf_EventExposure_Notify message including information of the subscribed events; and in response to the Nupf_EventExposure_Notify message, transmit, to the AF, an Nnef_EventExposure_Notify message including the subscribed information. 5.The NEF of claim 4, wherein a Nupf_EventExposure_Subscribe message is sent to the UPF to subscribe to the event, and wherein the Nupf_EventExposure_Notify message is received in response to the Nupf_EventExposure_Subscribe message.

6. The NEF of claim 5, wherein, The Nupf_EventExposure_Subscribe message includes the IP address of the UE. 7.A method of operation of a user plane function (UPF) in a wireless communication system, the method comprising: receiving a Nupf_EventExposure_Subscribe message for subscribing to an event of a specific service flow of a user equipment (UE); and sending a Nupf_EventExposure_Notify message including information of the subscribed event to a network exposure function (NEF), wherein a Nnef_EventExposure_Subscribe message including an internet protocol (IP) address of the UE is sent from an application function (AF) to the NEF, and wherein in response to the Nnef_EventExposure_Subscribe message, a request message including the IP address of the UE is sent from the NEF to a binding support function (BSF) to find the UPF to subscribe to the event of the specific service flow of the UE. 8.The method of claim 7, wherein The Nupf_EventExposure_Subscribe message includes the IP address of the UE. 9.A user plane function (UPF) in a wireless communication system, the UPF comprising: at least one processor; and at least one memory communicably coupled to the at least one processor and storing instructions executable by the at least one processor to, individually or in any combination: receive a Nupf_EventExposure_Subscribe message for subscribing to an event of a specific service flow of a user equipment (UE); and send a Nupf_EventExposure_Notify message including information of the subscribed event to a network exposure function (NEF), wherein a Nnef_EventExposure_Subscribe message including an internet protocol (IP) address of the UE is sent from an application function (AF) to the NEF, and wherein in response to the Nnef_EventExposure_Subscribe message, a request message including the IP address of the UE is sent from the NEF to a binding support function (BSF) to find the UPF to subscribe to the event of the specific service flow of the UE. 10.The UPF of claim 9, wherein The Nupf_EventExposure_Subscribe message includes the IP address of the UE.

Images