Protocol data unit session setup procedure for industrial traffic

Abstract

One disclosure of the present specification provides a method operating in a terminal. The method comprises the following steps of: sending a protocol data unit (PDU) session establishment request message; and in response to the transmission of the PDU session setup request message, which may include receiving a PDU session setup accept message or a PDU session setup reject message. The PDU session setup request message may include a PDU session type indicating industrial traffic. When a PDU session setup reject message is received, the PDU session setup reject message may include a cause value indicating that the network does not support the PDU session type.

Description

Technical Field

[0001] This manual involves mobile communications Background Art

[0002] Based on the success of the fourth generation of mobile communications, long term evolution (LTE) / LTE-Advanced (LTE-A), interest in the next generation, the fifth generation (so-called 5G), mobile communications is increasing, and research work is progressing.

[0003] The fifth generation of mobile communications defined by the International Telecommunication Union (ITU) is to provide data transmission speeds of up to 20Gbps and experience transmission speeds of at least 100Mbps anywhere. The official name is "IMT-2020", and the goal is to achieve commercialization worldwide in 2020.

[0004] The fifth generation of mobile communications supports multiple numerologies or subcarrier spacing (SCS) to support various services. For example, if the SCS is 15kHz, it supports wide area of ​​traditional cellular bands, if the SCS is 30kHz / 60kHz, it supports dense-urban, lower latency and wider carrier bandwidth, and when the SCS is above 60kHz, it supports bandwidth greater than 24.25GHz to overcome phase noise.

[0005] NR frequency band is defined as two types of frequency ranges (FR1, FR2). FR1 is 410MHz–7125MHz, and FR2 is 24250MHz–52600MHz, which can mean millimeter wave (mmW).

[0006] For the sake of convenience, in the frequency range used in the NR system, FR1 can represent "range below 6 GHz", FR2 can represent "range above 6 GHz", and can be called millimeter wave (millimeter wave, mmW).

[0007]

Table 1

[0008]

Table 2

[0009] First, URLLC involves use cases that require high reliability and low latency. For example, services such as autonomous driving, factory automation, and augmented reality require high reliability and low latency (e.g., latency below 1ms). The current 4G (LTE) latency is statistically 21-43ms (best 10%) and 33-75ms (middle). This is not enough to support services that require latency below 1ms.

[0010] Next, eMBB use cases involve use cases that require mobile ultra-wideband.

[0011] This ultra-wideband high-speed service seems difficult to be accommodated by the existing LTE / LTE-A designed core network.

[0012] Therefore, in the so-called fifth generation of mobile communications, there is an urgent need to redesign the core network.

[0013] Figure 1 is a diagram showing the structure of a next generation mobile communication network.

[0014] 5GC (5G Core) can include various components. Figure 1Including the Access and Mobility Management Function (AMF) 41, Session Management Function (SMF) 42, Policy Control Function (PCF) 43, User Plane Function (UPF) 44, Application Function (AF) 45, Unified Data Management (UDM) 46, and Non-3GPP InterWorking Function (Non-3GPP InterWorking Function) 49, which are part of it.

[0015] The UE 10 is connected to a data network through a Next Generation Radio Access Network (NG-RAN) via the UPF 44 .

[0016] The UE 10 may also receive data services via an untrusted non-3rd Generation Partnership Project (non-3GPP) access such as a Wireless Local Area Network (WLAN). To access the non-3GPP core network, a N3IWF 49 may be provided.

[0017] Figure 2 is an example showing the expected structure of the next generation mobile communication from the perspective of nodes.

[0018] refer to Figure 2 It can be seen that the UE is connected to the data network (DN) through the next generation Radio Access Network (RAN).

[0019] The control plane function (CPF) node shown performs all or part of the mobility management entity (MME) functions of the fourth generation mobile communication, as well as all or part of the control plane functions of the serving gateway (S-GW) and the PDN gateway (P-GW). The CPF node includes the access and mobility management function (AMF) and the session management function (SMF).

[0020] The user plane function (UPF) node shown is a type of gateway for sending and receiving user data. The UF node can perform all or part of the user plane functions of the S-GW and P-GW of the fourth generation mobile communication.

[0021] The Policy Control Function (PCF) shown is the node that controls the operator's policy.

[0022] The application function (AF) shown is a server that provides various services to UE.

[0023] The Unified Data Management (UDM) shown is a server that manages subscriber information, such as the Home Subscriber Server (HSS) of the fourth generation mobile communication. The UDM stores the subscriber information in a Unified Data Repository (UDR) and manages it.

[0024] The Authentication Server Function (AUSF) shown authenticates and manages the UE.

[0025] The Network Slice Selection Function (NSSF) shown is a node for network slicing as described later.

[0026] exist Figure 2In , the UE uses multiple protocol data units or packet data units (PDU) sessions to access two data networks simultaneously.

[0027] Figure 3 is a diagram showing an example of an architecture that supports simultaneous access to two data networks.

[0028] exist Figure 3 It shows the architecture where the UE uses one PDU session to access two data networks simultaneously.

[0029] Figure 2 and Figure 3 The reference points shown are as follows.

[0030] N1 represents the reference point between UE and AMF.

[0031] N2 represents the reference point between (R)AN and AMF.

[0032] N3 represents the reference point between (R)AN and UPF.

[0033] N4 represents the reference point between SMF and UPF.

[0034] N5 represents the reference point between PCF and AF.

[0035] N6 represents the reference point between UPF and DN.

[0036] N7 represents the reference point between SMF and PCF.

[0037] N8 represents the reference point between UDM and AMF.

[0038] N9 represents the reference point between UPFs.

[0039] N10 represents the reference point between UDM and SMF.

[0040] N11 represents the reference point between AMF and SMF.

[0041] N12 represents the reference point between AMF and AUSF.

[0042] N13 represents the reference point between UDM and AUSF.

[0043] N14 represents the reference point between AMFs.

[0044] N15 represents the reference point between PCF and AMF.

[0045] N16 represents the reference point between SMFs.

[0046] N22 represents the reference point between AMF and NSSF.

[0047] Figure 4 is another example diagram showing the structure of the Radio Interface Protocol between the UE and the gNB.

[0048] The wireless interface protocol is based on the 3GPP wireless access network standard. The wireless interface protocol consists of the physical layer, data link layer and network layer horizontally, and is divided into the user plane (User Plane) for data information transmission and the control plane (Control Plane) for control signal transmission vertically.

[0049] The protocol layer is based on the lower three layers of the Open System Interconnection (OSI) standard model which is well known in communication systems and can be divided into L1 (Layer 1), L2 (Layer 2) and L3 (Layer 3).

[0050] Each layer of the wireless protocol is described below.

[0051] The first layer, the physical layer, uses a physical channel to provide information transfer services. The physical layer is connected to the upper media access control layer through the transport channel, and the data between the media access control layer and the physical layer is transmitted through the transport channel. In addition, data is transmitted between different physical layers, that is, between the physical layers on the sending side and the receiving side, through the physical channel.

[0052] The second layer includes the Medium Access Control (MAC) layer, the Radio Link Control (RLC) layer and the Packet Data Convergence Protocol (PDCP) layer.

[0053] The third layer includes Radio Resource Control (RRC). The RRC layer is defined only in the control plane and is related to the establishment (setting), reset (Resetting) and release (Release) of Radio Bearers (RBs), and is responsible for the control of logical channels, transport channels, and physical channels. At this time, RB means the service provided by the second layer for data transmission between the terminal and E-UTRAN.

[0054] The Non-Access Stratum (NAS) layer performs functions such as connection management (session management) and mobility management.

[0055] The NAS layer is divided into NAS entities for mobility management (MM) and NAS entities for session management (SM).

[0056] 1) The NAS entity for MM generally provides the following functions.

[0057] As NAS processes related to AMF, they include: -Registration management and access management process, AMF supports the following functions: -Secure NAS signaling connection between UE and AMF (integrity protection, encryption) 2) The NAS entity for SM performs session management between the UE and SMF.

[0058] The SM signaling message is processed at the NAS-SM layer between the UE and the SMF, i.e. created and processed. The content of the SM signaling message is not interpreted by the AMF.

[0059] -When sending SM signaling, - The NAS entity for MM creates a NAS-MM message indicating the security header for NAS transmission of SM signaling, and derives the method and location of delivering SM signaling messages through the received additional information for NAS-MM.

[0060] - When receiving SM signaling, the NAS entity for SM performs an integrity check of the NAS-MM message and interprets the additional information to deduce the method and location of the SM signaling message.

[0061] At the same time, Figure 4 In the wireless communication network, the RRC layer, RLC layer, MAC layer and PHY layer located below the NAS layer are collectively referred to as the access stratum (AS).

[0062] The network system (ie, 5GC) for the next generation mobile communication (ie, 5G) also supports non-3GPP access. A representative example of non-3GPP access is WLAN access. WLAN access can include trusted WLAN and untrusted WLAN.

[0063] In the system used for 5G, AMF not only performs 3GPP access, but also performs registration management (RM) and connection management (CM) for non-3GPP access.

[0064] At the same time, in the future ultra-connected intelligent information society of the Fourth Industrial Revolution and 5G mobile communications, ultra-low latency (Ultra Reliable Low Latency Communications, URLLC) network technology, which is used to organically connect and exchange and process information between people and objects, online and offline, is becoming a necessary technology based on network infrastructure.

[0065] Time-Sensitive Networking (TSN) is introduced as a part of URLLC network technology.

[0066] However, the PDU session type in 3GPP 5GS (5G system) does not support TSN-based traffic. Summary of the invention

[0067] Technical issues Therefore, the purpose of the present specification is to propose a method for solving the above problems.

[0068] Technical Solution In order to solve the above-mentioned problem, a disclosure of this specification provides an operation method at a terminal. The method may include: the step of sending a Protocol Data Unit (PDU) session establishment request message; and the step of receiving a PDU session establishment acceptance message or a PDU session establishment rejection message in response to the sending of the PDU session establishment request message. The PDU session establishment request message may include a PDU session type for notifying industrial traffic. When receiving the PDU session establishment rejection message, the PDU session establishment rejection message may include a reason value indicating that the network does not support the PDU session type.

[0069] In order to solve the above-mentioned problem, a disclosure of the present specification provides a chipset installed in a terminal. The chipset includes: at least one processor; and at least one memory storing instructions and operably electrically connected to the at least one processor. Based on the instructions executed by the at least one processor, the operations performed may include: the step of sending a protocol data unit (PDU) session establishment request message; and the step of receiving a PDU session establishment acceptance message or a PDU session establishment rejection message in response to the sending of the PDU session establishment request message. The PDU session establishment request message may include a PDU session type notifying industrial traffic. When the PDU session establishment rejection message is received, the PDU session establishment rejection message may include a reason value indicating that the network does not support the protocol data unit session type.

