Method and device for enhancing network selection accuracy in wireless communication system

Abstract

The present disclosure relates to a communication method and system for integrating a fifth generation (5G) communication system supporting a higher data rate than a fourth generation (4G) system with Internet of Things (IoT) technology. The present disclosure can be applied to smart services based on 5G communication technology and IoT-related technologies, such as smart homes, smart buildings, smart cities, smart cars, connected cars, health care, digital education, smart retail, safety and security services. A method and apparatus for selecting a network function entity from a plurality of network function entities are provided.

Description

Technical Field

[0001] The present disclosure relates to a method for increasing the accuracy of a network selection set in a wireless communication system. More specifically, the present disclosure relates to a method for selecting a network function entity from a plurality of network function entities in a next generation wireless communication system. Background Art

[0002] In order to meet the increased demand for wireless data services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "beyond 4G networks" or "post-LTE systems."

[0003] 5G communication systems are considered to be implemented in higher frequency (millimeter wave (mmWave)) bands (e.g., 60 GHz bands) in order to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technologies are discussed in 5G communication systems.

[0004] In addition, in the 5G communication system, system network improvements are being developed based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, collaborative communications, coordinated multi-point (CoMP), receiving-end interference cancellation, etc.

[0005] In 5G systems, hybrid frequency shift keying FSK and quadrature amplitude modulation QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0006] The Internet, a human-centered connected network in which humans generate and consume information, is now evolving toward the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE), which is a combination of IoT technology and big data processing technology connected to cloud servers, has emerged. As technical elements required to realize IoT, such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology", and "security technology", sensor networks, machine-to-machine (M2M) communication, machine-type communication (MTC), etc. have been studied recently. Such an IoT environment can provide intelligent Internet technology services to create new value for human life by collecting and analyzing data generated between connected things. Through the integration and combination between existing information technology (IT) and various industrial applications, IoT can be applied to various fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0007] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communications (MTC), and machine-to-machine (M2M) communications can be implemented through beamforming, MIMO, and array antennas. Cloud radio access networks (RANs) as an application of the above-mentioned big data processing technologies can also be considered as an example of the convergence between 5G technologies and IoT technologies.

[0008] With the development of various information technology (IT) technologies, network equipment has been developed into virtualized network functions (NF, hereinafter, can be used interchangeably with "network elements") by applying virtualization technology, and the virtualized NF can be implemented in the form of software without physical limitations to be installed / run in various types of clouds or data centers (DCs). In particular, NF can be freely expanded, scaled, started, or terminated according to service requirements, system capacity, or network load. It should be noted that even if these NFs are implemented in the form of software, NF does not exclude physical configuration, because NF should be basically driven on physical configuration, such as fixed equipment. In addition, NF can be implemented with only a simple physical configuration, that is, hardware.

[0009] In order to support various services in these various network structures, network slicing technology has been introduced. Network slicing is a technology that logically configures the network as a collection of network functions (NFs) that support specific services and separates the network from other slices. When receiving various services, one terminal can access two or more slices. Summary of the invention

[0010] Technical issues

[0011] Aspects of the present disclosure address at least the above-mentioned problems and / or disadvantages and provide at least the advantages described below. Therefore, one aspect of the present disclosure is to provide a method and apparatus for efficiently managing a network configured with network slices for supporting various services and selecting a specific network element from a plurality of network elements.

[0012] Technical Solution

[0013] According to one aspect of the present disclosure, a method performed by a service communication proxy (SCP) entity in a wireless communication system is provided. The method includes sending a network function (NF) registration request message including an SCP profile of the SCP entity to a network repository function (NRF) entity, and receiving an NF registration response message including a result of the registration of the SCP entity from the NRF entity, wherein the SCP profile is maintained at the NRF entity.

[0014] In the method, the SCP profile may include a NF type of the SCP entity, a NF identifier of the SCP entity, and an address of the SCP entity, and the NF type of the SCP entity may be set to SCP.

[0015] In the method, the SCP profile includes at least one of an identifier related to a network slice associated with the SCP entity, SCP domain information associated with other SCP entities interconnected with the SCP entity, and NF set information associated with the NF entity served by the SCP entity.

[0016] In addition, the method also includes sending an NF discovery request message associated with the producer NF entity to the NRF entity, and receiving an NF discovery response message including information associated with the producer NF entity from the NRF entity.

[0017] According to another aspect of the present disclosure, a service communication proxy (SCP) entity in a wireless communication system is provided. The SCP entity includes a transceiver and a controller coupled to the transceiver, and the controller is configured to: send a network function (NF) registration request message including an SCP profile of the SCP entity to a network storage function (NRF) entity, and receive an NF registration response message including a result of the registration of the SCP entity from the NRF entity, wherein the SCP profile is maintained at the NRF entity.

[0018] According to another aspect of the present disclosure, a method performed by a network storage function (NRF) entity in a wireless communication system is provided. The method includes receiving a network function (NF) registration request message including an SCP profile of the SCP entity from a service communication proxy (SCP) entity, maintaining the SCP profile based on the NF registration request message, and sending an NF registration response message including a result of the registration of the SCP entity to the SCP entity.

[0019] According to another aspect of the present disclosure, a network storage function (NRF) entity in a wireless communication system is provided. The NRF entity includes a transceiver and a controller coupled to the transceiver, and the controller is configured to: receive a network function (NF) registration request message including an SCP profile of a service communication proxy (SCP) entity from a SCP entity, maintain the SCP profile based on the NF registration request message, and send an NF registration response message including a result of the registration of the SCP entity to the SCP entity.

[0020] Beneficial Effects

[0021] According to the disclosed embodiments, by managing a plurality of network function entities in a set unit and by selecting a network function entity from the set, radio resources can be effectively used and various services can be effectively provided to users.

[0022] Furthermore, according to the embodiment, the user can efficiently access the network function entities by efficiently searching for a plurality of network function entities providing various services.

[0023] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals represent like parts:

[0025] Figure 1 A block diagram showing a configuration of a wireless communication system according to various embodiments of the present disclosure;

[0026] Figure 2 A block diagram showing a configuration of a network structure according to an embodiment of the present disclosure;

[0027] Figure 3 A message flow chart showing operations for enabling SSF to interwork with a network according to an embodiment of the present disclosure is shown;

[0028] Figure 4 A message flow diagram showing operations for interworking the SSF with the RAN;

[0029] Figure 5 A message flow diagram showing the operation of using SSF to effectively reflect the configuration update of RAN to the core network;

