WO2021020834A1 - Method for accessing network by terminal - Google Patents

Abstract

A disclosure of the present specification provides a method for accessing a network by a terminal. The method may comprise the steps of: receiving information of at least one network slice from the network, the information comprising information regarding a restriction condition in which the terminal cannot access the at least one network slice or information regarding an allowance condition in which the terminal can access the at least one network slice; determining one network slice from among the at least one network slice, wherein, in the determination step, the information regarding the restriction condition or the information regarding the allowance condition is considered; and performing an access request to the determined one network slice.

Description

How the terminal accesses the network

The present invention relates to next-generation mobile communication.

With the success of LTE (long term evolution)/LTE-Advanced (LTE-A) for 4G mobile communication, interest in future mobile communication, that is, 5G mobile communication, is also increasing, and research is continuing.

It is expected that the next-generation mobile communication, that is, the 5th generation mobile communication, will realize a data service with a minimum speed of 1 Gbps. This high-speed service seems difficult to be accommodated by the core network designed for the existing LTE/LTE-A.

Therefore, in the so-called 5th generation mobile communication, redesign of the core network is urgently required.

1A is a diagram showing an expected structure of next-generation mobile communication from a node perspective It is an exemplary diagram .

As can be seen with reference to FIG. 1A, the UE may be connected to the core network through a next-generation radio access network (RAN). The next-generation core network may include a control plane (CP) function node and a user plane (UP) function node. The CP function node is a node that manages the UP function nodes and the RAN, and transmits and receives control signals. The CP function node performs all or part of the functions of the Mobility Management Entity (MME) of 4G mobile communication, and all or part of the control plane functions of the Serving Gateway (S-GW) and the PDN Gateway (P-GW). The UP function node is a kind of gateway through which user data is transmitted and received. The UP function node may perform all or part of the user plane functions of S-GW and P-GW of 4G mobile communication.

The illustrated policy control function (PCF) is a node that controls the operator's policy. In addition, the illustrated subscriber information server stores subscriber information of a user.

1B is a diagram showing an expected structure of next-generation mobile communication from a session management perspective It is an exemplary diagram .

As shown, the core network is divided into a control plane (CP) and a user plane (UP). In the control plane CP, there may be a policy control function (PCF) entity, a subscriber information server, and a CP node performing session management (SM). In addition, an UP function node may exist in the user plane UP. The nodes in the control plane CP are implemented through cloud virtualization. Similarly, nodes in the user plane (UP) are implemented through cloud virtualization.

The UE may request to create a session directed to the data network (DN) through the access network (AN). The session may be created and managed by a CP node for the session management (SM). In this case, the session management may be performed based on information stored in the subscriber information server and a policy of a service provider (eg, QoS management policy) stored in the policy control function (PCF) entity. That is, when the CP node for session management (SM) receives a request for session creation/modification/cancellation from the UE, it interacts with the subscriber information server and the policy control function (PCF), and the information And create/modify/release the session. In addition, the CP node for the session management (SM) selects an UP function node for the session and allocates resources of the core network. In addition, the CP node for the session management (SM) may directly allocate an IP address to the UE or may request the UP function node to allocate an IP address to the UE.

Next-generation mobile communication introduces the concept of network slicing in order to provide various services through a single network. Here, the slicing of the network is a combination of network nodes having a function required when providing a specific service.

In the 5G system, due to the network slicing technology, various services can be individually provided using a plurality of network slices.

Services provided by each network slice may be independent. Therefore, regions and users that can be accessed for each network slice may be different. That is, a specific network slice may not be available in a specific region or may not be used except for a specific user. However, a terminal in an inaccessible area or a terminal of an inaccessible user requests access to the network because the terminal itself cannot determine this even though the specific network slice cannot be used. After this, apart from the network notifying the terminal that the specific network slice cannot be accessed, there is a problem that radio resources are wasted due to the access request because the terminal has already performed an access request.

Disclosure of the present specification aims to solve the above-described problem.

In order to achieve the above object, one disclosure of the present specification proposes a method for a terminal to access a network. The method includes receiving information of at least one network slice from the network; Determining one network slice from among the at least one network slice; It may include performing an access request to the determined one network slice. In addition, the information may include information on a restriction condition in which the terminal cannot access to the at least one network slice or information on an allowance condition in which the terminal can access. In the determining step, the restriction condition information or the allowance condition information may be considered.

According to the disclosure of the present specification, the above-described problem is solved.

1A is an exemplary diagram showing an expected structure of next-generation mobile communication from a node perspective.

1B is an exemplary diagram showing an expected structure of next-generation mobile communication from a session management perspective.

2 is an exemplary diagram showing an example of an architecture for implementing the concept of network slicing.

3 is an exemplary diagram showing another example of an architecture for implementing the concept of network slicing.

4 is an exemplary diagram showing an architecture for implementing the concept of network slicing according to the first disclosure of the present specification.

5 is a flowchart according to the first embodiment of the present specification.

6 is a flowchart according to a second embodiment of the present specification.

7 is a flowchart according to a third embodiment of the present specification.

8 is a block diagram illustrating a configuration of a processor in which the disclosure of the present specification is implemented.

9 shows a wireless communication system according to an embodiment.

10 illustrates a block diagram of a network node according to an embodiment.

11 is a block diagram showing a configuration of a UE according to an embodiment.

12 is a block diagram showing in detail a transmission/reception unit of the first device shown in FIG. 9.

13 illustrates a communication system 1 applied to the disclosure of this specification.

It should be noted that the technical terms used in the present specification are only used to describe specific embodiments, and are not intended to limit the present invention. In addition, the technical terms used in the present specification should be interpreted as generally understood by those of ordinary skill in the technical field to which the present invention belongs, unless otherwise defined in the present specification, and excessively comprehensive It should not be construed as a human meaning or an excessively reduced meaning. In addition, when a technical term used in the present specification is an incorrect technical term that does not accurately express the spirit of the present invention, it will be replaced with a technical term that can be correctly understood by those skilled in the art to be understood. In addition, general terms used in the present invention should be interpreted as defined in the dictionary or according to the context before and after, and should not be interpreted as an excessively reduced meaning.

In addition, the singular expression used in the present specification includes a plurality of expressions unless the context clearly indicates otherwise. In the present application, terms such as constitute or have should not be construed as necessarily including all of the various components or steps described in the specification, and some components or some steps may not be included, and Or, it should be interpreted that it may further include additional components or steps.

In addition, terms including ordinal numbers such as first and second used herein may be used to describe various elements, but the elements should not be limited by the terms. These terms are only used for the purpose of distinguishing one component from another component. For example, without departing from the scope of the present invention, a first component may be referred to as a second component, and similarly, a second component may be referred to as a first component.

When a component is connected to or is said to be connected to another component, it may be directly connected or connected to the other component, but other components may exist in the middle. On the other hand, when a component is directly connected to or directly connected to another component, it should be understood that there is no other component in the middle.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings, but the same or similar components are assigned the same reference numerals regardless of the reference numerals, and redundant descriptions thereof will be omitted. In addition, in describing the present invention, when it is determined that a detailed description of a related known technology may obscure the subject matter of the present invention, a detailed description thereof will be omitted. In addition, it should be noted that the accompanying drawings are only intended to facilitate understanding of the spirit of the present invention, and should not be construed as limiting the spirit of the present invention by the accompanying drawings. The spirit of the present invention should be construed as extending to all changes, equivalents, or substitutes in addition to the accompanying drawings.

In the accompanying drawings, a UE (User Equipment) is illustrated as an example, but the illustrated UE may be referred to in terms of UE (100) (Terminal), ME (Mobile Equipment), and the like. In addition, the UE may be a portable device such as a notebook computer, a mobile phone, a PDA, a smart phone, or a multimedia device, or may be a non-portable device such as a PC or a vehicle-mounted device.

<Definition of terms>

Prior to the following description with reference to the drawings, in order to aid in understanding the present invention, terms used in the present specification will be briefly defined.

UE/MS: User Equipment/Mobile Station, refers to a UE (100) device.

EPS: stands for Evolved Packet System, and refers to a core network supporting a Long Term Evolution (LTE) network. Network in the form of UMTS evolution

PDN (Public Data Network): An independent network in which a server providing service is located

PDN-GW (Packet Data Network Gateway): Network node of the EPS network that performs the functions of UE IP address allocation, Packet screening & filtering, and Charging data collection.

Serving GW (Serving Gateway): Network node of EPS network that performs mobility anchor, packet routing, idle mode packet buffering, and triggering MME to page UE functions.

eNodeB: An EPS (Evolved Packet System) base station installed outdoors, and the cell coverage scale corresponds to a macro cell.

MME: stands for Mobility Management Entity, and serves to control each entity within the EPS to provide session and mobility for the UE.

Session: A session is a path for data transmission, and its unit may be a PDN, a bearer, an IP flow unit, etc. The difference between each unit can be classified into the entire target network unit (APN or PDN unit) as defined in 3GPP, the unit classified by QoS (Bearer unit) within the unit, and the destination IP address unit.

APN: An abbreviation for Access Point Name, which is provided to the UE as the name of an access point managed by the network. That is, it is a character string that refers to or identifies the PDN. In order to access the requested service or network (PDN), the P-GW goes through the corresponding P-GW, which is a predefined name (string) in the network so that this P-GW can be found. For example, the APN may be in the form of internet.mnc012.mcc345.gprs.

PDN connection: Indicates the connection from the UE to the PDN, that is, the association (connection) between the UE expressed by the ip address and the PDN expressed by the APN. This means a connection between entities in the core network (UE (100)-PDN GW) so that a session can be formed.

UE Context: context information of the UE used to manage the UE in the network, that is, context information consisting of UE id, mobility (current location, etc.), and session properties (QoS, priority, etc.)

NAS (Non-Access-Stratum): Upper stratum of the control plane between the UE and the MME. Supports mobility management, session management, and IP address maintenance between the UE and the network

PLMN: An abbreviation for Public Land Mobile Network, which means the operator's network identification number. In the roaming situation of the UE, PLMN is divided into Home PLMN (HPLMN) and Visited PLMN (VPLMN).

<Network Slice>

Hereinafter, slicing of a network to be introduced in next-generation mobile communication will be described.

Next-generation mobile communication introduces the concept of network slicing in order to provide various services through a single network. Here, the slicing of the network is a combination of network nodes having functions necessary to provide a specific service. The network nodes constituting the slice instance may be hardware independent nodes or logically independent nodes.

Each slice instance can be composed of a combination of all nodes necessary to configure the entire network. In this case, one slice instance can provide a service to the UE alone.

Alternatively, the slice instance may be composed of a combination of some of the nodes constituting the network. In this case, the slice instance may not provide a service to the UE alone, but may provide a service to the UE in connection with other existing network nodes. In addition, a plurality of slice instances may be linked to each other to provide a service to the UE.

A slice instance differs from a dedicated core network in that the entire network node including the core network (CN) node and the RAN can be separated. In addition, slice instances differ from dedicated core networks in that network nodes can be logically separated.

Figure 2 is a network Slicing It is an exemplary diagram showing an example of an architecture for implementing the concept.

As can be seen with reference to FIG. 2, the core network CN may be divided into several slice instances. Each slice instance may include one or more of a CP function node and a UP function node.

Each UE can use a network slice instance suitable for its service through an access network (AN).

Unlike shown in FIG. 2, each slice instance may share another slice instance and one or more of a CP function node and a UP function node. This will be described with reference to FIG. 3 as follows.

3 is a network Slicing Representing another example of an architecture for implementing the concept It is an exemplary diagram .

Referring to FIG. 3, a plurality of UP function nodes are clustered, and similarly, a plurality of CP function nodes are also clustered.

And, referring to FIG. 3, slice instance #1 (or instance #1) in the core network includes a first cluster of UP function nodes. In addition, the slice instance #1 shares the cluster of the CP function node with the slice #2 (or instance #2). The slice instance #2 includes a second cluster of UP function nodes.

The illustrated Core Network Selection Function (CNSF) selects a slice (or instance) capable of accommodating the service of the UE.

The illustrated UE can use service #1 through slice instance #1 selected by the CNSF, and can use service #2 through slice instance #2 selected by the CNSF.

In order to enable a UE to use multiple services simultaneously through multiple network slice instances by a single network operator, an architecture that allows a set (or cluster) of CP control nodes to be shared among multiple slice instances is presented. . This will be described with reference to FIG. 4 as follows.

Figure 4 shows the network Slicing Representing the architecture to implement the concept It is an exemplary diagram .

As can be seen with reference to FIG. 4, in order to use a service through a plurality of slice instances for each UE, a basic CP function node may be shared among slice instances.

Each slice instance may include a service specific CP function node and a UP function node, and a basic CP function node that can be shared with other slice instances.

A plurality of service specific CP function nodes may be gathered and grouped into one cluster (ie, set). Similarly, a plurality of UP function nodes may be grouped and grouped into one cluster (ie, a set).

Each slice instance can be used exclusively for UEs belonging to the same type.

The basic CP function node may allow the UE to enter the network by performing authentication and subscription verification. In addition, the basic CP function node can manage the mobility of the UE according to characteristics (eg, low mobility or high mobility).

The service specific CP function node manages the session.

Meanwhile, when the UE first accesses the operator's network, the basic CP function node is selected in the access network (AN). The selection may be performed by information of the UE (eg, the usage type of the UE).

When the UE performs the initial attach or after performing the attach, when there is a session request from the UE, the slice instance selection function within the core network is triggered to select a service-specific CP function node and an UP function node. I can. This selection may be performed based on subscriber information and information related to the session request from the UE (eg, the type of the requested service, information such as APN).

When the selection of the service-specific CP function node and the UP function node is set as default in the core network, the selection may be performed even if there is no session request from the UE. At this time, if there is a network slice instance set as default, it is assigned to the UE.

The UE may have a plurality of sessions through one slice instance or through a plurality of slice instances. When the UE requests a session, the node in charge of the slice selection function determines which slice instance can support the session requested by the UE. The determined slice instance is designated for the session.

Meanwhile, the UE may be connected to a plurality of slice instances through different basic CP function nodes.

