CN104053130A - Message processing method and device for relay network - Google Patents
Message processing method and device for relay network Download PDFInfo
- Publication number
- CN104053130A CN104053130A CN201410309234.4A CN201410309234A CN104053130A CN 104053130 A CN104053130 A CN 104053130A CN 201410309234 A CN201410309234 A CN 201410309234A CN 104053130 A CN104053130 A CN 104053130A
- Authority
- CN
- China
- Prior art keywords
- message
- base station
- rue
- network
- address
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a message processing method and device for a relay network. The relay network comprises the following network elements, namely relay user equipment and a host base station DeNB. The RUE is connected with a relay base station ReNB, and the ReNB is the network element in a user equipment network. The RUE is used for receiving a first message sent by the ReNB, and sending a second message to the DeNB or sending the first message to the DeNB through a data face, wherein the first message conforms to a multicast service Internet group management protocol. The DeNB is used for receiving the second message from the RUE or receiving the first message through the data face and reading the first message packaged in the second message or part of the message.
Description
Technical field
The present invention relates to data processing field, relate in particular to a kind of message treatment method and device of junction network.
Background technology
Multimedia broadcast/multicast service (evolved Multimedia Broadcast/Multicast Service, eMBMS) be a kind of technology that transmits data by shared network resource from a data source to multiple subscriber equipmenies, it is the exclusive definition of Long Term Evolution (Long Term Evolution, LTE) on MBMS basis.EMBMS, when multimedia service is provided, can effectively utilize Internet resources, realizes the multimedia service broadcast of higher rate.
LTE is at third generation partner program (The3rd Generation Partnership Project3GPP,) version 10 (R10) introduced relaying Relay characteristic, supporting provides transmission by the idle interface-free resources of LTE macro station for other base station.In Relay system, apply eMBMS, need to consider how BroadCast MultiCast Service passes through two network elements of Relay: host base station, for example host's evolution base station (Donor eNB, DeNB) and trunk subscriber equipment (being called for short RUE).
In R10 standard, Relay has only considered signaling and the business relaying of S1 and X2, does not consider the relaying of M1 business and the M2/M3 signaling of eMBMS business.Wherein, the protocol stack of M2/M3 signaling is consistent with X2 signaling with S1 signaling, can continue to use existing realization.M1 business is the IP multicast based on IGMPV3, needs new scheme to solve.
While using MBMS multicast bear, user by sending IGMP (Internet Group Management Protocol in unicast bearer, IGMP)/multicast communication audience finds (Multicast Listener Discovery, MLD) add message to carry out initiation business, in R10 standard, there is Tandem Gateway (Relay GateWay, Relay GW) exist scene under, host station is carried out M2/M3 application protocol (Application Protocol by message being transmitted to Relay GW as the translation proxy (Proxy) of M2/M3, AP) conversion, therefore by Relay GW to the information after being parsed of M2/M3 message, can obtain multicast group relevant information, directly send IGMP request msg by described multicast group relevant information, gateway for subscriber equipment service (is called for short, UE-UGW) multicast message request is to DeNB.
Visible: having introduced in relaying Relay characteristic LTE system, if when sending IGMP/MLD add message to initiate broadcasting/packet service in unicast bearer, Relay GW must be set in DeNB, so increased the complexity of DeNB.
Summary of the invention
The invention provides a kind of message treatment method and device of junction network, when method and apparatus provided by the present invention solves the LTE system of introducing via node in prior art and need to send IGMP/MLD add message to initiate broadcasting/packet service in unicast bearer, RelayGW must be set in DeNB, so increased the problem of the complexity of DeNB.
It should be noted that, in following content, using DeNB and ReNB giving an example as host base station and relay base station respectively, and easy for describing, may be in some be described using DeNB and ReNB respectively as the abbreviation of host base station and relay base station, but host base station in the present invention and relay base station be not limited to DeNB and ReNB for example.
First aspect, the embodiment of the present invention provides a kind of junction network, and described junction network comprises following network element: trunk subscriber equipment RUE and host base station DeNB, described RUE is connected with relay base station ReNB, and described ReNB is the network element in user equipment network, wherein,
Described RUE is used for: receive the first message that described ReNB sends, described the first message meets multicast service Internet Group Management Protocol IGMP; Wherein, described the first message comprises: the resource group # of user equipment (UE) appointment multicast group to be added, and the source IP address of described the first message IP address that is described ReNB;
Described RUE also for: send the second message to described DeNB or by data surface, described the first message is sent to described DeNB; Wherein, in described the second message, be packaged with described the first message, or, being packaged with the partial information of described the first message, the partial information of described the first message comprises: described resource group # and described source IP address;
Described DeNB is used for: receive described the second message or receive described the first message by described data surface from described RUE, read described the first message or the described partial information that in described the second message, encapsulate.
In conjunction with first aspect, in the possible implementation of the first, described the second message is non access stratum NAS message, described RUE also for: the partial information of described the first message or described the first message is packaged into described NAS message.
In conjunction with the possible implementation of the first of first aspect, in the possible implementation of the second, described RUE specifically for: the content of the agreement control item PCO using the partial information of described the first message or described the first message as described NAS message is packaged into described NAS message.
In conjunction with first aspect, in the third possible implementation, described RUE specifically for: described the first message is sent to described DeNB by the carrying by the grouped data network PDN between described RUE and described DeNB; Wherein, being carried as of described PDN: the one in the default bearer of special PDN, the existing dedicated bearer of PDN or the default bearer of existing PDN.
In conjunction with first aspect, or any one of first to three kind of possible implementation of first aspect, in the 4th kind of possible implementation, described DeNB also for: send the 3rd message to return network, described the 3rd message meets described IGMP, described the 3rd message comprises the described resource group # in described the first message or described partial information, and the source IP address of described the 3rd message IP address that is described DeNB.
In conjunction with first aspect, or any one of first to fourth of first aspect kind of possible implementation, in the 5th kind of possible implementation, described ReNB is used for: receive described resource group # from the mobile management entity UE-MME for subscriber equipment service, and send described the first message that comprises described resource group # to described RUE.
In conjunction with the 5th kind of possible implementation of first aspect, in the 6th kind of possible implementation, described ReNB specifically for: receive described resource group # by M2 or M3 interface from described UE-MME.
Second aspect, provides a kind of base station, and described base station belongs to junction network, and described junction network also comprises following network element: trunk subscriber equipment RUE, and described RUE is connected with relay base station ReNB, and described ReNB is the network element in user equipment network, and described base station comprises:
First module is used for: receive the non access stratum NAS message that described RUE sends;
Second unit is used for: the partial information of obtaining the first message or the first message from the content of the agreement control item PCO of described NAS message, described the first message meets multicast service Internet Group Management Protocol IGMP, and the partial information of described the first message comprises: the resource group # of appointment multicast group that user equipment (UE) is to be added and the IP address of described ReNB.
In conjunction with second aspect, in the possible implementation of the first, described base station also comprises:
Unit the 3rd is used for: send the second message to return network, described the second message meets described IGMP agreement, described the second message comprises the described resource group # in described the first message or described partial information, and the source IP address of described the second message IP address that is described DeNB.
In conjunction with first aspect, or the implementation that the first of first aspect is possible, in the possible implementation of the second, second unit is specifically for the part message of obtaining described the first message or the first message, wherein, described the first message is the message that meets multicast service Internet Group Management Protocol IGMP that described RUE receives from described ReNB.
The third aspect, provides a kind of trunk subscriber equipment RUE, and described RUE belongs to junction network, described junction network also comprises following network element: host base station DeNB, and wherein, described RUE is connected with relay base station ReNB, described ReNB is the network element in user equipment network, and described RUE comprises:
Receiving element is used for: receive the first message that described ReNB sends, described the first message meets multicast service Internet Group Management Protocol IGMP; Wherein, described the first message comprises: the resource group # of user equipment (UE) appointment multicast group to be added, and the source IP address of described the first message IP address that is described ReNB;
Transmitting element is used for: send the second message, to described DeNB or by data surface, described the first message is sent to described DeNB; Wherein, be packaged with described the first message, or described the second message is packaged with the partial information of described the first message in described the second message, the partial information of described the first message comprises: described resource group # and described source IP address.
In conjunction with the third aspect, in the possible implementation of the first, described the second message is non access stratum NAS message, transmitting element also for: the partial information of described the first message or described the first message is packaged into described NAS message.
In conjunction with the possible implementation of the first of the third aspect, in the possible implementation of the second, described transmitting element specifically for: the content of the agreement control item PCO using the partial information of described the first message or described the first message as described NAS message is packaged into described NAS message.
In conjunction with the third aspect, in the third possible implementation, described transmitting element specifically for: described the first message is sent to described DeNB by the carrying by the grouped data network PDN between described RUE and described DeNB; Wherein, being carried as of described PDN: the one in the default bearer of special PDN, the existing dedicated bearer of PDN or the default bearer of existing PDN.
In conjunction with the third aspect, in the 4th kind of possible implementation, described transmitting element sends described the second message and sends the 3rd message to return network for triggering described DeNB, described the 3rd message meets described IGMP, described the 3rd message comprises the described resource group # in described the first message or described partial information, and the source IP address of described the 3rd message IP address that is described DeNB.
Fourth aspect, provides a kind of message treatment method of junction network, and described junction network comprises following network element: trunk subscriber equipment RUE, with host base station DeNB, described RUE is connected with relay base station ReNB, and described ReNB is the network element in user equipment network, wherein, described method comprises:
Described RUE receives the first message that described ReNB sends, described the first message meets multicast service Internet Group Management Protocol IGMP, described the first message comprises: the resource group # of user equipment (UE) appointment multicast group to be added, and the source IP address of described the first message IP address that is described ReNB;
Described RUE sends the second message, to described DeNB or by data surface, described the first message is sent to described DeNB, wherein, in described the second message, be packaged with described the first message, or, be packaged with the partial information of described the first message, the partial information of described the first message comprises: described resource group # and described source IP address;
Described DeNB receives described the second message or receives described the first message by described data surface from described RUE, reads described the first message or the described partial information that in described the second message, encapsulate.
In conjunction with fourth aspect, in the possible implementation of the first, described the second message is NAS message.
In conjunction with the possible implementation of the first of fourth aspect, in the possible implementation of the second, the content of the agreement control item PCO of described NAS message comprises the partial information of described the first message and described the first message.
In conjunction with fourth aspect, in the third possible implementation, described RUE sends to described DeNB to comprise described the first message by data surface:
Described RUE sends to described DeNB by the carrying of the grouped data network PDN between self and described DeNB by described the first message; Wherein, being carried as of described PDN: the one in the default bearer of special PDN, the existing dedicated bearer of PDN or the default bearer of existing PDN.
In conjunction with fourth aspect, or any one in first to three kind of possible implementation of first aspect, in the 4th kind of possible implementation, the method also comprises:
Described DeNB sends the 3rd message to return network, described the 3rd message meets described IGMP agreement, described the 3rd message comprises the described resource group # in described the first message or described partial information, and the source IP address of described the 3rd message IP address that is described DeNB.
In conjunction with fourth aspect, or any one in first to fourth kind of possible implementation of first aspect, in the 5th kind of possible implementation, the method also comprises:
Described ReNB receives described resource group # from the mobile management entity UE-MME for subscriber equipment service, and sends described the first message that comprises described resource group # to described RUE.
In conjunction with the 5th kind of possible implementation of fourth aspect, in the 6th kind of possible implementation, described ReNB is from comprising for the mobile management entity UE-MME of subscriber equipment service receives described resource group #:
Described ReNB receives described resource group # by M2 or M3 interface from described UE-MME.
The 5th aspect, a kind of message treatment method of junction network is provided, described junction network comprises following network element: trunk subscriber equipment RUE, with host base station DeNB, described RUE is connected with relay base station ReNB, described ReNB is the network element in user equipment network, and wherein, described method comprises: described DeNB receives the non access stratum NAS message that described RUE sends; Described DeNB obtains the partial information of the first message or the first message from the content of the agreement control item PCO of described NAS message, described the first message meets multicast service Internet Group Management Protocol IGMP, and the partial information of described the first message comprises: the resource group # of appointment multicast group that user equipment (UE) is to be added and the IP address of described ReNB.
In conjunction with the 5th aspect, in the possible implementation of the first, described method also comprises: described DeNB sends the second message to return network, described the second message meets described IGMP agreement, described the second message comprises the described resource group # in described the first message or described partial information, and the source IP address of described the second message IP address that is described DeNB.
In conjunction with the possible implementation of the first of the 5th aspect, in the possible implementation of the second, described the first message message that meets described IGMP that to be described RUE receive from described ReNB.
The 6th aspect, a kind of message treatment method of junction network is provided, the method is applied in a trunk subscriber equipment RUE, described RUE belongs to junction network, described junction network also comprises following network element: host base station DeNB, and wherein, described RUE is connected with relay base station ReNB, described ReNB is the network element in user equipment network, and the method comprises:
Described RUE receives the first message that described ReNB sends, and described the first message meets multicast service Internet Group Management Protocol IGMP; Wherein, described the first message comprises: the resource group # of user equipment (UE) appointment multicast group to be added, and the source IP address of described the first message IP address that is described ReNB;
Described RUE sends the second message, to described DeNB or by data surface, described the first message is sent to described DeNB; Wherein, be packaged with described the first message, or described the second message is packaged with the partial information of described the first message in described the second message, the partial information of described the first message comprises: described resource group # and described source IP address.
In conjunction with the 6th aspect, in the possible implementation of the first, described the second message is non access stratum NAS message.
In conjunction with the possible implementation of the first of the 6th aspect, in the possible implementation of the second, described RUE sends the second message and comprises to described DeNB:
The content of agreement control item PCO using the partial information of described the first message or described the first message as described NAS message is packaged into described NAS message.
In conjunction with the 6th aspect, in the third possible implementation, describedly send to described DeNB to comprise described the first message by data surface:
Described the first message is sent to described DeNB by carrying by the grouped data network PDN between described RUE and described DeNB; Wherein, being carried as of described PDN: the one in the default bearer of special PDN, the existing dedicated bearer of PDN or the default bearer of existing PDN.
One or two in technique scheme, at least has following technique effect:
In this programme employing scheme, when multicast request in junction network is processed, DeNB need not arrange Relay GW module specially, because ReNB directly sends message (can be IGMP message under concrete condition) to DeNB, so DeNB can resolve the M2/M3AP message of ReNB, reduce the requirement of the upper system capability of DeNB.For ReNB network element in system, do not change initiating IGMP operation flow simultaneously, can substitute ReNB with existing Micro/Pico, reduce development and maintenance cost, the possibility of Liao Yi producer docking is provided simultaneously.
Brief description of the drawings
The structural representation of a kind of junction network that Fig. 1 provides for the embodiment of the present invention;
The structural representation of a kind of base station that Fig. 2 provides for the embodiment of the present invention;
Fig. 3 is the structural representation of host base station in the embodiment of the present invention two;
Fig. 4 is the structural representation of a kind of trunk subscriber equipment RUE in the embodiment of the present invention;
The schematic flow sheet of the message treatment method of a kind of junction network that Fig. 5 provides for the embodiment of the present invention four;
The schematic flow sheet of the message treatment method of a kind of junction network that Fig. 6 provides for the embodiment of the present invention five.
Embodiment
For making object, technical scheme and the advantage of the embodiment of the present invention clearer, below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is clearly described, obviously, described embodiment is the present invention's part embodiment, instead of whole embodiment.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtaining under creative work prerequisite, belong to the scope of protection of the invention.
Embodiment mono-
For the scheme that the clearer detailed explanation embodiment of the present invention provides, the junction network first according to the structure shown in Fig. 1, the embodiment of the present invention being provided (relay network) framework is described in detail, specifically comprises:
As shown in Figure 1, the scheme that the embodiment of the present invention provides is applicable to the network architecture shown in Fig. 1, this network architecture specifically comprises three parts: user equipment network (user equipment network, be called for short UEnetwork) in network element, junction network 100 and the return network (Backhaul Network) that the embodiment of the present invention provides, wherein:
Described return network is that the each equipment connecting by return network forms, wherein, the equipment belonging in return network can comprise: be the gateway (UE-UGW) of subscriber equipment service, many communities multicast cooperation entity (Multi-cell/multicast Coordination Entity, MCE), for the mobile management entity (being called for short UE-MME) of subscriber equipment service connects by return network.
Network element in described user equipment network comprises: relay base station ReNB (Relay eNB) and subscriber equipment (User Equipment, UE), wherein, the base station (eNB) that ReNB is RN.In the time that subscriber equipment need to be initiated multicast request, send the multicast group information of multicast request to described relay base station ReNB.
The junction network 100 that the embodiment of the present invention provides comprises: trunk subscriber equipment (RUE) 101, host base station (DeNB) 102; Wherein: described host base station 102 can connect multiple trunk subscriber equipment 101.
In the time that the network element in user equipment network, junction network 100 and return network (Backhaul Network) carry out information interaction, described ReNB is connected with described RUE, and described DeNB is by the equipment connection in return network and return network.Wherein, described ReNB is connected by Ethernet interface with described RUE, and described ReNB and described RUE can form via node RN.
Under the network architecture shown in Fig. 1, in the time that relay base station wishes to add the multicast group of appointment according to M2 interface message, initiate IGMP request.RUE receives after IGMP message, is delivered to DeNB.The information that original I GMP message carries, after DeNB processes, sends to information the return network on upper strata.
For the scheme that the more detailed description embodiment of the present invention provides, below in conjunction with the structure shown in Fig. 1, each part of a kind of junction network that the embodiment of the present invention is provided is described in detail, and specifically comprises:
Described junction network 100 comprises following network element (element): trunk subscriber equipment RUE101, and host base station DeNB102, described RUE is connected with relay base station ReNB103, and described ReNB103 is the network element in user equipment network, wherein,
In embodiments of the present invention, the each network element in described junction network can be autonomous device, can be also the component part as other equipment.For example: divide and just the described ReNB connecting by physical connection mode and RUE can be able to be considered as to via node RN by the form of connecting interface; For RN, described RUE, ReNB is a part of RN.
Described ReNB103 is used for: from receive the resource group # of user equipment (UE) 104 appointment multicast group to be added for the mobile management entity UE-MME of subscriber equipment service, and described the first message that transmission comprises described resource group # is to described RUE101.
Wherein, described ReNB103 specifically for: receive described resource group # by M2 or M3 interface from described UE-MME.
Described RUE101 is used for: receive the first message that described ReNB103 sends, described the first message meets multicast service Internet Group Management Protocol IGMP; Wherein, described the first message comprises: the resource group # of user equipment (UE) 104 appointment multicast group to be added, and the source IP address of described the first message IP address that is described ReNB103;
Because described the first message is the message that meets multicast service Internet Group Management Protocol IGMP, so in concrete environment for use, described the first message can be IGMP request message (IGMP Report).
Described RUE101 also for: send the second message to described DeNB102 or by data surface, described the first message is sent to described DeNB102; Wherein, in described the second message, be packaged with described the first message, or, being packaged with the partial information of described the first message, the partial information of described the first message comprises: described resource group # and described source IP address;
Described DeNB102 is used for: receive described the second message or receive described the first message by described data surface from described RUE101, read described the first message or the described partial information that in described the second message, encapsulate.
In order to realize the passback of message, described DeNB102 is after receiving the second message, and the Information generation one of meeting based in the second message can send to the 3rd message of return network, so:
Described DeNB also for: send the 3rd message to return network 105, described the 3rd message meets described IGMP agreement, described the 3rd message comprises the described resource group # in described the first message or described partial information, and the source IP address of described the 3rd message IP address that is described DeNB.
Wherein, add the effect of specifying multicast group in order to realize subscriber equipment, the destination address of described the first message, the second message is identical, and subscriber equipment is wished the group address of the multicast group adding.
In embodiments of the present invention, the mode that described RUE101 sends the second message to DeNB102 comprises multiple, optional:
One, can send described the second message by the form of NAS message, so:
Described the second message is non access stratum NAS message, described RUE101 also for: the partial information of described the first message or described the first message is packaged into described NAS message.
Wherein, when the second message is NAS message, for the content of described the first message is carried in described NAS message, the mode of specific implementation comprises multiple, for example: the first, is all encapsulated into whole the first message in described NAS message; The second, extracts the effective information of the first message, then effective information is appended to NAS message, and the equipment that receives NAS message is resolved and just can be got the first message afterwards described NAS message.For the second way, the realization that the embodiment of the present invention provides can be:
Described RUE101 specifically for: the content of the agreement control item PCO using the partial information of described the first message or described the first message as described NAS message is packaged into described NAS message.
Two, the first message is sent to DeNB102 by the mode of utilizing data surface to forward,
Described RUE101 specifically for: described the first message is sent to described DeNB by the carrying by the public data network PDN between described RUE and described DeNB; Wherein, being carried as of described PDN: the one in the default bearer of special PDN, the existing dedicated bearer of PDN or the default bearer of existing PDN.
In embodiments of the present invention, because the carrying of PDN comprises: the default bearer of special PDN, the existing dedicated bearer of PDN or the default bearer of existing PDN, in concrete use, need to select wherein a kind of mode to realize the embodiment of the present invention, so in order reasonably to utilize the characteristic of each carrying, select the mode of PDN carrying to be when concrete application:
In the time there is the default bearer of existing PDN, the preferential default bearer of selecting existing PDN; If there is no the default bearer of PDN, determine whether the dedicated bearer of PDN, if had, at the dedicated bearer of selecting existing PDN; In the case of the default bearer of PDN and the dedicated bearer of PDN all do not have, newly-built PDN default bearer.
Embodiment bis-
As shown in Figure 2, the embodiment of the present invention also provides a kind of base station, and this base station belongs to junction network, wherein this junction network also comprises following network element: trunk subscriber equipment RUE, described RUE is connected with relay base station ReNB, and described ReNB is the network element in user equipment network, and this base station comprises:
First module is for 201: receive the non access stratum NAS message that described RUE sends;
Second unit is for 202: the partial information of obtaining the first message or the first message from the content of the agreement control item PCO of described NAS message, described the first message meets multicast service Internet Group Management Protocol IGMP, and the partial information of described the first message comprises: the resource group # of appointment multicast group that user equipment (UE) is to be added and the IP address of described ReNB.
Wherein, described second unit 202 specifically for: obtain the part message of described the first message or the first message, wherein, described the first message message that meets multicast service Internet Group Management Protocol IGMP that to be described RUE receive from described ReNB.
For described data are sent to return network, this base station can also comprise:
Unit the 3rd is for 203: send the second message to return network, described the second message meets described IGMP agreement, described the second message comprises the described resource group # in described the first message or described partial information, and the source IP address of described the second message IP address that is described DeNB.
In embodiments of the present invention, as shown in Figure 3, described base station can be host base station (DeNB), under this host base station, can connect multiple described RUE.In the time that described base station is host base station, described first module can be that evolution base station, described second unit can be (to be called for short for the mobile management entity of RUE service, RUE-MME), described Unit the 3rd can be to be the gateway device of RUE service (being called for short RUE-UGW).
In embodiments of the present invention, the mode that described RUE sends the first message comprises multiple, and (1) is arranged on the partial information of the first message in the content of agreement control item PCO of described NAS message; (2) described the first message is directly encapsulated in described NAS message; (3) directly by data surface mode, the first message is forwarded to DeNB, so send the mode of the first message for RUE, the each functional module of DeNB that the embodiment of the present invention provides, the realization that realizes the first message forwarding comprises:
Mode one, when being packaged with described the first message (can be icmp packet) in the NAS message that described RUE sends, specific implementation can be:
Based on the structure shown in Fig. 3, the NAS message of the first message (can be icmp packet) that evolution base station in DeNB has received encapsulation that RUE sends, and the NAS message receiving is sent to the mobile management entity for RUE service that described RUE is corresponding (abbreviation RUE-MME); Described RUE-MME carries out decapsulation processing to described NAS message, obtains described the first message.Then described the first message being forwarded to the corresponding gateway device for described RUE service (is called for short, RUE-UGW), RUE-UGW directly revises after the source IP address of described the first message, sends to return network, registers corresponding multicast source to switch/router.
Mode two, when described RUE sends described the first message (can be icmp packet) by data surface mode, specific implementation can be:
Based on the structure shown in Fig. 3, evolution base station in DeNB is caught the first message that ReNB sends by data, then described the first message of catching being forwarded to the corresponding gateway device for described RUE service (is called for short, RUE-UGW), RUE-UGW directly revises after the source IP address of described the first message, send to return network, register corresponding multicast source to switch/router.
Mode three, when being packaged with a part of information of described the first message (can be icmp packet) in the NAS message that described RUE sends, specific implementation can be:
After the NAS message of a part of information of the first message that evolution base station in DeNB has received interpolation that RUE sends, and the NAS message receiving is sent to the mobile management entity for RUE service that described RUE is corresponding (abbreviation RUE-MME); Described RUE-MME resolves described NAS message, from agreement control item (the Protocol Control Option of described NAS message, PCO) resolve the partial information that obtains described the first message, re-construct the first message according to the partial information obtaining and send on return network.
Embodiment tri-
As shown in Figure 4, the embodiment of the present invention also provides a kind of trunk subscriber equipment RUE, trunk subscriber equipment RUE belongs to junction network, described junction network also comprises following network element: host base station DeNB, described RUE is connected with relay base station ReNB, described ReNB is the network element in user equipment network, and described trunk subscriber equipment RUE comprises:
Receiving element 401 for: receive the first message that described ReNB sends, described the first message meets multicast service Internet Group Management Protocol IGMP; Wherein, described the first message comprises: the resource group # of user equipment (UE) appointment multicast group to be added, and the source IP address of described the first message IP address that is described ReNB;
Transmitting element 402 for: send the second message to described DeNB or by data surface, described the first message is sent to described DeNB; Wherein, be packaged with described the first message, or described the second message is packaged with the partial information of described the first message in described the second message, the partial information of described the first message comprises: described resource group # and described source IP address.
Wherein said sending module can be non access stratum NAS message in described the second message sending, so:
Described transmitting element 402 also for: the partial information of described the first message or described the first message is packaged into described NAS message.
In order to save the resource of transmission information, the second message of transmission can only include a part for described the first message, so the part message of described the first message can be used certain parameter item in NAS message to send, so:
Described transmitting element 402 specifically for: the content of the agreement control item PCO using the partial information of described the first message or described the first message as described NAS message is packaged into described NAS message.
In addition, when the mode that described transmitting element 402 utilizes data surface to forward sends described the second message, specific implementation can be:
Described sending module 302 specifically for: described the first message is sent to described DeNB by the carrying by the grouped data network PDN between described RUE and described DeNB; Wherein, being carried as of described PDN: the one in the default bearer of special PDN, the existing dedicated bearer of PDN or the default bearer of existing PDN.
Further, after making DeNB receive described the second message, the content requests of described the second message is arrived to return network, the message of carrying in corresponding described the second message also can trigger described DeNB and send the 3rd message to return network.In the embodiment of the present invention:
Described transmitting element 402 sends described the second message and sends the 3rd message to return network for triggering described DeNB, described the 3rd message meets described IGMP, described the 3rd message comprises the described resource group # in described the first message or described partial information, and the source IP address of described the 3rd message IP address that is described DeNB.
Embodiment tetra-
As shown in Figure 5, the embodiment of the present invention provides a kind of message treatment method of junction network, the method applies in a junction network, described ultimate network comprises following network element: trunk subscriber equipment RUE and host base station DeNB, described RUE is connected with relay base station ReNB, described ReNB is the network element in user equipment network, and the method comprises:
Step 501, described ReNB is from the mobile management entity UE-MME reception resource group # for subscriber equipment service, and the first message that transmission comprises described resource group # is to described RUE;
Wherein said ReNB from the specific implementation that receives described resource group # for the mobile management entity UE-MME of subscriber equipment service can be:
Described ReNB receives described resource group # by M2 or M3 interface from described UE-MME.
Step 502, described RUE receives the first message that described ReNB sends, described the first message meets multicast service Internet Group Management Protocol IGMP, described the first message comprises: the resource group # of user equipment (UE) appointment multicast group to be added, and the source IP address of described the first message IP address that is described ReNB;
Step 503, described RUE sends the second message, to described DeNB or by data surface, described the first message is sent to described DeNB, wherein, in described the second message, be packaged with described the first message, or, be packaged with the partial information of described the first message, the partial information of described the first message comprises: described resource group # and described source IP address;
In this step, described RUE can send the second message also can directly send the first message to described DeNB, and specific implementation can be:
One, send the mode of the second message:
Described the second message can various forms, and the optional mode providing in the embodiment of the present invention is: described the second message is NAS message.
Further, be under the prerequisite of NAS message in described the second message, the mode that sends the part message of the first message can be: the content of the agreement control item PCO of described NAS message comprises the partial information of described the first message and described the first message.
Two, directly send described the first message by data surface mode:
Described RUE sends to described DeNB by the carrying of the grouped data network PDN between self and described DeNB by described the first message; Wherein, being carried as of described PDN: the one in the default bearer of special PDN, the existing dedicated bearer of PDN or the default bearer of existing PDN.
Step 504, described DeNB receives described the second message or receives described the first message by described data surface from described RUE, reads described the first message or the described partial information that in described the second message, encapsulate.
Step 505, described DeNB sends the 3rd message to return network, described the 3rd message meets described IGMP agreement, and described the 3rd message comprises the described resource group # in described the first message or described partial information, and the source IP address of described the 3rd message IP address that is described DeNB.
Above-mentioned steps 501～505th, the up process of request of data, because request of data success or unsuccessful return network send corresponding feedback message all can to the equipment of initiating request of data, concrete realizing in example, the process of transmitting of described feedback message can be the inverse process of step 501～505, also selects other all attainable modes to realize.
Embodiment five
As shown in Figure 6, the embodiment of the present invention provides the message treatment method that a kind of junction network is also provided, the method is applied in a trunk subscriber equipment RUE, described RUE belongs to junction network, described junction network also comprises following network element: host base station DeNB, and wherein, described RUE is connected with relay base station ReNB, described ReNB is the network element in user equipment network, and the method comprises:
Step 601, described RUE receives the first message that described ReNB sends, and described the first message meets multicast service Internet Group Management Protocol IGMP; Wherein, described the first message comprises: the resource group # of user equipment (UE) appointment multicast group to be added, and the source IP address of described the first message IP address that is described ReNB;
Step 602, described RUE sends the second message, to described DeNB or by data surface, described the first message is sent to described DeNB; Wherein, be packaged with described the first message, or described the second message is packaged with the partial information of described the first message in described the second message, the partial information of described the first message comprises: described resource group # and described source IP address.
Wherein, described the second message is used for triggering described DeNB and sends the 3rd message to return network, described the 3rd message meets described IGMP, described the 3rd message comprises the described resource group # in described the first message or described partial information, and the source IP address of described the 3rd message IP address that is described DeNB.
In embodiments of the present invention, the mode that described RUE sends the second message to DeNB comprises multiple, optional:
One, described the second message is non access stratum NAS message.
Wherein, in the time that described the second message is non access stratum NAS message, the second corresponding message comprises that the implementation of the part message of the first message can be:
The content of agreement control item PCO using the partial information of described the first message or described the first message as described NAS message is packaged into described NAS message.
Two, describedly send to described DeNB to comprise described the first message by data surface:
Described the first message is sent to described DeNB by carrying by the grouped data network PDN between described RUE and described DeNB; Wherein, being carried as of described PDN: the one in the default bearer of special PDN, the existing dedicated bearer of PDN or the default bearer of existing PDN.
Above-mentioned one or more technical schemes in the embodiment of the present application, at least have following technique effect:
In this programme employing scheme, when multicast request in junction network is processed, DeNB need not arrange Relay GW module specially, because ReNB directly sends message (can be IGMP message under concrete condition) to DeNB, so DeNB can resolve the M2/M3AP message of ReNB, reduce the requirement of the upper system capability of DeNB.For ReNB network element in system, do not change initiating IGMP operation flow simultaneously, can substitute ReNB with existing Micro/Pico, reduce development and maintenance cost, the possibility of Liao Yi producer docking is provided simultaneously.
It should be noted that, the various base stations in above-described embodiment can be evolution base stations, for example, be described as eNB (evolved NodeB) or eBTS (evovled base transceiver station).But the various base stations in above-described embodiment are not limited to evolution base station.
Method of the present invention is not limited to the embodiment described in embodiment, and those skilled in the art's technical scheme according to the present invention draws other execution mode, belongs to equally technological innovation scope of the present invention.
The software module that the method for describing in conjunction with embodiment disclosed herein or the step of algorithm can use hardware, processor to carry out, or the combination of the two is implemented.Software module can be placed in the storage medium of any other form known in random asccess memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable ROM, register, hard disk, moveable magnetic disc, CD-ROM or technical field.
Obviously, those skilled in the art can carry out various changes and modification and not depart from the spirit and scope of the present invention the present invention.Like this, if these amendments of the present invention and within modification belongs to the scope of the claims in the present invention and equivalent technologies thereof, the present invention is also intended to comprise these changes and modification interior.
Claims (25)
1. a junction network, is characterized in that, described junction network comprises following network element: trunk subscriber equipment RUE and host base station, and described RUE is connected with relay base station, and described relay base station is the network element in user equipment network, wherein,
Described RUE is used for: receive the first message that described relay base station sends, described the first message meets multicast service Internet Group Management Protocol IGMP; Wherein, described the first message comprises: the resource group # of user equipment (UE) appointment multicast group to be added, and the source IP address of described the first message IP address that is described relay base station;
Described RUE also for: send the second message to described host base station or by data surface, described the first message is sent to described host base station; Wherein, in described the second message, be packaged with described the first message, or, being packaged with the partial information of described the first message, the partial information of described the first message comprises: described resource group # and described source IP address;
Described host base station is used for: receive described the second message or receive described the first message by described data surface from described RUE, read described the first message or the described partial information that in described the second message, encapsulate.
2. junction network as claimed in claim 1, is characterized in that, described the second message is non access stratum NAS message, described RUE also for: the partial information of described the first message or described the first message is packaged into described NAS message.
3. junction network as claimed in claim 2, is characterized in that, described RUE specifically for: the content of the agreement control item PCO using the partial information of described the first message or described the first message as described NAS message is packaged into described NAS message.
4. junction network as claimed in claim 1, is characterized in that, described RUE specifically for: described the first message is sent to described host base station by the carrying by the grouped data network PDN between described RUE and described host base station; Wherein, being carried as of described PDN: the one in the default bearer of special PDN, the existing dedicated bearer of PDN or the default bearer of existing PDN.
5. the junction network as described in as arbitrary in claim 1～4, it is characterized in that, described host base station also for: send the 3rd message to return network, described the 3rd message meets described IGMP, described the 3rd message comprises the described resource group # in described the first message or described partial information, and the source IP address of described the 3rd message is the IP address of described host base station.
6. the junction network as described in as arbitrary in claim 1～5, it is characterized in that, described relay base station is used for: receive described resource group # from the mobile management entity UE-MME for subscriber equipment service, and send described the first message that comprises described resource group # to described RUE.
7. junction network as claimed in claim 6, is characterized in that, described relay base station specifically for: receive described resource group # by M2 or M3 interface from described UE-MME.
8. a base station, is characterized in that, described base station belongs to junction network, and described junction network also comprises following network element: trunk subscriber equipment RUE, and described RUE is connected with relay base station, and described relay base station is the network element in user equipment network, and described base station comprises:
First module is used for: receive the non access stratum NAS message that described RUE sends;
Second unit is used for: the partial information of obtaining the first message or the first message from the content of the agreement control item PCO of described NAS message, described the first message meets multicast service Internet Group Management Protocol IGMP, and the partial information of described the first message comprises: the resource group # of appointment multicast group that user equipment (UE) is to be added and the IP address of described relay base station.
9. base station as claimed in claim 8, is characterized in that, described base station also comprises:
Unit the 3rd is used for: send the second message to return network, described the second message meets described IGMP agreement, described the second message comprises the described resource group # in described the first message or described partial information, and the source IP address of described the second message is the IP address of described host base station.
10. base station as claimed in claim 8 or 9, it is characterized in that, second unit specifically for: obtain the part message of described the first message or the first message, wherein, described the first message message that meets described IGMP that to be described RUE receive from described relay base station.
11. 1 kinds of trunk subscriber equipment RUE, is characterized in that, described RUE belongs to junction network, described junction network also comprises following network element: host base station, described RUE is connected with relay base station, and described relay base station is the network element in user equipment network, and described RUE comprises:
Receiving element is used for: receive the first message that described relay base station sends, described the first message meets multicast service Internet Group Management Protocol IGMP; Wherein, described the first message comprises: the resource group # of user equipment (UE) appointment multicast group to be added, and the source IP address of described the first message IP address that is described relay base station;
Transmitting element is used for: send the second message, to described host base station or by data surface, described the first message is sent to described host base station; Wherein, be packaged with described the first message, or described the second message is packaged with the partial information of described the first message in described the second message, the partial information of described the first message comprises: described resource group # and described source IP address.
12. RUE as claimed in claim 11, is characterized in that, described the second message is non access stratum NAS message, transmitting element also for: the partial information of described the first message or described the first message is packaged into described NAS message.
13. RUE as claimed in claim 12, is characterized in that, described transmitting element specifically for: the content of the agreement control item PCO using the partial information of described the first message or described the first message as described NAS message is packaged into described NAS message.
14. RUE as claimed in claim 11, is characterized in that, described transmitting element specifically for: described the first message is sent to described host base station by the carrying by the grouped data network PDN between described RUE and described host base station; Wherein, being carried as of described PDN: the one in the default bearer of special PDN, the existing dedicated bearer of PDN or the default bearer of existing PDN.
15. RUE as claimed in claim 11, it is characterized in that, described transmitting element sends described the second message and sends the 3rd message to return network for triggering described host base station, described the 3rd message meets described IGMP, described the 3rd message comprises the described resource group # in described the first message or described partial information, and the source IP address of described the 3rd message is the IP address of described host base station.
The message treatment method of 16. 1 kinds of junction networks, is characterized in that, described junction network comprises following network element: trunk subscriber equipment RUE and host base station, described RUE is connected with relay base station, described relay base station is the network element in user equipment network, and wherein, described method comprises:
Described RUE receives the first message that described relay base station sends, described the first message meets multicast service Internet Group Management Protocol IGMP, described the first message comprises: the resource group # of user equipment (UE) appointment multicast group to be added, and the source IP address of described the first message IP address that is described relay base station;
Described RUE sends the second message, to described host base station or by data surface, described the first message is sent to described host base station, wherein, in described the second message, be packaged with described the first message, or, be packaged with the partial information of described the first message, the partial information of described the first message comprises: described resource group # and described source IP address;
Described host base station receives described the second message or receives described the first message by described data surface from described RUE, reads described the first message or the described partial information that in described the second message, encapsulate.
17. methods as claimed in claim 16, is characterized in that, described the second message is NAS message.
18. methods as claimed in claim 17, is characterized in that, the content of the agreement control item PCO of described NAS message comprises the partial information of described the first message and described the first message.
19. methods as claimed in claim 16, is characterized in that, described RUE sends to described host base station to comprise described the first message by data surface:
Described RUE sends to described host base station by the carrying of the grouped data network PDN between self and described host base station by described the first message; Wherein, being carried as of described PDN: the one in the default bearer of special PDN, the existing dedicated bearer of PDN or the default bearer of existing PDN.
20. methods as described in as arbitrary in claim 16～19, is characterized in that, the method also comprises:
Described host base station sends the 3rd message to return network, described the 3rd message meets described IGMP agreement, described the 3rd message comprises the described resource group # in described the first message or described partial information, and the source IP address of described the 3rd message is the IP address of described host base station.
21. methods as described in as arbitrary in claim 16～20, is characterized in that, the method also comprises:
Described relay base station receives described resource group # from the mobile management entity UE-MME for subscriber equipment service, and sends described the first message that comprises described resource group # to described RUE.
22. methods as claimed in claim 21, is characterized in that, described relay base station is from comprising for the mobile management entity UE-MME of subscriber equipment service receives described resource group #:
Described relay base station receives described resource group # by M2 or M3 interface from described UE-MME.
The message treatment method of 23. 1 kinds of junction networks, is characterized in that, described junction network comprises following network element: trunk subscriber equipment RUE, with host base station, described RUE is connected with relay base station, and described relay base station is the network element in user equipment network, wherein, described method comprises:
Described host base station receives the non access stratum NAS message that described RUE sends;
Described host base station obtains the partial information of the first message or the first message from the content of the agreement control item PCO of described NAS message, described the first message meets multicast service Internet Group Management Protocol IGMP, and the partial information of described the first message comprises: the resource group # of appointment multicast group that user equipment (UE) is to be added and the IP address of described relay base station.
24. methods as claimed in claim 23, is characterized in that, described method also comprises:
Described host base station sends the second message to return network, described the second message meets described IGMP agreement, described the second message comprises the described resource group # in described the first message or described partial information, and the source IP address of described the second message is the IP address of described host base station.
25. methods as described in claim 23 or 24, is characterized in that, described the first message is the message that meets described IGMP that described RUE receives from described relay base station.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410309234.4A CN104053130B (en) | 2014-06-30 | 2014-06-30 | The message treatment method and device of a kind of junction network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410309234.4A CN104053130B (en) | 2014-06-30 | 2014-06-30 | The message treatment method and device of a kind of junction network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104053130A true CN104053130A (en) | 2014-09-17 |
| CN104053130B CN104053130B (en) | 2017-10-17 |
Family
ID=51505404
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410309234.4A Active CN104053130B (en) | 2014-06-30 | 2014-06-30 | The message treatment method and device of a kind of junction network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104053130B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017054661A1 (en) * | 2015-09-28 | 2017-04-06 | 中兴通讯股份有限公司 | Wireless relay method, wireless relay, and wireless relay system |
| CN108696827A (en) * | 2018-07-16 | 2018-10-23 | 鼎桥通信技术有限公司 | A kind of transparent method of multicasting and equipment based on LTE |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101932124A (en) * | 2009-06-23 | 2010-12-29 | 财团法人资讯工业策进会 | Base station, relay station and backhaul control communication methods thereof |
| CN101998679A (en) * | 2009-08-13 | 2011-03-30 | 华为技术有限公司 | Transmission bearing relaying method, device and communication system |
| US20120213144A1 (en) * | 2011-02-23 | 2012-08-23 | Qualcomm Incorporated | Spatial techniques for evolved multimedia broadcast multicast service enhancement |
| CN103379443A (en) * | 2012-04-20 | 2013-10-30 | 中兴通讯股份有限公司 | Method and system for keeping multicast services continuous |
| CN103430575A (en) * | 2010-12-24 | 2013-12-04 | 辉达公司 | Wireless communication unit, integrated circuit and method for reception of broadcast communication |
-
2014
- 2014-06-30 CN CN201410309234.4A patent/CN104053130B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101932124A (en) * | 2009-06-23 | 2010-12-29 | 财团法人资讯工业策进会 | Base station, relay station and backhaul control communication methods thereof |
| CN101998679A (en) * | 2009-08-13 | 2011-03-30 | 华为技术有限公司 | Transmission bearing relaying method, device and communication system |
| CN103430575A (en) * | 2010-12-24 | 2013-12-04 | 辉达公司 | Wireless communication unit, integrated circuit and method for reception of broadcast communication |
| US20120213144A1 (en) * | 2011-02-23 | 2012-08-23 | Qualcomm Incorporated | Spatial techniques for evolved multimedia broadcast multicast service enhancement |
| CN103379443A (en) * | 2012-04-20 | 2013-10-30 | 中兴通讯股份有限公司 | Method and system for keeping multicast services continuous |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017054661A1 (en) * | 2015-09-28 | 2017-04-06 | 中兴通讯股份有限公司 | Wireless relay method, wireless relay, and wireless relay system |
| CN108696827A (en) * | 2018-07-16 | 2018-10-23 | 鼎桥通信技术有限公司 | A kind of transparent method of multicasting and equipment based on LTE |
| CN108696827B (en) * | 2018-07-16 | 2021-09-03 | 鼎桥通信技术有限公司 | LTE-based transparent multicast method and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104053130B (en) | 2017-10-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101307175B1 (en) | An access gateway, enb and method of the evolved multimedia broadcast multicast service | |
| US9225536B2 (en) | Method and device for implementing MBMS service when relay node is deployed in network | |
| JP6093037B2 (en) | Method, system, base station, and cluster EPC for establishing group call context | |
| JP4723457B2 (en) | Relay device, wireless communication system, and multicast relay method | |
| CN102469415B (en) | Method, terminal and system for point-to-multipoint calling in cluster system based on long term evolution (LTE) technology | |
| JP2018500836A (en) | Mechanism for providing LTE voice, Internet, and EMBMS services over Ethernet for connected home architecture | |
| US8855048B2 (en) | Method and system for peer-to-peer cellular communications | |
| US9456315B2 (en) | Multicast group reuse in cellular network multicase transport | |
| US20100110961A1 (en) | Method and apparatus for supporting mbms in system architecture evolution | |
| CN104618349A (en) | Trunk communication system, server and communication method | |
| WO2019114938A1 (en) | Method, system and apparatus for multicast session management in a 5g communication network | |
| RU2011117236A (en) | PROCESSING TRAFFIC OF A LOCAL DIRECT CONNECTION IN A HOME BASIC STATION | |
| US9648541B2 (en) | Apparatus and method for forwarding data based on software defined network in communication network | |
| WO2017004771A1 (en) | Enhanced multimedia broadcast and multicast service embms system and management method therefor | |
| CN102857873A (en) | Wideband digital cluster system based on TD-LTE (time division-long term evolution) and data transmission method thereof | |
| CN104661184A (en) | Method and equipment for satellite communication | |
| WO2009103213A1 (en) | Method and device for transmitting multimedia broadcast multicast service | |
| TW201622465A (en) | Coverage enhancement for multicast in a cellular network | |
| CN101868035A (en) | Multipoint cooperative transmission system and method thereof | |
| EP4184958A1 (en) | Method for multicast communication, and first network device and second network device | |
| CN104053130A (en) | Message processing method and device for relay network | |
| WO2015144196A1 (en) | Solution for critical communication security based on mbms security | |
| CN102334369B (en) | Message transmitting method and device thereof | |
| CN101552686B (en) | Synchronous data transmission method among broadcasting service element locations of multimedia multicasting | |
| CN109218997B (en) | Method and device for processing cluster call |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |