Device, system, method, and computer-readable medium for performing service delivery for multi-user mobile terminals

Abstract

To provide a wireless communication system, device, method, and computer-readable medium having computer-executable instructions for authenticating users and linking the users with subscription for mobile terminals.SOLUTION: An electronic device (UE) is configured to transmit, to a wireless network, a link request message requesting a user identifier be associated with an identifier corresponding to the electronic device; receive, from the wireless network, first configuration information and second configuration information, which are configuration information including an indication of one or more policy section identifiers (PSIs), in which at least part of the configuration information is associated with the user identifier, and including one or more UE route selection policy rules; and transmitting uplink data based on a determination that the condition in the received policy is satisfied.SELECTED DRAWING: Figure 7

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application was filed on June 7, 2019, which is incorporated by reference in its entirety. No. 62 / 858,565, filed on September 12, 2019. This application claims the benefit of U.S. Provisional Patent Application No. 62 / 899,202.

[0002] The present disclosure relates generally to wireless communications, and more particularly to a method and apparatus for authenticating a user and connecting the user to a mobile A wireless device having computer executable instructions for linking a wireless terminal with a subscription The present invention relates to a wired communication system, an apparatus, a method, and a computer-readable medium. [Background technology]

[0003] The "Background" discussion provided herein is intended to generally present the context of the present disclosure. As described in this Background section, the inventors' research and aspects of the description that may not be admitted as prior art at the time of filing. No part of this document is admitted expressly or impliedly as prior art.

[0004] Reference [1] 3GPP TR 22.904 specifies how a 3GPP system can This paper describes use cases in which it would be advantageous to identify

[0005] One use case from [1] is that two children, Lucy and Linus, The network determines who is using the UE and the mother's UE. So that different services are provided to the UE depending on whether it is Lucy or Linus. The 3GPP system For example, the network can be expanded by allowing Lucy or Linus to It can provide web filtering when using E. The network can enforce different time limits on different users. This scenario is The network maintains a profile for each user, and the profile determines Which UEs can be used to access the network and which services each user can access information about the user's rights to access the Service (i.e., subscriptions) This means that...

[0006] Therefore, the network must be aware of who is using the UE when granting access to a service. Consideration should be given to whether the Summary of the Invention

[0007] Exemplary embodiments of the present disclosure associate a user identifier with an identifier corresponding to an electronic device. a link request message to the wireless network requesting that the wireless network Verify that the user identifier is associated with a corresponding identifier on the electronic device from the and receiving an updated configuration for the electronic device from the wireless network. information, at least a portion of which is associated with a user identifier. The present invention provides an electronic device (e.g., a UE) configured to receive a

[0008] This Summary is intended to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is provided to identify key features or essential features of the claimed subject matter. are not intended to specify, and are not intended to be used to limit the scope of, the claimed subject matter. Moreover, claimed subject matter is not intended to be a substitute for any part of this disclosure. The present invention is not limited to limitations that solve any or all of the disadvantages listed.

[0009] The scope of the present disclosure will be determined from the following detailed description of exemplary embodiments when read in conjunction with the accompanying drawings. This is best understood from the [Brief description of the drawings]

[0010] [Figure 1A] FIG. 1A is a system diagram illustrating an example 3GPP architecture. [Figure 1B] FIG. 1B is a system diagram illustrating an example of a radio access network (RAN) architecture and a core network architecture. [Figure 1C] FIG. 1C is a system diagram illustrating an example of a radio access network (RAN) architecture and a core network architecture. [Figure 1D] FIG. 1D is a system diagram illustrating an example of a radio access network (RAN) architecture and a core network architecture. [Figure 1E] FIG. 1E is a system diagram illustrating an example 3GPP architecture. [Figure 1F] FIG. 1F is a system diagram of an example apparatus or device configured for wireless communication. [Figure 1G] FIG. 1G is a system diagram illustrating an example of a computing system for use in a communications network. [Diagram 2] FIG. 2 illustrates a 5G UE authentication procedure according to an exemplary embodiment. [Diagram 3] FIG. 3 illustrates a policy set entry according to an example embodiment. [Figure 4] FIG. 4 illustrates an EAP architecture according to an exemplary embodiment. [Diagram 5] FIG. 5 illustrates a network slice specific authentication and authorization procedure according to an exemplary embodiment. [Figure 6] FIG. 6 illustrates a UE initiated link procedure according to an example embodiment. [Figure 7] FIG. 7 illustrates a procedure for obtaining a user-identified authorized NSSAI according to an exemplary embodiment. [Figure 8] FIG. 8 illustrates policy set entry association information according to an example embodiment. [Figure 9] FIG. 9 illustrates a GUI for linking and unlinking user IDs according to an example embodiment. [Figure 10] Figure 10 shows the procedure for PDU session establishment authentication / authorization by the DN-AAA server. [Figure 11] FIG. 11 shows the procedure for DE request PDU session establishment for non-roaming and roaming with local breakout. [Figure 12] FIG. 12 shows the procedure for UE or network requested PDU session change (non-roaming and roaming with local breakout). [Figure 13] FIG. 13 shows a QoS rule information element. [Figure 14] FIG. 14 shows the QoS rule (u=m+2). [Figure 15] FIG. 15 shows the format of the User-Centric QoS Rules IE. [Figure 16] FIG. 16 shows the format of the User-Centric QoS Rules IE with Multiple User Identities. [Figure 17] FIG. 17 shows an extended procedure for DE request PDU session establishment for non-roaming with UCQR delivery and roaming with local breakout. [Figure 18]FIG. 18 shows an improved procedure for UE or network requested PDU session change (for non-roaming and roaming with local breakout) with UCQR delivery. [Figure 19] Figure 19 shows an extended network slice specific authentication and authorization procedure with UCQR distribution. [Figure 20] FIG. 20 shows an extended procedure for PDU session establishment authentication / authorization by the DN-AAA server with UCQR delivery. [Figure 21] FIG. 21 shows the format of the User-Centric QoS Rules IE with an implicit User Identity indication. [Figure 22] FIG. 22 illustrates a GUI for a multi-user UE receiving UCQR according to an example embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Further areas of applicability of the present disclosure will become apparent from the detailed description provided hereinafter. The detailed description of the exemplary embodiments is for purposes of illustration only. It is understood that this is not intended to necessarily limit the scope of the disclosure.

[0012] (Detailed Description) The 3rd Generation Partnership Project (3GPP) is a global initiative to develop and deploy wireless access, core transformers, and other Port network, as well as codec, security and quality of service Techniques for cellular communications network technology, including service capabilities including operations Recent wireless access technology (RAT) standards include WCDMA (registered trademark). ) (commonly known as 3G), LTE (commonly known as 4G), LTE-Advanced ed standard, and New Radio (NR), also known as "5G." Developments are expected to continue and include the definition of next generation radio access technologies (New RATs), which include: Providing new flexible wireless access below 7 GHz and new ultra-high-speed The expansion is expected to include the provision of mobile broadband wireless access. from new non-backwards compatible wireless access in new spectrum below 7 GHz. Addresses a broad set of 3GPP NR use cases that are expected to grow over time and have different requirements This includes different operating modes that can be multiplexed together in the same spectrum to achieve Ultra-mobile broadband is expected to be used in indoor applications and CM offering ultra-mobile broadband access opportunities for hotspots This is expected to include the Wave and mmWave spectrum. Broadband is 7GHz with cmWave and mmWave specific design optimizations The 8GbE LTE-C and 8GbE LTE-C networks are expected to share a common design framework with flexible wireless access.

[0013] 3GPP has identified various use cases that NR is expected to support and is A wide variety of user experience requirements for speed, latency, and mobility The use cases fall into the following general categories: eMBB, Ultra-Reliable Low Latency Communications (URLLC), Large-Scale Machine Type Communications (m MTC), network operations (e.g., network slicing, routing, migration and interworking, energy savings), and advanced vehicle-to-everything (eV2X) communications These include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-network (V2N) communications. Vehicle-to-Neutron (V2N), Vehicle-to-Pedestrian (V2P), and Vehicle-to-Pedestrian (V2P) communications with other entities. These categories of specific services and applications may include either Applications include, for example, monitoring and sensor networks, device remote control, and two-way remote control. Control, personal cloud computing, video streaming, wireless cloud office, first responder connection, car eco, disaster warning, real-time gaming multi-party video calls, autonomous driving, augmented reality, haptic internet, virtual reality, home office automation, robotics, and aerial drones. All of these use cases and and other use cases are contemplated herein.

[0014] The following are the service levels and core network technologies that may appear in the following descriptions: A list of acronyms related to the present invention is provided in Table 1. Unless otherwise stated, the acronyms used in this specification are The terms refer to the corresponding terms listed below.

[0015] [Table 1-1] [Table 1-2]

[0016] Exemplary Communication Systems and Networks FIG. 1A illustrates a system in which the systems, methods, and apparatus described and claimed herein may be used. 1 illustrates an exemplary communication system 100 that may be used in wireless communication. Line transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, 102e, 02f, and / or 102g, which may be referred to generally or collectively as WT The communication system 100 may be referred to as a wireless WTRU 102 or multiple WTRUs 102. Linear Access Network (RAN) 103 / 104 / 105 / 103b / 104b / 10 5b, Core Network 106 / 107 / 109, Public Switched Telephone Network (PSTN) 108, the Internet 110, other networks 112, and network services 113. The network service 113 may include, for example, a V2X server, a V 2X function, ProSe server, ProSe function, IoT service, video streaming , and / or edge computing, etc.

[0017] The concepts disclosed herein may be implemented in any number of WTRUs, base stations, networks, and / or It will be appreciated that the WTRU 1 may be used in conjunction with any of the network elements. Each of the first and second embodiments may be any type of device configured to operate and / or communicate in a wireless environment. The present invention may be a group of equipment or devices.

[0018] In the example of FIG. 1A, each of the WTRUs 102 is illustrated as a handheld wireless communication device. The wide variety of use cases contemplated for wireless communication are shown in Figures 1A-1E. Each WTRU may be referred to, by way of example only, as a User Equipment (UE), a mobile station, a fixed or mobile subscriber unit, mobile phones, pagers, mobile phones, personal digital assistants (PDAs), smartphones, laptops laptops, tablets, netbooks, notebook computers, personal computers, Wireless sensors, consumer electronics devices, wearables such as smart watches or smart clothing Devices, medical or e-health devices, robots, industrial equipment, drones, cars, buses or vehicles such as trucks, trains, or airplanes that transmit and / or comprising or arranged for any kind of apparatus or device to transmit or receive It is understood that the above may be included in the above.

[0019] The communication system 100 may also include a base station 114a and a base station 114b. In the example of FIG. 1A, each base station 114a and 114b is shown as a single element. In this case, the base stations 114a and 114b may be connected to any number of interconnected base stations and / or The base station 114a may include a core network 106. / 107 / 109, Internet 110, Network Services 113, and / or facilitates access to one or more communication networks, such as other networks 112 To achieve this, the WTRU 102 a, 102 b, and 102 c communicate wirelessly with at least one of the WTRUs 102 a, 102 b, and 102 c. The device may be any type of device that is configured to interface with the device. Similarly, the base station 114b is connected to the core network 106 / 107 / 109, the Internet 1 10, other networks 112, and / or network services 113, etc. To facilitate access to the above communication networks, remote radio heads (RRHs) are installed. ) 118a, 118b, transmitting and receiving points (TRPs) 119a, 119b, and and / or at least one of the roadside units (RSUs) 120a and 120b and a wired and / or any type of device configured to wirelessly interface with The RRHs 118a and 118b can be connected to the core networks 106 / 107 / 1 09, the Internet 110, network services 113, and / or other networks WT 112 to facilitate access to one or more communication networks. wirelessly interfaces with at least one of the RUs 102, e.g., the WTRU 102c. The device may be any type of device configured to

[0020] TRP119a, 119b are the core network 106 / 107 / 109, the Internet network 110, network services 113, and / or other networks 112, etc. WTRU 102d to facilitate access to one or more communication networks. and any type of device configured to wirelessly interface with at least one The RSUs 120a and 120b can be connected to the core network 106 / 107. / 109, the Internet 110, other networks 112, and / or networks To facilitate access to one or more communications networks, such as a network service 113, to wirelessly interface with at least one of the WTRUs 102e and 102f. The base station 114a, 114b, 114c, 114d, 114e, 114f, 114g, 114h ... 14b is a term used to refer to a base transceiver station (BTS), Node B, eNode B, Home Node B, Home eNodeB, Next Generation NodeB (gNodeB), Satellite, Site Controller, Access It can be an access point (AP), a wireless router, etc.

[0021] The base station 114a includes a base station controller (BSC), a radio network controller ( RNC), relay nodes, and / or other base stations and / or network elements (not shown) Similarly, the base can be part of RAN103 / 104 / 105. The base station 114b may be part of the RAN 103b / 104b / 105b, and may include a BSC, This may include other base stations and / or network elements (not shown), such as RNCs, relay nodes, etc. The base station 114a may be configured to serve a particular geographic area, which may be referred to as a cell (not shown). The base station may be configured to transmit and / or receive wireless signals within the base station. The base station 114b provides wired and wireless communications within a particular geographic area, which may be referred to as a cell (not shown). and / or may be configured to transmit and / or receive radio signals. , may be further divided into cell sectors. For example, the cell associated with base station 114a Thus, for example, the base station 114a has three sectors. The transceivers may include, for example, one transceiver for each sector of a cell. The base station 114a may employ multiple-input multiple-output (MIMO) technology, and thus, for example For example, multiple transceivers may be utilized for each sector of a cell.

[0022] The base station 114a may communicate with the base station 114b via any suitable wireless communication link (e.g., radio frequency (RF), (e.g., microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.) WTRU 102 via air interface 115 / 116 / 117 a, 102b, 102c, and 102g. The wireless interface 115 / 116 / 117 may be any suitable wireless access technology (RAT). ) can be established.

[0023] The base station 114b may be connected to any suitable wired (e.g., cable, fiber optic, etc.) or wireless Linear communication links (e.g., RF, microwave, IR, UV, visible light, cmWave, mmWave ave etc.) can be wired or air interface 115b / 116b / Through 117b, RRH118a and 118b, TRP119a and 119b, etc. and / or one or more of RSUs 120a and 120b. The air interface 115b / 116b / 117b may use any suitable RAT. can be established.