On the other hand, the core network may decide to change the basic CP function node for the UE for various reasons (eg, network management problem, change of UE subscription information, change of UE location, etc.). To this end, the core network may request detach/re-attach from the UE. Accordingly, when the UE reconnects to the network, the access network may select another basic CP function node.

In the above, the concept of network slicing has been described.

The network slice service of the 5G system can provide specialized network services for various industries. For example, when a manufacturing company wants to configure a network that can only access office equipment and machines of their employees and factories, conventionally, a wired network was constructed based on Ethernet, and in particular, Internet data between distant points For the exchange, a separate network was installed to maintain security. However, in the 5G system, the mobile communication service provider can virtualize the communication equipment installed by the mobile communication service provider, separate it into several network slices, and rent one of them to a third party such as the manufacturer. Based on this, the manufacturers can use the network slice service to construct a virtual dedicated network that only themselves can access.

However, in the above example, the manufacturer may want to use the network slice service only in a specific area. For example, if the manufacturing company's place of business is located only in Busan and Seoul, the manufacturer allows communication only when its employees connect to the network in Busan and Seoul when signing a network slice service contract with a mobile operator. In other areas, service access can be blocked to block unnecessary communication and increase security.

To this end, when the terminal registers its location in a certain area, the terminal transmits information (Requested N-SSAI) on the network slice to be provided to the network. Based on this, the network delivers information on the network slice (Allowed NSSAI) that can be provided in the region to the terminal according to the subscription condition of each terminal.

However, in the above process, the terminal first attempts to access in the current area, and then checks the information transmitted by the network. The terminal knows which network slice service can be provided in the corresponding area. If a terminal requests registration and network slice service provision to the network in an area where it is not provided with a service of a specific network slice, there is a problem in that the terminal uses radio resources unnecessarily to transmit the service provision request. have.

<Disclosures of this specification>

Disclosure of the present specification proposes methods for solving the above-described problem.

Hereinafter, an architecture presented in this specification and a procedure performed under the architecture will be described.

5 is the first of the present specification In Example 1 It is a flow chart that follows.

The terminal can transmit and receive signals with a radio access network (RAN) and a core network (CN) for wireless communication.

In the terminal, functions operating between the terminal and the RAN according to the function are called AS (Access Stratum), and the functions operating between the terminal and the core network are called NAS (Non-Access Stratum).

The RAN may be composed of a plurality of base stations (4G: eNodeB (eNB), 5G: gNodeB (gNB)).

The core network handles the Access and Mobility Management Function (AMF), which manages mobility through the NAS signal message processing of the terminal and the terminal location registration, and the control plane (CP) for the session between the terminal and the data network. There is SMF (Session Management Function).

The terminal may perform a registration procedure in the core network in order to perform wireless communication.

For registration, the terminal may transmit a registration request message to the core network. The registration request message may also include Single Network Slice Selection Assistance Information (S-NSSAI) indicating a network slice to be used by the terminal.

The core network may transmit a registration accept message to the terminal in response to the registration request. The registration accept message may include S-NSSAI.

The registration accept message may include information on network slices. The information may include permission condition information that the terminal can access for each network slice, and restriction condition information about the terminal that disables the use of the network slice.

For example, even if the terminal is a generally available network slice, the use of the network slice may be prohibited when the terminal is located in a specific area. In this case, the specific region may be a limiting condition in which the network slice cannot be used.

Conversely, even if the terminal is a network slice that cannot be used in general, the use of the network slice may be allowed when the terminal is located in a specific area. In this case, the specific region may be a condition for using the network slice. Constraints and allowance conditions for each network slice can be independent of each other.

As described above, the allowable conditions and constraints for the terminal may be related to a region as well as a TA (tracking area), a cell ID, and a frequency.

The core network may generate and include an encrypted identifier in a registration accept message and transmit it to the terminal. This value can be changed periodically or arbitrarily by the network. Signals transmitted from the network can be transmitted to all terminals because they are transmitted omni-directional rather than beamforming in the direction of a specific location by recognizing the location of the terminal. It is possible to allow only the terminal that wants to receive the signal to receive the signal, and the third terminal that is not allowed to receive the signal.

The above process may be performed in the process of establishing a PDU (protocol data unit) session.

Meanwhile, the terminal receives area information from a cell in a currently located area. Area info may be received through a system information block (SIB). Area information may include tracking area (TA), cell ID, and frequency information.

Local information can be delivered to the NAS layer of the terminal.

When data to be transmitted to the terminal is generated, the terminal may determine a network slice necessary for transmitting the data. The terminal may check whether there is information on the determined network slice from the information received from the core network. If there is information, it may be considered whether the current TA of the terminal, a cell ID, and a frequency to be used correspond to the above-described allowance condition and restriction condition of the determined network slice. As a result, it can be determined whether the terminal can use the determined network slice.

When the network slice is available, the terminal can initiate network access by sending a service request message to the core network. Alternatively, radio resource allocation may be requested through the RACH process. On the other hand, if the network slice cannot be used, the above process can be omitted.

By performing such a process, it is possible to increase efficiency by preventing a terminal from attempting to access a network in a service restricted area, thereby preventing unnecessary use of radio resources.

6 is the first of the present specification In Example 2 It is a flow chart that follows.

For registration, the terminal may transmit a registration request message to the core network. By including the S-NSSAI in the registration request message, the terminal can perform the registration process for the network slice it intends to use.

The core network may transmit a registration accept message to the terminal based on a registration request message. The registration accept message may include S-NSSAI. The registration accept message may include information on network slices. For each network slice, the information may include allowance condition information that enables the network slice to be used and restriction condition information that disables the use of the network slice.

For example, even if the terminal is a generally available network slice, the use of the network slice may be prohibited when the terminal is located in a specific area. In this case, the specific region may be a limiting condition in which the aforementioned network slice cannot be used.

Conversely, even if the terminal is a network slice that cannot be used in general, the use of the network slice may be allowed when the terminal is located in a specific area. In this case, the specific region may be an allowable condition for using the network slice. Constraints and allowance conditions for each network slice can be independent of each other.

As described above, the allowable condition and the limiting condition for the terminal may be not only for an area, but also for a TA (tracking area), a cell ID and a frequency.

The core network may generate and include an encrypted identifier in a registration accept message and transmit it to the terminal. This value can be changed periodically or arbitrarily by the network. The signal transmitted from the network can be transmitted to all terminals because it transmits a signal in omni-directional direction rather than by beamforming to a specific location by recognizing the location of the terminal. The signal can be received by only the terminal that wants to receive it, and it is possible to make it impossible for an unauthorized third terminal to receive the signal.

The above process can be performed in the process of establishing a PDU session.

Meanwhile, the UE receives slice radio resource configuration information from a cell in a region where it is currently located. The slice radio resource configuration information may include information on which radio resources can be used by the UE for each network slice in the corresponding cell or which radio resources are allocated.

When data to be transmitted to the terminal is generated, the terminal may determine a network slice necessary for transmitting the data.

The terminal may determine radio resource information allocated to the determined network slice (check radio resource). Radio resources may include random access resources. For example, when RACH resources are allocated for each network slice in a corresponding cell, the UE may determine the RACH resources allocated to the determined network slice.

