KR101144485B1 - Hierarchical service list - Google Patents

Abstract

The present invention relates to communication between a network and user equipment in a wireless communication system. The present invention includes receiving a communication on a first frequency; And receiving information on the first frequency, wherein the information indicates at least one transmission frequency that does not have an associated uplink service; And determining not to perform any transmission frequency search that does not have an associated uplink service different from the at least one transmission frequency.

Wireless communication, MBMS, layer

Description

Hierarchical Service List {HIERARCHICAL SERVICE LIST}

In accordance with 35 U.S.C §119, this application claims U.S provisional application No. Claim the benefit of the initial filing date and priority of 60/890, 152, the contents of which are incorporated by reference in their entirety.

The present invention relates to communication between a user equipment and a network in a wireless communication system.

The Universal Mobile Telecommunication System (UMTS) is a European third generation IMT-2000 mobile communication system that evolved from the European standard known as the global system for mobile communications (GSM). UMTS aims to provide improved mobile communication services based on GSM core network and wideband code division multiple access (W-CDMA) wireless access technology. In December 1998, ETSI in Europe, ARIB / TTC in Japan, T1 in the US, and TTA in Korea formed the Third Generation Partnership Project (3GPP) for detailed standardization of UMTS technology. In order to achieve the rapid and efficient technological development of UMTS, 3GPP is divided into five Technical Specification Groups (TSG) in consideration of the independence of network components and their operation. Each TSG is responsible for the development, approval, and management of standards within the relevant areas, among which the Radio Access Network (RAN) group (TSG RAN) is the W-CDMA access technology in UMTS. Develop standards for the functions, requirements, and interfaces of the UTRAN (UMTS Terrestrial Radio Access Network), a new radio access network to support this.

1 illustrates the basic structure (overview) of a UMTS network, which includes a mobile terminal (or UE) 1, a UTRAN 2 and a core network (CN) 3. The UTRAN 2 is composed of a plurality of Radio network controllers (RNCs) 4 and NodeBs 5 connected through the Iub interface. Each RNC 4 controls a number of NodeBs 5. Each NodeB 5 controls one or multiple cells, where one cell covers a given geographic area on a given frequency.

Each RNC 4 is connected to a core network (CN) 3, or to the CN's Mobile Switching Center (MSC) 6 entity and a generic Packet Radio Service (GPRS) Supporting Node (SGSN) 7 entity, via an Iu interface. RNCs 4 can be connected to other RNCs via an Iur interface.

     The RNC 4 is responsible for allocating and managing radio resources and serves as an access point for the core network 3.

The NodeBs 5 receives information transmitted by the physical layer of the UE1 through uplink and transmits data to the UE1 through downlink. The NodeBs 5 serve as an access point of UTRAN2 for the UE1.

SGSN7 is connected to EIR (equipment identity register) 8 through Gf interface, to MSC6 through Gs interface, to gateway GPRS support node (GGSN9) through GN interface, and to home subscriber server (HSS) through GR interface. .

The EIR8 maintains lists of UEs1 licensed for use in the network and maintains lists of UEs1 not licensed for use in the network.

The MSC6 controls a connection for a circuit switched service. MSC6 is connected to the media gateway (MGW11) via the NB interface, to the EIR8 via the F interface, and to the HSS10 via the D interface.

The MGW11 is connected to the HSS10 through the C interface and also to the public switched telephone network (PSTN). The MGW11 enables application of codecs between the PSTN and the connected RAN.

The GGSN9 is connected to the HSS10 through the GC interface and is connected to the Internet through the GI interface. The GGSN9 is responsible for routing, charging, and separation of data flows to different radio access bearers (RABs).

The HSS10 is responsible for subscription data of users.

UTRAN2 configures and maintains the RAB for communication between UE1 and CN3. The CN3 requests an end-to-end Quality of Service (QoS) requirement from the RAB, and the RAB supports the QoS requirements set by CN3. Thus, UTRAN2 can meet end-to-end QoS requirements by configuring and maintaining the RAB.

The services provided to a particular UE1 are broadly classified into circuit switched services and packet switched services. For example, a typical voice call service is a circuit switched service and a web browsing service over an Internet connection is classified as a packet switched service.

When supporting circuit switched service, RNC4s are connected to MSC6 of CN3, which is connected to a gateway mobile switching center (GMSC) which manages connection with other networks. When supporting the packet switched service, the RNC4s are connected to the CN3 (serving general packet radio service (GPRS) support node) and GGSN9 of CN3.

The SGSN7 supports packet communication with RNCs, and the GGSN9 manages connection with other packet switched networks such as the Internet.

2 is a diagram illustrating a structure of air interface protocols between UE1 and UTRAN2 according to the 3GPP radio access network standard. As shown in FIG. 2, the air interface protocol includes a physical layer, a data link layer, and a network layer as a vertical layer, and includes a user plane (U-plane) and control information for transmitting user data as a horizontal plane. It consists of a control plane (C-plane) for transmission. The user plane is an area for managing traffic information of a user such as voice or an IP (Internet Protocol) packet, and the control plane is an area for managing control information for an interface, call maintenance and management of a network. The protocol layers may be divided into a first layer L1, a second layer L2, and a third layer L3 based on three lower layers of the Open System Interconnection (OSI) reference model.

The first layer L1 or the physical layer provides an information transfer service to a higher layer by using various wireless transmission technologies, and media access control (Medium) which is a higher layer through a transport channel. It is connected to the Access Control (MAC) layer. The MAC layer and the physical layer exchange data with each other through a transport channel.

The second layer L2 includes a MAC layer, a Radio Link Control (RLC) layer, a Broadcast / Multicast Control (BMC) layer, and a Packet Data Convergence Protocol (PDCP). Contains the hierarchy. The MAC layer manages the mapping between logical channels and transport channels, provides allocation of MAC parameters for the allocation and reassignment of radio resources, and is connected to higher layers or RLC layers via logical channels.

Various logical channels are provided according to the type of information to be transmitted. In general, a control channel is used for transmitting control plane information, and a traffic channel is used for transmitting user plane information.

The logical channel may be a common channel or a dedicated channel depending on sharing. Logical channels include Dedicated Traffic Channel (DTCH), Dedicated Control Channel (DCCH), Common Traffic Channel (CTCH), Common Control Channel (CCCH), Broadcast Control Channel (BCCH), and Paging Control Channel (PCCH) or Shared Channel (SHCCH). Control Channel).

The BCCH provides information including information utilized by the terminal to access the system. UTRAN accesses the terminal using the PCCH.

For the purpose of multimedia broadcast / multicast service (MBMS), traffic and control channels exist in addition to the MBMS standard. MBMS control information is transmitted using an MBMS point-to-multipoint control channel (MCCH) and MBMS service data is transmitted using an MBMS point-to-multipoint Traffic Channel (MTCH).

Scheduling information is transmitted using an MMS (MBMS scheduling channel). A list of the various logical channels is shown in FIG.

The MAC layer is connected to the physical layer through transport channels and according to the type of transport channel managed, the MAC-b sublayer, the MAC-d sublayer, the MAC-c / sh sublayer, the MAC-hs sublayer, and the MAC -m can be divided into sublayers. The MAC-b sublayer manages a broadcast channel (BCH), which is a transport channel for broadcasting system information. The MAC-c / sh sublayer manages a common transport channel such as a forward access channel (FACH) or a downlink shared channel (DSCH) shared by a plurality of terminals, or a RACH (Radio Access Channel) as an uplink. The MAC-m sublayer manages MBMS data.

4 shows possible mapping between logical and transport channels on the side of the UE, and FIG. 5 shows possible mapping between logical and transport channels on the side of the UTRAN.

The MAC-d sublayer manages a dedicated channel (DCH), which is a dedicated transport channel for a specific terminal. The MAC-d sublayer is located in a Serving Radio Network Controller (SRNC) that manages the terminal, and one MAC-d sublayer exists in each terminal.

