WO2014179960A1

WO2014179960A1 - Method and device for network configuration

Info

Publication number: WO2014179960A1
Application number: PCT/CN2013/075389
Authority: WO
Inventors: 王可
Original assignee: 华为技术有限公司
Priority date: 2013-05-09
Filing date: 2013-05-09
Publication date: 2014-11-13
Also published as: CN104350771A

Abstract

The embodiments of the present invention provide a method and device for network configuration. The method comprises: a base station establishing a first public bearer, wherein the first public bearer is located between the base station and a machine type communication (MTC) relay, and the first public bearer is used for transmitting data of multiple terminals; the base station performing cascaded connection on the first public bearer and a second public bearer, wherein uplink and downlink transmission is performed on the data of the multiple terminals connected to the MTC relay through the first public bearer and the second public bearer, the second public bearer is located between the base station and a core network of the base station, and the second public bearer is used for transmitting the data of the multiple terminals. In the embodiments of the present invention, by way of performing cascaded connection on the public bearer of the MTC relay and the public bearer of the base station, the bearer of an air interface can be gathered, and the processing overheads of the base station can be reduced.

Description

Method and device for network configuration

The present invention relates to the field of communications, and more particularly to a method and apparatus for network configuration. Background technique

The Internet of Things realizes intelligent identification and management by connecting items to the Internet through information sensing devices, which means that a large number of small devices can access the cellular network wirelessly to realize inter-machine communication (Machine-To-Machine) , M2M). In the embodiment of the present invention, Machine-To-Machine (M2M) and Machine Type Communication (MTC) can be regarded as equivalent concepts.

According to the current standard definition, the information sensing devices used in the Internet of Things include radio frequency identification devices, infrared sensors, global positioning systems, laser scanners and the like. They are combined with the Internet to enable remote sensing and control of all items.