[0024] RRH118a, 118b, TRP119a, 119b and / or RSU120a , 120b may be any suitable wireless communication link (e.g., RF, microwave, IR, ultraviolet Air interface that can be V, visible light, cmWave, mmWave, etc. WTRU102c, 102d, 102e, 102d through 115c / 116c / 117c 2f. Air Interface 115c / 116 c / 117c may be established using any suitable RAT.

[0025] The WTRU 102 may communicate with any suitable wireless communication link (e.g., RF, microwave, IR, Sidelink can be ultraviolet UV, visible light, cmWave, mmWave, etc. communicate with each other via the direct air interface 115d / 116d / 117d, e.g. The air interfaces 115d / 116d / 117d may be any suitable It can be established using a RAT.

[0026] The communication system 100 may be a multiple access system, such as CDMA, TDMA, One or more channel access methods such as FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a and the WT RU102a, 102b, 102c, or RRH118a, 118b, RAN103b TRP119a, 119b and / or RSU120a and and 120b, and WTRUs 102c, 102d, 102e, and 102f are Implementing wireless technologies such as Universal Mobile Telecommunications System (UMTS) and Universal Terrestrial Radio Access (UTRA) It can be installed in a cellular environment, which uses Wideband CDMA (WCDMA) to communicate over the air interface. 115 / 116 / 117 and / or 115c / 116c / 117c WCDMA can be used in conjunction with High Speed ​​Packet Access (HSPA) and / or HSPA can include communication protocols such as Evolved HSPA (HSPA+). High Speed ​​Downlink Packet Access (HSDPA) and / or High Speed ​​Uplink Packet This may include high speed access (HSUPA).

[0027] The base station 114a and the WTRUs 102a, 102b in the RAN 103 / 104 / 105 , 102c, and 102g, or RRH118a and 118b, TRP119a, and and 119b, and / or RSU 120a in RAN 103b / 104b / 105b and 120b and WTRUs 102c and 102d are, for example, long-term evolution Use Aironet with LTE and / or LTE-Advanced (LTE-A) Interface 115 / 116 / 117 or 115c / 116c / 117c respectively Radio technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA) that can be established The air interface 115 / 116 / 117 or 115c can be implemented. / 116c / 117c may implement 3GPP NR technology. LTE and LTE- A-technology refers to LTE D2D and / or V2X technologies and interfaces (e.g., Similarly, 3GPP NR technology may include NR May include V2X technologies and interfaces (e.g., sidelink communications, etc.) do.

[0028] The base station 114a and the WTRUs 102a, 102b in the RAN 103 / 104 / 105 , 102c, and 102g, or RRH118a and 118b, TRP119a, and and 119b, and / or RSU 120a in RAN 103b / 104b / 105b and 120b, and WTRUs 102c, 102d, 102e, and 102f. IEEE802.16 (e.g. Worldwide Interoperability Format) Microwave Access (WiMAX), CDMA2000, CDMA2000 I X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 9 5 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications Global System for Mobile Communications (GSM) (registered trademark), Enhanced Data Rates for GSM Evolution (EDGE), Wireless technologies such as GSM EDGE (GERAN) can be implemented.

[0029] The base station 114c in FIG. 1A may be, for example, a wireless router, a Home Node B, a Home eNodeB, , or access points, e.g., business premises, homes, vehicles, trains, aircraft, To facilitate wireless connectivity in localized areas such as satellites, manufacturing, campuses, etc. Any suitable RAT may be utilized for this purpose. 2. For example, the WTRU 102e establishes a wireless local area network (WLAN). Wireless technologies such as IEEE 802.11 can be implemented to achieve this. 114c and a WTRU 102, for example, a WTRU 102d, form a wireless personal area network. Implement wireless technologies such as IEEE802.15 to establish wireless personal area networks (WPANs) The base station 114c and the WTRU 102, e.g., the WRTU 102e, may A cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, NR, etc.) can be used. As shown in FIG. 1A, base station 114c has a direct connection to the Internet 110. Therefore, the base station 114c can be connected to the core network 106 / 107 / 109. In some cases, it may not be necessary to access the Internet 110 via

[0030] RAN103 / 104 / 105 and / or RAN103b / 104b / 105b , one or more of the WTRUs 102 for voice, data, messaging, authorization and authentication; Applications and / or Voice over Internet Protocol (VoIP) ) network configured to provide a service. It can communicate with the core network 106 / 107 / 109. For example, Work 106 / 107 / 109 is a service that provides call control, billing services, and mobile location-based services, prepaid calls, Internet access, packet data network access , Ethernet connectivity, video distribution, etc., and / or user authentication. It can perform high-level security functions such as:

[0031] Although not shown in FIG. 1A, RAN103 / 104 / 105 and / or RAN1 03b / 104b / 105b and / or core network 106 / 107 / 109 , RAN103 / 104 / 105 and / or RAN103b / 104b / 105b and Communicate directly or indirectly with other RANs that use the same or different RATs. For example, the core network 106 / 107 / 109 may be RAN 103 / 104 / 105 and / or RAN 106 capable of utilizing E-UTRA radio technology In addition to being connected to RAN103b / 104b / 105b, it can also be connected to GSM or NR It may also communicate with other RANs (not shown) that employ wireless technologies.

[0032] The core network 106 / 107 / 109 also includes a WTRU 102 that is connected to the PSTN 108, A gateway for accessing the Internet 110 and / or other networks 112 The PSTN 108 can function as a gateway to the plain old telephone service (PO The Internet 110 may include a circuit-switched telephone network that provides TCP / IP. Transmission Control Protocol (TCP) in the Internet Protocol Suite, User Data Common protocols such as UDP (Universal Datagram Protocol), and Internet Protocol (IP) Interconnected computer networks and devices that use the communications protocol The other networks 112 may include other service providers. (b) includes any wired or wireless communication networks owned and / or operated by any provider. For example, the network 112 may be any type of packet data network. network (e.g. IEEE 802.3 Ethernet network), or RAN103 / Same RAT as 104 / 105 and / or RAN103b / 104b / 105b or Another core network connected to one or more RANs, where different RATs may be applied. It may contain a line.

[0033] WTRUs 102a, 102b, 102c, 102d, and 102e in the communication system 100 , and some or all of 102f may include multi-mode capabilities, e.g., W TRUs 102a, 102b, 102c, 102d, 102e, and 102f are different A plurality of transceivers for communicating with different wireless networks via wireless links. For example, the WTRU 102g shown in FIG. 1A may employ a cellular-based wireless technology. and a base station 114a that may employ IEEE 802 wireless technology. It can be configured to communicate with base station 114c.

[0034] Although not shown in FIG. 1A, the user equipment may have a wired connection to the gateway. It will be understood that the gateway may be a residential gateway (RG). The RG provides a connection to the core network 106 / 107 / 109. Many of the concepts contained herein may be implemented using wired connections to connect to a network. It will be appreciated that the present invention may be equally applicable to a UE that is a WTRU and a UE that is using For example, the wireless interfaces 115, 116, 117 and 115c / 116 The concepts that apply to c / 117c can be applied to wired connections as well.

[0035] FIG. 1B is a system diagram of an example RAN 103 and core network 106. As mentioned above, the RAN 103 uses UTRA radio technology to provide an air interface 115. The RAN 103 may also communicate with a core network 106. As shown in FIG. Thus, the RAN 103 communicates with the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, 102g, 102h, 102i, 102m, 102m through the air interface 115. b, and 102c, respectively. The nodes B 140a, 140b, and 140c may include , 140b, and 140c are each associated with a particular cell (not shown) in the RAN 103. The RAN 103 may also include RNCs 142a and 142b. The RAN 103 may include any number of Node Bs and Radio Network Controllers. It will be appreciated that the RNC may include:

[0036] As shown in FIG. 1B, Node Bs 140a, 140b are in communication with an RNC 142a. In addition, the Node B 140c can communicate with the RNC 142b. The nodes B 140a, 140b, and 140c are connected to the Iub interface. RNCs 142a and 142b can communicate with each other. RNC 142a and b can communicate with each other via the Iur interface. Each of the Node Bs 140a, 140b, and 142b is connected to a respective Node B 140a, 140b, and and 140c. 142b each include an outer loop power control, a load control, an admission control, a packet Scheduling, handover control, macro diversity, security functions, data The device may be configured to perform or support other functions, such as data encryption.

[0037] The core network 106 shown in FIG. 1B includes a media gateway (MGW) 144, Mobile Switching Center (MSC) 146, Serving GPRS Support Node (SGSN) 148, and / or a Gateway GPRS Support Node (GGSN) 150. Each of the aforementioned elements is shown as part of the core network 106. However, any one of these elements may be owned by an entity other than the core network operator. It will be understood that the information contained herein may be owned and / or operated by any party.

[0038] RNC 142a in RAN 103 communicates with the core network via the IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 can , and the PSTN to facilitate communications between 102c and traditional terrestrial communications devices. 108 to the WTRUs 102a, 102b, and 102c. can be provided.

[0039] RNC 142a in RAN 103 also communicates with the core network via an IuPS interface. The SGSN 148 may also be connected to the GG The SGSN 148 and the GGSN 150 can be connected to the WTR To facilitate communication between U102a, 102b, and 102c and IP-enabled devices To achieve this, the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, 102g, 102h, 102h, 102i, 102j ... 02b, and 102c.

[0040] The core network 106 may also be owned and / or operated by other service providers. Other networks 112, which may include other wired or wireless networks operated can be connected to

[0041] FIG. 1C is a system diagram of an example RAN 104 and core network 107. As described above, the RAN 104 communicates with the WTRU 102 via the air interface 116. a, 102b, and 102c. The RAN 104 may also be in communication with a core network 107.

[0042] The RAN 104 may include eNodeBs 160a, 160b, and 160c. However, it will be appreciated that the RAN 104 may include any number of eNodeBs. Node Bs 160a, 160b, and 160c each have an air interface 11 6 for communicating with the WTRUs 102a, 102b, and 102c. For example, the eNodeBs 160a, 160b, and 160c may include a transceiver. c can implement MIMO technology. Thus, the eNodeB 160a can For example, multiple antennas may be used to transmit wireless signals to WTRU 102a and WTRU 102b. It is possible to receive radio signals from a.

[0043] Each of the eNodeBs 160a, 160b, and 160c is connected to a particular cell (not shown). ) and can be used for radio resource management decisions, handover decisions, uplink The system is adapted to handle scheduling of users in the downlink and / or the network. As shown in FIG. 1C, eNodeBs 160a, 160b, and 160c can communicate with each other via the X2 interface.

[0044] The core network 107 shown in FIG. 1C includes a mobility management gateway (MME) 16 2, a serving gateway 164, and a packet data network (PDN) gateway Each of the aforementioned elements may include a core network 107. Although shown as part of the It is understood that the information contained herein may be owned and / or operated by entities other than the Company. cormorant.

[0045] The MME 162 communicates with the eNodeB 160a in the RAN 104 via the SI interface. , 160b, and 160c, and function as control nodes. For example, the MME 162 may Authentication of users, activation / deactivation of bearers, WTRU102a, 10 2b, and 102c, selection of a specific serving gateway during initial attachment. The MME 162 also communicates with the RAN 104 and the WAN 106, such as GSM or WCDMA. A control plane for switching between other RANs (not shown) employing other radio technologies The function can be provided.

[0046] The serving gateway 164 communicates with the e-mail server in the RAN 104 via the SI interface. Each of the Node Bs 160a, 160b, and 160c can be connected to the The serving gateway 164 generally serves the WTRUs 102a, 102b, and 102c. The Serving The gateway 164 also secures the user plane during inter-eNodeB handover. When the downlink data is available to the WTRUs 102a, 102b, and 102c, Triggering paging when the WTRUs 102a, 102b, and 102c It may also perform other functions such as managing and storing context.

[0047] The serving gateway 164 may also be connected to a PDN gateway 166. The PDN gateway supports WTRUs 102a, 102b, 102c, and IP To facilitate communication between devices, a packet-switched network such as the Internet 110 The network can be provided to the WTRUs 102a, 102b, and 102c. Cut.

[0048] The core network 107 may facilitate communication with other networks. For example, the core network 107 may include WTRUs 102a, 102b, and 102c. to a circuit-switched network such as the PSTN 108 to facilitate communication between the terrestrial Access may be provided to WTRUs 102a, 102b, and 102c. For example, the core network 107 may be an interface between the core network 107 and the PSTN 108. IP gateways that act as interfaces (for example, IP multimedia subsystems) In addition, the core network may include or communicate with an IMS server. The network 107 transmits the WTRUs 102a, 102b, and 102c to other service providers. (b) any other wired or wireless networks owned and / or operated by the In one embodiment, the present invention provides access to a network 112 through which the

[0049] FIG. 1D is a system diagram of an example RAN 105 and core network 109. The RAN 105 communicates with the WTR over the air interface 117 using NR radio technology. The RAN 105 can also communicate with the core network. Non-3GPP Interworking Function (N3IWF) 199 is a non-3G WTRU for communicating with the WTRU 102c over the air interface 198. GPP wireless technology can be adopted. N3IWF199 also supports core network 1 You may communicate with 09.

[0050] The RAN 105 may include g Node Bs 180a and 180b. It will be appreciated that gNodeB 180 may include any number of gNodeBs. a and 180b communicate with the WTRU 102a via the air interface 117, respectively. and 102b. If access and backhaul connections are used, the same air An interface may be used, which may include a core network over one or more gNBs. The Node Bs 180a and 180b may be a MIMO, Capable of implementing U-MIMO and / or digital beamforming technology Thus, the gNodeB 180a may, for example, use multiple antennas to WTRU 102a and can receive wireless signals from WTRU 102a. AN105 may also be applied to other types of base stations, such as eNodeB. It should be understood that the RAN 105 may use more than one type of base station. For example, the RAN may use eNodeBs and gNodeBs. This can be done.

[0051] The N3IWF 199 may include a non-3GPP access point 180c. It will be appreciated that the IWF 199 may include any number of non-3GPP access points. The non-3GPP access point 180c communicates with the non-3GPP access point 180c via the air interface 198. The non-three-port WTRU 102 may include one or more transceivers for communicating with the WTRU 102c. The GPP access point 180c communicates with the WTRU 10 via the air interface 198. It is possible to use the 802.11 protocol to communicate with 2c.

[0052] Each of the g NodeBs 180a and 180b is associated with a particular cell (not shown). and radio resource management decisions, handover decisions, uplink and / or The system may be configured to handle scheduling of users in the downlink, etc. As shown in FIG. 1D, the g-nodes B 180a and 180b can be, for example, They can communicate with each other via an interface.

[0053] The core network 109 shown in FIG. 1D may be a 5G core network (5GC). The core network 109 is a network of customer networks interconnected by a radio access network. The core network 109 can provide multiple communication services to the customers. As used herein, a term refers to a set of entities that perform the functions of a network. The term "core network entity" or "network function" refers to a core network. The term refers to any entity that performs one or more functions of a core network. The work entity may be a wireless and / or networked system, such as the system 90 shown in FIG. 1G. stored in a memory of a device or computer system configured for network communications; Implemented in the form of computer-executable instructions (software) that run on that processor It will be appreciated that the above may be a logical entity that is represented by a single entity.

