TWI672068B - Master device and slave device for accessing wireless network - Google Patents

Abstract

The invention provides a method: using user identification information stored in a mobile user equipment (UE) to connect to a communication service via a public wireless network in the UE; establishing a communication link between the UE and a device; generating Network access information (NAI) associated with the communication service in the UE; and sending the NAI from the UE to the device via the communication link. The method further includes using the NAI to connect the communication service in the device, and terminating the connection of the communication service in the UE.

Description

Master device and controlled device for accessing wireless network

Embodiments of the inventive concept are generally related to devices and methods capable of accessing a wireless network. More specifically, some embodiments of the inventive concept are related to semiconductor devices, system-on-a-chips, and users capable of accessing wireless networks and transmitting network access information (NAI) to other devices Equipment (user equipment; UE). Certain other embodiments of the inventive concepts are related to methods of enabling (or facilitating) device access to a wireless network and transmitting related NAI to other devices.

A wireless network is a system that implements (or supports) one or more interoperable components of one or more wireless communication services between two or more devices. Requesting, registering, identifying, using, and terminating wireless communication services involves multiple wireless-capable devices and wireless components associated with wireless networks (e.g., base stations, servers, radio channel equipment, mobility management equipment , Software resources, etc.). In some cases, limited resources within a wireless network may limit the number of users and / or the quality of service that users seek to access wireless communication services.

Many public wireless networks (PWN) (such as public wireless networks established and maintained by mobile phone companies), mobile wireless broadband systems and / or satellite systems (each of which can be based on a cellular communication protocol Providing communication services) is an example of contemporary wireless networks. Each PWN restricts access to the communication services it provides to authorized UEs. Therefore, authorized UEs can consider user terminals through PWN, and service providers that manage and operate PWN can provide subscriber identification information (SII) to individual user terminals. Thereafter, the SII can be used by the user terminal to establish authorized access to the PWN.

SII can be stored in a user terminal or can be inserted into / unplugged from a user terminal (for example, in the form of a so-called "subscriber identification module (SIM) card") SIM. One or more data encryption methods can be used to protect the data associated with the SII and the user terminal information stored on the SIM. The user terminal can use the SII stored in the SIM to use or access the communication service via the PWN.

In the electronics and communication industries, various attempts have been made to produce UEs equipped with wired / wireless communication functions. An example is the so-called Internet of Things (IoT) or Internet of Everything (IoE). IoT or IoE means that everyday things are connected via wired / wireless networks to share information. Therefore, IoT or IoE methods can be used to connect devices via a network, allowing them to share information across multiple technology areas including: smart home appliances, smart homes (eg, remote metering, heating / cooling management, home solar Systems, home safety systems) health care and smart cars.

Increasingly, users may wish to access PWNs using multiple UEs that include not only a single fixed UE but also mobile UEs. Therefore, in some cases, the user may be required to remove the SIM from the first UE capable of accessing the PWN and insert the SIM in the second UE, so that the second UE may be able to access the PWN. This process is labor-intensive, there is no continuity in data usage, and more than one UE cannot use the same SII to access PWN at the same time.

However, and from anything provided, in some cases, a user may purchase a SIM for each UE. This incurs the additional cost for each purchased SIM, there is desynchronization between different, which can cause data / communication loss, and each UE can have different wireless capabilities.

The user may wish to access (eg, upload data to and download data from) the PWN via multiple UEs, and also does not need to purchase a separate SIM for each UE. In other words, a user may wish to use one set of SII to freely access one or more PWNs simultaneously using one or more UEs. Therefore, there is a general need for devices and methods that allow users to freely access PWNs using multiple UEs.

In one embodiment of the inventive concept, a method includes: using user identification information (SII) stored in a master device to connect to a communication service via a public wireless network (PWN) in the master device; at the master device Establishing a communication link with the controlled device; generating network access information (NAI) associated with a communication service in the master device; and sending the NAI autonomous control device to the controlled device via the communication link.

In another embodiment of the inventive concept, a method includes: connecting a communication service in a master control device storing storage access authorization authentication; and generating, in the master control device, network status information associated with the connection of the communication service (network) status information (NSI); self-authorized authentication in the master control device and NSI derived NAI; establishment of a communication link between the master control device and the controlled device; sending the NAI autonomous control device to the controlled device via the communication link; use The NAI connects the communication service in the controlled device; and terminates the communication service in the master device.

In still another embodiment of the inventive concept, a method includes: connecting a first communication service in a first master control device that stores a first access authorization certificate; and generating a first communication service with the first communication service in the first master control device. The first network status information (1NSI) associated with the connection; the first network accessing information (1NAI) derived from the first access authorization certificate and 1NSI; A first communication link is established between the control device and the controlled device; 1NAI is sent from the first master control device to the controlled device and the 1NAI is stored in the controlled device via the first communication link; through the second communication The link completes the same process with the second master device and 2NAI; uses the 1NAI to connect the first communication service in the controlled device; and terminates the first communication service in the first master device.

In yet another embodiment of the inventive concept, a method includes: using SII stored in a master device to connect to a communication service via a PWN in the master device; establishing a communication link between the master device and the controlled device Send the NAI autonomous control device associated with the communication service to the controlled device via the communication link; use NAI to connect the communication service in the controlled device; terminate the connection of the communication service in the master control device; future autonomous via the communication link The control device requests the controlled device to release a connection release request for the communication service to the controlled device; and in response to the release request, terminates the communication service in the controlled device and reconnects the communication service in the master control device.

In yet another embodiment of the inventive concept, a mobile user device includes: a memory that stores software components; an application processor that controls the operation of the user device; and a connectivity unit that connects the user device and the device A communication link is established between them; and a communication processor, which connects a communication service via a PWN.

These and other embodiments of the inventive concept can support a variety of user equipment when accessing a wireless network.

Certain embodiments of the inventive concept will now be described with some additional details with reference to the accompanying drawings. The inventive concept may, however, be embodied in many different forms and should not be construed as limited to only the illustrated embodiments. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. Throughout the written description and drawings, like reference numerals and signs are used to indicate similar or similar elements.

It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may be present. In contrast, when an element is referred to as being "directly connected" or "directly coupled" to another element, there are no intervening elements present. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items. Other words used to describe the relationship between elements or layers should be interpreted similarly (for example, "between" versus "directly between", "adjacent" versus "directly adjacent", "between ... on "versus" directly on ... ").

It should be understood that, although the terms "first," "second," etc. may be used herein to describe various elements, components, regions, layers and / or sections, such elements, components, regions, layers and / or sections Paragraphs should not be limited by these terms. These terms are only used to distinguish one element, component, region, layer or section from another element, component, region, layer or section. Accordingly, a first element, component, region, layer, or section discussed below can be referred to as a second element, component, region, layer, or section without departing from the teachings of example embodiments.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit example embodiments. As used herein, the singular forms "a", "an" and "said" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should be further understood that the terms "including" and / or "comprising," as used herein, specify the presence of stated features, integers, steps, operations, elements and / or components, but do not exclude one or more other features, The presence or addition of integers, steps, operations, elements, components, and / or groups thereof.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which example embodiments of the inventive concepts are generally familiar. It should be further understood that terms such as those defined in commonly used dictionaries should be interpreted to have a meaning consistent with their meaning in the context of the relevant technology and will not be interpreted in an idealized or over-formal sense unless explicitly definition.

The described embodiments are generally related to supporting a user equipment (UE) connection to a wireless network. For example, in some embodiments, the master device may send network access information (NAI) to the controlled device in order to use NAI to connect to a communication service in the controlled device.

A UE according to various embodiments of the present inventive concept may refer to a device that is assembled to include electronic components, elements, and the like so as to enable support for a communication service by a predetermined communication resource. For example, a UE may include components required to establish a communication service with another UE or obtain access to a public wireless network. These components may be implemented differently in hardware, firmware, and / or software.

In some embodiments of the inventive concept, the UE may be implemented functionally and / or physically as a smart phone, tablet personal computer (PC), mobile phone, video phone, e-book reader, desktop PC, laptop PC, mini-notebook computer, workstation, server, Personal Digital Assistant (PDA), Portable Multimedia Player (PMP), MP3 player, mobile medical device, Camera, wearable device (for example, electronic glasses, Head-Mounted-Device (HMD), electronic cloth, electronic bracelet, electronic necklace, electronic accessory (or application accessory), electronic tattoo, wisdom Mirror or smart watch).

In other embodiments of the inventive concept, the UE may be implemented as part of a smart home appliance. Smart home appliances can include, for example, TV (TV), Digital Video Disk (DVD) players, Blu-ray players, audio devices, refrigerators, air conditioners, thermostats, vacuum cleaners, ovens, microwave ovens, washing machines, Air purifier, set-top box, home automation control panel, security control panel, TV box (for example, Samsung HomeSync ™, Apple TV ™ or Google TV ™), game console (for example , Xbox ™ or PlayStation ™), electronic dictionary, electronic buttons, video camera or electronic picture frame.

In some embodiments of the inventive concept, the UE may be implemented as a medical device (eg, a portable medical measurement device such as a blood glucose meter, heart rate meter, blood pressure meter, thermometer, magnetic resonance angiography (Magnetic Resonance Angiography); MRA), Magnetic Resonance Imaging (MRI), Computed Tomography (CT), medical cameras, ultrasound devices, etc. In some embodiments of the inventive concept, the UE may implement For navigation devices, Global Positioning System (GPS) receivers, Event Data Recorder (EDR), Flight Data Recorder (FDR), automotive infotainment devices, marine electronics ( For example, marine navigation systems, gyroscopes, and the like), avionics, safety equipment, car head units, industrial or home robots, Automatic Teller's Machine (ATM), Point of Sales (POS) ) Devices, IoT devices (e.g., light bulbs, Kinds of sensors, sprinkler systems, fire alarms, thermostat, lights, toaster, fitness equipment, hot water tanks, heaters, boilers, etc.) and the like.

In some embodiments of the inventive concept, the UE may be implemented as part of a furniture or building structure. The UE according to various embodiments of the inventive concept may be any one or combination of the devices and systems described above.

Alternatively, a UE according to some embodiments of the inventive concept may be a flexible UE. Therefore, it will be apparent to those skilled in the art that the UEs according to various embodiments of the present disclosure are not limited to the devices described above, and may include new UEs that can have technological development.

A UE according to various embodiments will now be described with reference to the accompanying drawings. The term 'user' as used herein may refer to a person using a UE or a device using a UE (eg, an artificial intelligence UE). The term 'subscriber' as used herein may refer to a user of a communication service provided by a user via a PWN that uniquely assigns SII.

FIG. 1 is a block diagram illustrating a wireless communication environment according to various embodiments of the inventive concept in one example.

Referring to FIG. 1, the main control device 110 and the controlled device 120 may be connected by an interface 130. The interface may be based on a fixed line or wireless, and may be a communication path between the master device 110 and the controlled device 120. The communication path may form a communication link. The interface 130 is not limited to a specific communication scheme. For example, the interface 130 may be implemented based on at least one protocol for wired communication and / or wireless communication. The communication link may include one or more of the following: local area network (LAN), Wi-Fi, near field communication (NFC), radio frequency (RF), wired Communication, cellular link, Bluetooth (BT), global positioning system (GPS), cable, infrared link, Internet, long term evolution (LTE), and WiMax.