[0030] Figure 6 A block diagram showing a configuration of a network configuration according to another embodiment of the present disclosure;

[0031] Figure 7 A message flow diagram showing operations for interworking the SSN with the RAN and the core network according to an embodiment of the present disclosure;

[0032] Figure 8 A message flow chart of a method for managing slice information through SSN according to an embodiment of the present disclosure is shown;

[0033] Figure 9a A message flow chart showing the overall operation of selecting a slice and AMF using SSN or SSF according to an embodiment of the present disclosure;

[0034] Figure 9b A flowchart showing the operation of selecting a slice and an AMF by an SSN or SSF according to an embodiment of the present disclosure is shown;

[0035] Fig.10 A message flow chart showing a method for adding information about an SCP to an NRF according to an embodiment of the present disclosure;

[0036] Fig.11 A message flow chart showing a method for executing information about SCP in NRF by NF during a registration process according to an embodiment of the present disclosure;

[0037] Fig.12 A message flow chart showing a method in which a NF receives information of other NFs through an NRF according to an embodiment of the present disclosure;

[0038] Fig.13 A block diagram showing a configuration of a UE device according to an embodiment of the present disclosure;

[0039] Fig.14 A block diagram showing a configuration of a RAN device according to an embodiment of the present disclosure; and

[0040] Fig.15 A block diagram showing a configuration of a NF device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0041] Before proceeding to the following detailed description, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The terms "include" and "comprising" and their derivatives are meant to include, but are not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives are meant to include, include within, interconnect with, contain, contained within, connected to or connected with, coupled to, communicable with, collaborate with, interleave, juxtapose, be close to, be bound to or bound with, have, have the property of, have a relationship with, and the like; and the term "controller" means any device, system, or portion thereof that controls at least one operation. Such a device can be implemented in hardware, firmware, or software, or some combination of at least the two. The functionality associated with any particular controller can be centralized or distributed, whether locally or remotely.

[0042] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or a portion thereof suitable for implementation in a suitable computer-readable program. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disk (DVD) or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store data and then rewrite, such as rewritable optical disks or erasable memory devices.

[0043] Definitions for certain other words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior and future uses of such defined words and phrases.

[0044] Discussed below Figures 1 to 15 The various embodiments used to describe the principles of the present disclosure in this patent document are exemplary only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0045] The terms used in this disclosure are used to describe specific embodiments and do not limit the scope of other embodiments. Unless the context clearly states otherwise, words used in the singular form include plural, and plural also include singular. The terms used herein, including technical or scientific terms, have the same meaning as those generally understood by those of ordinary skill in the art. Among the terms used in this disclosure, the terms defined in general dictionaries can be interpreted as having the same or similar meanings as in the context of the relevant technology, and unless clearly defined in this disclosure, the terms are not interpreted as having ideal or overly formal meanings. In some cases, the terms defined in this disclosure cannot be interpreted as excluding embodiments of the present disclosure.

[0046] In various embodiments of the present disclosure described below, the hardware approach is described as an example. However, since various embodiments of the present disclosure include techniques using both hardware and software, various embodiments of the present disclosure do not exclude a software-based approach.

[0047] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In all the accompanying drawings, the same reference numerals represent the same or similar parts. In addition, in order to avoid blurring the subject matter of the present disclosure, the detailed description of the known functions and structures introduced herein may be omitted.

[0048] When describing the embodiments in this specification, descriptions of technical contents that are well known in the field of the present disclosure and are not directly related to the present disclosure will be omitted. This is to clearly describe the subject matter of the present disclosure by omitting any unnecessary descriptions without obscuring the subject matter.

[0049] Similarly, in the accompanying drawings, some components are shown in exaggerated or schematic form or are omitted. In addition, the size of each component does not fully reflect the actual size. In the accompanying drawings, the same reference numerals represent the same components.

[0050] According to the detailed description given below in conjunction with the accompanying drawings, these advantages and features of the present disclosure and the methods for achieving them will become more apparent. However, the present disclosure is not limited to the following embodiments and can be implemented in different forms. The embodiments of the present disclosure can fully disclose the present disclosure and are provided to enable those skilled in the art to fully understand the scope of the present disclosure, and the present disclosure is limited by the scope of the claims. Throughout the specification, the same reference numerals represent the same components.

[0051] Herein, it is understood that each box of the flowchart and the combination of the flowchart can be performed by computer program instructions. Because 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, the instructions executed by the processor of the computer or other programmable data processing equipment generate a device for performing the functions described in the box of the flowchart. In order to implement the function in a particular way, because these computer program instructions can be stored in a computer-available or computer-readable memory that can guide a computer or other programmable data processing equipment, the instructions stored in the computer-available or computer-readable memory can produce a product including an instruction device for performing the functions described in the box of the flowchart. Because the computer program instructions can be installed on a computer or other programmable data processing equipment, a series of operation steps are performed on the computer or other programmable data processing equipment, and a process executed by a computer is generated, and the instructions for executing the computer or other programmable data processing equipment can provide steps for performing the functions described in the box of the flowchart.

[0052] In addition, each block may represent a module, segment or part of a code including at least one executable instruction for performing a specific logical function. In addition, in several alternative execution examples, it should be noted that the functions described in the blocks may be executed regardless of the order. For example, two consecutively shown blocks may be executed substantially simultaneously according to the corresponding functions, or may be executed in the opposite order at times.

[0053] In such a case, the term "unit" used in the present embodiment means software or hardware components, such as field programmable gate array (FPGA) or application specific integrated circuit (ASIC), and performs any function. However, "-unit" is not limited to software or hardware. "-unit" can be configured to be stored in an addressable storage medium, and is configured to reproduce at least one processor. Therefore, "-unit" includes, for example, components, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays and variables such as software components, object-oriented software components, class components and task components. The function provided in the component and "-unit" can be performed by coupling a smaller number of component and "-unit" or by subdividing the component and "-unit" into additional component and "-unit". In addition, the component and "-unit" can be realized in a way that reproduces at least one CPU in a device or a secure multimedia card.

[0054] Hereinafter, the present disclosure relates to a method and apparatus for supporting various services in a wireless communication system. Specifically, the present disclosure describes a technology for supporting various services by supporting mobility of UE in a wireless communication system.

[0055] For the convenience of description, the terms used in the following description to identify access nodes, terms referring to network entities or network functions (NFs), terms referring to messages, terms referring to interfaces between network objects, and terms referring to various identification information are shown. Therefore, the present disclosure is not limited to the terms described later, and other terms referring to objects with equivalent technical meanings may be used.

