User equipment, network equipment, and wireless communication method

Abstract

To provide user equipment, a network device, and a wireless communication method that operate as any of a plurality of categories corresponding to capabilities.SOLUTION: In a wireless communication system including a radio access network and user equipment (UE) 200, the UE 200 that operates as any of a plurality of categories corresponding to capabilities includes: an attachment processing unit 220 that performs attachment to a core network; an operation control unit 230 that causes the UE 200 to operate as a restricted category whose capabilities are more limited than a normal category; and a category notification unit 240 that notifies the core network of the category in which the UE 200 is operating during or after the attachment.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present invention relates to a user device, a network device, and a wireless communication method that operate as any one of a plurality of categories according to capabilities.

Background Art

[0002] The 3rd Generation Partnership Project (3GPP) has specified Long Term Evolution (LTE) and is specifying LTE-Advanced (hereinafter referred to as LTE including LTE-Advanced) for the purpose of further speeding up LTE. Further, in 3GPP, specifications of successor systems to LTE such as 5G New Radio (NR) are being studied.

[0003] Since Releases 13 and later of LTE, categories (UE categories) for inexpensive terminals (user devices) such as Internet of Things (IoT) modules have been defined. Specifically, categories M1 and M2 (hereinafter referred to as Cat.M) have been specified. This category is also called LTE-M or eMTC (enhanced Machine Type Communication).

[0004] Since the capabilities (such as communication speed) of a user device operating as Cat.M are limited compared to a user device (such as a smartphone) operating as a normal category (Cat.4 to 6, etc.), there is a demand to differentiate in terms of cost, etc. However, in the specifications of the conventional LTE Release (Release-14), the core network cannot determine whether the user device is operating as Cat.M (restricted category).

[0005] Therefore, it has been proposed that the wireless base station (eNB) determine the category of the user device based on the cell type in which the user device was located when it was attached to the core network (see Non-Patent Document 1). The eNB notifies the core network (specifically, the MME (Mobility Management Entity)) that the user device is operating as Cat.M. [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] “Identification of LTE-M (eMTC) traffic”, S2-182412, 3GPP TSG-SA2 Meeting #126, 3GPP, February 2018 [Overview of the project]

[0007] However, the method of notifying the core network of the category (Cat.M) via the eNB described above has the following problem. Specifically, if a user device has the capability for both Cat.M and normal categories, the user device can switch categories after attaching to the core network.

[0008] Therefore, when such a category switch occurs, the notification method described above has limitations in addressing the issue.

[0009] Therefore, the present invention has been made in view of these circumstances, and aims to provide a user device, a network device, and a wireless communication method that can reliably notify the core network or the like of the operating UE category, even when the UE has the capability of multiple UE categories, including Cat.M.

[0010] One aspect of the present invention is a user device (UE200) that operates as one of several categories according to its capabilities, comprising: an attachment processing unit (attachment processing unit 220) that performs attachment to a core network; an operation control unit (operation control unit 230) that operates the user device as a restricted category (Cat.M, LTE-M, eMTC) with more limited capabilities than a normal category; and a category notification unit (category notification unit 240) that notifies the core network of the category in which the user device is operating during or after the attachment.

[0011] One aspect of the present invention is a network device (e.g., MME300) that constitutes a core network, comprising: a category receiving unit (category receiving unit 301) that receives the category in which a user device (UE200) is operating from a user device that operates as one of a plurality of categories according to its capabilities; and a category transfer unit (category transfer unit 305) that transfers the category received by the category receiving unit to another network device (S-GW310) or a billing system.

[0012] One aspect of the present invention is a wireless communication method using a user device that operates as one of a plurality of categories according to its capabilities, comprising the steps of operating the user device as a restricted category with more limited capabilities than a normal category, and when attaching to a core network or after such attachment, the user device notifies the core network of the category in which the user device is operating. [Brief explanation of the drawing]