According to the current Third Generation Partnership Project (3 ^rd Generation Partnership Project,

The definition of 3GPP is that the transmission of the user equipment (UE, User Equipment) is implemented based on the Evolved Packet System (EPS) bearer. Each EPS bearer includes an air radio bearer (Data Radio Bearer, DRB). And the GTP (GPRS Tunnel Protocol) tunnel of the core network. Since the number of M2M devices may be very large, these large numbers of bearers may have a considerable impact on the radio access network (RAN) side and the core network entity.

In response to this problem, the concept of base station common bearer is proposed. After the common bearer of the base station is introduced, the part of the dedicated bearer other than the MTC UE can be canceled, and the service flow of the UE is directly mapped to the public bearer for transmission, thereby reducing the impact on the core network.

However, in this case, a large number of MTC UE bearers still exist on the air interface of the base station. MTC

The UE may include a device that accesses the cellular network in a wireless manner to implement M2M communication or MTC communication. MTC UE bearer refers to the bearer used to transmit the MTC UE. Moreover, since it is necessary to ensure coverage of these MTC UEs, it is also necessary to consume a considerable transmission power of the base station and the MTC UE. In the Medium Relay architecture of 3GPP R10, although the relay station can aggregate the bearers of the UE through the relay link, the bearer (GTP tunnel) of the logical UE is still separately established on the relay link, so for the base station , still can see the bearer of each UE, the processing overhead has not been reduced. Summary of the invention

Embodiments of the present invention provide a method and apparatus for network configuration, which can reduce processing overhead of a base station. In a first aspect, a method for network configuration is provided, the method comprising: a base station establishing a first common bearer, the first common bearer being located between the base station and a machine type communication MTC relay, the first common bearer being used for transmitting Data of the plurality of terminals; the base station cascading the first common bearer and the second common bearer, wherein data of the multiple terminals connected to the MTC relay is performed by using the first common bearer and the second common bearer Up and down transmission, the second common bearer is located between the base station and the core network of the base station, and the second common bearer is used for transmitting data of multiple terminals.

With reference to the first aspect, in a first possible implementation manner, the first common bearer that the base station establishes the MTC relay is implemented by: the base station receiving the first common bearer setup request sent by the mobility management entity MME, where the first common bearer The establishing request is used to request to establish the first public bearer, where the first common bearer setup request carries the bearer type indication information of the first common bearer; and the base station establishes the first common bearer according to the first common bearer setup request.

With reference to the first possible implementation manner of the first aspect, in a second possible implementation, the specific implementation is: the first common bearer setup request is generated by the MME according to the create bearer request message initiated by the MTC relay Or the first public bearer setup request is generated by the MME according to the create bearer request message initiated by the packet data gateway PGW that manages the MTC relay; wherein the create bearer request message is used to indicate that the first public bearer is created.

With reference to the second possible implementation of the first aspect, in a third possible implementation, the specific implementation is: The PGW is a gateway integrated by the base station.

With reference to the first possible implementation manner of the first aspect, in a fourth possible implementation, the establishing, by the base station, the first common bearer is further implemented by: the base station sending a connection reconfiguration request message to the MTC relay, where the connection is The reconfiguration request message carries the bearer type indication information of the first common bearer, and the connection reconfiguration request message is used by the MTC relay to complete the configuration of the first public carrier on the MTC relay side, where the The bearer type of the first public carrier is determined by the MTC relay.

With reference to the second possible implementation of the first aspect, the possible implementation manner of the fourth possible implementation manner, in a fifth possible implementation manner, the method further includes: establishing a first After the public bearer, the base station sends the identifier information of the first common bearer to the MTC relay. In combination with the second possible implementation manner of the first aspect, the possible implementation manner of the fifth possible implementation manner, in the sixth possible implementation manner, the specific implementation is: the first common bearer setup request And carrying the first bearer information of the first common bearer; or the first common bearer setup request further carrying the first bearer information and the second bearer information; wherein the first bearer information includes at least one of the following: a subsequent address, an identifier of the MTC relay, and an identifier of the first public bearer, where the identifier of the MTC relay is a device identifier or a cell identifier of the MTC relay; the second bearer information is different from the first Bearer information carrying information, the second bearer information is used to establish a gateway of the base station to the core network.

With reference to the first aspect, or the first possible implementation of the first aspect, to any one of the possible implementations of the sixth possible implementation of the first aspect, in a seventh possible implementation, the base station The cascading of the first common bearer and the second common bearer is implemented as follows: the base station implements the first common bearer and the second common bearer by configuring bearer mapping criteria between the first common bearer and the second common bearer The cascading, the bearer mapping criterion is used to enable data of multiple terminals of the MTC relay to perform uplink and downlink transmissions through the first common bearer and the second common bearer.

In conjunction with the seventh possible implementation of the first aspect, in an eighth possible implementation manner, the eNB cascading the first common bearer and the second common bearer is implemented by: the base station according to the acquired first public And transmitting the associated information to the PGW of the second public bearer, where the association information includes an address of the MTC relay and/or an identifier of the first public bearer; and the base station receives the first bearer mapping sent by the PGW. The criterion indication information, the first bearer mapping criterion indication information is used to notify the base station to add or update the bearer mapping criterion; the base station adds or updates the bearer mapping criterion according to the first bearer mapping criterion indication information.

With reference to the seventh possible implementation manner of the first aspect, or the eighth possible implementation manner of the first aspect, in a ninth possible implementation manner, the method further includes: the base station receiving the MTC The cascading indication information is cancelled; the base station deletes the bearer mapping criterion according to the cancel cascading indication information to cancel the cascading of the first common bearer and the second common bearer.

In a second aspect, a data transmission method is proposed, the method comprising: a machine type communication MTC relay transmitting data of a plurality of terminals connected to the MTC relay to a base station by using a first common bearer, wherein the first common bearer Located between the MTC trunk and the base station, the first common bearer is configured to cascade data with the second public bearer to enable data of the multiple terminals under the MTC relay to pass the first public bearer and the second public The bearer performs uplink and downlink transmission, and the second common bearer is located between the base station and the core network of the base station. With reference to the second aspect, in a first possible implementation manner, the method further includes: before the MTC relay sends data of the multiple terminals connected to the MTC relay to the base station by using the first common bearer, in the MTC A common bearer setup request is sent to the base station, and the common bearer setup request is used to create the first public bearer.

With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner, the method further includes: sending, by the first public bearer, the multiple connection to the MTC relay to the base station by using the first common bearer Before the data of the terminal is sent by the MTC relay to the base station, the MTC relay receives the identifier information of the first public bearer sent by the base station, where the identifier information of the first common bearer is used in the MTC. The configuration of the first common bearer on the relay side is performed.

With reference to the first possible implementation manner of the second aspect or the first possible implementation manner of the second aspect, the third possible implementation manner is implemented as follows: the common bearer setup request carries bearer type indication information, where The bearer type indication information is used to indicate the bearer type of the first public bearer.

In a third aspect, a common bearer mapping method is proposed, where the method includes: the service capability server receives the attachment information of the user equipment UE sent by the mobility management entity MME, where the attachment information includes address information of the site to which the UE is attached, and the site includes An MTC relay; the service capability server updates destination station information in a common header of the data packet of the UE according to the attachment information, where the packet data gateway managing the MTC relay determines, according to the destination station, the data packet of the UE a data transmission route between the common bearer and the second common bearer, the first common bearer being located between the base station and the MTC relay, the second common bearer being located at the base station and the core network, the first common bearer and the second common bearer Cascading transmission of data.

With reference to the third aspect, in a first possible implementation, the method further includes: the service capability server sending update confirmation information to the MME, where the update confirmation information indicates that the address of the site to which the UE is attached is updated successfully.

With reference to the third aspect or the first possible implementation manner of the third aspect, in a second possible implementation manner, the specific implementation is: the attachment information of the UE is forwarded by the MME through the MTC-IWF.

In a fourth aspect, a base station is provided, where the base station includes: a bearer establishing unit, configured to establish a first common bearer, where the first common bearer is located between the base station and a machine type communication MTC relay, where the first common bearer is used And a cascading unit, configured to cascade the first common bearer and the second common bearer, where the data connected to the multiple terminals of the MTC relay And performing uplink and downlink transmission by using the first common bearer and the second common bearer, where the second common bearer is located between the base station and a core network of the base station, where the second common bearer is used for transmitting data of multiple terminals.

With reference to the fourth aspect, in a first possible implementation, the base station further includes: a receiving unit, configured to receive a first common bearer setup request sent by the mobility management entity MME, where the first common bearer setup request is used to request to establish The first common bearer, the first common bearer setup request carries the bearer type indication information of the first common bearer; the bearer establishing unit is specifically configured to establish the first public according to the first common bearer setup request received by the receiving unit Hosted.

With reference to the first possible implementation manner of the fourth aspect, in a second possible implementation manner, the specific implementation is: the first common bearer setup request is generated by the MME according to the create bearer request message initiated by the MTC relay Or the first public bearer setup request is generated by the MME according to the create bearer request message initiated by the packet data gateway PGW that manages the MTC relay; wherein the create bearer request message is used to indicate that the first public bearer is created.

With reference to the second possible implementation manner of the fourth aspect, in a third possible implementation manner, the specific implementation is: the PGW is a gateway integrated by the base station.

With the second possible implementation of the fourth aspect or the second possible implementation of the fourth aspect, in a fourth possible implementation, the base station further includes: a sending unit, configured to be in the first public After the bearer is established, the identifier information of the first public bearer is sent to the MTC relay.

With reference to the second possible implementation manner of the fourth aspect, the possible implementation manner of the fourth possible implementation manner, in the fifth possible implementation manner, the specific implementation is: the first common bearer setup request And carrying the first bearer information of the first common bearer; or the first common bearer setup request further carrying the first bearer information and the second bearer information; wherein the first bearer information includes at least one of the following: a subsequent address, an identifier of the MTC relay, and an identifier of the first public bearer, where the identifier of the MTC relay is a device identifier or a cell identifier of the MTC relay; the second bearer information is different from the first Bearer information carrying information, the second bearer information is used to establish a gateway of the base station to the core network.

With reference to the first possible implementation manner of the fourth aspect, in a sixth possible implementation, the specific implementation is: the base station further includes: a sending unit, configured to send a connection reconfiguration request message to the MTC relay, where the connection is The reconfiguration request message carries the bearer type indication information of the first common bearer, and the connection reconfiguration request message is used by the MTC relay to complete the configuration of the first public bearer on the MTC relay side, where the Determining the first public load at the MTC relay The type of bearer.

With reference to the fourth aspect, in a seventh possible implementation, the specific implementation is: the cascading unit implements the first common bearer by configuring a bearer mapping criterion between the first common bearer and the second common bearer The cascading of the second common bearer, the bearer mapping criterion is used to enable data of multiple terminals of the MTC relay to perform uplink and downlink transmissions through the first common bearer and the second common bearer.

With reference to the seventh possible implementation of the fourth aspect, in an eighth possible implementation, the specific implementation is as follows: The base station further includes a sending unit and a receiving unit. a sending unit, configured to send, according to the acquired association information of the first public bearer, a common bearer update request to the PGW of the second public bearer, where the association information includes an address of the MTC relay and/or an identifier of the first public bearer; a receiving unit, configured to receive first bearer mapping criterion indication information that is sent by the PGW, where the first bearer mapping criterion indication information is used to notify the base station to add or update the bearer mapping criterion; the cascading unit is specifically configured to use the first The bearer mapping criteria indicates that the information is added or updated with the bearer mapping criteria.

With reference to the seventh possible implementation manner of the fourth aspect, or the eighth possible implementation manner of the fourth aspect, in a ninth possible implementation manner, the receiving unit is further configured to: receive the MTC relay The cascading indication information is deleted; the cascading unit is further configured to delete the bearer mapping criterion according to the cancel cascading indication information to cancel the cascading of the first common bearer and the second common bearer.

In a fifth aspect, a relay is provided, where the relay includes: a sending unit, configured to send a first public bearer setup request to the base station, where the first common bearer setup request is used to establish a first public bearer, where the first public The bearer is located between the relay and the base station, and the first common bearer is configured to be cascaded with the second common bearer, so that data of the multiple terminals under the relay passes the first common bearer and the second common bearer. Performing uplink and downlink transmission, the second common bearer is located between the base station and a core network of the base station.

With reference to the fifth aspect, in a first possible implementation, the specific implementation is: the relay further includes: a receiving unit, configured to receive, by the base station, identifier information of the first public bearer, so that the relay performs the The first common bearer is configured on the relay side.

With reference to the fifth aspect or the first possible implementation manner of the fifth aspect, in a second possible implementation, the specific implementation is: the first common bearer setup request carries bearer type indication information, where the bearer type indication information is used Indicates the bearer type of the first public bearer.

In a sixth aspect, a service capability server is provided, where the service capability server includes: a receiving unit, configured to receive an attachment information of a user equipment UE sent by a mobility management entity MME, where The information includes the address information of the site to which the UE is attached, the site includes the MTC relay, and the processing unit is configured to update the destination site address information in the common header of the data packet of the UE according to the attachment information, where the MTC is managed. The subsequent packet data gateway determines, according to the destination site address information, a data transmission route of the data packet of the UE in the first common bearer and the second common bearer, where the first common bearer is located between the base station and the MTC relay, the first The two common bearers are located at the base station and the core network, and the first common bearer and the second common bearer are cascaded to transmit data.

With reference to the sixth aspect, in a first possible implementation, the specific implementation is as follows: the service capability server further includes: a sending unit, configured to send, to the MME, update acknowledgement information, where the update acknowledgement information indicates an address of a site to which the UE is attached update completed.

With reference to the sixth aspect or the first possible implementation manner of the sixth aspect, in a second possible implementation manner, the specific implementation is: the attachment information of the UE is forwarded by the MME through the MTC-IWF. DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings to be used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only the present invention. For some embodiments, other drawings may be obtained from those of ordinary skill in the art without departing from the drawings.

FIG. 1 is a schematic structural diagram of a network configuration according to an embodiment of the present invention.

2 is a configuration method of a common bearer according to an embodiment of the present invention;

FIG. 3 is a flow chart of interaction of establishing a common bearer according to an embodiment of the present invention.

4 is a flow chart of the cascading interaction of the embodiment of the present invention.

FIG. 5 is a flow chart of the interaction of canceling cascading according to an embodiment of the present invention.

FIG. 6 is a flowchart of a method for creating a common bearer according to an embodiment of the present invention.

FIG. 7 is a flowchart of a common bearer mapping method according to an embodiment of the present invention.

FIG. 8 is a flow chart of interaction of data packet common header processing according to an embodiment of the present invention.

FIG. 9 is a schematic structural diagram of a base station according to an embodiment of the present invention.

FIG. 10 is a schematic structural diagram of a relay according to an embodiment of the present invention.

FIG. 11 is a schematic structural diagram of a service capability server according to an embodiment of the present invention.

FIG. 12 is a schematic structural diagram of another base station according to an embodiment of the present invention.

FIG. 13 is a schematic structural diagram of another relay according to an embodiment of the present invention.

FIG. 14 is a schematic structural diagram of another service capability server according to an embodiment of the present invention. detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without making creative labor are within the scope of the present invention.

The technical solution of the present invention can be applied to various communication systems, such as: Global System of Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access ( WCDMA, Wideband Code Division Multiple Access Wireless), General Packet Radio Service (GPRS), Long Term Evolution (LTE), etc.

A user equipment (UE, User Equipment), which may also be called a mobile terminal (Mobile Terminal), a mobile user equipment, etc., may communicate with one or more core networks via a radio access network (eg, RAN, Radio Access Network). The user equipment may be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, for example, a mobile device that can be portable, pocket, handheld, computer built, or in-vehicle, The wireless access network exchanges languages and/or data.

The base station may be a base station (BTS, Base Transceiver Station) in GSM or CDMA, or may be a base station (NodeB) in WCDMA, or may be an evolved base station (eNB or e-NodeB, evolutional Node B) in LTE. The present invention is not limited, but for convenience of description, the following embodiments are described by taking an eNB as an example.

FIG. 1 is a schematic structural diagram of a network configuration according to an embodiment of the present invention. In the architecture shown in FIG. 1, the UE of the MTC UE is carried as the air interface part of the UE to the MTC relay, the MTC relays to the base station (eNB), and the base station to the core network gateway (GW) are transmitted through the common bearer. The MTC relay refers to a relay station attached to the MTC UE, and the relay common bearer of the MTC relay to the base station can collect UE bearers of multiple MTC UEs under the MTC relay, and the base station to the base station of the core network gateway The common bearer can aggregate the relay common bearers of multiple MTC relays under the base station. The base station can implement the mapping relationship between the relay common bearer of the MTC relay and the common bearer of the base station of the base station in a cascade manner, so that the M2M data stream of the MTC UE is collected and transmitted through the relay common bearer and the base station common bearer.

2 is a configuration method of a common bearer according to an embodiment of the present invention. The method of Figure 2 is performed by a base station. 201. The base station establishes a first public bearer.

The first common bearer is located between the base station and the MTC relay, and the first common bearer is used to transmit data of multiple terminals, where the first common bearer can be used to transmit data of multiple terminals, for example, FIG. 1 The relay common bearer is shown.

In the embodiment of the present invention, multiple terminals under the MTC relay can share a first public carrier for service transmission, and no separate bearer (GTP tunnel) needs to be established for each terminal on the relay link.

202. The base station cascades the first public bearer and the second common bearer.

The data of the multiple terminals connected to the MTC relay is transmitted uplink and downlink through the first common bearer and the second common bearer. The second common bearer is located between the base station and the core network of the base station, and the second common bearer can be used to transmit data of multiple terminals, for example, the base station public bearer shown in FIG.

The cascading of the first common bearer and the second common bearer by the base station refers to the transmission mechanism of the base station by configuring the data flow in the first common bearer and the second common bearer, so that the data flow of the MTC UE can pass the first common bearer and the first Two common bearers are transmitted.

Of course, the second common bearer can also be used to transmit data of the terminal directly connected to the base station, which is not limited herein.

In the embodiment of the present invention, by cascading the common bearer of the MTC relay and the common bearer of the base station, the load of the air interface can be aggregated, and the processing overhead of the base station is reduced.

Optionally, the establishing, by the base station, the first common bearer of the MTC relay may include: receiving, by the base station, a first common bearer setup request sent by the mobility management entity MME, where the base station establishes the first public ^^ according to the first common bearer setup request Loaded. The first public bearer setup request is used to create the first public bearer, and the first common bearer setup request carries bearer type indication information of the first public bearer.

Optionally, as an embodiment, the first common bearer setup request may be generated by the MME according to the create bearer request message initiated by the MTC relay.

Alternatively, optionally, as another embodiment, the first common bearer setup request may be the

The MME is based on a packet data network gateway (Packet Data Network) that manages the MTC relay.

Gateway, PGW) initiates the creation of a bearer request message.