[0070] In order to solve the above-mentioned problem, a disclosure of the present specification provides a device for a terminal. The device may include: a transceiver unit; at least one processor; and at least one memory storing instructions and operably electrically connected to the at least one processor. Based on the instructions executed by the at least one processor, the operations performed may include: the step of sending a protocol data unit (PDU) session establishment request message; and the step of receiving a PDU session establishment acceptance message or a PDU session establishment rejection message in response to the sending of the PDU session establishment request message. The PDU session establishment request message may include a PDU session type notifying industrial traffic. When the PDU session establishment rejection message is received, the PDU session establishment rejection message may include a reason value indicating that the network does not support the PDU session type.

[0071] The industrial traffic may be traffic for a time-sensitive network (TSN), a time-sensitive communication (TSC), a deterministic network (DetNet), an ultra-reliable and low-latency communication (URLLC), or an industrial Internet of Things (IIoT).

[0072] The PDU session establishment reject message may include a backoff timer.

[0073] The PDU session establishment rejection message may include a retry indicator. The retry indicator may indicate whether the terminal is allowed to attempt the PDU session establishment process using the same data network name (DNN) and the same single network slice selection assistance information (NSSAI) in an equivalent public land mobile network (PLMN).

[0074] The protocol data unit session establishment request message may further include: capability information or indication related to the industrial traffic.

[0075] Based on being executed by the method or the at least one processor, the executed operations may further include: sending a registration request message including capability information or indication related to the industrial flow.

[0076] Based on the method or the at least one processor, the executed operations may further include: receiving a Registration Accept message including capability information or indication related to the industrial flow.

[0077] Based on the method or the at least one processor, the executed operations may further include: sending a UL Non-Access Stratum (NAS) transmission message including capability information or indication related to the industrial traffic.

[0078] Based on the method or the at least one processor, the executed operations may further include: sending a DL Non-Access Stratum (NAS) transmission message including capability information or indication related to the industrial traffic.

[0079] The capability information or indication related to the industrial traffic may be provided in the terminal or a universal subscriber identity module (USIM) of the terminal.

[0080] Effects of the Invention The terminal and the network can meet the service requirements for industrial traffic (e.g., TSN traffic, TSC traffic, DetNet traffic, URLLC traffic, or IIoT traffic) and effectively process it based on the new PDU session type for recognizing and distinguishing industrial traffic (e.g., TSN traffic, TSC traffic, DetNet traffic, URLLC traffic, or IIoT traffic) and the capability indication / information for industrial traffic (e.g., TSN traffic, TSC traffic, DetNet traffic, URLLC traffic, or IIoT traffic) alone or together. In addition, according to such an efficient industrial traffic (e.g., TSN traffic, TSC traffic, DetNet traffic, URLLC traffic, or IIoT traffic) session processing method, unnecessary signaling overhead can be reduced to minimize battery and resource waste of the terminal and the network. BRIEF DESCRIPTION OF THE DRAWINGS

[0081] Figure 1 is a diagram showing the structure of a next generation mobile communication network.

[0082] Figure 2 is an example showing the expected structure of the next generation mobile communication from the perspective of nodes.

[0083] Figure 3 is a diagram showing an example of an architecture that supports simultaneous access to two data networks.

[0084] Figure 4 is another example diagram showing the structure of the Radio Interface Protocol between the UE and the gNB.

[0085] Figure 5a and 5b is a signal flow diagram illustrating an exemplary PDU session establishment process.

[0086] Figure 6a and Figure 6b It shows the modification process of the PDU session.

[0087] Figure 7 is a diagram showing an example of a network architecture that interoperates with a TSN network.

[0088] Figure 8 is an example diagram illustrating an architecture that supports time-sensitive communications and time synchronization services.

[0089] Fig. 9 is an exemplary diagram showing a process according to one disclosure of the present specification.

[0090] Fig.10 is an exemplary diagram illustrating another process according to a disclosure of the present specification.

[0091] Fig.11 is a block diagram showing the configuration of a processor that implements the disclosure of this specification.

[0092] Fig.12 FIG. 2 is a diagram showing a wireless communication system according to an embodiment.

[0093] Fig.13 is a block diagram illustrating a network node according to an embodiment.

[0094] Fig.14 is a block diagram showing the configuration of UE 100 according to an embodiment.

[0095] Fig.15 It is shown in Fig.12 The transceiver unit of the first device shown in FIG. Fig.14 A block diagram of the transceiver unit of the device shown.

[0096] Fig.16 1 is a diagram showing a communication system 1 applicable to the disclosure of this specification.

[0097] Best Mode for Carrying Out the Invention It should be noted that the technical terms used in this specification are only used to describe specific embodiments and are not intended to limit the contents of this specification. In addition, unless specifically defined in different ways in this specification, the technical terms used in this specification should be interpreted as the meanings commonly understood by technicians in the technical field to which the disclosure of this specification belongs, and should not be interpreted as over-generalized meanings or over-reduced meanings. In addition, if the technical terms used in this specification are incorrect technical terms that cannot accurately express the contents and ideas of this specification, they should be replaced with technical terms that can be correctly understood by those skilled in the art. In addition, the general terms used in this specification should be interpreted as defined in the dictionary or according to the context, and should not be interpreted as over-reduced meanings.

[0098] In addition, singular expressions as used in this specification include plural expressions unless the context clearly indicates otherwise. In this application, terms such as "consisting of" or "having" should not be interpreted as necessarily including all the various constituent elements or steps described in the specification, and may not include some constituent elements or steps, or should be interpreted as also including additional constituent elements or steps.

[0099] In addition, the terms including ordinal numbers such as first, second, etc. used in this specification can be used to describe various constituent elements, but the constituent elements should not be limited by the terms. The terms are only used to distinguish one constituent element from another constituent element. For example, without departing from the scope of the rights, the first constituent element can be named as the second constituent element, and similarly, the second constituent element can also be named as the first constituent element.

[0100] When a component is mentioned as being connected or accessed to another component, it can be directly connected or accessed to another component, but other components may also exist in between. On the other hand, when it is mentioned that a component is directly connected or directly accessed to another component, it should be understood that there are no other components in between.

[0101] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings, but the same or similar constituent elements will be given the same figure marks regardless of the drawing symbols, and repeated descriptions thereof will be omitted. In addition, when interpreting the contents of this specification, if it is determined that the detailed description of the relevant known technology may obscure the gist of this specification, its detailed description will be omitted. In addition, it should be noted that the drawings are only for the purpose of facilitating the understanding of the contents and ideas of this specification, and should not be understood as limiting the contents and ideas of this specification by the drawings. The contents and ideas of this specification should be interpreted as extending to all changes, equivalents or substitutes other than the drawings.

[0102] In this specification, "A or B" may mean "only A", "only B", or "both A and B". In other words, in this specification, "A or B" may be interpreted as "A and / or B". For example, in this specification, "A, B or C" may mean "only A", "only B", "only C", or "any combination of A, B and C".

[0103] A slash ( / ) or a comma used in this specification may mean "and / or". For example, "A / B" may mean "A and / or B". Thus, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B, or C".

[0104] In the present specification, "at least one of A and B" may mean "only A", "only B", or "both A and B". In addition, the expression "at least one of A or B" or "at least one of A and / or B" in the present specification may be interpreted the same as "at least one of A and B".

[0105] In addition, in this specification, "at least one of A, B, and C" may represent "only A", "only B", "only C", or "any and all combinations of A, B, and C". In addition, "at least one of A, B, or C" or "at least one of A, B, and / or C" may represent "at least one of A, B, and C".

[0106] In addition, the parentheses used in this specification may represent "for example". Specifically, when expressed as "control information (PDCCH)", "PDCCH" is proposed as an example of "control information". In other words, "control information" in this specification is not limited to "PDCCH", and "PDDCH" may be proposed as an example of "control information". In addition, when expressed as "control information (i.e., PDCCH)", "PDCCH" may also be proposed as an example of "control information".

[0107] The technical features separately described in one drawing of this specification may be implemented separately or simultaneously.

[0108] In the drawings, a user equipment (UE) is shown by way of example, but the shown UE may also be referred to by terms such as UE 100 (terminal), mobile equipment, etc. In addition, the UE may be a portable device such as a laptop computer, mobile phone, PDA, smart phone, or multimedia device, or may be a non-portable device such as a PC or in-vehicle device.

[0109] <PDU Session Establishment Procedure> There may be the following two types of PDU session establishment procedures for the protocol data unit (PDU) session establishment procedure.

[0110] - PDU session establishment procedure initiated by the UE - PDU session establishment procedure initiated by the network. For this purpose, the network may send a device trigger message to the application of the UE.

[0111] Figure 5a and 5b are signal flowcharts showing exemplary PDU session establishment procedures.

[0112] Figure 5a and Figure 5b The shown procedures are based on the registration procedure shown in FIG. 5, assuming that the UE has already registered with the AMF. Therefore, it is assumed that the AMF has obtained the user subscription data from the UDM.

[0113] 1) UE sends a NAS message to AMF. The message may include single network slice selection assistance information (S-NSSAI), data network name (DNN), PDU session ID, request type and N1 SM information.

[0114] Specifically, the UE includes S-NSSAI from the NSSAI allowed by the current access type. If the information about the mapped NSSAI has been provided to the UE, the UE may provide all S-NSSAI based on the allowed NSSAI and corresponding S-NSSAI based on the information of the mapped NSSAI. The mapped NSSAI information is information that maps each S-NSSAI in the allowed NSSAI to the S-NSSAI of the NSSAI set for the Home Public Land Mobile Network (HPLMN).

[0115] More specifically, the UE may extract and store the information of the S-NSSAI and the mapped S-NSSAI in the registration process of FIG5 including the registration acceptance message received from the network (ie, AMF). Therefore, the UE includes the S-NSSAI based on the allowed NSSAI and the corresponding S-NSSAI based on the information of the mapped NSSAI in the PDU session establishment request message and sends it.

[0116] To establish a new PDU session, the UE may create a new PDU session ID.

[0117] The UE may send a NAS message including a PDU Session Establishment Request message in the N1 SM information to start the PDU Session Establishment procedure initiated by the UE. The PDU Session Establishment Request message may include a request type, SSC mode, and protocol configuration options.

[0118] If the PDU session establishment is for setting up a new PDU session, the request type indicates "initial request". However, if there is an existing PDU session between the 3GPP access and the non-3GPP access, the request type may indicate "existing PDU session".

[0119] The NAS message sent by the UE is encapsulated in an N2 message by the AN. The N2 message is transmitted to the AMF and may include user location information and access technology type information.

