Control plane based configuration for time sensitive networking

Abstract

A wireless device receives a request from a first station or a time-sensitive network (TSN) bridge indicating the configuration of the TSN bridge for the transmission of a stream of data packets. The wireless device transmits a non-access layer message to a session management function (SMF) containing at least one parameter for the configuration of the TSN bridge. The wireless device receives a response message from the SMF indicating that the TSN bridge has been configured for the transmission of a stream of data packets. The wireless device transmits a message to the first station indicating the successful configuration of the TSN bridge.

Description

Technology Field

[0001] Cross-reference regarding related applications

[0002] This application claims priority to U.S. Provisional Application No. 62 / 792,652, filed January 15, 2019, the full text of which is incorporated herein by reference. Brief explanation of the drawing

[0003] Various examples of different embodiments of the present invention are described herein with reference to the drawings. FIG. 1 is a drawing of an exemplary 5G system architecture according to one aspect of one embodiment of the present disclosure. FIG. 2 is a drawing of an exemplary 5G system architecture according to one aspect of one embodiment of the present disclosure. FIG. 3 is a system diagram of an exemplary wireless device and network node in a 5G system according to one aspect of one embodiment of the present disclosure. FIG. 4 is a system diagram of an exemplary network node according to one aspect of one embodiment of the present disclosure. FIGS. 5a and 5b illustrate two registration management status models within a UE (100) and an AMF (155) according to one aspect of the embodiments of the present disclosure. FIGS. 6a and 6b illustrate two connection management state models within a UE (100) and an AMF (155) according to one aspect of the embodiments of the present disclosure. FIG. 7 is a diagram of classification and traffic marking according to one aspect of one embodiment of the present invention. FIG. 8 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 9 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 10 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 11 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 12 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 13 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 14 is an exemplary drawing according to one aspect of one embodiment of the present disclosure. FIG. 15 is an exemplary drawing according to one aspect of one embodiment of the present invention. FIG. 16 is an exemplary drawing according to one aspect of one embodiment of the present disclosure. FIG. 17 is an exemplary drawing according to one aspect of one embodiment of the present disclosure. FIG. 18 is an exemplary drawing according to one aspect of one embodiment of the present invention. FIG. 19 is an exemplary drawing according to one aspect of one embodiment of the present disclosure. FIG. 20 is an exemplary drawing according to one aspect of one embodiment of the present disclosure. FIG. 21 is an exemplary drawing according to one aspect of one embodiment of the present disclosure. FIG. 22 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 23 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 24 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 25 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 26 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 27 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 28 is an exemplary drawing according to one aspect of one embodiment of the present disclosure. FIG. 29 is an exemplary drawing according to one aspect of one embodiment of the present disclosure. FIG. 30 is an exemplary drawing according to one aspect of one embodiment of the present disclosure. FIG. 31 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 32 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 33 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 34 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 35 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 36 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. FIG. 37 is an exemplary call flow according to one aspect of one embodiment of the present disclosure. Specific details for implementing the invention

[0004] Exemplary embodiments of the present disclosure enable the implementation of enhanced features and functions in 5G systems. Embodiments of the technology disclosed herein may be used in the field of network slicing for communication systems and 5G systems. More specifically, embodiments of the technology disclosed herein may relate to 5G core networks and 5G systems for network slicing in communication systems. Throughout the present disclosure, UE, wireless device, and mobile device are used interchangeably.

[0005] The following acronyms are used throughout this institution:

[0006] 5G 5th generation mobile communication network

[0007] 5GC 5G core network

[0008] 5GS 5G System

[0009] 5G-AN 5G access network

[0010] 5QI 5G QoS Indicator

[0011] AF Application Function

[0012] AMF Access and Mobility Management Function

[0013] AN access network

[0014] CDR Billing Data Record

[0015] CCNF Common Control Network Functions

[0016] CIoT Cellular IoT

[0017] CN Core Network

[0018] CP control plane

[0019] DDN Downlink Data Notification

[0020] DL Downlink

[0021] DN data network

[0022] DNN data network name

[0023] F-TEID, the complete form of TEID

[0024] GPSI General Public Subscription Identifier

[0025] GTP GPRS Tunneling Protocol

[0026] GUTI Global Unique Temporary Identifier

[0027] IMSI (International Mobile Subscriber Identification Number)

[0028] LADN Local Area Data Network

[0029] LI legal wiretapping

[0030] MEI terminal identifier

[0031] MICO terminal launch connection only

[0032] MME Mobility Management Equipment

[0033] MO terminal-based

[0034] MSISDN mobile subscriber ISDN

[0035] MT terminal termination

[0036] N3IWF non-3GPP interoperability

[0037] NAI Network Access Identifier

[0038] NAS non-access layer

[0039] NB-IoT Narrowband IoT

[0040] NEF Network Exposure Function

[0041] NF network function

[0042] NGAP Next Generation Application Protocol

[0043] NR (New Radio)

[0044] NRF Network Storage Function

[0045] NSI Network Slice Instance

[0046] NSSAI Network Slice Selection Support Information

[0047] NSSF Network Slice Selection Function

[0048] OCS Online Billing System

[0049] OFCS Offline Billing System

[0050] PCF policy control function

[0051] PDU Packet / Protocol Data Unit

[0052] PEI Permanent Equipment Identifier

[0053] PLMN mobile phone system network

[0054] RAN wireless access network

[0055] QFI QoS Flow Identity

[0056] RM Registration Management

[0057] S1-AP S1 Application Protocol

[0058] SBA Service-Based Architecture

[0059] SEA security anchor function

[0060] SCM Security Context Management

[0061] SMF Session Management Function

[0062] SMSF SMS function

[0063] S-NSSAI Single Network Slice Selection Support Information

[0064] SUCI Service User Correlation ID

[0065] SUPI Subscriber Permanent Identifier

[0066] TEID Tunnel Endpoint Identifier

[0067] TSN Time-Sensitive Networking

[0068] UE User Equipment

[0069] UL Uplink

[0070] UL CL Uplink Classifier

[0071] UPF User Plane Function

[0072] FIGS. 1 and 2 illustrate a 5G system including access networks and a 5G core network. An exemplary 5G access network may include an access network that connects to a 5G core network. The access network may include an NG-RAN (105) and / or a non-3GPP AN (165). An exemplary 5G core network may be connected to one or more 5G access networks (5G-ANs and / or NG-RANs). For example, as in FIGS. 1 and 2, where interfaces may be used for communication between functional elements and network elements, the 5G core network may include functional elements or network functions.

[0073] In one example, the network function may be a processing function in a network that may have functional operations and / or interfaces. The network function may be implemented as a network element on dedicated hardware and / or as a network node as illustrated in FIGS. 3 and 4, or as a software instance running on dedicated hardware and / or shared hardware, or as a virtualized function instantiated on a suitable platform.

