Method and apparatus for providing network service to various devices by using terminal

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. An operation method of a user equipment (UE) in a wireless communication system, according to an embodiment of the present disclosure, may comprise the steps of: receiving, from a non-3rd generation partnership project (non-3GPP) device, an internet protocol (IP) connectivity request message including a device identifier (ID) of the non-3GPP device connected to the UE and a credential capable of authenticating the non-3GPP device in a network; and transmitting, to an access and mobility management function (AMF), a protocol data unit (PDU) session establishment request message that requests generation of a PDU session for the non-3GPP device.

Description

Method and device for providing network services to various devices using terminals

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. More specifically, the present disclosure relates to a method and device for providing network services using a terminal to various devices in a wireless communication system.

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

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

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

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

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

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.

[0009] A method for operating a UE (user equipment) in a wireless communication system according to an embodiment of the present disclosure may include the steps of: receiving an IP (internet protocol) connection request message including a device identifier (ID) of a Non-3GPP (3rd generation partnership project) device connected to the UE and credentials capable of authenticating the Non-3GPP device in a network from the Non-3GPP device; and transmitting a PDU session establishment request message requesting creation of a PDU (protocol data unit) session for the Non-3GPP device to an AMF (access and mobility management function).

[0010] One embodiment of the present invention provides a device and method capable of effectively providing services to various devices connected to a terminal in a wireless communication system.

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

[0012] FIG. 1 illustrates the structure of a wireless communication system according to various embodiments of the present disclosure.

[0013] FIG. 2 illustrates a scenario in which various devices using a terminal according to an embodiment of the present disclosure use a network service.

[0014] FIG. 3 illustrates a scenario in which each device using a terminal according to an embodiment of the present disclosure uses a network service.

[0015] FIG. 4 illustrates a procedure in which devices connected to a terminal according to an embodiment of the present disclosure use a network service by utilizing the terminal's network operator.

[0016] Figure 5 illustrates the configuration of a terminal according to embodiments of the present disclosure.

[0017] FIG. 6 illustrates a configuration of a base station or network entity according to embodiments of the present disclosure.

[0018] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the attached drawings. It should be noted that, where possible, identical components are represented by identical reference numerals throughout the drawings. Furthermore, detailed descriptions of well-known functions and configurations that may obscure the gist of the present invention will be omitted.

[0019] In describing the embodiments herein, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present invention will be omitted. This is to avoid obscuring the gist of the present disclosure by omitting unnecessary explanations and to convey the gist more clearly.

[0020] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0021] The advantages and features of the present disclosure, and the methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

[0022] Furthermore, when describing the present disclosure, detailed descriptions of related functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0023] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a gNode B (gNB), an eNode B (eNB), a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, in the following, LTE (long-term evolution), LTE-A (LTE-advanced) or 5G (5 thAlthough the present disclosure may be described as an example of a 5G (new radio (NR)) system, the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. For example, this may include the 5G (new radio (NR)) mobile communication technology developed after LTE-A, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications within a range that does not significantly deviate from the scope of the present disclosure, as determined by a person having skilled technical knowledge.

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

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

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

[0027] Wireless communication systems have evolved from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 3GPP's HSPA (High Speed ​​Packet Access), LTE (or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2's HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE's 802.16e.

[0028] As a representative example of a broadband wireless communication system, the LTE system uses the OFDM (Orthogonal Frequency Division Multiplexing) method in the downlink and the SC-FDMA (Single Carrier Frequency Division Multiple Access) method in the uplink. The uplink refers to a wireless link in which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (eNode B, gNode B, or base station (BS)), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. The above-described multiple access method can distinguish the data or control information of each user by allocating and operating the time-frequency resources to be transmitted, including data or control information, so that they do not overlap with each other (i.e., so that orthogonality is established).

[0029] As a future communication system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra-Reliable Low Latency Communication (URLLC).

[0030] eMBB aims to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to support a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. Furthermore, 5G communication systems must simultaneously provide the peak data rate and an increased user-perceived data rate for terminals. To meet these requirements, improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology, are required. Furthermore, while LTE transmits signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by using a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz band.

[0031] At the same time, massive Machine Type Communications (mMTC) is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC requires supporting a large number of terminals within a cell, improving terminal coverage, extending battery life, and reducing terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km^2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, terminals supporting mMTC are likely to be located in shadow areas, such as basements, beyond cell coverage due to the nature of the service, and thus may require broader coverage compared to other services provided by 5G communication systems. Terminals supporting mMTC must be inexpensive, and since frequent battery replacement is unlikely, they may require extremely long battery lifespans, such as 10 to 15 years.

[0032] Finally, URLLC refers to a cellular-based wireless communication service used for a specific purpose (mission-critical). Examples include remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts. Therefore, URLLC communications must provide extremely low latency and high reliability. For example, services supporting URLLC must meet air interface latency requirements of less than 0.5 milliseconds and a packet error rate (PER) of less than 10^-5. Therefore, for services supporting URLLC, 5G systems must provide a shorter transmission time interval (TTI) than other services, and design requirements may require the allocation of extensive resources in the frequency band to ensure communication link reliability.

[0033] The three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters can be used. Of course, 5G is not limited to the three services described above.

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

[0035] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a Node B, a BS (Base Station), an eNB (eNode B), a gNB (gNode B), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel form to the embodiments of the present disclosure described below. In addition, the embodiments of the present disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person having skilled technical knowledge.

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

[0037] In the following description, terms used to identify connection nodes, terms referring to network entities (NEs) or network functions (NFs), terms referring to messages, terms referring to interfaces between network objects, terms referring to various identification information, etc. are examples provided for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0038] For convenience of explanation, some terms and names defined in the 3rd generation partnership project long-term evolution (3GPP) standards may be used. However, the present disclosure is not limited to these terms and names, and can be equally applied to systems conforming to other standards.

