KR102342572B1 - Apparatus for controlling the function of individual User Equipment and method therefor - Google Patents

Abstract

The mobile manager for controlling the functions of individual user devices according to an embodiment of the present invention includes a storage module for storing a blacklist that is a list of types and software versions of terminal devices, and when receiving a device identifier of the user device, the received device an information processing module that identifies the type and software version of the device of the user device from the identifier and determines whether the user device is a blacklist device having a function that is not fully implemented by comparing it with the blacklist stored in the storage module; As a result of the determination, if the user equipment is a blacklist device, a function control module for generating deactivation information for controlling to deactivate a specific function of the user equipment and transmitting the generated deactivation information to the base station is included.

Description

Apparatus for controlling the function of individual User Equipment and method therefor

The present invention relates to a function control technology of a user device, and more particularly, a user device is classified according to a device type (SPID: Subscriber Profile ID), color, and software version based on IMEISV (International Mobile Equipment ID Software Version) And, it relates to an apparatus for controlling a specific function of a divided individual user device, and a method therefor.

After the LTE technology was commercialized, as the number of subscribers increased and the types of devices increased, the functions defined by 3GPP (ex. RoHC/TTiB/CDRx, etc.) were implemented in devices and systems. There may be a case where it cannot be used in the entire system due to a problem. In this case, the overall system quality may deteriorate due to the inability to use the corresponding function, and the device must wait until the problem is corrected or the system must provide service with an issue. In the prior art, it is not possible to classify each device and restrict its function so that it cannot be used. Therefore, when many devices having a problem with a specific function are camped in a specific base station, there is a problem in that all devices camped in the corresponding base station must be operated with the corresponding function unavailable. In addition, when an additional terminal is serviced after system commercialization, there is a problem that the function cannot be used even if a corresponding issue occurs.

Korean Patent Registration No. 10-1317895, registered on October 07, 2013 (Title: System and method for performing terminal function control using function codes)

An object of the present invention is to classify a user device having a problem in a specific function due to implementation different for each manufacturer into a device type (SPID), color, and software version, and to provide an apparatus and method for individually controlling the user device is in providing.

The mobile manager for controlling functions of individual user equipment according to a preferred embodiment of the present invention for achieving the above object stores a blacklist, which is a list of types of terminal devices (SPID: Subscriber Profile ID) and software versions. Upon receiving the device identifier of the user device, the device type and software version of the user device are identified from the received device identifier, and the user device is not fully implemented by comparing it with the blacklist stored in the storage module. an information processing module that determines whether or not the device is a blacklist device having a non-functional function, and if the user device is a blacklist device as a result of the determination, generates deactivation information for controlling to deactivate a specific function of the user device; and a function control module for transmitting deactivation information to the base station.

When the information processing module receives a message indicating that a handover to the user device is required, the information processing module determines whether the user device is a blacklist device having an incompletely implemented function, and the function control module determines whether the user device is a blacklist device. As a result, if the user equipment is a blacklist device, deactivation information for controlling to deactivate a specific function of the user equipment is generated, and the generated deactivation information is transmitted to the target base station.

The device identifier is an International Mobile Equipment Identity and Software Version Number (IMEISV), and the function control module exposes a field indicating a device type and a software version of the user device, and masks the serial number field of the device identifier to It is characterized in that deactivation information is generated.

In order to achieve the above object, the base station for controlling the function of an individual user equipment according to a preferred embodiment of the present invention receives deactivation information for controlling to deactivate a specific function of the user equipment, and transmits the received deactivation information. and an information processing unit for storing the context of the user device, and a function control unit for controlling a specific function of the user device to be deactivated according to the deactivation information.

The deactivation information is characterized in that a field indicating a device type and software version is exposed and a serial number field is an International Mobile Equipment Identity and Software Version Number (IMEISV) masked.

The function control unit generates a control message for controlling the user device to deactivate the specific function, and transmits the generated control message to the user device.

When the user device accesses, the information processing unit determines whether the user device is a blacklist device having a function that is not fully implemented by referring to the stored deactivation information of the context of the user device, and the function control unit determines the As a result, if the user device is a blacklist device, it is characterized in that a specific function of the user device is controlled to be deactivated.