The UE may perform a RACH procedure based on the determined RACH resource (RACH procedure).

In the terminal, information on a plurality of network slices may be set. For each network slice, the information may include allowance condition information that enables the network slice to be used and restriction condition information that disables the use of the network slice. Constraints and allowance conditions for each network slice can be independent of each other. In order for the terminal to transmit data, the terminal may transmit a radio resource request only for data related to the permitted network slice in consideration of the permission condition and the restriction condition.

The network is based on various business models, and when different terminals use the network slice service, it blocks access to the network slice service from places where communication is not permitted, thereby increasing the efficiency of radio resources and reducing the use of radio resources between terminals. By reducing the interference, the delay time can be reduced, and radio resources can be used more quickly.

7 is the first part of the present specification In Example 3 It is a flow chart that follows.

Unlike the above-described embodiments, it corresponds to an embodiment in which the core network determines whether or not a network slice can be used. That is, the core network can determine the above-described allowable condition and restriction condition for the network slice.

First, the RAN transmits area information to the terminal. The area information may include area information where the terminal is currently located.

When data to be transmitted to the terminal is generated, the terminal may determine a network slice necessary for transmitting the data.

The terminal may transmit a service request message to the core network. The service request message may include information on the region, information on data, and information on the determined network slice.

The core network may check the information to determine the region where the terminal is located, the cell, and the determined network slice. The core network may check the context information managed with respect to the terminal to check the allowed condition and the restriction condition of the determined network slice. Then, the core network can determine whether the terminal can use the determined network slice.

If not available, the network may transmit a signal indicating that the determined network slice cannot be used to the terminal. Conversely, if available, the network may transmit a signal indicating that the determined network slice can be used to the terminal.

Here, the context information may be managed in the AMF of the terminal. For example, the AMF can manage the following context information.

Field	Explanation
SUPI	SUPI (Subscription Permanent Identifier) is a user's unchanging identifier in 5G system.
Routing Indicator	The terminal's routing indicator is capable of routing network signals to AUSF and UDM instances that can provide services to subscribers along with the SUCI / SUPI home network identifier.
AUSF Group ID	The AUSF group ID is for a given terminal.
UDM Group ID	The UDM group ID is for the terminal.
SUPI-unauthenticated-indicator	This indicates whether it is not SUPI certified.
GPSI	The existence of GPSI of the UE is determined by storage of the UDM.
5G-GUTI	5G Globally Unique Temporary Identifier.
PEI	Mobile Equipment Identity
Internal Group ID-list	This is a list of internal groups to which the terminal belongs.
UE Specific DRX Parameters	UE Specific DRX Parameters.
UE MM Network Capability	Represents the UE MM network function.
5GMM Capability	It includes other UE functions related to interworking with 5GCN or EPS.
Events Subscription	List of event subscriptions by other CP NFs. Displaying information about the events you are subscribed to and how to send those notifications.
AM Policy Association information includes the following AM policy information and PCF ID.
AM Policy Information	Information about AM policy provided by PCF. Includes policy control request trigger and policy control request information. Includes authorized RFSP and authorized service area restrictions.
PCF ID (ID(s))	This is the PCF's identifier for the AM policy. It is the identifier of the V-PCF and H-PCF in roaming. (Reference 　1)
Subscribed RFSP Index	It is an index for a specific RRM configuration of NG-RAN received from UDM.
RFSP Index in Use	This is an index for the specific RRM configuration of the NG-RAN currently in use.
MICO Mode Indication	Indicates the MICO mode of the terminal.
Voice Support Match Indicator	Indicates whether the terminal wireless function is compatible with the network configuration. AMF uses this as an input to establish IMS voice through indication of PS session support over 3GPP access.
Homogenous Support of IMS Voice over PS Sessions	If "IMS Voice over PS Sessions" is homogeneously supported or not homogeneously supported in all TAs of the serving AMF, or if the support is not homogeneous or unknown, it is indicated per terminal (see 5.16.3.3 [2] of TS 23.501). ).
UE Radio Capability for Paging Information	Information used by NG-RAN to improve paging for the terminal (see 　23.501　[2] of TS 5.4.4.1).
Information On Recommended Cells And RAN nodes For Paging	Information transmitted by the NG-RAN, used by the AMF when paging the UE to aid in the determination of the NG-RAN node to be paged, and to provide information on the recommended cell to each of these NG-RAN nodes. It optimizes the probability of successful paging while minimizing signal load.
UE Radio Capability Information	Information transmitted by NG-RAN nodes and stored in AMF. Instead, when the NB-IoT specific terminal radio access function is transmitted, the AMF transmits information to the NG-RAN node in the terminal context while switching to the CM-CONNECTED state except for the NB-IoT.
NB-IoT specific UE Radio Access Capability Information	NB-IoT specific UE radio access function.
SMSF Identifier	The identifier of the SMSF provided to the terminal in the RM REGISTERED state.
SMSF Address	The address of the SMSF provided to the terminal in the RM-REGISTERED state. (See 4.13.3.1).
SMS Subscription	Regardless of the access type, it represents the subscription to the SMS transmission service through the NAS.
SEAF data	Master security information received from AUSF.
Last used EPS PLMN ID	This is the last EPS PLMN identifier.
Paging Assistance Data for CE capable UE	Paging support data for the enhanced coverage level and cell ID provided by the last NG-RAN to which the terminal is connected.
Enhanced Coverage Restricted Information	Specifies whether CE mode B is restricted for the terminal, CE mode A and CE mode B are restricted for the terminal, or whether CE mode A and CE mode B are not restricted for the terminal.
Service Gap Time	It is used to set the service interval timer for service interval control (see TS 23.501 [2] 5.31.16).
Remaining Running Service Gap timer	The remaining time of the currently running service gap timer (see TS 23.501 [2] 5.31.16).
Terminal access and mobility Context Each access type level within In context about :
Access Type	Indicates the type of access to this context.
RM State	Registration management status.
Registration Area	Current registration area (set of tracking areas in the TAI list).
TAI of last registration (TAI of last registration)	The TA's TAI where the last registration request was initiated.
User Location Information	Information about your location.
Mobility Restrictions	Mobility restriction restricts the mobility processing or service access of the terminal. It consists of RAT restriction, prohibited area, service area restriction and core network type restriction. It may also contain a list of allowed CAGs and, optionally, an indication indicating whether the UE can access 5GS through the CAG cell.
AMF-Associated Expected UE Behavior parameters	For each terminal specified in 4.15.6.3, the expected terminal behavior parameter and the corresponding valid time are displayed.
Security Information for CP	As defined in TS 33.501 [15].
Security Information for UP	As defined in TS 33.501 [15].
Allowed NSSAI	NSSAIs consisting of one or more S-NSSAIs were allowed to provide PLMNs in the current registration area.
Mapping Of Allowed NSSAI	The mapping of allowed NSSAI is to map each S-NSSAI of allowed NSSAI to S-NSSAI of subscribed S-NSSAI.
Inclusion of NSSAI in RRC Connection Establishment Allowed by HPLMN	[3GPP access only] Defines whether the UDM has indicated that the UE can include NSSAI in the RRC connection configuration of the plain text.
Access Stratum Connection Establishment NSSAI Inclusion Mode	TS 23.501 [2] Defines the NSSAI (if any) to be included in the access layer connection establishment as specified in 5.15.9.
AMF UE NGAP ID (AMF UE NGAP ID)	It identifies the association with the terminal through the NG interface in AMF defined in TS 38.413 [10]
RAN UE NGAP ID (RAN UE NGAP ID)	As defined in TS 38.413 [10], it identifies the association with the terminal through the NG interface within the NG-RAN node.
Network Slice Instance(s)	Network slice instance selected by 5GC for this terminal.
URRP-AMF information	The UE Reachability Request Parameter contains a list of authenticated NF IDs related to the URRP-AMF flag. Each URRP-AMF flag indicates whether or not the terminal's reachability notification is authenticated for the relevant NF ID by the HPLMN.
bracket NSSAI level In context about :
NSSAI restriction	This information includes restrictions that apply to S-NSSAI. For example, a location or cell where S_NSSAI may or may not be used may be included.
bracket PDU Session level In context about:
S-NSSAI(s)	S-NSSAI related to the PDU session.
DNN	The relevant DNN for the PDU session.
Network Slice Instance ID	Network slice instance information for the PDU session.
PDU Session ID	PDU session identifier.
SMF Information	The associated SMF identifier and SMF address for the PDU session.
Access Type	This is the current access type of the PDU session.
EBI-ARP list	EBI and associated ARP pairs assigned to this PDU session.
5GSM Core Network Capability	TS 23.501 [2] UE 5GSM core network functions as defined in 5.4.4b.
SMF derived CN assisted RAN parameters tuning	These are the PDU session specific parameters received from the SMF and are used by AMF to derive the core network support RAN parameter tuning.
Note 　1: AMF transmits PCF ID to SMF during PDU session establishment. The SMF can select a PCF identified by PCF ID as described in TS 23.501 [2], 6.3.7.1. In the HR roaming case, the AMF transmits the H-PCF identifier as described in Section 4.3.2.2.2. In the case of LBO roaming, the AMF transmits the V-PCF identifier as described in Section 4.3.2.2.1.

