Dynamic network capability configuration

Abstract

To provide a method and a device for configuring desired network capabilities in a service-based network.SOLUTION: A method includes sending a first message to a network function (Access and Mobility Management Function (AMF)) indicating a requested operation, including slice registration, to be performed using a network slice by UE, and receiving a response from the network function including a rejection code indicating that the operation is rejected because a maximum number of UEs registered in the network slice has been reached.SELECTED DRAWING: Figure 15

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application is a continuation of U.S. patent application Ser. No. 62 / 817,811, filed March 13, 2019. and priority of U.S. Patent Application No. 62 / 931,376, filed November 6, 2019. The benefit of this patent is claimed, and is incorporated herein by reference in its entirety. [Background technology]

[0002] 3rd Generation Partnership Project: 3GPP) is a set of standards for radio access, core transport networks, and service capabilities ( Cellular technologies, including those that affect coding / decoding, security, and quality of service It develops technical standards for telecommunications network technologies. The Radio Access Technology (RAT) standard is WCDMA (registered trademark) (generally known as 3 G), LTE (commonly referred to as 4G), and LTE-Advanced standards 3GPP is working on the next generation of wireless technology called New Radio (NR), also known as 5G. We have begun efforts to standardize next-generation cellular technology.

[0003] The 5G Core Network (5GC) is a network slicing and service-based network functions based on the concept of virtualized network functions (NFs). Service Based Architecture (SBA) is included. Access and Mobility Management Function (AMF), Session Management Function (SMF) and policy control Various network functions, such as the Policy Control Function (PCF), are It provides various network function services through a space-based interface. , the service consumer communicates with the service provider using the same message and the same This means that any NF can use the interface provided by the AMF. You can subscribe to the same events as the Event Exposure service. Non-IP Data Delivery (NIDD), background data transmission (Ba Background Data Transfer (BDT), and Power Saving Mode (Power Saving Mode Various network capabilities, such as PSM, can be implemented through a set of NF services. Under the current SBA framework, the UE receives a request for network slice identification. Network Slice Selection Assistance Information :NSSAI) to configure and access the network. There is no direct way for the UE to indicate the desired network capabilities. Summary of the Invention

[0004] Under the current SBA framework of 5GC, the UE identifies the network slice. It configures and accesses the network by indicating a request NSSAI to However, there is no way for the UE to directly indicate its desired network capabilities. [Means for solving the problem]

[0005] Method and apparatus for configuring desired network capabilities in a service-based network - Patents.com and an apparatus are disclosed herein.

[0006] In one aspect, a new framework is described that includes a network capabilities layer. The UE and AS must have the network capabilities to support these applications. (e.g. background data transmission, non-IP data delivery) can be dynamically requested. In one implementation, the UE and the AS can determine which network the requested network capabilities are available to. A network slice that supports or provides services is required. It is not necessary to know whether the network supports the requested network capability or not. In some cases, the core network entity may not need to consider all the required In one embodiment, a network slice may be determined or configured to support the desired network capabilities.

[0007] In another aspect, the UE may communicate with the network to configure its desired network capabilities. This article describes how to initiate competency-based enrollment.

[0008] In yet another aspect, the UE is already registered with the network and When the UE needs to dynamically reconfigure its network capabilities, it can perform network capability-based registration updates. This article describes how to start a new project.

[0009] In yet another aspect, the NF or the application server may Network Capability Base U, which allows you to start updating Rice's network capabilities This section describes how to update the configuration.

[0010] Interface with User Plane Function (UPF) and The extended service-based architecture including the services provided by UPF is also described. I will write more later.

[0011] The network is configured to use the Network Capability Profile (NCAP) of the network slice. A mechanism that can deliver network capability information, called the Network Ability Profile (NCP), to UEs. Zum.

[0012] According to the network capability requested by the UE, the corresponding network capability profile is obtained. A method by which the network may inform the UE about an alternative network slice that the UE has. The UE initiates network capability based registration to configure the desired network capabilities. The mechanism by which

[0013] The UE registers a set of authorized NSSAIs including their corresponding NCPs during the basic UE registration procedure. The capabilities indicated by the received NCP are reflected in the UE's access If the grant S received from the core network is not sufficient for the application, the UE - May request an alternative network slice based on the NSSAI's NCP list do.

[0014] During the UE policy update procedure, the NCP of the network slice The mechanism by which it is delivered to the UE.

[0015] The core network may provide up to Enforces the number of PDU sessions and processes requests that are received after the maximum limit is reached. mechanism.

[0016] The core network enforces a maximum limit on the number of PDU sessions per network slice. This mechanism allows the UE to wait before retrying. The network slice notifies the network owner via a NAS message that it has reached its maximum limit. The network periodically notifies the UE.

[0017] The core network enforces the maximum number of UE registrations per network slice and A mechanism for handling registration requests that are received after the upper limit has been reached.

[0018] This Summary is provided in a simplified form to provide an overview of the detailed description of the invention, which is further described below. This Summary is provided to introduce a selection of key features or aspects of the claimed subject matter. It cannot identify qualitative characteristics or be used to limit the scope of the claimed subject matter. Moreover, it is not intended that the claimed subject matter incorporate any It is not intended to be limited to any limitation that addresses any or all of the disadvantages.

[0019] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, in which: There will be. [Brief description of the drawings]

[0020] [Figure 1A] FIG. 1A illustrates an example communication system. [Figure 1B] FIG. 1B is a block diagram of an example apparatus or device configured for wireless communication, such as, for example, a Wireless Transmit / Receive Unit (WTRU). [Figure 1C]FIG. 1C is a system diagram of an example Radio Access Network (RAN) and core network. [Figure 1D] FIG. 1D is a system diagram of another example RAN and core network. [Figure 1E] FIG. 1E is a system diagram of another example RAN and core network. [Figure 1F] FIG. 1F is a system diagram of another example RAN and core network. [Figure 1G] FIG. 1G is a block diagram of an exemplary computing system in which a node, entity, device or other apparatus of a communication system may be embodied. [Figure 2A] FIG. 2A illustrates a non-roaming 5G reference architecture with a service-based interface to the control plane. [Figure 2B] FIG. 2B is a diagram illustrating a non-roaming 5G system architecture including a depiction of reference points. [Diagram 3] FIG. 3 is a diagram illustrating examples of network functions, NF services, and NF service operations. [Figure 4] FIG. 4 is a diagram showing an example of a “request-response” NF service. [Diagram 5] FIG. 5 is a diagram illustrating an example of a “subscriber-notification” NF service. [Figure 6] FIG. 6 is a diagram illustrating a network capability configuration use case. [Figure 7] FIG. 7 illustrates an example network architecture including a network capabilities layer. [Figure 8] FIG. 8 illustrates a methodology for network capability-based registration. [Figure 9] FIG. 9 illustrates a method for network capability based registration updates. [Figure 10] FIG. 10 illustrates a method for network capability based UE configuration update. [Figure 11]FIG. 11 is a diagram illustrating an example of an extended service-based architecture that includes UPF and Nupf interfaces. [Figure 12] FIG. 12 illustrates an exemplary Graphical User Interface (GUI) for configuring network capabilities of a communications network. [Figure 13] FIG. 13 illustrates a method for a registration procedure using a network capability profile in a requesting NSSAI. [Figure 14] FIG. 14 illustrates a method for delivering a network capability profile to a UE as part of a UE policy. [Figure 15] FIG. 15 illustrates how a network handles the maximum number of PDU sessions in a network slice. [Figure 16] Figure 16 illustrates how NAS notification can be used to handle the maximum number of PDU sessions in a network slice. [Figure 17] FIG. 17 illustrates a procedure for handling the maximum number of UEs limit in a network slice. [Figure 18] FIG. 18 illustrates an example graphical user interface (GUI) illustrating that a UE may receive an NCP from a network and that the UE may accept the NCP or request a new NCP. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] Below is a list of acronyms that may appear in the following descriptions, in particular Unless otherwise indicated, the acronyms used herein stand for the corresponding terms listed below. Point. 5GC: 5G Core AF: Application Function AMF: Access and Mobility Management Function AS: Application Server CN: Core Network CP: Control Plane DL: Downlink DNN: Data Network Name EPC: Evolved Packet Core GUTI: Globally Unique Temporary Identifier LTE: Long Term Evolution MBMS: Multimedia Broadcast / Multicast Service Multicast Service) MME: Mobility Management Entity NAS: Non Access Stratum NCMF: Network Capability Management Function NCP: Network Capability Profile NEF: Network Exposure Function NF: Network Function NIDD: Non-IP Data Delivery NRF: NF Repository Function NSSAI: Network Slice Selection Assistance Information Selection Support Information) NSSF: Network Slice Selection Function NSI: Network Slice Instance PCF: Policy Control Function PDU: Protocol Data Unit PSM: Power Saving Mode QoS: Quality of Service RAN: Radio Access Network PLMN: Public Land Mobile Network SBA: Service Based Architecture SCS: Service Capability Server SD: Slice Differentiator (slice identification information) SM: Session Management SMF: Session Management Function SMSF: Short Message Service (SMS) Function t Message Service (SMS) function S-NSSAI: Single Network Slice Selection Assistance Information Workslice selection support information) SST: Slice / Service Type SUPI: SUbscription Permanent Identifier UDM / UDR: Unified Data Management / Unified Data Repository Integrated Data Repository) UE: User Equipment UL: Uplink UPF: User Plane Function

[0022] The following terms may mean the following:

[0023] "Core Network" refers to the center, core, or part of a telecommunications network. It provides a large number of communication services to customers interconnected by a line access network. A core network typically consists of several As used herein, the term "core network entity" includes " includes, for example, AMF, UDR / UDSF, UDM / UDR, N Core network functions such as RF, NEF, PCF, NF, SMF, AUSF, and NSSF Such a core network entity may be any entity that performs the following functions: Wireless and / or network communications as illustrated in FIG. 1B or FIG. 1G or stored in the memory of a device configured for a computer system and the program of the device The present invention is implemented in the form of software (i.e., computer-executable instructions) that executes on a processor. It will be appreciated that the physical entity may be a logical entity that is represented as a physical entity.

[0024] A Network Function (NF) is a set of functions that have defined functional behavior and a defined interface. NF refers to a processing function in a network that has a dedicated interface. as a network element or on dedicated hardware or on a suitable platform, e.g. cloud infrastructure It can be implemented as a virtualization function instantiated with

[0025] A "Network Function Instance" refers to an identifiable instance of an NF.

[0026] "Network Function (NF) Service" is a service-based interface that provides NF ("NF Service Producer") may provide services to NFs authorized by other NFs ("NF Service Producers"). It may be a type of capability exposed to a network (a “Network Consumer”). A Network Function may expose one or more NF services. For example: 5G AMF provides the Namf_EventExposure service, which allows certain mobile Allows AMF to send notifications to NFs that subscribe to security management related events become.

[0027] "NF service instance" refers to an identifiable instance of an NF service.

[0028] A "network capability" is a capability that the core network implements and that its users (e.g., UEs) can use to It contains the transport network characteristics that it provides to the network server (or application server). Examples of network capabilities include background data transmission and event monitoring. A network capability is defined as a capability that is provided through one or more NFs, one or more modes of NF services. This makes it possible.

[0029] "Network slices" provide specific network capabilities and characteristics It is a logical network that

[0030] A "network slice instance" forms a deployed network slice. ,The set of NF instances and the required resources (e.g., computing , storage and networking resources).

[0031] The Network Capability Profile is a set of network capabilities maintained by the NCMF. This is a device-specific information profile supported by network slices. Indicates network capability.

[0032] The "Network Capability Management Function" provides the UE / AS with a set of desired network capabilities. The NF configures the network slice to provide the OAM system. It may be part of.

[0033] The 3rd Generation Partnership Project (3GPP) is a global initiative to develop and deploy wireless access, core transformers, and other Port network and service capabilities (encoding, security, and service offerings) Technical regulations for cellular telecommunications network technologies, including those that affect the quality of communications Recent radio access technology (RAT) standards include WCDMA (generally known as 3G). G), LTE (commonly referred to as 4G), and LTE-Advanced standards 3GPP is working on a next-generation cellular network called New Radio (NR), also known as "5G." The 3GPP NR standard development is the next-generation wireless access point. It is expected that the new standard will include provisions for new access technologies (new RATs) below 6 GHz. New flexible wireless access provisions and new ultramodules above 6GHz It is envisaged that the standard will include provisions for mobile broadband wireless access. Flexible wireless access will be driven by new non-backward compatible technologies in new frequency bands below 6GHz. It is expected that these will consist of interchangeable wireless access, and will be multiplexed together in the same frequency band. This allows it to address a broad set of 3GPP NR use cases with diverse requirements. Ultra Mobile Broadband is expected to include different modes of operation, such as: For example, ultra-mobile broadband access for indoor applications and hotspots. The proposed range of frequencies is expected to include centimeter and millimeter wave frequencies, which will provide wireless connectivity. Mobile broadband is a combination of flexible wireless access below 6GHz and, in particular, Sharing a common design framework with inch-wave and mmWave specific design optimizations It is expected.

[0034] 3GPP has identified various user experience requirements for data rate, latency, and mobility. Various use cases that are expected to be supported by New Radio (NR) The broad categories of use cases are: Broadband access in high-density areas, ultra-high-speed indoor broadband Access, broadband access in the crowd, 50+Mbps everywhere, Ultra-low-cost broadband access, mobile broadband in vehicles), Critical Communication, large-scale machine-type communication, network operations (e.g. network slicing , routing, migration and interworking, energy conservation) and advanced vehicle tools Enhanced Vehicle-To-Everything (eV2X) communication is one example. Specific services and applications in these categories include, for example, These include monitoring and sensor networks, device remote control, two-way remote control, and personal Global cloud computing, video streaming, wireless cloud-based office services, emergency responder connectivity, car e-call, disaster warning, real-time gaming, These include multi-person video calling, autonomous driving, augmented reality, tactile internet, and virtual reality. All of these use cases and others are contemplated herein.

[0035] FIG. 1A illustrates a block diagram of a network in which the methods and apparatus described and claimed herein may be embodied. 1 illustrates an embodiment of an exemplary communication system 100 in which The system 100 includes wireless transmit / receive units (WTRUs) 102a, 102b, 102c, and / or 102d (which may be generally or collectively referred to as WTRUs 102). (Radio Access Network (RAN) 103 / 104 / 105 / 103b / 10 4b / 105b, Core Network 106 / 107 / 109, and Public Switched Telephone Network Public Switched Telephone Network (PSTN) 108 and the Internet 1 10 and other networks 112, although the disclosed embodiments may include any Any number of WTRUs, base stations, networks, and / or network elements are contemplated. It will be appreciated that the WTRUs 102a, 102b, 102c, 102d, and 102e Each of any type of device configured to operate and / or communicate in a wireless environment Each of the WTRUs 102a, 102b, 102c, 102d, 1 The 02e is depicted in Figures 1A to 1G as a handheld wireless communication device, but is a 5G wireless In various possible use cases for wireless communications, each WTRU may be, by way of example only, a user equipment ( UE), Mobile Station, Fixed or Mobile Subscriber Unit, Pager, Cellular Telephones, personal digital assistants (PDAs), smartphones, laptops Laptops, tablets, netbooks, notebook computers, personal computers data, wireless sensors, consumer electronics products, smart watches or smart clothing Able devices, medical or e-health devices, robots, industrial equipment, drones, e.g. , including in a car, truck, train, or airplane vehicle, transmitting wireless signals and / or or It will be understood that the present invention may be embodied in various other forms.

[0036] The communication system 100 may also include a base station 114a and a base station 114b. The station 114a is in wireless communication with at least one of the WTRUs 102a, 102b, and 102c. Interfaces with core network 106 / 107 / 109 and Internet 1 10, and / or other networks 112. The network may be any type of device configured to facilitate access to a network. The base station 114b includes RRHs (Remote Radio Heads) 118a, 118b and / or TRPs. (Transmission and reception points) 119a, 119b and at least one of them connected by wire and / or wireless The core network 106 / 107 / 109 and the Internet One or more communication networks, such as the network 110 and / or other networks 112. The device may be any type of device configured to facilitate access to a workpiece. The RRHs 118a and 118b are in wireless communication with at least one of the WTRUs 102c. The interfaces are Core Network 106 / 107 / 109 and Internet 110 , and / or other networks 112. The device may be any type of device configured to facilitate access to a TR. The P119a, 119b wirelessly interface with at least one of the WTRUs 102d. The interface is composed of the core network 106 / 107 / 109, the Internet 110, and and / or other networks 112. The device may be any type of device configured to facilitate access to the , base stations 114a and 114b are base transceiver stations (BTS). ), Node-B, eNode B, Home Node B, Home eNode B, Side controller, access point (AP), wireless router, etc. Although base stations 114a, 114b are each depicted as a single entity, The stations 114a, 114b may be any number of interconnected base stations and / or networks. It will be appreciated that the embodiment may include elements.