The main control device 110 and the controlled device 120 may be connected to a communication service via a public wireless network (PWN) 140. The main control device 110 may be a portable UE. The communication service can be a cellular voice / data service. The connection of the cellular voice / data service in the portable UE may include registering the portable UE with a mobility management entity (MME) of the PWN 140. PWN 140 can be based on LTE, LTE-advanced (LTE-A), code division multiple access (CDMA), wideband CDMA (W-CDMA), and universal mobile telecommunications system ( Universal mobile telecommunications system (UMTS), wireless broadband (Wi-Bro) or global system for mobile communication (GSM) provide wireless communication services.

The master device 110 is a user terminal that is authorized to access the PWN 140, and the controlled device 120 is a user terminal that is not inherently authorized to access the PWN 140. For example, in some embodiments of the inventive concept, the controlled device 120 lacks the NAI required to access the PWN 140-because it does not have a user identification module that provides the necessary user identification information (SII) connection Group (SIM), so it can gain access to PWN 140 up to the connected SIM.

However, in some embodiments of the present inventive concept, the master device 110 can (1) use internally stored SII (eg, SII stored in a connected SIM) to generate enough data to be connected to the master device 110 via the PWN 140. The NAI of the communication service, and (2) the generated NAI associated with the communication service is transmitted to the controlled device 120 via the communication link. The controlled device 120 may thereafter connect to a communication service in the controlled device 120 via the PWN 140 using NAI. Once the communication service is connected to the controlled device 120, the communication service in the main control device 110 is terminated. One possible relationship between SII and the corresponding NAI is illustrated in FIG. 2.

FIG. 2 is a table listing possible components of network access information (NAI) in the case of some embodiments of the inventive concept.

Referring to FIG. 2, NAI 210 may include one or more components in SII 220 and one or more components in network status information (NSI) 230. Accordingly, the following descriptive references to NAI 210 may refer to one or more components in SII 220 and / or one or more components in NSI 230. In this regard, SII 220 is still stored in the SIM even when the UE is powered off. PWN 140 requests SII 220 to verify that the user is a user. All information used to access the PWN 140 and stored in the SIM is SII 220. SII 220 may include some SIM information. In addition, as previously indicated, the SIM may be stored on a SIM card configured to be physically inserted into the master device 110 and thereafter removed from the master device. The controlled device 120 may not have a SIM card. The information recorded in the SIM can be protected by encryption or the like. The master device 110 can read and use the SII 220 stored on the SIM connected to the master device 110 to connect the communication service via the PWN 140. The SII 220 may include multiple SII components, and the NAI 210 may include at least one of multiple SII components or information derived from at least one of the multiple SII components.

SII 220 may include international mobile subscriber identity (IMSI) 221, temporary mobile subscriber identity (TMSI) 223, integrated circuit card identification (ICCID) 225, main The key (K) 227 and the globally unique temporary identifier (GUTI) 229. SIM can also store local area identity (LAI), operator-specific emergency numbers, short message service center (SMSC) numbers, service provider names (SPNs), and service dial numbers ( service dialing number (SDN), payment notification parameters, and value added service (VAS) applications.

IMSI 221 is an example of SII 220 and can be stored in SIM when SIM is purchased. IMSI 221 is used to identify users of PWN 140. The same values of IMSI 221 can be stored in SII 220 as well as on PWN 140. IMSI is rarely used, except for some instances (for example, when a call is connected).

For security reasons, TMSI 223 is used instead of IMSI 221. After connecting the communication service in the master device 110, the TMSI 223 is provided from the PWN 140 to the master device 110. TMSI 223 is changed from time to time by PWN 140.

ICCID 225 is an example of unique identification information and is used to identify the SIM. K 227 is the master key used for authentication, and the same value can be stored in SIM and PWN 140. GUTI 229 is an example of temporary identification information. GUTI 229 contains TMSI 223.

The communication service connected in the main control device 110 may generate a corresponding NSI 230. NAI 210 may include NSI 230. The NSI 230 may be stored in the master device 110 before the communication service in the master device 110 is terminated. When the NAI 210 autonomous control device 110 is sent to the controlled device 120, the NSI 230 may be stored in the controlled device 120. After the connection of the communication service in the master device 110 is terminated, according to the connection of the communication service in the controlled device 120, an updated NSI may be generated and stored in the controlled device 120. The updated NSI may be sent to the master device 110 via the communication link 130, and the NSI 230 stored in the master device 110 may be updated using the updated NSI from the controlled device 120. NSI 230 may include PWN cell identification information 231, radio resource control (RRC) status information 233, user tracking area (TA) information 235, and non-access stratum (NAS) status information One or more of 237.

The PWN cell identification information 231 may be used to indicate to which cell the UE currently belongs. When the user moves the UE to a neighboring PWN cell, the PWN cell identification information 231 will change.

The RRC status information 233 can be used by the controlled device 120 for seamless connection to the PWN 140, and can be used to indicate the current communication status of the main control device 110 or the controlled device 120. When the UE is connected without performing any communication behavior (for example, downloading data), the RRC state of the UE may be referred to as an RRC idle mode (for example, 'RRC_idle'), and when the UE is used for actual communication, the RRC state may be changed Called RRC connected mode (for example, 'RRC_connected').

The user TA information 235 may be used to indicate where the user is currently located.

The NAS information 237 can be used by the controlled device 120 for authentication for PWN 140 access, and can be used for encryption of the connection between the PWN 140 and the main control device 110 or the controlled device 120. NAS information 237 is an example of access status information and is information of a NAS protocol for mobile management, identification, authentication, and the like.

The NSI 230 may include information on the status of a communication service established by the master device 110 via the PWN 140, and information defining the status of access to the PWN 140 by the master device 110. The controlled device 120 may require the NSI 230 for the controlled device 120 to take over all or part of the communication services connected to the main control device 110.

Returning to FIG. 1, the controlled device may not have the NAI 210 required to access the PWN 140, even if the controlled device 120 has a communication processor capable of accessing a communication service via the PWN 140. If the controlled device has NAI 210, the controlled device 120 can access the communication service via the PWN 140.

For example, if the controlled device 120 can obtain the NAI 210 provided by the autonomously controlled device 110, the controlled device 120 can use the provided NAI 210 to access the communication service via the PWN 140.

The controlled device 120 may form a communication link to the main control device 110 via the interface 130, and use the communication link to obtain the NAI 210 provided by the autonomous control device 110. The NAI 210 may be information that the controlled device 120 needs to access the communication service via the PWN 140. The controlled device 120 may access the PWN 140 using the NAI 210 provided by the autonomous control device 110.

If access by multiple UEs is requested using information associated with the same user, PWN 140 will authorize only one UE to obtain access via a predetermined authentication procedure. For example, if the master device 110 and the controlled device 120 try to access the PWN 140 at the same time, the PWN 140 will generally give the master device 110 access priority, and if the master device requests access, the controlled device 120 is connected to the PWN 140, and the PWN 140 can release access by the controlled device 120.

FIG. 3 is a block diagram further illustrating, in one example, a user equipment usable in a network environment according to some embodiments of the inventive concept.

3, a UE 301 in a network environment 300 in various embodiments will be described. The UE 301 may include a bus 310, a processor 320, a memory 330, an input / output (I / O) interface 350, a display module 360, and a communication interface 370. In some embodiments, the UE may not include at least one of the above components, or may further include at least one other component. In some embodiments, at least one of the above components may be split into more than one component.

For example, the communication interface 370 may include an interface 130 including a communication link to facilitate communication between the master device 110 and the controlled device 120, and the communication interface may also include a communication processor to facilitate communication from the UE to PWN 140 connection.

The bus 310 may include, for example, a circuit that interconnects the components 310 to 370 and transmits communication signals (eg, control messages and / or data) between the components 310 to 370.

The processor 320 may include one or more of a central processing unit (CPU), an application processor (AP), and a communication processor (CP). The processor 320 may, for example, perform operations or data processing regarding control and / or communication of at least one other component of the UE 301.

Here, the processor 320 may maintain overall control as necessary to provide communication services via the PWN 140. The processor 320 may perform differentiated control depending on whether the UE 301 has access rights to the PWN 140. If the UE 301 has access rights to the PWN 140, the processor 320 will perform control associated with a master device (eg, the master device 110). Conversely, if the UE 301 does not have access rights to the PWN 140, the processor 320 will perform the control associated with the controlled device (eg, the controlled device 120).

Assuming that the UE 301 has access rights to the PWN 140 (for example, the UE 301 is the master device), the processor 320 may use the SII 220 as read by the processor 320 to access the PWN 140 in order to control the storage of wireless communication services. take. In addition, the processor 320 may form a communication link to another UE (eg, UE 302 or 304) via the communication interface 370, and provide the NAI 210 to another UE (eg, UE 302 or 304) via the formed communication link. ).

Assuming that the UE 301 does not have access to the PWN 140 (for example, the UE is a controlled device), the processor 320 may form a communication link to another UE (for example, the UE 302 or 304) via the communication interface 370, and A NAI 210 provided from another UE (eg, UE 302 or 304) is received via the formed communication link. In this case, the processor 320 may access the PWN 140 using the NAI 210 provided from another UE (eg, the UE 302 or 304) in order to establish and maintain a wireless communication service.

The memory 330 may include a volatile memory and / or a non-volatile memory (NVM). In a functional sense, the memory may further include, for example, a SIM card connected to the main control device 110. The memory 330 may be used to store, for example, various commands and / or data related to at least one other component of the UE 301. In one embodiment, the memory 330 may store the NAI 210. The NAI 210 may be stored in a memory 330 used to access the PWN 140.

The I / O interface 350 may, for example, serve as an interface capable of sending commands and / or data received from a user or another external UE to other components of the UE 301. The I / O interface 350 may output commands or data received from other components of the UE 301 to a user or another external UE.

The display module 360 may include, for example, a liquid crystal display (Liquid Crystal Display; LCD) display, a light emitting diode (Light Emitting Diode; LED) display, an organic LED (Organic LED; OLED) display, and a micro electro-mechanical system (Micro Electro- Mechanical System (MEMS) display or electronic paper display. The display module 360 may, for example, display various contents (for example, text, image, video, icon, symbol, or the like) for the user. The display module 360 may include a touch screen, and may receive a touch input, a gesture input, a proximity input, or a hover input by, for example, an electronic pen or a part of a user's body.

The communication interface 370 may establish communication between, for example, the UE 301 and an external UE (for example, the first external UE 302, the second external UE 304, or the server 306). For example, the communication interface 370 may be connected to the network 362 via wired or wireless communication to communicate with an external UE (eg, the second external UE 304 or the server 306). The communication interface 370 may communicate with an external UE (eg, the first external UE 302) via wireless or wired communication 364.

The communication interface 370 may support wireless communication services by connecting to a network 362 (eg, PWN 140). The communication interface can use SII 220 or NAI 210 to access the network.

The communication interface 370 may establish a communication link to an external UE (for example, the first external UE 302, the second external UE 304, or the server 306), and perform communication to communicate from the external UE (for example, the first The external UE 302, the second external UE 304, or the server 306) obtains the NAI 210.

The wireless or wired communication 364 may include, for example, at least one of LTE, LTE-A, CDMA, WCDMA, UMTS, WiBro, and GSM as a cellular communication protocol. Wireless or wired communication 364 may be wired and may include, for example, Universal Serial Bus (USB), High Definition Multimedia Interface (HDMI), and Recommended Standard 232 (RS-232) And at least one of the Plain Old Telephone Service (POTS). The network 362 may include, for example, a computer network (for example, a local area network (LAN) or a wideband local area network (WLAN)), an internet network, and a telecommunications network for a telephone network At least one of the roads.

Each of the first external UE 302 and the second external UE 304 may be equal to the UE 301 in type or different from the UE 301 in type (eg, receiver performance). In one embodiment, the server 306 may be a group of one or more servers. In various embodiments, all or some of the operations performed in UE 301 may be performed in other UEs (eg, UEs 302 and 304, or server 306). In one embodiment, if the UE 301 should perform any function or service automatically or on request, the UE 301 may additionally request another UE (eg, UE 302 and 304, or server 306) to perform one or more related to this Rather than the UE 301 itself performing one or more functions or services. Another UE (eg, UEs 302 and 304, or server 306) may perform one or more functions and / or services requested, and provide the result to UE 301. The UE 301 may provide the requested function or functions and / or services by using the complete received result or by otherwise processing the received result. For this purpose, for example, cloud computing, decentralized computing, or client-server computing can be used.

FIG. 4 is a block diagram further illustrating a user equipment usable in a network environment according to some embodiments of the inventive concept in another example.

Referring to FIG. 4, the UE 401 may include, for example, all or part of the UE 301 illustrated in FIG. 3. The UE may include one or more AP 410, communication module 420, SIM card 428, memory 430, sensor module 440, input device 450, display 460, interface 470, audio module 480, and camera module 491, power management module 495, battery 496, indicator 497, motor 498, and the like.

The AP 410 can control multiple hardware or software components connected to the AP 410 by driving, for example, an operating system (OS) or an application, and can perform various data processing and calculations. The AP 410 may be implemented as, for example, a system on chip (SoC). In one embodiment, the AP 410 may further include a graphic processing unit (GPU) and / or an image signal processor (ISP). The AP 410 may include at least some of the components (eg, the communication processor 423) illustrated in FIG. 4. The AP 410 can load commands or data received from at least one of other components (for example, non-volatile memory (NVM)) in volatile memory, process the loaded data, and store a variety of data in NVM in. The application processor 410 may control the operation of the UE 401 by selectively executing an operating system component, a driver component, and an application component. The application processor 410 may send the NAI 210.

The communication module 420 may be structurally equivalent to or similar to the communication interface 370 in FIG. 3. The communication module 420 may include, for example, a wired connectivity unit 421, a communication processor 423, a wireless connectivity unit 424, a BT module 425, a GPS module 426, an NFC module 427, and a radio frequency (RF) module 422.

The communication module 420 can use the SII 220 to connect to the communication service via the PWN 140, execute an action status transmission layer to generate the NAI 210, and store the NAI 210 in the memory 430.

The communication processor 423 may provide, for example, a voice call service, a video call service, a text service, an Internet service, or the like via a communication network. In one embodiment, the communication processor 423 may use the SII 220 and / or NAI 210 recorded in the SIM (for example, the SIM card 428) to perform the identification and authentication operations of the UE 401 in the communication network. NAI 210 may be provided from another UE (eg, UEs 302 and 304) and recorded in an allocated area in memory 330.

The communication processor 423 may perform at least some of the functions that the AP 410 may provide.

Each of the wireless connectivity unit 424, the BT module 425, the GPS module 426, and the NFC module 427 may include a processor for processing data transmitted / received via, for example, the module itself. In one embodiment, any of the wireless connectivity unit 424, the BT module 425, and the NFC module 427 may be used to communicate with another UE (eg, UEs 302 and 304). Any of the wireless connectivity unit 424, the BT module 425, and the NFC module 427 can obtain NAI 210 to be used during access to the PWN 140 by communicating with another UE (e.g., UE 302 and 304). .

In some cases, at least some (eg, at least two) of the communication processor 423, the wireless connectivity unit 424, the BT module 425, the GPS module 426, and the NFC module 427 may be incorporated into an integrated chip. chip; IC) or IC package.

The RF module 422 may, for example, transmit / receive a communication signal (for example, an RF signal). The RF module 422 may include, for example, a transceiver, a Power Amp Module (PAM), a frequency filter, a Low Noise Amplifier (LNA), an antenna, or the like. In another embodiment, at least one of the communication processor 423, the wireless connectivity unit 424, the BT module 425, the GPS module 426, and the NFC module 427 may transmit / receive an RF signal via a separate RF module.

The SIM card 428 may include, for example, a card equipped with a SIM and / or an embedded SIM that may contain uniquely identifying information (eg, ICCID 225) or information identifying a user (eg, IMSI 221). The SIM card 428 may include a portion of the memory 430.

The memory 430 may include, for example, an internal memory 432 or an external memory 434. The internal memory 432 may include, for example, volatile memory (for example, Dynamic RAM (DRAM), Static RAM (SRAM), Synchronous Dynamic RAM (SDRAM), etc.), non-volatile Memory (for example, One Time Programmable ROM (OTPROM), Programmable ROM (PROM), Erasable and Programmable ROM (EPROM)) Electrically Erasable and Programmable ROM (EEPROM), mask ROM, flash ROM, flash memory (eg, NAND flash memory or NOR flash memory At least one), a hard disk drive, and a solid state drive (SSD).

The external memory 434 may further include a flash drive (for example, Compact Flash (CF), Secure Digital (SD), Micro Secure Digital (micro SD), Micro Secure Digital (micro SD), Extreme Digital (xD), etc.) or memory stick. The external memory 434 may be functionally and / or physically connected to the UE 401 via various interfaces.

In one embodiment, the internal memory 432 or the external memory 434 included in the memory 430 may store the NAI 210 obtained from another UE (eg, UEs 302 and 304). For example, NAI 210 may include NSI 230, all or part of the SIM information (eg, SII 220), and the like. The NAI 210 may include RRC status information 233, NAS status information 237, and the like. The RRC status information 233 will be used by another UE (eg, UEs 302 and 304) for seamless connection to the PWN 140. NAS information 237 will be used by another UE (eg, UEs 302 and 304) to authenticate for its access to PWN 140. Some SIM information may include ICCID 225, IMSI 221, GUTI 229, TMSI 223, and the like.

The memory 430 may store a software component including an operating system component, a driver component, an application component, and a protocol stack component including a mobile status transmission layer.

The sensor module 440 may, for example, measure a physical quantity or detect an operating state of the UE 401, and convert the measured or detected information into an electrical signal. The sensor module 440 may include, for example, at least one of the following: a motion sensor 440A, a gyro sensor 440B, an atmospheric pressure sensor 440C, a magnetic sensor 440D, and an acceleration sensor 440E, grip sensor 440F, proximity sensor 440G, color sensor (eg, red / green / blue (RGB) sensor) 440H, biometric sensor 440I, temperature / humidity sensor 440J , Illuminance sensor 440K and ultraviolet (Ultra Violet; UV) sensor 440L. Additionally or alternatively, the sensor module 440 may include, for example, an electronic nose (E-nose) sensor, an electromyography (EMG) sensor, and an electroencephalogram (EEG) sensor Sensors, electrocardiogram (ECG) sensors, infrared (Infra Red) sensors, iris sensors, and fingerprint sensors.

The sensor module 440 may further include a control circuit for controlling at least one sensor belonging thereto. In some embodiments, the UE 401 may further include a processor configured to control the sensor module 440 as a part of the AP 410 or separately, so the UE 401 may control the sensing when the AP 410 is in a sleep state器 module440.

The input device 450 may include, for example, a touch panel 452, a (digital) pen sensor 454, a button 456, or an ultrasonic input device 458. The touch panel 452 can recognize a touch input by, for example, at least one of a capacitive method, a resistive method, an infrared method, and an ultrasonic method. The touch panel 452 may further include a control circuit. The touch panel 452 may further include a tactile layer to provide tactile feedback to the user.

The (digital) pen sensor 454 may be part of, for example, a touch panel, or may include a separate identification sheet. The keys 456 may include, for example, physical buttons, optical keys, or a keypad. The ultrasound input device 458 may check data by detecting an acoustic wave of a microphone (microphone; MIC) in the UE 401 using an input tool that generates an ultrasound signal.

The display 460 (eg, the display module 360) may include a panel 462, a hologram device 464, or a projector 466. The panel 462 may be structurally equivalent to or similar to the display module 360 in FIG. 3. The panel 462 may be implemented in, for example, a flexible manner, a transparent manner, or a wearable manner. The panel 462 and the touch panel 452 can be configured as a module. The hologram device 464 can display a stereoscopic image in the air using the interference of light. The projector 466 can display an image by projecting light onto a screen. The screen can be placed on the inner or outer surface of the UE 401. In one embodiment, the display 460 may further include a control circuit for one or more of the control panel 462, the hologram device 464, or the projector 466.

The interface 470 may include, for example, HDMI 472, USB 474, optical interface 476, or D-subminiature (D-sub) 478. The interface 470 may, for example, be incorporated into the communication interface 370 illustrated in FIG. 3. Additionally or alternatively, the interface 470 may include, for example, a Mobile High-definition Link (MHL) interface, a Secure Digital (SD) card / Multi-Media Card (MMC) interface, or infrared data Association (Infrared Data Association; IrDA) interface.

The audio module 480 can convert, for example, sound and electrical signals in both directions. At least some of the components of the audio module 480 may be incorporated into, for example, the I / O interface 350 illustrated in FIG. 3. The audio module 480 may process sound information received or output through, for example, a speaker (SPK) 482, a receiver 484, a headphone 486, or a microphone 488.

In one embodiment, the camera module 491, which is, for example, a device capable of capturing or capturing still images and videos, may include one or more image sensors (for example, a front sensor, a rear sensor). Or similar), lens, ISP, or flash (e.g., LED or xenon lamp).

The power management module 495 may, for example, manage power of the UE 401. In one embodiment, the power management module 495 may include a power management integrated circuit (PMIC), a charger integrated circuit (IC), or a battery gauge or fuel meter. The PMIC can have a wired charging scheme as well as a wireless charging scheme. The wireless charging scheme may include, for example, a magnetic resonance scheme, a magnetic induction scheme, an electromagnetic wave scheme, or the like, and the power management module 495 may further include additional circuits for wireless charging (for example, a loop coil, a resonance circuit, a rectifier, or the like) By). The battery gauge can measure, for example, the remaining capacity of the battery 496, the charging voltage, and the current or temperature. The battery 496 may include, for example, a rechargeable battery and / or a solar battery.

The indicator 497 may indicate a specific state (for example, an activation state, a message state, a charging state, or the like) of the UE 401 or a part thereof (for example, the AP 410). The motor 498 can convert electrical signals into mechanical vibrations, and can generate vibration or tactile effects. Although not shown, the UE 401 may include a processing unit (for example, a GPU) for supporting a mobile TV. The processing unit for supporting mobile TV can process media materials based on, for example, digital multimedia broadcasting (DMB), digital video broadcasting (DVB), media streams, or the like.

Each of the above-described components of the UE 401 according to various embodiments of the present disclosure may be configured as one or more components, and the names of the components may vary depending on the type of the UE. In various embodiments, the UE may be configured to include at least one of the components described above, and the UE may not include some of the components, or may further include additional other components. Some of the components of the UE according to various embodiments of the present disclosure may be configured as one entity by combining, thereby making it possible to perform the functions of the components in the same way, which may be performed before combining the components.

FIG. 5 is a block diagram further illustrating, in one example, a program module that can be used in some embodiments of the inventive concept.

Referring to FIG. 5, the program module 510 may include an operating system (OS) for controlling resources related to a UE (eg, UE 401) and / or various applications executing in the OS. The OS may include, for example, Android ™, iOS ™, Windows ™, Symbian ™, Tizen ™, Bada ™, or the like.

The program module 510 may include a core 520, an intermediate software 530, an API 560, and / or an application program 570. At least a part of the program module 510 may be pre-loaded in the UE or downloaded from a server (for example, the server 306). One or more of the core 520, the middleware 530, and the API 560 may be functionally "called" by the OS.

The core 520 may include, for example, a system resource manager 521 or a device driver 523. The system resource manager 521 can be used to perform control, allocation, or reclamation of system resources. In one embodiment, the system resource manager 521 may include a process manager, a memory manager, a file system manager, or the like. The device driver 523 may include, for example, a display driver, a camera driver, a Bluetooth driver, a shared memory driver, a USB driver, a keypad driver, a Wi-Fi driver, an audio driver, or inter-process communication (Inter-process communication; IPC) driver.

The middleware 530 may, for example, serve as an intermediary such that the API 560 or the application 570 may communicate with the core 520 to exchange data. The middleware 530 may provide, for example, functions normally required by the application 570, or may provide various functions to the application 570 via the API 560, so that the application 570 may efficiently use limited system resources in the UE. In one embodiment, the middleware 530 may include at least one of the following: runtime library 535, application manager 541, window manager 542, multimedia manager 543, resource manager 544, power manager 545, The library manager 546, the package manager 547, the connectivity manager 548, the notification manager 549, the location manager 550, the graphics manager 551, and the security manager 552.

The runtime library 535 may include, for example, a library module used by a compiler to add new functions through a programming language when the application program 570 is executed. The runtime library 535 can perform I / O management, memory management, or functions for arithmetic functions.

The application manager 541 may manage, for example, a life cycle of at least one of the applications 570. The window manager 542 can manage GUI resources used on the screen. The multimedia manager 543 may determine a format required for playback of various media files, and perform encoding or decoding of the media file using a codec for the format. The resource manager 544 can manage source code for at least one of the applications 570 and resources for memory or storage space.

The power manager 545 may manage a battery or power by operating with, for example, a basic input / output system (BIOS), and provide power information required for the operation of the UE. The database manager 546 may create, search, or change a database to be used by at least one of the applications 570. The package manager 547 can manage the installation or update of applications distributed in the form of package files.

The connectivity manager 548 may manage, for example, Wi-Fi or Bluetooth wireless connectivity. The notification manager 549 can be used to display or notify, such as message arrivals, appointments, and proximity alerts, in a manner that does not disturb the user. The location manager 550 may be used to manage location information of the UE. The graphics manager 551 can be used to manage graphics effects to be provided to a user, or a user interface associated therewith. The security manager 552 can be used to provide various security features required for system security or user authentication. In one embodiment, if the UE (eg, UE 301) includes a phone function, the middleware 530 may further include a phone manager for managing voice or video call features of the UE.

The intermediate software 530 may include an intermediate software module that forms a combination of various functions of the above components. The middleware 530 may provide modules specific to the type of the OS to provide differentiated functions. The middleware 530 may dynamically remove some of the existing components or add new components.

Depending on the OS, the API 560, for example, a set of API stylized functions, may be provided in different combinations. For example, the API 560 may provide one API set for each platform in Android or iOS, and provide two or more API sets for each platform in Tizen.

The application program 570 may include one or more applications capable of providing functions such as: homepage 571, dial pad 572, Short Message Service (SMS) / Multimedia Messaging Service (MMS) 573, real-time Instant Message (IM) 574, Browser 575, Camera 576, Alarm 577, Contact 578, Voice Dial 579, Email 580, Calendar 581, Media Player 582, Photo Album 583, Clock 584, Health (eg , Measurements of exercise volume, blood glucose, etc.) and environmental information (for example, the provision of atmospheric pressure, moisture, or temperature information).

In one embodiment, the application program 570 may include an application program (hereinafter, referred to as 'information' for convenience of information) between a UE (eg, UE 301) and an external UE (eg, UEs 302 and 304). Exchange applications'). The information exchange application may include, for example, a notification relay application for relaying specific information to external UEs, or a device management application for managing external UEs, or may include NAI 210 for accessing PWN 140.

