URSP assessment for unknown PDU session type

Abstract

Embodiments of the present disclosure relate to URSP assessment for unknown PDU session types. A method includes transmitting, by a user equipment (UE), a first message to a first device, the first message including a request to establish a communication based on a first communication session type and a first set of one or more session attributes associated with the first message. The UE receives a second message from the first apparatus, the second message comprising: an indication that a request to establish communication using the first communication session type is rejected; and after receiving the second message, removing from use the first set of one or more session attributes for establishing the communication, and retransmission of the first communication session type; and sending a third message to the first device or the second device, the third message including a request for communication based on the second communication session type and a second set of one or more session attributes associated with the third message.

Description

Technical Field

[0001] Various example embodiments relate generally to wireless networks, and more particularly, to user equipment routing policy (URSP) evaluation for unknown packet data unit (PDU) session types. Background Art

[0002] In order for a user equipment (UE) to exchange packet data units (PDUs) with a data network in a 5G system, the UE first initiates a PDU session establishment procedure. Such a procedure may be defined, for example, in Section 4.3.2.2 of the 3rd Generation Partnership Project (3GPP) TS23.502. Once the UE initiates a PDU session establishment procedure including a routing descriptor (RSD) of the PDU session type, the session is accepted or rejected by the network (e.g., a session management function (SMF) in the network). In the event that a PDU session is rejected, the UE will continue to attempt to initiate a PDU session with an RSD attachment time, resulting in rejection of subsequent PDU sessions. Summary of the invention

[0003] In one aspect of the present disclosure, a method includes: sending a first message by a user equipment (UE) to a first device, the first message including: a request to establish communication based on a first communication session type and a first set of one or more session attributes associated with the first message. The UE receives a second message from the first device, the second message including: an indication that the request to establish communication using the first communication session type is rejected; and after receiving the second message, removing the first set of one or more session attributes used to establish communication from use, and retransmission of the first communication session type; and sending a third message to the first device or the second device, the third message including: a request for communication based on a second communication session type and a second set of one or more session attributes associated with the third message, wherein a first combination including the first communication session type and the first set of one or more session attributes is different from a second combination including the second communication session type and the second set of one or more session attributes.

[0004] In one aspect of the method, the request to establish communications based on the first communications session type includes a request to establish a protocol data unit (PDU) communications session type or a packet data network (PDN) communications session type.

[0005] In one aspect of the method, the PDU communication session type includes one or more of the following: an IPv4 communication session type, an IPv6 communication session type, an IPv4v6 communication session type, an unstructured communication session type, or an Ethernet communication session type.

[0006] In one aspect of the method, the PDN communication session type includes one or more of: an IPv4 communication session type, an IPv6 communication session type, an IPv4v6 communication session type, a non-Internet Protocol (IP) communication session type, or an Ethernet communication session type.

[0007] In one aspect of the method, the first set of one or more session attributes includes: a first data network name (DNN), or a first access point name (APN).

[0008] In one aspect of the method, the second set of one or more session attributes includes: a second DNN, or a second APN.

[0009] In one aspect of the method, a first set of one or more session attributes includes: a first single network slice selection assistance information (S-NSSAI).

[0010] In one aspect of the method, the second set of one or more session attributes includes: a second S-NSSAI.

[0011] In one aspect of the method, a first communication session type and a first set of one or more session attributes are included in a first routing descriptor (RSD).

[0012] In one aspect of the method, a second communication session type and a second set of one or more session attributes are included in a second RSD.

[0013] In one aspect of the method, the first communication session type is the same as the second communication session type, or the first set of one or more session attributes is the same as the second set of one or more session attributes.

[0014] In one aspect of the method, the second message is a 5G System Session Management (5GSM) message, and the 5GSM message includes: an indication of an unknown PDU session type.

[0015] In one aspect of the method, the second message includes: 5GSM cause value #28 unknown PDU session type.

[0016] In one aspect of the method, the second message is an Evolved Packet System Session Management (ESM) message, the ESM message including an indication of an unknown Packet Data Network (PDN) session.

[0017] In one aspect of the method, the second message is an ESM cause value #28 unknown PDN session message.

[0018] In one aspect of the method, removing from use includes storing, by the UE, the first combination as a combination that is not to be used.

[0019] In one aspect of the method, the combination that is not to be used is consulted by the UE before sending the third message.

[0020] In one aspect of the present disclosure, a user equipment (UE) includes: at least one processor; and at least one memory, wherein the at least one memory stores instructions, which, when executed by the at least one processor, enable the user equipment to perform at least any one of the aforementioned methods.

[0021] In one aspect of the present disclosure, a device includes: at least one processor; and at least one memory, wherein the at least one memory stores instructions, which, when executed by the at least one processor, cause the device to perform at least any one of the aforementioned methods.

[0022] In one aspect of the present disclosure, a processor-readable medium stores instructions, which, when executed by at least one processor of a device, cause the device to at least perform any one of the aforementioned methods.

[0023] According to some aspects, the subject matter of the independent claims is provided. Some further aspects are defined in the dependent claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Some example embodiments will now be described with reference to the accompanying drawings.

[0025] Figure 1 is a diagram of an example embodiment of wireless networking between a network system and a user equipment (UE) according to an exemplary aspect of the present disclosure;

