Access control for user devices in connected mode

Abstract

A user equipment operating in a connected mode includes a first layer, a second layer, and a third layer. The first layer generates a request to send a non-initial non-access stratum (NAS) message through a first connection operated according to a first radio access technology (RAT). The second layer determines whether to prohibit the non-initial NAS message from accessing the first connection. In response to prohibiting access to the first connection, the first layer selects a connection to transfer the non-initial NAS message between the first connection and a second connection operated according to a second RAT. In some cases, the non-initial NAS message is a mobile originated short message service (SMS) message or an uplink NAS transport message. In some cases, the first layer is a NAS layer and the second layer is a radio resource control layer.

Description

Background Art

[0001] A wireless communication system includes a network of base stations (also referred to as a radio access network, gNodeB, eNodeB or access point) that provide wireless connections to one or more user devices within a corresponding geographic area or cell. In order to save battery power, the user device can operate in an idle mode that consumes less power but does not allow the user device to transmit uplink data to the core network. The user device is required to transmit an access attempt to the base station to obtain a radio connection and enter a connection mode, which allows the user device to transmit uplink data. If too many user devices use or attempt to use network resources, the base station and / or the core network may be overloaded. Therefore, some access attempts are prohibited (i.e., prevented or blocked) from idle user devices to reduce or limit the resource consumption of the user device. For example, a network operating according to the fourth generation (4G) standard (such as the long term evolution (LTE) standard) defined by the third generation partnership project (3GPP) imposes access restrictions on idle user devices to prevent idle user devices from registering or establishing a radio resource control (RRC) connection with the network. Access prohibition is usually performed by transmitting a prohibition configuration to the user device so that the user device can determine when to prohibit access attempts. BRIEF DESCRIPTION OF THE DRAWINGS

[0002] By referring to the accompanying drawings, the present disclosure may be better understood, and its numerous features and advantages become apparent to those skilled in the art. The use of the same reference symbols in different drawings indicates similar or identical items.

[0003] Figure 1 is a block diagram of a communication system that supports access control and selective use of 3GPP and non-3GPP connections for access attempts according to some embodiments.

[0004] Figure 2 is a block diagram of a network function virtualization (NFV) architecture according to some embodiments.

[0005] Figure 3 is a message flow for performing an access request for an initial non-access stratum (NAS) message according to some embodiments.

[0006] Figure 4 is a message flow for selectively performing an access request for a non-initial NAS message using a 3GPP or non-3GPP connection according to some embodiments.

[0007] Figure 5 is a block diagram of a user equipment supporting network access via 3GPP and non-3GPP connections according to some embodiments.

[0008] Figure 6is a block diagram of a communication system according to some embodiments. DETAILED DESCRIPTION

[0009] The fifth generation (5G) standard defined by 3GPP aims to alleviate the global bandwidth shortage by supporting wireless communications at frequencies above 6 gigahertz (GHz), such as the millimeter wave frequency range between 30 GHz and 300 GHz. The 5G standard applies access prohibition to user equipment in idle mode, connection valid mode, and connection invalid mode. Therefore, access prohibition is not only applied to initial non-access stratum (NAS) messages transmitted by the user equipment in idle mode, such as registration requests, deregistration requests, and service requests, but also to non-initial NAS messages transmitted by the user equipment in connected mode, such as requests for transmitting short message service (SMS) messages via NAS, uplink NAS transmission messages for establishing packet data unit (PDU) sessions, and uplink NAS transmission messages for requesting to modify PDU sessions. However, the current 5G standard does not define how to handle the situation where access attempts that trigger non-initial NAS messages are prohibited. Some embodiments of the user equipment support concurrent 3GPP and non-3GPP connections. Therefore, the 5G standard allows access via 3GPP or non-3GPP, for example, to pass a mobile-initiated SMS-over-NAS message from a user equipment via a connection to a Wi-Fi access point. However, if the 3GPP access lower layers (e.g., the access stratum AS layer below the NAS layer) of the user equipment prohibit access attempts, such as requesting transmission of a mobile originated SMS-over-NAS message via a 3GPP connection, then the connected user equipment cannot utilize the non-3GPP connection.