When the handover of the user equipment is determined, the information processing unit transmits the stored deactivation information in the context of the user equipment to the target base station.

When the information processing unit receives deactivation information for controlling to deactivate a specific function of the user device through handover, the information processing unit stores the received deactivation information as a context of the user device, and the function control unit stores the user device according to the deactivation information. It is characterized in that it controls a specific function of the device to be deactivated.

According to a preferred embodiment of the present invention, there is provided a method for controlling a function of an individual user equipment to achieve the above object, comprising the steps of: a mobile manager receiving a device identifier of the user equipment; By comparing the identifier's device type and software version and the blacklist, which is a list of device types and software versions for which a specific function is not fully implemented, whether the user device is a blacklist device having functions that are not fully implemented determining, by the mobility manager, if the user device is a blacklist device as a result of the determination, generating deactivation information for controlling to deactivate a specific function of the user device; and transmitting to the first base station.

After transmitting to the first base station, when the first base station receives the deactivation information, storing the received deactivation information as a context of the user equipment; The method further includes controlling a specific function of the device to be deactivated.

After the step of controlling the specific function of the user equipment to be deactivated, the step of receiving, by the mobility manager, a message indicating that a handover for the user equipment is required from the first base station, and the mobility manager targeting the deactivation information transmitting the deactivation information to a second base station that is a base station; and when the second base station receives the deactivation information, storing the received deactivation information as a context of the user equipment; The method further includes controlling a specific function of the user device to be deactivated.

After the step of controlling the specific function of the user equipment to be deactivated, the step of determining, by the first base station, the handover of the user equipment, and the first base station using the deactivation information stored as the context of the user equipment as a target base station transmitting to the second base station; when the second base station receives the deactivation information, storing the received deactivation information as a context of the user equipment; The method further includes controlling a specific function to be deactivated.

The deactivation information is characterized in that a field indicating a device type and software version is exposed and a serial number field is an International Mobile Equipment Identity and Software Version Number (IMEISV) masked.

According to the present invention, a user device in which a function causing a problem occurs in a base station is classified into a device type, color, and software version, and only the corresponding user device can individually deactivate the function to provide a service efficiently, and from the customer's point of view You can improve the quality of your experience.

1 is a diagram for explaining a communication system for controlling functions of individual user devices according to an embodiment of the present invention.
2 is a diagram for explaining a device identifier used to control a function of an individual user device according to an embodiment of the present invention.
3 is a block diagram for explaining the configuration of a movement manager for controlling functions of individual user devices according to an embodiment of the present invention.
4 is a block diagram for explaining the configuration of a base station for controlling functions of individual user equipment according to an embodiment of the present invention.
5 is a flowchart illustrating a method for controlling a function of an individual user device according to an embodiment of the present invention.
6 is a flowchart illustrating a method for controlling a function of an individual user device according to an additional embodiment of the present invention.
7 is a flowchart illustrating a method for controlling a function of an individual user device according to another embodiment of the present invention.

Hereinafter, with reference to the accompanying drawings, a preferred embodiment in which a person of ordinary skill in the art to which the present invention pertains can easily practice the present invention will be described in detail. However, when it is determined that a detailed description of a related well-known function or configuration may unnecessarily obscure the gist of the present invention in describing the operating principle of the preferred embodiment of the present invention in detail, the detailed description thereof will be omitted. This is to more clearly convey the essence of the present invention by omitting unnecessary description. In addition, the present invention can make various changes and can have various embodiments, and specific embodiments are illustrated in the drawings and described in detail in the detailed description, which is not intended to limit the present invention to specific embodiments, It should be understood to include all modifications, equivalents and substitutes included in the spirit and scope of the present invention.

In addition, when an element is referred to as being “connected” or “connected” to another element, it means that it is logically or physically connected or can be connected. In other words, it should be understood that a component may be directly connected or connected to another component, but another component may exist in between, and may be indirectly connected or connected.

In addition, the terms used herein are used only to describe specific embodiments, and are not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly dictates otherwise. In addition, terms such as "comprises" or "have" described in this specification are intended to designate that the features, numbers, steps, operations, components, parts, or combinations thereof described in the specification exist, but one or the It should be understood that the above does not preclude the possibility of the existence or addition of other features or numbers, steps, operations, components, parts, or combinations thereof.