FIG. 3 is a flow chart of establishing an interaction of a first public bearer according to an embodiment of the present invention. In the embodiment of the present invention, the base station does not have the functions of a PGW and a Serving Gateway (SGW). 301. Initiating an establishment process of the MTC relay public 7|

Optionally, in the embodiment of the present invention, the MTC relay public bearer establishment process may be initiated by the MTC relay and initiated by the network side. The network side here refers to the PGW that manages the MTC trunk. If the network side initiates, the PGW directly sends a create bearer request message. If the MTC relay is initiated, the PGW receives the indication information of the originating bearer setup procedure sent by the MTC relay, and sends a create bearer request message according to the indication information.

302. The PGW sends a create bearer request message.

The create bearer request message is used to request to create a first public bearer, and the PGW is a packet data gateway that manages the MTC relay. When the PGW sends a create bearer request message to the SGW, the PGW may carry the relay bearer type indication information, where the relay bearer type indication information may be used to notify the SGW and the MME that the first public bearer is used for the MTC relay public. A dedicated bearer carried.

303. The SGW sends a create bearer request message.

After receiving the bearer request message, the SGW transparently transmits the create bearer request message to the MME.

304. The MME sends a first common bearer setup request message to the base station.

After receiving the create bearer request message, the MME sends a first common bearer setup request message to the base station. When the bearer request message carries the relay bearer type indication information, the first public bearer setup request message may also carry the relay bearer type indication information.

The bearer setup information may include first bearer information and/or second bearer information. The first bearer information is used for the bearer setup information of the air interface DRB. In the embodiment of the present invention, the first bearer information may be used to create a first common bearer between the MTC relay and the base station. The second bearer information is used to create a bearer between the base station and the core network.

Optionally, in the first common bearer setup request message, the first bearer information of the first common bearer may be carried. The first bearer information may include at least one of the following: a TNL address of the MTC relay, an identifier of the MTC relay, and a tunnel endpoint identifier of the first common bearer. Further, the tunnel end identifier of the first public bearer may include a GTP tunnel end identifier TEID, an identifier of the MTC relay, and may include a device identifier or d, an area identifier of the MTC relay.

Alternatively, the first common bearer information and the second bearer information of the first common bearer may be carried in the first common bearer setup request message. For the content included in the first bearer information, refer to the foregoing description, and details are not described herein again. The second bearer information may include a base station to the core network The information between the bearers. Wherein, it may be specified that when the first bearer information is used, the second bearer information is not used, or the bearer established based on the second bearer information is not used.

305. The base station sends an RRC connection reconfiguration request message to the MTC relay.

Optionally, after receiving the first common bearer setup request message sent by the MME, the base station sends an RRC reconfiguration request message to the MTC relay according to the first common bearer setup request message. The MTC relay completes the configuration of the first public bearer on the MTC relay side according to the RRC connection reconfiguration request message to create a trunk bearer of the air interface. The RRC connection reconfiguration request message may carry the relay bearer type indication information of the first common bearer, and the MTC relay may determine the bearer type of the first common bearer according to the relay bearer type indication information.

306. The MTC relay feeds back a message that the RRC reconfiguration succeeds to the base station.

307. The base station sends a response message of the first common bearer setup request to the MME.

308. The MME sends a response message to the SGW to create a request message of the first public bearer.

309. The SGW sends a response message to the PGW to create a request message of the first public bearer.

310. The MTC relay and the base station exchange bearer information of the first common bearer.

It should be noted that step 310 is an optional step. When the first common bearer is established based on the GTP tunnel, the bearer information of the first common bearer may be exchanged between the MTC relay and the base station. The bearer information that the MTC relay and the base station interact with may include the TEID information of the public bearer.

For example, when the step 301 is initiated by the MTC relay, the TEID information of the first common bearer on the MTC relay side may be sent by the MTC relay to the base station.

Or, for example, when the step 301 is initiated by the PGW, the base station may send the TEID information of the first common bearer on the base station side to the MTC relay.

Optionally, as another embodiment, the base station may integrate the SGW and the PGW. The base station can integrate the SGW and the PGW, and the base station integrates the functions of the SGW and the PGW, or the base station includes the functional modules of the SGW and the PGW. In the prior art, the relayed EPS bearer exists between the relay and the PGW. In the embodiment of the present invention, the common bearer of the MTC relay exists between the MTC relay and the base station, and the MTC relay itself is a kind Relay, its EPS bearer must also exist between the MTC relay and the PGW. Therefore, when the base station integrates the PGW, the EPS bearer of the MTC relay can be used as the first public bearer.

In order to enable the base station to correctly map uplink (UL) and/or downlink (DL) data of multiple terminals in the MTC relay to the corresponding first public bearer, when the first common bearer is established, The first common bearer needs to be cascaded with the second common bearer, and the configuration data flow is first. The transmission mechanism of the public bearer and the second public bearer. Optionally, the cascading the first common bearer and the second common bearer by the base station may be implemented as: the base station implements the first common bearer and the second public by configuring a bearer mapping criterion between the first common bearer and the second common bearer A cascading of the bearer, where the bearer mapping criterion is used to enable the service data of the multiple terminals of the MTC relay to be uplink and downlink through the first common bearer and the second common bearer. The method for implementing the cascading of the first common bearer and the second common bearer by the base station by configuring the bearer mapping criterion between the first common bearer and the second common bearer is described in detail below. .