[0013] [Figure 1] Figure 1 is a schematic diagram of the overall configuration of the wireless communication system 10. [Figure 2] Figure 2 is a functional block diagram of the UE200. [Figure 3] Figure 3 shows the functional block diagrams of the MME300 and S-GW310. [Figure 4]Figure 4 is a functional block diagram of the P-GW320. [Figure 5] Figure 5 shows the notification sequence to the core network in the category in which the UE200 is operating. [Figure 6] Figure 6 shows a schematic example of a NAS message that the UE200 sends to the core network. [Figure 7] Figure 7 shows a schematic example of a message configuration that P-GW320 sends to OCS / OFCS400. [Figure 8] Figure 8 shows an example of the hardware configuration of UE200, MME300, S-GW310, and P-GW320. [Modes for carrying out the invention]

[0014] The embodiments will be described below with reference to the drawings. Note that identical or similar reference numerals are used to denote the same functions and components, and their descriptions will be omitted as appropriate.

[0015] (1) Overall outline of the wireless communication system Figure 1 is a schematic diagram of the overall configuration of the wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system that conforms to Long Term Evolution (LTE) and includes a wireless access network 20 and user equipment 200 (hereinafter referred to as UE200).

[0016] The radio access network 20 is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) as defined by 3GPP, and includes radio base stations 100 (hereinafter referred to as eNB100). The wireless communication system 10 is not necessarily limited to LTE (E-UTRAN). For example, the wireless access network 20 may be a wireless access network that includes a wireless base station that performs wireless communication with a UE200 (user equipment) defined as 5G.

[0017] The eNB 100 and the UE 200 perform wireless communication according to the LTE specifications. In particular, in this embodiment, the UE 200 operates as a category (UE category) for inexpensive terminals (user devices) such as Internet of Things (IoT) modules.

[0018] Specifically, the UE 200 can operate as categories M1, M2 (hereinafter, Cat.M). Note that Cat.M is also called LTE-M or eMTC (hereinafter, LTE-M or eMTC will also be used as appropriate in the expression).

[0019] Also, in this embodiment, the UE 200 can also operate as a normal UE category (normal category), specifically, Cat. 4 to 6, etc. That is, the UE 200 can operate as any one of a plurality of categories according to the capabilities of the user device including wireless capabilities (communication speed, etc.).

[0020] The eNB 100 can form a plurality of cells according to the UE category. In this embodiment, the eNB 100 forms a cell C1 for the normal category (Cat. 4 to 6, etc.) and a cell C2 for Cat.M1.

[0021] A Mobility Management Entity 300 (hereinafter, MME 300) is connected to the radio access network 20. The MME 300 houses the eNB 100 and provides mobility control for the UE 200, etc.

[0022] A Serving Gateway 310 (hereinafter, S-GW 310) is connected to the MME 300. Also, a Packet Data Network Gateway 320 (hereinafter, P-GW 320) is connected to the S-GW 310. The MME 300, S-GW 310, and P-GW 320 constitute the core network.

[0023] The S-GW310 is responsible for forwarding user data packets and other data for the UE200. The P-GW320 is located at the connection point to the external network, the Packet Data Network (PDN), and is responsible for assigning IP addresses for the UE200 and forwarding packets to the S-GW310.

[0024] The Online Charging System / Offline Charging System 400 (hereinafter referred to as OCS / OFCS400) performs billing processing associated with the provision of communication services to the UE200. The OCS / OFCS400 acquires the communication status of the UE200 and performs billing processing according to the service content. In this embodiment, the OCS / OFCS400 constitutes a billing system.

[0025] (2) Functional block configuration of the wireless communication system Next, the functional block configuration of the wireless communication system 10 will be described. Specifically, the functional block configurations of UE200, MME300, S-GW310, and P-GW320 will be described. Note that only the parts related to the features of this embodiment will be described below. Therefore, it goes without saying that the device also includes other functional blocks that are not directly related to the features of this embodiment.

[0026] (2.1)UE200 Figure 2 is a functional block diagram of the UE200. As shown in Figure 2, the UE200 comprises a wireless communication unit 210, an attachment processing unit 220, an operation control unit 230, and a category notification unit 240.

[0027] The wireless communication unit 210 performs wireless communication in accordance with the LTE method. Specifically, the wireless communication unit 210 transmits and receives wireless signals in accordance with the LTE method to and from the eNB100.

[0028] The attachment processing unit 220 performs the attachment to the core network. Specifically, the attachment processing unit 220 performs the attachment process to the core network by sending an Attach request to the MME 300. The attachment processing unit 220 also receives an Attach accept from the core network side, indicating that the Attach request has been received.