The RLC layer supports reliable data transmission according to an RLC operation mode, and performs partitioning and concatenation for a plurality of RLC service data units (RLC SDUs) delivered from an upper layer. When the RLC layer receives the RLC SDUs from an upper layer, the RLC layer adjusts the size of each RLC SDU in a proper manner in consideration of processing capacity to generate data units to which header information is added. The data units generated as described above are called protocol data units (PDUs). The PDUs are delivered to the MAC layer via a logical channel. The RLC layer includes an RLC buffer for storing the RLC SDUs and / or RLC PDUs.

The BMC layer schedules a cell broadcast message (called a 'CB message') transmitted from the core network and broadcasts the CB messages to terminals located in a specific cell or cells.

The PDCP layer, which is an upper layer of the RLC layer, allows data transmitted through a network protocol such as IPv4 or IPv6 to be effectively transmitted to a radio interface having a relatively small bandwidth. To achieve this, the PDCP layer reduces unnecessary control information used in wired networks, which is called header compression.

The radio resource control (RRC) layer is the lowest layer of the third layer L3 and is defined only in the control plane. The RRC layer controls transport channels and physical channels for setting, resetting and releasing or canceling the radio bearers (RBs). The RRC also manages additional services such as user mobility and location services within the RAN.

The RB refers to a service provided by the second layer (L2) for data transmission between the terminal and the UTRAN. In general, setting up a radio bearer refers to a process of setting detailed parameters and operation methods by defining characteristics of a protocol layer and a channel required to provide a specific data service.

Various possibilities of mapping between radio bearers and transport channels for a given UE do not always hold. The UE and the UTRAN infer a possible mapping according to the state of the UE and the process currently being performed by the UE / UTRAN. Various other states or modes are described in more detail below as far as the present invention contemplates.

Different transport channels are mapped to different physical channels. For example, the RACH transport channel may be mapped to a predetermined PRACH, DCH to DPCH, FACH and PCH to S-CCPCH, and DSCH to PDSCH. The physical channel is configured by RRC signaling exchange between the RNC and the UE.

The RRC mode indicates whether a logical connection exists between the RRC of the UE and the RRC of the UTRAN. If there is a connection, the terminal is in the RRC connected mode. If there is no connection, the terminal is in idle mode.

Since the RRC connection exists for the UEs in the RRC connected mode, the UTRAN may determine whether a specific terminal exists in the cell unit. For example, the UTRAN can determine which cell or set of cells the UE in the RRC connected mode and which physical channel the UE listens to, thereby effectively controlling the UE.

On the other hand, the UTRAN cannot determine the presence of the terminal in the idle mode. The existence of the terminal in the idle mode is determined only by the core network. In particular, the core network can determine only whether the terminal in the idle mode exists in an area larger than the cell, such as a location or a routing area. Therefore, the presence of the idle mode terminal is determined in a large area. In order to receive a mobile communication service such as voice or data, an idle terminal must move or change to an RRC connected mode. A description of possible transitions between modes and states is shown in FIG. 6.

The UE in RRC connected mode may be in various states such as CELL_FACH state, CELL_PCH state, CELL_DCH state, or URA_PCH state. Depending on the state, the UE performs different operations and listens to different channels.

For example, a UE in a CELL_DCH state may try to listen to a transport channel of a DCH type among various channels. Transport channels of the DCH type include DTCH and DCCH transport channels, which may be mapped to specific DPCH, DPDSCH or other physical channels.

The UE in CELL FACH state will listen to a number of FACH transport channels mapped to a particular S-CCPCH. The UE in the PCH state will listen to the PICH channel and the PCH channel mapped to a particular S-CCPCH physical channel.

It sends main system information to BCCH logical channel which is mapped on P-CCPCH (Primary Common Control Physical Channel). Specific system information blocks are sent on the FACH channel. When transmitting the system information to the FACH, the UE receives the configuration of the FACH on the BCCH or dedicated channel received on the P-CCPCH. When the system information is transmitted to the BCCH (ie, through the P-CCPCH), a system frame number is used to share the same timing reference between the UE and the Node-B in each frame or two sets of frames. ) Is sent. The P-CCPCH is transmitted using the same scrambling code as the primary common pilot channel (P-CPICH), which is the primary scrambling code of the cell. The spreading code used by the P-CCPCH always has a fixed spreading factor 256 and its number is 1. The UE is transmitted and fixed through the information transmitted from the network about the system information of neighboring cells which it has already read, or through a message received on the DCCH channel, or using the fixed SF 256 and the spread code number 0. The primary scrambling code can be known by searching for the P-CPICH transmitting the pattern.

The system information includes information on neighbor cells, configuration information of RACH and FACH transport channels, and configuration information of MICH and MCCH, which are dedicated channels for MBMS service.

Whenever the UE changes its current camping (idle mode) cell or when the UE selects a cell (in CELL_FACH, CELL_PCH or URA_PCH state), the UE verifies that it has available system information. . The system information is composed of System Information Blocks (SIBs), Master Information Blocks (MIBs), and scheduling blocks. The MIB is transmitted very often and provides timing information for scheduling blocks and various SIBs. For SIBs associated with a value tag, the MIB also contains information about the latest version of some SIBs. SIBs not associated with a value tag are associated with an expiration timer. SIBs associated with an expiration timer are no longer valid and need to be reread if the last read time of the SIB is greater than the expiration timer value. SIBs associated with a value tag are valid only if they have the same value tag as the value tag broadcast in the MIB. The block has an effective area range (area scope of validity) indicating in which cells the SIB is available, such as Cell, Public Land Mobile Network (PLMN) or equivalent PLMN.

An SIB having an area range 'Cell' is valid only for the cell to which it is read. SIBs with area range 'PLMN' are valid for all PLMNs, and SIBs with area range 'equivalent PLMN' are valid for all PLMNs and equivalent PLMNs.

In general, UEs read the system information when in the idle mode or in the CELL_FACH state, CELL_PCH state, or URA_PCH state of the cell they have selected or the cell in which they are staying. In the system information, UEs get information about neighboring cells on the same frequency, different frequency and different Radio Access Technologies (RAT). This allows UEs to know which cells are candidate cells for cell reselection.

MBMS is introduced in the UMTS standard in Release 6 (Rel-6) of the specification, which allows selective combining and transmission mode selection between point-to-many transmission, point-to-many and point-to-point bearers. It describes a technique for optimized transmission of the MBMS bearer service including. It is used to save radio resources when sending the same content to multiple users, thereby enabling services such as TV. MBMS data can be classified into two categories: control plane information and user plane information. The control plane information includes physical layer configuration information, transport channel configuration information, radio bearer configuration information, information on an ongoing service, aggregation information, scheduling information, and the like. In order for the UEs to receive such information, MBMS bearer specific control information for MBMS is transmitted to the UEs.

User plane data of MBMS bearers is matched to a dedicated transport channel for point-to-point service transmitted only to one UE, or shared transmission for point-to-many service transmitted to (or received by) multiple users at the same time. It can be mapped to a channel.

Point-to-point transmission is used to convey MBMS specific control / user plane information as well as dedicated control / user plane information between the network and the UE in RRC connected mode. The point-to-point transmission is used for multicast or broadcast mode of MBMS. DTCH is used for UEs in CELL_FACH and Cell_DCH states. This enables existing mapping to transport channels.

In order to make optimal use of cell resources, a function called aggregation is introduced in MBMS applications. This counting procedure is used to determine the number of UEs that wish to receive a given service, and is performed using the counting procedure shown in FIG. 7.

For example, a UE interested in a particular service receives information about the availability of MBMS services. The network may inform the UE that it should inform the network of its interest in the service in the same way that the UE sends 'access information' on the MCCH channel. Based on the probability factor included in the access information message, it is determined that only the interested UE will respond with a predetermined probability. In order to inform the network that the UE is interested in a given service, the UE will send an RRC connection establishment message or a cell update message to the network in the cell in which the UE has received the aggregate information. This message will contain an identifier indicating the service of interest to the UE.

If the network is operating on several frequencies, if the UE is camping on one frequency and the MBMS service is transmitted at another frequency, the UE will not be aware that the MBMS service is transmitted at the other frequency. Accordingly, the UE can receive information at frequency A indicating that a predetermined service is available at frequency B through a frequency convergence procedure.