4 is an interaction flow diagram of cascading a first public bearer and a second public bearer according to an embodiment of the present invention.

401a, triggering a cascade request.

After the MTC relay establishes the first common bearer, the indication information of the first common bearer cascade is sent to the base station.

Alternatively, after the base station establishes the first common bearer, the process of the first common bearer cascade is directly started. 402a. The base station sends a public bearer update request to the MME.

The base station may implement the cascading of the first common bearer and the second common bearer by sending a common bearer update request, where the associated information of the first common bearer may be carried in the common bearer update request.

The association information may include a TNL address of the MTC relay and an identifier of the first public bearer. The TNL address of the MTC relay can be the IP address + port number of the relay. The identifier of the first public bearer may be a tunnel identifier, an E-RAB identifier, an EPS bearer identifier, and the like.

The TNL address of the MTC relay can be used for data routing of the MTC service user, and the core network can also construct a TFT (service flow template) for carrying the binding according to the TNL address, and the data from the MTC relay can be used by using the TFT. Transmitting, by the first public bearer, the second public bearer, or transmitting the data packet delivered to the MTC relay from the second public bearer to the first bearer;

The identity of the MTC relay is used to indicate that the core network needs to establish a cascaded MTC relay of the first common bearer and the second common bearer.

Optionally, the association information may further include identifier information of the MTC relay, for example, a device identifier or a cell identifier of the MTC relay.

Optionally, the association information may further include: an attribute parameter of the first common bearer, for example, a Quality of Service (QoS) parameter, such as a QCI (Quality Class Identifier).

Specifically, the base station may acquire the association information during the process of the relay network access, the process of establishing the first common bearer by the base station, or the process of updating the first public bearer. 403a. The MME sends a public download update request to the SGW.

404a. The SGW sends a public bearer update request to the PGW.

The PGW is a packet data gateway that manages the MTC relay, and the S-GW is a serving gateway that connects the P-GW and the base station, and the signaling interaction between the PGW/S-GW and the base station is completed by the MME.

405a. The PGW sends first bearer mapping criterion indication information to the SGW.

According to the received association information, the PGW adds the bearer mapping criterion corresponding to the relay in the common bearer mapping criterion of the base station, and informs the base station to cascade the uplink corresponding to the common bearer (UpLink, UL). ) / Downlink (DL) mapping criteria. Or, the PGW updates the bearer mapping criterion corresponding to the relay in the common bearer mapping criterion of the base station according to the received association information, and informs the base station to cascade the UL/DL bearer corresponding to the relay that needs to be updated by using the signaling. Mapping criteria.

When the PGW notifies the base station, it generally needs to be forwarded by the SGW.

The UL mapping criterion required for the cascading common bearer may include an uplink (UL) traffic flow template (TFT), and the UL TFT may filter the data on the first common bearer according to the information of the packet header, and then Mapping to the second common bearer; or the UL mapping criterion may include indication information of the bearer identifier, and the base station may map the data on the first common bearer to the second common bearer according to the bearer identifier indication information in the UL mapping criterion.

The DL mapping criteria required for the cascading common 7-bit may include a DL TFT that filters out data on the second common bearer based on the information of the packet header and then maps to the first common bearer.

406a. The SGW sends first bearer mapping criterion indication information to the MME.

After receiving the first bearer mapping criterion indication information, the SGW forwards the information to the MME, and the MME forwards the information to the eNB.

407a. The MME sends the first mapping criterion indication information to the base station.

After receiving the first bearer mapping criterion indication information, the base station configures the bearer mapping criteria of the first common bearer and the second common bearer according to the first bearer mapping criterion indication information.

If the first bearer mapping criterion indication information indicates that the corresponding bearer mapping criterion is added, the corresponding 7|map mapping criterion is added.

If the first bearer mapping criterion indication information indicates that the corresponding bearer mapping criterion is updated, the corresponding 7|map mapping criterion is updated. 408a. The base station sends, to the MME, acknowledgement information that the configuration of the bearer mapping criterion is completed.

409a. The MME sends, to the SGW, acknowledgement information that the configuration of the bearer mapping criterion is completed.

410a. The SGW sends, to the PGW, acknowledgement information that the configuration of the bearer mapping criterion is completed.

At this time, the base station completes the cascading of the first common bearer and the second common bearer, and the data of the terminal connected to the MTC relay may be uplink and downlink through the first common bearer and the second common bearer.

Certainly, the base station may also adopt other data transmission mechanisms to implement the cascading of the first common bearer and the second common bearer. The embodiment of the present invention is not limited herein.

Optionally, as another embodiment, the base station may further receive the cancellation cascade indication information of the MTC relay. The base station may request, according to the cancellation cascading indication information, the PGW to delete the bearer mapping criteria of the corresponding first public bearer and the second common bearer.

FIG. 5 is a flowchart of an interaction of canceling a first common bearer and a second common bearer cascade according to an embodiment of the present invention.

401b, triggers the cancellation of the cascade request.

When the relay or base station deletes the first common bearer, the cancel cascading request may be triggered.

402b. The base station sends a public bearer cancellation cascade request to the MME.

The public bearer cancellation cascading request may carry the identifier of the first public bearer.

403b. The MME sends a public cancellation cancellation cascade request to the SGW.

404b: The SGW sends a public bearer cancellation cascading request to the PGW.

405b. The PGW sends the second bearer mapping criterion indication information to the SGW.

The PGW cancels the cascading request according to the received common bearer, and deletes the bearer mapping criterion corresponding to the relay in the common bearer mapping criterion of the base station, and informs the base station to cascade the UL corresponding to the trunk that needs to be deleted by using the signaling. /DL bearer mapping criteria.

406b. The SGW sends the second mapping criterion indication information to the MME.

After receiving the second bearer mapping criterion indication information, the SGW forwards the information to the MME, and the MME forwards the packet to the eNB.

407b. The MME sends second bearer mapping criterion indication information to the base station.

After receiving the second bearer mapping criterion indication information, the base station deletes the bearer mapping criteria of the first common bearer and the second common bearer according to the second bearer mapping criterion indication information.

408b. The base station sends, to the MME, acknowledgement information that the configuration of the bearer mapping criterion is completed.

409b: The MME sends, to the SGW, acknowledgement information that the configuration of the bearer mapping criterion is completed. 410b. The SGW sends, to the PGW, acknowledgement information that the bearer mapping criterion configuration is completed.

6 is a flow chart of a method for data transmission in an embodiment of the present invention. The method of Figure 6 is performed by the MTC relay.

610. The MTC relay sends data of multiple terminals connected to the MTC relay to the base station by using the first common bearer.

The first common bearer is located between the MTC trunk and the base station, where the first common bearer is used to cascade data with the second common bearer to pass data of multiple terminals under the MTC relay. The common bearer and the second common bearer transmit uplink and downlink, and the second common bearer is located between the base station and the core network of the base station.

In the embodiment of the present invention, data of multiple terminals connected to the MTC relay is sent to the base station by using the first common bearer, which reduces the processing overhead of the base station.

Optionally, before step 610, the method may further include:

601. The MTC relay sends a common bearer setup request to the base station, where the common bearer setup request is used to create the first public bearer.

Optionally, the public bearer setup request may be sent by the MTC relay to the base station by using the MME.

Further, after step 601, before step 610, the method may further include:

602. The MTC relay receives the identifier information of the first public bearer sent by the base station. The identifier information of the first common bearer may be used by the MTC trunk to perform the configuration of the first public bearer on the relay side, or the MTC relay may perform the first according to the identifier information of the first public bearer. The configuration of the public bearer on the relay side.

Optionally, the identifier information of the first common bearer is sent by the base station to the MTC relay by using the MME.

Optionally, the common bearer setup request may carry bearer type indication information, where the bearer type indication information is used to indicate a bearer type of the first public bearer.

FIG. 7 is a flowchart of a common bearer mapping method according to an embodiment of the present invention. The method of Figure 7 is performed by a Service Capability Server (SCS).

701. The SCS receives the attachment information of the UE sent by the MME.

The attachment information may include address information of a site to which the UE is attached, and the site includes an MTC relay. Of course, the site to which the UE is attached may also be a base station, which is not limited herein. The service capability server updates the destination site information in the common header of the data packet of the UE according to the attachment information,

