Method and device for managing terminal address in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. Specifically, the present disclosure provides a method and device for managing a terminal address in a wireless communication system.

Description

Method and device for managing terminal addresses in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more specifically, to a method and device for managing a terminal address in a wireless communication system.

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

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

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

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

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

[0007] In addition, the development of these 5G mobile communication systems will require the development of new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas, and large scale antennas, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI-based communication technology that utilizes artificial intelligence (AI) from the design stage and internalizes end-to-end AI support functions to realize system optimization, and next-generation distributed computing technology that realizes services with complexity that exceeds the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could be the basis.

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

[0009] Based on the discussion as described above, the disclosed embodiment provides a method and device for managing a terminal address in a wireless communication system.

[0010] The disclosed embodiment provides a device and method capable of effectively providing a service in a wireless communication system.

[0011] FIG. 1 is a diagram illustrating an example of a network structure and interface of a 5G system according to one embodiment of the present disclosure.

[0012] FIG. 2 illustrates a method for allocating an IP address for a PDU Session by an AF request according to one embodiment of the present disclosure.

[0013] FIG. 3 illustrates an update method for an existing PDU session when updating static IP address information according to one embodiment of the present disclosure.

[0014] FIG. 4 is a block diagram illustrating the structure of a terminal according to one embodiment of the present disclosure.

[0015] FIG. 5 is a block diagram illustrating the structure of a base station according to one embodiment of the present disclosure.

[0016] FIG. 6 is a block diagram illustrating the structure of a network entity according to one embodiment of the present disclosure.

[0017] According to one embodiment of the present disclosure, a method performed by a network exposure function (NEF) in a wireless communication system may include: receiving, from an application function (AF), a first parameter provisioning update request message including static IP address (static internet protocol address) allocation parameters of a terminal; determining whether the static IP address allocation parameters of the terminal are allowed based on the static IP address allocation parameters and configuration information of the terminal; and transmitting a response message including information regarding whether the static IP address allocation parameters of the terminal are allowed and the reason for the allowance based on the determination result.

[0018] Also, according to one embodiment of the present disclosure, in a method performed by UDM (unified data management), the method may include: receiving a parameter provisioning update message including fixed IP address allocation parameters of a terminal from an NEF; and transmitting a query message to a UDR (unified data repository) to validate the fixed IP address allocation parameters of the terminal; receiving a response message to the query message; determining whether the fixed IP address allocation parameters of the terminal are authenticated based on the response message; and transmitting a message including the determination result to a NEF (network exposure function).

[0019] In a network exposure function (NEF) of a wireless communication system, the NEF includes a transceiver; and at least one processor coupled to the transceiver, wherein the processor receives, from an application function (AF), a first parameter provisioning update request message including static IP address (static internet protocol address) allocation parameters of a terminal, determines whether the static IP address allocation parameters of the terminal are allowed based on the static IP address allocation parameters and configuration information of the terminal, and transmits a response message including information on whether the static IP address allocation parameters of the terminal are allowed and the reason based on the determination result.

[0020] According to one embodiment of the present disclosure, in a unified data management (UDM) of a wireless communication system, the UDM includes: a transceiver; and at least one processor coupled with the transceiver, wherein the at least one processor receives a parameter provisioning update message including fixed IP address allocation parameters of a terminal from a network exposure function (NEF), transmits a query message to a unified data repository (UDR) to validate the fixed IP address allocation parameters of the terminal, receives a response message to the query message, determines whether to authenticate the fixed IP address allocation parameters of the terminal based on the response message, and transmits a message including the determination result to a network exposure function (NEF).

[0021] The terms used in this disclosure are used only to describe specific embodiments and may not be intended to limit the scope of other embodiments. The singular expression may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by those of ordinary skill in the art described in this disclosure. Terms defined in general dictionaries among the terms used in this disclosure may be interpreted as having the same or similar meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined in this disclosure. In some cases, even if a term is defined in this disclosure, it cannot be interpreted to exclude embodiments of the present disclosure.

[0022] The various embodiments of the present disclosure described below illustrate a hardware-based approach as an example. However, since the various embodiments of the present disclosure include techniques utilizing both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach.

[0023] Hereinafter, various embodiments will be described in detail with reference to the accompanying drawings. Furthermore, when describing embodiments of the present disclosure, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the embodiments. Furthermore, the terms described below are defined in consideration of their functions in the embodiments, and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the contents throughout this specification.

[0024] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size.

[0025] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided solely to ensure the completeness of the present disclosure and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined solely by the scope of the claims.

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

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

[0028] Here, the term '~ unit' used in various embodiments of the present disclosure means a software or hardware component such as an FPGA or ASIC, and the '~ unit' can perform certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Accordingly, as an example, the '~ unit' may include components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, components and '~parts' may be implemented to regenerate one or more CPUs within a device or secure multimedia card.

[0029] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. At this time, it should be noted that the same components in the attached drawings are represented by the same reference numerals as much as possible. In addition, it should be noted that the attached drawings of the present disclosure are provided to help understand the present disclosure, and the present disclosure is not limited to the forms or arrangements illustrated in the drawings. In addition, detailed descriptions of well-known functions and configurations that may obscure the gist of the present disclosure will be omitted. It should be noted that in the following description, only the parts necessary for understanding the operation according to various embodiments of the present disclosure will be described, and the description of other parts will be omitted so as not to distract from the gist of the present disclosure. In addition, although the present disclosure describes various embodiments using terminology used in some communication standards (e.g., 3GPP (3rd Generation Partnership Project)), this is merely an example for explanation. The various embodiments of the present disclosure can be easily modified and applied to other communication systems.

[0030] In this disclosure, phrases such as “A / B”, “A and / or B”, “A or B”, “at least one of A and B”, “at least one of A or B”, “A, B, or C”, “at least one of A, B, and C”, and “at least one of A, B, or C” can each include any one of the items listed together in that phrase, or all possible combinations thereof. Terms such as “first”, “second”, or “first” or “second” may be used simply to distinguish the corresponding component from other corresponding components and do not limit the corresponding components in any other respect (e.g., importance or order).

[0031] In the present disclosure, network technology may refer to standard specifications defined by the International Telecommunication Union (ITU) or 3GPP (e.g., TS 23.501, TS 23.502, TS 23.503, etc.), and components included in the network structure of FIG. 1 described below may mean a physical entity, or may mean software performing an individual function, or hardware combined with software. Reference symbols shown as Nx, such as N1, N2, N3, ..., in the drawings represent known interfaces between NFs in a 5G core network (CN).

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

[0033] FIG. 1 is a diagram illustrating an example of a network structure and interface of a 5G system according to one embodiment of the present disclosure.