[0026] Figure 2 is a diagram of example components of a network system according to one illustrative aspect of the present disclosure;

[0027] Figure 3 is a diagram of an example embodiment of signals and operations between a UE, an SMF, and a PCF according to one illustrative aspect of the present disclosure; and

[0028] Figure 4 is a diagram of an example embodiment of components of a UE or network device according to one illustrative aspect of the present disclosure. DETAILED DESCRIPTION

[0029] In the following description, certain specific details are set forth in order to provide a thorough understanding of the disclosed aspects. However, one skilled in the relevant art will recognize that the aspects may be practiced without one or more of these specific details, or with other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers are not shown or described in detail to avoid unnecessarily obscuring the description of the aspects.

[0030] Reference throughout this specification to "an aspect" or "aspects" means that a particular feature, structure, or characteristic described in conjunction with that aspect is included in at least one aspect. Thus, the appearance of the phrase "in an aspect" or "in aspects" in various places throughout this specification does not necessarily refer to the same aspect. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more aspects.

[0031] The embodiments described in the present disclosure may be implemented in wireless networking devices, such as, but not limited to, devices utilizing wireless networking systems such as Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile Communications (GSM, 2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS, 3G) based on basic Wideband Code Division Multiple Access (W-CDMA), High Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), LTE Advanced, Enhanced LTE (eLTE), 5G New Radio (5G NR), 5G Advanced, 6G (and above), and 802.11ax (Wi-Fi 6). The term "eLTE" herein refers to LTE evolution connected to a 5G core. LTE is also known as Evolved UMTS Terrestrial Radio Access (EUTRA), or Evolved UMTS Terrestrial Radio Access Network (EUTRAN).

[0032] The present disclosure may use the term "serving network device" to refer to a network node or network device (or a portion thereof) that serves a UE. As used herein, the terms "send to," "receive from," and "cooperate" (and variations thereof) include communications that may or may not involve communications through one or more intermediate devices or nodes. The term "acquire" (and variations thereof) includes acquiring in a first instance, or reacquiring after a first instance. The term "connect" may mean a physical connection or a logical connection.

[0033] The present disclosure uses 5G NR as an example of a wireless network, and may use a smartphone and / or an extended reality headset as an example of a UE. It is intended and should be understood that these examples are merely illustrative, and the present disclosure may be applied to other wireless networks and user equipment.

[0034] Figure 1 1 is a diagram depicting an example of wireless networking between a network system 100 and a user equipment (UE) 150. The network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network devices 130 (e.g., test equipment). The network node 120 will be described in more detail below. As used herein, the term "network device" may refer to any component of the network system 100, such as a server 110, a network node 120, a network device 130, any of the aforementioned components, and / or any other component of the network system 100. Examples of network devices include, but are not limited to, devices that implement aspects of 5G NR, etc. The present disclosure describes embodiments involving 5G NR, as well as embodiments involving aspects defined by the Third Generation Partnership Project (3GPP). However, it is contemplated that embodiments involving other wireless networking technologies are included within the scope of the present disclosure.

[0035] The following description provides further details of an example of a network node. For example, in a 5G NR network, a gNodeB (also referred to as a gNB) may include a node that provides new radio (NR) user plane and control plane protocol ports to the UE and is connected to the 5G Core (5GC) via an NG interface, for example, in accordance with 3GPP TS 38.300 V16.6.0 (2021-06) Section 3.2, which is incorporated herein by reference.

[0036] The gNB supports various protocol layers, such as Layer 1 (L1) – physical layer, Layer 2 (L2), and Layer 3 (L3).

[0037] Layer 2 (L2) of NR is divided into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Service Data Adaptation Protocol (SDAP), where, for example:

[0038] oThe physical layer provides transport channels to the MAC sublayer;

[0039] o The MAC sublayer provides logical channels to the RLC sublayer;

[0040] o The RLC sublayer provides RLC channels to the PDCP sublayer;

[0041] o The PDCP sublayer provides radio bearers to the SDAP sublayer;

[0042] o The SDAP sublayer provides Quality of Service (QoS) flows to the 5GC;

[0043] oControl channels include the Broadcast Control Channel (BCCH) and the Physical Control Channel (PCCH).

[0044] For example, Layer 3 (L3) includes Radio Resource Control (RRC) (e.g., in accordance with Section 6 of 3GPP TS 38.300 V16.6.0 (2021-06)), which is hereby incorporated by reference.

[0045] For example, a gNB Central Unit (gNB-CU) includes logical nodes that host protocols such as Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) of a gNB or RRC and PDCP protocols of an en-gNB, which controls the operation of one or more gNB Distributed Units (gNB-DUs). The gNB-CU terminates the F1 interface connected to the gNB-DU. The gNB-CU may also be referred to herein as a CU, Central Unit, Centralized Unit, or Control Unit.

[0046] For example, a gNB distributed unit (gNB-DU) includes logical nodes such as the radio link control (RLC), media access control (MAC), and physical (PHY) layers of a hosted gNB or en-gNB, and its operation is partially controlled by the gNB-CU. One gNB-DU supports one or more cells. A cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected to the gNB-CU. The gNB-DU may also be referred to as a DU or distributed unit in this article.