In general, the MBMS point-to-many control channel (MCCH) is a logical channel used for point-to-many downlink transmission of control plane information between the UE and the network in an RRC connection or idle mode. The control plane information on the MCCH is MBMS specific and is transmitted to the UEs in the cell with the activated MBMS service. The MCCH may be transmitted in an S-CCPCH transmitting a DCCH of UEs in a CELL_FACH state, a standalone S-CCPCH, or the same S-CCPCH having an MTCH.

The MCCH is mapped to a specific FACH in the S-CCPCH as shown on the BCCH. In the soft combination, the MCCH is mapped to an S-CCPCH (CCTrCH in TDD) that is different from the MTCH. The reception of paging has priority over the reception of the MCCH for idle mode and URA / CELL_PCH UEs. The configuration (modification period, repetition period, etc.) of the MCCH is implemented in the system information transmitted on the BCCH.

In general, the MBMS point-to-multi-traffic channel (MTCH) is a logical channel used for point-to-down downlink transmission of user plane information between the UE and the network in an RRC connection or idle mode. The user plane information on the MTCH is MBMS service specific and is transmitted to the UEs in the cell with the activated MBMS service. The MTCH is mapped to a specific FACH in the S-CCPCH as indicated on the MCCH.

In general, the MBMS point-to-multiple scheduling channel (MSCH) is a logical channel used for point-to-down downlink transmission of MBMS service transmission schedules between a network and UEs in an RRC connection or idle mode. Control plane information on the MSCH is MBMS service and S-CCPCH specific and is transmitted to the UEs in the cell receiving the MTCH. MSCH is transmitted in each S-CCPCH carrying the MTCH. The MSCH is mapped to a specific FACH in the S-CCPCH as indicated on the MCCH. Due to different error conditions, the MSCH is mapped to a different FACH than the MTCH.

In general, FACH is used as a transport channel for the MTCH, MSCH and MCCH. In addition, the S-CCPCH is used as a physical channel for the FACH transmitting the MTCH, MSCH, or MCCH.

In general, the following connections between logical channels and transport channels exist only within the downlink: 1) MCCH may be mapped to FACH; 2) MTCH may be mapped to FACH; And 3) MSCH may be mapped to FACH. As seen from the UE and UTRAN side, the mapping is shown in FIGS. 8 and 9 respectively.

For MCCH, the RLC mode to be used is UM-RLC and has the enhancements needed to support out-of-sequence SDU delivery. The MAC header is used for logical channel type identification.

For MTCH, the RLC mode to be used is UM-RLC and has the enhancements needed to support optional combinations. Rapid repetition can be used in RLC-UM. The MAC header is used for logical channel type identification and MBMS service identification.

For MSCH, the RLC mode to be used is UM-RLC. The MAC header is used for logical channel type identification.

MBMS notification utilizes an MBMS specific PICH called MBMS Notification Indicator Channel (MICH) in a cell. Coding for the MICH is defined within state-3 physical layer specifications.

In general, MCCH information is transmitted on a predetermined schedule. Here, the schedule identifies a transmission time interval (TTI), i.e., a number of frames, that includes the start of MCCH information. The MCCH information is transmitted in many variable TTIs. The UTRAN transmits the MCCH information in successive TTIs. The UE 1) until it receives all MCCH information, 2) until it receives a TTI that does not include MCCH data, or 3) until the information contents indicate that no further reception is necessary (e.g. For example, the SCCPCH is continuously received until there is no change in the desired service information.

In this way, the UTRAN repeatedly transmits the MCCH information following scheduled transmission for improved reliability. The MCCH schedule is common to all services.

The entire MCCH information is transmitted periodically based on a 'repetition period'. The 'modification period' is defined as an integer multiple of the iteration period. MBMS ACCESS INFORMATION is transmitted periodically based on the 'access info period'. This period is an integer divider of the 'repeat period'. The value of the repetition period and the change period is provided in the system information of the cell to which the MBMS is transmitted.

MCCH information may be classified into critical and non-critical information.

The important information consists of MBMS NEIGHBORING CELL INFORMATION, MBMS SERVICE INFORMATION, and MBMS RADIO BEARER INFORMATION. The non-critical information corresponds to MBMS ACCESS INFORMATION. The change to the sensitive information is applied in the first MCCH transmission of the modification period and at the beginning of each modification period. The UTRAN transmits MBMS CHANGE INFORMATION including MBMS service IDs whose MCCH information has been changed in the modification period. The MBMS CHANGE INFORMATION is repeated at least once in each repetition period of the modification period. Changes to non-critical information can occur at any time.

10 illustrates a schedule for transmitting MBMS SERVICE INFORMATION and RADIO BEARER INFORMATION. Blocks marked differently represent different MCCH content.

To increase coverage, UEs located between different cells can simultaneously receive the same MBMS service from other cells and combine the received information as shown in FIG. 11. In this case, the UE reads the MCCH from the cell selected by the UE based on a predetermined algorithm.

Referring to FIG. 11, on the MCCH from the selected cell (eg, cell A-B), the UE receives information on the service of interest. The information includes information related to a configuration of a physical cell, a transport channel, an RLC configuration, a PDCP configuration, etc. of a current cell and adjacent cells (eg, cells AA and Cell B) that the UE can receive. It includes. In other words, the received information includes information that the UE needs to receive the MTCH carrying the service of interest to the cells A-A, A-B and B.

When the same service is carried on different cells, the UE may or may not combine services from different cells. Where a combination is possible, the combination is done at different levels, such as 1) noncombinable, 2) optional combination at RLC level, and 3) L1 combination at physical level.

An optional combination for MBMS point-to-many transmission is supported by RLC PDU numbering.

Thus, as long as the de-synchronization between MBMS point-to-multipoint transport streams does not exceed the RLC re-ordering capability of the UE, the optional combination within the UE may have similar MBMS RB. It is possible from the cells providing the bit rate.

Therefore, there is one RLC entity in the UE side.

For selective combination, there is one RLC entity per MBMS service that utilizes point-to-multiple transmissions within the cell group of the CRNC. All cells in the cell group are under the same CRNC. When asynchronous occurs between MBMS transmissions in neighboring cells belonging to one MBMS cell group, the CRNC may perform a re-synchronization operation to allow UEs to perform a selective combination between the cells. .

For TDD, optional combinations and soft combinations can be used when Node-Bs are synchronized. For FDD, soft combinations can be used when Node-Bs are synchronized within the soft combination reception window of the UE, the data fields of the soft combined S-CCPCHs being the same during the soft combination moment.

When a selective or soft combination between cells is valid, the UTRAN sends an MBMS NEIGHBORING CELL INFORMATION containing the MTCH configuration of available neighbor cells in the selective or soft combination. In partial soft combining applications, the MBMS NEIGHBORING CELL INFORMATION includes an L1-combination schedule, which is a function of the S-CCPCH transmitted in a serving cell by the UE in a serving cell. Along with MBMS NEIGHBORING CELL INFORMATION, the UE may receive MTCH transmissions from neighbor cells without receiving the MCCH of neighbor cells.

The UE determines the neighbor cell suitable for a selective or soft combination based on a threshold (eg measured CPICH Ec / No) and the presence of MBMS NEIGHBORING CELL INFORMATION of the neighbor cell. The feasibility for selective or soft combinations is signaled to the UE.

Long-term evolution (LTE) of UMTS is under discussion by the 3rd generation partnership project (3GPP) that standardized UMTS. The 3GPP LTE is a technology that enables high speed packet communication. Many techniques have been proposed for the purpose of LTE, including those aimed at reducing user and provider costs, improving service quality, and expanding and improving coverage and system capacity.

12 shows the architecture of an LTE system. Each aGW 115 is associated with one or multiple access gateways (aGW) 115. The aGW 115 is connected to the Internet and other nodes (not shown) that allow access to other networks such as GSM, UMTS, WLAN.

3GPP LTE is a high level requirement that requires reduced cost per bit, increased service availability, flexible use of frequency bands, simple structure, open interface, and proper power consumption of the terminal. In general, UTRAN 2 corresponds to Evolved-UTRAN (E-UTRAN), and NodeB 5 and / or RNC 4 corresponds to e-NodeB (eNB) 105 in the LTE system.

