Methods and apparatus for dynamic network slice selection in wireless communication systems
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-01-16
- Publication Date
- 2026-08-14
Smart Images
Figure CN122580904A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to methods and apparatus for dynamically selecting network slices in a wireless communication system. Background Technology
[0002] To meet the ever-increasing demand for wireless data traffic since the commercialization of fourth-generation (4G) communication systems, efforts have been focused on developing advanced fifth-generation (5G) or near-5G communication systems. For this reason, 5G or near-5G communication systems are also referred to as super-fourth-generation (4G) network communication systems or post-Long Term Evolution (LTE) systems. To achieve higher data transmission rates, the use of ultra-high frequency (millimeter-wave (mmWave)) bands (e.g., the 60 GHz band) is being considered for implementing 5G communication systems. To reduce propagation loss of radio waves in the ultra-high frequency band and increase the transmission range of radio waves, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are being discussed. To improve system networks, technologies are also being developed in 5G communication systems for advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), receiver interference cancellation, and more. In addition, advanced coding and modulation (ACM) methods, such as hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC), are being developed in 5G systems, as well as advanced access technologies, such as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA).
[0003] Simultaneously, the internet is evolving from a human-driven network of connections where humans create and consume information into a distributed network of the Internet of Things (IoT) where entities or things send, receive, and process information without human intervention. The Internet of Everything (IoE) technology has also emerged, combining technologies such as big data processing via connections to cloud servers with IoT technologies. To realize IoT, various technologies are needed, including sensing technologies, wired / wireless communication and network infrastructure, service interface technologies, and security technologies. Recently, technologies such as sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) for connecting things are being researched. In the IoT environment, intelligent information (IT) services that create new value for human life can be provided by collecting and analyzing data generated from connected things. Through the integration and combination of existing IT technologies with various industrial applications, IoT can be applied to a wide range of fields, such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.
[0004] In this regard, efforts are being made to apply 5G communication systems to IoT networks. For example, technologies related to sensor networks, M2M, and MTC are being implemented using 5G communication technologies (such as beamforming, MIMO, and array antenna schemes). Cloud radio access networks (cloud RAN), as an application of the aforementioned big data processing technologies, can serve as an example of the integration of 5G and IoT technologies.
[0005] Furthermore, efforts are underway to develop a sixth-generation (6G) communication system that is approximately five times faster than the highest speed of 5G. Therefore, implementation in higher frequency bands than 5G is being considered to achieve high data transmission rates.
[0006] With the advancement of the aforementioned wireless communication systems, a variety of services can be provided, and in particular, the demand for session continuity support technologies to provide seamless services is constantly growing. Summary of the Invention
[0007] Technical issues
[0008] Embodiments of this disclosure can provide methods and apparatus for effectively providing services in wireless communication systems.
[0009] Technical solution
[0010] As a technical means to achieve the above-mentioned technical objectives, a method for operating the Access and Mobility Management Function (AMF) in a wireless communication system is disclosed, including sending a subscription information request message corresponding to a User Equipment (UE) to a Unified Data Management (UDM), receiving a notification message about updated subscription information from the UDM, determining whether to update UE configuration information related to a network slice of the UE, sending updated UE configuration information to the UE when the UE configuration information related to the network slice is updated, and receiving a message from the UE indicating that the configuration information update is complete.
[0011] As a technical means to achieve the above-mentioned technical objectives, a method for operating Unified Data Management (UDM) in a wireless communication system is disclosed, comprising receiving a subscription information request message corresponding to a User Equipment (UE) from an Access and Mobility Management Function (AMF), receiving a message including information for network slice selection or reselection from an Application Function (AF), identifying a Subscription Permanent Identifier (SUPI) associated with the UE, sending a request message to a Unified Data Repository (UDR) to obtain subscriber information of the SUPI, obtaining the subscriber information from the UDR, sending a message to the UDR to update the subscriber information, sending a notification message to the AMF regarding the updated subscription information, receiving a subscription information request message for the UE from the AMF, and sending the updated subscription information to the AMF in response to the subscription information request message.
[0012] As a technical means to achieve the above-mentioned technical objectives, a method for operating a policy control function (PCF) in a wireless communication system is disclosed, comprising receiving a subscription information request message corresponding to a user equipment (UE) from an access and mobility management function (AMF), receiving a message including information for network slice selection or reselection from an application function (AF), sending a request message to a unified data repository (UDR) for obtaining subscriber information of a subscription permanent identifier (SUPI) associated with the UE, obtaining the subscriber information from the UDR, sending a message for updating the subscriber information to the UDR, sending a notification message about the updated subscription information to the AMF, receiving a policy information request message for the UE from the AMF, identifying the subscription information stored in the UDR based on the policy information request message, and sending the updated subscription information to the AMF in response to the policy information request message. Attached Figure Description
[0013] Figure 1 The structure of a fifth-generation (5G) system according to an embodiment of this disclosure is shown.
[0014] Figure 2 A dynamic network slice selection method in a wireless communication system according to an embodiment of the present disclosure is illustrated.
[0015] Figure 3 A dynamic network slice selection method in a wireless communication system according to an embodiment of the present disclosure is illustrated.
[0016] Figure 4 A network entity according to an embodiment of this disclosure is shown. Detailed Implementation
[0017] The following description will omit technical details that are well-known in the art but not directly related to this disclosure. By omitting content that may obscure the subject matter of this disclosure, the subject matter will be more clearly understood.
[0018] The effects and features of this disclosure, as well as the methods for implementing them, will be clearly understood by referring to the embodiments described in detail below with reference to the accompanying drawings. However, this disclosure is not limited to the embodiments described below, but can be implemented in many different forms.
[0019] In this document, terms used to identify access nodes, network entities, messages, interfaces between network entities, and various types of identification information are examples provided for ease of explanation. Therefore, this disclosure is not limited to the terms used herein, but different terms may be used to refer to items that have the same technical meaning.
[0020] In the following description, for ease of explanation, some terms and names defined by the 3GPP New Radio (3GPP NR) will be used. However, this disclosure is not limited to these terms and definitions, but can be applied equivalently to systems conforming to other standards. In this disclosure, a base station may refer to a gNB. Furthermore, the term 'terminal' may refer not only to mobile phones, NB-IoT devices, and sensors, but also to other wireless communication devices.
[0021] In the following description, a base station is an entity used to perform resource allocation for terminals, and can be at least one of gNB, eNB, Node B, base station (BS), radio access unit, base station controller, or network node. A terminal can include user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. However, it is not limited to these.
[0022] This disclosure can be applied to 3GPP NR (i.e., the 5G mobile communication standard). This disclosure can be applied to smart services based on 5G communication and Internet of Things (IoT) related technologies, such as smart homes, smart buildings, smart cities, smart cars, connected cars, healthcare, digital education, smart retail, and security and safety services.
[0023] Wireless communication systems are evolving from early systems that provided voice-oriented services to broadband wireless communication systems that provide high data rates and high-quality packet data services, such as 3GPP High-Speed Packet Access (HSPA), Long Term Evolution (LTE) or Evolved Universal Terrestrial Radio Access (E-UTRA), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2 High-Speed Packet Data (HRPD), Ultra Mobile Broadband (UMB), and the IEEE 802.16e communication standard.
[0024] As a representative example of this type of broadband wireless communication system, the LTE system employs Orthogonal Frequency Division Multiplexing (OFDM) for the downlink (DL) and Single-Carrier Frequency Division Multiple Access (SC-FDMA) for the uplink (UL). UL refers to the radio link used by the UE or MS to transmit data or control signals to the eNode B or BS, while DL refers to the radio link used by the BS to transmit data or control signals to the UE or MS. This multiple access scheme allocates and operates the time-frequency resources used to carry data or control information for each user without overlap, i.e., maintaining orthogonality, thereby distinguishing the data or control information for each user.
[0025] As the future communication system following LTE, 5G communication systems need to freely reflect various demands from users and service providers, thus supporting services that simultaneously meet diverse needs. Services considered for 5G communication systems may include enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLL), among others.
[0026] Although the following embodiments of this disclosure will now be described with a focus on, for example, LTE, LTE-A, LTE Pro, or fifth-generation (5G) (or new radio (NR), next-generation mobile communication) systems, they can be equivalently applied to other communication systems with similar technical backgrounds or channel types. Furthermore, the embodiments of this disclosure can also be applied to other communication systems with some modifications, without departing significantly from the scope of this disclosure as judged by one of ordinary skill in the art.
[0027] Descriptions of some well-known techniques that may obscure this disclosure will be omitted where necessary. Embodiments of this disclosure will now be described with reference to the accompanying drawings.
[0028] Figure 1 The structure of a 5G system according to various embodiments of the present disclosure is shown.
[0029] A 5G mobile communication network consists of 5G user equipment (5G UE) or terminals, a 5G radio access network (5G RAN) (e.g., base stations (BS), 5G node Bs (gNB), evolved Node Bs (eNB), etc.), and a 5G core network. The 5G core network can consist of network functions (NFs) such as Access and Mobility Management Functions (AMF) providing mobility management functions, Session Management Functions (SMF) providing session management functions, User Plane Functions (UPF) for data transmission, Policy Control Functions (PCF) providing policy control functions, Unified Data Management (UDM) providing functions for managing data such as subscriber data and policy control data, and Unified Data Repository (UDR) storing data from many different NFs. The 5G core network can also include other NFs, such as Network Slice Selection Function (NSSF), Network Data Analysis Function (NWDAF), Application Functions (AF), Data Network (DN), and Network Slice Admission Control Function (NSACF).
[0030] In the 3GPP system, the conceptual link connecting NFs in a 5G system is defined as a reference point. For example, reference... Figure 1 The reference points included in the 5G system architecture can be as follows: - N1: Reference point between UE and AMF - N2: Reference point between (R)AN and AMF - N3: Reference point between (R)AN and UPF - N4: Reference point between SMF and UPF - N5: Reference point between PCF and AF - N6: Reference point between UPF and DN - N7: Reference point between SMF and PCF - N8: Reference point between UDM and AMF - N9: Reference point between the two core UPFs.
[0031] - N10: Reference point between UDM and SMF
[0032] - N11: Reference point between AMF and SMF
[0033] - N12: Reference point between AMF and Authentication Server Function (AUSF)
[0034] - N13: Reference point between UDM and AUSF
[0035] - N14: Reference point between the two AMFs
[0036] - N15: Reference point between PCF and AMF in non-roaming scenarios, and reference point between PCF and AMF in the surveyed network in roaming scenarios.
[0037] In 5G systems, network slicing refers to the technology and architecture that enables various virtualized and independent logical networks to be implemented within a single physical network. Network operators provide services by configuring virtual end-to-end networks called network slices to meet the specific needs of specific services or applications. In this context, network slices can be distinguished by an identifier called Single Network Slice Selection Auxiliary Information (S-NSSAI). During UE registration, the network sends the UE a set of allowed slices (e.g., allowed NSSAIs), and the UE sends and receives application data through a Protocol Data Unit (PDU) session established with one S-NSSAI (i.e., a network slice) from that set.
[0038] Figure 2 A dynamic network slice selection method in a wireless communication system according to an embodiment of the present disclosure is illustrated. Figure 2 The present disclosure illustrates a method for providing network slice selection information during the registration process according to an embodiment of the present disclosure. Figure 2 The operations shown are not all necessary components; some operations may be omitted in some embodiments.
[0039] In operation 0, the AMF can send a subscription request for UE subscriber information to the UDM. The corresponding message may include the UE identifier and a Subscription Permanent Identifier (SUPI). In embodiments where the PCF is used instead of the UDM, the AMF can send a subscription request for UE subscriber information to the PCF. When using the PCF instead of the UDM, the PCF will be used in place of the UDM in the following description.
[0040] In Operation 1, the AF can send messages to the UDM via the Network Exposure Function (NEF) that include information for network slice selection or reselection (e.g., Nnef_ParameterProvision_Create, update, or delete messages).
[0041] In embodiments where PCF is used instead of UDM, AF can send messages to PCF via NEF that include information for network slice selection or reselection (e.g., Nnef_AMInfluence_Create, Update, or Delete messages).
[0042] When the AF sends a message directly to the UDM (or PCF), the AF can send the message of operation 2 (Nudm_ParameterProvision_Create, update, or delete message) directly to the UDM (or PCF) without going through the NEF.
[0043] The message sent by AF to NEF (or UDM) may include the following information: - UE identifier information: may include a General Public Subscription Identifier (GPSI) or a Subscription Permanent Identifier (SUPI). Alternatively, it may include an external group ID indicating multiple UEs.
[0044] - Transaction Reference ID: When the AF intends to update or delete information that exists from a previous request (e.g., by sending an update or delete message) to the NEF, the AF may include the corresponding transaction reference ID.
[0045] - Network slice selection information: Network slice selection information for the UE may include one or more S-NSSAI information to be used by the UE, information about other S-NSSAIs to be used in lieu of each S-NSSAI (other S-NSSAIs per S-NSSAI), and information about S-NSSAIs to be used for each application identifier (or for each application category identifier). Additionally, it may include time information (e.g., start time, end time, duration, etc.) indicating when the S-NSSAI information to be used in lieu of each S-NSSAI is applied.
[0046] - Priority information: Information indicating the priority of the application slice selection information can be included for each UE. When the alternative S-NSSAI included in the slice selection information (e.g., alternative S-NSSAI) is congested, the network can determine whether to allow the UE to use the alternative S-NSSAI based on the priority of the application slice selection information.
[0047] In embodiments where PCF is used instead of UDM, the information provided by AF may include an application identifier (e.g., application ID or AF service ID).
[0048] When the NEF receives a message from the AF in Operation 1, the NEF can authorize the AF's request. If authorization fails, Operations 2 through 5 can be skipped, and the NEF can send a response message to the AF in Operation 6, including information indicating failure or rejection. For example, if the S-NSSAI included in the request message from the AF is not included in the UE's subscriber information included in the AF request message, the NEF can send a response message to the AF including information indicating failure or rejection.
[0049] When the request to AF is successfully authorized, NEF can send a message to UDM (or PCF) in Operation 2 based on the message received in Operation 1. When NEF receives a create message in Operation 1, NEF can generate a transaction reference ID. The message sent by NEF to UDM (or PCF) can include the information included in the message received in Operation 1.
[0050] In Operation 3, when the message received in Operation 2 includes a UE identifier instead of a SUPI, the UDM can identify the SUPI associated with the UE based on stored information. When the message received in Operation 2 includes an external group ID, the UDM can identify the corresponding internal group ID based on stored information.
[0051] In order to authenticate the subscriber information changes according to the request of Operation 2 for the UE (e.g., SUPI) corresponding to the request of Operation 2, the UDM can obtain the subscriber information of SUPI from the UDR by sending a request message to the UDR to obtain the subscriber information of SUPI.
[0052] In embodiments where PCF is used instead of UDM, in order to authenticate the subscriber information change according to the request of Operation 2 for the UE (e.g., SUPI) corresponding to the request of Operation 2, PCF can obtain information from UDR by sending a request message to UDR to obtain subscriber information for SUPI or application ID.
[0053] In operation 4, when the subscriber information change in operation 3 is successfully authenticated, the UDM (or PCF) can send a message to the UDR to update the subscriber information. This message may include the following information: - SUPI - S-NSSAI per S-NSSAI: The network slice selection information included in the message of Operation 1 is included as is, or information derived from that network slice selection information may be included. For example, information about alternative slice identifiers to be used for each slice may be included. In this case, S-NSSAI per S-NSSAI may be included in the S-NSSAI subscribed to by the UE.
[0054] - Subscribed S-NSSAI: When the message of Operation 1 includes the UE's S-NSSAI, the UE's subscribed S-NSSAI can be updated based on this S-NSSAI information, including the subscribed S-NSSAI configured based on the UE's S-NSSAI.
[0055] Upon receiving an update message from the UDM (or PCF), the UDR can update the subscription information stored in the UDR using the SUPI included in the message as the data key. The UDR can update the associated subscription information based on the information included in the message (e.g., S-NSSAI per S-NSSAI or S-NSSAI of a subscription). When the corresponding subscription information (e.g., the subscription information corresponding to S-NSSAI per S-NSSAI or S-NSSAI of a subscription) already exists, the UDR can perform an overwrite based on the information included in the message received from the UDM (or PCF). When the corresponding subscription information does not exist, the UDR can add new subscription information (e.g., the subscription information corresponding to S-NSSAI per S-NSSAI or S-NSSAI of a subscription) based on the information included in the message received from the UDM (or PCF).
[0056] In Operation 5, the UDM (or PCF) may send a response message to the NEF (or to the AF if requested directly by the AF) in response to the request message of Operation 2. This message may include information about the result of processing the request of Operation 2.
[0057] In operation 6, upon receiving the message from operation 5, the NEF can send a response message to the AF regarding the message from operation 1. This message may include information about the result of processing the request for operation 1.
[0058] When the UDM (or PCF) updates subscription information (e.g., subscription information corresponding to S-NSSAI per S-NSSAI or subscribed S-NSSAI, or policy information in an embodiment using PCF) in operation 4, the UDM (or PCF) may send a notification message in operation 7 to the NF (e.g., AMF) that has subscribed to the subscription information (or policy information in an embodiment using PCF). When the information stored in the UDR includes time information along with S-NSSAI per S-NSSAI (e.g., slice identifier and replacement slice identifier information that need to be changed), the UDM or PCF may send a notification message to the AMF at the time when S-NSSAI per S-NSSAI is to be applied according to the time information. Furthermore, at the time when the application of S-NSSAI per S-NSSAI is to be disabled according to the time information, the UDM or PCF may send a notification message to the AMF for disabling (e.g., a notification message for replacing an existing slice). In this case, the notification message may only include the identifier of the existing slice being replaced.
[0059] When an alternative slice (e.g., a replacement slice) included in the information stored in the UDR is currently congested, the UDM or PCF may not send a notification message to the AMF. When a slice to be used as a replacement (e.g., a replacement slice) included in the information stored in the UDR is currently congested, and the information stored in the UDR includes priority information indicating high priority, the UDM or PCF may send a notification message to the AMF. Furthermore, the UDM or PCF may send a notification message to the AMF responsible for the UE with lower priority information to stop using the alternative slice (e.g., the replacement slice).
[0060] In this case, the notification message may include the following information: - SUPI or internal group identifier: may include SUPI (i.e., UE identifier) or internal group identifier.
[0061] - This may include subscription information corresponding to the S-NSSAI for each S-NSSAI.
[0062] - This can include subscriptions to S-NSSAI.
[0063] In Operation 8a, upon receiving the notification message from Operation 7, the AMF can determine whether to update the UE configuration information related to the network slice of the UE in response to the message. Furthermore, upon receiving the message from Operation 11 (described later), if there is a PDU session of S-NSSAI that needs to be changed, the AMF can send a message requesting the network slice to be replaced with an alternative S-NSSAI to the SMF responsible for that session, based on the information included in the message received in Operation 7.
[0064] When using the NSSF, the AMF can send a message to the NSSF to query UE configuration information. In this case, if the message received in Operation 7 includes the subscribed S-NSSAI, the AMF can add the subscribed S-NSSAI received in Operation 7 to the message to be sent to the NSSF.
[0065] When using NSSF and the message received in Operation 7 includes the S-NSSAI for each S-NSSAI (e.g., information about other slice identifiers to be used instead of each network slice identifier in one or more network slice identifiers that need to be changed), instead of deriving the requested NSSAI based on other alternative identifiers included in that information (e.g., including information about the network slice identifier requested by the UE) and adding the requested NSSAI to the message to be sent to NSSF (e.g., an nssf_NSSelection Get request) or sending that message to NSSF, the AMF can check whether the S-NSSAI that needs to be changed exists in the UE's existing allowed NSSAIs. If it does, based on the S-NSSAI for each S-NSSAI, it generates (or updates) the slice identifier information to be used instead of the S-NSSAI that needs to be changed (e.g., a mapping of the replacement S-NSSAI). When the alternative slice identifier (e.g., the alternative S-NSSAI) is not included in the allowed NSSAIs, the AMF can update the allowed NSSAIs. When an alternative slice identifier (e.g., an alternative S-NSSAI) is not included in the configured NSSAI, the AMF can update the configured NSSAI. When an update occurs to the mapping of an allowed NSSAI, configured NSSAI, or alternative S-NSSAI, the AMF can add the corresponding configuration information (e.g., one or more of the mappings of allowed NSSAI, configured NSSAI, or alternative S-NSSAI) to the UE configuration update command message to be sent to the UE via the RAN.
[0066] The NSSF can derive the allowed NSSAI and / or configured NSSAI based on messages received from the AMF, and then add the allowed NSSAI and / or configured NSSAI to the response message to be sent to the AMF. When the response message received from the NSSF includes allowed NSSAI or configured NSSAI, the AMF can add the corresponding configuration information (e.g., one or more of the allowed NSSAI or configured NSSAI) to the UE configuration update command message to be sent to the UE via the RAN.
[0067] When the AMF does not use NSSF and the message received in Operation 7 includes subscribed S-NSSAI, the AMF can update the allowed NSSAI and / or configured NSSAI based on the updated subscribed S-NSSAI. When an update occurs to one or more of the allowed NSSAI or configured NSSAI, the AMF can add the corresponding configuration information (e.g., one or more of the allowed NSSAI or configured NSSAI) to the UE configuration update command message to be sent to the UE via the RAN.
[0068] When the AMF does not use NSSF and the message received in Operation 7 includes the S-NSSAI for each S-NSSAI (e.g., information about other slice identifiers to be used instead of each of the network slice identifiers in one or more network slice identifiers that need to be changed), the AMF can check whether there is an S-NSSAI that needs to be changed among the UE's existing allowed NSSAIs. When there is an S-NSSAI that needs to be changed among the UE's existing allowed NSSAIs, the AMF can derive the slice identifier information to be used instead of the S-NSSAI that needs to be changed (e.g., the mapping of the alternative S-NSSAI) based on the S-NSSAI for each S-NSSAI. When an update occurs to the mapping of allowed NSSAIs, configured NSSAIs, or alternative S-NSSAIs, the AMF can add the corresponding configuration information (e.g., one or more of the mappings of allowed NSSAIs, configured NSSAIs, or alternative S-NSSAIs) to the UE configuration update command message to be sent to the UE via the RAN.
[0069] When the message received in operation 8a includes an allowed NSSAI, the UE can delete the stored allowed NSSAI and store the allowed NSSAI included in the received message. When the message received in operation 8a includes a configured NSSAI, the UE can delete the stored configured NSSAI and store the configured NSSAI included in the received message. When the message received in operation 8a includes a mapping for a replacement S-NSSAI, the UE can delete the stored mapping for the replacement S-NSSAI and store the mapping for the replacement S-NSSAI included in the received message. When a mapping for a replacement S-NSSAI is received (e.g., information indicating that a replacement S-NSSAI should be used instead of the existing S-NSSAI), the UE can use the replacement S-NSSAI to replace the existing S-NSSAI included in that information. For example, when a session is needed to send application data to an existing S-NSSAI, a session establishment request message for data transmission can be sent to the replacement S-NSSAI instead of the existing S-NSSAI. However, the session establishment request message can include existing S-NSSAI information along with the replacement S-NSSAI.
[0070] In Operation 8b, the UE can send a message to the AMF via the RAN, indicating that the configuration information update received in Operation 8a has been completed.
[0071] In Operation 9, the UE can send a registration request message to the AMF via the RAN. The registration request message can be an initial registration request (e.g., a registration request with the registration type set to initial registration) or a mobility registration update request (e.g., a registration request with the registration type set to mobility registration).
[0072] In operation 10, the AMF can send a request message including SUPI to the UDM to receive subscription information for the UE. In this embodiment, the AMF can send a request message including SUPI to the PCF to receive policy information for the UE.
[0073] In operation 11, upon receiving the message from operation 10, the UDM can retrieve the subscription information stored in the UDR via the SUPI included in the received message. The UDM can then add the subscription information to the response message to be sent to the AMF. The subscription information may include information updated via operation 4.
[0074] In this embodiment, when the message of operation 10 is received, the PCF can obtain the subscription information stored in the UDR through the SUPI included in the received message. This information may include the information updated through operation 4.
[0075] When the information stored in the UDR includes time information along with the S-NSSAI for each S-NSSAI (e.g., the slice identifier to be changed and the replacement slice identifier information), the UDM or PCF can send a notification message to the AMF at the time when the S-NSSAI for each S-NSSAI is to be applied according to the time information. Furthermore, at the time when the application of the S-NSSAI for each S-NSSAI is to be disabled according to the time information, the UDM or PCF can send a notification message to the AMF for disabling (e.g., a notification message for replacing an existing slice). In this case, the notification message may only include the identifier of the existing slice being replaced.
[0076] In Operation 12, upon receiving the message from Operation 11, the AMF can export UE configuration information related to the UE's network slice based on that message. Furthermore, upon receiving the message from Operation 11, if there is an S-NSSAI PDU session that needs to be changed, the AMF can send a message requesting the SMF responsible for that session to replace the network slice with an alternative S-NSSAI, based on the information included in the message received in Operation 7.
[0077] When using NSSF, AMF can send a message to NSSF to query UE configuration information. When the message received in Operation 11 includes subscribed S-NSSAI, AMF can add the subscribed S-NSSAI received in Operation 11 to the message to be sent to NSSF.
[0078] When using NSSF and the message received in Operation 11 includes the S-NSSAI for each S-NSSAI (e.g., information about other slice identifiers to be used instead of each network slice identifier in one or more network slice identifiers that need to be changed), instead of deriving the requested NSSAI based on other alternative identifiers included in that information (e.g., including information about the network slice identifier requested by the UE) and adding the requested NSSAI to the message to be sent to NSSF (e.g., an nssf_NSSelection Get request) or sending that message to NSSF, the AMF can check whether there is an S-NSSAI that needs to be changed in the UE's existing allowed NSSAIs. If there is, based on the S-NSSAI for each S-NSSAI, it generates (or updates) the slice identifier information to be used instead of the S-NSSAI that needs to be changed (e.g., a mapping of alternative S-NSSAIs). When the alternative slice identifier (e.g., an alternative S-NSSAI) is not included in the allowed NSSAIs, the AMF can update the allowed NSSAIs. When an alternative slice identifier (e.g., an alternative S-NSSAI) is not included in the configured NSSAI, the AMF can update the configured NSSAI. When an update occurs to the mapping of an allowed NSSAI, configured NSSAI, or alternative S-NSSAI, the AMF can add the corresponding configuration information (e.g., one or more of the mappings of allowed NSSAI, configured NSSAI, or alternative S-NSSAI) to the registration acceptance message to be sent to the UE via the RAN.
[0079] The NSSF can derive the allowed NSSAI and / or configured NSSAI based on the message received from the AMF, and then add the allowed NSSAI and / or configured NSSAI to the response message to be sent to the AMF. When the response message received from the NSSF includes allowed NSSAI or configured NSSAI, the AMF can add the corresponding configuration information (e.g., one or more of the allowed NSSAI or configured NSSAI) to the registration acceptance message to be sent to the UE via the RAN.
[0080] When the AMF does not use NSSF and the message received in Operation 11 includes subscribed S-NSSAI, the AMF can update the allowed NSSAI and / or configured NSSAI based on the updated subscribed S-NSSAI. When an update occurs to one or more of the allowed NSSAI or configured NSSAI, the AMF can add the corresponding configuration information (e.g., one or more of the allowed NSSAI or configured NSSAI) to the registration acceptance message to be sent to the UE via the RAN.
[0081] When the AMF does not use NSSF and the message received in Operation 11 includes the S-NSSAI for each S-NSSAI (e.g., information about other slice identifiers to be used instead of each of the network slice identifiers in one or more network slice identifiers that need to be changed), the AMF can check whether there is an S-NSSAI that needs to be changed among the UE's existing allowed NSSAIs. When there is an S-NSSAI that needs to be changed among the UE's existing allowed NSSAIs, the AMF can derive the slice identifier information to be used instead of the S-NSSAI that needs to be changed (e.g., the mapping of the replacement S-NSSAI) based on the S-NSSAI for each S-NSSAI. When an update occurs to the allowed NSSAI, the configured NSSAI, or the mapping of the replacement S-NSSAI, the AMF can add the corresponding configuration information (e.g., one or more of the allowed NSSAI, the configured NSSAI, or the mapping of the replacement S-NSSAI) to the registration acceptance message to be sent to the UE via the RAN.
[0082] When the message received in operation 12 includes an allowed NSSAI, the UE can delete the stored allowed NSSAI and store the allowed NSSAI included in the received message. When the message received in operation 12 includes a configured NSSAI, the UE can delete the stored configured NSSAI and store the configured NSSAI included in the received message. When the message received in operation 12 includes a mapping for an alternative S-NSSAI, the UE can delete the stored mapping for the alternative S-NSSAI and store the mapping for the alternative S-NSSAI included in the received message. When a mapping for an alternative S-NSSAI is received (e.g., information indicating that an alternative S-NSSAI should be used instead of an existing S-NSSAI), the UE can use the alternative S-NSSAI instead of the existing S-NSSAI included in that information. For example, when a session is needed to send application data to an existing S-NSSAI, a session establishment request message for data transmission can be sent to the alternative S-NSSAI instead of the existing S-NSSAI. However, the session establishment request message can include existing S-NSSAI information along with the alternative S-NSSAI.
[0083] Figure 3 A dynamic network slice selection method in a wireless communication system according to an embodiment of the present disclosure is illustrated. Figure 3 The operations shown are not all necessary components; some operations may be omitted in some embodiments.
[0084] In Operation 1, the AMF can send an AM Policy Association Establishment Request message to the PCF, and the PCF can generate an AM policy and then send a response message to the AMF. The PCF can also send a message to the Binding Support Function (BSF) to register itself as the PCF responsible for the UE. The message sent by the PCF to the BSF may include the PCF ID and the UE ID (e.g., SUPI or GPSI).
[0085] In Operation 2a, when the PCF is newly registered for the UE, the AF can send a subscription request message to the BSF directly or through the NEF to request the new PCF registration.
[0086] In operation 2b, after receiving the request from operation 2a, when a new PCF registration occurs for the UE (e.g., AM policy association establishment in operation 1), the BSF can send a notification message including the PCF ID to the AF directly or through the NEF.
[0087] In Operation 2c, the AF may determine to provide network slice selection information (e.g., network slice selection information) to the UE. This can occur, for example, when the AF requests the use of another network slice due to a problem with the existing network slice used by the UE, or when a change in network slice is required due to a modification to the UE user's subscription plan or membership.
[0088] When the AF determines to provide network slice selection information, the AF can send a request message to the PCF, AMF, or UDM to obtain network slice information for the UE (e.g., one or more of allowed NSSAI, subscribed S-NSSAI, and requested NSSAI). Upon receiving this message, the PCF, AMF, or UDM can add the network slice information for the UE (e.g., one or more of allowed NSSAI, subscribed S-NSSAI, and requested NSSAI) to a response message to be sent to the AF.
[0089] In Operation 2d, when the AF determines to provide network slice selection information, the AF can send a request message to the PCF directly or through the NEF, including the following information.
[0090] - UE identifier information: may include a General Public Subscription Identifier (GPSI) or a Subscription Permanent Identifier (SUPI). Alternatively, it may include an external group ID indicating multiple UEs.
[0091] - Network slice selection information: Network slice selection information for the UE may include one or more S-NSSAI information to be used by the UE, information about other S-NSSAIs to be used instead of each S-NSSAI (other S-NSSAIs per S-NSSAI), or information about S-NSSAIs to be used for each application identifier (or for each application category identifier).
[0092] In Operation 3, the PCF can receive the message from Operation 2d and, when the message includes network slice selection information, determine an update policy. When the message from Operation 2d includes the S-NSSAI for each S-NSSAI (e.g., information about other slice identifiers to be used in place of each of one or more network slice identifiers that need to be changed), the PCF can derive a policy that includes information instructing the UE to use another network slice instead of the existing network slice (replacing the S-NSSAI).
[0093] In Operation 4, the PCF can send the updated policy from Operation 3 to the AMF in a notification message. The notification message may include one or more of the following information: - Replacement S-NSSAI per S-NSSAI - UE ID (GPSI, SUPI, or UE address): UE identifier information - Policy Association ID: Information that identifies the policy In operations 5a and 5b, the following can be executed: Figure 2 The operation is the same as 8a and 8b.
[0094] In operation 6, the PCF can send a notification message to the AF indicating that the network slice selection information has been reflected.
[0095] Figure 4 A network entity 400 according to an embodiment of the present disclosure is shown. In the embodiment, network entity 400 may correspond to Figure 1 , 2 Or NSSF, NWDAF, UDM, NSACF, AMF, SMF, PCF, AF, UE, RAN, AN, UPF, DN, UDR, NEF, or BSF as shown in 3.
[0096] refer to Figure 4Network entity 400 may be configured with transceiver 410, processor 420, and memory 430. The transceiver 410, processor 420, and memory 430 of network entity 400 may operate according to the communication method of network entity 400 described above. However, the components of network entity 400 are not limited to these. For example, network entity 400 may include more components than described above. Furthermore, transceiver 410, processor 420, and memory 430 may be implemented on a single chip. Processor 420 may include one or more processors.
[0097] The receiver and transmitter of network entity 400 are collectively referred to as transceiver 410, which can send or receive signals to or from the UE or base station. The signals to be sent or received to or from the UE or base station may include control information and data.
[0098] Transceiver 410 can perform functions for transmitting and receiving signals on a wireless channel. For example, transceiver 410 can receive signals on a wireless channel and output those signals to processor 420, and transmit signals output from processor 420 on a wireless channel.
[0099] Memory 430 can store programs and data required for the operation of network entity 400. Furthermore, memory 430 can store control information or data included in signals received by network entity 400. Memory 430 may include storage media or combinations of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Alternatively, memory 430 may not exist separately but may be integrated into processor 420. Memory 430 may include volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. Memory 430 can also provide stored data upon request from processor 420.
[0100] Processor 420 can control a series of processes for network entity 400 to operate according to embodiments of the present disclosure. For example, processor 420 can receive and process control and data signals via transceiver 410. Processor 420 can transmit processed control and data signals via transceiver 410. Processor 420 can record data to or read data from memory 430. Processor 420 can perform the functions of the protocol stack required by the communication standard. For this purpose, processor 420 may include at least one processor or microprocessor. In embodiments, transceiver 410 or a portion of processor 420 may be referred to as a communication processor (CP).
[0101] Some embodiments have been described, but those skilled in the art will understand and appreciate that various modifications can be made without departing from the scope of this disclosure. Therefore, it will be apparent to those skilled in the art that this disclosure is not limited to the described embodiments but can cover the appended claims and their equivalents. For example, elements described in the singular form can be implemented in a distributed manner, while elements described in a distributed manner can be implemented in a combined manner.
[0102] The scope of this disclosure is defined by the appended claims, and those skilled in the art will understand that various changes in form and detail may be made without departing from the spirit and scope of this disclosure as defined by the appended claims and their equivalents.
Claims
1. A method for operating Access and Mobility Management Function (AMF) in a wireless communication system, the method comprising: Send a subscription information request message corresponding to the User Equipment (UE) to the Unified Data Management (UDM); Receive notification messages from the UDM regarding updated subscription information; Determine whether to update the UE configuration information related to the network slice of the UE; When the UE configuration information related to the network slice is updated, the updated UE configuration information is sent to the UE; as well as The UE receives a message indicating that the configuration information update is complete.
2. The method according to claim 1, wherein, The subscription information request message includes the UE's identifier.
3. The method according to claim 1, wherein, The notification message regarding the updated subscription information is received based on the time information stored in the UDR.
4. A method for operating a unified data management (UDM) in a wireless communication system, the method comprising: Receive subscription information request messages corresponding to the User Equipment (UE) from the Access and Mobility Management Function (AMF); Receive messages from the Application Function (AF) including information for network slice selection or reselection; Identify the subscription permanent identifier SUPI associated with the UE; Send a request message to the Unified Data Repository (UDR) to obtain subscriber information for the SUPI, and obtain the subscriber information from the UDR; Send a message for subscriber information update to the UDR; Send a notification message to the AMF regarding the updated subscription information; Receive a subscription information request message for the UE from the AMF; as well as In response to the subscription information request message, the updated subscription information is sent to the AMF.
5. The method according to claim 4, wherein, The subscription information request message includes the UE's identifier.
6. The method according to claim 4, wherein, The message that includes information for network slice selection or reselection includes at least one of UE identifier information, transaction reference identifier, network slice selection information, or information indicating the application priority of slice selection information.
7. The method according to claim 4, wherein, The message used for subscriber information updates includes at least one of SUPI, S-NSSAI information, or subscribed S-NSSAI information.
8. The method according to claim 4, wherein, The notification message regarding the updated subscription information is sent based on the time information stored in the UDR.
9. The method according to claim 4, wherein, The notification message regarding updated subscription information includes at least one of SUPI, internal group identifier, S-NSSAI information, or subscribed S-NSSAI information.
10. A method for operating a policy control function (PCF) in a wireless communication system, the method comprising: Receive subscription information request messages corresponding to the User Equipment (UE) from the Access and Mobility Management Function (AMF); Receive messages from the Application Function (AF) including information for network slice selection or reselection; Send a request message to the Unified Data Repository (UDR) to obtain subscriber information for the Subscription Permanent Identifier (SUPI) associated with the UE, and obtain the subscriber information from the UDR; Send a message for subscriber information update to the UDR; Send a notification message to the AMF regarding the updated subscription information; Receive a policy information request message for the UE from the AMF; Based on the policy information request message, identify the subscription information stored in the UDR; as well as In response to the policy information request message, updated subscription information is sent to the AMF.
11. The method according to claim 10, wherein, The subscription information request message includes the UE's identifier.
12. The method according to claim 10, wherein, The message including information for network slice selection or reselection includes at least one of UE identifier information, transaction reference identifier, network slice selection information, or information indicating the priority of the application of slice selection information.
13. The method according to claim 10, wherein, The message used for subscriber information updates includes at least one of SUPI, S-NSSAI information, or subscribed S-NSSAI information.
14. The method of claim 10, wherein, The notification message regarding the updated subscription information is sent based on the time information stored in the UDR.
15. The method according to claim 10, wherein, The notification message regarding updated subscription information includes at least one of SUPI, internal group identifier, S-NSSAI information, or subscribed S-NSSAI information.