Patent Description:
In general, a mobile communication system has been developed for the purpose of providing communication while ensuring the mobility of a user. The remarkable development of technology of the mobile communication system has brought high-speed data communication services as well as voice communication.

In recent years, standardization for a long-term evolution (LTE) system (evolved packet system (EPS) and 4th generation (<NUM>) system), as a next generation mobile communication system, has been processed by 3rd generation partnership project (3GPP). The LTE system is a technology for implementing high-speed packet-based communication with a transfer rate of up to about <NUM> Mbps higher than the data rate currently provided and is being standardized for commercialization by <NUM>.

In addition, in order to meet a growing demand for wireless data traffic after commercialization of <NUM> communication systems, efforts are underway to develop improved 5th generation (<NUM>) communication systems or pre-<NUM> communication systems. For this reason, <NUM> communication systems or pre-<NUM> communication systems are referred to as "beyond-<NUM> network communication systems" or "post-LTE systems.

In order to achieve a high data rate, implementation of <NUM> communication systems in super-high frequency (mm Wave) bands (e.g., a band of <NUM>) is being taken into consideration. In order to mitigate the path loss of radio waves and in order to increase the propagation distance of radio waves in super-high frequency bands, technologies, such as beamforming, massive multiple-input and multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large scale antennas, are being discussed in <NUM> communication systems.

Further, in order to improve the network of a system, technologies, such as evolved small cells, advanced small cells, a cloud radio access network (cloud radio access network (RAN)), an ultra-dense network, device-to-device (D2D) communication, wireless backhaul, moving networks, cooperative communication, coordinated multi-points (CoMP), interference cancellation, and the like, are being developed in <NUM> communication systems. In addition, in <NUM> systems, advanced coding modulation (ACM) schemes, such as hybrid frequency-shift keying (FSK) and quadrature amplitude modulation (QAM) (FQAM) and sliding window superposition coding (SWSC), and advanced connection technologies, such as filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA), are being developed.

Meanwhile, the Internet is evolving from a human-centered network, in which humans produce and consume information, into an Internet-of-things (IoT) network in which distributed components, such as things, exchange information with each other and process the same. Internet-of-everything (IoE) technology, which combines IoT technology with big-data processing technology through connection with cloud servers or the like, is also emerging. In order to implement IoT, technology elements, such as sensing technology, wired/wireless communication and network infrastructure, service interface technology, security technology, or the like, are required. Thus, in recent years, technologies for connecting things, such as a sensor network, machine-to-machine (M2M) communication, machine-type communication (MTC), or the like, have been studied. The IoT environment may provide intelligent Internet technology services that collect and analyze data produced from connected things, thereby creating new value in human life. The IoT may be applied to the fields of smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, health care, smart home appliances, and advanced medical services through fusion and combination between the existing information technology (IT) and various kinds of industries.

Accordingly, various attempts have been made in order to apply the <NUM> communication system to the IoT network. For example, technologies, such as a sensor network, M2M communication, MTC, or the like, have been implemented by means of <NUM> communication techniques such as beamforming, MIMO, array antennas, or the like. The application of the cloud RAN, as the big-data processing technology described above, may be an example of the fusion of <NUM> technology and IoT technology.

An example of the prior art can be found in document D1: "<NPL>.

Accordingly, an aspect of the disclosure is to provide a method for releasing a terminal, which has no subscriber identification module (SIM) profile, such as an open market terminal equipped with an embedded SIM (eSIM), is allowed to connect to a cellular network without authentication, and is provided with restricted local operator services (RLOS) by the provider, from the network at an appropriate time, unlike normal terminals connected to the cellular network. In addition, it is another aspect of the disclosure to provide a method of providing the terminal with information on how long the service will be available or information on when the service will expire and of terminating the connection of the terminal when the service is unavailable.

The technical problems to be solved by the disclosure are not limited to the above-mentioned technical problems, and other technical problems, which are not mentioned, will be clearly understood by those skilled in the art from the description below.

In accordance with an aspect of the disclosure, a method of a gateway (GW) in a wireless communication system is provided. The method includes configuring a packet data network (PDN) connection for restricted local operator services (RLOS), determining whether an expiration condition of the RLOS is satisfied, and deactivating the PDN connection for the ROLS, in case that the expiration condition of the RLOS is satisfied.