[0039] FIG. 1 illustrates the architecture of a wireless communication system according to various embodiments of the present disclosure. More specifically, FIG. 1 illustrates an example of the configuration of a 5G system. Referring to FIG. 1, a 5G network may include at least one of the following network entities (NEs) or network functions (NFs).

[0040] According to one embodiment, the (R)AN ((Radio) Access Network) is an entity that performs radio resource allocation of a terminal, and may include at least one of an eNode B, a Node B, a BS (Base Station), an NG-RAN (Next Generation Radio Access Network), a 5G-AN (5G Access Network), a 5G NR (5G New Radio), a radio access unit, a base station controller, or a node on a network.

[0041] According to one embodiment, the terminal may include a User Equipment (UE), a Next Generation UE (NG UE), a Mobile Station (MS), a cellular phone, a smartphone, a computer, an Internet of Things (IoT) device, or a multimedia system capable of performing a communication function.

[0042] Furthermore, while the embodiments of the present disclosure are described below using a 5G system as an example, the embodiments of the present disclosure can also be applied to other communication systems with similar technical backgrounds. Furthermore, the embodiments of the present disclosure can be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.

[0043] As wireless communication systems evolve from 4G to 5G, a new core network (CN) called the Next Generation Core (NG Core) or 5GC (5G Core Network) is defined. This new core network can virtualize all existing network entities (NEs) into network functions (NFs). According to one embodiment of the present disclosure, a network function may refer to a network entity, a network component, or a network resource.

[0044] According to one embodiment of the present disclosure, 5GC may include one or more NFs illustrated in FIG. 1. Of course, the present invention is not limited to the example illustrated in FIG. 1, and 5GC may include more or fewer NFs than the NFs illustrated in FIG. 1.

[0045] In one embodiment, the Access and Mobility Management Function (AMF) may be a network function that manages access and mobility of a terminal (UE). For example, the AMF may perform network functions such as terminal registration, connection, reachability, mobility management, access verification, authentication, and mobility event generation.

[0046] In one embodiment, a Session Management Function (SMF) may be a network function that manages a Packet Data Network (PDN) connection provided to a User Equipment (UE). The PDN connection may be referred to as a Protocol Data Unit (PDU) Session. For example, the SMF may perform network functions such as session management through establishing, modifying, and releasing sessions and maintaining tunnels between a User Plane Function (UPF) and the RAN, selecting and controlling a User Plane (UPF), controlling traffic processing in the UPF, and controlling the collection of charging data.