The above information may be obtained by the AMF from UDM (unified data management) or may be set according to a policy of a policy control function (PCF). In this way, when AMF manages NSSAI restriction information, when a request for a network slice from the terminal comes from the terminal, the AMF checks its own context information, and the network slice in the location and cell of the terminal The request can be sent to the SMF only when it is possible to check if the is available.

SMF can manage the following context information.

Field	Explanation
SUPI	SUPI (Subscription Permanent Identifier) is the subscriber's permanent ID in 5GS.
Trace reference	Identify a record or collection of records for a particular trace.
Trace type	Indicates the type of tracking.
OMC identity	Identify the OMC to receive the tracking record.
S-NSSAI	The requested S-NSSAI to the serving PLMN for the PDU session.
S-NSSAI restriction	This information includes restrictions that apply to S-NSSAI. For example, a location or cell where S_NSSAI can be used may be included.
HPLMN S-NSSAI	S-NSSAI request to HPLMN in home routing PDU session
Network Slice Instance ID	Network slice instance information for the PDU session.
DNN	The relevant DNN for the PDU session.
AMF Information	Associated AMF instance identifier and GUAMI.
Access Type	This is the current access type of the PDU session.
RAT type	RAT type used by the terminal.
PDU Session ID	The identifier of the PDU session.
H-SMF Information	The relevant H-SMF identifier and H-SMF address for the HR PDU session (V-SMF only).
PDU For each QoS flow in the session:
5G QoS Identifier (5QI)	This is the identifier of the authenticated QoS parameter for the service data flow.
ARP	Priority of allocation and retention of service data flows consisting of priority levels, preemption capabilities, and preemption vulnerabilities.
GFBR	Guaranteed flow bit rate (GFBR)-UL and DL.
MFBR	Maximum flow bit rate (MFBR)-UL and DL.
Priority Level	Represents the priority of resource scheduling among QoS flows.
Averaging Window	Represents the period for which the guaranteed and maximum bit rate is calculated.
Maximum Data Burst Volume	Represents the maximum amount of data to be transmitted within the 5G-AN PDB period.
Reflective QoS Control	It indicates to apply reflection QoS to SDF of TFT.
QoS Notification Control (QNC)	Indicates whether a notification is requested from the 3GPP RAN when the GFBR can no longer guarantee the QoS flow during the lifetime of the QoS flow (or if it can be done again).
Maximum Packet Loss Rate	Maximum packet loss rate-UL and DL..
With EPS Each to support interlocking On QFI about Mapping Made EPS Bearer Context :
EPS Bearer Id	The EPS bearer identity uniquely identifies the EPS bearer for one terminal accessed through the E-UTRAN.
Mapped EPS Bearer QoS	ARP, GBR, MBR, QCI.
PGW-U tunnel information	PGW-U S5/S8 GTP-U tunnel IP address and TEID information.
TFT	Traffic Flow Template.

The above information may be obtained from UDM by AMF or may be set according to the policy of PCF. SMF can manage NSSAI restriction information. When the terminal makes a request for a specific network slice, the SMF may first check the PDU session related to the corresponding NSSAI to determine the SMF that manages the corresponding PDU session. In addition, the request may be transmitted to the SMF, and additionally, information about the location or cell of the terminal may be transmitted. The SMF received this can check its own context information, check whether the location of the corresponding terminal and the cell can access the network slice, and only accept the request of the terminal and provide a service if possible. can do.

When the cell is changed after the UE enters the RRC connected mode, the AMF and SMF may not recognize that the cell is changed. In order to receive notification from the NG-RAN whenever the connected cell of the terminal changes, the AMF may request the NG-RAN to notify itself whenever the cell of the terminal changes. The AMF/SMF can identify the currently activated or requested PDU sessions and the NSSAI connected thereto, and determine whether each associated network slice is allowed in the changed cell. If not allowed, the AMF/SMF can deactivate or release the network slice that is already active, and if allowed, the above process can be omitted.

When the context (context) information of the terminal is formed in the NG-RAN, the AMF can determine which cell and which network slice service can be provided to the terminal by using the information it has or information received from the SMF. . For example, when a terminal requests radio resource allocation in a specific area where a network slice is not allowed, the network may ignore the request. In addition, when the NG-RAN tries to handover the terminal to another cell, or when handover to the unauthorized cell, the network slice service may be stopped, or the handover of the terminal only to a cell in which the use of the corresponding network slice is permitted. You can do it.

Information set in the terminal may need to be updated. For example, even though a specific network slice is currently permitted to be used in a corresponding region, the terminal may be set that the network slice cannot be used in the region. At this time, when data to use the network slice occurs in the terminal in the area, the terminal may transmit a signal including information indicating that the use of the network slice is prohibited to the AMF/SMF to the network. It may be determined that the network can use the network slice in the area despite the information. The network provides a service, and can deliver information about an updated network slice's allowance condition and restriction condition.