A method for receiving channel state information and an apparatus supporting the same according to an embodiment of the present invention will now be described in detail with reference to the drawings. In this case, the same reference numerals are used for parts having similar functions and actions throughout the drawings, and overlapping descriptions thereof will be omitted. In addition, in order to avoid obscuring the concept of the present invention, well-known structures and devices may be omitted or shown in block diagram form focusing on core functions of each structure and device.

First, a network environment to which an embodiment of the present invention is applied will be described. 1 is a diagram for explaining a communication system for controlling functions of individual user devices according to an embodiment of the present invention. 2 is a diagram for explaining a device identifier used to control a function of an individual user device according to an embodiment of the present invention.

First, referring to FIG. 1 , a communication system according to an embodiment of the present invention includes a user equipment (UE: User Equipment, 10), a base station (ENB: Evolved NodeB, 100), and a mobility manager (MME: Mobility Management Entity, 200). and a location register (HLR: Home Location Register/HSS: Home Subscriber Server, 300). In addition, the communication system further includes a Serving Gateway (SGW), a Packet Data Network 　 Gateway (PGW), a Gateway Location Register (GLR), etc., but not shown because it is not the gist of the present invention. and a detailed description thereof will be omitted.

The base station (eNB, 100) provides a wireless connection between the user equipment 10 and the network in a wireless section. That is, the base station 100 performs a function of connecting the user device 10 and the network in the wireless section.

The mobility manager (MME, 200) is for authenticating the user device 10 (Authentication). Key information for authenticating the user device 10 is stored in the location register 300 . The movement manager 200 receives such key information from the location register 300 and authenticates the user device 10 . In addition, the mobility manager (MME, 200) manages a bearer (EPS bearer). The bearer means a logical tunnel (GTP tunnel) created for the user equipment 10 to use a data network (e.g., internet). The mobility manager 200 manages the creation, change, and release of the tunnel. The MME 200 stores a network identifier (PLMN (Public Land Mobile Network) ID), and the MME 200 manages the movement state of the user equipment 10 accessed through the eNB 100 . That is, the mobility manager 200 may manage whether the user device 10 is in a camping state, whether it uses a data network, and the like.

The location register 300 stores key information and a user profile for authentication of the user device 10 . The subscriber profile includes QoS class information (priority, maximum available bandwidth, etc.) for each user's subscribed service product. Key information and user profile for authentication are transmitted from the location register 300 to the mobility manager 200 when the user device 10 accesses the network. The location register 300 may be a Home Location Register (HLR) or a Home Subscriber Server (HSS). The HSS is an advanced form of the HLR, and may perform functions such as configuration storage, identity management, and user state storage.

The user device 10 is composed of a mobile equipment (ME) and an identification module (USIM: Universal Subscriber Identity Module). The user device 10 is a concept including a device (ME) and a user who is provided with a mobile communication service using the device (ME). The same function may be implemented by different manufacturers, and a specific type of device (TE) produced by some manufacturers or the implementation of the software of the device (TE) may not be perfect, which may cause conflicts or problems. The present invention is to limit a function that causes a problem according to the type, color, and software version of the device (ME) regardless of the user. For this purpose, it should be possible to identify the type, color and software version of the device. International Mobile Subscriber Identity (IMSI), Globally Unique Temporary Identifier (GUTI), SAE-Temporary Mobile Subscriber Identity (S-TMSI), IP address, Cell - Radio Network Temporary Identifier (C-RNTI), UE S1 Application Protocol (S1AP) Identifiers such as ID and UE X2 Application Protocol (X2AP) ID are for identifying the user device 10 , and individual devices, colors, and software versions cannot be identified. Therefore, the present invention uses IMEISV (International Mobile Equipment Identity and Software Version Number). Hereinafter, the IMEISV will be referred to as a 'device identifier'.

Referring to FIG. 2 , the device identifier (IMEISV) includes a type approval code (TAC: Type Approval Code), a serial number (SNR: Serial Number), and a software version (SV: Software Version/SVN: Software Version Number). In addition, in the case of the old version, it further includes a Final Assembly Code (FAC). The device identifier (IMEISV) has a length of 16 digits for both the old version and the new version.