The configuring the PDN connection for the RLOS comprises receiving, from a mobility management entity (MME), a first message for configuring the PDN connection for the RLOS, configuring the PDN connection for the RLOS, and transmitting, to the MME, a second message in response to the configuring of the PDN connection for the RLOS.

The method further comprises configuring the expiration condition of the RLOS for the PDN connection.

In one embodiment, the expiration condition for the RLOS includes a preconfigured period time for the RLOS.

In accordance with the disclosure, a method of a terminal in a wireless communication system is provided. The method includes configuring a packet data network (PDN) connection for restricted local operator services (RLOS), and deactivating the PDN connection for the ROLS, in case that an expiration condition of the RLOS being satisfied is determined by a gateway (GW).

The configuring the PDN connection for the RLOS comprises transmitting, to a mobility management entity (MME), a first message for configuring the PDN connection for the RLOS, and receiving, from the MME, a second message in response to the configuring of the PDN connection for the RLOS.

The method further comprises receiving, from a mobility management entity (MME), the expiration condition of the RLOS for the PDN connection.

The expiration condition for the RLOS includes a preconfigured period time for the RLOS.

In accordance with the disclosure, a gateway (GW) in a wireless communication system is provided. The GW includes a transceiver, and a controller configured to configure a packet data network (PDN) connection for restricted local operator services (RLOS), determine whether an expiration condition of the RLOS is satisfied, and deactivate the PDN connection for the ROLS, in case that the expiration condition of the RLOS is satisfied.

In accordance the disclosure, a terminal in a wireless communication system is provided. The terminal includes a transceiver, and a controller configured to configure a packet data network (PDN) connection for restricted local operator services (RLOS), and deactivate the PDN connection for the ROLS, in case that an expiration condition of the RLOS being satisfied is determined by a gateway (GW).

An embodiment of the disclosure can provide a method of notifying a terminal connected to the network without authentication of conditions for terminating the connection and a method of releasing the connection of the terminal from the network according to the connection termination condition. In addition, an embodiment of the disclosure can provide a method of preventing an unauthenticated terminal from unnecessarily and continuously accessing the network and allowing the terminal or the user to request connection extension as necessary, thereby enabling efficient management of the connection resources of a cellular network with respect to the unauthenticated terminal.

Further, the size of each element does not entirely reflect the actual size.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart block or blocks.

Each block of the flowchart illustrations may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing the specified logical function(s).

As used herein, the "unit" refers to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the "unit" does not always have a meaning limited to software or hardware. The "unit" may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The elements and functions provided by the "unit" may be either combined into a smaller number of elements, "unit" divided into a larger number of elements, "unit. " Moreover, the elements and "units" or "modules" may be implemented to reproduce one or more central processing units (CPUs) within a device or a security multimedia card. Further, in the embodiments, the "unit" may include at least one processor.

In order to provide a subscriber identification module (SIM) profile to a terminal that has no SIM profile, such as an open market terminal equipped with an embedded SIM (eSIM), a method of providing restricted services to the terminal that has no SIM profile by allowing the terminal to access a cellular network is under discussion. In this case, the terminal connected to the network may be provided with services, such as SIM provisioning, internet protocol (IP) multimedia core network subsystem (IMS) voice calls, or the like, from the provider through restricted local operator services (RLOS).

If the connection with the terminal is continuously maintained, there may be a burden on the processing capacity of the network and a threat to security. Therefore, unlike an ordinary terminal connected to the cellular network through a user services identity module (USIM), a method for releasing the unauthenticated terminal from the network at an appropriate time is required.

<FIG> is a view illustrating a structure of a cellular network for serving an unauthenticated terminal according to an embodiment of the disclosure.

Referring to <FIG>, for RLOS, a terminal (e.g., user equipment (UE)) <NUM> may select a network providing the RLOS, and may access the same. The terminal <NUM> may secure connectivity without an authentication process when accessing a packet core network, and then may be provided with the RLOS from the provider.

The packet core network to which the terminal <NUM> connects in order to secure connectivity may be, for example, a cellular network providing data communication, such as an evolved packet system (EPS) providing LTE network services or a <NUM> system network. There is a mobility management (MM) functional entity for mobility management of the terminal and a session management (SM) functional entity for session management, which process signaling messages.