[0010] If the radio resource control (RRC) layer of the user equipment indicates that the access attempt is prohibited, the user equipment is prohibited from sending non-initial non-access stratum (NAS) messages (e.g., uplink NAS transmission messages) using the 3GPP connection. When the RRC layer indicates that the prohibition of the access category associated with the access attempt is relieved, if still needed, the non-initial NAS message is then sent through the 3GPP connection. However, if the user equipment supports both 3GPP connections and non-3GPP connections, when the user equipment is in connected mode, the user equipment selectively requests to transmit the mobile originated message through the 3GPP connection or the non-3GPP connection. Based on whether the request is prohibited in the RRC layer of the user equipment, a 3GPP connection or a non-3GPP connection is selected for transmitting the mobile originated message. For example, the NAS layer in the user equipment may transmit a query indicating the category or identity of the access request to the RRC layer, which returns a result indicating whether the access category or identity is prohibited. The user equipment transmits the request through the non-3GPP connection (if available) in response to the prohibition request in the RRC layer, and transmits the request through the 3GPP connection in response to the request not being prohibited in the RRC layer.

[0011] In some embodiments, transmission of mobile originated messages is selectively requested for one or more predetermined access categories or identities. For example, based on whether messages in these access categories are prohibited, the user equipment may selectively request transmission of a short message service (SMS) via a non-access stratum (NAS) message, an uplink NAS transmission message for establishing a packet data unit (PDU) session, or an uplink NAS transmission message for requesting modification of a PDU session. Access attempts associated with access categories that are prohibited at the user equipment need to be stopped until the RRC layer indicates that the access prohibition for the corresponding access category is relieved. Once the access prohibition is relieved, if still required, the user equipment initiates the transmission process over the 3GPP connection.

[0012] Figure 1 1 is a block diagram of a communication system 100 according to some embodiments, the communication system supporting access control and selectively using 3GPP and non-3GPP connections for access attempts. As used herein, a 3GPP connection refers to a connection that operates according to a standard established by 3GPP, such as a 5G standard or an LTE standard. Therefore, a 3GPP connection is a connection that operates according to a first radio access technology (RAT). As used herein, a non-3GPP connection refers to a connection that operates according to a non-3GPP standard such as a Wi-Fi standard for wireless access in an unlicensed band. Therefore, a non-3GPP connection is a connection that operates according to a second RAT that is different from the first RAT. Although for clarity, the technology disclosed herein is discussed in the context of 3GPP and non-3GPP connections, some embodiments of the communication system 100 implement different first RATs and second RATs.

[0013] The communication system 100 provides support for both mobile access and fixed access. As used herein, the term "mobile access" refers to accessing a communication system (e.g., the communication system 100) through an air interface. Therefore, mobile access may be referred to as wireless access, mobile communication, wireless communication, or other similar terms. The term "fixed access" refers to accessing a communication system using a device that is physically connected to the communication system, such as accessing a communication system such as the communication system 100 via wires, optical fibers, etc. Therefore, fixed access may be referred to as wired access, wired communication, or other similar terms. In some embodiments, the last leg of the fixed access connection may be provided by a wireless access point such as a Wi-Fi access point. The communication system 100 supports hybrid access, which allows a device to access the communication system 100 simultaneously using mobile access and fixed access.

[0014] The communication system 100 includes a core network 105, which can be accessed by a mobile device or a fixed device using a public user plane access and a control plane that supports public authentication, authorization and accounting (AAA) and policy control. As used herein, the phrase "user plane" refers to a part of a routing architecture that performs routing of packets arriving at an inbound interface. For example, a routing table can be used to implement the user plane to determine the path from the inbound interface to the correct outbound interface through a forwarding structure. The user plane may also be referred to as a data plane or a forwarding plane. As used herein, the phrase "control plane" refers to a part of a routing architecture that defines a network topology. For example, a control plane can be used to configure a routing table that is used to forward packets on a user plane. Control plane logic can also be used to establish a priority or quality of service for a packet, or to identify a packet that should be discarded.

[0015] The core network 105 includes an access and mobility management function (AMF) 110, which manages access control and mobility of devices in the communication system 100. The core network 105 also includes a session management function (SMF) 115 to establish and manage sessions in the communication system 100 according to network policies. The association between the user equipment and the core network 105 can be represented as a protocol data unit (PDU) session that can be managed by the SMF 115. The PDU session supports data connectivity between the user equipment and the data network. The core network 105 also includes a policy control function (PCF) 120, which stores policies for user equipment connected to the core network 105. Therefore, the information stored in the PCF 120 is used to apply policies to actions associated with the user equipment, such as mobility restrictions within the communication system 100.

