KR20090066079A - Apparatus and method for providing service of multiple sps in wireless communication network - Google Patents

Abstract

An apparatus and a method for providing a service of a plurality of service providers based on a service guide in a wireless communications network are provided to supply a network structure for providing a service on a single NAP by a plurality of VNO(Virtual Network Operators). An MNO(Mobile Network Operator) server(11) is positioned in an NAP(Network Access Provider) domain. The MNO server assigns an MVNO(Mobile Virtual Network Operator) zone in consideration of the resources of the information from the different service provider and corresponding NAP(Network Access Provider). The resources are especially divided by the MVNO zone. MVNO servers are positioned in CSN(Core Service Network). The service is provided according to the service guide through the corresponding MVNO zone by using the MVNO zone information.

Description

Apparatus and method for providing services of a plurality of service providers in a wireless communication network {APPARATUS AND METHOD FOR PROVIDING SERVICE OF MULTIPLE SPs IN WIRELESS COMMUNICATION NETWORK}

The present invention relates to an apparatus and a method for providing a service of a plurality of service providers in a wireless network, and more particularly, to a network structure and a control method for providing a service by a plurality of service providers for a single wireless network. .

In general, communication systems have been developed mainly for voice services, and are gradually developing into communication systems capable of not only voice but also data services and various multimedia services. However, the voice-oriented communication system has not satisfied the rapidly increasing user's service needs due to the relatively small transmission bandwidth and high usage fee. In addition, due to the development of the communication industry and increasing user demand for Internet services, there is an increasing need for a communication system capable of efficiently providing Internet services. As a result, an OFDM-based broadband wireless access system has been introduced to efficiently provide Internet services with broadband enough to meet the demand of users.

The main services of the broadband wireless access system include the Internet, Voice over IP (VoIP), and non-real time streaming services. In addition, recently, a multicast broadcast service (MBS), which is a real-time broadcasting service, is emerging as a new service.

Meanwhile, the global flow for wireless networks assumes a plurality of virtual network operators (VNOs) or a plurality of service providers (SPs) for a single physical network. In addition, a single SP may assume multiple VNOs or multiple NAPs (network access providers). Unlike a wired network, a wireless network basically has limited radio resources, a transmission rate varies according to a distance between a transmitting station and a receiving station, and the wireless capacity itself is variable and unpredictable. Accordingly, there is a demand for a flexible and optimized network structure that can meet the global trend while considering the characteristics of such a wireless network.

Currently, mobile WiMAX or IEEE 802.16 based broadband wireless access systems assume that NAP and NSP are basically the same. Here, a network access provider (NAP) represents an operator (eg, a mobile communication provider) that owns and operates an access service network (ASN), which is a physical network, and the network service provider (NSP) is a core service network (CSN). It is located in a network and represents a service provider that provides a service through NAP (or NO).

As described above, the future network should be able to service multiple VNOs for a single NAP, or a single VNO can provide services over multiple NAPs. The following are the items to be considered when designing such a network structure.

(1) The ASN should be able to determine which VNO the UE belongs to. For example, one base station resource may be divided and allocated to a plurality of VNOs. In this case, the base station should be able to determine which VNO the UE belongs to.

(2) The terminal should be able to determine whether there are base stations belonging to the same VNO in the vicinity for handover (HO: HandOver).

(3) Call flows associated with authenticators, paging controllers (PCs), and data path functions (DPFs) depend on how the ASNs are divided and how the ASNs manage resources. This is not the case at present.

(4) One VNO service zone should not only be composed of several base stations but also be managed by several base station controllers.

(5) The terminal should be able to receive the incoming service notification (notification) for the VNO network subscribed in the idle (dormant) state.

(6) The base station should be able to inform the terminal of the service zone identifier and the service channel MAC layer identifier.

(7) A network entity communicating with the terminal through the application layer (NE) should be located in the core service network (CSN).

(8) NAPs should be able to manage service requirements of different NSPs in an integrated manner to handle the requirements of all NSPs fairly and efficiently, and to control them from wasting NAP resources.

That is, there is a need for a flexible and optimized network structure that can meet all of the above requirements.