[0120] -N1 SM information may include a SM PDU DN request container, which contains information for PDU session authentication by an external DN.

[0121] 2) If the message indicates that the request type is "initial request" and the PDU Session ID does not have an existing PDU Session for the UE, the AMF may determine that this is a request for a new PDU Session.

[0122] If the NAS message does not contain S-NSSAI, the AMF may determine the requested default S-NSSAI for the PDU session based on the UE joining. The AMF may correlate the PDU session ID and the SMF ID and store them.

[0123] AMF can select SMF.

[0124] 3) AMF can send a Nsmf_PDUSession_CreateSMContext request message or a Nsmf_PDUSession_UpdateSMContext request message to the selected SMF.

[0125] The Nsmf_PDUSession_CreateSMContext request message may include SUPI, DNN, S-NSSAI(s), PDU session ID, AMF ID, request type, PCF ID, priority access, N1 SM container, user location information, access type, PEI, GPSI, UE presence in LADN service area, join PDU session state notification, DNN selection mode and tracking requirements. The SM container may include the PDU session establishment request message.

[0126] The Nsmf_PDUSession_UpdateSMContext request message may include SUPI, DNN, S-NSSAI, SMContext ID, AMFID, request type, N1 SM container, user location information, access type, RAT type, and PEI. The N1 SM container may include a PDU session establishment request message.

[0127] The AMF ID is used to identify the AMF serving the UE. The N1 SM information may include a PDU session establishment request message received from the UE.

[0128] 4) SMF sends a user data request message to UDM. The joiner data request message may include the joiner permanent ID and DNN. UDM may send a join data response message to SMF.

[0129] In the above process 3, if the request type indicates "existing PDU session", the SMF determines that the request is caused by the handover between 3GPP access and non-3GPP access. The SMF can identify the existing PDU session according to the PDU session ID.

[0130] If the SMF has not retrieved the SM-related joining data for the UE related to the DNN, the SMF can request the joining data.

[0131] The joining data may include information about the authenticated request type, authenticated SSC mode, and basic QoS profile.

[0132] The SMF may confirm whether the UE request complies with the user joining and local policies. Alternatively, the SMF rejects the UE request through NAS SM signaling (including the relevant SM rejection cause) sent by the AMF, and the SMF notifies the AMF that the PDU Session ID should be considered to be released.

[0133] 5) SMF sends Nsmf_PDUSession_CreateSMContextResponse message or Nsmf_PDUSession_UpdateSMContextResponse message to AMF.

[0134] The Nsmf_PDUSession_CreateSMContextResponse message may include Cause, SM ContextID or N1 SM container. The N1 SM container may include PDU Session Reject.

[0135] In the above process 3, SMF receives the Nsmf_PDUSession_CreateSMContext request message. If SMF can process the PDU session establishment request message, it creates the SMF SM Context and passes the SM Context ID to AMF.

[0136] 6) Optionally perform secondary authentication / authorization.

[0137] 7a) If operating PCC is used for the PDU session, the SMF selects the PCF.

[0138] 7b) In order to establish an SM policy association with the PCF, the SMF performs the SM policy association establishment process.

[0139] 8) If the request type in process 3 indicates "initial request", the SMF selects the SSC mode for the PDU session. If process 5 is not performed, the SMF may also select the UPF. For request type IPv4 or IPv6, the SMF may allocate an IP address / prefix for the PDU session.

[0140] 9) SMF executes the SM policy association modification program and provides information on the triggering conditions for the policy control request.

[0141] 10) The request type indicates "initial request" and the SMF initiates the N4 session establishment procedure using the selected UPF. If not, the SMF can initiate the N4 session modification procedure using the selected UPF.

[0142] 10a) SMF sends N4 Session Establishment / Modification Request message to UPF. Also, SMF may provide packet detection, enforcement and reporting rules to be installed in UPF for PDU session. When SMF allocates CN tunnel information, CN tunnel information may be provided to UPF.

[0143] 10b) UPF sends N4 Session Establishment / Modification Response message so that it can respond. If CN tunnel information is allocated by UPF, CN tunnel information can be provided to SMF.

[0144] 11) SMF sends Namf_Communication_N1N2MessageTransfer message to AMF. The Namf_Communication_N1N2MessageTransfer message may include PDU session ID, N2 SM information and N1 SM container.

[0145] The N2 SM information may include PDU Session ID, QFI (QoS Flow ID), QoS Profile, CN Tunnel Information, S-NSSAI from allowed NSSAI, Session AMBR, PDU Session Type, User Plane Security Enforcement Information, UE Integrity Protection Maximum Data Rate.

[0146] The N1 SM container may include a PDU Session Establishment Accept message.

[0147] The PDU Session Establishment Accept message may include allowed QoS rules, SSC mode, S-NSSAI, and allocated IPv4 address.

[0148] 12) AMF sends N2 PDU Session Request message to RAN. This message may include N2 SM information and NAS message. NAS message may include PDU Session ID and PDU Session Establishment Accept message.

[0149] AMF may send a NAS message including PDU Session ID and PDU Session Establishment Accept message. In addition, AMF includes the received N2 SM information from SMF in the N2 PDU Session Request message and sends it to RAN.

[0150] 13) The RAN may perform specific signaling exchanges with the UE related to the information received from the SMF.

[0151] The RA also allocates RAN N3 tunnel information for the PDU session.

[0152] The RAN delivers the NAS message provided in process 10 to the UE. The NAS message may include the PDU session ID and N1 SM information. The N1 SM information may include a PDU session establishment accept message.

[0153] The RAN sends a NAS message to the UE only when the necessary RAN resources are set up and the allocation of the RAN tunnel information is successful.

[0154] 14) RAN sends an N2 PDU Session Response message to AMF. The message may include the PDU Session ID, cause, and N2 SM information. The N2 SM information may include the PDU Session ID, (AN) tunnel information, and a list of allowed / rejected QoS profiles.

[0155] -RAN tunnel information may belong to the access network address of the N3 tunnel corresponding to the PDU session.

[0156] 15) AMF may send a Nsmf_PDUSession_UpdateSMContext request message to SMF. The Nsmf_PDUSession_UpdateSMContext request message may include N2 SM information. AMF may send the N2 SM information received from RAN to SMF.

[0157] 16a) If the N4 session for the PDU session has not been established, the SMF may initiate the N4 session establishment procedure with the UPF. Otherwise, the SMF may initiate the N4 session modification procedure with the UPF. The SMF may provide the AN tunnel information and the CN tunnel information. The CN tunnel information needs to be provided only if the SMF selects the CN tunnel information in procedure 8.

[0158] 16b) UPF may send an N4 session modification response message to SMF.

[0159] 17) SMF sends Nsmf_PDUSession_UpdateSMContextResponse message to AMF.

[0160] After the process is completed, AMF can pass related events to SMF.

[0161] 18) SMF sends Nsmf_PDUSession_SMContextStatusNotify message.

[0162] 19) SMF sends information to UE through UPF. Specifically, for PDU type IPv6, SMF can create IPv6 router advertisement and transmit it to UE through N4 and UPF.

[0163] 20) If the PDU session establishment fails during this process, SMF notifies AMF.

[0164] Figure 6a and Figure 6b It shows the modification process of the PDU session.

[0165] MA PDU Session is established / managed based on the PDU Session Modification procedure.

[0166] The PDU session modification procedure may be initiated by the UE or by the network.

[0167] 1a) If initiated by the UE: The UE may initiate the PDU Session Modification procedure by sending a NAS message. The NAS message may include an N1 SM container. The N1 SM container may include a PDU Session Modification Request message, a PDU Session ID, and information about the UE's integrity protection (Integrity Protection) maximum data rate. The PDU Session Modification Request message may include the PDU Session ID, packet filters, for the requested QoS, 5GSM core network function, and the number of packet filters. The UE's integrity protection maximum data rate shows the maximum data rate that the UE can support for UP integrity protection. The number of packet filters indicates the number of packet filters supported for QoS rules.

[0168] The NAS message is sent to the appropriate AMF via the RAN based on the UE's location information. The AMF then sends the Nsmf_PDUSession_UpdateSMContext message to the SMF. The message may include the Session Management (SM) Context ID and the N1 SM container. The N1 SM container may include the PDU Session Modification Request message.

[0169] 1b) When initiated by PCF in the network node, PCF initiates the SM policy association modification process to notify the SMF of the policy change.

[0170] 1c) When initiated by UDM between network nodes, UDM updates SMF's join data by sending Nudm_SDM_Notification message. SMF can update session management joiner data and send ACK message to UDM.

[0171] 1d) SMF can trigger QoS updates when initiated by SMF in a network node.

[0172] When 1a to 1d above are triggered, SMF can perform the PDU session modification process.

[0173] 1e) When the AN resource to which the QoS flow is mapped is released when initiated by the AN in the network node, the AN can notify the SMF. The AN can send an N2 message to the AMF. The N2 message may include a PDU session ID and N2 SM information. The N2 SM information may include QFI (QoS flow ID), user location information, and an indication that the QoS flow is released. The AMF may send an Nsmf_PDUSession_UpdateSMContext message. The message may include an SM Context ID and N2 SM information.

[0174] 2) The above SMF sends a report on the join event by executing the SM Policy Partnership Modification process. This step can be skipped if the PDU Session Modification process is triggered by 1b or 1d. If dynamic PCC is not configured in the network, the SMF applies internal policies to determine the changes to the QoS profile.

[0175] Processes 3 to 7 described later may not be performed when the PDU session modification only requires the operation of the UPF.

[0176] 3a) When initiated by the UE or AN, the SMF may respond to the AMF by sending a Nsmf_PDUSession_UpdateSMContext message. The message may include N2 SM information and N2 SM container. The N2 SM information may include PDU session ID, QFI, QoS profile and session-AMBR. The N1 SM container may include a PDU session modification command. The PDU session modification command may include PDU session ID, QoS rules, QuS rule operations, QoS flow unit QoS parameters and session-AMBR.

[0177] The N2 SM information may include information to be sent by the AMF to the AN. The N2 SM information may include a QFI and a QoS profile to inform the AN that one or more QoS flows are added or modified. If a PDU session modification is requested by a UE that is not configured with user plane resources, the N2 SM information to be delivered to the AN may include information for the establishment of user plane resources.

[0178] The N1 SM container may include a PDU session modification command to be delivered by the AMF via the UE. The PDU session modification command may include QoS rules and QoS flow unit (level) QoS parameters.

[0179] 3b) When initiated by SMF, SMF may send Namf_Communication_N1N2MessageTransfer message. The message may include N2 SM information and N1 SM container. N2 SM information may include PDU session ID, QFI, QoS profile, session-AMBR. N1 SM container may include PDU session modification command. PDU session modification command may include PDU session ID, QoS rules and QoS flow unit (level) QoS parameters.