[0034] A 5G system (5G mobile communication network) may be composed of a 5G UE (user equipment, terminal), a 5G RAN (radio access network, base station, gNB (5G nodeB), eNB (evolved nodeB, etc.), and a 5G core network. Of course, the present invention is not limited to the above examples, and the 5G system may include fewer or more components than the components described above.

[0035] According to one embodiment, the 5G core network is composed of network functions such as an access and mobility management function (AMF) that provides a mobility management function of a UE, a session management function (SMF) that provides a session management function, a user plane function (UPF) that performs a data transfer role, a policy control function (PCF) that provides a policy control function, a unified data management (UDM) that provides a data management function such as subscriber data and policy control data, and a unified data repository (UDR) that stores data of various network functions such as UDM. Of course, the present invention is not limited to the above examples, and the 5G core network may include fewer or more components than the components described above.

[0036] In one embodiment, the 3GPP system defines a conceptual link connecting NFs within a 5G system as a reference point. The following illustrates a reference point included in the 5G system architecture depicted in Figure 1.

[0037] - N1: Reference point between UE and AMF

[0038] - N2: Reference point between (R)AN and AMF

[0039] - N3: Reference point between (R)AN and UPF

[0040] - N4: Reference point between SMF and UPF

[0041] - N5: Reference point between PCF and AF

[0042] - N6: Reference point between UPF and DN

[0043] - N7: Reference point between SMF and PCF

[0044] - N8: Reference point between UDM and AMF

[0045] - N9: Reference point between two core UPFs

[0046] - N10: Reference point between UDM and SMF

[0047] - N11: Reference point between AMF and SMF

[0048] - N12: Reference point between AMF and AUSF

[0049] - N13: Reference point between UDM and authentication server function (AUSF)

[0050] - N14: Reference point between two AMFs

[0051] - N15: Reference point between PCF and AMF for non-roaming scenarios, reference point between PCF and AMF in visited network for roaming scenarios.

[0052] FIG. 2 illustrates a method for allocating an IP address for a PDU Session by an AF request according to one embodiment of the present disclosure.

[0053] According to one embodiment of the present disclosure, an AF may be authorized to provide static IP address(es) for a subscriber (or UE) for a given DNN and S-NSSAI. In this case, the static IP address for each UE ID (e.g., GPSI or UE IP address / port number) may be provided by an authorized AF via the NEF and stored as part of the UE subscription data. The AF may provide static IP addresses for multiple GPSIs.

[0054] In step 1, AF can send NEF a Nnef_ParameterProvision_Create or Nnef_ParameterProvision_Update request message. Of course, the message name is not limited to the above example.

[0055] The Nnef_ParameterProvision_Create or Nnef_ParameterProvision_Update request message may include the following information. Of course, the present invention is not limited to the examples below, and the Nnef_ParameterProvision_Create or Nnef_ParameterProvision_Update request message may include more or less information. In addition, among the information included below, DNN, S-NSSAI, UE ID(s), and Static IP address information per UE ID, or Static IP address request indicator may be defined as a single parameter set for Static IP address allocation. The name for the parameter set may be referred to as, for example, Static IP address Assignment Parameters. Of course, the name for the parameter set is not limited to the examples above.

[0056] - AF Identifier: May include an AF (application function) identifier.

[0057] -Transaction Reference ID: May contain an identifier for the request.

[0058] -UE ID(s): UE identifier information, which may include GPSI (generic public subscription identifier), MSISDN (mobile station international ISDN (integrated service digital network) number), or UE address information (e.g., IP address and port address). If the request message applies to all UEs (e.g., applies to S-NSSAI (single network slice selection assistance information) and / or DNN (data network name)), information indicating any UE instead of a UE ID or no UE ID may be included. In addition, more than one UE ID may be included. If more than one UE ID is included, Static IP address information or a Static IP address request indicator may be included for each UE ID.

[0059] -S-NSSAI and / or DNN: May contain slice identifier and / or data network name information.

[0060] -PLMN ID: PLMN (public land mobile network) identifier information may be included.

[0061] -SSC mode: SSC (session and service continuity) mode may be included (e.g., one or more of SSC mode 1, SSC mode 2, and SSC mode 3). If the message in step 1 includes Static IP address information or a Static IP address request indicator, the AF may include SSC mode 1 (i.e., indicating a PDU session that does not allow IP address changes). SSC mode 2 may indicate a PDU session that operates in a way that the existing session is released before a new session is established for replacement (i.e., break-before-make). SSC mode 3 may indicate a PDU session that operates in a way that the replacement session is first established before the existing session is released (i.e., make-before-break).

[0062] -Static IP address information: Static IP address information (i.e., IPv4 address or IPv6 address / prefix) or an IP address range (i.e., IPv4 address range or IPv6 address / prefix range) may be included. When requesting static IP address allocation for one or more UEs, static IP address information for each UE may be included. When requesting address allocation within a static IP range for one or more UEs, an IP address range for each UE may be included, or one IP address range may be included for the UE(s).

[0063] -Static IP address request indicator: When requesting allocation of a static IP address, an indicator requesting a static IP address (static IP address request indicator) may be included. If static IP address information is included for each UE, the static IP address request indicator may not be included.

[0064] According to one embodiment, upon receiving the message of step 1, the NEF may perform authentication as to whether the AF is authorized to perform a request for parameter provisioning creation / update of the AF based on the configuration information and the AF ID.

[0065] Additionally, according to one embodiment, if the message of step 1 includes an AF service ID and / or an AF ID and does not include an S-NSSAI / DNN, the NEF may identify (or derive) the corresponding S-NSSAI / DNN based on the configuration information from the AF service ID and / or the AF ID.

[0066] Additionally, according to one embodiment, when the AF provides GPSI to identify the UE, the NEF can convert the GPSI into a subscription permanent identifier (SUPI) through unified data management (UDM).

[0067] Additionally, according to one embodiment, when the AF provides UE address information to identify the UE, the NEF can convert the UE address information into SUPI via a binding support function (BSF) or UDM.

[0068] In one embodiment, the NEF may perform authentication on the parameters included in the AF request. The network operator (or mobile carrier) may use one of steps 1a, 3, or 3b to verify whether the same IP address / prefix has been assigned to another UE (i.e., included in the subscription information).

[0069] Additionally, in step 1, if AF wants to delete an already allocated Static IP address / prefix, it can send to NEF an Nnef_ParameterProvision_Delete request message or an Nnef_ParameterProvision_Update request message that does not include the Static IP address request indicator or Static IP address information among the parameters described for the above create message or update message. The message may include an indicator requesting deletion of the Static IP address / prefix.

[0070] In step 1a, if the request message received in step 1 includes UE ID, static IP address information, or static IP request indicator, the NEF can check whether static IP allocation is possible based on the configuration information or information received from the UDM for those parameters.

[0071] In one embodiment, the NEF may perform authentication based on the S-NSSAI, DNN included in the request message received in step 1 (or the corresponding S-NSSAI, DNN if the AF ID or AF service ID is included and the NEF derives the corresponding S-NSSAI, DNN) configuration information or information received from the UDM (e.g., allow only if the UE is subscribed to the corresponding S-NSSAI, DNN, otherwise reject).

[0072] In addition, according to one embodiment, the NEF may perform authentication based on information received from the UDM or may directly request authentication from the UDM. The NEF may transmit an authentication request message to the UDM, which may include a UE ID, static IP address information or a static IP request indicator, S-NSSAI, and DNN for authentication. Upon receiving the authentication request message, the UDM may perform authentication based on information stored in the UDR (unified data repository) for the UE ID included in the authentication request message. In response to the authentication request message, the UDM may transmit a response message to the NEF, which may include the following information, but is not limited to the following examples.

[0073] -Result: If the parameter Create or Update request message received from the NEF includes UE ID, S-NSSAI, and DNN Static IP address information, and if the UE's subscription information stored in the UDR does not include S-NSSAI or DNN, the UDM may include a message indicating failure and cause information (e.g., result=failed, cause=S-NSSAI, DNN not allowed to UE, or result=failed). In this case, the NEF may include result=failed, cause=S-NSSAI, DNN not allowed to UE, or result=failed in the response message sent to the AF in step 1b.

[0074] Additionally, according to one embodiment, if the Create request message received from the NEF includes UE ID, S-NSSAI, and DNN Static IP address information, and if the subscription information of the UE stored in the UDR already includes a Static IP address for the UE ID, S-NSSAI, and DNN, the UDM may include a message indicating failure and cause information (e.g., result=failed, cause= static IP address / prefix is ​​already assigned for the UE).

[0075] Alternatively, if the request message received from the NEF includes UE ID, S-NSSAI, DNN, and Static IP address, and the corresponding Static IP address / prefix has already been allocated for another UE, the UDM may include a message indicating failure and cause information (e.g., result=failed, cause=requested static IP address / prefix assigned for other UE). In this case, the NEF may include result=failed, cause=requested static IP address / prefix assigned for other UE in the response message sent to the AF in step 1b.

[0076] According to one embodiment, when the NEF performs authentication based on information received from the UDM, it may transmit a request message including a UE ID, S-NSSAI, and DNN. The UDM may transmit a response message to the NEF including static IP address / prefix information for the UE ID, S-NSSAI, and DNN based on information stored in the UDR. When the information received from the UDM includes static IP address / prefix information, and when the message including the requested static IP address / prefix for the UE is a Create message, the NEF may determine that the requested static IP address / prefix cannot be assigned because the static IP address / prefix has already been assigned. In this case, the NEF may include result=failed, cause=requested static IP address / prefix assigned for other UE in the response message transmitted to the AF in step 1b.

[0077] Also, according to one embodiment, if the message received from the AF includes a Static IP Address / prefix, the NEF can query the BSF to check (or identify) whether the requested Static IP Address is not used by another UE. The NEF can query the BSF for the static IP address for the requested UE by calling the Nbsf_Management procedure. The query request message transmitted to the BSF can include the Static IP address / prefix and the S-NSSAI, DNN included in the message received in step 1 (or the S-NSSAI, DNN converted for the AF Service ID included in the request message in step 1). The NEF receives the UE identifier (SUPI or GPSI) for the requested IP address from the BSF, and if the received UE identifier is different from the UE identifier included in the request message received from the AF, it can determine that the requested static IP address is used by another UE. In this case, the NEF may include result=failed, cause=requested static IP address / prefix is ​​used for other UE in the response message sent to the AF in step 1b. If the UE already has a static IP address / prefix (e.g., Ipv4 address, Ipv6 address / prefix) in its subscription information, the -Static IP address / prefix information may be included.

[0078] In Step 1b, NEF may send AF a response message (e.g., Nnef_ParameterProvision_Create / Update response) to the request message in Step 1. The response message may include the following information. Of course, the following examples are not limited, and the response message may include more or less information than the following.

[0079] -Result: NEF may include the corresponding result and cause information depending on the authentication (or parameter verification) performed in step 1a.

[0080] In one embodiment, if parameter verification succeeds, NEF may include a result indicating success. If parameter verification fails, NEF may include a result indicating failure and a cause depending on the case in step 1a.

[0081] Additionally, according to one embodiment, if a static IP address / prefix (e.g., Ipv4 address, Ipv6 address / prefix) exists in the message received from the UDM in step 1a, the NEF may include the static IP address / prefix information in the response message transmitted to the AF.

[0082] In one embodiment, when the AF receives the message of step 1b, it may determine that a static IP address has already been allocated for the UE and may not transmit a message to allocate a static IP address again.

[0083] In step 2, if the authentication to the AF in step 1 was successful, and if the authentication was performed in step 1a, the NEF may send a request message (e.g., a Nudm_ParameterProvision_Create / Update message) to the UDM containing the following information. Of course, the request message is not limited to the following examples, and may contain more or less information than the information below.

[0084] -AF Identifier: The AF identifier included in the message in step 1 may be included.

[0085] -Transaction Reference ID: May contain an identifier for the request.

[0086] -UE ID: May contain information included in the message in Step 1.

[0087] -S-NSSAI and / or DNN: May contain slice identifier and / or data network name information.

[0088] -PLMN ID: May contain PLMN identifier information.

[0089] -SSC mode: The SSC mode included in the message received in step 1 may be included (e.g., one or more of SSC mode 1, SSC mode 2, SSC mode 3). Alternatively, if the message in step 1 includes Static IP address information or a Static IP address request indicator, the NEF may include SSC mode 1 (i.e., indicating a PDU session that does not allow IP address changes).

[0090] -Static IP address information: It may include static IP address information (i.e., static IP address / prefix, which may be, for example, an IPv4 address or an IPv6 address / prefix) or an IP address range (i.e., an IPv4 address range or an IPv6 address / prefix range). If static IP address allocation is requested for one or more UEs, static IP address information for each UE may be included. If address allocation within a static IP range is requested for one or more UEs, an IP address range for each UE may be included, or one IP address range may be included for the UE(s).

[0091] -Static IP address request indicator: When requesting allocation of a static IP address, an indicator requesting a static IP address (static IP address request indicator) may be included. If static IP address information is included for each UE, the static IP address request indicator may not be included.

[0092] -Assigned Static IP address / prefix: If the message received in step 1 includes a Static IP address request indicator, the NEF may allocate one of the static IP addresses that are not yet allocated within the S-NSSAI and DNN to the UE and include the allocated static IP address / prefix. Alternatively, if the message received in step 1 includes a Static IP address range, the NEF may allocate one of the static IP addresses that are not yet allocated within the IP range to the UE and include the allocated static IP address / prefix.

[0093] Additionally, in step 2, if the request message received in step 1 is a message for deleting a Static IP address / prefix, the NEF may transmit a message for deleting the Static IP address / prefix to the UDM. The message may be a Nudm_ParameterProvision_Delete request message or a Nudm_ParameterProvision_Update request message that does not include the Static IP address / prefix among the parameters described for the above-described create message or update message. The message may include an indicator requesting deletion of the Static IP address / prefix.

[0094] In step 3, UDM can read subscription information from UDR via Nudr_DM_Query prior to changing information for validation of AF's request (i.e., request to change subscriber information or subscriber group information).

[0095] UDM can send Nudr_DM_Query message to UDR, which includes UE identifier (SUPI or GSPSI), DNN, and S-NSSAI as Data Key. Of course, the name of the message is not limited to the above example. If UDR already has a Static IP address stored for UE identifier, DNN, and S-NSSAI, it can include the allocated Static IP address / prefix in the response message sent to UDM.

[0096] Additionally, UDM can send Nudr_DM_Query message to UDR, which includes static IP address / prefix, DNN, and S-NSSAI as Data Key. Of course, the name of the message is not limited to the above example. If UDR identifies (or discovers) another UE with the same static IP address / prefix for DNN and S-NSSAI, UDR can include information in the response message sent to UDM indicating that the corresponding static IP address / prefix has already been allocated to another UE (e.g., static IP address / prefix in use for another UE).

[0097] UDM may determine that validation (or authentication) has failed for an AF request in the following cases, including but not limited to the following examples:

[0098] -If the Nudm_ParameterProvision_Create request message received from NEF includes UE ID, S-NSSAI, and DNN Static IP address information (or static IP address request indicator), and if the UE's subscription information stored in the UDR already includes a static IP address for the UE ID, S-NSSAI, and DNN.

[0099] -If S-NSSAI and DNN are not included in the UE's subscription information

[0100] -If the Static IP address / prefix included in the request message received from the NEF for the S-NSSAI or DNN has already been allocated to another UE (for example, if information indicating that the static IP address / prefix has already been allocated to another UE is received from the UDR)

[0101] In one embodiment, if the verification of the AF request in step 3 is successful, the UDM may perform step 3b. Alternatively, if the verification of the AF request fails, the UDM may skip step 3 and proceed to step 4.

[0102] In Step 3b, if the message received in Step 2 is a Nudm_ParameterProvision_Create or Update message and verification is successful, the UDM may send a request message to the UDR to update subscriber information. The message may include the following information. Of course, this is not limited to the examples below, and the request message may include more or less information than the information listed below.

[0103] -UE ID: SUPI can be included as key information.

[0104] -subscription data: Subscription data can be included as key information.

[0105] -S-NSSAI, DNN: S-NSSAI, DNN can be included as key information.

[0106] -Static IP address / prefix: If the message received in step 2 includes a Static IP address request indicator, UDM can allocate one of the static IP addresses that are not yet allocated within S-NSSAI and DNN to the UE and include the allocated static IP address / prefix. If the message received in step 2 includes a Static IP address range, UDM can allocate one of the static IP addresses that are not yet allocated within the IP range to the UE and include the allocated static IP address / prefix.

[0107] In one embodiment, if the message received in step 2 includes a static IP address, the UDM may allocate the IP address to the UE and include the allocated static IP address / prefix.

[0108] - SSC mode: If the message in step 2 includes an SSC mode, the corresponding SSC mode may be included (for example, one or more of SSC mode 1, SSC mode 2, and SSC mode 3).

[0109] Alternatively, if UDM decides to update the Static IP address / prefix after receiving the message in step 2, if the SSC mode in the subscriber information is not set to SSC mode 1 (or does not include SSC mode 1), it may include SSC mode 1 in the SSC mode of the subscriber information to update it to SSC mode 1.

[0110] If the request message received in step 1 is a message for deleting a Static IP address / prefix, the UDM may transmit a message for deleting the Static IP address / prefix to the UDR. The message may be a Nudr_DM_Delete request message or a Nudr_DM_Update request message that does not include the Static IP address / prefix among the parameters described for the above-described create message or update message. The message may include an instruction requesting deletion of the Static IP address / prefix.

[0111] In one embodiment, the UDR may send a response message to the UDM in response to the update request message. The response message may include the processing result (success or failure).

[0112] If the UDR identifies (or discovers) another UE with the same static IP address / prefix for the DNN and S-NSSAI, the UDR may include in the response message it sends to the UDM information indicating that the corresponding static IP address / prefix has already been allocated to another UE. In this case, the UDR may include a processing result indicating failure, along with a cause indicating that the requested static IP address / prefix is ​​already in use by another UE (e.g., result=failed, cause=static IP address / prefix in use for other UE).

[0113] In step 4, UDM can send a response message to step 2.

[0114] The response message for Step 2 may contain a Result (a value indicating success or failure).

[0115] According to one embodiment, the UDM may include information indicating the failure and cause information if the verification of the AF request in step 3 fails (e.g., result=failed, cause=S-NSSAI, DNN not allowed to UE or result=failed, cause=static IP address / prefix already allocated for UE or result=failed, cause=static IP address / prefix in use for other UE).

[0116] Alternatively, if the UDM receives a response message from the UDR for the Nudr_DM_Update request message sent to the UDR in step 3b, and the response message includes a processing result indicating failure and a cause that the static IP address / prefix was allocated to another UE (e.g., result=failed, cause=static IP address / prefix in use for other UE), the UDM may include information indicating failure and cause information (e.g., cause=static IP address / prefix in use for other UE).

[0117] Additionally, according to one embodiment, the UDM may include information indicating success if the validation of the AF request in step 3 is successful.

[0118] Additionally, UDM may include -Static IP address / prefix information in the response message if the UE already has a static IP address / prefix (e.g., Ipv4 address, Ipv6 address / prefix) in its subscription information for the AF request in step 3.

[0119] In step 5, when NEF receives the message of step 4 from UDM, it may send a response message for step 1 (e.g., Nnef_ParameterProvision_Create / Update response message) to AF. The message sent in step 5 may include the following information:

[0120] If the request message in step 1 is a request to multiple UEs, the information below may be included for each UE. Of course, the following examples are not limited thereto.

[0121] -result: May contain a value indicating success or failure. Depending on the result contained in the message in step 4, success or failure (and cause information) may be included.

[0122] -static IP address / prefix: May contain a static IP address / prefix assigned to the UE.

[0123] In steps 6a and 6b, the UE may transmit NAS messages (e.g., AN messages and N2 messages) to the AMF via the RAN to request PDU session establishment. The NAS messages for PDU session establishment requests may include a PDU Session ID, S-NSSAI, DNN, Request Type (initial request or existing PDU Session), and a PDU Session establishment request. Of course, the above examples are not limited.

[0124] In step 7, the AMF may select an SMF based on the S-NSSAI and DNN received in step 6, and then send an SM Context creation request message (e.g., Nsmf_PDUSession_CreateSMContext Request message) to the SMF. The SM Context creation request message may include the S-NSSAI, DNN, and PDU Session ID. Of course, the present invention is not limited to the above example.

[0125] In steps 8a-8b, if the SMF does not have subscriber information for the UE, it may send a request message to the UDM including the UE ID (e.g., SUPI), S-NSSAI, and DNN.

[0126] According to one embodiment, when the UDM receives a request message from the SMF, the UDM may obtain the subscriber information stored in the UDR (e.g., by transmitting and receiving the Nudr_DM_Query / response message in steps 9a-9b) and then transmit it to the SMF. At this time, if the allocation or update for the static IP address / prefix and / or SSC mode is performed for the UE in step 3b, the updated static IP address / prefix and / or SSC mode may be included in the message transmitted to the SMF.

[0127] Additionally, according to one embodiment, if the subscriber information received from the UDM includes a static IP address / prefix, the SMF may assign an IP address for the PDU Session of the UE to the static IP address / prefix.

[0128] According to one embodiment, if the subscriber information received from the UDM includes the SSC mode, the SMF may assign the SSC mode to the PDU Session of the UE.

[0129] Additionally, according to one embodiment, the SMF may determine the SSC mode for the PDU session as SSC mode 1 according to the operator policy if the subscriber information includes a static IP address / prefix.

[0130] In step 9, SMF may send AMF a response message for step 7 (e.g., an Nsmf_PDUSession_CreateSMContext Response message).

[0131] In step 10, SMF can perform a procedure (SM policy association establishment) with PCF to obtain policy information for the session.

[0132] In step 11, the SMF selects a UPF for the session and can transmit session establishment information via an N4 message. At this time, the previously allocated static IP address / prefix information may be transmitted to the UE's IP address. Of course, this example is not limited to the above example.

[0133] In step 12, if the subscriber information received from the UDM in step 8b includes a static IP address / prefix, and if the SMF has assigned an IP address for the UE's PDU Session to the static IP address / prefix, the SMF may include the static IP address / prefix in the N1 message container of a message (e.g., a Namf_Communication_N1M2messageTransfer message) to be transmitted to the AMF to transmit the assigned static IP address / prefix to the UE. Of course, the inclusion relationship of the message is not limited to the above example.

[0134] Additionally, according to one embodiment, the SMF may include the SSC mode in the N1 message container if the subscriber information received from the UDM in step 8b includes the SSC mode.

[0135] In step 13, if the message received from the SMF includes an N1 message, the AMF may include the information contained in the N1 message in an NAS message and transmit the NAS message to the RAN by including it in an N2 message. Of course, the inclusion relationship of the messages is not limited to the above example.

[0136] At step 14, the RAN may send an AN message including an NAS message to the UE.

[0137] If the NAS message includes a PDU Session establishment accept message with a Static IP address / prefix, the UE can use the Static IP Address / prefix as the IP address for the PDU session (e.g., store the IP address / prefix in the context information for the PDU Session). That is, the UE can use the received Static IP Address / prefix as the source address to use when transmitting IP packets through the PDU session.

[0138] In one embodiment, the UE may use the SSC mode as the IP address for the PDU session if the NAS message includes a PDU Session establishment accept message with the SSC mode.

[0139] In step 15, the remaining PDU session establishment procedures may be performed. The remaining PDU session establishment procedures are self-explanatory to those skilled in the art, so a detailed description thereof is omitted.

[0140] It is obvious to those skilled in the art that some of the steps described through FIG. 2 may not be performed or may be performed in a changed order.

[0141] FIG. 3 illustrates an update method for an existing PDU session when updating static IP address information according to one embodiment of the present disclosure.

[0142] Step 0a corresponds to the operations of steps 6, 7, and 8 of Fig. 2, so a detailed description is omitted.

[0143] In step 0b, the SMF may send a subscription request message (e.g., Nudm_SDM_Subscribe message) to the UDM indicating that it will send a notification message when subscriber information changes for the UE ID (e.g., SUPI), S-NSSAI, and DNN.

[0144] In step 0c, upon receiving the message from the SMF, the UDM may send a subscription request message (e.g., Nudr_DM_Subscribe / response message) to the UDR indicating that it will send a notification message when subscriber information changes for the UE ID, S-NSSAI, and DNN.

[0145] Steps 1 to 5 of FIG. 3 correspond to steps 1 to 5 of FIG. 2, so detailed descriptions are omitted.

[0146] In step 6, the UDR may send a notification message (e.g., a Nudm_SDM_Notify message) to the UDM if an update to the subscriber information was performed in step 3b. The notification message sent to the UDM may include the UE ID, DNN, S-NSSAI, and updated information (e.g., Static IP address / index) and / or information indicating that the SSC mode or Static IP address / index has been deleted. Of course, the above examples are not limited thereto.

[0147] In one embodiment, upon receiving a notification message from the UDR, the UDM may transmit a subscriber information change notification message to the SMF. The information change notification message may include the UE ID, DNN, S-NSSAI, updated information (e.g., Subscribed IP address / index), and / or information indicating that the SSC mode or Static IP address / index has been deleted. The present invention is not limited to the above examples.

[0148] In step 6a, the UDM may send a subscription message (e.g., a Subscribe message) requesting the SMF to notify it of the results of IP address allocation for S-NSSAI, DNN, and SUPI.

[0149] In step 7, if the subscriber information change notification message received from the UDM includes S-NSSAI, DNN, UE ID, and Static IP address / index, and if the IP address in use by the PDU Session for the S-NSSAI and DNN for the UE is different from the Static IP address / index (or if a PDU Session exists for the S-NSSAI and DNN for the UE), the SMF may send an N4 message including the new UE IP address to the UPF in charge of the PDU Session(s) to update the IP address in use for the corresponding PDU Session(s).

[0150] In one embodiment, if a subscriber information change notification message received from a UDM includes S-NSSAI, DNN, UE ID, and Static IP address / index, and if the IP address used by the PDU Session for the S-NSSAI and DNN for the UE is the same as the Static IP address / index, but the SSC mode used is not SSC mode 1, the SMF may send an N4 message including a new SSC mode to the UPF in charge of the PDU Session to update the SSC mode used for the corresponding PDU Session(s).

[0151] If the subscriber information change notification message received from the UDM includes information indicating that S-NSSAI, DNN, UE ID, and Static IP address / index have been deleted, and SSC mode (SSC mode 2 or SSC mode 3), and if a PDU Session exists for the S-NSSAI and DNN for the UE, the SMF may, depending on the configuration information, 1) transmit a message to the UPF and to the RAN / UE through the AMF to release the corresponding PDU Session, 2) perform a procedure to re-establish the PDU Session for applying a new IP address / prefix application method other than static IP allocation and applying the new SSC mode (or a procedure to change only the IP allocation method while maintaining the PDU session), or 3) may not release the corresponding PDU Session.