In the case of the EPS, as shown in <FIG>, a mobility management entity (MME) <NUM> serves as the MM functional entity and the SM functional entity. The MME <NUM> may select a gate way (GW) <NUM> providing the RLOS for the terminal <NUM> connected for the RLOS, and the terminal <NUM> may connect to an application server (AS) <NUM> via the GW <NUM> through a limited connectivity service. For example, the AS <NUM> may be a captive portal, or may be a proxy-call session control function (P-CSCF) in the case of an IMS service. In a <NUM> system network, an access and mobility management function (AMF) serves as the MM functional entity, and a session management function (SMF) serves as the SM functional entity and a control plane of the GW. A user plane function (UPF) plays the role corresponding to the user plane of the GW. A policy and charging rules function (PCRF) corresponds to a policy control function (PCF). Therefore, it should be understood that the embodiments mentioned in the disclosure can be applied to a <NUM> system network, as well as the EPS network.

For example, in the case where the embodiments are applied to 5GS, the evolved universal terrestrial radio access network (E-UTRAN) <NUM> may be interpreted as a <NUM>-radio access network (RAN), the mobility management operation of the MME <NUM> may be interpreted as an AMF, the session management operation of the MME <NUM> and the control plane operation of the GW <NUM> may be interpreted as an SMF, the user plane operation of the GW <NUM> may be interpreted as a UPF, and the PCRF may be interpreted as a PCF in the respective embodiments. The mobility management operation of the MME <NUM> refers to an operation of determining whether or not it corresponds to the RLOS and selecting the GW <NUM> for the RLOS (the SMF in <NUM> system network) without an authentication process. The session management operation of the MME <NUM> may refer to an operation of processing sessions, such as create-session request, session modification, EPS bearer activation, modification thereof, or the like, and the control plane operation of the GW <NUM> may refer to an operation of creating expiration conditions, traffic flow template (TFT), or the like in the case of the RLOS and providing corresponding information to the user plane of the GW <NUM>.

<FIG> is a view illustrating a method of informing an unauthenticated terminal of connection termination conditions through a protocol configuration option (PCO) and terminating a connection of the terminal if the connection termination conditions are satisfied according to an embodiment of the disclosure.

<FIG> shows a process of informing the terminal <NUM> connected without authentication of connection termination conditions and terminating connection of the terminal <NUM> if the connection termination conditions are satisfied according to an embodiment.

Referring to <FIG>, the E-UTRAN (e.g., eNB, gNB, base station, or the like) <NUM> broadcasts information indicating the RLOS support using a system information block (SIB) message if the RLOS is available, at operation <NUM>. Upon receiving the SIB message, the terminal <NUM> selects an appropriate public land mobile network (PLMN) from among the detected available PLMNs supporting the RLOS if the RLOS is required, at operation <NUM>.

The terminal <NUM> transmits an attach-request message to the MME <NUM> using the selected PLMN, and requests a network connection while informing that the attach-type is the RLOS, at operation <NUM>. For example, "attach type = 'RLOS‴ may be used. In this case, the attach-request message may include the identity of the terminal <NUM> (e.g., international mobile station equipment identity (IMEI)). The terminal <NUM> may transmit a PDN connectivity request included in the attach-request message as a piggyback.

The MME <NUM> may use the IMEI in order to determine whether or not the terminal <NUM> transmitting the attach-request message is eligible for the RLOS. A method in which the MME <NUM> determines whether or not the terminal <NUM> is eligible for the RLOS using the IMEI will be described as a separate embodiment.

If the attach-request message relates to the RLOS, the MME <NUM>, which has received the attach-request message, selects the GW <NUM> for the RLOS without an authentication/authorization process for security, at operation <NUM>. The MME <NUM> transmits a create-session request to the GW <NUM> selected for the RLOS, thereby making a request for establishing a PDN connection, at operation <NUM>. In this case, the create-session request message includes an RLOS access point name (APN) or an indication stating that it is for the RLOS. Upon receiving the create-session request, the GW <NUM> may allocate an IP address, and may produce default EPS bearer context. The default EPS bearer may be configured to produce a TFT such that the terminal <NUM> can use the traffic only for the RLOS and thus can communicate with a specific server, at operation <NUM>. In addition, expiration conditions for the RLOS to be provided to the terminal <NUM> may be acquired on the basis of a value predetermined in the GW <NUM> or a value received from a PCRF <NUM>. The expiration conditions for the RLOS may include all or some of, for example, an allowed service time indicating how long the RLOS is available, an allowed service volume indicating how much data can be transmitted, or an allowed inactivity period indicating how long the RLOS can last since the last data transmission/reception to/from the terminal <NUM>.