Accordingly, an object of the present invention is to provide a network structure and a control method for providing a service by a plurality of VNOs for a single NAP.

Another object of the present invention is to provide a network structure and a control method for providing a service through a plurality of NAP a single VNO.

Another object of the present invention is to provide an apparatus and method for determining a VNO to which a UE belongs in an ASN.

Another object of the present invention is to provide an apparatus and method for determining a base station belonging to the same VNO for handover in the terminal.

Still another object of the present invention is to provide an apparatus and a method for receiving an incoming service notification for a VNO network to which a terminal is subscribed in an idle or dormant state.

Another object of the present invention is to provide an apparatus and method for informing a terminal of a service zone identifier and a service channel MAC layer identifier.

It is still another object of the present invention to provide a network structure and a control method for collectively managing service requirements of different NSPs in NAP.

According to an aspect of the present invention for achieving the above object, in a network for providing services of different service providers through a wireless network, located in the network access provider (NAP) area, different service providers (Service Provider) At least one Mobile Network Operator (MNO) server that allocates a Mobile Virtual Network Operator (MVNO) zone in consideration of information from the NAP and the resources of the corresponding Network Access Provider (NAP), and allocates resources to each MVNO zone, and a CSN ( Core Service Network), and comprises a service guide using the information on the MVNO zone from the MNO server, and includes at least one MVNO server to provide a service through the MVNO zone according to the service guide, At least one MVNO provides services for a single NAP, and a single MVNO provides services over at least one NAP. All.

According to another aspect of the present invention, in a communication method of a network for providing services of different service providers through a wireless network, at least one MNO server located in the NAP area is different from a different service provider. The process of allocating an MVNO zone in consideration of the information of the NAP and the resources of the corresponding NAP, and allocating resources for each MVNO zone, and using at least one MVNO server located in the CSN using information on the MVNO zone from the MNO server. Forming a service guide, providing a service through a corresponding MVNO zone according to the service guide, at least one MVNO provides a service for a single NAP, and a single MVNO provides service through at least one NAP; It is characterized by providing.

As described above, the present invention proposes a flexible and optimized network structure capable of providing various services through a wireless network. In the network structure according to the present invention, since a plurality of VNOs provide services for a single NAP, and a single VNO provides services through a plurality of NAPs, a service of various operators can be flexibly provided through a wireless network. There is an advantage.

Hereinafter, the operating principle of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, detailed descriptions of well-known functions or configurations will be omitted if it is determined that the detailed description of the present invention may unnecessarily obscure the subject matter of the present invention. Terms to be described later are terms defined in consideration of functions in the present invention, and may be changed according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout the specification.

Hereinafter, the present invention will propose a network architecture for providing a service through a plurality of VNOs for a single NAP or providing a service through a plurality of NAPs.

First, terms used in the present invention are defined as follows.

Service Provider (SP): It is located in the Core Service Network (CSN) and represents an operator (eg, Google) that provides end-to-end services to users.

NAP (Network Access Provider): Represents an operator (eg, a mobile communication provider) that owns and operates an access service network (ASN), which is a physical network.

ASN: Represents a network composed of existing network entities (base station controller, base station, EMS, etc.).

NO: A network operator used in the same terms as NAP.

VNO (Virtual Network Operator): Located in CSN, it represents a service provider who provides a service by configuring virtual ASN through NAP.

NSP (Network Service Provider): Located in the CSN and in the same term as a VNO, a relationship of SP: NSP = n: m and NSP: NAP = n: m is possible.

And MNO represents mobile NO, and MVNO represents mobile VNO.

In the following description, the name of a network entity (NE) is defined according to a corresponding function, and may vary according to the intention of the standardization group and the operator. For example, the base station may be called an access point (AP), a radio access station (RAS), a node-B, or a base station (BS). In addition, the base station controller may be referred to as a radio network controller (RNC), a base station controller (BSC), an access control router (ACR), or an access service network gateway (ASN-GW). Here, the ASN-GW may perform a router function as well as a base station controller function.

In addition, the following wireless network describes an OFDM / OFDMA-based broadband wireless access system by way of example, but the network structure according to the present invention can be easily applied to other wireless systems.