702. The SCS updates destination station information in a common header of the data packet of the UE according to the attachment information.

The packet data gateway that manages the MTC relay determines, according to the destination station, a data transmission route of the data packet of the UE in the first common bearer and the second common bearer, where the first common bearer is located between the base station and the MTC trunk. The second public bearer is located at the base station and the core network, and the first common bearer and the second common bearer are cascaded to transmit data.

In the embodiment of the present invention, the common header of the data packet of the UE is updated according to the attachment information of the UE sent by the MME, so that the management MTC relay packet data gateway can determine the data packet in the first public bearer according to the information of the destination station of the common packet header. The data transmission route of the common bearer realizes the cascade transmission of the UE in the relay common bearer and the common bearer of the base station, and reduces the air interface overhead of the base station.

Optionally, the method further includes: the service capability server sending update confirmation information to the MME. The update confirmation information may be used to indicate that the address of the site to which the UE is attached is updated successfully.

Optionally, the attachment information of the UE is forwarded by the MME through a Machine Type Communication-InterWorking Function (MTC-IWF) entity.

The current bearer mapping is performed in a traffic flow template (TFT) operation, where the TFT may include one or more packet filters. By analyzing the packet header of the data packet, the IP packet satisfying the screening condition is mapped to the corresponding bearer for transmission. Since the number of MTC UEs may be very large, if the packet header of the UE IP packet is directly filtered through the Packet filter, a large number of Packet filters need to be configured for the TFT of the common bearer, and the processing overhead is considerable.

In order to reduce the overhead of the common bearer mapping, and thus reduce the impact on the bearer mapping entities after the introduction of the MTC service, a common IP header can be nested outside the IP header of the UE. By parsing the common header, data with the same common header is mapped to the same common bearer for transmission.

In order to reduce the overhead of the common bearer mapping, thereby reducing the impact on the mapping entities after the introduction of the MTC service, an intermediate layer, such as an IP layer, may be introduced. A public IP header can be nested outside the UE's IP header. When doing bearer mapping, just analyze the public IP header. Map data with the same common header to the same by parsing the common header Transfer in the public bearer.

The following line mapping is taken as an example. When the gateway performs downlink mapping, it is determined according to the common header to determine which base station to transmit data to the common bearer (second common bearer); then when the data packet is transmitted to the base station, the base station needs to According to this common header, it is judged on which relay's common bearer (first common bearer) the packet should be mapped for transmission.

