[go: up one dir, main page]

WO2016112678A1 - Dispositif et procédé de traitement de données - Google Patents

Dispositif et procédé de traitement de données Download PDF

Info

Publication number
WO2016112678A1
WO2016112678A1 PCT/CN2015/085466 CN2015085466W WO2016112678A1 WO 2016112678 A1 WO2016112678 A1 WO 2016112678A1 CN 2015085466 W CN2015085466 W CN 2015085466W WO 2016112678 A1 WO2016112678 A1 WO 2016112678A1
Authority
WO
WIPO (PCT)
Prior art keywords
tmgi
request message
layer
sai
relay node
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.)
Ceased
Application number
PCT/CN2015/085466
Other languages
English (en)
Chinese (zh)
Inventor
朱进国
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority claimed from CN201510342667.4A external-priority patent/CN106211087A/zh
Application filed by ZTE Corp filed Critical ZTE Corp
Publication of WO2016112678A1 publication Critical patent/WO2016112678A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

Definitions

  • the present invention relates to the field of communications, and in particular to a data processing method and apparatus.
  • Direct communication between devices in the vicinity using Device to Device can bring many benefits to the terminal, such as higher speed, lower latency and lower power consumption, and greatly improved.
  • the wireless resource efficiency of the operator, the D2D Relay mode is beneficial for operators to improve wireless coverage; for applications, the use of proximity information in the D2D communication process can develop more attractive new services.
  • the Public Safety system can also use D2D technology to enable communication between terminals without wireless coverage.
  • FIG. 1 is a schematic diagram of a D2D Relay architecture related to 3GPP in the related art, as shown in FIG. 1, including:
  • the remote terminal is also called User Equipment (UE).
  • UE User Equipment
  • the terminal is in the no-mobile signal coverage. It supports D2D discovery and communication through the PC5 interface and other terminals.
  • the remote terminal can also communicate with the network through the Relay node. .
  • Relay node also called a relay node, the node is a terminal, is within the coverage of mobile signals, supports other remote terminals to communicate with the network through the terminal, the Relay node supports Relay to discover the broadcast, and the remote terminal reads the broadcast information. Select the appropriate Relay node and communicate with the network through the node.
  • Base station Provides wireless coverage for the Relay terminal, and can also perform radio resource authorization and allocation for D2D discovery or communication when the Relay terminal performs communication.
  • the base station transmits downlink data through broadcast, which is beneficial to save air interface resources.
  • the air interface between the base station and the terminal is a Uu port.
  • Core network It is mainly responsible for the registration of the Relay node, the assignment of the IP address, and the bearer establishment.
  • the Relay node communicates with the external network through the core network.
  • the interface between the base station and the core network is an S1 interface.
  • the D2D key management server is mainly responsible for generating the D2D service security key, and the D2D key server may be combined with the short-range communication server or may be separately configured.
  • Cluster communication server The main functions of the cluster service include the management of the cluster service group, call setup, release, and management.
  • the UE and the trunking communication server are PC1 interfaces, and the UE initiates registration with the cluster communication server by using the interface, and obtains service-related information from the cluster communication server, and the UE also passes the The interface initiates a group call, request for voice, and the like to the cluster communication server.
  • FIG. 2 is a flow chart of initiating registration by a remote terminal through a Relay node according to the related art. As shown in FIG. 2, the process includes the following steps:
  • Step S202 The Relay node is in a radio coverage area, obtains D2D broadcast resources from the base station, and performs D2D broadcast, where the broadcast carries related information of the Relay node, including layer 2 (ie, MAC layer) user address, PLMN ID, and Relay node application. Information (such as the supported Access Point Name (APN) information), whether the Relay node is available, and so on.
  • layer 2 ie, MAC layer
  • API Access Point Name
  • Step S204 After the remote terminal selects a Relay node, the layer 2 user address of the Relay node is used to establish a layer 2 communication link with the Relay node.
  • Step S206 the Relay node allocates an IP address to the remote terminal, and the address may be an IPv4 address or an IPv6 address. After that, the remote terminal can communicate with the network through the Relay node.
  • Step S208 the remote terminal performs application layer registration with the cluster communication server.
  • Step S210 The cluster communication server returns a registration response to the remote terminal, where configuration information related to the cluster group communication, such as Temporary Mobile Group Identity (TMGI), group security related parameters, and group communication related Layer 2 group addresses, etc., where TMGI) is assigned by the application server to uniquely identify a group.
  • configuration information related to the cluster group communication such as Temporary Mobile Group Identity (TMGI), group security related parameters, and group communication related Layer 2 group addresses, etc., where TMGI) is assigned by the application server to uniquely identify a group.
  • the cluster server broadcasts the enhanced multimedia broadcast/multicast service (eMBMS) data corresponding to the TMGI through the network, and the relay node can accept the data. If the Relay node belongs to the group corresponding to the TMGI, the Relay node can know the group security related parameters of the application layer, and the data can be parsed, otherwise the Relay node cannot parse the data. Through the above process, the far terminal can perform unicast communication with the cluster server.
  • eMBMS enhanced multimedia broadcast/multicast service
  • the embodiments of the present invention provide a data processing method and apparatus, so as to at least solve the problem in the related art that is not used for the relay node to the terminal to perform multicast data transmission.
  • a data processing method including: receiving a request message for monitoring a temporary user group identifier TMGI sent by a user equipment, where the request message carries the TMGI and the Layer 2 group identifier corresponding to TMGI; listening in accordance with the request message
  • the received enhanced multicast and multicast service eMBMS data corresponding to the TMGI is sent to the user equipment through a PC5 interface, where the layer 2 destination address setting on the PC5 interface is set. Identify the layer 2 group.
  • the method further includes: feeding back a response message to the user equipment, where the response message carries the indication that the user equipment is exceeding The request message is resent after a predetermined time.
  • the method further includes: performing monitoring processing on the TMGI according to the request message.
  • the request message further carries the service area identity (SAI) corresponding to the TMGI
  • SAI service area identity
  • determining, by the SAI, the serving cell that performs the monitoring process on the TMGI includes: determining, according to the SAI, whether the SAI of the current serving cell is consistent with the SAI; if the determination result is yes, determining the location Determining that the current serving cell is the serving cell that performs the interception process on the TMGI; and/or, if the determination result is no, determining that the serving cell in the predetermined range of the current serving cell is to monitor the TMGI The treated cell being processed.
  • a data processing method including: sending a request message for monitoring a temporary user group identifier TMGI to a relay relay node, where the request message carries the TMGI And the layer 2 group identifier corresponding to the TMGI; the enhanced multicast and multicast service eMBMS data sent by the Relay node is received by the PC5 interface corresponding to the layer 2 group identifier, where the layer 2 on the PC5 interface The destination address is set to the layer 2 group identifier, and the eMBMS data is sent by the relay node in the case that the TMGI is monitored according to the request message.
  • the method further includes: acquiring, by the cluster server, a service area identifier SAI corresponding to the TMGI, where the SAI is used for prompting the location
  • the relay node determines, according to the SAI, a serving cell that performs monitoring processing on the TMGI, and sends the acquired SAI corresponding to the TMGI to the Relay node.
  • a data processing apparatus including: a first receiving module, configured to receive a request message for monitoring a temporary user group identifier TMGI sent by a user equipment, where the request message is Carrying the layer 2 destination address corresponding to the TMGI and the TMGI; the first sending module is configured to: when the TMGI is monitored according to the request message, the received enhanced multicast corresponding to the TMGI And the multicast service eMBMS data is sent to the user equipment through the PC5 interface, where the layer 2 destination address on the PC5 interface is set to the layer 2 group identifier.
  • a first receiving module configured to receive a request message for monitoring a temporary user group identifier TMGI sent by a user equipment, where the request message is Carrying the layer 2 destination address corresponding to the TMGI and the TMGI
  • the first sending module is configured to: when the TMGI is monitored according to the request message, the received enhanced multicast corresponding to the TMGI
  • the multicast service eMBMS data is sent to the user equipment through the
  • the device further includes: a feedback module, configured to feed back a response message to the user equipment, where the response message carries an indication that the user equipment resends the request message after a predetermined time is exceeded.
  • a feedback module configured to feed back a response message to the user equipment, where the response message carries an indication that the user equipment resends the request message after a predetermined time is exceeded.
  • the device further includes: a listening processing module, configured to perform a monitoring process on the TMGI according to the request message.
  • the device further includes: a determining module, configured to determine, according to the SAI, a service for monitoring the TMGI according to the SAI, when the request message further carries the service area identifier SAI corresponding to the TMGI Community.
  • a determining module configured to determine, according to the SAI, a service for monitoring the TMGI according to the SAI, when the request message further carries the service area identifier SAI corresponding to the TMGI Community.
  • the determining module includes: a determining unit, configured to determine, according to the SAI, whether the SAI of the current serving cell is consistent with the SAI; and the first determining unit is configured to determine, if the determination result is yes, The current serving cell is the serving cell that performs the interception process on the TMGI; and/or the second determining unit is configured to determine, in a case that the determination result is no, the serving cell in the predetermined range of the current serving cell The serving cell that performs the listening process on the TMGI.
  • a data processing apparatus comprising: a second sending module, configured to send a request message for monitoring a temporary user group identifier TMGI to a relay Relay node, wherein the request The message carries the TMGI and the layer 2 group identifier corresponding to the TMGI.
  • the second receiving module is configured to receive the enhanced multicast and multicast sent by the Relay node by using the PC5 interface corresponding to the layer 2 group identifier.
  • the service eMBMS data wherein the layer 2 destination address on the PC5 interface is set to the layer 2 group identifier, and the eMBMS data is sent by the relay node in the case that the TMGI is monitored according to the request message. .
  • the device further includes: a second obtaining module, configured to acquire a service area identifier SAI corresponding to the TMGI from the cluster server, where the SAI is used to prompt the relay node to determine a location according to the SAI
  • the serving cell that performs the monitoring process by the TMGI is configured to send the acquired SAI corresponding to the TMGI to the Relay node.
  • the request message for monitoring the temporary user group identifier TMGI sent by the user equipment is received, wherein the request message carries the TMGI and the layer 2 group identifier corresponding to the TMGI;
  • the enhanced multicast and multicast service eMBMS data corresponding to the TMGI is sent to the user equipment through the PC5 interface, where the request message is monitored to the TMGI, where the layer 2 on the PC5 interface is
  • the destination address is set to the layer 2 group identifier, which solves the problem that the related system does not use the relay node to the terminal for multicast data propagation, and provides a basis for the relay node to the terminal to perform multicast data transmission.
  • FIG. 1 is a schematic diagram of a D2D Relay architecture related to 3GPP in the related art
  • FIG. 2 is a flowchart of initiating registration by a remote terminal through a Relay node according to the related art
  • FIG. 3 is a flowchart 1 of a data processing method according to an embodiment of the present invention.
  • FIG. 4 is a second flowchart of a data processing method according to an embodiment of the present invention.
  • FIG. 5 is a block diagram 1 of a data processing apparatus according to an embodiment of the present invention.
  • FIG. 6 is a block diagram 1 of a data processing apparatus in accordance with a preferred embodiment of the present invention.
  • FIG. 7 is a block diagram 2 of a data processing apparatus in accordance with a preferred embodiment of the present invention.
  • FIG. 8 is a block diagram 3 of a data processing apparatus in accordance with a preferred embodiment of the present invention.
  • FIG. 9 is a block diagram 2 of a data processing apparatus according to an embodiment of the present invention.
  • FIG. 10 is a block diagram 4 of a data processing apparatus in accordance with a preferred embodiment of the present invention.
  • FIG. 11 is a schematic diagram of point-to-multipoint communication of D2D according to an embodiment of the present invention.
  • FIG. 13 is a flowchart of acquiring a key according to point-to-multipoint communication in the related art
  • 15 is a flow chart of a data processing method in accordance with a preferred embodiment of the present invention.
  • FIG. 3 is a flowchart 1 of a data processing method according to an embodiment of the present invention. As shown in FIG. 3, the process includes the following steps:
  • Step S302 receiving a request message for monitoring the temporary user group identifier TMGI sent by the user equipment, where the request message carries the TMGI and the layer 2 group identifier corresponding to the TMGI;
  • Step S304 in the case that the TMGI is monitored according to the request message, the received enhanced multicast and multicast service eMBMS data corresponding to the TMGI is sent to the user equipment through the PC5 interface, where The layer 2 destination address on the PC5 interface is set to the layer 2 group identifier.
  • a request message for monitoring the temporary user group identifier TMGI sent by the user equipment where the request message carries the layer 2 group identifier corresponding to the TMGI and the TMGI, and is monitored according to the request message.
  • the received enhanced multicast and multicast service eMBMS data corresponding to the TMGI is sent to the user equipment through the PC5 interface, where the layer 2 destination address on the PC5 interface is set to
  • the layer 2 group identification solves the problem that the related technology does not use the relay node to the terminal for multicast data transmission, and provides a basis for the relay node to the terminal to perform multicast data transmission.
  • the user equipment may send the interception request message in a certain period before receiving the request message for monitoring the temporary user group identifier TMGI sent by the user equipment, and then feedback the response to the user equipment.
  • the message wherein the response message carries a message indicating that the user equipment resends the request message after a predetermined time is exceeded, which improves the success rate of the monitoring process.
  • the TMGI After receiving the request message for monitoring the temporary user group identifier TMGI sent by the user equipment, the TMGI is monitored according to the request message.
  • the serving cell that performs the interception processing on the TMGI according to the SAI may be advanced according to the SAI. It is determined whether the TMGI can be monitored in the current area. If the monitoring is not available, the neighboring cell broadcasts are monitored whether there is a service area identifier for monitoring the TMGI, and if so, camped on the corresponding neighboring cell in advance.
  • the SAI is determined by the SAI to determine the serving cell of the TMGI. In an optional embodiment, whether the SAI of the current serving cell is consistent with the SAI may be determined according to the SAI; If the current serving cell is the serving cell that performs the interception process on the TMGI; and/or, if the determination result is no, determining that the serving cell in the predetermined range of the current serving cell is the TMGI.
  • the serving cell that listens for processing for example, determines whether the service area identifier of the neighboring cell is consistent with the SAI, and if it is consistent, camps in the neighboring cell in advance and performs monitoring processing on the TMGI.
  • FIG. 4 is a second flowchart of a data processing method according to an embodiment of the present invention. As shown in FIG. 4, the process includes the following steps:
  • Step S402 sending a request message for monitoring the temporary user group identifier TMGI to the relay relay node, where the request message carries the TMGI and the layer 2 group identifier corresponding to the TMGI;
  • Step S404 receiving, by the PC5 interface corresponding to the layer 2 group identifier, the enhanced multicast and multicast service eMBMS data sent by the Relay node, where the layer 2 destination address on the PC5 interface is set to the layer 2 group identifier.
  • the eMBMS data is sent by the Relay node in the case that the TMGI is monitored according to the request message.
  • the request message for monitoring the temporary user group identifier TMGI is sent to the Relay node, and the enhanced multicast and multicast service eMBMS data sent by the Relay node is received by the PC5 interface corresponding to the layer 2 group identifier.
  • the layer 2 destination address on the PC5 interface is set to the layer 2 group identifier, and the eMBMS data is sent by the relay node in the case that the TMGI is monitored according to the request message, which solves the problem in the related art.
  • the problem of the basics of multicast data transmission from the Relay node to the terminal provides a basis for the relay node to the terminal to carry out multicast data transmission.
  • the service area identifier SAI corresponding to the TMGI is obtained from the cluster server before the request message for monitoring the TMGI is sent to the Relay node, where the SAI is used for And prompting the relay node to determine, according to the SAI, a serving cell that performs monitoring processing on the TMGI, and send the acquired SAI corresponding to the TMGI to the Relay node.
  • the embodiment of the present invention provides a data processing device, which is used to implement the foregoing embodiments and preferred embodiments, and has not been described again.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 5 is a block diagram of a data processing apparatus according to an embodiment of the present invention. As shown in FIG. 5, the method includes:
  • the first receiving module 52 is configured to receive a request message for monitoring the temporary user group identifier TMGI sent by the user equipment, where the request message carries the layer 2 destination address corresponding to the TMGI and the TMGI;
  • the first sending module 54 is configured to send the received enhanced multicast and multicast service eMBMS data corresponding to the TMGI to the user through the PC5 interface, if the TMGI is monitored according to the request message.
  • the device wherein the layer 2 destination address on the PC5 interface is set to the layer 2 group identifier.
  • FIG. 6 is a block diagram of a data processing apparatus according to a preferred embodiment of the present invention. As shown in FIG. 6, the apparatus further includes:
  • the feedback module 62 is configured to feed back a response message to the user equipment, where the response message carries a message indicating that the user equipment resends the request message after a predetermined time is exceeded.
  • FIG. 7 is a block diagram 2 of a data processing apparatus according to a preferred embodiment of the present invention. As shown in FIG. 7, the apparatus further includes:
  • the interception processing module 72 is configured to perform a snooping process on the TMGI according to the request message.
  • FIG. 8 is a block diagram 3 of a data processing apparatus according to a preferred embodiment of the present invention. As shown in FIG. 8, the apparatus further includes:
  • the determining module 82 is configured to carry the service area identifier corresponding to the TMGI in the request message.
  • the serving cell that performs the interception process on the TMGI is determined according to the SAI.
  • the determining module 82 includes: a determining unit, configured to determine, according to the SAI, whether the service area of the current serving cell is consistent with the SAI; and the first determining unit is configured to determine, in a case that the determination result is yes, the current serving cell The serving cell that performs the monitoring process on the TMGI; and/or the second determining unit is configured to determine, in the case that the determination result is negative, the serving cell in the predetermined range of the current serving cell to perform the monitoring process on the TMGI The service area.
  • FIG. 9 is a second block diagram of a data processing apparatus according to an embodiment of the present invention. As shown in FIG. 9, the method includes:
  • the second sending module 92 is configured to send, to the Relay node, a request message for monitoring the temporary user group identifier TMGI, where the request message carries the TMGI and the layer 2 group identifier corresponding to the TMGI;
  • the second receiving module 94 is configured to receive the enhanced multicast and multicast service eMBMS data sent by the Relay node by using the corresponding PC5 interface of the layer 2 group identifier, where the layer 2 destination address on the PC5 interface is set to the The layer 2 group identifies that the eMBMS data is sent by the Relay node in the case that the TMGI is monitored according to the request message.
  • FIG. 10 is a block diagram 4 of a data processing apparatus according to a preferred embodiment of the present invention. As shown in FIG. 10, the apparatus further includes:
  • the second obtaining module 102 is configured to obtain, from the cluster server, the service area identifier SAI corresponding to the TMGI, where the SAI is used to prompt the relay node to determine a serving cell that performs monitoring processing on the TMGI according to the SAI;
  • the third sending module 104 is configured to send the acquired SAI corresponding to the TMGI to the Relay node.
  • FIG. 11 is a schematic diagram of point-to-multipoint communication of D2D according to an embodiment of the present invention. As shown in FIG. 11, terminal 1, terminal 2 and terminal 3 are located in the same communication group, and the following steps are included:
  • the terminal 1, the terminal 2, and the terminal 3 configure their own group related information, such as the layer 2 group identifier, and fill in the destination layer 2 address and the layer 2 user identifier when the group broadcasts, and fill in the original layer when used for group broadcasting.
  • group related information such as the layer 2 group identifier, and fill in the destination layer 2 address and the layer 2 user identifier when the group broadcasts, and fill in the original layer when used for group broadcasting.
  • This information can be statically configured on the terminal. The user can use it when there is no coverage area. It can be obtained from the network side when the user is in the coverage area.
  • step S1104 the terminal 1, the terminal 2, and the terminal 3 obtain the radio resource information of the group communication.
  • the terminal obtains the radio resource parameters of the communication when the terminal is in the coverage area.
  • the communication calling party terminal 1 obtains the transmitted resource information, and the communication acceptor terminal 2 and the terminal 3 obtain the received resource information.
  • step S1106 the terminal 1 performs the D2D communication broadcast by using the obtained transmission resource information
  • the destination layer 2 address is the layer 2 group identifier
  • the source layer 2 address is the layer 2 user identifier of the terminal 1
  • the destination layer 3 address is the layer 3 group IP. Multicast address.
  • the terminal 2 and the terminal 3 use the obtained received resource information to listen to the D2D communication broadcast, and first determine whether or not they are within the group indicated by the destination layer 2 address, and then continue.
  • the terminal 2 and the terminal 3 also use the appropriate layer 2 destination address together with the layer 2 source address to perform authentication and decryption operations using an appropriate security algorithm.
  • Terminal 2 and terminal 3 then receive the point-to-multipoint broadcast that terminal 1 sends via the PC5 interface.
  • the Relay node can accept eMBMS broadcasts from the base station, and also supports single-point to multi-point D2D communication between the remote terminals.
  • the remote terminal receives the eMBMS broadcast through the Relay node, and obtains the eMBMS broadcast data from the Relay node through the PC5 interface.
  • FIG. 12 is a flowchart of data processing by using a relay according to an embodiment of the present invention. As shown in FIG. 12, the security protection on the PC5 interface is not considered in the process, and the following steps are included:
  • step S1202 the remote terminal selects a suitable Relay node by listening to the broadcast of the Relay node, and obtains an IP address from the Relay node.
  • the Relay node needs to configure itself or obtain the layer 2 user identifier from the network side.
  • Step S1204 The remote terminal interacts with the cluster communication server to complete registration, and obtains related configuration information, such as a group identifier TMGI, a layer 2 group identifier, a group security related parameter, and the like from the cluster server. In the non-coverage area, the terminal can also use the locally configured related parameters for group communication.
  • related configuration information such as a group identifier TMGI, a layer 2 group identifier, a group security related parameter, and the like.
  • the terminal can also use the locally configured related parameters for group communication.
  • Step S1206 The remote terminal initiates a TMGI listening request to the Relay node, where the message carries the requested TMGI and the corresponding layer 2 group identifier, and the layer 2 group identifier is obtained from the cluster communication server in step S1204.
  • Step S1208 The Relay node saves the TMGI and the corresponding layer 2 group identifier, and returns a far terminal TMGI listening response.
  • the response message carries a timer, indicating that the remote terminal needs to re-initiate the TMGI listening request after the timer expires.
  • Step S1210 The Relay node starts to monitor the base station broadcast in the current camping cell, whether there is a requested TMGI related radio broadcast;
  • Step S1212 If the Relay node monitors that the base station has a TMGI related broadcast, the Relay node notifies the remote terminal that there is currently a TMGI related broadcast through the PC5 interface. In an optional embodiment, if only one user requests the TMGI broadcast, the message is unicast. If two or more remote terminals request the same TMGI broadcast, the Relay node may be similar to the instance 3. Multicast to send this message.
  • Step S1214 the Relay node starts to receive the eMBMS data related to the TMGI, and performs a point-to-multipoint broadcast through the PC5 interface, and the layer 2 address of the data packet sent on the PC5 interface is the layer 2 group identifier corresponding to the TMGI, and the source The address is the layer 2 user ID of the obtained Relay node.
  • the remote terminal After receiving the broadcast, the remote terminal will check the destination layer 2 group identifier of the data packet, and if the local remote terminal is in the group, accept the data packet.
  • the remote node can accept eMBMS data relayed through the Relay node.
  • FIG. 13 is a flowchart of acquiring a key according to point-to-multipoint communication in the related art, as shown in FIG. 13, including the following steps:
  • step S1302 the UE1 and the proximity server perform service authorization.
  • Step S1304 The UE1 sends a key request to the D2D key management server, where the layer 2 group identifier of the group in which the user is located and the security algorithm supported by the terminal.
  • the group ID of the group in which the user is located is a 24-bit layer 2 address.
  • Step S1306 The D2D key management server returns a response message to the UE1, with parameters such as a group user identifier allocated to the UE1, a PMK (ProSe MIKEY Key) of the D2D key management server, a PMK identifier, a validity period timer, and an encryption algorithm.
  • the group user ID uniquely identifies the user within the group and is also a 24-bit layer 2 address.
  • the PMK is used for communication between the subsequent UE and the D2D key management server using the MICKEY mechanism.
  • Step S1308 The UE1 and the D2D key management server use the MIKEY mechanism to communicate, and the UE1 acquires a PGK (ProSe Group Key) and a PGK identifier associated with the group identifier and a validity period timer.
  • PGK ProSe Group Key
  • step S1310 the UE2 performs service authorization with the proximity communication server.
  • Step S1312 - Step S1316 is similar to the foregoing steps S1302-S1308.
  • the UE 2 After the authentication and authorization, the UE 2 also obtains the PMK, the PMK identifier, and the PGK and PGK identifiers from the D2D key management server.
  • step S1318 - step S1320 UE1 and UE2 derive PTK (ProSe Traffic Key) and PEK (ProSe Encryption Key) according to the group user identifier obtained according to the PGK, and then packet data convergence protocol layer (Packet Data Convergence Protocol, PDCP for short)
  • PTK ProSe Traffic Key
  • PEK ProSe Encryption Key
  • the layer protects the user data packet according to the PEK.
  • the related PDCP data packet header is the PGK identifier and the PTK identifier, as shown in Table 1 below.
  • the terminal then broadcasts, and the layer 2 destination address of the broadcast is the group standard in steps S1304 and S1312.
  • the source address is the group user ID in S1306 and S1314.
  • the receiver After receiving the encrypted data packet, the receiver obtains the group identifier and the group user identifier according to the destination address and the source address of the layer 2, learns the PGK identifier and the PTK identifier according to the PDCP layer header, learns the PGK according to the PGK identifier, and then calculates the corresponding PTK and PEK. And then decrypt the encrypted packet.
  • the Relay node can receive eMBMS broadcasts from the base station, and can also support single-point to multi-point D2D communication between the remote terminals, but how the remote terminal accepts the eMBMS broadcast through the Relay node, which has not been detailed yet.
  • the solution also does not consider how the Relay node encrypts broadcast packets on the PC5 interface.
  • FIG. 14 is a flowchart of performing encryption in a data processing process according to an embodiment of the present invention. As shown in FIG. Security protection on the interface, including the following steps:
  • step S1402 the remote terminal selects a suitable Relay node by listening to the broadcast of the Relay node, and obtains an IP address from the Relay node.
  • the Relay node needs to configure itself or obtain the layer 2 user identifier from the network side.
  • Step S1404 interacting with the cluster communication server, completing registration, and obtaining relevant configuration information, such as a group identifier TMGI, a layer 2 group identifier, and a group security related parameter, from the cluster server.
  • relevant configuration information such as a group identifier TMGI, a layer 2 group identifier, and a group security related parameter
  • Step S1406 The remote terminal sends a key request to the D2D key management server through the Relay node, where the message carries a layer 2 group identifier and a security algorithm supported by the terminal.
  • Step S1408 The D2D key management server returns a response message to the remote terminal, where the group user identifier assigned to the remote terminal, the PMK of the D2D key management server, the PMK identifier, the validity period timer, and the encryption algorithm are included.
  • the group user ID uniquely identifies the user within the group and is also a 24-bit layer 2 address.
  • the PMK is used for communication between the subsequent UE and the D2D key management server using the MICKEY mechanism.
  • step S1410 the remote terminal and the D2D key management server use the MIKEY mechanism for communication, and acquire the PGK and PGK identifiers associated with the group identifier and the expiration timer.
  • Step S1412 The remote terminal initiates a TMGI listening request to the Relay node, where the message carries the requested TMGI, the layer 2 group identifier, and optionally, the D2D key management server.
  • Step S1414-Step S1418 similar to steps S1406-S1410, the Relay node sends a key request to the D2D key management server, acquires parameters such as the PMK, the PMK identifier, and the group user identifier corresponding to the group, and obtains the group through the MIKEY process. PGK, PGK identification and expiration timer. If there are multiple users in the group requesting to listen to the TMGI, step S1414-step S1418 is only executed once.
  • Step S1420 the Relay returns the far terminal TMGI listening response, and the response message has a timing
  • the device indicates that the remote terminal needs to re-initiate the TMGI listening request after the timer expires.
  • step S1422 the Relay node starts to listen to the base station broadcast, whether there is a requested TMGI related broadcast.
  • Step S1424 If the Relay node monitors that the base station has a TMGI related broadcast, the Relay node notifies the remote terminal that there is currently a TMGI related broadcast through the PC5 interface. If only one user requests the TMGI broadcast, the message is unicast. If two or more remote terminals request the same TMGI broadcast, the Relay node can send the message through the similar multicast of instance 3.
  • Step S1426 the Relay node starts to receive the eMBMS data related to the TMGI, and performs a point-to-multipoint broadcast through the PC5 interface, and the destination layer 2 address of the data packet sent on the PC5 interface is the layer 2 group identifier obtained in step S1412.
  • the source address is the group user identifier of the Relay node obtained in step S1416. After receiving the remote node, it determines whether it is within the group of the layer 2 destination group identifier.
  • the data packet is accepted and decrypted: first, according to the remote terminal, the group identifier and the group user identifier are obtained according to the layer 2 address, and then according to The PDCP layer header knows the PGK identifier and the PTK identifier, then learns the PGK according to the PGK identifier, then calculates the PTK according to the PGK, the group user identifier, and the PTK identifier, then calculates the PEK according to the PTK, and decrypts the encrypted data packet by using the PEK.
  • the remote node can accept the eMBMS data relayed through the Relay node, and the PC5 interface has security protection.
  • the Relay node may correspond to the TMGI.
  • the service area identifier determines in advance whether the camped cell can listen to the TMGI, and the method includes the following steps:
  • Step S1502 The remote terminal and the cluster communication server perform interaction, complete registration, and obtain relevant configuration information from the cluster server.
  • the SAI corresponding to the TMGI is acquired, and the SAI is obtained.
  • the cell broadcast parameter includes the SAI.
  • the terminal can determine whether the cell can receive the cluster broadcast corresponding to the TMGI by reading the SAI parameter.
  • Step S1504 The remote terminal initiates a TMGI interception request to the Relay node, and the message carries the SAI corresponding to the TMGI in addition to the TMGI and/or the layer 2 group identifier.
  • Step S1506 After receiving the request, the Relay node listens to the broadcast message of the base station, and determines whether the current serving cell and the requested serving cell are consistent.
  • Step S1508 if consistent, indicating that the local area can listen to the requested TMGI broadcast, the Relay node returns a remote terminal TMGI listening response, and the response message carries a timer indicating that the remote terminal needs to re-initiate the TMGI monitoring after the timer expires. request. If they are inconsistent, listen to the Relay node Whether other nearby cell broadcasts the SAI, if any, camps in advance to the corresponding neighboring cell and returns the far terminal TMGI listening response. If the nearby cell does not broadcast the SAI, indicating that the current location of the Relay node cannot be monitored by the TMGI broadcast, the Relay node may reject the TMGI listening request of the far terminal.
  • the Relay node can know in advance whether the current area can monitor the TMGI, or camp in advance to other base stations that can hear the TMGI broadcast.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above technical solution of the present invention can be applied to the field of communications, and solves the problem that the related system does not have a basis for relay data transmission from the relay node to the terminal, and provides a basis for the relay node to the terminal to perform multicast data transmission.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un dispositif et un procédé de traitement de données. Le procédé consiste à : recevoir un message de demande qui est envoyé par un équipement d'utilisateur et utilisé pour la surveillance d'une identité de groupe mobile temporaire (TMGI), le message de demande portant la TMGI et une identité de groupe de couche 2 correspondant à la TMGI ; et lors de la détection de la TMGI en fonction du message de demande, envoyer des données de service de diffusion/multidiffusion multimédia amélioré (eMBMS) reçues, correspondant à la TMGI, à l'équipement d'utilisateur par l'intermédiaire d'une interface PC5, une adresse de destination de couche 2 sur l'interface PC5 étant définie comme étant l'identité de groupe de couche 2. La présente invention permet de résoudre le problème dans l'état de la technique selon lequel il n'existe pas de base pour la propagation de données depuis un nœud relais vers un terminal, fournissant ainsi la base pour la propagation de données de multidiffusion depuis le nœud relais vers le terminal.