[0029] Attach request and Attach accept are types of Non-Access Stratum (NAS) messages, as defined in 3GPP TS24.301.

[0030] The motion control unit 230 controls the operation of the UE200. In particular, in this embodiment, the motion control unit 230 controls which UE category the UE200 operates as.

[0031] Specifically, the motion control unit 230 can operate the UE200 as a Cat.M1 (restricted category), which has more limited capabilities than the normal categories (such as Cat. 4 to 6). Of course, the motion control unit 230 can also operate the UE200 in any of the Cat. 4 to 6 UE categories.

[0032] The operation control unit 230 can switch the category of UE200 between the normal category and the restricted category. However, UE200 may be a user device dedicated to Cat.M and not compatible with the normal category.

[0033] The category notification unit 240 notifies the core network of the category of the UE200. Specifically, the category notification unit 240 notifies the core network of the category in which the UE200 is operating.

[0034] As described above, the UE200 can operate in one of several categories (normal category or restricted category). The category notification unit 240 notifies the core network of the UE category in which the UE200 is currently operating, based on the control result from the operation control unit 230.

[0035] The category notification unit 240 can notify the core network of the category in which the UE200 is operating when the attachment processing unit 220 attaches to the core network. Furthermore, the category notification unit 240 can also notify the core network of the category in which the UE200 is operating at that time after the attachment.

[0036] Specifically, the category notification unit 240 can notify the core network of the category in which the UE200 is operating when the category of the UE200 is switched by the operation control unit 230.

[0037] Alternatively, the category notification unit 240 may notify the core network of the category in which the UE200 is operating, i.e., Cat.M1, if the UE200 is located in a cell for Cat.M1 (cell C2).

[0038] The category notification unit 240 notifies the MME300 of the UE category in which the UE200 is operating using NAS messages. If the UE200 is attached to the core network, an Attach request can be used. After attachment, depending on the timing of the UE200's category switching by the operation control unit 230, a Service request (see TS24.301 Chapter 8.2.25), Tracking area update complete (see TS24.301 Chapter 8.2.27), etc., can be used. Alternatively, a new NAS message notifying the UE category in which the UE200 is operating may be used.

[0039] Figure 6 shows a schematic example of a NAS message that the UE200 sends to the core network.

[0040] As shown in Figure 6, the NAS message M1 contains a UE identifier that uniquely identifies the UE200 (e.g., EPS mobile identity) and information about the category in which the UE200 is operating (Cat.M1). Of course, in reality, message M1 contains many more elements (for example, for an Attach request, see 3GPP TS24.301 Chapter 8.2.4).

[0041] (2.2) MME300 and S-GW310 Figure 3 is a functional block diagram of the MME300 and S-GW310. In other words, the MME300 and S-GW310 have similar functional block configurations with respect to the characteristic parts in this embodiment. The following explanation will use the MME300 as an example.

[0042] As shown in Figure 3, the MME300 includes a category receiving unit 301, a session communication unit 303, a category transfer unit 305, and a priority processing unit 307.

[0043] The category receiver 301 receives the category in which the UE200 is operating from the UE200. Specifically, the category receiver 301 obtains the category information (see Figure 6) contained in the NAS message sent from the UE200.

[0044] The session communication unit 303 establishes a non-access layer (NAS) session necessary for communication with the UE200 and performs communication through that session. The session communication unit 303 also establishes a GTP (GPRS Tunneling Protocol) session necessary for communication with the S-GW310 and performs communication through that session.

[0045] The category transfer unit 305 transfers the category of the UE200 received by the category receiving unit 301 to the S-GW310 (another network device). Specifically, the category transfer unit 305 transfers the category of the UE200 to the S-GW310 via the GTP session established by the session communication unit 303. The structure of the message forwarded to the S-GW310 by the category transfer unit 305 is generally the same as the NAS message (message M1) shown in Figure 6.

[0046] The priority processing unit 307 performs priority processing for the UE200. For example, if the category in which the UE200 is operating is Cat.M1, the priority processing unit 307 can perform packet forwarding for the UE200 with a higher priority than user devices in the normal category.

[0047] Alternatively, if the category in which the UE200 is operating is Cat.M1, the priority processing unit 307 can perform packet forwarding for the UE200 with a lower priority than user devices in the normal category.