1 illustrates a network structure according to an embodiment of the present invention.

As shown, the network structure can be largely divided into a NAP region and an NSP region. Here, the base station (BS) 13, the base station controller (ASN_GW) 12, and the MNO server 11 belong to the NAP area, and the MVNO server 10 belongs to the NSP area (CSN). The base station controller 12 and the base station 13 may be classified into an access service network (ASN). In addition, the MVNO server 10 and the MNO server 11 is a function entity, as shown, may exist as a separate server or may be located in another network entity NE of the corresponding area NSP or NAP. have. Also, when the NSP and the NAP are the same, that is, when there is no MVNO, the MVNO server 10 and the MNO server 11 functions may be integrated and located in the same network entity.

Referring to FIG. 1, first, the MVNO server 10 is located in a CSN and is a functional entity that each service provider (SP) may have. It has an interface with external broadcasting content server (or content provider) and AAA (Authentication, Authorization, Accounting) server, and NAP service zone provisioning information and operator policy (eg QoS, authentication and billing policy) information. Perform the function of sending to. In addition, the MVNO server 10 performs a function of transmitting a service guide (MVNO identifier, NSP & NAP service zone information, service timetable) to the terminal.

The MNO server 11 is located in the NAP area and performs a function for comprehensively determining the requirements of different SPs (or MVNOs) and the situation of NAPs (base station controllers, base stations, WSMs, etc.) to provide optimized services. do. For example, the MVO server 11 configures an MVNO zone, generates a service guide including information on the MVNO zone, and delivers the service guide to the MVNO server 10. In addition, the MVO server 11 manages all resources (eg, NAP service zone, NAP resources allowed for each MVNO) related to the service, and finally determines resource allocation information (eg, number of subscribers allowed), Flow number and BW total, allowable flow number per QoS type, and BW total) are transmitted to the MVNO server 10 and the ASN. Here, the NAP service zone may be composed of various combinations of a base station, a base station controller, and an EMS. For example, the minimum unit may be a base station or a base station controller or a base station and a base station controller managed by the EMS. On the other hand, the resource allocation information can be used for rock lock control and resource scheduling.

The base station controller 12 manages connection and mobility of subscribers, and assigns a unique service flow (SF) for each UL / DL. It also has an interface with a CSN such as an AAA server and a service server.

The base station 13 is a network entity located between the base station controller 12 and a mobile station (MS). The base station 13 interfaces with the terminal through a wireless connection according to the PHY & MAC standard, and provides the terminal with connection and bearer traffic between radio sections.

On the other hand, the terminal (not shown) is an end-to-end service consumption subject, and is wirelessly connected to the base station 13. In addition, the terminal may receive a service guide from the MVNO server 10 through the application layer. Meanwhile, the terminal decodes a broadcast message transmitted from the base station (eg, DL-MAP, DCD, NBR-ADV message, etc.) and compares it with its subscription information to determine whether it is a region where the service can be received. Determine. In addition, neighbor base stations capable of receiving a service are determined. For example, the DCD message may inform the MVNO list allowed by the subcell, and the NBR-ADV message may inform the HO list of the subcells (BSID list) available for each MVNO. As another example, the terminal may receive the MVNO list through a separate MAC interworking procedure.

Although not shown, a policy server, an AAA (Authentication, Authorization, Accounting) server, a network management server, a home agent (HA), a content provider, and the like may be configured.

The AAA server may manage authentication and billing information, and may include a subscription profile repository (SPR) function for managing profile information for each subscriber. In addition, the AAA server may manage the security key and the lifetime derived from the subscriber-specific broadcast service authorization information and initial authentication.

The network management server (WSM or EMS or OMC) is responsible for the maintenance and repair of the NE belonging to the ASN, and performs the function of delivering information necessary for the initialization and operation of each NE.

A policy server is a network entity that enforces an operator policy, and performs a function of delivering a QoS requirement (QoS profile) of a terminal (application layer) or a service flow to an ASN. In order to trigger the MAC layer call processing (creation, modification, and deletion) interworking procedure, PDF (Policy Decision Function) is required.In the case of static QoS, AAA, EMS or MVNO server plays the role of PDF. In the case of dynamic QoS (QoS), the existing policy charging rule function (PCRF) can be used, and the AAA or MVNO server can play a PDF role. In addition, the terminal may be equipped with a major PDF function.