[0047] In one embodiment, the Policy Control Function (PCF) may be a network function that applies a mobile communication operator's service policy, charging policy, and policy for PDU Session to a terminal.

[0048] In one embodiment, Unified Data Management (UDM) may be a network function that stores subscriber information. For example, UDM may perform functions such as generating authentication information for 3GPP security, processing user identifiers (User IDs), managing a list of network functions supporting UEs, and managing subscription information.

[0049] In one embodiment, the Network Exposure Function (NEF) may provide information about a terminal to a server outside the 5G network. Furthermore, NEF may provide the ability to provide information necessary for 5G network services and store it in the Unified Data Repository (UDR).

[0050] In one embodiment, the User Plane Function (UPF) may be a gateway function that transmits user data (e.g., PDU) to the Data Network (DN). More specifically, the UPF may perform a data processing function so that data transmitted by a terminal can be transmitted to an external network or data received from an external network can be transmitted to the terminal. For example, the UPF may perform network functions such as serving as an anchor between Radio Access Technologies (RATs), packet routing and forwarding, packet inspection, user plane policy application, traffic usage report generation, and buffering.

[0051] In one embodiment, the Network Repository Function (NRF) may store profiles of NFs and perform discovery of NFs.

[0052] In one embodiment, the Authentication Server Function (AUSF) can perform terminal authentication in a 3GPP access network and a non-3GPP access network.

[0053] According to one embodiment, the Network Slice Selection Function (NSSF) may perform a function of selecting a Network Slice Instance provided to a terminal.

[0054] In one embodiment, the Network Data Analytics Function (NWDAF) may collect data from multiple NFs (NFs) for the purpose of efficiently operating the 5GC network. In one embodiment, the collected data may be analyzed using a machine learning (ML) model, and the analyzed results may be provided back to the NFs to help each NF provide efficient network services.

[0055] In one embodiment, an Application Function (AF) can communicate with a network operator so that an external server (Application Server) can utilize network services provided by the network operator. Depending on the deployment entity, an AF can be classified as an internal AF or an external AF. An internal AF deployed by a network operator can communicate directly with network function providers (NFs) within the network operator. An AF deployed by a third-party service provider (3rd-party service provider) may need to go through an NEF to communicate with NFs within the network operator.

[0056] In one embodiment, the DN (Data Network) may be a data network through which a terminal transmits and receives data in order to use a network operator's service or a third-party service.

[0057] In one embodiment, the Network Slice Admission Control Function (NSACF) may limit the number of PDU sessions of registered terminals in each slice, thereby performing a resource management function.

[0058] In one embodiment, the Network Slice-Specific Authentication and Authorization Function (NSSAAF) may create a slice authentication context for a terminal and perform slice-specific authentication and authorization procedures.

[0059] In one embodiment, the Edge Application Server Discovery Function (EASDF) may create a domain name system (DNS) context for a PDU session and may perform functions such as storing a UE IP (internet protocol) address, DNS message processing rules, etc. in the context.

[0060] In one embodiment, a Service Communication Proxy (SCP) may perform indirect communication functions such as service discovery, call response, etc.

[0061] In one embodiment, the terminal may include an IoT device. The IoT device may include a device that does not use battery power or operates with very little power, and such an IoT device may be referred to as an ambient IoT device (or Ambient IoT).

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

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

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

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

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

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

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

[0069] Additionally, in 3GPP systems, the 5G system architecture may include service-based interfaces such as the following examples.

[0070] - Nnssf: Service-based interface by NSSF

[0071] - Nnssaaf: Service-based interface by NSSAAF (Network Slice-Specific Authentication and Authorization Function)

[0072] - Nnef: Service-based interface by NEF

[0073] - Nausf: Service-based interface by AUSF

[0074] - Nnrf: Service-based interface by NRF

[0075] - Namf: Service-based interface by AMF

[0076] - Npcf: Service-based interface by PCF

[0077] - Nsmf: Service-based interface by SMF

[0078] - Nupf: Service-based interface by UPF

[0079] - Nudm: Service-based interface by UDM

[0080] - Naf: Service-based interface by AF

[0081] - Nasaf: Service-based interface by AUSF

[0082] - Neasdf: Service-based interface by EASDF (Edge Application Server Discovery Function)

[0083] - Nnwdaf: Service-based interface by NWDAF