If the GW <NUM> transmits the expiration conditions for the RLOS to the MME <NUM>, at operation <NUM>, the MME <NUM> performs the remaining PDN connection establishment process and attachment process so as to include the received expiration conditions for the RLOS in the PCO of an activate-default EPS bearer context request message, at operation <NUM>, and so as to transmit the same together with an attach-accept message, thereby establishing a PDN connection and completing the attachment process via operations <NUM> and <NUM>. Upon receiving the expiration conditions for the RLOS included in the PCO, the terminal <NUM> notifies the user of the expiration conditions for the RLOS through a display of the terminal <NUM>, at operation <NUM>.

Meanwhile, if the user makes a request for updating the expiration conditions for the RLOS while the terminal <NUM> accesses the RLOS via the established PDN connection and is served (for example, if the user wishes to extend the service period or wishes to modify an available volume through a captive portal server), the terminal <NUM> makes a request to the AS <NUM> for the RLOS for updating the conditions, at operation <NUM>. Then, the AS <NUM> for the RLOS, which received the request, transmits modified expiration conditions for the RLOS to the PCRF <NUM>, and the PCRF <NUM> updates the modified expiration conditions for the RLOS with respect to the GW <NUM>, at operation <NUM>.

Alternatively, when the terminal <NUM> connects, for the RLOS, to the AS <NUM> for the RLOS through the established PDN connection and the user selects one of various RLOSs provided by the provider, the expiration conditions for the RLOS will vary with the selected RLOS. That is, an allowed service time indicating how long the RLOS is available, an allowed service volume indicating how much data can be transmitted, or an allowed inactivity period indicating how long the RLOS can last since the last data transmission/reception to/from the terminal <NUM> may be set to be different in values from each other. To this end, the AS <NUM> transmits, to the PCRF <NUM>, the expiration conditions for the RLOS determined according to the selection, and the PCRF <NUM> updates the modified expiration conditions for the RLOS with respect to the GW <NUM>, at operation <NUM>.

Upon receiving the modified expiration conditions for the RLOS, the GW <NUM> requests modification of the session in order to transmit the received conditions to the terminal <NUM> through the PCO and includes the modified expiration conditions for the RLOS in the PCO of an SM network attached storage (NAS) message (e.g., modify-EPS bearer context request message) to thus transmit the same via the MME <NUM>, at operations <NUM> and <NUM>. Upon receiving the PCO, the terminal <NUM> notifies the user of the expiration conditions for the RLOS through a display of the terminal <NUM>, at operation <NUM>.

The GW <NUM> monitors the user usage status according to the expiration conditions for the RLOS. For example, if the allowed service time is set, the GW <NUM> determines, through a timer, whether or not the allowed service time has expired; if the allowed service volume is set, the GW <NUM> determines whether or not the usage amount of the terminal <NUM> exceeds the allowed service volume; and if the allowed inactivity period is set, the GW <NUM> determines whether or not the elapsed time since the last data transmission/reception exceeds the allowed inactivity period, thereby continuously checking whether or not the expiration conditions for the RLOS are satisfied.

If the expiration conditions for the RLOS are not satisfied, or if the GW <NUM> recognizes that a voice over LTE (VoLTE) call of the terminal <NUM> using the VoLTE service through the RLOS has been terminated, the GW <NUM> performs a process of terminating the RLOS for the terminal <NUM>, at operation <NUM>. The GW <NUM> may recognize that the VoLTE call has been terminated if data is no longer transmitted to the corresponding QCI = <NUM> bearer for a specific period of time or if a message instructing to delete the QCI = <NUM> bearer due to the call termination is received from the PCRF <NUM>.

In order to terminate the RLOS for the terminal <NUM>, the GW <NUM> transmits, to the MME <NUM>, a delete-default EPS bearer request in relation to the PDN connection for the RLOS, at operation <NUM>, and if it is identified that the terminal <NUM> has one PDN connection, the MME <NUM> transmits a detach-request message, at operation <NUM>, to the terminal <NUM>, thereby terminating the connection of the terminal <NUM>.