[0016] The core network 105 also includes a unified data manager (UDM) 125 that handles credentials, location management, subscription management, etc. The UDM 125 stores data including user subscription data, such as subscription identifiers, security credentials, subscription data related to access and mobility, and subscription data related to sessions. The core network 105 also includes one or more user plane functions (UPFs) 130 that can be deployed in the communication system 100 to provide services to users of the communication system 100. As described herein, the user plane function 130 can serve as an endpoint for a service flow for broadcast, multicast, or unicast packets. Therefore, the user plane function 130 can store an endpoint identifier for a service flow. The user plane function 130 is connected to a data network 135.

[0017] The entities within the core network 105 are connected by various interfaces, which are implemented according to standards such as the 5G network architecture. Some embodiments of the core network 105 include other functions, such as those described in the examples for clarity. Figure 1Authentication functions and network function repository functions not shown in FIG. As discussed herein, some embodiments of the core network 105 are implemented using network function virtualization and software defined networking. For example, different network slices may be used to instantiate different instances of AMF 110, SMF 115, UPF 130, or UDM 125 for different users or devices. Each protocol data unit (PDU) session is part of one network slice.

[0018] The core network 105 provides network access to the user equipment 140 via mobile access. For example, the user equipment 140 may access the core network 105 via a base station 145 (or a radio access network) connected to the AMF 110 via a corresponding interface such as an N2 interface. The base station 145 also connects to the AMF 110 via a corresponding interface, such as the N2 interface, which is not shown in the figure for clarity. Figure 1 The N3 interface shown in Figure 1 is connected to UPF120. According to the 5G standard defined by 3GPP, some embodiments of base station 145 are implemented as 5G Gigabit NodeB (gNB). Core network 105 also provides network access to user equipment 140 via fixed access. For example, user equipment 140 can establish a connection with a residential gateway 150, which has a wired connection with Ethernet 155. In the illustrated embodiment, wireless access technology is used to implement the final branch of the fixed access connection between user equipment 140 and core network 105. For example, Wi-Fi access point 160 can be used to provide the last branch of the fixed access connection. However, in other cases, user equipment 140 is connected to residential gateway 150 using a wired connection. Some embodiments of wired connection use line terminal devices such as digital subscriber line access multiplexers (DSLAM) or gigabit passive optical networks (GPON).

[0019] The interworking function 165 is provided between the Ethernet 155 and the core network 105. The interworking function 165 may also be referred to as a non-3GPP interworking function (N3IWF). The interworking function 165 is configured to modify or convert messages transmitted from a fixed access user equipment to the core network 105 so that from the perspective of the core network 105, the fixed access user equipment appears to access the core network 105 according to a mobile access standard or protocol. The interworking function 165 is also configured to modify or convert messages transmitted from the core network 105 to the fixed access user equipment so that the messages received by the fixed access user equipment conform to the corresponding fixed access standard or protocol. The interworking function 165 supports handover with the AMF 110 and the UPF 130.

[0020] The user equipment 140 operates in an idle mode or one of two connected modes (connection invalid mode and connection valid mode). In the idle mode, the user equipment 140 can select a public land mobile network (PLMN), receive broadcast system information, perform cell reselection mobility, and receive a paging message to notify the user equipment 140 of the availability of mobile station terminated data. The idle user equipment 140 does not transmit uplink data to the core network 105. The idle user equipment 140 must switch to one of the connected modes to receive downlink data or transmit uplink data. In the connection invalid mode, the user equipment 140 receives broadcast system information, performs cell reselection mobility, receives a paging message initiated by the radio access network, maintains a user plane and a control plane connection with the core network 105, and has a corresponding context stored in the radio access network and the user equipment 140. In the connection valid mode, the user equipment 140 maintains a user plane and a control plane connection with the core network 105, and has a corresponding context stored in the radio access network and the user equipment 140. The radio access network knows the identity of the cell including the user equipment 140. Unicast data may be delivered to and from the user equipment 140 in the connection active mode. The network may also be able to control the mobility of the user equipment 140, for example based on measurements performed by the user equipment 140.