[0152] SMF can apply updated subscriber information (i.e., not assigning deleted static IP address / prefix and new SSC mode) to new PDU session establishment request for the corresponding S-NSSAI, DNN.

[0153] In step 8, if the subscriber information change notification message received from the UDM includes S-NSSAI, DNN, UE ID, and Static IP address / index, and if the IP address being used by the PDU Session for the S-NSSAI and DNN for the UE is different from the Static IP address / index (or if a PDU Session exists for the S-NSSAI and DNN for the UE), the SMF may transmit an NAS message (e.g., Namf_Communication_N1M2messageTransfer) to the UE through the AMF to update the IP address being used for the corresponding PDU Session(s). The N1 message transmitted to the UE may include the following information, but is not limited to the following examples.

[0154] -PDU Session ID

[0155] -Static IP address / prefix: The updated IP address / prefix for the PDU session may be included. For example, if the PDU Session Type is IPv4, the updated IPv4 address may be included. If the PDU Session Type is IPv6, the updated IPv6 address / prefix may be included. If the PDU Session Type is IPv4v6, the updated IPv4 address and / or updated IPv6 address / prefix may be included.

[0156] -PDU session Modification command (or PDU session release command)

[0157] An indicator may be included to indicate to the UE to re-request a PDU session for the same S-NSSAI, DNN.