Optionally, the destination address in the common header can be set to the relayed TNL address (the relay's IP address + port number). Further, a Packet filter may be added to the DLTFT of the common bearer (second common bearer) of the base station for filtering the IP packet including the relay address, so that the MTC UE data under the relay is transmitted to the correct base station public. The bearer (second common bearer) is transmitted.

Similarly, the base station may also configure a packet filter for analyzing downlink data packets received from the base station common bearer (second common bearer). If the destination address is found to be a relay IP address, the data packet is forwarded to the corresponding data packet. The relay is transmitted on the common bearer (the first public bearer).

After the relay receives the data packet from the relay common bearer (the first common bearer), by removing the common header, the UE can obtain IP information such as the UE, and then map the data packets to the bearers of the respective UEs according to the information.

On the basis of determining the common packet header mechanism, only the attached site of the UE is known, and the corresponding common header is added to the data of the UE, so that the mapping of the data of the common bearer can be realized.

FIG. 8 is a flow chart of interaction of data packet common header processing according to an embodiment of the present invention. The interaction process is applicable to data transmission after the first common bearer and the second common bearer are cascaded, where the first common bearer is between the base station and the MTC relay, and the second common bearer is between the base station and the core network.

801. The MME is informed that the attached site of the UE changes.

The UE is transmitted by using a first common bearer between the MTC relay and the base station. The site to which the UE is attached is an MTC relay. Of course, the site to which the UE is attached may also be a base station or a common relay node, which is not limited herein.

The MME needs to determine the site (base station or relay) to which the UE is currently attached, as well as the address information of the site. In the prior art, the MME can obtain the TNL address of the base station, and when the MTC relay is used as the UE to enter the website, the MME can also obtain the IP address of the packet data network (PDN) of the MTC relay.

When the UE is attached to the base station, it is apparent that the MME knows the address information of the base station used. However, when the UE is attached to the MTC relay, the 3GPP R10 is taken as an example. In the Relay architecture of the 3GPP R10, the MME regards the MTC relay attached to the UE as a cell under the base station and does not consider it as a medium. Following the cell, the address information of the base station to which the MTC relay belongs is still used. Therefore, the UE is required to inform the MME when the UE accesses or switches to the MTC relay. The UE currently accesses the relay cell of the MTC relay. In this case, the IP address of the common packet header needs to be replaced with the IP address of the MTC relay.

802. The MME sends the address information of the newly attached UE to the MTC-IWF.

As described in step 801, the address information of the newly attached UE may be the TNL address of the base station or the PDN IP address of the MTC relay.

803. The MTC-IWF sends the address information of the newly attached UE to the SCS.

804. The SCS updates the public header of the destination site according to the site address information.

The SCS updates the public header of the destination site according to the site address information, so that the public bearer mapping can be changed.

805. The SCS sends an indication that the destination site address update is completed to the MTC-IWF.

806. The MTC-IWF sends an indication that the destination site address update is completed to the MME.

After the MME receives the indication that the update is successful, the subsequent data of the UE is transmitted based on the address of the new destination site.

FIG. 9 is a schematic structural diagram of a base station 900 according to an embodiment of the present invention. The base station 900 can include: a bearer setup unit 901 and a cascade unit 902.

The bearer establishing unit 901 can establish a first common bearer.

The first common bearer is located between the base station and the MTC relay, and the first common bearer is used to transmit data of multiple terminals, where the first common bearer can be used to transmit data of multiple terminals.

The cascading unit 902 can cascade the first common bearer and the second common bearer.

The data of the multiple terminals connected to the MTC relay is transmitted uplink and downlink through the first common bearer and the second common bearer. The second common bearer is located between the base station and the core network of the base station, and the second common bearer can be used to transmit data of multiple terminals.

In the embodiment of the present invention, the base station 900 can cascade the bearers of the air interface by reducing the common bearer between the MTC relay and the base station and the common bearer between the base station and the core network, thereby reducing the processing overhead of the base station.

Optionally, as an embodiment, the first common bearer setup request may be generated by the MME according to the create request message initiated by the MTC relay.

Alternatively, optionally, in another embodiment, the first common bearer setup request may be that the MME generates a bearer request message initiated according to a Packet Data Network Gateway (PGW) that manages the MTC relay. Optionally, as an embodiment, the PGW is a gateway integrated by the base station 900; or, alternatively, as another embodiment, the PGW is a gateway independent of the base station 900.

Optionally, base station 900 can also include a transmitting unit 904. The sending unit 904 may send the identifier information of the first public bearer to the MTC relay after the first common bearer is established.

Optionally, in the first public bearer setup request message, the first bearer information of the first public bearer may be carried. The first bearer information may include at least one of the following: a TNL address of the MTC relay, an identifier of the MTC relay, and a tunnel endpoint identifier of the first common bearer. Further, the tunnel end identifier of the first public bearer may include a GTP tunnel end identifier TEID, an identifier of the MTC relay, and may include a device identifier or d, an area identifier of the MTC relay.

Alternatively, the first common bearer information and the second bearer information of the first common bearer may be carried in the first common bearer setup request message. The content included in the first bearer information may refer to the foregoing description, and details are not described herein again. The second bearer information may include information for establishing a bearer between the base station and the core network. Wherein, it may be specified that when the first bearer information is used, the second bearer information is not used, or the bearer established based on the second bearer information is not used.

Optionally, the sending unit 904 can send a connection reconfiguration request message to the MTC relay. The connection reconfiguration request message may carry the bearer type indication information of the first common bearer, where the connection reconfiguration request message is used by the MTC relay to complete the configuration of the first public bearer on the MTC relay side, the bearer type The indication information is used by the MTC relay to determine a bearer type of the first public bearer.

Optionally, the cascading unit 902 is specifically configured to implement cascading the first common bearer and the second common bearer by configuring bearer mapping criteria between the first common bearer and the second common bearer. The bearer mapping criterion is used to enable data of multiple terminals of the MTC relay to perform uplink and downlink transmissions through the first public bearer and the second common bearer.

Further, the sending unit 904 may further send a common bearer update request to the PGW of the second public bearer according to the acquired association information of the first common bearer, where the association information includes an address of the MTC relay and/or the first public bearer. Logo. The receiving unit 903 may further receive first bearer mapping criterion indication information sent by the PGW, where the first bearer mapping criterion indication information is used to notify the base station to add or update the bearer mapping criterion. The cascading unit 902 may specifically add or update the bearer mapping criterion according to the first bearer mapping rule indication information.

Further, the receiving unit 903 can also receive the cancellation cascade indication information of the MTC relay. The cascading unit 902 may also delete the bearer mapping criterion according to the cancel cascading indication information to cancel the first A common bearer and a cascade of the second common bearer.

The base station 900 can also perform the method of FIG. 2 and the functions of the base station in the embodiments shown in FIG. 2, FIG. 3, FIG. 4, and FIG. 5, which are not described herein again.

FIG. 10 is a schematic structural diagram of a relay 1000 according to an embodiment of the present invention. The relay 1000 can include a transmitting unit 1001.

The transmitting unit 1001 can transmit data of multiple terminals connected to the relay 1000 to the base station through the first common bearer. The first common bearer is located between the relay 1000 and the base station, where the first common bearer is used to cascade data with the second common bearer to enable data of multiple terminals under the relay 1000 to pass the first common bearer. And performing uplink and downlink transmission with the second common bearer, where the second common bearer is located between the base station and a core network of the base station.

In the embodiment of the present invention, the relay 1000 sends data of multiple terminals connected to the relay 1000 to the base station through the first common bearer, which reduces the processing overhead of the base station.

Optionally, the sending unit 1001 may further send a common bearer setup request to the base station, where the common bearer setup request is used to create the first public bearer. Optionally, the common bearer setup request may be sent by the relay 1000 to the base station by using the MME.

Alternatively, the relay 1000 may further include a receiving unit 1002. The receiving unit 1002 can receive the identification information of the first public transmission sent by the base station. The identifier information of the first public bearer may be used by the relay 1000 to perform the configuration of the first public bearer on the relay side, or the relay 1000 may perform the first public bearer according to the identifier information of the first public bearer. Relay side configuration.

Optionally, the identifier information of the first common bearer is sent by the base station to the relay 1000 by using the MME.

Optionally, the first common bearer setup request may carry bearer type indication information, where the bearer type indication information is used to indicate a bearer type of the first public bearer.

The relay 1000 can perform the method of FIG. 6 and implement the functions of the MTC relay in the embodiment shown in FIG. 3, FIG. 4 and FIG. 5, and details are not described herein again.

FIG. 11 is a schematic structural diagram of a service capability server 1100 according to an embodiment of the present invention. The service capability server 1100 can include a receiving unit 1101 and a processing unit 1102.

The receiving unit 1101 may receive the attachment information of the user equipment UE sent by the mobility management entity MME.

The attachment information may include address information of a site to which the UE is attached, where the site includes

MTC relay. Certainly, the site to which the UE is attached may also be a base station, which is not limited herein. System.

The processing unit 1102 may update the destination site address information in the common header of the data packet of the UE according to the attachment information.

The packet data gateway that manages the MTC relay determines, according to the destination site address information, a data transmission route of the data packet of the UE in the first common bearer and the second common bearer, where the first common bearer is located at the base station and the MTC trunk. The second common bearer is located between the base station and the core network, and the first common bearer and the second common bearer are cascaded to transmit data.

In the embodiment of the present invention, the service capability server 1100 updates the common header of the data packet of the UE according to the attachment information of the UE sent by the MME, so that the management MTC relay packet data gateway can determine the data packet according to the information of the destination site of the common packet header. The data transmission route of the public bearer and the second common bearer realizes the cascade transmission of the UE in the relay common bearer and the common bearer of the base station, and reduces the air interface overhead of the base station.

Optionally, the service capability server 1100 may further include a sending unit 1103, and may send update confirmation information to the MME, where the update confirmation information indicates that the address of the site to which the UE is attached is updated successfully.

Optionally, the attachment information of the UE may be interoperable by the MME through a machine type communication function.

(Machine Type Communications-InterWorking Function, MTC-IWF) Entity forwarding.

The service capability server 1100 can also perform the method of FIG. 7 and implement the functions of the SCS in the embodiment shown in FIG. 8, and details are not described herein again.

Figure 12 is a schematic block diagram of a base station 1200 in accordance with an embodiment of the present invention. Base station 1200 can include a processor

1202 and memory 1203.

The processor 1202 can establish a first common bearer and cascade the first common bearer and the second common bearer.

The first common bearer is located between the base station and the MTC relay, and the first common bearer is used to transmit data of multiple terminals, where the first common bearer can be used to transmit data of multiple terminals; The bearer is located between the base station and the core network of the base station, and the second common bearer can be used to transmit data of multiple terminals. The data of the multiple terminals connected to the MTC relay is transmitted uplink and downlink through the first public bearer and the second common bearer.

The memory 1203 can store instructions that cause the processor 1202 to establish a first common bearer, and can also store instructions that cause the processor 1202 to cascade the first common bearer with the second common bearer.

In the embodiment of the present invention, the base station 1200 performs a common bearer between the MTC relay and the base station, The common bearer between the base station and the core network is cascaded, and the bearers of the air interface can be aggregated to reduce the processing overhead of the base station.

Further, the base station 1200 may further include a transmitter 1201, a receiver 1204, and the like. The processor 1202 controls the operation of the base station 1200, which may also be referred to as a CPU (Central Processing Unit). Memory 1203 can include read only memory and random access memory and provides instructions and data to processor 1202. A portion of memory 1203 may also include non-volatile random access memory (NVRAM). In a particular application, transmitter 1201 and receiver 1204 can be coupled to antenna 1205. The various components of base station 1200 are coupled together by a bus system 1206, which may include, in addition to the data bus, a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are labeled as bus system 1206 in the figure.

The method disclosed in the foregoing embodiments of the present invention may be applied to the processor 1202 or implemented by the processor 1202. Processor 1202 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1202 or an instruction in the form of software. The processor 1202 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware. Component. The methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out. The general purpose processor can be a microprocessor or the processor can be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly embodied by the execution of the hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 1203, and the processor 1202 reads the information in the memory 1203 and completes the steps of the above method in combination with the hardware thereof.

Optionally, the receiver 1204 may receive the first common bearer setup request sent by the MME, where the first common bearer setup request carries the bearer type indication information of the first common bearer. The processor 1202 is specifically configured to establish the first public bearer according to the first common bearer setup request received by the receiver 1204.

Alternatively, optionally, as another embodiment, the first common bearer setup request may be the The MME is based on a packet data network gateway (Packet Data Network) that manages the MTC relay.

Gateway, PGW) initiates the creation of a bearer request message.

Optionally, as an embodiment, the PGW is a gateway integrated by the base station 1200.

Alternatively, as another embodiment, the PGW is a gateway independent of the base station 1200.

Optionally, the transmitter 1201 may further send the identifier information of the first public bearer to the MTC relay after the first common bearer is established.

Optionally, in the first common bearer setup request message, the first bearer information of the first common bearer may be carried. The first bearer information may include at least one of the following: a TNL address of the MTC relay, an identifier of the MTC relay, and a tunnel end identifier of the first public. Further, the tunnel end identifier of the first public bearer may include a GTP tunnel end identifier TEID, an identifier of the MTC relay, and may include a device identifier or d, an area identifier of the MTC relay.

Alternatively, the transmitter 1201 can send a connection reconfiguration request message to the MTC relay. The connection reconfiguration request message may carry the bearer type indication information of the first common bearer, where the connection reconfiguration request message is used by the MTC relay to complete the configuration of the first public node 7 on the MTC relay side, where the bearer The type indication information is used by the MTC relay to determine a bearer type of the first common bearer.

Optionally, the processor 1202 specifically implements cascading the first common bearer and the second common bearer by configuring a bearer mapping criterion between the first common bearer and the second common bearer. The bearer mapping criterion is used to enable data of multiple terminals of the MTC relay to perform uplink and downlink transmissions through the first public bearer and the second common bearer.

Further, the transmitter 1201 may send a common bearer update request to the PGW of the MTC relay according to the acquired association information of the first public bearer. The receiver 1204 can receive the first bearer mapping criterion indication information sent by the PGW. The processor 1202 may specifically add or update the bearer mapping criteria of the first common bearer and the second common bearer according to the first bearer mapping criterion indication information. The association information includes a TNL address of the MTC relay and/or the first public bearer. The first bearer mapping criterion indication information is used to notify the base station that the base station needs to be added or updated.

A mapping criterion corresponding to the MTC relay, the mapping criterion may include an uplink transmission mapping criterion and/or a downlink transmission bearer mapping criterion.

Further, the receiver 1204 can also receive the cancellation cascade indication information of the MTC relay. The processor 1202 may also delete the first common carrier according to the indication information and to cancel the second cascade public _₇ | ₇ contained | carrier mapping criteria.