[0180] If the UE is in the CM-IDLE state and ATC is activated, after the AMF updates and stores the UE context based on the Namf_Communication_N1N2MessageTransfer message, processes 3 to 7 described later can be skipped. When the UE enters a reachable state, that is, when the UE enters the CM-CONNECTED state, the AMF can send an N1 message to synchronize the UE and the UE context.

[0181] 4) AMF may send an N2 PDU Session Request message to AN. The N2 PDU Session Request message may include the N2 SM information and NAS message received from SMF. The NAS message may include the PDU Session ID and N1 SM container. The N1 SM container may include a PDU Session Modification Command.

[0182] 5) AN performs AN signaling exchanges with the UE related to the information received from the SMF. For example, in the case of NG-RAN, in order to modify the required AN resources related to the PDU session, an RRC connection reconfiguration procedure (ConnectionReconfiguration) can be performed with the UE.

[0183] 6) The AN sends an N2 PDU Session ACK message in response to the received N2 PDU Session Request. The N2 PDU Session ACK message may include N2 SM information and user location information. The N2 SM information may include a list of accepted / rejected QFIs, AN tunnel information, and PDU Session ID.

[0184] 7) AMF sends the N2 SM information and user location information received from AN to SMF through the Nsmf_PDUSession_UpdateSMContext message. Then, SMF sends the Nsmf_PDUSession_UpdateSMContext message to AMF.

[0185] 8) SMF sends an N4 session modification request message to UPF to update the N4 session of UPF contained in the PDU session modification.

[0186] When a new QoS flow is created, the SMF works with the UPF to update the UL packet detection rules for the new QoS flow.

[0187] 9) The UE sends a NAS message in response to the received PDU Session Modification Command. The NAS message may include the PDU Session ID and the N1 SM container. The N1 SM container may include the PDU Session Modification Command ACK.

[0188] 10) AN sends the NAS message to AMF.

[0189] 11) AMF may send the N1 SM container and user location information received from AN to SMF via Nsmf_PDUSession_UpdateSMContext message. The N1 SM container may include PDU session modification command ACK. SMF may send Nsmf_PDUSession_UpdateSMContext response message to AMF.

[0190] 12) In order to update the N4 session of the UPF included in the PDU session modification, the SMF sends an N4 session modification request message to the UPF. The message may include the N4 session ID.

[0191] 13) When the SMF interacts with the PCF in the above process 1b or 2, the SMF can inform the PCF whether to execute the PCC decision through the SM policy association modification process.

[0192] The SMF may notify the requesting entity of user location information associated with the PDU session change.

[0193] A. Coordination or adjustment between 5GSM and ESM using the N26 interface a) The PDU Session Type of the PDU Session is mapped to the PDN Type of the default EPS bearer as follows.

[0194] a-1) If the PDU Session Type is "Unstructured", the PDN Type is set to "non-IP".

[0195] a-2) If the PDU Session Type is "IPv4", the PDN Type is set to "IPv4".

[0196] a-3) If the PDU Session Type is "IPv6", the PDN Type is set to "IPv6".

[0197] a-4) If the PDU Session Type is "IPv4v6", the PDN Type is set to "IPv4v6".

[0198] a-5) If the PDU Session Type is "Ethernet" and one of the UE and the network does not support Ethernet PDN type in S1 mode, or both the UE and the network do not support Ethernet PDN type in S1 mode, the PDN Type is set to "Non-IP".

[0199] a-6) If the PDU Session Type is "Ethernet" and both the UE and the network support Ethernet PDN type in S1 mode, the PDN type is set to "Ethernet".

[0200] b) The PDU address of the PDU session is mapped to the PDN address of the default EPS bearer as follows.

[0201] b-1) If the PDU Session Type is "IPv4", "IPv6" or "IPv4v6", the PDN Address of the Default EPS Bearer Context is set to the PDU Address of the PDU Session.

[0202] b-2) If the PDU Session Type is "Ethernet" or "Unstructured", the PDN Address of the Default EPS Bearer Context is set to 0 (zero).

[0203] B. PDU session type The following PDU session types can be supported.

[0204] IPv4; IPv6; IPv4v6; Ethernet (Ether Type as defined in IEEE Std 802.3 [31A]); and Unstructured.

[0205] C. Allocate IP addresses through NAS signaling If the UE requests an IP connection, the UE may set the PDU session type in the PDU session establishment request message as follows based on its own IP stack capability.

[0206] a) UE: 1) If IPv6 and IPv4 are available, the PDU session type can be set to IPv4, IPv6 or IPv4v6 according to the policy set or received by the UE.

[0207] 2) If only IPv6 is available, the PDU session type can be set to IPv6.

[0208] 3) If only IPv4 is available, the PDU session type can be set to IPv4.

[0209] b) If the IP version capability is not known within the UE (MT and TE are separated and the capabilities of TE are not notified to the MT), the UE may set the PDU session type to IPv4v6.

[0210] When the UE wishes to use DHCPv4 for IPv4 address allocation, the UE may notify the network using the Extended Protocol Configuration Option Information Element (IE) in the PDU Session Establishment Request message.

[0211] When a PDU session establishment request message is sent by the UE, in order to allocate an IP address, the network may consider the PDU session type, the network operator's policy and the UE's joining information.

[0212] a) When the network sets the Selected PDU Session Type IE to IPv4, the network may include an IPv4 address within the PDU Address IE.

[0213] b) When the network sets the Selected PDU Session Type IE to IPv6, the network may include the interface identifier for the IPv6 link-local address in the PDU Address IE.

[0214] c) If the network sets the Selected PDU Session Type IE to IPv4v6, the network may include the interface identifier for both the IPv4 address and the IPv6 link-local address in the PDU Address IE.

[0215] D UE requested PDU session establishment process D-1. Initiation of the PDU session establishment process requested by the UE In order to enable the UE to initiate the PDU session establishment procedure, the UE creates a PDU session establishment request message.

[0216] If the UE requests to establish a new emergency PDU session, the UE sets the PDU Session Type IE to IP Version Capability and includes it in the PDU Session Establishment Request message.

[0217] If the UE supports reflective QoS, the UE may set the RQoS bit to "Support Reflective QoS" in the 5GSM Capability IE in the PDU Session Establishment Request message.

[0218] a) The UE may request to establish a new PDU Session of type "IPv4", "IPv6", "IPv4v6" or "Ethernet".

[0219] b) the case where the UE requests to transfer to the 5GS an existing PDN connection within the EPS of “IPv4”, “IPv6”, “IPv4v6” or “Ethernet” PDN type, or an existing PDN connection within the EPS of “non-IP” PDN type mapped to “Ethernet” PDU drawing type; or, c) Request to transfer an existing PDN connection in an untrusted non-3GPP access connected to an EPC of PDN type “IPv4”, “IPv6” or “IPv4v6” to the 5GS.

[0220] D-2. When the PDU session establishment procedure requested by the UE is accepted by the network When a connection using the requested DN is accepted over the network, SMF creates a PDU Session Establishment Accept message.

[0221] The SMF sets the PDU session type IE selected in the PDU session establishment accept message to the selected PDU session type, that is, the PDU session type of the PDU session.

[0222] If the PDU SESSION SETUP REQUEST message includes the PDU SESSION TYPE IE set by "IPv4v6", the SMF may select "IPv4", "IPv6" or "IPv4v6" as the selected PDU SESSION TYPE. If the joiner information or SMF settings or both the joiner information and SMF settings are restricted to only IPv4 or only IPv6 for the DNN selected by the network, the SMF may include the 5GSM Cause value #50 "PDU Session Type IPv4 only allowed" or the 5GSM Cause value #51 "PDU Session Type IPv6 only allowed" in the 5GSM Cause IE in the PDU SESSION SETUP ACCEPT message, respectively.

[0223] If the selected PDU Session Type is "IPv4", the SMF may include the PDU Address IE in the PDU SESSION ESTABLISHMENT ACCEPT message and set the PDU Address IE to the IPv4 address allocated to the UE in the PDU session.

[0224] If the selected PDU Session Type is "IPv6", the SMF includes the PDU Address IE in the PDU Session Establishment Accept message and sets the PDU Address IE to the interface identifier of the IPv6 link-local address allocated to the UE in the PDU session.

[0225] If the selected PDU Session Type is "IPv4v6", the SMF includes the PDU Address IE in the PDU SESSION ESTABLISHMENT ACCEPT message and sets the PDU Address IE to the interface identifier of the IPv4 address allocated to the UE in the PDU session and the IPv6 link-local address allocated to the UE in the PDU session.

[0226] If the selected PDU Session Type is "IPv4", "IPv6", "IPv4v6" or "Ethernet" and the PDU SESSION SETUP REQUEST message includes a 5GSM Capability IE with the RQoS bit set by "Reflective QoS supported", it is assumed that the SMF supports reflective QoS for the QoS flows belonging to the PDU Session and an RQ Timer IE setting the RQ timer may be included in the PDU SESSION SETUP ACCEPT message.

[0227] If the selected PDU Session Type is "IPv4", "IPv6", "IPv4v6" or "Ethernet", and if the PDU Session Establishment Request message contains the maximum number of packet filters supported, the SMF may assume that this number is the maximum number of packet filters supported by the UE for this PDU Session. If not, the SMF may assume that the UE can support 16 packet filters for this PDU Session.

[0228] If the selected PDU session type is "Ethernet", the PDU session establishment request message includes a 5GSM function IE with an EPT-S1 bit set by "Support Ethernet PDN type in S1 mode", and the network supports Ethernet PDN type in S1 mode, the SMF may set the EPT-S1 bit of the 5GSM network feature support IE in the PDU session establishment accept message to "Support Ethernet PDN type in S1 mode".

[0229] D-3. When the PDU session establishment process requested by the UR is not accepted by the network If connection for the requested DN is rejected by the network, the SMF creates a PDU Session Establishment Reject message.

[0230] In order to notify the reason for rejecting the PDU session establishment, the SMF can set the 5GSM reason IE in the PDU session establishment reject message.

[0231] The 5GSM Cause IE can represent one of the following SM cause values.

[0232] #8: Operator determined barring #26: Insufficient resources #27: DNN is missing or unknown; #28: Unknown PDU session type; #29: User authentication or authorization failed #31: request rejected, unspecified #32: service option not supported; #33: requested service option not subscribed; #35: PTI in use; #38: Network failure; #39: Request reactivation; #50: PDU session type only allows IPv4; #51: PDU session type only allows IPv6; #54: PDU session does not exist; #57: Only PDU session type IPv4v6 is allowed; #58: Only allow untrusted PDU session types; #61: Only PDU session type Ethernet allowed; #67: Insufficient resources for specific slices and DNNs; #68: SSC mode is not supported; #69: Insufficient resources for specific slices; If the PDU Session Establishment Request message includes a PDU Session Type IE set to IPv6, and the Joiner Information or SMF Settings or both the Joiner Information and SMF Settings are restricted to IPv4 only for the requested DNN, the SMF may include a 5GSM Cause value #50 "Only PDU Session Type IPv4 allowed" in the 5GSM Cause IE in the PDU Session Establishment Reject message.