A Type Approval Code (TAC) is 6 or 8 digits long and uniquely identifies the model of the mobile device in question. A serial number (SNR) is six digits long (CCCCCC) and is a number to uniquely identify each device with the same TAC and FAC. The software version (SV/SVN) is two digits long and identifies the software version number of the mobile device. The Final Assembly Code (FAC) is a code that identifies the location of the final production stage and can have two digits. In the case of the old version where the final assembly code (FAC) exists, the type approval code (TAC) has 6 digits.

The present invention identifies the device type, color, and software version of the user device 10 using a device identifier (IMEISV), and the user device 10 is a type of device having a problem with a specific function, or the user device 10 ), if a version of the software having a problem with a specific function is installed, the corresponding function of the user device 10 is deactivated.

Next, a description will be given of the mobility manager (MME, 200) for controlling functions of individual user devices according to an embodiment of the present invention. 3 is a block diagram for explaining the configuration of a movement manager for controlling functions of individual user devices according to an embodiment of the present invention. Referring to FIG. 3 , the mobility manager 200 includes a communication module 210 , a storage module 220 , and a control module 230 .

The communication module 210 is for communication with the user device 10 and the base station 100 . The communication module 210 performs communication for exchanging data including necessary information with the user device 10 and the base station 100 . The communication module 210 extracts data from packets received from the user device 10 and the base station 100 and transmits the extracted data to the control module 230 . For example, the extracted data may be various messages. In addition, when receiving data for transmission from the control module 230 to the user device 10 and the base station 100 , the communication module 210 configures the received data into packets and transmits the received data. For example, the data may be a message including deactivation information and the like.

The storage module 220 serves to store programs and data necessary for the operation of the movement manager 200 , and may be divided into a program area and a data area. The program area may store a program for controlling the overall operation of the movement manager 200 and an operating system (OS) for booting the movement manager 200 . The data area is an area in which data generated according to the operation of the movement manager 200 and data necessary for the operation of the movement manager 200 are stored. Such data includes a blacklist, context of the user device, device identifier (IMEISV), deactivation information, and the like. Each type of data stored in the storage module 220 may be deleted, changed, or added according to a user's operation.

The control module 230 may control the overall operation of the movement manager 200 and the signal flow between internal blocks of the movement manager 200 , and may perform a data processing function of processing data. The control module 230 is preferably a central processing unit (CPU). The control module 230 includes an information processing module 231 and a function control module 233 . The information processing module 231 identifies the device type, color and software version of the user device 10 from the device identifier (IMEISV), and compares it with the blacklist stored in the storage module 220 so that the user device 10 is perfect. It is determined whether it is a blacklisted device with a function that is not implemented properly. When the user device 10 is a blacklist device, the function control module 233 generates deactivation information for controlling to deactivate a specific function of the user device 10 , and transmits the deactivation information to the base station 100 through the communication module 210 . ) can be transmitted. The operation of the control module 230 including the information processing module 231 and the function control module 233 will be described in more detail below.

Next, the base station 100 for controlling functions of individual user equipment according to an embodiment of the present invention will be described. 4 is a block diagram for explaining the configuration of a base station for controlling functions of individual user equipment according to an embodiment of the present invention. Referring to FIG. 4 , the base station 100 includes a communication unit 110 , a storage unit 120 , and a control unit 130 .

The communication unit 110 is for communication with the user device 10 and the mobile manager 200 . The communication unit 110 performs communication for exchanging data including necessary information with the user device 10 or the mobile manager 200 . The communication unit 110 extracts data from a packet received from the user device 10 or the mobile manager 200 , and transmits the extracted data to the control unit 130 . For example, the extracted data may be deactivation information or the like. In addition, when the communication unit 110 receives data to be transmitted from the control unit 130 to the user device 10 or the mobility manager 200 , the communication unit 110 configures the received data into packets and transmits the received data. For example, the received data includes various messages.

The storage unit 120 serves to store programs and data necessary for the operation of the base station 100 , and may be divided into a program area and a data area. The program area may store a program for controlling the overall operation of the base station 100 and an operating system (OS) for booting the base station 100 . The data area is an area in which data generated according to the operation of the base station 100 and data necessary for the operation of the base station 100 are stored. Such data includes, for example, the context of the user device, deactivation information, and the like. Various types of data stored in the storage unit 120 may be deleted, changed, or added according to a user's manipulation.