In the network structure of FIG. 1 described above, the network entities located in the CSN, the AAA server, the policy server, the HA, and the MVNO server, may each have their own servers. In addition, in the network structure of FIG. 1, although the physical region of each MVNO is separated, multiple MVNO zones may overlap for the same base station.

Looking at the basic operation according to the network structure of Figure 1 described above are as follows.

Physically existing NEs of a NAP may be shared by a plurality of MVNOs, and may operate in four architectures as follows.

(1) A separate virtual authenticator, virtual paging controller, and virtual data path function (DPF) exist for each MVNO, so that call processing, authentication, billing, handover (HO), and bearer binding are present. Bearer binding & QoS mapping is handled only within one MVNO.

(2) Even if a separate virtual authenticator, a virtual paging controller, and a virtual DPF exist for each MVNO, the UE may support handover in a plurality of MVNOs. In this case, the QoS policy, authentication, and billing policy will be different, so it is necessary to be able to deliver and translate information required for the movement between MVNOs. Specifically, the following three cases can be assumed.

First, without IP relocation, a network entity (such as a policy server and an AAA server) in charge of QoS policy, authentication, and billing policy can transfer this information to the base station controller ASN_GW without interworking procedures.

Second, the network entity in charge of the authentication and billing policy can transfer this information to the base station controller through interworking procedures without IP reassignment and QoS policy changes.

Third, when it is necessary to update IP and QoS, a full network entry is performed instead of a handover procedure.

(3) The authenticator, paging controller, and DPF manage multiple MVNOs, but do not allow movement between MVNOs. In this case, the MVNO to which the terminal belongs must be managed.

(4) The authenticator, paging controller, and DPF manage multiple MVNOs and allow movement between MVNOs.

When defining the MVNO as described above, look at how to identify the MVNO as follows.

(1) How to use CID

-How to use CID range without distinguishing by MVNO

In this case, software blocks that need to be distinguished must use separate identifiers. For example, a QoS parameter such as a network access identifier (NAI) or a MAC address may be used as the terminal identifier.

-How to distinguish and use the CID range by MVNO

For example, the upper 4 bits of the CID 16 bits may be used as the MVNO identifier, and the lower 12 bits may be used as the service flow (SF) identifier. At this time, if the NAP server integrated management of the upper 4 bits, it is possible to uniformly manage the base station and the base station controllers belonging to the NAP. In this case, the NAP server should inform the base station controller and the base station of this information.

(2) How to use BSID (NAP server allocates MVNO identifier and informs ASN)

In this case, the MVNO identifier may be distinguished using the upper 24 bits of the BSID or the lower 24 bits.

Based on the contents of FIG. 1 described above, the functions of the network entity according to the present invention are summarized in Table 1 below.

NE Functions Location AAA server Authentication, Authorization, Accounting, Subscription profile repository CSN MVNO server (NSP) Subscription management Service guide provisioning NSP zone ID & IP layer ID allocation & management Service guide distribution to MS User authentication & authorization Key management & distribution User interaction Notification & alert Service Provider (CSN) MNO Server (NAP) C-plane -NSP Zone ID & NAP Zone ID mapping allocation -NSP IP ID & NAP MAC ID mapping allocation -NAP zone ID & NAP ASN_GW ID & BSID mapping -ASN resource allocation (# of users, # of SFs per class or per subcell or per BS or per ASN_GW, etc) -Service guide manipulation -Service guide Delivery to MVNO server -Support of notification & alert by MVNO server U-Plane -Bearer Connection Setup & Release Network Operator (NAP) Base station controller (ASN_GW) Communication with NAP server, AAA, HA, PDF Authentication and billing information management of all allowed devices IP allocation support Bearer connection setup & release of all allowed devices Network Operator (NAP)

As shown in Table 1, by placing the MNO server in the NAP, a service area overlapped by a plurality of SPs can be configured as a separate MNO zone. In addition, one MVNO server may provide a service through a plurality of NAPs (that is, a plurality of MNO server functions) from one SP point of view. In addition, various combinations of NSP service zones and NAP service zones can be operated. That is, the relationship of NSP service zone: NAP service zone = n: m is possible.

Hereinafter, an overall procedure for receiving a service of a terminal based on the network structure of FIG. 1 described above will be described.

2 illustrates an overall procedure for receiving a service in a network structure according to an embodiment of the present invention.

Referring to FIG. 2, first, the MNO server of the NAP region negotiates with the ASN in step 201 to collect information necessary for MVNO zone configuration. In addition, the MNO server negotiates with the MVNO server in step 203 to collect information necessary for MVNO zone configuration. At this time, the MNO server may obtain NSP service zone provisioning information, operator policy (QoS, authentication and billing policy, etc.) information from different SP (service provider), the situation of NAP (base station) from the ASN Identifier and location information, etc.) can be obtained.