[0233] If the PDU Session Establishment Request message includes a PDU Session Type IE set to IPv6, and the Joiner Information or SMF Settings or both the Joiner Information and SMF Settings are restricted to unsupported "IPv4" PDU Session Type and "IPv6" PDU Session Type for the requested DNN, the SMF may include a 5GSM cause value #28 "Unknown PDU Session Type" in the 5GSM Cause IE in the PDU Session Establishment Reject message.

[0234] If the PDU SESSION ESTABLISHMENT REQUEST message includes a PDU SESSION TYPE IE set to "IPv4", and the joiner information or SMF settings or both the joiner information and SMF settings are restricted to allow only IPv6 for the requested DNN, the SMF sets the 5GSM cause value #51 "Only PDU Session Type IPv6 allowed" as the 5GSM cause IE in the PDU SESSION ESTABLISHMENT REJECT message.

[0235] If the PDU Session Establishment Request message includes a PDU Session Type IE set to "IPv4", and if the joiner information or the SMF settings or both the joiner information and the SMF settings do not support session type "IPv4" and session type "IPv6" for the requested DNN, the SMF may include a 5GSM cause value #28 "Unknown PDU Session Type" in the 5GSM cause IE of the PDU Session Establishment Reject message.

[0236] If the PDU Session Establishment Request message includes a PDU Session Type IE set to "IPv4v6", and if the joiner information or SMF settings or both the joiner information and SMF settings do not support a PDU Session Type of "IPv4v6" and a session type of "IPv4" as well as a PDU Session Type of "IPv6" for the requested DNN, the SMF may include a 5GSM cause value #28 "Unknown PDU Session Type" in the 5GSM Cause IE of the PDU Session Establishment Reject message.

[0237] If the PDU Session Establishment Request message includes a PDU Session Type IE set to "Unstructured" or "Ethernet", and the joiner information or SMF settings or both the joiner information and SMF settings do not support the requested PDU Session Type DNN, the SMF may include a 5GSM cause value #28 "Unknown PDU Session Type" in the 5GSM cause IE of the PDU Session Establishment Reject message.

[0238] If the PDU SESSION ESTABLISHMENT Request message is used to establish an MA PDU session, and the PDU SESSION ESTABLISHMENT Request message includes a PDU SESSION TYPE IE set to "Unstructured", and the SMF configuration does not support this PDU SESSION TYPE, then the SMF may include a 5GSM Cause value #28 "Unknown PDU SESSION TYPE" in the 5GSM Cause IE of the PDU SESSION ESTABLISHMENT REJECT message.

[0239] The network may include the Back-off timer value IE in the PDU Session Establishment Reject message.

[0240] If the 5GSM cause value is #50 "PDU session type IPv4 only allowed", #51 "PDU session type IPv6 only allowed", #57 "PDU session type IPv4v6 only allowed", #58 "PDU session type unstructured only allowed" or #61 "PDU session type Ethernet only allowed", the network may include a retry indicator without a backoff timer value in order to inform the UE that attempts to establish a PDU session in an identical PLMN in N1 mode using the same PDU session type for the same DNN and the same S-NSSAI are allowed.

[0241] The SMF may send a PDU Session Establishment Reject message.

[0242] When the PDU Session Establishment Reject message and the PDU Session ID are received through the NAS transmission process, the UE stops timer T3580 and releases the allocated PTI value. The PDU Session can be considered not established.

[0243] If the 5GSM cause value is #28 "Unknown PDU Session Type" and the PDU Session Establishment Request message includes a PDU Session IE indicating the PDU Session Type, the UE may ignore the Backoff Timer Value IE and Retry Indicator provided by the network. The UE may send other PDU Session Establishment Request messages in order to establish a new PDU Session using the PDU Session Type IE indicating a different PDU Session Type.

[0244] If the 5GSM cause value is #50 "Only PDU Session Type IPv4 allowed", #51 "Only PDU Session Type IPv6 allowed", #57 "Only PDU Session Type IPv4v6 allowed" or #58 "Only PDU Session Type Unstructured allowed" or #61 "Only Ethernet PDU Session Type allowed", the UE may ignore the Backoff Timer Value IE provided by the network. The UE may evaluate the available USRP rules. Until one of the following conditions is met, the UE shall not immediately send other PDU Session Establishment Request messages for the same DNN and the same HPLMNS-NSSAI in order to obtain a PDU Session Type other than that allowed by the network.

[0245] a) At the time of receiving the PDU Session Establishment Reject message, the US is registered with a new PLMN which is not listed in the Equivalent PLMN List; b) at the time of receiving the PDU SESSION SETUP REJECT message, the US is registered in a new PLMN present in the Equivalent PLMN List and the network does not include a retry indicator in the PDU SESSION SETUP REJECT message, or the network does not include a retry indicator indicating that retries are allowed in the Equivalent PLMN in the message; c) When the UE is powered off, or d) when it is removed by the universal subscriber identity module (USIM), or if the UE does not support access in the SNPN, so that the entry in the "Subscriber Data List" of the current SNPN is updated, or when the UE supports access in the SNPN but the entry in the "Subscriber Data List" is updated.

[0246] For 5GSM cause value #50 "Only PDU session type IPv4 allowed", 5GSM cause value #51 "Only PDU session type IPv6 allowed", 5GSM cause value #57 "Only PDU session type IPv4v6 allowed", 5GSM cause value #58 "PDU only unstructured session type allowed" and 5GSM cause value #61 "Only Ethernet PDU session type allowed", the UE can ignore the value of the RATC bit in the Retry Indicator IE provided by the network.

[0247] <Time-Sensitive Networking (TSN)> On the other hand, the time-sensitive network TSN will be described.

[0248] In the future ultra-connected intelligent information society of the fourth industrial revolution and 5G mobile communications, ultra-low latency (URLLC; Ultra Reliable Low Latency Communications) network technology, which is used to organically connect people and objects, online and offline, etc. to exchange and process information, is becoming a necessary technology based on network infrastructure. As a result, 3GPP is also actively accommodating the challenging requirements of vertical industry fields, and is developing research on the Industrial Internet of Things (IioT) centered on automation to maximize the productivity and profitability of industry through changes in communication infrastructure. In particular, task-oriented industries such as smart factories, smart grids, and smart traffic systems require ultra-reliable and low-latency communication performance at the wired infrastructure level, so new technologies to support them are reflected in the standards.

[0249] IEEE TSN technology has emerged to realize the Industrial Internet of Things (IIoT) that connects multiple devices and systems in these industrial sites. IEEE TSN technology is considered to be the next-generation industrial network standard that can accommodate most network application examples of Ethernet by combining multiple existing IEEE standards into one packet technology. In 3GPP, 5G-TSN technology is vigorously promoted for standardization after Rel-16 for the vertical field diffusion of 5G technology. 5G-TSN technology is a technology that basically integrates IEEE TSN technology into 5G system (5GS; 5G system), and is a time-sensitive communication technology (Time-Sensitive Communications, TSC) that defines and supports various IIoT service requirements. In TSC, 5GS and TSN basically go through the time synchronization process. After that, TSC QoS Flow based on TSC assistance information is supported.

[0250] Figure 7 is a diagram showing an example of a network architecture that interoperates with a TSN network.

[0251] Reference Figure 7 , the 5G system can communicate with the TSN bridge through the external network. The logical TSN bridge may include TSN translation functionality for the user plane and control plane to interoperate between the 5GS system and the TSN system. The 5GS TSN translation function may include a device-side TSN translator (DS-TT) and a network-side TSN translator (NW-TT). TSNAF is part of 5GC and can provide control plane translation functions that will integrate 5GS and TSN. In 5GC and RAN, processes, wireless communication links, etc. that are characteristics of the 5G system may not be visible in the TSN network. 5GS provides TSN input (ingress) ports and output (egress) ports through DS-TT and NW-TT.

[0252] In order to discover the Ethernet device connected to the DS-TT, the DS-TT may support the link layer connection retrieval and reporting. In order to discover the Ethernet device connected to the NW-TT, the NW-TT may also support the link layer connection retrieval and reporting. If the DS-TT does not support the link layer connection retrieval and reporting, the NW-TT performs the link layer connection retrieval and reporting instead of the DS-TT, so that the Ethernet device connected to the DS-TT can be retrieved.

[0253] Figure 8 is an example diagram illustrating an architecture that supports time-sensitive communications and time synchronization services.

[0254] Reference Figure 8 , in order to support time synchronization services for Ethernet or IP type sessions, DS-TT, NW-TT and Time Sensitive Communication and Time Synchronization Function (TSCTSF) are shown. NEF provides 5GS capability information to support time synchronization services. TSCTSF controls DS-TT and NW-TT.

[0255] UPF / NW-TT transmits (g)PTP messages.

[0256] When the UPF supports more than one NW-TT, there can be a one-to-one association between the NW-TT and the network instance or a one-to-one association between the NW-TT and the network instance together with the DNN / S-NSSAI in the UPF. When there are multiple network instances in the UPF, each network instance can be considered to be logically separate.

[0257] <Deterministic Networking (Det Net) The deterministic network DetNet technology being developed by the IETF DetNet WG is a technology that expands the application scope of Ethernet TSN technology (Layer 2 technology) and integrates with IP and MPLS basic networks (Layer 3 technology). Ultimately, DetNet technology refers to the technology that supports the extension of Ethernet TSN technology (Layer 2 technology) to IP technology (Layer 3 technology). In 3GPP, in order to support IETF DetNet technology from Rel-18 to 5GS, the TSC framework extension technology is reflected in the standard.

[0258] There are five common traffic PDU session types in the current 3GPP 5GS (5G system): IPv4, IPv6, IPv4v6, Ethernet (IEEE Std 802.3) and unstructured types. When setting up a PDU session, the terminal sets a type in IPv4, IPv6, IPv4v6, Ethernet (IEEE Std 802.3) or unstructured type according to the terminal configuration or application support, and includes it in the PDU session type IE of the PDU session establishment request message and sends it to the network.

[0259] However, from the perspective of the IP layer (Layer 3) of TSN traffic, i.e., PDU session, there is no way to differentiate TSN traffic and process it according to QoS and application service requirements.