[0158] According to one embodiment, if a subscriber information change notification message received from a UDM includes S-NSSAI, DNN, UE ID, and Static IP address / index, and if the IP address being used by the PDU Session for the S-NSSAI and DNN for the UE is the same as the Static IP address / index, but the SSC mode being used is not SSC mode 1, the SMF may transmit an NAS message to the UE through the AMF to update the SSC mode being used for the corresponding PDU Session(s). The N1 message transmitted to the UE may include the following information, but is not limited to the following examples.

[0159] -PDU Session ID

[0160] -SSC mode: SSC mode 1 may be included.

[0161] -PDU session Modification command (or PDU session release command)

[0162] An indicator may be included to indicate to the UE to re-request a PDU session for the same S-NSSAI, DNN.

[0163] In step 9, if the message received from the SMF includes an N1 message, the AMF may include the information included in the N1 message in an NAS message and transmit the NAS message to the RAN by including it in an N2 message.

[0164] In step 10, the RAN may transmit an AN message including an NAS message to the UE.

[0165] If a PDU Session establishment modification command is included in a NAS message with a Static IP address / prefix, the UE can update the Static IP Address / prefix to a new IP address for the PDU session (e.g., update the IP address / prefix in the context information for the PDU Session). That is, the UE can use the received Static IP Address / prefix as the source address to be used when transmitting IP packets through the PDU session.