[0037] The base station 114a may be part of the RAN 103 / 104 / 105. AN also includes a Base Station Controller (BSC), a wireless network Others such as Radio Network Controller (RNC) and relay nodes Base station 114b may also include base stations and / or network elements (not shown). , RAN 103b / 104b / 105b, which may also be part of Base Station Controller (BSC), Radio Network Controller (RNC), Relay Node The base station may also include other base stations and / or network elements (not shown), such as Station 114a transmits wireless signals within a particular geographic area (not shown), sometimes called a cell. The base station 114b may be configured to transmit and / or receive signals. may transmit wired and / or wireless signals within a particular geographic area (not shown) A cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may provide, for example, one UE for each sector of the cell. In one embodiment, the base station 114a may include three transceivers. In some cases, multiple-input multiple output (MIMO) technology is used. Thus, multiple transceivers may be utilized per sector of a cell.

[0038] The base station 114a may communicate with any suitable wireless communication link (e.g., Radio Frequency (RF) :RF), Microwave, Infrared (IR), Ultraviolet (UV), Possible Air Interface 115 / 116 / 117 to communicate with one or more of the WTRUs 102a, 102b, and 102c. The air interface 115 / 116 / 117 may be implemented using any suitable wireless access point. The cellular endothelial cell may be established using the Reactive Access Technology (RAT).

[0039] The base station 114b may be implemented using any suitable wired (e.g., cable, fiber optic, etc.) or Wireless communication links (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV) ), visible light, centimeter wave, millimeter wave, etc.), wired or air interface RRH118a, 118b and / or TR115b / 116b / 117b through It may communicate with one or more of P119a, 119b. Air Interface The stations 115b / 116b / 117b may use any suitable radio access technology (RAT). may be established.

[0040] RRH118a, 118b and / or TRP119a, 119b may be any suitable Wireless communication links (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV) ), visible light, centimeter wave, millimeter wave, etc.), air interface 115c / 116c / 117c to communicate with one or more of the WTRUs 102c, 102d. The air interface 115c / 116c / 117c may be any suitable The QoS may be established using various radio access technologies (RATs).

[0041] More particularly, as noted above, the communication system 100 is a multiple access system. and may be one of CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. Alternatively, multiple channel access schemes may be employed. For example, RAN103 / 10 The base station 114a and the WTRUs 102a, 102b, and 102c in RRH118a, 118b and TRP119 in RAN103b / 104b / 105b a, 119b and WTRUs 102c, 102d are universal mobile telecommunications systems. Universal Mobile Telecommunications System (UMTS), Terrestrial Wireless Access (Universal Terrestrial Radio Access:UTRA) and other wireless technologies are often implemented. This allows the use of Wideband CDMA (WCDMA) for air-interface communication. - Establish phase 115 / 116 / 117 or 115c / 116c / 117c respectively WCDMA stands for High-Speed ​​Packet Access. :HSPA) and / or Evolved HSPA (HSPA+) communications HSPA stands for High-Speed ​​Downlink Packet Access (HSPA) Downlink Packet Access (HSDPA) and / or High Speed ​​Uplink Packet Access This may include High-Speed ​​Uplink Packet Access (HSUPA).

[0042] In one embodiment, the base station 114a and the WTRUs 102a, 102b, and 102c Or RRH118a, 118b and TR in RAN103b / 104b / 105b P119a, 119b and WTRU102c, 102d are evolved UMTS terrestrial radio access Evolved UMTS Terrestrial Radio Access (E-UTRA) and other wireless technologies may be implemented to support Long Term Evolution (LTE) and / or L Air interface 1 using LTE-Advanced (LTE-A) 15 / 116 / 117 or 115c / 116c / 117c can be established respectively. In the future, the air interface 115 / 116 / 117 will be based on 3GPP NR technology. There is a possibility to implement.

[0043] In one embodiment, a base station 114a in the RAN 103 / 104 / 105 and a WTRU 102a, 102b, 102c, or RAN 103b / 104b / 105b RRH118a, 118b and TRP119a, 119b with WTRU102c, 102 d stands for IEEE802.16 (e.g., Worldwide Interoperability Framework). Worldwide Interoperability For Microwave Access ccess:WiMAX)), CDMA2000, CDMA2000 1X, CDMA200 0 EV-DO, Interim Standard 2000 (IS-2000), interim Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global Standard for Mobile Communications Global System For Mobile Communications (GSM (registered trademark)) Enhanced Data Rates For GSM Evolution (EDG E), GSM EDGE (GERAN), and other wireless technologies may be implemented.

[0044] The base station 114c in FIG. 1A may be a wireless router, a home NodeB, a home eNodeB, or The device may be a wireless device or an access point, for example in a place such as an office, a home, a vehicle, or a campus. Any suitable RAT may be used to facilitate wireless connectivity within a local area, such as a In one embodiment, the base station 114c and the WTRU 102e may use IEEE 802.11b / g / n. 02.11 and other wireless technologies to establish wireless local area networks (WLANs) In one embodiment, the base station 114 may establish a wireless local area network (WLAN). The WTRU102c and WTRU102d implement wireless technologies such as IEEE802.15 to Establishing a Wireless Personal Area Network (WPAN) In yet another embodiment, the base station 114c and the WTRU 102e may -based RAT (e.g. WCDMA, CDMA2000, GSM, LTE, LTE- A) may be used to establish a picocell or femtocell. As shown in FIG. 1A, Additionally, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114c is connected to the Internet via the core network 106 / 107 / 109. In some cases, access to the network 110 may not be required.

[0045] RAN103 / 104 / 105 and / or RAN103b / 104b / 105b , may communicate with the core network 106 / 107 / 109, The network may include voice, data, applications, and / or voice over internet. Protocol (Voice Over Internet Protocol: VoIP) service on WTRU102 a, 102b, 102c, 102d It may be any type of network. For example, the core network 106 / 107 / 109 provides call control, billing services, mobile location-based services, prepaid code provide services such as internet connectivity, video streaming, and / or It may also implement high-level security features such as user authentication.

[0046] Although not shown in FIG. 1A, RAN103 / 104 / 105 and / or RAN 103b / 104b / 105b and / or Core Network 106 / 107 / 109 RAN103 / 104 / 105 and / or RAN103b / 104b / 105b may communicate directly or indirectly with other RANs employing the same or different RATs. For example, it will be appreciated that the RAN 103 may utilize E-UTRA radio technology. / 104 / 105 and / or RAN 103b / 104b / 105b In addition, the core network 106 / 107 / 109 also includes another The RAN may also be in communication with the RAN (not shown).

[0047] The core network 106 / 107 / 109 also includes the WTRUs 102a, 102b, 2c, 102d, 102e are connected to the PSTN 108, the Internet 110, and / or It may also function as a gateway to access other networks 112 . PSTN108 is a standard telephone service (Plain Old Telephone Service: POTS). The Internet 110 may include a circuit-switched telephone network that provides Protocol (Transmission Control Protocol: TCP), User Datagram Protocol UDP (User Datagram Protocol), and TCP / IP Internet Protocol Common communications such as Internet Protocol (IP) in the Colu Suite A global network of interconnected computer networks and devices that use protocols Network 112 may include a global system operated by other service providers. This may include wired or wireless communication networks owned and / or operated by the company. For example, the network 112 may include the RAN 103 / 104 / 105 and / or the RAN 10. One or more that may employ the same RAT as 3b / 104b / 105b or a different RAT. The RAN may include another core network connected to the RAN or multiple RANs.

[0048] Within the communication system 100, WTRUs 102a, 102b, 10c, 10d, 10e, 10f ... WTRUs 102a, 102b, 102c, 102d, or any part thereof. 02c, 102d, and 102e communicate with different wireless networks through different wireless links. For example, the WTRU 102e shown in FIG. 1A may include multiple transceivers for receiving A base station 114a, which may employ ruler-based wireless technology, and an IEEE 802.11 wireless The wireless LAN may be configured to communicate with a base station 114c, which may employ wireless technology.

[0049] FIG. 1B illustrates a wireless communications unit (WTRU) 102 in accordance with an embodiment illustrated herein. FIG. 1B is a block diagram of an exemplary apparatus or device configured for signaling. In particular, the example WTRU 102 includes a processor 118, a transceiver 120, a transmit / receive element 122, and a 2, speaker / microphone 124, keypad 126, display / touchpad / Indicator 128, non-removable memory 130, removable memory 132, power supply 1 34. Global Positioning System (GPS) chipset 13 6, and other peripherals 138. The WTRU 102 may include It should be understood that the present invention may include any subcombination of the above elements. ,The ,embodiments ,include, ,among ,other ,applications, ,including ,a ,Base ,Transmitter ,Station ,(BTS), ,Node-B, Site Controller, Access Point (AP), Home Node-B, Advanced Home Node ode-B(Evolved Home Node-B:eNodeB), home evolved Node-B e Evolved Node-B (HeNB), Home Evolved Node-B Gateway, and Pro Base stations 114a and 114b, such as x-nodes, and / or base stations 114a and 114b is an element of the elements depicted in FIG. 1B and described herein. It is possible that some or all of the above may be included.

[0050] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital Digital Signal Processor (DSP), multiple microprocessors one or more microprocessors associated with the DSP cores; a controller; Microcontrollers, Application Specific Integrated Circuits ircuit:ASIC, Field Programmable Gate Array FPGA (Field Programmable Gauge) circuits, any other type of Integrated Circuit (Integrated Circuit C), a state machine, etc. The processor 118 may be a signal coding, a data processing processing, power control, input / output processing, and / or operation of the WTRU 102 within a wireless environment. The processor 118 may also implement any other functionality that enables the transmission / reception In FIG. 1B, Although the processor 118 and the transceiver 120 are shown as separate components, The processor 118 and the transceiver 120 are integrated together in an electronic package or chip. It will be well understood.

[0051] The transmit / receive element 122 communicates with the base station through the air interface 115 / 116 / 117. to transmit signals to or receive signals from a station (e.g., base station 114a). For example, in one embodiment, the transmit / receive element 122 may be configured to transmit an RF signal. In one embodiment, the antenna may be configured to transmit and / or receive. Thus, the transmit / receive element 122 may transmit and / or receive IR, UV, or visible light signals, for example. Alternatively, it may be an emitter / detector configured to receive. In the embodiment, the transmit / receive element 122 is adapted to transmit and receive both RF and optical signals. The transmit / receive element 122 may be configured to transmit and receive any combination of wireless signals. It will be appreciated that the device may be configured to receive and / or transmit a

[0052] In addition, although the transmit / receive element 122 is depicted in FIG. 1B as a single element, the WT The RU 102 may include any number of transmit / receive elements 122. More specifically, the WT The RU 102 may employ MIMO technology. Thus, in one embodiment, The RU 102 transmits and receives radio signals through the air interface 115 / 116 / 117. The system includes two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving. That's fine.

[0053] The transceiver 120 modulates the signal to be transmitted by the transmit / receive element 122. , and may be configured to demodulate signals received by the transmit / receive element 122. As mentioned above, the WTRU 102 may have multi-mode capabilities. The transceiver 120 is configured to allow the WTRU 102 to communicate with a wireless LAN, such as UTRA and IEEE 802.11. Any device that has multiple transceivers to enable communication over multiple RATs good.

[0054] The processor 118 of the WTRU 102 controls the speaker / microphone 124, the keypad 1 26, and / or a display / touchpad / indicator 128 (e.g., LCD Display (Liquid Crystal Display: LCD) display device or organic light-emitting diode It is connected to an Organic Light-Emitting Diode (OLED) display device. The processor 118 may also receive user input data from the The data is fed to a speaker / microphone 124, a keypad 126, and / or a display / The touch pad / indicator 128 may also output the touch pad / indicator 128. In addition, the processor 118 may Any type of removable memory 130 and / or removable memory 132 The device may access information from and store data in suitable memory. The available memory 130 may be a random access memory (RAM). ), Read-Only Memory (ROM), hard disk, or any The removable memory 132 may include other types of memory storage devices. , Subscriber Identity Module (SIM) cards, memory sticks and Secure Digital (SD) memory cards. In one embodiment, the processor 118 is a server or a home computer (not shown). access information in memory that is not physically located on the WTRU 102, such as in Data may be stored there.

[0055] The processor 118 may derive power from a power source 134 and may be connected to other The power supply 13 may be configured to distribute and / or control power to the components. 4 may be any suitable device that provides power to the WTRU 102. For example, power supply 13 4 may include one or more dry batteries, solar cells, fuel cells, etc.

[0056] The processor 118 also generates location information (e.g., longitude, latitude, and latitude) to the GPS chipset 136. In addition to or instead of information from the GPS chipset 136, the WT The RU 102 communicates with a base station (e.g., Receive location information from base stations 114a, 114b) and / or from two or more nearby base stations The location may be determined based on the timing of the signal being received from the station. The U102 may obtain location information by any suitable location determination method while remaining consistent with an embodiment. It will be appreciated that this may also be achieved.