For example, the notification relay application may include sending notification information generated by other applications in the UE (e.g., SMS / MMS application, email application, health care application, environmental information application, or the like) to Functions of external UEs (eg, UEs 302 and 304). The notification relay application may, for example, receive notification information from an external UE and provide the received notification information to a user. The device management application may, for example, manage the brightness of the display of at least a portion of the function (eg, the enabling / deactivation of the external UE itself or some of its components, or an external UE (eg, UE 304) for communicating with the UE) Or resolution adjustment), or an application that manages (e.g., installs, deletes, or updates) an external UE or services provided by an external UE (e.g., call service or messaging service).

In one embodiment, the application 570 may include an application (eg, a healthcare application) specified depending on the nature of the external UE (eg, UEs 302 and 304) (eg, the nature of the UE, and the type of the UE is a mobile medical device) Program). In one embodiment, applications 570 may include applications received from external UEs (eg, server 306 or UEs 302 and 304). In one embodiment, the application 570 may include a pre-loaded application, or a third-party application that can be downloaded from a server. The names of the components of the program module 510 according to the illustrated embodiment may vary depending on the type of the OS.

In various embodiments, at least a portion of the program module 510 may be implemented by software, firmware, and / or hardware. At least a portion of the program module 510 may be implemented (or executed) by, for example, a processor (eg, AP 410). At least a portion of the program module 510 may include, for example, a module, a program, a routine, an instruction set, or a processing sequence for performing one or more functions.

The term 'module' as used herein may refer to a unit comprising any one or combination of hardware, software, and firmware. The term 'module' is used interchangeably with terms such as 'unit', 'logic', 'logical block', 'component' or 'circuit'. A 'module' can be the smallest unit or part of an integrated component. A 'module' may be the smallest unit or part thereof that performs one or more functions. The 'module' can be implemented mechanically or electronically. For example, a 'module' may include an application-specific integrated circuit (ASIC) chip, a field-programmable gate array (FPGA), and a programmable logic device. At least one of them, each of them performs any operation known or to be developed in the future.

At least a portion of a device (eg, a module or its function) or method (eg, an operation) according to various embodiments of the present disclosure may be, for example, instructions stored in a computer-readable storage medium in the form of a programmed module Implementation. If the instructions are executed by one or more processors (eg, the processor 320), the one or more processors may perform functions corresponding to the instructions. The computer-readable storage medium may be, for example, the memory 430.

Computer-readable storage media may include magnetic media (for example, hard disks, floppy disks, magnetic tapes, etc.), optical media (for example, Compact Disc Read Only Memory (CD-ROM), digital versatile discs (Digital Versatile Disc (DVD), etc.), magnetic-optical media (eg, magneto-optical discs, etc.), and hardware devices (eg, Read Only Memory (ROM), Random Access Memory (Random Access Memory) ; RAM), flash memory, etc.). Program instructions can include not only machine code created by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. The hardware device may be configured to operate as one or more software modules to perform operations in various embodiments of the present disclosure, and vice versa.

The module or program module according to various embodiments may include at least one of the components described above, and the module or program module may not include some of the components, or may include additional other components. Operations performed by modules or program modules or by other components according to various embodiments may be performed sequentially, in parallel, repeatedly, and / or tentatively. Some operations may be performed in a different order, or may be omitted, or other operations may be added.

FIG. 6 is a block diagram illustrating various connections between a plurality of UEs using a communication service via PWN 140 according to an embodiment of the inventive concept.

Referring to FIG. 6, as an example, multiple UEs include a first master control device 620, a controlled device 630, and a second master control device 640. The first master control device 620 may contain a SIM 624, the second master control device 640 may contain a SIM 644, and the controlled device 630 may not have a SIM, but may have an NVM 634. SIM 624 and 644 may contain access authorization authentication (eg, SII 220) to connect to communication services via PWN 140, but the controlled device may lack access authorization authentication internally to connect to communication services via PWN 140.

The first master device 620 may have a first SII (1SII) stored in the SIM 624 and may be connected to a first communication service. The first master control device 620 may generate a first NSI (1NSI) associated with the connection of the first communication service, and may derive a first NAI (1NAI) from the 1SII and the 1NSI. The first master control device 620 may establish a first communication link (eg, a wireless connectivity link 650) between the first master control device 620 and the controlled device 630.

The second master device 640 may have a second SII (1SII) stored in the SIM 644, and may be connected to a second communication service. The second master control device 640 may generate a second NSI (2NSI) associated with the connection of the second communication service, and may derive a second NAI (2NAI) from the 2SII and 2NSI. The second master control device 640 may establish a second communication link (eg, a wired connectivity link 660) between the second master control device 640 and the controlled device 630.

The first master control device 620 may send the 1NAI to the controlled device 630 through the first communication link (for example, the wireless communication link 650), and the controlled device 630 may store the 1NAI in the controlled device 630 (for example, NVM 634). The second master control device 640 may send the 2NAI to the controlled device 630 via the second communication link (eg, the wired communication link 660), and the controlled device 630 may store the 2NAI in the controlled device 630 (eg, NMV 634 )in.

Therefore, the controlled device 630 may connect to the first communication service via the PWN 140 using 1NAI, and the first communication service may be terminated in the first master control device 620. PWN 140 will not allow multiple UEs to access PWN 140 using the same SII. The controlled device 630 may generate an updated 1NAI during connection to a first communication service in the controlled device 630, and may communicate between the controlled device 630 and the first via the first communication link (eg, the wireless communication link 650). The main control device 620 synchronizes the updated 1NAI.

For example, the controlled device 630 may receive data from the first communication service via the PWN 140, and the controlled device 630 may relay the data from the controlled device 630 via the first communication link (eg, a wireless communication link). To the first main control device 620. The controlled device 630 may connect to the second communication service via the PWN 140 using 2NAI, and the second communication service may be terminated in the second master control device 640. The controlled device 630 may generate an updated 2NAI during the connection of the second communication service in the controlled device 630, and may communicate between the controlled device 630 and the second via the second communication link (eg, the wired communication link 660). The main control device 640 synchronizes the updated 2NAI.

In addition, the second communication service may be terminated in the second master control device 640, the controlled device 630 may receive data from the first communication service, and the controlled device may relay data from the controlled device to at least two devices ( It includes a first master control device 620 via a first communication link and a second master control device 640 via a second communication link). The first master device 620, the second master device 640, and the controlled device 630 may support the use of a common communication service via the PWN 140.

Even if the controlled device 630 is connected to the PWN 140 and the first master control device 620 and the second master control device 640 are no longer connected to the PWN 140, the user can still enjoy by using the first master control device 620 and the second master control device 640 Communication services via controlled devices. The first master control device 620 and the second master control device 640 can enjoy communication services via the controlled device via a communication link (eg, wireless communication link 650, wired communication link 660).

If the two master devices 620 and 640 have the same SII 220, the controlled device 630 can receive the NAI 210 from only one of the two master devices 620 and 640. In this case, if the controlled device 630 has accessed the PWN 140, the access to the PWN 140 for both of the two master devices 620 and 640 may be released or may not be permitted.

As described above, the plurality of UEs 620, 630, and 640 may include communication processors 622, 632, and 642, respectively, and a connectivity unit. The connectivity unit may include wireless connectivity units 626, 636, and 646, and wired connectivity units 628, 638, and 648.

The communication processors 622, 632, and 642 may support operations that allow their UEs to use communication services via the PWN 140. Each of the wireless connectivity units 626, 636, and 646 can support the operation of the UE forming a wireless connectivity link 650 to another UE based on a predetermined wireless communication protocol, and transmit / receive information via the formed wireless connectivity link 650 (for example, NAI 210, NSI 230, modem status information, etc.). The wired connectivity units 628, 638, and 648 can each support the operation of the UE forming a wired connectivity link 660 to another UE based on a predetermined wired communication protocol, and transmitting / receiving information via the formed wired connectivity link 660 (for example, NAI 210, NSI 230, modem status information, etc.). The wireless connectivity link 650 may be expressed as a 'connectivity interface' or a 'wireless interface'. The wired connectivity link 660 may be expressed as a 'cable interface' or a 'wired interface'.

The wireless connectivity unit 636 in the controlled device 630 may provide the NSI 230 (eg, modem status information) to the master control device 620 via the wireless connectivity link 650. The wired connectivity unit 638 in the controlled device 630 may provide the NSI 230 (eg, modem status information) to the master control device 640 via the wired connectivity link 660. The NSI 230 may be provided to the master devices 620 and 640 only if the communication service attributed to the PWN 140 changes the NSI 230.

For example, after an event corresponding to at least one of the following occurs, the NSI 230 may be provided to the master control devices 620 and 640: inter-cell delivery, change of cell identification information, change of TMSI 223, master Changes in physical proximity between the control device and the controlled device, changes in power conditions for the master control device and one of the controlled devices, and the connectivity of the communication link between the master control device and the controlled device change.

The main control devices 620 and 640 may update the existing NSI using the NSI provided from the controlled device 630.

After requesting access to the PWN 140, the master devices 620 and 640 may instruct the controlled device 630 to terminate the communication service. In response to the command, the controlled device 630 may release its access to the PWN 140. In this way, the master devices 620 and 640 can access the PWN 140 using the updated NSI.

FIG. 7 is a block diagram illustrating various components of a master device according to an embodiment of the inventive concept in one example.

Referring to FIG. 7, the main control device 700 may include a communication processor 710, a SIM card 720, a connectivity unit 730, and an application processor 740. The communication processor 710 may have information to be used to access the PWN 140. For example, the communication processor 710 may include NSI 230 (for example, RRC status information 233, NAS information 237) and SII 220 (for example, all or part of SIM information) to connect to a communication service via PWN 140. For the components of the main control device 700, only the components required for various embodiments of the present disclosure are illustrated in the drawings.

The communication processor 710 can access (or read) the SII 220 recorded in the SIM card 720, and can access the PWN 140 using the read SII 220. The SIM card 720 can record various information such as ICCID 225, IMSI 221, GUTI 229, and TMSI 223 as SII 220.

If the communication processor 710 is successfully connected to the communication service via the PWN 140, the communication processor 710 may transmit / receive information (eg, application data, etc.) associated with the communication service via the PWN 140. The communication processor 710 may generate and update the NSI 230 such as RRC status information 233 and NAS information 237, which correspond to access to a cellular network and communication services via a communication service via a connection via the PWN 140.

The communication processor 710 may send the NSI 230 and all or part of the SII 220 to the connectivity unit 730 so that the NAI 210 may be provided to the controlled device.

The connectivity unit 730 may include a wireless communication module, a wired communication module, and the like. The wireless communication module may allow the main control device 700 to form a wireless link to the controlled device based on a predetermined wireless communication protocol, and transmit / receive information (e.g., NAI 210, NSI 230, modem status information, Application data, etc.). The wired communication module may allow the main control device 700 to form a wired link to the controlled device based on a predetermined wired communication protocol, and transmit / receive information (e.g., NAI 210, NSI 230, modem status information, Application data, etc.).

The NAI 210 may provide the connectivity unit 730 with information to the controlled device. The NAI 210 may be configured by the connectivity unit 730 using the NSI 230 provided from the communication processor 710 and all or part of the SII 220. The NSI may include RRC status information 233 and NAS information 237. RRC status information 223 will be used by the controlled device for seamless connection to PWN 140, and NAS information 237 will be used by the controlled device for authentication.

The modem status information may be an instance of the NSI 230 that the connectivity unit 730 has received from the controlled device. The modem status information may be information related to a communication environment in which the controlled device uses a communication service via the PWN 140. For example, the modem status information may include information about changes in the communication environment, such as inter-cell handovers, changes in cell identification information, and changes in TMSI 223. When the master device accesses the PWN 140 and / or uses a communication service via the PWN 140, the modem status information can be used by the master device.

Application data can be provided by the master device to or received from the controlled device. For example, for the application data that the master device will provide to the controlled device, the communication processor 710 may receive the application data from the PNW 140 and provide the received application data through the application processor 740. The application data provided to the controlled device may include information based on which master device 700 controls the controlled device. The application data provided from the controlled device may be provided to the application processor 740 or may be passed to the communication processor 710 via the application processor 740. The application data received from the controlled device may contain information about the processing results of an operation performed by the controlled device.

For the overall operation of the master device 700, the application processor 740 may control the components of the master device 700. The application processor 740 may perform a control operation that processes information provided from the communication processor 710 and information provided from the connectivity unit 730.

FIG. 8 is a block diagram illustrating various components of a controlled device according to an embodiment of the inventive concept, in one example.

Referring to FIG. 8, the controlled device 800 may include a communication processor 810, a connectivity unit 820, and an application processor 830. For the components of the controlled device 800, only the components required for various embodiments of the present disclosure are illustrated in the drawings.

The communication processor 810 may have at least one type of NAI 210 to be used for accessing the PWN 140. The communication processor 810 may include the NAI 210 individually for each master device. As illustrated, it may be noted that the communication processor 810 may receive and manage NAI 210 (eg, 210a, 210b, 210c, 210d) from four master devices. The communication processor 810 may receive the NAI 210 via the connectivity unit 820.

The communications processor 810 may select one of the stored NAIs 210 and attempts to access the PWN 140 using the selected NAI.

If the communication processor 810 is successfully connected to the PWN 140, the communication processor 810 may transmit / receive information (eg, application data, etc.) associated with a communication service via the connected PWN 140. The communication processor 810 may generate and update NSI 230 such as RRC status information 233 and NAS information 237, which correspond to access to a common or different communication service of the cellular network and the connected PWN 140.

The connectivity unit 820 may include a wireless communication module, a wired communication module, and the like. The wireless communication module may allow the controlled device 800 to form a wireless link to at least one master device based on a predetermined wireless communication protocol, and transmit / receive information (e.g., NAI 210, NSI 230, modem status) via the formed wireless link. Information, app data, etc.). The wired communication module may allow the controlled device 800 to form a wired link to the master control device based on a predetermined wired communication protocol, and transmit / receive information (e.g., NAI 210, NSI 230, modem status information, Application data, etc.).

NAI 210 may include NSI 230, all or part of SII 220, and the like. The NSI 230 may include RRC status information 233 'RRC info', NAS information 237 'NAS info', and the like. The RRC status information 233 will be used by the controlled device for seamless connection to the PWN 140, and the NAS information 237 will be used by the controlled device for authentication. All or part of the SII 220 may include ICCID 225, IMSI 221, GUTI 229, TMSI 223, and the like.

The modem status information may provide an example of the NSI 230 of the master unit from the connectivity unit 820. The modem status information may be information related to a communication environment in which the controlled device uses a communication service via the PWN 140. For example, the modem status information may include information about changes in the communication environment, such as inter-cell handovers, changes in cell identification information, and changes in TMSI 223. The modem status information can be used by the master device to access the PWN 140 and / or use communication services via the PWN 140.

The application data can be data that the connectivity unit 820 can provide to the master control device or the autonomous control device. For example, for the application data that the controlled device will provide to the master device, the application data may be received from the PWN 140 and passed by the communication processor 810, or may be provided by the application processor 830. The application data provided to the master device may contain information about the processing results of an operation performed by the controlled device. Application data provided by the autonomous control device may be provided to the application processor 830 or the communication processor 810. The application data provided by the autonomous control device may include information based on which master control device controls the controlled device 800.

For the overall operation of the controlled device 800, the application processor 830 may control the components of the controlled device 800. The application processor 830 may perform a control operation that processes information provided from the communication processor 810 and information provided from the connectivity unit 820.

FIG. 9 is a flowchart outlining a control flow in a master control device according to an embodiment of the inventive concept.

Referring to FIG. 9, in operation 910, the master device may access the PWN 140 and provide a communication service via the connected PWN 140. The master device can access the PWN 140 by connecting the SIM in the master device, reading the SII 220 from the SIM, storing the SII 220 in the master device, and connecting the stored SII to a communication service. The master device can access the PWN 140 by using the stored access authorization credentials.

In operation 912, the master device may generate or update the NSI 230 associated with the provision of communication services via the PWN 140. In addition to RRC information 233, NSI 230 may also include physical information. The entity information may include cell identification information (cell ID) 231. In addition to NSI 230, some or all of SII 220 can also be generated and updated. SII 220 may include paging information (IMSI 221 or TMSI 223) and the like. The master device can derive the NAI 210 from the access authorization certificate (eg, some or all of the SII 220) and the NSI 230. The master device may store the NSI 230 or NAI 210 in the master device before terminating the communication service in the master device.

In operation 914, the master device may determine whether there is a need to provide the NAI 210 to the controlled device. The determination may be made in response to a request from a user, the occurrence of a situation where the master control device may no longer provide communication services, or a request from the controlled device.

If there is a request for delivery of NAI 210, the master device may connect the communication link to at least one controlled device in operation 916. For the connection of the communication link, the master control device can determine whether to enable its connectivity unit and the connectivity unit installed in the controlled device. The communication link may include a wireless link using a wireless resource, or a wired link using a wired resource such as a cable. For example, wireless links may be connected using wireless communication protocols such as Wi-Fi, Bluetooth, and NFC.

If connectivity is not available in the master device, the master device can switch on connectivity. The master device can confirm whether the correct controlled device can be connected. If the correct controlled device can be connected, the master device can set the connectivity (that is, set the connection in Wi-Fi or Bluetooth to find the location of the two devices within the connectable proximity in NFC) .

The master device can receive a first signal containing information on whether the controlled device can be connected to the master device via connectivity (Wi-Fi, BT, NRF, etc.). The master control device may receive a second signal containing information on whether the controlled device is capable of connecting to the PWN 140. The first signal and the second signal may be the same signal, may be distinct signals, or may be combined into one signal.

If the master control device meets a predetermined condition, the master control device may execute a communication link connection procedure with the controlled device in operation 916. Similarly, if the controlled device meets a predetermined condition, the controlled device may also execute a communication link connection procedure with the master control device.

In one embodiment, the predetermined condition may be a communication environment condition where the master device and the controlled device can establish a communication link and exchange information via the formed communication link. The communication environmental conditions may vary depending on the type of communication protocol to be used to form the communication link. The predetermined condition may be set in advance for each communication protocol to be used. For example, communication protocols can be divided into wired communication protocols and wireless communication protocols. A wireless communication protocol that is a protocol supporting a communication link may be a protocol defined for Wi-Fi, NFC, BT, and the like.

In order to determine whether the communication environment meets a predetermined condition, the master device or the controlled device may use its received signal strength and its at least one sensor. In addition, the determination of whether the communication environment meets predetermined conditions can be replaced by monitoring whether a user's request is received.