After collecting the information necessary to configure the MVNO zone, the MNO server processes the collected information in step 205 to form an MVNO zone (or NSP zone or virtual ASN zone). At this time, the MNO server is [NSP zone ID & NAP zone ID] mapping, [NSP IP ID & NAP MAC ID] mapping, [NAP zone ID & NAP ASN_GW ID & BSID] mapping, ASN resource allocation (by class or subcell) Alternatively, the number of users and the number of service flows allowed per base station or base station controller) may be performed.

In step 207, the MNO server delivers a service guide including information on the MVNO zone to the MVNO server of the CSN. In step 209, the MNO server delivers mapping information about the MVNO zone (base station list for each MVNO, resource allocation information, etc.) to the ASN. The ASN can perform call admission control and resource scheduling for each MVNO using the resource allocation information from the MNO server.

The MVNO server then stores the service guide from the MNO server in step 211. In this case, the MVNO server may reconfigure and store the service guide from the MNO server including NSP information such as application layer ID and NSP zone information, if necessary. Here, the MVNO server is a network entity of the CSN (Core Service Network) that can communicate with the terminal through the application layer. In step 213, the ASN stores mapping information (base station list for each MVNO, resource allocation information, etc.) from the MNO server.

The above process may be performed whenever a service guide reconfiguration is required due to joining a new SP or changing a service timetable of an existing SP.

On the other hand, if the user wants to receive the service guide, the terminal requests the service guide to the MVNO server through the application layer communication in step 215. The service guide request may be automatically performed inside a user's key action or terminal.

If the service guide is requested from the terminal, the MVNO server distributes the service guide to the terminal in step 217. At this time, the MVNO server may transmit a service guide directly to the terminal through application layer communication as shown, or, as another example, triggers a MAC layer call generation interworking procedure (eg, DSA) through the ASN to serve through a DSA-REQ message. You can send the guide. As another example, when the terminal transmits the DSA-REQ, the base station-base station controller-MNO server-MVNO server transmits the request, and the service guide is delivered in the reverse order so that the base station finally puts the service guide in the DSA-RSP to the terminal. Can transmit As another example, the terminal may receive the service guide through a message (eg, DCD, etc.) broadcast from the base station.

On the other hand, the terminal stores the service guide received in step 219. In this case, the service guide may include a content list and a service timetable.

In step 221, the base station of the ASN constructs a list of MVNOs (MVNO list) supported by the MSN based on the mapping information from the MNO server, and broadcasts the MVNO list through a broadcast message. The broadcast message may be, for example, a DL-MAP message, a downlink channel descriptor (DDC) message, or the like.

In step 223, the terminal decrypts the broadcast received from the base station, and determines whether it is an area that can receive a service through the MVNO list in the broadcast message.

If the service area is available, the terminal receives the content selected by the user from the MVNO server or the content provider in step 225. In step 227, the base station of the ASN constructs a neighbor base station list for each MVNO based on the mapping information from the MNO server, and generates a neighbor base station advertisement message (NBR-AVD message) for the neighbor base station list for each MVNO. Broadcast via

In step 229, the terminal decodes the neighbor base station advertisement message received from the base station, extracts and stores the neighbor base station list for each MVNO from the neighbor base station advertisement message. The neighbor base station list stored for each MVNO may be used to perform handover.