[0057] The processor 118 may further include additional features, functionality, or wired or wireless connectivity. One or more software and / or hardware modules that provide the functionality For example, the peripherals 138 may include: Various sensors such as accelerometers, biometric (e.g. fingerprint) sensors, e-compass , satellite transceivers, digital cameras (for photos or videos), Universal Serial Bus ( Universal Serial Bus (USB) port or other interconnection interface, vibration device devices, TV receivers, hands-free headsets, Bluetooth (registered trademark) Modules, Frequency Modulated (FM) radio units, digital music players Layer, Media Player, Video Game Player Module, Internet Browser etc. may be included.

[0058] The WTRU102 can be used in sensors, consumer electronics products, smart watches or smart clothing. Wearable devices, medical or e-health devices, robots, industrial equipment, other equipment or devices, such as a vehicle, car, truck, train, or airplane. The WTRU 102 may include one of the peripheral devices 138. via one or more interconnection interfaces, such as an interconnection interface; other components, modules, or systems of such equipment or devices May be connected.

[0059] FIG. 1C is a system diagram of the RAN 103 and the core network 106 according to one embodiment. As mentioned above, RAN103 adopts UTRA radio technology to improve the air interface. The RAN may communicate with the WTRUs 102a, 102b, and 102c through the RAN base station 115. 103 may also communicate with a core network 106. As shown in FIG. 103 communicates with the WTRUs 102a, 102b, and 102c through the air interface 115. Node-B1, each of which may include one or more transceivers for communicating with Node-B 140a, 140b, 140c may be provided. Each of the cells c may be associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a, 142b. It is understood that the number of Node-Bs and RNCs may be included while remaining consistent. Hello.

[0060] As shown in FIG. 1C, Node-Bs 140a and 140b communicate with an RNC 142a. In addition, the Node-B 140c may communicate with the RNC 142b. -B140a, 140b, 140c communicate with the corresponding RNs via the Iub interface. The RNCs 142a and 142b may communicate with the Iur Inter-Network Controllers (RNCs). Each of the RNCs 142a, 142b may communicate with each other via a Each Node-B 140a, 140b, and 140c connected to the In addition, each of the RNCs 142a, 142b may be configured to control the outer loop power. control, load control, admission control, packet scheduling, handover control, macro diversity to perform or support other functions, such as network connectivity, security functions, or data encryption. The present invention may be configured as follows.

[0061] The core network 106 shown in FIG. 1C includes a media gateway (M GW) 144, Mobile Switching Center (MSC) 146, Serving GPRS Support Node (SGSN) 148, and and / or Gateway GPRS Support Node (GPRS Node) Each of the above elements may include a GSN (Governing System No. 150). Although depicted as parts of the core network, any one of these elements may be part of the core network operator. You understand that the information contained herein may be owned and / or operated by entities other than Infosys. Let's do it.

[0062] RNC 142a in RAN 103 communicates with the core network via the IuCS interface. The MGW 144 may be connected to the MSC 146 in the network 106. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 may c, access to a circuit-switched network such as the PSTN 108, and 2a, 102b, 102c and conventional terrestrial communication devices.

[0063] RNC 142a in RAN 103 also communicates with the core network via the IuPS interface. The SGSN 148 may be connected to the GGSN 1 50. The SGSN 148 and the GGSN 150 may be connected to the WTRU 102a, 02b, 102c provide access to packet-switched networks such as the Internet 110 and provides a secure connection between the WTRUs 102a, 102b, and 102c and IP-enabled devices. It may be promoted.

[0064] As noted above, the core network 106 may also be owned by other service providers. and / or other wired or wireless networks operated The input / output 112 may be connected to the

[0065] FIG. 1D is a system diagram of the RAN 104 and the core network 107 according to one embodiment. As mentioned above, the RAN 104 adopts E-UTRA radio technology and The WTRUs 102a, 102b, and 102c may communicate with each other through the interface 116. The AN 104 may also be in communication with a core network 107.

[0066] The RAN 104 may include eNodeBs 160a, 160b, and 160c. Note that AN 104 may include any number of eNodeBs while remaining consistent with an embodiment. It will be understood that the eNodeBs 160a, 160b, and 160c are each to communicate with the WTRUs 102a, 102b, and 102c via the interface 116. , may comprise one or more transceivers. 160a, 160b, and 160c may implement MIMO technology. The de-B 160a transmits wireless signals to, for example, the WTRU 102a and Multiple antennas may be used to receive radio signals from 2a.

[0067] Each of the eNode-Bs 160a, 160b, and 160c is connected to a particular cell (as shown in FIG. and radio resource management decisions, handover decisions, uplink The present invention is configured to handle scheduling of users in the downlink and / or in the upstream. As shown in FIG. 1D, the eNode-Bs 160a, 160b, and 160c may They may communicate with each other through the X2 interface.

[0068] The core network 107 shown in FIG. 1D includes a mobility management gateway (Mobility Management Gateway). Management Gateway (MME) 162, a serving gateway 164, and a packet Including a Packet Data Network (PDN) Gateway 166 Although each of the above elements is depicted as part of the core network 107, Any one of these elements may be provided to an entity other than the core network operator. It is understood that the software may be owned and / or operated by

[0069] The MME 162 communicates with the eNode-B 1 in the RAN 104 via the S1 interface. 60a, 160b and 160c, respectively, and function as control nodes. For example, the MME 162 may bearer activation / deactivation; WTRUs 102a, 102b; 102c is responsible for selecting a specific serving gateway during the initial connection. The MME 162 may also communicate with the RAN 104 and other networks, such as GSM or WCDMA. A control plane function is provided to switch between other RANs (not shown) that employ radio technologies. The facility may also provide

[0070] The serving gateway 164 communicates with the RAN 104 via the S1 interface. Each of the eNode-Bs 160a, 160b, and 160c may be connected to a service node. The signaling gateway 164 generally provides a Routes and forwards user data packets from U102a, 102b, and 102c The serving gateway 164 may also serve as a user gateway during inter-eNodeB handover. The plane anchor, downlink data to WTRU 102a, 102b, and 102c Triggering paging when the WTRUs 102a, 102b, and 102c are available It may perform other functions such as managing and storing context.

[0071] The serving gateway 164 also notifies the WTRUs 102a, 102b, and 102c of the provides access to packet-switched networks such as the Internet 110 and the WTRU 1 PDs that may facilitate communication between 02a, 102b, 102c and IP-enabled devices N gateway 166.

[0072] The core network 107 may facilitate communication with other networks. The PSTN 108 and other networks are connected to the WTRUs 102a, 102b, and 102c. which circuit-switched network the WTRUs 102a, 102b, 102 c and traditional terrestrial communication devices. For example, the core network 107 serves as an interface between the core network 107 and the PSTN 108. IP gateways (e.g. IP Multimedia Subsystem (IMS) servers) that ) may be included in or in communication with the WTRU. 102a, 102b, 102c, owned and / or Access to network 112, which may include other wired or wireless networks operated access may be provided.

[0073] FIG. 1E is a system diagram of the RAN 105 and core network 109 according to one embodiment. The RAN105 uses IEEE802.16 wireless technology and has an air interface. 117, which communicates with the WTRUs 102a, 102b, and 102c. It may be an Access Service Network (ASN). As discussed, the different functional entities of the WTRUs 102a, 102b, 102c, and the RAN 105 The communication link between the entity and the core network 109 may be defined as a reference point. .

[0074] As shown in FIG. 1E, the RAN 105 includes base stations 180a, 180b, and 180c, and an AS N gateways 182, while the RAN 105 remains consistent with the embodiment. It will be appreciated that the system may include any number of base stations and ASN gateways. Each of the base stations 180a, 180b, and 180c is associated with a particular cell in the RAN 105. The WTRUs 102a, 102b may be associated with each other through the air interface 117. , 102c. In this case, the base stations 180a, 180b, and 180c may implement MIMO technology. Thus, the base station 180a, for example, transmits wireless signals to the WTRU 102a and the WTRU 102b. Multiple antennas may be used to receive radio signals from the U102a. Stations 180a, 180b, 180c also handle handoff triggers, tunnel establishment, wireless resource allocation, and Traffic management, traffic classification, and Quality of Service (QoS) policy enforcement The ASN gateway 182 may provide mobility management functions such as traffic management. It may act as a data aggregation point and also handle paging, caching of subscriber profiles, The router 104 may also be responsible for routing to the router network 109.

[0075] Air interface between the WTRUs 102a, 102b, 102c and the RAN 105 117 may be defined as the R1 reference point that implements the IEEE 802.16 specification. Each of the WTRUs 102a, 102b, and 102c has a logical interface (not shown) may be established with the core network 109. The logical interface between 102c and the core network 109 provides authentication, authorization, IP R2 Reference that may be used for host configuration management and / or mobility management It may be defined as a point.

[0076] The communication link between each of the base stations 180a, 180b, and 180c is As an R8 reference point that contains protocols to facilitate WTRU handover and transfer of data The base stations 180a, 180b, and 180c and the ASN gateway 182 may be defined as The communication link between the WTRU 102a and the WTRU 102b may be defined as the R6 reference point. , 102b, 102c, respectively, based on the mobility events associated with each of the mobility events. The protocol may include protocols that facilitate security management.

[0077] As shown in FIG. 1E, the RAN 105 may be connected to a core network 109. The communication link between the AN 105 and the core network 109 is for example for data transfer and It may be defined as the R3 reference point that contains protocols that facilitate mobility management capabilities. The network 109 is a Mobile IP Home Agent (MHA). MIP-HA) 184, Authentication, Authorization, Accounting The above elements may include an authentication, authorization, and accounting (AAA) server 186, and a gateway 188. Each is represented as part of the core network 109, but among these elements Any one of the following is owned and / or operated by an entity other than the core network operator: It will be understood that the information may be subject to change or manipulation.

[0078] The MIP-HA may be responsible for IP address management and may also 02b, and 102c are localized between different ASNs and / or different core networks. The MIP-HA 184 may enable the WTRUs 102a, 102b to b, 102c to provide access to packet-switched networks such as the Internet 110 and facilitates communication between the WTRUs 102a, 102b, 102c and IP-enabled devices. The AAA server 186 serves to support user authentication and user services. The gateway 188 may facilitate interworking with other networks. For example, the gateway 188 may provide the WTRUs 102a, 102b, and 102c with a PS Provides access to circuit-switched networks such as TN108 and WTRU102a, 10 2b, 102c and conventional terrestrial communication devices. The WTRUs 102a, 102b, and 102c are connected to the other service providers. This may include other wired or wireless networks owned and / or operated by The network 112 may provide access to the network 112 .

[0079] Although not shown in FIG. 1E, the RAN 105 may be connected to other ASNs, and It will be appreciated that the core network 109 may be connected to other core networks. The communication link between the RAN 105 and other ASNs is A protocol for coordinating mobility of the WTRUs 102a, 102b, and 102c between the The R4 reference point may be defined as the R4 reference point that may include the core network 109 and other cores. The communication link between the home core network and the visited core network is R5 reference point may be defined which may include protocols facilitating the interconnection between stomach.

[0080] The core network entities described herein and illustrated in FIGS. are identified by the names given to those entities in existing 3GPP specifications. However, in the future, those entities and functions may be identified by other names. Certain entities or functions may be subject to change without notice, including future 3GPP NR specifications. Please understand that these may be combined in future specifications published by 3GPP. It should be understood, therefore, that the particular network entities described and illustrated in FIGS. The properties and functions are provided by way of example only, and the subject matter disclosed and claimed herein may Any similar provisions, whether now prescribed or hereafter prescribed, It should be understood that the present invention may be embodied or implemented in a communications system.