[0260] In summary, in order to be able to distinguish TSN traffic at the IP layer (Layer 3) of these TSN traffic, that is, from the perspective of PDU session, it is necessary to newly define new PDU session types for TSN traffic and / or new capability information for TSN traffic.

[0261] <Disclosure of this specification> Therefore, one disclosure of this specification is to propose to newly add a new PDU session type for TSN traffic and / or new capability information for TSN traffic.

[0262] Specifically, according to a disclosure of this specification, when a terminal sends a PDU session establishment request message to a network (ie, SMF), in order to be able to recognize and distinguish between general traffic and other sessions for industrial traffic, the PDU session type can be set to TSN, TSC, DetNet, URLLC or IIoT before sending. Therefore, the network (SMF) recognizes general traffic and other industrial traffic, and distinguishes them from the others to carry out the relevant QoS and session establishment process.

[0263] General traffic and other industrial traffic may refer to time-sensitive / deterministic or Ultra-Reliable Low Latency Communication (URLLC) or Industrial IoT (Internet of Things), IIoT or time-sensitive Communication (TSC) traffic or traffic related to sessions.

[0264] Fig. 9is an exemplary diagram showing a process according to one disclosure of the present specification.

[0265] Reference Fig. 9 According to a disclosure of this specification, the UE may send a PDU session establishment request message including a PDU session type of TSN, TSC, DetNet, URLLC or notification IIoT.

[0266] At this time, if the network does not support the PDU session type used for general traffic and other industrial traffic, the SMF can send a PDU session establishment reject message.

[0267] If the network does not support the PDU session type for general traffic and other industrial traffic, according to one disclosure of this specification, the PDU session establishment reject message may include #28 unknown PDU session type reject cause as a cause value.

[0268] In addition, if the network only supports TSN (or DetNet) PDU session type, while rejecting the terminal request, a new cause value, such as #xy: only allowed PDU session type TSN (or DetNet) is included in the PDU session establishment reject message and sent.

[0269] At this time, the terminal receiving the rejection message can send a PDU session setting request message to the network to request setting of other PDU session types.

[0270] General traffic and other industrial traffic may refer to time-sensitive / deterministic or Ultra-Reliable Low Latency Communication (URLLC) or Industrial IoT (Internet of Things), IIoT or Time-sensitive Communication (TSC) traffic or traffic related to the session. In addition, the new cause value may mean #xy: Only PDU session type TSN (or DetNet, IIoT, URLLC, TSC) is allowed.

[0271] I. Improvements in coordination or adjustment between 5GSM and ESM using the N26 interface a) The PDU Session Type of the PDU Session is mapped to the PDN Type of the default EPS bearer as follows.

[0272] a-1) If the PDU Session Type is "Unstructured", the PDN Type is set to "Non-IP".

[0273] a-2) If the PDU Session Type is "IPv4", the PDN Type is set to "IPv4".

[0274] a-3) If the PDU Session Type is "IPv6", the PDN Type is set to "IPv6".

[0275] a-4) If the PDU Session Type is "IPv4v6", the PDN Type is set to "IPv4v6".

[0276] a-5) If the PDU Session Type is "Ethernet" and either the UE or the network does not support Ethernet PDN type in S1 mode, or neither the UE nor the network supports Ethernet PDN type in S1 mode, the PDN Type is set to "Non-IP".

[0277] a-6) If the PDU Session Type is "Ethernet" and both the UE and the network support Ethernet PDN type in S1 mode, the PDN type is set to "Ethernet".

[0278] a-7) If the PDU Session Type is for general traffic and other industrial traffic, and the UE and the network support the PDU Session Type in S1 mode, the PDU Session Type can be set to TSN, TSC DetNet, URLLC or IIoT. General traffic and other industrial traffic can refer to time-sensitive / deterministic or Ultra-Reliable Low Latency Communication (URLLC) or Industrial IoT (Internet of Things), IIoT or time-sensitive Communication (TSC) traffic or traffic of related sessions.

[0279] b) The PDU address of the PDU session is mapped to the PDN address of the default EPS bearer as follows.

[0280] b-1) If the PDU Session Type is "IPv4", "IPv6" or "IPv4v6", the PDN Address of the Default EPS Bearer Context is set to the PDU Address of the PDU Session.

[0281] b-2) If the PDU Session Type is "Ethernet", the PDU Session Type is TSN, TSC, DetNet, URLLC or IIoT, or the PDU Session Type is "Unstructured", the PDN Address of the Default EPS Bearer Context is set to 0 (zero).

[0282] II. Improvements to PDU Session Type The following PDU session types can be supported.

[0283] IPv4; IPv6; IPv4v6; Ethernet (Ether Type as defined in IEEE Std 802.3[31A]); and Unstructured.

[0284] TSN, TSC, DetNet, URLLC or IIoT III. Improvements to the PDN session establishment process when the UE request is not accepted by the network If the connection for the requested DN is rejected by the network, the SMF creates a PDU Session Establishment Reject message.

[0285] In order to notify the reason for rejecting the PDU session establishment, SMF can set the 5GSM reason IE in the PDU session establishment reject message.

[0286] The 5GSM Cause IE can represent one of the following SM cause values.

[0287] #8: Operator determined barring #26: Insufficient resources #27: DNN is missing or unknown; #28: Unknown PDU session type; #29: User authentication or authorization failed #31: request rejected, unspecified #32: service option not supported; #33: requested service option not subscribed; #35: PTI in use; #38: Network failure; #39: Request reactivation; #50: PDU session type only allows IPv4; #51: PDU session type only allows IPv6; #54: PDU session does not exist; #57: Only PDU session type IPv4v6 is allowed; #58: Only allow untrusted PDU session types; #61: Only PDU session type Ethernet allowed; #xy: only allowed PDU session type TSN (or TSC, DetNet, URLLC, IIoT); #67: Insufficient resources for specific slices and DNNs; #68: SSC mode is not supported; #69: Insufficient resources for specific slices; If the PDU Session Establishment Request message includes a PDU Session Type IE set to "Unstructured", the PDU Session Establishment Request message includes a PDU Session Type IE set to TSN, TSC, DetNet, URLLC or IIoT, or the PDU Session Establishment Request message includes a PDU Session Type IE set to "Ethernet", and the joiner information or SMF settings or both the joiner information and SMF settings do not support the PDU Session Type for the requested DNN, the SMF may include a 5GSM cause value #28 "Unknown PDU Session Type" in the 5GSM cause IE of the PDU Session Establishment Reject message.

[0288] If the 5GSM cause value is #50 "Only PDU Session Type IPv4 allowed", #51 "Only PDU Session Type IPv6 allowed", #57 "Only PDU Session Type IPv4v6 allowed", #58 "Only PDU Session Type Unstructured allowed", #xy Only PDU Session Type TSN (or TSC, DetNet, URLLC, IIoT) allowed or #61 "Only PDU Session Type Ethernet allowed", the network may include a retry indicator without a backoff timer value in order to inform the UE that attempts to establish a PDU session in the same PLMN in N1 mode using the same PDU session type for the same DNN and the same S-NSSAI are allowed.

[0289] SMF sends a PDU session establishment reject message.

[0290] The UE may then receive a PDU session establishment reject message.

[0291] If the 5GSM cause value is #50 "Only PDU session type IPv4 allowed", #51 "Only PDU session type IPv6 allowed", #57 "Only PDU session type IPv4v6 allowed", #58 "Only PDU session type unstructured allowed", #xy Only PDU session type TSN (or TSC, DetNet, URLLC, IIoT) allowed, or #61 "Only PDU session type Ethernet allowed", the UE may ignore the Back-off Timer Value IE provided by the network.

[0292] For 5GSM cause values ​​#50 "Only PDU session type IPv4 allowed", #51 "Only PDU session type IPv6 allowed", #57 "Only PDU session type IPv4v6 allowed", #58 "Only PDU session type unstructured allowed", #xy Only PDU session type TSN (or TSC, DetNet, URLLC, IIoT) allowed and #61 "Only PDU session type Ethernet allowed", the UE may ignore the value of the RATC bit in the Retry Indicator IE provided by the network.

[0293] Fig.10 is an exemplary diagram illustrating another process according to a disclosure of the present specification.

[0294] On the one hand, in order to recognize and distinguish general traffic from other industrial traffic, the terminal, i.e., UE, can attach the PDU session type representing TSN, TSC, DetNet, URLLC or IIoT and the traffic-related capability indication / information separately or together to the 5GSM capability IE (Information Element) or extended protocol configuration option IE or new IE of the PDU session establishment request message and send it to the network.

[0295] Alternatively, the terminal, ie, the UE, may include the capability indication / information related to the industrial traffic in an additional information IE or a new IE of the UL NASTRANSPORT message and send the result to the network.

[0296] Alternatively, the terminal, i.e., the UE, may include capability indication / information related to industrial traffic in a 5GMM capability IE or a new IE of a registration request message and send it to the network.

[0297] General traffic and other industrial traffic may refer to time-sensitive / deterministic or Ultra-Reliable Low Latency Communication (URLLC) or Industrial IoT (Internet of Things), IIoT or time-sensitive Communication (TSC) traffic or traffic related to sessions.

[0298] On the one hand, the above disclosure of the present invention is applicable regardless of the capability, indication or configuration of the terminal UE 100. The capability, indication or configuration may refer to the terminal, that is, the UE can support / operate capability, indication or setting TSN (or DetNet), time-sensitive / deterministic, Ultra-Reliable Low Latency Communication (URLLC), Industrial IoT (Internet of Things), IIoT or time-sensitive Communication (TSC).

[0299] In addition, the terminal, i.e., UE 100, is configured with TSN (or DetNet), time-sensitive / deterministic, ultra-reliable low latency communication (URLLC), industrial IoT (Internet of Things), IIoT, or time-sensitive communication (TSC), or a terminal having corresponding capabilities, i.e., UE performs / operates TSN (or DetNet), time-sensitive / deterministic, ultra-reliable low latency communication (URLLC), industrial IoT (Internet of Things), IIoT, or time-sensitive communication (TSC) or receives or sends corresponding services / traffic, and a terminal having such settings or capabilities, i.e., UE, can apply / operate the above-mentioned disclosure of this specification.

[0300] At this time, according to the subscriber information or the operator and network policy, UE 100 is set to TSN (or DetNet), time-sensitive / deterministic, ultra-reliable low latency communication (URLLC), Industrial IoT (Internet of Things), IIoT or time-sensitive communication (TSC), or has corresponding capabilities.

[0301] The corresponding TSN (or DetNet), time-sensitive / deterministic, Ultra-Reliable Low Latency Communication (URLLC), Industrial IoT (Internet of Things), IIoT or Time-sensitive Communication (TSC) settings or capability information can be pre-configured in the terminal, i.e., UE (U) SIM, or received from the network (Core Network, CN). The network CN can refer to the Access and Mobility Management Function (AMF) or Session Management Function (SMF) of the 5G mobile communication network.