Although not shown in FIG. 2, the ASN may identify which VNO the UE belongs to in an initial access procedure. For example, ASN_GW has a mapping table in [terminal identifiers (eg, MAC address, NAI, realm, etc.) vs MVNO zone list], which can be acquired during the initial access procedure (ranging procedure, authentication procedure, etc.). The MVNO list to which the terminal belongs can be obtained using the terminal identifier. As another example, when the mapping table exists in another network entity (eg, AAA server, MNO server, etc.), the ASN may request the MVNO list to which the terminal belongs.

3 illustrates a configuration of a terminal according to an embodiment of the present invention.

As shown, the terminal includes an RF processing unit 300, a modem 302, a MAC layer processing unit 304, an IP layer processing unit 306, an application layer processing unit 308.

Referring to FIG. 3, first, the RF processor 300 transmits a baseband signal from a modem 302 through RF processing through an antenna, and converts an RF signal received through the antenna into baseband sample data. To the modem 502.

Modem 302 is a block for physical layer encoding and decoding. In case of transmission, the modem 302 performs physical layer encoding processing (channel encoding, interleaving, modulation, OFDM modulation (or CDMA modulation), etc.) from the MAC layer processing unit 304 to the RF processing unit 300. To pass. In case of reception, the modem 302 performs physical layer decoding processing (OFDM demodulation (or CDMA demodulation), modulation, deinterleaving, channel decoding, etc.) of the signal from the RF processing unit 300 to the MAC layer processing unit 304. To pass.

The MAC layer processor 304 encodes a service data unit (SDU) from the IP layer processor 306 into a MAC PDU, configures the MAC PDU in a burst, and delivers the MAC PDU to the modem 302. On the contrary, the MAC layer processing unit 304 extracts and decodes the MAC PDU from the received burst from the modem 302, and assembles the MAC PDU into an SDU and delivers it to the IP layer processing unit 306.

The IP layer processing unit 306 configures application layer data from the application layer processing unit 308 as an IP packet (SDU) and delivers the data to the MAC layer processing unit 304, and conversely, the IP packet from the MAC layer processing unit 304. To be assembled into application layer data and transferred to the application layer processing unit 308.

Looking at the operation of the present invention based on the structure of Figure 3 as follows.

First, when it is necessary to receive a service guide, the application layer processing unit 308 generates an application layer message requesting the service guide and transmits it to the MVNO server 10, and in response, the service guide (MVNO zone identifier, content list, service) An application layer message including a timetable) is received from the MVNO server 10. The service guide thus received is managed by the application layer processor 308.

Meanwhile, the MAC layer processor 304 decodes a broadcast message (eg, DL-MAP, DCD, etc.) received from the base station to obtain a list of MVNOs (MVNO list) supported by the base station. In addition, the MAC layer processing unit 304 decodes the neighbor base station advertisement message received from the base station to obtain a list of neighbor base stations for each MVNO. The MVNO list and the neighbor base station list for each MVNO thus obtained may be managed in a MAC layer or an application layer.

When the user applies for the service, the application layer processor 308 checks the MVNO zone identifier from the service guide, and determines whether the MVNO zone identifier is included in the MVNO list. If it is included in the MVNO list, the user requests the MVNO server to request content. In this case, the application layer may trigger the MAC_init DSA procedure by triggering the MAC layer, or the MVNO server receiving the service request through the application layer triggers the ASN to proceed with the BS_init DSA procedure, thereby receiving a wireless connection ( connection).

Meanwhile, when handover is required, the MAC layer processor 304 may determine a handover candidate base station list (or handover target base station) using the neighbor base station list for each MVNO.

4 illustrates a procedure for acquiring an MVNO list and a neighbor base station list for each MVNO in a terminal according to an embodiment of the present invention.

Referring to FIG. 4, first, during an initial access, the terminal performs a network entry procedure with the base station in step 401. At this time, the ASN can identify which VNO the UE belongs to. For example, ASN_GW has a mapping table in [terminal identifier (eg MAC address, NAI, realm, etc.) vs MVNO zone list] and can be acquired during the initial access procedure (ranging procedure, authentication procedure, etc.). The MVNO list to which the terminal belongs can be obtained by using the terminal identifier. As another example, when the mapping table exists in another network entity (eg, AAA server, MNO server, etc.), the ASN may request the MVNO list to which the terminal belongs.