[0056] In the following, for the convenience of description, the present disclosure uses the terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) and 5G standards. However, the present disclosure is not limited to the terms and names and can be equally applied to systems conforming to other standards.

[0057] In the present disclosure, the targets for exchanging information for access control and state management will be collectively referred to as NFs. NFs may be, for example, at least one of an access and mobility management function (hereinafter referred to as AMF) device, a session management function (hereinafter referred to as SMF) device, and a network slice selection function (hereinafter referred to as NSSF) device. However, even when NFs are actually implemented as instances (AMF instances, SMF instances, NSSF instances, etc.), the embodiments of the present disclosure are also applicable.

[0058] In the present disclosure, an instance may mean a state in which a specific NF exists in the form of software code, and in which physical or / and logical resources that can be allocated from a computing system are to be executed so as to perform the function of the NF in a physical computing system (e.g., a specific computing system existing on a core network). Therefore, each instance in all NFs, such as an AMF instance and an SMF instance, may mean that physical or / and logical resources can be allocated and used for NF operations from a specific computing system existing on a core network. As a result, when NF devices such as physical AMF and SMF exist, NF instances that receive allocation of physical or / and logical resources for NF operations and use physical or / and logical resources from a specific computing system existing on a network may perform the same operations.

[0059] Figure 1 A wireless communication system according to various embodiments of the present disclosure is shown.

[0060] refer to Figure 1 , as some nodes using a radio channel in a wireless communication system, a radio access node (RAN) 110 and a user equipment (UE) 120 are shown. Figure 1 Only one RAN 110 and one UE 120 are shown, but other RANs that are the same or similar to the RAN 110 may also be included. Figure 1Only the case where only one UE 120 communicates within one RAN 110 is shown. However, it is apparent that multiple UEs may actually communicate within one RAN 110.

[0061] The RAN 110 is a network infrastructure that provides wireless access to the UE 120. The coverage of the RAN 110 is defined as a certain geographic area based on the distance over which a signal can be transmitted ( Figure 1 RAN 110 may be referred to as “access point (AP)”, “eNodeB (eNB)”, “fifth generation node (5G node)”, “radio point”, “transmission / reception point (TRP)” or other terms having equivalent technical meanings, in addition to the RAN.

[0062] UE 120 is a device used by a user and performs communication with RAN 110 through a wireless channel. In some cases, UE 120 may operate without user participation. For example, UE 120 is a device that performs machine type communication (MTC) and may not be carried by a user. Figure 1 The illustrated UE 120 may include at least one user portable device and include at least one MTC. Figure 1 The UE 120 may be referred to as a “terminal”, “mobile station”, “subscriber station”, “remote terminal”, “wireless terminal”, “user equipment” or other terms having equivalent technical meanings.

[0063] The AMF device 131 may be a network entity that manages wireless network access and mobility of the UE 120. The SMF device 132 may be a network entity that manages a connection to a packet data network for providing packet data to the UE 120. The connection between the UE 120 and the SMF 132 may be a PDU session.

[0064] The user plane function (hereinafter, referred to as UPF) device 133 may be a gateway or a network entity that acts as a gateway for transferring packets transmitted and received by the UE 120. The UPF device 133 may be connected to a data network (DN) 140 connected to the Internet to provide a path for transmitting and receiving data between the UE 120 and the DN 140. Therefore, the UPF device 133 may route data to be transmitted through the Internet in packets transmitted by the UE 120 using the Internet data network.

[0065] The network slice selection function (NSSF) device 134 may be a network entity that performs the network selection operation (e.g., network slice selection operation) described in the present disclosure. The operation of the NSSF device 134 will be described in more detail in the figures described later.

[0066] The authentication server function (AUSF) device 151 may be equipment (network entity) that provides services for a subscriber authentication process.

[0067] The network exposure function (NEF) device 152 can access information for managing the UE 120 in the 5G network, and can be a network entity that can subscribe to the mobility management events of the UE, subscribe to the session management events of the UE, request session-related information, set the billing information of the corresponding UE, request to change the PDU session policy of the UE, and send small data about the UE.

[0068] The network storage function (NRF) device 153 may be a network entity (NF) having a function of storing state information of NFs and processing a request for finding NFs that other NFs can access.

[0069] The policy and charging function (hereinafter referred to as PCF) device 154 may be a network entity that applies a service policy and a charging policy of a mobile communication service provider and a policy for a PDU session to the UE 120 .

[0070] The unified data management (hereinafter referred to as UDM) device 155 may be a network entity that stores information about the subscriber and / or the UE 120 .

[0071] The application function (AF) device 156 may be a network entity (NF) having a function of providing services to users by interworking with a mobile communication network.

[0072] The service communication agent (SCP) device 157 is a NF that provides functions such as NF discovery for communication between NFs and message transmission between NFs. According to the provider's choice, the SCP device 157 can operate in a form integrated with the NRF device 153, and in such a case, the SCP device 157 includes the functions of the NRF device 153, or conversely, the NRF device 153 can include the functions of the SCP device 157.

[0073] In the following, for the convenience of description, the targets for exchanging information on access control and state management will be collectively referred to as NFs. NFs may be one of NF devices, such as access and mobility management function (hereinafter referred to as AMF) devices, session management function (hereinafter referred to as SMF) devices, and network slice selection function (NSSF) devices. However, even when NFs are actually implemented as instances (AMF instances, SMF instances, NSSF instances, etc.), the embodiments of the present disclosure are also applicable.

[0074] When the number of RANs in the network is large, or when the number of NFs (e.g., AMF) of the core network that need to receive configuration information of the RAN is large, signaling overload occurs, or there may be a situation where the network configuration information is inconsistent or conflicting due to differences in the transmission and processing time of the signaling. In addition, when the RAN needs to select the NF of the core network using a specific service, network configuration state, or slice information, it is inefficient to reflect all such information or changes to the RAN.

[0075] In the present disclosure, a technology is proposed that can be used to effectively exchange configuration information between the RAN and the core network and select an appropriate core network based on the service type or slice.

[0076] Figure 2 A block diagram showing a configuration of a network configuration according to an embodiment of the present disclosure.

[0077] The network configuration includes an NF (referred to as a slice support function (SSF) 230 in this disclosure) for sending information of the RAN 210 related to network slicing to the core network, or selecting an AMF 220 capable of supporting network slicing. In this embodiment, the SSF 230 operates as an NF of the core network and is interconnected with the RAN 210 as an N2' (or S1') interface, and is interconnected with other core network NFs 220 and 240 as a service-based interface (SBI).