[0047] As used herein, the term "network node" may refer to any one of a gNB, a gNB-CU, or a gNB-DU, or any combination thereof. A RAN (Radio Access Network) node or a network node (such as, for example, a gNB, a gNB-CU, or a gNB-DU, or a part thereof) may be implemented using, for example, a device having at least one processor configured to support and / or provide and / or process functionalities and / or features related to the CU and / or DU, and / or at least one protocol (sub) layer (e.g., layer 2 and / or layer 3) of the RAN (Radio Access Network) and / or at least one memory with processor-readable instructions (program). Different functional divisions between central units and distributed units are possible. The following will be combined with Figure 4 to describe examples of such devices and components.

[0048] The gNB-CU and gNB-DU parts may be located in one place, or physically separated, for example. The gNB-DU may even be further divided into two parts, for example, one including a processing device and one including an antenna. The central unit (CU) may also be referred to as a baseband unit / radio equipment controller / cloud-RAN / virtual-RAN (BBU / REC / C-RAN / V-RAN), an open-RAN (O-RAN), or a part thereof. The distributed unit (DU) may also be referred to as a remote radio head / remote radio unit / radio equipment / radio unit (RRH / RRU / RE / RU) or a part thereof. Hereinafter, in various example embodiments of the present disclosure, a network node supporting at least one of the central unit functions or the layer 3 protocols of the radio access network may be, for example, a gNB-CU. Similarly, a network node supporting at least one of the distributed unit functions or the layer 2 protocols of the radio access network may be, for example, a gNB-DU.

[0049] A gNB-CU may support one or more gNB-DUs. A gNB-DU may support one or more cells and may therefore support a serving cell for a user equipment (UE) or a candidate cell for handover, dual connectivity, and / or carrier aggregation.

[0050] User equipment (UE) 150 may be or include other types of user equipment such as a wireless or mobile device, a device having a wireless interface to interact with a RAN (radio access network), a smart phone, a vehicle-mounted device, an IoT device, or an M2M device. Such a UE 150 may include: at least one processor; and at least one memory including program code; wherein the at least one memory and the computer program code are configured to, together with the at least one processor, enable the device to at least perform certain operations, such as, for example, an RRC connection with a RAN. Figure 4 An example of components of a UE is described. In an embodiment, the UE 150 may be configured to generate a message (e.g., including a cell ID) to be sent to the RAN via radio (e.g., to reach and communicate with a serving cell). In an embodiment, the UE 150 may generate, send, and receive RRC messages containing one or more RRCPDUs (packet data units). Those skilled in the art will understand the RRC protocol and other processes that the UE may perform.

[0051] Continue to refer Figure 1In the example of a 5G NR network, the network system 100 provides one or more cells that define the coverage area of ​​the network system 100. As described above, the network system 100 may include a gNB of the 5G NR network, or may include any other device configured to control radio communications and manage radio resources within a cell. As used herein, the term "resource" may refer to a radio resource, such as a resource block (RB), a physical resource block (PRB), a radio frame, a subframe, a time slot, a subband, a frequency region, a subcarrier, a beam, etc. In an embodiment, the network node 120 may be referred to as a base station.

[0052] Figure 1 Examples are provided and are merely illustrative of the network system 100 and the UE 150. Those skilled in the art will appreciate that the network system 100 includes Figure 1 Components not shown in the figure, and it will be understood that other user devices can communicate with the network system 100.

[0053] Figure 2 yes Figure 1 A 5G NR network may be described as an example of a network system 100, and aspects described below may also apply to other types of network systems. The network system may be based on Figure 1 1 and 2. The signals and connections shown in 220 are operated so that the UE 150 communicates with the network system 100 through the radio access network 225. In addition, the network system can be divided into user plane components and functions, and control plane components and functions, as shown and described in this document. Unless otherwise specified, the terms "component", "function" and "service" are used interchangeably in this document, and they may refer to instructions executed by one or more processors and implemented by the one or more processors.

[0054] Example functions of the components are described below. The example functions are merely illustrative, and it should be understood that additional operations and functions may be performed by the components described herein. In addition, the connections between the components may be virtual connections over service-based interfaces, such that any component may communicate with any other component. In this way, any component may act as a service "producer" for any other component acting as a service "consumer" to provide services for network functions.

[0055] For example, the core network 210 is described in the control plane of the network system. The core network 210 may include an authentication server function (AUSF) 211, an access and mobility function (AMF) 212, and a session management function (SMF) 213. The core network 210 may also include a network slice selection function (NSSF) 214, a network exposure function (NEF) 215, a network repository function (NRF) 216, and a unified data management function (UDM) 217, which may include a unified data repository (UDR) 224.

[0056] Additional components and functions of the core network 210 may include application functions 218, policy control functions (PCF) 219, network data analysis functions (NWDAF) 220, analysis data repository functions (ADRF) 221, management data analysis functions (MDAF) 222, and operation and management functions (OAM) 223.

[0057] The user plane includes UE 150, radio access network (RAN) 225, user plane function (UPF) 226, and data network (DN) 227. RAN 225 may include a combination of Figure 1 The RAN 225 may be a network node or nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides a connection for data sent through the RAN 225. For example, the DN 226 identifies services from a service provider, Internet access, and third-party services.