In step 403, the UE checks whether a broadcast message (eg, a DCD message) including an MVNO list is received during the network entry procedure or after the network entry procedure. Here, the MVNO list may include identifiers of MVNOs supported by the serving base station.

When the broadcast message is received, the terminal proceeds to step 405 to extract the MVNO list supported by the serving base station from the broadcast message, and stores the extracted MVNO list.

On the other hand, if the broadcast message is not received, the terminal proceeds to step 407 to check whether a neighbor base station advertisement message (eg, NBR-ADV message) is received. When the neighbor base station advertisement message is received, the terminal extracts the neighbor base station list for each MVNO from the neighbor base station advertisement message in step 409 and stores the neighbor base station list for each MVNO. The neighbor base station list stored for each MVNO may be used for handover.

5 illustrates an operation procedure for receiving a service in a terminal according to an embodiment of the present invention.

Referring to FIG. 5, in step 501, the terminal checks whether an MVNO connection is required according to a user's request. In general, the service guide may include information about MVNOs allowed to the user (MVNO identifier, content list, service timetable), and the user may attempt to connect to one of the allowed MVNOs.

When the MVNO connection is required, the terminal checks the list of supportable MVNOs of the serving base station obtained from the broadcast message in step 503.

In step 505, the terminal checks whether an identifier of the requested MVNO is included in the MVNO list. That is, it is determined whether a service can be received from the connection requested MVNO.

When the identifier of the connection requested MVNO is included in the MVNO list, the terminal receives a content (service) selected by the user in step 507. In this case, a wireless connection for receiving content may be established through an MS_init DSA or BS_init DSA procedure. If the identifier of the requested MVNO is not included in the MVNO list, the terminal proceeds to step 509 and displays the service unavailable on the display window.

6 illustrates a handover procedure in consideration of MVNO in a terminal according to an embodiment of the present invention.

Referring to FIG. 6, the terminal first determines a need for handover in step 601. In general, the terminal scans the neighbor base stations for handover, and may determine the need for handover using the scanning result (signal strength of the base station). If it is determined that handover is necessary, the terminal may transmit a handover request message to the base station, and the handover request message may include a handover candidate base station list.

That is, when handover is required, the terminal configures a handover candidate base station list in step 603. In this case, the candidate base station list may be determined by referring to the neighbor base station list for each MVNO as well as the signal strength of the base station. If the terminal is receiving a service from a specific MVNO, it is preferable that the terminal constructs a candidate list using neighboring base stations belonging to the same MVNO.

After configuring the handover candidate base station list, the terminal performs a handover procedure later using the handover candidate base station list in step 605.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined not only by the scope of the following claims, but also by the equivalents of the claims.

1 is a diagram illustrating a network structure according to an embodiment of the present invention.

2 is a diagram illustrating an overall procedure for receiving a service in a network structure according to an embodiment of the present invention.

3 is a diagram illustrating a configuration of a terminal according to an embodiment of the present invention.

4 is a diagram illustrating a procedure for obtaining an MVNO list and a neighbor base station list for each MVNO in a terminal according to an embodiment of the present invention.

5 is a diagram illustrating an operation procedure for receiving a service in a terminal according to an embodiment of the present invention.

6 is a diagram illustrating a handover procedure in consideration of MVNO in a terminal according to an embodiment of the present invention.

Claims (24)