PCT/CN2015/085466 2015-01-16 2015-07-29 Dispositif et procédé de traitement de données Ceased WO2016112678A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201510024332 2015-01-16
CN201510024332.8 2015-01-16
CN201510342667.4 2015-06-18
CN201510342667.4A CN106211087A (zh) 2015-01-16 2015-06-18 数据处理方法及装置

Publications (1)

Publication Number Publication Date
WO2016112678A1 true WO2016112678A1 (fr) 2016-07-21

Family

ID=56405199

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/085466 Ceased WO2016112678A1 (fr) 2015-01-16 2015-07-29 Dispositif et procédé de traitement de données

Country Status (1)

Country Link
WO (1) WO2016112678A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108243631A (zh) * 2016-10-27 2018-07-03 华为技术有限公司 一种接入网络的方法及设备
CN109101394A (zh) * 2018-07-09 2018-12-28 珠海格力电器股份有限公司 数据处理方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101340355A (zh) * 2007-07-03 2009-01-07 华为技术有限公司 一种多媒体广播/组播业务的实现方法、系统及装置
WO2013173323A1 (fr) * 2012-05-14 2013-11-21 Research In Motion Limited Maintien de continuité mbms
CN103428642A (zh) * 2013-07-16 2013-12-04 北京邮电大学 基于中继的簇内d2d多播方法
US20140286222A1 (en) * 2013-03-22 2014-09-25 Mediatek Inc. Group Communication over LTE eMBMS

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101340355A (zh) * 2007-07-03 2009-01-07 华为技术有限公司 一种多媒体广播/组播业务的实现方法、系统及装置
WO2013173323A1 (fr) * 2012-05-14 2013-11-21 Research In Motion Limited Maintien de continuité mbms
US20140286222A1 (en) * 2013-03-22 2014-09-25 Mediatek Inc. Group Communication over LTE eMBMS
CN103428642A (zh) * 2013-07-16 2013-12-04 北京邮电大学 基于中继的簇内d2d多播方法

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108243631A (zh) * 2016-10-27 2018-07-03 华为技术有限公司 一种接入网络的方法及设备
US10904763B2 (en) 2016-10-27 2021-01-26 Huawei Technologies Co., Ltd. Network access method and device
CN109101394A (zh) * 2018-07-09 2018-12-28 珠海格力电器股份有限公司 数据处理方法和装置
CN109101394B (zh) * 2018-07-09 2023-05-09 珠海格力电器股份有限公司 数据处理方法和装置