[0302] In addition, the network includes the above-mentioned settings or capability information / indications in the 5GS network feature support IE (Information Element) or a new IE (Information Element) of the registration acceptance message and provides it to the terminal for setting.

[0303] In addition, the network includes the above-mentioned setting or capability information / indication in a new IE (Information Element) of the configuration update command message and provides it to the terminal, that is, the UE, and performs setting.

[0304] In addition, the network includes the above-mentioned setting or capability information / indication in an additional information IE (Information Element) or a new IE (Information Element) of the DL NAS TRANSPORT message and provides it to the terminal, that is, the UE, and performs setting.

[0305] In addition, the network includes the above-mentioned setting or capability information / indication in a management object (MO) and provides it to the terminal, that is, UE, and performs settings.

[0306] Hereinafter, a device to which the disclosure of this specification as described above can be applied will be described.

[0307] Fig.11 is a block diagram showing the configuration of a processor that implements the disclosure of this specification.

[0308] refer to Fig.11It can be seen that the processor 1020 that implements the disclosure of this specification may include multiple circuits to implement the functions, processes and / or methods described and proposed in this specification. For example, the processor 1020 may include a first circuit 1020-1, a second circuit 1020-2, and a third circuit 1020-3. In addition, although not shown, the processor 1020 may also include more circuits. Each circuit may include multiple transistors.

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

[0310] The processor may be installed in the UE.

[0311] The first processor circuit (1020-1) installed on the UE is The second processor circuit (1020-2) installed on the UE is The third processor circuit (1020-3) installed on the UE is Fig.12 FIG. 2 is a diagram showing a wireless communication system according to an embodiment.

[0312] Reference Fig.12 , a wireless communication system may include a first device 100a and a second device 100b.

[0313] The first device 100a may be a UE described in the disclosure of this specification. Alternatively, the first device 100a may be a base station, a network node, a sending UE, a receiving UE, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, an unmanned aerial vehicle (UAV), an artificial intelligence (AI) module, a robot, an augmented reality (AR) device, a virtual reality (VR) device, a mixed reality (MR) device, a holographic device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, a device related to 5G services, or other devices related to the field of the fourth industrial revolution.

[0314] The second device 100b may be a network node (e.g., AMF or MME) described in the disclosure of this specification. Alternatively, the second device 100b may be a base station, a network node, a sending UE, a receiving UE, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, an unmanned aerial vehicle (UAV), an artificial intelligence (AI) module, a robot, an augmented reality (AR) device, a virtual reality (VR) device, a mixed reality (MR) device, a holographic device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, a device related to 5G services, or other devices related to the field of the fourth industrial revolution.

[0315] For example, UE 100 may be a mobile phone, a smart phone, a laptop computer, a digital broadcast UE device, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation, a slate PC, a tablet PC, an ultrabook, a wearable device (e.g., a smartwatch, a smart glass), a head mounted display (HMD), etc. For example, the HMD may be a display device worn on the head. For example, the HMD may be used to implement VR, AR, or MR.

[0316] For example, a drone may be a flying object that flies by radio control signals without human piloting. For example, a VR device may include a device that realizes an object or background in a virtual world, etc. For example, an AR device may include a device that connects an object or background in a virtual world to an object or background in a real world, etc. and realizes it. For example, an MR device may include a device that merges an object or background in a virtual world into an object or background in a real world, etc. and realizes it. For example, a holographic device may include a device that uses holography, which is an interference phenomenon of light that occurs when two lasers meet, to record and reproduce three-dimensional information to realize a 360-degree stereoscopic image. For example, a public safety device may include a live video device or a video device that can be worn on a user, etc. For example, an MTC device and an IoT device may be a device that does not require direct human intervention or manipulation. For example, an MTC device and an IoT device may include a smart meter, a bending machine, a thermometer, a smart light bulb, a door lock, or various sensors, etc. For example, a medical device may be a device that is intended to diagnose, treat, alleviate, treat, or prevent a disease. For example, a medical device may be a device that is intended to diagnose, treat, alleviate, or correct an injury or disability. For example, a medical device may be a device that is intended to inspect, replace, or deform a structure or function. For example, a medical device may be a device that is intended to regulate pregnancy. For example, a medical device may include a diagnostic device, a surgical device, an (in vitro) diagnostic device, a hearing aid or a surgical device. For example, a security device may be a device installed to prevent possible risks and maintain safety. For example, a security device may be a camera, CCTV, a recorder or a black box. For example, a fintech device may be a device that can provide financial services such as mobile payments. For example, a fintech device may include a payment device or a point of sales (POS). For example, a climate / environmental device may include a device that monitors or predicts the climate / environment.

[0317] The first device 100a may include at least one processor (such as processor 1020a), at least one memory (such as memory 1010a) and at least one transceiver (such as transceiver 1031a). Processor 1020a can perform the above functions, processes and / or methods. Processor 1020a can execute one or more protocols. For example, processor 1020a can execute one or more layers of a wireless interface protocol. Memory 1010a is connected to processor 1020a and can store various types of information and / or commands. Transceiver 1031a is connected to processor 1020a and can be controlled to send and receive wireless signals.

[0318] The second device 100b may include at least one processor (such as processor 1020b), at least one memory device (such as memory 1010b) and at least one transceiver (such as transceiver 1031b). Processor 1020b can perform the above functions, processes and / or methods. Processor 1020b can implement one or more protocols. For example, processor 1020b can implement one or more layers of a wireless interface protocol. Memory 1010b is connected to processor 1020b and can store various types of information and / or commands. Transceiver 1031b is connected to processor 1020b and can be controlled to send and receive wireless signals.

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

[0320] 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.

[0321] Fig.13 is a block diagram illustrating a network node according to an embodiment.

[0322] Specifically, Fig.13 The diagram shows in detail a case where a base station is divided into a central unit (CU) and a distributed unit (DU).

[0323] Reference Fig.13 , base stations W20, W30 can be connected to the core network W10, and base station W30 can be connected to the adjacent base station W20. For example, the interface between base stations W20, W30 and the core network W10 can be called NG, and the interface between base station W30 and the adjacent base station W20 can be called Xn.

[0324] The base station W30 can be divided into CU W32 and DU W34, W36. That is, the base station W30 can be separated and operated by layers. CUW32 can be connected to one or more DU W34, W36, for example, the interface between CU W32 and DU W34, W36 can be called F1. CU W32 can perform the functions of the upper layers of the base station, and DU W34, W36 can perform the functions of the lower layers of the base station. For example, CU W32 can be a logical node of the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) layers of the hosting base station (e.g., gNB), and DU W34, W36 can be a logical node of the radio link control (RLC), media access control (MAC), and physical (PHY) layers of the hosting base station. Alternatively, CU W32 may be a logical node hosting the RRC and PDCP layers of a base station (e.g., en-gNB).

[0325] The operation of DU W34, W36 can be partially controlled by CU W32. One DU W34, W36 can support one or more cells. One cell can only be supported by one DU W34, W36. One DU W34, W36 can be connected to one CU W32, and through appropriate implementation one DU W34, W36 can be connected to multiple CUs.

[0326] Fig.14 is a block diagram showing the configuration of UE 100 according to an embodiment.

[0327] especially, Fig.14 The UE 100 shown in FIG. 1 is a more detailed view of the above Fig.13 Figure 1 of the first device.

[0328] UE 100 includes a memory 1010 , a processor 1020 , a transceiver unit 1031 , a power management module 1091 , a battery 1092 , a display 1041 , an input unit 1053 , a speaker 1042 , a microphone ( 1052 ), a subscriber identification module (SIM) card, and one or more antennas.

[0329] The processor 1020 may be configured to implement the functions, processes and / or methods described and suggested in this specification. The layers of the wireless interface protocol may be implemented in the processor 1020. The processor 1020 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits and / or data processing devices. 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, Modem). An example of the processor 1020 may be a processor provided by Qualcomm ® SNAPDRAGON™ series processors manufactured by Samsung ® EXYNOSTM series processors manufactured by Apple ® A series processors manufactured by MediaTek ® HELIO™ series processors manufactured by INTEL ® ATOM™ series processors or corresponding next-generation processors manufactured by .

[0330] The power management module 1091 manages the power of the processor 1020 and / or the transceiver unit 1031. The battery 1092 supplies power to the power management module 1091. The display 1041 outputs the results processed by the processor 1020. The input unit 1053 receives input to be used by the processor 1020. The input unit 1053 can be displayed on the display 1041. The SIM card is an integrated circuit for identifying the international mobile subscriber identity (IMSI) and securely storing the keys associated with it in mobile devices such as mobile phones and computers to identify subscribers and perform authentication. Contact information can also be stored in multiple SIM cards.

[0331] The memory 1010 is operably coupled to the processor 1020 and stores various information for operating the processor 610. The memory 1010 may include a read-only memory (ROM), a random access memory (RAM), a flash memory, a memory card, a storage medium, and / or other storage devices. When the embodiment is implemented by software, the technology described in this specification may be implemented by a module (e.g., a process, a function, etc.) that performs the functions described in this specification. The module may be stored in the memory 1010 and executed by the processor 1020. The memory 1010 may be implemented within the processor 1020. Alternatively, the memory 1010 may be implemented outside the processor 1020 and may be communicatively connected to the processor 1020 by various means known in the art.

[0332] The transceiver unit 1031 is operably coupled to the processor 1020 and sends and / or receives wireless signals. The transceiver unit 1031 includes a transmitter and a receiver. The transceiver unit 1031 may include a baseband circuit for processing wireless frequency signals. The transceiver unit controls one or more antennas to send and / or receive wireless signals. The processor 1020 communicates command information to the transceiver unit 1031 in order to initiate communication, for example, to send a wireless signal constituting voice communication data. The function of the antenna is to send and receive wireless signals. When receiving a wireless signal, the transceiver unit 1031 can transmit the signal and convert the signal to baseband in order to be processed by the processor 1020. The processed signal can be converted into audible or readable information output through the speaker 1042.

[0333] Speaker 1042 outputs sound related results processed by processor 1020. Microphone 1052 receives sound related input to be used by processor 1020.

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

[0335] Fig.15 It is shown in Fig.12 The transceiver unit of the first device shown in FIG. Fig.14 A block diagram of the transceiver unit of the device shown.