The base station 1200 can also perform the method of FIG. 2 and the functions of the base station in the embodiments shown in FIG. 2, FIG. 3, FIG. 4, and FIG. 5, which are not described herein again.

Figure 13 is a schematic block diagram of a relay 1300 in accordance with an embodiment of the present invention. Relay 1300 can include a processor 1302, a memory 1303, a transmitter 1301, and a receiver 1304.

The processor 1302 can transmit data of the plurality of terminals connected to the relay 1300 from the first common bearer to the base station through the transmitter 1301. The first common bearer is located between the relay 1300 and the base station, and the first common bearer is configured to cascade the data with the second common bearer to enable the data of the multiple terminals under the relay 1300 to pass the first common bearer. And performing uplink and downlink transmission with the second common bearer, where the second common bearer is located between the base station and a core network of the base station.

The memory 1303 can store instructions for causing the processor 1302 to transmit data of a plurality of terminals connected to the relay 1300 from the first common bearer to the base station through the transmitter 1301.

In the embodiment of the present invention, the relay 1300 sends data of multiple terminals connected to the relay 1300 to the base station by using the first common bearer, which reduces the processing overhead of the base station.

Further, the relay 1300 may further include a receiver 1304 and the like. The processor 1302 controls the operation of the relay 1300, which may also be referred to as a CPU (Central Processing Unit). Memory 1303 can include read only memory and random access memory and provides instructions and data to processor 1302. A portion of memory 1303 may also include non-volatile random access memory (NVRAM). In a particular application, transmitter 1301 and receiver 1304 can be coupled to antenna 1305. The various components of the relay 1300 are coupled together by a bus system 1306, which may include, in addition to the data bus, a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are labeled as bus system 1306 in the figure.