[0078] Figure 3 A message flow chart of operations for enabling SSF to interwork with a network according to an embodiment of the present disclosure is shown.

[0079] refer to Figure 3 , SSF can perform NF registration process for providing and using services to NRF (or SCP) through SBI (301). SSF can transmit its NF profile (NF type = SSF, access address, instance ID, capability, supported PLMN ID, supported area, supported AMF set information, supported S-NSSAI information, etc.) to NRF.

[0080] The AMF may use a service provided by the SSF, or perform a process and operation for selecting the SSF, so as to send information to the SSF (302). When there is no previously selected SSF and the AMF does not have sufficient information for SSF selection, the AMF may perform an SSF discovery process through the NRF or SCP, and receive information for selecting the SSF.

[0081] The AMF may request a service to store the network slice information it supports in the SSF (303). The request message may include the NF instance ID of the AMF, a list of globally unique AMF IDs (GUAMIs) supported by the AMF, supported NSSAIs, and information about the NSSFs to be interconnected. The information about the NSSF may include one or more IP addresses of the NSSF or a fully qualified domain name (FQDN) that can be searched for the NSSF. Thereafter, the SSF may store the information of the corresponding AMF and use the information for the slice selection operation.

[0082] The SSF may send a response message to the AMF using the information received from the RAN, the response message including the network slice information supported by the RAN interconnected with the AMF (304). In this case, in order to selectively configure the target slice information available in the AMF in the information received from the RAN, the SSF may use the GUAMI information, the AMF area or the AMF area, and the AMF set information transmitted by the AMF. The AMF may store the information received from the SSF and use the information to add / update the NSSAI availability information to the NSSF, or to perform slice-related operations.

[0083] Figure 4 A message flow diagram illustrating operations for interworking of the SSF with the RAN is shown.

[0084] refer to Figure 4 , the operations for interworking between SSF and RAN are as follows: A new RAN is added to the network or the configuration of the RAN is updated (401).

[0085] When a new relationship and connection with the network configuration and management of the AMF is required, the RAN may perform a RAN establishment procedure, or when an existing connection exists, the RAN may perform a RAN configuration update procedure (402). In such a case, the request message sent by the RAN may include the name and identifier of the RAN, and a list of TAs supported by the RAN. The TA list may include one or more S-NSSAIs supported by the corresponding TA of each TA. In addition, the RAN may include in the request message an indicator indicating whether it supports a slice management selection operation using the SSF.

[0086] The AMF may send a response message to the request from the RAN. In this case, the response message may include configuration information of the AMF, and include the name of the AMF, a list of GUAMIs supported by the AMF, and information about the SSF to which the RAN will access (403). The response message sent by the AMF may include an indicator indicating whether the AMF supports the use of the slice management and selection functions of the SSF. The information of the SSF to which the RAN will access may be one or more IP addresses of the SSF or the FQDN where the SSF can be searched.

[0087] The RAN may store the SSF information together with the AMF information (404).

[0088] Through the above process, RAN can update or add RAN configuration information or slice-related information (supporting TA, S-NSSAI, etc.) (405).

[0089] When a new relationship and connection for slice configuration and management with the SSF is required, the RAN may perform a RAN establishment (NG' establishment) procedure, or when an existing connection exists, the RAN may perform a RAN configuration update procedure (406). In such a case, the request message sent by the RAN may include the name and identifier of the RAN, and a list of TAs supported by the RAN. The TA list may include one or more S-NSSAIs supported by the corresponding TA of each TA. In addition, the RAN may include information about the target AMF to which the corresponding information is to be applied in the request message. The AMF target information may be a GUAMI list, or AMF area information, or a combination of AMF area and collection information. The SSF that has received the information may store the slice information of the RAN, and when there is information that needs to be sent to the AMF as the target, the SSF may perform a procedure for transmitting the information.

[0090] Figure 5 A message flow diagram showing the operation of using SSF to effectively reflect the configuration update of RAN to the core network.

[0091] refer to Figure 5 , RAN may be newly added or configuration information or slice-related information (supporting TA, S-NSSAI, etc.) may be updated or added (501).

[0092] When a new relationship and connection for slice configuration and management with the SSF is required, the RAN may perform a RAN setup (NG' setup) procedure, or when an existing connection exists, the RAN may perform a RAN configuration update procedure (502). In such a case, the request message sent by the RAN may include the name and identifier of the RAN, and a list of TAs supported by the RAN. The TA list may include one or more S-NSSAIs supported by the corresponding TA of each TA. In addition, the RAN may include information about the target AMF to which the corresponding information is to be applied in the request message. The AMF target information may be a GUAMI list

[0093] or AMF area information, or a combination of AMF area and collection information.

[0094] SSF can store slice information of RAN.

[0095] When slice information is added / updated and needs to be notified to the core network, the SSF may perform operations for this (503). Specifically, the SSF may transmit information to a slice instance suitable for a slice within the core network, to an NSSF that selects an AMF, or to an NRF that helps select an NF within the core network. The SSF may determine whether network slices and TA information are added or updated based on information received from the RAN to be considered in the slice selection process. When the network configuration for slice selection is updated, the SSF may call a service for NSSAI availability update to the NSSF (or may be replaced by an NF that manages and looks up network status information, such as an NRF and SCP). Network slice selection assistance information (NSSAI) may be configured with one or more S-NSSAIs. The service request message may include a TAI list and an NSSAI to be added or updated. In addition, the service request message may include information about the AMF to which the slice information will be applied. The AMF target information may be a GUAMI list or AMF area information, or a combination of AMF area and collection information.

[0096] When the slice and slice supported area (TA) information needs to be updated according to the request of the SSF, the NSSF may update or add the slice and slice supported area (TA) information (504). In such a case, the data stored by the NSSF may be identified using the identifier (ID) of the requested SSF instance. The NSSF may determine the time point (time) at which the updated NSSAI availability is applied. In addition, the NSSF may use the previously stored information and the received information to update the authorized NSSAI availability information, which includes information about slices and areas that are allowed or not allowed to be used.

[0097] NSSF sends a response to the request from SSF, and when the authorized slice information (AuthorizedNssaiAvailability) is updated or added, NSSF can notify the information including this (505). In this case, in order to match the updated availability application time point with several NFs, NSSF can include time information in the response message and send it. The NF that has received the time information operates by applying the updated information from the time when the corresponding time condition is satisfied.

[0098] NSSF can update the NSSAI availability information of other AMF instances belonging to AMF as the target together (506). That is, NSSF can update the NSSAI availability information identified by the instance ID of the AMF included in the target AMF received from SSF together. Therefore, the authorized slice information of the corresponding AMF instance can be updated together, and when the NSSAI availability information or AuthorizedNssaiAvailability is updated or added, NSSF can send a message to each AMF instance to notify this. This can be performed using the NSSAI availability update notification service. In such a case, in order to match the updated availability application time point with other AMF instances, NSSF can include and send the corresponding time information in the message to be sent to the AMF instance. The AMF that has received the time information operates by applying the updated information starting when the corresponding time condition is met.

[0099] The AMF may send a response to the RAN's request (507).

[0100] Figure 6 A block diagram showing a configuration of a network configuration according to another embodiment of the present disclosure.

[0101] The network configuration includes a node (referred to as a slice support node (SSN) 630 in this disclosure) for sending information of the RAN 610 related to network slicing to the core network, or selecting an AMF 620 capable of supporting network slicing. In this embodiment, the SSN 630 operates as a node of the RAN network and is interconnected with other RANs as Xn' (or X2') interfaces, AMF 620 as N2' (or S1') interfaces, and other core network NF 640 as service-based interfaces (SBI).