[0074] In one example, the access and mobility management function (AMF) (155) may include the following functions (some of the functions of the AMF (155) may be supported in a single instance of the AMF (155): termination of the RAN (105) CP interface (N2), termination of the NAS (N1), NAS encryption and integrity protection, registration management, connection management, reachability management, mobility management, lawful interception (in the case of AMF (155) events and interfaces to LI systems), provision of transport for session management, SM messages between the UE (100) and the SMF (160), transparent proxy for routing SM messages, access authentication, access authorization, provision of transport for SMS messages between the UE (100) and the SMSF, security anchor function, interaction with the SEA, the AUSF (150), and the UE (100), reception of an intermediate key established as a result of the UE (100) authentication process, security context management (SCM) for receiving a key from the SEA used to derive network-specific keys, and / or other.

[0075] In one example, the AMF (155) can support non-3GPP access networks through an N2 interface with the N3IWF (170), NAS signaling with the UE (100) on the N3IWF (170), authentication of UEs connected on the N3IWF (170), mobility of the UE (100) connected via non-3GPP access (165) or connected via 3GPP access (105) and non-3GPP access (165) simultaneously, authentication, management of individual security context state(s), support of a coordinated RM context valid on 3GPP access (105) and non-3GPP access (165), and support of CM management contexts for the UE (100) for connection via non-3GPP access.

[0076] In one example, an AMF (155) area may include one or more sets of AMFs (155). An AMF (155) may include some AMFs (155) that service a given area and / or network slice(s). In one example, there may be multiple AMFs (155) for each AMF (155) area and / or network slice(s). An application identifier may be an identifier that can be mapped to a specific application traffic detection rule. A configured NSSAI may be an NSSAI that can be provided to a UE (100). A DN (115) access identifier (DNAI) for a DNN may be an identifier for user plane access to a DN (115). Initial registration may be associated with the registration of UE (100) of RM-DEREGISTERED (500, 520) states. The N2AP UE (100) association may be a logic for each UE (100) association between a 5G AN node and an AMF (155). The N2AP UE-TNLA-binding may be a binding between the N2AP UE (100) association for a given UE (100) and a specific transport network layer, TNL association.

[0077] In one example, the session management function (SMF) (160) may include one or more of the following functions (one or more of the SMF (160) functions may be supported in a single instance of the SMF (160): session management (e.g., session establishment, modification and release including session establishment, maintaining a tunnel between the UPF (110) and the AN (105) node), UE (100) IP address allocation and management (including optional authorization), selection and control of UP function(s), configuration of traffic coordination in the UPF (110) to route traffic to an appropriate destination, termination of interfaces for policy control functions, policy enforcement and partial control of QoS, policy enforcement and partial control of QoS, lawful interception (in the case of SM events and interfaces to the LI system), termination of SM parts of NAS messages, downlink data notification, initiation of AN-specific SM information transmitted to (R)AN (105) via the AMF (155) on N2, determination of the session's SSC mode, roaming function, Support for local enforcement for applying QoS SLAs (VPLMN), billing data collection and billing interface (VPLMN), lawful interception (in the case of SM events and interface to LI systems in the VPLMN), and interaction with an external DN (115) for transmitting signaling for PDU session authorization / authentication by the external DN (115), etc.

[0078] In one example, the user plane function (UPF) (110) may include one or more of the following functions (some of the UPF (110) functions may be supported in a single instance of the UPF (110): an anchor point for RAT-in / RAT-to-mobility (if applicable), an external PDU session point interconnected to a DN (115), packet routing and forwarding, packet inspection and user plane portion of policy rule enforcement, lawful interception (UP collection), traffic usage reporting, an uplink classifier supporting traffic flow routing to a data network, a branch point to support multi-home PDU session(s), QoS processing for the user plane, uplink traffic verification (SDF for QoS flow mapping), transport-level packet marking on the uplink and downlink, downlink packet buffering, downlink data notification triggering, etc.

[0079] In one example, UE (100) IP address management may include the allocation and deallocation of UE (100) IP addresses and / or the updating of allocated IP addresses. UE (100) may set the requested PDU type during the PDU session establishment procedure based on its IP stack capabilities and / or configuration. In one example, SMF (160) may select the PDU type of the PDU session. In one example, if SMF (160) receives a request with a PDU type set to IP, SMF (160) may select PDU type IPv4 or IPv6 based on DNN configuration and / or operator policies. In one example, SMF (160) may provide a cause value to UE (100) to indicate whether a different IP version is supported by the DNN. In one example, if SMF (160) receives a request for PDU type IPv4 or IPv6 and the requested IP version is supported by the DNN, SMF (160) may select the requested PDU type.

[0080] In an exemplary embodiment, 5GC elements and the UE (100) may support the following mechanisms: During the PDU session establishment procedure, the SMF (160) may transmit an IP address to the UE (100) via SM NAS signaling. Once a PDU session can be established, IPv4 address assignment and / or IPv4 parameter configuration via DHCPv4 may be utilized. If IPv6 is supported, IPv6 prefix assignment may be supported via IPv6 stateless autoconfiguration. In one example, 5GC network elements may support IPv6 parameter configuration via stateless DHCPv6.

[0081] 5GC can support the allocation of static IPv4 addresses and / or static IPv6 prefixes based on subscription information within the UDM (140) and / or on a DNN-based configuration for each subscriber.

[0082] User plane function(s) (UPF) (110) can handle user plane paths of PDU sessions. UPF (110), which provides an interface to the data network, can support the function of PDU session anchors.

[0083] In one example, the policy control function (PCF) (135) may support an integrated policy framework for controlling network behavior, may provide policy rules for controlling flat function(s) to enforce policy rules, and may implement a front end for accessing subscription information related to policy decisions within a user data store (UDR).

[0084] The network exposure function (NEF) (125) can provide means to securely expose services and functions provided by 3GPP network functions, can convert between information exchanged with AF (145) and information exchanged with internal network functions, and can receive information from other network functions.

[0085] In one example, the network storage function (NRF) (130) may support a service discovery function that can receive an NF discovery request from an NF instance, provide information about the discovered (to be discovered) NF instance to the NF instance, and maintain information about available NF instances and their supported services.

[0086] In one example, the NSSF (120) can select a set of network slice instances that service the UE (100) and determine an allowed NSSAI. In one example, the NSSF (120) can determine an AMF (155) configured to be used to service the UE (100) and / or determine a list of candidate AMFs 155(s)(155) by querying the NRF (130) based on the configuration.

[0087] In one example, the data stored within the UDR may include at least user subscription data, including at least subscription identifiers, security credentials, access and mobility-related subscription data, session-related subscription data, policy data, etc.

[0088] In one example, AUSF (150) can support authentication server functions (AUSF 150).

[0089] In one example, an application function (AF 145) can interact with a 3GPP core network to provide services. In one example, based on operator deployment, application functions may be trusted by the operator to interact directly with relevant network functions. Application functions that are not allowed to directly access network functions by the operator may interact with relevant network functions using an externally exposed framework (e.g., via NEF (125)).

[0090] In one example, the control plane interface between the (R)AN (105) and the 5G core network can support connections to the 5GC of a number of different types of AN(s) (e.g., 3GPP RAN (105), N3IWF (170) for untrusted access (165)). In one example, the N2 AP protocol can be used for both 3GPP access (105) and non-3GPP access (165). In one example, the control plane interface between the (R)AN (105) and the 5G core network can support decoupling between the AMF (155) and other functions, such as the SMF (160), which may need to control services supported by the AN(s) (e.g., control of UP resources within the AN (105) for PDU sessions).

[0091] In one example, 5GC can provide policy information from PCF (135) to UE (100). In one example, the policy information may include a network discovery and selection policy, a UE (100) route selection policy (URSP), an SSC mode selection policy (SSCMSP), a network slice selection policy (NSSP), a DNN selection policy, a non-seamless offload policy, etc.

[0092] In one example, as illustrated in FIGS. 5a and 5b, a registration manager RM may be used to register or unregister a UE / user (100) using the network and to establish a user context within the network. Connection management may be used to establish and release a signal connection between the UE (100) and the AMF (155).

[0093] In one example, a UE (100) may register with a network to receive services that require registration. In one example, the UE (100) may update its registration with the network periodically (periodic registration update) to remain accessible, or according to mobility (e.g., mobility registration update), or to update its performance or renegotiate protocol parameters.

[0094] In one example, the initial registration procedure as illustrated in FIGS. 8 and FIGS. 9 may include the execution of network access control functions (e.g., user authentication and access authorization based on subscription profiles within the UDM (140)). FIGS. 9 is a continuation of the initial registration procedure illustrated in FIGS. 8. As a result of the initial registration procedure, the identity of the AMF (155) being serviced may be registered in the UDM (140).

[0095] In one example, registration management, RM procedures can be applied to both 3GPP access (105) and non-3GPP access (165).

[0096] FIG. 5a may illustrate the RM states of the UE (100) as observed by the UE (100) and the AMF (155). In an exemplary embodiment, two RM states, RM-DEREGISTERED (500) and RM-REGISTERED (510), may be used in the UE (100) and the AMF (155), which may reflect the registration state of the UE (100) within a selected PLMN. In one example, in the RM DEREGISTERED state (500), the UE (100) may not be registered with the network. Since the UE (100) context within the AMF (155) may not contain valid location or routing information for the UE (100), the UE (100) may not be reachable by the AMF (155). In one example, the UE (100) context may be stored in the UE (100) and the AMF (155). In one example, in the RM REGISTERED state (510), the UE (100) can be registered with the network. In the RM-REGISTERED (510) state, the UE (100) can receive services that may require registration with the network.

[0097] In an exemplary embodiment, in an AMF (155) for a UE (100) that can reflect the registration status of the UE (100) in a selected PLMN, two RM statuses, RM-DEREGISTERED (520) and RM-REGISTERED (530), may be used.

[0098] As illustrated in FIGS. 6a and 6b, the connection management (CM) may include establishing and releasing a signaling connection between the UE (100) and the AMF (155) via an N1 interface. The signaling connection may be used to enable NAS signaling exchange between the UE (100) and the core network. The signaling connection between the UE (100) and the AMF (155) may include both an AN signaling connection between the UE (100) and the (R)AN (105) (e.g., an RRC connection via 3GPP access), and an N2 connection to the UE (100) between the AN and the AMF (155).

[0099] As illustrated in FIGS. 6a and 6b, for the NAS signal connection between the AMF (155) and the UE (100), two CM states, CM-IDLE (600, 620) and CM-CONNECTED (610, 630), may be used. In the CM-IDLE (600) state, the UE (100) may be in the RM-REGISTERED (510) state and may not have an established NAS signal connection with the AMF (155) via N1. The UE (100) may perform cell selection, cell reselection, PLMN selection, etc. In the CM-CONNECTED (610) state, the UE (100) may have a NAS signal connection with the AMF (155) via N1.

[0100] In an exemplary embodiment, in the AMF (155), two CM states, CM-IDLE (620) and CM-CONNECTED (630), may be used for the UE (100).

[0101] In one example, an RRC inactive state may be applied to an NG-RAN (e.g., this may be applied to NRs and E-UTRAs connected to a 5G CN). Based on the network configuration, the AMF (155) may provide auxiliary information to the NG RAN (105) regarding whether the UE (100) can be transmitted in an RRC inactive state to support the decision of the NG RAN (105). If the UE (100) is in an RRC inactive state and CM-CONNECTED (610), the UE (100) may resume the RRC connection due to uplink data delay, terminal initiation signaling procedures as a response to RAN (105) paging to notify the network that it has left the RAN (105) notification area, etc.

[0102] In one example, NAS signaling management may include establishing and releasing NAS signaling connections. In the CM-IDLE (600) state, a NAS signaling connection establishment function may be provided by the UE (100) and the AMF (155) to establish a NAS signaling connection for the UE (100). A procedure to release the NAS signaling connection may be initiated by a 5G (R)AN (105) node or the AMF (155).

[0103] In one example, reachability management of the UE (100) can detect whether the UE (100) is reachable and can provide the UE (100) location (e.g., access node) to the network to reach the UE (100). Reachability management can be performed by paging the UE (100) and tracking the UE (100) location. UE (100) location tracking may include both UE (100) registration area tracking and UE (100) reachability tracking. The UE (100) and the AMF (155) can trade off UE (100) reachability characteristics in the CM-IDLE (600, 620) state during the registration procedure and registration update procedure.

[0104] In one example, two UE (100) reachability categories may be compromised between the UE (100) and the AMF (155) for the CM-IDLE (600, 620) state. 1) UE (100) reachability that allows mobile device terminated data while the UE (100) is in CM-IDLE (600) mode. 2) Terminal Initiation Connection Only (MICO) mode. The 5GC may support a PDU connection service that provides the exchange of PDUs between the UE (100) and the data network identified by the DNN. The PDU connection service may be supported through PDU sessions established upon a request from the UE (100).

[0105] In one example, a PDU session may support one or more PDU session types. PDU sessions may be established (e.g., upon request by UE (100)), modified (e.g., upon request by UE (100) and 5GC) and / or released (e.g., upon request by UE (100) and 5GC) using NAS SM signaling exchanged via N1 between UE (100) and SMF (160). Upon request from the application server, 5GC may trigger a specific application in UE (100). Upon receiving the trigger, UE (100) may transmit it to an identified application within UE (100). An identified application within UE (100) may establish a PDU session for a specific DNN.

[0106] In one example, the 5G QoS model may support a QoS flow-based framework as illustrated in FIG. 7. The 5G QoS model may support both QoS flows that require a guaranteed flow bitrate and QoS flows that may not require a guaranteed flow bitrate. In one example, the 5G QoS model may support reflected QoS. The QoS model may include flow mapping or packet marking in the UPF (110)(CN_UP)(110), AN (105), and / or UE (100). In one example, packets may arrive from and / or be scheduled for the application / service layer (730) of the UE (100), UPF (110)(CN_UP)(110), and / or AF (145).

[0107] In one example, a QoS flow may be the granularity of QoS differentiation within a PDU session. A QoS flow ID, QFI, may be used to identify QoS flows in a 5G system. In one example, user plane traffic with the same QFI within a PDU session may receive the same traffic forwarding processing. The QFI may be carried within an encapsulation header on N3 and / or N9 (e.g., without any modification to the end-to-end packet header). In one example, the QFI may be applied to PDUs having different types of payloads. The QFI may be unique within a PDU session.

[0108] In one example, QoS parameters of a QoS flow may be provided to (R)AN (105) as a QoS profile via N2 when NG-RAN is used during PDU session establishment, QoS flow establishment, or whenever a user plane is activated. In one example, a default QoS rule may be required for all PDU sessions. SMF (160) may assign a QFI to a QoS flow and derive QoS parameters from information provided by PCF (135). In one example, SMF (160) may provide the QFI to (R)AN (105) along with a QoS profile containing QoS parameters of the QoS flow.

[0109] In one example, a 5G QoS flow may be a granularity for QoS forwarding processing in a 5G system. Traffic mapped to the same 5G QoS flow may receive the same forwarding processing (e.g., scheduling policy, queue management policy, rate shaping policy, RLC configuration, etc.). In one example, providing different QoS forwarding processing may require separate 5G QoS flows.

[0110] In one example, the 5G QoS metric may be a scalar that can be used as a reference for specific QoS forwarding actions (e.g., packet loss rate, packet delay budget) to be provided to the 5G QoS flow. In one example, the 5G QoS metric may be implemented in the access network by a 5QI that references node-specific parameters capable of controlling QoS forwarding processing (e.g., weighted scheduling, acknowledgment threshold, queue management threshold, link layer protocol configuration, etc.).

[0111] In one example, the 5GC can support edge computing and allow operator(s) and third-party services to be hosted close to the UE's access connection point. The 5G core network can select a UPF (110) close to the UE (100) and execute traffic coordination from the UPF (110) to the local data network via the N6 interface. In one example, the selection and traffic coordination may be based on UE (100) subscription data, UE (100) location, information from application functions (AF) (145), policies, other relevant traffic rules, etc. In one example, the 5G core network can expose network information and performance to edge computing application functions. Support for edge computing features may include local routing in which the 5G core network can select a UPF (110) to route user traffic to the local data network, traffic coordination in which the 5G core network can select traffic to be routed from the local data network to an application, for example, session and service continuity enabling UE (100) and application mobility, user plane selection and reselection based on input from application functions, network performance exposure in which the 5G core network and application functions can provide information to each other via NEf (125), QoS and billing in which the PCF (135) can provide rules for QoS control and billing for traffic routed to the local data network, and support for the local area data network in which the 5G core network can support connections to LADN in a specific area where applications are deployed.

[0112] One exemplary 5G system may be a 3GPP system including a 5G access network (105), a 5G core network, and a UE (100). An allowed NSSAI may be, for example, an NSSAI provided by a service PLMN during the registration process, which may represent an NSSAI allowed by the network for a UE (100) in a service PLMN for the current registration area.

[0113] In one example, a PDU connection service may provide an exchange of PDUs between a UE (100) and a data network. A PDU session may be an association between a UE (100) and a data network DN (115) that can provide a PDU connection service. The type of association may be IP, Ethernet, and / or unstructured association.

[0114] The establishment of a user plane connection to a data network through network slice instance(s) may include the following steps: performing an RM procedure to select an AMF (155) that supports the required network slices, and establishing one or more PDU session(s) to the required data network through the network slice instance(s).

[0115] In one example, the set of network slices for the UE (100) may be changed at any time while the UE (100) can be registered with the network, and may be initiated by the network or the UE (100).

[0116] In one example, the periodic registration update may be the re-registration of the UE (100) upon the expiration of the periodic registration timer. The requested NSSAI may be an NSSAI that the UE (100) can provide to the network.

[0117] In one example, a service-based interface may indicate how a set of services can be provided / exposed by a given NF.

[0118] In one example, service continuity may be an uninterrupted user experience of the service, including cases where the IP address and / or anchor point may change. In one example, session continuity may refer to the continuity of a PDU session. A PDU session with IP type session continuity may imply that the IP address is preserved for the lifetime of the PDU session. An uplink classifier may be a UPF (110) function that aims to redirect uplink traffic toward a data network DN (115) based on filter rules provided by the SMF (160).

[0119] In one example, a 5G system architecture can support data connectivity and services that enable deployments for using technologies such as network function virtualization and / or software-defined networking. The 5G system architecture can leverage service-based interactions between control plane (CP) network functions, where identified. In a 5G system architecture, the separation of user plane (UP) functions from control plane functions can be considered. The 5G system can enable network functions to interact directly with other NF(s) if necessary.

[0120] In one example, a 5G system can reduce dependencies between the access network (AN) and the core network (CN). The architecture may include a converged access-agnostic core network having a common AN-CN interface capable of integrating different 3GPP and non-3GPP access types.

[0121] In one example, a 5G system can support stateless NFs, which are an integrated authentication framework in which computing resources are separated from storage resources, performance exposure, and simultaneous access to local and centralized services. To support low-latency services and access to local data networks, UP functions can be deployed close to the access network.

[0122] In one example, a 5G system may support roaming with home routing traffic and / or local breakout traffic at a visited PLMN. An exemplary 5G architecture may be service-based, and interactions between network functions may be represented in two ways: (1) a service-based representation of network functions within a control plane that allows other authorized network functions to access their services (e.g., illustrated in FIG. 1). This representation may also include point-to-point references if necessary. (2) a reference point representation illustrating interactions between NF services in network functions described by a point-to-point reference (e.g., N11) between any two network functions.

[0123] In one example, a network slice may include core network control plane and user plane network functions, 5G radio access networks, N3IWF functions for non-3GPP access networks, etc. Network slices may vary depending on the supported features and network function implementations. An operator may deploy multiple network slice instances that deliver the same features, but may deploy them for different groups of UEs, for example, when delivering different committed services and / or because they may be dedicated to customers. The NSSF (120) may store mapping information between a slice instance ID and an NF ID (or NF address).

[0124] In one example, the UE (100) may be serviced by one or more network slice instances via 5G-AN simultaneously. In one example, the UE (100) may be serviced by k network slices at a time (e.g., k=8, 16, etc.). An AMF (155) instance that logically services the UE (100) may belong to a network slice instance that services the UE (100).

[0125] In one example, a PDU session may belong to one specific network slice instance per PLMN. In one example, different network slice instances may not share a PDU session. Different slices may have slice-specific PDU sessions using the same DNN.

[0126] S-NSSAI (Single Network Slice Selection Auxiliary Information) can identify network slices. S-NSSAI may include a slice / service type (SST), which may refer to expected network slice behavior in terms of features, services, and / or slice differentiator (SD). The slice differentiator may be optional information that complements the slice / service type(s) to allow for additional differentiation to select a specific network slice instance that corresponds to the indicated slice / service type from potentially multiple network slice instances. In one example, the same network slice instance may be selected using different S-NSSAIs. The CN portion of the network slice instance(s) serving the UE (100) may be selected by the CN.

[0127] In one example, the subscription data may include S-NSSAI(s) of network slices subscribed to by the UE (100). One or more S-NSSAIs may be marked as default S-NSSAIs. In one example, k S-NSSAIs may be marked as default S-NSSAIs (e.g., k=8, 16, etc.). In one example, the UE (100) may subscribe to 8 or more S-NSSAIs.

[0128] In one example, the UE (100) may be configured by an HPLMN having an NSSAI configured for each PLMN. If the registration procedure of the UE is successfully completed, the UE (100) may obtain an allowed NSSAI for such PLMN from the AMF (155), which may include one or more S-NSSAIs.

[0129] In one example, an allowed NSSAI may take precedence over a configured NSSAI for a PLMN. The UE (100) may use an S-NSSAI within the allowed NSSAI corresponding to a network slice for subsequent network slice selection procedures in the PLMN being served.

[0130] In one example, the establishment of a user plane connection to a data network through network slice instance(s) may include the step of performing an RM procedure to select an AMF (155) capable of supporting the required network slice, and the step of establishing one or more PDU sessions to the required data network through network slice instance(s).

[0131] In one example, when a UE (100) registers with a specific PLMN, if the UE (100) has a configured NSSAI or an allowed NSSAI for that PLMN, the UE (100) may provide the network and NAS layers of the RRC with a requested NSSAI, including S-NSSAI(s) corresponding to the slice(s) for which the UE (100) is attempting to register, a temporary user ID, etc., if already assigned to the UE. The requested NSSAI may be a configured-NSSAI, an allowed-NSSAI, etc.

[0132] In one example, when a UE (100) registers with a specific PLMN, for that PLMN, if the UE (100) does not have a configured NSSAI or an allowed NSSAI, the RAN (105) can route NAS signaling from the UE (100) to a default AMF (155) or vice versa.

[0133] In one example, a network based on local policies, subscription changes and / or UE (100) mobility may change the set of allowed network slice(s) to which the UE (100) is enrolled. In one example, the network may make the change during the enrollment process or trigger a notification to the UE (100) about the change of supported network slices using an RM process (which may trigger the enrollment process). The network may provide the UE (100) with a new list of allowed NSSAIs and trace zones.

[0134] In one example, during the registration process of a PLMN, if the network determines that a UE (100) can be serviced by a different AMF (155) based on network slice(s) aspects, the AMF (155) that first receives the registration request may redirect the registration request to another AMF (155) through the RAN (105) or through direct signaling between the initial AMF (155) and the target AMF (155).

[0135] In one example, a network operator may provide a network slice selection policy (NSSP) to a UE (100). The NSSP may include one or more NSSP rules.

[0136] In one example, if the UE (100) has one or more PDU sessions established corresponding to a specific S-NSSAI, the UE (100) may route user data of an application in one of the PDU sessions, unless other conditions within the UE (100) may prohibit the use of the PDU sessions. If the application provides a DNN, the UE (100) may consider the DNN to determine which PDU session to use. In one example, if the UE (100) does not have a PDU session established with a specific S-NSSAI, the UE (100) may request a new PDU session corresponding to the S-NSSAI, along with a DNN that may be provided by the application. In one example, to enable the RAN (105) to select appropriate resources to support network slicing in the RAN (105), the RAN (105) may know the network slices used by the UE (100).

[0137] In one example, the AMF (155) may select an SMF (160) from a network slice instance based on S-NSSAI, DNN and / or other information, e.g., UE (100) subscriptions and local operator policies, etc., when the UE (100) triggers the establishment of a PDU session. The selected SMF (160) may establish a PDU session based on S-NSSAI and DNN.

[0138] In one example, to support network-controlled privacy of slice information for slices accessible to the UE (100), when the UE (100) recognizes or is configured so that privacy considerations can be applied to the NSSAI, if the UE (100) does not have a NAS security context, the UE (100) may not include the NSSAI in NAS signaling, and the UE (100) may not include the NSSAI in unprotected RRC signaling.

[0139] In one example, for roaming scenarios, network slice-specific network functions in VPLMN and HPLMN may be selected based on the S-NSSAI provided by the UE (100) during PDU connection establishment. If a standardized S-NSSAI is used, the selection of slice-specific NF instances may be performed by one or more PLMN(s) based on the provided S-NSSAI. In one example, VPLMN may map the HPLMN's S-NSSAI to the VPLMN's S-NSSAI based on a roaming agreement (e.g., a mapping to the VPLMN's default S-NSSAI). In one example, the selection of slice-specific NF instances in VPLMN may be performed based on the VPLMN's S-NSSAI. In one example, the selection of any slice-specific NF instance in HPLMN may be based on the HPLMN's S-NSSAI.

[0140] As illustrated in FIGS. 8 and 9, the registration procedure can be performed by the UE (100) to receive services, enable mobility tracking, enable reachability, etc.

[0141] In one example, the UE (100) may transmit an AN message (805) (including parameters of the AN, an RM-NAS registration request (registration type, SUCI or SUPI or 5G-GUTI, last visited TAI (if available), security parameters, requested NSSAI, mapping of the requested NSSAI, UE (100) 5GC performance, PDU session status, PDU session(s) to be reactivated, follow-on request, MICO mode priority), etc.) to the (R)AN (105). In one example, for NG-RAN, the AN parameters may include, for example, SUCI or SUPI or 5G-GUTI, a selected PLMN ID, and a requested NSSAI. In one example, the AN parameters may include a cause for establishment. The cause for establishment may provide a reason for requesting the establishment of an RRC connection. In one example, the registration type may indicate whether the UE (100) intends to perform an initial registration (i.e., when the UE (100) is in an RM-DEREGISTERED state), a mobility registration update (e.g., when the UE (100) is in an RM-REGISTERED state and initiates the registration process due to mobility), a periodic registration update (e.g., when the UE (100) is in an RM-REGISTERED state and initiates the registration process due to the expiration of the periodic registration update timer), or an urgent registration (e.g., when the UE (100) is in a restricted service state). In one example, if the UE (100) performs an initial registration (i.e., when the UE (100) is in an RM-DEREGISTERED state) for a PLMN that does not already have a 5G-GUTI, the UE (100) may include its SUCI or SUPI in the registration request. If the home network provides a public key to protect the UE's SUPI, the SUCI may be included.If the UE (100) receives a UE (100) configuration update command indicating that the UE (100) needs to be re-registered and that the 5G-GUTI is invalid, the UE (100) may perform an initial registration and may include SUPI in the registration request message. In the case of an urgent registration, SUPI may be included if the UE (100) does not have a valid 5G-GUTI, and PEI may be included if the UE (100) does not have a valid 5G-GUTI and does not have SUPI. In other cases, 5G-GUTI may be included, which may indicate the final serviced AMF (155). If the UE (100) is already registered through a non-3GPP access in a PLMN different from the new PLMN of the 3GPP access (e.g., a registered PLMN, or not an equivalent PLMN of a registered PLMN), the UE (100) may not provide the 5G-GUTI assigned by the AMF (155) during the registration process in the non-3GPP access in the 3GPP access. If the UE (100) is already registered through a 3GPP access in a PLMN different from the new PLMN of the non-3GPP access (e.g., a registered PLMN), the UE (100) may not provide the 5G-GUTI assigned by the AMF (155) during the registration process in the non-3GPP access in the non-3GPP access. The UE (100) may provide the UE's usage settings based on its configuration. In the case of an initial registration or mobility registration update, to ensure that the network can verify whether the S-NSSAI(s) within the requested NSSAI are allowed based on the subscribed S-NSSAI, the UE (100) may include a mapping of the requested NSSAI, which may be a mapping of one or more S-NSSAIs of the requested NSSAI to the S-NSSAI of the NSSAI configured for the HPLMN.If available, the last visited TAI may be included to help the AMF (155) create a registration zone for the UE. In one example, security parameters may be used for authentication and integrity protection. The requested NSSAI may represent network slice selection auxiliary information. The PDU session status may represent previously established PDU sessions in the UE. If the UE (100) is connected to two AMFs (155) belonging to different PLMNs via 3GPP access and non-3GPP access, the PDU session status may represent established PDU sessions of the current PLMN within the UE. To represent the PDU session(s) that the UE (100) may intend to activate UP connections, the PDU session(s) to be reactivated may be included. If the UE (100) is outside the availability zone of the LADN, the PDU session(s) to be reactivated may not include the PDU session corresponding to the LADN. If the UE (100) may have uplink signaling in a waiting state and the UE (100) may not include PDU session(s) to be reactivated, or if the registration type may indicate that the UE (100) may want to perform an urgent registration, a follow-on request may be included.

[0142] In one example, if SUPI is included or 5G-GUTI does not indicate a valid AMF (155), (R)AT (105) may select an AMF (155) based on (R)AT and the requested NSSAI (if available) (808). If the UE (100) is in a CM-CONNECTED state, (R)AN (105) may forward a registration request message to the AMF (155) based on the UE's N2 connection. If (R)AN (105) may not select a suitable AMF (155), (R)AN (105) may forward the registration request to an AMF (155) configured to perform the AMF (155) selection (808).

[0143] In one example, the (R)AN (105) may send an N2 message (810) (including N2 parameters, an RM-NAS registration request (registration type, SUPI or 5G-GUTI, last visited TAI (if available), security parameters, a requested NSSAI, a mapping of the requested NSSAI, UE (100) 5GC performance, PDU session status, PDU session(s) to be reactivated, a keep-alive request, and a MICO mode priority), etc.) to a new AMF (155). In one example, when NG-RAN is used, the N2 parameters may include a selected PLMN ID, location information, cell identity, and RAT type related to the cell where the UE (100) is waiting. In one example, when NG-RAN is used, the N2 parameters may include the cause of establishment.

[0144] In one example, the new AMF (155) may send Namf_Communication_UEContextTransfer (a complete registration request) (815) to the previous AMF (155). In one example, if the UE's 5G-GUTI is included in the registration request and the AMF (155) being serviced has changed since the last registration procedure, the new AMF (155) may call the Namf_Communication_UEContextTransfer service operation (815) on the previous AMF (155), which includes an integrity-protected complete registration request (IE), to request the UE's SUPI and MM context. The previous AMF (155) may use the integrity-protected complete registration request (IE) to verify that the context transfer service operation call corresponds to the requested UE (100). In one example, the previous AMF (155) may send event subscription information by one or more NF consumers for the UE to the new AMF (155). In one example, if the UE (100) identifies itself using PEI, the SUPI request may be omitted.

[0145] In one example, the previous AMF (155) may send a response (815) to the new AMF (155) for Namf_Communication_UEContextTransfer(SUPI, MM context, SMF (160) information, PCF ID). In one example, the previous AMF (155) may respond to the new AMF (155) for the Namf_Communication_UEContextTransfer call by including the UE's SUPI and MM context. In one example, if the previous AMF (155) holds information regarding established PDU sessions, the previous AMF (155) may include SMF (160) information including S-NSSAI(s), SMF (160) identities, and PDU session ID. In one example, if the previous AMF (155) holds information regarding an active NGAP UE-TNLA binding for N3IWF, the previous AMF (155) may include information regarding the NGAP UE-TNLA binding.

[0146] In one example, if SUPI is not provided by the UE (100) and is not retrieved from the previous AMF (155), an identity request procedure (820) may be initiated by the AMF (155) sending an identity request message requesting SUCI to the UE (100).

[0147] In one example, the UE (100) can respond using an identity response message (820) containing SUCI. The UE (100) can derive SUCI by using the provided public key of the HPLMN.

[0148] In one example, the AMF (155) may decide to initiate UE (100) authentication (825) by calling the AUSF (150). The AMF (155) may select the AUSF (150) based on a SUPI or SUCI. In one example, the AMF (155) is configured to support emergency registration for unauthenticated SUPIs, and if the UE (100) indicates registration type emergency registration, the AMF (155) may skip the authentication and security setup, or the AMF (155) may accept that authentication may fail and the registration process may continue.

[0149] In one example, authentication (830) may be performed by the Nudm_UEAuthenticate_Get operation. The AUSF (150) may discover the UDM (140). If the AMF (155) provides SUCI to the AUSF (150), the AUSF (150) may return SUPI to the AMF (155) after authentication is successful. In one example, if network slicing is used, the AMF (155) may determine whether the registration request needs to be rerouted to where the initial AMF (155) refers to the AMF (155). In one example, the AMF (155) may initiate NAS security functions. In one example, upon completion of the NAS security function setup, the AMF (155) may initiate an NGAP procedure so that the 5G-AN can use it to secure procedures with the UE. In one example, the 5G-AN can store a security context and acknowledge it to the AMF (155). The 5G-AN can use the security context to protect messages exchanged with the UE.

[0150] In one example, the new AMF (155) may send Namf_Communication_RegistrationCompleteNotify (835) to the previous AMF (155). If the AMF (155) is changed, the new AMF (155) may notify the previous AMF (155) that the registration of the UE (100) within the new AMF (155) can be completed by calling the Namf_Communication_RegistrationCompleteNotify service operation. If the authentication / security procedure fails, the registration may be denied, and the new AMF (155) may call the Namf_Communication_RegistrationCompleteNotify service operation toward the previous AMF (155) with a denial indication reason code. The previous AMF (155) may continue as if the UE (100) context transfer service operation was never received. If one or more S-NSSAIs used in the previous registration area may not be serviced in the target registration area, the new AMF (155) may determine which PDU sessions may not be supported in the new registration area. The new AMF (155) may call the Namf_Communication_RegistrationCompleteNotify service operation toward the previous AMF (155), including the rejected PDU session ID and the reason for rejection (e.g., S-NSSAI is no longer available). The new AMF (155) may change the PDU session state accordingly. The previous AMF (155) may notify the corresponding SMF (160)(s) to release the UE's SM context locally by calling the Nsmf_PDUSession_ReleaseSMContext service operation.

[0151] In one example, a new AMF (155) may transmit an identity request / response (840) (e.g., PEI) to the UE (100). If the PEI is not provided by the UE (100) or is not retrieved from the previous AMF (155), an identity request procedure may be initiated by the AMF (155) transmitting an identity request message to the UE (100) to retrieve the PEI. The PEI may be transmitted encrypted and may not be authenticated unless the UE (100) performs an emergency registration. In the case of an emergency registration, the UE (100) may include the PEI in the registration request.

[0152] In one example, the new AMF (155) can initiate an ME identity check (845) by calling the N5g-eir_EquipmentIdentityCheck_Get service operation (845).

[0153] In one example, based on SUPI, a new AMF (155) can select a UDM (140) (905). The UDM (140) can select a UDR instance. In one example, the AMF (155) can select a UDM (140).

[0154] In one example, if the AMF (155) has changed since the last registration procedure, or if the UE (100) provides a SUPI that does not refer to a valid context within the AMF (155), or if the UE (100) registers the same AMF (155) that is already registered for a non-3GPP access (e.g., the UE (100) is registered for a non-3GPP access and may initiate a registration procedure to add a 3GPP access), the new AMF (155) may be registered with the UDM (140) using Nudm_UECM_Registration (910) and may subscribe to be notified when the UDM (140) can unregister the AMF (155). The UDM (140) may store the AMF (155) identity associated with the access type and may not remove the AMF (155) identity associated with a different access type. The UDM (140) can store information provided from the subscription within the UDR by Nudr_UDM_Update. In one example, the AMF (155) can retrieve access and mobility subscription data and SMF (160) select subscription data using Nudm_SDM_Get (915). The UDM (140) can retrieve this information from the UDR by Nudr_UDM_Query (access and mobility subscription data). After a successful response is received, the AMF (155) can subscribe to be notified using Nudm_SDM_Subscribe (920) if the requested data can be modified. The UDM (140) can subscribe to the UDR by Nudr_UDM_Subscribe. If GPSI is available in the UE (100) subscription data, GPSI can be provided to the AMF (155) from the subscription data from the UDM (140). In one example, the new AMF (155) can provide the access type to be serviced to the UE (100) for the UDM (140), and the access type can be set to 3GPP access.The UDM (140) can store the associated access type along with the AMF (155) serviced within the UDR via Nudr_UDM_Update. The new AMF (155) can create an MM context for the UE (100) after obtaining mobility subscription data from the UDM (140). In one example, if the UDM (140) stores the associated access type along with the AMF (155) serviced, the UDM (140) can initiate Nudm_UECM_DeregistrationNotification (921) to the previous AMF (155) corresponding to the 3GPP access. The previous AMF (155) can remove the UE's MM context. If the reason for removing the service NF indicated by the UDM (140) is initial registration, the previous AMF (155) may call the Namf_EventExposure_Notify service operation on all associated SMFs (160) of the UE (100) to notify that the UE (100) has been unsubscribed from the previous AMF (155). Upon receiving this notification, the SMF (160) may release the PDU session(s). In one example, the previous AMF (155) may not subscribe to the UDM (140) for the subscription data using Nudm_SDM_unsubscribe (922).

[0155] In one example, when the AMF (155) decides to initiate communication with the PCF (135), for example, when the AMF (155) has not yet acquired an access and mobility policy for the UE (100) or when the access and mobility policy within the AMF (155) is no longer valid, the AMF (155) may select the PCF (135) (925). When the new AMF (155) receives a PCF ID from the previous AMF (155) and successfully contacts the PCF (135) identified by the PCF ID, the AMF (155) may select the (V-)PCF identified by the PCF ID. If the PCF (135) identified by the PCF ID is not used (e.g., no response from the PCF (135)), or if there is no PCF ID received from the previous AMF (155), the AMF (155) can select the PCF (135) (925).

[0156] In one example, the new AMF (155) may perform policy association establishment (930) during the registration process. When the new AMF (155) contacts the PCF (135) identified by the (V-)PCF ID received during the movement between the AMFs (155), the new AMF (155) may include the PCF-ID in the Npcf_AMPolicyControl Get operation. When the AMF (155) notifies the PCF (135) of mobility restrictions (e.g., UE (100) location) for coordination, or when the PCF (135) updates mobility restrictions due to certain conditions (e.g., application in use, time and date), the PCF (135) may provide the updated mobility restrictions to the AMF (155).

[0157] In one example, PCF (135) can call the Namf_EventExposure_Subscribe service operation (935) to subscribe to UE (100) events.

[0158] In one example, the AMF (155) may send Nsmf_PDUSession_UpdateSMContext (936) to the SMF (160). In one example, the AMF (155) may call Nsmf_PDUSession_UpdateSMContext if the PDU session(s) to be reactivated are included in the registration request. The AMF (155) may send an Nsmf_PDUSession_UpdateSMContext request to the SMF (160) associated with the PDU session(s) to activate the user plane connections of the PDU session(s). The SMF (160) may decide to trigger, for example, the insertion, removal, or change of the intermediate UPF (110) of the PSA. If intermediate UPF (110) insertion, removal, or relocation is performed for PDU session(s) that are not included in the PDU session(s) to be reactivated, the procedure may be performed without N11 and N2 interactions updating the N3 user plane between (R)AN (105) and 5GC. AMF (155) may call the Nsmf_PDUSession_ReleaseSMContext service operation toward SMF (160) if any PDU session state indicates that it has been released from UE (100). AMF (155) may call the Nsmf_PDUSession_ReleaseSMContext service operation toward SMF (160) to release any network resources associated with the PDU session.

[0159] In one example, the new AMF (155) can send an N2 AMF (155) mobility request (940) to the N3IWF. If the AMF (155) is changed, the new AMF (155) can create an NGAP UE (100) association for the N3IWF to which the UE (100) is connected. In one example, the N3IWF can respond to the new AMF (155) using an N2 AMF (155) mobility response (940).

[0160] In one example, a new AMF (155) may transmit a registration approval (955) (including a 5G-GUTI, registration area, mobility restriction, PDU session status, allowed NSSAI, [mapping of allowed NSSAI], periodic registration update timer, LADN information and allowed MICO mode, IMS voice assistance indication on PS session, emergency service assistance indicator, etc.) to the UE (100). In one example, the AMF (155) may transmit a registration approval message to the UE (100) indicating that the registration request has been approved. If the AMF (155) assigns a new 5G-GUTI, the 5G-GUTI may be included. If the AMF (155) assigns a new registration area, the registration area may be transmitted to the UE (100) via the registration approval message (955). If the registration area included in the registration approval message does not exist, the UE (100) may consider the previous registration area to be valid. In one example, if mobility restrictions can be applied to the UE (100), mobility restrictions may be included, and the registration type may not be an urgent registration. The AMF (155) may present established PDU sessions to the UE (100) in the PDU session state. The UE (100) may locally remove any internal resources associated with PDU sessions that are not marked as established in the received PDU session state. In one example, if the UE (100) is connected to two AMFs (155) belonging to different PLMNs via 3GPP access and non-3GPP access, the UE (100) may locally remove any internal resources associated with PDU sessions of the current PLMN that are not marked as established in the received PDU session state. If PDU session state information is in the registration request, the AMF (155) may present the PDU session state to the UE. The mapping of an allowed NSSAI may be a mapping of one or more S-NSSAIs of an allowed NSSAI to an S-NSSAI configured for HPLMN.The AMF (155) may include LADN information for LADNs available within the registration area for the UE determined by the AMF (155) in the registration approval message (955). If the UE (100) includes MICO mode in the request, the AMF (155) may respond whether MICO mode can be used. The AMF (155) may set an IMS voice support indicator on the PS session. In one example, to set an IMS voice support indicator on the PS session, the AMF (155) may perform a UE / RAN radio information and compatibility request procedure to check the compatibility of the UE (100) and the RAN radio performance related to IMS voice on the PS. In one example, an emergency service support indicator may notify the UE (100) that emergency services are supported, and, for example, the UE (100) may request a PDU session for emergency services. In one example, the handover restriction list and UE-AMBR can be provided to the NG-RAN by the AMF (155).

[0161] In one example, the UE (100) may send a registration complete (960) message to the new AMF (155). In one example, the UE (100) may send a registration complete message (960) to the AMF (155) to acknowledge that a new 5G-GUTI may be assigned. In one example, if information regarding the PDU session(s) to be reactivated is not included in the registration request, the AMF (155) may disconnect the signaling connection with the UE (100). In one example, if a connection-keeping request is included in the registration request, the AMF (155) may not disconnect the signaling connection after the completion of the registration procedure. In one example, if the AMF (155) knows that some signaling is pending within the AMF (155) or between the UE (100) and the 5GC, the AMF (155) may not disconnect the signaling connection after the completion of the registration procedure.

[0162] As illustrated in FIGS. 10 and 11, a service request procedure, for example, a service request procedure triggered by the UE (100) in the CM-IDLE state, may be used to request the establishment of a secure connection to the AMF (155). FIG. 11 is a continuation of FIG. 10 illustrating the service request procedure. The service request procedure may be used to enable user plane connections for established PDU sessions. The service request procedure may be triggered by the UE (100) or 5GC, and may be used when the UE (100) is in CM-IDLE and / or CM-CONNECTED, and may selectively enable user plane connections for some of the established PDU sessions.

[0163] In one example, a UE (100) in a CM IDLE state may initiate a service request procedure to transmit uplink signaling messages, user data, etc., such as in response to a network paging request. In one example, after receiving a service request message, the AMF (155) may perform authentication. In one example, after establishing a signaling connection to the AMF (155), the UE (100) or the network may transmit signaling messages through the AMF (155), for example, a PDU session establishment from the UE (100) to the SMF (160).

[0164] In one example, for any service request, the AMF (155) may respond with a service acknowledgment message to synchronize the PDU session state between the UE (100) and the network. If the service request may not be acknowledged by the network, the AMF (155) may respond to the UE (100) with a service denial message. The service denial message may include an indication or cause code requesting the UE (100) to perform a registration update procedure. In one example, for a service request due to user data, the network may take additional actions if user plane connection activation may not be successful. In the example illustrated in FIGS. 10 and 11, two or more UPFs may be included, for example, the previous UPF (110-2) and the PDU session anchor PSA UPF (110-3).

[0165] In one example, the UE (100) may transmit an AN message to the (R)AN (105) containing AN parameters, mobility management, and MM NAS service requests (1005) (e.g., a list of PDU sessions to be activated, a list of allowed PDU sessions, security parameters, PDU session status, etc.). In one example, the UE (100) may provide a list of PDU sessions to be activated when the UE (100) can reactivate the PDU session(s). A list of allowed PDU sessions may be provided by the UE (100) when a service request may be a response to paging or NAS notifications, and may identify PDU sessions that may be transmitted to or associated with access to which the service request may be transmitted. In one example, for NG-RAN, the AN parameters may include a selected PLMN ID and a cause of establishment. The cause of establishment may provide the reason for requesting the establishment of an RRC connection. The UE (100) can send a NAS service request message encapsulated within an RRC message for the RAN (105) to the AMF (155).

[0166] In one example, if a service request can be triggered for user data, the UE (100) can identify the PDU session(s) that are activated in the NAS service request message by using a list of PDU sessions to be activated. If a service request can be triggered for signaling, the UE (100) may not identify any PDU session(s). If this procedure can be triggered for a paging response and / or if the UE (100) can simultaneously have user data to be transmitted, the UE (100) can identify the PDU session(s) that are activated in the MM NAS service request message by using a list of PDU sessions to be activated.

[0167] In one example, if a service request on a 3GPP access can be triggered in response to paging indicating a non-3GPP access, the NAS service request message can identify, from a list of allowed PDU sessions, a list of PDU sessions associated with the non-3GPP access that can be reactivated via 3GPP. In one example, the PDU session status can indicate PDU sessions available to the UE (100). In one example, the UE (100) may not trigger a service request procedure for a PDU session corresponding to the LADN if the UE (100) may be outside the available area of ​​the LADN. The UE (100) may not identify these PDU session(s) in a list of PDU sessions to be activated if the service request can be triggered for other reasons.

[0168] In one example, (R)AN (105) may transmit an N2 message (1010) (e.g., a service request) containing N2 parameters, an MM NAS service request, etc. to an AMF (155). The AMF (155) may reject the N2 message if it may not be able to process the service request. In one example, if NG-RAN can be used, the N2 parameters may include a 5G-GUTI, a selected PLMN ID, location information, a RAT type, a cause of establishment, etc. In one example, the 5G-GUTI may be obtained from an RRC procedure, and (R)AN (105) may select an AMF (155) based on the 5G-GUTI. In one example, the location information and the RAT type may be related to a cell where the UE (100) can wait. In one example, based on the PDU session status, the AMF (155) may initiate a PDU session release procedure in the network for PDU sessions where the PDU session ID(s) may be indicated as not available to the UE (100).

[0169] In one example, if a service request is not integrity protected or if integrity protection verification fails, the AMF (155) may initiate a NAS authentication / security procedure (1015).

[0170] In one example, when the UE (100) triggers a service request to establish a signal connection following the successful establishment of a signal connection, the UE (100) and the network can exchange NAS signaling.

[0171] In one example, the AMF (155) can send a PDU session update context request (1020), for example, an Nsmf_PDUSession_UpdateSMContext request including PDU session ID(s), cause(s), UE (100) location information, access type, etc. to the SMF (160).

[0172] In one example, the Nsmf_PDUSession_UpdateSMContext request may be invoked by the AMF (155) when the UE (100) can identify the PDU session(s) to be activated in the NAS service request message. In one example, the Nsmf_PDUSession_UpdateSMContext request may be triggered by the SMF (160) which may be associated with a different PDU session ID(s) that are not the PDU session(s) identified by the UE (100) that trigger the procedure. In one example, the Nsmf_PDUSession_UpdateSMContext request may be triggered by the SMF (160) when the current UE (100) location may be outside the area of ​​validity for the N2 information provided by the SMF (160) during the network-triggered service request procedure. The AMF (155) may not transmit the N2 information provided by the SMF (160) during the network-triggered service request procedure.

[0173] In one example, the AMF (155) can determine the PDU session(s) to be activated and send an Nsmf_PDUSession_UpdateSMContext request to the SMF (160) associated with the PDU session(s), along with a set of causes to indicate the establishment of user plane resources for the PDU session(s).

[0174] In one example, if the procedure may be triggered in response to paging indicating a non-3GPP access, and the list of allowed PDU sessions provided by the UE (100) may not include the PDU session that the UE (100) was paged to, the AMF (155) may notify the SMF (160) that the user plane for the PDU session may not be reactivated. The service request procedure may succeed without reactivating the user plane for any PDU session, and the AMF (155) may notify the UE (100).

[0175] In one example, if the PDU session ID may correspond to a LADN and the SMF (160) can determine that the UE (100) may be outside the availability zone of the LADN based on the location of the UE (100) reported by the AMF (155), the SMF (160) may decide to maintain the PDU session (based on local policies), deny activation of the user plane connection for the PDU session, and notify the AMF (155). In one example, if the procedure may be triggered by a network-triggered service request, the SMF (160) may notify the UPF (110) that sent the data notification to discard downlink data for the PDU sessions and / or not provide additional data notification messages. The SMF (160) may respond to the AMF (155) with an appropriate denial cause, and the user plane activation of the PDU session may be stopped.

[0176] In one example, if the PDU session ID may correspond to a LADN and the SMF (160) can determine that the UE (100) may be outside the availability zone of the LADN based on the location of the UE (100) reported by the AMF (155), the SMF (160) may decide to release the PDU session (based on local policies). The SMF (160) may release the PDU session locally and notify the AMF (155) that the PDU session may be released. The SMF (160) may respond to the AMF (155) with an appropriate denial reason, and the user plane activation of the PDU session may be stopped.

[0177] In one example, if the UP activation of a PDU session can be approved by the SMF (160) based on location information received from the AMF (155), the SMF (160) can check the UPF (110) selection (1025) criteria (e.g., slice isolation requirements, slice coexistence requirements, dynamic load of the UPF (110), relative static capacity of the UPF (110) among UPFs supporting the same DNN, UPF (110) locations available in the SMF (160), UE (100) location information, performance of the UPF (110), and capabilities required for a specific UE (100) session). In one example, a suitable UPF (110) may be selected by matching the required functions and features for the UE (100), DNN, and PDU session type (i.e., IPv4, IPv6, Ethernet type, or unstructured type), and where applicable, by matching the static IP address / prefix, the SSC mode selected for the PDU session, the UE (100) subscription profile in the UDM (140), DNAI as included in the PCC rules, local operator policies, S-NSSAI, the access technology used by the UE (100), the UPF (110) logical topology, etc., and may decide to perform one or more of the following: continue using the current UPF(s); if the UE (100) moves out of the service area of ​​the UPF (110) that was previously connected to the (R)AN (105) while maintaining the UPF(s) acting as the PDU session anchor, select a new intermediate UPF (110) (or add / remove the intermediate UPF (110); For example, if the UE (100) moves out of the service area of ​​the anchor UPF (110) while connected to the RAN (105), trigger the re-establishment of the PDU session to perform relocation / reassignment of the UPF (110) acting as the PDU session anchor.

[0178] In one example, the SMF (160) may send an N4 session establishment request (1030) to the UPF (110) (e.g., a new intermediate UPF (110)). In one example, if the SMF (160) may select the new UPF (110) to operate as an intermediate UPF (110-2) for a PDU session, or if the SMF (160) may select to insert an intermediate UPF (110) for a PDU session that may not have an intermediate UPF (110-2), an N4 session establishment request (1030) message providing packet detection, data forwarding, enforcement, and reporting rules to be installed on the new intermediate UPF may be sent to the new UPF (110). PDU session anchor addressing information (on N9) for this PDU session may be provided to the intermediate UPF (110-2).

[0179] In one example, when a new UPF (110) is selected by the SMF (160) to replace the previous (intermediate) UPF (110-2), the SMF (160) may include a data forwarding indication. The data forwarding indication may indicate to the UPF (110) that a second tunnel endpoint may be reserved for DL ​​data buffered from the previous I-UPF.

[0180] In one example, the new UPF (110) (intermediate) may send an N4 session establishment response message (1030) to the SMF (160). If the UPF (110) can assign CN tunnel information, the UPF (110) may provide the SMF (160) with DL CN tunnel information and UL CN tunnel information (e.g., CN N3 tunnel information) for the UPF (110) acting as the PDU session anchor. If a data forwarding indication can be received, the new (intermediate) UPF (110) acting as the N3 endpoint may send DL CN tunnel information for the previous (intermediate) UPF (110-2) to the SMF (160). The SMF (160) may start a timer to release resources within the previous intermediate UPF (110-2).

[0181] In one example, if the SMF (160) can select a new intermediate UPF (110) for the PDU session or remove the previous I-UPF (110-2), the SMF (160) can send an N4 session modification request message (1035) to the PDU session anchor, PSA UPF (110-3), which provides data forwarding indications and DL tunnel information from the new intermediate UPF (110).

[0182] In one example, if a new intermediate UPF (110) can be added for a PDU session, the (PSA) UPF (110-3) can start transmitting DL data to the new I-UPF (110) as indicated in the DL tunnel information.

[0183] In one example, if a service request can be triggered by the network and the SMF (160) can remove the previous I-UPF (110-2) and not replace the previous I-UPF (110-2) with a new I-UPF (110), the SMF (160) may include a data forwarding indication within the request. The data forwarding indication may indicate to the (PSA) UPF (110-3) that a second tunnel endpoint may be reserved for DL ​​data buffered from the previous I-UPF (110-2). In this case, the PSA UPF (110-3) may begin buffering DL data that can be received simultaneously from the N6 interface.

[0184] In one example, the PSA UPF (110-3) (PSA) may send an N4 session modification response (1035) to the SMF (160). In one example, if a data forwarding indication can be received, the PSA UPF (110-3) may be an N3 endpoint and may send CN DL tunnel information for the previous (intermediate) UPF (110-2) to the SMF (160). The SMF (160) may start a timer to release resources from the previous intermediate UPF (110-2) (if any).

[0185] In one example, the SMF (160) may send an N4 session modification request (1045) (which may include, for example, a new UPF (110) address, a new UPF (110) DL tunnel ID, etc.) to the previous UPF (110-2). In one example, if a service request can be triggered by the network and / or if the SMF (160) can remove the previous (intermediate) UPF (110-2), the SMF (160) may send an N4 session modification request message to the previous (intermediate) UPF (110-2) and provide DL tunnel information for buffered DL data. If the SMF (160) can assign a new I-UPF (110), DL tunnel information from the new (intermediate) UPF (110) may operate as an N3 endpoint. If the SMF (160) may not assign a new I-UPF (110), the DL tunnel information may be from a new UPF (110) (PSA) (110-3) acting as an N3 endpoint. The SMF (160) may start a timer to monitor the forwarding tunnel. In one example, the previous (intermediate) UPF (110-2) may send an N4 session modification response message to the SMF (160).

[0186] In one example, if the I-UPF (110-2) can be relocated and a forwarding tunnel is established to the new I-UPF (110), the previous (intermediate) UPF (110-2) can forward the buffered data to the new (intermediate) UPF (110) acting as the N3 endpoint. In one example, if the previous I-UPF (110-2) can be removed and the new I-UPF (110) can not be assigned to the PDU session and a forwarding tunnel is established to the UPF (110)(PSA)(110-3), the previous (intermediate) UPF (110-2) can forward the buffered data to the UPF (110)(PSA)(110-3) acting as the N3 endpoint.

[0187] In one example, upon receiving a request for Nsmf_PDUSession_UpdateSMContext with a cause including, for example, the establishment of user plane resources, the SMF (160) may send an N11 message (1060), for example, an Nsmf_PDUSession_UpdateSMContext response (including N1 SM container (PDU session ID, PDU session re-establishment indication), N2 SM information (PDU session ID, QoS profile, CN N3 tunnel information, S-NSSAI), and cause) to the AMF (155). The SMF (160) may determine whether UPF (110) reassignment can be performed based on UE (100) location information, UPF (110) service area and operator policies. In one example, for a PDU session that the SMF (160) can determine to be serviced by the current UPF (110), e.g., a PDU session anchor or an intermediate UPF, the SMF (160) can generate N2 SM information and send an Nsmf_PDUSession_UpdateSMContext response (1060) to the AMF (155) to establish user plane(s). The N2 SM information may include information that the AMF (155) can provide to the RAN (105). In one example, for a PDU session that the SMF (160) can determine to require the relocation of the UPF (110) for the PDU session anchor (UPF), the SMF (160) can refuse the activation of the UP of the PDU session by sending an Nsmf_PDUSession_UpdateSMContext response to the UE (100) via the AMF (155), which may include an N1 SM container. The N1 SM container may include a corresponding PDU session ID and a PDU session re-establishment indicator.

[0188] When receiving a Namf_EventExposure_Notify from AMF (155) to SMF (160) indicating that the UE (100) is reachable, if SMF (160) may have pending DL data, SMF (160) may call the Namf_Communication_N1N2MessageTransfer service operation on AMF (155) to establish user plane(s) for PDU sessions. In one example, SMF (160) may resume sending a DL data notification to AMF (155) in the case of DL data.

[0189] In one example, if the AMF (155) can notify the SMF (160) that the PDU session may correspond to a LADN and the UE (100) may be outside the availability zone of the LADN, or that the UE (100) may be reached for a regulated priority service and the PDU session to be activated may not be for a regulated priority service, or if the SMF (160) can decide to perform a PSA UPF (110-3) relocation for the requested PDU session, the SMF (160) can send a message to the AMF (155) to refuse the activation of the UP of the PDU session by including the cause in the Nsmf_PDUSession_UpdateSMContext response.

[0190] In one example, the AMF (155) may transmit an N2 request message (1065) (e.g., N2 SM information received from the SMF (160), security context, AMF (155) signaling link ID, handover restriction list, MM NAS service acknowledgment, list of recommended cells / TAs / NG-RAN node identifiers) to the (R)AN (105). In one example, the RAN (105) may store the security context, the AMF (155) signaling link ID, QoS information for QoS flows of PDU sessions that can be activated, and N3 tunnel IDs within the UE (100) RAN (105) context. In one example, the MM NAS service acknowledgment may include the PDU session status within the AMF (155). If the activation of the UP of the PDU session can be denied by the SMF (160), the MM NAS service acknowledgment may include the reason why the PDU session ID and user plane resources may not be activated (e.g., LADN is not available). During the session request procedure, the local PDU session release may be indicated to the UE (100) through the session status.

[0191] In one example, if there are multiple PDU sessions that may include multiple SMFs (160), the AMF (155) may not wait for responses from all SMFs (160) before it can transmit N2 SM information to the UE (100). The AMF (155) may wait for all responses from the SMFs (160) before it can transmit an MM NAS service acknowledgment message to the UE (100).

[0192] In one example, the AMF (155) may include at least one N2 SM information from the SMF (160) when the procedure can be triggered for PDU session user plane activation. The AMF (155) may transmit additional N2 SM information (if any) from the SMF (160) in individual N2 message(s) (e.g., N2 tunnel setup request). Alternatively, if multiple SMFs (160) may be included, the AMF (155) may transmit one N2 request message to the (R)AN (105) after all Nsmf_PDUSession_UpdateSMContext response service actions can be received from all SMFs (160) associated with the UE (100). In this case, the N2 request message may include N2 SM information received from one or more of the Nsmf_PDUSession_UpdateSMContext response and PDU session ID so that the AMF (155) can associate responses with the related SMF (160).

[0193] In one example, if the RAN (105) (e.g., NG-RAN) node can provide a list of recommended cells / TAs / NG-RAN node identifiers during the AN release procedure, the AMF (155) may include information from a list of N2 requests. The RAN (105) may use this information to allocate a RAN (105) notification area if the RAN (105) can determine to enable an RRC inactive state for the UE (100).

[0194] If, during the PDU session establishment procedure, the AMF (155) receives from the SMF (160) an indication that the UE (100) may be using a PDU session associated with latency-sensitive services for any of the PDU sessions established for the UE (100), and if the AMF (155) receives from the UE (100) an indication that CM-CONNECTED can be supported in an RRC disabled state, the AMF (155) may include auxiliary information regarding the UE's RRC disabled. In one example, the AMF (155) based on the network configuration may include auxiliary information regarding the UE's RRC disabled.

[0195] In one example, (R)AN (105) may send a message to UE (100) to perform RRC connection reconfiguration (1070) with UE (100) based on QoS information for all QoS flows of PDU sessions and data wireless bearers in which UP connections can be activated. In one example, user plane security may be established.

[0196] In one example, if the N2 request may include an MM NAS service acknowledgment message, the RAN (105) may forward the MM NAS service acknowledgment to the UE (100). The UE (100) may locally delete the context of PDU sessions that may not be available in the 5GC.

[0197] In one example, if N1 SM information can be transmitted to the UE (100) and indicates that some PDU session(s) can be re-established, the UE (100) can initiate PDU session re-establishment for the PDU session(s) that can be reset after the service request procedure is completed.

[0198] In one example, if user plane radio resources can be set up, uplink data from the UE (100) can be forwarded to the RAN (105). The RAN (105) (e.g., NG-RAN) can transmit uplink data to a provided UPF (110) address and tunnel ID.

[0199] In one example, (R)AN (105) may send an N2 request Ack (1105) (e.g., N2 SM information (including AN tunnel information, a list of accepted QoS flows for PDU sessions where UP connections are active, and a list of denied QoS flows for PDU sessions where UP connections are active)) to AMF (155). In one example, the N2 request message may include N2 SM information(s), e.g., AN tunnel information. RAN (105) may respond to the N2 SM information with a separate N2 message (e.g., N2 tunnel setup response). In one example, if multiple N2 SM information is included in the N2 request message, the N2 request Ack may include multiple N2 SM information and information that enables AMF (155) to associate responses with the relevant SMF (160).

[0200] In one example, the AMF (155) may send an Nsmf_PDUSession_UpdateSMContext request (1110) (N2 SM information (AN tunnel information), RAT type) to the SMF (160) for each PDU session. If the AMF (155) can receive N2 SM information (one or more) from the RAN (105), the AMF (155) may forward the N2 SM information to the relevant SMF (160). If the UE (100) time zone may change compared to the last reported UE (100) time zone, the AMF (155) may include the UE (100) time zone (IE) in the Nsmf_PDUSession_UpdateSMContext request message.

[0201] For example, when a dynamic PCC is deployed, the SMF (160) may initiate notification regarding new location information to the PCF (135) by calling an event exposure notification operation (e.g., the Nsmf_EventExposure_Notify service operation) (if subscribed). The PCF (135) may provide updated policies by calling a policy control update notification message (1115) (e.g., the Npcf_SMPolicyControl_UpdateNotify operation).

[0202] In one example, if the SMF (160) can select a new UPF (110) to act as an intermediate UPF (110) for a PDU session, the SMF (160) can initiate an N4 session modification procedure (1120) for the new I-UPF (110) and provide AN tunnel information. Downlink data from the new I-UPF (110) can be forwarded to the RAN (105) and UE (100). In one example, the UPF (110) can send an N4 session modification response (1120) to the SMF (160). In one example, the SMF (160) can send an Nsmf_PDUSession_UpdateSMContext response (1140) to the AMF (155).

[0203] In one example, when a forwarding tunnel can be established for a new I-UPF (110) and the timer SMF (160) set for the forwarding tunnel can expire, the SMF (160) may send an N4 session modification request (1145) to the new (intermediate) UPF (110) acting as an N3 endpoint to release the forwarding tunnel. In one example, the new (intermediate) UPF (110) may send an N4 session modification response (1145) to the SMF (160). In one example, the SMF (160) may send an N4 session modification request (1150) or an N4 session release request to the PSA UPF (110-3). In one example, if the SMF (160) can continue to use the previous UPF (110-2), the SMF (160) can send an N4 session modification request (1155) while providing AN tunnel information. In one example, the SMF (160) can select a new UPF (110) to operate as an intermediate UPF (110), and if the previous UPF (110-2) is not a PSA UPF (110-3), the SMF (160) can initiate resource release by sending an N4 session release request (release cause) to the previous intermediate UPF (110-2) after the timer expires.

[0204] In one example, the previous intermediate UPF (110-2) may send an N4 session modification response or an N4 session release response (1155) to the SMF (160). The previous UPF (110-2) may acknowledge the modification or release of resources with an N4 session modification response or an N4 session release response message. After this procedure is completed, the AMF (155) may call the Namf_EventExposure_Notify service operation to notify mobility-related events to NFs that may subscribe to the events. In one example, if the SMF (160) is subscribed to a UE (100) that is moving to or out of a region of interest, or if it can indicate that the UE's current location may be moving to or out of a subscribed region of interest, or if the SMF (160) is subscribed to a LADN DNN and the UE (100) may be moving to or out of a region where the LADN is available, or if the UE (100) may be in MICO mode and the AMF (155) has notified the SMF (160) that the UE (100) is unreachable and the SMF (160) may not send a DL data notification to the AMF (155), the AMF (155) may call Namf_EventExposure_Notify toward the SMF (160), and the AMF (155) may notify the SMF (160) that the UE (100) is reachable, or If SMF (160) subscribes to the UE (100) reachability status, AMF (155) can notify the UE (100) of reachability.

[0205] An exemplary PDU session establishment procedure is illustrated in FIGS. 12 and FIGS. 13. In an exemplary embodiment, where the PDU session establishment procedure may be utilized, the UE (100) may transmit a NAS message (1205) (or SM NAS message) to the AMF (155) containing an NSSAI, an S-NSSAI (e.g., requested S-NSSAI, allowed S-NSSAI, subscribed S-NSSAI, etc.), a DNN, a PDU session ID, a request type, a previous PDU session ID, an N1 SM container (PDU session establishment request), etc. In one example, to establish a new PDU session, the UE (100) may generate a new PDU session ID. For example, if an urgent service may be required and an urgent PDU session may not yet be established, the UE (100) may initiate the UE (100) requested PDU session establishment procedure with a request type indicating an urgent request. In one example, the UE (100) may initiate the requested PDU session establishment procedure by transmitting a NAS message containing a request to establish a PDU session within an N1 SM container. The request to establish a PDU session may include a PDU type, an SSC mode, protocol configuration options, etc. In one example, the request type may indicate an initial request if the request to establish a new PDU session is to establish a new PDU session, and may indicate an existing PDU session if the request refers to an existing PDU session between a 3GPP access and a non-3GPP access or an existing PDN connection of the EPC. In one example, the request type may indicate an urgent request if the request to establish a PDU session for urgent services is to establish a PDU session for urgent services. If the request refers to an existing PDU session for urgent services between a 3GPP access and a non-3GPP access, the request type may indicate an existing urgent PDU session.In one example, a NAS message transmitted by the UE (100) may be encapsulated by an AN within an N2 message directed to the AMF (155), which may include user location information and access technology type information. In one example, a PDU session establishment request message may include an SM PDU DN request container containing information for authorizing a PDU session by an external DN. In one example, if the procedure may be triggered for an SSC mode 3 operation, the UE (100) may include a previous PDU session ID in the NAS message that may indicate the PDU session ID of the current PDU session to be released. The previous PDU session ID may be an optional parameter that may be included in this case. In one example, the AMF (155) may receive a NAS message (e.g., a NAS SM message) from the AN along with user location information (cell ID in the case of the RAN (105)). In one example, the UE (100) may not trigger the establishment of a PDU session for a PDU session corresponding to the LADN when the UE (100) is outside the availability zone of the LADN.

[0206] In one example, the AMF (155) may determine, based on the request type, that a NAS message or an SM NAS message may respond to a request for a new PDU session and that a PDU session ID may not be used for any existing PDU session(s) of the UE (100). If the NAS message does not contain an S-NSSAI, the AMF (155) may determine a default S-NSSAI for the requested PDU session based on the UE (100) subscription, or based on an operator policy, if only one default S-NSSAI may be included. In one example, the AMF (155) may perform an SMF (160) selection (1210) and select an SMF (160). If the request type may indicate an initial request or the request may be due to a handover from an EPS, the AMF (155) may store the association of the S-NSSAI, PDU session ID, and SMF (160) ID. In one example, if the request type is an initial request and the message may contain a previous PDU session ID representing an existing PDU session, the AMF (155) may select an SMF (160) and store the association between the new PDU session ID and the selected SMF (160) ID.

[0207] In one example, the AMF (155) may send an N11 message (1215) to the SMF (160), for example, an Nsmf_PDUSession_CreateSMContext request (including SUPI or PEI, DNN, S-NSSAI, PDU session ID, AMF (155) ID, request type, N1 SM container (PDU session establishment request), user location information, access type, PEI, GPSI), or an Nsmf_PDUSession_UpdateSMContext request (including SUPI, DNN, S-NSSAI, PDU session ID, AMF (155) ID, request type, N1 SM container (PDU session establishment request), user location information, access type, RAT type, PEI). In one example, if the AMF (155) may not have an association with the SMF (160) for the PDU session ID provided by the UE (100) (e.g., if the request type indicates an initial request), the AMF (155) may call the Nsmf_PDUSession_CreateSMContext request, but if the AMF (155) already has an association with the SMF (160) for the PDU session ID provided by the UE (100) (e.g., if the request type indicates an existing PDU session), the AMF (155) may call the Nsmf_PDUSession_UpdateSMContext request. In one example, the AMF (155) ID may be the UE's GUAMI that uniquely identifies the AMF (155) servicing the UE (100). The AMF (155) may forward the PDU session ID along with an N1 SM container containing a PDU session establishment request received from the UE (100). AMF (155) may provide PEI instead of SUPI if the UE (100) is registered for emergency services without providing SUPI. If the UE (100) is registered for emergency services but is not authenticated, AMF (155) may indicate that SUPI is not authenticated.

[0208] In one example, if the request type may not indicate an urgent request or an existing urgent PDU session, and if the SMF (160) is not yet registered and subscription data may not be available, the SMF (160) may register with the UDM (140), retrieve subscription data (1225), and subscribe to be notified when subscription data can be modified. In one example, if the request type may indicate an existing PDU session or an existing urgent PDU session, the SMF (160) may determine that the request may be due to a handover between 3GPP access and non-3GPP access, or due to a handover from an EPS. The SMF (160) may identify an existing PDU session based on the PDU session ID. The SMF (160) may not create a new SM context, but instead may update an existing SM context and provide a representation of the updated SM context to the AMF (155) in the response. If the request type may be an initial request and the previous PDU session ID may be included in the Nsmf_PDUSession_CreateSMContext request, SMF (160) can identify the existing PDU session to be released based on the previous PDU session ID.

[0209] In one example, the SMF (160) may send an N11 message response (1220) to the AMF (155), for example, a PDU session creation / update response, an Nsmf_PDUSession_CreateSMContext response (1220) (cause, SM context ID or N1 SM container (PDU session rejection (cause))) or an Nsmf_PDUSession_UpdateSMContext response.

[0210] In one example, if the SMF (160) can perform auxiliary authorization / authentication (1230) while the DN-AAA server establishes a PDU session, the SMF (160) can select the UPF (110) and trigger the PDU session establishment authorization / authentication.

[0211] In one example, if the request type can represent an initial request, the SMF (160) may select an SSC mode for the PDU session. The SMF (160) may select one or more UPFs as needed. For PDU type IPv4 or IPv6, the SMF (160) may assign an IP address / prefix to the PDU session. For PDU type IPv6, the SMF (160) may assign an interface identifier for the UE (100) to construct its link-local address. For unstructured PDU type, the SMF (160) may assign an IPv6 prefix for tunneling between the PDU session and N6 points (based on UDP / IPv6).

[0212] In one example, when a dynamic PCC is deployed, the SMF (160) can perform PCF (135) selection (1235). If the request type indicates an existing PDU session or an existing urgent PDU session, the SMF (160) can use the PCF (135) already selected for the PDU session. If a dynamic PCC is not deployed, the SMF (160) can apply a local policy.

[0213] In one example, the SMF (160) may perform a session management policy establishment procedure (1240) to establish a PDU session with the PCF (135) and obtain default PCC rules for the PDU session. GPSI may be included in the SMF (160) if available. If the request type in 1215 indicates an existing PDU session, the SMF (160) may notify the PCF (135) of events previously subscribed to by the session management policy modification procedure, and the PCF (135) may update policy information within the SMF (160). The PCF (135) may provide the SMF (160) with authorized session-AMBR and authorized 5QI and ARP. The PCF (135) may subscribe to IP allocation / deallocation events within the SMF (160) (and may subscribe to other events).

[0214] In one example, based on the emergency DNN, the PCF (135) can set the ARP of the PCC rules to a value that can be reserved for emergency services.

[0215] In one example, if the request type within 1215 indicates an initial request, the SMF (160) may select an SSC mode for the PDU session. The SMF (160) may select one or more UPFs as needed (1245). For PDU type IPv4 or IPv6, the SMF (160) may assign an IP address / prefix to the PDU session. For PDU type IPv6, the SMF (160) may assign an interface identifier for the UE (100) to construct its link-local address. For unstructured PDU type, the SMF (160) may assign an IPv6 prefix for tunneling between the PDU session and N6 points (e.g., based on UDP / IPv6). In one example, for an Ethernet PDU type PDU session, neither a MAC nor an IP address may be assigned to the UE (100) by the SMF (160) for this PDU session.

[0216] In one example, if the request type within 1215 is an existing PDU session, the SMF (160) can retain the same IP address / prefix that can be assigned to the UE (100) from the source network.

[0217] In one example, if the request type in 1215 indicates an existing PDU session that refers to an existing PDU session that has been moved between 3GPP access and non-3GPP access, the SMF (160) may maintain the SSC mode of the PDU session, e.g., the current PDU session anchor and IP address. In one example, the SMF (160) may trigger the insertion of a new intermediate UPF (110) or the allocation of a new UPF (110). In one example, if the request type indicates an urgent request, the SMF (160) may select the UPF (110) (1245) and select SSC mode 1.

[0218] In one example, the SMF (160) may perform a session management policy modification (1250) procedure to report some events to a previously subscribed PCF (135). If the request type is an initial request, a dynamic PCC is deployed, and the PDU type is IPv4 or IPv6, the SMF (160) may notify the PCF (135) (previously subscribed) with the assigned UE (100) IP address / prefix.

[0219] In one example, PCF (135) can provide updated policies to SMF (160). PCF (135) can provide authorized Session-AMBR and authorized 5QI and ARP to SMF (160).

[0220] In one example, if the request type indicates an initial request, the SMF (160) may initiate an N4 session establishment procedure (1255) to the selected UPF (110). The SMF (160) may initiate an N4 session modification procedure to the selected UPF (110). In one example, the SMF (160) may send an N4 session establishment / modification request (1255) to the UPF (110) and may provide packet detection, enforcement, reporting rules, etc. to be installed on the UPF (110) for this PDU session. If CN tunnel information is assigned by the SMF (160), the CN tunnel information may be provided to the UPF (110). If optional user plane deactivation is required for this PDU session, the SMF (160) may determine a deactivation timer and provide it to the UPF (110). In one example, the UPF (110) may acknowledge by transmitting an N4 session establishment / modification response (1255). If CN tunnel information is assigned by the UPF, the CN tunnel information may be provided to the SMF (160). In one example, if multiple UPFs are selected for a PDU session, the SMF (160) may initiate an N4 session establishment / modification procedure (1255) to one or more UPFs (110) of the PDU session.

[0221] In one example, the SMF (160) may transmit a Namf_Communication_N1N2MessageTransfer (1305) message (PDU session ID, access type, N2 SM information (PDU session ID, QFI(s), QoS profile(s), CN tunnel information, S-NSSAI, Session-AMBR, PDU session type, etc.), and an N1 SM container (including PDU session establishment acknowledgment (QoS rule(s), selected SSC mode, S-NSSAI, assigned IPv4 address, interface identifier, Session-AMBR, selected PDU session type, etc.)). If multiple UPFs are used for the PDU session, the CN tunnel information may include tunnel information related to the UPF (110) that terminates N3. In one example, N2 SM information may convey information that the AMF (155) can forward to the (R)AN (105) (e.g., CN tunnel information corresponding to the core network address of the N3 tunnel corresponding to the PDU session, one or more QoS profiles and corresponding QFIs may be provided to the (R)AN (105), the PDU session ID may be used by signaling with the UE (100) to indicate to the UE (100) the association between the AN resources and the PDU session for the UE (100), etc.). In one example, the PDU session may be associated with S-NSSAI and DNN. In one example, the N1 SM container may include a PDU session establishment acknowledgment that the AMF (155) can provide to the UE (100). In one example, a number of QoS rules and QoS profiles may be included in the PDU session establishment acknowledgment within the N1 SM and in the N2 SM information. In one example, Namf_Communication_N1N2MessageTransfer (1305) may further include a PDU session ID and information that allows AMF (155) to know access to the UE (100) to use.

[0222] In one example, the AMF (155) may transmit an N2 PDU session request (1310) (including N2 SM information and a NAS message (PDU session ID, N1 SM container (PDU session establishment approval, etc.))) to the (R)AN (105). In one example, the AMF (155) may transmit to the (R)AN (105) a NAS message (1310) that may include a PDU session ID and a PDU session establishment targeting the UE (100), and N2 SM information received from the SMF (160) within the N2 PDU session request (1310).

[0223] In one example, the (R)AN (105) may issue an AN-specific signal exchange (1315) with the UE (100) that may be related to information received from the SMF (160). In one example, for a 3GPP RAN (105), an RRC connection reconfiguration procedure may occur with the UE (100) to establish necessary RAN (105) resources related to QoS rules for a PDU session request (1310). In one example, the (R)AN (105) may assign (R)AN (105) N3 tunnel information for a PDU session. In the case of a dual connection, the master RAN (105) node may assign some (zero or more) QFIs to the master RAN (105) node and others to the secondary RAN (105) node. AN tunnel information may include tunnel endpoints for one or more included RAN (105) nodes, and QFIs assigned to one or more tunnel endpoints. QFIs may be assigned to a master RAN (105) node or a secondary RAN (105) node. In one example, (R)AN (105) may forward a NAS message (1310) (PDU session ID, N1 SM container (PDU session establishment acknowledgment)) to UE (100). If the necessary RAN (105) resources are established and the (R)AN (105) tunnel information assignment is successful, (R)AN (105) may provide a NAS message to UE (100).

[0224] In one example, the N2 PDU session response (1320) may include a PDU session ID, a cause, N2 SM information (PDU session ID, AN tunnel information, a list of accepted / rejected QFI(s)), etc. In one example, the AN tunnel information may correspond to the network address of the N3 tunnel corresponding to the PDU session.

[0225] In one example, the AMF (155) can forward N2 SM information received from (R)AN (105) to the SMF (160) via the Nsmf_PDUSession_UpdateSMContext request (1330) (including N2 SM information, request type, etc.). In one example, if a list of denied QFI(s) is included in the N2 SM information, the SMF (160) can release the QoS profiles associated with the denied QFI.

[0226] In one example, the SMF (160) may initiate an N4 session modification procedure (1335) to the UPF (110). The SMF (160) may provide AN tunnel information to the UPF (110) as well as corresponding forwarding rules. In one example, the UPF (110) may provide an N4 session modification response (1335) to the SMF (160).

[0227] In one example, the SMF (160) may send the Nsmf_PDUSession_UpdateSMContext response (1340) (cause) to the AMF (155). In one example, the SMF (160) may subscribe to UE (100) mobility event notifications from the AMF (155) by calling the Namf_EventExposure_Subscribe service operation after this step (e.g., location reports, UE (100) moving into or out of the area of ​​interest). In the case of LADN, the SMF (160) may subscribe to LADN service area event notifications for UE (100) moving into or out of the area of ​​interest by providing the LADN DNN as an indicator for the area of ​​interest. The AMF (155) may forward the relevant events subscribed to by the SMF (160).

[0228] In one example, the SMF (160) may send Nsmf_PDUSession_SMContextStatusNotify(release) (1345) to the AMF (155). In one example, if the PDU session establishment is unsuccessful during the procedure, the SMF (160) may notify the AMF (155) by calling Nsmf_PDUSession_SMContextStatusNotify(release) (1345). The SMF (160) may release any N4 session(s) created, any PDU session address (if assigned) (e.g., IP address), and unassociate with the PCF (135).

[0229] In one example, for IPv6 of the PDU type, the SMF (160) can generate an IPv6 router advertisement (1350) and transmit it to the UE (100) via N4 and UPF (110).

[0230] In one example, if a PDU session may not be established, the SMF (160) may unsubscribe from changes to session management subscription data for the corresponding (SUPI, DNN, S-NSSAI) using Nudm_SDM_Unsubscribe(SUPI, DNN, S-NSSAI) when the SMF (160) no longer handles the UE (100)'s PDU session for this (DNN, S-NSSAI) (1360). In one example, if a PDU session may not be established, the SMF (160) may unsubscribe from a given PDU session using Nudm_UECM_Deregistration(SUPI, DNN, PDU session ID) (1360).

[0231] The 5GS can operate as a standalone Time-Sensitive Networking (TSN) network or as part of a non-standalone TSN network, e.g., an industrial telecommunications network. The 5GS can support three modes of operation as illustrated in Fig. 15. In the fully distributed model illustrated at the bottom of Fig. 15, TSN end stations, e.g., senders and receivers, can transmit TSN stream requirements directly to the TSN network. Each TSN bridge on the path from sender to receiver can propagate TSN user and network configuration information, along with the active topology for the TSN stream, to neighboring bridge(s). Network resources can be managed locally at each TSN bridge. In the centralized network and distributed user model illustrated in the middle of Fig. 15, TSN end stations, e.g., senders and receivers, can transmit TSN stream requirements directly to the TSN network. The TSN stream requirements are forwarded to a centralized network configuration (CNC). TSN bridges can provide their network performance information and active topology information to the CNC. The CNC can have a complete view of the TSN network and is enabled to calculate each end-to-end communication path from the sender to receivers that satisfy the TSN stream requirements provided by the end stations. The calculation result can be provided by the CNC as network configuration information, specifically as TSN configuration information for each TSN bridge in the path between the included TSN end stations (from senders to receivers). In the fully centralized model illustrated at the top of Fig. 15, TSN end stations, e.g., senders and receivers, can transmit TSN stream requirements to a centralized user configuration (CUC). The CUC can adapt the TSN end station stream requirements before transmitting them to the CNC.Except for the fact that CNC can transmit specific TSN configuration information to CUC, CNC performs the same operations as described in the centralized network / distributed user model. CUC can determine / derive TSN configuration information for TSN end stations and notify them accordingly.

[0232] In one example, a TSN system can use 5GS as a TSN link, a TSN bridge, etc. A TSN system can be integrated with 5GS.

[0233] For example, as illustrated in FIG. 17, the 5GS can be used as a TSN link to an external network, for example, as an Ethernet connection / link between a UE and a UPF. The link can be defined by connected entities, namely two TSN bridges, or one TSN end station and one TSN bridge, two TSN end stations, etc. Link performance can be described by the inlet / outlet ports of the TSN bridge connected to the end of the link, or by the TSN streaming requirements of the TSN end stations directly connected to the link. The exposed performance may include latency information, link speed, available bandwidth information, etc.

[0234] In the example illustrated in FIGS. 18 and 19, the 5GS can be used as a TSN bridge. The 5GS can receive TSN-related reservation requests using a 5G QoS framework. The 5GS can use 5G internal signaling to satisfy the TSN reservation requests. When the 5GS is deployed as a TSN bridge (e.g., a logical TSN bridge), the TSN bridge may include an adaptation function that converts 5GS protocols and information objects into TSN protocols and information objects, and vice versa. The 5GS bridge may provide TSN inlet and outlet ports through a TSN converter (device) on the UE side and through a TSN converter (CP and UP) on the CN side toward the DN. The 5GS bridge may support different TSN configuration models. In one example, one or more TSN-compliant interfaces may be used by the TSN bridge with their respective protocols toward TSN end stations, TSN bridges, CNCs, CUCs, etc. on the control plane and / or user plane. Functions required for the TSN bridge's self-management and interaction with the CNC may be located in the network converter.

[0235] In one example, as illustrated in FIG. 20, the 5GS can be integrated with a TSN system. When the 5GS is integrated with a TSN system, individual nodes of the 5GS (e.g., UPF, gNB, etc.) can interact with TSN procedures initiated by TSN endpoints and TSN controllers. This allows the 5GS and associated infrastructure to exist as multiple TSN-compatible endpoints.

[0236] As illustrated in FIG. 14, the 5GS can be integrated with a TSN system. The TSN system can generate control and data traffic and transmit it to the 5GS. The control and data traffic may include TSN QoS information, stream information, port information, etc. Ethernet frames and / or headers may be mapped to or encapsulated within 5G frames / packets and transmitted to the 5GS via a wireless interface. A 5G wireless terminal having an integrated Ethernet adapter may be connected to a wireless device (UE).

[0237] In an exemplary embodiment, a 3GPP network may support TSN bridge delay managed object attributes (e.g., independentDelayMin / Max, dependentDelayMin / Max, etc.) for a 3GPP bridge based on 3GPP attributes, e.g., QoS flow packet delay budget (PDB) values, guaranteed flow bitrate (GFBR), maximum data burst volume (MDBV) displayed in the QoS profile, etc. Mapping of 3GPP attributes to TSN performances may be in an SMF and / or PCF, and exposure of performances toward the TSN bridge may be made through an NEF, SMF, PCF, etc.

[0238] In one example, a TSN bridge delay managed object may include frame length-related attributes per tuple (entry port, exit port, traffic class). Frame length-related attributes may include independentDelay Min / Max (e.g., bridge delay occurring regardless of frame size (usually in ns)), dependentDelay Min / Max (e.g., bridge delay occurring per base volume (usually in ps per byte)), etc.

[0239] In one example as illustrated in FIG. 21, when a centralized model or a fully centralized model and a centralized network / distributed user model are used in a TSN network, 5GS can be enhanced to operate as a TSN bridge in the network. Since CNC maintains the performance of each TSN bridge and the topology of the network in the TSN network, AF can operate as a controller function that collects information related to 5GS virtual bridges and registers it with CNC through a TSN-defined application interface. In one example, based on the information maintained by CNC, CNC can calculate forwarding and scheduling rules for each bridge for the TSN stream required by CUC, which collects TSN stream requirements from end stations for the fully centralized model. In one example, control plane-based QoS compromises can be used. As illustrated in FIG. 21, CNC can generate a TSN-aware QoS profile for the stream by compromising with PCF through the TSN AF. TSN AF can convert TSN traffic characteristics into TSN QoS requirements, TSN QoS profiles, etc.

[0240] In one example, for a control plane-based solution, the AF may operate as a controller function to collect information related to the 5GS virtual bridge (e.g., the AF may receive information from the SMF and register it with the CNC through TSN-defined application interfaces). Such information may include bridge identity, port identity, bridge delay, transmission delay, bridge-related topology information, etc. In one example, the bridge identity may identify a TSN bridge in a TSN network. In one example, ports may identify ports within a TSN bridge. Bridge delay may include the delay values ​​of frames as they pass through the bridge, which may include the maximum and minimum of independent and dependent delays. Transmission delay may be the delay for frames transmitted from a TSN bridge port to a neighbor port on another bridge. Bridge-related topology may include the bridge and port identities and port performance of the TSN bridge and neighbor bridges. In one example, the identities of the virtual bridges and associated ports of the UPF can be pre-configured on the UPF and reported to the AF via the SMF when the UPF is set up. A UE or PDU session can be virtualized as a virtual port on a virtual bridge having an (unique) identity that can be assigned by the SMF or UPF. The TSN AF can interact with the 5G CN, perform mapping between new deterministic QoS profiles for 5GS and TSN network parameters, and trade traffic processing and related QoS policies. In one example, the TSN AF can make direct calls through other 5GC NFs or NEFs.

[0241] In one example, 5GS virtual bridge information may include a bridge ID, port IDs, internal bridge information (e.g., bridge delay), and bridge port-related information (e.g., propagation delay). Information about the 5GS virtual bridge, such as the bridge ID, port IDs, internal bridge information (e.g., bridge delay), and bridge port-related information (e.g., propagation delay), may be reported to the AF by the 5GS control plane.

[0242] In an example as illustrated in FIG. 28, a 5GS virtual bridge may exist for every TSN network (indicated by DNN) and every UPF, and the 5GS virtual bridge user plane may include UPF ports and UE ports connected to these UPF ports via PDU sessions. The identities of the virtual bridge and the associated UPF ports may be pre-configured on the UPF and may be reported to the AF via the SMF when the UPF is set up or a PDU session is established. UE port identities may be unique within the 5GS virtual bridge and may be assigned by the UPF. Information regarding UPF ports and UE ports may be reported to the AF by the SMF directly or via the NEF. Information regarding UPF ports may be reported to the SMF by the UPF using node-level signaling or PDU session-level signaling. Information regarding UE ports may be reported to the SMF by the UE on the NAS or on the UP of its corresponding PDU session. In one example, the UE can operate in switch mode, Ethernet switch mode, etc. In one example, the UE port of the 5GS virtual bridge can be a physical port of the UE, a virtual port / interface of the UE, etc.

[0243] In one example, traffic scheduling on a TSN bridge may occur per traffic class, which is the service level of packet transmission. TSN bridge ports may support different traffic classes. In one example, if the TSN bridge knows the VLANs, TSN bridge ports may support different VLANs. When an SMF selects a UPF for a PDU session, it may consider the traffic classes and VLANs subscribed to by the UE.

[0244] As illustrated in FIG. 28, UPF1 and UPF2 support different VLANs and traffic classes based on their placement. When UE1 and UE2 establish a PDU session, UPF1 and UPF2 are each selected to satisfy the subscribed VLANs and traffic classes. Since there is a bridge delay defined in 802.1QCC for each port pair and each traffic class, UPF can determine the correct port pairs to service the PDU session, and SMF can report the bridge delay for these port pairs. For example, in the case of UE1 in the figure, UPF1 can determine Port 1 supporting traffic class 2, VLAN (100), requested by UE1 to service the PDU session. Subsequently, SMF can report the bridge delay for traffic class 2 for the port pair (UE1 Port and UPF1 Port 1).

[0245] In an example as illustrated in FIG. 29, for 5GS virtual bridge topology discovery, the UPF and UE may report topology information, such as 802.1AB defined in the SMF, when receiving Link Layer Discovery Protocol (LLDP) packets from one or more devices (e.g., UE, end station, TSN device, Ethernet device, etc.). Topology information may be reported when initially discovered or when changed / modified. The UPF and UE may transmit LLDP packets to enable one or more devices to discover / report the 5GS virtual bridge. One or more 5GS virtual bridges may support transmitting LLDP or receiving LLDP. For propagation delay and port performance, as defined in 802.1Qcc, the UPF and UE may report this to the SMF in a manner similar to topology information reporting. 5GS may support TSN network-specific QoS characteristics and mapping between these QoS characteristics and traffic classes. The Packet Delay Budget (PDB) in QoS characteristics can be used to realize maximum delay transmission for deterministic delivery. The SMF can obtain QoS characteristics for the UE's subscribed traffic classes, and the SMF can use the PDB within them as the bridge delay for the corresponding traffic class of the port pair. The AF can collect / aggregate / acquire / receive and maintain 5GS virtual bridge-related information. The AF can operate as the control plane of the 5GS virtual bridge and can register or update this information with the CNC as defined in 802.1Qcc and 802.1AB. For QoS profile generation, the AF can maintain the relationship between the UE ID, 5GS virtual bridge ID, and UE port ID. The AF can determine / discover the corresponding UE ID when receiving TSN stream rules (bridge ID, incoming port ID, outgoing port ID, stream description, stream ID, etc.) from the CNC.AF can determine the traffic class from the TSN stream rule and map the traffic class to the corresponding 5QI.

[0246] In an exemplary embodiment, the TSN bridge may report performance. In one example, the identities of the 5GS virtual bridge and UPF ports may be pre-configured on the UPF based on placement. The UPF may report port performance and propagation delay as defined in 802.1Qcc, topology information as defined in 802.1AB, and the corresponding DNN to the SMF using node-level signaling, and the SMF may forward the received information directly to the AF or via the NEF to create or update the 5GS virtual bridge and bridge ports. The UE may send a request to establish a PDU session to the AMF. The AMF may select the SMF for the PDU session. The SMF may receive the UE-subscribed traffic classes and VLANs from the UDM, and receive QoS attributes (e.g., 5QI, PDB) corresponding to the subscribed traffic classes from the PCF. The SMF can select a UPF to support registered traffic classes and subscribed VLANs. The SMF can send an N4 session establishment request to the UPF with DNN, traffic class IDs, and VLAN values ​​to request the assignment of UE port IDs and the determination of the UPF ports to be served. The UPF can determine a 5GS virtual bridge for the PDU session and assign an identity to the UE port. Based on the traffic classes and VLANs supported by the DN, the UPF can determine the UPF ports to service the PDU session. The UPF can send to the SMF the assigned UE port identity with the corresponding 5GS virtual bridge identity, service UPF port IDs with the corresponding traffic class IDs, etc. The SMF can send the 5GS virtual bridge ID associated with the PDU session and assign a UE port ID to the UE. This information can be used for the UE to perform topology discovery and information reporting.SMF can take PDBs from QoS attributes as bridge delays for corresponding traffic classes and port pairs, and can transmit 5GS virtual bridge related information (bridge delays, UE port ID, UPF port ID, traffic class, 5GS virtual bridge ID, UE ID) to AF or NEF to add UE ports or update bridge attributes.

[0247] In one example, if a PDU session is established, the UE can report its port performance and propagation delay as defined in 802.1Qcc, and topology information as defined in 802.1AB to the NAS or SMF via the user plane. The AF can receive, collect, and aggregate data and maintain 5GS virtual bridge characteristics, including the bridge ID, port IDs of UPF ports, port IDs of UE ports, port-related performance, and bridge delays of port pairs. When bridge characteristics change, the AF can transmit the 5GS virtual bridge characteristics to the CNC to create a TSN bridge or update the bridge.

[0248] In an exemplary embodiment, the UE may operate as an Ethernet switch. The SMF may configure the UE to operate as an Ethernet switch having configuration parameters provided during the establishment of a PDU session or the configuration of a TSN bridge. The PDU session may provide access to an end station through the TSN bridge to communicate with one or more end stations. The UE operating as an Ethernet switch may be part of one or more TSN systems. One or more backend devices may be connected to the UE operating as an Ethernet switch. In one example, the SMF may provide configuration parameters to the UE in switch mode. Configuration parameters may include an indicator of whether the UE in Ethernet switch mode can turn on or off the Spanning Tree algorithm, a periodic timer for transmitting BDPU messages, a bridge identifier of the UE in Ethernet switch mode, an indicator of whether the UE in Ethernet switch mode can notify of a change in the state of a port, and an indicator of whether the UE in Ethernet switch mode can report a list of MAC address(s) of connected TSN end stations, backend devices, etc. in backend networks.

[0249] In one example, if the SMF indicates to the UE to report a list of MAC address(s) of backend devices or TSN end stations, the UE in switch mode can obtain a list of MAC address(s) of backend devices connected to or changed in backend networks. In one example, when a single PDU session provides communication to two or more TSN systems, the UE can obtain / determine the MAC address(s) and the mapping relationships between the TSN systems. The UE can notify the SMF of the list of MAC address(s) and mapping relationships during the PDU session establishment / modification procedure when the UE receives an indicator or detects changes to backend devices. The SMF can provide a UPF Ethernet packet filter set and forwarding rule(s) based on the MAC address(s) and mapping relationships. The UPF can detect and forward Ethernet frames based on the Ethernet packet filter set and the forwarding rule(s) received from the SMF.

[0250] In one example, a UE in Ethernet switch mode can report port states resulting from the execution of a spanning tree algorithm, and accordingly, the SMF can control the port states of the UPF based on the report to prevent the waste of network resources.

[0251] In one example, the UPF may support S-tags (IEEE 802.1ad) and C-tags (IEEE 802.1q). In one example, a PDU session may provide access to one or more TSN systems, TSN end stations, etc. S-tags and / or C-tags may be used for streams of data packets. TSN system configuration may be pre-configured on the UE or provided to the UE by a network, e.g., an SMF, etc. In one example, a TSN system identifier may be used to identify a TSN system, one or more TSN end stations, etc. In one example, the operator may assign a list of TSN system or TSN end station identifiers to the UEs. Identifiers may be configured in a UDR, UDM, etc. The SMF may be configured by the operator to have mapping tables for TSN identifiers, VLAN IDs, C-tags, S-tags, etc. The SMF can map a list of TSN end station identifiers connected to the UE, which is notified into S-tags and C-tags through PDU session establishment procedures and via packet filters for uplink traffic. The UPF can insert S-tags and C-tags onto traffic transmitted to N6, etc., based on packet filters for uplink traffic.

[0252] In an exemplary embodiment, the UE may receive an SRP message from an end station. The UE may map the SRP message to 3GPP QoS parameters. The UE may initiate a PDU session establishment procedure to request a PDU session for a TSN system or a TSN end station that supports the QoS parameters derived from the SRP.

[0253] In one example, a 3GPP system, 5GS, etc., may be used to operate as a TSN bridge. The TSN system may transmit and receive data packets, streams of data packets, etc., having network resource requirements determined by SRP messages, SRP advertisements, sender advertisements, etc. Existing technologies require that a PDU session be established prior to SRP propagation between TSN end stations. Existing technologies do not provide mechanisms for transmitting SRP messages prior to PDU session establishment, which may result in excessive signaling and inefficient use of network resources. Embodiments of the present disclosure provide mechanisms for improving the performance of TSN systems, TSN bridge configurations, etc.

[0254] In an exemplary embodiment, a first station (e.g., a TSN end station) may transmit SRP messages, sender advertisements, resource reservation requests, etc. to a wireless device or UE. The TSN end station may transmit SRP messages to the UE via a TSN converter device, a TSN adapter device, etc. The TSN converter device or the TSN adapter device may convert TSN protocol and information objects into 5GS protocol and information objects (and vice versa). The TSN converter device or the TSN adapter device may use a 3GPP wireless terminal having an integrated Ethernet adapter. In one example, the UE may use an integrated Ethernet adapter, a TSN converter, etc. In one example, the first station, the TSN end station, etc. may be a 3GPP device / UE, a non-3GPP device / UE, a gateway, a resident gateway, an Ethernet switch, a virtual switch, a 3GPP and / or non-3GPP interface, etc. If the TSN end station is a 3GPP device, the interaction between the TSN end station and the UE can be performed through the PC5 interface, PC3 interface, device-to-device (D2D) interface, etc.

[0255] In one example, an SRP message (e.g., transmitted from a TSN end station to a UE) may include a stream ID, data frame parameters, traffic specification (TSpec), priority and / or rank, accumulated latency, etc.

[0256] In one example, a stream ID may be an identifier for identifying a stream. A stream ID may be one or more (e.g., eight) octets that uniquely identify a stream. In one example, a stream ID may be subdivided into a 48-bit MAC address associated with a sender and a 16-bit unique ID used to distinguish different streams supplied by the same sender. In one example, a stream ID may use different encodings of one or more (e.g., eight) octets.

[0257] In one example, data frame parameters may be address information for a stream used to configure the bridge's filtering tables for reserved items. These parameters may further include a destination MAC address, a VLAN identifier, etc. In one example, the destination MAC address may be the destination MAC address of the streaming data packets. In one example, the destination MAC address may be a multicast or locally managed address. In one example, the VLAN identifier may identify the VLAN used for the streaming data packets.

[0258] A Traffic Spec (TSpec) for a stream can be used to configure stream traffic shaping mechanisms on bridges over ports associated with the stream. The TSpec may further include a maximum frame size parameter (e.g., MaxFrameSize), a maximum interval frame parameter (e.g., MaxIntervalFrames), etc. In one example, the maximum frame size parameter may include a value or parameter representing the maximum frame size that a sender (TSN end station) can generate as part of the stream. The maximum interval frame parameter may be the number of frames that a sender can generate per class measurement interval.

[0259] In one example, Priority and Rank (e.g., PriorityAndRank) may contain information regarding the priority class and urgency status of the stream. Priority and Rank may include data frame priority, rank value, etc. Data frame priority may be used to generate a Priority Code Point (PCP) tag for the data stream. Rank may be one or more bits to identify urgent streams versus non-urgent streams (e.g., urgent streams may use a value of 0, and non-urgent streams may use 1).

[0260] In one example, accumulated latency may represent the worst-case latency that a stream may experience from the sender to the receiver. This value may change after it has been registered by a participant. If a participant transmits an attribute with an accumulated latency change from a previously registered value, it may modify / change the propagation of the attribute from sender advertisement to sender failure using a failure information code (e.g., indicating that the reported latency has changed). The sender may initialize this value with an estimate of the maximum expected delay between the outflow of a packet from the sender's network interface and its arrival at the network peer on that path to the receiver. Each bridge on the path may add the maximum expected delay between the inflow of a packet on its port and its arrival at the next peer on the path.

[0261] In one example, when a UE receives a sender advertisement, an SRP message, etc. from a TSN end station, a TSN converter, a TSN adapter device, etc., the UE may decide to establish a PDU session for a stream to be transmitted by the TSN end station. In one example, based on an information element identifying a request type, the UE may decide that an SRP request (e.g., an SRP message) is required. The UE may decide to establish a PDU session (e.g., an indication that the PDU session is for SRP / TSN, etc.) and may perform a PDU session establishment procedure. The UE may decide to modify the PDU session for SRP / TSN and may perform a PDU session modification procedure.

[0262] In one example, if the UE determines that a PDU session establishment procedure is required, the UE may send a NAS message to the AMF. The NAS message may include an SRP message, a PDU session type indicating that the request is for an SRP (e.g., type = SRP / TSN), S-NSSAI(s), DNN, PDU session ID, request type, previous PDU session ID, N1 SM container (PDU session establishment request), etc. In one example, the NAS message may include an identifier of the TSN system, identifiers of one or more bridges (TSN bridges, etc.), and the UE's port identifier for the TSN bridge, etc. In one example, the DNN may identify the TSN system, a set / group of TSN bridges, etc.

[0263] In an exemplary embodiment, the SRP message may include an identifier (stream ID) of a stream of data packets, at least one transport parameter for the stream of data packets, etc. The at least one transport parameter for the stream of data packets may include data frame parameters, a user for network requirement parameters, priority and rank indication parameters, a latency value, a traffic specification parameter, etc. In one example, the data frame parameters may include a source MAC address for the stream of data packets, a destination MAC address for the stream of data packets, a VLAN identifier, etc. In one example, the user for network requirement parameters may include a parameter indicating latency requirements for the stream of data packets, a parameter indicating redundancy requirements for the stream of data packets, etc. In one example, the latency value may include an accumulated latency value, etc. In one example, the traffic specification parameter may include a parameter indicating the size of the data frame, a parameter indicating the number of data frames, etc.

[0264] To establish a new PDU session, the UE may generate a new PDU session ID. The UE may initiate the UE-requested PDU session establishment procedure by transmitting a NAS message containing a PDU session establishment request within an N1 SM container. In one example, the N1 SM container may contain an SRP message. In one example, the NAS message may contain a container for an SRP message object. The PDU session establishment request may include an SRP message, a PDU session ID, a requested PDU session type (e.g., type = SRP), a requested SSC mode, a 5GSM performance PCO, an SM PDU DN request container, the number of packet filters, an always-on PDU session request indicator, etc. The request type may indicate an initial request if the PDU session establishment is a request to establish a new PDU session, and may indicate an existing PDU session if the request refers to an existing PDU session switching between 3GPP access and non-3GPP access, or a PDU session handover from an existing PDN connection in the EPC.

[0265] 5GSM core network performance can be provided by the UE and processed by the SMF. 5GSM performance may include UE integrity protection maximum data rates.

[0266] The number of packet filters may indicate the number of supported packet filters for signaled QoS rules for an established PDU session. The number of packet filters indicated by the UE may be valid for the lifetime of the PDU session.

[0267] NAS messages transmitted by the UE can be encapsulated by AN within an N2 message directed to the AMF. NAS messages may include user location information, access type information, etc.

[0268] In one example, the UE may include an S-NSSAI from an allowed NSSAI of the current access type in a NAS message. The S-NSSAI may be an allowed NSSAI for a TSN system, one or more TSN bridges, etc. If a mapping of an allowed NSSAI is provided to the UE, the UE may provide an S-NSSAI from the allowed NSSAI, a corresponding S-NSSAI from the mapping of the allowed NSSAI, etc.

[0269] In one example, a UE can establish a PDU session for AS, AF, CUC, CNC, etc. If the UE establishes a PDU session for AS, AF, CUC, CNC, etc., and the UE is configured to discover a CUC or CNC address during connection establishment, the UE may include an indicator requesting identifiers for CUC, CNC, etc. within an SM container.

[0270] In an exemplary embodiment, the AMF may determine that a message corresponds to an SRP request, an SRP message, etc. The AMF may select an SMF. The AMF may select an SMF based on an SMF-ID received from the UDM. The AMF may select an SMF based on a PDU session type, e.g., an SRP. Based on the request type indicating an initial request and the PDU session ID not being used for any existing PDU session(s) of the UE, the AMF may determine that the message corresponds to a request for a new PDU session. If the NAS message does not contain an S-NSSAI, the AMF may determine a default S-NSSAI for the requested PDU session based on the operator policy, or based on the UE subscription if it contains only one default S-NSSAI. In one example, the AMF may determine a (default) S-NSSAI based on an identifier such as a TSN system, a TSN bridge (e.g., a bridge ID). In one example, if interaction with a CUC or CNC is required, the AMF may determine the CUC and / or CNC based on the S-NSSAI, UE subscription, TSN system identifier, etc. In one example, the AMF may select a locally configured CNC or CUC for the TSN bridge. If the NAS message contains an S-NSSAI but does not contain a DNN, the AMF may determine the DNN for the requested PDU session by selecting a default DNN for this S-NSSAI if a default DNN exists in the UE's subscription information, and otherwise, the AMF may select a locally configured DNN for this S-NSSAI.If the AMF cannot select an SMF (e.g., if the DNN provided by the UE is not supported by the network, or if the DNN provided by the UE does not exist in the list of subscribed DNNs for S-NSSAI and the wildcard DNN is not included in the list of subscribed DNNs), the AMF may reject a NAS message containing a PDU session establishment request from the UE for an appropriate reason.

[0271] In an exemplary embodiment, the AMF may send a session creation request to the SMF. In one example, the session creation request may include Nsmf_PDUSession_CreateSMContext Request, Nsmf_PDUSession_UpdateSMContext Request, etc. The Nsmf_PDUSession_CreateSMContext request may include an SRP message, a PDU session type (e.g., type = SRP), an identifier of the TSN system, an identifier of the TSN bridge, a bridge ID, a port ID, SUPI, DNN, S-NSSAI(s), a PDU session ID, an AMF ID, a request type, a PCF ID, a priority access, an N1 SM container (PDU session establishment request), user location information, an access type, PEI, GPSI, the presence of a UE within the LADN service area, a subscription to PDU session status notifications, a DNN selection mode, a tracing requirement, etc. In one example, the Nsmf_PDUSession_UpdateSMContext request may include an SRP message, a PDU session type (e.g., type = SRP), an identifier of the TSN system, an identifier of the TSN bridge, a bridge ID, a port ID, SUPI, DNN, S-NSSAI(s), a PDU session ID, an AMF ID, a request type, an N1 SM container (PDU session establishment request), user location information, access type, RAT type, PEI, etc.

[0272] In one example, the AMF ID may be the UE's GUAMI identifying the AMF servicing the UE. The AMF may forward the PDU session ID along with an N1 SM container containing a PDU session establishment request received from the UE. The GPSI may be included in the AMF if available. The AMF may determine the access type and RAT type based on the global RAN node ID associated with the N2 interface.

[0273] In one example, the AMF may provide PEI if the UE is in a restricted service state and has registered for emergency services (i.e., emergency registration) without providing SUPI.

[0274] In one example, the SMF may receive an establishment cause from the AMF. The establishment cause may indicate that the PDU session is intended for an SRP, an SRP message, an SRP procedure, a TSN system resource reservation, etc. If the SMF receives an establishment cause as part of AN parameters from the AMF while the registration procedure or service request procedure is associated with priority services (e.g., TSN, SRP, MPS, MCS), the AMF may include a message priority header to indicate priority information. The SMF can use the message priority header to determine whether a UE request is exempt from NAS-level congestion control. Other NFs relay priority information by including the message priority header in service-based interfaces. The AMF may include an identifier for a PCF (e.g., PCF ID) in the Nsmf_PDUSession_CreateSMContext request. The PCF ID can identify the H-PCF in the case of non-roaming and the V-PCF in the case of local breakout roaming.

[0275] In one example, the SMF can receive an SRP message from the AMF. The SMF can receive the SRP message via an N11 interface, etc. The AMF can use service-based interaction messaging with the SMF (e.g., Nsmf_PDUSession_CreateSMContext, etc.) via the N11 interface. In one example, the SMF can extract the SRP message from the Nsmf_PDUSession_CreateSMContext message. The SMF can extract / derive / decapsulate stream information from the SRP message and provide it as a QoS flow request to the PCF. In one example, the SMF can map the SRP message to the QoS flow request. The SMF can select a PCF or use a locally configured PCF to obtain PCC rules for the PDU session. The SMF can perform a Session Management (SM) policy association establishment procedure. The policy association procedure can be used to establish an SM policy association with the PCF and to obtain (default) PCC rules for the PDU session. The policy association procedure may utilize GPSI. In one example, if the SM policy association is for an existing PDU session, the SMF may provide information about the policy control request trigger condition(s) that were satisfied by the SM policy association modification procedure initiated by the SMF. In one example, the PCF may transmit policy information to the SMF.

[0276] In one example, an SMF may select a User Plane Function (UPF). The SMF may select a UP based on SRP performance, one or more components of an SRP message, TSN performance support, etc. The SMF may query a Network Repository Function (NRF) to select a UPF. The SMF may use the Nnrf_NFDiscovery service, the Nnrf_NFDiscovery_Request service operation, and / or a similar NRF. The SMF may send a discovery request message (e.g., Nnrf_NFDiscovery_Request message, Nnrf_discovery_request message, etc.) containing an NF type (e.g., UPF), SRP performance, one or more components of an SRP message, TSN performance support, etc. to the NRF representing a request to select / discover a UPF for a TSN (system). The NRF may send a query response (e.g., Nnrf_NFdiscovery_response, etc.) containing the identifier of the UPF, the address of the UPF, etc.

[0277] In one example, the SMF may send a session establishment request (e.g., an N4 session establishment request) to the UPF. The N4 session establishment request may include packet detection rules for QoS flows, a bridge ID (e.g., an identifier of a TSN bridge), a port ID (e.g., associated with a TSN system, a stream of data packets, an SRP, etc.), an identifier of the N4 session (N4 session ID), a PDU session type (e.g., TSN, SRP, Ethernet, IPv4, IPv6, destructured, etc.), and an identifier of the session (e.g., a PDU session). In one example, the TSN bridge may include one or more pairs / tuples of UEs and one or more UPFs.

[0278] The SMF can send an N4 session establishment / modification request to the UPF and can provide packet detection, enforcement, and reporting rules to be installed in the UPF for the PDU session. If CN tunnel information is assigned by the SMF, the CN tunnel information may be provided to the UPF. If optional user plane deactivation is required for the PDU session, the SMF can determine a deactivation timer and provide it to the UPF. In one example, the value for the deactivation timer may be determined based on SRP messages and TSN system requirements. The UPF may acknowledge by sending an N4 session establishment / modification response to the SMF. If CN tunnel information is assigned by the UPF, the CN tunnel information may be provided to the SMF.

[0279] In one example, the SMF can transmit / forward an SRP message to the UPF. In response to receiving the SRP message, the SMF can transmit the SRP message to the second TSN bridge. The SMF can transmit the SRP message to the second TSN bridge through an exit port for the TSN system. The second TSN bridge can receive the SRP through a port of the UE, a port of the UPF, etc. In one example, the UPF can transmit the SRP message to the second station (e.g., a TSN end station, a TSN device, a non-3GPP device, a 3GPP device, etc.). In one example, in response to receiving the SRP message, the second station can transmit an SRP response message (e.g., an SRP message response, a receiver ready message / advertisement, etc.). The SRP response message may be a receiver ready message indicating that the second station of the TSN system is ready to receive / transmit / transmit TSN data packets, a stream of data packets, etc. In one example, the second station can transmit an SRP response message through the second TSN bridge (e.g., through one or more TSN bridges).

[0280] In one example, the second station can send an SRP message response (SRP response message) to the UPF. The UPF can send / forward the SRP response message to the SMF through an N4 session identified by an N4 session ID. The UPF can send the SRP response message through a session established between the SMF and the UPF for a PDU session of the TSN system. The session between the SMF and the UPF may be an N4 session. The UPF can send the SRP response message through an N4 session, an N4 message, an N4 reporting procedure, etc., including an N4 session ID, a port ID, a TSN bridge ID, an SRP response message, an identifier of the second station, an identifier of the first station, etc.

[0281] In one example, the second station may be an AF, an AS, etc. In one example, the AF, an AS, etc. may transmit an SRP response message in response to receiving an SRP message. The AS / AF may receive the SRP message via an NEF, PCF, SMF, UPF, etc. The second station may receive the SRP message via a control plane or a user plane, via a PDU session, signaling, etc. In one example, the SRP response message may be transmitted by the second station upon the successful establishment of a PDU session for the TSN system or the SRP. In one example, the SMF may transmit the SRP message to the second TSN bridge or one or more TSN bridges if the SRP request is successful (e.g., if the establishment of a PDU session for the TSN is successful). In an exemplary embodiment, the second station (e.g., one or more receiver(s), etc.) may request the network to reserve resources for transmitting and / or receiving a stream of data packets for the TSN system. In one example, an SRP message may trigger a service request procedure for one or more receiver(s), or the establishment of a network initiation PDU session or the modification of a network initiation PDU session. In one example, if a request from a second station (receivers) for the reservation of network resources (e.g., based on an SRP message, etc.) fails, the second station(s) may send a receiver failure message to the sender (e.g., the first station). In one example, the SRP may be propagated / transmitted through one or more TSN bridges. Errors, failure of the reservation of resources based on the SRP message, resources insufficient to support the reservation for the SRP, etc., may result in a sender readiness failure, a sender failure, and / or similar messages.In one example, if the path from the receiver to the sender does not have sufficient resources to support an SRP request for a stream of data packets, a sender failure message may be transmitted / propagated to the end stations.

[0282] In one example, the SMF can transmit SRP messages to the Application Function (AF), AS, etc. The SMF can transmit SRP messages to the UPF via the N4 interface. The UPF can transmit SRP messages to the AF / AS. The SMF can transmit SRP messages to the AF, AS, etc. via the NEF. The SMF can transmit SRP messages to the NEF using the Nnef service operation procedure (e.g., a message delivery request including the AF ID, AS ID, etc.). The SMF can select the NEF based on local information or via the NRF, UDM, UDR, etc.

[0283] In one example, the SMF can send an SRP message to the PCF through the N7 interface. The SMF can utilize service-based interactions of the PCF, such as Npcf service operations. The SMF can send a message to the PCF that includes an SRP message, SUPI, bridge ID, etc. The SMF can send an SRP message to the PCF. The PCF can determine an AF, AS, or centralized controller (e.g., CNC, CUC, etc.) and can send the SRP message to the AF, AS, centralized controller, etc.

[0284] In one example, the SMF may send a Namf_Communication_N1N2MessageTransfer message to the AMF, which includes a PDU session ID, N2 SM information (PDU session ID, QFI(s), QoS profile(s), CN tunnel information, S-NSSAI from allowed NSSAI, Session-AMBR, PDU session type, User plane security hardening information, UE integrity protection maximum data rate), N1 SM container (PDU session establishment acknowledgment (QoS rule(s) and, if necessary, QoS flow level QoS parameters for QoS flow(s) associated with QoS rule(s), selected SSC mode, S-NSSAI(s), DNN, assigned IPv4 address, interface identifier, Session-AMBR, selected PDU session type, reflection QoS timer (if available), P-CSCF address(s), [Always-on PDU session])), etc. The N2 SM information may include information that the AMF can forward to the (R)AN node. N2 SM information may include CN tunnel information corresponding to the core network address of the N3 tunnel corresponding to the PDU session, one or more QoS profiles and corresponding QFIs that may be provided to (R)AN, a PDU session ID that may be used by AN signaling with the UE to indicate to the UE the association between (R)AN resources and the PDU session for the UE, the PDU session associated with the S-NSSAI and DNN, and user plane security enhancement information. The N1 SM container may include a PDU session establishment acknowledgment that the AMF may provide to the UE. If the UE requests P-CSCF discovery, the message may include P-CSCF IP address(s) as determined by the SMF. The PDU session establishment acknowledgment may include an S-NSSAI from an allowed NSSAI.

[0285] In one example, the PDU session establishment acknowledgment within the N1 SM and N2 SM information may include one or more QoS rules, QoS flow-level QoS parameters for the QoS flow(s) associated with these QoS rule(s) and QoS profiles. Namf_Communication_N1N2MessageTransfer may include a PDU session ID that enables the AMF to know access to the UE to be used.

[0286] In one example, an AMF may send an N2 PDU session request to a station (e.g., RAN, NGRAN, etc.). The N2 PDU session request may include N2 SM information, a NAS message (PDU session ID, N1 SM container (acknowledgment of PDU session establishment)), etc. The AMF may send to the (R)AN a NAS message containing a PDU session ID and an acknowledgment of PDU session establishment targeting a UE, and the N2 SM information received from the SMF within the N2 PDU session request. In one example, a station (e.g., (R)AN) may send / issue AN-specific signaling to a UE. The (R)AN may issue an AN-specific signaling exchange with the UE that may be related to the information received from the SMF. For example, in the case of NG-RAN, RRC connection reconfiguration may occur as the UE establishes the necessary NG-RAN resources related to the QoS rules for the PDU session request. The (R)AN may assign (R)AN N3 tunnel information for the PDU session. In one example, for dual connections, the master RAN node may assign some (zero or more) QFIs to the master RAN node and others to the secondary RAN node. AN tunnel information may include tunnel endpoints for one or more included (R)AN node(s) and QFIs assigned to one or more tunnel endpoint(s). QFIs may be assigned to the master RAN node or the secondary RAN node. In one example, the (R)AN may forward a NAS message (PDU session ID, N1 SM container (acknowledgment of PDU session establishment)) to the UE. The (R)AN may provide a NAS message to the UE if the necessary (R)AN resources are established and the assignment of (R)AN tunnel information is successful.In one example, (R)AN may transmit an N2 PDU session response message (e.g., including PDU session ID, cause, N2 SM information (PDU session ID, AN tunnel information, list of accepted / rejected QFI(s), user plane enforcement policy notification, etc.)) to the AMF. The AN tunnel information may correspond to the access network address of the N3 tunnel corresponding to the PDU session. In one example, if a station (e.g., NG-RAN, (R)AN, etc.) rejects the QFI(s), the SMF may update the QoS rules and, if necessary, the QoS flow-level QoS parameters for the QoS flow associated with the QoS rule(s) in the UE. The NG-RAN may refuse to establish UP resources for the PDU session if it cannot implement user plane security enhancement information with the required values. In this case, the SMF may release the PDU session. NG-RAN can notify SMF of a priority value when user plane security reinforcement cannot be implemented.

[0287] In one example, the AMF may send an Nsmf_PDUSession_UpdateSMContext request (e.g., including N2 SM information, request type, etc.) to the SMF. The AMF may forward the N2 SM information received from the (R)AN to the SMF. If a list of denied QFI(s) is included in the N2 SM information, the SMF may release the QoS profiles associated with the denied QFI(s). If a user plane hardening policy notice within the N2 SM information indicates that user plane resources cannot be established, and the user plane hardening policy indicates specific requirements (e.g., using a "required" field, etc.), the SMF may release the PDU session. The SMF may initiate an N4 session modification procedure with the UPF. The SMF may provide the AN tunnel information, corresponding forwarding rules, etc. to the UPF. The UPF may provide an N4 session modification response to the SMF. In one example, the SMF may send an Nsmf_PDUSession_UpdateSMContext response (e.g., including the cause value, etc.) to the AMF. In one example, the SMF may send a release message to the AMF, e.g., Nsmf_PDUSession_SMContextStatusNotify(Release). If the PDU session establishment is unsuccessful during the procedure, the SMF may notify the AMF by calling Nsmf_PDUSession_SMContextStatusNotify(Release). The SMF may release any created N4 session(s), any assigned PDU session address (e.g., IP address), and release the association with the PCF.

[0288] In one example, the SMF can forward / transmit an SRP response message to the UE. The SMF can transmit the SRP message via non-access layer messages (e.g., SM-NAS, NAS-SM, etc.). The SMF can use the N11 interface between the SMF and the AMF to transmit the SRP response message. The SMF can use messages such as Namf_Communication_N1N2MessageTransfer to transmit the SRP response message. The Namf_Communication_N1N2MessageTransfer message may include the SRP response message, the identifier of the first station, etc.

[0289] In one example, a UE (e.g., a wireless device, etc.) may receive an SRP response message from an SMF via a NAS message as illustrated in FIGS. 22 and 24. The UE may receive an SRP response message via an AMF and a station. In one example, as illustrated in FIGS. 23 and 25, the UE may receive an SRP response message via a PDU session, a UPF, a user plane, etc. In one example, in response to receiving an SRP response, the UE may determine that the SRP response message is for a sender (a first station of the TSN). The UE may extract a received message that may include an SRP response message, an end station identifier, a TSN bridge ID, a port ID, etc., and transmit the SRP response message to the first end station via a port. The UE may transmit the SRP response message to the sender via a TSN converter, an Ethernet adapter, an N60 interface, etc. The sender (the first end station) may transmit a stream of data packets to one or more receivers, for example, via a PDU session.

[0290] In the exemplary embodiment illustrated in FIG. 27, the first TSN bridge can transmit an SRP message to a TSN end station through the second TSN bridge. The TSN bridge (e.g., the first TSN bridge) can transmit the SRP message to a CNC, CUC, etc. The CNC can determine the TSN bridge based on elements of the SRP message, identifiers of the TSN end station, etc. The CNC can transmit the SRP message to the second TSN bridge (e.g., including a 3GPP system, a 5G system, etc.). In one example, the PCF, SMF, NEF, etc. of the 5GS can transmit a trigger to a UE connected to / associated with the (TSN) end station. The association can be determined based on a bridge ID, port ID, UE ID, UPF ID, ports of the UPF / UE associated with the TSN system or the TSN end station, etc. In one example, the CNC can receive the SRP message and forward the SRP message to an AF. The AF can transmit the SRP to the NEF. The NEF can transmit an SRP message to the PCF or SMF. In one example, the AF / AS can receive an SRP message from the first TSN bridge. The AF / AS can transmit the SRP message to the PCF or SMF. The AF / AS can transmit the SRP message to the PCF or SMF via the NEF. In one example, the SMF, PCF, NEF, etc., can trigger a PDU session establishment / modification having an indication that the PDU session establishment / modification may be for a TSN system, SRP propagation, etc. In one example, the PCF, SMF, NEF, etc., can map the SRP message to one or more QoS flow parameters. In one example, the PCF can trigger a policy delivery procedure for a UE (e.g., URSP) that triggers the PDU session establishment. The URSP may include S-NSSAI, DNN, association between the PDU session ID and the TSN system, one or more QoS flow requirements, etc.A UE can establish a PDU session based on URSP by performing a PDU session establishment request or a PDU session modification request. The UE can send a NAS message to an SMF (e.g., via an AMF). The NAS message may include an SRP message, a PDU session type indicating that the request is for SRP / TSN (e.g., type = SRP / TSN), S-NSSAI(s), a DNN, a PDU session ID, a request type, a previous PDU session ID, an N1 SM container (PDU session establishment request), etc. In one example, the NAS message may include an identifier of a TSN system, identifiers of one or more bridges (TSN bridges, etc.), a UE port identifier for a TSN bridge, etc. In one example, the DNN may identify a TSN system, a set / group of TSN bridges, etc.

[0291] In one example, the PCF may execute an SM policy-associated modification procedure initiated by the PCF to notify the SMF of modifications to policies. This may be triggered, for example, by a policy decision or by a request from an AF, for example, an application function affecting traffic routing. The UDM may update the SMF's subscription data via Nudm_SDM_Notification (e.g., including SUPI, session management subscription data, etc.). The SMF may update the session management subscription data and acknowledge the UDM by returning an Ack (e.g., containing SUPI, etc.). In one example, the SMF may request a modification. The SMF may modify a PDU session. This procedure may be triggered based on a locally configured policy or by (R)AN. This may be triggered when the UP connection is active and the SMF marks the state of one or more QoS flows as being deleted from 5GC but not synchronized with the UE.

[0292] In one example, the SMF may call Namf_Communication_N1N2MessageTransfer. Namf_Communication_N1N2MessageTransfer may include an SRP message, an indication that the request is for TSN / SRP, a PDU session type indicating a TSN / SRP type PDU session, N2 SM information (PDU session ID, QFI(s), QoS profile(s), session-AMBR), N1 SM container (PDU session modification command (PDU session ID, QoS rule(s), QoS flow-level QoS parameters for the QoS flow(s) associated with the QoS rule(s), if necessary, QoS rule actions and QoS flow-level QoS parameter actions, session-AMBR)), etc.

[0293] In one example, when the UE is in the CM-IDLE state and ATC is enabled, the AMF can update and save the UE context based on Namf_Communication_N1N2MessageTransfer. If the UE is reachable, for example, when the UE enters the CM-CONNECTED state, the AMF can forward N1 messages to synchronize the UE context with the UE. The AMF can send an N2 PDU session request message to the (R)AN (including, for example, N2 SM information received from the SMF, NAS messages (SRP messages, PDU session type = TSN / SRP, PDU session ID, N1 SM container (PDU session modification command)), etc. The (R)AN can issue an AN-specific signaling exchange with the UE related to the information received from the SMF. For example, in the case of NG-RAN, RRC connection reconfiguration may occur along with the UE modifying the necessary (R)AN resources related to the PDU session. (R)AN may acknowledge an N2 PDU session request by sending an N2 PDU session Ack (N2 SM information (list of accepted / rejected QFI(s), AN tunnel information, PDU session ID, auxiliary RAT usage data), user location information) message to the AMF. In the case of dual connections, if one or more QFIs are added to the PDU session, the master RAN node may assign one or more of these QFIs to an NG-RAN node that was not previously included in the PDU session. In this case, the AN tunnel information includes new N3 tunnel endpoints for the QFIs assigned to the new NG-RAN node. Correspondingly, if one or more QFIs are removed from the PDU session, the (R)AN node may no longer be included in the PDU session, and the corresponding tunnel endpoints may be removed from the AN tunnel information.NG-RAN can reject QFI(s) if, for example, the maximum data rate for UE integrity protection is exceeded and the user plane security hardening information for the corresponding QoS profile cannot be implemented.

[0294] The AMF can forward / transmit user location information and N2 SM information received from the AN to the SMF through the Nsmf_PDUSession_UpdateSMContext service operation. The SMF can respond with an Nsmf_PDUSession_UpdateSMContext Response. The N2 SM information may include auxiliary RAT usage data. If the (R)AN rejects the QFI(s), the SMF is responsible for updating the QoS rules and, if necessary, the QoS flow-level QoS parameters for the QoS flow(s) associated with the QoS rule(s) in the UE accordingly. The SMF can update the N4 sessions of the UPF(s) included by the PDU session modification by sending an N4 session modification request message to the UPF based on the QoS flow derived from the SRP message. If a new QoS flow is created, the SMF can update the UPF with the UL packet detection rules of the new QoS flow derived / mapped from the SRP message.

[0295] The UE can acknowledge a PDU session update command by sending a NAS message. The NAS message may include an SRP message, PDU session type, port ID, bridge ID, PDU session ID, N1 SM container (PDU session update command (Ack)), etc. In one example, the N1 SM container may include an SRP message. (R)AN may forward the NAS message to an AMF. The AMF may send / forward the N1 SM container (SRP message, PDU session update command (Ack)) and user location information and / or similar items received from the AN to the SMF through the Nsmf_PDUSession_UpdateSMContext service operation. The SMF may respond with an Nsmf_PDUSession_UpdateSMContext Response.

[0296] In one example, the SMF can update the N4 sessions of the UPF(s) included in the PDU session modification by sending an N4 session modification request (N4 session ID) message to the UPF. For PDU sessions of the Ethernet PDU session type, the SMF can notify the UPF to add or remove Ethernet packet filter set(s) and forwarding rule(s).

[0297] In one example, when an SMF interacts with a PCF, the SMF may notify the PCF whether a PCC decision can be implemented by performing an SM policy association modification procedure disclosed to the SMF.

[0298] In one example, as illustrated in FIG. 28, a TSN end station can transmit an SRP message, and the SRP message can be propagated through one or more TSN bridges. In one example, one or more TSN bridges can receive an SRP or sender advertisement message through a control plane or a user plane. A CNC or CUC can coordinate the distribution of SRP messages based on SRP messages, SRP requirements, TSN requirements, etc. A CUC and / or CNC can manage the topology for the TSN bridges to meet one or more requirements such as redundancy, reliability, latency, etc.

[0299] In an exemplary embodiment, a wireless device may receive a Stream Reservation Protocol (SRP) message from a first station requesting the reservation of network resources for a stream of data packets for a time-sensitive network (TSN). The SRP message may include an identifier for the stream of data packets, at least one transmission parameter for the stream of data packets, etc. In one example, the wireless device may decide to establish a Packet Data Unit (PDU) session for the TSN based on the SRP message. The wireless device may transmit a second message to a Session Management Function (SMF) requesting the establishment of a PDU session for the stream of data packets. The second message may be made via an AMF. The second message may include the SRP message, a parameter indicating that the PDU session is for the TSN, etc. The wireless device may receive an SRP response message indicating that the second station is ready to receive the stream of data packets. The SRP response message may be received via a UP, CP, SMF, AMF, UPF, etc. The wireless device can transmit / forward an SRP response message to the first station.

[0300] In one example, a wireless device can receive a stream of packets from a first station. The wireless device can transmit / forward the stream of packets through a PDU session. The wireless device can receive an SRP message from the first station through a TSN converter.

[0301] In an exemplary embodiment, at least one transmission parameter for a stream of data packets may include an identifier of the stream of data packets (stream ID), data frame parameters, a user for network requirement parameters, priority and rank indication parameters, a latency value, a traffic specification parameter, etc. In one example, the data frame parameters may include a source MAC address for the stream of data packets, a destination MAC address for the stream of data packets, an identifier of a VLAN, etc. In one example, the user for network requirement parameters may include a parameter indicating latency requirements for the stream of data packets, a parameter indicating redundancy requirements for the stream of data packets, etc. In one example, the latency value may include an accumulated latency value, etc. In one example, the traffic specification parameter may include a parameter indicating the size of the data frame, a parameter indicating the number of data frames, etc.

[0302] In an exemplary embodiment, the second message may be a Non-Access Layer (NAS) message. In one example, the SRP response message may be a NAS message. The SRP response message may be received through a session management function. In one example, the SRP response message may be received through a PDU session. The SRP response message may be received through a user plane function.

[0303] In an exemplary embodiment, the SMF can extract at least one transmission parameter for a stream of data packets.

[0304] In one example, the SMF can send a QoS flow request for a stream of data packets to the PCF. The SMF can receive at least one PCC rule for the QoS flow of the stream of data packets from the PCF.

[0305] In one example, the second message may further include an identifier of a TSN bridge. The TSN bridge may be a 3GPP system comprising one or more incoming port(s) and one or more outgoing port(s). One or more outgoing port(s) may include a radio device, a user plane function, etc. One or more incoming port(s) may include a radio device, a user plane function (UPF), etc. In one example, the second message may include an identifier of a port (of a UE in switch mode) associated with a first end station of the TSN system.

[0306] In one example, the SMF can transmit an SRP message to a User Plane Function (UPF).

[0307] In one example, a network exposure function (NEF) can receive an SRP message from an SMF. The NEF can transmit the SRP message to a network node. The network node may include a TSN conversion device, a policy control function, an application function, etc. The network node can transmit the SRP message to a second TSN bridge. In one example, the second TSN bridge can receive an SRP message from the network node via an NEF / PCF / AF.

[0308] In an exemplary embodiment, a wireless device may receive a Stream Reservation Protocol (SRP) message from a session management function, AMF, PCF, etc., requesting the reservation of network resources for a stream of data packets for a time-sensitive network (TSN). The SRP message may include an identifier (stream ID) of the stream of data packets, at least one transmission parameter for the stream of data packets, etc.

[0309] In one example, the wireless device may decide to establish a packet data unit (PDU) session for the TSN based on an SRP message. In one example, the wireless device may transmit a second message to a session management function (SMF) requesting the establishment of a PDU session for a stream of data packets. The second message may include an SRP message, parameters indicating that the PDU session is for the TSN, etc.

[0310] In one example, the wireless device may receive an acknowledgment message indicating that the PDU session to the TSN system is successful. The wireless device may transmit an SRP message to the first station. The wireless device may receive an SRP response message from the first end station. The wireless device may transmit an SRP response to the second station.

[0311] In an exemplary embodiment, the Session Management Function (SMF) may receive a message from a wireless device requesting the establishment of a PDU session for a stream of data packets for a Time-Sensitive Network (TSN). In one example, the message may include a Stream Reservation Protocol (SRP) message. The SRP message may include an identifier for the stream of data packets, at least one transport parameter for the stream of data packets, a parameter indicating that the PDU session is for the TSN, etc. In one example, at least one transport parameter for the stream of data packets may include an identifier for the stream of data packets. In an exemplary embodiment, at least one transport parameter for the stream of data packets may further include an identifier for the stream of data packets (stream ID), data frame parameters, a user for network requirement parameters, priority and rank indication parameters, a latency value, traffic specification parameters, etc. In one example, the data frame parameters may include a source MAC address for the stream of data packets, a destination MAC address for the stream of data packets, an identifier for a VLAN, etc. In one example, the user of network requirement parameters may include parameters indicating latency requirements for a stream of data packets, parameters indicating redundancy requirements for a stream of data packets, etc. In one example, the latency value may include an accumulated latency value, etc. In one example, the traffic specification parameter may include parameters indicating the size of a data frame, parameters indicating the number of data frames, etc.

[0312] The SMF can determine, based on the message, whether the PDU session establishment may be for the TSN system. The SMF can determine quality of service requirement parameters based on at least one transmission parameter for the stream of data packets. The SMF, as a network function, can transmit an SRP message targeting a second station. The SMF can transmit a second message to the UPF requesting the establishment of a PDU session for the TSN system. The second message may include an identifier for the stream of data packets, quality of service requirement parameters, etc. The network function may be at least one of the NEF, UPF, etc.

[0313] According to various embodiments, a device such as, for example, a wireless device, an off-network wireless device, a station, etc., may include one or more processors and memory. The memory may store instructions that, when executed by one or more processors, cause the device to perform a series of operations. Examples of exemplary operations are illustrated in the accompanying drawings and specification. Features from various embodiments may be combined to create other embodiments.

[0314] FIG. 34 is a flowchart according to one aspect of an exemplary embodiment of the present disclosure. In step (3410), the wireless device may receive a request from the first station indicating the configuration of a time-sensitive network (TSN) bridge for the transmission of a stream of data packets. In step (3420), the wireless device may transmit a non-access layer message containing at least one parameter for the configuration of the TSN bridge to the session management function (SMF). In step (3430), the wireless device may receive a response message from the SMF indicating that the TSN bridge has been configured for the transmission of a stream of data packets. In step (3440), the wireless device may transmit a message to the first station indicating the successful configuration of the TSN bridge.

[0315] FIG. 35 is a flowchart according to one aspect of an exemplary embodiment of the present invention. In step (3510), a wireless device of a time-sensitive network (TSN) bridge may receive a configuration message from a session management function requesting the reservation of network resources for a stream of data packets for the TSN bridge. In step (3520), based on the configuration message, the wireless device may decide to modify a packet data unit (PDU) session through the TSN bridge for the transmission of a stream of data packets. In step (3430), the wireless device may transmit a NAS message to the session management function (SMF) containing at least one transmission parameter for a stream of data packets.

[0316] FIG. 36 is a flowchart according to one aspect of an exemplary embodiment of the present invention. In step (3610), a session management function (SMF) may receive a NAS message from a wireless device containing at least one transmission parameter for a stream of data packets. In step (3620), the SMF may decide to configure a UPF for TSN packet transmission. In step (3630), the SMF may transmit a message to the UPF configuring the UPF for the TSN bridge.

[0317] FIG. 37 is a flowchart according to one aspect of an exemplary embodiment of the present invention. In step (3710), the session management function may receive a first request message from the access and mobility management function indicating that the first request message is for a time-sensitive network (TSN) bridge. In step (3720), the SMF may select a user plane function (UPF) that supports the TSN function based on the elements of the request message. In step (3730), the SMF may send a second request message to the UPF to configure the UPF for the TSN bridge.

[0318] In one example, a wireless device may receive a request from a first station indicating the configuration of a Time-Sensitive Network (TSN) bridge for the transmission of a stream of data packets. The wireless device may transmit a non-access layer message to a Session Management Function (SMF) containing at least one parameter for the configuration of the TSN bridge. The wireless device may receive a response message from the SMF indicating that the TSN bridge has been configured for the transmission of a stream of data packets. The wireless device may transmit a message to the first station indicating the successful configuration of the TSN bridge. In one example, the request may include a Stream Reservation Protocol (SRP) message requesting the configuration of a Time-Sensitive Network (TSN) bridge for the transmission of a stream of data packets between the first station and the second station. The SRP message may include an identifier for the stream of data packets, at least one parameter for the configuration of the TSN bridge, etc. At least one transmission parameter for a stream of data packets includes an identifier for the stream of data packets, data frame parameters, a user for network requirement parameters, priority and rank indication parameters, latency values, traffic specification parameters, etc. The response message may be an SRP response message indicating that the second station is ready for transmission of the stream.

[0319] In an exemplary embodiment, a wireless device may receive a Stream Reservation Protocol (SRP) message from a first station requesting the configuration of a Time-Sensitive Network (TSN) bridge for the transmission of a stream of data packets between the first station and the second station. The SRP message may include an identifier for the stream of data packets, at least one parameter for the configuration of the TSN bridge, etc. In one example, the wireless device may transmit a non-access layer message containing the SRP message to a Session Management Function (SMF) to configure the TSN bridge. The wireless device may receive an SRP response message indicating that the second station is ready for the transmission of the stream. The wireless device may transmit the SRP response message to the first station. In one example, the SRP response may be received from a control plane network component of the TSN bridge. The SRP response may be received from the second station of the TSN system. The wireless device may determine that a TSN-type PDU session is required for the transmission of the stream of data packets. The access layer message may further include a parameter indicating that the PDU session is for a TSN bridge or a TSN end station. The wireless device may decide to transmit the SRP via a control plane message. The identifier of the stream of data packets may include the identifier of the first station, the identifier of the second station, etc.

[0320] In an exemplary embodiment, a wireless device may receive a Stream Reservation Protocol (SRP) message from a first station requesting the reservation of network resources for a stream of data packets between the first station and the second station via a time-sensitive network (TSN) bridge. The SRP message may include an identifier for the stream of data packets, at least one transmission parameter for the stream of data packets, etc. Based on the SRP message, the wireless device may decide to establish a Packet Data Unit (PDU) session for the TSN. The wireless device may transmit a second message to a Session Management Function (SMF) requesting the establishment of a PDU session for the stream of data packets. The second message may include the SRP message, a parameter indicating that the PDU session is for the TSN, etc. The wireless device may receive an SRP response message indicating that the second station is ready to receive the stream of data packets. The wireless device may transmit an SRP response message to the first station. In one example, the wireless device may receive a stream of packets from the first station. A wireless device can transmit a stream of packets through a PDU session. In one example, the wireless device can receive an SRP message from a first station through a TSN converter. At least one transmission parameter for a stream of data packets may include an identifier for the stream of data packets, data frame parameters, a user for network requirement parameters, priority and rank indication parameters, latency values, traffic specification parameters, etc. Data frame parameters may include a source MAC address for the stream of data packets, a destination MAC address for the stream of data packets, an identifier for a VLAN, etc.The user for network requirement parameters may include parameters indicating latency requirements for a stream of data packets, parameters indicating redundancy requirements for a stream of data packets, etc. Latency values ​​may include accumulated latency values. Traffic specification parameters may include parameters indicating the size of a data frame, parameters indicating the number of data frames, etc. The second message may be a Non-Access Layer (NAS) message. The SRP response message may be a NAS message. The SRP response message may be received through a session management function. The SRP response message may be received through a PDU session. The SRP response message may be received through a user plane function. The wireless device may extract at least one transport parameter for a stream of data packets. The wireless device may map at least one transport parameter to a Quality of Service (QoS) parameter. The second message may further include an identifier of a TSN bridge. The TSN bridge may be a 3GPP system including an entry port and an exit port. The exit port may include a wireless device or a user plane function. The entry port may include a wireless device or a user plane function. The second message may include an identifier of a port associated with the first end station of the TSN system. The SMF may transmit an SRP message to the user plane function (UPF).

[0321] In an exemplary embodiment, a wireless device of a time-sensitive network (TSN) bridge may receive a configuration message from a session management function requesting the reservation of network resources for a stream of data packets for the TSN bridge. Based on the configuration message, the wireless device may decide to modify a packet data unit (PDU) session through the TSN bridge for the transmission of the stream of data packets. The wireless device may transmit a NAS message to the session management function (SMF) that includes at least one transmission parameter for the stream of data packets. In one example, the configuration message may include an identifier for the stream of data packets, at least one transmission parameter for the stream of data packets, etc. The at least one transmission parameter for the stream of data packets may include an identifier for the stream of data packets, data frame parameters, a user for network requirement parameters, priority and rank indication parameters, latency values, traffic specification parameters, etc. The NAS message may include an SRP message, a parameter indicating that the PDU session is for the TSN, etc. The SRP message may include identifiers for streams of data packets, data frame parameters, user for network requirement parameters, priority and rank indication parameters, latency values, traffic specification parameters, etc. The wireless device may receive an acknowledgment message indicating that the PDU session to the TSN system is successful. The wireless device may transmit the SRP message to the first station. The wireless device may receive an SRP response message from the first station. The wireless device may transmit the SRP response message to the second station.

[0322] In an exemplary embodiment, a wireless device may receive a Stream Reservation Protocol (SRP) message from a session management function requesting the reservation of network resources for a stream of data packets for a time-sensitive network (TSN). The SRP message may include an identifier for the stream of data packets, at least one transmission parameter for the stream of data packets, etc. Based on the SRP message, the wireless device may decide to establish a Packet Data Unit (PDU) session for the TSN. The wireless device may transmit a second message to the session management function (SMF) requesting the establishment of a PDU session for the stream of data packets. The second message may include the SRP message, a parameter indicating that the PDU session is for the TSN, etc. The wireless device may receive an acknowledgment message indicating that the PDU session for the TSN system is successful. The wireless device may transmit the SRP message to a first station. The wireless device may receive an SRP response message from a first end station. The wireless device may transmit the SRP response to a second station.

[0323] In an exemplary embodiment, a session management function (SMF) may receive a NAS message from a wireless device containing at least one transport parameter for a stream of data packets. The SMF may decide to configure a UPF for TSN packet transmission. The SMF may send a message to the UPF configuring the UPF for the TSN bridge. The NAS message may contain an identifier of the time-sensitive networking (TSN) bridge. The SMF may receive an acknowledgment message from the UPF indicating the successful configuration of the bridge. The message may include components of at least one transport parameter for a stream of data packets.

[0324] In an exemplary embodiment, a Session Management Function (SMF) may receive a NAS message from a wireless device containing an identifier of a Time-Sensitive Networking (TSN) bridge. The SMF may decide to configure a UPF for TSN packet transmission. The SMF may send a message to the UPF configuring the UPF for the TSN bridge. The SMF may receive an acknowledgment message from the UPF indicating successful configuration of the bridge. The NAS message may be a request for the establishment of a PDU session for Time-Sensitive Networking (TSN) packet transmission through the TSN bridge. The NAS message may include an identifier of a port of the wireless device. The port may be associated with the TSN bridge. The message may be an N4 session establishment request. The message may include an identifier of the TSN bridge, an identifier of the port associated with the packet transmission, etc. The acknowledgment message may include an identifier of the TSN bridge. The message may include a Stream Reservation Protocol (SRP). The SRP may include an identifier for a stream of data packets, data frame parameters, user for network requirement parameters, priority and rank indication parameters, latency values, traffic specification parameters, etc. The message may include an identifier for a stream of data packets. The SMF may send a QoS flow request for a stream of data packets to the PCF. The SMF may receive at least one PCC rule for a QoS flow of a stream of data packets from the PCF.

[0325] In an exemplary embodiment, a session management function (SMF) may receive a message from a wireless device requesting the establishment of a PDU session for time-sensitive network (TSN) packet transmission through a TSN bridge. The SMF may decide to configure a UPF for TSN packet transmission. The SMF may send a session establishment request to the UPF, including the identifier of the TSN bridge, the identifier of the port associated with the packet transmission, etc. The SMF may receive an acknowledgment from the UPF indicating the successful configuration of the port for packet transmission.

[0326] In an exemplary embodiment, a Session Management Function (SMF) may receive a message from a wireless device requesting the establishment of a PDU session for a stream of data packets for a Time-Sensitive Network (TSN). The message may include a Stream Reservation Protocol (SRP) message containing an identifier for the stream of data packets, at least one transmission parameter for the stream of data packets, and a parameter indicating that the PDU session is for the TSN. Based on the message, the SMF may determine that the PDU session establishment is for the TSN system. Based on at least one transmission parameter for the stream of data packets, the SMF may determine a Quality of Service requirement parameter. The SMF may transmit an SRP message targeting a second station as a network function. The SMF may transmit a second message requesting the establishment of a PDU session for the TSN system to a UPF. The second message may include an identifier for the stream of data packets, a Quality of Service requirement parameter, etc. In one example, the network function may be at least one of a Network Exposure Function (NEF) or a User Plane Function (UPF). The SMF can transmit a QoS flow request for a stream of data packets to the PCF. The SMF can receive at least one PCC rule for the QoS flow of the stream of data packets from the PCF. The QoS flow request may include at least one transport parameter for the stream of data packets.

[0327] In an exemplary embodiment, the session management function may receive from a wireless device a time-sensitive networking (TSN) system, a first message indicating a request for establishing a PDU session for a stream of data packets, a first message including an identifier for the stream of data packets, and at least one parameter characterization requirement for the transmission of the stream of data packets. Based on the first message, the SMF may determine that the request for establishing a PDU session is for the TSN system. Based on the at least one parameter characterization requirement for the transmission of the stream of data packets, the SMF may determine a quality of service requirement parameter. The SMF may send a second message to the UPF requesting the establishment of a PDU session for the TSN system, and including an identifier for the stream of data packets and a quality of service requirement parameter. In one example, the SMF may send a request for a QoS flow to the PCF. The SMF may receive one or more PCC rule(s) for the QoS flow from the PCF. The NEF may receive an SRP message from the SMF. The NEF may send the SRP message to a network node. A network node may include a TSN converter device, a policy control function, or an application function. A network node may transmit an SRP message to a second TSN bridge. A network node may receive an SRP message from the second TSN bridge.

[0328] In an exemplary embodiment, the session management function may receive a first request message from the access and mobility management function indicating that the first request message is for a time-sensitive network (TSN) bridge. Based on the components of the request message, the SMF may select a user plane function (UPF) that supports TSN functionality. The SMF may send a second request message to the UPF to configure the UPF for the TSN bridge. In one example, the first request message may be for a PDU session establishment request. The first request message may be an N11 request message. The second request message may be an N4 session establishment request message. The SMF may send a discovery request to the network store function (NRF) to select the UPF. The SMF may receive an identifier of a UPF that supports TSN functionality from the NRF. The discovery request message may include TSN performance metrics.

[0329] In an exemplary embodiment, the Session Management Function (SMF) may receive a PDU session establishment request from the Access and Mobility Management Function indicating that the PDU session is for a Time-Sensitive Network (TSN) bridge. The SMF may send a discovery request message to the Network Repository Function (NRF) to select a user plane function, and the discovery request message may include TSN performance metrics. The SMF may receive an identifier of a UPF that supports the TSN function from the NRF. The SMF may send a session establishment request message to the UPF.

[0330] In this specification, a and an and similar phrases are to be interpreted as at least one and one or more. In this specification, the term "can" is to be interpreted, for example, as "can." That is, the term "can" may indicate that the phrase following the term "can" may be an example of one of a number of suitable possibilities that may or may not be used in one or more of various embodiments. If A and B are set and all elements of A are also elements of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell1, cell2} are {cell1}, {cell2}, and {cell1, cell2}.

[0331] In this specification, parameters (information elements: IEs) may include one or more objects, and each of these objects may include one or more other objects. For example, if parameter (IE) N includes parameter (IE) M, parameter (IE) M includes parameter (IE) K, and parameter (IE) K includes parameter (information element) J, for example, N includes K and N includes J. In an exemplary embodiment, when one or more messages include multiple parameters, this implies that a specific parameter within the multiple parameters is present in at least one of the one or more messages, but does not necessarily have to be present in each of the one or more messages.

[0332] Many of the components described in the disclosed embodiments may be implemented as modules. A module is defined as a separable element that performs the functions defined herein and has an interface defined to another element. The modules described herein may be implemented as hardware, software combined with hardware, firmware, wetware (i.e., hardware having biological elements), or a combination thereof, and these may be behaviorally equivalent. For example, modules may be implemented as software routines written in a computer language configured to be executed by a hardware machine (e.g., C, C++, Fortran, Java, Basic, MATLAB, etc.) or as modeling / simulation programs such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript. Additionally, it may be possible to implement modules using physical hardware, including discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, and C++. FPGAs, ASICs, and CPLDs are often programmed using VHSIC hardware description language (VHDL) or hardware description languages ​​(HDLs) such as Verilog, which configure connections between internal hardware modules with smaller functions on programmable devices. Finally, it is necessary to emphasize that the aforementioned technologies are often used in combination to achieve the results of functional modules.

[0333] Exemplary embodiments of the present invention may be implemented using various physical and / or virtual network elements, software-defined networking, and virtual network functions.

[0334] The disclosure of this patent document includes content protected by copyright. The copyright owner gives no objection to facsimile reproduction by anyone of the patent document or patent application, as indicated in the patent file or record of the Patent Office for limited purposes required by law, but otherwise retains all copyright rights.

[0335] Although various embodiments have been described above, it should be understood that they are presented as examples and are not limited thereto. It will be apparent to those skilled in the art that various changes in form and detail may be made without departing from the spirit and scope of the invention. In fact, after reading the above description, it will be apparent to those skilled in the art(s) that alternative embodiments can be implemented. Accordingly, the embodiments should not be limited by any of the exemplary embodiments described above. In particular, it should be noted that, for example, the above description focuses on example(s) using 5G AN. However, those skilled in the art will recognize that embodiments of the invention may be implemented in one or more legacy systems or systems including LTE. The disclosed methods and systems may be implemented in wireless or wired systems. Features of the various embodiments presented in the invention may be combined. One or more features (methods or systems) of one embodiment may be implemented in other embodiments. To create improved transmission and reception systems and methods, a limited number of exemplary combinations have been shown to indicate to a person skilled in the art the possibility of combining features in various embodiments.

[0336] Additionally, it should be understood that any drawings highlighting functions and advantages are presented for illustrative purposes only. The disclosed architecture is sufficiently flexible and configurable to be used in ways other than those depicted. For example, operations listed in any flowchart may be rearranged or used optionally in some embodiments.

[0337] Furthermore, the purpose of the summary of this disclosure is to enable the United States Patent and Trademark Office and the public, in general, and particularly scientists, engineers, and practitioners in the art who are not familiar with patent or legal terminology or grammar, to quickly determine from a brief examination the nature of the technical disclosure of this application. The summary of this disclosure is not intended to limit the scope of the invention in any way.

[0338] Finally, it is the applicant's intention to claim including expression language of means or steps that can be interpreted pursuant to 35 USC 112. Claims that do not explicitly express phrases of means or steps are not interpreted pursuant to 35 USC 112.

Claims

Claim 1 A method comprising the steps of: receiving, by a wireless device, one or more TSN parameters representing one or more ports on a TSN bridge from a time-sensitive network (TSN) converter device; transmitting a non-access stratum (NAS) message to an access and mobility management function (AMF) by the wireless device, wherein the NAS message represents a request to establish a PDU session for the TSN bridge and includes the one or more TSN parameters; and receiving, by the wireless device, a message from the AMF representing acceptance of the PDU session for the TSN bridge. Claim 2 A method according to claim 1, wherein one or more TSN parameters include priority parameters. Claim 3 A method according to claim 1, wherein one or more TSN parameters include TSN stream identification parameters. Claim 4 A method according to claim 1, wherein the NAS message includes a port identity associated with the wireless device. Claim 5 A method according to claim 1, wherein the NAS message indicates that the PDU session type of the request is for TSN. Claim 6 A wireless device comprising one or more processors and a memory for storing instructions, wherein the instructions cause the wireless device to perform the method of any one of claims 1 to 5 when executed by the one or more processors. Claim 7 A non-transient computer-readable medium comprising a command, wherein the command causes the one or more processors to perform the method of any one of claims 1 to 5 when executed by one or more processors. Claim 8 A method comprising the steps of: receiving, by means of an Access and Mobility Management Function (AMF), a non-access stratum (NAS) message from a wireless device indicating a request to establish a PDU session including one or more TSN parameters representing one or more ports on a TSN bridge; and transmitting by means of the AMF to the wireless device a message indicating an acknowledgment of the PDU session for the TSN bridge. Claim 9 In claim 8, the method wherein one or more of the above TSN parameters include priority parameters. Claim 10 In claim 8, the method wherein one or more TSN parameters include TSN stream identification parameters. Claim 11 A method according to claim 8, wherein the NAS message includes a port identity associated with the wireless device. Claim 12 In paragraph 8, the method wherein the NAS message indicates that the PDU session type of the request is for TSN. Claim 13 An access and mobility management function (AMF) comprising one or more processors and a memory for storing instructions, wherein the instructions, when executed by the one or more processors, cause a base station to perform the method of any one of claims 8 through 12. Claim 14 A non-transient computer-readable medium comprising a command, wherein the command causes the one or more processors to perform the method of any one of claims 8 through 12 when executed by one or more processors. Claim 15 A system comprising a wireless device including one or more processors and memory for storing instructions, wherein the instruction, when executed by the one or more processors, causes the wireless device to receive one or more TSN parameters representing one or more ports on a TSN bridge from a time-sensitive network (TSN) converter device and to transmit a non-access stratum (NAS) message to an access and mobility management function (AMF), wherein the NAS message represents a request to establish a PDU session for the TSN bridge and includes the one or more TSN parameters, and to receive a message from the AMF representing an acknowledgment of the PDU session for the TSN bridge. A system comprising one or more processors and memory for storing instructions, wherein the instruction, when executed by the one or more processors, causes the AMF to receive the NAS message from the wireless device and wherein the NAS message represents a request to establish the PDU session and includes the one or more TSN parameters, and to transmit a message to the wireless device representing an acknowledgment of the PDU session.

Images