<FIG> is a view illustrating a method of informing an unauthenticated terminal of connection termination conditions through a PCO and terminating a connection of the terminal if the connection termination conditions are satisfied according to an embodiment of the disclosure.

<FIG> shows a process of informing the terminal <NUM> connected without authentication of connection termination conditions and terminating connection of the terminal <NUM> if the conditions are satisfied according to an embodiment.

Referring to <FIG>, the E-UTRAN <NUM> broadcasts information indicating the RLOS support using an SIB message if the RLOS is available, at operation <NUM>. Upon receiving the SIB message, the terminal <NUM> selects an appropriate PLMN from among the detected available PLMNs supporting the RLOS if the RLOS is required, at operation <NUM>.

The terminal <NUM> transmits an attach-request message to the MME <NUM> using the selected PLMN, and requests the network connection while informing that the attach-type is the RLOS, at operation <NUM>. For example, "attach type = 'RLOS'" may be used. In this case, the attach-request message may include the identity of the terminal <NUM> (e.g., IMEI). The terminal <NUM> may transmit a PDN connectivity request included in the attach-request message as a piggyback.

The MME <NUM> may use the IMEI in order to determine whether or not the terminal <NUM> sending the attach-request message is eligible for the RLOS. A method in which the MME <NUM> determines whether or not the terminal <NUM> is eligible for the RLOS using the IMEI will be described as a separate embodiment.

If the attach-request message relates to the RLOS, the MME <NUM>, which has received the attach-request message, selects the GW <NUM> for the RLOS without an authentication/authorization process for security, at operation <NUM>. The MME <NUM> transmits a create-session request to the GW <NUM> selected for the RLOS, thereby making a request for establishing a PDN connection, at operation <NUM>. In this case, the create-session request message includes an RLOS APN or an indication stating that it is for the RLOS. Upon receiving the create-session request, the GW <NUM> may allocate an IP address, and may produce default EPS bearer context. The default EPS bearer may be configured to produce a TFT so that the terminal <NUM> can use the traffic only for the RLOS and thus can communicate with a specific server, at operation <NUM>. In addition, expiration conditions for the RLOS to be provided to the terminal <NUM> may be acquired on the basis of a value predetermined in the GW <NUM> or a value received from the PCRF <NUM>. The expiration conditions for the RLOS may include all or some of, for example, an allowed service time indicating how long the RLOS is available, an allowed service volume indicating how much data can be transmitted, or an allowed inactivity period indicating how long the RLOS can last since the last data transmission/ reception to/from the terminal <NUM>.

If the GW <NUM> transmits the expiration conditions for the RLOS to the MME <NUM>, at operation <NUM>, the MME <NUM> performs the remaining PDN connection establishment process and attachment process so as to include the received expiration conditions for the RLOS in the PCO of an activate-default EPS bearer context request message, at operation <NUM>, and so as to transmit the same together with an attach-accept message, thereby establishing a PDN connection and completing the attachment process via operations <NUM> and <NUM>. Upon receiving the expiration conditions for the RLOS contained in the PCO, the terminal <NUM> notifies the user of the expiration conditions for the RLOS through a display of the terminal <NUM>, at operation <NUM>.

Meanwhile, if the user makes a request for updating the expiration conditions for the RLOS while the terminal <NUM> accesses the RLOS via the established PDN connection and is served, the terminal <NUM> produces an expiration condition proposal for the modified RLOS to be requested, and includes the expiration condition proposal for the modified RLOS in the PCO of an SM NAS message (e.g., EPS bearer resource modification request message), thereby transmitting the same to the MME <NUM>, at operation <NUM>. Upon receiving the NAS message, the MME <NUM> transfers the corresponding PCO to the GW <NUM>, at operation <NUM>, and the GW <NUM> directly identifies whether or not the expiration condition proposal for the RLOS requested by the terminal <NUM> is acceptable or enquires the PCRF <NUM> of the expiration condition proposal, thereby determining whether or not to accept the expiration condition proposal, at operation <NUM>. In addition, the GW <NUM> includes the determined expiration conditions for the RLOS in the PCO of a modify-EPS bearer context request message to thus transmit the same to the terminal <NUM> via the MME <NUM>, at operation <NUM>.