In 3GPP LTE systems, System Information (SI) transmits other cell and network specific parameters to the UE for successful attachment to the network. The system information also facilitates paging and allows the UE to use other network services. Every cell constantly broadcasts its system information on a channel, such as a broadcast control channel (BCCH). In addition, every UE registering with the network or performing a handover to a specific cell first reads the cell specific information.

The present invention relates to communication between a user equipment and a network in a wireless communication system.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned in accordance with the practice of the invention. The objects and other advantages of the present invention will be realized and attained by means of the baths pointed forth in the written description and claims hereof as well as the appended drawings in particular.

In order to achieve the advantages associated with the specific and broadly described objects of the present invention, the present invention provides a method of communication between a network and a user device. The method includes receiving a communication on a first frequency; Receiving information on the first frequency, wherein the information indicates at least one transmission frequency that does not have an associated uplink service; And determining not to search for any transmission frequency that does not have an associated uplink service different from the at least one transmission frequency.

Advantageously, the method further comprises determining that said at least one transmission frequency indicated by said information includes all frequencies that provide point-to-many service and do not have an associated uplink service.

Advantageously, said first frequency has associated uplink and downlink services. According to one aspect of the invention, the method comprises the steps of monitoring at least one service provided on the at least one transmission frequency; Determining a service available for reception; And receiving the available service.

In another embodiment of the present invention, a method of communication between a network and a user equipment (UE) comprises: receiving communication on a first frequency; Receiving information on the first frequency, the information indicating that there is no frequency that does not have an associated uplink service; And determining not to search for any transmission frequency that does not have an associated uplink service. Advantageously, said first frequency has associated uplink and downlink services.

In another embodiment of the present invention, a method of communication between a network and a user equipment (UE) comprises: receiving communication on a first frequency; Receiving information on the first frequency, wherein the information does not include any frequency that does not have an associated uplink service and does not indicate that there is no frequency that does not have an associated uplink service; And determining to search for a transmission frequency that does not have an associated uplink service.

In one aspect of the invention, the transmission frequency without the associated uplink service provides a point-to-many service. In another aspect of the invention, the first frequency has associated uplink and downlink services. In another aspect of the invention, the method comprises the steps of: monitoring at least one service provided on the transmission frequency that does not have an associated uplink service; Determining a service available for reception; And receiving the available service.

In another embodiment of the present invention, a communication method between a network and a user equipment (UE) comprises the steps of: transmitting a communication on a first frequency; Transmitting information on the first frequency, wherein the information indicates at least one transmission frequency that does not have an associated uplink service.

Advantageously, the information instructs the UE not to search for any transmission frequency that does not have an associated uplink service that is different from the at least one transmission frequency. Advantageously, said at least one transmission frequency indicated by said information includes all frequencies that provide point-to-many service and do not have an associated uplink service. Advantageously, said first frequency has associated uplink and downlink services.

 In another embodiment of the present invention, a method of communication between a network and a user equipment (UE) comprises: transmitting a communication on a first frequency; And transmitting information on the first frequency, wherein the information indicates that there is no frequency that does not have an associated uplink service.

Advantageously, the information instructs the UE not to do any transmission frequency search that does not have an associated uplink service. Advantageously, said first frequency has associated uplink and downlink services.

In another embodiment of the present invention, a method of communication between a network and a user equipment (UE) comprises: transmitting a communication on a first frequency; And transmitting information on the first frequency, wherein the information does not include any frequency that does not have an associated uplink service and does not indicate that there is no frequency that does not have an associated uplink service. . Advantageously, said information instructs said UE to make a transmission frequency search that does not have an associated uplink service. Advantageously, said transmission frequency with no associated uplink service provides point-to-many service. Advantageously, said first frequency has associated uplink and downlink services.

It should be noted that the foregoing general description of the invention and the following detailed description are merely illustrative and explanatory only and may provide a more detailed description of the invention that may be raised.

The following drawings are provided to aid a more detailed understanding of the present invention, are incorporated in and constitute a part of this specification, illustrate embodiments of the invention, and together with the description serve to explain the principles of the invention. Features, components, and aspects of the invention, which are referred to by the same reference numbers in different figures, represent the same or similar features, components, and aspects in one or more embodiments.

1 shows a conventional UMTS network.

2 shows a conventional air interface protocol between a UE and a UTRAN.

3 shows a logical channel structure.

4 shows a possible mapping between logical channels and transport channels from the UE perspective.

5 shows a possible mapping between logical and transport channels from the UTRAN perspective.

6 shows a possible UE state transition.

7 shows a typical counting procedure.

8 shows a mapping between logical channels and transport channels from the UE perspective.

9 shows a mapping between logical channels and transport channels from the UTRAN perspective.

10 shows a schedule in which MBMS service information and radio bearer information are transmitted together.

11 shows a UE receiving an MBMS service from multiple cells.

12 shows a structure of an LTE system.

FIG. 13 shows an FDD MBMS multicarrier network in Rel-6 with Rel-7 dual receiver UEs.

14 illustrates operation of a dual receiver UE in accordance with an embodiment of the present invention.

15 shows an MBMS multicarrier network in Rel-6 with optimization for Rel-7 dual receiver UEs.

16 shows cells that the UE allows to act on MCCH.

17 illustrates cells in which the UE attempts to receive MCCH / MTCH.

18 shows a Rel-6 network (single carrier / multicarrier) with separate independent MBMS downlink only frequency for dual receiver UEs (FDD / TDD).

19 is a flowchart illustrating a communication method between a network and a dual receiver UE according to the first embodiment of the present invention.

20 illustrates a network between a dual receiver UE and a network according to another embodiment of the present invention.

It is a flowchart explaining a communication method.

FIG. 21 illustrates a unicast network including two single frequency network regions and different cells covering the same geographical region according to the first embodiment of the present invention.

FIG. 22 illustrates three frequencies used for provisioning a multicell multicast broadcast single frequency network (MBSFN) according to an embodiment of the present invention.

23 shows a block diagram of a mobile station (MS) or UE in accordance with an embodiment of the present invention.

The present invention relates to communication between a network and a user device in a wireless communication system.

DETAILED DESCRIPTION A detailed description will be made of embodiments of the invention, examples of which are set forth in the following figures. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or similar parts.

Various embodiments of the present invention include a method for simultaneous reception of MBMS service and dedicated service on two different frequencies. Specific embodiments include matters such as counting, point-to-point setting, and frequency convergence.

With regard to frequency division duplex (FDD) cases, adding a second receiver to a UE dedicated to MBMS has several advantages and provides freedom to the network. Such dual receiver UEs provide some desirable options. For example, the second receiver can be used to reduce the potential number of conflicts, and can be used for the addition of frequencies that are dedicated to MBMS and received by the second receiver.

It is desirable for the network to have backward capabilities for use with UEs that do not have dual receivers. To ensure reverse capability, the network may be supplied with specific functionality to address these issues. For example, the network may inform via dedicated or common control signaling whether specific UE behavior is allowed for dual receiver UEs. One technique is to set MBMS default behavior so that the UE does not use a second receiver (FDD or TDD) for reception of MBMS.

One technique for avoiding non-Rel.7 UEs (eg, UEs that do not have dual receivers) from camping on the dedicated MBMS frequency is to 'hide the frequency from such UEs. 'to be. Using this technique, cells associated with the dedicated MBMS frequency are not included in the neighbor cell list of frequencies available to all UEs. In particular, an additional cell or frequency related to MBMS can be selectively provided via BCCH / MCCH, for example using a specific extension, so that only dual receiver UEs can listen to the dedicated frequency. .

Another issue is that single receiver UEs will detect the MBMS frequency during the periodic frequency scan. One way to solve this issue is not to broadcast one or more of the following SIBs: 1, 3, 5 5bis, or 7 (SIB 13 for TDD cases) on the frequency.