[0054] In the example of FIG. 1D, the 5G core network 109 provides access and mobility management functions. (AMF) 172, Session Management Function (SMF) 174, User Plane Function (UPF ) 176a and 176b, User Data Management Function (UDM) 197, Authentication Server Function ( AUSF) 190, Network Exposure Function (NEF) 196, Policy Control Function (PCF ) 184, Non-3GPP Interworking Function (N3IWF) 199, User Data Repo Each of the aforementioned elements may include a 5G Core Network Although shown as part of Work 109, any one of these elements may be part of the Core Network. May be owned and / or operated by an entity other than the work operator It will be understood that the 5G core network does not necessarily have to consist of all of these elements. may consist of additional elements, and may consist of multiple instances of each of these elements. It will also be appreciated that the network functions may be configured in a number of different ways. However, they are not shown to be Diameter routing agents or message bridges. It should be appreciated that communication may be via a routing agent such as a

[0055] In the example of Figure 1D, the connections between network functions are represented by a set of interfaces or standards. This is achieved through points. Network functions are not affected by other network functions or services. It is modeled, described, or implemented as a set of services that are invoked or called by It will be appreciated that the invocation of a network function service can be implemented in a network Direct connections between network functions, messaging exchange over a message bus, software This can be accomplished via a function call or the like.

[0056] The AMF 172 may be connected to the RAN 105 via an N2 interface. For example, the AMF 172 may perform registration management, connection management, reachability management, and It can handle functionality management, access authentication, and access authorization.

[0057] The AMF configures a user plane tunnel to the RAN 105 via the N2 interface. The AMF172 uses the N11 interface to It can receive user plane tunnel configuration information from the SMF via AMF17. 2 generally communicates with the WTRUs 102a, 102b, and 102c via the N1 interface. 2c. N1 Inter The face is not shown in FIG. 1D.

[0058] The SMF 174 may be connected to the AMF 172 via an N11 interface. Similarly, the SMF is connected to the PCF184 via the N7 interface and the N4 interface. The SMF 174 may be connected to the UPFs 176a and 176b via an interface. For example, the SMF 174 can perform session management, IP address assignment for WTRUs 102a, 102b, and 102c, UPF 176a and managing and configuring traffic steering rules in UPF 176b; and It may be responsible for generating downlink data notifications to the AMF 172.

[0059] UPF176a and UPF176b are WTRU102a, 102b, and 102 110 to facilitate communication between the device and other devices. The WTRUs 102a, 102b, and 103 provide access to the Power Distribution Network (PDN). UPF176a and UPF176b are also available for other types of The WTRUs 102a, 102b, and 103 provide access to the packet data network of the For example, the other network 112 may be an Ethernet network. network or any type of network that exchanges packets of data. The UPF176a and UPF176b are connected to the SMF174 via the N4 interface. It can receive traffic steering rules from UPF176a and UP F176b is a packet data network that connects to the N6 interface. or by connecting to each other and to other UPFs via the N9 interface. This allows the provision of access to a packet data network. In addition to providing access to the data network, the UPF176 also provides packet routing. Handling and forwarding, policy rule enforcement, and quality of service handling for user plane traffic , it can be responsible for downlink packet buffering.

[0060] The AMF 172 is also connected to the N3IWF 199 via the N2 interface, for example. The N3IWF may be used to implement wireless interfaces not defined by 3GPP, for example. The WTRU 102c facilitates a connection between the WTRU 102c and the 5G core network 170 via an interface technology. AMF will interact with N3IW in the same or similar manner as it interacts with RAN105. Can interact with F199.

[0061] The PCF184 is connected to the SMF174 via the N7 interface and the N15 interface. It is connected to the AMF172 via the interface and to the application via the N5 interface. The AF 188 may be connected to the AF.

[0062] The N15 and N5 interfaces are not shown in FIG. 1D. Providing policy rules to control plane nodes such as AMF172 and SMF174 This allows the control plane nodes to enforce these rules. 4 sends policies to AMF172 for WTRU102a, 102b, and 102c. As a result, AMF can transmit the policy to the W The policy can then be distributed to the TRUs 102a, 102b, and 102c. may be implemented or applied in the WTRUs 102a, 102b, and 102c. can.

[0063] UDR178 serves as a repository for authentication credentials and subscription information The UDR can be connected to a network function, which results in The network function allows you to add, read, and modify data that resides in the repository. For example, the UDR178 can be connected to the PCF184 via the N36 interface. Similarly, the UDR178 can be connected to the NEF19 via the N37 interface. 6, the UDR178 can be connected to the UDM19 via the N35 interface. It can be connected to 7.

[0064] The UDM197 acts as an interface between the UDR178 and other network functions. The UDM197 provides network functionality through the access of the UDR178. For example, the UDM197 can authorize AM The F172 can be connected to the UDM197 via the N10 interface. Similarly, the UDM197 can be connected to the N13 interface. The UDR178 and UDM197 are connected to the AUSF190 via the It may be tightly integrated.

[0065] The AUSF190 performs authentication related operations and communicates with the UDM1 through the N13 interface. 78 and then connects to the AMF172 via the N12 interface.

[0066] NEF196 is a framework for application-specific capabilities and services within the 5G Core Network109. The disclosure will be made to Application Function (AF) 188 on the N33 API interface. The NEF can be connected to the AF188 via the N33 interface. 5G Core Network109 capabilities and services to be made available to other networks. It can be connected to the network function.

[0067] The application function 188 is a network function in the 5G core network 109. The interaction between the application function 188 and the network function is , may be performed via a direct interface or via the NEF 196 The application functions 188 may be considered part of the 5G core network 109. It may be located within or outside the 5G core network 109 and may be part of the mobile network operator. It may also be deployed by companies that have a business relationship with the operator.

[0068] Network slicing is the process of connecting one or more networks behind an operator's air interface. To mobile network operators to support "virtual" core networks on This is a mechanism that can be used across a single RAN. The core network is designed to support different RANs or different service types that are deployed. Network slicing involves "slicing" a network into one or more virtual networks. Ising says that operators have diverse requirements in the areas of functionality, performance and separation, for example. Customized to provide optimized solutions for different market scenarios that demand This allows for the formation of a network.

[0069] 3GPP is upgrading the 5G core network to support network slicing Network slicing has very diverse and sometimes extreme requirements. A diverse set of 5G use cases (e.g., large-scale IoT, critical communications, virtual 2X, and advanced mobile broadband) It is a great tool that can be used by computer scientists. Otherwise, each use case will have its own specific set of performance, scalability, and availability constraints. When a network has usability requirements, the network architecture must be adapted to accommodate a broader range of use cases. It is likely not flexible and scalable enough to efficiently support your needs. In addition, the introduction of new network services needs to become more efficient.

[0070] Referring again to FIG. 1D, in a network slicing scenario, the WTRU 102a , 102b, or 102c connect to the AMF172 via the N1 interface. An AMF can be logically part of one or more slices. F is a WTRU 102a, 102b, or 102c and one or more UPFs 176a and and 176b, SMF 174, and other network functions. UPF176a and 176b, SMF174, and other network Each of the work functions can be part of the same slice or different slices. If they are part of different slices, they will use different computing resources. are isolated from each other in the sense that they can share the same access, security credentials, etc. This can be done.

[0071] The core network 109 may facilitate communication with other networks. For example, the core network 109 is a 5G core network between the 5G core network 109 and the PSTN 108. IP Multimedia Subsystem (IMS) servers that act as interfaces to It can contain or communicate with any IP gateway. For example, Network 109 is a short message service that facilitates communication via short message service. Contains or is capable of communicating with a SMS service center For example, the 5G core network 109 includes WTRUs 102a, 102b, and 102 188 and a server or application function 189. In addition, the core network 170 can provide a This may include other wired or wireless networks owned and / or operated by The WTRUs 102a, 102b, and 102c may be provided with access to a network 112 that includes It can be provided.

[0072] The core network described herein and shown in Figures 1A, 1C, 1D, and 1E The network entities are responsible for the requirements given to them in certain existing 3GPP specifications. Although these entities and functions are identified by the names used in this document, in the future, these entities and functions may be identified by other names. The specific entities or functions may be identified in future 3GPP NR specifications. It is understood that these specifications may be combined in future specifications published by 3GPP, including Accordingly, the embodiments described and illustrated in FIGS. 1A, 1B, 1C, 1D, and 1E are The specific network entities and functions shown are provided as examples only; The subject matter disclosed and claimed herein is not intended to be limiting, whether currently or in the future. Regardless, it will be appreciated that the present invention may be embodied or implemented in any similar communication system. will be done.

[0073] FIG. 1E illustrates an exemplary communication system in which the systems, methods, and devices described herein may be used. The communication system 111 includes a wireless transmit / receive unit (WTRU). )A, B, C, D, E, F, base station gNB121, V2X server 124, and roadside user In practice, the present invention may include the RSUs 123a and 123b. The presented concepts may be used in any number of WTRUs, base stations gNBs, V2X networks, and / or or other network elements. WTRUs A, B, C, D, E, and F are in the access network coverage 122. WTRUs A, B, and C form a V2X group. Among them, WTRU A is the group lead, and WTRUs B and C are group members. WTRUs A, B, C, D, E, and F are in the access network coverage area. When the 129b interface is under the same network, the 129b interface communicates with the gNB 121. (Only B and F are shown under the network coverage in Figure 1E.) WTRUs A, B, C, D, E, and F are in the access network coverage (e.g. For example, A, C, WTRU A, B, C, D, E, F can communicate with each other, and D and and E are below or outside of network coverage in Figure 1E) In this case, sidelink (PCS or NRPCS) interfaces 125a, 125b, They can communicate directly with each other via 128.

[0074] WTRUs A, B, C, D, E, and F are connected to the Vehicular to Network (V2N) 126 or communicates with RSU 123a or 123b via sidelink interface 125b. WTRUs A, B, C, D, E, and F can be used for vehicle-to-infrastructure (V2I) The WTRU may communicate with the V2X server 124 via an interface 127. A, B, C, D, E, and F communicate via the Vehicle-to-Personal (V2P) interface 128. The UE can then communicate with another UE.

[0075] FIG. 1F illustrates a WTRU 102, such as the WTRU 102 of FIG. 1A, FIG. 1B, FIG. 1C, FIG. 1D, or FIG. 1E. Configured for wireless communication and operation in accordance with the systems, methods, and apparatus described herein FIG. 1 is a block diagram of an example apparatus or device WTRU 102 that may be As shown in FIG. 1F, the example WTRU 102 includes a processor 118, a transceiver 116, and a 20, transmit / receive element 122, speaker / microphone 124, keypad 126, device Display / Touchpad / Indicator 128, Non-removable Memory 130, Removable Bubble memory 132, power supply 134, Global Positioning System (GPS) chipset 136, and other peripherals 138. The WTRU 102 may include any of the aforementioned elements. It will be understood that subcombinations may be included.

[0076] Also, the base stations 114a and 114b, and / or, among others, but not limited to, Transceiver Station (BTS), Node B, Site Controller, Access Point AP, Home Node B, Evolved Home Node B (eNodeB), Home Evolved Node B HeNB, Home evolved Node B Gateway, Next generation Node B (gNode B) , and the nodes that the base stations 114a and 114b can represent, such as proxy nodes. may include some or all of the elements shown in FIG. 1F and described herein.

[0077] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital Signal Processor (DSP), multiple microprocessors, one or more associated with a DSP core Microprocessors, controllers, microcontrollers, application specific integrated circuits ( ASICs, Field Programmable Gate Array (FPGA) circuits, any other type The processor 118 may be a microprocessor, a microcomputer, a microcomputer integrated circuit (IC), a state machine, or the like. signal coding, data processing, power control, input / output processing, and / or The processor 1 may perform any other function that enables the processor to operate in the environment. 18 may be coupled to a transceiver 120, which may include the transmit / receive element 12 1F illustrates a configuration in which the processor 118 and the transceiver 120 are coupled to separate Although shown as components, the processor 118 and transceiver 120 are part of an electronic package. It will be appreciated that it may be integrated into the cage or the chip.

[0078] The UE transmit / receive element 122 transmits / receives signals via the air interface 115 / 116 / 117. 1A) to a base station (e.g., base station 114a in FIG. 1A) or over the air. Configured to receive signals from another UE via interface 115d / 116d / 117d For example, the transmit / receive element 122 may transmit and / or receive an RF signal. The transmit / receive element 122 may be, for example, an antenna configured to receive An emitter configured to transmit and / or receive IR, UV, or visible light signals / The transmit / receive element 122 may transmit and receive both RF and optical signals. The transmit / receive element 122 may be configured to transmit and receive wireless signals or It may be configured to transmit and / or receive any combination of wired signals. It will be understood that.

[0079] Additionally, although the transmit / receive element 122 is shown in FIG. 1F as a single element, it may be a WTR The U 102 may include any number of transmit / receive elements 122. More specifically, The TRU 102 may employ MIMO technology. 2 for transmitting and receiving radio signals via the air interface 115 / 116 / 117 The wireless communication system may include one or more transmit / receive elements 122 (eg, multiple antennas).