The controller 130 may control the overall operation of the base station 100 and signal flow between internal blocks of the base station 100 and perform a data processing function of processing data. The control unit 130 is preferably a central processing unit (CPU). The control unit 130 includes an information processing unit 131 and a function control unit 133 . Specific operations of the control unit 130 including the information processing unit 131 and the function control unit 133 will be described in more detail below.

Next, a method for controlling a function of an individual user device according to an embodiment of the present invention will be described. 5 is a flowchart illustrating a method for controlling a function of an individual user device according to an embodiment of the present invention. In FIG. 5 , a first base station 101 and a second base station 102 exist, and the user equipment 10 selects the first base station 101 as a serving cell and starts a procedure for establishing an initial connection (Initial Connection Establishment). Assume you are doing

Referring to FIG. 5 , the user device 10 transmits a device identifier (IMEISV) in step S110. This device identifier (IMEISV) is transmitted to the mobility manager 200 through the first base station 100 . According to an embodiment, the device identifier (IMEISV) transmits an Attach Request message transmitted by the user device 10 to the first base station 101 and the first base station 101 to the mobility manager 200 . may be transmitted by being included in the initial user equipment (Initial UE) message. According to another embodiment, when the mobile manager 200 transmits an Identity Request message to the user device 10 , the user device 10 transmits an Identity Response message to the mobile manager 200 . Also, the device identifier (IMEISV) may be included in an identity response message and transmitted to the mobility manager 200 .

Upon receiving the device identifier (IMEISV), the mobile manager 200 may generate deactivation information using the device identifier (IMEISV). The deactivation information is information for limiting a specific function of the specific user device 10 by classifying the device type, color, and software version. The mobility manager 200 may identify the device type, color, and software version of the user device 10 from the device identifier (IMEISV) of the user device 10 . If the type, color, and software version of the corresponding device have a problem in a specific function, the mobile manager 200 may manage the user device 10 as a blacklist. Here, the blacklist is a list of device types, colors, and software versions that cause problems such as crashing with the system or bringing a load on the system because a specific function is not fully implemented. Here, the specific function includes a power saving technology, a high-definition video (HDV) compression technology, and the like, and more specifically, Robust Header Compression (RoHC), transmission time interval bundling (TTiB), Connected mode Discontinuous Reception (CDRx), etc. can be exemplified.

When the information processing module 231 of the mobile manager 200 receives the device identifier (IMEISV) of the user device 10 from the first base station 101 through the communication module 210, the device identifier received in step S120 ( IMEISV) identifies the device type, color, and software version of the user device 10, and compares it with the blacklist stored in the storage module 220. The user device 10 has a function that is not fully implemented. Determines whether it is a list device.

As a result of the determination, if the corresponding user device 10 is a blacklist device having a function that is not fully implemented, the function control module 233 of the mobility manager 200 uses the device identifier (IMEISV) in step S130 to Deactivation information for controlling to deactivate a specific function of the user device 10 is generated. The device identifier (IMEISV) includes a type approval code (TAC), a serial number (SNR) and a software version (SV/SVN) as shown in FIG. 2, and in the case of the old version, the final assembly code (FAC) include more The function control module 233 is a device identifier (IMEISV) field indicating the device type, color, and software version of the user device 10, that is, a type approval code (TAC), a final assembly code (FAC), a software version ( SV/SVN) and masking the serial number (SNR) to generate deactivation information.

Then, the function control module 233 of the mobility manager 200 transmits the deactivation information generated through the communication module 210 to the first base station 101 in step S140 . In this case, the deactivation information may be transmitted while being included in an Initial Context Setup Request message.

When the information processing unit 131 of the first base station 101 receives deactivation information through the communication unit 110 , the deactivation information received in step S150 is stored in the storage unit 120 as a context of the user device 10 .

Then, in step S160 , the first base station 101 may control a specific function of the corresponding user device 10 to be deactivated.

