Method for providing time-sensitive networking service and deterministic networking service in wireless communication system, and apparatus therefor

Abstract

An operating method of a core network for providing a wireless communication service in a wireless communication system, of the present disclosure, to a terminal in which at least one protocol data unit (PDU) session is configured and a time-sensitive networking (TSN) service and a deterministic networking (DetNet) service are not supported, and which moves from a first area configured as a first tracking area (TA) to a second area that supports the TSN service and the DetNet service and is configured as a second TA may comprise steps in which: a first access and mobility management function (AMF) associated with the first TA of the core network receives, from the terminal, a registration request message related to a mobility update procedure for handover from the first area to the second area and updating of terminal location information; and the first AMF transmits, to the terminal, a registration accept message related to the completion of the mobility update procedure, wherein the registration request message includes information related to whether the terminal supports the TSN service and the DetNet service.

Description

Method and apparatus for providing time-sensitive networking services and deterministic networking services in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for providing time-sensitive networking services and deterministic networking services in a wireless communication system.

[0002]

[0003] In the future hyper-connected intelligent information society, Ultra Reliable Low Latency Communications (URLLC) networking technology is emerging as an essential foundational network infrastructure technology to enable the organic interconnection of people and objects, as well as online and offline environments, to exchange and process information. Accordingly, 3GPP has been conducting research on automation-centric Industrial Internet of Things (IIoT) that can maximize industrial productivity and profitability through changes in communication infrastructure, while actively accommodating the challenging requirements of vertical industry domains. In particular, mission-oriented industries such as smart factories, smart grids, and intelligent transportation systems require ultra-reliable, low-latency communication performance comparable to wired infrastructure; therefore, new technologies to support this are being incorporated into standards.

[0004] IEEE Time-Sensitive Networking (IETS) technology emerged to implement the Industrial Internet of Things (IIoT), which aims to network various facilities and systems in industrial sites. IEEE TSN is considered a next-generation industrial network standard capable of encompassing most network application cases that extend standard Ethernet, as it is a single package technology combining various existing IEEE standards. Following Rel-16, 3GPP has actively pursued the standardization of 5G-TSN technology to expand 5G technology across vertical domains. Fundamentally, 5G-TSN is a Time-Sensitive Communications (TSC) technology designed to integrate IEEE TSN technology into 5G systems (5GS) and defines and supports various IIoT service requirements. In TSC, 5GS and TSN fundamentally undergo a time synchronization process. Subsequently, it supports TSC QoS flows based on TSCAI (TSC Assistance Information).

[0005] Deterministic Networking (DetNet), currently being developed by the IETF DetNet WG, is a Layer 3 technology that extends the scope of Ethernet TSN technology (Layer 2 technology) to integrate with IP and MPLS-based networks. Ultimately, DetNet technology refers to a technology that supports and provides the extension of Ethernet TSN technology (Layer 2 technology) to IP technology (Layer 3 technology). In Rel-18, 3GPP is incorporating TSC framework extension technologies into the standard to support IETF DetNet technology in 5GS.

[0006]

[0007] The present disclosure aims to provide a method and apparatus for providing time-sensitive networking services and deterministic networking services in a wireless communication system.

[0008] The problems to be solved by the present disclosure are not limited to those mentioned above, and other problems not mentioned will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.

[0009]

[0010] A method of operation of a core network for providing wireless communication services to a terminal moving to a second area set as a second TA, wherein at least one protocol data unit (PDU) session is established in a wireless communication system according to the present disclosure, time-sensitive networking (TSN) service and deterministic networking (DetNet) service are not supported, and the TSN service and the DetNet service are supported in a first area set as a first tracking area (TA), comprises the steps of: a first Access and Mobility Management function (AMF) associated with the first TA of the core network receiving a Registration Request message from the terminal related to a mobility update procedure for handover from the first area to the second area and updating terminal location information; and the first AMF transmitting a Registration Accept message related to the completion of the mobility update procedure to the terminal, wherein the Registration Request message may include information related to whether the terminal supports the TSN service and the DetNet service.

[0011] Additionally, a core network system for providing wireless communication services to a terminal moving to a second area set as a second TA, wherein at least one protocol data unit (PDU) session according to the present disclosure is established, time-sensitive networking (TSN) services and deterministic networking (DetNet) services are not supported, and said TSN services and said DetNet services are supported in a first area set as a first tracking area (TA), comprises a first Access and Mobility Management function (AMF) associated with the first TA, a second AMF associated with the second TA, and a session management function (SMF) associated with the second TA; wherein the first AMF is configured to receive a Registration Request message from the terminal related to a mobility update procedure for handover from the first area to the second area and updating terminal location information, and to transmit a Registration Accept message related to the completion of said mobility update procedure to the terminal, and wherein the Registration Request message is configured to include the terminal's said TSN service and the It may include information regarding the support status of the DetNet service.

[0012] Additionally, a method performed by a terminal having at least one protocol data unit (PDU) session established in a wireless communication system according to the present disclosure comprises the steps of: transmitting a Registration Request message related to a mobility update procedure for handover from the first area to the second area and updating terminal location information to a first AMF associated with the first TA when moving from a first area set as a first tracking area (TA) where time-sensitive networking (TSN) services and deterministic networking (DetNet) services are not supported to a second area set as a second TA where the TSN services and the DetNet services are supported; and receiving a Registration Accept message related to the completion of the mobility update procedure from the first AMF. The Registration Request message may include information related to whether the terminal supports the TSN services and the DetNet services.

[0013] Additionally, a terminal of a wireless communication system according to the present disclosure comprises a transceiver and a controller connected to the transceiver, wherein, when moving from a first area set as a first tracking area (TA) where time-sensitive networking (TSN) services and deterministic networking (DetNet) services are not supported and the TSN services and the DetNet services are supported and the terminal moves to a second area set as a second TA, the controller transmits a Registration Request message related to a mobility update procedure for handover from the first area to the second area and updating terminal location information to a first Access and Mobility Management function (AMF) associated with the first TA, and receives a Registration Accept message related to the completion of the mobility update procedure from the first AMF, and the registration request message may include information regarding whether the terminal supports the TSN services and the DetNet services.

[0014]

[0015] The present disclosure has the effect of providing a method and apparatus for providing time-sensitive networking services and deterministic networking services in a wireless communication system.

[0016] The effects obtained by the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.

[0017]

[0018] Figure 1 is a diagram illustrating the structure of a next-generation mobile communication system.

[0019] Figure 2 is a figure showing an example of a general registration procedure.

[0020] Figure 3 is a figure showing an example of registration through AMF reallocation.

[0021] Figure 4 is a figure showing an example of onboarding SNPN UE registration.

[0022] Figure 5 is a figure showing an example of a UE request PDU session setup procedure.

[0023] Figure 6 is a figure showing an example of a PDCU session modification procedure requested by a UE.

[0024] FIG. 7 is a flowchart illustrating detailed operations performed in the AMF / SMF reallocation scheme for network-based and TSN / DetNet services proposed in the present disclosure.

[0025] FIG. 8 is a flowchart illustrating detailed operations performed in the AMF / SMF reallocation scheme for network-based and TSN / DetNet services proposed in the present disclosure.

[0026] FIG. 9 is a flowchart illustrating detailed operations performed according to the AMF / SMF selection method for terminal-based and TSN / DetNet proposed in the present disclosure.

[0027] FIG. 10 is a flowchart illustrating detailed operations performed according to the AMF / SMF selection for terminal-based and TSN / DetNet proposed in the present disclosure.

[0028] FIG. 11 is a flowchart illustrating an example of a method performed by a first AMF in a wireless communication system according to one embodiment of the present disclosure.

[0029] FIG. 12 is a flowchart illustrating an example of a method performed by a second AMF in a wireless communication system according to one embodiment of the present disclosure.

[0030] FIG. 13 is a drawing illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0031] FIG. 14 is a drawing illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0032] FIG. 15 is a drawing illustrating the structure of a network in a wireless communication system according to one embodiment of the present disclosure.

[0033]

[0034] Embodiments of the present disclosure will be described in detail below with reference to the drawings. However, detailed descriptions of known functions or configurations that may obscure the gist of the present disclosure in the following description and the attached drawings are omitted. Additionally, throughout the present disclosure, the term "comprising" any component means that, unless specifically stated otherwise, it does not exclude other components but may include additional components.

[0035] Additionally, terms such as first, second, etc. may be used to describe various components, but said components should not be limited by said terms. Such terms may be used for the purpose of distinguishing one component from another. For example, without departing from the scope of the rights of the present disclosure, the first component may be named the second component, and similarly, the second component may be named the first component.

[0036] The terms used in this disclosure are used merely to describe specific embodiments and are not intended to limit this disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this application, terms such as “comprising” or “comprising” are intended to specify the existence of the described features, numbers, steps, actions, components, parts, or combinations thereof, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0037] Unless specifically defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which this disclosure pertains. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and should not be interpreted in an ideal or overly formal sense unless explicitly defined in this disclosure.

[0038] Figure 1 is a diagram illustrating the structure of a next-generation mobile communication system.

[0039] Referring to FIG. 1, as illustrated, the wireless access network of a next-generation mobile communication system (New Radio, NR) consists of a next-generation base station (New Radio Node B, hereinafter gNB) (110) and an AMF (105, Access and Mobility Management function) provided in a 5G core (5GC). A user terminal (New Radio User Equipment, hereinafter NR UE or terminal) (115) connects to an external network through the gNB (110) and the AMF (105).

[0040] In FIG. 1, the gNB corresponds to the eNB (Evolved Node B) of the existing LTE system. The gNB is connected to the NR UE via a wireless channel and can provide superior service compared to the existing Node B (or eNB) (120). In the next-generation mobile communication system, since all user traffic is serviced through a shared channel, a device is required to collect state information such as the buffer state, available transmission power state, and channel state of the NR UEs and perform scheduling, and this is handled by the gNB (110). A single gNB typically controls multiple cells. To achieve ultra-high-speed data transmission compared to existing LTE, it can have a maximum bandwidth greater than the existing maximum bandwidth, and can additionally incorporate beamforming technology by using Orthogonal Frequency Division Multiplexing (hereinafter referred to as OFDM) as the wireless access technology. Additionally, an Adaptive Modulation & Coding (hereinafter referred to as AMC) method is applied to determine the modulation scheme and channel coding rate according to the terminal's channel state.

[0041] The AMF (105) performs functions such as mobility support, bearer configuration, and QoS configuration. The AMF (105) is a device responsible for various control functions as well as mobility management functions for the terminal, and is connected to multiple base stations. Additionally, the next-generation mobile communication system can be interconnected with the existing LTE system, and the AMF (105) is connected to the MME (125) via a network interface. The MME (125) is connected to the existing base station, eNB (130). A terminal (115) that supports LTE-NR Dual Connectivity can transmit and receive data while maintaining a connection (135) to both the gNB and the eNB.

[0042] The following describes Enablers for Time Sensitive Communications, Time Synchronization, and Deterministic Networking. For a detailed description, refer to 3GPP TS 23.501 V18.8.0 3 rd Refer to Section 5.27 on pages 359 through 384 of Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 18), and the contents thereof are briefly described in this specification.

[0043] The 5G system functions that can be used independently or in combination to enable time-sensitive communication, time synchronization, and deterministic networking are as follows.

[0044] - Delay-sensitive GBR;

[0045] - A hold and forward mechanism that schedules traffic as defined in IEEE Std 802.1Q for Ethernet PDU sessions of DS-TT and NW-TT (see 3GPP TS 23.501 Section 5.27.4) to eliminate jitter in flows passing through the 5G system when the 5G system must transparently participate as a bridge in a TSN network;

[0046] - TSC Assistance Information (TSCAI): Describes the TSC flow traffic characteristics described in Section 5.27.2 of 3GPP TS 23.501, which may be optionally provided for use in gNBs to enable more efficient scheduling of radio resources for periodic traffic, and applies to PDU session types Ethernet and IP;