[0166] In one embodiment, the UE may use the SSC mode as an IP address for the PDU session if the NAS message includes a PDU Session establishment modification command message with the SSC mode.

[0167] In step 11, if the NAS message received in step 10 includes an indicator indicating to perform PDU Session re-establishment with a Static IP address / prefix, the UE may release the existing PDU session and transmit a NAS message to the AMF via the RAN to request establishment of a new PDU session. At this time, the same S-NSSAI and DNN as the existing PDU session may be included in the NAS message.

[0168] Additionally, according to one embodiment, if the NAS message received in step 10 includes an indicator indicating to perform PDU Session re-establishment with SSC mode, the UE may release the existing PDU session and transmit a NAS message to the AMF via the RAN for requesting establishment of a new PDU session. At this time, the NAS message may include the same S-NSSAI, DNN, and requested SSC mode set to SSC mode 1 as the existing PDU session.

[0169] According to one embodiment, the UE may first release the existing PDU session and then perform a new PDU session request (i.e., release the existing PDU session and then send a PDU session establishment request message through the NAS), or may establish a new PDU session and then release the existing PDU session (i.e., send a PDU session establishment request message through the NAS and receive a PDU Session Establishment accept message from the network and then release the existing PDU session).

[0170] In steps 12 and 13, if the SMF receives the subscription request message of step 6a from the UDM and a static IP address is allocated for the PDU session for the corresponding S-NSSAI, DNN, and SUPI, the SMF may send a notification message to notify the UDM of this. The notification message may include a result indicating allocation and the allocated IP address / prefix. When the UDM receives the notification message from the SMF, the UDM may send a notification message including the allocation result and the allocated IP address / prefix to the NEF. When the NEF receives the notification message from the UDM, the NEF may send a notification message including the allocation result and the allocated IP address / prefix to the AF.