[0102] Figure 7 A message flow diagram of operations for interworking the SSN with the RAN and the core network according to an embodiment of the present disclosure is shown.

[0103] refer to Figure 7, a new RAN may be added to the network, or the configuration of the RAN may be updated (701).

[0104] When a new relationship and connection with the network configuration and management of the SSN is required, the RAN performs an Xn' establishment procedure, or when an existing connection exists, the RAN performs a RAN configuration update procedure (702). In such a case, the request message sent by the RAN may include the name and identifier of the RAN, and a list of TAs supported by the RAN. The TA list may include one or more S-NSSAIs supported by the corresponding TA of each TA. In addition, the request message may include area information of the AMF to be interconnected by the RAN or information of the AMF to be targeted. The AMF target information may be a GUAMI list or AMF area information, or a combination of AMF area and set information. In addition, the RAN may include an indicator in the request message indicating whether it supports the slice management selection operation using the SSN.

[0105] The SSN sends a response to the request from the RAN, and in this case, the response includes the configuration information of the SSN, and may include the name of the SSN and the information of the target AMF to be interconnected with the SSN (703). The AMF target information may be a GUAMI list or AMF area information, or a combination of AMF area and collection information.

[0106] When a new relationship and connection with AMF for slice configuration and management is required, the SSN may perform an NG' establishment procedure, or when an existing connection exists, a RAN configuration update procedure (704) may be performed. In such a case, the request message sent by the SSN may include the name and identifier of the SSN, and a list of TAs supported by the SSN, and the list of TAs may include one or more S-NSSAIs supported by the corresponding TA of each TA. The TA and slice information provided by the SSN may be generated using information received from the RAN. The AMF that has received the information may store the slice information of the RAN, and when there is information that needs to be sent to other NFs, perform processing for transmitting the information.

[0107] The AMF sends a response message to the SSN, and in this case, the response may include information of the AMF, the name of the AMF, a GUAMI list supported by the AMF, and information of slices supported by the AMF (705). The slice information supported by the AMF may be used to select a slice or AMF to be accessed by the UE later. That is, the slice information may be used to select a slice or AMF to transmit a message (NAS message, such as an initial UE message, a registration request message, etc.) of the UE received from the RAN.

[0108] Figure 8A message flow chart of a method for managing slice information through SSN according to an embodiment of the present disclosure is shown.

[0109] refer to Figure 8 , RAN may be newly added or configuration information or slice-related information (supporting TA, S-NSSAI, etc.) may be updated or added (801).

[0110] When a new relationship and connection with the slice configuration and management of the SSN is required, the RAN may perform an Xn' establishment procedure, or when an existing connection exists, the RAN may perform a RAN configuration update procedure (802). In such a case, the request message sent by the RAN may include the name and identifier of the RAN, and a list of TAs supported by the RAN. The TA list may include one or more S-NSSAIs supported by the corresponding TA of each TA. In addition, the RAN may include information about the target AMF to which the corresponding information is to be applied in the request message. The AMF target information may be a GUAMI list or AMF area information, or a combination of AMF area and collection information. The SSN that has received the information may store the slice information of the RAN.

[0111] When slice information is added / updated and needs to be notified to the core network, the SSN can select AMF as the target (803). When the SSN includes only AMF area information in the information received from the RAN, the SSN can select an AMF set or AMF instance belonging to the AMF area.

[0112] The SSN may transmit the slice information to a slice instance suitable for the slice within the core network, to the NSSF that selects the AMF, or to the NRF that helps select the NF within the core network (804). The SSN may determine whether the network slice and TA information are added or updated based on the information received from the RAN to be considered in the slice selection process. When the network configuration for slice selection is updated, the SSN may call the NSSF for a service for NSSAI availability update (or may be replaced by a NF that manages and looks up network status information, such as an NRF and SCP) to the NSSF. The network slice selection assistance information (NSSAI) may be configured with one or more S-NSSAIs. The service request message may include a list of TAIs to be added or updated and the NSSAI. In addition, the service request message may include information about the AMF to which the slice information will be applied. The AMF target information may be a GUAMI list, AMF area information, or a combination of AMF area and collection information.

[0113] When the slice and slice support area (TA) information needs to be updated according to the request of the SSN, the NSSF may update or add the information (805). In such a case, the data stored by the NSSF may be identified using the identifier (ID) of the requested SSN instance. The NSSF may determine the point in time (time) at which the updated NSSAI availability is applied. In addition, the NSSF may use the previously stored information and the received information to update the authorized NSSAI availability information, which includes information about slices and areas that are allowed or not allowed to be used.

[0114] NSSF sends a response to the request of SSF, and when the authorized slice information (AuthorizedNssaiAvailability) is updated or added, NSSF can notify the information including this (806). In this case, in order to match the updated availability application time point with various NFs, NSSF can include the time information in the response message and send it. The NF that has received the time information operates by applying the updated information starting from when the corresponding time condition is satisfied.