This approach allows the UE to respond to counting at the frequency / cell camping regardless of the cell associated with the MBMS service broadcast.

 In addition, specific handling may be implemented to allow the RNC to correlate with a counting response / PtP configuration for dual receiver UEs, for example using an appropriate service identifier.

 Another technique to optimize MBMS services is to use the TDD spectrum for MBMS transmissions, and the FDD spectrum for dedicated services. In this scenario, it is advantageous not to include the uplink capability in the TDD so that the UE only needs the reception capability and not the transmission capability.

The current solution is not to provide the MBMS service transmitted on the TDD spectrum in the FDD spectrum, and vice versa. This type of interaction does not currently exist within the Rel-6 network and potentially raises interoperability issues related to TDD dedicated UEs. Similar to the case of the hidden FDD frequency, such an issue can be solved by not sending SIB 13 in the TDD cells that do not support uplink operation. In this scenario, the MICH is broadcast within one frequency (e.g., the FDD frequency that the UE is camping for regular service), and the UE also starts the TDD receiver at the start of the session. desirable. One possibility would be to use a service indicating that the UE should start receiving TDD frequency, or use a specific extension for MCCH messages that can be used to signal that a given service is only available in the relevant TDD frequency / cell. .

In general, dual receiver UEs are dedicated services and MBMS point-to-point (PtP) / point-to-point (PtM) on one frequency (frequency A), as well as MBMS service transmitted on PtM bearers on a separate frequency (frequency B). You can receive the service at the same time. Examples that provide this are as follows.

Frequency A may be characterized as FDD or TDD (Dedicated Service and MBMS) and is the frequency at which the UE is camping for receiving the Dedicated Service. This frequency may include channels independent from MBMS, MICH independent from the MBMS service on frequency B, or MCCH, and MTCH (depending on MBMS service reception with the dual receiver possible).

Frequency B can be characterized as FDD or TDD (additional MBMS capability). The frequency may include BCCH, MICH independent of receipt of MBMS service or dedicated service on frequency A, or MCCH, and MTCH (depending on receiving MBMS service on frequency A with the dual receivers possible).

In embodiments of the present invention, dual receiver UEs are useful within different number of scenarios. For example, in an MBMS multicarrier Rel-6 network, Rel-6 frequency convergence and counting may be used for transmission of only one frequency. And, the Rel-7 rule for dual receiver UEs without network impact can be used to allow the UE to receive dedicated and MBMS services without limitation.

In another example, within an MBMS multicarrier Rel-6 network that includes optimization for Rel-7 dual receiver UEs, Rel-6 frequency convergence and counting may be used for transmission of only one frequency. And, Rel-7 rules for dual receiver UEs can be implemented without network impact, allowing unlimited reception of dedicated and MBMS services. And, the Rel-7 mechanism for dual receiver UEs can be used to allow for optimization of resources to receive dedicated and MBMS services without limitation.

In another example, within a Rel-6 network (single carrier or multicarrier) with separate independent MBMS downlink only frequency for Rel-7 dual receiver UEs (FDD / TDD). A mechanism for paging on the Rel-6 network may be used to activate the dual receiver for receiving MBMS services.

It is useful to define the behavior of a typical dual receiver UE in a Rel-6 MBMS network comprising two frequency layers. An example of this is shown in FIG. 13. In this scenario, the operator has deployed a multicarrier network with, for example, 5 MHz frequency or more. Counting, PtP setting, and frequency convergence will be described below.

Regarding counting, if counting is initiated, or if the RNC directs the service to transmit on a PtP bearer, the current solution is that the UE is camping on frequency B and the UE receiving MTCH and MCCH on individual frequency A acts ( behave) does not provide a way. Many solutions to these problems are possible and the present invention contemplates them.

For example, the UE may respond with an RRC request / URA update / cell update on the frequency it is camping on. This action assumes that the network is implemented such that the UE response is correlated with the signal transmitted on another cell / frequency.

Thus, it is beneficial for the network to control whether or not such functionality is allowed.

Another example includes a UE responding with an RRC request / URA update / cell update at the frequency that received the counting information, or indicating that the service is sent to a PtP bearer. This scenario requires the UE to perform cell reselection. Thus, it is useful to determine when to allow the UE to perform such cell reselection.

One technique for realizing this characteristic is frequency convergence (e.g., using an additional receiver if the conditions for frequency convergence are met, the UE performs an RRC request / URA updater / cell update on the frequency it receives). Is to reuse a specific offset for Another possibility is to add specific parameters via dedicated signaling or into MCCH to allow the cell reselection.

Another example relates to a situation where a UE does not respond to counting and PtP settings on a frequency where the UE is not camping, but the UE continues to receive the MTCH. This behavior is similar to the situation where the UE does not have dual receiver capabilities. Such a scenario usually does not cause any problem unless the network signals a specific indication for other operation, and thus can be considered the default behavior for dual receiver UEs.

Regarding PtP establishment, the current solution includes the UE initiating an RRC Connection Setup / Cell Update message to respond to a PtP bearer establishment request. In this scenario, there is no indication for the associated service so that the Rel-6 network generally does not expect a request for an MBMS PtP bearer for which it has not started establishing a PtP bearer. Thus, a dual receiver UE in such a situation will only respond to a PtP bearer setup indication on the corresponding uplink frequency where the PtP bearer setup is being indicated in the MCCH. In this regard, in response to the PtP bearer setup, the RCC connection request / cell update may be arranged such that the MCCH can only be performed on the corresponding uplink frequency transmitted in the downlink. That is, the UE may be implemented to respond only if it is camping on the uplink frequency corresponding to the MCCH to which the PtP setting indication has been transmitted.

Regarding frequency convergence, it does not properly address whether or not the dual receiver UE performs frequency convergence. In particular, such a solution does not take into account the possibility of supporting a separate receiver for MBMS, but only indicates that the UE is to listen to the MTCH / MCCH / MSCH of the frequency / cell it is camping on. Should be.

The dual receiver UE should stay on its chosen frequency if it can receive the preferred frequency through its dual receiver. This may be done by the dual receiver UE not applying frequency convergence as long as the UE can receive the subscribed service. Alternatively, the network can control whether the UEs use their additional receiver capabilities, or rather apply frequency convergence.

Currently, frequency convergence is done to allow UEs camping on a frequency on which the MBMS service is not broadcast to select a frequency on which the service is broadcast.

The dual receiver UE according to the embodiment of the present invention is not required to select the frequency of the MBMS service when the service is transmitted on the PtM bearer. However, it should be noted that the network may perform counting again or may switch to a PtP bearer at any time. In this case, the UE may respond with the same frequency as the frequency for receiving the indication. Thus, the UE may be configured to only reselect the preferred frequency where counting or PtP configuration is required to be performed.

Alternatively, the dual receiver UE may follow the Rel-6 requirement as if the UE does not have dual receiver capability including prioritization.

Another alternative is to not follow frequency convergence unless the UE cannot receive the predetermined service. In this case, the UE will perform frequency convergence in response to the counting or PtP configuration, or will not perform frequency convergence if it needs to respond to the counting or MBMS PtP configuration. Other actions are also possible in the case of counting and MBMS PtP bearer setup.

According to the Rel-6 rule, the UE will instruct the network if its preferred frequency is different from the frequency currently being used for the dedicated service. However, for a dual receiver UE, even if the preferred service is transmitted on a different frequency on the PtM bearer, it does not appear to be any significant issue for the dual receiver UE, indicating that the network is hoping for a frequency change. May have drawbacks. Thus, the UE can receive all the services it wants and should not use MBMS change fairy message under the situation that the predetermined service is transmitted on different frequency. As such, the dual receiver UE is not required to indicate to the network the preferred service / frequency or RBS to be terminated, as long as all the prioritized services are available by its dual receiver capability.

Operation of a dual receiver UE in accordance with an embodiment of the present invention is shown in FIG. 14.

In time interval '0', camping and MICH reception on frequency B of the UE are shown. Upon detecting the MICH, the UE starts reading the MCCH on frequency B and additionally receives frequency convergence information (time interval '1'). Since the UE may comprise a dual receiver, the UE may then activate the second receiver and start receiving the MCCH of frequency A (time interval '2'). The UE does not need to receive the MICH on frequency B, but can optionally resume receiving the MICH or MCCH on frequency B, if desired.