[0171] It is obvious to those skilled in the art that some of the steps described through FIG. 3 may not be performed or may be performed in a changed order.

[0172] FIG. 4 is a block diagram illustrating the structure of a terminal (UE) according to one embodiment of the present disclosure.

[0173] As illustrated in FIG. 4, the terminal of the present disclosure may include a processor (420), a transceiver (400), and a memory (410). However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. Furthermore, the processor (420), the transceiver (400), and the memory (410) may be implemented in the form of a single chip.

[0174] According to one embodiment of the present disclosure, the processor (420) can control a series of processes by which the terminal can operate according to the above-described embodiments of the present disclosure. For example, the processor (420) can control components of the terminal to perform the network slice change support method according to the above-described embodiments. The processor (420) can control components of the terminal to perform the above-described embodiments of the present disclosure by executing a program stored in the memory (410). In addition, the processor (420) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0175] According to one embodiment of the present disclosure, the transceiver (400) can transmit and receive signals with a network entity, another terminal, or a base station. The signals transmitted and received with the network entity, another terminal, or a base station can include control information and data. The transceiver (400) can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-converts a received signal. However, the transceiver (400) is only one embodiment, and the components of the transceiver (400) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (400) can receive a signal through a wireless channel, output it to the processor (420), and transmit the signal output from the processor (420) through the wireless channel.