[0047] - Time Synchronization: Describes how the 5GS operates as a PTP relay (IEEE Std 802.1AS), boundary clock, or transparent clock (IEEE Std 1588) for PDU session types Ethernet and IP, and how the 5GS detects and reports the time synchronization status;

[0048] - RAN feedback on BAT (burst arrival time) offset and adjusted period is a mechanism supported by NG-RAN and 5G CN to enable the AF (application function) to adapt to the BAT offset and adjusted period received from NG-RAN for a given traffic flow.

[0049] All of the aforementioned functions can be used by integrating a 5G system into an IEEE 802.1 TSN network as a bridge.

[0050] To support the above features that enable time-sensitive communication, time synchronization, and deterministic networking, during PDU session setup, the UE must request that the PDU session be set as an always-on PDU session, and the PDU session is set as an always-on PDU session. Time-sensitive communication, time synchronization, and deterministic networking can be enabled by using at least one of the above features.

[0051] - Home-routed PDU sessions are not supported;

[0052] - PDU sessions are supported only in SSC mode 1;

[0053] - Service continuity is not supported when a UE moves from 5GS to EPS (i.e., interoperability with EPS is not supported for time synchronization or PDU sessions for TSC or deterministic networking).

[0054] The following describes general matters regarding the registration procedure. For a detailed description of the registration procedure, refer to 3GPP TS 23.502 V18.8.0(3 rd Refer to Section 4.2.2.3 on pages 31 through 59 of Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 18)), and the contents thereof are briefly described in this specification.

[0055] The UE must register with the network to receive services, enable mobility tracking, and enable reachability. The UE initiates the registration process using one of the following registration types.

[0056] - Initial registration on 5GS

[0057] - Mobility Registration Update

[0058] - Regular registration update (due to a predefined period of inactivity)

[0059] - Emergency Registration

[0060] - Initial registration for disaster roaming specified in Section 5.40 of 3GPP TS 23.501

[0061] - Disaster Roaming Mobility Registration Update specified in Section 5.40 of 3GPP TS 23.501

[0062] - SNPN (standalone non-public network) onboarding registration

[0063] As defined in 3GPP TS 24.501, the cleartext IE that a UE can transmit in a registration request message when the UE does not have a NAS security context is as follows:

[0064] - Registration type

[0065] - SUCI or 5G-GUTI or PEI

[0066] - Security parameters

[0067] - Additional GUTI

[0068] - 4G tracking area update

[0069] - Indicates that the UE is moving in EPS

[0070] - PLMN with disaster conditions

[0071] - When a UE registers with an SNPN, the NID of the SNPN that assigned the 5G-GUTI.

[0072] Aspects related to dual registration of 3GPP and non-3GPP access are described in Section 4.12 of 3GPP TS 23.502. The general registration call flow in Section 4.2.2.2.2 of 3GPP TS 23.502 is used when a UE is registered to a 3GPP access when it is already registered to a non-3GPP access, and vice versa. To register to a 3GPP access when a UE is already registered to a non-3GPP access scenario, an AMF change may be required as described in detail in Section 4.12.8 of 3GPP TS 23.502.

[0073] The general registration call flow of Section 4.2.2.2.2 of 3GPP TS 23.502 is also used when a UE in a restricted service state (see 3GPP TS 23.122) registers only for an urgent service (referred to as urgent registration; see 3GPP TS 23.501 Section 5.16.4).

[0074] Figure 2 is a figure showing an example of a general registration procedure.

[0075] For a detailed description of the general registration procedure, refer to 3GPP TS23.4502 4.2.2.2.2, which is briefly summarized below.

[0076] (Operation 1) The UE sends an AN message to the (R)AN for a registration request.

[0077] (Operation 2) If 5G-S-TMSI or GUAMI is not included or 5G-S-TMSI or GUAMI does not represent a valid AMF, (R)AN selects an AMF based on (R)AT and the requested NSSAI, if possible.

[0078] (Operation 3) (R)AN sends an N2 message to request registration with the new AMF.

[0079] (Operation 4) Depending on the condition, send a Namf_Communication_UEContext Transfer(Registration request completed) request message from the new AMF to the previous AMF, or send a Nudsf_Unstructured Data Management_Query() request message from the new AMF to the UDSF.

[0080] (Operation 5) Depending on the condition, send a Namf_Communication_UEContextTransfer(SUPI, UE context of AMF) response message from the previous AMF to the new AMF, or send a Nudsf_Unstructured Data Management_Query() response message from UDSF to the new AMF.

[0081] (Operation 6) Depending on the condition, send an Identity Request() message from the new AMF to the UE.

[0082] (Operation 7) Conditionally, send the Identity Response() message from the UE to the new AMF.

[0083] (Operation 8) The AMF may decide to call the AUSF to initiate UE authentication. In this case, the AMF selects the AUSF based on SUPI or SUCI as described in Section 6.3.4 of 3GPP TS 23.501.

[0084] (Operation 9a) If authentication is required, AMF requests authentication from AUSF.

[0085] (Operation 9b) If a NAS security context does not exist, a NAS security initiation is performed as described in 3GPP TS 33.501.

[0086] (Operation 9c) If the 5G-AN requests UE context, the AMF initiates an NGAP procedure to provide the 5G-AN with security context as specified in 3GPP TS 38.413.

[0087] (Operation 9d) 5G-AN saves the security context and informs AMF.

[0088] (Operation 10) Depending on the condition, the new AMF sends the Namf_Communication_RegistrationStatusUpdate message to the previous AMF.

[0089] (Operation 11) Depending on the condition, the new AMF and UE exchange Identity Request / Response (PEI) messages.

[0090] (Operation 12) Optionally, the new AMF calls the N5g-eir_EquipmentIdentityCheck_Get service operation to initiate ME identity verification.

[0091] (Operation 13) When Operation 14 is performed, the new AMF selects a UDM based on SUPI.

[0092] (Operation 14a-c) If the AMF has changed since the last registration procedure, if the UE registration type is initial registration or urgent registration, or if the UE provides a SUPI that does not refer to a valid context in the AMF, or if the UE registers to the same AMF that it has already registered to a non-3GPP connection, the new AMF registers to the UDM using Nudm_UECM_Registration for the connection to be registered.

[0093] (Operation 14d) If the UDM stores the relevant access type (e.g., 3GPP) with the serving AMF as shown in Operation 14a, and if a previous AMF corresponding to the same access (e.g., 3GPP) exists, the UDM sends Nudm_UECM_DeregistrationNotification (see Section 5.2.3.2.2) to the previous AMF.

[0094] (Operation 14e) Conditionally, if the previous AMF does not have a UE context for a different connection type (e.g., a non-3GPP connection), the previous AMF uses Nudm_SDM_unsubscribe to unsubscribe the subscription data to the UDM.

[0095] (Operation 15) When the new AMF decides to start PCF communication, the new AMF selects the PCF.

[0096] (Action 16) Optionally, the new AMF performs AM policy link setup / modification. This action is skipped for urgent registration.

[0097] (Operation 17) Conditionally, the new AMF sends the Nsmf_PDUSession_UpdateSMContext() or Nsmf_PDUSession_ReleaseSMContext() message to the SMF.

[0098] (Operation 18) Conditionally, if the new AMF and the existing AMF are in the same PLMN, the new AMF sends a request to modify the UE context to N3IWF / TNGF / W-AGF as specified in 3GPP TS 29.413.

[0099] (Operation 19) N3IWF / TNGF / W-AGF sends a UE context modification response to the new AMF.

[0100] (Operation 19a). Conditionally, after the new AMF receives a response message from N3IWF, W-AGF, or TNGF in Operation 19, the new AMF registers with the UDM using Nudm_UECM_Registration as in Operation 14a, but sets the access type to "Non-3GPP Access".

[0101] (Operation 19b) If, under the condition, the UDM stores the relevant access type (i.e., non-3GPP) as specified in Operation 19a along with the serving AMF, the UDM sends a Nudm_UECM_DeregistrationNotification message to the PCF for the previous AMF corresponding to the same (i.e., non-3GPP) access.

[0102] (Operation 19c) The previous AMF uses Nudm_SDM_unsubscribe to unsubscribe from the UDM to the data subscribed to by the UDM.

[0103] (Operation 21) The new AMF sends a registration acceptance message to the UE.

[0104] (Operation 21b) Optionally, the new AMF performs UE policy association setup as defined in Section 4.16.11 of 3GPP TS23.502. This operation is omitted in the case of urgent registration.

[0105] (Operation 22) Conditionally, the UE sends a message that registration is complete with the new AMF.

[0106] (Operation 23) Conditionally, if the access and mobility subscription data provided by the UDM to the AMF in Operation 14b contains roaming information steering and there is an indication that the UDM is requesting the UE to acknowledge receiving this information, the AMF provides the UE's acknowledgment to the UDM using Nudm_SDM_Info.

[0107] (Operation 23a) In the case of registration via 3GPP connection, if the AMF does not disconnect the signaling connection, the AMF transmits RRC disable support information to the NG-RAN.

[0108] (Operation 24) Conditionally, after Operation 14a, in parallel with the preceding operation, AMF uses Nudm_UECM_Update to send an indication to UDM that "Uniform support for IMS Voice over PS sessions".

[0109] (Operation 25) Conditionally, if the UE indicates support for network slice-specific authentication and acknowledgment procedures to the UE MM core network function of the registration request, and any S-NSSAI of the HPLMN is subject to network slice-specific authentication and acknowledgment, the relevant procedures are executed in this operation (see 3GPP TS23.502 Section 4.2.9.1).

[0110] Below, registration with AMF re-allocation is described. For a detailed description of registration with AMF re-allocation, refer to Section 4.2.2.2.3 of 3GPP TS23.502.

[0111] When an AMF receives a registration request, for example, if the initial AMF is not a suitable AMF to provide services to the UE, the AMF may need to reroute the registration request to another AMF. The registration procedure with AMF reassignment described in Fig. 3 is used to reroute the UE's NAS message to a target AMF during the registration procedure.

[0112] Figure 3 is a figure showing an example of registration through AMF reallocation.

[0113] Referring to Fig. 3, the initial AMF and the target AMF register the corresponding functions to the NRF.

[0114] (Operation 1) When the UE is in the CM-IDLE state, operations 1 and 2 of Fig. 2 (Figure 4.2.2.2.2-1 of 3GPP TS23.502) are performed, and the (R)AN transmits a registration request message to the initial AMF within the initial UE message. When the UE is in the CM-CONNECTED state and triggers the registration procedure, the NG-RAN transmits a registration request message within the uplink NAS transmission message to the serving AMF, which is the initial AMF. The AMF may omit operations 2 and 3 of Fig. 2.

[0115] (Operation 2) When the AMF needs SUPI and / or UE’s subscription information to determine whether to reroute the registration request, or when the registration request was not sent to integrity protection, or when integrity protection is marked as failed, the AMF performs operations 4 through 9a or 9b of FIG. 2.

[0116] (Operation 3a). Conditionally, if the initial AMF needs the UE’s subscription information to determine whether to reroute the registration request and the UE’s slice selection subscription information was not provided by the previous AMF, the AMF selects a UDM as described in Section 6.3.8 of 3GPP TS 23.501.

[0117] (Operation 3b) The initial AMF sends the Nudm_SDM_Get(SUPI, Slice Selection Subscription data) message to the UDM.

[0118] (Operation 3c) UDM sends a response message to Nudm_SDM_Get to the initial AMF.

[0119] (Operation 4a) Conditionally, the initial AMF sends the Nnssf_NSSelection_Get(...) message to the NSSF.

[0120] (Operation 4b) Conditionally, NSSF sends the Nnssf_NSSelection_Get(...) message to the initial AMF.

[0121] (Operation 5) Conditionally, the initial AMF sends the Namf_Communication_Registration StatusUpdate(failure cause) message to the previous AMF.

[0122] (Operation 6a) Conditionally, the initial AMF sends the Nnrf_NFDiscovery_Request(NF type, AMF set) message to the NRF.