Similar Documents

Publication Publication Date Title
EP3107349B1 (fr) Procédé et dispositif de communication
EP3047696B1 (fr) Communication de dispositif à dispositif entre dispositifs de communication sans fil en utilisant identité de groupes et de l'application
CN112565315B (zh) 位置信息获取、位置服务配置方法和通信设备
CN114731720B (zh) 支持同时具有不同业务流量的多运营商的5g双连接机制
EP4354913A1 (fr) Procédé de transmission de données, équipement utilisateur, noeud de service et support de stockage
WO2014040506A1 (fr) Procédé et dispositif de découverte de terminal et de traitement de découverte
US20150341494A1 (en) Method, system, base station and cluster EPC for establishing group call context
WO2015149463A1 (fr) Procédé et appareil de traitement pour découverte d2d
WO2016107205A1 (fr) Procédé et dispositif pour une transmission de données dans des communications de relais
KR100836028B1 (ko) 멀티캐스트 브로드캐스트 서비스 제공 방법
KR20150084628A (ko) 이동 통신에서 ProSe그룹 통신 또는 공공 안전을 지원하기 위한 보안 방안 및 시스템
US9642115B2 (en) Method for implementing trunk service based on long term evolution and trunk user terminal
CN104885492A (zh) 侦听装置对装置通信
WO2016180117A1 (fr) Procédé et appareil de sélection de nœud relais dans un réseau de dispositif à dispositif
CN104956763B (zh) 用于设备到设备通信的方法和装置
CN104283602A (zh) 集群中继方法、装置及系统
CN105704641B (zh) 设备到设备d2d数据传输方法、装置及d2d ue
WO2016169232A1 (fr) Procédé, appareil et système d'authentification de multidiffusion de service d2d
CN106211087A (zh) 数据处理方法及装置
WO2016086419A1 (fr) Procédé, dispositif et système de diffusion/multidiffusion multimédia
WO2014106401A1 (fr) Procédé, système et équipement permettant de réaliser une session d'appel collectif de grappe en lte (évolution à long terme)
WO2016112678A1 (fr) Dispositif et procédé de traitement de données
WO2024037210A1 (fr) Procédé et appareil de communication de sécurité de diffusion
WO2015165224A1 (fr) Procédé et appareil de traitement d'autorisation, serveur de proximité et serveur d'abonné domestique
WO2014121599A1 (fr) Procédé et dispositif associé pour transférer des informations de charge de réseau cellulaire

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15877592

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15877592

Country of ref document: EP

Kind code of ref document: A1