For the master device, if its communication link to at least one controlled device is connected, the master device can pass the operation data (downlink data) received from the PWN 140 to the at least one controlled device via the communication link . Conversely, the master device may transmit the operation data (uplink data) received from at least one controlled device to the PWN 140 via a communication link, and relay this data or data derived therefrom. Therefore, in one aspect of the concept of the present invention, the download relay can be understood as proceeding from PWN to the controlled device to the master control device, and the upload relay can be understood as proceeding from the autonomous control device to the controlled device to PWN. For example, suppose a user wants to download a very large amount of data (for example, a movie) from his PWN to his master control device, then downloading the corresponding data via a powerful controlled device can be compared to downloading the corresponding data directly to the master Installation is good (for example, efficient).

If the master device is connected to the communication link of the at least one controlled device, the master device may transmit the NAI 210 via the connected communication link in operation 918. NAI 210 may include NSI 230 and SII 220. The NSI 230 may include RRC status information 233, NAS status information 237, and the like. The RRC status information 233 will be used by the at least one controlled device for seamless connection to the cellular network, and the NAS information 237 will be used by the at least one controlled device to authenticate access to the PWN 140. The SII 220 may include all or part of the SII recorded in the SIM card of the master device. Part of the SII may be any of ICCID 225, IMSI 221, GUTI 229, and TMSI 223. SII 220 may include information derived from at least one of a plurality of SII components. The SII 220 may include a TMSI 223 provided from the PWN 140 to the master device after connecting a communication service in the master device.

The provision of the NAI 210 to the controlled device may mean that the master device has approved the controlled device's access to the PWN 140. In this case, the master device may block a communication service that the master device is already using by the PWN 140.

The NAI 210 common program can be initiated by a command from the master device or by a request from the controlled device.

After transmitting the NAI 210 to at least one controlled device, the master device may release access to the PWN 140 (eg, terminate the connection of the communication service in the master device) in operation 920. The reason why the master device releases access to the PWN 140 is to prevent a situation where the master device attempts to access the PWN 140 together with at least one controlled device that has received the NAI 210. For example, when the master device disables its communication processor or enters a sleep mode, it can release access to the PWN 140. After the access to the PWN 140 is released, the master device can use the communication service via the communication link only.

After the communication service in the master device is terminated, the master device can listen to the communication service without transmitting via the communication service via the master device. Listening involves continuously monitoring the need for communication services connected to the master device.

In operation 922, the master device may synchronize one or more components of the NAI 210 (eg, NSI 230, modem status information) updated by the controlled device that accesses the PWN 140 and uses the communication service. The synchronization of the NAI 210 is to match the operation of the NAI 210 stored in the master device and the NAI 210 stored in the controlled device. To this end, the master control device may receive the NAI from the controlled device via the communication link, and update the existing NAI with the received NAI. This operation can be synchronized for NAI 210.

Synchronization for NAI 210 enables the master device to easily reconnect to PWN 140. In other words, if the NAI 210 is synchronized, the master device can use the NAI 210 to quickly re-access the PWN 140.

Synchronization for NAI 210 may be performed periodically or after a predetermined event occurs. The predetermined event may correspond to at least one of the following: inter-cell delivery, change in cell identification information, change in TMSI 223, change in physical proximity between the master device and the controlled device, and for master Changes in power conditions of one of the device and the controlled device, and changes in connectivity of the communication link between the master device and the controlled device.

The controlled device can be in standalone mode or relay mode. If the controlled device is in the independent mode, the controlled device replaces the master device and the controlled device accesses the PWN 140 on behalf of the master device, and the controlled device receives data from the PWN 140. NAI 210 is synchronized between the controlled device and the master device, but data (eg, uplink data, downlink data) is not synchronized between the controlled device and the master device.

In operation 924, if the controlled device is in the relay mode, the master control device transmits uplink data to the controlled device and receives downlink data from the controlled device. With the exception of NAI 210, this is being synchronized between the controlled device and the master device. The master device can transmit the uplink data to the controlled device via the communication link, and thereafter, the controlled device can relay the data to the communication service. The master device may receive downlink data from the controlled device via the communication link that the controlled device may have received from the communication service. The relay mode may allow multiple UEs (eg, the master device) to transmit data uplink to and from the PWN 140 downlink via the controlled device. Relay mode may allow UEs with poor characteristics (eg, lower performance receivers, transmitters, or batteries) to pass through devices (eg, controlled devices) ) Access PWN 140.

In operation 926, the master device may continuously monitor whether there is a demand for accessing the PWN 140. Although the master device is not transmitting directly via the PWN 140, the master device can listen to communication services without transmitting. Situations where there is a need to access the PWN 140 may arise in response to a user's request, a paging from the PWN 140, a request from a controlled device, and the like.

In one embodiment, the master control device may receive a report from the controlled device connected to the PWN 140 indicating the termination of the communication service via the PWN 140. In this case, the master device may resume the blocked communication service via the PWN 140.

In one embodiment, the master device may instruct the controlled device to release its access to the PWN 140 according to its own requirements. The master device may send a command to release access to the PWN 140 via a communication link connecting the master device to the controlled device.

For example, when an event requiring access to the PWN 140 occurs, the master control device may instruct the controlled device to release its access to the PWN 140. In response to the command, the controlled device will terminate the communication service that the controlled device is already using via PWN 140. The controlled device needs to report its termination of the communication service to the master device. After receiving the report indicating the termination of the communication service, the master device may attempt to access the PWN 140. In this case, the master can consider the updated NSI 230.

The master device shall be able to restore (or revoke) the controlled device's access to the PWN 140. As one example, in operation 928, the master device may send a command to the controlled device to terminate the communication service via the PWN 140 via the communication link. In response to the command, the master control device may receive a report from the controlled device indicating the termination of the communication service.

In operation 930, the master device may re-access the PWN 140 using the NAI 210 or the NSI 230 through the synchronous update. If the PWN 140 is re-accessed, the master device may provide a communication service via the PWN 140 in operation 934.

Although not illustrated in FIG. 9, after receiving a report indicating the termination of the communication service from the controlled device, the master device may resume the blocked communication service via the PWN 140.

In one embodiment, a master device shares a NAI 210 with a controlled device. It will be apparent to those skilled in the art that, as another example, according to the procedure illustrated in FIG. 9, one master device may share the NAI 210 with multiple controlled devices. Further, it can be assumed that one controlled device receives NAI 210 from each of a plurality of master devices. In this case, one controlled device may select one of a plurality of NAI 210 and utilize a communication service via PWN 140 using the selected NAI 210. Although only one hypothetical physical controlled device exists in the foregoing example, the controlled device is actually an operational combination of multiple controlled devices, where multiple NAIs are stored and selectively used to establish and maintain via PWN One or more communication services. In addition, it is also possible for one controlled device to establish multiple communication services on behalf of multiple controlled devices, and each controlled device has transmitted the corresponding NAI to the controlled device. In this way, a controlled device can act as a powerful "public device" with the ability to relay data to multiple users at a relatively high data rate.

FIG. 10 is a flowchart outlining a control flow for operation of the system according to an embodiment of the inventive concept.

Referring to FIG. 10, in operation 1010, the controlled device may connect a communication link to the master device in response to a user's request or a request from the master device. For the connection of the communication link, the controlled device can determine whether its connectivity unit and the connectivity unit installed in the master control device are enabled. The controlled device determines whether the controlled device can be connected to the master control device. The communication link may include a wireless link using a wireless resource, or a wired link using a wired resource such as a cable. For example, wireless links may be connected using wireless communication protocols such as Wi-Fi, Bluetooth, and NFC.

The controlled device may send a first signal containing information on whether the controlled device can be connected to the master device via connectivity (Wi-Fi, BT, NRF, etc.). The master control device may send a second signal containing information as to whether the controlled device is connected or not. The controlled device may send information including whether the controlled device is capable of connecting to the PWN 140. The first signal and the second signal may be the same signal, may be distinct signals, or may be combined into one signal.

The controlled device may lack the access authorization authentication required to connect to the communication service internally. If the controlled device connects the communication link to at least one master control device, the controlled device may receive the NAI 210 via the connected communication link in operation 1012. NAI 210 may include NSI 230 and SII 220. The NSI may include RRC status information 233, NAS status information 237, and the like. The controlled device will use RRC status information 233 for seamless connection to PWN 140. During authentication for access to PWN 140, the controlled device will use NAS status information 237. The SII 220 may include all or part of the SII recorded in the SIM card of the master device. Part of the SII may be any of ICCID 225, IMSI 221, GUTI 229, and TMSI 223. The controlled device can store NSI 230 or NAI 210 in the controlled device.

After receiving the NAI 210 from at least one master device, the controlled device may attempt to access the PWN 140 using the received NAI in operation 1014. If the access to the PWN 140 is successful, in operation 1016, the controlled device may provide a communication service via the public PWN 140.

After a periodic or predetermined event occurs, in operation 1018, the controlled device may perform synchronization with at least one master device regarding the changed NAI (eg, NSI 230, modem status information). The controlled device may generate an updated NSI 230 according to a connection via a communication service of the PWN 140 in the controlled device and store it in the controlled device. Synchronization for NAI 210 may be performed on the assumption that a communication link is connected between the controlled device and at least one master device. The predetermined event may correspond to at least one of the following: inter-cell delivery, change in cell identification information, change in TMSI 223, change in physical proximity between the master device and the controlled device, and for master control Changes in power conditions of one of the device and the controlled device, and changes in connectivity of the communication link between the master device and the controlled device.

The controlled device can be in standalone mode or relay mode. If the controlled device is in the independent mode, the controlled device replaces the master device and the controlled device accesses the PWN 140 on behalf of the master device, and the controlled device receives data from the PWN 140. NAI 210 is synchronized between the controlled device and the master device, but data (eg, uplink data, downlink data) is not synchronized between the controlled device and the master device.

In operation 1020, if the controlled device is in the relay mode, the controlled device relays the data received via the communication service to the master control device. In operation 1022, if the controlled device is in the relay mode, the controlled device relays the data received via the master control device to the communication service. With the exception of NAI 210, this is being synchronized between the controlled device and the master device. The relay mode may allow multiple UEs (eg, the master device) to transmit data uplink to and from the PWN 140 downlink via the controlled device. Relay mode may allow UEs with poor characteristics (eg, lower performance receivers, transmitters, or batteries) to pass through devices (eg, controlled devices) with superior characteristics (eg, better performance receivers, transmitters, or batteries) ) Access PWN 140.

If the communication link to the at least one master device is connected, the controlled device may transmit operation data (eg, downlink data) received from the PWN 140 to the at least one master device via the communication link. The controlled device may transmit the operation data (for example, uplink data) received from the at least one master device to the PWN via the communication link.

In operation 1024, the controlled device may monitor whether a request to release access to the PWN 140 occurs. The release of access to PWN 140 may be requested by the user, requested by the master device, or requested via PWN 140 (eg, paging from PWN). If the release of access to the PWN 140 is requested by the master device, the controlled device may report the release of the access to the PWN 140. The controlled device may report the release of access by sending a termination indication to the master device via the communication link. After receiving the access release request, the controlled device may release access to the PWN 140 in operation 1026.

FIG. 11 is an operation diagram illustrating a call processing program that can be used according to some embodiments of the inventive concept.

Referring to FIG. 11, consider a scenario in which multiple UEs (eg, a master device 1110 and a controlled device 1140) respond to paging of a specific user by a base station 1120.

In operation 1112, the base station 1120 may receive a paging from a mobility management entity (MME) 1130. The paging may include a SII 220 (eg, TMSI 223) to identify the UE to be paged. In operations 1114 and 1116, the base station 1120 may determine the UE to be paged based on the SII 220, and page the determined UE. Instead of the independent paging master control device 1110 and the controlled device 1140, the base station 1120 can handle only one paging based on the SII 220.

Both the main control device 1110 and the controlled device 1140 can receive paging from the base station 1120. For this purpose, it should be assumed that the master control device 1110 provides the NAI 210 to the controlled device 1140. For example, it can be assumed that the master device 1110 and the controlled device 1140 have the same TMSI 223.

In operations 1122 and 1124, the master device 1110 and the controlled device 1140 may transmit the random access preamble to the base station 1120 in response to the paging of the base station 1120.

After receiving random access preambles from multiple UEs (eg, a master device 1110 and a controlled device 1140), in operation 1126, the base station 1120 may determine from among the multiple UEs that it will establish an RRC connection The UE to which it arrived. Only one UE may be able to access a base station 1120 with a single SII 220. In other words, if more than one UE attempts to connect to PWN 140, only one will be allowed to connect to PWN 140. If the base station 1120 receives multiple responses from UEs having the same SII 220, the master device may have higher priority. The base station 1120 may use information from the components of the SII 220 that only the master device 1110 has to determine a UE. The only information that only the master device 1110 has may include IMSI 221 and the like. For this purpose, preferably, the master device 1110 will be used to access temporarily generated information (eg, TMSI 223) for accessing PWN 140 (eg, cellular network) rather than unique information for users (eg, IMSI 221) Inserted into NAI 210 provided to controlled device 1140.

If the base station selects a UE, the base station 1120 may establish an RRC connection to the selected UE in operation 1128.

FIG. 12 is a general flowchart outlining a control flow that can be used with a base station in the case of some embodiments of the inventive concept.

Referring to FIG. 12, in operation 1210, the base station may monitor whether responses are received from multiple UEs in response to the paging. The response may be considered as an access request from multiple UEs. In operation 1212, the base station may select a UE to which it will establish an RRC connection from among multiple UEs received from the response.

For example, the base station can use the information that only the master device has to determine a UE. The only information that only the master device has may include IMSI 221 and the like. To this end, the master device may insert temporarily generated information (e.g., TMSI 223) for accessing PWN 140 (e.g., cellular network) instead of unique information for the user (e.g., IMSI 221) to provide to Network access information for controlled devices.

If the base station selects a UE, the base station may establish an RRC connection to the selected UE in operation 1214 and provide a communication service for the selected UE based on the established RRC connection.

13A, 13B, 13C, 13D, and 13E (collectively, FIGS. 13A to 13E) are respective block diagrams illustrating various components of a UE according to an embodiment of the inventive concept.

13A to 13E illustrate examples of implementations of a device according to an embodiment of the present disclosure. For example, the components packaged in application processor (AP) chips 1310A, 1310B, 1310C, and 1310D may be different depending on the implementation examples in FIGS. 13A to 13E. The AP chips 1310A, 1310B, 1310C, and 1310D may each be a semiconductor wafer. The AP chips 1310A, 1310B, 1310C, and 1310D may each have a structure in which a CPU 1311 is combined with a plurality of units via a bus 1312. In FIGS. 13A to 13E, the units connected to the CPU 1311 via the bus 1312 may be different from each other. For example, as a package, the AP chip may or may not include DRAM and CP (eg, a modem). FIG. 13A illustrates an example of a structure in which a DRAM and a CP (for example, a modem) are placed outside the AP chip, and FIGS. 13B to 13E illustrate an example of a structure in which the DRAM and a CP (for example, a modem) are placed inside the AP chip. Although not illustrated, it is obvious that the device may have only one of a DRAM and a CP (for example, a modem) together with the AP chip to constitute a package structure.

Four additional images according to FIG. 13B, FIG. 13C, FIG. 13D, and FIG. 13E are added for SoC-related content addition. If there is a requirement for a small appearance size in the field of wearables and IoT, it is applicable.

FIG. 13A illustrates an example of a device having a structure in which an AP, a DRAM, and a CP (eg, a modem) are separated according to an embodiment of the present disclosure. However, the DRAM 1314 may form a package together with the AP chip 1310A.

Referring to FIG. 13A, the AP chip 1310A may have a structure in which the CPU 1311 is connected to the SMC 1313, the DMC 1314, and the communication interfaces 1315 and 1316 via the bus 1312. The communication interface 1315 may connect a modem chip (eg, CP) 1340 disposed outside the AP chip 1310A to the CPU 1311, and the communication interface 1316 may connect a connectivity chip 1350 disposed inside the AP chip 1310A to the CPU 1311. The SMC 1313 can connect a flash memory (or non-volatile memory (NVM)) 1320 located outside the AP chip 1310A to the CPU 1311, and the DMC 1314 can connect a DRAM 1330 located inside the AP chip 1310A to the CPU 1311 .

The device having the proposed structure can be operated as one of a master device and a controlled device. The master control device may have a SIM card, or have a structure to replace the SIM card, and may perform an operation of transmitting NAI to at least one controlled device. The controlled device may have a structure for managing NAI, and may perform an operation of accessing a specific public network using the NAI provided by the autonomously controlled device.

When the device is operated as a master device, the modem chip 1340 can obtain NAI from the information written in the NVM / SIM 1360. The modem chip 1340 can pass the obtained NAI to the communication interface 1315. The communication interface 1315 can pass the NAI to the CPU 1311 via the bus 1312. The CPU 1311 may provide the NAI to the communication interface 1316 via the bus 1312. The communication interface 1316 may pass the NAI to a connectivity chip 1350 provided outside the AP chip 1310A. The connectivity chip 1350 may transmit NAI to at least one controlled device based on a predetermined communication scheme (eg, Wi-Fi).

When the device is operated as a controlled device, the connectivity chip 1350 may receive a NAI transmitted by an autonomously controlled device based on a predetermined communication scheme (eg, Wi-Fi). The connectivity chip 1350 may pass the received NAI to the communication interface 1316. The communication interface 1316 can transfer the NAI to the CPU 1311 via the bus 1312. The CPU 1311 may provide the NAI to the communication interface 1315 via the bus 1312. The communication interface 1315 can pass the NAI to the modem chip 1340 provided outside the AP chip 1310A. The modem chip 1340 can write the NAI provided from the AP chip 1310A into the NVM 1360. In this case, the modem chip 1340 can obtain the NAI written in the NVM 1360 and use the obtained NAI to access a specific public network.

In its operation, the device of FIG. 13A may perform the following steps. (1) The communications processor (CP) disposed on the modem chip 1340 may use, for example, NAI stored in one of the DRAM memory 1330, the NVM 1320, or a register associated with the modem chip 1340. Start the network registration process. (2) Once the network registration procedure is successful, the CP can then store the successfully used NAI in NVM / SIM 1360. (3) Thereafter, after receiving the mobile state transfer request in the AP chip 1310A, the connectivity chip 1350 may be used to establish connectivity between the device and another device via a communication link. (4) Together with the connectivity in response to the mobile state transfer request, the stored NAI can be extracted from the NVM / SIM 1360. (5) Next, the CP of the modem chip 1340 can pass through the communication interface 1315, the bus 1312, the CPU 1311, the connectivity interface 1316, the connectivity chip 1350, and the communication link finally established between the device in FIG. 13A and another device The channel transmits NAI to another device.

FIG. 13B illustrates an example of a device having a structure in which an AP chip includes a DRAM and a CP (eg, a modem) according to an embodiment of the present disclosure. However, the DRAM 1318 may be placed outside the AP chip 1310B.