[0021] Some embodiments of user equipment 140 implement multiple transmitters, receivers, or transceivers operating in accordance with different RATs. For example, user equipment 140 uses a first transceiver operating in accordance with the 5G standard defined by 3GPP and a second transceiver operating in accordance with a non-3GPP standard such as Wi-Fi to communicate in an unlicensed band. Thus, user equipment 140 is able to maintain separate connections operating in accordance with different RATs in parallel in some cases, such as a 5G connection with base station 145 and a Wi-Fi connection with access point 160.

[0022] If the user equipment 140 is in idle mode, the user equipment 140 may transmit an access request to initiate a communication session with the core network 105. For example, the access request may be transmitted as an initial non-access stratum (NAS) message. If the access request is accepted, a connection 170 is established between the user equipment 140 and the core network 105, in which case the user equipment 140 enters a connected mode. The idle user equipment 140 also transmits other initial NAS messages, such as a deregistration request and a service request. When the user equipment 140 operates in one of the connected modes, the user equipment 140 transmits a non-initial access request. The non-initial NAS request includes a request to transmit a short message service (SMS) message via NAS, an uplink NAS transmission message for establishing a packet data unit (PDU) session, and an uplink NAS transmission message requesting modification of a PDU session transmitted by the user equipment in the connected mode.

[0023] As discussed in detail herein, user equipment 140 may determine that non-initial NAS requests are prohibited, such that user equipment 140 does not transmit non-initial NAS requests to base station 145 via connection 170. In some cases, in response to determining that an attempt to transmit a request to base station 145 is prohibited, user equipment 140 transmits a request to send a non-initial NAS message to access point 160 via connection 175. For example, in response to access prohibition of an access request, user equipment 140 stops the request via connection 170. In response to prohibiting access to the first connection, user equipment 140 remains in the current cell and applies a cell reselection process. User equipment 140 may then transmit a request using connection 175 in response to prohibiting access to connection 170. Alternatively, if the request is still needed, user equipment 140 transmits the request after stopping the request in response to the prohibition being relieved.

[0024] Figure 2 is a block diagram of a NFV architecture 200 according to some embodiments. The NFV architecture 200 is used to implement Figure 1 Some embodiments of the communication system 100 shown. For example, instances of AMF 110, SMF 115, PCF 120, and UDM 125 can be instantiated as virtual functions in a NFV architecture 200. The NFV architecture 200 includes hardware resources 201, which include computing hardware 202, storage hardware 203, and network hardware 204. The computing hardware 202 is implemented using one or more processors, the storage hardware 203 is implemented using one or more memories, and the network hardware 204 is implemented using one or more transceivers, transmitters, receivers, interfaces, etc.

[0025] The virtualization layer 205 provides an abstract representation of the hardware resources 201. The abstract representations supported by the virtualization layer 205 can be managed using a virtualization infrastructure manager 210, which is part of the NFV management and orchestration (M&O) module 215. Some embodiments of the manager 210 are configured to collect and forward performance measurements and events that may occur in the NFV architecture 200. For example, performance measurements can be forwarded to an orchestrator (ORCH) 217 ​​implemented in the NFV M&O 215. The hardware resources 201 and the virtualization layer 205 can be used to implement virtual resources 220, which include virtual computing resources 221, virtual storage resources 222, and virtual networking resources 223.

[0026] The virtual networking functions (VNF1, VNF2, VNF3) run on the NFV infrastructure (e.g., hardware resources 201) and utilize virtual resources 220. For example, virtual machines supported by virtual computing resources 221, virtual storage supported by virtual storage resources 222, or virtual networks supported by virtual network resources 223 may be used to implement the virtual networking functions (VNF1, VNF2, VNF3). The element management system (EMS1, EMS2, EMS3) is responsible for managing the virtual networking functions (VNF1, VNF2, VNF3). For example, the element management system (EMS1, EMS2, EMS3) may be responsible for fault and performance management. In some embodiments, each virtual networking function (VNF1, VNF2, VNF3) is controlled by a corresponding VNF manager 225, which exchanges information and coordinates actions with the manager 210 or the orchestrator 217.

[0027] The NFV architecture 200 may include an operations support system (OSS) / business support system (BSS) 230. The OSS / BSS 230 handles network management, including fault management using OSS functions. The OSS / BSS 230 also handles customer and product management using BSS functions. Some embodiments of the NFV architecture 200 use a set of descriptors 235 for storing descriptions of services, virtual network functions, or infrastructure supported by the NFV architecture 200. The information in the descriptors 235 can be updated or modified by the NFV M&O 215.