[0081] The 5G core network 170 shown in FIG. 1F includes an access and mobility management function (AMF ) 172, Session Management Function (SMF) 174, User Plane Function (UPF) 176 , User Data Management (UDM) 178, Authentication Server Function ( Authentication Server Function (AUSF) 180, network exposure function Function (NEF), Policy Control Function (PCF) 184, Non-3GPP Interworking Function (Non-3Gpp Interworking Function: N3IWF) 192, and application functions Each of the above elements may include the 5G Core Network1 Although depicted as part of the 70, any one of these elements may be part of the core network. may be owned and / or operated by entities other than the network operator. It will be understood that the 5G core network will not consist of all of these elements. may consist of additional elements, and multiples of each of these elements may It should also be understood that each network function may be configured with are shown in Figure 1F as being directly connected to each other, but Communicated through a routing agent such as an agent or message bus It should be understood that there are cases where

[0082] AMF172 connects to RAN103 / 104 / 105 / 10 via the N2 interface. 3b / 104b / 105b and function as a control node. For example, the AMF 172 may perform registration management, connection management, reachability management, access authentication, and the like. The AMF 172 may be responsible for granting access to the WTRUs 102a, 102b, and 102c. 02b, 102c may route and forward NAS packets to / from them.

[0083] The SMF 174 may be connected to the AMF 172 via an N11 interface. , may be connected to the PCF184 via the N7 interface, and N4 interface The SMF 174 may be connected to the UPF 176 via a For example, the SMF 174 may be used for session management, , IP address allocation in 102c, management of traffic steering rules in UPF 176, and The IEEE 802.11b may be responsible for the configuration and generation of downlink data notifications.

[0084] The SMF 174 may be connected to the UPF 176, which provides access to the Internet 1 10, the WTRU to access the Data Network (DN) 190 102a, 102b, and 102c, and The SMF 174 may facilitate communication between N4 and P-enabled devices. The traffic steering rules within the UPF 176 may be managed and configured via the UPF 176. 76 is a packet data unit (PDU) session and data network Interconnection with the network, packet routing and forwarding, policy rule enforcement, user Quality of service processing for plane traffic and buffering of downlink packets It may also serve as a ring.

[0085] The AMF172 may be connected to the N3IWF192 via the N2 interface. The N3IWF communicates with the WTRU over a non-3GPP-defined air interface technology. Facilitates connectivity between 102a, 102b, 102c and the 5G core network 170.

[0086] The PCF 184 may be connected to the SMF 174 via an N7 interface; It may be connected to the AMF172 via the N15 interface, and the N5 interface The PCF 184 may be connected to an Application Function (AF) 188 via a provides policy rules to control plane nodes such as AMF172 and SMF174. Each control plane node may then be able to enforce these rules.

[0087] The UDM178 acts as a repository for authentication credentials and subscription information. The UDM is connected to other functions such as the AMF172, SMF174 and AUSF180. You may do so.

[0088] The AUSF180 performs authentication related operations and transmits the UDM1 through the N13 interface. 78, which connects to the AMF 172 via the N12 interface.

[0089] The NEF exposes capabilities and services within the 5G core network 170. The NEF may connect to the AF 188 via an interface and other control plane and user plane functions (180, 178, 172, 172, 184, 176 and N 3IWF) to export the capabilities and services of the 5G core network170 You may zoom in.

[0090] The 5G core network 170 may facilitate communication with other networks, such as The core network 170 is an interface between the 5G core network 170 and the PSTN 108. IP gateways (for example, IP multimedia subsystems) that act as interfaces For example, the core network may include or communicate with an Internet Management System (IMS) server. 170 is a short message service that facilitates communication via short message service. It may also include or communicate with a service (SMS) service center. For example, The 5G core network 170 is a network between the WTRUs 102a, 102b, and 102c and the server. In addition, the core network 170 may facilitate the switching of non-IP data packets. The WTRUs 102a, 102b, and 102c may include WTRUs owned and operated by other service providers. and / or other wired or wireless networks operated Access to 2 may be provided.

[0091] Figure 1G shows the RAN 103 / 104 / 105, the core network 106 / 107 / 109 , PSTN 108, the Internet 110, or some other network 112. The various nodes or functional entities of the communication network shown or described herein may be An exemplary computing system in which one or more devices of the present invention may be embodied. FIG. 9 is a block diagram of a system 90.

[0092] The computing system 90 may include a computer or a server, The form of the software (including the location or The method may be implemented primarily by computer readable instructions, which may be implemented by any means. Such computer readable instructions may be implemented by the computing system 90. The processor 91 may be a general purpose processor. processors, special purpose processors, conventional processors, digital signal processors (DSPs), Multiple microprocessors, one or more microprocessors associated with a DSP core Processors, controllers, microcontrollers, application specific integrated circuits (ASICs), Field Programmable Gate Array (FPGA) circuits, any other type of integrated circuit ( The processor 91 may be a digital integrated circuit (IC), a state machine, etc. processing, power control, input / output processing, and / or communication with the computing system 90 It may also implement any other functionality that enables it to operate within a network. Processor 81 is an optional processor distinct from main processor 91 and The processor 91 and the processor 92 may perform additional functions or assist the processor 91. and / or co-processor 81 for processing data related to the methods and apparatus described herein. The system may receive, generate and process data.

[0093] In operation, the processor 91 fetches, decodes, and executes instructions to perform computing The information is transmitted to other resources via the system bus 80, which is the main data transfer path of the operating system. Such a system bus transfers data to and from the computer's resources. Connects components within the operating system 90 and defines a medium for data exchange The system bus 80 typically includes data lines for transmitting data, address lines, and Address lines for sending data, and interrupts and manipulating the system bus. An example of such a system bus 80 is a PCI (Peripheral Computer Interface) The NI PXI Express Component Interconnect bus is a NI PXI Express Component Interconnect bus.

[0094] The memories coupled to the system bus 80 include random access memory (RAM) 82 and and read only memory (ROM) 93. Such memory is used for storing and reading information. ROM 93 generally cannot be easily modified. The data stored in RAM 82 may be used by the processor 91 or other It can be read or modified by the hardware device. Access to M82 and / or ROM93 is controlled by memory controller 92. The memory controller 92 converts the virtual address into a physical address when an instruction is executed. The memory controller 92 may provide an address translation function to convert the It also isolates processes within the system and isolates system processes from user processes. Therefore, a program operating in the first mode may provide a memory protection function. A process can only access memory that is mapped by its own process virtual address space. can access the same file as another process unless memory sharing between processes is configured. It is not possible to access memory within the virtual address space of

[0095] In addition, the computing system 90 includes a processor 91, a printer 94, 84, mouse 95 and disk drive 85. The peripheral controller 83 may also be responsible for:

[0096] The display 86 controlled by the display controller 96 is 90. Visual output includes text, graphics, animated graphics, and video. Visual output is a graphical user interface (GUI). The display 86 may be a CRT-based video display. Play, LCD-based flat panel displays, gas plasma-based flat panel displays It may be implemented as a panel display or touch panel. The converter 96 supplies the power needed to generate the video signal that is sent to the display 86. Contains child components.

[0097] Further, the computing system 90 includes the RAN 103 / 104 / 10 of FIGS. 5. Core network 106 / 107 / 109, PSTN 108, Internet 110 or other network 112. 90 so that the computing system 90 can Allows communication with other nodes or functional entities of the network, e.g. The communication circuitry may include a communication circuit such as a network adapter 97. The communication circuitry may be provided alone or in a In combination with the processor 91, certain devices, nodes, or functions described herein may It may be used to implement the transmitting and receiving steps of the entity.

[0098] Any or all of the devices, systems, methods and processes described herein The present invention relates to a computer-executable instruction (e.g., a program) stored on a computer-readable storage medium. The instructions may be embodied in the form of a program code, which is transmitted to the processor 118 or 9. When executed by a processor, such as a processor 1, the processor is caused to implement the system described herein. It is understood that the systems, methods, and processes described herein may be implemented and / or performed. Any step, operation, or function described herein may be implemented by any such computer. Implemented in the form of computer-executable instructions for wireless and / or wired network communications The method may be executed by a processor of a configured device or a computing system. A computer-readable storage medium is any non-transitory (e.g., tangible or physical) medium for storing information. Volatile and non-volatile media, removable and non-removable, implemented in any logical method or technology Such computer readable storage media, including removable media, do not include signals. The computer-readable storage medium may include RAM, ROM, EEPROM, flash memory, etc. Memory or other memory technology, CD-ROM, Digital Versatile Disk (DVSD) DVD or other optical disk storage devices, magnetic cassettes, magnetic tapes, magnetic Disk storage device or other magnetic storage device or devices for storing desired information Any information that can be used for This includes, but is not limited to, any other tangible or physical medium.

[0099] Figure 2A illustrates a service-based interface within the network control plane. FIG. 1 is a block diagram of a non-roaming network architecture of a 5G network. FIG. 2B illustrates another view of the 5G network of FIG. 2A and shows various network functions. FIG. 1 is a block diagram illustrating the reference points through which the mobility management and Note that the session management functions are separated. Registration Management and Connection Management (RM / CM) A single N1 NAS connection is used for both the SM and SM related messages and procedures. A single N1 termination point is located in the AMF. The AMF stores SM-related NAS information. The AMF manages registration and NAS signalling exchanged with the UE. The SMF handles the NAS signalling exchanged with the UE. The session management part is handled by the

[0100] The 5G system architecture is based on Network Function Virtualization (NFV). alization (NFV) and Software Defined Networking Data connectivity and networking to enable deployment using technologies such as Software Defined Networking (SDN) The 5G system architecture is defined to support the identified Control Plane (CP) network functions to leverage service-based interactions To be designed.

[0101] As described above, an NF is a set of defined functional operations and defined interfaces. NF is a processing function in a network that has a dedicated hardware. as a component or as a software instance running on dedicated hardware, Alternatively, you can run the instance on a suitable platform, such as a cloud infrastructure. In some cases, it may be implemented as an integrated virtualization function.

[0102] Furthermore, as described above, NF services are implemented through a service-based interface. F ("NF Service Producer") and other authorized NFs ("NF Service Providers"). NF is a type of capability exposed to a single "capability consumer." An NF service may expose multiple NF services. In general, an NF service is a service that A NF may provide capabilities to a given consumer. The NFs may provide different capabilities and therefore different A NF may provide different NF services to its consumers. Each service is self-contained, reusable, and provided by the same NF. Use a management scheme that is independent of other NF services, e.g. scaling, repair, etc. Each NF service is designed to be accessible through an interface. An interface may consist of one or more operations. FIG. 3 shows the relationship between NFs, NF services and their operations.

[0103] Within this NF service framework, there are two network functions: consumer and processor. Interaction between the QoS and the QoS producers follows two mechanisms:

[0104] "Request-Response": The control plane NF_B (NF service producer) sends a request to another control plane An action is performed by lane NF_A (NF service consumer), or provide certain NF services, provide information, or both NF_B provides NF services based on the request of NF_A. To satisfy this, NF_B may in turn consume NF services from other NFs. In this request-response mechanism, the communication is between two NFs (consumer and producer). ) and the producer's one-time response to a consumer request is , within a certain time frame. Figure 4 shows the request-response communication mechanism. This shows the flow of the theory.

[0105] "Subscribe-Notify": The control plane NF_A (NF service consumer) NF services provided by another control plane, NF_B (NF service producer) Multiple control plane NFs can subscribe to the same control plane NF service. The NF_B may subscribe to the results of this NF service. The subscription request notifies interested NFs that they are subscribing to the service. NF service consumer to which event notifications from the F service producer need to be sent. It also contains the notification endpoint (e.g., notification URL) for the subscription. The request can be a periodic update or a notification triggered through a certain event (e.g., This includes notifications when requested information changes, a certain threshold is reached, etc. Figure 5 shows the flow of the subscription-notification communication mechanism.

[0106] As an example, Table 1 is based on 3GPP TS 23.502, Procedures for the 5G System; Stage AMF services and AMF defined in 2, v15.1.0, Release 15, 2018-03 Indicates a service operation.

[0107] [Table 1]

[0108] Network slicing is a technology that is used to scale up mobile operators' networks, backhaul and behind the air interface across the fixed parts of both the When used by mobile network operators supporting "ideal" networks This is a mechanism that can be used to Multiple virtual networks supporting different service types operating across a single RAN This is done by "slicing" the network into separate networks. For example, different market segments may require different requirements in terms of functionality, performance, and independence. Customized network to provide optimized solutions for your scenarios This allows the operator to create the workpiece.

[0109] As described above, a network slice is a set of specific network capabilities and network A PLMN may contain a logical network that provides network characteristics. The network services include the core network control plane and user plane NFs. A Rice instance is a set of NF instances that form a deployed network slice. The set and required resources (e.g., computing, storage and network Includes the following:

[0110] Network slicing is a combination of supported characteristics and network function optimizations. In such cases, the network slice may be divided into different slices / services. An operator may distribute the same characteristics to different groups of UEs. There are cases where multiple network slice instances are deployed, e.g. Network slice instances deliver different committed services and / or or customer specific, in which case such a network slice , through different slice identification information, although they may be of the same slice / service type. be identified.

[0111] The network, through the 5G-AN, will notify the UE of the access type through which it is registered. (i.e., 3GPP access and / or N3GPP access) One or more network slices associated with up to eight different S-NSSAIs A service instance may be used to provide services to a single UE at the same time. The AMF instance providing the service is the network slice that provides the service to the UE. In other words, this AMF instance belongs to each of the U It is common to each network slice instance that serves E.

[0112] A network slice is identified by an S-NSSAI, which consists of: . Slice / Service Type (SST): Envisioned in terms of characteristics and services Network slicing operation. Slice Identification (SD): Multiple networks of the same slice / service type Optional information supplementing the slice / service type to identify the slice.

[0113] S-NSSAI is a standard value (i.e., such an S-NSSAI is a standardized SST value). Includes only SSTs but not SDs) or non-standard values ​​(i.e., such SN The SSAI includes both SST and SD, or SST only without standardized SST values. S-NSSAI with non-standard values ​​may have a PL Identifies a single associated network slice in the MN. SN includes non-standard values The SSAI is not associated with any PLMN other than the one with which the S-NSSAI is associated. It is not used by the UE in the access stratum procedures. Table 2 is based on 3GPP TS 23.501, System Architecture for the 5G System; Stage 2, v15.1.0, Release 15, 2018-0 The standardized SST values ​​defined in [3] are shown.

[0114] An NSSAI is a collection of S-NSSAIs. An NSSAI is a set of NSSAIs, It can be an NSSAI, or an Authorized NSSAI. The grant and request NSSAIs sent in the nulling message may contain up to eight S-NSSAs. I exists. A request NSSAI is signaled by the UE to the network. The AMF, network slice, and network providing the service for this UE This allows the network to select the slice instance.

[0115] [Table 2]

[0116] Based on the operator's operation or deployment needs, one network slice instance can be An instance may be associated with one or more S-NSSAIs and may be associated with one S-NSSAI. An NSSAI may be associated with one or more network slice instances. Multiple network slice instances associated with the same S-NSSAI The services may be deployed in the same or different tracking areas. Multiple network slice instances associated with the same tracking area When deployed in S-NSSA, the AMF instance serving the UE will Logically belonging to two or more network slice instances associated with I is (i.e., common).

[0117] With reference to Figure 6 and as mentioned above, 5GC will be a network slicing and virtualization Defined a Service-Based Architecture (SBA) based on the concept of Network Functions (NF) Different network functions (e.g. AMF, SMF and PCF) support service-based It provides different network function services through the service interface. The same messages and procedures are used by service consumers to communicate with service providers. For example, any NF may use the Event Exposure Services may subscribe to the same events as other Event Exposure Services. On the one hand, Non-IP Data Delivery (NIDD), Background Data Transmission (BDT), and Various network capabilities such as NF services and Power Save Mode (PSM) are Under the current SBA framework, the UE communicates with the network. The network is configured and configured by indicating a request NSSAI that identifies the network slice. However, the UE may directly indicate the desired network capabilities. There is no way to do this.

[0118] For example, vehicles running V2X applications may transmit data in the background (B DT), Multimedia Broadcast / Multicast Service (MBMS) and Event monitoring capabilities may need to be used. The UE or the corresponding V2X application is configured to ensure that the network slice has the desired network capabilities. Either the application server or the application server must establish a configuration with the core network (CN). On the other hand, smart home devices that integrate sensors and cameras are D. Networking such as data buffering, group messaging and device triggering The device may need to utilize a different set of work capabilities without human intervention. Many IoT devices do not have a common graphical interface. There are different levels of input from the device (e.g., level of network capability, network based on the level of the work slice identifier, or the level of the NF service It is desirable for the network to be able to automatically configure the network slices.

[0119] Furthermore, as mentioned above, the service-based architecture of 5GC will Each network function is a service-based interface. It provides a set of network function services through the (e.g., event monitoring, location services) defines a set of network function services. It may be implemented through any entity (e.g. NF, UE and SCS / An AS may subscribe to a service by participating in the same operation. However, there are some limitations to the existing SBAs defined by the 5GC.

[0120] First, the granularity of network function services hinders flexible network capability configuration. Each Network Function provides different Network Function services in different ways. (For example, AMF provides mobility management, location management, and event monitoring / export.) Each network capability provides different services from different network functions. For example, IoT The device can then configure the MIoT service by setting the slice / service type value to MIoT. However, some specific network features may be required. There is no way for the UE to indicate capabilities such as non-IP data delivery or event monitoring / reporting capabilities. In this example, the V2X application server (AS) transmits background data (BD T) Capability Availability may be required. Current Network Capability Framework Based on this, the BDT capability includes the BDT policy provided by the PCF. The Npcf_BDTPolicyControlNF service provided by NEF, and the Nnef_BDTPNe The GotiationNF service is required. In addition, the Nsmf_PDUSessi provided by SMF on is required to manage the PDU session for future data transfer. It is difficult for the UE / AF / AS to determine the required network function services. To enable BDT, the UE or SCS / AS must provide these network function services. The UE and AS do not need to be aware of the network capabilities rather than the NF services. They will be more interested.

[0121] Second, when the UE registers with the core network, e.g., in a request NSSAI, However, this may provide an indication of the type of slice you want to The information may be PLMN specific and non-standardized, resulting in, for example, The UE may not recognize when the E registers for the first time or when the UE roams. In such cases, the UE may include this information when attempting to register with the network. can't.

[0122] Third, some IoT devices have constraints, so the core network may need to be automated. Network capability configuration allows those devices to dynamically configure their network capabilities. Based on existing methods, it is hoped that the present invention will help dynamically add or Deleting (i.e., updating the network slice to which the UE registers) This will trigger a configuration update process, which in turn triggers a registration process, and in some cases Therefore, the UE needs to repeatedly enter IDLE mode and then the registration process. This should not be necessary, and is not feasible for constrained IoT devices. It may be too complicated.

[0123] Fourth, the scope of the existing SBA is limited to the control plane NF. The Upward Proxy Function (UPF) is not involved. UPF provides some control functions such as QoS enforcement and event monitoring. It has the function of Service-Based Interface and UPF to improve SBA. It is desired to define a service.

[0124] Fifth, the UE sends a registration request to the core network, but the UE does not There is no way to demonstrate competence.

[0125] Sixth, the UE receives an authorization NSSAI when registering with the network. The UE knows whether the required capability can be supported by the authorized NSSAI. do not.

[0126] Seventh, if there is a change in the UE context, e.g. the UE moves from EPS to 5G or when updating the network capabilities of a slice (e.g., maximum data rate). If required by an AS that has a PCC rule and network license for the UE, A change in the UE's service information (and therefore a change in the NCP) may be required. There may be the ability to communicate such changes to the UE as policy updates. E-Policy may need to be expanded to incorporate NCP. 5GS is U E.

[0127] Eighth, a network slice has a maximum number of PDU sessions that can be processed simultaneously. The number of PDU sessions may be limited. UE uses network slices to establish PDU sessions. When attempting to establish a new network, and the network slice capacity reaches its peak, U E. 5G systems currently do not address this situation.

[0128] Ninth, another network capability handles the maximum number of UE registrations per network slice If a UE attempts to register to a network slice and If the network capacity for the maximum UE registrations reached its limit, the UE will terminate the registration. You can't. The current 5GS doesn't address such cases.

[0129] A UE application attempts to initiate a data flow (e.g., an IP data flow). At that time, the UE needs to determine the slice and data network associated with the flow. 5G systems provide one way to solve this problem in URSP. The rules include an application identifier, which limits traffic from a given application. In some cases, the UE is instructed on how to route traffic. Disadvantages of this approach uses an application identifier that matches the installed application. The UE needs to be configured with the slice and data network associated with the flow. Another approach to determining the network to which a flow needs to be associated is to - Enabling the UE to indicate NSSAI and data network (DNN) The drawback of this approach is that it is difficult to implement the UE application using S-NSSAI and DNN. The application must be configured and these parameters must be visible to the network. It is necessary for it to be possible.

[0130] The network capabilities of the slice and how these capabilities are configured in the slice The present disclosure provides a method and apparatus for enabling a network to indicate to a UE whether a This information allows UE applications to indicate to the UE the capabilities they require. It may be used by the UE in situations where it is possible to During RSP evaluation, determine the slices and PDU sessions used for data flow. The UE can use this information when it needs to know the network The UE indicates its network capabilities and their desired configuration to the network and transmits it in the desired configuration. A method by which a network can provide a UE with slice identifiers that can provide these capabilities Also disclosed.

[0131] Explain the concept of Network Capability Profile (NCP). NCP is a slice Below is a list of the network capabilities and how each is organized. These are presented below.

[0132] Issues with existing service-based architectures and corresponding NF frameworks The technical solutions for this are disclosed below. These solutions are based on the service-based architecture. This allows for more dynamic and flexible operation in the architecture and is also useful for end users (i.e. Improved programmability of service-based architecture for UE and AS Desired network connectivity through service-based interfaces and procedures. To make it easier for users (e.g., UE and AS) to configure the network capabilities and characteristics, The following items will be explained.

[0133] First, we describe a new framework that includes the network capability layer. and ASs must increase their network capabilities (e.g. ,Background data transmission,Non-IP data delivery,Maximum DL / UL data rate of UE , Maximum delay tolerance, Maximum guaranteed DL throughput, Group characteristics, Message delivery options In one implementation, the UE and the AS may dynamically request a network Which network slices support or provide the network capabilities Knowing whether the network slice you are connecting to supports the requested network capabilities Core network entities may not need to have knowledge or care about Determine or configure a network slice that supports all required network capabilities You may do so.

[0134] Second, the network determines the network capability profile (N A mechanism by which network capability information, referred to herein as CP, may be delivered to a UE. Based on the required network capabilities, the corresponding network capability profile is created. The method by which the network may inform the UE about the alternative network slice containing the This will also be described.

[0135] Third, the UE uses a network capability base to configure its desired network capabilities. This article will show you how to start registering your account.

[0136] Fourth, the UE uses the network capability base to configure its desired network capabilities. This article describes how to start registering your account.

[0137] Fifth, the UEs are already registered in the network and have their network capabilities UE initiates network capability-based registration update when dynamic reconfiguration is required The method will be described.

[0138] Sixth, the NF or application server creates the network slice for the UE. Network Capability Based UE Configuration Update to enable initiation of network capability update process A new method is described.

[0139] Seventh, the security of authorized NSSAIs including their corresponding NCPs during the basic UE registration procedure. This disclosure discloses a method by which the UE can receive the packet indicated by the received NCP. If the capabilities provided by the UE are not sufficient for the UE's application, the UE shall Select an alternative network slice based on the NCP list of authorized S-NSSAIs received from It may be possible to request it.

[0140] Eighth, the network slice is updated as part of the UE policy during the UE policy update procedure. The method by which the NCP is delivered to the UE is disclosed.

[0141] Ninth, the core network must establish a PDU session for each network slice during the PDU session establishment procedure. Enforces the maximum number of PDU sessions for each request and rejects requests that arrive after the maximum limit is reached. The method of processing is disclosed.

[0142] Tenth, the core network must maximize the number of PDU sessions per network slice. We disclose a method to handle the maximum limit, where the UE waits before retrying. via NAS messages, so that a network slice can be The network periodically notifies the UE that a

[0143] 11. The core network enforces the maximum number of UE registrations per network slice. The present invention discloses a method for handling registration requests received after the maximum limit has been reached.

[0144] 12. The interface with the User Plane Function (UPF) and the UPF An extended service-based architecture is described that includes the services offered.

[0145] In accordance with these aspects, a network capability to support the application is provided. To configure the UE, the UE may send a network capability configuration request, and the UE may A network slice is provided along with an identification of the network slice that supports the desired network capabilities. Based on these characteristics, the network that receives the request may receive a network capability configuration response. A network entity may perform one or more of the following operations: The network slice providing the service supports the required network capabilities. Checking the network capability profile to determine whether the . A new network slice that provides the UE with all the required network capabilities Selection of. UE can be served by any existing network slice If this is not possible, a new network is created that provides the UE with all the required network capabilities. Starting a slice (instance). NAS signaling with the UE to provide the newly selected network slice Select the new entity to terminate on. Update the network capability profile of the selected network slice. Respond with information about the network slice and network capabilities that provide the service Response to the UE.

[0146] The network capability profile may include one or more of the following: Identifiers of the network slice and the corresponding network slice instance . · An identifier for the list of supported network capabilities. - Serving PLMN Identifier. · Area information providing service by network capabilities.

[0147] The network capability configuration request may include one or more of the following: Identification of one or more desired network capabilities. · Identification of the application requiring network capabilities. A configured NSSAI or an authorized NSSA that the UE was assigned to during a previous registration process NSSAI which may be I. An identifier associated with the UE. Area information that serves the requested network capabilities. · Availability schedule for required network capacity. · The QoS level of network capabilities required (e.g. service response time). The desired level of multi-tenancy (e.g., one or more network capabilities) (The number of applications in the UE that require the use of power).

[0148] Further according to the above aspect, the network entity performs one or more of the following operations: may carry out multiple measures. A network entity that triggers a network capability configuration update procedure for the UE. Receive a network capability configuration request from the service. New network slices and / or NAS signal termination points for the UE Or determine if a new network entity needs to be selected. Selection of a new network slice and / or NAS termination point for the UE. Sending a configuration update message to the UE. Sending a response to the triggering network entity.

[0149] The network entity receiving the request may further perform one or more of the following: This may be the case. The network slice providing the service supports the required network capabilities. Checking the network capability profile to determine whether the . A new network slice that provides the UE with all the required network capabilities Selection of. NAS signaling with the UE to provide the newly selected network slice Select the new entity to terminate on. Update the network capability profile of the selected network slice. - Communication with information on the network slice and network capabilities that provide the service Transmission of the information to the UE.

[0150] Alternatively, the network entity may initiate a network capability configuration update procedure for the UE. Instead of triggering the application server to send a network capability configuration request, The trigger for the process may be determined by:

[0151] The UE may do one or more of the following: Submitting a registration request. Receipt of the registration response, which contains the NCP of the network slice.

[0152] Further according to the above-mentioned embodiment, one or more of the following operations may be performed. The response may come from the AMF. -AMF retrieves subscribed S-NSS from UE subscription information in UDM. May acquire AI NCP. AMF receives authorization from another network function such as UDM, NSSF or NRF. -May obtain NCP from NSSAI. The response may contain an S-NSSAI that was not included in the registration request and The request may include the NCP of each S-NSSAI. Based on the NCP list in the S-NSSAI received from the core network, the UE An alternative network slice may be required.

[0153] The UE may receive an NCP as part of the UE policy received in a NAS message. good.

[0154] Further according to the above aspect, the network entity performs one or more of the following operations: may carry out multiple measures. Receiving a trigger to update the UE's NCP policy. UE policy and NCP policy (NCP policy) in S-NSSAI to be sent to the UE Check the latest PSI to find the National Committee on Policies (NCCP). · Integration of NCPP with UE Policy. · Delivering the NCPP to the UE using the UE Policy Container.

[0155] Further according to the above aspect, when selecting a route during evaluation of the URSP rule, the UE may The UE may use information in the NCPP. For example, the UE may associate with a higher priority route. In situations where the maximum data rate of the assigned slice is low, the lower priority RS They may choose to establish the route described in D.

[0156] The UE may do one or more of the following: Attempts to establish a PDU session with the network. Rejected with a cause code indicating that the maximum PDU session limit for the slice has been reached and receive wait timer. PDU until the waiting timer expires or the UE stops the PDU session. No session establishment attempts are made.

[0157] Further according to the above aspect, the network entity performs one or more of the following operations: may carry out multiple measures. Increment or decrement the count each time a PDU session is established or terminated. Use of a counter that increments or decrements. Blocks UE requests to establish PDU sessions as soon as the maximum limit is reached In response, the UE may transmit a cause code to the UE. Includes the reason for access denial along with the timer.

[0158] The UE may do one or more of the following: NAS notification that the maximum PDU session limit has been reached and a wait timer Received. Wait until the waiting timer expires before requesting PDU session establishment, or Wait for E to stop another PDU session for the same slice.

[0159] Further according to the above aspect, the network entity performs one or more of the following operations: may carry out multiple measures. Increment or decrement the count each time a PDU session is established or terminated. Use of a counter that increments or decrements. · Notify the UE when the condition is resolved.

[0160] Further according to the above aspect, the UE may perform one or more of the following operations: There is. A NAS message is received from the network indicating the condition has been resolved. Reset the wait timer and retry the PDU session establishment process. Wait until the wait timer expires and retry the PDU session establishment process.

[0161] The UE may perform one or more of the following operations: · Request for UE registration procedure. Rejection with cause code indicating maximum UE registration limit reached and wait timer will be done. Until the waiting timer expires or any UE is deregistered from the slice The UE will not be asked to register until

[0162] Further according to the above aspect, the network entity performs one or more of the following operations: may carry out multiple measures. Increment or decrement the count each time a UE registers or deregisters. Use of counters to measure. As soon as the maximum limit is reached, the network entity blocks the UE's registration request. In some cases, the UE may lock and send a cause code to the UE in response. contains the reason for the access denial along with a wait timer. · Notify the UE that the condition has been resolved.

[0163] Further according to the above aspect, the UE may perform one or more of the following operations: There is. · Obey the wait timer. A NAS message is received from the network indicating the condition has been resolved. · Resetting the waiting timer and retrying and attempting the UE registration request.

[0164] (Network Slicing Framework for 5G Core Networks) Figure 7 shows a network slice (including the corresponding NFs and NF services) and a UE / A Has a network capability layer between S (e.g., BDT, NIDD and event monitoring) The network architecture shown in the figure is the network slice structure. This allows for finer granularity in the configuration and allows UE / AS to configure their network characteristics The new layer may include a logical layer, which makes it easier to Alternatively or additionally, the desired network slice type may be indicated. By indicating capabilities (e.g. BDT, NIDD and event monitoring), the UE and It allows the SCS / AS to request desired network capabilities.

[0165] The UE / AS sends a direct request to the core network indicating the desired network capabilities In some cases, a new NF (herein referred to as the Network Capability Management Function (NCMF)) may be used. The network slices that provide the desired network capabilities to the UE / AS are constructed. The NCMF may act to create network capabilities within the core network. Layer management functions may be implemented.

[0166] The new NFs enable finer granularity for configuring network services. On the one hand, the UE / AS may be aware of the available NFs and NF services. without requiring network capabilities (e.g. background data transmission, This allows the network slicing to directly indicate how The UE / AS can provide a particular capability without the UE / AS having to have knowledge of what capability the UE / AS provides. The UE and AS can request the network for their applications. On the other hand, some may be interested only in the level of core network capabilities. The entity is required to change the existing framework due to the demands from the UE / AS at the level of network capabilities. The system allows operations at the NF and NF service levels without any changes to the network framework. May be maintained.

[0167] The NCMF may have one or all of the following functions:

[0168] First, the NCMF provides a mapping between network capabilities and NF services. That is, the mapping information may support network capabilities. It may indicate the set of NFs and corresponding NF services that are required to support This information can be used to determine which NFs and NF services are included in the network slice. Whether a network slice can support a network capability depends on whether There may be a judgement.

[0169] Second, NCMF is a network that is supported by network slices. A network administrator may administer and maintain a profile that contains information identifying a set of capabilities. The network capability profile information is used by the UE / AS to determine the network capabilities for that application. This can be useful when requesting additional or updated network capabilities.

[0170] Third, NCMF also provides network operation and management (OAM) services. &M) system to manage network slices, NFs, and NF services. The NCMF may also obtain information about the network and / or device capabilities of the NCMF. To support the desired network capabilities, network slices, network segments, The O&M system manages the Rice instances, NFs, and / or NF services. may be requested.

[0171] NCMF stands for Standalone Network Function, AMF, SMF, or PCF, etc. A logical function that resides in, or is provided by, another network function in It may also be a service that is provided.

[0172] (Mapping information between network capabilities and NF services) Determine whether a network slice can support a particular network capability A matrix indicating the NF services that are required to support the network capabilities in order to For example, background data transmission (BD T) Capability is provided by the PCF to determine the BDT policy. The cyControl service and the Nnef_BDTPNegotiation service provided by NEF In addition, the Nsmf_PDUSession service provided by SMF is expected to be It may be necessary to manage PDU sessions for data transfer. Table 3 shows the to provide mapping information between network capabilities and their required NF services An example of a data structure is shown below.

[0173] [Table 3]

[0174] The NCMF may obtain mapping information from the network O&M system. The ping information may be managed and stored in the NCMF. The NCMF may be managed by the NSSF or the NR F, so that the above mapping can be used in the NSSF or NRF as well. The ping information may be managed and stored.

[0175] (Network Capability Profile) The network capability profile is a network slice maintained by the NCMF. Each network slice may contain an information profile for each Table 4 shows the network capabilities of a given network slice. An example of an information field that may be included in a capabilities profile is shown below. Please note that a profile (NCP) is a set of per slice information elements.

[0176] [Table 4-1] [Table 4-2]

[0177] The NCMF may manage and retain the information set out in Tables 3 and 4. The network NF adds or removes network capabilities from the UE / AS. A request to update (e.g., modify one or more parameters of a network capability) If a request is received, the request is forwarded to a network slice that has already been requested to serve the request. The request will be forwarded to the NCMF to determine whether the device supports network capabilities. If the network slice does not support the network capability, the NCM F is the network that provides the service to support the requested network capability. It may further determine whether a service slice can be configured, i.e., Whether the slices are configurable to support network capabilities functionally and the serving slices are configured to support the network capabilities. has sufficient resources (e.g., available processor and memory resources) to be Whether it is or not.

[0178] Optionally, together with the NSSF or NRF where NF and NF service information is maintained. Alternatively or additionally, the information in Tables 3 and 4 may be , may be managed and maintained at the NSSF or NRF.

[0179] Another alternative is to store this information in the UDR, which allows the NCMF, NSS Access to data storage without discovering and communicating with the F or NRF Any NF may obtain this information more easily by

[0180] As another alternative, the network capability profile may be implemented as a slice identifier in the S-NSSAI. In this way, the network slice may be implemented as a separate information (SD) embodiment. It is possible for a device to indicate the network capabilities it supports. This allows Same slice / service type (SST) of the network slice (e.g. MIoT, eMBB ) value but supports different network capabilities. It may be possible to distinguish

[0181] On the UE / AS side, once the registration or registration update procedure is completed, the UE / AS can start the service. The network capabilities supported by the network slices that provide In addition, multiple network slices may operate on the UE. Since the network may serve different applications, Which network capabilities are supported by which applications? The UE / AS may maintain information about which

[0182] (Network slice capability configuration) The network capability profile in Table 4 defines the network capabilities supported by the slice. For each slice capability, include a network slice capability field. This field consists of: Indicates the specific capabilities supported by the slice. The following are examples of capabilities that may be supported: Support for these capabilities may be provided by the network. Therefore, it may be indicated to the UE. Maximum number of UEs per network slice Maximum number of PDU sessions per network slice Maximum UL and DL data rates per UE in network slices Support for deterministic communication · Support for group communication Support for specified isolation levels Support for location-based messaging Maximum packet size support Support for mission-critical communications Support for MMTel Performance monitoring support Session and Service Continuity (S SC) mode support Non-IP Data Delivery (NIDD) and / or Reliable Data Services (Reli Support for RDS (Real-Time Data Service) Support for certain RATs Support for specific device speeds Support for specific vertical applications such as V2X and mIoT communications R Only UEs located within the service area can access / connect to the network slice. Support for specific service areas where you can connect to a tracking It may be an area, a registration area or a geographic area. A network slice instance that can be instantiated for a network slice. Maximum number of chests. Support for certain relay mechanisms Multiple tunneling mechanisms (L2TP tunnel, GRE tunnel or VPN tunnel) support. Network slice coverage area (international, national, regional, cell-limited) Support for multiple cellular networks (e.g., cellular, sector, base station, etc.) Support for delay tolerance for the UE. Support for guaranteed DL throughput for the UE. Prediction frequency, which indicates how often the KQI and KPI predictions are provided to the UE Support for quality degradation in advance. The UE may send a request and receive predictive information about quality degradation in advance. In some cases, slices may be switched if necessary. Support for SSC modes (SSC mode 1, SSC mode 2, SSC mode 3, S SC mode 4) Periodic traffic that can help optimize scheduling / performance for UEs Support for deterministic communication. Because the terminal is restricted by the frequency to be used, multiple radio frequency bands (e.g. For example, n1, n77, n38, etc. Support for a variety of access technologies. Uniformly available upstream bandwidth throughout the coverage area of ​​the network slice Define the achievable data rate of a network slice instance on a link Support for uplink throughput per network slice. How network slices (or mobile networks) handle user data Support for user data access that defines what the UE needs to do to The data may be tunneled through a private network. Either the data is routed to the network or all UE data can remain local. A slice that defines all of the QoS related parameters supported by the work slice. Support for quality of service parameters. · Important for URLLC (Ultra-Reliable Low Latency Communication) and MIoT (Massive IoT) A slash indicating the maximum transmission unit (MTU) that may be required or supported. Support for the maximum packet size supported by the device. Therefore, the UE must support this In some cases, it may be necessary to comply with the requirements. Support for network slice isolation levels (physical or logical isolation), which If it affects or supports UEs that are separated based on slices, There is a match.

[0183] Please note that some of the capabilities listed above may require additional configuration. For example, the capability "Support guaranteed DL throughput for UE" requires a specific DL throughput value. This information may be related to the network speed (e.g., 100 Mbps). The "Network Capability Parameters" are represented in the "Network Capability Parameters" field. , may be indicated to the UE by the network.

[0184] (Network Capability-Based Registration) The network capability layer in Figure 7, which may be implemented in the form of an NCMF, allows the UE to The UE can request the desired network capabilities of a particular NF and NF service. There is no need to know whether a service is available at the network slice.

[0185] FIG. 8 illustrates an example of a method for network capability based registration. When a UE registers, E is an indication of the set of desired network capabilities that support the application. and the network supports all of the required network capabilities. It responds with the NSSAI and NSI ID that identify the network slice to which it will The network response may also indicate the S-NSSAI associated with each capability. The steps of the registration method are shown in Figure 8. For illustrative purposes only, Please note that only the relevant information is listed below. The registration procedure includes mobility management, Other information may be used, such as information related to session management, etc.

[0186] In step 1, the UE sends a registration request message to a RAN node in the communication network. In the request message, the UE may indicate the following information: Each is identified by a network capability identifier (ID), This information should be provided in the network capabilities listed in Table 4. The information may be associated with the requesting NSSAI. and one network capability profile is provided per S-NSSAI of NSSAI When initiating registration for the first time, the UE has network capability mapping information. The UE may include some requirements for network capabilities, resulting in As a result, network entities (e.g., AMF, NCMF) will Determine whether the existing network slice can serve the UE Required network capacity availability schedule, required network capacity Several requirements, such as network capacity, QoS level, and the required level of multi-tenancy, are considered. The UE may select a number of different UEs based on the type of application running on the UE. An application can determine the type of network capabilities it requires based on the Therefore, the UE may need to acquire the 5G core network capabilities. What network capabilities do different applications require? The UE may need to retain some information when communicating with the AS. This information may be obtained through application level signaling. Previous NSSAI: If available, if the UE has registered with the PLMN in the past The UE may include one or more S-NSSAIs assigned to the RA. N nodes may help select the AMF and provide the required network capabilities. Might be used by AMF to configure / select supported network slices. The included NSSAI may be the configured NSSAI provided to the UE during a previous registration process, or may be an authorized NSSAI. The parameter is optional. Application ID: The application requesting the requested network capability. In some cases, a UE may be served by multiple network slices. Each network slice will be provided with services and will support applications such as mIoT and eMBB. It is conceivable that a service may be provided to a different set of applications. Applications and network capabilities are divided by different network slices. Therefore, which applications are supported on which networks The UE holds information indicating the set of network capabilities provided by the slice. In some cases, two or more UEs may be used to serve different applications. It is also possible that one network capability may be supported by a network slice. Alternatively, the UE may use the applications without associating any network capabilities with them. The SCS / AS may provide an application ID and determine which application is The network is contacted to determine whether it is associated with a network capability. This may reduce the burden on the UE and may be useful for constrained devices. PLMN ID: This indicates the PLMN to which the UE is attempting to register (the UE must provide this information In order to provide the same network capabilities, different PLMNs have different Since network slices may be configured, the PLMN ID is This may facilitate the selection of the service and AMF. · UE Identifiers such as GUTI and / or SUPI (if available). Area information: Used to select a network slice to serve the UE This information may be in the form of a TAI, registration area or geographic area. Required network capacity availability schedule. · The QoS level of network capabilities required (e.g. service response time). The required level of multi-tenancy (e.g., the need to use network capabilities) This information, together with the network capability requirements mentioned above, For example, based on availability and scalability requirements, The NFs, NF services, and NF services are used to meet the demands on network capacity. Whether to get a new instance or whether a new instance needs to be instantiated This may be useful for network O&M systems to determine.

[0187] In step 2, upon receiving the registration request, the RAN node responds with the requested network capabilities and and the AMF may be selected based on the following information: Which AMF provides which network slice identified by the NSSAI Association information between NSSAI and AMF. Mapping information between network capabilities and S-NSSAI.

[0188] By adding the above information to the N2 message, the AMF can send it to the RAN node. The RAN node may obtain the above information by To inform the network slice information and supported network capabilities information, The above information is periodically transmitted from the core network to the RAN node. The RAN node may obtain the information.

[0189] If the RAN node does not have any of the above information or does not If the RAN node does not know any AMF that supports the capability, it A default AMF may be selected based on configuration. In this case, a different AMF may be selected later. E may be selected to provide the service.

[0190] In step 3, the RAN node may forward the registration request to the selected AMF.

[0191] In step 4, the AMF communicates with the UDM to obtain some subscription information. and / or obtain some UE context information and network capability information You may choose to contact UDR to request a refund.

[0192] Then, in step 5, the AMF determines the requested network capabilities, as well as the Required network capacity availability schedule, required network capacity UE network requirements, such as the required QoS level and the level of multi-tenancy required. Contact NCMF to obtain information on network slices that can support capacity utilization requirements. The AMF MAY include the requested network capability information in the message. Alternatively, the AMF may require the capabilities indicated in the network capability profile in step 1. To check whether the S-NSSAI in the requested NSSAI can be provided, You may contact CMF.

[0193] In step 6, the NCMF will map existing network slices to network capabilities. Check the network configuration information to see if the network supports all of the required network capabilities. The NCMF may send an NSSAI back to the AMF to identify the requested slice. Any existing network system capable of supporting all of the network capabilities provided If the rice cannot be identified, the NCMF may indicate this in the response message. The CMF shall contain the S-NSSAI which the UE can use to obtain the requested service. The NCMF may provide a new set of NSIDs for each S-NSSAI to the AMF. The NCMF may provide the network capability profile for each S-NSSAI to the AMF. The file may be provided to the AMF.

[0194] In step 7, the NSSAIs required for all of the requested network capabilities are identified. In order to determine whether AMF can provide all of the It may compare locally stored network slice information. If so, the AMF updates the UE context and performs step 10. If not, the AMF requests the NSSF to perform network slice selection. However, you may proceed to Steps 8 and 9 if: (1) the NSSAI AMF cannot provide everything. (2) AMF will decide whether it can provide NSSAI. (3) It is not possible to determine whether the network can support all of the required network capabilities. The NCMF indicates that there is no existing network slice.

[0195] In step 8, the AMF receives the requested network capability information, PLMN ID and possible By providing UE information such as 5G-GUTI capabilities and SUPI if possible. Request the NSSF to select a network slice instance.

[0196] In step 9, based on the UE ID and PLMN ID, the NSSF identifies the NS The network may validate the SAI and provide the UE with all of the requested network capabilities. You may select a work slice instance. When a new AMF set is selected, the NSSF may also select an NRF. The new AMF then selects the NF instance and The NSSF shall respond with the following information: You may reply to any or all of them. · NSSAI. The selected NSI ID that corresponds to the NSSAI in the request. NRF address. · The selected AMF set and / or AMF address.

[0197] If the existing network slice cannot serve the UE, A new network slice providing services and a corresponding network slice instance To start up an instance, the NSSF contacts the Operations and Management (O&M) system. This is also fine.

[0198] In step 10, upon receiving the response, the AMF notifies the NCMF of the selected network The QoS management unit may advertise mapping information between network slices and network capabilities. For example, in step 7, the NCMF must support all of the required network capabilities. This is necessary if no network slice can be found.

[0199] In step 11, the NCMF determines the selected network slice and network capabilities. , and may update the mapping information between them.

[0200] In step 12a, if the current AMF can serve the UE, the AMF AMF may send a registration response to the RAN node, which forwards the response to the UE. The N2 message from the RAN node to the network Capability profile, i.e., selected network slice information and network Contains all of the information about the network capabilities supported by the slice. In addition, location information or registration area information may be included in the response to inform the RAN node and The UE may be provided with information to match the selected network slice. It allows the device to be linked or associated with the device.

[0201] The registration acceptance message is sent to the network capability profile for each S-NSSAI in the authorized NSSAI. The network capability profile may include a network slice. Table 4 shows the network capabilities of a network slice. It lists the contents of the work capability profile.

[0202] When a UE is served by multiple network slices, which application The network slice instance determines the network capabilities of the application. The UE may retain information identifying which of the following is to be provided:

[0203] If the network slice cannot support the capabilities required by the UE, AM F is a rejection message containing an error / reason code indicating why the request failed to be supported behind the scenes. A message may be sent.

[0204] Alternatively, the network may be designed to closely match the required network capability profile. The UE may transmit a network capability profile of the corresponding network slice to the UE. For example, if a UE requires a guaranteed DL throughput network capability of 10 Gbps, The network will then match the network capability profiles of the available network slices. It may be possible to scan the most available network with guaranteed DL throughput. If the network capability is 8Gbps, the network will send the network capability profile to the UE. submit a request to approve the network capability profile and register with the network slice On the other hand, it may indicate whether it can agree on the network capability profile of the slice. The UE may want to provide more network capabilities and / or better support beyond what the UE wants. service quality (e.g. average UE UL / DL data rate, average delay, etc.) good.

[0205] If the network sends a counter network capability profile to the UE, the UE It may reject or accept the submitted network capability profile. If the UE accepts the offered network capability profile, it responds positively. The AMF may then send a If the UE rejects the offered network capability profile, a reject message (reject code) to the AMF. In this case, the AMF The response is with the default network slice and its network capability profile. You may answer.

[0206] Alternatively, if the required network capabilities are not available, the network will The UE may be provided with a default slice NCP that has sufficient network capabilities.

[0207] In step 12b, if a new AMF is selected to serve the UE; The current AMF is 3GPP TS 23.502, Procedures for the 5G System; Stage 2, Follow the steps in v15.1.0, Release 15, 2018-0 to convert the AMF to the target The AMF relocation process may be started by issuing a tact.

[0208] Generally speaking, the network capability request information delivered in step 1 is transmitted between the UE and the AMF. Any NAS such as NAS-MM signaling or NAS-SM between the UE and the SMF In this sense, the information may be encapsulated in a service request message, and Session Management Related Request messages. The SM message may include a network capability request. For example, the UE may A new application may be launched that requires the use of capabilities X, Y and Z. The UE is already registered and has a PDU session in the network slice. The UE may be connected to the same network that supports network capabilities X, Y and Z. A PDU session is created with an indication to start a new PDU session on the workslice. If slice 1 is sufficient for this PDU session, or if a new slice is required for this PDU session To confirm this, the AMF or SMF may trigger an exchange with the NCMF.

[0209] (Network Capability-Based Registration Update) Even after completing registration, if the UE requires new network capabilities, For example, a UE may receive a new New IoT applications will be launched and services will be provided by network slices. In some cases, the UE may require NIDD characteristics that are not supported by the UE. 1 illustrates an example of a method for work capability based registration updates.

[0210] The network capability information provided in step 1 can be considered as an NCP.

[0211] In step 1, the UE may initiate a registration update process using a Registration Update Request message. ,This message may contain one or all of the following information: NSSAI: This is the configured NSSAI and / or NSSAI that the UE obtained during the previous registration process. or authorized NSSAI. PLMN ID: This is the PLMN ID that identifies the UE to be served by the network slice. This is used to indicate the PLMN in which the NSI ID: This is the network slice instance that serves the UE. This indicates the Application ID: This is the application ID of the UE that requires new network capabilities. This is the application identifier. Required network capabilities: The UE must be able to support new applications that start running on the UE. The type of network capability required may be determined based on the type of application. A single application may require multiple network capabilities. Required network capacity availability schedule, required network capacity Network capabilities QoS levels (e.g. service response time) and multi-tenancy required level (e.g. number of applications in the UE that require use of network capabilities) Information related to the UE's network capability usage requirements, such as: Required network capacity availability schedule. · The QoS level of network capabilities required (e.g. service response time). The required level of multi-tenancy (e.g., the need to use network capabilities) This information, together with the network capability requirements mentioned above, For example, based on availability and scalability requirements, Whether an infrastructure, NF, or NF service can be used to meet the requirement or whether a new infrastructure The network O&M system determines whether an instance needs to be instantiated. This may be useful in determining whether

[0212] In step 2, the serving AMF notifies the UE that it requires new network capabilities. and whether the information provided by the UE is valid. This is also fine.

[0213] In step 3, the serving AMF receives some more information about the UE and and contacting the UDM / UDR to obtain the UE context in the UDR. It may be selected arbitrarily.

[0214] In step 4, the AMF providing the service may Determine whether new network capabilities requested by Rice can be supported The AMF providing the service must be able to support the requested network capability. If so, this may be due to network slicing providing the service or different networks Regardless of whether the change is due to a cross-slice or not, AMF proceeds to step 12.

[0215] In step 5, the serving AMF provides the required network capabilities and UE or is unable to support the network capacity usage requirements of If it cannot determine whether the AMF that The AMF to be provided shall provide the UE context, NSSAI and required The NCMF may then send a network capability configuration request containing the network capability information to be configured.

[0216] In step 6, upon receiving the request, the network device supports the requested network capability. To find a network slice, NCMF searches for available network slices. Mapping information between the network devices and their network capabilities, and network capability profiles You can check the file.

[0217] Then, in step 7, the NCMF decides to renew the service without changing the AMF that provides the service. The required network capabilities can be supported by any network slice. You may decide whether or not this is the case.

[0218] In step 8a, the NCMF determines whether the serving network slice is assigned by the UE. If the NSSF determines that it cannot support the requested network capabilities, it may request a new network The command prompts the user to select a network slice.

[0219] In step 9a, the NSSF determines one or more network slice instances, In some cases, a new set of AMFs and NRFs may be selected. The NSSF Any selection result that includes a set of SI IDs, NSSAIs, NRF addresses, and AMFs If a new AMF is selected, the AMF relocation process continues in step 12b. If a new network slice is selected without changing the AMF, A UE may connect to both network slices simultaneously. Existing network slices If the network cannot serve the UE, a new network can be selected to serve the UE. To start a slice and the corresponding network slice instance, the NSSF May contact the Operations and Management (O&M) system.

[0220] In step 8b, a serving network slice is requested by the UE. If the NCMF determines that network capability can be supported, During the inactive period, the NCMF updates the network slice information that it provides. , requesting that the network slice indicate that it supports the network capability. The NCMF may send the requested network capabilities to the NSSF. information, the NSI ID serving the UE, and the NS served by the AMF It may also include SAI.

[0221] In step 9b, the NSSF updates the network slice information and sends it to the N May respond to CMF.

[0222] In step 10, the NCMF also notifies the UE that the network slice is The mapping information may be updated to indicate that the network supports this capability.

[0223] In step 11, the NCMF provides the AMF providing the service with one or more of the following pieces of information: may send a response with all · NSSAI. If 'a' a new network slice is selected, then the new NSI ID. - In case 'a' a new network slice is selected, a new AMF set. The AMF providing the service and the network slice providing the service are connected to the network. If "b", the configuration results in a network capability that can be supported.

[0224] In step 12, if "b", the serving AMF shall Update the network slice information that provides the service or, in the case of "a", update the AMF A procedure to relocate the device may then be initiated.

[0225] In step 13, the AMF providing the service is changed. If not, the U If a new AMF is selected by the NSSF, the target AMF may respond to E. , may contact new network capabilities that have been enabled to verify registration updates. .

[0226] (Network Capability Based UE Configuration Update) In addition to the UE, the network or AS also provides the network scalability to provide the service. A UE may initiate a UE configuration update due to a network capability update of the device. For example, Events in the network or AS may trigger an action to be taken. . A new application is started in the SCS / AS and the UE receives the new application of the SCS / AS. As a result, new network capabilities are available. Required to support new applications. Network functions / networks in the network slices that provide services For some reason, such as load balancing issues or scaling down of a slice instance The network slice is then switched to serve the UE. Twerk wants.

[0227] FIG. 10 illustrates a method for network capability based UE configuration update.

[0228] In step 0, the UE completes registration with the network and The prerequisites assume that the application server has a connection to the Application Server (AS) through It's Tep.

[0229] In step 1a, a particular event occurs, such as when a new application session is required. Network capability of a network slice serving a UE due to an event For new applications, the AS may decide to add or update The AS can then determine the type of network capacity required based on the type of new application. The committee may decide on a group.

[0230] In step 1b, the AMF load balances the network slices it serves. Changing the network slice serving the UE due to any reason Decides to do so.

[0231] In step 2a, the AS sends a network capability configuration request message to the NCMF via the NEF. The information provided in this step may be an NCP and includes the following information: may include: · UE identity, such as SUPI, GUTI or external UE identity. NS, which represents the network slice providing the service for the connection between the UE and the AS SAI. Added to the network slice to support communication between UE and AS New network capability information. Required network capacity availability schedule, required network capacity Network capability QoS level (e.g. service response time) and multitenant The required level of connectivity (e.g., the U that requires the use of required network capabilities) Network configuration for communication between UE and AS (e.g., number of applications of UE or AS) Information related to network capacity usage requirements. Application metric indicating the applications associated with the required network capabilities tion ID. - A reference ID used to refer to this network capability configuration transaction. This is the NE It may be assigned by F. NSI ID: Indicates the network slice instance that serves the UE. vinegar.

[0232] In step 2b, the AMF sends a network capability configuration request message to the NCMF. .

[0233] In step 3, upon receiving the request, the NCMF to the UDM / UDR to get the encryption information and the UE context in the UDR. You may choose to contact them at your discretion.

[0234] In step 4, the NCMF receives the network slice information and the required network Capability information may be checked. The purposes of these checks are as follows: Network slice information, network slice instance information, etc. Verify the information provided by the network functions. The network slice providing the service requires network capacity and U Determining whether the network capacity usage requirements of E and AS can be supported. This can be achieved by checking the network capability profile of the network slice. If this is not possible, step 5 is performed.

[0235] In step 5, the network slice providing the service is assigned to the network capability required. If the NCMF finds that the network cannot support the current network, the NCMF will notify the NSSF of the new network. Select a network slice or request to create a new network slice. In some cases, it may be possible to detect that the network slice providing the service is overloaded. It is possible that NCMF will discover new slices, in which case NCMF will provide the new slices to NSSF. You may be asked to choose.

[0236] In step 6, NCMF or NSSF notifies the AM that the network configuration process should continue. F is notified. Processing is triggered by AS (i.e., steps 1a and 2a) In this case, AMF is UE ID, NSSAI, NSI ID, SCS / AS ID, NEF You will be provided with your AMF ID and reference ID for later contact with NEF. It may be used by

[0237] In step 7, the AMF communicates with the UE and triggers a UE configuration update. The MF notifies the UE of the NCP of the slice, which includes one or more of the following information: New network capability information. Identifying the network slice, especially when a new network slice is selected NSSAI will do it. Reference ID. SCS / AS ID.

[0238] In step 8, the UE initiates the registration update procedure presented in FIG.

[0239] In step 9, if the AS initiates the registration update process as soon as it is completed, then A The MF sends a response message to the AS via the NEF.

[0240] Figure 10 shows an example of a network entity that initiates a process, where the AMF initiates a process. Note that this is a scenario where other network entities may be involved. Actions may also be initiated by the entity, e.g. UE policy changes or network A PCF may initiate an action due to a change in the work slice selection policy. , which can potentially impact the provisioning of network capabilities for the UE. The network slice selection process may be triggered by the PCF.

[0241] (Registration procedure using the network capability profile of the requesting NSSAI) NCMF configures the network capabilities of the network slices and In this section, The detailed instructions will explain the above mentioned method in detail and will be sent to the UE by the NCP together with the NSSAI. Describe how an NCP may be transmitted (e.g., one NCP per S-NSSAI). Figure 13 shows how this can be done and how it can be implemented to support configuration of network capabilities. This example illustrates how the initial registration procedure can be extended, but the same extensions are applicable to the mobility registration renewal and It should be understood that the present invention is also applicable to periodic registration update procedures.

[0242] Figure 13 shows the initial registration, mobility registration, and peripheral registration defined in 3GPP TS 23.502. FIG. 13 illustrates how the periodic registration procedure can be updated. The report focuses specifically on the parts of the registration procedure that are most in need of expansion or enhancement. Figure 13 shows that the NCMF is a standalone NF, or a logical function. Note that it shows that it is instead part of an OAM system or Or it may be part of another NF, such as an SMF or an AMF.

[0243] As illustrated in FIG. 13, the AMF determines the slice capabilities for which the UE will register. In addition, the UE may request certain capabilities and provide this capability information to the UE. In addition, the S-NSSAI and associations that the UE can register may be In some cases, the network may provide the UE with a list of NCPs that have been configured.

[0244] In step 1, the UE sends a registration request, which includes a request NSSAI. The R)AN node sends a request to the AMF. The registration request is used for initial registration, mobility registration, As previously described herein, the NSS A registration request is sent to indicate to the network the desired capabilities of each S-NSSAI of the AI. It may also include CP.

[0245] In step 2, the (R)AN node performs the following steps as described in TS 23.501 [1], clause 6.3.5: Select an AMF that is suitable for your needs.

[0246] In step 3, the (R)AN node forwards the registration request message to the AMF.

[0247] In step 4, based on the registration request from the UE, the AMF The UE may query the UDM / UDR to obtain the The scribe S-NSSAI may be included.

[0248] In step 5, if no information was obtained in the previous step, the S- As per NSSAI, AMF should request network capability profile from NCMF. The key point in such a query is that it must include the S-NSSAI (i.e., the NSSAI). This is something that is necessary.

[0249] Alternatively, the AMF may use the N-S-NSSAI to obtain the NCP associated with each S-NSSAI. Each S-NSSAI is notified by querying another NF, such as an SSF or an NRF. The associated NCP may be obtained.

[0250] In step 6, the NCMF may reply to the AMF with the NCP of the requested S-NSSAI. stomach.

[0251] In step 7, as part of the registration acceptance message, the AMF sends the authorized NSSAI and configuration NSSAI and NCP and configured NSSAI for each S-NSSAI within the authorized NSSAI The UE sends an NCP for each S-NSSAI in the AI. The NCP and may be considered part of the configuration NSSAI.

[0252] Optionally, the network may send an advertisement NSSAI to the UE. The advertised NSSAIs include a list of S-NSSAIs and their corresponding NCPs. This list and the corresponding S-NSSAI are the list of available slots for the UE. It may be an advertisement of the device and an indication of the capabilities of each slice. The S-NSSAI in may not be part of the Requested NSSAI or the Authorized NSSAI. The purpose of the Advertised NSSAI is to be added to its Established NSSAI or Authorised NSSAI. It may be to provide the UE with information about slices that the UE may request. Alternatively, the advertised NSSAI may be part of the established NSSAI.

[0253] In step 8, the slice capacity is insufficient, meaning that the permitted NSSAI and / or or the NCP provided with the S-NSSAI is not sufficient. In this case, the UE may evaluate the advertised NSSAI and may also select a preferred SN within the advertised NSSAI. If it finds an SSAI, it will initiate the registration renewal procedure and notify the requesting NSSAI. The UE and the network then perform a registration update procedure. and the network updates the UE's Authorization NSSAI and Configuration NSSAI accordingly. This is also fine.

[0254] (Network capability profile delivery via UE policy updates) NCP-related UE policies may be referred to as NCP policies or NCPPs. In this section, we explain how the core network can deliver NCPs to the UE as part of the UE policy. This document describes how NCP policies may be implemented. By using the UE configuration update of the transparent UE policy delivery procedure, Note that in some cases, the existing procedure may be extended. Figure 14 focuses on how the existing procedure may be extended. This method involves applying the points to some of the events listed in step 0. This may be triggered by an event.

[0255] In step 0, an event may occur. A notification of the event is sent to the PCF. As a result, the PCF decides whether the NCP policy needs to be updated. Examples of events include: An OAM system or an authorized AS sends update requests and NCPs. The request may be sent via the NEF, for example the AS or OAM. to increase the maximum UL or DR data rate possible by a UE in a slice. or to increase or decrease the maximum number of possible PDU sessions in a slice. The NEF may send a request to the NEF to The PCF receives notification from the AMF that the UE has changed its location (e.g., the UE location Policies may be constrained to geographical areas and new policies may need to be updated. (In some cases.) The PCF receives a change to the subscribed S-NSSAI for a UE or UE group. Receive notification that a new S-NSSAI has been added (for example, the network administrator has (You may need to renew your UE Subscription for any applicable Software or Software Updates.) The PCF receives notification that the UE has moved from EPS to 5GS. The UE moves to 5GS. Receive a new set of UE policies for The UE (via the NAS) sends a policy update request to the PCF. UE Policy Update The UE's requirements for new features will be driven by the download of applications that require new network capabilities. This may be in response to downloading, launching, and / or installation. For example, Users may download gaming applications that require AR / VR settings. This includes policies to accommodate changes in data rates and other CN resources. A new set of policies may be required. The request may include an application or OS identifier. may include: The network function that the PCF is associated with a slice is reconfigured (e.g., a new New NFs are instantiated or removed, existing NFs are scaled up or down The device receives notification from the OAM or from the NRF that the device has been · NCMF sends updated NCP information in S-NSSAI to PCF.

[0256] In step 1, the PCF determines which UE access selection and / or PDU session selection Checks the latest list of PSI to determine which relevant policies should be sent to the UE. The PCF will contact the NCMF to obtain a new set of NCPs for S-NSSAI. or NCMF needs to notify PCF of new NCP information of S-NSSAI. The PCF reads the extended UE policy data including the NCPP.

[0257] In step 2, PCF uses the Namf_Communication_N1N2MessageTransfer service of AMF. Invokes an operation. The message contains the SUPI, a UE policy container, and a UE policy. The container contains the NCPP for the UE, in other words, any other UE policy. Such NCPs are treated by 5GS as UE policies and they are either a RON policy or information integrated with an ANDSP or URSP policy It is.

[0258] In step 3, the UE receives the If the ,AMF ​​is registered and reachable by the AMF, the AMF ,will update the AMF local policy. Based on the policy, the UE policy controller can access the UE via one of the registered and reachable accesses. The UE transparently forwards the IEEE 802.11b / g / n (including the NCPP) to the UE.

[0259] In step 4, the UE receives and stores the NCPP policy. provided to UE as part of the URSP rules or ANDSP. may be considered NCP Information as part of the policy set forth herein. .

[0260] An example of how the UE may behave is based on the following policy: If the NCP policy indicates a new periodic traffic rule, the UE On the other hand, the UE may need to periodically update the duration of reception or transmission of If the UE does not have a policy for the traffic, it will not receive any messages within a certain period of time. For example, the UE may implement new policies by sending and receiving messages. may need to continuously transmit sensor signals to the server every 10 seconds, but It is expected to move at high speeds, so it may be updated every 5 seconds. The check rule may be integrated into the URSP rule by expanding the URSP confirmation standard. Then, the URSP rules are evaluated, so that a communication period may be indicated to the UE. The UE can take this information into account when If the NCP policy indicates a maximum UL and / or DL ​​data rate, the UE When evaluating the RSP rules, the UE shall consider the maximum UL and DL data provided in the NCP information. The UE may take the rate into account when establishing a route as described in the RSD or the URSAP. It may decide not to do so and establish a route with a lower priority instead. For example, ,Lower priority routes allow higher UL or DL ​​maximum data rates. Once the route is established, the UE may choose to use the maximum UL and / or DL ​​data rate. The route is then assigned to the application that initiated the traffic and the application that configured the same route after the route was established. NCP may provide the SLA to any other application that uses the SLA. If the UE indicates the maximum UL throughput per slice, the UE The limits are enforced by monitoring the aggregate throughput of all applications. NCP policy indicates location-based messaging and the UE appears in a constrained location If so, the UE may need to stop receiving or transmitting data in the message. The network may provide this information to the UE as a validation criterion within the URSP rules, or A network is a standalone entity that is considered when all URSP rules are evaluated. This information may be provided to the UE as an NCP policy. This policy may be taken into account when evaluating all routes that contain S-NSSAI from There is a match. The UE may choose to register to a different slice, which may allow for a more favorable NCP policy. In other words, the UE may send a registration update request to the network to sending a registration update request, which may include the request NSSAI to be updated; The updated request NSSAI also corresponds to the S for which the UE has just received a policy. -May not contain NSSAIs.

[0261] (Handling maximum number of PDU sessions) This section describes the configuration for several PDU sessions per network slice. How the network handles the default limits and whether it can establish more PDU sessions. The procedure for how the UE can handle the request if it finds that it cannot Please write it as follows.

[0262] (Maximum PDU Session Handling during PDU Session Establishment Process) The network is a set of PDU sessions that may be established within a network slice. A network slice may support a maximum number of However, a PDU session establishment request may still be received from the UE. There may be some scenarios where such requests may be handled in this section. Figure 15 shows how to do this, and uses the existing FIG. 15 illustrates how the existing PDU session establishment procedure can be extended. It specifically focuses on those parts of the registration process that are necessary or most in need of enhancement.

[0263] In step 0, the network slice determines the maximum number of possible PDU sessions per slice. It is composed of the NCMF, which is a network of A PDU session counter is added to count the number of PDU sessions involved in a traffic slice. This session counter is updated when each PDU session is established or released. The NCMF increments or decrements the PDU session count by 1. Once the connection is established, notification may be received from SMF.

[0264] In step 1, the UE sends a PDU session establishment request to the AM via the (R)AN node. Send to F.

[0265] In step 2, as soon as it receives a PDU session establishment request from the UE, the AMF or The SMF checks whether a new PDU session can be established on the slice. The request includes the S-NSSAI. The NCMF Check the PDU session count of the slice to see if the number of PDU sessions is less than the maximum. Check the session counter. NCMF verifies that the number of PDU sessions is less than the maximum. If it indicates that the PDU session is possible, otherwise the PDU session is This is not permitted and the PDU session establishment request will be rejected.

[0266] In step 3, the remaining PDU session establishment procedures according to TS 23.501 are carried out and the PDU A session establishment response is sent to the UE. If no PDU session should be allowed (all That is, the slice has reached its maximum number of PDU sessions) If the SMF indicates that the AMF or SMF is notified, the AMF or SMF shall send the error / cause code to the UE. indicates that the network slice has reached its maximum limit for PDU session counts, and may reject the request. In this case, the UE may reevaluate its URSP rules and select a different An attempt to establish a PDU session may be made within a slice, and the response may be sent to a Indicates how long the UE should wait before attempting to establish a PDU session in However, if a PD in the same slice is not received before the wait timer expires, When the U-session is stopped, the UE may reset the waiting timer and retry. Time may be integrated into the time window (route selection validation criteria) of the URSP rules. Therefore, the URSP rules are reevaluated before retrying the PDU session establishment.

[0267] After receiving the PDU session establishment rejection message, the UE may take the following actions: If a reject slice is not available and a lower priority URSP or RSD rule is applied, Re-evaluate the URSP rules using knowledge that the PDU session will be established using the Wait for the wait timer, then re-evaluate the URSP rule and Try to establish the PDU session again. If you stop a PDU session in the same slice and the wait timer has not expired, Disabling / removing it and then re-evaluating the URSP rule will The UE may be suspended from the slice if it attempts to establish the session again. It is proposed to improve the PDU session establishment request so that the session ID can be indicated. This extension to the PDU session establishment procedure allows slices to be immediately re-establish a new, higher priority PDU session. Desirable if the UE wishes to stop a PDU session of lower priority, provided that There is a good possibility.

[0268] (Handling Max PDU Sessions using NAS Notification) This section describes how to notify the UE that the network slice has reached its maximum limit. We now describe how NAS notification can be used to achieve this. Figure 16 shows how this can be done. .

[0269] In step 0, the network slice determines the maximum number of possible PDU sessions per slice. It is composed of the NCMF, which is a network of A PDU session counter is added to count the number of PDU sessions involved in a traffic slice. This session counter is updated when each PDU session is established or released. The NCMF increments or decrements the PDU session count by 1. When an application is established, it may receive notification from the SMF. SMF detects when the number of PDU sessions in a slice reaches or falls below the maximum value. Subscribe to NCMFs to be notified when they rotate.

[0270] In step 1, the UE and the network UE to PDU session establishment procedure as described in As soon as a session establishment request is received, the AMF or SMF creates a new PDU session on the slice. The request is sent to the NCMF to check whether a session can be established. S-NSSAI. NCMF checks whether the number of PDU sessions in the slice is less than the maximum Check the PDU session counter for the slice to see if NCM If F indicates that the number of PDU sessions is less than the maximum, then the PDU session is possible. If not, the PDU session is not allowed and the PDU session establishment request is The case where a PDU session is rejected is described above in this specification. This procedure example assumes that the PDU session establishment is successful.

[0271] In step 2, the AMF or SMF determines whether the network slice is Receive notification from NCMF that the maximum number has been reached.

[0272] In step 3, the AMF sends a NAS notification to all UEs registered in the slice. The NAS notification determines how much the UE is ready to receive the PDUs before attempting to establish a PDU session within the slice. It includes a wait timer that indicates how long the device must wait before the wait timer expires. When a PDU session in the same slice is stopped, the UE shall reset the waiting timer and restart the PDU session. The waiting time is integrated into the time window of the route selection confirmation criteria of the URSP rules. The URSP rules are reevaluated before retrying the PDU session establishment.

[0273] In step 4, if the waiting timer expires or the UE completes a PDU session in the same slice, Stop.

[0274] In step 5, the PDU session stop procedure decrements the NCMF counter. The PDU session counter is decremented to a predefined value. Send notifications to AMF and SMF when the number of DU sessions drops to a given value .

[0275] In step 6, the AMF sends a NAS notification to all UEs registered in the slice. The NAS notifies the user that the condition has been resolved and the PDU session is newly established on the slice. Alternatively, the notification indicates that the PDU session establishment request was rejected with a cause code. The UE may be transmitted only to rejected UEs.

[0276] In step 7, the UE resets the waiting timer and establishes a PDU session in the slice. may be attempted.

[0277] (Handling the maximum number of UEs in a network slice) The network determines the maximum number of UEs that can be simultaneously registered to a network slice. The network may have the capability to limit the number of registered UEs to that maximum. There are scenarios in which a request for registration to the arriving network slice may be received from the UE. This section describes how to handle such cases. 17 shows how.

[0278] In step 0, a counter may be maintained in the NCMF. The count is incremented or reset by one when each UE registers or deregisters. When a UE is registered or deregistered, the AMF provides an indication / notification. may be sent to the NCMF so that the counter is incremented or may be decremented. NCMF sub-classifies all AMFs in a slice. As a result, when a UE registers to a slice, the NCMF The subscription request may indicate an S-NSSAI, The notification from the AMF may also include the UE ID and the S-NSSAI, so that The NCMF tracks registered UEs, queries the status of registered UEs, and This helps to avoid counting errors in situations where subscription or unsubscription notifications are received. The NCMF may also indicate to the AMF that there is a limit to the number of UEs registered in a slice. As a result, the AMF may check by the NCMF for the admission of new UE registrations. (i.e. checking that limits have not been reached).

[0279] In step 1, the UE (UE1) and the network UE1 performs the UE registration procedure as described in As soon as the AMF receives the request, it sends it to the NCMF or starts the NCMF service. Checks whether a new UE can be registered in the slice. The request is S-NSSAI The NCMF checks the UE registration counter for the slice and Check if the number of UEs is less than the maximum number of UEs registered in the slice. If it indicates that the UE is registered, then the UE registration is allowed. This step of the procedure is not allowed and the UE registration request will be rejected. It is assumed that UE registration via

[0280] In step 2, the AMF receives a notification that the network slice has reached the maximum number of UEs. may be received from the NCMF. The NCMF will retry registration to the S-NSSAI. Provide the AMF with a waiting timer that indicates how long the UE needs to wait before stomach.

[0281] In step 3, a different UE (e.g., UE2) sends a UE registration request to the network. The request may indicate, for each slice, whether registration in the slice is denied. The UE may wish to receive notification when the cause of this rejection has been resolved.

[0282] The AMF receives a notification from the NCMF that the network slice has reached the maximum number of UEs. If not, the AMF checks whether the UE is able to register, as described in step 1. Please note that you may contact NCMF to check whether this is the case.

[0283] In step 4, the AMF informs the network slice that the maximum number of UE registrations limit has been reached. If the slice is notified, the AMF shall inform the UE that the request has been rejected and that the slice A UE Registration Response message with a cause value indicating that the request was rejected because the maximum number of registrations has been reached. The UE may then send a UE registration request to UE2 again in the same slice due to the rejection. The UE is provided with a waiting timer which it must use to determine when it may attempt to On the other hand, if the slice limit has not been reached, UE2 and the network may Perform the registration procedure as described in PP TS 23.502, section 4.2.2.2.2.

[0284] In step 5, a UE that is already registered in the network slice (e.g., UE3) , it may be deregistered from the network slice.

[0285] In step 6, the AMF may inform the NCMF about the deregistration of this UE. The MF may decrement the counter. In addition, the NCMF may send a notification to It may inform the AMF that a work slice is currently below its maximum limit.

[0286] In step 7, the AMF sends the cause code (i.e., network slice is at its maximum limit) The registration is rejected due to the message (message about the arrival of the request and the waiting timer) and the request Any UE (e.g., UE2) that still has a waiting timer running may be notified of the NAS This NAS notification indicates that the restrictive condition has been resolved.

[0287] In step 8, upon receiving the NAS message from the network, the UE2: The wait timer may be reset and an attempt made to register with the slice.

[0288] Alternatively, the UE may attempt UE registration after the wait timer expires.

[0289] This procedure is an extension or alternative to the network capability based registration procedure described earlier in this specification. Please note that this may be considered an extension.

[0290] (Handling maximum UL and DL data rates within a slice) As mentioned before, the network determines the maximum UL that a UE can use within a slice. and DL data rates to the UE. These maximum data rates may be This applies across all PDU sessions in the

[0291] The network also ensures that whenever a PDU session is established within a slice, The information may be provided to the UE.

[0292] The network may inform the UE that it has exceeded the maximum UL or DL ​​data rate in a slice. Whenever the UE detects a NAS notification, it may send a NAS notification to the UE. A large UL or DL ​​data rate may be indicated so that the UE can enforce it.

[0293] (NCMF Service) As mentioned above, the NCMF will develop and implement the following functions related to network capabilities and network slices: Table 5 lists the information that is used to enable these operations. This section provides a list of NCMF services that may be provided to

[0294] [Table 5]

[0295] Alternatively, if the NCMF is co-located with the NSSF or UDM / UDR, see Table 5 The NCMF services shown in the table are NSSF services or UDM / UDR services. It may also be defined.

[0296] (New UPF service) In the 5G service-based architecture, the UPF is used as the user plane function. However, UPF provides a number of features such as QoS enforcement, data buffering, and event monitoring. Some UPF services may have some control over the UPF. It is also possible to add additional functions by extending the service-based architecture. ,Extensible service-based architecture with UPF and Nupf interfaces Table 6 shows the list of UPF services.

[0297] [Table 6]

[0298] (Nupf_EventExposure) This service allows other NFs to subscribe to certain events in the UPF. ,provided to get notified when a subscribed event occurs. UPF may provide subscription services for the following events: DL data packets buffered in UPF exceed the timeout threshold or limit This can be done on a per QoS flow, per session, It can be per UE or per UPF. UPF acts as an uplink classifier for local data networks or as a The 10GbE PDU session is selected as the branch point for the 10GbE PDU session. The UPF can be used via 3GPP access or via non-3GPP access (i.e. It is selected as the anchor point for the PDU session (i.e., through the N3IWF). Information on the SCS / AS originating the traffic and the specific regulations in force The reason is that policy rules containing information are enforced by the UPF on specific traffic. And the packet is dropped. · The total number of connected UEs supported by the UPF exceeds a certain threshold. The total number or percentage of rejected or failed connection attempts exceeds a threshold. This is especially important when The total number or percentage of connection attempts that were rejected or failed due to a specified cause value exceeds a threshold. The provisions of this section may be further limited to require notice in certain cases. · Computing resources are less than the threshold. The total number of sessions managed by UPF exceeds a certain threshold. The (guaranteed) aggregate data rate of sessions managed by the UPF exceeds a certain threshold. Exceed. The utilization rate of memory allocated to downlink data buffering exceeds a certain threshold. Exceed. Mapping DL data traffic to QoS flows fails, and the application There is no PDR that matches the data.

[0299] The following information is included in your subscription (or unsubscription) request or notification: May be used in messages. Subscription ID Notification address / ID Event ID and corresponding parameters: For example, an event where a PDU session becomes congested. When an event occurs, the PDU session ID, QFI and resource utilization are included. When a packet is dropped, the cause of the drop, the session ID, The FI and the number of packets buffered at the UPF are provided.

[0300] If the AF does not have direct access to the UPF through a service-based interface, The NEF may be a service consumer.

[0301] (Nupf_StatusMonitoring) This service receives information from the UPF about the PDU session state and QoS enforcement state. Through this service, UPF will ask NFs to provide the following information: stomach. UPF acts as an anchor point, branch point, or uplink classifier, respectively Number of PDU sessions if The amount of downlink data buffered in the UPF. This is per application. and per UE, per UE group, per PDU session, per QoS flow, or per position. The IP address may be per location (i.e., within a network area). · The number of PDU sessions connected to the UE via non-3GPP access. The currently realized bit rate. This can be per application, per UE, per E-group, per PDU session, per QoS flow, or by location (i.e. network area). Packet error rate (loss rate). This is per application, per UE. ,Per UE group, per PDU session, per QoS flow, or per location (i.e. , within a network area). Storage resources used for data buffering and charging related information such as CDR Percentage of users.

[0302] If the AF does not have direct access to the UPF through a service-based interface, The NEF may be a service consumer.

[0303] (Nupf_PDUSession) This service manages PDU sessions, including creating, updating, and releasing PDU sessions. The SMF provides the capability to initiate certain procedures to manage the PDU security. Session-related procedures may include the following information: PDU session information such as S-NSSAI and network slice instance ID Application ID and associated network slice ID · DNN PDU session type, e.g. non-IP, Ethernet or IP type Session Service Continuity (SSC) mode Maximum bitrate per QoS, maximum aggregate bitrate per session, maximum performance QFI and related QoS parameters such as packet loss rate Reflective QoS support indication Packet detection rules for both DL and UL traffic Detection Rule:PDR) SMF information such as SMF ID, SMF instance ID, etc. Tunnel information for N3 and N6 tunnels (e.g. for NIDD forwarding) respectively Billing Policy ID The UPF acts as an uplink classifier or a branch point associated with a PDU session. Indication of what has been added or removed UE IDs such as 5G-GUTI and SUPI IP address and port number

[0304] (Graphical user interface example) Figure 12 shows the possible uses for configuring network capabilities in a 5G network. 1 illustrates an example user interface. (UE), service provider (SCS / AS), network operator, or other Displayed by or on behalf of a network entity or user For example, the user interface may be a display 128 of FIG. , or may be displayed by display 86 of FIG. 1G.

[0305] FIG. 18 shows that the UE may receive an NCP for an authorization S-NSSAI from the network. The user interface is shown in Figure 1. Based on the application requirements, the UE receives Approve network slices based on the NCP or from the core network A new NCP / network slice can be requested.

[0306] The above-mentioned network entity performs the steps as shown in Figures 8 to 10. For example, UE, (R)AN, AMF, NCMF, NSSF, UDR / UDSF, U DM / UDR, NRF, NEF, PCF, NF, SCS / AS, (R)AN, SMF, etc. 1B or 1G, The method includes storing the program in a memory of a device configured for network communication or a computer system, and the program The form of software (i.e., computer-executable instructions) that runs on the processor of a device. It will be appreciated that the present invention may be a logical entity that may be implemented in a multi-threaded manner, i.e. The methods shown in FIGS. 8 to 10 may be implemented using the apparatus or computer shown in FIG. 1B or FIG. 1G. Software (i.e., computer executable software) stored in the memory of a device such as a system The computer-executable instructions may be implemented in the form of computer-executable instructions that are executed by a processor of the device. When executed by the method, the steps shown in Figures 8 to 10 are performed. The functionality shown in Table 10 may be implemented as a set of virtualized network functions. It should be further understood that network functions do not necessarily need to communicate directly. Rather, they may communicate through a forwarding or routing function. Any transmitting and receiving steps shown in are performed under the control of a processor of the device and The device communicates with the computer based on computer-executable instructions (e.g., software) executed by the It will also be appreciated that the above-described configuration may be implemented by a signal processing circuit.

[0307] Additional embodiments may include the following.

[0308] Embodiment 1. An apparatus comprising a processor and a memory, the memory being The computer-executable instructions are stored in the memory, and the computer-executable instructions are executed by the processor. When the device is A request for network capability configuration to a core network entity of a communication network and transmitting a request to one or more networks requested by the device. transmitting a list of call capabilities; Receive one or more requested network capabilities from a core network entity receiving a response including an identifier of the supported network slice; An apparatus for performing an operation including:

[0309] Embodiment 2. The request is: An identifier for one or more requested network capabilities; one or more required network capabilities to support one or more required network capabilities Network slice ID and / or network slice selection information, and One or more applications hosted on a device that requires the required network capabilities Application specific identifier, 2. The device of embodiment 1, further comprising one or more of:

[0310] Embodiment 3. The request is: Device identifier, an identifier of the Public Land Mobile Network (PLMN) on which the device may register, information associated with the geographic area within which the device requires network capabilities; 3. The device of embodiment 2, further comprising one or more of:

[0311] Embodiment 4. The request is: An availability schedule associated with one or more requested network capabilities. information that identifies the A Quality of Service (QoS) associated with one or more requested network capabilities. ) level, A multi-tenant level associated with one or more requested network capabilities. information that identifies the 3. The device of embodiment 2, further comprising one or more of:

[0312] Embodiment 5. A method implemented by a user equipment (UE), comprising: A request for network capability configuration to a core network entity of a communication network and transmitting a request to the one or more networks requested by the UE. transmitting a list of call capabilities; Receive one or more requested network capabilities from a core network entity receiving a response including an identifier of the supported network slice; The method includes:

[0313] Embodiment 6. The request is: An identifier for one or more requested network capabilities; one or more required network capabilities to support one or more required network capabilities Network slice ID and / or network slice selection information, and One or more applications hosted on the UE that require the requested network capabilities Application specific identifier, 6. The method of embodiment 5, further comprising one or more of:

[0314] Embodiment 7. The request is: an identifier of the UE, Identifiers of Public Land Mobile Networks (PLMNs) on which the UE may register; information associated with a geographic area within which the UE requires network capabilities; 7. The method of embodiment 6, further comprising one or more of: Embodiment 8. The request is: An availability schedule associated with one or more requested network capabilities. Information specifying the rule, A Quality of Service (QoS) associated with one or more requested network capabilities. ) level, A multi-tenant level associated with one or more requested network capabilities. information that identifies the 7. The method of embodiment 6, further comprising one or more of:

[0315] Embodiment 9. An apparatus for implementing an entity of a core network, the apparatus comprising: The computer includes a processor and a memory, the memory storing computer-executable instructions, The computer-executable instructions, when executed by the processor, configure the core network entity. To Titi, From a user equipment (UE), one or more network capabilities requested by the UE receiving a request including a list of The network associated with the network slice currently serving the UE Based on the network capability profile, the network slice currently serving the UE is Determine whether the device supports one or more requested network capabilities And, The network slice currently serving the UE may be one or more requested If the requested network capability cannot be supported, the requested network capability or capabilities will be New network segments that can support network capabilities and provide services to UEs forming or selecting a chair; a UE receiving a selected set of network capabilities selected to support the one or more requested network capabilities; sending a response including an identifier of the network slice to be An apparatus for performing an operation including:

[0316] Embodiment 10. The network capability profile includes: Identifiers of the network slice and the corresponding network slice instance; A list of identifiers of supported network capabilities, Identifier of the serving PLMN, Area information on which services are provided based on network capabilities; 10. The device of embodiment 9, comprising one or more of:

[0317] Embodiment 11. The request is: An identifier for one or more requested network capabilities; one or more required network capabilities to support one or more required network capabilities Network slice ID and / or network slice selection information, and One or more servers hosted on a user device that requires the required network capabilities. A number of application-specific identifiers, 10. The device of embodiment 9, further comprising one or more of:

[0318]

[0023] Embodiment 12. The instructions further include for a core network entity to: 10. The apparatus of embodiment 9, further comprising:

[0319]

[0036] Embodiment 13. The instruction further includes informing the core network entity of the newly selected Terminates non-access stratum (NAS) signaling with the UE providing the network slice. and performing an operation including selecting a new core network entity to be 10. The apparatus according to embodiment 9.

[0320]

[0036] Embodiment 14. The instruction further includes informing the core network entity of the newly selected Updating the network capability profile associated with the network slice 10. The apparatus of embodiment 9, which performs the operations including:

[0321]

[0036] Embodiment 15. A method implemented by an entity of a core network, comprising: From a user equipment (UE), one or more network capabilities requested by the UE receiving a request including a list of The network associated with the network slice currently serving the UE Based on the network capability profile, the network slice currently serving the UE is Determine whether the device supports one or more requested network capabilities And, The network slice currently serving the UE may be one or more requested If the requested network capability cannot be supported, the requested network capability or capabilities will be New network segments that can support network capabilities and provide services to UEs forming or selecting a chair; a UE receiving a selected set of network capabilities selected to support the one or more requested network capabilities; sending a response including an identifier of the network slice to be The method includes:

[0322] Embodiment 16. The network capability profile includes: Identifiers of the network slice and the corresponding network slice instance; A list of identifiers of supported network capabilities, Identifier of the serving PLMN, Area information on which services are provided based on network capabilities; 16. The method of embodiment 15, comprising one or more of:

[0323] Embodiment 17. The request is: An identifier for one or more requested network capabilities; one or more required network capabilities to support one or more required network capabilities Network slice ID and / or network slice selection information, and One or more servers hosted on a user device that requires the required network capabilities. A number of application-specific identifiers, 16. The method of embodiment 15, further comprising one or more of:

[0324] Embodiment 18. The method of embodiment 1 further comprising: activating a new network slice. 5. The method according to claim 5.

[0325] Embodiment 19. Non-access with UE providing newly selected network slice Selecting a new core network entity to terminate the NAS signaling 16. The method of embodiment 15, further comprising:

[0326] Embodiment 20. Network associated with newly selected network slice 16. The method of embodiment 15, further comprising updating the capability profile.

[0327] Embodiment 21. An apparatus comprising a processor and a memory, the memory being a The computer-executable instructions are stored in the memory, and the computer-executable instructions are executed by the processor. Then, the device Access Mobility of Network Slices in the Core Network of a Telecommunications Network receiving a message from an application management function (AMF), the message being a threshold receiving a request including a determination whether the request has been satisfied; sending a response to the message to the AMF; An apparatus for performing an operation including:

[0328] Embodiment 22. The device supports access and mobility management functions in a network slice. In some cases, a user terminal may be subscribing to a slice, resulting in the user terminal requesting registration in the slice. or when attempting to establish a PDU session with a network slice 22. The apparatus of embodiment 21, capable of receiving

[0329] Embodiment 23. The request includes a network slice identifier and a user terminal identification information 22. The device of embodiment 21.

[0330] Embodiment 24. The device is configured to register a user terminal to a network slice of a core network. Or a counter that increments or decrements each time a user unsubscribes. 22. The device of embodiment 21, wherein

[0331] Embodiment 25. The device is a PDU set using a network slice of a core network. A count is incremented or 22. The apparatus of embodiment 21, utilizing a decrementing counter.

[0332] Embodiment 26. The response to the AMF indicates that the network slice has reached a threshold 22. The apparatus of embodiment 21, further comprising a notification.

[0333] 27. The response to the access and mobility management function is to register when a threshold is reached. Retry recording or retry establishing a PDU session with network slicing. a wait timer indicating how long the user terminal must wait before performing 22. The device of embodiment 21.

[0334] The illustrations of the embodiments described herein are provided to provide a general understanding of the structure, function, and operation of the various embodiments. Each figure is intended to provide a method and apparatus for implementing the present invention using the structures or methods described herein. To provide a complete description of all of the elements and characteristics of the devices and systems Many other embodiments will be apparent to those of skill in the art upon review of this disclosure. Other aspects may be utilized and derived from this disclosure, in which case the structure Structural and logical substitutions and changes may be made without departing from the scope of this disclosure. Accordingly, the disclosure and the figures are to be regarded as illustrative rather than restrictive. It should be.

[0335] The description of the embodiments is provided to enable one or more of the embodiments to be made or used. Various modifications will be readily apparent and the general principles defined herein may be practiced without departing from the spirit and scope of the present disclosure. The present disclosure may be applied to other aspects without departing from the scope thereof. It is not intended that the present invention be limited to the embodiments set forth herein, but rather that the present invention be limited to the embodiments set forth herein by the appended claims. It offers the widest range of possibilities consistent with the principles and novel properties as defined. be.

Claims

1. An apparatus implementing a first network function and comprising a processor and a memory, The memory stores instructions that, when executed by the processor, cause the device to In place, receiving a first message from a user terminal by the first network function; The first message includes a requested and receiving the operation, sending a second message by the first network function to a second network function. and wherein the second message indicates whether a threshold associated with the operation has been met. indicating a request for a decision; The first network function receives from the second network function a signal indicating that a threshold is met. receiving a first response indicative of said determination whether The first network function notifies the user terminal whether the operation is permitted. transmitting a second response including the indication; An apparatus for performing an operation including:

2. The operation may be a slice registration or a protocol data unit (PDU).

2. The apparatus of claim 1, further comprising at least one of: a) a session establishment;

3. The first network function is an Access and Mobility Management Function. The apparatus of claim 1 , further comprising an Automatic Management Function (AMF).

4. The second network function is a Network Capability Management function.

2. The apparatus of claim 1, further comprising a non-compensation function (NCMF).

5. The threshold value is a maximum number of user terminals that can be registered in the network slice, or the maximum number of PDU sessions that can be established using the network slice, The apparatus of claim 1 , wherein the apparatus is associated with at least one of the first and second inputs.

6. The operation includes a slice registration, and the second response is a and an indication that the operation is rejected because the maximum number of requested UEs has been reached. The apparatus of claim 1 , comprising:

7. The operation includes establishing a PDU session, and the second response is The operation was rejected because the maximum number of PDU sessions in the The apparatus of claim 1 including an indication.

8. The second response may be to send another message indicating a request for the operation to be performed.

8. The method of claim 6, further comprising:

13. The device according to any one of claims 1 to 12.

9. The instructions may further include a message to the device indicating a request for the operation to be performed. A non-access stratum (Non Access Stratum) message including an indication that the UE may transmit 8. The method of claim 6, further comprising the step of transmitting a NAS (Access Stratum) message to the UE.

13. The device according to any one of the preceding claims.

10. A user equipment (UE) having a processor and a memory, The memory stores instructions that, when executed by the processor, To, Instructs the network function to perform the requested operation using the network slice. and transmitting a first message indicating that the operation is a slice registration or a protocol. a session establishment of a session data unit (PDU); The network function determines whether the number of UEs registered in the network slice reaches a maximum. an indication that the operation was rejected because the network The operation was rejected because the maximum number of PDU sessions in Rice has been reached. receiving a response including one of the indications; A user terminal that causes an operation including the steps of:

11. 2. The method of claim 1, wherein the network function comprises an access and mobility management function (AMF).

1. A user terminal according to claim 0.

12. The response is made before sending another message indicating a request for the operation to be performed.

11. The method of claim 10, further comprising: A user terminal.

13. The instructions may further include instructing the UE to perform the operation after expiration of the amount of time.

13. The user terminal of claim 12, further comprising a user terminal configured to transmit a further message indicating a request for a

14. The instructions further include causing the UE to stop the slice registration based on the response. The user terminal according to claim 10.

15. The command further instructs the UE to stop the PDU session based on the response. and sending another message indicating a request for the operation to be performed.

11. A user terminal as described in claim 10.

16. The instructions may further include for the UE to: receiving an indication from the network function that the operation may be requested again; receiving a non-access stratum (NAS) message including In response to said NAS message, another message is sent indicating a request for said operation to be performed. Send a message, A user terminal according to claim 10.

Images