[0058] AMF 212 handles connection and mobility tasks. AUSF 211 receives authentication requests from AMF 212 and interacts with UDM 217 to authenticate and verify network responses for determining successful authentication. SMF 213 performs packet data unit (PDU) session management and manages session contexts with UPF 226.

[0059] NSSF 214 may select a network slice instance (NSI) and determine the allowed network slice selection assistance information (NSSAI). This selection and determination is used to set up AMF 212 to provide services to UE 150. NEF 215 ensures third-party access to network services to create dedicated network services. NRF 216 acts as a repository for storing network functions to allow functions to register and discover each other.

[0060] UDM 217 generates authentication vectors for use by AUSF 211 and ADM 212, and provides user identification processing. UDM 217 may be connected to UDR 224, which stores data associated with authentication, applications, etc. AF 218 provides application services (e.g., streaming services, etc.) to users. PCF 219 provides policy control functions. For example, PCF 219 can help with network slicing and mobility management, as well as provide quality of service (QoS) and charging functions.

[0061] NWDAF 220 collects data (e.g., from UE 150 and network systems) to perform network analysis and provides insights into functions that utilize the analysis when providing services. ADRF 221 allows consumers to store, retrieve, and remove data and analysis. MDAF 222 provides additional data analysis services for network functions. OAM 223 provides provisioning and management processing functions to manage elements in the network or elements connected to the network (e.g., UE 150, network nodes, etc.).

[0062] Figure 2 These are merely examples of components of a network system, and various variations are considered to be within the scope of the present disclosure. In an embodiment, a network system may include Figure 2 In an embodiment, the network system may not include other components not shown in the figure. Figure 2 In an embodiment, components and connections may be in the same manner as Figure 2 These and other embodiments are considered to be within the scope of the present disclosure.

[0063] Although further details will be provided below, as described above, in order for the UE to exchange protocol data units (PDUs) with a data network via a 5G system, the UE initiates a PDU session establishment procedure according to, for example, Section 4.3.2.2 of 3GPP TS 23.502.

[0064] In various embodiments, the UE initiates the PDU session establishment process by sending a PDU session establishment request message to the SMF (e.g., according to Section 8.3.1 of 3GPP TS 24.501). The SMF receiving the PDU session establishment request message accepts or rejects the request. The UE initiating the PDU session establishment process determines the attributes of the PDU session that the UE requests to establish. In various embodiments, the attributes of the PDU session may be shown in 3GPP TS 23.501, which is understood by those skilled in the art.

[0065] In short, the UE can use the UE routing policy (URSP) to determine the PDU session attributes. For example, the UE evaluates the received URSP rules to select a specific route (eg, PDU session attributes) suitable for a specific service for the application.

[0066] In the URSP rules set forth in, for example, 3GPP TS24.526, services may be determined by a service descriptor (TD), and routes may be determined by a routing descriptor (RSD). An RSD may contain multiple parameters, and a PDU session type may include a type of PDU session (e.g., IPv4, IPv6, IPv4v6, or Ethernet). Those skilled in the art will appreciate the PDU session type that may be specified by an RSD.

[0067] If the UE follows the selected RSD and the attempt to establish a PDU Session fails because the requested PDU Session type cannot be recognized or is not allowed, the network may respond with a 5GSM cause value #28 "Unknown PDU Session Type" message. For example, the Data Name Network (DNN) requested by the PDU Session does not support the type of PDU Session requested by the UE. In this example case, the UE may continue to retry multiple times to establish a PDU Session with the DNN, resulting in multiple failure messages.

[0068] Although further details are briefly provided below, in various embodiments, a UE that receives a failure message from a network (e.g., a network device) may attempt to establish a PDU session with the same PDU session type for another DNN that may support the PDU session type. In various embodiments, a UE that receives a failure message from a network may remember the type of PDU session type that caused the failure for a particular DNN and may ignore any RSDs that use the same PDU session type that caused the failure. In various embodiments, the UE may ignore any PDU session type / DNN combination for which a 5GSM cause value #28 "Unknown PDU Session Type" message is received during the URSP rule evaluation process.

[0069] As used herein, communication with a radio access network (RAN) may refer to and mean communication with a portion of the RAN, such as with a network node (e.g., DU and / or CU), or another portion of the RAN. As used herein, communication with a core network may refer to and mean communication with one or more services / applications of the core network, such as an AMF or another service of the core network.

[0070] As used herein, in various embodiments, the terms "first" and "second", etc. may refer to the first instance or second instance of a message sent / received by a component (e.g., UE, device, etc.), or the first component or second component in a sequence of the components. In various embodiments, the terms "first" and "second" do not imply any order. Therefore, these terms are used in a non-restrictive manner and may refer to any message, operation, device, component, etc.

[0071] According to the brief description, Figure 3 3 is a diagram of an exemplary embodiment of signals and operations 300 between a UE, an SMF, and a PCF according to an exemplary aspect of the present disclosure. The following paragraphs will describe various signals and operations. It should be understood that the described signals may have associated operations, and the described operations may have associated signals.