[0048] In the case of S-GW310, the session communication unit 303 establishes a GTP session with MME300 and P-GW320, and the category transfer unit 305 transfers the category of UE200 to P-GW320.

[0049] (2.3) P-GW320 Figure 4 is a functional block diagram of the P-GW320. As shown in Figure 4, the P-GW320 includes a category receiving unit 321, a session communication unit 323, a priority processing unit 325, and a detail information transmission unit 327.

[0050] The category receiver 321 receives the category in which the UE200 is operating from the S-GW310. Specifically, the category receiver 321 obtains the category information contained in the message sent from the S-GW310 via the GTP session.

[0051] The session communication unit 323 establishes a GTP session with the S-GW310. The session communication unit 323 also establishes a GTP session necessary for communication with the OCS / OFCS400. Alternatively, the session communication unit 323 may establish a File Transfer Protocol (FTP) session with the OCS / OFCS400.

[0052] The priority processing unit 325 performs priority processing for the UE200. The priority processing unit 325 provides the same functionality as the priority processing unit 307 of the MME300 (S-GW310).

[0053] The details information transmission unit 327 transmits details information to the OCS / OFCS400. The details information shows the usage details of the communication service by the UE200 (communication service type (including Cat.M or normal category type), communication time, packet volume, etc.).

[0054] Figure 7 shows a schematic example of a message that P-GW320 sends to OCS / OFCS400.

[0055] As shown in Figure 7, the message M2 transmitted via the GTP session (or FTP session) includes a UE identifier that uniquely identifies the UE200 (e.g., EPS mobile identity), detail information, and information about the category in which the UE200 is operating (Cat.M1).

[0056] Upon receiving message M2, the OCS / OFCS400 uses the information in that category to perform billing processing based on the usage status of the communication service by the UE200.

[0057] (3) Operation of the wireless communication system Next, we will describe the operation of the wireless communication system 10. Specifically, we will describe the notification operation to the core network of the category in which the UE200 is operating.

[0058] Figure 5 shows the notification sequence to the core network in the category in which the UE200 is operating. As shown in Figure 5, the eNB100 and UE200 exchange radio information for the cell in which the UE200 is located (S10).

[0059] Here, we assume that UE200 is located in a Cat.M1 cell (cell C2). eNB100 and UE200 secure wireless resources corresponding to Cat.M1 and establish a wireless bearer between eNB100 and UE200. This enables wireless communication between eNB100 and UE200.

[0060] As UE200 enters a Cat.M1 cell (cell C2), its category (UE category) is set to Cat.M1 (S20). Note that in Figure 5, "LTE-M" is used to indicate that other restricted categories (such as Cat.M2) may also be included.

[0061] The UE200 sends a NAS message (see Figure 6) to the MME300 (S30). As mentioned above, when attaching to the core network, the UE200 sends an Attach request to the MME300. The Attach request includes information about the category in which the UE200 is operating (LTE-M).

[0062] Furthermore, the UE200 may send NAS messages to the MME300 after attaching to the core network. Such NAS messages include, as mentioned above, Service request and Tracking area update complete, depending on the UE200's category switching timing.

[0063] The MME300 forwards the relevant category (LTE-M) contained in the NAS message received from the UE200 to the S-GW310 (S40). Specifically, the MME300 forwards the message containing that category to the S-GW310 via the GTP session.

[0064] Furthermore, the MME300 may perform priority processing for the UE200 based on the received category. Prioritization processing includes, as described above, increasing or decreasing the priority of packet forwarding to the UE200.

[0065] Similarly, S-GW310 forwards the category (LTE-M) contained in the message received from MME300 to P-GW320 (S50). Specifically, S-GW310 forwards the message containing the category to P-GW320 via the GTP session. S-GW310 may also perform priority processing for UE200 based on the received category.

[0066] P-GW320 transmits the details information of UE200 to OCS / OFCS400 (S60). Specifically, P-GW320 adds the relevant category (LTE-M) contained in the message forwarded from S-GW310 to the details information.

[0067] The P-GW320 sends a message (see Figure 7) containing the category and detail information to the OCS / OFCS400. The P-GW320 may also perform priority processing for the UE200 based on the received category.