Referring to FIG. 13B, the AP chip 1310B may have a structure in which the CPU 1311 is connected to the SMC 1313, the DMC 1314, the modem (for example, CP) 1317, and the communication interface 1316 via the bus 1312. The communication interface 1316 may connect a connectivity chip 1350 disposed outside the AP chip 1310B to the CPU 1311. A modem (for example, a CP) 1317 may connect an NVM / SIM 1360 disposed outside the AP chip 1310B to the CPU 1311. The SMC 1313 can connect a flash memory (or non-volatile memory (NVM)) 1320, which is external to the AP chip 1310B, to the CPU 1311. The DMC 1314 can connect the DRAM 1318 disposed inside the AP chip 1310B to the CPU 1311. Alternatively, the DRAM 1318 may be placed outside the AP chip 1310B.

The device having the proposed structure can be operated as one of a master device and a controlled device. The master control device may have a SIM card, or have a structure to replace the SIM card, and may perform an operation of transmitting NAI to at least one controlled device. The controlled device may have a structure for managing NAI, and may perform an operation of accessing a specific public network using the NAI provided by the autonomously controlled device.

When the device is operated as a master device, the modem 1317 can obtain the NAI from the information written in the NVM / SIM 1360 placed outside the AP chip 1310B. The modem 1317 can pass the obtained NAI to the CPU 1311 via the bus 1312. The CPU 1311 may provide the NAI to the communication interface 1316 via the bus 1312. The communication interface 1316 may pass the NAI to a connectivity chip 1350 provided outside the AP chip 1310B. The connectivity chip 1350 may transmit NAI to at least one controlled device based on a predetermined communication scheme (eg, Wi-Fi).

In other cases, the modem 1317 can obtain the NAI from the information written in the NVM / SIM 1360. The modem 1317 can pass the obtained NAI to the communication interface 1316 via the bus 1312. The communication interface 1316 may pass the NAI to a connectivity chip 1350 provided outside the AP chip 1310B. The connectivity chip 1350 may transmit NAI to at least one controlled device based on a predetermined communication scheme (eg, Wi-Fi).

When the device is operated as a controlled device, the connectivity chip 1350 may receive a NAI transmitted by an autonomously controlled device based on a predetermined communication scheme (eg, Wi-Fi). The connectivity chip 1350 may pass the received NAI to the communication interface 1316. The communication interface 1316 can transfer the NAI to the CPU 1311 via the bus 1312. The CPU 1311 can pass the NAI to the modem 1317 via the bus 1312. The modem 1317 can write the received NAI in the NVM 1360 provided outside the AP chip 1310B. In this case, the CPU 1311 can obtain the NAI written in the NVM 1360 via the modem 1317 provided inside the AP chip 1310B, and use the obtained NAI to access a specific public network.

In other cases, the connectivity chip 1350 may receive a NAI transmitted by an autonomous control device based on a predetermined communication scheme (eg, Wi-Fi). The connectivity chip 1350 may transmit the received NAI to the communication interface 1316. The communication interface 1316 can transfer the NAI to the modem 1317 via the bus 1312.

The modem 1317 can obtain the NAI from the information written in the NVM / SIM 1360, and use the obtained NAI to access a specific public network.

FIG. 13C illustrates another example of a device having a structure in which an AP chip includes a DRAM and a CP (eg, a modem) according to an embodiment of the present disclosure. However, the DRAM 1318 may be placed outside the AP chip 1310C.

Referring to FIG. 13C, the AP chip 1310C may have a structure in which the CPU 1311 is connected to the SMC 1313, the DMC 1314, a modem (for example, CP) 1317, and a connectivity unit 1319 via a bus 1312. A modem (for example, a CP) 1317 may connect an NVM / SIM 1360 disposed outside the AP chip 1310C to the CPU 1311. The SMC 1313 can connect a flash memory (or non-volatile memory (NVM)) 1370 external to the AP chip 1310C to the CPU 1311. The DMC 1314 can connect the DRAM 1318 placed outside the AP chip 1310C to the CPU 1311. Alternatively, the DRAM 1318 may be placed outside the AP chip 1310C.

The device having the proposed structure can be operated as one of a master device and a controlled device. The master control device may have a SIM card, or have a structure to replace the SIM card, and may perform an operation of transmitting NAI to at least one controlled device. The controlled device may have a structure for managing NAI, and may perform an operation of accessing a specific public network using the NAI provided by the autonomously controlled device.

When the device is operated as a master device, the modem 1317 can obtain the NAI from the information written in the NVM / SIM 1360 placed outside the AP chip 1310C. The modem 1317 can pass the obtained NAI to the CPU 1311 via the bus 1312. The CPU 1311 may provide the NAI to the connectivity unit 1319 via the bus 1312. The connectivity unit 1319 may transmit the NAI to at least one controlled device based on a predetermined communication scheme (for example, Wi-Fi).

In other cases, the modem 1317 can obtain the NAI from the information written in the NVM / SIM 1360 placed outside the AP chip 1310C. The modem 1317 may pass the obtained NAI to the connectivity unit 1319 via the bus 1312. The connectivity unit 1319 may transmit the NAI to at least one controlled device based on a predetermined communication scheme (for example, Wi-Fi).

When the device is operated as a controlled device, the connectivity unit 1319 may receive the NAI transmitted by the autonomously controlled device based on a predetermined communication scheme (eg, Wi-Fi). The connectivity unit 1319 may pass the received NAI to the CPU 1311 via the bus 1312. The CPU 1311 can pass the NAI to the modem 1317 via the bus 1312. The modem 1317 can write the received NAI in the NVM 1360 provided outside the AP chip 1310C. In this case, the CPU 1311 can obtain the NAI written in the NVM 1360 via the modem 1317 provided inside the AP chip 1310C, and use the obtained NAI to access a specific public network.

In other cases, the connectivity unit 1319 may receive the NAI transmitted by the autonomous control device based on a predetermined communication scheme (eg, Wi-Fi). The connectivity unit 1319 may pass the received NAI to the modem 1317 via the bus 1312. The modem 1317 can write the received NAI in the NVM 1360 provided outside the AP chip 1310C. In this case, the modem 1317 can obtain the NAI written in the NVM 1360 and use the obtained NAI to access a specific public network.

FIG. 13D illustrates another example of a device having a structure in which an AP chip includes a DRAM and a CP (eg, a modem) according to an embodiment of the present disclosure. However, the DRAM 1318 may be placed outside the AP chip 1310D.

Referring to FIG. 13D, the AP chip 1310D may have a structure in which the CPU 1311 is connected to the SMC 1313, the DMC 1314, the modem (for example, CP) 1317, and the connectivity unit 1319 via the bus 1312. A modem (for example, a CP) 1317 may connect an NVM 1360 disposed inside the AP chip 1310D to the CPU 1311. The SMC 1313 can connect a flash memory (non-volatile memory (NVM)) 1320 external to the AP chip 1310D to the CPU 1311. The DMC 1314 can connect the DRAM 1318 disposed inside the AP chip 1310D to the CPU 1311. Alternatively, the DRAM 1318 may be placed outside the AP chip 1310D.

The device having the proposed structure can be operated as one of a master device and a controlled device. When the device is operated as a master control device, the master control device may perform an operation of transmitting NAI to at least one controlled device by using the NVM 1360 on behalf of the SIM card. The controlled device may have a structure for managing NAI and perform an operation of accessing a specific public network using the NAI provided by the autonomously controlled device.

When the device is operated as a master device, the modem 1317 can obtain NAI from information written in the NVM 1360 provided inside the AP chip 1310D. The modem 1317 can pass the obtained NAI to the CPU 1311 via the bus 1312. The CPU 1311 may provide the NAI to the connectivity unit 1319 via the bus 1312. The connectivity unit 1319 may transmit the NAI to at least one controlled device based on a predetermined communication scheme (for example, Wi-Fi).

In other cases, the modem 1317 can obtain the NAI from the information written in the NVM 1360 provided inside the AP chip 1310D. The modem 1317 may pass the obtained NAI to the connectivity unit 1319 via the bus 1312. The connectivity unit 1319 may transmit the NAI to at least one controlled device based on a predetermined communication scheme (for example, Wi-Fi).

When the device is operated as a controlled device, the connectivity unit 1319 may receive the NAI transmitted by the autonomously controlled device based on a predetermined communication scheme (eg, Wi-Fi). The connectivity unit 1319 may pass the received NAI to the CPU 1311 via the bus 1312. The CPU 1311 can pass the NAI to the modem 1317 via the bus 1312. The modem 1317 can write the received NAI in the NVM 1360 provided inside the AP chip 1310D. In this case, the CPU 1311 can obtain the NAI written in the NVM 1360 via the modem 1317 provided inside the AP chip 1310D, and use the obtained NAI to access a specific public network.

In other cases, the connectivity unit 1319 may receive the NAI transmitted by the autonomous control device based on a predetermined communication scheme (eg, Wi-Fi). The connectivity unit 1319 may pass the received NAI to the modem 1317 via the bus 1312. The modem 1317 can write the received NAI in the NVM 1360 provided inside the AP chip 1310D. In this case, the modem 1317 can obtain the NAI written in the NVM 1360 and use the obtained NAI to access a specific public network.

FIG. 13E illustrates another example of a device having a structure in which an AP chip includes a DRAM and a CP (eg, a modem) according to an embodiment of the present disclosure. However, the DRAM 1318 may be placed outside the AP chip 1310E.

The device shown in FIG. 13E may be structurally the same as the device shown in FIG. 13D. However, the NVM / SIM may be provided inside the AP chip 1310E and / or outside the AP chip 1310E. In this case, another component (for example, DRAM 1318 and the like) may perform a function corresponding to NVM / SIM. In this case, the detailed operation of the device operating as a master device or a controlled device may be the same as described above, and thus a detailed description thereof will be omitted.

FIG. 14 illustrates an example of an SoC corresponding to an IoT device according to an embodiment of the present disclosure.

Referring to FIG. 14, in a SoC corresponding to an IoT device, all functional blocks or a combination of some of the functional blocks may be configured as one chip. In this paper, the modem 1422, the connectivity module 1450, the DRAM 1480, and the flash memory (NVM) 1490 can be configured by separate chips.

The AP 1410 can control operations by the components included in the SoC. The modem 1422 can perform overall operations for cellular communication such as 3G, LTE, and the like. The modem 1422 may include a CP 1424, an internal memory 1426, and other H / W. The internal memory 1426 can support the fast operation of the communication protocol.

Memory interface 1430 may perform overall operations for information exchange with DRAM 1480 and / or flash memory (NVM) 1490. The peripheral interface 1440 may perform communication with at least one external device. The connectivity module 1450 may perform wireless communication with at least one external device based on a wireless protocol. The communication scheme defined by the predetermined wireless protocol may include Bluetooth, WLAN, GPS, and the like. Network on Chip (NOC) 1460 can serve as an interface for information exchange between components included in the SoC.

In addition, the SoC may further include an audio subsystem 1472, a system timer 1474, a security module 1476, a multimedia module 1478, and the like.

FIG. 15 illustrates an example of a boot sequence operation in a SoC according to an embodiment of the present disclosure.

Referring to FIG. 15, the AP may initialize internal ROM code (for example, clock and / or stack) after starting its operation (①), and maintain a reset signal (②) for at least one CP.

The AP can copy the images of the boot loader programs BL1 and BL2 of the AP from external memory (for example, flash memory) to internal memory (for example, SRAM) (③). External boot devices (such as flash memory, USB, serial flash memory, and the like) can set the environment through the Operating Mode (OM) pin. Images can be checked based on AP code signature. In BL1 or BL2, AP_CPU can initialize the DRM controller. Images can be moved to DRAM. After startup, the AP_CPU can initiate the use of DRAM.

AP_CPU can copy CP code from external memory (for example, flash memory) to internal memory (ie, internal SRAM) (④). AP_CPU can allocate memory area for CP code / data / heap (⑤). The AP can generate a CP reset signal (⑥). At least one CP start sequencer can start the CP system (⑦). At least one CP boot sequencer can copy the CP boot loader code from the internal SRAM (IRAM) of the CP to the private area (⑧) of the DRAM.

CP_PMU can generate CP_CPU reset signal (⑨). CP_CPU can start CP boot code loading operation from the IRAM on the CP side (⑩). CP_CPU can drive the CP code (⑪) by the data in the private area of DRAM.

The operation in the CP_CPU will be described in detail below to allow the controlled device to connect with the PWN based on the SoC described above and the boot sequence operation according to the embodiment of the present disclosure.

In order for the controlled device to connect with the PWN, NAI (all or some of RRC, NSI, SII, and the like) may be required. For this purpose, the CP_CPU of the master device can use the mobile state transfer layer (the code of the CP) to perform the operation of transferring NAI to the controlled device. Among the controlled devices, the NAI for the master device required to connect to the PWN can even be stored in SIM, NVM or DRAM.

In order to pass the NAI to the controlled device using the mobile state transfer layer (the code of the CP), the CP_CPU can use one of the following boot sequence methods of the SoC.

In the first method, the master control device can load the mobile status transmission layer (the code of the CP) according to the processes ④ and ⑤, and then load it into the CP through the processes ⑥, ⑦, and ⑧. If it is necessary to transfer the NAI to the controlled device, the master control device can transfer the NAI to the controlled device via ⑨ and ⑩. The processes ⑨ and ⑩ correspond to the processes in which the CP_CPU can operate the action status transfer layer (CP code) loaded on the IRAM via processes ⑥, ⑦, and ⑧.

In the second method, the main control device can load the action state transmission layer (the code of the CP) written in the flash memory into a predetermined area of the DRAM or the internal memory through the process and ⑤. If it is necessary to transfer the NAI to the controlled device, the master control device may transfer the NAI to the controlled device through the process. Process ⑪ corresponds to the process in which CP_CPU can drive the action state transfer layer (CP code) loaded on the DRAM after process ⑤.

In the third method, if it is necessary to transfer the NAI to the controlled device while the mobile state transfer layer (the code of the CP) is not loaded on the DRAM (the memory of the executable program), the master device may The NAI is passed to the controlled device according to the proposal in the second method.

For the transfer of NAI according to the three proposed methods, a method of outputting an output signal containing the NAI generated by the CP_CPU to the outside using a mobile state transfer layer (CP code) can be used. For example, in CP_CPU, NAI can be output to the outside of the data machine (or SoC) via connectivity or cable without passing through the AP. In addition, in the CP_CPU, the NAI can be output to the outside of the modem (or SoC) through the AP via the connectivity or cable. As mentioned above, if NAI (all or some of RRC, NSI, SII, and the like) transfer from the autonomous device to the controlled device is necessary for the controlled device to connect with the PWN, the action status transmission stored in the NVM The layer (CP code) can be executed by the CP or CP_CPU of the SoC. To execute the mobile state transfer layer (CP code) stored in the NVM, the proposed methods (a), (b), and (c) can be used. Through the execution of the action state transfer layer (CP code) by the CP or CP_CPU of the SoC, the NAI autonomous control device can be transmitted to the controlled device in the form of signals. For the transmission of signals containing NAI, a mobile state transfer layer (CP code) can be used.

FIG. 16 is a conceptual diagram illustrating various protocol stacking layers of a UE according to some embodiments of the inventive concept in one example.

Referring to FIG. 16, an example 1610 of a UE's contract stacking component is shown. The protocol stack assembly may include one or more of a first layer 1620, a second layer 1630, a third layer 1640, and a fourth layer 1650.

The first layer 1620 may include a physical layer 1622 that can carry all information from a medium access layer (MAC) transport channel over the air interface.

The second layer 1630 may include one or more of a MAC 1632, a radio link control (RLC) 1634, and a packet data convergence control (PDCP) 1636. The MAC 1632 can be responsible for mapping between logical channels and transport channels. RLC 1634 can be responsible for the transmission of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs. PDCP 1636 can be responsible for header compression and decompression of IP data, transmission of data (eg, user plane or control plane), and maintenance of PDCP sequence number (SN).

The third layer 1640 may include one or more of RRC 1642 and NAS 237. RRC 1642 may include broadcasting of system information related to: paging, establishment, maintenance, and release of RRC 1642 connections between NAS 237, AS, UE, security functions (including key management, establishment of point-to-point radio bearers , Configure, maintain, and release). The NAS 1644 may be the highest layer of the control plane before the mobile status transmission layer between the UE and the MME 1130. The NAS 1644 can support the mobility of the UE and the session management program to establish and maintain IP connectivity between the UE and the PWN 140.

The fourth layer 1650 may include an action status transmission layer 1652. If the UE is the master device, the mobile status transmission layer 1652 may transmit the NAI 210 stored in the SIM of the master device to the controlled device. If the UE is a controlled device, the mobile status transmission layer 1652 may receive the NAI 210 from the master device to be stored in the NVM of the controlled device.

FIG. 17 is a block diagram illustrating an M2M mobile state transfer protocol 1700 via a mobile state transfer layer according to an embodiment of the inventive concept, in one example.

Referring to FIG. 17, an example of the M2M mobile state transfer protocol 1700 includes a controlled device 1720, a master control device 1730, a base station 1740 (eg, an eNB), and an MME 1750.

The master device 1730 is connected to the base station 1740 through RRC 1732, 1741, PDCP 1733, 1742, RLC 1734, 1743, MAC 1735, 1744, and SII 1736, 1745. The master device 1730 is connected to the MME 1750 via NAS 1731 and 1751. The mobile status transmission layer 1752 autonomously controls the NAS 1721, 1731, 1751, RRC 1722, 1732, 1741, SII 1726, 1736, 1745, and application data 1710A, 1710B via communication links (for example, Wi-Fi, BT, NFC). Device 1730 is transmitted to controlled device 1720. Controlled device 1720 then contains NAI 210 for connection to PWN 140.

18A, 18B, and 18C are respective examples of control and data planes of a controlled device 1820 operating in independent mode and relay mode according to some embodiments of the inventive concept.

Referring to FIG. 18A, 1800A is an example of a control plane of a controlled device 1820 in a stand-alone mode or a relay mode. Once the master device 1810 has transmitted the NAI 210 (eg, NAS 1811, 1821, RRC 1812, 1822, and SII 1816, 1826) to the controlled device 1820, the controlled device 1820 may replace the master device 1810. Example 1800A illustrates a control plane of a controlled device 1820 in both independent mode and relay mode. The controlled device 1820 is connected to the base station 1830 through RRC 1822, 1831, PDCP 1823, 1832, RLC 1824, 1833, MAC 1825, 1834, and SII 1826, 1835, and the controlled device 1820 is connected to the MME through NAS 1821, 1841 1840. The controlled device 1820 accesses the PWN 140 (for example, the base station 1830, the MME 1840) on behalf of the master device 1810. The controlled device 1820 sends the updated NAS 1811, 1821 and RRC 1812, 1822 to the master device 1810.

Referring to FIG. 18B, 1800B is an example of a data plane of a controlled device in a standalone mode. The controlled device 1850 receives application data 1851 from the PWN 140 (eg, base station 1860, MME). The controlled device 1850 does not relay application data 1851 to the master device.

Referring to FIG. 18C, 1800C is an example of a data plane of a controlled device in a relay mode. The controlled device 1880 receives application data 1881 from the PWN 140 (eg, base station 1890, MME). The controlled device 1880 transmits the application data 1881 from the PWN 140 (eg, the base station 1890, the MME) to the master control device 1870 via a communication link (eg, Wi-Fi, BT, NFC, etc.). The controlled device 1880 functions as a mobile base station.