In case the allowable conditions and constraints change, the network transmits the timer information together when transmitting the information to be set to the terminal to the terminal, and when the timer value expires, the terminal deletes the information or requests the network for new information. You can do it.

Degree 8 is Configuration of a processor in which the disclosure of this specification is implemented Block diagram Show.

As can be seen with reference to FIG. 8, the processor 1020 in which the disclosure of the present specification is implemented includes a plurality of circuits to implement the proposed functions, procedures, and/or methods described herein. can do. For example, the processor 1020 may include a first circuit 1020-1, a second circuit 1020-2 and a third circuit 1020-3. Further, although not shown, the processor 1020 may include more circuits. Each circuit may include a plurality of transistors.

The processor 1020 may be referred to as an application-specific integrated circuit (ASIC) or an application processor (AP), and includes at least one of a digital signal processor (DSP), a central processing unit (CPU), and a graphics processing unit (GPU). can do.

The processor may be included in the UE.

The first circuit 1010-1 of the processor may receive information on at least one network slice from a network.

In the first circuit, the message including the information may include an identifier for the terminal.

The second circuit 1020-2 of the processor may determine one network slice from among the at least one network slice.

The second circuit may determine whether the terminal can use one network slice based on restriction condition information or allow condition information.

The third circuit 1020-3 of the processor may perform an access request to the determined one network slice.

The third circuit may transmit a service request message.

The processor may further include a fourth circuit (not shown) for transmitting a registration request message to the network before receiving information on the at least one network slice.

The information on the at least one network slice may include: information on a restriction condition in which the terminal cannot access to the at least one network slice or information on an allowance condition in which the terminal can access.

The restriction condition information may be information on an area inaccessible to the network slice, information on a frequency inaccessible to the network slice, and cell ID (identification ) May be information.

The registration request message may include: Single Network Slice Selection Assistance Information (S-NSSAI).

Degree 9 is Work In the examples It shows a wireless communication system according to.

Referring to FIG. 9, the wireless communication system may include a first device 100a and a second device 100b.

The first device 100a may be the UE described in the disclosure of this specification. Alternatively, the first device 100a is a base station, a network node, a transmitting UE, a receiving UE, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone (Unmanned Aerial Vehicle). , UAV), AI (Artificial Intelligence) module, robot, AR (Augmented Reality) device, VR (Virtual Reality) device, MR (Mixed Reality) device, hologram device, public safety device, MTC device, IoT device, medical device, It may be a fintech device (or financial device), a security device, a climate/environment device, a device related to 5G service, or a device related to the fourth industrial revolution field.

The second device 100b may be a network node (eg, AMF or MME) described in the disclosure of the present specification. Alternatively, the second device 100b is a base station, a network node, a transmitting UE, a receiving UE, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, a drone (Unmanned Aerial). Vehicle, UAV), AI (Artificial Intelligence) module, robot, AR (Augmented Reality) device, VR (Virtual Reality) device, MR (Mixed Reality) device, hologram device, public safety device, MTC device, IoT device, medical device , Fintech devices (or financial devices), security devices, climate/environment devices, devices related to 5G services, or other devices related to the 4th industrial revolution field.

For example, the UE is a mobile phone, a smart phone, a laptop computer, a digital broadcasting UE device, a personal digital assistants (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, Includes tablet PC, ultrabook, wearable device, for example, a watch-type UE device (smartwatch), a glass-type UE device (smart glass), HMD (head mounted display)), and the like. can do. For example, the HMD may be a display device worn on the head. For example, HMD can be used to implement VR, AR or MR.

For example, a drone may be a vehicle that is not human and is flying by a radio control signal. For example, the VR device may include a device that implements an object or a background of a virtual world. For example, the AR device may include a device that connects and implements an object or background of a virtual world, such as an object or background of the real world. For example, the MR device may include a device that combines and implements an object or background of a virtual world, such as an object or background of the real world. For example, the hologram device may include a device that implements a 360-degree stereoscopic image by recording and reproducing stereoscopic information by utilizing an interference phenomenon of light generated by the encounter of two laser lights called holography. For example, the public safety device may include an image relay device or an image device wearable on a user's human body. For example, the MTC device and the IoT device may be devices that do not require direct human intervention or manipulation. For example, the MTC device and the IoT device may include a smart meter, a bending machine, a thermometer, a smart light bulb, a door lock, or various sensors. For example, the medical device may be a device used for the purpose of diagnosing, treating, alleviating, treating or preventing a disease. For example, the medical device may be a device used for the purpose of diagnosing, treating, alleviating or correcting an injury or disorder. For example, a medical device may be a device used for the purpose of examining, replacing or modifying a structure or function. For example, the medical device may be a device used for the purpose of controlling pregnancy. For example, the medical device may include a device for treatment, a device for surgery, a device for (extra-corporeal) diagnosis, a device for hearing aid or a procedure. For example, the security device may be a device installed to prevent a risk that may occur and maintain safety. For example, the security device may be a camera, CCTV, recorder, or black box. For example, the fintech device may be a device capable of providing financial services such as mobile payment. For example, the fintech device may include a payment device or a point of sales (POS). For example, the climate/environment device may include a device that monitors or predicts the climate/environment.

The first device 100a may include at least one or more processors such as the processor 1020a, at least one or more memories such as the memory 1010a, and at least one or more transceivers such as the transceiver 1031a. The processor 1020a may perform the functions, procedures, and/or methods described above. The processor 1020a may perform one or more protocols. For example, the processor 1020a may perform one or more layers of a radio interface protocol. The memory 1010a is connected to the processor 1020a and may store various types of information and/or commands. The transceiver 1031a may be connected to the processor 1020a and controlled to transmit and receive radio signals.

The second device 100b may include at least one processor such as a processor 1020b, at least one memory device such as a memory 1010b, and at least one transceiver such as a transceiver 1031b. The processor 1020b may perform the functions, procedures, and/or methods described above. The processor 1020b may implement one or more protocols. For example, the processor 1020b may implement one or more layers of a radio interface protocol. The memory 1010b is connected to the processor 1020b and may store various types of information and/or commands. The transceiver 1031b may be connected to the processor 1020b and controlled to transmit and receive radio signals.

The memory 1010a and/or the memory 1010b may be respectively connected inside or outside the processor 1020a and/or the processor 1020b, or other processors through various technologies such as wired or wireless connection. It can also be connected to.

The first device 100a and/or the second device 100b may have one or more antennas. For example, the antenna 1036a and/or the antenna 1036b may be configured to transmit and receive wireless signals.

Degree 10 is Work In the examples A block diagram of a network node according to the following is illustrated.

In particular, FIG. 10 is a diagram illustrating in detail a case where a base station is divided into a central unit (CU) and a distributed unit (DU).

Referring to FIG. 10, the base stations W20 and W30 may be connected to the core network W10, and the base station W30 may be connected to the neighboring base station W20. For example, the interface between the base stations W20 and W30 and the core network W10 may be referred to as NG, and the interface between the base station W30 and the neighboring base stations W20 may be referred to as Xn.