[0072] like Figure 3 As shown in FIG. , the UE may include Figure 1 UE 150 described in the above, and the SMF may include SMF 213, and the PCF may include Figure 2 PCF 219 described in.

[0073] Prior to operation 301, the PCF sends a message including a URSP rule, and the UE receives the message including the URSP rule. Upon receiving the URSP rule, the UE evaluates the URSP rule related to selecting an RSD and a DNN included in the URSP rule at operation 301. In various embodiments, the UE may select a first RSD and a first DNN to attempt to establish a PDU session for communicating with the network.

[0074] For example, at operation 302, the UE may select a first RSD (e.g., RSD_1) having a first DNN (e.g., DNN=ABC), which includes a first PDU session type (e.g., IPv4), and one or more other parameters / attributes (e.g., attribute NSSAI, session and service continuity (SSC) mode). Those skilled in the art will appreciate that any type of RSD, DNN, and PDU session may be selected according to operation 302.

[0075] In various embodiments, the PDU session type (such as the first PDU session type) may include any of the following: IPv4, IPv6, IPv4v6, unstructured, or Ethernet PDU session type. In one or more embodiments, the attributes may include any one or more of the following: DNN, access point name (APN), or single network slice selection assistance information (S-NSSAI). In various embodiments, the RSD may include a packet data network (PDN) session.

[0076] Accordingly, at operation 303, the UE sends a PDU session establishment request message to the SMF, and the SMF receives the PDU session establishment request message. In various embodiments, the PDU session establishment request message includes a selection of the UE for the PDU session (e.g., DNN=ABC, PDU session type=IPv4, other parameters, etc.).