[0123] (Operation 6b) Conditionally, send a response message for Nnrf_NFDiscovery_Request to the NRF part AMF.

[0124] (Operation 7(A)). If the initial AMF decides to deliver the NAS message directly to the target AMF based on local policy and subscription information, the initial AMF sends Namf_Communication_N1MessageNotify to the target AMF to deliver the rerouted NAS message.

[0125] (Operation 7(B)). Conditionally, if the UE is in the CM-IDLE state, and based on local policy and subscription information, the initial AMF decides to forward a NAS message to the target AMF via the (R)AN unless the target AMF is returned from the NSSF and identified by the list of candidate AMFs, the initial AMF sends an NGAP NAS rerouting request message to the (R)AN (Operation 7a). The NGAP rerouting request NAS message contains information about the target AMF and a full registration request message. If the initial AMF has obtained information as described in Operation 4b, that information is included. The (R)AN sends an initial UE message to the target AM indicating a rerouting due to slicing, including the information from Operation 4b provided by the NSSF (Operation 7b).

[0126] (Operation 8) After receiving the registration request message transmitted in Operation 7(A) or Operation 7(B), the target AMF continues the registration procedure from Operation 4 to Operation 22 of FIG. 2, which includes the target AMF corresponding to the new AMF containing the UE context retrieved from the previous AMF.

[0127] Below, we will describe registration with onboarding SNPN. For a detailed description of registration with onboarding SNPN, refer to Section 4.2.2.2.4 of 3GPP TS23.502.

[0128] Specifies a method for registering a UE with ON-SNPN to provision the UE with SO-SNPN credentials and other information to enable SNPN access, as defined in Section 5.30.2.10 of 3GPP TS 23.501.

[0129] Compared to the operation of the flowchart described in Fig. 2, the SNPN registration procedure modified as follows must be supported as specified in Section 4.2.2.2.2 of 3GPP TS 23.501 of the flowchart. for the three cases shown in Fig. 4, namely, when the DCS hosts the AAA server, when the DCS hosts the AUSF / UDM, and when the DCS is not involved.

[0130] Figure 4 is a figure showing an example of onboarding SNPN UE registration.

[0131] Referring to Fig. 4, (Operation 1) the UE sends a registration request message to the NG-RAN. When the UE connects to the 5GS for onboarding, the AN parameter must include an onboarding indication.

[0132] (Operation 2) Based on the onboarding indication of Operation 1, the NG-RAN selects an AMF as described in Section 6.3.5 of 3GPP TS 23.501.

[0133] (Operation 3) NG-RAN sends an N2 message containing the registration request described in Operation 1 to AMF.

[0134] (Operation 4) Conditionally, the new AMF sends the Namf_Communication_UEContext Transfer(complete Registration Request) message to the previous AMF.

[0135] (Operation 5) Conditionally, the previous AMF sends a response message for Namf_Communication_UEContext Transfer to the new AMF.

[0136] (Operations 6-7) Operations 6 and 7 of Fig. 2 (Figure 4.2.2.2.2-1 of 3GPP TS 23.502) are not performed.

[0137] (Operation 8) When the AMF receives a NAS registration request with the 5GS registration type set to "SNPN Onboarding", the AMF applies locally configured AMF configuration data for onboarding to restrict UE network usage to onboarding only, and stores an indication in the AMF's UE context that the UE is registered for onboarding. The AMF selects an AUSF as described in Section 5.30.2.10.2.6 of 3GPP TS 23.501.

[0138] (Operation 9) Certification is performed as described in 3GPP TS 33.501.

[0139] For a DCS hosting an AAA server based on a local configuration as shown in Operation 9-1, the AUSF sends a SUPI to the AAA server in the DCS domain via NSSAAF, and the AAA server in the DCS domain authenticates the UE based on the data received from the AUSF. During the authentication process, the AAA server in the DCS domain may provide the PVS FQDN and / or PVS IP address for the UE to the AUSF via NSSAAF, and the AUSF then provides the PVS FQDN and / or PVS IP address to the AMF.

[0140] For a DCS hosting an AUSF / UDM as shown in Operation 9-2, the AUSF of the DCS domain performs the UDM selection. The AMF transmits the SUCI and primary UE credentials received from the UE to the AUSF of the DCS domain, and the AUSF authenticates the UE based on the data received from the AMF and the subscription data received from the UDM of the DCS domain. During the authentication process, the AUSF of the DCS domain provides the PVS FQDN and / or PVS IP address to the AMF.

[0141] In cases where the DCS is not involved during primary authentication as in Operation 9-3, the AMF selects the local AUSF as defined in Section 6.3.4 of 3GPP TS 23.501 and performs primary authentication for the local AUSF using the default UE credentials as described in 3GPP TS 33.501.

[0142] (Operation 10) Conditionally, the new AMF sends a Namf_Communication_Registration StatusUpdate message to the previous AMF.

[0143] (Operation 11) Conditionally, the AMF and the UE exchange identity request / response (PEI).

[0144] (Operation 12) Optionally, the new AMF initiates ME identity verification by calling the N5g-eir_EquipmentIdentityCheck_Get service operation (see Section 5.2.4.2.2 of 3GPP TS 23.502).

[0145] (Operations 13-20) Operations 13 to 20 of FIG. 2 are not performed.

[0146] (Operation 21) The AMF sends a registration acceptance message to the UE indicating that the registration request for the onboarding SNPN has been accepted.

[0147] (Operation 22) The UE sends a registration completion message to the AMF.

[0148] The terms and definitions set forth in 3GPP TR 21.905 apply to this disclosure. The terms defined in this disclosure take precedence over the definitions of the same terms in 3GPP TR 21.905.

[0149] 5GMM-IDLE mode: Where this term is used alone in the present disclosure, a UE in 5GMM-IDLE mode may be in 5GMM-IDLE mode through 3GPP access or in 5GMM-IDLE mode through non-3GPP access.

[0150] 5GMM-CONNECTED mode: Where this term is used alone in the present disclosure, a UE in 5GMM-CONNECTED mode may be in 5GMM-CONNECTED mode through 3GPP access or in 5GMM-CONNECTED mode through non-3GPP access.

[0151] 5GMM-IDLE mode over 3GPP access: A UE is in 5GMM-IDLE mode over 3GPP access when there is no N1 NAS signaling connection between the UE and the network over 3GPP access. In this disclosure, the term 5GMM-IDLE mode for 3GPP access corresponds to the term CM-IDLE state for 3GPP access in 3GPP TS 23.501 [8].

[0152] 5GMM-CONNECTED mode for 3GPP access: The UE is in 5GMM-CONNECTED mode when an N1 NAS signaling connection exists between the UE and the network via 3GPP access. In this disclosure, the term 5GMM-CONNECTED mode via 3GPP access corresponds to the term CM-CONNECTED state for 3GPP access in 3GPP TS 23.501 [8].

[0153] For a detailed description of the UE request PDU session setup procedure, see 3GPP TS 24.501 V18.9.0 3 rdRefer to Section 6.4.1 on pages 653 through 713 of Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 18). This specification is to incorporate the relevant content by reference, and a detailed description of the UE request PDU session establishment procedure is omitted. Referring to FIG. 5, which illustrates an example of the UE request PDU session establishment procedure, the UE request PDU session establishment procedure may result in a PDU session being established or not established by the UE sending a PDU SESSION ESTABLISHMENT REQUEST message to the SMF, and the SFM sending a PDU SESSION ESTABLISHMENT ACCEPT message or a PDU SESSION ESTABLISHMENT REJECT message to the US. At this time, the UE starts timer T3580 by sending a PDU SESSION ESTABLISHMENT REQUEST message to the SMF, and terminates timer T3580 when it receives a PDU SESSION ESTABLISHMENT ACCEPT message or a PDU SESSION ESTABLISHMENT REJECT message.

[0154] A detailed description of the procedure for establishing a session for a UE request PDU accepted by the network is cited in Section 6.4.1.3 of 3GPP TS 24.501, and is omitted from this specification.

[0155] A detailed description of cases where the PDU session setup procedure requested by the UE is not accepted by the network is cited in Section 6.4.1.4 of 3GPP TS 24.501, and is omitted from this specification.

[0156] A detailed description of handling the set maximum number of PDU sessions is cited in Section 6.4.1.5 of 3GPP TS 24.501, and is omitted from this specification.

[0157] A detailed description of the handling of the maximum number of active user plane resources allowed in a UE's PDU session in NB-N1 mode is cited in Section 6.4.1.5A of 3GPP TS 24.501, and is omitted from this specification.

[0158] A detailed description of abnormal cases in the UE is cited in Section 6.4.1.6 of 3GPP TS 24.501, and is omitted from this specification.

[0159] A detailed description of abnormal cases on the network side is referred to in Section 6.4.1.7 of 3GPP TS 24.501, and is omitted from this specification.

[0160] For a detailed description of the UE request PDU session modification procedure, see 3GPP TS 24.501 V18.9.0 3 rdRefer to Section 6.4.2 on pages 713 through 742 of Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 18). This specification describes the contents by reference and omits a detailed description of the UE request PDU session modification procedure. Referring to FIG. 6, which illustrates an example of the UE request PDU session modification procedure, the UE request PDU session modification procedure involves the UE sending a PDU SESSION MODIFICATION REQUEST message to the SMF, and the network request PDU session modification procedure proceeds so that the PDU session is modified, or the modification may be rejected if the UE receives a PDU SESSION MODIFICATION REJECT message. At this time, the UE starts timer T3581 while sending a PDU SESSION MODIFICATION REQUEST message to the SMF, and terminates timer T3581 when it recognizes that the network request PDU session modification procedure is in progress or receives a PDU SESSION MODIFICATION REJECT message.

[0161] A detailed description of the initiation of the UE request PDU session modification procedure is cited in Section 6.4.2.2 of 3GPP TS 24.501, and is omitted from this specification.

[0162] A detailed description of the procedure for modifying UE request PDU sessions accepted by the network is cited in Section 6.4.2.3 of 3GPP TS 24.501, and is omitted from this specification.

[0163] A detailed description of cases where UE request PDU session modification procedures are not allowed in a network is referenced in Section 6.4.2.4 of 3GPP TS 24.501, and is omitted from this specification.

[0164] A detailed description of the case where the UE is abnormal in the UE request PDU session modification procedure is cited in Section 6.4.2.5 of 3GPP TS 24.501 and is briefly described in this specification.

[0165] The following abnormal cases can be identified.

[0166] a) Expiration of Timer T3581.

[0167] b) Invalid PDU session ID.

[0168] c) Conflict between the network request PDU session release procedure and the UE request PDU session modification procedure.

[0169] d) If the UE has already canceled reflective QoS, process DL user data packets marked with RQI

[0170] e) Conflict between the network request PDU session modification procedure and the UE request PDU session modification procedure.

[0171] f) When a PDU session modification request message is received with the PDU session ID set to the same value as the PDU session ID sent by the UE, along with an indication that the 5GSM message was not delivered due to service area restrictions, the UE must stop the procedure and stop timer T3581.

[0172] g) When a 5GSM message is not delivered due to a routing failure, and a PDU session modification request message is received with the PDU session ID set to the same value as the PDU session ID sent by the UE, the UE must stop timer T3581 and stop the procedure.

[0173] ga) When a UE accessing via a satellite NG-RAN cell receives an indication that a 5GSM message was not delivered, such as receiving information that the PLMN cannot operate at the current UE location along with a PDU session modification request message in which the PDU session ID IE at the current UE location is set to the same value as the PDU session ID transmitted by the UE, the UE must stop timer T3581 and stop the procedure.

[0174] h) Conflict between the PDU session modification procedure requested by the UE and the N1 NAS signal disconnection

[0175] i) The PDU session modification procedure requested by the UE is denied when the UE initiates a procedure to drop one or more non-default QoS rules for the PDU session:

[0176] A detailed description of abnormal cases on the network side in the UE request PDU session modification procedure is cited in Section 6.4.2.6 of 3GPP TS 24.501 and is briefly described in this specification.

[0177] The following abnormal cases can be identified:

[0178] a) If the PDU session is an urgent PDU session and the 5GSM cause IE is not included in the PDU SESSION MODIFICATION REQUEST message, or is not triggered according to item 6.4.2.1 e), or is set as a 5GSM cause, the SMF must reject the PDU SESSION MODIFICATION REQUEST message using 5GSM cause #31 "Request denied, unspecified" rather than 5GSM causes #41, #42, #44, #45, #83, #84, #85.

[0179] b) The PDU session is inactive for the received PDU session ID.

[0180] c) Conflict between the network request PDU session modification procedure and the UE request PDU session modification procedure.

[0181] d) AMF provides "messages are exempt from DNN-based congestion enabled in AMF," but UE request PDU session modification procedures are not exempt from DNN-based congestion control.

[0182] e) AMF provides "messages are exempt from S-NSSAI and DNN-based congestion enabled in AMF," but the PDU session modification procedure requested by the UE is not exempted only in S-NSSAI-based congestion control.

[0183] f) The AMF provides "messages exempted only from S-NSSAI-based congestion enabled in the AMF," but the PDU session modification procedure requested by the UE is not exempted from S-NSSAI-based congestion control.

[0184] g) The 5G access network cannot transmit the message.

[0185] In the 5G System (5GS) described above, TSN / DetNet services may be supported according to operator policies or network settings. At this time, TSN / DetNet services may be supported differently depending on the Tracking Area (TA) or Cell ID.

[0186] In a heterogeneous 5GS environment where TSN / DetNet service support varies by TA or cell, when a terminal capable of supporting TSN / DetNet services moves from a general area that does not support TSN / DetNet services to an area that does, it typically performs a Mobility Registration update procedure. However, rapid TSN / DetNet service cannot be provided by performing only this Mobility Registration update procedure. Therefore, the following problem scenarios may occur.

[0187] 3GPP networks configure TSN / DetNet service support differently by TA or cell identifier, and based on this, heterogeneous 5GS with different TSN / DetNet service support is deployed. In this case, the terminal is a terminal capable of supporting TSN / DetNet services, and the network that does not support TSN / DetNet services is configured as AMF#1, and the network that supports TSN / DetNet services is configured as AMF#2. In this environment, it is assumed that the area configured as TA#1 that does not support TSN / DetNet services is Area#1, and the area configured as TA#2 that supports TSN / DetNet services is Area#2.

[0188] When a terminal capable of supporting TSN / DetNet services moves from receiving general services in Area #1 (TA#1), which does not support TSN / DetNet services, to Area #2 (TA#2), which does support TSN / DetNet services, the terminal performs a standard mobility registration update procedure. Consequently, AMF#1, a network that does not support TSN / DetNet services, processes the aforementioned registration procedure for mobility update requested by the terminal to update the terminal's location. However, despite moving to Area #2 (TA#2), which does support TSN / DetNet services, the terminal is still unable to receive TSN / DetNet services. This is because, looking at the current operation of the 3GPP standard, the terminal cannot provide information on TSN / DetNet service support to the network, and there is no description of a method for the network (AMF#1) to find and process a new network (e.g., AMF#2) so that the terminal can receive TSN / DetNet services.

[0189] Even if a terminal moves to Area #2 (TA#2) that supports TSN / DetNet services, performs a standard mobility update procedure first, and then attempts a PDU Session Establishment request procedure to receive TSN / DetNet services, based on the current operation of 3GPP standards, the network (AMF#1) does not recognize the request for TSN / DetNet services from the terminal and performs a standard PDU Session Establishment request procedure, and consequently, cannot provide TSN / DetNet services to the terminal. Therefore, a solution for providing TSN / DetNet services quickly and efficiently must be defined in the standard specifications.