The base station W30 may be divided into a CU (W32) and DU (W34, W36). That is, the base station W30 may be hierarchically separated and operated. The CU (W32) may be connected to one or more DUs (W34, W36), for example, the interface between the CU (W32) and the DU (W34, W36) may be referred to as F1. The CU (W32) may perform the function of upper layers of the base station, and the DUs (W34, W36) may perform the function of lower layers of the base station. For example, the CU (W32) is a logical node that hosts radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) layers of a base station (eg, gNB) The DU (W34, W36) may be a logical node hosting a radio link control (RLC), a media access control (MAC), and a physical (PHY) layer of the base station. Alternatively, the CU (W32) may be a logical node hosting the RRC and PDCP layers of the base station (eg, en-gNB).

The operation of the DUs W34 and W36 may be partially controlled by the CU W32. One DU (W34, W36) may support one or more cells. One cell can be supported by only one DU (W34, W36). One DU (W34, W36) may be connected to one CU (W32), and one DU (W34, W36) may be connected to a plurality of CUs by appropriate implementation.

Degree 11 is Work In the examples Follow UE's Composition Block diagram .

In particular, FIG. 11 is a diagram illustrating the UE of FIG. 9 in more detail above.

The UE includes a memory 1010, a processor 1020, a transmission/reception unit 1031, a power management module 1091, a battery 1092, a display 1041, an input unit 1053, a speaker 1042 and a microphone 1052, SIM (subscriber identification module) card, contains one or more antennas.

The processor 1020 may be configured to implement the proposed functions, procedures and/or methods described herein. Layers of the air interface protocol may be implemented in the processor 1020. The processor 1020 may include an application-specific integrated circuit (ASIC), another chipset, a logic circuit, and/or a data processing device. The processor 1020 may be an application processor (AP). The processor 1020 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). Examples of the processor 1020 are SNAPDRAGONTM series processors manufactured by Qualcomm®, EXYNOSTM series processors manufactured by Samsung®, A series processors manufactured by Apple®, HELIOTM series processors manufactured by MediaTek®, INTEL®. It may be an ATOMTM series processor manufactured by or a corresponding next-generation processor.

The power management module 1091 manages power for the processor 1020 and/or the transceiver 1031. The battery 1092 supplies power to the power management module 1091. The display 1041 outputs the result processed by the processor 1020. The input unit 1053 receives an input to be used by the processor 1020. The input unit 1053 may be displayed on the display 1041. A SIM card is an integrated circuit used to securely store an international mobile subscriber identity (IMSI) used to identify and authenticate a subscriber in a mobile phone device such as a mobile phone and a computer and a key associated therewith. You can even store contact information on many SIM cards.

The memory 1010 is operatively coupled to the processor 1020 and stores various pieces of information for operating the processor 610. The memory 1010 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium, and/or other storage device. When an embodiment is implemented as software, the techniques described in this specification may be implemented as a module (eg, a procedure, a function, etc.) that performs a function described in this specification. Modules may be stored in memory 1010 and executed by processor 1020. The memory 1010 may be implemented inside the processor 1020. Alternatively, the memory 1010 may be implemented outside the processor 1020 and may be communicatively connected to the processor 1020 through various means known in the art.

The transceiver 1031 is operatively coupled to the processor 1020, and transmits and/or receives a radio signal. The transceiver 1031 includes a transmitter and a receiver. The transceiver 1031 may include a baseband circuit for processing radio frequency signals. The transceiver unit controls one or more antennas to transmit and/or receive radio signals. The processor 1020 transmits command information to the transmission/reception unit 1031 to transmit, for example, a radio signal constituting voice communication data in order to initiate communication. The antenna functions to transmit and receive radio signals. When receiving a radio signal, the transceiver 1031 may transmit a signal for processing by the processor 1020 and convert the signal into a baseband. The processed signal may be converted into audible or readable information output through the speaker 1042.

The speaker 1042 outputs a sound-related result processed by the processor 1020. The microphone 1052 receives a sound related input to be used by the processor 1020.

The user inputs command information such as a telephone number, for example, by pressing (or touching) a button of the input unit 1053 or by voice activation using the microphone 1052. The processor 1020 receives the command information and processes to perform an appropriate function, such as dialing a phone number. Operational data may be extracted from the SIM card or the memory 1010. In addition, the processor 1020 may display command information or driving information on the display 1041 for user recognition and convenience.

Degree 12 is In detail, the transmission/reception unit of the first device shown in FIG. 9 Block diagram .

Referring to FIG. 12, the transceiver 1031 includes a transmitter 1031-1 and a receiver 1031-2. The transmitter 1031-1 includes a DFT (Discrete Fourier Transform) unit 1031-11, a subcarrier mapper 1031-12, an IFFT unit 1031-13 and a CP insertion unit 1031-14, and a wireless transmission unit 1031 -15). The transmitter 1031-1 may further include a modulator. In addition, for example, a scramble unit (not shown; a scramble unit), a modulation mapper (not shown; modulation mapper), a layer mapper (not shown; layer mapper), and a layer permutator (not shown; layer permutator) may be further included, It may be disposed prior to the DFT unit 1031-11. That is, in order to prevent an increase in the peak-to-average power ratio (PAPR), the transmitter 1031-1 first passes the information through the DFT 1031-11 before mapping the signal to the subcarrier. After performing subcarrier mapping of the signal spread by the DFT unit 1031-11 (or precoded in the same sense) through the subcarrier mapper 1031-12, an Inverse Fast Fourier Transform (IFFT) unit 1031- 13) to make a signal on the time axis.

The DFT unit 1031-11 outputs complex-valued symbols by performing DFT on input symbols. For example, when Ntx symbols are input (however, Ntx is a natural number), the DFT size is Ntx. The DFT unit 1031-11 may be called a transform precoder. The subcarrier mapper 1031-12 maps the complex symbols to each subcarrier in the frequency domain. The complex symbols may be mapped to resource elements corresponding to a resource block allocated for data transmission. The subcarrier mapper 1031-12 may be referred to as a resource element mapper. The IFFT unit 1031-13 outputs a baseband signal for data, which is a time domain signal, by performing IFFT on an input symbol. The CP insertion unit 1031-14 copies a part of the rear part of the baseband signal for data and inserts it into the front part of the baseband signal for data. Inter-symbol Interference (ISI) and Inter-Carrier Interference (ICI) are prevented through CP insertion, so that orthogonality can be maintained even in a multipath channel.

On the other hand, the receiver 1031-2 includes a radio receiver 1031-21, a CP removal unit 1031-22, an FFT unit 1031-23, and an equalization unit 1031-24. The wireless receiving unit 1031 -21, CP removing unit 1031-22, and FFT unit 1031-23 of the receiver 1031-2 are a wireless transmission unit 1031-15 at the transmitting end 1031-1, It performs the reverse function of the CP insertion unit 1031-14 and the IFF unit 1031-13. The receiver 1031-2 may further include a demodulator.

<Scenario to which the disclosure of this specification can be applied>

Although not limited thereto, various descriptions, functions, procedures, proposals, methods, and/or operational flow charts of the disclosure of the present specification disclosed in this document are used in various fields requiring wireless communication/connection (eg, 5G) between devices. Can be applied.