[0084] According to various embodiments of the present disclosure, mobile communication service providers have proposed a method for enabling various users' devices to utilize network services using the user's terminal. This service allows devices that cannot use mobile networks to connect to the terminal using various wireless technologies (e.g., Bluetooth, Wi-Fi, etc.) and utilize the terminal's mobile communication service to utilize the network services.

[0085] This disclosure proposes a method for providing network services to various devices using the aforementioned terminal. In particular, it proposes a method for distinguishing the traffic generated by each device and charging for it on a per-device basis.

[0086] FIG. 2 illustrates a scenario in which various devices using a terminal according to an embodiment of the present disclosure use a network service.

[0087] A terminal (210) subscribed to a mobile communications service provider can register with the network (5GC) (230) and create a PDU session to use network services. Furthermore, the network (230) can store subscriber information (subscription data) (240) to provide subscriber authentication and customized services.

[0088] However, devices (221, 223) that cannot subscribe to a mobile communication service provider cannot subscribe to a network service provider and use the network service. These devices (221, 223) can use the network service of the network service provider by connecting to the terminal (220) using the user's various wireless communication technologies (e.g., Bluetooth, Wi-Fi, etc.) and then using the network service provided by the terminal (220).

[0089] In the method of utilizing the network of a network operator using the existing terminal (220) described above, the network operator cannot distinguish between devices (221, 223) that connect to the terminal (220) and use the network service, and thus cannot provide QoS appropriate for each device. In addition, from the network operator's perspective, when devices (221, 223) that use the terminal (220) other than the subscribed terminal (220) use the network, they cannot distinguish between them and charge each device.

[0090] In order to solve the above-described problem, the present invention uses a terminal (220) to distinguish each device (221, 223) using a network service on the network and to store information (Device Profile) (251, 253) about each device (221, 223) on the network to provide a network service suitable for each device. In addition, the present invention proposes a method for distinguishing data transmitted and received by each device (221, 223) and charging each device separately.

[0091] Figure 3 illustrates a scenario in which each device using a terminal uses a network service.

[0092] The present invention proposes a method of allocating individual PDU sessions to each device (311, 313) in order to distinguish the traffic transmitted and received by each device (311, 313) in the network (5GC) (330). A terminal (320) subscribed to a mobile communication service provider can use network services in the network (330). In order to provide subscriber authentication and customized services, the network (330) can store subscriber information (subscription data) (340).

[0093] When each device (311, 313) is connected to a terminal (320) and requests data communication with a data network (330) through the terminal (320), the terminal (320) can establish a new PDU session for each device (311, 313). In addition, when creating the corresponding PDU session, the network (330) can set QoS values ​​of the PDU session based on device profile information (351, 353) including information of each device (311, 313).

[0094] The present disclosure may provide a method for a 5GC to identify a non-3GPP device connected to a UE or a 5G-RG (Residential Gateway) and a method for policy control over traffic related to individual non-3GPP devices. To provide the method, the present disclosure proposes 1) establishment of non-3GPP device-specific PDU sessions, 2) authentication / authorization during PDU session establishment, and 3) applying QoS parameters based on a device profile.

[0095] There may be multiple connections between at least one non-3GPP device and the UE (or 5G-RG), and a single NAS (Non Access Stratum) connection may be established between the UE (or 5G-RG) and the 5GC. The 5GC may apply at least one of separate charging, different QoS support, and restrict the number of simultaneously active devices to at least one non-3GPP device.

[0096] FIG. 4 illustrates a procedure in which devices connected to a terminal according to an embodiment of the present disclosure use a network service by utilizing the terminal's network operator.

[0097] Referring to FIG. 4, the communication system may include a Non-3GPP device, a terminal (UE), AMF, SMF, UPF, PCF / AUSF, UDM / UDR, NEF, and AF.

[0098] In step 401, the Non-3GPP device connected to the terminal is connected to the Data Network (DN) rd In order to transmit or receive data to or from a Party Service Provider (PSP), an IP CONNECTIVITY REQUEST message can be transmitted to the terminal. The IP CONNECTIVITY REQUEST message can include at least one of a Device Identifier of a Non-3GPP device, a Credential that can authenticate the device on the network, and additionally, Secondary Authentication information for authenticating the device on the DN to which the device wishes to connect.