Upon receiving the PCO, the terminal <NUM> notifies the user of the expiration conditions for the RLOS through a display of the terminal <NUM>, at operation <NUM>.

If the expiration conditions for the RLOS are not satisfied, or if the GW <NUM> recognizes that the VoLTE call of the terminal <NUM> using the VoLTE service through the RLOS has been terminated, the GW <NUM> performs a process of terminating the RLOS for the terminal <NUM>, at operation <NUM>. The GW <NUM> may recognize that the VoLTE call has been terminated if data is no longer transmitted to the corresponding QCI = <NUM> bearer for a specific period of time, or if a message instructing to delete the QCI = <NUM> bearer due to the call termination is received from the PCRF <NUM>.

<FIG> is a view illustrating a method of terminating a connection of an unauthenticated terminal if the terminal switches to an idle state according to an embodiment of the disclosure.

<FIG> shows a process of preventing unnecessary resource waste of a network by a method for releasing the terminal <NUM> connected without authentication if the terminal <NUM> switches to an idle state.

Referring to <FIG>, when the terminal <NUM> is provided with the RLOS by performing the attachment process for the RLOS and establishing a PDN connection for the RLOS, as described in the above embodiments, at operations <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>), the E-UTRAN <NUM> operates an inactivity timer for the terminal <NUM>, and if no transmission/reception is made with respect to the terminal <NUM> for a predetermined period of time, at operation <NUM>, the E-UTRAN <NUM> terminates the radio resource control (RRC) connection to the terminal <NUM>, at operation <NUM>, and transmits an S1 UE context release request message to the MME <NUM>, at operation <NUM>, thereby allowing the terminal <NUM> to switch to an idle mode.

In this case, the terminal <NUM> connected for the RLOS through the RRC connection performs an implicit detachment without transmitting a detach-request message to the MME <NUM>, at operation <NUM>, and the MME <NUM>, which has received the S1 UE context release request, also performs an implicit detachment without transmitting a separate detach-request message to the terminal <NUM> connected for the RLOS, at operation <NUM>.

<FIG> is a view illustrating a method of informing an unauthenticated terminal of connection termination conditions using an attachment message and terminating a connection of the terminal if the connection termination conditions are satisfied according to an embodiment of the disclosure.

<FIG> shows a process of informing an unauthenticated terminal (e.g., the terminal <NUM>) of connection termination conditions using an attachment message and terminating a connection of the terminal if the connection termination conditions are satisfied according to an embodiment.

If the attach-request message relates to the RLOS, the MME <NUM>, which has received the attach-request message, selects the GW <NUM> for the RLOS without an authentication/authorization process for security, at operation <NUM>. The MME <NUM> transmits a create-session request to the GW <NUM> selected for the RLOS, thereby making a request for establishing a PDN connection, at operation <NUM>. In this case, the create-session request message includes an RLOS APN or an indication stating that it is for the RLOS. Upon receiving the create-session request, the GW <NUM> may allocate an IP address, and may produce default EPS bearer context. The default EPS bearer may be configured to produce a TFT so that the terminal <NUM> can use the traffic only for the RLOS and thus can communicate with a specific server, at operation <NUM>.

The GW <NUM> transmits TFT information to the MME <NUM>, as described above, at operation <NUM>, and the MME <NUM> may include expiration conditions for the RLOS in an attach-accept message, and may transmit the same to the terminal <NUM>, at operation <NUM>. The expiration conditions for the RLOS may be acquired on the basis of a value predetermined in the MME <NUM>, and may include all or some of, for example, an allowed service time indicating how long the RLOS is available or an allowed inactivity period indicating how long the RLOS connection can last since the terminal <NUM> came to the idle mode.

The terminal <NUM> notifies the user of the expiration conditions for the RLOS, which is received by means of the attach-accept message, through a display of the terminal <NUM>, at operation <NUM>.

Then, the remaining PDN connection establishment process and attachment process are completed, at operation <NUM>.

The MME <NUM> monitors the user usage status according to the expiration conditions for the RLOS. For example, if the allowed service time is set, the MME <NUM> determines, through a timer, whether or not the allowed service time has expired, and if the allowed inactivity period is set, the MME <NUM> determines whether or not the allowed inactivity period has expired since the terminal <NUM> entered the idle state, thereby continuously checking whether or not the expiration conditions for the RLOS are satisfied.