[0077] Upon receiving the PDU session establishment request message, if the requested DNN does not support the requested PDU session type, for example, at operation 304, the SMF sends a PDU session establishment reject (cause value #28 "Unknown PDU session type") message to the UE, and the UE receives the PDU session establishment reject (cause value #28 "Unknown PDU session type") message. In various embodiments, the session rejection message (such as the PDU session establishment reject message) may be an Evolved Packet System Session Management (ESM) message, the ESM message including a cause value #28 for an unknown PDN. In various embodiments, the rejected combination of the first PDU session type and the first one or more attributes may be stored (e.g., in a memory) so that the session establishment request is not requested again for the rejected combination.

[0078] Upon receiving a PDU session establishment reject (cause value #28 "unknown PDU session type") message from the SMF, at operation 305, the UE may determine that the first RSD includes another / second DNN (e.g., DNN=XYZ), the first PDU session type, and other parameters that the UE seeks to establish communication with the network. Accordingly, the UE may decide to reuse the first RSD combined with the second DNN.

[0079] Accordingly, in various embodiments, at operation 306, the UE sends a second PDU session establishment request message to the SMF, and the SMF receives the second PDU session establishment request message. The second PDU session establishment request message includes the UE selection for the PDU session (e.g., DNN=XYZ, PDU session type=IPv4, other parameters, etc.).

[0080] If the 5GSM cause value in the PDU session establishment reject message at operation 304 is #28 "Unknown PDU session type", and the PDU session establishment request message sent at operation 305 contains a PDU session type IE indicating the PDU session type, the UE 300 will ignore the backoff timer value IE and the retry indicator IE (if any) provided by the network. The UE 300 can send another PDU session establishment request message 306 to establish a new PDU session with another DNN (for example, another DNN in the same routing descriptor, if any) or another PDU session type (for example, another PDU session type in another routing descriptor, if any). If the PDU session is a multi-access PDU session, the UE's behavior for the 5GSM cause value #28 also applies.

[0081] Similar operations may be applied to EPS. If the ESM cause value in the PDN connection rejection message at operation 304 is #28 "Unknown PDN type", and the PDN connection request message sent at operation 305 contains a PDN type IE indicating the PDN connection type, the UE will ignore the backoff timer value IE provided by the network, and the retry indicator IE (if any). The UE 300 may send another PDN connection request message 306 having a PDN type IE indicating another PDN connection type, or having an access point name IE indicating another access point name.

[0082] If the second DNN supports the requested PDU session, the PDU session is established. For example, at operation 307, it is proposed that the SMF rejects the new combination set forth in the second PDU session establishment request message.

[0083] Accordingly, at operation 308, the SMF sends a PDU session establishment reject (cause value #28 "Unknown PDU session type") message to the UE, and the UE receives the PDU session establishment reject (cause value #28 "Unknown PDU session type") message.

[0084] When a PDU session establishment rejection (cause value #28 "unknown PDU session type") message is received at operation 308, the UE determines a next RSD (e.g., RSD_2) having the first DNN, the first PDU session type, and other parameters at operation 309. At operation 310, in various embodiments, the UE decides not to establish a PDU session with the second RSD and determines a subsequent RSD to establish communication. Accordingly, at operation 311, the UE determines a subsequent RSD (e.g., RSD_3) having the first DNN (DNN=ABC), the second PDU session type (e.g., IPv6), and other parameters for establishing a PDU session.

[0085] In various embodiments, when the UE evaluates the RSD, if the RSD includes a PDU session type and one or more DNNs, and for all possible [PDU session type, DNN] combinations contained in the selected routing descriptor, the network has rejected the request to establish a PDU session with a 5GSM cause value #28 "Unknown PDU session type" or rejected the request to establish a PDN connection with an ESM cause value #28 "Unknown PDN connection type"; or if the RSD does not include a DNN, and for the [PDU session type, no DNN] combination, the network has rejected the request to establish a PDU session with a 5GSM cause value #28 or rejected the request to establish a PDN connection with an ESM cause value #28 "Unknown PDN connection type", the UE does not use the RSD to establish the PDU session or PDN connection, and evaluates another RSD or other information in the UE.

[0086] Accordingly, at operation 312, the UE sends a subsequent PDU session establishment request message to the SMF, and the SMF receives the subsequent PDU session establishment request message. The subsequent PDU session establishment request message includes the UE's selection for the PDU session (e.g., DNN=ABC, PDU session type=IPv6, other parameters, etc.). In various embodiments, the UE may send a subsequent PDU session establishment request message to another SMF (e.g., a second SMF). In various embodiments, the UE may send a subsequent PDU session establishment request message to the same SMF as the SMF to which the UE sent the first PDU session establishment request message.

[0087] When accepting a PDU session, the SMF sends a PDU session establishment accept message to the UE, and the UE receives the PDU session establishment accept message. In various embodiments, the UE may remember and ignore (e.g., skip) any next RSD containing the same PDU session type that was rejected with a 5GSM cause value #28 "Unknown PDU session type" for the same DNN. For example, the UE may skip any PDU session type / DNN combination for which the UE receives a 5GSM cause value #28 "Unknown PDU session type" message during the URSP rule evaluation process. In various embodiments, before sending a PDU session establishment request, the stored combinations of PDU session type / one or more attributes (e.g., DNN) may be viewed / consulted so that these combinations are not used (e.g., skipped) to establish a PDU session.

[0088] Figure 3 The operations are merely illustrative and variations are contemplated within the scope of the present disclosure. In an embodiment, the operations may include Figure 3 Other operations not shown in the figure. In an embodiment, the operation may not include Figure 3 In an embodiment, the operation may be performed in the same manner as Figure 3 300. These and other embodiments are considered to be within the scope of the present disclosure. Those skilled in the art will appreciate that although various example components are described as performing various functions, other components may perform those functions described in Figure 300.

[0089] The operation is described below from the perspective of the UE. From this perspective, a method may include: sending a first message by a user equipment (UE) to a first device, the first message including: a request to establish communication based on a first communication session type and a first set of one or more session attributes associated with the first message. The UE receives a second message from the first device, the second message including: an indication that the request to establish communication using the first communication session type is rejected; and after receiving the second message, removing the first set of one or more session attributes used to establish communication from use, and retransmission of the first communication session type; and sending a third message to the first device or the second device, the third message including: a request for communication based on a second communication session type and a second set of one or more session attributes associated with the third message, wherein a first combination including the first communication session type and the first set of one or more session attributes is different from a second combination including the second communication session type and the second set of one or more session attributes.

[0090] Reference now Figure 4, a block diagram of example components of a UE or network equipment (e.g., a RAN or core network) is shown. The device includes an electronic memory 410, a processor 420, a network interface 440, and a memory 450. The various components can be communicatively coupled to each other. The processor 420 can be, and can include, any type of processor, such as a single-core central processing unit (CPU), a multi-core CPU, a microprocessor, a digital signal processor (DSP), a system on a chip (SoC), or any other type of processor. The memory 450 can be a volatile type of memory (e.g., RAM), or a non-volatile type of memory (e.g., NAND flash memory). The memory 450 includes processor-readable instructions that can be executed by the processor 420 to cause the device to perform various operations, including those mentioned herein, such as Figure 3 operation.

[0091] Electronic storage 410 may be, and may include, any type of electronic storage for storing data, such as a hard drive, a solid-state drive, an optical disk, and / or other non-transitory computer-readable media, as well as other types of electronic storage. Electronic storage 410 stores processor-readable instructions for causing, or being configured to cause, the device to perform its operations, and also stores data associated with such operations, such as storing data related to the 5G NR standard, as well as other data. Network interface 440 may implement wireless networking technologies such as 5G NR and / or other wireless networking technologies.

[0092] Figure 4 The components shown in the figure are merely examples, and those skilled in the art will appreciate that the device includes other components not shown, and may include any of the multiple illustrated components. These and other embodiments are considered to be within the scope of the present disclosure. For example, a transmitter and a receiver may be included as components for sending and receiving signals.

[0093] Other embodiments of the present disclosure include the following examples.

[0094] Example 1.1. A user equipment (UE), comprising:

[0095] means for sending, by the UE, a first message to the first device, the first message comprising: a request to establish communications based on a first communications session type and a first set of one or more session attributes associated with the first message;

[0096] means for receiving, by the UE from the first device, a second message including an indication that a request to establish communications using the first communications session type was denied;

[0097] means for removing from use the first set of one or more session attributes used to establish communications and retransmissions of the first communications session type after receiving the second message; and

[0098] A component for sending a third message by a UE to a first device or a second device, the third message comprising: a request for communication based on a second communication session type and a second set of one or more session attributes associated with the third message, wherein a first combination including the first communication session type and the first set of one or more session attributes is different from a second combination including the second communication session type and the second set of one or more session attributes.

[0099] Example 1.2. The UE of Example 1.1, wherein the request to establish communications based on the first communication session type comprises a request to establish a protocol data unit (PDU) communication session type or a packet data network (PDN) communication session type.

[0100] Example 1.3. The UE of Example 1.2, wherein the PDU communication session type comprises one or more of the following: an IPv4 communication session type, an IPv6 communication session type, an IPv4v6 communication session type, an unstructured communication session type, or an Ethernet communication session type.

[0101] Example 1.4. The UE of Example 1.2, wherein the PDN communication session type comprises one or more of the following: an IPv4 communication session type, an IPv6 communication session type, an IPv4v6 communication session type, a non-Internet Protocol (IP) communication session type, or an Ethernet communication session type.

[0102] Example 1.5. The UE of Example 1.1, wherein the first set of one or more session attributes includes: a first data network name (DNN), or a first access point name (APN).

[0103] Example 1.6. The UE of Example 1.5, wherein the second set of one or more session attributes includes: a second DNN or a second APN.

[0104] Example 1.7. A UE according to Example 1.1, wherein the first set of one or more session attributes includes: first single network slice selection assistance information (S-NSSAI).

[0105] Example 1.8. The UE of Example 1.7, wherein the second set of one or more session attributes includes: a second S-NSSAI.

[0106] Example 1.9. The UE of Example 1.1, wherein the first communication session type and the first set of one or more session attributes are included in a first routing descriptor (RSD).

[0107] Example 1.10. The UE of Example 1.1, wherein a second communication session type and a second set of one or more session attributes are included in the second RSD.

[0108] Example 1.11. The UE of Example 1.1, wherein the first communication session type is the same as the second communication session type, or the first set of one or more session attributes is the same as the second set of one or more session attributes.

[0109] Example 1.12. The UE of Example 1.1, wherein the second message is a 5G System Session Management (5GSM) message, the 5GSM message comprising: an indication of an unknown PDU session type.

[0110] Example 1.13. A UE according to Example 1.12, wherein the second message includes: 5GSM cause value #28 unknown PDU session type.

[0111] Example 1.14. The UE of Example 1.1, wherein the second message is an Evolved Packet System Session Management (ESM) message, the ESM message comprising: an indication of an unknown packet data network (PDN) session.

[0112] Example 1.15. The UE of Example 1.14, wherein the second message is an ESM cause value #28 unknown PDN session message.

[0113] Example 1.16. The UE of Example 1.1, wherein removing from use comprises storing, by the UE, the first combination as a combination that is not to be used.

[0114] Example 1.17. A UE according to Example 1.16, wherein the combination that is not used is consulted by the UE before sending the third message.

[0115] Example 2.1. A user equipment (UE), comprising:

[0116] at least one processor; and

[0117] at least one memory storing instructions that, when executed by at least one processor, cause the apparatus to at least:

[0118] sending a first message to a first device, the first message comprising: a request to establish communications based on a first communications session type and a first set of one or more session attributes associated with the first message;

[0119] receiving a second message from the first device, the second message comprising: an indication that a request to establish communications using the first communications session type was denied;

[0120] After receiving the second message, removing from use the first set of one or more session attributes used to establish communications and retransmissions of the first communications session type; and

[0121] A third message is sent to the first device or the second device, the third message including: a request for communication based on a second communication session type and a second set of one or more session attributes associated with the third message, wherein a first combination including the first communication session type and the first set of one or more session attributes is different from a second combination including the second communication session type and the second set of one or more session attributes.

[0122] The embodiments and aspects disclosed herein are examples of the present disclosure and may be embodied in various forms. For example, although some embodiments herein are described as separate embodiments, each embodiment in the embodiments herein may be combined with one or more embodiments in other embodiments herein. The specific structural and functional details disclosed herein should not be interpreted as restrictive, but as the basis of the claims and as a representative basis for teaching those skilled in the art to adopt the present disclosure differently with virtually any appropriate detailed structure. Throughout the description of the drawings, the same reference numerals may refer to similar or identical elements.

[0123] For example, as described above, in various embodiments, in a PDU session establishment operation with URSP rules, the PDU session establishment for the UE is rejected, where the 5GSM reason value #28 of the PDU session type is "Unknown PDU session type", and the specific DNN and the RSD used for the request contain other DNNs, then the UE may retry the PDU session establishment using the same PDU session type but with a different DNN value before moving to evaluating another RSD.

[0124] In various embodiments, the UE may ignore / skip any next RSD containing the same PDU Session Type rejected with 5GSM cause value #28 "Unknown PDU Session Type" for the same DNN. For example, the UE skips any PDU Session Type / DNN combination for which the UE receives a 5GSM cause value #28 "Unknown PDU Session Type" message during the URSP rule evaluation process.

[0125] In various embodiments, the UE may save time and signaling overhead of retrying another PDU session establishment with the same DNN and PDU session type combination which would fail again with the same 5GSM cause value #28 “Unknown PDU Session Type”.

[0126] Although the above operations and signals are described in the context of a 5G wireless system, these operations and signals can be applied to any type of communication network. In various embodiments, although #28 implies that a specific combination of DNN and PDU session type is rejected, the UE can attempt a request with a different DNN and single network slice selection assistance information (S-NSSAI) slice combination for the same PDU session type.

[0127] The phrases "in one aspect," "in multiple aspects," "in various aspects," "in some aspects," or "in other aspects" may each refer to one or more of the same or different aspects according to the invention. The phrase "plurality" may refer to two or more.

[0128] In various embodiments, the terms "first message" and "second message," as well as any subsequent messages, may refer to any messages sent or received in sequence, and are not necessarily limited to any particular message.

[0129] The phrases "in an embodiment," "in multiple embodiments," "in various embodiments," "in some embodiments," or "in other embodiments" may each refer to one or more of the same or different embodiments according to the invention. A phrase in the form "A or B" means "(A), (B), or (A and B). A phrase in the form "at least one of A, B, or C" means "(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C)."

[0130] Any method, program, algorithm or code described herein can be converted into programming language or computer program, or expressed in programming language or computer program. As used herein, the terms "programming language" and "computer program" each include any language for specifying instructions to a computer, and include, but are not limited to, the following languages ​​and their derivatives: assembly, basic, batch file, BCPL, C, C+, C++, Delphi, Fortran, Java, javascript, machine code, operating system command language, Pascal, Perl, PL1, Python, scripting language, visual basic, the metalanguage of the program itself, and all first generation, second generation, third generation, fourth generation, fifth generation or more computer languages. Also include databases and other data patterns, and any other metalanguage. There is no difference between the language of interpreting, compiling, or using compiling and interpreting both methods. There is no difference between the compiled version and the source version of the program. Therefore, the reference to the program is a reference to any and all such states, wherein the programming language can exist in more than one state (such as source, compiling, object, or link). The reference to the program can include the intention of actual instructions and / or these instructions.

[0131] Although aspects of the present disclosure are shown in the accompanying drawings, it is not intended that the disclosure be limited thereto, but rather that the scope of the present disclosure be as broad as the art will allow, and the specification is read similarly. Therefore, the above description should not be interpreted as limiting, but merely as an example of specific aspects. Those skilled in the art will envision other modifications within the scope and spirit of the appended claims.

Claims

1. A method for communication, the method comprising: Sending, by a user equipment (UE) to a first device, a first message comprising: a request to establish communications based on a first communications session type and a first set of one or more session attributes associated with the first message; receiving, by the UE, from the first device, a second message comprising: an indication that the request to establish communications using the first communications session type is denied; removing from use said first set of one or more session attributes for establishing communications, and retransmissions of said first communications session type, after said receiving said second message; and A third message is sent by the UE to the first device or the second device, the third message including: a request for communication based on a second communication session type and a second set of one or more session attributes associated with the third message, wherein a first combination of the first communication session type and the first set of one or more session attributes is different from a second combination of the second communication session type and the second set of one or more session attributes, and wherein the first communication session type is the same as the second communication session type.

2. The method of claim 1 , wherein the request to establish communications based on the first communications session type comprises: A request to establish a protocol data unit (PDU) communication session type, or a packet data network (PDN) communication session type.

3. The method of claim 2, wherein the PDU communication session type comprises one or more of the following: an IPv4 communication session type, an IPv6 communication session type, an IPv4v6 communication session type, an unstructured communication session type, or an Ethernet communication session type.

4. The method of claim 2, wherein the PDN communication session type comprises one or more of the following: an IPv4 communication session type, an IPv6 communication session type, an IPv4v6 communication session type, a non-Internet Protocol (IP) communication session type, or an Ethernet communication session type.

5. The method of claim 1 , wherein the first set of one or more session attributes comprises: A first data network name (DNN) or a first access point name (APN).

6. The method of claim 5, wherein the second set of one or more session attributes comprises: A second DNN or a second APN.

7. The method of claim 1 , wherein the first set of one or more session attributes comprises: First Single Network Slice Selection Assistance Information (S-NSSAI).

8. The method of claim 7, wherein the second set of one or more session attributes comprises: Second S-NSSAI.

9. The method of claim 1, wherein the first communication session type and the first set of one or more session attributes are included in a first routing descriptor (RSD).

10. The method of claim 1, wherein the second communication session type and the second set of one or more session attributes are included in a second RSD.

11. The method according to claim 1, wherein the second message is a 5G System Session Management (5GSM) message, and the 5GSM message includes: Indication of unknown PDU session type.

12. The method according to claim 11, wherein the second message comprises: 5GSM cause value #28 Unknown PDU session type.

13. The method according to claim 1, wherein the second message is an Evolved Packet System Session Management (ESM) message, the ESM message comprising: An indication of an unknown packet data network (PDN) session.

14. The method according to claim 13, wherein the second message is an ESM cause value #28 unknown PDN session message.

15. The method of claim 1, wherein said removing from use comprises: The first combination is stored by the UE as a combination that will not be used. The method according to claim 15 , wherein before the sending of the third message, the combination that will not be used is referenced by the UE.

17. An apparatus for communication, comprising: at least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least perform the method according to any one of claims 1 to 16.

18. The apparatus of claim 17, wherein the apparatus comprises a user equipment.

19. A processor-readable medium storing instructions which, when executed by at least one processor of a device, cause the device to at least perform the method according to any one of claims 1 to 16.

Images