In the network for providing services of different service providers through a wireless network, Located in Network Access Provider (NAP) area, MVNO (Mobile Virtual Network Operator) zone is allocated in consideration of information from different service providers and resources of corresponding network access provider (NAP), and for each MVNO zone. At least one mobile network operator (MNO) server for allocating resources, Located in the CSN (Core Service Network), and comprises a service guide using the information on the MVNO zone from the MNO server, and includes at least one MVNO server to provide a service through the MVNO zone according to the service guide , At least one MVNO provides services for a single NAP or a single MVNO provides services over at least one NAP. The method of claim 1, Located in the NAP area, the network further comprises an ASN (Access Service Network) to perform the lock control and resource scheduling using the resource allocation information for each MVNO from the MNO server. The method of claim 2, A network characterized in that different MVNOs operate independently of each other and do not allow handover between MVNOs. The method of claim 2, A network characterized in that different MVNOs operate independently of each other and allow handover between MVNOs. The method of claim 2, A network characterized in that different MVNOs share an authenticator, a paging controller, and a data path function (DPF) and do not allow handover between MVNOs. The method of claim 2, A network characterized in that different MVNOs share an authenticator, a paging controller, and a data path function (DPF), and allow handover between MVNOs. The method of claim 2, And the base station in the ASN broadcasts an MVNO list supported by the base station. The method of claim 2, The base station in the ASN is characterized in that the broadcasting of the neighbor base station list for each MVNO. The method of claim 2, The ASN is characterized in that the MVNO to which the terminal subscribes using the terminal identifier obtained through the initial access procedure. The method of claim 2, And a terminal obtaining a supportable MVNO list of the base station and a list of neighboring base stations capable of handover by MVNO through a message broadcast from a base station in the ASN. The method of claim 1, The MVNO server may serve as a user equipment for subscription management, service guide provisioning, NSP zone ID and IP layer ID allocation and management, and user equipment. At least one of service guide distribution to MS, performing user authentication & authorization, key management & distribution, user interaction, and notification & alert functions. A network characterized by performing one function. The method of claim 1, The MNO server includes NSP zone ID and NAP Zone ID mapping allocation, NAP zone ID, ASN_GW ID and BSID mapping, and ASN resources. Assignment (# of users, # of SFs per class or per subcell or per BS or per ASN_GW, ets), service guide manipulation, Service Guide delivery to MVNO server, MVNO server A network characterized by performing at least one of the functions of support of notification & alert by MVNO servers. In a communication method of a network for providing services of different service providers through a wireless network, At least one MNO server located in the NAP area allocates an MVNO zone in consideration of information from different service providers and resources of the corresponding NAP, and allocates resources for each MVNO zone; At least one MVNO server located in the CSN comprises the step of configuring the service guide using the information on the MVNO zone from the MNO server, and providing the service through the corresponding MVNO zone according to the service guide, At least one MVNO provides services for a single NAP or a single MVNO provides services over at least one NAP. The method of claim 13, The ASN located in the NAP region, further comprising the step of performing the rock lock control and resource scheduling using the resource allocation information for each MVNO from the MNO server. The method of claim 14, Different MVNOs operate independently of each other and do not allow handover between MVNOs. The method of claim 14, Different MVNOs operate independently of each other and allow handover between MVNOs. The method of claim 14, Different MVNOs sharing an authenticator, a pagining controller and a DPF, and do not allow handover between MVNOs. The method of claim 14, Different MVNOs sharing an authenticator, a paging controller, and a DPF, and allowing handover between MVNOs. The method of claim 14, And transmitting, by the base station in the ASN, an MVNO list supported by the base station. The method of claim 14, The base station in the ASN, further comprising the step of broadcasting a neighbor base station list for each MVNO. The method of claim 14, The ASN further comprises the step of identifying the MVNO subscribed to the terminal by using the terminal identifier obtained through the initial access procedure. The method of claim 14, The terminal further includes the step of obtaining a supportable MVNO list of the base station and the MVNO-specific handover possible neighbor base station list through a message broadcast from the base station in the ASN. The method of claim 13, The MVNO server may serve as a user equipment for subscription management, service guide provisioning, NSP zone ID and IP layer ID allocation and management, and user equipment. At least one of service guide distribution to MS, performing user authentication & authorization, key management & distribution, user interaction, and notification & alert functions. A method characterized by performing one function. The method of claim 13, The MNO server includes NSP zone ID and NAP Zone ID mapping allocation, NAP zone ID, ASN_GW ID and BSID mapping, and ASN resources. Assignment (# of users, # of SFs per class or per subcell or per BS or per ASN_GW, ets), service guide manipulation, Service Guide delivery to MVNO server, MVNO server And at least one of a support of notification & alert by MVNO servers function.

Images