14 illustrates service transmission on the MTCH. In a situation where an MBMS service is started on the PtP bearer, the UE may perform frequency convergence in time intervals '3 and 4' and request a PtP bearer.

When the Rel-6 UE performs frequency convergence, it will generally follow the Rel-6 internal frequency cell selection rule. At present, there are no suitable solutions for how a dual receiver UE can receive the MBMS MTCH as much as possible using its dual receiver capabilities. However, in the present embodiment, the technique for doing this is to allow dual receiver UEs to follow the internal frequency cell reselection rule, and to read the BCCH on the frequency for MBMS reception.

Alternatively, the dual receiver UE may be implemented to select cells belonging to the network to which it has registered, or to select cells that provide MBMS service subscribed to by the UE. To ensure that these requirements are met, the UE may use, for example, a preferred frequency list in the cells it is camping on (if possible), or a neighboring cell list. Still other methods include the introduction of an MBMS specific neighbor cell or frequency list that includes cells or frequencies that are allowed to listen for dual receiver UEs.

In such a scenario, the dual receiver UE may receive the MBMS service to which it subscribes. However, in order to perform counting and PtP requests, the UE generally still needs to perform frequency convergence.

In order to optimize the control of dual receiver UEs, the MCCH can carry certain extensions that can only be read by UEs having specific capabilities (eg, dual receivers, FDD / TDD receivers, and others). Can be arranged. An example of this is shown in FIG. 15. This minimizes or eliminates the aforementioned drawbacks so that the UE can respond to counting / MBMS PtP setup on another frequency / cell when compared to the cell of the UE having information about counting.

In order to indicate permission to the UE, information is generally transmitted to the UE using, for example, the BCCH or MCCH. This may be implicit information such as frequency convergence information in the MBMS general information message. That is, if an adjacent frequency is indicated, the UE may then be allowed to respond to counting for any MCCH received within the given neighbor frequency. However, as shown in FIG. 16, this causes the UE to be camping in cell '6', for example, and respond to counting in cell '7'. This would not be overly useful because RNCII, not RNCI, controls cell '7'. Therefore, it would be beneficial to bring in explicit instructions.

For example, the explicit indication may be sent on frequency B, and within cell '5', which cells of frequency A may be allowed to transmit a Counting Response / MBMS PtP bearer request, or vice versa. can do. (E.g., for cells of frequency A, an indication of from which cells of frequency B a counting response can be transmitted), a cell on which the UE is camping and a cell on which the UE is reading the MCCH ( If cell from) is controlled by the same RNC, the RNC can only interpret the counting response / MBMS PtP bearer request.

If the UE is not instructed to respond to the counting / PtP setting indicated in the MCCH at frequency A (on the cell that the UE is camping on), within frequency B, the UE will still follow frequency convergence. There is a need. However, such scenarios are relatively rare, in which case the UE is allowed not to follow the counting and PtP settings.

In order to minimize the impact for counting the individual counting indicators, dual receiver UEs may be implemented similar to the method currently being performed for idle / connected mode access probability coefficients and counting ranges. That is, the dual receiver UE will transmit a response on a frequency different from the frequency on which the MCCH was transmitted, if it is instructed to allow transmission, and if a particular access probability coefficient / counting range is included. This method allows the MTCH to perform counting / PtP setup on other frequencies transmitted. (E.g., when MBMS MTCH is transmitted on frequency A, counting / PtP setting may be performed on frequency B for UEs with dual receiver capability, and counting / PtP setting for Rel-6 UEs is frequency May be performed only on A.) If such a mechanism is desired, the UE may be implemented to continue reading the MCCH on frequency B during the ongoing service so that it may respond to counting / PtP configuration.

To ensure that the RNC can link a counting response / PtP establishment request, the dual receiver UE responds to a message received on an MCCH transmitted on another cell when compared to the cell the UE is camping on. It is beneficial. The response may include additional information in a message sent to the network, such as an indication of a related service, the cell in which the MCCH was received, the frequency in which the MCCH was received, and the like. have.

In general, a dual receiver UE for UMTS can, for example, efficiently receive MBMS services and dedicated services simultaneously. However, within Rel-6, the network generally does not have information about the UE restriction, or the extra freedom that the UE has for receiving MBMS service. If the UE can receive the MTCH on a different frequency than the dedicated service, it is advantageous to inform the network of this capability (e.g., when establishing an RRC connection or in any other case).

An additional feature to facilitate dual receiver operation is to link the MBMS cell with the cell the UE is camping on. This feature will be described with reference to FIG. 17. According to this feature, consider the situation where the UE is camping on a cell of frequency B. In this case, an indication is given to distinguish which cell or set of cells in frequency A is arranged side by side with cells of frequency B. Therefore, this limits the number of cells that the UE should select for receiving MBMS service.

In FIG. 17, if the UE is camping on cell '5' and it is on frequency B, pointing the UE to cells '1, 2' indicates that these cells have the same coverage. It is beneficial because it has. This reduces the complexity of the dual receiver UE and allows the dual receiver UE to reduce information regarding cell reselection that needs to be transmitted on the MBMS frequency. This is particularly useful when the frequency is used as the MBMS dedicated frequency.

In detailed operation, portions of the configuration (e.g., MCCH, MTCH, MSCH, and radio bearer configuration of cells and services in frequency A) may receive only MTCH / MSCH, not BCCH / MCCH, on frequency A. In order to be necessary, it may be desirable to broadcast on frequency B.

In the present scenario, in general, the dual receiver UE can always receive the MBMS service to which it has subscribed, without any impact from the MBMS service. Thus, since such a UE does not need to follow frequency convergence, there is no more impact on the UE in the case of simultaneous reception of dedicated and MBMS data.

As mentioned above, in general, dual receiver UEs do not need to transmit on frequency A, which is, for example, the frequency at which the MBMS service is transmitted. However, it is envisioned that Rel-6 UEs can camp on this frequency because of the defect capability conditions that can be presented. Thus, the UE can connect to the network. Therefore, the network may be equipped with a transmitter and a receiver under such a situation.

It has been established that there is a possibility that a dual receiver UE can camp on a frequency different from the frequency on which it received the MBMS service. This means that the UE can respond to counting on the frequency it is camping on, rather than the frequency where the service is to be broadcast. This makes it possible to introduce frequencies that are shown to Rel-7 UEs and are generally reserved for MBMS traffic. This allows the use of a dedicated band for MBMS where only the downlink may be required. In other words, there is no need for receivers in the present base stations. It also has the advantage of no impact on ongoing dedicated services.

Downlink only MBMS carriers may be implemented in base stations that do not have a receiver device. In order to prevent Rel-6 UEs from reselecting downlink dedicated MBMS service, for example, related SIBs may be used by the operator, or other techniques to prevent Rel-6 and previous UEs from selecting the carrier. It is useful not to be sent on the carrier to be blocked. In addition, specific indications may be implemented to enable Rel-7 dual receiver UEs to recognize cells within the present frequency as cells providing regular MBMS service.

In order to allow Rel-7 dual receiver MBMS UEs to select the carriers, a specific indication in the Rel-7 extension on BCCH or MCCH (eg, Rel-7 MBMS inter-frequency dual receiver cell information list Is useful. If desired, inter-frequency FDD and / or TDD cells may also be added.

The various embodiments presented herein provide important advantages for network operation. For example, the operators only need to deploy the necessary components for the MBMS, which allows a low cost for the deployment of the MBMS. Under circumstances where TDD is used, an asymmetric spectrum for MBMS may also be deployed.

UEs without dual receivers may receive MBMS service on an MBMS downlink dedicated spectrum (eg, as soon as the UE receives paging messages on the MBMS downlink dedicated frequency, or the UE would like to initiate a call). When moving to the frequency), there may be limitations in terms of counting and PtP settings.

More detailed benefits include counting at a frequency other than the frequency at which the MTCH was received and / or allowing PtP configuration, indication of cells of similar coverage, use of configuration information of MBMS channels in adjacent cells, and the network. A dual receiver capability indication of the UE.