[0336] Reference Fig.15 , the transceiver unit 1031 includes a transmitter 1031-1 and a receiver 1031-2. The transmitter 1031-1 includes a discrete Fourier transform (DFT) unit 1031-11, a subcarrier mapper 1031-12, an IFFT unit 1031-13, a CP insertion unit 1031-14, and a wireless transmission unit 1031-15. The transmitter 1031-1 may also include a modulator. In addition, for example, a scramble unit (not shown), a modulation mapper (not shown), a layer mapper (not shown), and a layer permutator (not shown) may also be included, which may be set before the DFT unit 1031-11. That is, in order to prevent the increase of the peak-to-average power ratio (PAPR), the transmitter 1031-1 first passes the signal through the DFT 1031-11 before mapping the signal to the subcarrier. The signal spread (or precoded in the same sense) by the DFT unit 1031 - 11 is mapped to subcarriers by the subcarrier mapper 1031 - 12 , and then passes through the Inverse Fast Fourier Transform (IFFT) unit 1031 - 12 again to create a signal on the time axis.

[0337] The DFT unit 1031-11 performs DFT on the input symbol and outputs a complex-valued symbol. For example, if Ntx symbols (where Ntx is a natural number) are input, the DFT size is Ntx. The DFT unit 1031-11 may be referred to as a transform precoder. The subcarrier mapper 1031-12 maps the complex-valued symbols to each subcarrier in the frequency domain. The complex-valued symbols may be mapped to resource elements corresponding to resource blocks allocated for data transmission. The subcarrier mapper 1031-12 may be referred to as a resource element mapper. The IFFT unit 1031-13 performs IFFT on the input symbol and outputs a baseband signal of the data as a time domain signal. The CP insertion unit 1031-14 copies a portion of the rear portion of the baseband signal for data and inserts it into the front portion of the baseband signal for data. By inserting CP, inter-symbol interference (ISI) and inter-carrier interference (ICI) can be prevented, thereby maintaining orthogonality even in a multipath channel.

[0338] On the other hand, the receiver 1031-2 includes a wireless receiving unit 1031-21, a CP removal unit 1031-22, an FFT unit 1031-23, an equalization unit 1031-24, etc. The wireless receiving unit 1031-21, the CP removal unit 1031-22, and the FFT unit 1031-23 of the receiver 1031-2 perform the inverse functions of the wireless transmitting unit 1031-15, the CP insertion unit 1031-14, and the IFF unit 1031-13 in the transmitting end 1031-1. The receiver 1031-2 may also include a demodulator.

[0339] <Scenarios to which this specification is applicable> Although not limited thereto, the various descriptions, functions, processes, suggestions, methods and / or operational flowcharts disclosed herein of the present specification may be applicable to a variety of fields requiring wireless communication / connection (e.g., 5G) between devices.

[0340] In the following, more detailed examples will be provided with reference to the accompanying drawings. In the following drawings / descriptions, unless otherwise specified, the same reference numerals represent the same or corresponding hardware blocks, software blocks or functional blocks.

[0341] Fig.16 1 is a diagram showing a communication system 1 applicable to the disclosure of this specification.

[0342] Reference Fig.16, the disclosed communication system 1 applicable to the present specification includes a wireless device, a base station and a network. Among them, the wireless device refers to a device that performs communication using a wireless access technology (such as 5GNR (new RAT), Long Term Evolution (LTE)), and is called a communication / wireless / 5G device. Although not limited to this, the wireless device may include a robot 100a, a vehicle 100b-1, 100b-2, an eXtended Reality (XR) device 100c, a handheld device (Hand-held device) 100d, a home appliance 100e, an Internet of Things (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 driving vehicle, a vehicle capable of inter-vehicle communication, etc. Among them, the vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). XR devices include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices, and can be embodied in the form of head-mounted devices (HMD), head-up displays (HUD) equipped in vehicles, televisions, smart phones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Mobile devices may include smart phones, smart pads, wearable devices (e.g., smart watches, smart glasses), computers (e.g., laptops, etc.), etc. Home appliances may include televisions, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, base stations and networks may also be implemented through wireless devices. A specific wireless device 200a may operate as a base station / network node for other wireless devices.

[0343] The wireless devices 100a~100f can be connected to the network 300 through the base station 200. Artificial Intelligence (AI) technology can be applied to the wireless devices 100a~100f, and the wireless devices 100a~100f can be connected to the AI ​​server 400 through the network 300. The network 300 can be formed using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices 100a~100f can communicate with each other through the base station 200 / network 300, but can also communicate directly (e.g., sidelink communication) without passing through the base station / network. For example, vehicles 100b-1, 100b-2 can communicate directly (e.g., vehicle to vehicle (V2V) / vehicle to everything (V2X) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices 100a~100f.

[0344] Wireless devices 100a~100f / base station 200, base station 200 / base station 200 can establish wireless communication / connection 150a, 150b, 150c. Among them, the wireless communication / connection can be established through various wireless access technologies (for example, 5GNR) such as uplink / downlink communication 150a and side link communication 150b (or, D2D communication), communication between base stations 150c (for example, relay, Integrated Access Backhaul (IAB)), etc. Through wireless communication / connection 150a, 150b, 150c, wireless devices and base stations / wireless devices, and base stations and base stations can send / receive wireless signals to each other. For example, wireless communication / connection 150a, 150b, 150c can send / receive signals through various physical channels. To this end, based on the various suggestions disclosed in this specification, at least a part of various configuration information setting processes for sending / receiving wireless signals, various signal processing processes (for example, channel coding / decoding, modulation / demodulation, resource mapping / demapping, etc.) and resource allocation processes can be performed.

[0345] The above is an exemplary description through preferred embodiments, but the disclosure of this specification is not limited to such specific embodiments. Therefore, it can be modified, changed or improved in various forms within the scope of the concept of this specification and the scope of the claims.

[0346] In the above exemplary system, the method is described as a series of steps or boxes based on the flowchart, but the order of the steps described is not limited, and as mentioned above, some steps can occur in other orders or at the same time as other steps. In addition, those skilled in the art will understand that the steps shown in the flowchart are not exclusive, and other steps may be included or one or more steps in the flowchart may be deleted without affecting the scope of the rights.

[0347] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to implement an apparatus, and the technical features of the device claims of this specification may be combined to implement a method. In addition, the technical features of the method claims of this specification and the technical features of the device claims may be combined to implement an apparatus, and the technical features of the method claims of this specification and the technical features of the device claims may be combined to implement a method.

Claims

1. An operation method at a terminal, the method comprising: The step of sending a protocol data unit session establishment request message; as well as In response to the sending of the protocol data unit session establishment request message, a step of receiving a protocol data unit session establishment accept message or a protocol data unit session establishment reject message, The protocol data unit session establishment request message includes a protocol data unit session type notifying industrial traffic, and When the protocol data unit session establishment reject message is received, the protocol data unit session establishment reject message includes a reason value indicating that the network does not support the protocol data unit session type.

2. The method according to claim 1, wherein: The industrial traffic is traffic used for time-sensitive networking, time-sensitive communication, deterministic networking, ultra-reliable and low-latency communication, or industrial Internet of Things.

3. The method according to claim 1, wherein: The protocol data unit session establishment reject message includes a backoff timer.

4. The method according to claim 1, wherein: The protocol data unit session establishment rejection message includes a retry indicator, The retry indicator shows whether the terminal is allowed to attempt a protocol data unit session establishment procedure in an equivalent public land mobile network using the same data network name and the same single network slice selection assistance information.

5. The method according to claim 1, wherein: The protocol data unit session establishment request message also includes: Capacity information or indications related to said industrial flow rate.

6. The method according to claim 1, further comprising: The step of sending a registration request message including capability information or indication related to the industrial flow.

7. The method according to claim 1, further comprising: The step of receiving a registration acceptance message including capability information or indication related to the industrial flow.

8. The method according to claim 1, further comprising: The step of sending a non-access stratum transmission message including capability information or indication related to the industrial traffic.

9. The method according to claim 1, further comprising: The step of receiving a non-access stratum transmission message including capability information or indication related to the industrial traffic.

10. The method according to claim 1, wherein: Capability information or indication related to the industrial flow is set in the terminal or a universal user identification module of the terminal.

11. A chipset installed in a terminal, the chipset comprising: at least one processor; as well as at least one memory storing instructions and being operably electrically connected to the at least one processor, and Based on the instruction being executed by the at least one processor, the operations performed include: The step of sending a protocol data unit session establishment request message; as well as In response to the sending of the protocol data unit session establishment request message, a step of receiving a protocol data unit session establishment accept message or a protocol data unit session establishment reject message, The protocol data unit session establishment request message includes a protocol data unit session type notifying industrial traffic, and When the protocol data unit session establishment reject message is received, the protocol data unit session establishment reject message includes a reason value indicating that the network does not support the protocol data unit session type.

12. The chipset according to claim 11, wherein: The industrial traffic is traffic used for time-sensitive networking, time-sensitive communication, deterministic networking, ultra-reliable and low-latency communication, or industrial Internet of Things.

13. The chipset according to claim 11, wherein: The protocol data unit session establishment rejection message includes a retry indicator, The retry indicator shows whether the terminal is allowed to attempt a protocol data unit session establishment procedure in an equivalent public land mobile network using the same data network name and the same single network slice selection assistance information.

14. The chipset according to claim 11, wherein: The protocol data unit session establishment request message also includes: Capacity information or indications related to said industrial flow rate.

15. The chipset according to claim 11, wherein: Based on the instruction being executed by the at least one processor, the executed operations also include: The step of sending a registration request message including capability information or indication related to the industrial flow.

16. A device for a terminal, the device comprising: Transceiver unit; at least one processor; as well as at least one memory storing instructions and being operably electrically connected to the at least one processor, and Based on the instruction being executed by the at least one processor, the operations performed include: The step of sending a protocol data unit session establishment request message; as well as In response to the sending of the protocol data unit session establishment request message, a step of receiving a protocol data unit session establishment accept message or a protocol data unit session establishment reject message, The protocol data unit session establishment request message includes a protocol data unit session type notifying industrial traffic, and When the protocol data unit session establishment reject message is received, the protocol data unit session establishment reject message includes a reason value indicating that the network does not support the protocol data unit session type.

17. The device according to claim 16, wherein: The industrial traffic is traffic used for time-sensitive networking, time-sensitive communication, deterministic networking, ultra-reliable and low-latency communication, or industrial Internet of Things.

18. The device according to claim 16, wherein: The protocol data unit session establishment rejection message includes a retry indicator, The retry indicator shows whether the terminal is allowed to attempt a protocol data unit session establishment procedure in an equivalent public land mobile network using the same data network name and the same single network slice selection assistance information.

19. The device according to claim 16, wherein: The protocol data unit session establishment request message also includes: Capacity information or indications related to said industrial flow rate.

20. The device according to claim 11, wherein Based on the instruction being executed by the at least one processor, the executed operations also include: The step of sending a registration request message including capability information or indication related to the industrial flow.

Images