[0028] The NFV architecture 200 implements network slicing that provides control plane functions or user plane functions, such as Figure 1110, SMF 115, AUSF 120, and UDM 125 shown in FIG. A network slice is a complete logical network that provides communication services and network capabilities that may be different between each slice. A user device can simultaneously access multiple slices that support multiple service flows between the core network and the user device. Some embodiments of the user device provide network slice selection assistance information (NSSAI) parameters to the network to help select a slice instance of the user device. A single NSSAI may cause multiple slices to be selected. The NFV architecture 200 can also use device capabilities, subscription information, and local operator policies to make selections. NSSAI is a collection of smaller components, namely a single NSSAI (S-NSSAI), each of which includes a slice service type (SST) and a possible slice distinguisher (SD). The slice service type refers to the expected network behavior in terms of functions and services (for example, specifically for broadband or large-scale IoT), while the slice distinguisher can help select from multiple network slice instances of the same type, for example to separate traffic related to different services into different slices.

[0029] Figure 3 is a message flow 300 for performing an access request for an initial NAS message according to some embodiments. Figure 1 The message flow 300 is implemented in some embodiments of the user equipment 140 shown in FIG. The user equipment includes a session management layer (5GSM), a mobility management layer (5GMM), and a radio resource control (RRC) layer. The session management layer is referred to as the "upper" layer, and the RRC layer is referred to as the "lower" layer.

[0030] For the purpose of establishing or modifying a PDU session, the session management layer transmits a request 305 to send an initial uplink NAS transfer message. In response to receiving the request 305, the mobility management layer sends a message 310 indicating the access category or one (or more) access identifiers of the request 305. The message 310 including the request and the access category or identifier is transmitted to the lower RRC layer, which determines whether to prohibit the access request. The RRC layer returns a message 315 indicating the prohibition result, such as "prohibited" or "not prohibited". An example of a technique for determining whether to prohibit an access request in an access category or with one (or more) access identifiers is disclosed in "Network Slice Specific Access Barring for Wireless Networks" with serial number 62 / 544,519 filed on August 11, 2017, which is incorporated herein by reference in its entirety. An example of a technique for unified access control is disclosed in 3GPP Technical Specification 24.501, which is incorporated herein by reference in its entirety.