If the controlled device is in the relay mode, the mobile communication layer 1652 transmits application data 1881 and 1871 between the controlled device 1880 and the master device 1870 via the communication link. If the controlled device is in the independent mode, the mobile transmission layer 1652 does not transmit application data 1881 or 1871 between the controlled device 1880 and the master device 1870.

FIG. 19 illustrates an example of an implementation of one NAI shared by multiple devices according to an embodiment of the present disclosure.

Referring to FIG. 19, one master control device 1910 may have a SIM card containing user identification information and the like, and two controlled devices 1920 and 1930 may not have a SIM card. One master control device 1910 and two controlled devices 1920 and 1930 are each assumed to support D2D communication. Among the two controlled devices, the first controlled device 1920 may be a smart watch, and the second controlled device 1930 may be a vehicle.

In operations 1940 and 1960, the master control device 1910 may transfer the action status to the first controlled device 1920 and / or the second controlled device 1930. For example, the handover action state may correspond to an operation in which the master control device 1910 provides NAI to the controlled device.

After receiving the delivered action status, the first controlled device 1920 and / or the second controlled device 1930 can perform synchronization with the action status of the master control device 1910 in operations 1950 and 1970, which allows the master control device 1910 The operating state is shared with the first controlled device 1920 and the second controlled device 1930.

FIG. 20 illustrates examples of various implementations of an embodiment according to the present disclosure.

Referring to FIG. 20, the base station 2002 may form a giant cell 2000 as a service area. Heterogeneous devices may exist in the giant cell 2000. A device (for example, a master device) having a USIM card installed therein may perform communication with the base station 2002 via a direct or indirect path.

The main control device 2004 is shown to perform direct communication with the base station 2002. In addition, three cases where the main control device 2004 performs communication with the base station 2002 via an indirect path are shown.

The first case corresponds to an example of implementation of a master device corresponding to a UE located in a bus. For example, the main control devices 2014 and 2016 may be located in a bus. Each of the main control devices 2014 and 2016 can be connected through a D2D solution and a relay device (EXO-US) 2012 installed in the bus. Each of the master device 2014 and 2016 may provide its own USIM information to the relay device (EXO-US) 2012 via a D2D connection. In this case, the relay device (EXO-US) 2012 may use the USIM information provided by each of the autonomous control devices 2014 and 2016 to connect the master control devices 2014 and 2016 to the base station 2002. In other words, the relay device (EXO-US) 2012 can operate as a controlled device of the master control device 2014 and 2016.

The second case is an example of implementation of the master device corresponding to the UEs 2026 and 2028 located in the small cell 2020. For example, the relay device 2022 may form a small cell 2020 as a service area. Obviously, the relay device 2022 can perform cellular communication with the base station 2002.

The first master control device 2026 may be connected to the relay device 2022 based on a predetermined wireless communication scheme to provide its own USIM information to the relay device 2022. In this case, the relay device 2022 may be a controlled device of the first master control device 2026, and the relay device 2022 may use the USIM information to connect the first master control device 2026 to the base station 2002.

A heterogeneous device (EXO-UE) 2024 may exist in a small cell 2020. A heterogeneous device (EXO-UE) 2024 may be connected to a small cell 2020 based on a communication scheme such as D2D.

The second master control device 2028 may be connected to the heterogeneous device (EXO-UE) 2024 based on a predetermined wireless communication scheme to provide its own USIM information to the heterogeneous device (EXO-UE) 2024. In this case, the heterogeneous device (EXO-UE) 2024 may use the USIM information to connect the second master control device 2028 to the base station 2002 via the relay device 2022.

The third case corresponds to an example of implementation of a master device corresponding to a UE located in a vehicle. For example, the master control device 2034 may be located in a vehicle. The master control device 2034 may be connected to a control device (EXO-US) 2032 installed in a vehicle through a D2D scheme. The master device 2034 may provide its own USIM information to the controlled device (EXO-US) 2032 via a D2D connection. In this case, the controlled device (EXO-US) 2032 can use the USIM information provided by the autonomous control device 2034 to connect the master control device 2034 to the base station 2002.

In one embodiment, the base station 2002, the controlled devices 2012, 2022, and 2032, and the relay device 2022 and the controlled device 2024 forming a small cell 2020 may have honeycomb connectivity. The controlled devices 2012, 2022, 2032, and 2024 and the main control device 2014, 2016, 2028, and 2034 may have local end connectivity.

FIG. 21 illustrates a network structure that can implement the present disclosure.

Referring to FIG. 21, the network structure may include (a) a structure in which the UE can directly access the macro cell, (b) a structure in which the UE can access the macro cell through a small cell, and (c) a UE can access through a controlled device (eg, A heterogeneous UE (HetUE) accesses a structure of a small cell, and accesses a giant cell via the small cell. UE and HetUE can be connected to each other based on M2M or local or personal area network (for example, Wi-Fi, BT, etc.), and other components can be connected to each other based on cellular network (for example, 3G, LTE, etc.)

FIG. 22 illustrates the effects expected by embodiments of the present disclosure, that is, from the perspective of self heterogeneous UE (HetUE) 2200, subscriber 2210, operator 2220, and chipset supplier and UE manufacturer 2230 to illustrate gain.

Referring to FIG. 22, the user 2210 can reduce the cost of using a communication network such as a cellular network, and can share data services with low-cost devices. In addition, the user 2210 can not only increase the user's throughput and reduce the power consumption of the portable device, but also simplify on-demand installation and reselect the device without interruption.

The chipset supplier and UE manufacturer 2230 can realize different choices for the characteristics of the external architecture, no silicon changes are needed, and the UE performance can be improved (no less stringent battery and size restrictions).

Operator 2220 can attribute high revenues due to increased traffic and support data services for low-cost devices. In addition, the operator 2220 can achieve higher spectrum efficiency, low deployment costs, no impact on the network, and possible rapid technology adoption.

Obviously, various embodiments proposed in the present invention can be applied based on Internet of Things (IoT) devices. An IoT device can be any device that can exchange information with at least one other device. The IoT device may have no limitation on the types of resources that the IoT device may use for information exchange with other devices. In other words, the IoT device can support information exchange based on at least one of wired resources and wireless resources.

IoT devices may include accessible interfaces for information exchange. The accessible interface may include a modem communication interface capable of accessing at least one of a wired local area network (LAN), a wireless local area network, and a mobile cellular network. The wireless LAN can be a network that supports Bluetooth (BT), Wireless Fidelity (Wi-Fi), Zigbee, and the like, and the mobile cellular network can support 3rd Generation (3rd Generation; 3G), Long Term Evolution (LTE) and similar networks.

23A and 23B illustrate examples of an IoT system according to various embodiments of the present disclosure.

Referring to FIG. 23A, the IoT system 2300A may include multiple IoT devices 2310, 2320, 2330, and 2340, an access point (AP) 2350, a gateway (GW) 2360, and a communication network (CN). ) 2370, at least one server, and the like. At least one server may include a management server 2380.

The multiple IoT devices 2310, 2320, 2330, and 2340 can be divided into an active device and a passive device. An active device may be a device that can generate an operating voltage on its own and operates based on it. For example, the active device may be a refrigerator, an air conditioner, a phone, a car, and the like. Passive devices may be devices that operate based on power applied by external devices and the like. For example, the passive device may include a radio frequency identification (RFID) tag or an NFC tag.

According to one embodiment, the IoT devices 2310, 2320, 2330, and 2340 may collect data using a sensor, and transmit the collected data to an external device based on a predetermined communication protocol. The IoT devices 2310, 2320, 2330, and 2340 may receive control information and / or data based on a predetermined communication protocol. The predetermined communication protocol may be a protocol supporting a communication service based on a wired / wireless LAN, the Internet, or a cellular network.

The IoT devices 2310, 2320, 2330, and 2340 can directly access the communication network without the help of other devices according to a predetermined communication protocol. For example, an IoT device 2340 such as a vehicle may directly access a communication network 2370 based on a predetermined communication protocol. Other IoT devices 2310, 2320, and 2330 can access the communication network 2370 by means of other devices. Among the IoT devices 2310, 2320, and 2330 that can access the communication network 2370 by means of other devices, easy-to-mobile IoT devices 2330 such as smartphones, tablet PCs, and the like can support direct communication network 2370 Communication agreement.

The AP 2330 may connect a plurality of IoT devices 2310, 2320, and 2330 to the communication network 2370 via the GW 2360, or may connect it to at least one other IoT device. The AP 2330 may be provided independently or embedded in another IoT device.

As an example, the AP 2330 can be embedded in a television. In this case, the user can monitor or control at least one IoT device connected to the AP 2330 on the display of the TV.

As another example, in addition to its own unique functions, a smart phone can also perform the functions of an AP. In this case, the smartphone can be connected to the communication network 2370 to perform its own unique function, and the IoT device can also be connected to the communication network 2370 or other IoT devices.

The GW 2360 may change the protocol to connect the AP 2350 to an external communication network 2370 (eg, the Internet or a public communication network). The GW 2360 may connect at least one IoT device connected via the AP 2350 to an external communication network 2370. The GW 2360 and AP 2350 can be configured as one device or incorporated into one device. The AP 2350 may perform the function of a first gateway, and the GW 2360 may perform the function of a second gateway.

The GW 2360 is provided independently or can be embedded in another IoT device. As an example, in addition to its own unique functions, a smart phone can also perform the functions of a GW. In this case, the smart phone may be connected to the communication network 2370 to perform its own unique function, and the IoT device may also be connected to the communication network 2370.

The communication network 2370 may include an Internet and / or a public communication network. Depending on the type of resources supported by the public communication network, the public communication network can be classified into a wired communication network and a wireless communication network. Public communication networks may include mobile cellular networks. As an example, the communication network 2370 may provide a path (eg, a channel or the like) via which the communication network 2370 may pass information collected by the IoT devices 2310, 2320, 2330, and 2340 to the server 2390 or further处 装置。 Devices.

The server 2390 may collect information provided by the IoT devices 2310, 2320, 2330, and 2340 via the communication network 2370. The server 2390 may store and manage the collected information based on a predetermined format, or reproduce the information through analysis. The server 2390 may provide the analysis result and / or the reproduced information to another server and / or an IoT device via the communication network 2370.

For example, the server 2390 can collect information about the user's blood glucose from the IoT device in real time. In this case, the server 2390 may analyze the health status of the user based on the collected blood glucose information, and manage the analysis results and / or report the analysis results to the IoT device. In order to analyze the health status of the user, the server 2390 may refer to a predetermined glucose threshold and an existing health status analysis result. As a result of the analysis, if it is determined that the user is in a critical state, the server 2390 may transmit information indicating a risk situation of the user to a pre-registered IoT device.

The management server 2380 may operate the communication network 2370 and / or perform user management and the like. For example, the management server 2380 can operate and manage a public communication network, and allows only previously allowed users' IoT devices to access the public communication network operated by the management server 2380.

Multiple IoT devices 2310, 2320, 2330, and 2340 can be grouped. As an example, multiple IoT devices 2310, 2320, 2330, and 2340 may be grouped considering their unique characteristics. In other words, multiple IoT devices 2310, 2320, 2330, and 2340 can be grouped into home gadgets group 2310, home appliances group 2320, entertainment group 2330, transportation group (or vehicle group) 2340, and the like. In addition, multiple IoT devices 2310, 2320, 2330, and 2340 can be grouped into a temperature control group for controlling room temperature, a home appliance group (depending on power consumption, it is divided into a large home appliance group and a small home appliance) Groups), cleaning groups to control room clarity (e.g., air cleaning and floor cleaning), lighting groups to control indoor lighting, and entertainment devices (e.g., TVs, audio devices, and the like) Entertainment group. The temperature control group may include an air conditioner, a power window, a power window curtain, and the like.

An IoT device may belong to one group or multiple groups. For example, air conditioners may belong to the large household appliances group and the temperature control group. Smart phones may belong to the home gadgets group 2310 and the entertainment group 2330.

FIG. 23B illustrates an example of an IoT system including a distributed server in addition to the IoT device in FIG. 23A.

Referring to FIG. 23B, the IoT network system 2300B may include various components included in the IoT network system 2300A shown in FIG. 23A. For example, in addition to the IoT network system 2300A, the IoT network system 2300B may further include a distributed server 2390. Since components substantially the same as those in FIG. 23A are substantially the same in configuration and operation, a detailed description thereof will be omitted herein for convenience.

The decentralized server 2390 may include a plurality of sub-servers 2390-A, 2390-B, and 2390-C, or may be connected to the plurality of sub-servers 2390-A, 2390-B and via a no-load transmission link and the like 2390-C. The decentralized server 2390 may distribute the work to be processed to at least one sub-server 2390-A, 2390-B, or 2390-C. In other words, the decentralized server 2390 can process tasks to be processed in a decentralized manner through the sub-servers 2390-A, 2390-B, and 2390-C, and can perform scheduling for decentralized processing.

For example, the distributed server 2390 can analyze the requests transmitted through the communication network 2360 by scheduling, and can predict the amount of associated data and workload based on the analysis results. The decentralized server 2390 may allocate the requested work by communicating with at least one of the plurality of sub-servers 2390-A, 2390-B, and 2390-C depending on the prediction result. In this case, the distributed server 2390 may receive status information for each of the plurality of sub-servers 2390-A, 2390-B, and 2390-C, and may reflect the received status information during a schedule. The distributed server 2390 can improve the overall performance of the IoT network system by scheduling.

In one embodiment with reference to FIGS. 23A and 23B, among a plurality of IoT devices 2310, 2320, 2330, and 2340, an IoT device that allows access to a plurality of communication networks 2370 may pass network access information to AP 2350 or at least one IoT device. In this case, the AP 2350 or at least one IoT device can successfully connect with the communication network 2370 based on the network access information.

For example, if the AP 2350 successfully connects with the communication network 2370 based on the network access information, the AP 2350 may connect at least one IoT device connected to the AP 2350 to the communication network 2370. In this case, at least one IoT device connected to the AP 2350 should not necessarily have network access information.

If multiple IoT devices request their connection to the communication network 2370, the AP 2350 may schedule the connection. For example, the AP 2350 may consider the priority and the like to determine the connection order of multiple IoT devices that have requested its connection to the communication network 2370.

The AP 2350 can monitor whether the IoT device that has provided network access information is outside its service area, and controls the AP device 2350 or other IoT devices to connect to the communication network 2370 based on the monitoring results. For example, if the communication link to an IoT device that has provided network access information is truncated (or lost), the AP 2350 may discard the network access information that the AP 2350 already holds. In this case, the AP 2350 may no longer be allowed to access the communication network 2370.

FIG. 24 illustrates the appearance of a smart watch as an example of an IoT device according to an embodiment of the present disclosure.

Referring to FIG. 24, the IoT device 2400 may include at least one sensor 2410 for connecting information about the surrounding environment. The sensor 2410 can sense at least one of ambient temperature, illumination, UV index, speed, image information, and the like. Preferably, the position at which the sensor 2410 is installed may be determined depending on conditions required for sensing.

For example, if the sensor 2410 is a sensor for measuring a user's heart rate, the sensor 2410 should be installed on a body part where the sensor 2410 can be attached to the user's heart rate. Position. If the sensor 2410 is a UV sensor for measuring the UV index, the sensor 2410 should be installed in such a manner that it can sense the surrounding light environment.

The IoT device 2400 may include a display 2420. The display 2420 may display internal status information 2450 of the IoT device 2400. The display 2420 may include a touch sensor (not shown). In this case, the display 2420 may use a touch sensor to detect a user's touch point, touch direction, and touch type.

The display 2420 may have input / output functions and appearance for a user interface. For example, the display 2420 may display at least one icon 2460 and an input / output menu on its screen. In this case, the user can control the IoT device 2400 through the touch sensor and the user interface.

The IoT device 2400 may further include a button 2430 as an input device. In this case, the user can use the button 2430 to change the state of the IoT device 2400 to an active state or turn on the display 2420. The display 2420 can be used to display a top menu of the user interface.

The IoT device 2400 may further include a package 2440 that supports at least one of the sensor 2410, the display 2420, and the button 2430. The support 2470 can be used to attach the package 2440 to a particular target. For example, the support 2470 may be a wristband.

The IoT device 2400 may have a slot (not shown) into which a SIM card can be inserted. The user can access the communication network based on information written on a SIM card inserted into a slot of the IoT device 2400 (for example, user identification information and the like) or network access information provided from another IoT device.

FIG. 25 illustrates an example of a configuration of an IoT device according to an embodiment of the present disclosure.

25, the IoT device 2500 may include a processor (eg, an application processor (AP)) 2510, a transmitter / receiver 2520, a memory 2530, a display 2540, an I / O interface 2550, and a sensor 2560. The IoT device 2500 may have a built-in battery for supplying power internally, or a power supply for supplying power externally.

The transmitter / receiver 2520 corresponding to the communication interface may perform communication with an external device. The communication interface 2520 may be a wireless local communication interface such as a local area network (LAN), Bluetooth, wireless fidelity (Wi-Fi), Zigbee, and the like, or may be accessed such as 3rd generation (3G), LTE) and similar cellular communication interfaces for mobile cellular networks.

The communication interface 2520 may include a transmitter and / or a receiver. The transmitter and / or receiver can transmit and / or receive information via the AP or GW. The IoT device 2500 may transmit and / or receive control information or data by communicating with users or other IoT devices. In other words, the IoT device 2500 can transmit internal states and / or data to the outside via a transmitter, and receive control commands and / or data from the outside via a receiver.

The processor may perform operations for information processing. For example, the AP 2510, which is one of the processors, may execute an application installed in the IoT device 2500 and process operations corresponding to it.

The display 2540 may provide a UI to a user. In this case, the user can control the IoT device 2500 based on the UI provided on the display 2540.

The memory 2530 can store control command codes, control data, or user data for controlling the IoT device 2500. The memory 2530 may include at least one of a volatile memory or a non-volatile memory. Non-volatile memory may include at least one of various memories such as: read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), Electrically erasable and programmable ROM (EEPROM), flash memory, phase-change RAM (PRAM), magnetic RAM (MRAM), resistive RAM (RRAM), iron Electrical RAM (ferroelectric RAM; FRAM) and the like. Volatile memory may include at least one of various memories such as: dynamic RAM (DRAM), static RAM (SRAM), synchronous DRAM (SDRAM), phase-change RAM (PRAM), Magnetic RAM (MRAM), resistive RAM (RRAM), ferroelectric RAM (FeRAM), and the like.

In addition to the memory 2530, the IoT device 2500 may further include a storage device. The storage device may be, for example, a hard disk drive (HDD), a solid state drive (SSD), an embedded multimedia card (eMMC), a universal flash memory (universal flash memory) storage; UFS) and similar non-volatile media. The storage device may store user information, collected sensing information, and the like.

FIG. 26 illustrates another example of a configuration of an IoT device according to an embodiment of the present disclosure.