The method disclosed in the foregoing embodiments of the present invention may be applied to the processor 1302 or implemented by the processor 1302. The processor 1302 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1302 or an instruction in a form of software. The processor 1302 described above may be a general purpose processor, Digital signal processor (DSP), application specific integrated circuit (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component. The methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or executed. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 1303, and the processor 1302 reads the information in the memory 1303, and completes the steps of the above method in combination with the hardware thereof.

Optionally, the transmitter 1301 may further send a common bearer setup request to the base station, where the common bearer setup request is used to create the first public bearer. Optionally, the common bearer setup request may be sent by the relay 1300 to the base station by using the MME.

Optionally, the receiver 1304 can receive the identifier information of the first public bearer sent by the base station. The identifier information of the first common bearer may be used by the relay 1300 to perform the configuration of the first public bearer on the relay side, or the relay 1300 may perform the first public bearer according to the identifier information of the first common bearer. The configuration of the secondary side. Optionally, the identifier information of the first common bearer is sent by the base station to the relay 1300 by using the MME.

The relay 1300 can also perform the method of FIG. 6 and implement the functions of the MTC relay in the embodiment shown in FIG. 3, FIG. 4 and FIG. 5, and details are not described herein again.

FIG. 14 is a schematic structural diagram of a service capability server 1400 according to an embodiment of the present invention. The service capability server 1400 can include: a receiver 1404, a processor 1402, and a memory 1403.

The receiver 1404 may receive the attachment information of the user equipment UE sent by the mobility management entity MME. The attachment information may include address information of a site to which the UE is attached, and the site includes an MTC relay. Of course, the site to which the UE is attached may also be a base station, which is not limited herein.

The processor 1402 may update the destination site address information in the common header of the data packet of the UE according to the attachment information. The packet data gateway that manages the MTC relay determines, according to the destination site address information, a data transmission route of the data packet of the UE in the first common bearer and the second common bearer, where the first common bearer is located at the base station and the MTC trunk. Between the second public bearer is located The base station and the core network, the first common bearer and the second common bearer cascade to transmit data.

The memory 1403 may store an instruction for causing the processor 1402 to update the destination site address information in the common header of the data packet of the UE according to the attachment information.

In the embodiment of the present invention, the service capability server 1400 updates the common header of the data packet of the UE according to the attachment information of the UE sent by the MME, so that the management MTC relay packet data gateway can determine the data packet according to the information of the destination site of the common packet header. The data transmission route of the public bearer and the second common bearer realizes the cascade transmission of the UE in the relay common bearer and the common bearer of the base station, and reduces the air interface overhead of the base station.

In addition, the service capability server 1400 may also include a transmitter 1401 and the like. The processor 1402 controls the operation of the service capability server 1400, which may also be referred to as a CPU (Central Processing Unit). Memory 1403 can include read only memory and random access memory and provides instructions and data to processor 1402. A portion of memory 1403 may also include non-volatile random access memory (NVRAM). In a particular application, transmitter 1401 and receiver 1404 can be coupled to antenna 1405. The various components of the service capability server 1400 are coupled together by a bus system 1406, which may include, in addition to the data bus, a power bus, a control bus, and a status signal bus. However, for clarity of description, various buses are labeled as bus system 1406 in the figure.

The method disclosed in the above embodiments of the present invention may be applied to the processor 1402 or implemented by the processor 1402. Processor 1402 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1402 or an instruction in the form of software. The processor 1402 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware. Component. The methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out. The general purpose processor can be a microprocessor or the processor can be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly embodied by the execution of the hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 1403, and the processor 1402 reads the information in the memory 1403 and completes the steps of the above method in combination with the hardware.

Optionally, the transmitter 1401 may send an update confirmation message to the MME, where the update confirmation message is sent. The information indicates that the address of the site to which the UE is attached is updated successfully.

Optionally, the attachment information of the UE may be forwarded by the MME through the MTC-IWF entity.

The service capability server 1400 can also perform the method of FIG. 7 and implement the functions of the SCS in the embodiment shown in FIG. 8, which will not be further described herein.

It should be understood that, in various embodiments of the present invention, the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present invention. The implementation process constitutes any limitation.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in a combination of electronic hardware or computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

It will be apparent to those skilled in the art that, for the convenience of the description and the cleaning process, the specific operation of the system, the device and the unit described above may be referred to the corresponding processes in the foregoing method embodiments, and details are not described herein again.

In the several embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed. In addition, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical, mechanical or otherwise.

The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

The functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the present invention The technical solution may be embodied in the form of a software product in essence or in part of the prior art, the computer software product being stored in a storage medium, including a plurality of instructions for causing one The computer device (which may be a personal computer, server, or network device, etc.) performs all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes. .

The above is only the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the appended claims.

Claims

Rights request

1. A public bearer configuration method, characterized by including:

The base station establishes a first common bearer, the first common bearer is located between the base station and the machine type communication MTC relay, and the first common bearer is used to transmit data of multiple terminals;

The base station cascades the first public bearer and the second public bearer, wherein data of multiple terminals connected to the MTC relay is uploaded and dropped through the first public bearer and the second public bearer. line transmission, the second common bearer is located between the base station and the core network of the base station, and the second common bearer is used to transmit data of multiple terminals.

2. The method of claim 1, wherein the base station establishing the first public bearer of the MTC relay includes:

The base station receives a first public bearer establishment request sent by the mobility management entity MME. The first public bearer establishment request is used to request the establishment of the first public bearer. The first public bearer establishment request carries the first public bearer. Bearer type indication information;

The base station establishes the first public bearer according to the first public bearer establishment request.

3. The method of claim 2, characterized in that,

The first public bearer establishment request is generated by the MME according to the create bearer request message initiated by the MTC relay; or,

The first public bearer establishment request is generated by the MME according to the create bearer request message initiated by the packet data gateway PGW that manages the MTC relay;

Wherein, the create bearer request message is used to indicate creating the first public bearer.

4. The method of claim 3, wherein the PGW is a gateway integrated with the base station.

5. The method of claim 2, wherein establishing the first public bearer by the base station further includes:

The base station sends a connection reconfiguration request message to the MTC relay. The connection reconfiguration request message carries the bearer type indication information of the first public bearer. The connection reconfiguration request message is used for the MTC relay. The configuration of the first public bearer on the MTC relay side is completed, and the bearer type indication information is used by the MTC relay to determine the bearer type of the first public bearer.

6. The method according to any one of claims 3 to 5, characterized in that: After the establishment of the first public bearer, it also includes:

The base station sends the identification information of the first public bearer to the MTC relay.

7. The method according to any one of claims 3 to 6, characterized in that,

The first public bearer establishment request also carries the first bearer information of the first public bearer; or the first public bearer establishment request also carries the first bearer information and the second bearer information; wherein, the first public bearer establishment request further carries the first bearer information and the second bearer information; One bearer information includes at least one of the following: the address of the MTC relay, the identifier of the MTC relay, and the identifier of the first public bearer, where the identifier of the MTC relay is the identifier of the MTC relay. Device identification or cell identification; The second bearer information is bearer information different from the first bearer information, and the second bearer information is used to establish a bearer from the base station to a gateway of the core network.

8. The method according to any one of claims 1 to 7, wherein the base station cascading the first public bearer and the second public bearer includes:

The base station realizes the concatenation of the first public bearer and the second public bearer by configuring a bearer mapping criterion between the first public bearer and the second public bearer, and the bearer mapping criterion is used to Data of multiple terminals relayed by the MTC is caused to be transmitted uplink and downlink through the first common bearer and the second common bearer.

9. The method of claim 8, wherein the base station cascading the first public bearer and the second public bearer includes:

The base station sends a public bearer update request to the PGW of the second public bearer based on the obtained association information of the first public bearer. The association information includes the address of the MTC relay and/or the address of the first public bearer. logo;

The base station receives the first bearer mapping criterion indication information sent by the PGW, and the first bearer mapping criterion indication information is used to notify the base station to add or update the bearer mapping criterion; The mapping criterion indication information adds or updates the bearer mapping criterion.

10. The method of claim 8 or 9, further comprising:

The base station receives the cascade cancellation indication information of the MTC relay;

The base station deletes the bearer mapping criterion according to the concatenation cancellation indication information to cancel the concatenation of the first public bearer and the second public bearer.

11. A data transmission method, characterized by including:

The Machine Type Communication MTC relay sends connections to the base station through the first public bearer to the MTC Relay data of multiple terminals, wherein the first common bearer is located between the MTC relay and the base station, and the first common bearer is used to concatenate with the second common bearer so that the Data of multiple terminals under the MTC relay are transmitted uplink and downlink through the first common bearer and the second common bearer, and the second common bearer is located between the base station and the core network of the base station.

12. The method according to claim 11, characterized in that, before the MTC relay sends data of multiple terminals connected to the MTC relay to the base station through the first common bearer, it further includes:

The MTC relay sends a public bearer establishment request to the base station, where the public bearer establishment request is used to create the first public bearer.

13. The method of claim 12, wherein before the MTC relay sends data of multiple terminals connected to the MTC relay to the base station through the first common bearer, the MTC relay After the base station sends a public bearer establishment request, it also includes:

The MTC relay receives the identification information of the first public bearer sent by the base station, and the identification information of the first public bearer is used by the MTC relay to configure the first public bearer on the relay side. .

14. The method according to claim 12 or 13, characterized in that the public bearer establishment request carries bearer type indication information, and the bearer type indication information is used to indicate the bearer type of the first public bearer.

15. A public bearer mapping method, characterized by including:

The service capability server receives the attachment information of the user equipment UE sent by the mobility management entity MME, where the attachment information includes address information of the site to which the UE is attached, and the site includes a machine type communication MTC relay;

The service capability server updates the destination site information in the public header of the UE's data packet based on the attachment information, wherein the packet data gateway managing the MTC relay determines the UE's data packet based on the destination site. In the data transmission route of the first public bearer and the second public bearer, the first public bearer is located between the base station and the MTC relay, the second public bearer is located between the base station and the core network, and the first public bearer is located between the base station and the core network. The public bearer and the second public bearer transmit data in cascade.

16. The method of claim 15, further comprising:

The service capability server sends an update confirmation message to the MME, and the update confirmation message The information indicates that the address of the station to which the UE is attached is updated successfully.

17. The method according to claim 15 or 16, characterized in that the attachment information of the UE is forwarded by the MME through the machine type communication interactive function entity MTC-IWF.

18. A base station, characterized by including:

A bearer establishment unit, configured to establish a first public bearer, which is located between the base station and the machine type communication MTC relay, and the first public bearer is used to transmit data of multiple terminals;

A cascading unit configured to cascade the first public bearer and the second public bearer, wherein data of multiple terminals connected to the MTC relay passes through the first public bearer and the second public bearer. The bearer performs uplink and downlink transmission, the second common bearer is located between the base station and the core network of the base station, and the second common bearer is used to transmit data of multiple terminals.

19. The base station according to claim 18, further comprising:

A receiving unit, configured to receive a first public bearer establishment request sent by the mobility management entity MME, where the first public bearer establishment request is used to request establishment of the first public bearer, where the first public bearer establishment request carries the third public bearer establishment request. - bearer type indication information of the public bearer;

The bearer establishment unit is specifically configured to establish the first public bearer according to the first public bearer establishment request received by the receiving unit.

20. The base station according to claim 19, characterized in that,

21. The base station according to claim 20, characterized in that the PGW is a gateway integrated with the base station.

22. The base station according to claim 20 or 21, further comprising: a sending unit, configured to send the identifier of the first public bearer to the MTC relay after the first public bearer is established. information.

23. The base station according to any one of claims 20 to 22, characterized in that,

The first public bearer establishment request also carries the first bearer information of the first public bearer; or the first public bearer establishment request also carries the first bearer information and the second bearer information; Wherein, the first bearer information includes at least one of the following: an address of the MTC relay, an identifier of the MTC relay, and an identifier of the first public bearer, wherein the identifier of the MTC relay is the The equipment identification or cell identification of the MTC relay; The second bearer information is bearer information different from the first bearer information, and the second bearer information is used to establish a gateway from the base station to the core network. load.

24. The base station of claim 19, further comprising:

A sending unit, configured to send a connection reconfiguration request message to the MTC relay, where the connection reconfiguration request message carries bearer type indication information of the first public bearer, and the connection reconfiguration request message is used for the MTC The relay completes the configuration of the first public bearer on the MTC relay side, and the bearer type indication information is used by the MTC relay to determine the bearer type of the first public bearer.

25. The base station according to claim 18, wherein the cascading unit is specifically configured to implement the first public bearer by configuring a bearer mapping criterion between the first public bearer and the second public bearer. Concatenation of a common bearer and the second common bearer, the bearer mapping criterion is used to enable uplink and downlink transmission of data of multiple terminals of the MTC relay through the first common bearer and the second common bearer .

26. The base station of claim 25, further comprising:

A sending unit configured to send a public bearer update request to the PGW of the second public bearer according to the obtained association information of the first public bearer, where the association information includes the address of the MTC relay and/or the first public bearer. The identity carried;

A receiving unit, configured to receive the first bearer mapping criterion indication information sent by the PGW, where the first bearer mapping criterion indication information is used to notify the base station to add or update the bearer mapping criterion;

The cascading unit is specifically configured to add or update the bearer mapping criterion according to the first bearer mapping criterion indication information.

27. The base station according to claim 25 or 26, characterized in that,

The receiving unit is also configured to receive the concatenation cancellation indication information of the MTC relay; the cascading unit is also configured to delete the bearer mapping criterion according to the concatenation cancellation indication information to cancel the first public bearer. and the cascading of the second public bearer.

28. A relay, characterized by including:

A sending unit, configured to send a first public bearer establishment request to the base station, where the first public bearer The establishment request is used to establish a first public bearer. The first public bearer is located between the relay and the base station. The first public bearer is used to concatenate with a second public bearer so that the relay Data of multiple terminals under the base station are transmitted uplink and downlink through the first common bearer and the second common bearer, and the second common bearer is located between the base station and the core network of the base station.

29. The relay of claim 28, further comprising:

The receiving unit is configured to receive the identification information of the first public bearer sent by the base station, so that the relay configures the first public bearer on the relay side.

30. The relay according to claim 28 or 29, wherein the first public bearer establishment request carries bearer type indication information, and the bearer type indication information is used to indicate the bearer type of the first public bearer. .

31. A business capability server, characterized by: including:

A receiving unit configured to receive attachment information of the user equipment UE sent by the mobility management entity MME, where the attachment information includes address information of a site to which the UE is attached, and the site includes a machine type communication MTC relay;

A processing unit configured to update the destination site address information in the public header of the data packet of the UE according to the attachment information, wherein the packet data gateway that manages the MTC relay determines the UE based on the destination site address information. The data transmission route of the data packet between the first public bearer and the second public bearer, the first public bearer is located between the base station and the MTC relay, the second public bearer is located between the base station and the core network, so The first public bearer and the second public bearer transmit data in cascade.

32. The service capability server according to claim 31, further comprising: a sending unit, configured to send update confirmation information to the MME, where the update confirmation information indicates that the address of the site to which the UE is attached is updated successfully. .

33. The service capability server according to claim 31 or 32, wherein the attachment information of the UE is forwarded by the MME through the machine type communication interactive function entity MTC-IWF.