[0190] In the following, specific methods for providing TSN / DetNet services quickly and efficiently to a terminal when the terminal moves from an area that does not support TSN / DetNet services (e.g., Area #1 configured as TA#1) to an area that supports TSN / DetNet services (e.g., Area #2 configured as TA#2).

[0191] First, as a method to quickly and efficiently provide TSN / DetNet services to a terminal when the terminal moves from an area that does not support TSN / DetNet services (e.g., Area #1 set as TA#1) to an area that supports TSN / DetNet services (e.g., Area #2 set as TA#2), a method may be considered to include (capability) indication / information indicating "the terminal has the ability to receive TSN / DetNet services" and / or "the terminal requests the provision of TSN / DetNet services" in the registration request / response message of FIG. 2 or FIG. 4 and the PDU session establishment request / accept message of FIG. 5. That is, the (capability) indication / information may indicate only that "the terminal has the capability to receive TSN / DetNet services," only that "the terminal requests the provision of TSN / DetNet services," or both that "the terminal has the capability to receive TSN / DetNet services" and that "the terminal requests the provision of TSN / DetNet services." In this case, the (capability) indication / information may be referred to as TSN / DetNet (capability) indication / information. In particular, this method may be based on UE-based and AMF selection for TSN / DetNet services.

[0192] In the present disclosure, a terminal supporting TSN / DetNet services means a terminal capable of receiving TSN / DetNet services, and may or may not actually receive TSN / DetNet services from a network.

[0193] Additionally, in the present disclosure, a terminal that does not support TSN / DetNet services may mean a terminal that lacks the ability to receive TSN / DetNet services. That is, a terminal that does not support TSN / DetNet services cannot receive TSN / DetNet services even if it is connected to a network that supports TSN / DetNet services.

[0194] Additionally, in the present disclosure, a network supporting TSN / DetNet services refers to a network capable of providing TSN / DetNet services. That is, a network supporting TSN / DetNet services may actually provide TSN / DetNet services to a terminal, or it may not actually provide TSN / DetNet services to a terminal. However, in the present disclosure, it may be understood that providing TSN / DetNet services is the default operation of a network supporting TSN / DetNet services.

[0195] Additionally, in the present disclosure, a network that does not support TSN / DetNet services may mean a network that lacks the ability to provide TSN / DetNet services. That is, a network that does not support TSN / DetNet services cannot provide TSN / DetNet services to a terminal.

[0196] In addition, in the present disclosure, receiving TSN / DetNet services from a network can be understood as two processes: first, a process in which an environment / setting in which the terminal can receive TSN / DetNet services from a network is first configured (i.e., a state in which TSN / DetNet services are supported), and based on this, actually receiving TSN / DetNet services from a network.

[0197] - Example 1 -

[0198] FIG. 7 is a flowchart illustrating detailed operations performed in the AMF / SMF reallocation scheme for network-based and TSN / DetNet services proposed in the present disclosure.

[0199] (Operation 0) A 3GPP network may configure support for TSN / DetNet services differently by TA (Tracking Area) or cell identifier, and based on this, heterogeneous 5GS with different support for TSN / DetNet services may be deployed. At this time, the terminal is a terminal capable of supporting TSN / DetNet services (capable of receiving TSN / DetNet services), and the network may include a network that does not support TSN / DetNet services (cannot provide TSN / DetNet services) (hereinafter referred to as AMF#1 for convenience of explanation) and a network that supports TSN / DetNet services (capable of providing TSN / DetNet services) (hereinafter referred to as AMF#2 for convenience of explanation). In this environment, an area that does not support TSN / DetNet services (hereinafter referred to as Area #1 for convenience of explanation) may be set as TA#1, and an area that supports TSN / DetNet services (hereinafter referred to as Area #2 for convenience of explanation) may be set as TA#2. Additionally, the terminal already has one (one or more) PDU session configured as a general service connection in the area that does not support TSN / DetNet services (TA#1). That is, the terminal is in a CM-CONNECTED state, which is a state in which a connection with the 5GC has been established. Here, the CM-CONNECTED state may refer to the 5GMM-CONNECTED mode over 3GPP access. Additionally, the CM-CONNECTED state may include a terminal in the 5GMM-CONNECTED mode having an RRC disable instruction as a parameter. At this time, the network managing / responsible for the PDU session configured as a general service connection is set to SMF#1.

[0200] (Operation 1) When a terminal capable of supporting TSN / DetNet services is receiving general services from a network (AMF#1) in Area #1 (TA#1), which does not support TSN / DetNet services, and then moves to Area #2 (TA#2), which supports TSN / DetNet services, the terminal sends a Registration Request message to the network (AMF#1 in 5GC) to perform a standard Mobility Registration update procedure. At this time, the terminal and the network may first perform a handover procedure (Operation 1.1), and after completing the handover procedure, perform the Mobility Registration update procedure. At this time, the terminal recognizes that Area #2 is an area that supports TSN / DetNet services and, in order to receive TSN / DetNet services in Area #2, includes TSN / DetNet (capability) indications / information in the Registration Request message and sends it to the network (AMF#1). Here, the terminal can recognize that Area #2 is an area that supports TSN / DetNet services based on TSN / DetNet service area information by TA or cell identifier provided from the AS layer.

[0201] (Operation 2) A network that does not support TSN / DetNet (AMF#1) receives a Registration Request message containing TSN / DetNet (capability) instructions / information from a terminal, performs a standard Mobility Registration update procedure, and updates the terminal's location information (UE location update) based on the Mobility Registration update procedure (Operation 2.1). Afterward, the network that does not support TSN / DetNet (AMF#1) responds by sending a Registration Accept message to the terminal and completes the execution of the standard Mobility Registration update procedure.

[0202] (Operation 3) A network that does not support TSN / DetNet (AMF#1) receives a Registration Request message containing TSN / DetNet (capability) indication / information from a terminal (wherein the Registration Request message may be an initial Registration Request message, and the same applies hereinafter), and can recognize that the terminal supports TSN / DetNet services based on the TSN / DetNet (capability) indication / information. The network (AMF#1) must find a new network that supports TSN / DetNet services and relocate / re-allocate the terminal recognized as supporting TSN / DetNet services. Therefore, the network (AMF#1) can immediately perform the AMF re-allocation procedure illustrated in FIG. 3 to find a new network that supports TSN / DetNet services and relocate / re-allocate the terminal. Here, since the registration procedure was performed on the terminal in the CM-CONNECTED state, the AMF reallocation (relocation) procedure can be performed (when a UE is in the CM-CONNECTED state and starts the registration procedure, the NG-RAN sends a registration request message in the Uplink NAS Transport message to the initial AMF, which is the AMF in service).

[0203] (Operation 4a) The previous network (AMF#1) performs an AMF re-allocation procedure based on "local / operator policy or subscriber information" and "TSN / DetNet (capability) indication / information," and through this, finds, selects, and allocates a new network (AMF#2) that supports TSN / DetNet services. Then, the previous network (AMF#1) directly transmits a Registration Request with TSN / DetNet (capability) indication / information message received from the terminal to the new network (AMF#2) (Operation 4a). At this time, the new network (AMF#2) processes the Registration Request with TSN / DetNet (capability) indication / information received from the previous network (AMF#1) to register the terminal, and responds by transmitting a Registration Accept message to the terminal (Operation 4c), thereby completing the Registration request procedure. At this time, the new network (AMF#2) may respond by including TSN / DetNet (capability) instructions / information in the Registration Accept message to indicate permission or availability for the terminal's request for TSN / DetNet service support.

[0204] (Operation 4b) When the previous network (AMF#1) performs an AMF re-allocation procedure based on "local / operator policy or subscriber information" and "TSN / DetNet (capability) indication / information" and finds, selects, and allocates a new network (AMF#2) that supports TSN / DetNet services, the previous network (AMF#1) transmits a Registration Request with TSN / DetNet (capability) indication / information received from the terminal to the new network (AMF#2) through the access network (e.g., the base station to which the terminal is newly connected via handover within the (R)AN). At this time, the previous network (AMF#1) transmits the information of the new network (AMF#2) and the NAS message (Registration Request with TSN / DetNet (capability) indication / information) to the (R)AN, and the (R)AN transmits the NAS message ((initial) Registration Request with TSN / DetNet (capability) indication / information) to the new network (AMF#2) based on the information of the new network (AMF#2) (Operation 4b.1). The new network (AMF#2) processes the registration request message containing the TSN / DetNet (capability) indication / information received from the (R)AN to register the terminal, and responds to the terminal with a registration acceptance message (Operation 4c) to complete the registration request procedure.At this time, the new network (AMF#2) may respond by including TSN / DetNet (capability) instructions / information in the Registration Accept message to indicate permission or availability for the terminal's request for TSN / DetNet service support.

[0205] Depending on local / operator policies or subscription information, either action 4a or action 4b may be performed.

[0206] (Operation 5) Meanwhile, after the preceding AMF selection operation is completed, the selected new network (AMF#2) that supports TSN / DetNet services selects SMF#2, a new session management function (SMF) that supports TSN / DetNet services. At this time, AMF#2 can select SMF#2 that supports TSN / DetNet services by performing an SMF selection procedure based on TSN / DetNet (capability) instructions / information (transmitted by the terminal).

[0207] (Operation 6) When the terminal receives a Registration Accept message from the network (AMF#2) containing TSN / DetNet (capability) instructions / information, it recognizes that the registration process is complete and that it is now possible to receive TSN / DetNet services from the network (AMF#2). Accordingly, upon recognizing that it is now possible to receive TSN / DetNet services from the network (AMF#2), the terminal may immediately perform a PDU Session Modification procedure to receive TSN / DetNet services from the network (AMF#2). To perform the PDU Session Modification procedure, the terminal may transmit a PDU Session Modification Request message to the network (AMF#2). At this time, the PDU Session Modification Request message includes information on an Always-on PDU session requested. Always-on PDUs may be used for session setup management to ensure rapid service connectivity and QoS, such as with TSN / DetNet services.

[0208] (Operation 7) A network (SMF#2) that receives a Session Modification Request message containing information on an Always-on PDU session requested from a terminal, processes the modification of the Always-on PDU session and the QoS guarantee related to the TSN / DetNet service for the PDU session setup for the TSN / DetNet service requested by the terminal, and then sends a Session Modification Accept with Always-on PDU session indication message to the terminal in response to the terminal's PDU session modification request. At this time, the Always-on PDU session indication may be information indicating that the PDU session requested by the terminal to receive the TSN / DetNet service is being modified into an Always-on PDU session. When the terminal receives a Session Modification Accept message from the network (SMF#2), it immediately receives TSN / DetNet services through the corresponding configured PDU session (Always-on PDU session for TSN / DetNet service(s) / application(s)).

[0209] - Example 2 -

[0210] Next, as a method to quickly and efficiently provide TSN / DetNet services to a terminal when the terminal moves from an area that does not support TSN / DetNet services (e.g., area #1 set as TA#1) to an area that supports TSN / DetNet services (e.g., area #2 set as TA#2), a method may be considered to include (capability) indication / information indicating "the terminal has the ability to receive TSN / DetNet services" and / or "the terminal requests the provision of TSN / DetNet services" in a registration request / accept message and a PDU session establishment request / accept message. That is, the (capability) indication / information may indicate only that "the terminal has the capability to receive TSN / DetNet services," only that "the terminal requests the provision of TSN / DetNet services," or both that "the terminal has the capability to receive TSN / DetNet services" and that "the terminal requests the provision of TSN / DetNet services." In this case, the (capability) indication / information may be referred to as TSN / DetNet (capability) indication / information. In particular, this method may be a method based on network-based and AMF / SMF re-allocation (relocation) for TSN / DetNet services.

[0211] FIG. 8 is a flowchart illustrating detailed operations performed in the AMF / SMF reallocation scheme for network-based and TSN / DetNet services proposed in the present disclosure.

[0212] (Operation 0) A 3GPP network may configure support for TSN / DetNet services differently by TA (Tracking Area) or cell identifier, and based on this, heterogeneous 5GS with different support for TSN / DetNet services may be deployed. At this time, the terminal is a terminal capable of supporting TSN / DetNet services (capable of receiving TSN / DetNet services), and the network may include a network that does not support TSN / DetNet services (cannot provide TSN / DetNet services) (hereinafter referred to as AMF#1 for convenience of explanation) and a network that supports TSN / DetNet services (capable of providing TSN / DetNet services) (hereinafter referred to as AMF#2 for convenience of explanation). In this environment, an area that does not support TSN / DetNet services (hereinafter referred to as Area #1 for convenience of explanation) may be set as TA#1, and an area that supports TSN / DetNet services (hereinafter referred to as Area #2 for convenience of explanation) may be set as TA#2. Additionally, the terminal already has one (one or more) PDU session configured for general service connection in the area that does not support TSN / DetNet services (TA#1). That is, the terminal is in a CM-CONNECTED state, which is a state in which a connection with the 5GC has been established. Here, the CM-CONNECTED state may refer to 5GMM-CONNECTED mode over 3GPP access. Additionally, the CM-CONNECTED state may include the UE in 5GMM-CONNECTED mode with RRC inactive indication. At this time, the network managing / responsible for the PDU sessions configured for general service connections is set to SMF#1.

[0213] (Operation 1) When a terminal capable of supporting TSN / DetNet services is receiving general services from a network (AMF#1) in Area #1 (TA#1) that does not support TSN / DetNet services, and then moves to Area #2 (TA#2) that supports TSN / DetNet services, the terminal sends a Registration Request message to the network (AMF#1) to perform a general Mobility Registration update procedure. At this time, the terminal and the network may first perform a handover procedure (Operation 1.1), and after completing the handover procedure, perform the Mobility Registration update procedure. At this time, the terminal recognizes that Area #2 is an area that supports TSN / DetNet services, and in order to receive TSN / DetNet services in Area #2, it includes TSN / DetNet (capability) indications / information in the Registration Request message and sends it to the network (AMF#1). Here, the terminal can recognize that Area #2 is an area that supports TSN / DetNet services based on the TA (Tracking Area) or TSN / DetNet service area information by cell identifier provided from the AS layer.

[0214] (Operation 2) A network that does not support TSN / DetNet (AMF#1) receives a Registration Request message containing TSN / DetNet (capability) instructions / information from a terminal, performs a standard Mobility Registration update procedure, and can update the terminal's location information based on the Mobility Registration update procedure (Operation 2.1). Afterward, the network that does not support TSN / DetNet (AMF#1) responds by sending a Registration Accept message to the terminal and can complete the execution of the standard Mobility Registration update procedure.

[0215] (Operation 3) A network that does not support TSN / DetNet (AMF#1) receives a Registration Request message containing TSN / DetNet (capability) indication / information from a terminal (wherein the Registration Request message may be an initial Registration Request message, and the same applies hereinafter), and can recognize that the terminal is a terminal that supports TSN / DetNet services based on the TSN / DetNet (capability) indication / information. The network (AMF#1) must find a new network that supports TSN / DetNet services and relocate / re-allocate the terminal recognized as supporting TSN / DetNet services. Therefore, the AMF re-allocation procedure illustrated in FIG. 3 for finding a new network that supports TSN / DetNet services and relocating / re-allocating the terminal can be performed immediately. Here, since the registration procedure was performed on the terminal in the CM-CONNECTED state, the AMF reallocation (relocation) procedure can be performed (when a UE is in the CM-CONNECTED state and starts the registration procedure, the NG-RAN sends a registration request message in the Uplink NAS Transport message to the initial AMF, which is the AMF in service).

[0216] (Operation 4a) When the previous network (AMF#1) performs an AMF re-allocation procedure based on "local / operator policy or subscriber information" and "TSN / DetNet (capability) instructions / information" and finds, selects, and allocates a new network (AMF#2 within 5GC) that supports TSN / DetNet services, the previous network (AMF#1) directly transmits a registration request message containing TSN / DetNet (capability) instructions / information received from the terminal to the new network (AMF#2) (Operation 4a). At this time, the new network (AMF#2) processes the registration request containing TSN / DetNet (capability) instructions / information received from the previous network (AMF#1) to register the terminal, transmits a Registration Accept message to the terminal (Operation 4c), and completes the registration request procedure. At this time, the new network (AMF#2) may respond by including TSN / DetNet (capability) instructions / information in the Registration Accept message to indicate permission or availability for the terminal's request for TSN / DetNet service support.

[0217] (Operation 4b) When the previous network (AMF#1) performs an AMF re-allocation procedure based on "local / operator policy or subscriber information" and "TSN / DetNet (capability) instructions / information," and thereby finds, selects, and allocates a new network (AMF#2 within 5GC) that supports TSN / DetNet services, the previous network (AMF#1) transmits a registration request message containing the TSN / DetNet (capability) instructions / information received from the terminal to the new network (AMF#2) through an access network (e.g., a base station to which the terminal is newly connected via handover within the (R)AN). At this time, the previous network (AMF#1) transmits a NAS message containing the new network (AMF#2) information and the registration request message containing the TSN / DetNet (capability) instructions / information to the (R)AN, and the (R)AN transmits the NAS message to the new network (AMF#2) based on the new network (AMF#2) information (Operation 4b.1). The new network (AMF#2) processes a registration request message containing TSN / DetNet (capability) instructions / information received from (R)AN to register the terminal, transmits a registration acceptance message to the terminal (operation 4c), and completes the registration request procedure. At this time, the new network (AMF#2) may respond by including TSN / DetNet (capability) instructions / information in the registration acceptance message to indicate permission or availability for the terminal's request for TSN / DetNet service support.

[0218] Depending on local / operator policies or subscription information, either action 4a or action 4b may be performed.

[0219] (Operation 5) Meanwhile, after the preceding AMF selection operation is completed, the new network (AMF#2) that supports the selected TSN / DetNet service subsequently selects SMF#2, which is a new session management function (SMF) that supports the TSN / DetNet service. At this time, AMF#2 can select SMF#2 that supports the TSN / DetNet service by performing an SMF selection procedure based on the TSN / DetNet (capability) instruction / information (transmitted by the terminal).

[0220] (Operation 6) When the terminal receives a Registration Accept message from the network (AMF#2) containing TSN / DetNet (capability) instructions / information, it recognizes that the registration process is complete and that it is now possible to receive TSN / DetNet services from the network (AMF#2). At this time, the terminal recognizes that it is now possible to receive TSN / DetNet services from the network (AMF#2) and, simultaneously, in order to immediately receive TSN / DetNet services from the network (AMF#2), it may perform a procedure for establishing a new PDU session for TSN / DetNet services, separate from the existing PDU session for general services. To perform the PDU session establishment procedure, the terminal may send a PDU session establishment request message to the network (AMF#2). At this time, the PDU Session Establishment Request message includes information on an Always-on PDU session requested. The Always-on PDU may be for managing session setups to ensure rapid service connection and QoS, such as with TSN / DetNet services.

[0221] (Operation 7) A network (SMF#2) that receives a PDU session establishment request message from a terminal containing information on an always-on PDU session request, processes the establishment of an always-on PDU session and QoS guarantees related to the TSN / DetNet service for the PDU session establishment for the TSN / DetNet service requested by the terminal, and then sends a Session Establishment Accept with Always-on PDU session indication message to the terminal as a response to the terminal's PDU session establishment request. At this time, the always-on PDU session indication may be information indicating that the PDU session requested by the terminal to receive TSN / DetNet services is established as an always-on PDU session. When the terminal receives the Session Establishment Accept message from the network (SMF#2), it immediately receives TSN / DetNet services through the corresponding established PDU session (Always-on PDU session for TSN / DetNet service(s) / application(s)).

[0222] - Example 3 -

[0223] Next, as a method to provide TSN / DetNet services quickly and efficiently to the terminal when the terminal moves from an area that does not support TSN / DetNet services (e.g., Area #1 set as TA#1) to an area that supports TSN / DetNet services (e.g., Area #2 set as TA#2), a method may be considered to include (capability) indication / information indicating "the terminal has the ability to receive TSN / DetNet services" and / or "the terminal requests the provision of TSN / DetNet services" in a registration request / acceptance message and a PDU session modification request / acceptance message. That is, the (capability) indication / information may indicate only "the terminal has the ability to receive TSN / DetNet services," only "the terminal requests the provision of TSN / DetNet services," or both "the terminal has the ability to receive TSN / DetNet services" and "the terminal requests the provision of TSN / DetNet services." In this case, the (capability) indication / information may be referred to as TSN / DetNet (capability) indication / information. In particular, this approach may be based on UE-based and AMF / SMF selection for TSN / DetNet services.

[0224] FIG. 9 is a flowchart illustrating detailed operations performed according to the AMF / SMF selection method for terminal-based and TSN / DetNet proposed in the present disclosure.

[0225] (Operation 0) A 3GPP network may configure support for TSN / DetNet services differently for each TA or cell identifier, and based on this, heterogeneous 5GS with different support for TSN / DetNet services may be deployed. In this case, the terminal is a terminal capable of supporting TSN / DetNet services (capable of receiving TSN / DetNet services), and the network may include a network that does not support TSN / DetNet services (cannot provide TSN / DetNet services) (AMF#1 / SMF#1 within 5GC) and a network that supports TSN / DetNet services (capable of providing TSN / DetNet services) (AMF#2 / SMF#2 within the 5GC). In this environment, the TA in the area that does not support TSN / DetNet services (hereinafter referred to as Area #1 for convenience of explanation) may be set to TA#1, and the TA in the area that supports TSN / DetNet services (hereinafter referred to as Area #2 for convenience of explanation) may be set to TA#2. Additionally, the terminal already has one (one or more) PDU session configured as a general service connection in the area that does not support TSN / DetNet services (Area #1 configured as TA#1). That is, the terminal is in a CM-CONNECTED state, which is a state in which a connection with the 5GC has been established. Here, the CM-CONNECTED state may refer to 5GMM-CONNECTED mode over 3GPP access. Additionally, the CM-CONNECTED state may include a terminal in 5GMM-CONNECTED mode with an RRC disable instruction. At this time, the network managing / responsible for the PDU session configured as a general service connection is set to SMF#1.

[0226] (Operation 1) When a terminal capable of supporting TSN / DetNet services is receiving general services from a network (AMF#1) in Area #1 (TA#1) that does not support TSN / DetNet services, and then moves to Area #2 (TA#2) that supports TSN / DetNet services, the terminal sends a Registration Request message to the network (AMF#1) to perform a general Mobility Registration update procedure. At this time, the terminal and the network may first perform a handover procedure (Operation 1.1), and after completing the handover procedure, perform the Mobility Registration update procedure. At this time, the terminal recognizes that Area #2 is an area that supports TSN / DetNet services, and in order to receive TSN / DetNet services in Area #2, it includes TSN / DetNet (capability) indications / information in the Registration Request message and sends it to the network (AMF#1). According to one embodiment, the terminal can recognize that Area #2 is an area that supports TSN / DetNet services based on the Tracking Area (TA) or TSN / DetNet service area information provided by the AS layer.

[0227] (Operation 2) A network that does not support TSN / DetNet (AMF#1) receives a Registration Request message containing TSN / DetNet (capability) instructions / information from a terminal, performs a standard Mobility Registration update procedure, and updates the terminal's location information (UE location update) based on the Mobility Registration update procedure (Operation 2.1). Afterward, the network that does not support TSN / DetNet (AMF#1) responds by sending a Registration Accept message to the terminal and completes the execution of the standard Mobility Registration update procedure.

[0228] (Operation 3) Meanwhile, a network that does not support TSN / DetNet (AMF#1) can recognize that "the terminal has the ability to receive TSN / DetNet services" and / or "the terminal requests the provision of TSN / DetNet services" upon receiving a Registration Request message containing TSN / DetNet (capability) instructions / information from the terminal. Accordingly, the former network (AMF#1) can respond by sending a Registration Accept message to the terminal in Operation 2 above so that the terminal can discover a new network (AMF#2) that supports TSN / DetNet services and be assigned to the discovered new network (AMF#2). After the previous network (AMF#1) completes the execution of the standard Mobility Registration update procedure by completing the transmission of the Registration Accept message, the previous network (AMF#1) may immediately transmit a Configuration Update Command with (initial) Registration requested as a parameter to the terminal. At this time, the reason the previous network (AMF#1) transmits the Configuration Update Command with (initial) Registration requested as a parameter to the terminal is to enable the terminal to search for a new network (AMF#2) that supports TSN / DetNet services by performing the initial Registration Request procedure, and to be assigned to the new network (AMF#2) that supports TSN / DetNet services.

[0229] (Operation 4) When the terminal receives a configuration update command containing an (initial) registration request as a parameter from a previous network (AMF#1) that does not support TSN / DetNet services, it sends a Configuration Update Complete message to the previous network (AMF#1) in response (Operation 4), and then immediately sends an Initial Registration Request message to the previous network (AMF#1) (Operation 4.1). At this time, TSN / DetNet (capability) instructions / information may be included in the Initial Registration Request message. In addition, to enable the base station ((R)AN) to find and select a new network (AMF#2) that supports TSN / DetNet services (can provide TSN / DetNet services) based on TSN / DetNet (capability) instructions / information, the terminal's NAS provides TSN / DetNet (capability) instructions / information to the RRC, and the terminal's RRC can include the TSN / DetNet (capability) instructions / information received from the NAS in an RRC setup completion message (RRCSetupComplete message) and transmit it to the base station. Based on the TSN / DetNet (capability) instructions / information, the base station performs an AMF selection procedure (Operation 4.2) to search for and select a new network (AMF#2) that supports TSN / DetNet services (can provide TSN / DetNet services).

[0230] (Operation 5) When the base station selects a new network (AMF#2) that supports TSN / DetNet services through the AMF selection procedure, it can transmit the terminal's NAS message (initial registration request message) to the selected new network (AMF#2) (Operation 5).

[0231] Subsequently, a new network (AMF#2) supporting TSN / DetNet services, newly selected through the base station's AMF selection procedure, can complete the processing of the terminal's (initial) registration request and complete the initial registration request procedure by responding to the terminal with a Registration Accept message (Operation 5.1). At this time, the new network (AMF#2) supporting TSN / DetNet services may respond by sending a Registration Accept message to the terminal containing TSN / DetNet (capability) instructions / information as a sign of permission or availability for the terminal's request to provide TSN / DetNet services.

[0232] (Operation 6) Meanwhile, after the execution of the preceding AMF selection procedure is completed, the selected new network (AMF#2) that supports TSN / DetNet services subsequently selects SMF#2, which is a new session management function (SMF) that supports TSN / DetNet services. At this time, AMF#2 can select SMF#2 that supports TSN / DetNet services by performing the SMF selection procedure (Operation 6) based on the TSN / DetNet (capability) instruction / information (transmitted by the terminal).

[0233] (Operation 7) When the terminal receives a Registration Accept message containing TSN / DetNet (capability) instructions / information from the new network (AMF#2), it recognizes that the registration process is complete and that it is now possible to receive TSN / DetNet services from the new network (AMF#2). Accordingly, upon recognizing that it is now possible to receive TSN / DetNet services from the new network (AMF#2), the terminal may immediately perform a procedure for PDU Session Modification to modify the existing PDU session for general services in order to receive TSN / DetNet services from the new network (AMF#2). For the PDU Session Modification procedure, the terminal may transmit a PDU Session Modification Request message to the network (AMF#2) (Operation 7). In this case, the PDU Session Modification Request message includes information on an Always-on PDU session requested. The Always-on PDU may be used for session setup management to ensure rapid service connectivity and QoS, such as with TSN / DetNet services.

[0234] (Operation 8) A network (SMF#2) that receives a PDU session modification request message containing information on an always-on PDU session request from a terminal processes the change / modification to an always-on PDU session and the QoS guarantee related to the TSN / DetNet service for the modification of the PDU session for the TSN / DetNet service requested by the terminal, and then transmits a Session Modification Accept with Always-on PDU session indication message to the terminal as a response to the terminal's PDU session modification request. At this time, the always-on PDU session indication may be information indicating that the PDU session requested by the terminal to receive the TSN / DetNet service is changed / modified to an always-on PDU session. When the terminal receives a Session Modification Accept message from the network (SMF#2) (Operation 8), it immediately receives TSN / DetNet services through the corresponding configured PDU session (Always-on PDU session for TSN / DetNet service(s) / application(s)).

[0235] - Example 4 -

[0236] Next, as a method to provide TSN / DetNet services quickly and efficiently to the terminal when the terminal moves from an area that does not support TSN / DetNet services (e.g., Area #1 set as TA#1) to an area that supports TSN / DetNet services (e.g., Area #2 set as TA#2), a method may be considered to include (capability) indication / information indicating "the terminal has the ability to receive TSN / DetNet services" and / or "the terminal requests the provision of TSN / DetNet services" in a registration request / acceptance message and a PDU session formation request / acceptance message. That is, the (capability) indication / information may indicate only "the terminal has the ability to receive TSN / DetNet services," only "the terminal requests the provision of TSN / DetNet services," or both "the terminal has the ability to receive TSN / DetNet services" and "the terminal requests the provision of TSN / DetNet services." In this case, (capability) instructions / information may be referred to as TSN / DetNet (capability) instructions / information. In particular, this approach may be a method based on UE-based and AMF / SMF selection for TSN / DetNet services.

[0237] FIG. 10 is a flowchart illustrating detailed operations performed according to the AMF / SMF selection for terminal-based and TSN / DetNet proposed in the present disclosure.

[0238] (Operation 0) A 3GPP network may configure support for TSN / DetNet services differently for each TA or cell identifier, and based on this, heterogeneous 5GS with different support for TSN / DetNet services may be deployed. In this case, the terminal is a terminal capable of supporting TSN / DetNet services (capable of receiving TSN / DetNet services), and the network may include a network that does not support TSN / DetNet services (cannot provide TSN / DetNet services) (AMF#1 / SMF#1 within 5GC) and a network that supports TSN / DetNet services (capable of providing TSN / DetNet services) (AMF#2 / SMF#2 within the 5GC). In this environment, the TA in the area that does not support TSN / DetNet services (hereinafter referred to as Area #1 for convenience of explanation) may be set to TA#1, and the TA in the area that supports TSN / DetNet services (hereinafter referred to as Area #2 for convenience of explanation) may be set to TA#2. Additionally, the terminal already has one (one or more) PDU session configured as a general service connection in the area that does not support TSN / DetNet services (Area #1 configured as TA#1). That is, the terminal is in a CM-CONNECTED state, which is a state in which a connection with the 5GC has been established. Here, the CM-CONNECTED state may refer to 5GMM-CONNECTED mode over 3GPP access. Additionally, the CM-CONNECTED state may include a terminal in 5GMM-CONNECTED mode with an RRC disable instruction. At this time, the network managing / responsible for the PDU session configured as a general service connection is set to SMF#1.

[0239] (Operation 1) When a terminal capable of supporting TSN / DetNet services is receiving general services from a network (AMF#1) in Area #1 (TA#1) that does not support TSN / DetNet services, and then moves to Area #2 (TA#2) that supports TSN / DetNet services, the terminal sends a Registration Request message to the network (AMF#1) to perform a general Mobility Registration update procedure. At this time, the terminal and the network may first perform a handover procedure (Operation 1.1), and after completing the handover procedure, perform the Mobility Registration update procedure. At this time, the terminal recognizes that Area #2 is an area that supports TSN / DetNet services, and in order to receive TSN / DetNet services in Area #2, it includes TSN / DetNet (capability) indications / information in the Registration Request message and sends it to the network (AMF#1). According to one embodiment, the terminal can recognize that Area #2 is an area that supports TSN / DetNet services based on the Tracking Area (TA) or TSN / DetNet service area information provided by the AS layer.

[0240] (Operation 2) A network that does not support TSN / DetNet (AMF#1) receives a Registration Request message containing TSN / DetNet (capability) instructions / information from a terminal, performs a standard Mobility Registration update procedure, and updates the terminal's location information (UE location update) based on the Mobility Registration update procedure (Operation 2.1). Afterward, the network that does not support TSN / DetNet (AMF#1) responds by sending a Registration Accept message to the terminal and completes the execution of the standard Mobility Registration update procedure.

[0241] (Operation 3) Meanwhile, a network that does not support TSN / DetNet (AMF#1) can recognize that "the terminal has the ability to receive TSN / DetNet services" and / or "the terminal requests the provision of TSN / DetNet services" upon receiving a Registration Request message containing TSN / DetNet (capability) instructions / information from the terminal. Accordingly, the former network (AMF#1) can respond by sending a Registration Accept message to the terminal in Operation 2 above so that the terminal can discover a new network (AMF#2) that supports TSN / DetNet services and be assigned to the discovered new network (AMF#2). After the previous network (AMF#1) completes the execution of the standard Mobility Registration update procedure by completing the transmission of the Registration Accept message, the previous network (AMF#1) may immediately transmit a Configuration Update Command with (initial) Registration requested as a parameter to the terminal. At this time, the reason the previous network (AMF#1) transmits the Configuration Update Command with (initial) Registration requested as a parameter to the terminal is to enable the terminal to search for a new network (AMF#2) that supports TSN / DetNet services by performing the initial Registration Request procedure, and to be assigned to the new network (AMF#2) that supports TSN / DetNet services.

[0242] (Operation 4) When the terminal receives a configuration update command containing an (initial) registration request as a parameter from a previous network (AMF#1) that does not support TSN / DetNet services, it sends a Configuration Update Complete message to the previous network (AMF#1) in response (Operation 4), and then immediately sends an Initial Registration Request message to the previous network (AMF#1) (Operation 4.1). At this time, TSN / DetNet (capability) instructions / information may be included in the Initial Registration Request message. In addition, to enable the base station ((R)AN) to find and select a new network (AMF#2) that supports TSN / DetNet services (can provide TSN / DetNet services) based on TSN / DetNet (capability) instructions / information, the terminal's NAS provides TSN / DetNet (capability) instructions / information to the RRC, and the terminal's RRC can include the TSN / DetNet (capability) instructions / information received from the NAS in an RRC setup completion message (RRCSetupComplete message) and transmit it to the base station. Based on the TSN / DetNet (capability) instructions / information, the base station performs an AMF selection procedure (Operation 4.2) to search for and select a new network (AMF#2) that supports TSN / DetNet services (can provide TSN / DetNet services).

[0243] (Operation 5) When the base station selects a new network (AMF#2) that supports TSN / DetNet services through the AMF selection procedure, it can transmit the terminal's NAS message (initial registration request message) to the selected new network (AMF#2) (Operation 5).

[0244] Subsequently, a new network (AMF#2) supporting TSN / DetNet services, newly selected through the base station's AMF selection procedure, can complete the processing of the terminal's (initial) registration request and complete the initial registration request procedure by responding to the terminal with a Registration Accept message (Operation 5.1). At this time, the new network (AMF#2) supporting TSN / DetNet services may respond by sending a Registration Accept message to the terminal containing TSN / DetNet (capability) instructions / information as a sign of permission or availability for the terminal's request to provide TSN / DetNet services.

[0245] (Operation 6) Meanwhile, after the execution of the preceding AMF selection procedure is completed, the selected new network (AMF#2) that supports TSN / DetNet services subsequently selects SMF#2, which is a new session management function (SMF) that supports TSN / DetNet services. At this time, AMF#2 can select SMF#2 that supports TSN / DetNet services by performing the SMF selection procedure (Operation 6) based on the TSN / DetNet (capability) instruction / information (transmitted by the terminal).

[0246] (Operation 7) When the terminal receives a Registration Accept message containing TSN / DetNet (capability) instructions / information from the new network (AMF#2), it recognizes that the registration process is complete and that it is now possible to receive TSN / DetNet services from the new network (AMF#2). Accordingly, upon recognizing that it is now possible to receive TSN / DetNet services from the new network (AMF#2), the terminal may immediately perform a procedure for establishing a new PDU session for TSN / DetNet services, separate from the existing PDU session for general services, in order to receive TSN / DetNet services from the new network (AMF#2). To perform the PDU session establishment procedure, the terminal may transmit a PDU session establishment request message to the network (AMF#2) (Operation 7). At this time, the PDU Session Establishment Request message includes information on an Always-on PDU session requested. The Always-on PDU may be for managing session setups to ensure rapid service connection and QoS, such as with TSN / DetNet services.

[0247] (Operation 8) A network (SMF#2) that receives a Session Establishment Request message containing information on an Always-on PDU session requested from a terminal, processes the establishment of an Always-on PDU session and QoS guarantees related to the TSN / DetNet service for the PDU session establishment for the TSN / DetNet service requested by the terminal, and then transmits a Session Establishment Accept with Always-on PDU session indication message to the terminal in response to the terminal's PDU session establishment request. At this time, the Always-on PDU session indication may be information indicating that the PDU session requested by the terminal to receive the TSN / DetNet service is established as an Always-on PDU session. When the terminal receives a Session Establishment Accept message from the network (SMF#2), it immediately receives TSN / DetNet services through the corresponding configured PDU session (Always-on PDU session for TSN / DetNet service(s) / application(s)).

[0248] Additionally, when a terminal moves from an area that does not support TSN / DetNet services (e.g., Area #1 set as TA#1) to an area that supports TSN / DetNet services, the area that supports TSN / DetNet services may be an area in which all or part of each of at least one area set with different TA values ​​overlaps. For example, when a terminal moves from Area #1 that does not support TSN / DetNet services to an area that supports TSN / DetNet services, the area that supports TSN / DetNet services may be an area in which all or part of each of Area #2 set as TA#2, Area #3 set as TA#3, ... Area #k set as TA#k (k is a natural number) overlaps. For the sake of convenience of explanation, the following description is limited to cases where a terminal moves from an area that does not support TSN / DetNet services (e.g., Area #1 set as TA#1) to an area that supports TSN / DetNet services, and parts of Area #2 set as TA#2 and Area #3 set as TA#3 overlap within the area that supports TSN / DetNet services.

[0249] In this case, the operations performed between the terminal and the network in the area that does not support TSN / DetNet services (AMF#1 / SMF#1) and the network in the area that supports TSN / DetNet services (AMF#2 / SMF#2) may be basically the same as the operations described above, but there may be differences in the following operations.

[0250] First, regarding (Operation 4), when the (R)AN (base station) performs an AMF selection procedure to search for and select a new network that supports TSN / DetNet services (can provide TSN / DetNet services) based on the TSN / DetNet (capability) instructions / information obtained from the terminal via the RRC Setup Complete message, it can select both AMF#2 associated with Area #2 set as TA#2 and AMF#3 associated with Area #3 set as TA#3.

[0251] Subsequently, in relation to (Operation 5), (R)AN (base station) may transmit the terminal's NAS message (initial Registration Request message) to AMF#2 and AMF#3, respectively. Next, AMF#2 and AMF#3 may complete the processing of the terminal's (initial) Registration Request and complete the initial Registration Request procedure by responding to the terminal with a Registration Accept message. At this time, the new AMF#2 and AMF#3 that support TSN / DetNet services may respond by transmitting a Registration Accept message to the terminal that includes TSN / DetNet (capability) instructions / information, in the sense of permission / support for the terminal's request to provide TSN / DetNet services.

[0252] Next, in relation to (Operation 7), when the terminal receives a Registration Accept message containing TSN / DetNet (capability) instructions / information from AMF#2 and AMF#3, respectively, it recognizes that the registration procedure is complete and that it is possible to receive TSN / DetNet services from AMF#2 and AMF#3, respectively. At this time, the terminal may perform an operation to select the more suitable network among AMF#2 and AMF#3 that support TSN / DetNet services. The terminal may perform an operation to select the more suitable network among AMF#2 and AMF#3 based on at least one condition. The quality of the received signal may be considered as at least one condition, and the quality of the received signal may be determined based on the quality of the received signal of the Registration Accept message received by the terminal from AMF#2 and AMF#3, respectively (forwarded from the base station associated with AMF#2 and the base station associated with AMF#3, respectively).

[0253] Next, in relation to (operation 8), the terminal may perform a procedure to modify the PDU session or form a PDU session with the SMF associated with the AMF determined to be the more suitable network among AMF#2 and AMF#3.

[0254] Additionally, the aforementioned measures may be implemented in combination with each other.

[0255] According to various embodiments of the present disclosure, based on TSN / DetNet (capability) indications / information including information regarding "the terminal supports TSN / DetNet services" and / or "the terminal requests the provision of TSN / DetNet services," the network may redeploy / reassign / reselect new network nodes (AFM, SMF, etc.) that support TSN / DetNet services. Through this, TSN / DetNet services can be provided to the terminal quickly and effectively. Furthermore, by supporting rapid TSN / DetNet service provision and QoS guarantees according to such an efficient TSN / DetNet service processing method, an optimized UX can be provided to the user / device.

[0256] FIG. 11 is a flowchart illustrating an example of a method performed by a first AMF in a wireless communication system according to one embodiment of the present disclosure.

[0257] Referring to FIG. 11, a first Access and Mobility Management function (AMF) associated with a first tracking area (TA) assigned to a first area where time-sensitive networking (TSN) services and deterministic networking (DetNet) services are not supported can receive a Registration Request message from a terminal related to a mobility update procedure for updating terminal location information from the first area to a second area where the TSN services and DetNet services are supported and a second TA is assigned (710).

[0258] At this time, the registration request message may include information regarding whether the terminal supports the TSN service and the DetNet service.

[0259] Next, the first AMF can send a Registration Accept message to the terminal regarding the completion of the mobility update procedure (720).

[0260] Next, the first AMF may perform an AMF re-allocation procedure to allocate a second AMF associated with the second TA allocated to the second area where the TSN service and the DetNet service are supported to the terminal (730).

[0261] FIG. 12 is a flowchart illustrating an example of a method performed by a second AMF in a wireless communication system according to one embodiment of the present disclosure.

[0262] Referring to FIG. 12, a second Access and Mobility Management function (AMF) associated with a second tracking area (TA) allocated to a second area that supports time-sensitive networking (TSN) services and deterministic networking (DetNet) services can receive a registration request message containing information regarding whether the terminal supports the TSN services and the DetNet services (810).

[0263] Next, the second AMF can determine a second SMF associated with the second AMF based on information regarding whether the terminal supports the TSN service and the DetNet service (820).

[0264] FIG. 13 is a drawing illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0265] Referring to FIG. 13, the terminal may include a transceiver comprising a terminal receiver (900) and a terminal transmitter (910), a memory (not shown), and a terminal processing unit (905, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver (900, 910), memory, and terminal processing unit (905) of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more components or fewer components than the components described above. Furthermore, the transceiver, memory, and processor may be implemented in the form of a single chip.

[0266] The transceiver (900, 910) can transmit and receive signals with a base station ((R)AN). Here, the signal may include control information and data. To this end, the transceiver (900, 910) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver, and the components of the transceiver are not limited to an RF transmitter and an RF receiver.

[0267] Additionally, the transceiver (900, 910) can receive a signal through a wireless channel and output it to a processor (905), and transmit the signal output from the processor (905) through a wireless channel.

[0268] Memory can store programs and data necessary for the operation of the terminal. Additionally, memory can store control information or data included in signals transmitted and received by the terminal. Memory may be composed of storage media or combinations of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, there may be multiple memories.

[0269] Additionally, the processor (905) can control a series of processes to enable the terminal to operate according to the above-described embodiment. For example, the processor (905) can control the components of the terminal to receive a DCI composed of two layers and receive multiple PDSCHs simultaneously. There may be multiple processors (905), and the processor (905) can perform the control operation of the terminal components by executing a program stored in memory.

[0270] FIG. 14 is a drawing illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0271] Referring to FIG. 14, a base station ((R)AN) may include a transceiver unit comprising a base station receiver (1030) and a base station transmitter (1010), a memory (not shown), and a base station processing unit (1005, or a base station control unit or processor). According to the communication method of the base station described above, the transceiver unit (1000, 1010), memory, and base station processing unit (1005) of the base station may operate. However, the components of the base station are not limited to the examples described above. For example, the base station may include more components or fewer components than the components described above. In addition, the transceiver unit, memory, and processor may be implemented in the form of a single chip.

[0272] The transceiver (1000, 1010) can transmit and receive signals with a terminal. Here, the signal may include control information and data. To this end, the transceiver (1000, 1010) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver, and the components of the transceiver are not limited to an RF transmitter and an RF receiver.

[0273] Additionally, the transceiver (1000, 1010) can receive a signal through a wireless channel and output it to a processor, and transmit the signal output from the processor through a wireless channel.

[0274] Memory can store programs and data necessary for the operation of the base station. Additionally, memory can store control information or data included in signals transmitted and received by the base station. Memory can be composed of storage media or combinations of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, there may be multiple memories.

[0275] The processor (1005) can control a series of processes to enable the base station to operate according to the embodiments of the present disclosure described above. For example, the processor (1005) can control each component of the base station to configure two layers of DCIs containing allocation information for a plurality of PDSCHs and to transmit them. There may be multiple processors (1005), and the processor (1005) can perform control operations on the components of the base station by executing a program stored in memory.

[0276] FIG. 15 is a drawing illustrating the structure of a network in a wireless communication system according to one embodiment of the present disclosure.

[0277] In the previous description and FIG. 15, the network refers to a device equipped in the 5G core network (5GC), which may be an AMF, SMF, PCF, AUSF, or UDM.

[0278] Referring to FIG. 15, the network may include a transceiver comprising a network receiver (1000) and a network transmitter (1110), a memory (not shown), and a network processing unit (1105, or a network control unit or processor). Depending on the communication method of the network described above, the transceiver (1100, 1110), memory, and network processing unit (1105) of the network may operate. However, the components of the network are not limited to the examples described above. For example, the network may include more components or fewer components than the components described above. Furthermore, the transceiver, memory, and processor may be implemented in the form of a single chip.

[0279] The transceiver (1100, 1110) can transmit and receive signals with a base station. Here, the signal may include control information and data. According to one embodiment, the transceiver (1100, 1110) can transmit a signal to the base station or receive a signal from the base station via a wired IP network. However, this is merely one embodiment of the transceiver, and the components of the transceiver are not limited thereto.

[0280] Additionally, the transceiver (1100, 1110) can receive a signal through a wireless channel and output it to a processor (1105), and transmit the signal output from the processor (1105) through a wireless channel.

[0281] Memory can store programs and data necessary for the operation of a network. Additionally, memory can store control information or data included in signals transmitted and received by the network. Memory can be composed of storage media or combinations of storage media, such as ROM, RAM, hard disks, CD-ROMs, and DVDs. Additionally, there may be multiple memory units.

[0282] Additionally, the processor (1105) can control a series of processes to enable the network to operate according to the above-described embodiment. There may be multiple processors, and the processor (1105) can perform control operations on the components of the network by executing a program stored in memory.

[0283] The methods according to the claims of the present disclosure or the embodiments described in the disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

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

[0285] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disc storage devices, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0286] Additionally, the program may be stored on an attachable storage device that can be accessed via a communication network such as the Internet, Intranet, LAN (local area network), WAN (wide area network), or SAN (storage area network), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

[0287] In the specific embodiments of the present disclosure described above, the components included in the disclosure are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.

[0288] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

Claims

A method of operation of a core network for providing wireless communication services to a terminal moving to a second area set as a second TA, wherein at least one protocol data unit (PDU) session is established, time-sensitive networking (TSN) service and deterministic networking (DetNet) service are not supported, and said TSN service and said DetNet service are supported in a first area set as a first tracking area (TA), wherein the method comprises: A first Access and Mobility Management function (AMF) associated with the first TA of the core network receives a Registration Request message from the terminal related to a mobility update procedure for handover from the first area to the second area and terminal location information update; The above first AMF includes the step of transmitting a Registration Accept message related to the completion of the mobility update procedure to the terminal, and A method in which the above registration request message includes information regarding whether the terminal supports the TSN service and the DetNet service. In claim 1, the above method is, The first AMF transmits a configuration update command message (Configuration Update Command with initial Registration requested) to the terminal, the message including a registration request as a parameter; The first AMF receives a Configuration Update Complete message from the terminal; The first AMF receives an initial registration request message from the terminal, the message including information regarding whether the terminal supports the TSN service and the DetNet service; The step of the first AMF determining the second AMF of the core network supporting the TSN service and the DetNet service based on an AMF reallocation operation; The step of the first AMF transmitting the initial registration request message to the second AMF; The step of the second AMF transmitting to the terminal an initial registration acceptance message containing information indicating that it permits support for the TSN service and the DetNet service; and A method comprising the step of the second AMF selecting an SMF (session management function) associated with the second TA. In Article 2, The step of the first AMF transmitting the initial registration request message to the second AMF is A method comprising the step of the first AMF directly transmitting the initial registration request message to the second AMF. In Article 2, The step of the first AMF transmitting the initial registration request message to the second AMF is The step of the first AMF transmitting information about the second AMF and the initial registration request message to the base station to which the terminal is connected; and A method comprising the step of the second AMF receiving the initial registration request message from the base station. In claim 1, the above method is, The first AMF transmits a configuration update command message (Configuration Update Command with initial Registration requested) to the terminal, the message including a registration request as a parameter; The first AMF receives a Configuration Update Complete message from the terminal; A second AMF selected by a base station to which the terminal is connected, based on information regarding whether the terminal supports the TSN service and the DetNet service, receives an initial registration request message from the base station containing information regarding whether the terminal supports the TSN service and the DetNet service; and The step of the second AMF transmitting to the terminal an initial registration acceptance message containing information indicating that it permits support for the TSN service and the DetNet service; and A method comprising the step of the second AMF selecting an SMF (session management function) associated with the second TA. In any one of paragraphs 2 through 5, The above SMF includes the step of performing a PDU session modification procedure with the terminal to modify the PDU session that was set on the terminal, wherein A method in which the modified PDU session based on the above PDU session modification procedure is an always-on PDU session. In any one of paragraphs 2 through 5, The above SMF includes the step of performing a PDU session formation procedure with the terminal to form a PDU session separate from the PDU session set on the terminal, wherein A method in which a PDU session formed based on the above PDU session formation procedure is an always-on PDU session. A core network system for providing wireless communication services to a terminal moving to a second area set as a second TA, wherein at least one protocol data unit (PDU) session is established, time-sensitive networking (TSN) service and deterministic networking (DetNet) service are not supported, and said TSN service and said DetNet service are supported in a first area set as a first tracking area (TA), wherein The first AMF (Access and Mobility Management function) associated with the above-mentioned first TA; A second AMF associated with the above second TA; and It includes an SMF (session management function) associated with the above-mentioned second TA, and The above-mentioned first AMF is, Receiving a Registration Request message from the terminal related to a mobility update procedure for handover from the first area to the second area and terminal location information update, and The above terminal is configured to transmit a Registration Accept message related to the completion of the mobility update procedure, and A core network system in which the above registration request message includes information regarding whether the terminal supports the TSN service and the DetNet service. In Article 8, The above-mentioned first AMF is, Sending a configuration update command message (Configuration Update Command with initial Registration requested) containing a registration request as a parameter to the above terminal, and Receive a Configuration Update Complete message from the above terminal, and Receive an initial registration request message from the terminal that includes information regarding whether the terminal supports the TSN service and the DetNet service, and Determine the second AMF of the core network supporting the TSN service and the DetNet service based on the AMF reallocation operation, and The above second AMF is configured to transmit the above initial registration request message, and The above second AMF is, Transmit an initial registration acceptance message to the above terminal, the message including information indicating permission to support the TSN service and the DetNet service, and A core network system configured to select an SMF (session management function) associated with the above-mentioned second TA. In Article 9, A core network system configured such that the first AMF is configured to directly transmit the initial registration request message to the second AMF. In Article 9, The first AMF is configured to transmit information about the second AMF and the initial registration request message to the base station to which the terminal is connected, and The above-mentioned second AMF is a core network system configured to receive the first registration request message from the base station. In Article 8, The above-mentioned first AMF is, Sending a configuration update command message (Configuration Update Command with initial Registration requested) containing a registration request as a parameter to the above terminal, and Receive a Configuration Update Complete message from the above terminal, and Based on information regarding whether the terminal supports the TSN service and the DetNet service, the second AMF selected by the base station to which the terminal is connected is, Receiving an initial registration request message from the base station containing information regarding whether the terminal supports the TSN service and the DetNet service, and Transmit an initial registration acceptance message to the above terminal, the message including information indicating permission to support the TSN service and the DetNet service, and A core network system configured to select an SMF (session management function) associated with the above-mentioned second TA. In any one of paragraphs 9 through 12, The above SMF is configured to perform a PDU session modification procedure with the terminal to modify the PDU session that was set on the terminal, and A core network system in which the modified PDU session based on the above PDU session modification procedure is an always-on PDU session. In any one of paragraphs 9 through 12, The above SMF is configured to perform a PDU session formation procedure with the terminal to form a PDU session separate from the PDU session set on the terminal, and A core network system in which the PDU session formed based on the above PDU session formation procedure is an always-on PDU session. A method performed by a terminal having at least one protocol data unit (PDU) session established in a wireless communication system, wherein the method comprises: When moving from a first area configured as a first tracking area (TA) where time-sensitive networking (TSN) services and deterministic networking (DetNet) services are not supported to a second area configured as a second TA where the TSN services and DetNet services are supported, the step of transmitting a Registration Request message related to a mobility update procedure for handover from the first area to the second area and terminal location information update to a first Access and Mobility Management function (AMF) associated with the first TA; and The method includes the step of receiving a Registration Accept message from the first AMF regarding the completion of the mobility update procedure, and A method in which the above registration request message includes information regarding whether the terminal supports the TSN service and the DetNet service. In claim 15, the above method is, A step of receiving a Configuration Update Command message (Configuration Update Command with initial Registration requested) containing a registration request as a parameter from the first AMF; A step of transmitting a Configuration Update Complete message to the first AMF; A step of transmitting an initial registration request message containing information regarding whether the terminal supports the TSN service and the DetNet service to the first AMF; A method comprising the step of receiving an initial registration acceptance message from a second AMF selected by the first AMF, the message including information indicating permission to support the TSN service and the DetNet service. In claim 15, the above method is, A step of receiving a Configuration Update Command message (with initial Registration requested) containing a registration request as a parameter from the first AMF; A step of transmitting a Configuration Update Complete message to the first AMF; A method comprising the step of receiving an initial registration acceptance message including information indicating that support for the TSN service and the DetNet service is permitted from a second AMF selected by a base station connected to the terminal, based on information regarding whether the terminal supports the TSN service and the DetNet service. In Article 16 or Article 17, The method includes the step of performing a PDU session modification procedure with an SMF (session management function) selected by the second AMF to modify the configured PDU session, wherein A method in which the modified PDU session based on the above PDU session modification procedure is an always-on PDU session. In Article 16 or Article 17, The method includes the step of performing a PDU session formation procedure with an SMF (session management function) selected by the second AMF to form a PDU session separate from the previously established PDU session, wherein A method in which a PDU session formed based on the above PDU session formation procedure is an always-on PDU session. In a terminal of a wireless communication system, the terminal is, transceiver; and Includes a controller connected to the above transceiver, The above controller is, In a situation where at least one protocol data unit (PDU) session is established, and time-sensitive networking (TSN) services and deterministic networking (DetNet) services are not supported, when moving from a first area set as a first tracking area (TA) to a second area set as a second TA where said TSN services and said DetNet services are supported, a Registration Request message related to a mobility update procedure for handover from the first area to the second area and terminal location information update is transmitted to a first Access and Mobility Management function (AMF) associated with said first TA. It is configured to receive a Registration Accept message related to the completion of the mobility update procedure from the first AMF, and The above registration request message includes information regarding whether the terminal supports the TSN service and the DetNet service, the terminal.

Images