[0176] According to one embodiment of the present disclosure, the memory (410) can store programs and data necessary for the operation of the terminal. In addition, the memory (410) can store control information or data included in signals transmitted and received by the terminal. The memory (410) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (410). In addition, according to one embodiment, the memory (410) can also store a program for performing the aforementioned network slice change support method.

[0177] FIG. 5 is a block diagram illustrating the structure of a base station according to one embodiment of the present disclosure.

[0178] As illustrated in FIG. 5, the terminal of the present disclosure may include a processor (520), a transceiver (500), and a memory (510). However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. Furthermore, the processor (520), transceiver (500), and memory (510) may be implemented in the form of a single chip.

[0179] According to one embodiment of the present disclosure, the processor (520) can control a series of processes by which the terminal can operate according to the above-described embodiments of the present disclosure. For example, the processor (520) can control components of the terminal to perform the network slice change support method according to the above-described embodiments. The processor (520) can control components of the terminal to perform the above-described embodiments of the present disclosure by executing a program stored in the memory (510). In addition, the processor (520) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0180] According to one embodiment of the present disclosure, the transceiver (500) can transmit and receive signals with a network entity, another base station, or a terminal. The signals transmitted and received with the network entity, another base station, or a terminal may include control information and data. The transceiver (500) may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-downconverts a received signal. However, the transceiver (500) is only one embodiment, and the components of the transceiver (500) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (500) may receive a signal through a wireless channel, output it to the processor (520), and transmit the signal output from the processor (520) through the wireless channel.

[0181] According to one embodiment of the present disclosure, the memory (510) can store programs and data necessary for the operation of the terminal. In addition, the memory (510) can store control information or data included in signals transmitted and received by the terminal. The memory (510) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (510). In addition, according to one embodiment, the memory (510) can store a program for performing the aforementioned network slice change support method.

[0182] FIG. 6 is a block diagram illustrating the structure of a network entity according to one embodiment of the present disclosure.

[0183] As illustrated in FIG. 6, the network entity of the present disclosure may include a processor (620), a transceiver (600), and a memory (610). However, the components of the network entity are not limited to the examples described above. For example, the network entity may include more or fewer components than the components described above. In addition, the processor (620), the transceiver (600), and the memory (610) may be implemented in the form of a single chip. In addition, according to one embodiment of the present disclosure, the network entity may refer to a network function (NF), and the NF may include a RAN, an AMF, a PCF, an UDM, an AF, a NEF, and a UTM.

[0184] According to one embodiment of the present disclosure, the processor (620) can control a series of processes by which the NF can operate according to the above-described embodiments of the present disclosure. For example, the processor (620) can control components of a network entity to perform a network slice change support method according to the above-described embodiments. The processor (620) can control components of a terminal to perform the above-described embodiments of the present disclosure by executing a program stored in the memory (610). In addition, the processor (620) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0185] According to one embodiment of the present disclosure, the transceiver (600) can transmit and receive signals with other network entities, base stations, or terminals. The signals transmitted and received with other network entities or terminals can include control information and data. The transceiver (600) can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-converts a received signal. However, the transceiver (600) is only one embodiment, and the components of the transceiver (600) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (600) can receive a signal through a wireless channel, output it to the processor (620), and transmit the signal output from the processor (620) through the wireless channel.

[0186] According to one embodiment of the present disclosure, the memory (610) may store programs and data necessary for the operation of the network entity. Furthermore, the memory (610) may store control information or data included in signals transmitted and received by the network entity. The memory (610) may be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. Furthermore, there may be a plurality of memories (610). Furthermore, according to one embodiment, the memory (610) may store a program for performing the aforementioned network slice change support method.

[0187] According to one embodiment of the present disclosure, a method performed by a network exposure function (NEF) in a wireless communication system may include: receiving, from an application function (AF), a first parameter provisioning update request message including static IP address (static internet protocol address) allocation parameters of a terminal; determining whether the static IP address allocation parameters of the terminal are allowed based on the static IP address allocation parameters and configuration information of the terminal; and transmitting a response message including information regarding whether the static IP address allocation parameters of the terminal are allowed and the reason for the allowance based on the determination result.

[0188] The above response message may include an indicator indicating failure and information about the reason for failure if the terminal's fixed IP address allocation parameters are not allowed.

[0189] The method may further include: a step of determining whether to authorize the AF; a step of transmitting a second parameter provisioning update message including fixed IP address allocation parameters of the terminal to a unified data management (UDM) if the AF is authorized; and a step of receiving a response message including information regarding whether to allow the update request and the reason for the approval from the UDM.

[0190] The method may further include a step of transmitting the response message if the AF is not permitted.

[0191] The fixed IP address allocation provisioning parameters of the above terminal may include at least one of a generic public subscription identifier (GPSI), a data network name (DNN), a single network slice selection assistance information (S-NSSAI), and fixed IP address information.

[0192] If at least one of S-NSSAI or DNN is not included in the fixed IP address allocation provisioning parameters of the terminal, it can be obtained based on the AF identifier.

[0193] According to one embodiment of the present disclosure, a method for performing unified data management (UDM) may include: receiving a parameter provisioning update message including fixed IP address allocation parameters of a terminal from an NEF; and transmitting a query message to a unified data repository (UDR) to validate the fixed IP address allocation parameters of the terminal; receiving a response message to the query message; determining whether the fixed IP address allocation parameters of the terminal are authenticated based on the response message; and transmitting a message including the determination result to a network exposure function (NEF).

[0194] The method may further include the step of transmitting an update request message for updating the fixed IP address allocation parameters of the terminal to the UDR; and the step of receiving a response message regarding the update result from the UDR.

[0195] The fixed IP address allocation parameters of the above terminal may include at least one of GPSI (Generic Public Subscription Identifier), DNN (Data Network Name), S-NSSAI (Single Network Slice Selection Assistance Information), and fixed IP address information.

[0196] The above method further includes a step of transmitting a notification message to an SMF when a fixed IP address of the terminal is updated, and a PDU (Protocol Data Unit) session of the terminal can be released by the notification message.

[0197] According to one embodiment of the present disclosure, in a network exposure function (NEF) of a wireless communication system, the NEF includes: a transceiver; and at least one processor coupled with the transceiver, wherein the processor receives, from an application function (AF), a first parameter provisioning update request message including static Internet Protocol address (IP) allocation parameters of a terminal, determines whether the static IP address allocation parameters of the terminal are allowed based on the static IP address allocation parameters and configuration information of the terminal, and transmits a response message including information regarding whether the static IP address allocation parameters of the terminal are allowed and the reason based on the determination result.