[0080] The transceiver 120 modulates and transmits the signals transmitted by the transmit / receive element 122. / can be configured to demodulate the signal received by the receiving element 122. As mentioned, the WTRU 102 may have multi-mode capabilities. The transceiver 120 may be configured to support multiple RATs, such as NR and IEEE802. 02.11 or NR and E-UTRA, or or the same RA via multiple beams to different RRHs, TRPs, RSUs, or nodes. The WTRU may include a number of transceivers for enabling the WTRU to communicate with the The processor 118 of the 102 includes a speaker / microphone 124, a keypad 126, and and / or a display / touchpad / indicator 128 (e.g., an LCD LCD display unit or Organic Light Emitting Diode (OLED) display The processor may be coupled to a processor unit (CPU) and may receive user input data therefrom. The processor 118 also includes a speaker / microphone 124, a keypad 126, and / or or display / touchpad / indicator 128. Additionally, the processor 118 may include a non-removable memory 130 and / or a removable The information may be accessed from any type of suitable memory, such as a removable memory 132, The non-removable memory 130 can store data. RAM, read-only memory (ROM), hard disk, or any other type The removable memory 132 may include a subscriber identity module (SIM) and a memory storage device. SIM cards, memory sticks, Secure Digital (SD) memory cards, etc. The processor 118 may include a cloud or edge computing platform. on a server hosted on a Windows platform or a home computer (not shown). Access information from memory that is not physically located on the TRU102 and store data in memory The data can be stored.

[0081] The processor 118 may receive power from a power source 134 and may include a It may be configured to distribute and / or control power to other components. 134 may be any suitable device for providing power to the WTRU 102. For example, power source 134 may include one or more dry batteries, solar cells, fuel cells, and the like.

[0082] 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 TRU 102 receives an air interface signal from a base station (e.g., base stations 114a, 114b). Receive location information via 115 / 116 / 117 and / or two or more nearby Its location can be determined based on the timing of signals received from base stations. The TRU 102 may obtain location information by any suitable location-determining method. It will be understood that.

[0083] The processor 118 may be further coupled to other peripherals 138. The device may include one or more software components that provide additional features, functionality, and / or wired or wireless connectivity. The device may include software and / or hardware modules. For example, The sensor 138 may include an accelerometer, a biometric (e.g., fingerprint) sensor, an e-compass, a satellite tracker, Transceiver, digital camera (for photo or video), Universal Serial Bus (US B) Ports or other interconnection interfaces, vibration devices, television transceivers, handset Free headset, Bluetooth module, Frequency Modulation (FM) radio Geo Unit, Digital Music Player, Media Player, Video Game Player Module The device may include various sensors such as a browser, a mobile device, and an internet browser.

[0084] The WTRU102 can be used in sensors, consumer electronics, smart watches or smart clothing. Any wearable device, medical or e-health device, robot, industrial equipment, draw to other equipment or devices, such as vehicles, including automobiles, trucks, trains, or airplanes The WTRU 102 may include one of the peripherals 138. Such interfaces may be connected via one or more interconnection interfaces, such as a may be connected to other components, modules or systems of any equipment or device. Cut.

[0085] Figure 1G shows the RAN 103 / 104 / 105, the core network 106 / 107 / 109 , the PSTN 108, the Internet 110, other networks 112, or networks 1A, 1C, 1D, 1E, 1F, 1G, 1H, 1I, 1J, 1K ... D, and one or more devices of the communication network shown in FIG. 1E may be embodied. FIG. 9 is a block diagram of an exemplary computing system 90. The system 90 may comprise a computer or server, and may primarily comprise computer-readable instructions The computer readable instructions may be stored in such software. or the form of the Software, regardless of where or how it is accessed; Such computer readable instructions may be implemented in a computing system 90. The program may be executed within the processor 91 to cause the processor 91 to perform operations. There are general purpose processors, special purpose processors, conventional processors, digital signal processors (D SP), multiple microprocessors, one or more microprocessors associated with a DSP core controllers, microcontrollers, application specific integrated circuits (ASICs), Field Programmable Gate Array (FPGA) circuits, any other type of integrated circuit (IC The processor 91 may be a clock, a clock generator ... processing, power control, input / output processing, and / or communication with the computing system 90 It may perform any other function that enables it to operate within a network. Processor 81 may perform additional functions or assist processor 91. The processor 91 and the main processor 91 may be separate and optional processors. and / or co-processor 81 for processing data related to the methods and apparatus disclosed herein. The system can receive, generate, and process data.

[0086] In operation, the processor 91 fetches, decodes, and executes instructions to perform computing Information is transferred between other resources via the system bus 80, which is the system's main data transfer path. Such a system bus transfers data between components within the computing system 90. System bus 80 typically connects data The data line is used to send data, the address line is used to send addresses, and the system interrupt line is used to send and control lines for operating the system bus. An example of such a system bus 80 is a PC I (Peripheral Component Interconnect) bus.

[0087] Memory coupled to the system bus 80 includes random access memory (RAM) 82 and and read only memory (ROM) 93. Such memory is used for storing and retrieving information. ROM 93 generally contains memory that cannot be easily altered. The data stored in RAM 82 is then read by the processor 91 or other hardware. The RAM 82 and / or Access to the ROM 93 can be controlled by a memory controller 92. The memory controller 92 converts the virtual address into a physical address when the instruction is executed. The memory controller 92 can also provide an address translation function to translate Isolate processes within the system and use memory reserves to separate system processes from user processes. Therefore, a program that operates in the first mode can provide a protection function. Access only memory mapped by its own process virtual address space Unless memory sharing between processes is configured, the virtual address of another process It is not possible to access memory in the address space.

[0088] Further, the computing system 90 includes a processor 91, a printer 94, a keyboard 95, and a communicates commands to peripherals such as the board 84, mouse 95, and disk drive 85 A peripheral controller 83 may be included to serve the role.

[0089] The display 86 controlled by the display controller 96 is It is used to display the visual output generated by the input system 90. Such visual output can include text, graphics, animated graphics, and The visual output may include graphical user interfaces (e.g., The display 86 may be provided in the form of a CRT-based video display. Play, LCD-based flat panel displays, gas plasma-based flat panel displays The display controller can be implemented as a panel display or a touch panel. The controller 96 contains the electronic components necessary to generate the video signal that is sent to the display 86. include.

[0090] Further, the computing system 90 may be To enable them to communicate with other nodes or functional entities of the network RAN 103 / 104 / 105, Core Network 106 / 107 / 109, PST N108, the Internet 110, the WTRU 102, or Figs. 1A, 1B, 1C, 1D, and other networks 112 of FIG. 1E. The device may be used to connect a computing system 90 to a It may include communications circuitry, such as a wireless or wired network adapter 97. may be used alone or in combination with the processor 91 to implement the specific devices, that are used to perform the sending and receiving steps of a can be done.

[0091] Any or all of the devices, systems, methods, and processes described herein may be Computer-executable instructions (e.g., program code) stored on a computer-readable storage medium. The instructions may be embodied in a processor, such as processor 118 or 91. When executed by the processor, the processor is It is understood that the methods and processes described herein may include, but are not limited to, performing and / or causing the execution of the methods and processes described herein. Any of the steps, acts, or functions described may be implemented using wireless and / or wired networks. The method is executed on a processor of a device or computing system configured for network communication. Such implementations may be implemented in the form of computer-executable instructions. A computer-readable storage medium is any non-transitory (e.g., tangible or physical) medium for storing information. Volatile and non-volatile, removable and removable, implemented by physical methods or techniques Although computer-readable storage media includes non-transitory media, such computer-readable storage media do not include signals. The computer-readable storage medium may be a RAM, a ROM, an EEPROM, a flash memory or other Memory technology, CD-ROM, Digital Versatile Disk (DVD) or other optical disks Storage devices, magnetic cassettes, magnetic tapes, magnetic disk storage devices or other magnetic storage devices or any other desired information, This includes any other tangible or physical medium that can be accessed by the system. The present invention is not limited to these.

[0092] (Detailed Description) The present disclosure relates to a UE, a network that authenticates a user, and a network that supports the user. Configured to detect specific events that trigger a request to link to a subscription This is related to the configuration that is performed when the network provides the UE with an updated configured NSSAI. Here, each NS in the updated configured NSSAI The SAI is associated with one or more user identifiers.

[0093] The present disclosure also provides a method for linking a user to a subscription in a UE, the UE being able to Deciding to send the requested NSSAI and receive a new authorized NSSAI and the new requested NSSAI and the S-NSSAI within the allowed NSSAI are Explain how it is associated with a user identifier.

[0094] This disclosure also describes an efficient way to associate a user identity with policy information. The Identification has made few changes to the format and content of the PSI and URSP policies. and changes in user activity, associations, or links can affect the network. associated with the PSI so that the network does not need to send new PSI to the UE. It is possible.

[0095] The present disclosure also provides a method for determining which events are updated to the UE from the network via PSI / user-related This section explains how to request attachment information.

[0096] (Subscription Identifier) In the 3GPP system, the IMSI (International Mobile Subscriber Identity) is the subscription identifier. The IMSI consists of three fields. MCC (Mobile Country Code) MNC (Mobile Network Code) MSIN (Mobile Subscriber Identification Number) IMSI is a type of SUPI.

[0097] (Device Identifier) In the 3GPP system, the IMEI (International Mobile Equipment Identity) is used to identify the UE. This is the device identifier used for

[0098] In IEEE802 systems, the MAC (Media Access Control) address is A device identifier used to identify the network interface controller. It is.

[0099] (user identifiers, user profiles and subscriptions) 3GPP to support a user-centric authentication layer in addition to existing subscription authentication The results of this study are presented in the literature. [1]

[0100] In this study, a 3GPP system is customized for different users using the same UE. Method for providing a service behind a gateway having a 3GPP subscription How to identify users of devices located in a devices without 3GPP access, and access to 3GPP services via non-3GPP access We evaluated a method that uses a user identifier that is linked to the subscription to which the user subscribes.

[0101] User identity in the 3GPP system is defined as the identity of a user and the mobile The MNO must identify the network operator (MNO) and the user. It has a business relationship, is responsible for authenticating and authorizing user requests, and maintains information records associated with the user. It plays a role in maintaining the

[0102] 3GPP User Identity is a method for identifying at least two entities, i.e., a user and a mobile node. O) can have two fields to identify the user. The username portion of the identifier can be formatted as "username@mnoname" The user ID can be an alphanumeric string that is resolved into a user identification.

[0103] There can be different formats of the 3GPP user identity. For example, The format may be used on interfaces external to the 5GC and may be used in internal formats. The bit may be used on interfaces internal to the 5GC.

[0104] There can be different types of 3GPP user identities. The user identity may identify a person (e.g., a name or alias). The 3GPP user identity of the app can identify non-3GPP devices. The application identifier identifies the smartwatch. 5GC uses the user profile It may contain details about a user in the UE, and the UE subscription may include details about the user of the UE. The user profile of various users that can recognize the user ID of the It is expected that users will maintain user profiles and sub-files. Linked to subscriptions that may have many relationships with subscriptions The user identity is stored during the UE / user subscription to a user profile. The link action can act as a key to the user profile or subscription. Based on events in the network, such as administrators or third parties who create / update subscriptions The user profile is linked to the subscription. In fact, users access the system using the UE associated with the subscription. This is an instruction in the 5GC that it is possible to do so.

[0105] The user ID can be different based on the system in which the user is registered.

[0106] (Registration, configuration updates, and PDU session related procedures) The 5G Registration, PDU Session Establishment, and Service Request procedures are It is used to activate, reactivate, and deactivate the This section provides information about these three steps and a configuration update procedure.

[0107] [Table 2]

[0108] (5GC Certification Procedure) The 5G UE authentication procedure is described in Section 5.2.10.2.3 of Reference [6]. A transcript of the procedure is shown in Figure 2. The AMF receives the UE's SUPI (i.e., IMSI ) to Nausf_UEAuthentication_Auth during UE registration. The enticate procedure can be invoked to authenticate the UE.

[0109] (Network slice identification) Network slices are classified as S-NSSAI (Single Network Slice Selection Assistance Information) The S-NSSAI is identified by the slice / service type (SST) and slice It consists of a signal discriminator (SD).

[0110] An NSSAI is a collection of S-NSSAIs. There are three types of NSSAIs:

[0111] The configured NSSAI is the NSSAI that is configured on the UE and that the UE is permitted to use. The UE can use a different configured NSSA for each PLMN. I can be used.

[0112] The configuration specifies how the configured NSSAI maps to the HPLMN configured NSSAI. The instruction may include instructions on whether to

[0113] The requested NSSAI is provided to the network by the UE during registration. The network uses it to determine which network node should serve the UE. and determines which network slice the UE should be allowed to connect to.

[0114] Upon completion of registration, the network provides the UE with an authorized NSSAI. The received NSSAI is the S-NSSAI (i.e., slice )

[0115] (PDU Session) The PDU session is associated with an S-NSSAI and a DNN.

[0116] In the PDU session establishment request sent to the network, the UE shall The PDU Session ID shall provide a unique session identifier for each UE. An identifier used to uniquely identify one of the PDU sessions of a PDU session of E. If the LMN is used for two accesses, it is used for both 3GPP and non-3GPP accesses. To support handover between PDU sessions, the PDU session ID is stored in the UDM. It shall be so.

[0117] (URSP rules) URSP (UE Route Selection Policy) rules determine how to route outgoing traffic. The policy used by the UE to decide what traffic to forward. Can be routed to an established PDU session and can be routed outside the PDU session The PDUs can be offloaded to non-3GPP accesses or new PDU sessions can be created. The establishment can be triggered. The rules are provided to the UE by the PCF of 5GC.

[0118] A URSP rule has two main parts: The traffic descriptor part is the part that describes the traffic to which the rule applies. Used by the UE to determine which traffic is to be transmitted. Routes that can be used to route data to A Route Selection Descriptor (RSD) part that contains the description of the route (SSAI, DNN, access type, etc.) .

[0119] The UE may also be used to decide how to handle traffic. A local priority can be used to route requests to a URSP. can be.

[0120] (UE Policy Information Organization) The policy information portion of the UE's subscription is stored in a policy set entry 300 (e.g. For example, a policy set entry is organized into a UDR as shown in Figure 3. Each PSI consists of zero or more ANDSP and / or URSP policies. This is described in reference [5] and shown in Figure 7.

[0121] FIG. 7 can also be viewed as a representation of how policy information is stored in the UE. The network transmits policy information to the UE at PSI granularity. In other words, I is the minimum amount of policy information that the network can send to the UE, and the UE The minimum amount of policy information that can be rejected. PSI consists of just one ANDSP rule. It can contain one rule or one URSP rule.

[0122] (Extensible Authentication Protocol (EAP)) EAP is not an authentication method, but can be used to enforce a specific authentication method. In other words, EAP is a common authentication framework that consists of peers, authenticators, and A protocol that allows servers to negotiate which authentication method will be used The selected authentication method is then performed inside the EAP protocol.

[0123] EAP is defined in RFC 3748[9]. [9] describes the EAP packet format. It describes basic functions such as the protocol, procedures, and negotiation of the desired authentication mechanism. FIG. 4 shows a block diagram of a basic EAP architecture 400. EAP is , radius or diameter protocols can be used.

[0124] Note that it is not sufficient to describe an authentication mechanism as EAP. There are many EAP methods defined by the IETF. .

[0125] This document explains, for example, whether the selected EAP method is based on UMTS-AKA, RFC We assume that the EAP-AKA is the EAP-SIM defined in

[10] . However, The concepts presented in this document are intended to be used regardless of the EAP authentication method chosen. can be done.

[0126] (Slice-specific authentication and authorization) In Release 16 of the 5G system, 3GPP will provide slice-specific authentication and authorization. It was agreed to add a procedure to support this. This procedure requires that the UE When the network attempts to register to the EA The EAP-based authentication procedure allows the To be allowed to access the network, the UE must provide a user identity and associated network credentials. The new procedure is described in references [7] and [8]. This is shown in Figure 5, which is copied from Reference [8].

[0127] (Secondary authorization / authentication by DN-AAA server during PDU session establishment) PDU session establishment authentication / authorization is optional by SMF during PDU session establishment. If triggered and the DN-AAA server is located in 5GC and directly reachable, UPF This may be done transparently via the UPF or directly by the DN-AAA server without going through UPF. Figure 10 is copied from [6] and shows the DN-AA during PDU session establishment. This shows the procedure for authentication / authorization by the A server.

[0128] (PDU session establishment and modification) (DE required in non-roaming and roaming with local breakout PDU session established. Figure 11 shows the non-roaming case and the roaming case with local breakout. This is copied from reference [6], which shows the PDU session establishment process in This procedure is used by the UE to establish a new PDU session.

[0129] (UE or network requested PDU session change (non-roaming and localized) Roaming with breakout PDU Session Modification Procedure Requested by UE or Network (Non-Roaming and roaming with local breakout scenario) is shown in Figure 12. The procedure is copied from [6]. This procedure is used to change the PDU session. It is used by the UE or the network for

[0130] (QoS flow) A QoS flow is the finest granularity of QoS distinction in a PDU session. The S-Flow ID (QFI) is used to identify QoS flows in 5G systems. User plane traffic with the same QFI in a PDU session is considered to be the same traffic. Receives the QoQ forwarding process (e.g., scheduling, admission thresholds) within the SGS. S-flows are controlled by the SMF and are pre-configured or can be established.

[0131] Any QoS flow is characterized by: Provided to the AN by the SMF via the AMF via the N2 reference point, or by the AN Pre-configured QoS profiles within; One or more QoS rules and, optionally, the QoS rules associated with these QoS rules. Flow-level QoS parameters are transmitted by the SMF over the N1 reference point through the AMF and / or applying reflective QoS control to the UE. and QoS parameters that may be derived by the UE by ·One or more UL and DL PDRs provided to the UPF by the SMF.

[0132] (QoS Profile) For each QoS flow, the QoS profile includes the following QoS parameters: Let: 5G QoS Identifier (5QI); and · Allocation and Retention Priority (ARP).

[0133] For each non-GBR QoS flow only, the QoS profile includes the following QoS parameters: It can also contain: ·Reflective QoS attributes (RQA).

[0134] For each GBR QoS flow only, the QoS profile includes the following QoS parameters: This also includes: Guaranteed Flow Bit Rate (GFBR) - UL and DL; and Maximum Flow Bit Rate (MFBR) - UL and DL; and For GBR QoS flows only, the QoS profile has the following QoS parameters: It may also contain one or more of: Notification Control: Maximum Packet Loss Rate – UL and DL.

[0135] Each QoS profile defines one corresponding QoS It has a flow identifier (QFI).

[0136] (QoS rules) (Signaled QoS rules) The UE classifies and marks the UL user plane traffic based on the QoS rules. QoS rules may be provided explicitly to the UE (i.e. using the PDU Session Establishment / Modification procedures). QoS rules may be pre-configured in the UE, or explicitly signaled using the QoS rules Or it may be derived implicitly by the UE by applying reflective QoS.

[0137] QoS rules include: a) an indication of whether the QoS rule is a default QoS rule; b) The QoS Flow Identifier (QFI) of the associated QoS flow; c) QoS Rule Identifier (QRI); d) any packet filter set; and e) Priority value.