If the expiration conditions for the RLOS are not satisfied, or if the MME <NUM> recognizes that the VoLTE call of the terminal <NUM> using the VoLTE service through the RLOS has been terminated, the MME <NUM> performs a process of terminating the RLOS for the terminal <NUM>, at operation <NUM>. The MME <NUM> may recognize that the VoLTE call has been terminated if a message instructing to delete the QCI = <NUM> bearer due to the call termination is received from the GW <NUM>.

In order to terminate the RLOS, if it is identified that the terminal <NUM> has one PDN connection, the MME <NUM> transmits a detach-request message, at operation <NUM>, to the terminal <NUM>, thereby terminating the connection of the terminal <NUM>.

<FIG> is a view illustrating a method of restricting connection of an unauthenticated terminal if the terminal excessively accesses the network according to an embodiment of the disclosure.

<FIG> shows a process of restricting a connection of an unauthenticated terminal (e.g., the terminal <NUM>) if the terminal <NUM> excessively accesses the network according to an embodiment.

The MME <NUM> may use the IMEI in order to determine whether or not the terminal <NUM> sending the attach-request message is eligible for the RLOS, at operation <NUM>. For example, when the terminal <NUM> corresponding to the received IMEI accesses the network for the RLOS, the MME <NUM> may increase a counter by one, thereby recording the number of connections of the corresponding terminal <NUM> for the RLOS within a predetermined period of time. In this case, if the number of connections of the terminal <NUM> exceeds a number predetermined by the provider within a predetermined period of time, the MME <NUM> rejects the attachment attempt.

Alternatively, in the case where the terminal <NUM> is connected for the RLOS and is released from the network, the MME <NUM> records information on how long the terminal <NUM> corresponding to the IMEI has been provided with the service, and if the terminal <NUM> of the same IMEI attempts to access the network, the MME <NUM> rejects the connection if the usage time of the terminal <NUM> exceeds an RLOS service time predetermined by the provider, within which one terminal can be provided with the RLOS.

In the case where the MME <NUM> rejects the connection attachment attempt of the terminal <NUM>, the MME <NUM> may transmit an attach-reject message to the terminal <NUM>, and the attach-reject message may include "error cause = abused usage" stating that connection has been rejected because the RLOS service connections limit was exceeded, at operation <NUM>. In this case, the MME <NUM> may include an RLOS back off timer value, as information on the period of time for which the RLOS connection is blocked, in the attach-reject message, and may transmit the same to the terminal <NUM>.

If the RLOS back off timer value is not provided to the terminal <NUM>, the RLOS back off timer value may follow a default value.

The terminal <NUM> does not make an attachment attempt for the RLOS to the same PLMN before the RLOS back off timer expires, at operation <NUM>.

<FIG> is a view illustrating a method of restricting a connection of an unauthenticated terminal if the terminal excessively accesses the network according to an embodiment of the disclosure.

Referring to <FIG>, the terminal <NUM> performs an attachment process for the RLOS and establishes a PDN connection for the RLOS as described in the above embodiments, at operations <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>).

The terminal <NUM> connects to the AS <NUM> (e.g., captive portal server) for the RLOS through the PDN connection, and enters user information for using the application service, at operation <NUM>. For example, the terminal <NUM> enters an email address, a username, user's credit card information, or the like. Based on the information, the AS <NUM> determines whether or not the user is entitled to use the RLOS, at operation <NUM>.

For example, when the corresponding user accesses the network for the RLOS, the AS <NUM> may increase a counter by one, thereby recording the number of connections of the corresponding user for the RLOS within a predetermined period of time. In this case, if the number of connections of the terminal <NUM> exceeds a number predetermined by the provider within a predetermined period of time, the AS <NUM> terminates the RLOS and informs the user of the same, thereby performing a process of terminating the PDN connection for the RLOS.

Alternatively, in the case where the terminal <NUM> is connected for the RLOS and is released, the AS <NUM> records information on how long the user has been provided with the RLOS, and when the same user attempts to make a connection for the RLOS, if the usage time of the user exceeds an RLOS service time predetermined by the provider, within which one terminal can be provided with the RLOS, the AS <NUM> stops the RLOS and informs the user of the same, thereby performing a process of terminating the PDN connection for the RLOS.