According to an embodiment, the function control unit 133 of the first base station 101 generates a control message for controlling to deactivate a specific function and transmits it to the user device 10 through the communication unit 110 to the user device 10 . can disable certain features.

According to another embodiment, when providing a service to the connected user device 10 , the information processing unit 131 refers to the deactivation information of the context of the user device 10 stored prior to the storage unit 120 ( S150 ). It is determined whether the user device 10 is a blacklist device having a function that is not fully implemented. As a result of the determination, if the corresponding user device 10 is a blacklist device having a function that is not fully implemented, the function control unit 133 of the first base station may control a specific function of the user device 10 to be deactivated. .

Next, a method for controlling a function of an individual user device according to an additional embodiment of the present invention will be described. 6 is a flowchart illustrating a method for controlling a function of an individual user device according to an additional embodiment of the present invention. FIG. 6 is a diagram showing the second base station 102 while receiving a service from the first base station 101 in a state in which the first base station 101 stores deactivation information in the context of the user equipment 10 as described in FIG. 5 . Assume that a moving handover is in progress. Also, in FIG. 6 , it is assumed that a direct interface between the base stations 101 and 102 does not exist, so that an S1 interface-based handover is performed.

Referring to FIG. 6 , when the first base station 101 determines handover (S1 based handover) of the user equipment 10, the first base station 101 sends the user equipment 10 to the mobility manager 200 in step S210. ) may transmit a handover required message indicating that a handover is required.

Accordingly, when the information processing module 231 of the mobility manager 200 receives a handover required message from the first base station 101 through the communication module 210, in step S220, the device of the user device 10 Identifies the device type, color, and software version of the user device 10 from the identifier (IMEISV), and compares it with the blacklist stored in the storage module 220 so that the user device 10 has a function that is not fully implemented Determines whether it is a blacklisted device or not.

As a result of the determination, if the corresponding user device 10 is a blacklist device having a function that is not fully implemented, the function control module 233 of the mobility manager 200 uses the device identifier (IMEISV) in step S230 to Deactivation information for controlling to deactivate a specific function of the user device 10 is generated. The function control module 233 may generate deactivation information by masking the serial number (SNR) of the device identifier (IMEISV).

Then, the function control module 233 of the mobility manager 200 transmits the deactivation information generated through the communication module 210 in step S240 to the second base station 102 that is the target base station of the handover. In this case, the deactivation information may be transmitted while being included in a handover request message.

When the information processing unit 131 of the second base station 102 receives deactivation information through the communication unit 110 , the deactivation information received in step S250 is stored in the storage unit 120 as the context of the user device 10 .

Accordingly, in step S260 , when the user equipment 10 completes the handover, the second base station 101 may control a specific function of the user equipment 10 to be deactivated.

According to one embodiment, the function control unit 133 of the second base station 101 generates a control message for controlling to deactivate a specific function and transmits it to the user device 10 through the communication unit 110 to the user device 10 . can disable certain features.

According to another embodiment, when providing a service to the user equipment 10 on which the handover has been completed, the information processing unit 131 of the second base station 102 stores the user equipment 10 stored before the storage unit 120 (S250). ), it is determined whether the corresponding user device 10 is a blacklist device having a function that is not fully implemented with reference to the deactivation information of the context. As a result of the determination, if the corresponding user device 10 is a blacklist device having a function that is not fully implemented, the function control unit 133 of the second base station 102 controls a specific function of the user device 10 to be deactivated. can do.

Next, a method for controlling a function of an individual user device according to another embodiment of the present invention will be described. 7 is a flowchart illustrating a method for controlling a function of an individual user device according to another embodiment of the present invention. FIG. 7 shows the second base station 102 while receiving a service from the first base station 101 in a state where the first base station 101 stores deactivation information in the context of the user equipment 10 as described in FIG. 5 . Assume that a moving handover is in progress. In addition, FIG. 7 assumes a situation in which a direct interface exists between the base stations 101 and 102 to perform an X2 interface-based handover.

Referring to FIG. 7 , when the first base station 101 determines the handover of the user device 10 (X2 based handover), the information processing unit 131 of the first base station 101 is configured to perform an X2 interface in step S310. Deactivation information is transmitted to the second base station 102 to the second base station 102 . In this case, the deactivation information is transmitted through a handover request message. In X2 handover, the handover request message includes the context of the user equipment 10 , and as described above, deactivation information is stored as the context of the user equipment 10 . Accordingly, deactivation information is transmitted to the second base station 102 through a handover request message.

