JP2016027712A - Network controlled extended access barring for multi-service user devices - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a technique of determining whether network access associated with a data use device has been granted.SOLUTION: A method includes determining whether it is a mixed access class, and determining whether extended access barring (EAB) network access has been granted. The method also includes barring EAB network access for a data use device if EAB access has not been granted for the data use device to access a network. The method further includes granting network access for all services for the data use device if the EAB access has been granted for the data use device to access the network.SELECTED DRAWING: Figure 6

Description

  Data traffic in mobile communication networks is gradually increasing for several reasons. One aspect that can result in a significant amount of data traffic in the network is the increasing amount of data-centric machine-to-machine (M2M) devices connected to mobile communication systems. Examples of such M2M devices are in the fields of transportation, health care, manufacturing, retail, etc., for example.

  In one implementation, the computer-implemented method includes a network access class associated with the data using device that is an extended access class (EAB) network access protocol for at least one service and at least one other. Determining whether the access class is a mixed access class that includes an EAB network access protocol for the service, and determining whether EAB access is granted to the data consuming device for accessing the network; Restricting EAB network access for data-using devices when EAB access is not permitted to the data-using device for accessing the network; Granting network access for all services for the data using device if the data using device for accessing the network is allowed EAB access.

  In addition, the computer-implemented method may further include updating the network access class associated with the data usage device when a new network access class is accepted.

  In addition, determining whether the network access class associated with the data consuming device is a mixed access class is based on a subscriber identity module (SIM) associated with the data consuming device. It may further include determining a network access class.

  In addition, at least one service may be a time-critical service and at least one other application may be a non-time-critical service.

  In addition, the computer-implemented method may further include coordinating a separate packet data protocol (PDP) context for each network access protocol.

  In addition, the computer-implemented method may further include assigning a separate random access channel to a service that conforms to the EAB network access protocol.

  In addition, the network may be a third generation partnership project (3GPP) network.

  According to another implementation, a data using device includes a memory that stores a plurality of instructions and a request for network access based on at least one service associated with the data using device by executing the instructions in the memory. At least one service in response to the request for identification of the network access class associated with the data usage device and accepting the request for identification of the network access class associated with the data usage device Providing an identification of a mixed access class associated with the device, including a non-EAB network access protocol for and an EAB network access protocol for at least one other service, and A processor configured to receive a network access based on one service even without, may include.

  In addition, the data using device may be one of a wireless phone, a cellular phone, a smartphone, a personal digital assistant (PDA), a laptop computer, a personal computer, or a tablet computer.

  According to another implementation, the device executes a memory in which multiple instructions are stored and the instructions in the memory so that the network access class associated with the data-using device can be used for time-critical services. Determine if it is a mixed access class that allows full network access and network access based on machine type communication for non-time critical services, and whether access is allowed for machine type communication in the network Network for machine type communication by data-using device if network access for machine type communication is not allowed for the network And a processor configured to allow network access for all services for data consuming devices when network access is permitted for machine type communication for the network. You may go out.

  In addition, the processor is further configured to update the network access class associated with the data using device when a new network access class is accepted.

  In addition, when determining whether the network access class associated with the data consuming device is a mixed access class, the processor is responsive to the network access class based on the subscriber identity module associated with the data consuming device. Further configured to determine a class.

  In addition, the processor is further configured to coordinate a separate packet data protocol (PDP) context for each network access protocol.

  In addition, the processor is further configured to allocate a separate random access channel for services that accept network access based on machine type communication for non-time critical services.

  In addition, the network is a third generation partnership project (3GPP) network.

  In another implementation, the computer-readable medium includes computer-executable instructions, wherein the computer-executable instructions include instructions for determining whether the network access class associated with the data usage device is a mixed access class. May be included. The mixed access class includes a non-extended access control (EAB) network access protocol for at least one service and an EAB network access protocol for at least one other service. The computer executable instructions may include instructions for determining whether EAB access is allowed for the network. Computer-executable instructions also include instructions for regulating EAB network access for data-using devices when EAB access is not allowed for the network, and all services when EAB access is allowed for the network. Instructions may be included to allow network access for.

  In addition, when determining whether the network access class associated with the data using device is a mixed access class, the computer readable instructions are based on a subscriber identity module (SIM) associated with the data using device. Instructions for determining the network access class.

  In addition, the computer readable instructions include instructions for updating the network access class associated with the data usage device based on the SIM associated with the data usage device when a new network access class is accepted. Including.

  In addition, the computer readable instructions further include instructions for coordinating a separate packet data protocol (PDP) context for each network access protocol.

  In addition, the computer readable instructions further include instructions for allocating a separate random access channel for services according to the EAB network access protocol.

  The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate one or more embodiments described herein and, in conjunction with the description, explain the embodiments. Is.