Hereinafter, it will be illustrated in more detail with reference to the drawings. In the following drawings/description, the same reference numerals may exemplify the same or corresponding hardware block, software block, or functional block, unless otherwise indicated.

13 illustrates a communication system 1 applied to the disclosure of this specification.

13, a communication system 1 applied to the disclosure of the present specification includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (eg, 5G NR (New RAT), LTE (Long Term Evolution)), and may be referred to as a communication/wireless/5G device. Although not limited thereto, wireless devices include robots 100a, vehicles 100b-1 and 100b-2, eXtended Reality (XR) devices 100c, hand-held devices 100d, and home appliances 100e. ), an Internet of Thing (IoT) device 100f, and an AI device/server 400. For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, and a vehicle capable of performing inter-vehicle communication. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (eg, a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, including HMD (Head-Mounted Device), HUD (Head-Up Display), TV, smartphone, It can be implemented in the form of a computer, wearable device, home appliance, digital signage, vehicle, robot, and the like. Portable devices may include smart phones, smart pads, wearable devices (eg, smart watches, smart glasses), computers (eg, notebook computers, etc.). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors, smart meters, and the like. For example, the base station and the network may be implemented as a wireless device, and the specific wireless device 200a may operate as a base station/network node to another wireless device.

The wireless devices 100a to 100f may be connected to the network 300 through the base station 200. AI (Artificial Intelligence) technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI server 400 through the network 300. The network 300 may be configured using a 3G network, a 4G (eg, LTE) network, or a 5G (eg, NR) network. The wireless devices 100a to 100f may communicate with each other through the base station 200 / network 300, but may perform direct communication (e.g. sidelink communication) without going through the base station / network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g. V2V (Vehicle to Vehicle)/V2X (Vehicle to Everything) communication). In addition, the IoT device (eg, sensor) may directly communicate with other IoT devices (eg, sensors) or other wireless devices 100a to 100f.

Wireless communication/ connections 150a, 150b, and 150c may be established between the wireless devices 100a to 100f / base station 200 and the base station 200 / base station 200. Here, the wireless communication/connection includes various wireless access such as uplink/downlink communication 150a, sidelink communication 150b (or D2D communication), base station communication 150c (eg relay, Integrated Access Backhaul). This can be achieved through technology (eg 5G NR) Through wireless communication/ connections 150a, 150b, 150c, the wireless device and the base station/wireless device, and the base station and the base station can transmit/receive radio signals to each other. For example, the wireless communication/ connection 150a, 150b, 150c may transmit/receive signals through various physical channels. To this end, based on various proposals disclosed herein, transmission/reception of radio signals At least some of a process of setting various configuration information for, a process of processing various signals (eg, channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.), a resource allocation process, and the like may be performed.

Although preferred embodiments have been exemplarily described above, the disclosure of the present specification is not limited to such specific embodiments, and thus modifications, changes, or modifications in various forms within the scope of the spirit and claims of the present specification It can be improved.

In the exemplary system described above, the methods are described on the basis of a flowchart as a series of steps or blocks, but are not limited to the order of the steps described, and certain steps may occur in a different order or concurrently with the steps described above. have. In addition, those skilled in the art will understand that the steps shown in the flowchart are not exclusive, other steps may be included, or one or more steps in the flowchart may be deleted without affecting the scope of the rights.

The claims set forth herein may be combined in a variety of ways. For example, the technical features of the method claims of the present specification may be combined to be implemented as a device, and the technical features of the device claims of the present specification may be combined to be implemented by a method. In addition, the technical characteristics of the method claim of the present specification and the technical characteristics of the device claim may be combined to be implemented as a device, and the technical characteristics of the method claim of the present specification and the technical characteristics of the device claim may be combined to be implemented by a method.

Claims (26)

1. As a method for a terminal to access a network,

   Receiving information on at least one network slice from the network,

   The information includes information on a restriction condition in which the terminal cannot access to the at least one network slice or information on an allowance condition in which the terminal can access;

   Determining one network slice from among the at least one network slice,

   In the determining step, the constraint condition information or the allowance condition information is considered;

   And performing an access request to the determined one network slice.
2. The method of claim 1, wherein the constraint information is information about an area inaccessible to a network slice.
3. The method of claim 1, wherein the restriction condition information is information on radio resources that cannot be accessed for a network slice.
4. The method of claim 1, wherein the restriction condition information is information on a cell ID (identification) that cannot access a network slice.
5. The method of claim 2, wherein the information on the inaccessible area includes at least one of a tracking area (TA) and a cell identification (ID).
6. The method of claim 1, further comprising transmitting a registration request message to the network before receiving information on the at least one network slice.
7. The method of claim 6, wherein the registration request message includes Single Network Slice Selection Assistance Information (S-NSSAI).
8. The method of claim 1,

   Further comprising the step of transmitting a registration request message,

   The information is received by being included in a response message to the registration request message.
9. The method of claim 1, wherein the step of requesting access

   A method comprising transmitting a service request message.
10. The method of claim 9,

    Based on the determined one network slice, further comprising the step of selecting one of a plurality of radio resources,

    The service request message is transmitted on the selected resource.
11. The method of claim 10, wherein the plurality of radio resources

    A method including a first radio resource for a first slice and a second radio resource for a second slice.
12. The method of claim 10, wherein the radio resource includes a resource for random access.
13. The method of claim 1, wherein determining the one network slice comprises:

    And determining whether the terminal can use the one network slice based on the restriction condition information or the allowance condition information.
14. As a terminal connecting to the network,

    A transceiver;

    Including a processor that processes the connection request,

    The processor receives information on at least one network slice from the network,

    The information includes information on a restriction condition that the terminal cannot access or information on an access permission condition for the at least one network slice,

    The processor determines one network slice from among the at least one network slice in consideration of the restriction condition information or the allowance condition information,

    The processor is a terminal that performs an access request to the determined one network slice.
15. 15. The terminal of claim 14, wherein the restriction condition information is information on a region in which the network slice cannot be accessed.
16. The terminal of claim 14, wherein the restriction condition information is information on radio resources that cannot be accessed for a network slice.
17. 15. The terminal of claim 14, wherein the restriction condition information is information on a cell ID (identification) that cannot access a network slice.
18. The terminal of claim 15, wherein the information on the inaccessible area includes at least one of a tracking area (TA) and a cell identification (ID).
19. The terminal of claim 14, further comprising transmitting a registration request message to the network before receiving information on the at least one network slice.
20. The terminal of claim 19, wherein the registration request includes Single Network Slice Selection Assistance Information (S-NSSAI).
21. The method of claim 14,

    The processor transmits a registration request message,

    The information is received by being included in a response message to the registration request message.
22. The terminal of claim 14, wherein the access request comprises transmitting a service request message.
23. The method of claim 22,

    The processor selects one of a plurality of radio resources based on the determined one network slice,

    The service request message is transmitted on the selected resource.
24. The method of claim 23, wherein the plurality of random access resources

    A terminal including a first radio resource for a first slice and a second radio resource for a second slice.
25. The terminal of claim 23, wherein the radio resource includes a resource for random access.
26. The method of claim 14,

    The processor determines whether or not the terminal can use the one network slice based on the restriction condition information or the allowance condition information.

Images