Method and apparatus for retrieving and selecting a server for terminal authentication and subscription data transfer
Patent Information
- Application Number
- CN202180036730.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-05-21
- Filing Date
- 2021-05-20
- Publication Date
- 2026-11-03
- Estimated Expiration
- 2041-05-20
AI Technical Summary
In non-public networks, existing technologies struggle to effectively detect and select servers used for user device authentication and subscription data transmission.
By receiving the address information from the network access identifier, a default credential server is selected, and a provisioning server is selected using it. The UE authentication process is performed, and session management functions and user plane functions are selected to achieve authentication and subscription data transmission.
It enables the efficient selection and authentication of servers in wireless communication systems, ensuring the transmission of user equipment subscription data.
Smart Images

Figure CN115669084B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to a communication system, and more specifically, to a method for detecting and selecting a server for user equipment (UE) authentication and subscription data transmission so that the UE can receive subscription data in a non-public network (NPN). Background Technology
[0002] To meet the increased demand for wireless data traffic since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems".
[0003] 5G communication systems are considered to be implemented in higher frequency (millimeter wave (mmWave) bands, such as the 60 GHz band), to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO (multi-input multi-output), full dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed for 5G communication systems.
[0004] In addition, in 5G communication systems, development is underway to improve system networks based on advanced small cells, radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multi-point (CoMP), and receiver interference cancellation.
[0005] In 5G systems, hybrid FSK (Frequency-shift keying) and QAM (Quadrature Amplitude Modulation) modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding modulation (ACM), as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.
[0006] Compared to traditional 4G systems, 5G systems aim to support a wider range of services. Key services may include enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), massive machine-type communication (mMTC), evolved multimedia broadcast / multicast service (eMBMS), and so on. Systems supporting URLLC and eMBB services can be referred to as URLLC systems and eMBB systems, respectively. The terms "service" and "system" are used interchangeably.
[0007] Unlike traditional 4G systems, URLLC service is a new service being considered in 5G systems, and it requires extremely high reliability compared to other services (e.g., approximately 10). -5 The packet error rate and low latency (e.g., approximately 0.5 milliseconds) are required. To meet these stringent requirements, URLLC services may need shorter Transmission Time Intervals (TTIs) than eMBB services, and various operating schemes using short TTIs should be considered.
[0008] The Internet, a human-centric network for generating and consuming information, is now evolving into the Internet of Things (IoT). In the IoT, distributed entities, such as things, exchange and process information without human intervention. Through connection to cloud servers, the Internet of Everything (IoE), combining IoT technology with big data processing technology, has emerged. Because IoT implementations require technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology, sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) have recently been studied.
[0009] This IoT environment can provide intelligent internet technology services that create new value for human life by collecting and analyzing data generated between connected things. IoT can be applied to various fields through the integration and combination of existing information technology (IT) and various industrial applications, including smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.
[0010] With this in mind, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-type communication (MTC), and machine-to-machine (M2M) communication can be implemented using beamforming, MIMO, and array antennas. The application of cloud radio access networks (RAN), as a big data processing technology, can also be considered an example of the convergence between 5G and IoT technologies.
[0011] Thus, due to the development of mobile communication systems, various services are available. Therefore, there is a need for an efficient way to use non-public networks (NPNs) to provide various services in places such as factories, schools, and companies using their own networks. Summary of the Invention
[0012] Technical issues
[0013] This disclosure aims to provide a method and apparatus for detecting and selecting servers for user equipment (UE) authentication and subscription data transmission in a non-public network (NPN).
[0014] Technical solution
[0015] According to embodiments of this disclosure, a method for selecting a server in a first independent non-public network (SNPN) that a user equipment (UE) is logging into in a wireless communication system includes: receiving a network access identifier configured as a unique identifier of the UE from the UE; selecting a default credential server based on address information about a default credential server included in the network access identifier; and receiving address information about a provisioning server selected by the default credential server from the default credential server.
[0016] The method may also include selecting the session management function (SMF) and user plane function (UPF) corresponding to the provisioning server selected by the default credential server.
[0017] The method may also include sending an authentication request, including authentication information about the UE, to a default credential server, and receiving a response from the default credential server indicating successful authentication of the UE.
[0018] The method may also include receiving identification information about a second SNPN serving the UE from a default credential server.
[0019] According to an embodiment of this disclosure, a method for a UE to enable a first SNPN (Service Provider Network) to select a server in a wireless communication system includes: sending a network access identifier configured as a unique identifier for the UE to the first SNPN; and performing a UE authentication process using a provisioning server selected by a default credential server corresponding to address information included in the network access identifier.
[0020] The operation method may also include receiving information about a second SNPN serving the UE from the supply server.
[0021] According to an embodiment, an SMF and a UPF corresponding to the provisioning server selected by the default credential server can be selected.
[0022] According to embodiments of this disclosure, a SNPN for UE login and selection of a server in a wireless communication system includes: a transceiver; and a controller that controls receiving a network access identifier configured as a unique identifier of the UE from the UE, selecting a default credential server based on address information about a default credential server included in the network access identifier, and controlling receiving address information about a provisioning server selected by the default credential server from the default credential server.
[0023] According to embodiments of this disclosure, an operation method for a UE logging into a SNPN that selects a server in a wireless communication system includes a transceiver and a controller that controls the transmission of a network access identifier configured as a unique identifier for the UE to a first SNPN, and performs a UE authentication process using a provisioning server selected by a default credential server corresponding to address information included in the network access identifier.
[0024] Beneficial effects
[0025] The methods and apparatus according to embodiments of this disclosure can effectively select a server for user equipment (UE) authentication and subscription data transmission in a wireless communication system. Attached Figure Description
[0026] Figure 1 This is a diagram illustrating the structure of a fifth-generation (5G) network according to an embodiment of the present disclosure.
[0027] Figure 2 This is a diagram illustrating an entity for sending a user subscription to a user equipment (UE) according to an embodiment of this disclosure.
[0028] Figure 3a and Figure 3b This is a diagram illustrating the UE onboarding process for receiving user subscription data for a UE according to an embodiment of this disclosure.
[0029] Figure 4 This is a diagram illustrating the structure of a network entity or server according to an embodiment of this disclosure.
[0030] Figure 5 This is a diagram illustrating the structure of a UE according to an embodiment of the present disclosure. Detailed Implementation
[0031] Embodiments of this disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that in the drawings, the same reference numerals denote the same parts. Furthermore, detailed descriptions of well-known functions or structures of this disclosure will be avoided to prevent obscuring the subject matter.
[0032] In describing embodiments of this disclosure, descriptions of technical concepts well-known in the art to which this disclosure pertains and not directly related to this disclosure will be omitted. This is intended to make the subject matter of this disclosure clearer by omitting unnecessary descriptions.
[0033] For the same reason, some components are exaggerated, omitted, or shown schematically in the accompanying drawings. The drawn size of each component does not perfectly reflect its actual size. In each drawing, the same reference numerals are assigned to the same or corresponding parts.
[0034] The advantages and features of this disclosure, as well as methods of implementing them, will become apparent from the following detailed description of embodiments taken in conjunction with the accompanying drawings. However, this disclosure can be implemented in various ways and is not limited to the embodiments set forth herein. Rather, these embodiments are provided to make this disclosure complete and thorough, and to fully convey its scope to those skilled in the art, and this disclosure is defined only by the appended claims. Throughout the specification, the same reference numerals denote the same components.
[0035] It will be understood that each block of a flowchart and block diagram, as well as combinations of blocks in a flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be loaded onto a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, such that instructions executed via the processor of the computer or other programmable data processing apparatus create parts for implementing the functions specified in the flowchart block(s). These computer program instructions can also be stored in a computer-usable or computer-readable storage medium that can instruct the computer or other programmable data processing apparatus to operate in a particular manner, such that instructions stored in the computer-usable or computer-readable storage medium produce an article of art comprising instruction parts that implement the functions / actions specified in the flowchart and / or block(s). Computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operations to be performed on the computer or other programmable data processing apparatus, thereby producing a computer-implemented process, such that instructions executing on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart and / or block(s).
[0036] Furthermore, the block diagrams may illustrate sections of module, segment, or code comprising one or more executable instructions for performing a specific logical function(s). It should also be noted that, in several modifications, the functions of these blocks may be executed in different orders. For example, two consecutive blocks may be executed substantially simultaneously, or they may be executed in reverse order depending on their functions.
[0037] The term "unit" as used herein means, but is not limited to, software or hardware components that perform certain tasks, such as field-programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs). Units can advantageously be configured to reside on addressable memory media and to execute on one or more processors. Thus, by way of example, a unit can include components such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided in components and "units" can be combined into fewer components and "units," or further divided into additional components and "units." Furthermore, components and "units" can be implemented to execute on one or more central processing units (CPUs) in a device or secure multimedia card.
[0038] In embodiments of this disclosure, the base station (BS) that is the entity that allocates resources to the user equipment (UE) can be at least one of a node B, an evolved Node B (eNode B or eNB), a next-generation Node B (gNode B or gNB), a radio access unit, a base station controller (BSC), or a network node.
[0039] The terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. The embodiments of this disclosure described below are applicable to other communication systems with similar technical backgrounds or channel structures. Furthermore, as those skilled in the art will recognize, this disclosure can also be applied to other communication systems with modifications without significantly departing from its scope.
[0040] For ease of description, terms are given for identifying access nodes, for representing network entities or network functions (NFs), for representing messages, for representing interfaces between network entities, and for representing various types of identification information used in the following description. Therefore, this disclosure is not limited to the terms described below, and these terms may be replaced by other technically equivalent terms.
[0041] For ease of description, certain terms and names are defined in the 3GPP Long Term Evolution (LTE) and / or 3GPP New Radio (NR) standards. However, this disclosure is not limited to the terms and names mentioned above and can be applied equivalently to systems conforming to other standards.
[0042] Embodiments of this disclosure will now be described with reference to the accompanying drawings.
[0043] Figure 1 The structure of a 5G network according to an embodiment of this disclosure is shown. The network entities or network nodes included in the 5G network will be described below.
[0044] Reference Figure 1 The wireless communication system that forms a 5G network may include UE 100 and multiple network entities 101 to 125.
[0045] The (radio) access network ((R)AN) 101, which is the entity that allocates radio resources to UE 100, can be at least one of eNode B, gNode B, Node B, BS, Next Generation Radio Access Network (NG-RAN), 5G-AN, Radio Access Unit, BTS, or network node.
[0046] UE 100 may be at least one of a user equipment, a next-generation (NG) UE, an MS, a cellular phone, a smartphone, or a computer. Furthermore, UE 100 may include a multimedia system capable of performing communication functions.
[0047] While embodiments of this disclosure have been described by way of example in the context of a 5G system, the embodiments of this disclosure can be applied to other communication systems with similar technical backgrounds. Furthermore, as those skilled in the art will recognize, this disclosure can also be applied to other communication systems with modifications, without significantly departing from the scope of this disclosure.
[0048] As wireless communication systems evolve from 4G to 5G, a new core network, the Next Generation Core (NGcore) or 5G Core Network (5GC), has been defined. The new core network virtualizes all existing network entities (NEs) into network functions (NFs). According to embodiments of this disclosure, NF can refer to network entities, network components, and network resources.
[0049] According to embodiments of this disclosure, 5GC may include Figure 1 The NF shown is clearly shown. It is evident that 5GC can include more than... Figure 1The NF shown is more or less than NF, not limited to Figure 1 Examples.
[0050] According to embodiments of this disclosure, the access and mobility management function (AMF) 109 may be an NF that manages the mobility of the UE.
[0051] According to embodiments of this disclosure, the session management function (SMF) 111 may be an NF that manages packet data network (PDN) connections provided to the UE. A PDN connection may be referred to as a protocol data unit (PDU) session.
[0052] According to embodiments of this disclosure, the policy control function (PCF) 121 may be an application of service policies, charging policies, and policies for PDU sessions of mobile communication operators to the NF of the UE.
[0053] According to embodiments of this disclosure, unified data management (UDM) 123 may be an NF that stores information about subscribers.
[0054] According to embodiments of this disclosure, an application function (AF) can be an application function operated by a UE manufacturer, service provider, or public terrestrial mobile network (PLMN) operator. However, even if an AF is not an application function operated by a UE manufacturer, it may still mean another application function that manages the UE's radio capabilities and radio capability identifiers (IDs).
[0055] According to embodiments of this disclosure, when delivering 5G core services, the service communication proxy (SCP) 113 can act as a proxy server to relay communications with the appropriate NF to the NF.
[0056] According to embodiments of this disclosure, the network exposure function (NEF) 117 can be a function that provides information about the UE to a server outside the 5G network. Furthermore, NEF 117 can provide the information required to provide services to the 5G network and store that information in a unified data repository (UDR).
[0057] According to embodiments of this disclosure, the user plane function (UPF) 103 may function as a gateway for sending user data (PDUs) to the data network (DN) 105.
[0058] According to embodiments of this disclosure, the network repository function (NRF) 119 can perform the function of discovering NFs.
[0059] According to embodiments of this disclosure, the authentication server function (AUSF) 107 can perform UE authentication in both 3GPP access networks and non-3GPP access networks.
[0060] According to embodiments of this disclosure, the network slice selection function (NSSF) 115 can perform the function of selecting network slice instances provided to the UE.
[0061] According to embodiments of this disclosure, DN 105 may be a data network through which UE 100 sends and receives data in order to use network operator services or third-party services.
[0062] Figure 2 This is a diagram illustrating an entity for sending a user subscription to a UE according to an embodiment of this disclosure.
[0063] Reference Figure 2 The wireless communication system used to send user subscriptions to the UE may include the UE 200, an onboarding stand-alone non-public network (O-SNPN) 210, a default credential server (DCS) 220, a provisioning server (PS) 230, and an SNPN 240 for storing user subscription data.
[0064] First, assume that UE 200 does not have user subscription data and has default UE credentials assigned by DCS 220. Furthermore, DCS 220 can assign a unique UE ID to UE 200 to uniquely identify UE 200.
[0065] O-SNPN 210 can provide UE 200 with either a user plane (UP) based Internet Protocol (IP) connection (UE login) or a control plane (CP) based non-access stratum (NAS) connection (UE login), enabling UE 200 without user subscription data to download user subscription data. To determine whether to provide login service to UE 200, DCS 220 can receive UE authentication requests.
[0066] The DCS 220 can pre-configure and store the default UE credentials and unique UE ID for the UE 200. When performing UE registration for login, the DCS 220 can receive authentication requests for the UE 200 from the O-SNPN 210. The default UE credentials are used to authenticate the UE 200.
[0067] Furthermore, when PS 230 sends subscription data to UE 200, DCS 220 can receive authentication / authorization requests for UE 200 from PS 230 to determine whether the UE is authorized to receive subscription data. DCS 220 can be the manufacturer of UE 200 or a third party connected to the manufacturer or SNPN operator.
[0068] PS 230 can receive user subscription data such as network certificates and user configuration information from network operators and send the user subscription data to UE 200.
[0069] Both PS 230 and DCS 220 can exist as a single server. Like DCS 220, PS230 can be a server owned by a third party connected to the UE manufacturer or SNPN operator. PS230 can communicate with DCS 220 for UE200 authentication / authorization.
[0070] The SNPN 240, which carries user subscription data, can send the user subscription data to the UE 200 via the PS 230. In this case, the network operator may have UE ID information about the UE to which the user subscription data will be sent.
[0071] Figure 3a and Figure 3b A UE login process for receiving user subscription data for a UE according to an embodiment of this disclosure is illustrated.
[0072] refer to Figure 3aThe wireless communication system used to perform the UE login process may include UE 300, 5G-AN 310, 5GC320, PS 330, DCS 340 and service network 350.
[0073] The 5G-AN 310 performs radio resource allocation for the UE 300 and sends system information to the UE 300. Furthermore, the 5GC320 can be implemented as an SNPN, and the serving network 350 can be implemented as a network (NPN or PLMN) that stores user subscription data (network credentials and configuration information).
[0074] In step S301, UE 300 is pre-configured with default UE credentials and a unique UE ID assigned by DCS 340. Although default UE credentials are configured for UE 300, network credentials are not configured for UE 300. Network credentials can be provided to UE 300 as part of the login process.
[0075] According to an embodiment, when there is an agreement between the UE manufacturer and the SNPN, the UE 300 may have an initial default configuration (e.g., the SNPN's PLMN ID and NIF, S-NSSAI, DNN, etc.).
[0076] The UE ID assigned by DCS 340 should uniquely identify UE 300. The manufacturer of the UE, primarily an Internet of Things (IoT) device or a third party connected to some manufacturer, is highly likely to be responsible for DCS 340.
[0077] To assign a unique ID to a UE in the absence of a specific standards organization, the UE ID may include information about the DCS340. In order to assign a unique ID to the UE 300, this disclosure proposes using a UE ID in the form of a network access identifier (NAI) that includes information about the DCS 340.
[0078] The NAI is in the form of "user@realm", and information about the DCS 340 can be included in the realm, enabling the logging network to identify the server to be selected for authentication of the corresponding UE from among multiple DCSs. In particular, since the address of the DCS server can be included in the realm information, DCS discovery / addressing can be performed immediately.
[0079] In step S303, during initial access, UE 300 can detect and select the O-SNPN based on the received broadcast system information. The O-SNPN is not necessarily the same as the SNPN with network credentials.
[0080] During initial access, UE 300 can send its unique UE ID and default UE credentials to SNPN 320, since there is no subscription data for SNPN 320. UE 300 can also send additional information to SNPN 320, such as application ID or service provider ID.
[0081] In this disclosure, UE 300 may use a NAI that includes information about DCS 340 as its unique UEID. UE 300 may send the NAI that includes information about DCS 340 to SNPN 320.
[0082] In step S305, SNPN 320 can receive the unique UE ID of UE 300 in the form of NAI, and detect and select DCS 340 by using the domain information included in the NAI. In particular, since the domain information may include Uniform Resource Locator (URL) information about DCS 340, SNPN 320 can send a UE authentication message for UE authentication to DCS 340.
[0083] Furthermore, since the DCS 340 may have a contract with a specific SNPN for login services for its UEs, the SNPN 320 can determine whether to provide the UE with a connection for login by using the domain information included in the NAI.
[0084] In step S307, SNPN 320 can send the UE's unique UE ID and default UE credentials to DCS 340, which manages UE 300, thereby requesting authentication of UE 300 regarding whether UE 300 is allowed to access the network for login purposes. Authentication can be performed by selecting primary authentication or network slice specific authentication and authorization (NSSAA).
[0085] In step S309, DCS 340 can perform authentication on UE 300, and upon successful authentication, receive subscription data from SNPN 350 containing the subscription data to be received by UE 300, and select PS 330 to send the subscription data to UE 300. In this case, DCS 340 has a list of SNPNs that the UE manufacturer has signed up with and subscribed to. Considering the UE type and current location, it selects the most suitable network from the signed SNPNs and selects PS 330 that supports that network. Like the SNPNs, PS 300 capable of supporting the selected SNPN can be selected from the list of PSs signed up with the manufacturer. According to an embodiment, when multiple service networks are available, priority information may also be included.
[0086] In step S311, DCS 340 may send a response indicating successful UE authentication, address information about the selected PS 300, and the ID (PLMN ID or PLMN ID+NID) of the selected serving network 350 to the login network 320.
[0087] In step S313, the login network 320 should select SMF and UPF to create a PDU session, which will provide the UE 300 with a restricted data connection accessible only by the selected PS 330. For this purpose, the login network 320 uses the address of the selected PS received from the DCS 340.
[0088] refer to Figure 3b In step S315, the login network 320 can send the address of the selected PS and S-NSSAI / DNN information received from DCS340 for creating a PDU session to the UE 300. The UE 300 can create a PDU session using the received S-NSSAI / DNN information and send data to PS 330 using the address information about PS 330. When the PS-related information differs from the information stored during pre-configuration, the PS-related information can be updated in the UE.
[0089] In step S317, UE 300 can create a configuration PDU session. The PDU session is created using known or pre-configured S-NSSAI / DNN or S-NSSAI / DNN information received from DCS 340.
[0090] In steps S319 to S323, subscription data can be requested from PS 330 using information pre-configured at the application layer in UE 300, or using address information about the selected PS received from DCS 340. PS 330 can identify the domain portion of the unique UE ID information about the UE and request UE authentication by sending the default UE credentials of UE 300 to DSC 340. In this case, UE 300 can also send the serving network ID (PLMN ID or PLMN ID+NID) and serving network priority information received from DCS 340.
[0091] In step S325, PS 330 can request and receive other UE configuration parameters (e.g., PDU session parameters, such as SNSSAI, DNN, URSP, QoS rules and other parameters required to access SNPN and establish regular PDU sessions) and network credentials for future SNPN subscriptions from the serving network 350.
[0092] In step S327, PS 330 can send the data received from the serving network 350 in step S325 to UE 300.
[0093] When data is successfully received in step S327, in step S329, UE 300 can release the configuration PDU session of the login network 320 and perform deregistration to the login network 320.
[0094] In step S331, UE 300 can receive network services by registering with serving network 350 using the received subscription data. The login network 320 and the serving network 350 can be the same or different.
[0095] Figure 4 This is a diagram illustrating the structure of a network entity or server according to an embodiment of this disclosure.
[0096] refer to Figure 1 Each of the network entities or servers described in Figure 3 may include Figure 4 The configuration. For example, the structures of SMF, NEF, AF, etc., can correspond to the reference. Figure 4 The described structure. For example, structures such as PS and DCS can correspond to the reference. Figure 4 The structure described.
[0097] refer to Figure 4According to embodiments of the present disclosure, a network entity or server may include a transceiver 410, a memory 420, and a processor 430. The transceiver 410, processor 430, and memory 420 of the network entity or server can operate according to the above-described communication method.
[0098] However, the components of a network entity or server are not limited to the examples described above. For instance, a network entity or server may include more or fewer components than those described above. Furthermore, transceiver 410, processor 430, and memory 420 may be implemented as a single chip. Additionally, processor 430 may include one or more processors.
[0099] Transceiver 410 is a general term for both a receiver and a transmitter, and can transmit signals to and receive signals from a BS, UE, network entity, or server. Signals transmitted to and received from the BS, UE, network entity, or server may include control information and data. For this purpose, transceiver 410 may include a radio frequency (RF) transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies and down-converts the received signal with low noise. However, this is merely one embodiment of transceiver 410, and the components of transceiver 410 are not limited to RF transmitters and RF receivers.
[0100] Furthermore, transceiver 410 can receive signals on the radio channel and output the received signals to processor 430, and can also transmit signals output from processor 430 on the radio channel.
[0101] Memory 420 can store programs and data required for the operation of the network entity or server. Furthermore, memory 420 can store control information or data included in signals received by the network entity or server. Memory 420 can be configured as a storage medium or a combination of storage media, such as read-only memory (ROM), random access memory (RAM), hard disk, compact disk-ROM (CD-ROM), and digital versatile disk (DVD). Moreover, memory 420 can be included within processor 430, rather than residing separately.
[0102] Processor 430 can control a series of processes that enable a network entity or server to operate according to the embodiments of this disclosure described above. For example, processor 430 can receive and process control signals and data signals via transceiver 410. Furthermore, processor 430 can transmit processed control signals and data signals via transceiver 410. Multiple processors 430 may be present, and each processor 430 can execute programs stored in memory 420 to perform control operations on components of the network entity or server.
[0103] Figure 5 This is a diagram illustrating the structure of a UE according to an embodiment of the present disclosure.
[0104] Reference Figure 1 The UE described in Figure 3 can correspond to Figure 5 The UE. (Refer to...) Figure 5 The UE may include a transceiver 510, a memory 520, and a processor 530. According to the communication method described above, the transceiver 510, processor 530, and memory 520 of the UE can operate. For example, the UE may include more or fewer components than those described above. Furthermore, the transceiver 510, processor 530, and memory 520 may be implemented as a single chip. Additionally, the processor 530 may include one or more processors.
[0105] Transceiver 510 is a general term for a receiver and transmitter of a UE, and can transmit and receive signals to and from a BS, server, or other UE. Signals transmitted to and received from the BS, server, or other UE may include control information and data. For this purpose, transceiver 510 may include an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies and down-converts the received signal with low noise. However, this is merely one embodiment of transceiver 510, and the components of transceiver 510 are not limited to RF transmitters and RF receivers.
[0106] Furthermore, transceiver 510 can receive signals on the radio channel and output the received signals to processor 530, and can also transmit signals output from processor 530 on the radio channel.
[0107] The memory 520 can store programs and data required for the operation of the network entity or server. Furthermore, the memory 520 can store control information or data included in signals received by the UE. The memory 520 can be configured as a storage medium or a combination of storage media, such as ROM, RAM, hard disk, CD-ROM, and DVD. Moreover, the memory 520 can be included in the processor 530, rather than residing separately.
[0108] The processor 530 can control a series of processes that enable the UE to operate according to the embodiments of the present disclosure described above. For example, the processor 530 can receive and process control signals and data signals via the transceiver 510. Furthermore, the processor 530 can transmit the processed control signals and data signals via the transceiver 510. Multiple processors 530 may be present, and each processor 530 can execute programs stored in the memory 520 to perform control operations on the components of the UE.
[0109] The methods described in the claims or specification of this disclosure can be implemented in hardware, software, or a combination of hardware and software.
[0110] When these methods are implemented in software, a computer-readable storage medium storing at least one program (software module) can be provided. The at least one program stored in the computer-readable storage medium is configured to be executable by at least one processor in an electronic device. The at least one program includes instructions to cause the electronic device to perform the methods according to the claims or embodiments of this disclosure.
[0111] The program (software module or software) can be stored in RAM, non-volatile memory including flash memory, ROM, electrically erasable programmable ROM (EEPROM), disk storage devices, CD-ROMs, DVDs, any other type of optical storage device, or magnetic tape cartridges. Alternatively, the program can be stored in a memory configured as some or all of these. Furthermore, there can be multiple instances of each component memory.
[0112] Furthermore, the program can be stored in an attachable storage device accessible via a communication network such as the Internet, intranet, local area network (LAN), wide area network (WLAN), or storage area network (SAN), or a combination thereof. Such a storage device can be connected to a device implementing embodiments of this disclosure via an external port. Additionally, a separate storage device on the communication network can be connected to a device implementing embodiments of this disclosure.
[0113] In the specific embodiments of this disclosure described above, the elements included in this disclosure are represented in singular or plural form according to the specific embodiments. However, for ease of description, singular or plural expressions are appropriately chosen in the context, and this disclosure is not limited to singular or plural components. Even if a component is represented as plural, it can still be singular. Even if a component is represented as singular, it can still be plural in number.
[0114] The embodiments of this disclosure disclosed in the specification and accompanying drawings are presented merely as specific examples to readily explain the technical concepts of this disclosure and aid in understanding it, and are not intended to limit the scope of this disclosure. That is, it will be apparent to those skilled in the art that other modifications can be made based on the technical spirit of this disclosure. Furthermore, the above embodiments can be combined as needed. For example, the BS and UE can operate in combinations of portions of different embodiments of this disclosure. Moreover, the embodiments of this disclosure are applicable to other communication systems, and other modifications are also possible based on the technical spirit of the embodiments.
Claims
1. A method performed by a user equipment (UE) in a wireless communication system logging into an independent non-public network (SNPN), the method comprising: Receive the UE's unique identifier from the UE, wherein the UE's unique identifier is in the form of a network access identifier; The default credential server is selected based on information included in the field portion of the UE's unique identifier; and During the UE's authentication process, the address information of the provisioning server is received from the default credential server.
2. The method of claim 1 further includes selecting a Session Management Function (SMF) and a User Plane Function (UPF) corresponding to the provisioning server selected by the default credential server.
3. The method according to claim 1, further comprising: Send an authentication request, including authentication information about the UE, to the default credential server; as well as Receive a response from the default credential server indicating that the UE has successfully authenticated.
4. The method according to claim 1, wherein, The information included in the field portion of the UE's unique identifier corresponds to the address of the default credential server.
5. A method performed by a user equipment (UE) logging into an independent non-public network (SNPN) of a wireless communication system, the method comprising: Send the UE's unique identifier to the SNPN, wherein the UE's unique identifier is in the form of a network access identifier; and The UE authentication process is performed using the provisioning server selected by the default credential server. The default credential server is selected based on information included in the domain portion of the UE's unique identifier.
6. The method according to claim 5, wherein, The information included in the field portion of the UE's unique identifier corresponds to the address of the default credential server.
7. The method according to claim 5, wherein, If the UE authentication process is successful, the provisioning server is selected by the default credential server.
8. A standalone non-public network (SNPN) that a user equipment (UE) in a wireless communication system is logging into, the SNPN comprising: transceiver; as well as A controller, coupled to the transceiver and configured to control: Receive the UE's unique identifier from the UE, wherein the UE's unique identifier is in the form of a network access identifier. A default credential server is selected based on information included in the domain portion of the UE's unique identifier, and During the UE's authentication process, the address information of the provisioning server is received from the default credential server.
9. The SNPN according to claim 8, wherein, The controller selects the Session Management Function (SMF) and User Plane Function (UPF) corresponding to the provisioning server selected by the default credential server.
10. The SNPN according to claim 8, wherein, The controller controls the sending of an authentication request, including authentication information about the UE, to the default credential server, and controls the receiving of a response from the default credential server indicating successful authentication of the UE.
11. The SNPN according to claim 8, wherein, The information included in the field portion of the UE's unique identifier corresponds to the address of the default credential server.
12. A user equipment (UE) that logs into an independent non-public network (SNPN) of a wireless communication system, the UE comprising: transceiver; as well as A controller, coupled to the transceiver and configured to control: Send the UE's unique identifier to the SNPN, wherein the UE's unique identifier is in the form of a network access identifier, and The UE authentication process is performed using the provisioning server selected by the default credential server. The default credential server is selected based on information included in the domain portion of the UE's unique identifier.
13. The UE according to claim 12, wherein, The information included in the field portion of the UE's unique identifier corresponds to the address of the default credential server.
14. The UE according to claim 12, wherein, If the UE authentication process is successful, the provisioning server is selected by the default credential server.