[0099] The Device Identifier of a non-3GPP device can be used to identify a device that uses a network service by using a terminal in the network. The Device Identifier is a network, 3 rd It can be stored in the Party Service Provider. Additionally, each non-3GPP device can adopt the NAI (Network Access Identifier) ​​format to be assigned a globally unique ID. For example, a device manufacturer can assign an ID to a non-3GPP device using the operator's domain and a unique device ID within each operator.

[0100] In step 402, a terminal that receives an IP CONNECTIVITY request from a non-3GPP device may transmit a request message (PDU Session Establishment Request) to the network for creating a new PDU session for the non-3GPP device if there is no previously created PDU session for the non-3GPP device. The request message (PDU Session Establishment Request) may include information received from the non-3GPP device (at least one of a Device Identifier, Credentials for authentication of the non-3GPP device, and optionally, secondary authentication information). The request message (PDU Session Establishment Request) may set the value of "Request Type" to "Initial Request for non-3GPP device" to inform the network that the purpose of creating the PDU session is for the non-3GPP device connected to the terminal.

[0101] In step 403, AMF can perform authentication for non-3GPP devices requesting network services. When a terminal registers with the network, AMF can receive all device profile information of devices associated with the terminal from the UDM / UDR.

[0102] According to one embodiment, the Device Profile information may include at least one of the following information:

[0103] Device Identifier

[0104] Identifier Information of UE / 5G-RG (e.g., Subscription Permanent Identifier (SUPI) or Generic Public Subscription Identifier (GPSI))

[0105] Credential for authentication of non-3GPP devices

[0106] QoS Information

[0107] Device Information (e.g., hardware (H / W) and software (S / W) specifications)

[0108] Secondary authentication information

[0109] In one embodiment, the AMF may perform authentication on a device by comparing the device's Credential information included in the PDU Session Establishment Request with the Credential value included in the device's Device Profile information.

[0110] Additionally, the network can limit the number of devices connected to a terminal and using network services. Specifically, the terminal subscriber information can contain information on the number of devices that can connect to the terminal and use network services simultaneously. If the number of devices requesting network services from the terminal exceeds the number of concurrent users, the network may reject the creation of a PDU session.

[0111] In step 404, the AMF may send a PDUSession_CreateSMContext Request message to the SMF. The PDUSession_CreateSMContext Request message may include at least some of the data that the terminal sent to the AMF.

[0112] In step 405, the SMF may request UE subscription information data and device profile information from the UDM / UDR. To request device profile information, the SMF may include a device identifier (Device Identifier) ​​in the message in addition to the terminal ID (e.g., SUPI).

[0113] If the Non-3GPP device sent a message including Secondary Authentication Information to the terminal in step 401, AF(3) is sent in step 406. rd Device authentication procedures may be performed by a Party Service Provider (PSP). Device authentication procedures may occur when a Non-3GPP device attempts to use a specific DN, or when a 3GPP device attempts to use a specific DN. rd This may occur when a Party Service Provider attempts to update the Device Profile information stored on the network.

[0114] Secondary Authentication Information may include at least one of the Fully Qualified Domain Name (FQDN) / IP address information of the authentication server for authentication and the terminal authentication information.

[0115] In step 407, if AF wants to update the device profile information of the device, AF can update the device profile information by sending the updated device profile information to UDM / UDR via NEF.

[0116] If the Device Profile information has been updated by AF, the UDM / UDR can transmit the updated Device Profile information to the SMF in step 408.

[0117] In step 409, the SMF may select a PCF. In step 410, the SMF may transmit QoS information to the PCF based on device profile information to provide appropriate QoS for each non-3GPP device. Upon receiving the QoS information from the SMF, the PCF may transmit policy information appropriate for the non-3GPP device to the SMF based on the QoS information. In step 411, the SMF may select a UPF.

[0118] In step 412, the SMF can configure the selected UPF and N4 Session. The SMF can send the Packet Detection Rule (PDR), QoS Enforcement Rule (QER), and Usage Reporting Rule (URR) to the UPF with N4 Context information. The network can add a device identifier (ID) to each rule for device-specific QoS application and charging. That is, when a non-3GPP device uses multiple PDU sessions, the network can perform device-specific charging by recording the amount of data transmitted using each PDU session by device identifier (Device Identifier).