Other benefits are provisions that prevent or prevent Rel-6 UEs from attempting to camp on MBMS downlink dedicated frequencies, an indication that the MBMS service is broadcast on a hidden frequency, and within normal frequencies used for the dedicated service. MBMS downlink dedicated frequency indication.

19 is a flowchart illustrating a communication method between a network and a dual receiver UE according to an embodiment of the present invention. Block 105 provides for receiving a first signal from a first network node at a first frequency. In addition, at block 110, two signals are received over a point-to-multiple (PtM) control channel from two network notes at two frequencies. Block 115 provides for receiving a request from the two network nodes at the two frequencies, the request being carried on the PtM control channel. Another operation includes sending a response to the request from the second network node to the first network node (block 120).

20 is a flowchart describing a communication method between a network and a dual receiver UE according to another embodiment of the present invention. Block 130 provides for receiving communication from the primary network node, and block 135 provides for identifying that the primary network node lacks uplink capability. One operation requires confirming that the first network node provides MBMS service (block 140). Another operation includes receiving the MBMS service from the primary network node despite confirmation of the lack of uplink capability (block 145).

In general, a single frequency network (SFN) region contains a collection of cells that transmit exactly the same frequency and content. Such a group of cells may be called an SFN cell cluster. From a UE point of view, in more detail, from a receiver point of view within the UE, the SFN cell cluster may be considered as a single cell.

In a single frequency network, there may be different SFN regions that transmit different frequencies and have different sizes.

FIG. 21 illustrates a unicast network including two single frequency network regions (SFN cell clusters), and other cells covering the same geographical area, according to an embodiment of the present invention. Referring to FIG. 21, the two SFN cell clusters operate at the frequencies A and B, respectively, and the single transmission network operates at the frequency C. Preferably, in order to operate the UE efficiently, each cell in the single transmission network refers to the presence of frequencies A and B. Thus, only when the single transmission network indicates the presence of available SFN frequencies in the same geographical area, the UE can power up its receiver.

In addition, the SFN cell cluster instructs the UE not only the service provided in another SFN cell cluster operating on different frequencies within the same coverage area, but also the service provided in the SFN cell cluster.

Accordingly, the UE only needs to receive information of one SFN cell cluster so that it can know all services provided in other SFN cell clusters within the same coverage area. In the UE's benefit, battery consumption is greatly reduced by the methods described above, so the UE can freely select any of the frequencies operating in SFN mode to monitor available services.

The problem arises when the SFN cell clusters operating on different frequencies are severely changed within coverage. For example, one SFN cell cluster may provide service coverage throughout the country and operate on one frequency, while many other SFN cell clusters operate on different frequencies and provide local services. Therefore, since the SFN cell cluster covering the entire country must transmit the same content everywhere, the SFN cell cluster covering the whole country indicates all services available within the frequencies providing local services. It is difficult to indicate. Moreover, if there are different services within each SFN cluster that provide only regional coverage, and if there are many regional SFN regions, then all the information related to the services available within the regional SFN clusters is returned to the national SFN cluster. It is difficult to instruct Thus, whether the UE should regularly check for availability of services on frequency, or the UE may depend on the fact that the availability of the services is indicated in the cluster where the UE is camping. It is desirable to provide a means to indicate whether or not there is.

22 illustrates three frequencies used to provide multi-cell multicast broadcast single frequency network (MBSFN) services according to an embodiment of the present invention. As mentioned above, it is difficult for an SFN cluster with a larger coverage area to indicate which services are available on the SFN cluster with a smaller coverage area. Therefore, a UE receiving the SFN cluster with the larger coverage area is regularly tuned to other available frequencies to monitor which services are available.

According to the invention, it is desirable to provide the UE with information for determining whether the presence of services provided on other frequencies is indicated on the frequency that the UE receives. Upon receiving the information, the UE only receives one frequency to be notified of whether it should periodically check for the availability of a service on other frequencies, and the availability of all services offered on the other frequency. It can be determined whether or not it is enough.

In the present invention, if there are several additional frequencies that provide services informing that the available services are not indicated on the frequency that the UE is currently listening to, any of the frequencies is any It is advantageous to provide information as to whether to provide information about the services available on the frequency. For example, referring to FIG. 22, frequency A indicates that there are other frequencies B, C providing services. . However, the services available on frequencies B and C are not informed on the frequency A. Thus, a UE receiving frequency A must receive frequencies B, C regularly to assure knowledge of the services it wants to receive.

In addition, on frequency A, it can be informed that frequency C refers to all services available on frequencies B, A. Moreover, it can be informed on frequency A that frequency B provides information about the services provided on frequency A, but does not provide information about the services provided on frequency C. Thus, the UE receiving the information prefers to receive the frequency C to ensure that it knows all available services.

In the UMTS MBMS system on the MCCH, it is possible to indicate the frequencies for providing MBMS services in the 'MBMS general information' message. This process is used to indicate adjacent frequencies that provide services. However, more information is needed to indicate whether the services provided on other frequencies also appeared on the frequency at which the messages were sent.

Within the UMTS single transmission behavior, associated with each MBMS preferred frequency layer is an offset value and an indication of whether hierarchical cell structures are used. In order to allow the UE to know whether information on available services for a given frequency is provided, any of the offset value or the indication is reused, so that 1) the availability of services on other frequencies is currently Appear on a frequency, in which case the UE does not need to regularly read other frequencies for available services; Or 2) the availability of services on other frequencies does not appear on the current frequency, in which case the UE needs to receive other frequencies regularly so that it can know about the available services on other frequencies; Indicates.

If the availability of services on other frequencies does not appear on the current frequency, information about each frequency indicating whether or not the other available frequencies need only provide information already contained in the information provided on the particular frequency It is preferable to provide. Thus, the UE can directly identify a set of frequencies that provide only information that is not available on other frequencies.

Preferably, the information may be indicated by priority. For example, if two frequencies appear with the same priority, this means that each of the two frequencies contains information that is not necessarily included in other frequencies of the same priority. In addition, frequencies indicated at higher priority include all information related to frequencies notified at lower priority.

Referring to FIG. 22, cluster I represents frequency B with priority '1' and may provide an indication that services available on frequency B do not appear on frequency A. Moreover, cluster I represents frequency C with priority '2' and may provide notification that services available on frequency C do not appear on frequency A. Thus, the UE will know how to additionally receive the frequency C in order to know all available services. Preferably, the UE receiving the frequency C periodically receives the frequency C, in addition to the frequency A. Alternatively, once the frequency C is received, the UE can only choose to receive the frequency C because the UE knows that all available services appear on the frequency C.

Referring again to FIG. 22, cluster IV may indicate that the availability of frequencies A, B appears on frequency C. FIG. In addition, the cluster IV may indicate that services available on frequencies A and B appear on frequency C.

Therefore, the UE receiving the cluster IV preferably monitors only the frequency C.

Referring back to FIG. 22, cluster II may indicate that services available on frequency A appear on frequency B. FIG. However, services available on frequency C do not appear on frequency B. Therefore, the UE receiving the cluster II preferably receives the frequency C in addition to the frequency B. Alternatively, once the frequency C is received, the UE can only choose to receive the frequency C because the UE knows that all available services appear on the frequency C.

In another aspect of the present invention, a flag per frequency may indicate the received frequencies in order to know all available services.

Referring to FIG. 22, cluster I may indicate frequency B with a notification that services available on frequency B do not appear on frequency A. FIG. In addition, cluster I may indicate frequency C with an indication that the services available on frequency C do not appear on frequency A, and that the frequency C is the only frequency that needs to be received to know all available services. have. Thus, the UE can know how to additionally receive the frequency C to know all available frequencies. Preferably, the UE receiving the cluster I receives the frequency C periodically, in addition to the frequency A. Alternatively, since the UE knows that all available services appear on the frequency C, the UE can only choose to receive the frequency C.

Referring again to FIG. 22, cluster IV may indicate that the availability of frequencies A, B appears on frequency C. FIG. In addition, the cluster IV may indicate that services available on frequencies A and B appear on frequency C.

Therefore, the UE receiving the cluster IV preferably monitors only the frequency C.