26, the IoT device 2600 may include an AP 2610, a communication interface 2626, a security module 2620, a storage device 2612, a memory 2614, a display 2616, an I / O interface 2618, a data bus 2636, a power supply 2630, and / or At least one sensor 2632 and 2634.

The AP 2610 can control the overall operation of the IoT device 2600. The AP 2610 can execute applications that provide Internet browsers, games, videos, and the like. According to an embodiment of the disclosure, the AP 2610 may include a single-core processor or a multi-core processor. For example, the AP 2610 may include a multi-core processor such as a dual-core processor, a quad-core processor, and a six-core processor. According to the illustrated embodiment of FIG. 26, the AP 2610 may further include a cache memory disposed outside and / or inside the AP 2610.

The security module 2620 may include a processor 2622 and a security element 2624. The security module 2620 including the processor 2622 and the security element 2624 may be formed as a package. An internal bus INT_BUS connecting the processor 2622 to the secure element 2624 may be formed inside the package. The security element 2624 may include a function capable of defending against attacks from the outside (for example, laboratory attacks). Therefore, the security element 2624 can safely store security data. The processor 2622 can be connected to the AP 2610.

The sensor 2632 may be an image sensor for sensing images and the like. If the sensor 2632 is connected to the AP 2610, the sensor 2632 can transmit image information generated by image sensing to the AP 2610. The image sensor 2634 may be a biosensor for sensing biometric information and the like. For example, the sensor 2634 can detect fingerprints, iris patterns, vein patterns, heart rate, blood glucose, and the like, and generate sensing data corresponding to the detection, and can provide the generated sensing data to the security module 2620 contains the processor 2622. However, the sensor 2632 and the sensor 2634 are not limited to a specific sensor (for example, an image sensor or a biosensor), and may be such as an illuminance sensor, an acoustic sensor, an acceleration sensor, and Any sensor like that.

The security module 2620 and the AP 2610 can generate a session key through mutual authentication. For example, the security module 2620 and the AP 2610 may use the first credential CT1 stored in the secure element 2624, the second credential CT2 stored in the AP 2610, and the authentication department collectively stored in the AP 2610 and the secure element 2624. The public key CA_PB performs mutual authentication.

After successful mutual authentication, the security module 2620 and the AP 2610 may generate a session key using the first private key PR1 stored in the secure element 2624 and the second private key PR2 stored in the AP 2610.

The security module 2620 may encode the sensing data SSD using the generated session key, and transmit the encoded sensing data SSD to the AP 2610. The AP 2610 can use the generated session key to obtain the sensing data SSD by decoding the transmitted data encoded by the security module 2620.

Due to the operations described above, the IoT device 2600 can improve the security level based on data transmission. The secure element 2624 together with the AP 2610 may be formed into a package.

The security module 2620 may further include a processor 2622. The processor may encrypt the sensing data SSD provided by the self-sensor 2634. The processor 2622 may control communication between the AP 2610 and the secure element 2624. In this case, the secure element 2624 and the processor 2622 may be formed into one package.

The storage device 2612 may store a startup image for starting the IoT device 2600. For example, the storage device 2612 may include a non-volatile memory device such as a flash memory element, an SSD, and the like.

The memory 2614 may store data required for the operation of the IoT device 2600. For example, the memory 2614 may include volatile memory such as DRAM, SRAM, and the like.

The I / O interface 2618 may include input members such as a touch pad, a keypad, input buttons, and the like, and output members such as a display, a speaker, and the like. The power supply 2630 may supply an operation voltage required for the operation of the IoT device 2600. The power supply 2630 may include a power supply unit and / or a battery.

According to an embodiment of the present disclosure, the IoT device 2600 may be any mobile system, such as a mobile phone, a smart phone, a personal digital assistant (PDA), and a portable multimedia player (PMP). , Digital cameras, music players, portable game consoles, navigation systems, laptops, and the like.

FIG. 27 conceptually illustrates a hardware (H / W) and software (S / W) structure of an IoT device according to an embodiment of the present disclosure.

Referring to FIG. 27, the IoT device may define operations among layers of hardware (H / W) 2710, operating system (OS) 2720, application (APPS) 2730, and user 2740.

The hardware 2710 of the IoT device may include multiple components. The hardware 2710 of the IoT device may include an AP 2711, a sensor 2712, a memory 2713, a communication interface 2714, an I / O interface and display 2715, and the like. For example, the AP 2711, the sensor 2712, the memory 2713, and the communication interface 2714 may correspond to the AP 2510, the sensor 2560, the memory 2530, and the communication interface 2520 shown in FIG. 25, respectively. The I / O interface and the display 2715 may correspond to the I / O interface 2618 and the display 2616 shown in FIG. 26. The IoT device may further include an OS 2720 and / or an application 2730.

Application 2730 means software (s / w) and services that implement specific functions. User 2740 means a subject using application 2730. The user 2740 can communicate with the application 2730 via a user experience (UX). The application program 2730 can be made based on each service purpose, and the application program can communicate with the user 2740 via a UI corresponding to each purpose. The application 2730 can perform the operation requested by the user 2740. The application program 2730 can call the contents of the application protocol interface (API) 2726 and the library 2727 when necessary.

API 2726 and library 2727 can perform gigantic operations that are responsible for specific functions, and provide an interface if communication with lower layers is required. If the application 2730 requests an operation from a lower layer via the API 2726 and the library 2727, the API 2726 and the library 2727 can classify the incoming request into the areas of security 2723, network 2724, and management 2725.

The API 2726 and the library 2727 may operate the required layers depending on the requested domain. For example, when a function related to the network 2724 is requested, the API 2726 can transmit the required parameters to the layer of the network 2724 and call the related function. The network 2724 may communicate with lower layers to perform the requested operation. If the lower layer does not exist, the API 2726 and the library 2727 can directly perform the operation requested by the network 2724.

The driver 2721 included in OS 2720 can be used to pass requests classified in the upper layer to the layer of H / W 2710, while managing H / W 2710 and checking the status. If the driver 2721 requests operation from the layer of H / W 2710, the firmware 2722 included in OS 2720 can convert the request, so that the layer of H / W 2710 can accept the request. The firmware 2722 for converting requests and passing the converted requests to H / W 2710 may be implemented to be incorporated into driver 2721 or H / W 2710.

The IoT device may include a driver 2721 and a firmware 2722 from the API 2726, and may have an OS 2720 built therein for managing the entire IoT device. The OS 2720 can be stored in the memory 2713 in the form of control command code and data. As an example, since the low-cost IoT device with simple functions is smaller in memory size, the low-cost IoT device may include control software instead of the OS.

H / W 2710 can perform sequential or out-of-order processing of requests (or commands) passed by driver 2721 and firmware 2722, and store the processing results in a register in H / W 2710, or connect to H / W 2710 in memory 2713. The stored processing results can be returned to the driver 2721 and the firmware 2722.

H / W 2710 can request an operation in the upper layer by generating an interrupt. If an interruption occurs, the part managing the 2725 in the OS 2720 can check the interruption and then handle the interruption by communicating with the core part of the H / W 2710. For example, if the character 'R' is input via the keyboard constituting H / W 2710, the interrupt can be passed to the management 2725 in OS 2720, or it can be passed directly to the core of H / W 2710. The core of H / W 2710 can output the value 'R' to the display via a predetermined function block.

FIG. 28 illustrates an example of a service using an IoT device according to an embodiment of the present disclosure. Here, it will be assumed that the IoT device is a wearable IoT device.

Referring to FIG. 28, a scenario using an IoT device may include health services, personal security services, social network service (SNS) services, information services, smart home services, and the like. To this end, the IoT service system 2800 may include at least one IoT device 2810, GW 2820, server 2830, and at least one service provider 2840, 2850, or 2860.

The IoT device 2810 may be implemented by a wearable IoT device such as: smart glasses, headphones, electrocardiograph / photoplethysmograph (ECG / PPG) measurer, belt, belt / meter, blood glucose level tester, temperature Control clothes, shoes, necklaces and the like. The wearable IoT device may include a sensor for sensing the status of the user 2812, the surrounding environment, and / or the user's commands. The IoT device 2810 may have a built-in battery or include a wireless charging function for power supply. The IoT device 2810 may include a wireless communication function for communicating with the outside.

The GW 2820 can transmit the information collected by the sensors to the server 2830 or the analysis information transmitted from the server 2830 to the IoT device via the communication network. For example, the GW 2820 may be connected to an IoT device via a short-range wireless communication protocol, and a smart phone capable of connecting with a wireless communication network such as Wi-Fi, 3G, or LTE may be used as the GW 2820. The GW 2820 can be connected to the server 2830 via the Internet or a wireless communication network.

The server 2830 may generate service information by storing or analyzing the collected information, or provide the stored information and / or analysis information to the service provider 2840, 2850, or 2860.

The service provider 2840, 2850, or 2860 may analyze the collected information and provide the analyzed information to the user 2812. Here, the service may refer to providing useful information, alerts, and personal protection for the user 2812, or providing control information of the wearable IoT device 2810.

Among the service providers, the smart home service provider 2850 can identify the user information received from the user 2812, and control the IoT device provided in the home of the user 2812 based on the value set in the server. For example, the smart home service provider 2850 may provide for controlling IoT devices related to heating / cooling installed in the home of the user 2812, IoT devices related to energy resources such as gas, water, and electricity, and Smart home services such as IoT devices related to indoor conditions such as lighting, humidity, and clean air, and / or IoT devices related to exercise prescriptions determined in consideration of the daily activities of users 2812.

The leisure service provider 2840 may provide services related to the leisure activities of the user 2812. For example, the leisure service provider 2840 may recommend food and shopping information, restaurants, and the like by receiving information about the physical condition or location of the user 2812.

The health and safety service provider 2860 may provide emergency medical / policing services based on the status information of the user 2812. In addition, the health and safety service provider 2860 can send an alert to the user 2812, or pass the precautions to the user 2812 based on the information about the spread of the virus, and can also recommend the food and diet information that the user 2812 should pay attention to for health.

The smart glasses may be worn on the face of the user 2812. Smart glasses can be achieved by using dry eye sensors, blink sensors, image sensors, electroencephalogram (EEG) sensors, touch sensors, speech recognition sensors, GPS, and the like The surrounding environment of the user 2812, the state (or condition) of the user 2812, and commands of the user 2812 are sensed. The information sensed by the smart glasses can be transmitted to the server 2830.

The server 2830 can provide effective services to the user 2812 based on the sensed information. For example, the server 2830 can send electrical stimulation information to the user 2812 based on the EEG information received by the user 2812. Based on the electrical stimulation information, the server 2830 can process abnormal brain waves. In this case, the smart glasses may process the abnormal brain waves of the user 2812 or adjust the emotion of the user 2812 by using the electrical stimulation information.

The headset may be worn by the user 2812 in such a manner that the headset is inserted into or covered by the ear. The headset may sense the physical information and commands of the user 2812 by using a temperature sensor, an image sensor, a touch sensor, and the like.

The ECG / PPG measuring device can use the ECG sensor to measure the ECG of the user 2812. The belt may include a sensor for measuring waist, breathing, or obesity of the user 2812, and may also include a vibration function or an electrical stimulation function for treating obesity or pain. Bands / watches can include sensors related to the user's temperature, heart rate, sleep, pressure, UV, oxygen saturation, optics, gyroscope, GPS, PPG, ECG, skin conductivity, pedometer, and the like . The band / table may include a gas injection function or the like for combating harassment.

The blood glucose level tester may include a sensor for measuring the blood glucose level of the user 2812. The sensor for measuring the blood glucose level may be a non-invasive sensor. The measured blood glucose level can be transmitted to the server 2830 via the smart phone of the user 2812 or the GW 2820.

The temperature-controlled clothing may include a sensor for measuring the body temperature or ambient temperature of the user 2812. The temperature-controlled clothing can control the heating / cooling function by comparing the measured temperature with a predetermined temperature. The temperature-controlled garment may be, for example, a baby or adult diaper or underwear. The paper diaper or underwear may sense the state of the user 2812 by embedding a skin conductivity sensor, a temperature sensor, a strip detection sensor, or a pressure sensor therein, and notify the paper based on the sensing result Change time of diaper or underwear or perform heating / cooling function. Paper diapers or underwear can be embedded with thin hot wires or cooling tubes for heating / cooling.

The shoe may include sensors for the weight of the user 2812, pressure in each part of the sole, air pollution in the shoe, humidity, odor, GPS, and the like. The information collected by these sensors can be transmitted to the server 2830. The server 2830 may transmit to the user 2812 information such as an alarm for notifying the user 2812 of posture correction and shoe cleaning or replacement. Applications installed on the smartphone can perform these operations on behalf of the server 2830.

The necklace may include sensors for sensing the user's breath, pulse, body temperature, exercise, calorie burn, GPS, EEG, voice, ECG, PPG, and the like. The information collected by the sensor can be analyzed by itself in the IoT device or transmitted to the server 2830.

The service providers 2840, 2850, and 2860 may provide related services to the user 2812 based on the user information provided via the server 2830. For example, after the dog's voice is sensed through a necklace mounted around the dog's neck, the service provider can provide a voice translation service based on the sensed information. The information provided by the speech translation service can be played by speakers built into the necklace.

The foregoing embodiments have been described with respect to only some use cases regarding health, smart home, leisure, and the like. However, the proposed IoT service system 2800 can be used in a wide range of industries and is not limited thereto. For example, it is clear that the IoT service system 2800 can even be applied to services for e-commerce, logistics, building management, and the like.

Multiple IoT devices for the proposed embodiment may share a single user identification information or a network access information that replaces the user identification information. For example, it can be assumed that the smart phone is equipped with a SIM card having user identification information, and a communication link is formed between the smart phone and various IoT devices shown in FIG. 28. Smartphones can share their user identification information or network access information with various IoT devices via communication links. In this case, various IoT devices can access the communication network based on the shared network access information, and exchange information with the server 2830 via the communication network.

In order for various IoT devices to access a communication network based on shared network access information, a schedule for use may be applied. By doing so, it is possible to prevent one user from simultaneously connecting multiple IoT devices to the communication network based on the same user identification information.

FIG. 29 illustrates an example of a service using an IoT device according to an embodiment of the present disclosure. It is assumed herein that the IoT device is an IoT device applicable to a vehicle.

Referring to FIG. 29, an IoT device applied to a vehicle may provide usage scenarios regarding vehicle management, collision avoidance, vehicle operation services, and the like. To this end, the IoT service system 2900 may include one vehicle 2912 having a plurality of sensors. The IoT service system 2900 may include an engine control unit (ECU) 2920, a server 2932, and at least one service provider 2938 or 2940.

The vehicle 2912 may include a plurality of sensors, such as an engine part sensor, an anti-collision sensor, a vehicle operation sensor, and the like. The engine part sensor may include at least one of the following: a blood oxygen sensor, a coolant temperature sensor, a coolant level sensor, a manifold absolute pressure sensor (or a MAP sensor) ), BARO pressure sensor (BRO pressure sensor; BPS), throttle position pressure sensor (TPS), mass airflow sensor (MAF), leaf air flue sensor, card Karman vortex gas flu sensor, knock sensor, air temperature sensor, exhaust gas recirculation valve position sensor (EGR), crankshaft position sensor (CKP), camshaft position sensor , Engine oil level sensor, transmission oil level sensor, brake oil level sensor.

The BPS can measure the air pressure and provide the measured air pressure to the ECU 2920. The ECU 2920 may consider the air pressure measured by the BPS to correct the fuel injection amount, the ignition timing, and the like. The MAP sensor can use the pressure of the inlet manifold to provide volume information to the ECU 2920. The MAF sensor provides information about the quality of the inlet air to the ECU 2920. The ECU 2920 may use the information about the quality of the inlet air provided by the MAF sensor to determine the amount of fuel.

A leaf flu sensor is a sensor provided by connecting a moving blade to a variable resistor in an engine air inlet system. The Kaman vortex gas flu detector is a hot wire or hot film gas flu detector. The knock sensor, which is a sensor for detecting knock occurring in the engine, may be an acceleration sensor. For the exhaust gas recirculation valve position sensor (EGR), if the combustion gas has a large amount of carbon monoxide (CO) or hydrocarbons (HC), the blood oxygen sensor can provide a signal value to the ECU 2920. The ECU 2920 can transmit the signal value to the EGR solenoid valve so that the exhaust gas can be recovered.

The crankshaft position sensor (CKP) is a sensor used to detect the number of revolutions of the engine and the precise position of the piston. The camshaft position sensor is a sensor for controlling fuel injection timing and ignition timing.

The anti-collision sensor may include at least one of the following: an airbag collision sensor, a front video camera, a rear video camera, an infrared camera, a multi-beam laser, a long-range radar, a short radar, and an ultrasonic sensor Device.

The vehicle operation sensor may include at least one of the following: GPS, temperature sensor, humidity sensor, tire pressure sensor, steering angle sensor, wheel speed sensor (WSS or ABS) , Vehicle speed sensor (VSS), gravity sensor, electromechanical steering system, electronic accelerator and electronic circuit breaker.

The ECU 2920 may collect vehicle driving information 2924 received from a plurality of sensors, and transmit the collected vehicle driving information 2924 to a server 2932 via a communication network. The ECU 2920 and the server 2932 can communicate (or exchange) vehicle status information 2926, driver information 2928, and / or accident history information 2930 with each other.

The service company 2938 may refer to the vehicle status information 2926, the driver information, and / or the accident history information 2930 stored in the server 2932 to provide various services such as analysis information for vehicles and alarms. For example, various services may include at least one of a road accident information service, an express direction service, an accident disposal notification service, an accident insurance premium calculation information service, a failure rate decision information service, an emergency roadside service, and the like. The service company 2938 may share the vehicle-related information stored in the server 2932 with the contract user. The contract user 2934 can enter the contract with the service company 2938 based on the shared information.

The contract user 2934 may be a vehicle manufacturer. In this case, the vehicle manufacturer may perform tasks such as vehicle recall and establishment of a vehicle advertising plan based on information provided by the self-service company 2938. The service company 2938 may be a car sharing / transport company. In this case, the service company 2938 can provide the vehicle information to the contract user 2934 and provide the vehicle so that the contract user 2934 can drive the vehicle, or can provide a ride-hailing service so that the contract user 2934 can board the vehicle.

The service company 2938 can realize the access control and service functions of the vehicle owned by the driver 2922 by receiving personal information of the driver stored in the second server 2936. For example, the service company 2938 can receive the NFC tag information stored in the driver's 2922 table, and compare the received NFC tag information with the NFC tag information stored in the server to release the vehicle's locking device. In addition, when the vehicle arrives at the home of the driver 2922, the service company 2938 may transmit the vehicle arrival information to the home of the driver 2922.

The public service provider 2940 may refer to the accident history information 2930 stored in the server 2932 to provide road accident information, roundabout information, disaster alarms, and the like to multiple drivers. The utility service provider 2940 may develop a plan to build a safety infrastructure based on collected vehicle driving information.