When the information processing unit 131 of the second base station 102 receives deactivation information through the communication unit 110 , the deactivation information received in step S320 is stored in the storage unit 120 as a context of the user device 10 .

Accordingly, in step S330 , when the user equipment 10 completes the handover, the second base station 101 may control a specific function of the user equipment 10 to be deactivated.

According to one embodiment, the function control unit 133 of the second base station 101 generates a control message for controlling to deactivate a specific function and transmits it to the user device 10 through the communication unit 110 to the user device 10 . can disable certain features.

According to another embodiment, when providing a service to the user equipment 10 on which the handover has been completed, the information processing unit 131 of the second base station 102 stores the user equipment 10 stored before the storage unit 120 (S250). ), it is determined whether the corresponding user device 10 is a blacklist device having a function that is not fully implemented with reference to the deactivation information of the context. As a result of the determination, if the corresponding user device 10 is a blacklist device having a function that is not fully implemented, the function control unit 133 of the second base station 102 controls a specific function of the user device 10 to be deactivated. can do.

The method according to an embodiment of the present invention may be provided in the form of a computer-readable medium suitable for storing computer program instructions and data. Such a computer-readable recording medium may include program instructions, data files, data structures, etc. alone or in combination, and includes all types of recording devices in which data readable by a computer system is stored. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks and magnetic tapes, compact disk read only memory (CD-ROM), and optical recording media such as DVD (Digital Video Disk). Stores program instructions such as Magneto-Optical Media, ROM (Read Only Memory), RAM (Random Access Memory), Flash memory, etc. and hardware devices specially configured to perform In addition, the computer-readable recording medium is distributed in a computer system connected through a network, so that the computer-readable code can be stored and executed in a distributed manner. In addition, functional programs, codes, and code segments for implementing the present invention can be easily inferred by programmers in the technical field to which the present invention pertains.

Although the above has been described and illustrated in relation to the preferred embodiment for illustrating the technical idea of the present invention, the present invention is not limited to the configuration and operation as shown and described as such, and without departing from the scope of the technical idea. It will be apparent to those skilled in the art that many changes and modifications to the present invention are possible. Accordingly, all such suitable alterations and modifications and equivalents are to be considered as being within the scope of the present invention.

According to the apparatus and method for controlling the function of individual user equipment according to the present invention, the user equipment in which the function causing the problem occurs in the base station is classified into the type, color and software version of the device, and the divided user equipment However, by individually disabling the function, the service can be provided efficiently and the quality of experience can be improved from the customer's point of view. The present invention has industrial applicability because it has sufficient potential for marketing or business, as well as to the extent that it can be clearly implemented in reality.

10: user device 100: base station
110: communication unit 120: storage unit
130: control unit 131: information processing unit
133: function control unit 200: movement manager
210: communication module 220: storage module
230: control module 231: information processing module
233: function control module

Claims (14)