[0115] NSSF can update the NSSAI availability information of other AMF instances belonging to AMF as the target together (807). That is, NSSF can update the NSSAI availability information identified by the instance ID of the AMF included in the target AMF received from SSF together. Therefore, the authorized slice information of the corresponding AMF instance can be updated, and when the NSSAI availability information or the authorized AuthorizedNssaiAvailability is updated or added, the NSSF can send a message to each AMF instance to notify this. This can be performed using the NSSAI availability update notification service. In such a case, in order to match the updated availability application time point with other AMF instances, NSSF can include and send the corresponding time information in the message to be sent to the AMF instance. The AMF that has received the time information operates by applying the updated information starting when the corresponding time condition is met.

[0116] The AMF may send a response to the RAN's request (808).

[0117] Figure 9a A message flow chart showing the overall operation of selecting a slice and AMF using SSN or SSF according to an embodiment of the present disclosure is shown. Figure 9b A flowchart of the operation of selecting slices and AMF by SSN or SSF according to an embodiment of the present disclosure is shown.

[0118] First, refer to Figure 9a The whole process of selecting slices and AMF using SSN (or SSF) according to the present disclosure is described.

[0119] The UE may send an RRC message including a NAS message for registration to the RAN (901). In this case, in order to use the service, the UE may include slice information (NSSAI) to access as an AS layer or NAS layer parameter.

[0120] The RAN may select an AMF using an identifier (ID) used by the UE, slice information that the UE intends to access, and configuration information. When the RAN cannot select an AMF using slice information, or when the AS layer slice information is not included in a message sent by the UE (902), the RAN may select an SSN (or SSF) and send an initial UE message sent by the UE to the SSN (or SSF) (903).

[0121] The SSN (or SSF) may receive subscription information from the UDM as needed, and in such a case, may receive slice information applicable to the subscriber, subscribed S-NSSAI, etc. (904). When the UE message includes slice information selected by the UE (e.g., requested NSSAI and / or subscribed NSSAI), the SSN may take this into account and select the AMF taking into account the subscription information received from the UDM (905). When the AMF is selected, the SSN may send a rerouting NAS message to the RAN, the rerouting NAS message including information that may identify the AMF (e.g., AMF information, AMF set information, or GUAMI) and the initial UE message (or registration request) sent by the UE (906).

[0122] The RAN may use the information received from the SSN (or SSF) to reselect an AMF to send the UE's request (907). When an AMF is designated and interworking with the corresponding AMF is possible, the RAN may select the corresponding AMF. When receiving the AMF set information, the RAN may select an AMF in the AMF set. The RAN retransmits the UE message to the selected AMF.

[0123] Figure 9b Shown according to the reference Figure 9a The described embodiments are related to the operation of SSN (or SSF) of time series streams.

[0124] Reference Figure 9b , SSN (or SSF) may receive an RRC message including a NAS message for registration sent by the UE to the RAN from the RAN (921). The UE message sent by the UE to the RAN may include a subscriber identifier (ID), slice information that the UE intends to access, and configuration information.

[0125] If necessary, the SSN (or SSF) may receive the subscription information of the UE from the UDM using the information (e.g., subscriber identifier) ​​included in the UE message received from the RAN (922). In this case, the slice information of the S-NSSAI applicable to the subscriber and subscription may be received.

[0126] When the UE message includes slice information selected by the UE (e.g., requested NSSAI and / or subscribed NSSAI), the SSN (or SSF) may consider the slice information and, taking into account the subscription information received from the UDM, select the AMF to provide the slice to the UE (923).

[0127] When the AMF selection is completed, the SSN (or SSF) may send a rerouting NAS message in response to the UE's initial request message to the RAN, the message including information that may identify the AMF (e.g., AMF information, AMF set information, or GUAMI) and a UE message (initial UE message or registration request) sent by the UE (924).

[0128] The RAN having received the rerouting NAS message uses the information included in the message to identify the AMF serving the UE and sends the UE's initial request message to the selected AMF; thus, communication between the UE and the selected AMF can be initiated (925).

[0129] Fig.10 A message flow chart of a method for adding information about an SCP to an NRF according to an embodiment of the present disclosure is shown.

[0130] Reference Fig.10In order to register the information of the SCP and send the information of the SCP when requesting other NFs, the SCP may send a request message (1001) requesting NF registration (new) or update (change) to the NRF. In such a case, the request message sent by the SCP may include an SCP profile (NF ID and address of the SCP, communication mode of the SCP, connection information with other SCPs, and NF information interconnected with the SCP), which includes parameters, features and configuration information of the SCP, and feature information supported by functions supported by the SCP. The supported feature information may include whether each of indirect communication, entrusted discovery, and binding indications of the SCP is supported. The supported features may be included in a part of the NF profile, or may be separated from a part of the NF profile and included in the request message in a separate data format. In addition, when the SCP belongs to a specific NW slice, the SCP may include one or more identifiers (S-NSSAI) of the slice as the target. The interconnected NF information and SCP information may include the ID and address of the interconnected NF / SCP, and include information indicating the connection order between each NF / SCP in a network configuration interconnected by multiple hops. When requesting NF registration / update to the NRF, the registration request can be processed by specifying its type (NF type) as SCP, treating SCP as one NF type, or can be processed as a separate SCP registration / update request.

[0131] The NRF may use the received information to store / update the information of the SCP (1002) and send a response to the request to the SCP (1003). The response message may include updated supported features that can be used in the network currently registered by the SCP. The content and message configuration that may be included in the supported features may be the same as the content and message configuration included in the request message. In addition, the response of the NRF may include information that is additionally applied when the SCP communicates with other NFs (profiles of other connected SCPs, supported features, etc.).

[0132] When the NRF receives a discovery request for the SCP or a discovery request for configuration information about a specific slice from other NFs, the NRF can use the information of the stored SCP to provide information (1004). When the NRF receives a discovery request for a specific NF or NF service from the NF, if the candidate NF or NF service selected according to the request of the NRF has an interconnected SCP, the NRF can transmit the information of the selected NF or NF service and the SCP together in response (SCP ID, SCP address, operation communication mode). When the connection between the NF and the SCP is configured with multiple hops in the network configuration, from the perspective of the NF (or SCP) requesting discovery, the discovery response can transmit only information about the NF (or SCP) of the next hop, or can include all information of the NF (or SCP) on the transmission path including the sequence of each hop.

[0133] Fig.11 A message flow chart showing a method for executing information about SCP in NRF by NF during a registration process according to an embodiment of the present disclosure.