FIG. 1 illustrates an example long term evolution (LTE) network in which the systems and / or methods described herein may be implemented. FIG. 2 is a block diagram illustrating an identifier associated with a data using device and an associated network access protocol. It is a block diagram of a network access control device. FIG. 4 is a diagram illustrating an exemplary configuration of one or more of the components of FIGS. FIG. 3 is an illustration of an example user device. FIG. 5 is a flow diagram of an exemplary process for extended access control through network control of a user device.

  The following detailed description refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements. Also, the following detailed description is merely for purposes of illustration and description and is not intended to limit the claimed invention.

  Embodiments described herein control access of a data usage device (eg, a consumer terminal) to a network based on a control plane that includes an extended access restriction (EAB) network access class and a non-EAB network access class. The present invention relates to a device, a method, and a system for providing a connected terminal. The same network terminal may allow non-time critical background activity to follow machine type communication while allowing time critical activity at the data consuming device, reducing the risk of network congestion.

  FIG. 1 is a diagram of an exemplary LTE network 100. As shown, the LTE network 100 includes several data using devices 102, an access network (AN) 110, an evolved packet core (EPC) network 120, and the Internet or dedicated packet data. A packet data network (PDN) 140 such as a network is included.

  The data using device 102 includes several user equipment (UE) devices 104-1, 104-2 and 104-x (collectively or individually referred to as UEs 104) and several machine-to-machine (M2M ) Devices 106-1, 106-2 and 106-x (collectively referred to as M2M 106 or individually referred to as M2N 106). As described herein, data usage device 102 may communicate data based on a particular network access class associated with a particular data usage device 102 in network 100.

  The UE 104 may be a radiotelephone, a personal communication system (PCS) terminal (eg, a cellular radiotelephone can be combined with data processing and data communication functions), a wireless telephone, a cellular telephone, a smartphone. A personal digital assistant (PDA) (which may include, for example, a wireless phone, pager, Internet / intranet access, etc.), laptop computer, personal computer, tablet computer, or other type of computing or communication device. In an exemplary implementation, UE 104 may include any device that can communicate on AN 110, EPC network 120, and / or PDN 140. The UE 104 may operate according to one or more versions of the LTE communication standard, for example. As described herein, the UE 104 determines the network access class to which a particular network access request belongs and is therefore based on a control plane that includes extended access control (EAB) and non-EAB for the particular request. An indicator may be included (by a network terminal in network 100) that may be used to accept access to network 100.

  M2M 106 is a machine-to-machine communication (ie machine type as described in machine type communication (MTC)) (eg 3rd Generation Partnership Project (3GPP) technical report (TR) 37.868). A device that communicates with the network 100 using communication)) may be included. One fundamental aspect of communication between M2M devices such as the M2M106 described herein is that communication is typically done without human intervention, such as low latency in connection setup for M2M connections. The requirement is relaxed. The M2M 106 captures data regarding one or more events or conditions (such as temperature, inventory level, fuel level, etc.) and uses the data over the network 100 for application (machine readable instructions) at another device (eg, a network terminal, etc.). May be a device (such as a sensor or meter) that includes the ability to relay to the other device, and the data is restocked with information that can be used to manage the M2M 106 or conditions associated with the M2M 106 (eg, restocked) Item, temperature to be adjusted, etc.). In an exemplary implementation, M2M 106 may include any device that can communicate using machine-to-machine communication on AN 110, EPC network 120, and / or PDN 140. The M2M 106 may operate according to one or more versions of the LTE communication standard, for example.

  The AN 110 includes a communication network that connects a subscriber (eg, UE 104) to a service provider. In one example, AN 110 may include a Wi-Fi network or other access network (eg, in addition to E-UTRAN 112). The AN 106 is an evolved universal terrestrial radio access network (E-UTRAN) 112 and several eNodeB (eNB) 114-1, 114-2 or enhanced node base stations (collectively or individually). eNB 114). Each eNB 114 may include a corresponding multicast coordination entity (MCE) 116 (each MCE 116-1, 116-2 and 116-x, collectively or individually referred to as MCE 116).

  E-UTRAN 112 includes a radio access network that may support high data rates, packet optimization, high capacity, coverage, and the like. The E-UTRAN 112 may include a plurality of eNBs 14.

  The eNB 114 includes a network device that operates according to one or more versions of the LTE communication standard. For example, the eNB 114 responds to a request from the data using device 102 or sends information regarding the data using device 102 to a mobility management entity (MME) 122 and / or a serving gateway (SGW) 126 in the EPC 120. Can be configured to forward or set up a tunneling session with other devices (eg, SGW 126). The eNB 114 is a base station in the network 100 and may include control plane connections to other network elements. The eNB 114 may include an MCE 116.

  The MCE 116 is a multi-cell multimedia broadcast multicast service (MBMS) using MBSFN operation by all eNBs 114 in a multicast / broadcast single frequency network (MBSFN) area. May allocate radio resources to be used. The MBSFN area is a specific area where multiple cells transmit the same content using a single frequency network. Each eNB 114 may have an associated MCE 116, and the MCE 116 may be incorporated into the eNB 114. Alternatively, the MCE 116 may be part of another network element. Each eNB 114 is served by a single MCE 116 if the MCE 116 is part of another network element. In addition to time / frequency radio resource allocation, the MCE 116 may determine or implement further details of the radio configuration such as modulation and coding scheme (MCS). The MCE may also be involved in MBMS session control signaling.

  The EPC 120 may include a 3GPP LTE wireless communication standard core network architecture. The EPC 120 includes an MME 122, a home subscriber server (HSS) / authentication, authorization, and accounting (AAA) server 124, a serving gateway (SGW) 126, a policy and charging rule function (PCRF). : A policy and charging rules function (128) device, a PDN gateway (PGW) 130, a broadcast multicast service center (BMSC) 132, and an MBMS gateway (MBMS GW) 134 may be included. . The devices / networks of the network 100 may be connected to each other via a wired connection and / or a wireless connection.

  The MME 122 is responsible for idle mode tracking and paging procedures (eg, including retransmissions) for the data using device 102. For example, the MME 122 maintains information regarding the current state (eg, power state, location, etc.) of the data using device 102. The MME 122 is also involved in the bearer activation / deactivation process (eg, for the UE 104) and operates to select a particular SGW 126 for the data using device 102 during initial connection and during LTE handover. In addition, the MME 122 authenticates the data using device 102 (eg, by interaction with the HSS 124). Non-access stratum (NAS) signaling terminates at the MME 122, which generates a temporary identification and allocates it to the data using device 102 (eg, UE 104).

  Further, the MME 122 can check the authorization of the data usage device 102 to connect to the service provider's public land mobile network (PLMN) and for the data usage device 102 (eg, a particular UE 104). Enforce roaming restrictions. The MME 122 may be a termination point in the EPC network 120 for NAS signaling encryption / integrity protection and may handle security key management. The MME 122 is an S3 interface that terminates at the MME 122 (ie, an interface that provides a connection between the serving general packet radio service (GPRS) support node (SGSN) and the MME 122 in the LTE network). ) Can be used to provide a control plane function for mobility between LTE and second generation mobile communications or third mobile generation communications (2G / 3G) 3GPP access networks. The MME 122 may also terminate the S6a interface (allowing transmission of subscription and authentication data) to the HSS 124 for the roaming UE 104.

  The HSS / AAA 124 is configured to include a master user database that supports devices on the PDN 140 that handle calls, such as proxy devices, session border controllers, and the like. The HSS / AAA 124 may include subscription related information (eg, subscriber profile), may perform user authentication and authorization based on requests accepted from the MME 122, and provide information regarding subscriber location and IP information. obtain.

  The SGW 126 routes and forwards user data packets, acts as a radio mobility anchor for the user plane during inter-eNB handover, and mobility between LTE and other 3GPP technologies (“Inter-3GPP mobility” Also serves as a wireless anchor for. As shown, the SGW 126 is connected to the eNB 114 to provide a radio layer mobility control plane. In addition, the SGW 126 manages and stores contexts associated with the UE 104 (eg, IP bearer service parameters, network internal routing information, etc.).

  The PCRF 128 provides policy control decision and flow-based charging control functions. The PCRF 128 may provide network control for service data flow detection, gate control, quality of service (QoS), flow-based charging, and the like. The PCRF 128 may determine how a particular service data flow should be handled and may ensure that user plane traffic mapping and treatment matches the user's subscription profile.

  The PGW 130 processes a gateway, router, switch, firewall, network interface controller (NIC), hub, bridge, proxy server, optical add / drop multiplexer (OADM), or data. And / or some other type of device to transfer. The PGW 130 provides a connection of the data usage device 102 to an external packet data network (eg, PDN 140) by being a traffic exit / entry point for the data usage device 102. As briefly described above, the data using device 102 connects to the PGW 130 via one or more tunnels established between the eNB 114 and the PGW 130, such as one or more GPRS Tunneling Protocol (GTP) tunnels. obtain. Data using device 102 may connect to multiple PGWs simultaneously to access multiple PDNs. The PGW 130 may perform policy enforcement, per-user packet filtering, charging support, lawful intercept, and packet screening. The PGW 130 may also serve as an anchor for mobility between 3GPP technology and non-3GPP technology.

  The BMSC 132 may be a functional entity that manages the provision of multicast or broadcast services to the data consuming device 102, and possibly to associated end users as currently implemented in 2G and 3G MBMS architectures. . BMSC 132 may provide an entry point for content providers or other broadcast / multicast sources external to the network. BMSC 132 may perform authorization, scheduling, and security procedures that support multicast or broadcast services. For example, the BMSC 132 may provide authorization for terminals that request to activate MBMS services. BMSC 132 may schedule broadcast / multicast sessions. The BMSC 132 may also perform MBMS data integrity and confidentiality protection and issue MBMS session announcements.

  The BMSC 132 may support MBMS bearer signaling to set up and release context upon MBMS session establishment and termination. The BMSC 132 may also support user-related signaling, for example, for multicast session approval, or for user sessions that join or disconnect from the multicast session.

  The MBMS GW 134 may transmit / broadcast the MBMS packet to each eNB 114 that transmits the service (broadcast or multicast). The MBMS GW 134 may be a logical entity that exists between the BMSC 132 and the eNB 114 in the network 100. The MBMS GW 134 may be part of another network entity such as a router. The MBMS GW 134 may transfer MBMS user data to the eNB 114 using IP multicast. The MBMS GW 134 may perform MBMS session control signaling (eg, session start / stop) to the E-UTRAN 112 via the MME 122.

  The PDN 140 includes a network that provides data services (eg, by packet or any other Internet Protocol (IP) datagram). For example, the PDN 140 may include the Internet, an intranet, an asynchronous transfer mode (ATM) network, and the like.

  FIG. 1 shows three UEs 104, two M2M devices 106, AN110, EPC120, PDN140, E-UTRAN112, two eNB114, MME122, HSS124, SGW126, PCRF128, PGW130, BMSC132, and MBMS GW134 for simplicity. Has been. In practice, there may be more or fewer devices or components. For example, a typical network 100 includes millions of subscriber UEs 104, thousands of eNBs 114, hundreds of SGWs 126 and several PGWs 130 and MBMS GWs 134, which form a hierarchical access network substantially, In the access network, traffic is passed from the PDN 140 to the UE 104 via, for example, specific MBMS GW 134, PGW 130, SGW 126, and eNB 114.

  In the implementation described herein, based on a control plane that includes extended access control (EAB) and non-EAB, terminal controlled access of a data using device to a network, such as a network enabled using the 3GPP specification, is provided. Disclosed processes and methods are disclosed. Further, the functions described as being performed by any one device may be performed by any other device (or combination of devices) in network 100.

  FIG. 2 is a diagram illustrating NAS signaling based on a network access class for a data using device 102 in the network 100. As shown, each data usage device 102 has an associated identifier (non-EAB identifier 204, mixed access identifier 206, EAB identifier 208) that identifies the associated network access class for the data usage device 102. Can do. For example, each identifier may be included in a universal subscriber identity module (USIM) for each data using device 102. The presence and format of the non-access layer configuration file on the USIM may be as specified in 3GPP Technical Specification (TS) 31.102.

  The non-EAB identifier 204 may be included in one or more of the UEs 104 in the network 100, eg, the UE 104-1. The non-EAB identifier 204 may indicate that all network access requests from the associated UE 104 should be granted based on the non-EAB network access protocol 210 for all services requested by the UE 104. For example, UE 104 may request and receive network access for time critical services such as voice calls, web browsing, streaming services. In addition, UE 104 also uses non-EAB network access protocol 210 to request network access for non-time critical services where latency and other connection requirements are similar (and possibly identical) to M2M traffic. Can receive. Non-time critical services include data downloads for software updates (for operating system updates or installed program / application updates) or email synchronization, social networking, weather forecasting, cloud-based storage, etc. Activities such as automatic background updates and other services that are not time critical may be included. In some cases, non-time critical services can be repeatedly initiated by UE 104-1 without direct human intervention.

  The mixed access identifier 206 may be included in one or more of the UEs 104 in the network 100, eg, the UE 104-x. The mixed access identifier 206 allows several network access requests, such as time critical applications and / or activities, from a particular UE, in this example UE 104 -x, to be granted based on the non-EAB network access protocol 210. Can indicate what to do.

  However, the mixed access identifier 206 may also indicate that certain activities, such as non-time critical background activity at the UE 104 -x, should follow the EAB network access protocol 212. In other words, certain activities can be specified to follow machine type communication concepts for network access, which can significantly reduce the risk of network congestion. Activity according to the EAB network access protocol 212 may be temporarily regulated by the network 100. The mixed access identifier 206 classifies less time critical services to follow EAB signaling, while a signaling control device in the network 100 such as the MME 122 maintains a predetermined minimum quality of service for time critical services, while It may be possible to handle a greater amount of data-using device 102 using a busy network protocol (eg, a network connection protocol that requires confirmation before subsequent transmissions).

  An EAB identifier 208 may be included in each of the M2Ms 106. The EAB identifier 208 may indicate that the M2M 106 is classified into a network access class that conforms to the EAB network access protocol 212. A signaling device in network 100 may signal M2M 106 temporary restrictions based on EAB network access protocol 212. In addition, a separate random access channel (RACH) for devices following the EAB network access protocol 212 may be defined. The RACH is separate (and often more (e.g., more than) for data use device 102 according to EAB network access protocol 212 from data use device 102 according to non-EAB network access protocol 210 within network 100. It may provide a higher) access collision probability (due to low relative bandwidth allocation and / or transmission reliability requirements).

  MME 122 is for NAS signaling, NAS signaling security, idle mode UE reachability, tracking area list management, roaming, authorization, and initiation of EPS bearer establishment between SGW and PGW and between SGW and eNB Host the functionality of

  The MME 122 may also host functions for network access control. For example, data access for the data usage device 102 is associated when the data usage device 102 makes a network access request to the MME 122 or when the data usage device 102 is paged by the MME 122 to initiate a communication setup. Determined (granted or regulated) based on a given identifier (eg, for 3GPP access technology based on “NAS configuration” located on USIM card). The identifier may be configured as defined in TS31.102.

  The SGW 126 hosts functions for wireless mobility anchoring. The PGW 130 hosts functions for UE IP address allocation, packet filtering, IP mobility anchoring, and lawful intercept.

  FIG. 3 is a functional block diagram of the network access control device 300. The network access control device 300 may include a network access class identification module 302, a mixed access scheduling module 304, and an access scheduling module 306. Network access control device 300 may be incorporated into MME 122 or network access control device 300 may be implemented in conjunction with MME 122 or other devices in network 100.

  The network access class identification module 302 may determine whether a particular access class is applicable for the data usage device 102 based on the identifier associated with the data usage device 102. For example, the network access class identification module 302 may determine that only EAB is applicable for the data using device 102 (ie, M2M 106). The network access class identification module 302 may determine a different network access class for the UE 104, as described below in connection with FIG.

  The mixed access scheduling module 304 defines a specific network access protocol for applications and services associated with the data usage device 102 that includes the mixed access identifier 206, such as the UE 104-x described in connection with FIG. Can be identified. Mixed access scheduling module 304 may simultaneously include EAB and non-EAB membership for different associated applications and services (and may also follow non-EAB network access protocol 210 or EAB network access protocol 212). ). The mixed access scheduling module 304 also does not rely on the pre-defined identifier (eg, SIM information) as defined in TS 24.368 to configure the data using device 102 to a specific network access device. You may adjust to follow the protocol.

  FIG. 4 illustrates UE 104, M2M 106, one or more devices in AN 110, EPC 120, PDN 140, E-UTRAN 112, eNB 114, MME 122, HSS 124, SGW 126, PCRF 128, PGW 130, BMSC 132, described in FIGS. FIG. 6 is an illustration of exemplary components of a device 400 that may support the MBMS GW 134. Each of UE 104, access network 104, EPC 120, PDN 140, E-UTRAN 112, eNB 114, MME 122, HSS 124, SGW 126, PCRF 128, PGW 130, BMSC 132, and MBMS GW 134 may include one or more devices 400. As shown in FIG. 4, the device 400 may include a bus 410, a processor 420, a memory 430, an input device 440, an output device 450, and a communication interface 460.

  Bus 410 may allow communication between components of device 400. The processor 420 may include one or more processors or microprocessors that interpret and execute instructions. In other implementations, processor 420 may be implemented as one or more application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or the like. May be included.

  The memory 430 stores information and instructions for the processor 420 to execute, a random access memory (RAM) or another type of dynamic storage device, static information and instructions for the processor 420. Storing read only memory (ROM) or another type of static storage device and / or some other type of magnetic or optical recording medium and corresponding information and / or instructions May include a drive for.

  Input device 440 may include devices that allow an operator to enter information into device 400, such as a keyboard, keypad, mouse, pen, microphone, one or more biometric mechanisms, and the like. The output device 450 may include a device that outputs information to an operator, such as a display or a speaker.

  Communication interface 460 may include one or more transceivers that allow device 400 to communicate with other devices and / or systems. For example, the communication interface 460 may include a mechanism for communicating with other devices, such as other devices of the network 100.

  As described herein, device 400 may perform certain operations in response to processor 420 executing software instructions included in a computer-readable medium, such as memory 430. The computer readable medium may include a non-transitory memory device. A memory device may include space within a single physical memory device and may be distributed across multiple physical memory devices. Software instructions may be loaded into memory 430 from another computer-readable medium or from another device via communication interface 460. Software instructions included in memory 430 may cause processor 420 to perform the processes described herein. Alternatively, wiring circuits are used in place of or in combination with software instructions to implement the processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.

  Although exemplary components of the device 400 are shown in FIG. 4, in other implementations the device 400 has fewer components, different components, differently arranged components than those shown in FIG. Or additional components may be included. As an example, in some implementations, input device 440 and / or output device 450 may not be implemented by device 400. In these situations, device 400 may be a “headless” device that does not explicitly include an input device or an output device. Alternatively or additionally, one or more components of device 400 may perform one or more other tasks described as being performed by one or more other components of device 400. Good.

  FIG. 5 is a diagram of an exemplary user device 500, such as one or more of the UEs 104 shown in FIGS. As shown, user device 500 may include a speaker 504, a display 506, control keys 508, a keypad 510, and a microphone 512. User device 500 may include other components (not shown in FIG. 5) that assist in receiving, transmitting, and / or processing data. Furthermore, other configurations of the user device 500 are possible.

  Speaker 504 may provide audible information to a user of user device 500. Display 506 may include a display screen for providing visual information such as video images and photographs to the user, and may include a touch screen display for accepting input from the user. For example, the display 506 may provide information regarding incoming or outgoing calls, phone numbers, contact information, current time, voicemail, email, and the like. Display 506 may display a graphical user interface (not shown) that includes a list of available visual voicemails.

  Control key 508 may allow the user to interact with user device 500 to cause user device 500 to perform one or more operations such as interacting with a visual voicemail application. Control keys 508 may include soft keys that can perform the functions shown on display 506 directly above the keys. Keypad 510 may include a standard telephone keypad and may include additional keys to allow information input (eg, typing) to user device 500. Microphone 512 may receive audible information from the user.

  Device 500 may generate a request for network access based on at least one service associated with device 500. The device 500 receives a request for identification of a network access class associated with the device 500, and in response to a mixed access class (eg, based on a SIM (not shown)) associated with the device 500. Identification can be provided. The mixed access class includes a non-EAB network access protocol 210 for at least one service and an EAB network access protocol 212 for at least one other service for the device 500. Device 500 may receive network access based on a mixed access class and at least one service.

  FIG. 6 is a flow diagram of an exemplary process for determining network access as described herein. In one implementation, process 600 may be performed by network access control device 300. In another implementation, some or all of process 600 may be performed by another device or group of devices including or excluding network access control device 300.

  Process 600 may begin when network access control device 300 reads an identifier for the access class of data using device 102 (block 602). For example, when connected to the network, the data using device 102 may be a non-EAB network access if, for example, the data using device 102 is an EAB device that communicates using the EAB network access protocol 212 (ie, an EAB only access class). If it is a non-EAB device that communicates using protocol 210 (ie, non-EAB only access class), or mixed access class protocol, ie, EAB network access protocol 212 for one service, another service For a data using device 102 if it is a mixed access class device (ie, mixed access class) that communicates using a non-EAB network access protocol 210 To indicate a plurality of network access protocol associated, may signal a network access class associated with the data used device 102 to the network access control device 300. The network access control device 300 may receive information from the SIM card of the data usage device 102 that includes a network access class identifier for the data usage device 102.

  At block 604, if the network access protocol for the data using device 102 is the EAB network access protocol 212 (ie, the data using device 102 receives access based only on EAB) (block 602, EAB only). In particular, the network access control device 300 may determine whether EAB access for the data using device 102 is permitted. EAB access may be granted at predetermined intervals in the network 100 or based on the current or predicted network capacity or transaction volume in the network 100 (or a portion of the communication channel in the network 100 such as the RACH described above). In this case, the data using device 102 is an EAB-only device and is regarded as the M2M 106.

  If EAB access is not permitted (block 604, no), the network access control device 300 only emergency calls access to the network 100 (to / from the data use device 102) for the data use device 102. (Block 606). If EAB access is allowed (block 604, yes), the network access control device 300 may allow network access for the data usage device 102 for all services (block 608).

  At block 610, if the network access protocol for the data using device 102 is a mixed access class (block 602, mixed access class), the network access control device 300 may use EAB access for the data using device 102. Can be determined.

  If EAB access is not allowed (block 610, No), the network access control device 300 limits network access to the network 100 to only services associated with the data-using device 102 that is only non-EAB. (Ie, the network access control device 300 may regulate network access for EAB services) (block 612).

  If EAB access is allowed (block 610, yes), the network access control device 300 may allow network access of the data usage device 102 for all services (block 614). According to an example, the network access control device 300 may support a separate PDP context for EAB services.

  As shown in block 610 to block 614, the network access control device 300 may provide a classification of EAB and non-EAB services from the same data usage device 102 simultaneously. In these examples, the data using device 102 may follow general access restrictions for time critical high priority services associated with the network 100, while data connections from less time critical background services are , Initiated by the data usage device 102 only if EAB restriction allows, and follows the EAB random access procedure.

  At block 616, if the network access protocol for the data using device 102 is non-EAB only (block 602, non-EAB only), the network access control device 300 may use the data using device 102 for all services. Network access.

  At block 618, the network access control device 300 may change the SIM of the data using device 102 through device management as defined in TS 24.368.

  The above description of example implementations provides illustration and description, and is not intended to be exhaustive or to limit the embodiments described herein to only those disclosed. Absent. Modifications and variations are possible in light of the above teachings, and modifications and variations may be obtained by implementing these embodiments. For example, machine type communication may be allowed for an individual data usage device 102 or a subclass of data usage device 102 (eg, a medical facility on network 100) and all data usage using machine type communication. It may be authorized for device 102 (ie all EAB devices).

  For example, although a series of blocks are described with respect to FIG. 6, the order of the blocks may be changed in other implementations. Furthermore, independent blocks may be executed in parallel.

  It will be apparent that various aspects of the above description may be implemented as many different forms of software, firmware, and hardware in the implementations shown in the figures. The actual software code or dedicated control hardware used to implement these aspects does not limit the invention. Thus, the behavior and behavior of these aspects have been described without reference to specific software code. It will be appreciated that the software and control hardware can be designed to implement these aspects based on the description herein.

  The term “comprises / comprising” as used herein is understood to specify the presence of the described feature, integer, step or component, but one or more other features, integer, It should be emphasized that it does not exclude the presence or addition of steps, components, or groups thereof.

  Any element, operation, or instruction used in this application should not be construed as critical or essential to the implementation described herein unless so indicated. Also, as used herein, the article “a” is intended to include one or more items. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.

Claims (1)

A network access class associated with the data consuming device has a non-extended access control (non-EAB) network access protocol for at least one service and an EAB network access protocol for at least one other service. Determining by the network access control device whether the mixed access class includes,
In response to determining that the network access class associated with the data using device is the mixed access class, determining whether the data using device is allowed EAB network access to access the network. To do
Regulating EAB network access for the data using device in response to determining that the data using device is not allowed to access the network to access the network;
Permitting network access for all services for the data using device in response to determining that the data using device is allowed EAB network access to access the network;
A computer-implemented method comprising:

Images