a storage module for storing a blacklist that is a list of types of terminal devices (SPID: Subscriber Profile ID) and software versions;
Upon receiving the device identifier of the user device, the type and software version of the user device are identified from the received device identifier, and compared with the type and software version of the terminal device in the blacklist stored in the storage module, the user device is perfect. an information processing module for judging whether a blacklist device has a function that is not implemented properly; and
As a result of the determination, if the user device is a blacklist device, a function control module that generates deactivation information for controlling to deactivate a specific function of the user device and transmits the generated deactivation information to the base station; characterized in that it comprises a;
Mobility manager to control the functions of individual user devices. According to claim 1,
The information processing module
When receiving a message informing that the user equipment needs handover, it is determined whether the user equipment is a blacklist device having a function that is not fully implemented,
The function control module is
If the user equipment is a blacklist device, generating deactivation information for controlling to deactivate a specific function of the user equipment, and transmitting the generated deactivation information to a target base station
Mobility manager to control the functions of individual user devices. The method of claim 1,
The device identifier is an International Mobile Equipment Identity and Software Version Number (IMEISV),
The function control module is
The deactivation information is generated by exposing a field indicating the device type and software version of the user device and masking the serial number field of the device identifier.
Mobility manager to control the functions of individual user devices. The type and software version of the user device identified from the device identifier of the user device by the mobile manager is compared with the type and software version of the terminal device in the stored blacklist, and the user device has a function that is not fully implemented. an information processing unit configured to store the received deactivation information as a context of the user device when receiving deactivation information generated by determining whether the device is a list device and controlling to deactivate a specific function of the user device; and
and a function control unit for controlling a specific function of the user device to be deactivated according to the deactivation information.
A base station for controlling the functions of individual user equipment. 5. The method of claim 4,
The deactivation information is
A field indicating the device type and software version is exposed, and the serial number field is a masked International Mobile Equipment Identity and Software Version Number (IMEISV)
A base station for controlling the functions of individual user equipment. 5. The method of claim 4,
The function control unit
generating a control message for controlling the user device to deactivate the specific function, and transmitting the generated control message to the user device
A base station for controlling the functions of individual user equipment. 5. The method of claim 4,
The information processing unit
When the user device accesses, it is determined whether the user device is a blacklist device having functions that are not fully implemented by referring to the stored deactivation information of the context of the user device,
The function control unit
If the user device is a blacklist device, characterized in that the control to deactivate a specific function of the user device
A base station for controlling the functions of individual user equipment. 5. The method of claim 4,
The information processing unit
When the handover of the user equipment is determined, the deactivation information stored in the context of the user equipment is transmitted to a target base station.
A base station for controlling the functions of individual user equipment. 5. The method of claim 4,
The information processing unit
Upon receiving deactivation information for controlling to deactivate a specific function of the user device through handover, the received deactivation information is stored as a context of the user device,
The function control unit
Controlling a specific function of the user device to be deactivated according to the deactivation information
A base station for controlling the functions of individual user equipment. ◈Claim 10 was abandoned when paying the registration fee.◈ receiving, by the mobile manager, a device identifier of the user device;
The mobile manager compares the type and software version of the received device identifier with the type and software version of the terminal device in the blacklist, which is a list of types and software versions of devices in which a specific function is not fully implemented, and the user device determining whether the device is a blacklist device having a function that is not fully implemented;
generating, by the mobility manager, deactivation information for controlling to deactivate a specific function of the user device when the user device is a blacklist device as a result of the determination; and
and transmitting, by the mobility manager, the generated deactivation information to a first base station.
A method for controlling the functions of individual user equipment. ◈Claim 11 was abandoned when paying the registration fee.◈ 11. The method of claim 10,
After transmitting to the first base station,
when the first base station receives the deactivation information, storing the received deactivation information as a context of the user equipment; and
controlling, by the first base station, to deactivate a specific function of the user equipment according to the deactivation information;
A method for controlling the functions of individual user equipment. ◈Claim 12 was abandoned when paying the registration fee.◈ 12. The method of claim 11,
After the step of controlling the specific function of the user device to be deactivated,
receiving, by the mobility manager, a message from the first base station indicating that handover to the user equipment is required;
transmitting, by the mobility manager, the deactivation information to a second base station that is a target base station;
when the second base station receives the deactivation information, storing the received deactivation information as a context of the user equipment; and
controlling, by the second base station, to deactivate a specific function of the user equipment according to the deactivation information;
A method for controlling the functions of individual user equipment. ◈Claim 13 was abandoned when paying the registration fee.◈ 12. The method of claim 11,
After the step of controlling the specific function of the user device to be deactivated,
determining, by the first base station, a handover of the user equipment;
transmitting, by the first base station, deactivation information stored in the context of the user equipment to a second base station that is a target base station;
when the second base station receives the deactivation information, storing the received deactivation information as a context of the user equipment; and
controlling, by the second base station, to deactivate a specific function of the user equipment according to the deactivation information;
A method for controlling the functions of individual user equipment. ◈Claim 14 was abandoned at the time of payment of the registration fee.◈ 11. The method of claim 10,
The deactivation information is an International Mobile Equipment Identity and Software Version Number (IMEISV) in which a field indicating a device type and software version is exposed and a serial number field is masked.
A method for controlling the functions of individual user equipment.

Images