[0068] The OCS / OFCS400 uses the information for that category to perform billing processing based on the usage of communication services by the UE200. In other words, the OCS / OFCS400 can recognize which category the UE200 is operating under in near real time, and can apply specific billing plans for that category (LTE-M).

[0069] (4) Action and Effects According to the embodiment described above, the following effects can be obtained. Specifically, the UE200 notifies the core network of the category (LTE-M) in which the UE200 is operating. In particular, the UE200 can notify the core network of the category in which the UE200 is operating at that time, not only when attaching to the core network, but also after attachment.

[0070] Therefore, even if the UE200's category is switched after it is attached to the core network, the core network can be reliably notified of the category in which the UE200 is operating after the switch.

[0071] Such an issue can occur when the UE200 is capable of operating in any of multiple categories, but even in such cases, the UE200 can reliably notify the core network of the category in which it is operating.

[0072] Furthermore, the MME300, S-GW310, and P-GW320, which constitute the core network, can sequentially forward information indicating the category and notify the OCS / OFCS400 of that category.

[0073] In other words, according to the wireless communication system 10, even if the UE200 has the capability for multiple UE categories, including Cat.M (LTE-M, eMTC), the UE200 can reliably notify the core network of the UE category it is currently operating in. Furthermore, the core network can reliably notify the OCS / OFCS400 of that UE category.

[0074] Furthermore, OCS / OFCS400 can apply category-specific billing policies based on the information of the category. This allows for differentiation of billing policies between user devices operating as a standard category and user devices operating as Cat.M (LTE-M, eMTC).

[0075] In this embodiment, when the UE200's category is switched, it can notify the core network of the category in which the UE200 is operating. Therefore, the core network and OCS / OFCS400 can recognize which category the UE200 is operating in near real-time. This allows for granular differentiation of services and billing policies based on the category in which the UE200 is currently operating.

[0076] In this embodiment, when a UE200 is located in a cell for Cat.M1 (cell C2), it can notify the core network of the category (Cat.M1) in which the previous UE200 was operating. Therefore, even when the UE200 attaches to the core network, or when the category is switched after attachment, the category in which the UE200 is operating can be detected using a common scheme. This simplifies the implementation of the UE200.

[0077] In this embodiment, the UE200 uses NAS messages to notify the core network of the UE category in which it is operating. Therefore, it is possible to notify the core network of the category in which the UE200 is operating while utilizing existing NAS messages. This simplifies the implementation of the UE200.

[0078] (5) Other embodiments Although the present invention has been described above in accordance with the embodiments, it will be obvious to those skilled in the art that the present invention is not limited to these descriptions and that various modifications and improvements are possible.

[0079] In the embodiment described above, the UE200 sends a NAS message containing the category in which the UE200 is operating to the MME300, and the MME300, S-GW310, and P-GW320 sequentially forward the category. However, depending on the type of message, the UE200 may send the message containing the category directly to the S-GW310 or P-GW320 instead of the MME300.

[0080] In the embodiment described above, the P-GW320 established a GTP or FTP session with the OCS / OFCS400, but the session established between the P-GW320 and the OCS / OFCS400 is not limited to GTP or FTP. In other words, any session other than GTP or FTP is acceptable as long as it is possible to send message M2 (see Figure 7) containing UE identifier, detail information, and category information.

[0081] In the embodiments described above, Cat.M (LTE-M, eMTC) was used as an example, but the definition is not limited to these categories, as long as it is an IoT category different from the usual categories (such as Cat. 4-6). For example, it could be an NB (Narrow Band)-IoT category.

[0082] Furthermore, the block diagrams (Figures 2-4) used in the description of the embodiments above show functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Also, the means of realizing each functional block are not particularly limited. That is, each functional block may be realized by one device that is physically and / or logically coupled, or by two or more physically and / or logically separated devices that are directly and / or indirectly connected (for example, wired and / or wirelessly) and realized by these multiple devices.

[0083] Furthermore, the UE200, MME300, S-GW310, and P-GW320 (the devices) described above may function as computers that perform the processing of the present invention. Figure 8 shows an example of the hardware configuration of the device. As shown in Figure 8, the device may be configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, and bus 1007.

[0084] Each functional block of the device (see Figures 2-4) is implemented by any hardware element of the computer device, or a combination of such hardware elements.

[0085] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc.