[0119] Figure 5 illustrates the configuration of a terminal according to embodiments of the present disclosure.

[0120] A terminal according to one embodiment of the present disclosure may include a processor (520) that controls the overall operation of the terminal, a transceiver (500) including a transmitter and a receiver, and a memory (510). Of course, the terminal is not limited to the above-described examples, and the terminal may include more or fewer components than those illustrated in FIG. 5.

[0121] According to one embodiment of the present disclosure, the transceiver (500) can transmit and receive signals with network entities or other terminals. The signals transmitted and received with the network entities may include control information and data. In addition, the transceiver (500) can receive signals via a wireless channel, output them to the processor (520), and transmit the signals output from the processor (520) via the wireless channel.

[0122] According to one embodiment of the present disclosure, the processor (520) can control the terminal to perform any one of the operations described above. Meanwhile, the processor (520), the memory (510), and the transceiver (500) do not necessarily have to be implemented as separate modules, and of course, they can be implemented as a single component in the form of a single chip. In addition, the processor (520) and the transceiver (500) can be electrically connected. In addition, the processor (520) can include an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, a controller, or at least one processor.

[0123] According to one embodiment of the present disclosure, the memory (510) can store data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the memory (510) can provide the stored data upon request of the processor (520). The memory (510) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (510). In addition, the processor (520) can perform the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (510).

[0124] FIG. 6 illustrates a configuration of a base station or network entity according to embodiments of the present disclosure.

[0125] A network entity according to one embodiment of the present disclosure may include a processor (620) that controls the overall operation of the network entity, a transceiver (600) including a transmitter and a receiver, and a memory (610). Of course, the present invention is not limited to the above-described examples, and the network entity may include more or fewer components than those illustrated in FIG. 6.

[0126] According to one embodiment of the present disclosure, the transceiver (600) can transmit and receive signals with at least one of other network entities or terminals. The signals transmitted and received with at least one of the other network entities or terminals may include control information and data.

[0127] According to one embodiment of the present disclosure, the processor (620) can control a network entity to perform any one of the operations described above. Meanwhile, the processor (620), the memory (610), and the transceiver (600) do not necessarily have to be implemented as separate modules, and can of course be implemented as a single component in the form of a single chip. In addition, the processor (620) and the transceiver (600) can be electrically connected. In addition, the processor (620) can include an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, a controller, or at least one processor.

[0128] According to one embodiment of the present disclosure, the memory (610) can store data such as basic programs, application programs, and setting information for the operation of a network entity. In particular, the memory (610) provides the stored data upon request of the processor (620). The memory (610) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (610). In addition, the processor (620) can perform the above-described embodiments based on a program for performing the above-described embodiments of the present disclosure stored in the memory (610).

[0129] It should be noted that the aforementioned configuration diagrams, examples of control / data signal transmission methods, examples of operational procedures, and configuration diagrams are not intended to limit the scope of the present disclosure. That is, not all components, entities, or operational steps described in the embodiments of the present disclosure should be construed as essential components for implementing the disclosure, and implementations may be made without detracting from the essence of the disclosure even if only some components are included. Furthermore, each embodiment may be combined and operated as needed. For example, parts of the methods proposed in the present disclosure may be combined to operate network entities and terminals.

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

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

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

[0133] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

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

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

[0136] While the detailed description of the present disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the claims described below but also by equivalents thereof. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the above-described embodiments can be combined and operated with each other as needed. For example, parts of the methods proposed in the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above-described embodiments have been presented based on a 5G, NR system, other modifications based on the technical idea of ​​the above-described embodiments can be implemented with other systems such as LTE, LTE-A, and LTE-A-Pro systems.

Claims

1. In a method of operating a UE (user equipment) in a wireless communication system, A step of receiving an IP connectivity request message including a device identifier (DID) of a Non-3GPP (3rd generation partnership project) device connected to the UE and a credential that can authenticate the Non-3GPP device in a network from the Non-3GPP device; and A method characterized by comprising a step of transmitting a PDU session establishment request message requesting creation of a PDU (protocol data unit) session for the above Non-3GPP device to an AMF (access and mobility management function).