[0138] Explicitly signaled QoS rules are unique within a PDU session and are handled by the SMF The same QoS flow, i.e., the same QFI, There can be two or more associated QoS rules.

[0139] The default QoS rules must be sent to the UE for each PDU session establishment. Associated with a QoS flow.

[0140] For unstructured type PDU sessions, the default QoS rule is the packet filter set, in which case the default QoS rule applies to all packets in the PDU session. Defines the processing of

[0141] (Derived QoS rules) The derived QoS rules can be applied to IPv4, IPv6, IPv4v6 or Ethernet PDs. Only applicable to PDU sessions of U session type.

[0142] Reflective QoS in the UE is achieved by dividing the DL user data received via a PDU session by the Create a derived QoS rule associated with the PDU session based on the packet. do.

[0143] Each derived QoS rule includes: a) QoS Flow Identifier (QFI); b) Packet filters for the UL direction; and c) A priority value of 80 (decimal). Note: On the network side, the corresponding QoS rules are different numbers ranging from 70 to 99 (decimal). The priority values ​​may be associated with different priority values.

[0144] Within a PDU session: a) There are zero, one, or multiple derived QoS rules associated with a given QFI. There may be b) At most one derived QoS associated with a given packet filter in the UL direction. There can be rules.

[0145] Once the QoS rule is derived by the UE, the UE starts a timer (T3583) and When the rule expires, the UE deletes the rule. Then, the UE sends DL packets for which the UE does not have a rule. The next time it is received it will trigger the creation of a new rule.

[0146] (QoS rule structure) The purpose of the QoS Rules information element is to indicate the set of QoS rules to be used by the UE. The QoS rules are described in 3GPP TS 24.501

[11] . Such a set of parameters is given.

[0147] The QoS rule information element is a type 6 information element with a minimum length of 7 octets. The maximum length is 65538 octets.

[0148] The QoS rule information element 1300 is encoded as shown in FIG. is shown in Figure 14 below.

[0149] (QoS flow mapping) The SMF assigns a QFI to the new QoS flow and determines whether the flow is The QoS profile, corresponding UPF instructions and QoS rules from other information provided Derive.

[0150] For each SDF, where applicable, the SMF shall explicitly signal according to the following principles: Generate a nulled QoS rule and provide it to the UE along with an addition operation: · A unique (for the PDU session) QoS rule identifier is assigned; The QFI in a QoS rule is the QFI of the QoS flow to which the PCC rule is bound. be set; The packet filter set of the QoS rule is the UL SDF filter of the PCC rule and Optionally generated from the DL SDF filter (but not for signaling to the UE) only from SDF filters with instructions); The QoS rule priority value is set to the priority value of the PCC rule in which the QoS rule is created. ; For dynamically allocated QFIs, QoS flow-level QoS parameters (e.g. For example, 5QI, GFBR, MFBR, averaging window, see TS 24.501

[11] ) , are signaled to the UE in addition to the QoS rules associated with the QoS flow.

[0151] At UL, it is as follows: For PDU sessions of type IP or Ethernet, the UE must Q until a rule (i.e., a packet filter that matches the UL packet) is found. Based on the priority value of the QoS rule, the UL packet in the packet filter set in the QoS rule is The UL packet is evaluated against the UL filter. If no matching QoS rule is found, the UE discards the UL data packet. It shall be so. For unstructured type PDU sessions, the default QoS rule is packet filtering. The UL packet does not contain any filter set and all UL packets are allowed. The UE assigns QoS to UL packets using the QFI in the corresponding matching QoS rule. Binding to a flow. The UE uses the stored QoS rules to control the UL user plane traffic and the QoS Determine the mapping between the S flows. The UE marks the UL PDU with the QFI of the QoS rule that contains the matching packet filter. and assigns the corresponding access to the QoS flow based on the mapping provided by the (R)AN. The access point / access point specific resources are used to transmit the UL PDUs.

[0152] (Mention of the issue) Reference [1] 3GPP TR 22.904 specifies how a 3GPP system can communicate with a UE user interface. This paper describes use cases in which it would be advantageous to identify

[0153] One use case from [1] is that two children, Lucy and Linus, The network determines who is using the UE and the mother's UE. So that different services are provided to the UE depending on whether it is Lucy or Linus. The 3GPP system For example, the network can be expanded by allowing Lucy or Linus to It can provide web filtering when using E. The network can enforce different time limits on different users. This scenario is The network maintains a profile for each user, and the profile determines Which UEs can be used to access the network and which services each user can access information about the user's rights to access the Service (i.e., subscriptions) Moreover, it means that each user may require or demand different QoS. Allows you to use different applications or services within your device (e.g. games, videos streaming, etc.), different users can have different user experiences. Different users may wish to use different user interfaces based on their agreement with the MNO. This means that you are entitled to the experience.

[0154] The above use cases are intended to allow access to services that include network slices. It is clear that the network should take into account who is using the UE when to.

[0155] Furthermore, based on the described scenario, reference [1] concludes that 3GPP systems: User-specific service settings and parameters such as QoS parameters with the user's user ID This suggests that the parameters can be preserved.

[0156] URSP rules determine which network segments are targeted for a given type of application traffic. Information on whether to use Rice and PDU sessions and data networks One of the problems addressed in this disclosure is to configure the UE using How the URSP rules can be expanded to take into account or incorporate Furthermore, the present disclosure provides a method for determining who is using or can use the UE. This section addresses when and how the URSP rules for the UE are updated based on whether the UE is configured to use the UE's UE-specific URSP.

[0157] Returning to the use case mentioned earlier in this section, the person using the UE changes dynamically. For example, when Lucy finishes surfing the web, You can place the handset on the table and Linus can pick up the device later. This scenario is useful if the network is not aware of user changes. It is necessary to be able to detect when a UE user has changed their account on the UE. It must be possible to deactivate and suspend, i.e. temporarily deactivate When there is a user change, the network also checks whether the UE is active. It is necessary to be able to change the services that can be accessed by the user. Regarding which services a UE can access when We investigate how this affects the UE's configured and allowed NSSAI.

[0158] In the above use case, Lucy and Linus have different user accounts and Thus, Lucy and Linus can use different Different applications can log into different user accounts and have different QoS requirements. Users can also subscribe to and unsubscribe from custom QoS. Note also that each user can compensate the MNO for the services provided. To experience a proper quality of service in E, QoS rules must be implemented according to the user's preferences. The user ID must be linked or stored in the user's profile and sent to the UE. Therefore, the network must provide some rules for the UE to associate with it. It is necessary to be able to configure QoS rules in the UE so that the network can In the “user aware” scenario, the network detects that the user is no longer connected to the network from the UE. For example, this may be the case when Lu Cy and Linus' mother called the network operator and requested a specific location, time, etc. Terminate or change those authorizations so that you are only permitted to use the UE in In such a scenario, the network may It must be possible to deactivate or suspend, i.e. temporarily deactivate, There is a need.

[0159] As previously described herein, user IDs may have inconsistent sizes. Sending longer names over the air all the time can increase the amount of radio signaling resources. Therefore, for optimal calculations, it is recommended to use user IDs with consistent size IEs. It may be desirable to represent

[0160] (overview) In Rel-I 7, 3GPP will define which user data plane traffic is associated with The present disclosure is directed to investigating ways to extend 5G systems to recognize when a signal is being received. It focuses on the following aspects: The network performs traffic extension of the QoS rule IE based on the user / user ID. Filter data based on the user (capillary device, application, or person) that generated it Configure the UE with the policy or route that will be used to route the results A method for delivering user-specific QoS rules obtained by the above method to the UE.

[0161] The present disclosure provides a method for a network to authenticate a user and link the user to a UE subscription. How can the UE detect a particular event that requires it to This outlines how the network provides the UE with an updated configured NSSAI. Here, each S NS in the updated configured NSSAI The SAI is associated with one or more user identifiers.

[0162] The present disclosure further provides a method for linking a user to a subscription for a UE, the UE being able to Decide to send a new requested NSSAI and receive a new authorized NSSAI. and S-NSSAs within new requested and authorized NSSAIs. Explain how I is associated with a user identifier.

[0163] The UE is connected to a network that can be accessed by a user associated with the UE. When connected to each slice, the UE must decide which traffic to route to each slice. This disclosure also provides a method for determining whether a UE can receive traffic based on the user carrying the traffic. Networks are tied to user identities so that different policies can be applied. It also describes how the determined URSP policy can be provided to the UE. Specifically, this disclosure proposes an efficient way to associate user identities with policy information. User Identification changes little to the format and content of PSI and URSP policies. can remain unchanged and can be updated by changes in user activity, associations, or links. , the PSI is associated with the PSI so that the network does not need to send new PSI to the UE. The present disclosure also provides information about which events are updated to the UE from the network. This section explains how to request PSI / user association information.

[0164] Furthermore, this disclosure describes a new User-Centric QoS Rule (UCQR) Explains how CQR can be encoded into NAS information elements and introduces new Describes which procedures can be extended to deliver information elements to the UE and How can E associate user traffic with user-centric QoS rules? This article explains:

[0165] The present disclosure provides a method for identifying user IDs by a network in order to reduce information element size. and provides the UE with an address for subsequent message exchanges between the UE and the network. Explain how it can be used in a variety of ways.

[0166] (Detailed Description) The present disclosure relates to a method for detecting when a new user is associated with a UE (or is no longer associated with a UE). How the network detects that a user association has changed The network detects which services are available to the UE when and the network is unable to provide service when the user is associated. This section focuses on how the UE requests to be allowed to access

[0167] Section 1 describes when a user logs on and off the UE, and when the user The UE's configured NS when it is linked and when it is not linked to the UE Explain how SAI will be affected.

[0168] Section 2 describes when a user logs on and off the UE, and when a user The UE's authorized NSSAI when linked and unlinked Explain how it can be updated.

[0169] Section 3 provides information about how URSP rules, or information associated with URSP rules, are used by users. Updated to take into account whether a user has generated traffic that is causing a URSP rule to be evaluated. This article explains how this can be achieved.

[0170] Section 4 describes the structure of the proposed User-Centric QoS Rules (UCQR) and the user Regarding new information elements that can be used to transmit central QoS rules to the UE explain.

[0171] Section 5 describes various aspects such as UCQR delivery to the UE, PDU session establishment, etc. Explain the GPP procedure.