[0086] Memory 1002 is a computer-readable recording medium, such as ROM (Read Only). Memory 1002 may consist of at least one of the following: Memory, EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory). Memory 1002 may also be called registers, cache, main memory, etc. Memory 1002 can store executable programs (program code), software modules, etc., that can implement the methods according to the embodiments described above.

[0087] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. Storage 1003 may also be called an auxiliary storage device. The recording medium described above may also be, for example, a database, server, or other suitable medium including memory 1002 and / or storage 1003.

[0088] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via a wired and / or wireless network, and is also referred to as a network device, network controller, network card, communication module, etc.

[0089] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0090] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may consist of a single bus or different buses may be used for communication between devices.

[0091] Furthermore, the notification of information is not limited to the embodiments described above and may be carried out by other methods. For example, the notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or a combination thereof. Also, RRC signaling may be called an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.

[0092] Furthermore, the input and output information may be stored in a specific location (e.g., memory) or managed in a management table. The input and output information may be overwritten, updated, or appended to. The output information may be deleted. The input information may be sent to other devices.

[0093] The sequences and flowcharts in the embodiments described above may be rearranged in order, as long as there is no inconsistency.

[0094] Furthermore, the specific operations performed by the MME300, S-GW310, and P-GW320 in the embodiments described above may also be performed by other network nodes (devices). Additionally, the functions of the MME300, S-GW310, or P-GW320 may be provided by a combination of multiple other network nodes.

[0095] Terms used herein and / or terms necessary for understanding this specification may be replaced with terms having the same or similar meaning. For example, where applicable, channels and / or symbols may be signals, and signals may be messages. Also, the terms "system" and "network" may be used interchangeably.

[0096] Furthermore, parameters may be expressed as absolute values, relative values ​​from a given value, or by corresponding other information. For example, wireless resources may be indicated by an index.

[0097] The eNB100 (base station) can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which can also be provided with communication services by a base station subsystem (e.g., a small indoor base station RRH: Remote Radio Head).

[0098] The terms "cell" or "sector" refer to a base station and / or part or all of the coverage area of ​​a base station subsystem that provides communication services within this coverage. Furthermore, the terms “base station,” “eNB,” “cell,” and “sector” may be used interchangeably in this specification. Base stations may also be referred to by terms such as fixed station, NodeB, eNodeB (eNB), gNodeB (gNB), access point, femtocell, and small cell.

[0099] The UE200 may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0100] As used herein, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0101] Furthermore, the terms “including,” “comprising,” and their variations are intended to be comprehensive, as are “equipped with.” In addition, the term “or” as used herein or in the claims is not intended to be exclusive OR.

[0102] Any reference to elements using designations such as “first,” “second,” etc., as used herein, does not generally limit the quantity or order of those elements. These designations may be used herein as a convenient way to distinguish between two or more elements. Therefore, references to first and second elements do not imply that only two elements may be employed therein, or that the first element must precede the second element in any way.

[0103] Throughout this specification, where articles are added by translation, such as a, an, and the in English, these articles shall be considered plural unless the context clearly indicates otherwise.

[0104] As described above, embodiments of the present invention have been presented, but the statements and drawings that constitute part of this disclosure should not be understood as limiting the invention. Various alternative embodiments, examples, and operational techniques will become apparent to those skilled in the art from this disclosure. [Explanation of Symbols]

[0105] 10 Wireless communication systems 20 Wireless Access Networks 100 eNB 200 UE 210 Wireless Communication Section 220 Attachment Processing Unit 230 Operation Control Unit 240 Category Notification Section 300 MME 301 Category Receiver 303 Session Communications Department 305 Category Transfer Section 307 Priority Processing Unit 310 S-GW 320 P-GW 321 Category Receiver 323 Session Communications Department 325 Priority Processing Unit 327 Detailed Information Transmission Department 400 OCS / OFCS 1001 Processor 1002 memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus

Claims

[Claim 1] Network devices that constitute the core network, A category receiving unit receives the category of the user device operating as one of several categories according to its capabilities after the user device has attached to the core network and a wireless bearer has been established, and the category of the user device has been switched to a restricted category with a limited communication speed. A category transfer unit transfers the categories received by the category receiving unit to the Serving Gateway that constitutes the core network. A network device equipped with the following features.

Images