[0031] The user equipment determines (at 320) whether to start a mobile initiated NAS transmission procedure based on the information returned in message 315. If message 315 indicates that the access request is prohibited, the user equipment does not start a mobile initiated NAS transmission procedure. The user equipment remains in the current serving cell and applies a standard cell reselection procedure. In some cases, the RRC layer then returns another message ( Figure 3 The RRC layer may return a message to the mobility management layer indicating that the barring is relieved for the access class or access identifier associated with the previously barred access attempt. If still required, in response to receiving the message indicating that the barring is relieved, a mobile initiated NAS transfer procedure is started.

[0032] Figure 4 4 is a message flow 400 for selectively performing an access request for a non-initial NAS message using a 3GPP or non-3GPP connection according to some embodiments. Figure 1 Message flow 400 is implemented in some embodiments of the user equipment 140 shown in . The user equipment includes an SMS layer (SMS), a mobility management layer (5GMM), and a radio resource control (RRC) layer. The session management layer is referred to as the "upper" layer, and the RRC layer is referred to as the "lower" layer. The user equipment operates in a connected mode. Some embodiments of the user equipment operate in a connection invalid mode or a connection valid mode. The user equipment implements multiple sets of transmitters, receivers, or transceivers to support communications through, for example, a 3GPP connection according to the 5G standard and through a non-3GPP connection such as a Wi-Fi connection in an unlicensed band. In the illustrated embodiment, the user equipment is registered to access the data network via both a 3GPP connection and a non-3GPP connection.

[0033] The SMS layer of the connected user equipment uses the 3GPP connection transport to send a request for a non-initial uplink NAS transport message 405. In the illustrated embodiment, the SMS layer transports a request to send a mobile originated SMS over NAS message 405. Some embodiments of the SMS layer are also configured to transmit requests for other non-initial uplink NAS transport messages, including an uplink NAS transport message for establishing a PDU session, an uplink NAS transport message for requesting to modify a PDU session, and the like.

[0034] In response to receiving the request 405, the mobility management layer sends a message 410 indicating the access category or one (or more) access identifiers of the request 405. The message 410 is transmitted to the lower RRC layer, which determines whether to prohibit the access request of the 3GPP connection. The RRC layer returns a message 415 indicating the prohibition result, such as "prohibited" or "not prohibited". The mobility management layer then selects a connection to transmit the non-initial uplink NAS transport message. In response to prohibiting access to the first connection, some embodiments of the mobility management layer select between the 3GPP connection and the non-3GPP connection.

[0035] The user equipment determines (at block 420) whether to transmit a request to send an SMS over NAS message (or other non-initial uplink NAS transmission message) using the 3GPP connection based on the information returned in message 415. If message 415 indicates that the access request is prohibited, the mobility management layer in the user equipment does not select the 3GPP connection. The user equipment does not start a mobile initiated NAS transmission procedure to initiate an access attempt for the 3GPP connection. The user equipment remains in the current serving cell and applies a standard cell reselection procedure.

[0036] Since the user device is registered to communicate with the data network via a non-3GPP connection such as a Wi-Fi connection, the user device determines whether the non-3GPP connection is available. If so, the mobility management layer determines (at block 425) that the user device can transmit the SMS over NAS message (or other non-initial uplink NAS transmission message) via the non-3GPP connection. Therefore, the mobility management layer in the user device selects the non-3GPP connection and transmits a request 430 to the non-3GPP access lower layer (Wi-Fi) implemented in the user device. The request 430 is to send the SMS over NAS message (or other non-initial uplink NAS transmission message) using the non-3GPP connection available to the user device.

[0037] Non-3GPP connections are not always available to the user equipment, so the user equipment is not always able to send SMS over NAS messages (or other non-initial uplink NAS transport messages) over the non-3GPP connection. In this case, the user equipment continues to avoid making access attempts due to the barring. If the RRC layer subsequently returns another message indicating that the barring is relieved ( Figure 4 430), and access requests are no longer barred for access categories or access identifiers associated with previously barred access attempts, a mobile initiated NAS transfer procedure is started (at block 435) in response to receiving a message indicating that barring is relieved.

[0038] Figure 5is a block diagram of a user equipment 500 supporting network access via 3GPP and non-3GPP connections according to some embodiments. The user equipment 500 is used to implement Figure 1 Some embodiments of the user equipment 140 are shown in FIG. The user equipment 500 is configured to implement Figure 3 The message flow 300 shown in FIG. Figure 4 Some embodiments of the message flow 400 shown in FIG.

[0039] The user equipment 500 includes an SMS layer 505 that generates a request to send an SMS over NAS message. Some implementations of the SMS layer 505 also generate requests for other non-initial uplink NAS messages, including an uplink NAS transport message for establishing a PDU session, an uplink NAS transport message for requesting to modify a PDU session, etc. The user equipment 500 may also implement other layers ( Figure 5 5. The user equipment 500 includes a session management layer 510 configured to send an initial uplink NAS transmission message for the purpose of establishing or modifying a PDU session.

[0040] The mobility management layer 515 in the user equipment 500 is configured to determine the access barring state in response to receiving a request from the SMS layer 505 or the session management layer 510. Some embodiments of the mobility management layer 515, also referred to as the NAS layer, generate a message indicating the access category or one (or more) access identifiers of the request. The mobility management layer 515 transmits the request to the RRC layer 520, which determines whether to prohibit the access request of the 3GPP connection. The RRC layer 520 returns a message indicating the prohibition result to the mobility management layer 515, such as "prohibited" or "not prohibited".

[0041] The user equipment 500 also includes a non-3GPP access layer 525 to support communication via a non-3GPP connection such as a Wi-Fi connection. In response to the RRC layer 520 returning a message indicating that the access request for the 3GPP connection is prohibited, the mobility management layer 515 transmits a request to the non-3GPP access layer 525 to send a non-initial uplink NAS message via the non-3GPP connection. Therefore, depending on whether access via the 3GPP connection is prohibited, the user equipment 500 can selectively transmit a non-initial uplink NAS message via a 3GPP or non-3GPP connection.

[0042] Figure 66 is a block diagram of a communication system 600 according to some embodiments. The communication system 600 includes a core network 605, which is accessible via a wireless access network including a base station 610 operating according to the 5G standard and via an access point 615 operating according to the Wi-Fi standard. Instead of or in combination with the base station 610 and the access point 615, some embodiments of the communication system 600 may be accessed via other devices operating according to the RAT.

[0043] The communication system 600 includes a Figure 1 The user equipment 140 and Figure 5 620 of some embodiments of the user equipment 500 shown in . The user equipment 620 includes a transceiver 625 for transmitting and receiving signals via an antenna 630. Some embodiments of the transceiver 625 include multiple radios for communicating according to different wireless access technologies, such as a radio 635 for communicating with a base station 610 via a 3GPP connection 640, and a radio 645 for communicating in an unlicensed Wi-Fi band (Wi-Fi) via a non-3GPP connection 650. The user equipment 620 also includes a processor 655 and a memory 660. The processor 655 executes instructions stored in the memory 660 and stores information such as results of the executed instructions in the memory 660. Some embodiments of the transceiver 625, the processor 655, and the memory 660 are configured to perform Figure 3 The message flow 300 shown in FIG. Figure 4 4. The portion of the message flow 400 shown in FIG.

[0044] Therefore, the user device 620 is able to identify and handle the following abnormal situations.

[0045] Abnormal condition: The lower layers indicate that the access attempt is prohibited.

[0046] The UE shall not start a UE initiated NAS transmission procedure. The UE stays in the current serving cell and standard cell reselection procedures may apply.

[0047] If the event triggering the access attempt is a request from upper layers to send mobile originated SMS over NAS (for example, the access attempt is classified as access category 6 (for mobile originated SMS) due to the request from upper layers to send mobile originated SMS over NAS), and the UE is registered to the network via both 3GPP access and non-3GPP access, the UE may transmit the UL NAS TRANSPORT message via the non-3GPP access if available.

[0048] Otherwise, if still needed, a UE initiated NAS transfer procedure is started when lower layers indicate that the barring for the access class associated with the access attempt is relieved.

[0049] In some embodiments, certain aspects of the above-mentioned technology may be implemented by one or more processors of a processing system that executes software. The software includes one or more sets of executable instructions stored or otherwise tangibly embodied on a non-transitory computer-readable storage medium. The software may include instructions and certain data that manipulate one or more processors when executed by one or more processors to perform one or more aspects of the above-mentioned technology. A non-transitory computer-readable storage medium may include, for example, a magnetic disk or optical disk storage device, a solid-state storage device such as a flash memory, a cache, a random access memory (RAM), or other one or more non-volatile memory devices, etc. The executable instructions stored on a non-transitory computer-readable storage medium may be in the form of source code, assembly language code, object code, or other instruction formats that are interpreted or otherwise executable by one or more processors.

[0050] Computer-readable storage media may include any storage media or combination of storage media that can be accessed by a computer system during use to provide instructions and / or data to the computer system. Such storage media may include, but are not limited to, optical media (e.g., compact discs (CDs), digital versatile discs (DVDs), Blu-ray discs), magnetic media (e.g., floppy disks, tapes, or magnetic hard disks), volatile memory (e.g., random access memory (RAM) or cache), non-volatile memory (e.g., read-only memory (ROM) or flash memory), or micro-electromechanical system (MEMS)-based storage media. Computer-readable storage media may be embedded in a computing system (e.g., system RAM or ROM), fixedly attached to a computing system (e.g., a magnetic hard drive), removably attached to a computing system (e.g., an optical disc or flash memory based on a universal serial bus (USB)), or connected to a computer system via a wired or wireless network (e.g., a network accessible storage (NAS)).

[0051] It should be noted that not all activities or elements described above in the general description are required, parts of a specific activity or device may not be required, and one or more other activities may be performed, or elements other than those described may be included. Furthermore, the order in which the activities are listed is not necessarily the order in which they are performed. Moreover, the concepts have been described with reference to specific embodiments. However, those of ordinary skill in the art will appreciate that various modifications and changes may be made without departing from the scope of the present disclosure as set forth in the appended claims. Therefore, the present specification and drawings are to be regarded as illustrative rather than restrictive, and all such modifications are intended to be included within the scope of the present disclosure.

[0052] Benefits, other advantages, and solutions to problems have been described above with respect to specific embodiments. However, benefits, advantages, solutions to problems, and any features that may make any benefit, advantage, or solution appear or become more significant should not be interpreted as being key, required, or essential features of any or all claims. In addition, the specific embodiments disclosed above are merely illustrative, as the disclosed subject matter may be modified and practiced in different but equivalent ways that are obvious to those skilled in the art having the benefit of the teachings herein. Except as described in the appended claims, it is not intended to limit the details of construction or design shown herein. Therefore, it is understood that the specific embodiments disclosed above may be changed or modified, and all such changes are considered to be within the scope of the disclosed subject matter. Therefore, the protection sought herein is as set forth in the following claims.

Claims

1. A device for performing access control, the device comprising: at least one processor; and at least one memory, the at least one memory comprising computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: determining that a lower layer indicates prohibition of a non-initial access attempt to transmit an uplink non-access stratum transmission message to the network via a 3GPP access, In response to determining that the event triggering the non-initial access attempt was a request to send a mobile originated SMS over non-access stratum and the device is registered with the network via both 3GPP access and non-3GPP access, transmitting the uplink non-access stratum transport message via the non-3GPP access.

2. The apparatus of claim 1 , wherein the computer program code is configured to, with the at least one processor, cause the apparatus to: Additionally, when the lower layer indicates that the prohibition is relieved, a mobile initiated non-access stratum transmission procedure is initiated.

3. The apparatus of claim 1 , wherein the computer program code is configured to, with the at least one processor, cause the apparatus to determine that the lower layer indicates that the access attempt is prohibited, and to determine whether the event triggering the access attempt is the request from an upper layer to send the mobile originated SMS over non-access stratum at the non-access stratum.

4. The apparatus of claim 1, wherein the computer program code is configured to, with the at least one processor, cause the apparatus to determine that the lower layer indicates that the access attempt via 3GPP access is prohibited.

5. The apparatus of claim 1, wherein the computer program code is configured to, with the at least one processor, cause the apparatus to: transmit the uplink non-access stratum transmission message if it is determined that the lower layer indicates that the access attempt is prohibited.

6. The apparatus of claim 1, wherein the uplink non-access stratum transport message carries the mobile originated SMS and is transmitted via a non-3GPP access.

7. The apparatus of claim 1, wherein the computer program code is configured to, with the at least one processor, cause the apparatus to: A determination is made as to whether the device is registered with the network via both a 3GPP access and a non-3GPP access.

8. The apparatus of claim 1, wherein the computer program code is further configured to, with the at least one processor, cause the apparatus to: if non-3GPP access is available, transmitting the uplink non-access stratum transport message carrying the mobile originated SMS via the non-3GPP access, Additionally, if the lower layer indicates that prohibition is relieved, the uplink non-access stratum transport message carrying the mobile originated SMS is transported via a 3GPP access transport.

9. A method for performing access control, the method comprising: determining in the device that a lower layer indicates that a non-initial access attempt to transmit an uplink non-access stratum transmission message to a network via a 3GPP access is prohibited, In response to determining that the event triggering the access attempt was a request to send a mobile originated SMS over non-access stratum and the device is registered with the network via both 3GPP access and non-3GPP access, transmitting the uplink non-access stratum transport message in the device via the non-3GPP access.

10. The method of claim 9, further comprising: Additionally, when the lower layer indicates that the prohibition is relieved, a mobile initiated non-access stratum transmission procedure is initiated.

11. The method of claim 9, wherein the determining that the lower layer indicates that the access attempt is prohibited is performed at a non-access stratum.

12. The method of claim 9, wherein the determining that the lower layer indicates that the access attempt is prohibited comprises: A determination is made that the lower layers indicate that the access attempt via 3GPP access is prohibited.

13. The method of claim 9, wherein the uplink non-access stratum transport message carries the mobile originated SMS and is transmitted via a non-3GPP access.

14. The method of claim 9, further comprising: A determination is made as to whether the device is registered with the network via both a 3GPP access and a non-3GPP access.

15. The method of claim 9, further comprising: if non-3GPP access is available, transmitting the uplink non-access stratum transport message carrying the mobile originated SMS via the non-3GPP access, Additionally, if the lower layer indicates that prohibition is relieved, the uplink non-access stratum transport message carrying the mobile originated SMS is transported via a 3GPP access transport.

Images