[0198] The above response message may include an indicator indicating failure and information about the reason for failure if the terminal's fixed IP address allocation parameters are not allowed.

[0199] The at least one processor may determine whether to authorize the AF, and if the AF is authorized, transmit a second parameter provisioning update message including fixed IP address allocation parameters of the terminal to a unified data management (UDM), and receive a response message from the UDM including information regarding whether to allow the update request and the reason for the approval.

[0200] According to one embodiment of the present disclosure, in a unified data management (UDM) of a wireless communication system, the UDM includes: a transceiver; and at least one processor coupled with the transceiver, wherein the at least one processor receives a parameter provisioning update message including fixed IP address allocation parameters of a terminal from a network exposure function (NEF), transmits a query message to a unified data repository (UDR) to validate the fixed IP address allocation parameters of the terminal, receives a response message to the query message, determines whether to authenticate the fixed IP address allocation parameters of the terminal based on the response message, and transmits a message including the determination result to a network exposure function (NEF).

[0201] The at least one processor may transmit a notification message to the SMF when the fixed IP address of the terminal is updated, and the PDU (Protocol Data Unit) session of the terminal may be released by the notification message.

[0202] It should be noted that the configuration diagrams, exemplary diagrams of control / data signal transmission / reception methods, and exemplary diagrams of operating procedures illustrated in FIGS. 1 to 6 are not intended to limit the scope of the embodiments of the present disclosure. That is, not all components, entities, or operational steps described in FIGS. 1 to 6 should be construed as essential components for the implementation of the disclosure, and implementation may be performed within a scope that does not detract from the essence of the disclosure even if only some components are included.

[0203] The operations of the embodiments described above can be realized by providing a memory device storing the corresponding program code in any component within the device. That is, the control unit within the device can execute the operations described above by reading and executing the program code stored in the memory device through a processor or a CPU (Central Processing Unit).

[0204] The various components and modules of the entity or terminal device described in the present disclosure may be operated using hardware circuits, such as logic circuits based on complementary metal oxide semiconductors, firmware, software, and / or hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates, and application-specific semiconductors.

[0205] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

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

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

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

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

[0210] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. In a method for performing a network exposure function (NEF) in a wireless communication system, the method comprises: A step of receiving a first parameter provisioning update request message including static internet protocol address allocation parameters of a terminal from an application function (AF); A step of determining whether the fixed IP address allocation parameters of the terminal are allowed based on the fixed IP address allocation parameters and setting information of the terminal; and A method comprising a step of transmitting a response message including information on whether or not the fixed IP address allocation parameters of the terminal are allowed and the reason for doing so based on the judgment result.

2. In paragraph 1, A method wherein the above response message includes an indicator indicating failure and information on the reason for failure when the fixed IP address allocation parameters of the terminal are not allowed.

3. In paragraph 1, The above method, A step for determining whether to authorize the above AF; If the AF is permitted, a step of transmitting a second parameter provisioning update message including fixed IP address allocation parameters of the terminal to the UDM (unified data management); and A method further comprising the step of receiving a response message from the UDM including information regarding whether or not the update request is accepted and the reason for the acceptance.

4. In paragraph 3, The above method, A method further comprising the step of transmitting the response message if the AF is not permitted.

5. In paragraph 1, A method in which the fixed IP address allocation provisioning parameters of the above terminal include at least one of a generic public subscription identifier (GPSI), a data network name (DNN), a single network slice selection assistance information (S-NSSAI), and fixed IP address information.

6. In paragraph 5, A method for obtaining based on the identifier of the AF, when at least one of the S-NSSAI or the DNN is not included in the fixed IP address allocation provisioning parameters of the terminal.

7. In the method of performing UDM (unified data management), the method comprises: A step of receiving a parameter provisioning update message including fixed IP address allocation parameters of a terminal from NEF; and A step of sending a query message to a unified data repository (UDR) to validate the fixed IP address allocation parameters of the terminal; A step of receiving a response message to the above query message; A step of determining whether to authenticate the fixed IP address allocation parameters of the terminal based on the response message; and A method comprising the step of transmitting a message including the above decision result to a network exposure function (NEF).

8. In the 7th paragraph, the method, A step of transmitting an update request message to the UDR to update the fixed IP address allocation parameters of the terminal; and A method further comprising the step of receiving a response message regarding the update result from the UDR.

9. In paragraph 7, A method in which the fixed IP address allocation parameters of the terminal include at least one of GPSI (Generic Public Subscription Identifier), DNN (Data Network Name), S-NSSAI (Single Network Slice Selection Assistance Information) and fixed IP address information.

10. In the 7th paragraph, the method, If the fixed IP address of the terminal is updated, further comprising a step of sending a notification message to the SMF, A method in which the PDU (Protocol Data Unit) session of the terminal is released by the above notification message.

11. In the network exposure function (NEF) of a wireless communication system, the NEF is: transceiver; and At least one processor coupled to the transceiver, the processor comprising: Receive a first parameter provisioning update request message including static internet protocol address allocation parameters of the terminal from an application function (AF), Based on the fixed IP address allocation parameters and setting information of the terminal, it is determined whether the fixed IP address allocation parameters of the terminal are allowed. NEF, which transmits a response message including information on whether or not the fixed IP address allocation parameters of the terminal are allowed and the reason for doing so based on the above judgment result.

12. In paragraph 11, The above response message includes an indicator indicating failure and information about the reason for failure, if the terminal's fixed IP address allocation parameters are not allowed.

13. In paragraph 11, At least one processor, Determine whether to authorize the above AF, If the above AF is permitted, a second parameter provisioning update message including fixed IP address allocation parameters of the terminal is transmitted to the UDM (unified data management), NEF, which receives a response message from the UDM containing information regarding whether or not an update request is accepted and the reason for the acceptance.

14. In the UDM (unified data management) of a wireless communication system, the UDM is: transceiver; and At least one processor coupled to the transceiver, wherein the at least one processor comprises: Receive a parameter provisioning update message containing fixed IP address allocation parameters of the terminal from NEF, To validate the fixed IP address allocation parameters of the above terminal, a query message is sent to the UDR (unified data repository), Receive a response message to the above query message, Based on the above response message, determine whether to authenticate the fixed IP address allocation parameters of the terminal, A UDM that sends a message containing the above decision result to a network exposure function (NEF).

15. In paragraph 14, At least one processor, When the fixed IP address of the terminal is updated, a notification message is sent to SMF, UDM, in which the PDU (Protocol Data Unit) session of the terminal is released by the above notification message.

Images