2. In paragraph 1, the IP connection request message, A method characterized in that the Non-3GPP device further includes secondary authentication information for authenticating the Non-3GPP device in a DN (data network) to which the Non-3GPP device additionally wishes to connect.

3. In the second paragraph, the PDU session establishment request message, A method characterized in that it includes at least one of the device ID of the Non-3GPP device, the credential capable of authenticating the Non-3GPP device in the network, and the secondary authentication information for authenticating the Non-3GPP device.

4. In paragraph 3, A method characterized in that a request type included in the PDU session establishment request message is set to an initial request for the Non-3GPP device to indicate that the purpose of creating the PDU session is for the Non-3GPP device connected to the UE.

5. In paragraph 1, A method characterized in that the QoS (quality of service) value of the PDU session for the Non-3GPP device is set based on device profile information of the Non-3GPP device.

6. In a wireless communication system, a method for operating an AMF (access and mobility management function) A step of receiving, from the UE, a PDU session establishment request message including a device identifier (DID) of a Non-3GPP (3rd generation partnership project) device connected to the UE (user equipment) and credentials capable of authenticating the Non-3GPP device in a network, and requesting the creation of a PDU (protocol data unit) session for the Non-3GPP device; and A method characterized by comprising a step of performing authentication for the Non-3GPP device based on the device ID of the Non-3GPP device and the credentials capable of authenticating the Non-3GPP device.

7. In paragraph 6, the PDU session establishment request message, A method characterized in that the Non-3GPP device further includes secondary authentication information for authenticating the Non-3GPP device in a DN (data network) to which the Non-3GPP device additionally wishes to connect.

8. In paragraph 7, A method characterized in that a request type included in the PDU session establishment request message is set to an initial request for the Non-3GPP device to indicate that the purpose of creating the PDU session is for the Non-3GPP device connected to the UE.

9. In paragraph 6, A method characterized in that the QoS (quality of service) value of the PDU session for the Non-3GPP device is set based on device profile information of the Non-3GPP device.

10. In a wireless communication system, in UE (user equipment), At least one transceiver; At least one processor communicatively connected to said at least one transceiver; and At least one memory communicatively connected to at least one processor, The memory stores instructions that the at least one processor can execute alone or in combination, the instructions causing the UE to: Receive an IP connectivity request message including a device identifier (Device Identifier) ​​of a Non-3GPP (3rd generation partnership project) device connected to the UE and a credential that can authenticate the Non-3GPP device in a network from the Non-3GPP device, A UE characterized in that it transmits a PDU session establishment request message requesting the creation of a PDU (protocol data unit) session for the above Non-3GPP device to an AMF (access and mobility management function).

11. In paragraph 10, the IP connection request message, A UE characterized in that the Non-3GPP device further includes secondary authentication information for authenticating the Non-3GPP device in a DN (data network) to which the Non-3GPP device additionally wishes to connect.

12. In paragraph 11, the PDU session establishment request message, A UE characterized in that it includes at least one of the device ID of the Non-3GPP device, the credential capable of authenticating the Non-3GPP device in the network, and the secondary authentication information for authenticating the Non-3GPP device.

13. In paragraph 12, A UE characterized in that a request type included in the PDU session establishment request message is set to an initial request for the Non-3GPP device to indicate that the purpose of creating the PDU session is for the Non-3GPP device connected to the UE.

14. In paragraph 10, A UE characterized in that the QoS (quality of service) value of the PDU session for the Non-3GPP device is set based on device profile information of the Non-3GPP device.

15. In the AMF (access and mobility management function) of a wireless communication system, At least one transceiver; At least one processor communicatively connected to said at least one transceiver; and At least one memory communicatively connected to at least one processor, The memory stores instructions that the at least one processor can execute alone or in combination, the instructions being: A device identifier (DID) of a Non-3GPP (3rd generation partnership project) device connected to a UE (user equipment) and a credential capable of authenticating the Non-3GPP device in a network are included, and a PDU session establishment request message is received from the UE, requesting the creation of a PDU (protocol data unit) session for the Non-3GPP device, AMF characterized in that authentication for the Non-3GPP device is performed based on the device ID of the Non-3GPP device and the credentials capable of authenticating the Non-3GPP device.

Images