According to an embodiment of the present disclosure, multiple IoT devices installed in a vehicle may share a single user identification information or a network access information that replaces the user identification information. For example, it can be assumed that a driver's smart phone is equipped with a SIM card having user identification information, and a communication link is formed between the smart phone and various IoT devices installed in a vehicle. Smartphones can share their user identification information or network access information with various IoT devices via communication links. In this case, various IoT devices can access the communication network based on the shared network access information, and exchange information with the server 2932 via the communication network.

In order for various IoT devices to access a communication network based on shared network access information, a schedule for use may be applied. By doing so, it is possible to prevent one user from simultaneously connecting multiple IoT devices to the communication network based on the same user identification information.

FIG. 30 schematically illustrates the packaging of an IoT device according to an embodiment of the disclosure.

Referring to FIG. 30, the flexible packaging device 3000 may correspond to the IoT device 2500 or 2600 shown in FIG. 25 or FIG. 26. The flexible packaging device 3000 may include a flexible packaging substrate 3010 and first to fifth components 3011 to 3015.

The first component 3011 may include a security module (eg, 2620 in FIG. 26). In this case, the first component 3011 may be a system-in-package (SiP) on which the processor and the secure element are stacked. The fourth component 3014 and the fifth component 3015 may include an AP, a memory, and / or a storage device. For example, the AP, memory, and / or storage device that may be included in the fourth component 3014 and the fifth component 3015 may correspond to the AP 2610, the memory 2614, and / or the storage device 2612 shown in FIG. 26, respectively. The third component 3013 may include a sensor (eg, 2632 and / or 2634 in FIG. 26).

At least one of the first to fifth components 3011 to 3015 may be any one of the communication interface 2626, the actuator 2628, the power supply 2620, or a passive element (not shown) shown in FIG. 26.

The flexible package substrate 3010 is a flexible printed circuit board that can be easily bent and can be used in wearable IT devices and the like, and the flexible package substrate 3010 can be an organic substrate or a tape substrate. The flexible package substrate 3010 may include, for example, a core board 3002 having an upper surface and a lower surface, and a resin layer 3001 formed on the upper surface and the lower surface.

The resin layer 3001 may be formed in a multilayer structure. A signal layer, a ground layer, or a power supply layer constituting the wiring pattern 3003 may be interposed between the multilayer structures. An individual wiring pattern may be formed on the resin layer 3001. In the drawings, the fine pattern drawn on the flexible package substrate 3010 may mean a wiring pattern 3003 or a plurality of passive elements (not shown).

A solder bump 3004 may be added as one of the members connecting the flexible package substrate 3010 and the component 3011. An underfill material 3005 may be inserted around the solder bump 3004. The underfill material 3005 can protect the solder bump 3004 from physical stress. The flexible package substrate 3010 and the components 3011 to 3015 may be connected by a thermal compression bonding method, which uses a metal material (for example, Cu, Au, and the like) instead of the solder bump 3004.

The components 3011 to 3015 may be mounted on the flexible package substrate 3010 via external connection members and the like, but are not limited thereto. In other words, more semiconductor wafers can be mounted on the flexible package substrate 3010, and the semiconductor wafers can be stacked vertically with each other using a suitable connection method to reduce the mounting area.

The foregoing illustrates embodiments and should not be construed as limiting. Although a few embodiments have been described, those skilled in the art will readily appreciate that many modifications in the embodiments are possible without substantially departing from the scope of the inventive concept. Accordingly, all such modifications are intended to be included within the scope of the inventive concept as defined by the scope of the following patent applications.

110, 700, 1110, 1730, 1810, 1870, 1910, 2004, 2014, 2016, 2034: main control device 120, 630, 800, 1140, 1720, 1820, 1850, 1880, 1920, 1930: controlled device 130, 470: Interface 140: Public Wireless Network (PWN) 210, 210a, 210b, 210c, 210d, 1721, 1731, 1751: Network Access Information (NAI) 220, 1726, 1736, 1745, 1816, 1826, 1835, 1855, 1864, 1885, 1894: User Identification Information (SII) 221: International Mobile Subscriber Identity (IMSI) 223: Temporary Mobile Subscriber Identity (TMSI) 225: Integrated Circuit Card Identification (ICCID) 227: Master Key ( K) 229: Globally Unique Temporary Identifier (GUTI) 230: Network Status Information (NSI) 231: PWN Cell Identification Information 233: Radio Resource Control (RRC) Status Information 235: User Tracking Area (TA) Information 237: Non-Storage Layering (NAS) status information 300: network environment 301, 302, 304, 401, 2026, 2028: user equipment (UE) 306, 2830, 2932: server 310, 1312: bus 320: processor 330, 2614, 2713: Memory 350: Input / output (I / O) interface Surface 360: display module 362: network 364: wireless or wired communication 370, 2626, 2714: communication interface 400: examples 410, 740, 830, 1410, 2510, 2610, 2711: application processor (AP) 420: Communication module 421: Wired connectivity unit 422: Radio frequency (RF) module 423: Communication processor 424: Wireless connectivity unit 425: BT module 426: GPS module 427: NFC module 428, 720: SIM card 430 , 2530: Memory 432: Internal memory 434: External memory 440: Sensor module 440A: Motion sensor 440B: Gyroscope sensor 440C: Atmospheric pressure sensor 440D: Magnetic sensor 440E : Acceleration sensor 440F: Grip sensor 440G: Proximity sensor 440H: Color sensor (eg, red / green / blue (RGB) sensor) 440I: Biometric sensor 440J: Temperature / humidity Sensor 440K: Illuminance sensor 440L: Ultraviolet (UV) sensor 450: Input device 452: Touch panel 454: (Digital) pen sensor 456: Button 458: Ultrasonic input device 460, 2540: Display 462: Panel 464: Hologram device 46 6: Projector 472: HDMI 474: USB 476: Optical interface 478: D-sub (D-sub) 480: Audio module 482: Speaker (SPK) 484: Receiver 486: Headphone 488: Microphone 491: Camera mode Group 495: Power management module 496: Battery 497: Indicator 498: Motor 510: Program module 520: Core 521: System Explorer 523: Device driver 530: Intermediate software 535: Runtime library 541: Application Manager 542: window manager 543: multimedia manager 544: resource manager 545: power manager 546: library manager 547: package manager 548: connectivity manager 549: notification manager 550: location manager 551 : Graphic Manager 552: Security Manager 560: API 570: Application 571: Homepage 572: Dialpad 573: Short Message Service (SMS) / Multimedia Messaging Service (MMS) 574: Instant Messaging (IM) 575: Browser 576 : Camera 577: Alarm 578: Contact 579: Voice Dial 580: Email 581: Calendar 582: Media Player 583: Photo Album 584: Clock 620: First Main control devices 622, 632, 642, 710, 810, 1424: communication processors 624, 644: SIM 626, 636, 646: wireless connectivity units 628, 638, 648: wired connectivity units 634: non-volatile memory (NVM) 640: second master device 650: wireless connectivity link 660: wired connectivity link / wired communication link 730, 820, 1319: connectivity unit 910, 912, 914, 916, 918, 920, 922, 924, 926, 928, 930, 934, 1010, 1012, 1014, 1016, 1018, 1020, 1022, 1024, 1026, 1112, 1114, 1116, 1122, 1124, 1126, 1128, 1210, 1212, 1214, 1940, 1950, 1960, 1970: operations 1120, 1740, 1830, 1860, 1890, 2002: base station 1130, 1750, 1840: mobile management entity (MME) 1310A, 1310B, 1310C, 1310D, 1310E: application processor (AP) chip 1311: central processing unit (CPU) 1313: SMC 1314: DMC 1315, 1316: communication interface 1317, 1422: modem 1318, 1480: dynamic RAM (DRAM) 1320, 1370, 1490: flash memory ( Or non-volatile memory (NVM)) 1330: DRAM / DRAM memory 13 40: modem chip 1350: connectivity chip 1360: NVM / SIM 1426: internal memory 1430: memory interface 1440: peripheral interface 1450: connectivity module 1460: network on chip (NOC) 1472: audio subsystem 1474: System timers 1476, 2620: Security module 1478: Multimedia modules 1610, 1800A, 1800B, 1800C: Example 1620: First layer 1622: Physical layer 1630: Second layer 1632, 1735, 1725, 1735, 1744, 1815, 1825, 1834, 1854, 1863, 1884, 1893: Media Access Control (MAC) 1634, 1724, 1734, 1743, 1814, 1824, 1833, 1853, 1862, 1883, 1892: Radio Link Control (RLC) 1636, 1723, 1733, 1742, 1813, 1823, 1832, 1852, 1862, 1882, 1891: Packet Data Aggregation Control (PDCP) 1640: Third layer 1642, 1722, 1732, 1741, 1812, 1822, 1831: RRC 1644, 1721 , 1731, 1751, 1811, 1821, 1841: NAS 1650: fourth layer 1652: mobile status transfer layer 1700: M2M mobile status transfer protocol 1710A, 1710B: application data 1752: mobile status transfer layer 1851, 1871, 1881: application Program Data 2000: Mega cell 2012: Relay device (EXO-US) 2020: Small cell 2022: Relay device 2024: Heterogeneous device (EXO-UE) 2032: Controlled device (EXO-US) 2200: Heterogeneous UE (HetUE) 2210: user 2220: operator 2230: chipset supplier and UE manufacturer 2300A: IoT system 2300B: IoT network system 2310, 2320, 2330, 2340, 2400, 2500, 2600, 2810: IoT device 2350: access point ( AP) 2360, 2820: Gateway (GW) 2370: Communication network (CN) 2380: Management server 2390: Server 2390-A, 2390-B, 2390-C: Sub-servers 2410, 2560, 2632 2634, 2712: sensor 2420, 2616: display 2430: button 2440: package 2450: internal status information 2460: icon 2470: support 2622: processor 2520: communication interface (transmitter / receiver) 2550, 2618: I / O interface 2612: Storage device 2624: Security element 2628: Actuator 2630: Power supply 2710: Hardware (H / W) 2715: I / O interface and display 2720: Operating system (OS) 2721: Driver 2722: Firmware 2723: Security 2724: Network 2725 Management 2726: Application Protocol Interface (API) 2727: Library 2730: Application Program (APPS) 2740, 2812, 2814: User 2800, 2900: IoT Service System 2840, 2850, 2860: Service Provider 2912: Vehicle 2920: Engine control unit (ECU) 2922: driver 2924: vehicle driving information 2926: vehicle status information 2928: driver information 2930: accident history information 2934: contract user 2936: second server 2938: service provider / service company 2940 : Service provider / Public service provider 3000: Flexible packaging device 3001: Resin layer 3002: Core board 3003: Wiring pattern 3004: Solder bump 3005: Underfill material 3010: Flexible packaging substrate 3011: First component 3012: second component 3013: third component 3314: fourth component 3015: fifth component ①, ②, ③, ④, ⑤, ⑥, ⑦, ⑧, ⑨, ⑩, ⑪: process

Several embodiments of the inventive concept are illustrated by examples. FIG. 1 is a block diagram generally illustrating a wireless communication environment according to an embodiment of the inventive concept. Figure 2 is a table listing examples of possible components of network access information. FIG. 3 is a block diagram illustrating a network environment according to an embodiment of the inventive concept. FIG. 4 is a block diagram further illustrating a user equipment according to an embodiment of the inventive concept in one example. FIG. 5 is a block diagram further illustrating, in one example, a program module according to some embodiments of the inventive concept. FIG. 6 is a block diagram illustrating various connections between multiple user equipments (UEs) and a public wireless network according to some embodiments of the inventive concept, in one example. FIG. 7 is a block diagram illustrating certain components of a master control device according to an embodiment of the inventive concept. FIG. 8 is a block diagram illustrating certain components of a controlled device according to an embodiment of the inventive concept. FIG. 9 is a flowchart outlining a control flow in a master control device according to an embodiment of the inventive concept. FIG. 10 is a flowchart outlining a control flow in a controlled device according to an embodiment of the inventive concept. FIG. 11 is an operation diagram illustrating a call processing program that can be used with certain embodiments of the inventive concept. FIG. 12 is a general flowchart outlining a control flow in a base station according to an embodiment of the inventive concept. 13A, 13B, 13C, 13D, and 13E are block diagrams illustrating components of a user equipment according to various embodiments of the inventive concept, respectively. FIG. 14 is a conceptual diagram illustrating an agreement stack that can be used with a user equipment according to various embodiments of the inventive concept, in one example. FIG. 15 is a conceptual diagram illustrating an M2M action state transfer protocol via a action state transfer layer that may be used with certain embodiments of the inventive concept, in one example. FIG. 16 is a conceptual diagram illustrating various examples of data plane control and control of a controlled device operating in a relay mode in an independent mode. FIG. 17 is a block diagram illustrating an M2M mobile state transfer protocol 1700 via a mobile state transfer layer according to an embodiment of the inventive concept, in one example. 18A, 18B, and 18C are respective examples of control and data planes of a controlled device 1820 operating in independent mode and relay mode according to some embodiments of the inventive concept. FIG. 19 illustrates an example of an implementation of one NAI shared by multiple devices according to an embodiment of the present disclosure. FIG. 20 illustrates examples of various implementations of an embodiment according to the present disclosure. FIG. 21 illustrates a network structure that can implement the present disclosure. FIG. 22 illustrates the effects expected by embodiments of the present disclosure. 23A and 23B illustrate examples of an IoT system according to various embodiments of the present disclosure. FIG. 24 illustrates the appearance of a smart watch as an example of an IoT device according to an embodiment of the present disclosure. FIG. 25 illustrates an example of a configuration of an IoT device according to an embodiment of the present disclosure. FIG. 26 illustrates another example of a configuration of an IoT device according to an embodiment of the present disclosure. FIG. 27 conceptually illustrates a hardware (H / W) and software (S / W) structure of an IoT device according to an embodiment of the present disclosure. FIG. 28 illustrates an example of a service using an IoT device according to an embodiment of the present disclosure. Here, it will be assumed that the IoT device is a wearable IoT device. FIG. 29 illustrates an example of a service using an IoT device according to an embodiment of the present disclosure. FIG. 30 schematically illustrates the packaging of an IoT device according to an embodiment of the disclosure.

Claims (18)

A master control device comprising: a first memory storing user identification information (SII) for allowing the master control device to connect to the master control device via a public wireless network (PWN) communication service; communication processing A device connected to the communication service in the main control device, and in response to the connection of the communication service in the main control device, generating a network state information (NSI) including generated by the communication processor Network access information (NAI), and stores the NAI in the second memory; a connectivity unit for establishing a communication link between the master control device and the controlled device, wherein the connectivity unit Sending the NAI stored in the second memory to the controlled device via the communication link, so that the controlled device is enabled to directly connect via the PWN using the sent NAI The communication service, the connectivity unit receiving, from the controlled device via the communication link, an updated including an updated NSI associated with the connection of the communication service in the controlled device NAI, the communication The processor updates the NAI stored in the second memory according to the updated NAI received by the connectivity unit. The master control device according to item 1 of the patent application scope, wherein the communication processor terminates the communication service in the master control device after sending the NAI to the controlled device via the communication link. The connection. The main control device according to item 1 of the scope of patent application, wherein the SII includes a plurality of SII components, and the NAI stored in the second memory includes the SII components from the plurality of SII components. Information derived from at least one of them. The master control device according to item 3 of the scope of patent application, wherein the SII component includes at least one of the following: temporary mobile subscriber identity (TMSI), globally unique temporary identifier (GUTI), integrated Circuit Card Identification (ICCID), International Mobile Subscriber Identity (IMSI), and master key. The master control device according to item 1 of the patent application scope, wherein the NAI includes a temporary mobile user identification code provided from the PWN to the master control device when the communication service in the master control device is connected. (TMSI). The main control device according to item 1 of the patent application scope, wherein the communication processor updates all the data stored in the second memory before terminating the connection of the communication service in the controlled device. Mentioned NAI. The master control device according to item 1 of the patent application scope, wherein the NSI includes at least one of the following: PWN cell identification information, radio resource control (RRC) status information, and non-access stratum (NAS) status Information and user tracking area (TA) information. The main control device according to item 1 of the patent application scope, wherein the main control device is a portable electronic device, the communication service is a cellular voice / data service, and the communication service in the main control device The connection includes registering the master control device with a mobility management entity (MME) of the PWN. The main control device according to item 1 of the scope of patent application, wherein the communication link includes a local area network (LAN), Wi-Fi, near field communication (NFC), radio frequency (RF), wired communication, and a cellular chain At least one of Bluetooth, Bluetooth (BT), and Global Positioning System (GPS). A master control device includes: a communication processor that uses a stored user identification information (SII) to connect a communication service in the master control device via a public wireless network (PWN) to generate a communication with the master control device; Network state information (NSI) associated with the connection of the communication service, and storing the NSI in the master control device; a connectivity unit that establishes a direct connection between the master control device and multiple slave devices A communication link of at least one controlled device selected from among, and sending the NSI from the master control device to the at least one controlled device via the communication link, wherein in response to the use of the at least one controlled device, The NSI connection sent is via the communication service of the PWN, and the connectivity unit receives a connection associated with the connection of the communication service by the at least one controlled device via the PWN. The updated NSI, and the communication processor updates the stored NSI according to the updated NSI. The master control device according to claim 10, wherein the communication processor terminates the master control device after the NSI is sent to the at least one controlled device via the communication link. The connection of the communication service. The main control device according to item 10 of the scope of patent application, further comprising: a user identity identification module (SIM) storing the SII, wherein the connectivity unit sends at least one of the SII via the communication link. Partially from the NSI to the at least one controlled device. The main control device according to item 10 of the scope of patent application, wherein the main control device is a portable electronic device, the communication service is a cellular voice / data service, and the communication service in the main control device The connection includes registering the master control device with a mobility management entity (MME) of the PWN. A controlled device includes: a connectivity unit for establishing a communication link between the controlled device and a master control device, and receiving communications including controlling the master device via a public wireless network (PWN) Network access information (NAI) of the connected network status information (NSI) of the service; a communications processor, receiving the NAI from the master control device, and using the NAI to initially establish the controlled via the PWN The communication service in the device generates an updated NAI including an updated NSI while storing the connection of the communication service in the controlled device, and stores the updated NAI, wherein the updated NAI The connectivity unit sends the updated NAI to the master control device via the communication link, so that the master control device is enabled to reconnect with the master control device using the updated NAI. Communication service. The controlled device according to item 14 of the application, wherein the connectivity unit is further configured to establish a communication link between the controlled device and another device different from the main control device. The controlled device according to item 14 of the patent application scope, wherein the communication processor sends the updated NAI to the master control device via the communication link, and then terminates all of the controlled devices. The link of the communication service. The controlled device according to item 14 of the patent application scope, wherein the NAI includes a temporary mobile user identifier provided from the PWN to the controlled device while maintaining the communication service in the controlled device. (TMSI). The controlled device according to item 14 of the scope of patent application, wherein the controlled device is a portable electronic device, the communication service is a cellular voice / data service, and the communication service in the controlled device The connection includes registering the controlled device with a mobility management entity (MME) of the PWN using the NAI received from the master control device.