In order to terminate the PDN connection for the RLOS, the AS <NUM> makes a request to the PCRF <NUM> for terminating the corresponding RLOS flow, and the PCRF <NUM> makes a request to the GW <NUM> for terminating the PDN connection, at operation <NUM>. Accordingly, the GW <NUM> transmits a delete-default EPS bearer request message to the MME <NUM>, at operation <NUM>, and in order to terminate the RLOS, the MME <NUM> identifies that the terminal <NUM> has one PDN connection and transmits a detach-request message, at operation <NUM>, to the terminal <NUM>, thereby terminating the connection of the terminal <NUM>.

<FIG> is a view illustrating a configuration of a terminal according to an embodiment of the disclosure.

Referring to <FIG>, the terminal according to an embodiment may include a transceiver <NUM> and a controller <NUM> for controlling the overall operation of the terminal. In addition, the transceiver <NUM> may include a transmitter <NUM> and a receiver <NUM>.

The transceiver <NUM> may transmit and receive signals to and from other network entities.

The controller <NUM> may control the terminal so as to perform one of the operations described in the above embodiments. It should be noted that the controller <NUM> and the transceiver <NUM> are not necessarily implemented as separate modules, and may be implemented as a single component such as a single chip. The controller <NUM> and the transceiver <NUM> may be electrically connected to each other. In addition, for example, the controller <NUM> may be a circuit, an application-specific circuit, or at least one processor. Further, the operations of the terminal may be realized by providing a memory device storing the corresponding program code to a certain component in the terminal.

<FIG> is a view illustrating a configuration of a base station according to an embodiment of the disclosure.

Referring to <FIG>, the base station according to an embodiment may include a transceiver <NUM> and a controller <NUM> for controlling the overall operation of the base station. In addition, the transceiver <NUM> may include a transmitter <NUM> and a receiver <NUM>.

The controller <NUM> may control the base station so as to perform one of the operations described in the above embodiments. It should be noted that the controller <NUM> and the transceiver <NUM> are not necessarily implemented as separate modules, and may be implemented as a single component such as a single chip. The controller <NUM> and the transceiver <NUM> may be electrically connected to each other. In addition, for example, the controller <NUM> may be a circuit, an application-specific circuit, or at least one processor. Further, the operations of the base station may be realized by providing a memory device storing the corresponding program code to a certain component in the base station.

In addition, although it is not shown in the drawings, the network entity, such as the MME, the GW, the PCRF, the AS, or the like, according to an embodiment may include a transceiver and a controller for controlling the overall operation of the network entity. In addition, the transceiver may include a transmitter and a receiver. The transceiver may transmit and receive signals to and from other network entities. The controller may control the network entity so as to perform one of the operations described in the above embodiments. It should be noted that the controller and the transceiver are not necessarily implemented as separate modules, and may be implemented as a single component such as a single chip. The controller and the transceiver may be electrically connected to each other. In addition, for example, the controller may be a circuit, an application-specific circuit, or at least one processor. Further, the operations of the network entity may be realized by providing a memory device storing the corresponding program code to a certain component in the network entity.

It should be noted that the view illustrating the configuration of the terminal, the view illustrating an example of the control/data signal transmission method, the view illustrating an example of the operational procedure of the terminal, or the view illustrating the configuration of the terminal device, which are shown in <FIG>, are not intended to limit the scope of the disclosure. That is, it should not be interpreted that all the elements, entities, or operations illustrated in <FIG> are essential elements for the implementation of the disclosure, and the disclosure can be implemented by only some elements without departing from the subject matter of the disclosure.

The above described operations of the base station or UE may be implemented by providing a memory device storing corresponding program codes in any constituent unit of the base station or UE apparatus. That is, the controller of the base station or UE may perform the above described operations by reading and executing the program code stored in the memory device by means of a processor or a CPU.

Claim 1:
A method performed by a gateway, GW (<NUM>), in a wireless communication system, the method comprising:
receiving, from a mobility management entity, MME (<NUM>), a create session request message including information related to restricted local operator services, RLOS;
determining whether an allowed service time for the RLOS is expired; and
transmitting, to the MME, a request message for deleting a default evolved packet system, EPS, bearer of a packet data network, PDN, connection for the RLOS, in case that the allowed service time for the RLOS is expired.