[0134] refer to Fig.11 NF can receive the setting information of the SCP interconnected with it (SCP ID, SCP address, SCP support functions, etc.) (1101). This information can be obtained by receiving a message from the SCP, obtained through the OAM system, or stored in the NF setting information.

[0135] NF can register its information and the information of interconnected SCPs, and send NF registration (new) or update (change) request to NRF so that its information can be sent when requesting other NFs (1102). In such a case, the request message sent by NF to NRF can include not only its NF profile, but also the profile of SCP (NF ID of SCP, address of SCP, communication mode of SCP, connection information with other SCPs, etc.), and the profile of SCP includes parameters, features and setting information of SCP interconnected with NF, and supported feature information supported by SCP. Supported feature information may include whether to support each of indirect communication, entrusted discovery, and binding indication of SCP. Supported features may be included in a part of SCP profile, or may be separated from a part of SCP profile and included in the request message in a separate data format. In addition, when SCP belongs to a specific NW slice, SCP may include one or more identifiers of the slice as the target. Information of interconnected SCPs may include ID and address of interconnected SCPs, and may include information indicating the connection order between NF / SCPs in a network configuration of multi-hop interconnection. The profile of the SCP may be included as part of the NF profile of the NF, or may be classified as a separate data type to be included in the request message.

[0136] The NRF may store / update information of the NF and interconnected SCPs using the information received from the NF (1103), and send a response to the NF request (1104).

[0137] When the NRF receives a discovery request for the SCP or a discovery request for configuration information about a specific slice from other NFs, the NRF can use the stored SCP information to provide information (1105). Optionally, when the NRF receives a discovery request for a specific NF or NF service from the NF, if the candidate NF or NF service selected according to the request of the NRF has an interconnected SCP, the NRF can transmit information about the SCP (SCP ID, SCP address, operation communication mode) together with the selected NF or NF service information in response. When the connection between the NF and the SCP is configured with multiple hops in the network configuration, from the perspective of the NF (or SCP) requesting discovery, the discovery response can only transmit information about the NF (or SCP) of the next hop, or can include all information about the NF (or SCP) on the transmission path including the sequence of each hop.

[0138] Fig.12 A message flow chart showing a method in which a NF receives information of other NFs through an NRF according to an embodiment of the present disclosure.

[0139] refer to Fig.12 , one NF of the network (which may operate as a consumer or a producer) may send a discovery request (1201) to the NRF for finding or selecting other NFs or NF services or receiving information. In such a case, the request message sent by the NF may include information about the NF or NF service that is the discovery target, supported feature information supported by the requesting NF, and information indicating that SCP information is additionally requested. The supported feature information may include indirect communication, delegated discovery, SM context transfer, binding indication, and whether each NF set is supported as an enhancement to SBA in the NF support function. In addition, when the requesting NF needs to receive SCP information about a specific NW slice, the requesting NF may include an identifier of the slice that is the target in the request message.

[0140] The NRF may search for an NF or NF service that satisfies the conditions of the NF request (1202) and send a response (1203). When the request message received by the NRF includes information that explicitly notifies that SCP information is requested together, the response message may include information about the SCP that can be used between the requested NF and the selected NF or NF service and the supported features of the SCP (SCP address, NF ID, identification of supported slices of the SCP, connection relationship between the SCP and other SCPs, etc.), the communication mode of the NF using the SCP (one of modes A, B, C, and D), whether to use indirect communication, and whether to use delegated discovery. Even if there is no information explicitly indicating that SCP-related information is requested together in the NF request message, when the supported features of the requesting NF include whether to use a communication mode or indirect communication using SCP and whether to use delegated discovery, the NRF may determine whether the SCP can be used based on the message, and include the information related to the SCP in the response message and transmit it. When the connection between NFs and SCPs in the network configuration is configured with multiple hops, from the perspective of the NF (or SCP) requesting discovery, the discovery response can transmit only information about the NF (or SCP) of the next hop, or include all information about the NF (or SCP) on the transmission path including the sequence of each hop.

[0141] The NF may store the information received from the NRF and then use the SCP-related information (whether to use SCP, SCP address, NF ID, indirect communication, whether to use delegated discovery, etc.) received when communicating with the NF or NF service received in response (not shown). When the response received from the NRF includes information that there is no SCP or does not include SCP information, the NF may assume that there is no SCP in subsequent operations.

[0142] Fig.13 A block diagram showing the structure of a UE according to an embodiment of the present disclosure is shown.

[0143] Reference Fig.13 , the UE may include a transceiver 1310, a UE controller 1320, and a storage unit 1330. In the present disclosure, the UE controller 1320 may be defined as a circuit, an application specific integrated circuit, or at least one processor.

[0144] The transceiver 1310 may send signals to and receive signals from other network entities. The transceiver may receive system information from the RAN, for example, and receive synchronization signals or reference signals.

[0145] According to the embodiments proposed in the present disclosure, the UE controller 1320 may control the overall operation of the UE. For example, the UE controller may control the signal flow between the blocks to perform operations according to the above-mentioned figures and flowcharts. Specifically, the UE controller may operate according to control signals from the RAN and exchange messages or signals with the UE and / or network entities.

[0146] The storage unit 1330 may store at least one of information transmitted and received by the transceiver 1310 and information generated by the UE controller 1320 .

[0147] Fig.14 A block diagram showing the structure of a RAN according to an embodiment of the present disclosure. Fig.14 The RAN shown may include the SSN described above.

[0148] Reference Fig.14 , the RAN may include a transceiver 1410, a RAN controller 1420, and a storage unit 1430. In the present disclosure, the RAN controller 1420 may be defined as a circuit, an application specific integrated circuit, or at least one processor.

[0149] The transceiver 1410 may send signals to other network entities and receive signals from other network entities. The transceiver may send, for example, system information to the UE, send a synchronization signal or a reference signal, and receive information from the NF for providing a service to the UE.

[0150] According to the embodiments proposed in the present disclosure, the RAN controller 1420 may control the overall operation of the RAN. For example, the RAN controller may control the signal flow between the blocks to perform operations according to the above-mentioned figures and flowcharts. Specifically, the RAN controller may exchange messages or signals with the UE, the RAN, and / or the network entity.

[0151] The storage unit 1430 may store at least one of information transmitted and received by the transceiver and information generated by the RAN controller.