[0172] 1. Processing of configured NSSAI during user event The set of services that a UE can access in a PLMN (i.e., the service A configured NSSAI is a registered and configured update NSSAI. It is provided to the UE during the procedure. 3GPP systems have been extended to become "user aware". In this case, the 3GPP system may not know which user is using the UE or which user is using the UE. The UE's configured NSSAI needs to be changed based on what the UE can use. is possible.

[0173] 5GC allows user profiles to be linked to subscriptions It is anticipated that user profiles for various users can be maintained that can recognize the user. The linking action is assumed to be an administrative action to update the user profile or subscriptions. The information can be based on events in the network, such as the user or a third party. The fact that the file is linked to a subscription means that the user The 5GC standard allows users to access the system using a UE associated with the Once a user profile is linked to a subscription, The work may send a configuration to the UE.

[0174] Update messages as described above. Configuration update messages are sent when a user subscribes to In addition, the configuration may be extended to indicate to the UE that the UE is linked to the Update messages are updated based on which users are linked to the subscription. For example, each user may have a separate configured NSSAI. SSAI may be provided and configured for traffic not associated with a user. SSAI may be provided and configured N for traffic associated with all users. An SSAI may be provided, or a single configured NSSAI may be provided, A user identity may be associated with each S-NSSAI in the established NSSAI.

[0175] In some cases, link behavior may be based on events local to the UE. do.

[0176] For example, a user may access a GUI on the UE and request to link the UE with a subscription. A user's invocation of the GUI sends a request to the network. The request can trigger the UE to perform an authentication procedure in which the user is authenticated. The request can be a NAS request, such as a registration update message, that includes the user identity. The registration update message triggers a separate EAP-based authentication procedure in which the user is authenticated. The EAP authentication procedure can interact with the GUI. For example, The authentication procedure involves providing a GUI that requests and receives a password or other verification information. An example of the GUI is shown in Figure 9 and explained below. If the user is successfully authenticated, If so, the network may send a UE Configuration Update (UCU) message to the UE. The UCU message contains an indication that the user has been authenticated and that the user is currently subscribed to The updated configured NSSAI is based on the fact that the application is linked to the The UCU message can also provide the UE with a new authorized NSSAI. The format of the Authorized NSSAI is the network's authorization status for which users are authorized. The UE is informed that it is authorized to access each S-NSSAI using the NSSAI only. This procedure can be extended to allow for the following: As shown.

[0177] The procedure in Figure 6 shows how the UE notifies the network that a user is currently associated with the UE. This procedure indicates whether the user is no longer logged in to the UE. It can also be used by the UE to indicate to the network that it is not However, the authentication procedure may be skipped, but the event still occurs if the UE is configured The present invention may result in a network that can verify and / or update authorized NSSAIs. An indication from the UE to the network that the user should be unlinked from the UE's subscription or the user no longer exists, but the user's profile This indicates to the network that the UE is attached and can remain linked. The UE can then determine that the user should remain linked to the subscription. Whether or not to show it can depend on input from a GUI. For example, the GUI can that the user no longer wishes to be associated with the UE or that the user no longer subscribes To indicate to the UE that it does not wish to be associated with the session (i.e., unlinked). It can be used to indicate that the user should no longer be associated with the UE, and If the UE indicates that the user is no longer linked to the subscription, The network is configured to automatically reconnect when the user is no longer using the UE or when the UE subscription is no longer available. The UE receives a new configured NSSAI that is updated to take into account the fact that it is not linked to the can be provided.

[0178] The procedure in Figure 6 illustrates how the UE allows the network to associate a user identity with the UE. indicates whether the network should send a new configured NSSAI to the UE as a result. The new configured NSSAI is the one that the user is currently linked to the UE subscription. Contains the S-NSSAI that was not previously in the UE's NSSAI because it was configured NSSAI also noted that since users are now linked to their UE subscriptions, It may no longer contain certain S-NSSAIs that were previously in the UE's NSSAI.

[0179] 1. In step 1 of Figure 6, a local event in the UE indicates that a new user is associated with the UE. An example of a local event is a GUI (i.e. people who type new usernames into their browsers, web browsers, applications, etc., and other The device is paired, connected, or connected to the UE via Bluetooth or Wi-Fi. The event also includes a UE receiving a user identification from another device after communicating with the UE. receiving a password or credential information using the user identifier. Based on the input or received information, the user ID and and associated credentials can be derived. 2. In step 2 of Figure 6, the UE adds a user identifier to the UE's subscription. The user sends a registration update request to the AMF to indicate that he or she wants to associate with the AMF. Includes the user ID. 3. In step 3 of FIG. 6, the UE sends a link update request to the UDM. The request is The UDM indicates the UE's SUPI and the user's User ID. The UDR is a repository that stores user applications, and the UDR is a repository that stores user profiles. Access to the repository and UE subscription and user profile information If the information indicates that the link is allowed, the UDM The UE responds that it can be linked with the request. 4. Optionally, in step 4 of FIG. 6, the AUSF communicates with the UE to authenticate the user. The messages between the AUSF and the UE are sent via the AMF. The authentication procedure begins when the UE receives the Send the password or password hash received via the GUI to AUSF It may include the following. 5. In step 5 of Figure 6, the AMF sends a registration response to the UE. If the authentication procedure in step 4 was performed, the response is Indicates to the UE whether the User ID is linked to the option. If the response indicates a failure, the response should include the cause of the failure (e.g., authentication failure or unrecognized user). Links not authorized by the user ID or user or authorized by the subscriber If the link is successful, the registration response contains a cause code indicating the new configuration. A new constructed NSSAI may be associated with a user ID. The flow stops here. . b. If the authentication procedure in step 4 was not performed, the response is The flow includes the following steps: Continued in 6. 6. In step 6 of FIG. 6, the UE performs an authentication procedure with the network. The procedure can be EAP-based and includes the network slice specific authentication and The authentication procedure can be similar to the authorization procedure. This includes sending passwords or password hashes received over the network. or may include the UE prompting the user to enter a password. . 7. In step 7 of FIG. 6, the AMF sends a configuration update request to the UE, sending a message The new configured NSSAI is associated with a user ID. The UE may include a SNSSAI that may be attached to the UE. The UE responds to the configuration update with the following indication:

[0180] The procedure described in Figure 6 begins with the NAS layer of the UE sending a registration request to the network. Alternatively, N other nodes may be used to send requests to the network. An AS message may be used.

[0181] (2. Processing of Authorized NSSAI) Once the user has successfully authenticated with the network, the UE can access different NSSAIs. The user can request to be authorized. Upon successful reception of the configured NSSAI, the UE shall be prompted to send a Registration update message. A registration update message can be triggered based on the user ID. The requested NSSAI can be provided to the network. The format is used by the UE to determine which users are allowed access to each S-NSSAI. The network can be updated to allow users to indicate to the network how they wish to The network uses the user's profile to determine which S-NSSAI the user is allowed to access. It checks whether the NSSAI should be allowed to access the UE and uses this information to assign the authorized NSSAI to the UE. The format of the authorized NSSAI is determined by which user can send the authorized NSSAI to each SN. This procedure indicates to the UE whether it is authorized to access the SSAI. As shown in Figure 7. 1. In step 1 of Figure 7, a local event of the UE is notified to the UE and to the network. A local event causes a determination that a new requested NSSAI should be sent. Examples of local events are , including completing the procedure of FIG. 6. Another example of a local event is when another device uses Bluetooth or After pairing, connecting, or communicating with the UE via Wi-Fi, different users may The E must be unlocked, logged into the UE, and generate application traffic. include. 2. In step 2 of FIG. 7, the UE sends a registration update request to the network. The request checks whether each S-NSSAI in the NSSAI is associated with one or more User IDs. and which user ID is associated with each S-NSSAI. The UE may update the requested NSSAI to reflect the S-NSSAI. It is not associated with a specific user ID, but instead is associated with a subscription It can be used to indicate that a user ID is associated with an S-NSSAI. If not indicated, the network shall notify the UE that the S-NSSAI is This can be interpreted as an indication that the company wishes to associate its products only with the 3. In step 3 of Figure 7, the AMF confirms the UE's subscription and step 1. The UE is granted access by querying the user profile indicated in 1. This step involves multiple queries, e.g. To obtain the subscribed S-NSSAI of the UE, the key is the SUPI of the UE. A UDM query for the user's subscribed S, whose data key is the user's ID. - A UDM query for obtaining the NSSAI. 4. In step 4 of Figure 7, the AMF responds to the UE with an Allowed NSSAI. The message is sent to the user that each S-NSSAI is linked to the UE's subscription. For example, the message may further indicate to the UE whether the UE can associate with the It is possible to provide a list of user IDs that can access each S-NSSAI from The message also prohibits access to each S-NSSAI from the UE. The message may also provide a list of user IDs for a particular S-NSSAI to be sent to the UE. can only be associated with a subscription of one or more users The S-NSSAI can indicate that the UE can be subscribed. The results show that the UE can only be associated with a slot. The traffic exchanged between the device and the UE is charged to the UE subscription and the user. Please note that this is a matter of discretion.

[0182] (3. Application Traffic Processing) As mentioned above, when an application generates traffic, the UE determines which URS To determine if a P rule should be associated with the traffic, the traffic is If a matching rule is found, the UE Determine which route the bot should take (e.g., DNN and S-NSSAI) To assess the RSD of the rule further.

[0183] The traffic descriptor in the URSP rule is updated to include a User ID field. It is possible.

[0184] The UE uses this new field to determine whether the rule is indicated in the User ID field. Know that it only applies to traffic generated by one of the user IDs. If there is no user identity associated with the URSP rule, the UE may This can be interpreted as meaning that the rule applies only to traffic that is not associated with a However, this approach may complicate the evaluation of the URSP rules for the UE. Complexity can increase when a service generates traffic that does not match the URSP rules.

[0185] When this scenario occurs, the match-all URSP rule typically However, some RSDs in match-all URSP rules are , which is permitted to be accessed by the UE but not by the associated user. Therefore, the UE may not know whether the route is You need to check whether it is a valid choice.

[0186] Another approach to handle the provisioning and evaluation of URSP rules is to A separate set of URSP rules is associated with each user and UE. Provision a set of URSP rules that can be used by any user (i.e., without a specific user) However, there are some shortcomings in this approach. The point is that the network will send more data and signaling to the device. It may be necessary to (e.g., the URS used by some users and UEs) The P rules may be very similar or even identical).

[0187] Somewhat reduces the amount of data and signaling required between the UE and the network. Another approach that can reduce the overhead is for the network to provide the UE with two sets of URSP rules. A set can be created without being associated with a specific user. Advantageously, the second set may include a user identifier. However, this approach Some RSD in the match-all URSP rule generates the traffic being evaluated. Contains slices that are allowed to be accessed by one user, not multiple users. Therefore, the UE is still plagued by the fact that the route may You need to check whether it is a valid choice for the user.

[0188] The format of the RSD can also be updated to include a user ID, but this This also means that the UE detects that the traffic matches the URSP rules and decides which route to use. This complicates URSP evaluation in the sense that some of the criteria may not be applicable to users. The UE must then check other URSP rules until a match is found. The current URSP evaluation rules indicate that the match-all rule cannot be applied. .

[0189] The preferred approach is to not modify the URSP rules to include the user ID, but instead to Allows the network to indicate to the UE which user is associated with each URSP rule One advantage of this approach is that when a new user associates with the UE, There is no need to send URSP rules to the UE when a new user associates with the UE. The advantage of this approach is that the URSP rules do not need to be changed when a new network is added. Instead, the network , which users are or are no longer associated with each URSP rule. Therefore, the information that needs to be sent to the UE can be Alternatively, the PSI can be associated with the user identity. When the network provides the PSI to the UE, the PSI is associated with a specific user identity. It can also indicate to the UE which PSI it is currently connected to or associated with. When the UE indicates to the network that it is installed (i.e., registered), E may also indicate the user ID that it believes is associated with each PSI. If the network indicates that I is not associated with any user identity, the UE Assuming that PSI should be used for traffic not associated with any user, Alternatively, the PSI may be configured to include the URSP rules and user ID. The user ID is associated with all URSP rules in the PSI. The network may be included in the PSI without updating the URSP rules included in the PSI. The NAS procedures can be updated so that the user ID that is being accessed can be updated.

[0190] Figure 8 shows that the policy set entry for the UE contains six PSIs and the UE is The example shows scenario 800 associated with three users (users A, B, and C). The policy in PSI#1 is used for traffic from users A and B. The policies in PSI#1 and PSI#2 are used only for traffic from User A. The policy in PSI#4 is used only for traffic from user B. The policy in PSI#5 is used only for traffic from user B. The policy is for traffic that is not associated with any user (i.e., The policy in PSI#6 applies to all Traffic (i.e. all users and all traffic).

[0191] The policy set association information is sent to the UE in the same manner as that used to send PSI. AS messages (e.g., registration responses, or UE policy containers or PSI-containing Any NAS message) can be sent by the network to the UE. The network then transmits this information to the UE in order to install or configure the information in the UE. It can be sent.

[0192] The policy set association information is used to send PSI to the network. The same NAS message (e.g., registration request, or UE policy container or PS It can be sent from the UE to the network in any NAS message containing I. The UE can determine which rules or association information is installed or configured in the UE. This information can then be sent to the network to inform the network whether .

[0193] If an ANDSP rule is associated with a user identity, the UE When it is logged in, associated to the UE, or generating traffic on the UE Note that a policy can be considered active only when sea ​​bream.

[0194] Section 1 may cause the network to update the UE's configured NSSAI. We have described various events. These same events are updated in the network. The new or updated policy set entry association information is sent to the UE along with the new or updated policy set entry association information. The new or updated PSI can be transmitted by the UE. User ID so that RSP rules can know which user ID is associated with which user ID Contains or is associated with a user ID.

[0195] (4. User-Centric QoS Rules (UCQR)) The QoS Rule Identifier (QRI) is a part of a user's profile that links the corresponding QoS rule. The user profile can be stored in the UDR. Alternatively, the user's QoS rules can be stored in some other database. User-centric QoS rules can be transmitted to the UE. Regarding new information elements that can be used to transmit user-centric QoS rules to the UE, The system performs this through procedures such as PDU session establishment, registration, and UE configuration update. The new IE can be triggered to be sent to the UE. This is discussed later in this document.

[0196] The QoS rules IE is described in TS 24.501

[11] . User-centric QoS A new type of IE can be created for the rule. The new IE is The new IE is called User-Centric QoS Rules (UCQR). The structure or format of the UCQR IE (e.g., UCQR IE1500) The set is shown in FIG.

[0197] Note that in FIG. 15, the UCQR IE includes a new IE called User ID. The format of the user ID may be an alphanumeric string of varying length. The length of the User ID IE may be used to indicate the length of the string to the UE. can be done.

[0198] FIG. 16 illustrates how a user-centric QoS rule IE (e.g., UCQR IE 1600) can be used to It shows how it can be further extended to carry rules for the user. This indicates the corresponding UCQR for user 1 to user m.

[0199] Alternatively, the length of the User ID may be fixed and expressed in octets. The UCRQ IE MAY be formatted to contain multiple User ID IEs. Therefore, a QoS rule that applies to multiple users can be The IE can be provided to the UE.

[0200] Alternatively, a new UCQR IE may be created to provide user-centric QoS rules to the UE. Instead, the format of the existing QoS Rules IE is extended to include the User ID. This may also be the case.

[0201] Alternatively, a new type of user-centric QoS rule is created to include the user ID, It may be carried in the QoS rule IE.

[0202] Yet another alternative is to extend the structure of the QoS rule IE in Figure 13 to include the QoS of the user ID. The mapping to rules shall be provided, possibly at the bottom of the QoS Rule IE structure. In this way, only a limited amount of changes to the existing format can be achieved. can be achieved.

[0203] The presence of a user ID in the QoS IE indicates that a set of QoS rules corresponds to the user ID. to the UE that the It can be an instruction.

[0204] 5. User-centric QoS rule distribution and enforcement This section describes the various 3GPP procedures by which UCQR can be delivered to the UE. I will explain this in more detail.

[0205] (UCQR delivery during DE requested PDU session establishment process) FIG. 17 shows the DE requested PDU session establishment process.

[0206] 1. Step 1 in Figure 17 - UE to AMF: A user or application A NAS message can be triggered for PDU session establishment with the user ID. The messages from the UE to the network are NAS messages (S-NSSAI, DN N, PDU Session ID, Request Type, Old PDU Session ID, N1 SM Context The message contains one or more user IDs. The user ID can be enhanced to include the NAS SM container (PDU session establishment The presence of a user ID may be part of a PD request by an identified user. The UE can indicate to the network that a U-session will be used. If a specific user ID is not provided in the request within the page, the procedure is l The PDU session establishment process described in 16[6] can be reverted to, and the PD A U-session is related to the UE and includes all the PDU sessions involved in the UE-originated PDU sessions. The same QoS rules can be applied to multiple users. Note that the SM PDU DN request container can also contain a user ID. Please note that the user ID is required for secondary authentication and authorization with the DN-AAA server. It is possible. 2. Step 2 in Figure 17 - The AMF selects an appropriate SMF. 3. Step 3 in Figure 17 - AMF to SMF: The AMF sends the Nsmf_PDU session Nsmf_CreateSMContext request or Nsmf_PDUSession_Upda Invoke one of the teSMContext requests and use the user ID provided by the UE Includes. 4. Step 4 in Figure 17 – Corresponding SUPI, DNN, and S-NSS for HPLMN If session management subscription data for the AI ​​is not available, the SMF Obtain administrative enrollment data. User profile information is available for an identified user. If not possible, the SMF obtains the information from the UDR. et(SUPI, User ID, Session Management Join Data, DNN, HPLMN SN SSAI) and this subscription data is passed to Nudm_SDM_Subscribe(SU PI, User ID, Session Management Join Data, DNN, S-NSSAI of HPLMN) You can subscribe to be notified of any changes using the Subscriptions are managed by the user's profile as described in Section 5.2. Note that the process Nudm_ SDM_Get, Nudm_SDM_Subscribe, Nudr_DM_Query In this case, the SMF can request information from the user's profile based on the user ID. The response is based on the user's profile and subscriptions that exist in the UDM / UDR. The QoS rules may include user-centric QoS rules obtained from option relationships. If the UE request is considered not valid, the SMF shall not establish a PDU session. decides not to accept 5. Step 5 of Figure 17 - SMF to AMF: The SMF is NSMF_PDUSession_CreateSMContext in response to the request Response (Cause, SM Context ID or N1 SM Container (PDU Session Rejected ( Cause))) or Nsmf_PDUSession_UpdateSMContext response provide one of the answers. In step 3, SMF creates Nsmf_PDUSession_CreateSMCo If an ntext request is received and the SMF is able to process the PDU session establishment request In this case, the SMF creates an SM context and notifies the SMF by providing the SM context ID. The device responds to the AMF. This response is based on information obtained from the user profile via UDM / UDR. This can include the UCQR created by the SMF. 6. Step 6 in Figure 17 - Optional secondary authentication / authorization. UCQR is responsible for After completion, the message can be delivered to the UE. This process is described in Section 5.5.4. It is written. 7a. Step 7a in Figure 17 – Dynamic PCC should be used for the PDU session In this case, the SMF is based on the PC standard described in TS 23.501

[12] , clause 6.3.7.1. F Select. If the request type is "Existing PDU Session" or "Existing Urgent PDU If the SMF indicates "session", the SMF will use the PCF already selected for the PDU session. shall be used. If not, the SMF may apply local policies. 7b. Step 7b of Figure 17 - The SMF establishes an SM policy association with the PCF; To get the default PCC rules for the PDU session, use the SM policy association GPSI is included in the SMF when available. If the request type in step 3 indicates "existing PDU session", the SMF policy association change procedure initiated by SMF. - It can provide information about the control request trigger conditions. The PCF shall incorporate the PCC Rules into the User Subscription and / or User Profile. can be associated with a user subscription and / or user profile The rule can contain the QoS Rule Identifier (QRI) of the UCQR belonging to the user. Optionally, the company may enforce PCC rules for each user based on UCQR. do. Or, if the PDU session requires reauthentication / reauthorization, authentication and authorization are not successful. If successful, the SMF can request a UDM for a new UCQR. Note: The purpose of step 7 is to receive the PCC rules before selecting the UPF. If CC rules are not required as input for UPF selection, step 8 is followed by step Step 7 can be performed. 8~10. Steps 8~10 in Figure 17 are based on 4.3.2.2 of TS 23.502[6]. It can correspond to .1-1. 11. Step 11 in Figure 17 - From SMF to AMF: AMF is the Namf_Commu Call nication_NlN2 message transfer. Namf_Communication_NlN2 Message transfer is a user The user-centric QoS rules may be extended to include PDU session-centric QoS rules. This may be included in the session establishment acceptance message. The N2 SM information carries information that the AMF forwards to the (R)AN. The N1 SM container contains a PDU session establishment acceptance provided by the AMF to the UE. If necessary for QoS, multiple user-centric QoS rules, QoS flow-level QoS parameters Data The flows associated with those user-centric QoS rules and QoS profiles are It may be included in the PDU session establishment acceptance in the SM and in the N2 SM information. 12. Step 12 in Figure 17 - AMF:N2 PDU Session Request to (R)AN ( N2 SM Information, NAS Message (PDU Session ID, N1 SM Container (PD U Session Establishment Acceptance), [CN Assisted RAN Parameter Tuning]. AMF PDU session ID and PDU session establishment acceptance targeted to the UE, and N2 NAS message containing N2 SM information received from SMF in PDU session request The message is sent to the (R)AN. 13. Step 13 in Figure 17 - (R)AN to UE: The (R)AN receives from the SMF The AN may issue an AN-specific signaling exchange with the UE related to the received information. The AN receives the NAS message (PDU session ID, N 1 SM container (PDU session establishment acceptance) to the UE. The (R)AN The AN-specific signaling exchange with E is related to the received N2 command. A NAS message shall be provided to the UE only if it contains additional resources. If SM information is not included in step 11, steps 14 to 20 below are omitted. 14. Steps 14-20 of FIG. 17 are unchanged from FIG.

[0207] A user triggers a UE to establish a PDU session with a core network. and a second user can transmit via the same PDU session from the UE. Please note that there may be situations where two people can initiate data traffic. If multiple users share a PDU session, this incident will be reported as a PDU session change. A typical case is when the UE is in a PD A PDU session may be established and another user may be attempting to use the existing PDU session. When initiating data traffic to be sent from the Depending on how the UE is defined according to the IEEE 802.11 standard, one of the following is delivered to the UE: It is possible. 1. The same new UCQR for both users (UCQR with the user IDs of both users) ) 2. A new UCQR dedicated to the second user. 3. A new UCQR that is different for each user. 4. Updating the mapping of user ID to QoS rules via the new UCQR IE.

[0208] (User-centric QoS rule distribution during PDU session modification process) PDU Session Modification Procedure Requested by UE or Network (Non-Roaming and roaming with local breakout scenario) is shown in FIG. 18. Several occasions or conditions may result in a session change and therefore a new UCQR allocation to the UE. Some conditions can be: · Change user. Add users. A new user joining an existing PDU session. - Application changes. Adding an application session to an existing PDU session. Ending an application session. Policy changes and billing due to changes in subscriptions (e.g. application tokens) QoS Upgrade for Traffic

[0209] 1. The procedure can be triggered by the following events: Step 1a of Figure 18. (Initiated by a user or application in the UE) Modify) A user or application can initiate a PDU session modification procedure. When a NAS message is sent, the message is extended to include one or more user IDs. The NAS message can be sent by the (R)AN with an indication of the user location information. The AMF forwards the PDU to the AMF via the Nsmf_PDUSession_UpdateSM Call Context.

[0210] A user-triggered PDU session modification procedure starts a user authentication procedure. It is possible.

[0211] Step 1b in Figure 18. (SMF Requested Change) The PCF requests the policy change. Performs a PCF-initiated SM policy association change procedure to notify the SMF. This is Policy decisions or AF requests, e.g., traffic routing for application functions This case may have been triggered by an impact on the user subgroup. Includes referencing UDMs for subscription and user profile information and the User's UCQR may be taken into account for the PCC policy or changes thereto. In the PCF notification, the PCF sends a changed PDU to the SMF indicating the policy change. The SMF may include an indication of the UCQR required for the session. A new UCQR can be fetched, or the PCF can send the UCQR to the SMF. Step 1c in Figure 18. (SMF Request Changes made) UDM is Nudm_SDM_Notification(SUPI, session Update the subscription data in the SMF via the SMF Management Subscription Data.

[0212] This notification can be extended to include the new UCQR for the UE. The MF updates the session management subscription data and returns an Ack by (SUPI). Therefore, the UDM is acknowledged.

[0213] Step 1d in Figure 18. (SMF requested change) The SMF requests the PDU session to be changed. This procedure can also be based on locally configured policies. It may be triggered based on the (R)AN or it may be triggered from the (Service)AN. A UP connection is activated (as described in the service request procedure) and the SMF is The status of the QoS flow is deleted in 5GC but is not yet synchronized with the UE. It can also be triggered if marked.

[0214] Step 1d-1 in Figure 18. The change of PDU session is New QoS rules may need to be taken into account. The SMF and requests new information from the user profile from the UDM and simultaneously enforces the PCC rules. or vice versa, and will be implemented for the modified PDU session. It is possible.

[0215] If the SMF receives one of the triggers in steps 1b to 1d, the SMF Initiate the Request PDU Session Modification procedure.

[0216] Step 1e of Figure 18. (AN Initiated Change) The (R)AN checks whether notification control is configured. When the AN resources to which the QoS flows are mapped are released, regardless of whether is shown in the SMF.

[0217] Figure 18, Step 2. SMF detects SM policy association changes initiated by SMF. Reports any subscribed events to the PCF by executing a procedure. This step involves obtaining the user ID and the corresponding subscription / profile. This can be extended by the association of file information with PCC rules. The PDU session change procedure can include an information exchange between the PDU session and the UDM. If triggered by b or 1d, this step can be skipped. If dynamic PCC is not deployed, the SMF determines whether to change the QoS profile. Local policies may be applied to determine whether

[0218] Step 2a in Figure 18. If redundant transmission is not activated for the PDU session, If the SMF decides to perform redundant transmission for a new QoS flow, the SMF F is additional CN tunnel information if CN tunnel information is assigned by SMF Additional CN tunnel information is provided to the UPF via an N4 Session Modification Request. The SMF also configures the UP to perform packet duplication and deletion of QoS flows. Give instructions to F.

[0219] If redundant transmission is activated on a PDU session and SMF stops redundant transmission, If the decision is made to use the SMF as a redundant tunnel for the PDU session, the SMF Instruct UPF to release N tunnel information and perform packet duplication for the corresponding QoS flow. and also instructs UPF to stop the deletion.

[0220] Step 2b in Figure 18. The UPF responds to the SMF. PDU sessions and PDUs indicated to UPF to perform packet duplication and deletion If redundant transmission is not activated for the SMF, the UPF transmits the CN tunnel information If assigned by UPF, assign additional CN tunnel information. The CN tunnel information is provided to the SMF.

[0221] If redundant transmission is not activated for the PDU session and SMF is In a, it is decided to perform redundant transmission of a new QoS flow using two I-UPFs. If set, the UPF will use the CN tunnel information if it is assigned by the UPF. N tunnel information is allocated. The CN tunnel information of the two I-UPFs is provided to the SMF. do.

[0222] In step 3a of FIG. 18, in case of a change initiated by the UE or the AN, the SM F sends the AM via Nsmf_PDUSession_UpdateSMContext In response to F, Nsmf_PDUSession_UpdateSMContext Both the N1 SM container and the N2 SM information contain user-centric QoS rules.

[0223] In the case of signaled QoS, the new UCQR is the QoS of the modified PDU session. The signaled Qo S allows the SMF to update the U of the new UCQR for the modified PDU session. DM / UDR can be requested.

[0224] The N2 SM information carries information that the AMF provides to the (R)AN. It includes one or more QoS profile to inform the (R)AN that a QoS flow has been added or changed It can contain a file and a corresponding QFI, which indicates when one or more QoS flows are deleted. The SMF may contain only the QFI to notify the (R)AN that the SMF has been removed. For each QoS flow, the corresponding redundant transmission indicator indicates whether redundant transmission should be performed. It can be indicated whether the PDU session change is due to the (R)AN release in step 1e. When triggered by the (R)AN release, the N2 SM information carries the acknowledgment of the (R)AN release. The PDU Security Header is used for PDU sessions that do not have user plane resources established. When a session change is requested by the UE, the N2 SM information provided to the (R)AN is , contains information for the establishment of user plane resources.

[0225] The N1 SM container carries the PDU session modification command that the AMF should deliver to the UE. It sends a notification that one or more user-centric QoS rules have been added, deleted, or modified. In order to inform the UE of the user-centric QoS rule, the QoS flow associated with UCQR is flow-level QoS parameters and corresponding QoS rule operations if required for The QoS may include flow-level QoS parameter calculations.

[0226] Figure 18, step 3b. For changes requested by the SMF, the SMF is extended with UCQR. Namf_Communicati with N2 SM information and N1 SM containers Call on_N1N2 message transfer.

[0227] In the case of changes requested by the SMF, the SMF shall We have already consulted with UDM about the user profile and therefore Namf_Com munication_N1N2 Message Transfer Message New UCQR It can be assumed that

[0228] Step 3c in Figure 18. The SMMF related parameters are updated from the UDM. If F requests a change, the SMF will tune to the AMF by using the SMF-derived CN-assisted RA In addition, the SMF can provide the UD for the corresponding user. M with a new UCQR. The SMF can be received from the AM Nsmf_PDUSession_SMContextStatusNotify fy (SMF derived CN assisted RAN parameter adjustment). The AMF SMF-derived CN-assisted RAN parameter adjustment in associated PDU session context Step 4 in Figure 18. The AMF sends an N2 PDU session request to the (R)AN. (N2 SM information received from SMF, NAS message (PDU session ID, N1 SM container (PDU session change command)) messages can be sent The PDU session modification command may contain a new UCQR for the UE. do.

[0229] Step 5 of Figure 18. The (R)AN communicates with the UE related to the information received from the SMF. The (R)AN can issue a specific signaling exchange. As an S procedure, the UCQR received from the SMF / UDM on behalf of the user is delivered to the UE. This can be done.

[0230] Steps 6 to 13 correspond to 4.3.3.2.1-1 of TS 23.502[6]. It is possible.

[0231] (UCQR distribution during network slice specific secondary authentication process) Once a user is authenticated and authorized, UCQR performs network slice specific authentication and During the SSAA process, the UE can receive the ACK and ACK information for the authenticated user. Figure 19 shows that the UCQR is delivered to the UE together with the SSAA success message. do.

[0232] The S-NSSAI may be associated with a user identity, and this association may be It may be stored in the DR and / or AAA-S server. If the configuration of the S-NSSAI is changed, the UDM / UDM via SMF / AUSF R can trigger the SSAA process. On the other hand, AAA-S belongs to a third party. When the settings from S-NSSAI to the user are updated by AAA-S , the AAA-S can trigger an SSAA to the user.

[0233] The network slice-specific secondary authentication process is similar to the PDU session establishment procedure. It is understood that CN does not include SMF. However, it does include network functions (e.g. The extent to which a third-party entity has control over a network slice is determined by the U AAA servers or other network devices that may have the ability to contribute to CQR distribution It may include a function.

[0234] Step 1 in Figure 19. Based on changes in subscription information or to AAA-S Triggered by the S-NS, which requires network slice-specific authentication and authorization In the case of SAI, the AMF triggers the initiation of network slice specific authentication and authorization procedures. It can be done.

[0235] Step 2 in Figure 19. The AMF sends the NAS MM transport media containing the S-NSSAI. UE user information about EAP authentication (EAP ID) for S-NSSAI in the message This is the S-NSSAI of the H-PLMN and can be used to request a local user ID. This is not the S-NSSAI value mapped to the rule.

[0236] Steps 3 to 17 in Figure 19. E in clause 4.2.9.2 of TS 23.502[6] Part of the AP-based SSAA process.

[0237] Step 18 in Figure 19. If the user of the UE is successfully authenticated, the AMF sends a query Nud m_SDM_Get(UCQR) can be sent to the UDM. The UDM can then Consult and inquire from the user's profile and user subscriptions The UDM can extract the UCQR specific to the user. The UCQR can be placed in the UDR by the SMF or PCF. In some cases, this may be the case.

[0238] Step 19 in Figure 19. As part of the authentication and authorization process, the AMF M transport message (user-centric QoS rule [success], EAP success / failure) This message is sent by the AMF to the send user-centric QoS rules only to the NAS MM transport message (EAP failure) can be sent.

[0239] Step 20 in Figure 19. This step is specified in 4.2.9.2 of TS 23.502[6]. This corresponds to step 19 of the section.

[0240] (UCQR rule distribution during secondary PDU session authentication process) Figure 20 shows that UCQR can be delivered to the UE after the secondary PDU session authentication is successful. It shows how it can be done.

[0241] The SMF determines that it is necessary to contact the DN-AAA server. The SM PDU DN request container provided by the UE in the NAS request. Use the SM PDU D to identify the DN-AAA server based on the local configuration. The N-Request Container shall be extended to include the User ID during the PDU Session Establishment Request. This can be done.

[0242] 1. Step 1 of Figure 20 – To carry DN related messages between SMF and DN If there is no existing N4 session that can be used, the SMF selects a UPF, Triggers N4 session establishment. 2. Step 2 of Figure 20 - The SMF sends the enhanced SM received from the UE in a NAS message The DN Request Container is provided to the DN-AAA via the UPF. The DN Request Container IE contains information for PDU session authorization by an external DN. The SM PDU DN request container is in Network Access Identifier (NAI) format. It contains its DN unique identifier and PDU Session ID [9] conforming to the RFC 2222 standard, if available. In this case, the SMF provides the GPSI in the signaling exchanged with the DN-AAA. ,Transparently relays messages received from SMF to the DN-AAA server. 3. Step 3 of Figure 20 - Step 3 is the message exchange between the UE and the DN AAA server. The DNN-AAA server receives user authentication and authorization decisions from the user. The identity can be taken into account and the DN authorization profile index can be determined. . 4. Step 4 in Figure 20 – DN-AAA server reports successful authentication / reception of the PDU session Verify authorization. The DN-AAA server can provide: successful authentication / SM PDU DN response container to SMF to indicate authorization; DN Authorization Data PDU as defined in clause 5.6.6 of TS 23.501

[12] The IP address assigned to the session and / or the PDU session for the UE Notify the N6 traffic routing information or MAC address used by The IP address (or IPV6 prefix) for the request PDU session. The UE may need a new set of UCQR for the corresponding user identity. The instructions were: N6 traffic routing information is specified in clause 5.6.7 of TS 23.501

[12] . It is defined. After successful DN authentication / authorization, the session is maintained between SMF and DN-AAA When the SMF receives DN authorization data, the SMF Applying policy and charging controls using the (see paragraph 6). This DN authorization profile index points to policy and charging control data. This can be aligned with the requirements of the corresponding users. 5. Step 5 in Figure 20 – SMF via PCF or SMF is notified by DN-AAA The UD can request the UDM for the UCQR of the user of the UE that is authenticated and authorized by the UD The M / UDR provides the UCQR to the SMF. 6. Step 6 in Figure 20 - The SMF via the AMF delivers the new UCQR to the UE. 7. Step 7 in Figure 20 - The UE recalculates the PD based on the newly received user-centric QoS rules. This is a variation of steps 7 and 8, except that you can now establish and start a U session. No change.

[0243] (Further optimization of UCQR rule distribution) As previously described herein, user IDs may be of inconsistent size (e.g., person-name@m no.net, person-name.domain-id@mno.net, etc. Sending longer names over the air constantly may increase the amount of radio signaling resources. Therefore, for optimal calculation, we recommend using user IDs with consistent IE size. One way to represent the user identity of a user in a UE is as follows: The solution is to have a translation table that contains user IDs with numeric aliases that correspond to the , the user ID person-name@mno-name.net will be converted to the number 76 can.

[0244] Once the subscription and user profile are linked, the network The alias number of the user ID can be sent to E.

[0245] The advantage of receiving the alias is that the alias is local to the UE and has a size of The advantage of this is that it allows for small (e.g. one octet) ids. All signaling can use this alias, resulting in OTA signaling. The amount of smacking is reduced.

[0246] It is sent from the network to the UE and is described in the paper as containing the user ID. In all messages, the user ID alias can be used instead. I want to be understood.

[0247] Alternatively, the user ID can be assigned to each user-centric QoS rule in the list, as shown in FIG. Depending on the position, the UCQR IE (e.g., UCQR IE2100) may be implied. In this case, the user identity may instead be already configured (separately) in the UE. It may be the index of the UE in the list of UEs. For example, the index of the user is , may be an alias previously signalled to the UE. The quality can save further resource consumption on signaling.

[0248] (GUI) Figure 9 shows how a person operating a cellular device can identify a user whose user ID is associated with the cellular device. Used to request to be linked and unlinked from attached subscriptions. 9 illustrates an exemplary GUI 900 that can be used in the This is explained further in 5.1.

[0249] FIG. 22 shows the result when a user logs into a multi-user UE and the UE receives UCQR. 22 shows the GUI 2200 of an instance. Multiple users may have accounts on the UE. Each user may have access to multiple applications within his or her account. In FIG. 22, a user logs in to the UE with a user ID, user 4523. It can trigger the Extended PDU Session establishment or modification procedures. do.

[0250] The concepts described in this disclosure may be applied to non-public networks (NPNs). When this concept is applied to NPNs, the format of the user identifier is The mat may be such that the identity of the NPN is part of the user identifier, or The user identifier is a field that can be resolved by the network to the identity of an NPN. This allows the network to determine which UDM / UDRs are associated with which user profile. This is necessary to be able to determine whether a file is involved in the storage of Alternatively, all messages and procedures proposed in this disclosure as including a user identifier may be , an NPN identification indicating that the user identifier is associated with a non-public network; It can also include children.

[0251] Any of the methods and processes described herein may be stored on a computer readable storage medium. Even if embodied in the form of computer-executable instructions (i.e., program code) The instructions are often sent to computers, servers, M2M terminal devices, M2M gateway devices, and other devices. When executed by a machine, the systems, methods, and processes described herein can be performed and In particular, it will be understood that the steps, acts, or functions described above may be implemented in any manner. Any of the functions may be implemented in the form of such computer-executable instructions. A computer-readable storage medium is implemented in any method or technology for storing information. This includes both volatile and non-volatile, removable and non-removable media, Such a computer-readable storage medium does not include a signal. AM, ROM, EEPROM, Flash memory or other memory technologies, CD-ROM , digital versatile disks (DVDs) or other optical disk storage devices, magnetic cassettes, A magnetic tape, magnetic disk storage device or other magnetic storage device, or a device for storing the desired information Any program that can be used to access any computer This includes, but is not limited to, any other physical medium.

[0252] In describing preferred embodiments of the subject matter of the present disclosure, as shown in the figures, for the sake of clarity, Certain terms are used, however claimed subject matter may be modified in any way to suit the particular terms so selected. No limitation to the specific terminology is intended, and each specific element may accomplish a similar purpose. It is to be understood that the present invention includes all technical equivalents that operate in a similar manner to accomplish the present invention.

[0253] Therefore, it is to be understood that the disclosed system and method may not deviate from its spirit or essential characteristics. It will be understood by those skilled in the art that the present invention may be embodied in other specific forms without departing from the spirit and scope of the present invention. Therefore, the embodiments disclosed herein are illustrative and not restrictive in all respects. It is not intended to be exhaustive or to limit the disclosure to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be practiced without departing from the spirit and scope of the present disclosure. can be obtained without departing from the breadth or scope of the present specification. Although a particular configuration has been described, other configurations may be employed. and other embodiments (e.g., combinations, rearrangements, etc.) will be enabled by this disclosure and will be apparent to those of skill in the art. and are considered to be within the scope of the disclosed subject matter and any equivalents thereof. Features of the disclosed embodiments may be combined to produce additional embodiments within the scope of the invention. They can be combined, rearranged, omitted, etc. Features can be used advantageously without the corresponding use of other features. Applicant wishes to exclude all such alternatives, modifications and variations that fall within the spirit and scope of the disclosed subject matter. , equivalents, and modifications are intended to be covered herein.

[0254] Reference to a singular element does not mean "one and only one" unless expressly stated otherwise. rather, "one or more." When a phrase similar to "at least one of A, B, or C" is used, this The phrase may have A alone present in an embodiment, B alone present in an embodiment, C alone present in an embodiment, Any combination of elements A, B, and C may be present in an embodiment, or any combination of elements A, B, and C may be present in a single embodiment. It is intended to be interpreted to mean that A and B may be present in the embodiment. and B, A and C, B and C, or A and B and C.

[0255] Unless an element is expressly recited using the word "means," any element in this specification may be The elements of the claims should also be construed under the provisions of 35 U.S.C. § 112(±). As used herein, "comprises" and "comprises" are used interchangeably. The term "comprising" or any other variation thereof is intended to include a non-exclusive inclusion. Any process, method, article, or apparatus that includes a list of elements is intended to be It does not include only those elements, but any elements not explicitly listed or The scope of the present invention is not to be construed as limiting the present invention, but rather as a contemplated embodiment. The above description is not intended to limit the scope of the invention, but rather to limit the scope of the claims. and all modifications within its scope are intended to be included.

[0256] JPEG2024170400000005.jpg161167

Claims

1. 1. An electronic device comprising: Associating a user identifier with an identifier corresponding to a subscription associated with the electronic device. sending a link request message to the wireless network requesting that the From the wireless network, the user identifier is associated with the electronic device. receiving a registration response verifying that the subscription identifier is associated with the updated configuration information for the electronic device from the wireless network; receiving configuration information, at least a portion of which is associated with the user identifier; R, The circuit is configured to Electronic devices.

2. The circuit is connected to a graphical user interface (GUI) of the electronic device. Based on the input information, the user identifier is associated with the electronic device. configured to determine that the received identifier should be associated with the received identifier; The electronic device of claim 1 .

3. the circuitry wirelessly pairs with another electronic device; upon receiving the user identifier from the other electronic device, , determining that the electronic device should be associated with the subscription identifier associated with the electronic device. The electronic device of claim 1 configured to:

4. The electronic device of claim 1 further comprising receiving an alias for the user ID. Chair.

5. A subscription identifier associated with the electronic device is an international mobile subscription identifier for the electronic device. Identification of Users (ISMI) 5. The electronic device of claim 4.

6. The circuitry connects the user to the wireless network based on the user identifier. configured to run a process to authenticate, The electronic device of claim 1 .

7. The updated configuration information is available to the electronic device and to the user. indicating at least one additional service associated with the identifier; The electronic device of claim 1 .

8. The updated configuration information is updated based on the network slice selection assistance information of the electronic device ( The NSSAI includes at least one NSSAI associated with the user identifier. Containing one single network slice selection assistance information (S-NSSAI); The electronic device of claim 1 .

9. When the circuitry receives the updated configuration information, the circuitry updates the user identifier to A structure that links to available services that are authorized to be accessed by the identifier. configured to update configuration information, The electronic device of claim 1 .

10. The circuitry includes: a user identifier and a subscription identification associated with the electronic device; A registration renewal request that requests access to a service based on at least one of the children of the configured to transmit over the wireless network; The electronic device of claim 1 .

11. The circuitry receives a signal based on the user identifier and the subscription identifier corresponding to the electronic device. and transmitting a registration update request to the wireless network requesting access to a service based on the It is configured as follows: The electronic device of claim 1 .

12. The circuitry receives a registration update request requesting access to a service based on the user identifier. configured to transmit a request to the wireless network; The electronic device of claim 1 .

13. The circuitry determines which access the electronic device is authorized to have based on the registration update request. and configured to receive information identifying one or more services to be 11. The electronic device of claim 10.

14. The circuitry stores each of a plurality of user identifiers in a memory accessible by the user identifier. configured to store information linking the user to one or more services for which the user is authorized to use the service; It is being The electronic device of claim 1 .

15. The circuitry determines how traffic generated in the electronic device is processed. configured to receive and store information corresponding to a policy section that identifies which wherein at least one of the policy sections is associated with the user identifier. Can be attached, The electronic device of claim 1 .

16. The circuitry detects that a policy section is no longer associated with the user identifier. and configured to receive information indicative of 16. The electronic device of claim 15.

17. The circuit indicates that the PDU session should be associated with a user identifier. Send a PDU session establishment request and set up a PDU session with a QoS rule. and receiving a PDU session establishment response from the The electronic device of claim 1 .

18. the QoS rules indicate whether they are associated with a user identifier; 20. The electronic device of claim 17.

19. 1. A method performed by an electronic device, comprising: A user identifier is requested to be associated with a subscription identifier associated with said electronic device. transmitting a link request message to a wireless network requesting a link to be established; The wireless network receives a notification from the user that the user identifier is associated with the electronic device. receiving a registration response verifying that the received registration is associated with the registered identifier; updated configuration information for the electronic device from the wireless network; receiving configuration information, at least a portion of which is associated with the user identifier; and method.

20. A non-transitory computer readable medium containing computer program instructions, said computer The computer program instructions, when executed by an electronic device, cause the electronic device to: A user identifier is requested to be associated with a subscription identifier associated with said electronic device. transmitting a link request message to the wireless network requesting a link to the wireless network; From the wireless network, the user identifier is associated with the electronic device. receiving a registration response confirming that the registration response is associated with the subscription identifier; updated configuration information for the electronic device from the wireless network; receiving configuration information, at least a portion of which is associated with the user identifier; Let, Non-transitory computer-readable medium.

Images