Referring back to FIG. 22, cluster II may indicate that services available on frequency A appear on frequency B. FIG. In addition, the cluster II may indicate that services available on frequency C do not appear on frequency B, and may indicate a flag that frequency C is the only frequency that needs to be received to know all available services. . Preferably, the UE receiving the cluster II receives the frequency C periodically, in addition to the frequency B.

Alternatively, since the UE knows that all available services appear on the frequency C, the UE can only choose to receive the frequency C.

23 is a block diagram of a mobile station (MS) or UE1 in accordance with the present invention. The UE1 includes a processor (or digital signal processor) 210, an RF module 235, a power management module 205, an antenna 240, a battery 255, a display 215, a keypad 220, a memory 230, a speaker 245, and a microphone 250.

The user enters instructional information, such as a phone number, for example, by pressing buttons on the keypad 220 or by voice activation using the microphone 250. The microprocessor 210 receives and processes the directive information to perform appropriate functions such as telephone number dialing. Operational data may be retrieved from the memory module 230 to perform the function. In addition, the processor 210 may display the directive information and operation information on the display 215 for the user's reference and convenience.

The processor 210 issues directive information to the RF module 235 to initiate communication such as, for example, transmitting wireless signals comprising voice communication data. The RF module 235 includes a receiver and a transmitter for receiving and transmitting wireless signals. Antenna 240 facilitates the transmission and reception of wireless signals. Upon receiving wireless signals, the RF module 235 forwards and converts the signals to a baseband frequency for processing by the processor 210. The processed signals are transformed into, for example, audible and readable information output through the speaker 245. The processor 210 also includes protocols and functions necessary to perform the various processes described herein.

It will be apparent to those skilled in the art that the mobile station 1 may be easily implemented, alone or in combination with external support logic, for example, using the processor 210, or other data, or digital processing device. Although the present invention is described in the context of mobile communication, the present invention may also be used in any wireless communication systems using mobile devices such as PDAs or laptop computers with wireless communication capabilities.

In addition, the use of specific terms describing the invention should not limit the scope of the invention to any form of wireless communication system such as UMTS. The invention is also applicable to other wireless communication systems that use other air interfaces such as TDMA, CDMA, FDMA, WCDMA, and others.

The embodiments may be implemented as a method, apparatus, or article of manufacture, using standard programming and / or engineering techniques to produce software, firmware, hardware, or any combination thereof. Can be.

As used herein, the term 'manufacturing item' refers to hardware logic (eg, integrated circuit chip, field programmable gate array (FPGA), application specific integrated circuit (ASIC), or the like), or computer readable medium. (Eg, magnetic storage media (eg, hard disk drives, floppy disks, tapes, etc.), optical storage (CD-ROMs, optical disks, etc.), volatile and nonvolatile memory devices (eg, Code or logic implemented within EEPROMs, ROMs, PROMs, RAMs, DRAMs, SPRAMs, firmware, programmable logic, etc. Code in computer readable media is accessed and executed by a processor.

The code in which the preferred embodiments are implemented may be more accessible through the transmission media or from a file server on the network. In this case, the manufacturing item in which the code is implemented may include transmission media such as network transmission line, wireless transmission media, signals propagating through space, radio waves, infrared signals. Of course, those skilled in the art will recognize that many changes can be made in this configuration without departing from the scope of the present invention and that the article of manufacture may include any information bearing medium known in the art.

The logic implementation shown in this figure has been described as certain actions occurring in a particular order. In other implementations, certain logical operations may be performed in a different order, modified or removed, and still implement preferred embodiments of the present invention. Moreover, steps can be added to the logic described above, which can still be consistent with implementations of the invention.

The above embodiments and advantages are merely illustrative and should not be construed as limiting the invention. The present invention is applicable to other kinds of apparatus and processes. The description of the invention is for the purpose of description and is not intended to limit the scope of the claims. Various alternatives, modifications and variations will be apparent to those skilled in the art. In the claims, the means plus function clauses are intended to carry out the structure described herein, as well as the equivalent structure and function and structural equivalents recited above.

Claims (21)

Receiving information on a first frequency (frequency A), wherein the information is multicast broadcast single frequency networks (MBSFN) transmission frequencies (frequency B) that do not have an associated uplink service. Is information associated with a frequency list indicating available MBSFN transmission frequencies; Selectively receiving a service at transmission frequencies not having an associated uplink service among the MBSFN frequencies indicated by the frequency list of the received information; The service is received in a multicast broadcast single frequency network (MBSFN), where the MBSFN has at least one single frequency network (SFN) area with a series of cells, the series of cells being the same frequency A method of communication between a network and a user equipment (UE) using a multicast broadcast single frequency network, characterized in that the series of cells operates as a single cell to a specific user equipment (UE) by transmitting content. 2. The network of claim 1, wherein the information includes all MBSFN transmission frequencies that provide point-to-multiple services and do not have an associated uplink service. Communication method. 2. A method according to claim 1, wherein said first frequency has associated uplink and downlink services. The method of claim 1, further comprising: monitoring at least one service provided on the transmission frequency; Selecting an available service; And receiving the intermittent service. The communication method between a network and a user equipment (UE) using a multicast broadcast single frequency network, further comprising. The method of claim 1, wherein the information is Method for communication between a network and a user equipment (UE) using a multicast broadcast single frequency network, characterized in that it is information indicating that there is no MBSFN transmission frequency without an associated uplink service. The method of claim 1, wherein the transmission frequencies A method of communication between a network and a user equipment (UE) using a multicast broadcast single frequency network, which does not have an associated uplink service and provides point-to-multiple services. At least one antenna connected to a radio frequency (RF) module; A processor for controlling a user equipment (UE); The processor is Receive, from a multicast broadcast single frequency networks (MBSFN), a frequency list indicating available MBSFN transmission frequencies to use for receiving MBMS service; As indicated by the frequency list, determine whether all frequencies for cells operating in a single frequency network (SFN) mode are based on available MBSFN frequencies to use for receiving MBMS service; A user device in communication with a multicast broadcast single frequency network (MBSFN), characterized in that selectively receiving MBMS services from frequencies for cells determined to operate in SFN mode. The method of claim 7, wherein the MBMS service is Received over a single frequency network (SFN) cell cluster, The SFN cell cluster is a series of cells that transmit the same frequency and the same content, wherein the cells are part of the same geographic area, wherein the user equipment communicates with a multicast broadcast single frequency network (MBSFN). Transmitting information on a first frequency (frequency A), wherein the information is multicast broadcast single frequency networks (MBSFN) that do not have an associated uplink service (frequency B) Is information associated with a frequency list indicating available MBSFN transmission frequencies; The service is provided from a multicast broadcast single frequency network (MBSFN), where the MBSFN has at least one single frequency network (SFN) area having a set of cells, A method of communication between a network and a user equipment (UE) using a multicast broadcast single frequency network, wherein the series of cells operate as a single cell by transmitting cells of the same frequency and the same content. 10. The method of claim 9, wherein the information is A multicast broadcast single frequency network, instructing the user device to receive service at a transmission frequency that does not have an associated uplink service, among all MBSFN transmission frequencies that provide point-to-many service and do not have an associated uplink service. Communication method between the network and the user equipment (UE) using. The method of claim 9, wherein the information is A method of communication between a network and a user equipment (UE) using a multicast broadcast single frequency network comprising all MBSFN transmission frequencies that provide point-to-many service and do not have an associated uplink service. The method of claim 9, wherein the information is A method of communication between a network and a user equipment (UE) using a multicast broadcast single frequency network characterized by having associated uplink and downlink services. The method of claim 9, wherein the information is A communication method between a network and a user equipment (UE) using a multicast broadcast single frequency network, characterized in that there are no MBSFN transmission frequencies that do not have an associated uplink service. The method of claim 13, wherein the information is And instructing the user device not to search for MBSFN transmission frequencies that do not have an associated uplink service. 10. The method of claim 9, At least one of the MBSFN transmission frequencies without associated uplink service provides point-to-multiple services, wherein the network and user equipment (UE) using a multicast broadcast single frequency network. delete delete delete delete delete delete

Images