[0152] Fig.15 A block diagram showing the structure of a NF (including NF instances) according to an embodiment of the present disclosure. Fig.15 The NF shown may include at least one of the above-mentioned SSF, AMF, NSSF, NRF, SCP, and UDM, and is not limited to a specific NF.

[0153] Reference Fig.15 , the NF may include a transceiver 1510 , a NF controller 1520 , and a storage unit 1530 .

[0154] The transceiver 1510 may send and receive signals with other network entities. For example, the transceiver may send system information to the RAN and send synchronization signals or reference signals.

[0155] According to an embodiment proposed in the present disclosure, the NF controller 1520 may control the overall operation of the NF.

[0156] The storage unit 1530 may store at least one of information transmitted and received by the transceiver and information generated by the RAN controller.

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

[0158] When implemented with software, a computer-readable storage medium storing at least one program (software module) may be provided. At least one program stored on the computer-readable storage medium may be configured to be executed by at least one processor in an electronic device. At least one program may include instructions that enable an electronic device to perform a method according to the embodiments described in the claims and / or this disclosure.

[0159] Such a program (software module, software) may be stored in a non-volatile memory including a random access memory (RAM) and a flash memory, a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), a magnetic disk storage device, a compact disk ROM (CD-ROM), a digital versatile disk (DVD), other forms of optical storage devices, and a cassette tape. Alternatively, the program may be stored in a memory configured with a combination of part or all thereof. In addition, each constituent memory may include a plurality of.

[0160] In addition, the program can be stored in an attachable storage device, which can be accessed through a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN) or a storage area network (SAN), or a communication network configured with a combination thereof. Such a storage device can be connected to the device that performs the disclosed embodiment through an external port. In addition, an independent storage device on a communication network can access the device that performs the disclosed embodiment.

[0161] In the above specific embodiments of the present disclosure, the components included in the present disclosure are expressed in the singular or plural according to the specific embodiments proposed. However, for the case proposed for the convenience of description, the singular or plural expression is appropriately selected, and the present disclosure is not limited to the singular or plural constituent elements, and even the constituent elements expressed in the plural may be configured in the singular, or even the constituent elements expressed in the singular may be configured in the plural.

[0162] Although the present disclosure has been described with various embodiments, various changes and modifications may occur to those skilled in the art. The present disclosure is intended to encompass such changes and modifications as fall within the scope of the appended claims.

Claims

1. A method performed by a service communication agent SCP entity in a wireless communication system, the method comprising: Sending a network function NF registration request message including the SCP profile of the SCP entity to the network storage function NRF entity; and receiving, from the NRF entity, a NF registration response message including a result of the registration of the SCP entity, wherein the SCP profile is maintained at the NRF entity, and The SCP profile includes information associated with at least one other SCP entity connected to the SCP entity.

2. The method according to claim 1, wherein: The SCP profile also includes the NF type of the SCP entity, the NF identifier of the SCP entity, and the address of the SCP entity, and Among them, the NF type of the SCP entity is set to SCP.

3. The method according to claim 1, wherein: The SCP profile also includes at least one of an identifier related to a network slice associated with the SCP entity and NF information associated with at least one NF entity served by the SCP entity.

4. The method according to claim 1, further comprising: Sending a NF Discovery Request message associated with the producer NF entity to the NRF entity; and An NF Discovery Response message including information associated with a producer NF entity is received from the NRF entity.

5. A service communication agent SCP entity in a wireless communication system, the SCP entity comprising: a transceiver configured to transmit and receive signals; and A controller is coupled to the transceiver and is configured to: Sending a network function NF registration request message including the SCP profile of the SCP entity to the network storage function NRF entity, and receiving, from the NRF entity, a NF registration response message including a result of the registration of the SCP entity, wherein the SCP profile is maintained at the NRF entity, and The SCP profile includes information associated with at least one other SCP entity connected to the SCP entity.

6. The SCP entity according to claim 5, wherein: The SCP profile also includes the NF type of the SCP entity, the NF identifier of the SCP entity, and the address of the SCP entity, and Among them, the NF type of the SCP entity is set to SCP.

7. The SCP entity according to claim 5, wherein: The SCP profile also includes at least one of an identifier related to a network slice associated with the SCP entity and NF information associated with at least one NF entity served by the SCP entity.

8. The SCP entity of claim 5, wherein: The controller is configured as: Sending a NF Discovery Request message associated with the Producer NF entity to the NRF entity, and An NF Discovery Response message including information associated with a producer NF entity is received from the NRF entity.

9. A method performed by a network storage function (NRF) entity in a wireless communication system, the method comprising: receiving a network function NF registration request message including an SCP profile of the SCP entity from a serving communication proxy SCP entity; Maintaining SCP profile based on NF registration request message; and sending a NF registration response message including the result of the registration of the SCP entity to the SCP entity, and The SCP profile includes information associated with at least one other SCP entity connected to the SCP entity.

10. The method according to claim 9, in, The SCP profile also includes the NF type of the SCP entity, the NF identifier of the SCP entity, and the address of the SCP entity. The NF type of the SCP entity is set to SCP. The SCP profile also includes at least one of an identifier related to a network slice associated with the SCP entity and NF information associated with at least one NF entity served by the SCP entity.

11. The method according to claim 9, further comprising: receiving, from the SCP entity, a NF discovery request message associated with a producer NF entity; and An NF discovery response message including information associated with the producer NF entity is sent to the SCP entity.

12. A network storage function (NRF) entity in a wireless communication system, the NRF entity comprising: a transceiver configured to transmit and receive signals; and A controller is coupled to the transceiver and is configured to: receiving a network function NF registration request message including an SCP profile of the SCP entity from a serving communication proxy SCP entity, Maintaining the SCP profile based on the NF Registration Request message, and sending a NF registration response message including the result of the registration of the SCP entity to the SCP entity, and The SCP profile includes information associated with at least one other SCP entity connected to the SCP entity.

13. The NRF entity according to claim 12, wherein: The SCP profile also includes the NF type of the SCP entity, the NF identifier of the SCP entity, and the address of the SCP entity, and Among them, the NF type of the SCP entity is set to SCP.

14. The NRF entity according to claim 12, wherein: The SCP profile also includes at least one of an identifier related to a network slice associated with the SCP entity and NF information associated with at least one NF entity served by the SCP entity.

15. The NRF entity according to claim 12, wherein: The controller is configured as: receiving, from the SCP entity, an NF Discovery Request message associated with a producer NF entity, and An NF discovery response message including information associated with the producer NF entity is sent to the SCP entity.

Images