[go: up one dir, main page]

WO2018103016A1 - 数据处理方法和设备 - Google Patents

数据处理方法和设备 Download PDF

Info

Publication number
WO2018103016A1
WO2018103016A1 PCT/CN2016/108895 CN2016108895W WO2018103016A1 WO 2018103016 A1 WO2018103016 A1 WO 2018103016A1 CN 2016108895 W CN2016108895 W CN 2016108895W WO 2018103016 A1 WO2018103016 A1 WO 2018103016A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
processed
relay
information
resource
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/CN2016/108895
Other languages
English (en)
French (fr)
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.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
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 to JP2019530393A priority Critical patent/JP7101675B6/ja
Priority to US16/466,007 priority patent/US10959211B2/en
Priority to EP16923238.6A priority patent/EP3547791B1/en
Priority to CN201680090848.5A priority patent/CN109964535B/zh
Priority to KR1020197018493A priority patent/KR20190092458A/ko
Priority to CN202210308959.6A priority patent/CN114978450A/zh
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to PCT/CN2016/108895 priority patent/WO2018103016A1/zh
Priority to EP21184574.8A priority patent/EP3914038A1/en
Priority to TW106141706A priority patent/TWI746710B/zh
Publication of WO2018103016A1 publication Critical patent/WO2018103016A1/zh
Anticipated expiration legal-status Critical
Priority to US17/171,926 priority patent/US20210168765A1/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/02—Selection of wireless resources by user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/155—Ground-based stations
    • H04B7/15528—Control of operation parameters of a relay station to exploit the physical medium
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user

Definitions

  • the present application relates to the field of communications and, more particularly, to a data processing method and apparatus.
  • D2D Device-to-Device
  • the data transmission between the network device and the remote terminal device can be assisted by the D2D relay.
  • the D2D communication mode can be adopted between the terminal device for the D2D relay and the remote terminal, and the terminal for the D2D relay can be used.
  • a cellular communication mode is used between the device and the network device, wherein the terminal device for communicating the auxiliary network device with the terminal device may be referred to as a relay terminal device, and the relay terminal device may also be non-assisted with other terminal devices. The way to communicate directly with network devices.
  • the embodiment of the present application provides a data processing method and device, which can accurately identify whether the acquired data is relay data.
  • a data processing method comprising:
  • the receiving end acquires data to be processed
  • determining whether the to-be-processed data is relay data, according to the information carried in the to-be-processed data includes:
  • media access control layer Media Access The information carried by the Protocol Data Unit (PDU) in the Control, MAC) layer, the information carried by the PDU in the Radio Link Control (RLC) layer, or the information carried in the PDU in the adaptation layer. And determining whether the to-be-processed data is relay data.
  • PDU Protocol Data Unit
  • RLC Radio Link Control
  • determining whether the to-be-processed data is relay data, according to the information carried in the to-be-processed data includes:
  • the relay information indication field included in the to-be-processed data indicates that the to-be-processed data is relay data, determining that the to-be-processed data is relay data;
  • the identifier of the remote terminal When the identifier of the remote terminal is carried in the adaptation layer of the data to be processed, determining that the to-be-processed data is relay data; or
  • the relay information indication field is carried in a physical layer control channel or a physical layer traffic channel.
  • the relay information indication field is carried in Downlink Control Information (DCI) or Uplink Control Information (UCI) through a physical control channel; or
  • DCI Downlink Control Information
  • UCI Uplink Control Information
  • the relay information indication field is carried by a front end of physical traffic channel data in a physical layer traffic channel.
  • determining whether the to-be-processed data is relay data, according to the information carried in the message used for applying the resource to the to-be-processed data includes:
  • BSR Buffer Status Report
  • determining whether the to-be-processed data is relay data, according to the information carried in the BSR used for applying the resource to the to-be-processed data includes:
  • a relay data indication information for indicating a resource for relaying data, identification information of a remote terminal, or relaying specific logical channel information, determining that the to-be-processed data is a relay data.
  • the resource information occupied by the message used for applying for the resource is performed according to the to-be-processed data, and determining whether the to-be-processed data is relay data includes:
  • Determining whether the to-be-processed data is relay data according to at least one of a time domain resource, a frequency domain resource, a code domain resource, and a power resource occupied by the scheduling request used for applying the resource to the to-be-processed data.
  • Data including:
  • the time domain resource occupied by the scheduling request is a relay-specific time domain resource, and/or the frequency domain resource occupied by the scheduling request is a relay-specific frequency domain resource, and/or a code occupied by the scheduling request.
  • the domain resource is a relay-specific code domain resource, and/or the airspace resource occupied by the scheduling request is a relay-specific airspace resource, and/or the power resource occupied by the scheduling request is a relay-specific power resource. Determining that the to-be-processed data is relay data.
  • determining whether the to-be-processed data is relay data, according to the information required to obtain the to-be-processed data includes:
  • C-RNTI Cell Radio Network Temporary Identity
  • determining whether the to-be-processed data is relay data, according to the C-RNTI used to obtain the to-be-processed data includes:
  • the C-RNTI used for acquiring the to-be-processed data is a relay-specific C-RNTI, it is determined that the to-be-processed data is relay data.
  • the receiving end is a relay terminal device, and performing operations on the to-be-processed data according to whether the to-be-processed data is relay data, including:
  • the to-be-processed data is relay data
  • the adaptation layer for processing before submitting the to-be-processed data to the adaptation layer for processing, submit the to-be-processed data to an adaptation layer for processing, and after being processed by the adaptation layer
  • the pending data is relayed to the remote terminal or network device;
  • the data to be processed is submitted to the adaptation layer for processing, and the data to be processed is identified as relay data, the data is relayed to the remote terminal or the network device.
  • the receiving end is a network device, and performing operations on the to-be-processed data according to whether the to-be-processed data is relay data, including:
  • the to-be-processed data is relay data
  • the to-be-processed data before submitting the to-be-processed data to the adaptation layer for processing, submit the to-be-processed data to an adaptation layer for processing, and after being processed by the adaptation layer
  • the pending data is submitted to the packet data convergence protocol (Packet Data) Convergence Protocol, PDCP) layer processing; or
  • the data to be processed is submitted to the adaptation layer for processing, and the data to be processed is identified as relay data, the data to be processed is delivered to the PDCP layer for processing.
  • performing operations on the to-be-processed data according to whether the to-be-processed data is relay data including:
  • the to-be-processed data is delivered to the PDCP layer for processing.
  • the to-be-processed data belongs to a layer two message.
  • a data processing apparatus comprising means for performing the method of the first aspect or any alternative implementation thereof.
  • a data processing apparatus comprising a processor and a memory.
  • the memory stores program code for calling the program code stored in the memory to execute the method in the first aspect or various implementation manners thereof.
  • a computer readable medium storing program code for execution by a terminal device, the program code comprising instructions for performing the method of the first aspect or various implementations thereof .
  • the information carried in the to-be-processed data the information carried in the message used for applying the resource to the to-be-processed data, the message used for applying the resource to the to-be-processed data is occupied. And determining at least one of the resource information and the information required to obtain the to-be-processed data, determining whether the to-be-processed data is relay data; and determining whether the to-be-processed data is relay data, so that The operation data is the relay data, and the operation for the data to be processed is performed.
  • FIG. 1 is a schematic diagram of a wireless communication system in accordance with an embodiment of the present application.
  • FIGS. 2a and 2b are schematic diagrams of a protocol stack in accordance with an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a data processing method according to an embodiment of the present application.
  • FIG. 4 is a schematic block diagram of a data processing device in accordance with an embodiment of the present application.
  • FIG. 5 is a schematic block diagram of a data processing device in accordance with an embodiment of the present application.
  • system and “network” are used interchangeably herein.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the character "/" in this article generally indicates that the contextual object is an "or" relationship.
  • Network device 100 can be a device that communicates with a terminal device. Each network device 100 can provide communication coverage for a particular geographic area and can communicate with terminal devices located within the coverage area.
  • the network device 100 may be a base station (Base Transceiver Station (BTS) in a GSM system or a Code Division Multiple Access (CDMA) system, or may be a base station (NodeB, NB) in a WCDMA system, or may be An evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device may be a relay station, an access point, In-vehicle devices, wearable devices, network-side devices in future 5G networks, or network devices in the future evolution of the Public Land Mobile Network (PLMN).
  • BTS Base Transceiver Station
  • CDMA Code Division Multiple Access
  • NodeB NodeB
  • NB base station
  • An evolved base station Evolutional Node B, eNB or eNodeB
  • CRAN Cloud Radio Access Network
  • the network device may be a relay station, an access point, In-vehicle devices, wearable devices
  • the wireless communication system 100 also includes a plurality of terminal devices, such as terminal devices 121, 122, 123, 124, 125, and 126 as shown in FIG.
  • the terminal device can be mobile or fixed.
  • the terminal device may refer to an access terminal, a user equipment (User Equipment, UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, and a user agent. Or user device.
  • UE User Equipment
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), A handheld device having a wireless communication function, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a future 5G network, or a terminal device in a future evolved PLMN, or the like.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • FIG. 1 exemplarily shows a network device and six terminal devices.
  • the wireless communication system 100 may include multiple network devices and other numbers of terminal devices, which are not limited in this embodiment of the present application.
  • the wireless communication system 100 may further include other network entities such as a Mobile Management Entity (MME), a Serving Gateway (S-GW), and a Packet Data Network Gateway (P-GW).
  • MME Mobile Management Entity
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • embodiments of the present application are not limited thereto.
  • the terminal device can communicate in a cellular communication mode or a D2D communication mode, wherein in the cellular communication mode, the terminal device can communicate with other terminal devices through the network device; in the D2D communication mode, the terminal device can pass the D2D link Communicate directly with other terminal devices.
  • the terminal device 121 and the terminal device 125 may be referred to as remote terminal devices, and the terminal device 121 and the terminal device 125 may communicate with the network device 110 through the relay terminal devices 122 and 124, respectively.
  • the terminal device 122 and the terminal device 124 may relay data between the remote terminal device 121 and the remote terminal device 125 and the network device 110.
  • the terminal device 122 and the terminal device 124 may be referred to as a relay terminal device.
  • the relay terminal devices 122 and 124 can also directly communicate with the network device in a manner that does not assist other terminal devices; the terminal device 123 can communicate with the network device 110 without relaying the terminal device, and does not need to relay other terminal devices with Network device 110 communicates.
  • the terminal devices 122, 123, 124, and 126 and the network device 110 have a Uu interface, and can communicate with the network device 110 by using a cellular communication technology.
  • the relay terminal device and the remote terminal device have a PC5 interface, and the D2D communication technology is used for communication.
  • the D2D communication technology may be specifically a bypass (SideLink, SL) technology in LTE, or may be a WIFI in a WLAN.
  • the embodiment of the present application does not limit the technology, such as the Bluetooth, or other D2D communication technologies.
  • the terminal device 121 and the terminal device 125 can also directly communicate with the network device 110 through the relay terminal device. At this time, the terminal device 121 and the terminal device 125 and the network device have a Uu interface, and can adopt a cellular communication technology and Network device 110 communicates.
  • the relay terminal device and the remote terminal device may use the layer 2 relay mode to perform data transmission.
  • the Uu interface and the PC5 interface may use Layer 2 PDUs (for example, MAC PDUs, RLC PDU or PDCP PDU) is relayed.
  • Layer 2 PDUs for example, MAC PDUs, RLC PDU or PDCP PDU
  • Figure 2a shows the protocol stack between the remote terminal device, the relay terminal device, the base station and the core network in transmitting data.
  • Figure 2b shows the protocol stack used by the terminal device to transmit user plane data between the base station, the serving gateway and the packet data network gateway.
  • the remote terminal device, the relay terminal device, and the layer 2 of the network device have an adaptation layer.
  • the remote terminal device and the relay terminal device may transmit a packet processed by the adaptation layer and the lower layer corresponding to the D2D communication technology, where the D2D communication technology is specifically LTE.
  • the lower layer may be specifically a MAC layer and a physical (PHY) layer, and if the D2D communication technology is other communication technologies, for example, Bluetooth or WIFI technology, etc., the lower layer
  • the layer corresponding to the MAC layer and the physical layer in the other communication technologies; the packet processed by the PHY layer, the MAC layer, the RLC layer, and the adaptation layer may be transmitted between the relay terminal device and the base station; the remote terminal device When directly communicating with the base station, the packet processed by the PDCP layer can be transmitted; when communicating with the core network, the remote terminal device can transmit the packet to be processed by the network protocol (Internet Protocol, IP) layer.
  • IP Internet Protocol
  • the adaptation layer may be located between the RLC layer and the PDCP, which is not limited in this embodiment of the present application.
  • a packet processed by the L1 (Layer 1, Layer 1), MAC, RLC, and PDCP layers can be transmitted between the terminal device and the base station, and the base station and the serving gateway can transmit through L1 and L2 (Layer 2).
  • Layer 2 UDP/IP and GTP-U layer processed messages, between the service gateway and the packet data network gateway can be transmitted through L1, L2, UDP/IP (UDP is User Datagram Protocol) And GTP-U (for the user plane GPRS (General Packet Radio Service, General Packet Radio Service) tunneling protocol, GPRS Tunneling Protocol for the user plane) layer processed messages.
  • UDP/IP User Datagram Protocol
  • GTP-U for the user plane GPRS (General Packet Radio Service, General Packet Radio Service) tunneling protocol, GPRS Tunneling Protocol for the user plane) layer processed messages.
  • the processing performed by the terminal device when communicating as the relay terminal device with the network device and the remote terminal device is different from the processing performed when the non-relay terminal device communicates with the network device, and the network The device is different from the operation of processing the non-relay data.
  • the embodiment of the present application provides a data processing method, and the relay terminal device and the network device can identify whether the acquired data is a relay. Data, and perform the corresponding operation for whether the data is relay data.
  • FIG. 3 is a schematic diagram of a data processing method 200 provided by an embodiment of the present application.
  • the method 200 can be applied to the wireless communication system 100 described above, but the embodiment of the present application is not limited thereto.
  • the method 200 includes the following.
  • the receiving end acquires data to be processed.
  • the method 200 can be applied to the relay transmission of the uplink data, that is, the remote terminal device transmits the uplink data to the network device by using the relay terminal device, and the device at the transmitting end is specifically the remote terminal device, and the receiving end can be Relay terminal device or network device.
  • the method 200 is also applicable to the relay transmission of the downlink data, that is, the network device transmits the downlink data to the remote terminal device by using the relay terminal device, and at this time, the sending end device is a network device, and the receiving end may be in the middle.
  • the terminal device is not limited in this embodiment.
  • the to-be-processed data belongs to a Layer 2 encapsulated packet.
  • the information carried in the message used for applying the resource to the to-be-processed data the information carried in the message used for applying the resource to the to-be-processed data, the resource information occupied by the message used for applying for the resource to be processed, and acquiring the to-be-processed data At least one of the information required to process the data, determining whether the data to be processed is relay data.
  • determining the to-be-processed data according to the data in the physical layer of the data to be processed, the information carried by the PDU in the MAC layer, the information carried by the PDU in the RLC layer, or the information carried in the PDU in the adaptation layer. Whether it is relay data.
  • the data to be processed is determined to be the relay data according to the information of the bearer in the to-be-processed data, where the data to be processed is determined to be the relay data according to the information of the bearer in the data to be processed. It is also possible to combine other information, for example, information required to acquire the data to be processed, and determine whether the data to be processed is relay data.
  • the relay information indication field included in the to-be-processed data indicates that the to-be-processed data is relay data, it is determined that the to-be-processed data is relay data.
  • the relay information indication field is carried in a physical layer control channel or a physical layer traffic channel.
  • the relay information indication field is carried in a DCI or a UCI through a physical control channel; or the relay information indication field is carried in a front end of the physical service channel data in the physical layer traffic channel, where the front end may be Refers to the front of the physical traffic channel data in the time domain.
  • the relay information indication field may be a one-bit field.
  • 1 may represent that the to-be-processed data is relay data
  • 0 may represent that the to-be-processed data is non-relay data.
  • the data to be processed is determined to be relay data.
  • the to-be-processed data is determined to be relay data.
  • the specific bearer identification information may be specified by a protocol, or may be configured by a network device.
  • BSR Buffer State Report
  • the relay data can be identified by combining other information, for example, information carried in the data to be processed.
  • the data to be processed is determined to be Relay data.
  • the BSR may have a relay data indication field, and if the information carried by the relay data indication field is used for the requested resource for relaying data, determining that the to-be-processed data corresponding to the BSR is relay data,
  • the relay data indication field may be a 1-bit field. For example, 1 may represent the applied resource for relaying data, and 0 may represent the applied resource for relaying data.
  • determining whether the to-be-processed data is relay data wherein the resource information occupied by the scheduling request used for applying for the resource may be used to identify the relay data only according to the to-be-processed data, and may also be combined with other information to perform relay data. Identification, no specific limitation here.
  • the time domain resource occupied by the scheduling request is a relay specific time domain resource
  • the frequency domain resource occupied by the scheduling request is a relay specific frequency domain resource, and/or occupied by the scheduling request.
  • the code domain resource is a relay-specific code domain resource
  • the airspace resource occupied by the scheduling request is a relay-specific airspace resource
  • the power resource occupied by the scheduling request is a relay-specific power resource, and is determined.
  • the data to be processed is relay data.
  • the relay specific time domain resource, and/or the relay specific frequency domain resource, and/or the relay specific code domain resource, and/or the relay specific airspace resource, and/or Or the specific power resource of the relay may be specified by a protocol, or may be configured by a network device.
  • the resource of the scheduling request application may be used to transmit the BSR, and the BSR may carry the data volume of the data to be processed, and is used to apply for a specific transmission resource for the data to be processed.
  • determining whether the to-be-processed data is relay data according to the C-RNTI used for acquiring the to-be-processed data where the relay data may be identified only according to the C-RNTI, or may be combined with other information.
  • the identification of data is not specifically limited herein.
  • the C-RNTI used for acquiring the to-be-processed data is a relay-specific C-RNTI, determining that the to-be-processed data is relay data.
  • the relay-specific C-RNTI may be specified by a protocol, or may be configured by a network device.
  • the identifier information of the remote terminal carried in the adaptation layer in the data to be processed, the bearer identification information in the adaptation layer, and the message used to apply for the resource for the to-be-processed data are used.
  • the resource information that is occupied, and/or the information required to obtain the data to be processed, and the judgment of the relay data may be referred to as implicitly indicating whether the data is relay data, and the dedicated relay data may be used to indicate resources, which may be reduced. Resource overhead.
  • an operation for the to-be-processed data is performed according to whether the to-be-processed data is relay data.
  • the receiving end is a relay terminal device, and when the relay terminal device determines that the to-be-processed data is relay data before submitting the to-be-processed data to the adaptation layer for processing, the to-be-processed data is delivered to the The adaptation layer performs processing, and relays the to-be-processed data processed by the adaptation layer to the remote terminal or the network device.
  • the receiving end is a relay terminal device, and after the relay terminal device submits the to-be-processed data to the adaptation layer for processing, and identifies that the to-be-processed data is relay data, the data is relayed to the data.
  • Remote terminal or network device After the relay terminal device submits the to-be-processed data to the adaptation layer for processing, and identifies that the to-be-processed data is relay data, the data is relayed to the data.
  • Remote terminal or network device after the relay terminal device submits the to-be-processed data to the adaptation layer for processing, and identifies that the to-be-processed data is relay data.
  • the receiving end is a network device, and before the network device submits the to-be-processed data to the adaptation layer for processing, determining that the to-be-processed data is relay data, and submitting the to-be-processed data to the adaptation layer. Processing, and processing the to-be-processed data processed by the adaptation layer to the PDCP layer for processing.
  • the receiving end is a network device, and after the network device submits the to-be-processed data to the adaptation layer for processing, and identifies that the to-be-processed data is the relay data, the to-be-processed data is delivered to the PDCP layer. deal with.
  • the receiving end may be a network device or a relay terminal device.
  • the information carried in the to-be-processed data the information carried in the message used for applying the resource to the to-be-processed data, the message used for applying the resource to the to-be-processed data is occupied. And determining at least one of the resource information and the information required to obtain the to-be-processed data, determining whether the to-be-processed data is relay data; and determining whether the to-be-processed data is relay data, so that The operation data is the relay data, and the operation for the data to be processed is performed.
  • FIG. 4 is a schematic block diagram of a data processing device 400 in accordance with an embodiment of the present application. As shown in FIG. 4, the data processing device 400 includes an acquisition unit 410, a determination unit 420, and a processing unit 430.
  • the obtaining unit 410 is configured to acquire data to be processed
  • the determining unit 420 is configured to: according to the information carried in the to-be-processed data, information carried in a message used to apply for a resource to the to-be-processed data
  • the processing unit 430 is configured to: according to at least one of the resource information occupied by the message used for the application for the resource, and the information required to obtain the data to be processed, to determine whether the data to be processed is relay data;
  • the data to be processed is whether it is relay data, and an operation for the data to be processed is performed.
  • the determining unit 420 is specifically configured to:
  • the information carried by the protocol data unit PDU in the MAC layer of the medium access control layer, the information carried by the PDU in the radio link control RLC layer, or the PDU in the adaptation layer determines whether the to-be-processed data is relay data.
  • the determining unit 420 is specifically configured to:
  • the relay information indication field included in the to-be-processed data indicates that the to-be-processed data is relay data, determining that the to-be-processed data is relay data;
  • the identifier of the remote terminal When the identifier of the remote terminal is carried in the adaptation layer of the data to be processed, determining that the to-be-processed data is relay data; or
  • the relay information indication field is carried in a physical layer control channel or a physical layer traffic channel.
  • the relay information indication field is carried on a downlink control signal that passes through a physical control channel.
  • the relay information indication field is carried by a front end of physical traffic channel data in a physical layer traffic channel.
  • the determining unit 420 is specifically configured to:
  • Determining whether the to-be-processed data is relay data according to the information carried in the buffer status report BSR used for applying the resource to the to-be-processed data.
  • the determining unit 420 is specifically configured to:
  • a relay data indication information for indicating a resource for relaying data, identification information of a remote terminal, or relaying specific logical channel information, determining that the to-be-processed data is a relay data.
  • the determining unit 420 is specifically configured to:
  • Determining whether the to-be-processed data is relay data according to at least one of a time domain resource, a frequency domain resource, a code domain resource, and a power resource occupied by the scheduling request used for applying the resource to the to-be-processed data.
  • the determining unit 420 is specifically configured to:
  • the time domain resource occupied by the scheduling request is a relay-specific time domain resource, and/or the frequency domain resource occupied by the scheduling request is a relay-specific frequency domain resource, and/or a code occupied by the scheduling request.
  • the domain resource is a relay-specific code domain resource, and/or the airspace resource occupied by the scheduling request is a relay-specific airspace resource, and/or the power resource occupied by the scheduling request is a relay-specific power resource. Determining that the to-be-processed data is relay data.
  • the determining unit 420 is specifically configured to:
  • the determining unit 420 is specifically configured to:
  • the C-RNTI used for acquiring the to-be-processed data is a relay-specific C-RNTI, it is determined that the to-be-processed data is relay data.
  • the data processing device 400 is a relay terminal device, and the processing unit 430 is specifically configured to:
  • the to-be-processed data is relay data
  • the adaptation layer for processing before submitting the to-be-processed data to the adaptation layer for processing, submit the to-be-processed data to an adaptation layer for processing, and after being processed by the adaptation layer
  • the pending data is relayed to the remote terminal or network device;
  • the data to be processed is submitted to the adaptation layer for processing, and the data to be processed is identified as relay data, the data is relayed to the remote terminal or the network device.
  • the data processing device 400 is a network device, and the processing unit 430 is specifically configured to:
  • the to-be-processed data is relay data
  • the to-be-processed data before submitting the to-be-processed data to the adaptation layer for processing, submit the to-be-processed data to an adaptation layer for processing, and after being processed by the adaptation layer
  • the pending data is submitted to the PDCP layer for processing;
  • the data to be processed is submitted to the adaptation layer for processing, and the data to be processed is identified as relay data, the data to be processed is delivered to the PDCP layer for processing.
  • processing unit 430 is specifically configured to:
  • the to-be-processed data is delivered to the PDCP layer for processing.
  • the to-be-processed data belongs to a layer two message.
  • data processing device 400 can implement the method 300 shown in FIG. 3, and details are not described herein for brevity.
  • FIG. 4 is a schematic block diagram of a data processing device 500 in accordance with an embodiment of the present application.
  • the device 500 includes a processor 510 and a memory 520.
  • the memory 520 can store program code, and the processor 510 can execute the program code stored in the memory 520.
  • the device 500 can include a transceiver 530 that can be externally communicated by the transceiver 530.
  • the processor 510 can call the program code stored in the memory 520 to perform the corresponding operations in the method 300 shown in FIG. 3.
  • the processor 510 can call the program code stored in the memory 520 to perform the corresponding operations in the method 300 shown in FIG. 3.
  • the device 500 may be a terminal device, or may be a system chip that can be placed in the terminal device; or the device 500 may be a network device or a system chip that can be placed in the network device.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

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

Abstract

本申请实施例提供一种数据处理方法和设备，能够准确的识别获取到的数据是否是中继数据。该方法包括：接收端获取待处理数据；根据所述待处理数据中承载的信息、对所述待处理数据进行申请资源所用的消息中承载的信息，对所述待处理数据进行申请资源所用的消息占用的资源信息，以及获取所述待处理数据所需的信息中的至少一种，确定所述待处理数据是否为中继数据；根据所述待处理数据为是否为中继数据，执行针对所述待处理数据的操作。

Description

数据处理方法和设备 技术领域
本申请涉及通信领域，并且更具体地，涉及一种数据处理方法和设备。
背景技术
设备到设备(Device-to-Device，D2D)技术是指邻近的终端设备可以在近距离范围内通过直连链路的方式进行数据传输。
可以通过D2D中继辅助网络设备和远端终端设备之间的数据传输，此时，用于D2D中继的终端设备与远端终端之间可以采用D2D通信模式，而用于D2D中继的终端设备和网络设备之间使用蜂窝通信模式，其中，可以将用于辅助网络设备与终端设备进行通信的终端设备可以称为中继终端设备，该中继终端设备也可以以非辅助其他终端设备的方式直接与网络设备进行通信。
对于网络设备或中继终端设备而言，如何准确的识别获取到的数据是否是中继数据是一项亟待解决的问题。
发明内容
本申请实施例提供一种数据处理方法和设备，能够准确的识别获取到的数据是否是中继数据。
第一方面，提供了一种数据处理方法，包括：
接收端获取待处理数据；
根据所述待处理数据中承载的信息、对所述待处理数据进行申请资源所用的消息中承载的信息，对所述待处理数据进行申请资源所用的消息占用的资源信息，以及获取所述待处理数据所需的信息中的至少一种，确定所述待处理数据是否为中继数据；
根据所述待处理数据为是否为中继数据，执行针对所述待处理数据的操作。
可选地，根据所述待处理数据中承载的信息，确定所述待处理数据是否为中继数据，包括：
根据所述待处理数据的物理层中的数据、媒体接入控制层(Media Access  Control，MAC)层中的协议数据单元(Protocol Data Unit，PDU)承载的信息、无线链路控制(Radio Link Control，RLC)层中PDU承载的信息、或适配层中的PDU中承载的信息，确定所述待处理数据是否为中继数据。
可选地，根据所述待处理数据中承载的信息，确定所述待处理数据是否为中继数据，包括：
在所述待处理数据包括的中继信息指示字段指示所述待处理数据为中继数据时，确定所述待处理数据为中继数据；或
在所述待处理数据的适配层中携带远端终端的标识信息时，确定所述待处理数据为中继数据；或，
在所述待处理数据的适配层中携带承载标识信息时，确定所述待处理数据为中继数据；或，
在所述待处理数据的适配层中携带特定的承载标识信息时，确定所述待处理数据为中继数据。
可选地，所述中继信息指示字段承载于物理层控制信道中，或物理层业务信道中。
可选地，所述中继信息指示字段承载于通过物理控制信道的下行控制信息(Downlink Control Information，DCI)或上行控制信息(Uplink Control Information，UCI)中；或，
所述中继信息指示字段承载于物理层业务信道中的物理业务信道数据的前端。
可选地，根据对所述待处理数据进行申请资源所用的消息中承载的信息，确定所述待处理数据是否为中继数据，包括：
根据对所述待处理数据进行申请资源所用的缓存状态报告((Buffer Status Report，BSR)中携带的信息，确定所述待处理数据是否为中继数据。
可选地，根据对所述待处理数据进行申请资源所用的BSR中携带的信息，确定所述待处理数据是否为中继数据，包括：
在所述BSR中携带用于指示申请的资源用于中继数据的中继数据指示信息，远端终端的标识信息，或中继特定的逻辑信道信息时，确定所述待处理数据为中继数据。
可选地，根据所述待处理数据进行申请资源所用的消息占用的资源信息，确定所述待处理数据是否为中继数据，包括：
根据对所述待处理数据进行申请资源所用的调度请求占用的时域资源、频域资源、码域资源和功率资源中的至少一种，确定所述待处理数据是否为中继数据。
可选地，根据对所述待处理数据进行申请资源所用的调度请求占用的时域资源、频域资源、码域资源和功率资源中的至少一种，确定所述待处理数据是否为中继数据，包括：
在所述调度请求占用的时域资源为中继特定的时域资源，和/或所述调度请求占用的频域资源为中继特定的频域资源，和/或所述调度请求占用的码域资源为中继特定的码域资源，和/或所述调度请求占用的空域资源为中继特定的空域资源，和/或所述调度请求占用的功率资源为中继特定的功率资源时，确定所述待处理数据为中继数据。
可选地，根据获取所述待处理数据所需的信息，确定所述待处理数据是否为中继数据，包括：
根据获取所述待处理数据所用的小区无线网络临时标识(Cell Radio Network Temporary Identity，C-RNTI)，确定所述待处理数据是否为中继数据。
可选地，根据获取所述待处理数据所用的C-RNTI，确定所述待处理数据是否为中继数据，包括：
在获取所述待处理数据所用的C-RNTI为中继特定的C-RNTI时，确定所述待处理数据为中继数据。
可选地，所述接收端为中继终端设备，根据所述待处理数据为是否为中继数据，执行针对所述待处理数据的操作，包括：
在将所述待处理数据递交到适配层进行处理之前，确定所述待处理数据为中继数据时，将所述待处理数据递交到适配层进行处理，并将经过适配层处理后的所述待处理数据中继到远端终端或网络设备；或
在将所述待处理数据递交到适配层进行处理之后，识别出所述待处理数据为中继数据时，对所述数据中继到远端终端或网络设备。
可选地，所述接收端为网络设备，根据所述待处理数据为是否为中继数据，执行针对所述待处理数据的操作，包括：
在将所述待处理数据递交到适配层进行处理之前，确定所述待处理数据为中继数据时，将所述待处理数据递交到适配层进行处理，并将经过适配层处理后的所述待处理数据递交到分组数据汇聚协议(Packet Data  Convergence Protocol，PDCP)层进行处理；或
在将所述待处理数据递交到适配层进行处理之后，识别出所述待处理数据为中继数据时，将所述待处理数据递交到PDCP层进行处理。
可选地，根据所述待处理数据为是否为中继数据，执行针对所述待处理数据的操作，包括：
在所述待处理数据为非中继数据时，将所述待处理数据递交到PDCP层进行处理。
可选地，所述待处理数据属于层二报文。
第二方面，提供了一种数据处理设备，该设备可以包括执行第一方面或其任一种可选实现方式中的方法的单元。
第三方面，提供了一种数据处理设备，该设备包括处理器和存储器。其中，该存储器中存储程序代码，该处理器用于调用存储器中存储的程序代码执行第一方面或其各种实现方式中的方法。
第四方面，提供一种计算机可读介质，所述计算机可读介质存储用于终端设备执行的程序代码，所述程序代码包括用于执行第一方面或其各种实现方式中的方法的指令。
因此，在本申请实施例中，根据所述待处理数据中承载的信息、对所述待处理数据进行申请资源所用的消息中承载的信息，对所述待处理数据进行申请资源所用的消息占用的资源信息，以及获取所述待处理数据所需的信息中的至少一种，确定所述待处理数据是否为中继数据；可以准确的确定待处理数据是否为中继数据，从而可以根据所述待处理数据为是否为中继数据，执行针对所述待处理数据的操作。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是根据本申请实施例的无线通信系统的示意性图。
图2a和图2b是根据本申请实施例的协议栈的示意性图。
图3是根据本申请实施例的数据处理方法的示意性流程图。
图4是根据本申请实施例的数据处理设备的示意性框图。
图5是根据本申请实施例的数据处理设备的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请的一部分实施例，而不是全部实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动的前提下所获得的所有其他实施例，都应属于本申请保护的范围。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
图1是本申请实施例的应用的无线通信系统100的示意图，该无线通信系统100包括可以包括至少一个网络设备110。网络设备100可以是与终端设备通信的设备。每个网络设备100可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备进行通信。该网络设备100可以是GSM系统或码分多址(Code Division Multiple Access，CDMA)系统中的基站(Base Transceiver Station，BTS)，也可以是WCDMA系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备、未来5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
该无线通信系统100还包括多个终端设备，例如，如图1所示的终端设备121、122、123、124、125和126。该终端设备可以是移动的或固定的。该终端设备可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、 具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、未来5G网络中的终端设备或者未来演进的PLMN中的终端设备等。
图1示例性地示出了一个网络设备和六个终端设备，可选地，该无线通信系统100可以包括多个网络设备并以及其它数量的终端设备，本申请实施例对此不做限定。此外，该无线通信系统100还可以包括移动管理实体(Mobile Management Entity，MME)、服务网关(Serving Gateway，S-GW)、分组数据网络网关(Packet Data Network Gateway，P-GW)等其他网络实体，但本申请实施例不限于此。
具体地，终端设备可以以蜂窝通信模式或D2D通信模式进行通信，其中，在蜂窝通信模式中，终端设备可以通过网络设备与其它终端设备通信；在D2D通信模式中，终端设备可以通过D2D链路直接与其它终端设备通信。
在图1示出的多个终端设备中，终端设备121和终端设备125可以称为远端终端设备，该终端设备121和终端设备125可以分别通过中继终端设备122和124与网络设备110通信；终端设备122和终端设备124可以中继远端终端设备121和远端终端设备125与网络设备110之间的数据，此时，终端设备122和终端设备124可以称为中继终端设备，该中继终端设备122和124也可以以非辅助其他终端设备的方式直接与网络设备进行通信；终端设备123可以即不用通过中继终端设备与网络设备110进行通信，也不用中继其他终端设备与网络设备110进行通信。
其中，终端设备122、123、124和126与网络设备110之间具有Uu接口，可以采用蜂窝通信技术与网络设备110进行通信。中继终端设备与远端终端设备之间具有PC5接口，采用D2D通信技术进行通信，其中，该D2D通信技术可以具体为LTE中的旁路(SideLink，SL)技术，也可以为WLAN中的WIFI或蓝牙等技术，或者为其它D2D通信技术，本申请实施例对此不做限定。当然，终端设备121和终端设备125也可以不通过中继终端设备直接与网络设备110进行通信，此时，终端设备121和终端设备125与网络设备之间具有Uu接口，可以采用蜂窝通信技术与网络设备110进行通信。
在本申请实施例中，中继终端设备与远端终端设备之间可以采用层二中继的方式进行数据传输，此时，在Uu接口和PC5接口都可以采用二层PDU(例如MAC PDU、RLC PDU或PDCP PDU)的方式进行中继传输。
图2a示出了远端终端设备、中继终端设备、基站和核心网在传输数据之间的协议栈。图2b示出了终端设备与基站、服务网关和分组数据网络网关之间在传输用户面数据时所采用的协议栈。
如图2a所示，远端终端设备、中继终端设备和网络设备的层二具有适配层。远端终端设备和中继终端设备在传输中继数据时，可以传输通过适配层以及与D2D通信技术相对应的更下的层处理的报文，其中，如果该D2D通信技术具体为LTE的旁路技术，则该更下的层可以具体为MAC层和物理(Physical，PHY)层，而如果该D2D通信技术为其它通信技术，例如，蓝牙或WIFI技术等等，则该更下的层可以为该其他通信技术中与MAC层和物理层相对应的层；中继终端设备与基站之间可以传输经过PHY层、MAC层、RLC层以及适配层处理的报文；远端终端设备在直接与基站进行通信时，可以传输经过PDCP层处理的报文；远端终端设备在与核心网进行通信时，可以传输将经过网络协议(Internal Protocol，IP)层处理的报文。
可选地，该适配层可以位于RLC层和PDCP之间，本申请实施例对此不做限定。
如图2b所示，终端设备与基站之间可以传输经过L1(Layer 1、层1)、MAC、RLC和PDCP层处理的报文，基站和服务网关之间可以传输经过L1、L2(Layer 2，层2)、UDP/IP和GTP-U层处理的报文，服务网关与分组数据网络网关之间可以传输经过L1、L2、UDP/IP(UDP是用户数据包协议(User Datagram Protocol))和GTP-U(用于用户面的GPRS(通用分组无线服务，General Packet Radio Service)隧道协议，GPRS Tunnelling Protocol for the user plane)层处理的报文。
从以上描述可知，终端设备在作为中继终端设备与网络设备和远端终端设备进行通信时所进行的处理，与作为非中继终端设备与网络设备进行通信时所进行的处理不同，以及网络设备在处理中继数据时，与处理非中继数据的操作也不同，为此，本申请实施例提供了一种数据处理方法，中继终端设备和网络设备可以识别获取的数据是否是中继数据，并针对该数据是否是中继数据，来执行相应的操作。
图3示意性地示出了本申请实施例提供的数据处理方法200。该方法200可以应用于上述无线通信系统100，但本申请实施例不限于此。
如图3所示，该方法200包括以下内容。
在210中，接收端获取待处理数据。
具体地，该方法200可以应用于上行数据的中继传输，即远端终端设备通过中继终端设备向网络设备传输上行数据，此时，发送端设备具体为远端终端设备，接收端可以为中继终端设备或网络设备。可选地，该方法200也可以应用于下行数据的中继传输，即网络设备通过中继终端设备向远端终端设备传输下行数据，此时，发送端设备为网络设备，接收端可以为中继终端设备，但本申请实施例对此不做限定。
可选地，该待处理数据属于二层封装报文。
在220中，根据该待处理数据中承载的信息、对该待处理数据进行申请资源所用的消息中承载的信息，对该待处理数据进行申请资源所用的消息占用的资源信息，以及获取该待处理数据所需的信息中的至少一种，确定该待处理数据是否为中继数据。
可选地，根据该待处理数据的物理层中的数据、MAC层中的PDU承载的信息、RLC层中PDU承载的信息、或适配层中的PDU中承载的信息，确定该待处理数据是否为中继数据。
可选地，可以根据待处理数据中的承载的信息，确定该待处理数据是否为中继数据，其中，可以仅根据待处理数据中的承载的信息，确定该待处理数据是否为中继数据，也可以结合其他信息，例如，获取该待处理数据所需的信息，确定该待处理数据是否为中继数据。
在一种实现方式中，在该待处理数据包括的中继信息指示字段指示该待处理数据为中继数据时，确定该待处理数据为中继数据。
可选地，该中继信息指示字段承载于物理层控制信道中，或物理层业务信道中。
可选地，该中继信息指示字段承载于通过物理控制信道的DCI或UCI中；或，该中继信息指示字段承载于物理层业务信道中的物理业务信道数据的前端，其中，前端可以是指在时域上处于物理业务信道数据的前方。
可选地，该中继信息指示字段可以是一比特的字段，例如，1可以代表该待处理数据为中继数据，0可以代表该待处理数据为非中继数据。
在一种实现方式中，在该待处理数据的适配层中携带远端终端的标识信息时，确定该待处理数据为中继数据。
在一种实现方式中，在该待处理数据的适配层中携带承载标识信息时， 确定该待处理数据为中继数据。
在一种实现方式中，在该待处理数据的适配层中携带特定的承载标识信息时，确定该待处理数据为中继数据。
可选地，该特定的承载标识信息可以是协议规定，也可以是网络设备配置的。
可选地，根据对该待处理数据进行申请资源所用的缓存状态报告(Buffer State Report，BSR)中携带的信息，确定该待处理数据是否为中继数据，，其中，可以仅利用对该待处理数据进行申请资源所用的BSR中携带的信息进行中继数据的识别，当然也可以结合其他信息，例如，待处理数据中承载的信息，进行中继数据的识别。
可选地，在该BSR中携带用于指示申请的资源用于中继数据的中继数据指示信息，远端终端的标识信息，或中继特定的逻辑信道信息时，确定该待处理数据为中继数据。
具体地，在BSR可以具有中继数据指示字段，如果该中继数据指示字段携带的信息用于申请的资源用于中继数据时，则确定该BSR对应的该待处理数据为中继数据，其中，该中继数据指示字段可以是1比特的字段，例如，1可以代表申请的资源用于中继数据，0可以代表申请的资源用于中继数据。
可选地，根据对该待处理数据进行申请资源所用的调度请求占用的时域资源、频域资源、码域资源(例如，前导码)和功率资源(例如，接收功率区间)中的至少一种，确定该待处理数据是否为中继数据，其中，可以仅根据该待处理数据进行申请资源所用的调度请求占用的资源信息进行中继数据的识别，也可以结合其他信息进行中继数据的识别，在此不做具体限定。
可选地，在该调度请求占用的时域资源为中继特定的时域资源，和/或该调度请求占用的频域资源为中继特定的频域资源，和/或该调度请求占用的码域资源为中继特定的码域资源，和/或该调度请求占用的空域资源为中继特定的空域资源，和/或该调度请求占用的功率资源为中继特定的功率资源时，确定该待处理数据为中继数据。
可选地，该中继特定的时域资源，和/或该中继特定的频域资源，和/或该中继特定的码域资源，和/或该中继特定的空域资源，和/或该中继特定的功率资源可以是协议规定的，也可以是网络设备配置的。
可选地，调度请求申请的资源可以用于传输BSR，而BSR可以携带待处理数据的数据量，而用于为待处理数据申请具体的传输资源。
可选地，根据获取该待处理数据所用的C-RNTI，确定该待处理数据是否为中继数据，其中，可以仅根据C-RNTI进行中继数据的识别，也可以结合其他信息进行中继数据的识别，在此不做具体限定。
可选地，在获取该待处理数据所用的C-RNTI为中继特定的C-RNTI时，确定该待处理数据为中继数据。
可选地，该中继特定的C-RNTI可以是协议规定的，也可以是网络设备配置的。
可选地，在本申请实施例中，利用待处理数据中的适配层中携带的远端终端的标识信息，适配层中的承载标识信息，对该待处理数据进行申请资源所用的消息占用的资源信息，和/或获取该待处理数据所需的信息进行中继数据的判断，可以称为通过隐式指示数据是否是中继数据，可以无需专门的中继数据指示资源，可以减少资源开销。
在230中，根据该待处理数据为是否为中继数据，执行针对该待处理数据的操作。
可选地，该接收端为中继终端设备，中继终端设备在将该待处理数据递交到适配层进行处理之前，确定该待处理数据为中继数据时，将该待处理数据递交到适配层进行处理，并将经过适配层处理后的该待处理数据中继到远端终端或网络设备。
可选地，该接收端为中继终端设备，中继终端设备在将该待处理数据递交到适配层进行处理之后，识别出该待处理数据为中继数据时，对该数据中继到远端终端或网络设备。
可选地，该接收端为网络设备，在网络设备将该待处理数据递交到适配层进行处理之前，确定该待处理数据为中继数据时，将该待处理数据递交到适配层进行处理，并将经过适配层处理后的该待处理数据递交到PDCP层进行处理。
可选地，该接收端为网络设备，在网络设备将该待处理数据递交到适配层进行处理之后，识别出该待处理数据为中继数据时，将该待处理数据递交到PDCP层进行处理。
可选地，在该待处理数据为非中继数据时，将该待处理数据递交到PDCP 层处理，此时，该接收端可以为网络设备，也可以为中继终端设备。
因此，在本申请实施例中，根据所述待处理数据中承载的信息、对所述待处理数据进行申请资源所用的消息中承载的信息，对所述待处理数据进行申请资源所用的消息占用的资源信息，以及获取所述待处理数据所需的信息中的至少一种，确定所述待处理数据是否为中继数据；可以准确的确定待处理数据是否为中继数据，从而可以根据所述待处理数据为是否为中继数据，执行针对所述待处理数据的操作。
图4是根据本申请实施例的数据处理设备400的示意性框图。如图4所示，该数据处理设备400包括获取单元410、确定单元420和处理单元430。
其中，获取单元410，用于获取待处理数据；确定单元420，用于根据所述待处理数据中承载的信息、对所述待处理数据进行申请资源所用的消息中承载的信息，对所述待处理数据进行申请资源所用的消息占用的资源信息，以及获取所述待处理数据所需的信息中的至少一种，确定所述待处理数据是否为中继数据；处理单元430，用于根据所述待处理数据为是否为中继数据，执行针对所述待处理数据的操作。
可选地，所述确定单元420具体用于：
根据所述待处理数据的物理层中的数据、媒体接入控制层MAC层中的协议数据单元PDU承载的信息、无线链路控制RLC层中PDU承载的信息、或适配层中的PDU中承载的信息，确定所述待处理数据是否为中继数据。
可选地，所述确定单元420具体用于：
在所述待处理数据包括的中继信息指示字段指示所述待处理数据为中继数据时，确定所述待处理数据为中继数据；或
在所述待处理数据的适配层中携带远端终端的标识信息时，确定所述待处理数据为中继数据；或，
在所述待处理数据的适配层中携带承载标识信息时，确定所述待处理数据为中继数据；或，
在所述待处理数据的适配层中携带特定的承载标识信息时，确定所述待处理数据为中继数据。
可选地，所述中继信息指示字段承载于物理层控制信道中，或物理层业务信道中。
可选地，所述中继信息指示字段承载于通过物理控制信道的下行控制信 息DCI或上行控制信息UCI中；或，
所述中继信息指示字段承载于物理层业务信道中的物理业务信道数据的前端。
可选地，所述确定单元420具体用于：
根据对所述待处理数据进行申请资源所用的缓存状态报告BSR中携带的信息，确定所述待处理数据是否为中继数据。
可选地，所述确定单元420具体用于：
在所述BSR中携带用于指示申请的资源用于中继数据的中继数据指示信息，远端终端的标识信息，或中继特定的逻辑信道信息时，确定所述待处理数据为中继数据。
可选地，所述确定单元420具体用于：
根据对所述待处理数据进行申请资源所用的调度请求占用的时域资源、频域资源、码域资源和功率资源中的至少一种，确定所述待处理数据是否为中继数据。
可选地，所述确定单元420具体用于：
在所述调度请求占用的时域资源为中继特定的时域资源，和/或所述调度请求占用的频域资源为中继特定的频域资源，和/或所述调度请求占用的码域资源为中继特定的码域资源，和/或所述调度请求占用的空域资源为中继特定的空域资源，和/或所述调度请求占用的功率资源为中继特定的功率资源时，确定所述待处理数据为中继数据。
可选地，所述确定单元420具体用于：
根据获取所述待处理数据所用的小区无线网络临时标识C-RNTI，确定所述待处理数据是否为中继数据。
可选地，所述确定单元420具体用于：
在获取所述待处理数据所用的C-RNTI为中继特定的C-RNTI时，确定所述待处理数据为中继数据。
可选地，所述数据处理设备400为中继终端设备，所述处理单元430具体用于：
在将所述待处理数据递交到适配层进行处理之前，确定所述待处理数据为中继数据时，将所述待处理数据递交到适配层进行处理，并将经过适配层处理后的所述待处理数据中继到远端终端或网络设备；或
在将所述待处理数据递交到适配层进行处理之后，识别出所述待处理数据为中继数据时，对所述数据中继到远端终端或网络设备。
可选地，所述数据处理设备400为网络设备，所述处理单元430具体用于：
在将所述待处理数据递交到适配层进行处理之前，确定所述待处理数据为中继数据时，将所述待处理数据递交到适配层进行处理，并将经过适配层处理后的所述待处理数据递交到PDCP层进行处理；或
在将所述待处理数据递交到适配层进行处理之后，识别出所述待处理数据为中继数据时，将所述待处理数据递交到PDCP层进行处理。
可选地，所述处理单元430具体用于：
在所述待处理数据为非中继数据时，将所述待处理数据递交到PDCP层进行处理。
可选地，所述待处理数据属于层二报文。
应理解，该数据处理设备400可以实现图3所示的方法300，为了简洁，在此不再赘述。
图4是根据本申请实施例的数据处理设备500的示意性框图。如图5所示，该设备500包括处理器510和存储器520。其中，该存储器520可以存储有程序代码，该处理器510可以执行该存储器520中存储的程序代码。
可选地，如图4所示，该设备500可以包括收发器530，处理器510可以收发器530可以对外通信。
可选地，该处理器510可以调用存储器520中存储的程序代码，执行图3所示的方法300中的相应操作，为了简洁，在此不再赘述。
可选地，该设备500可以是终端设备，也可以是可置于终端设备中的系统芯片；或者，该设备500可以是网络设备，也可以是可置于该网络设备中的系统芯片。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描 述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (30)

  1. 一种数据处理方法，其特征在于，包括：
    接收端获取待处理数据；
    根据所述待处理数据中承载的信息、对所述待处理数据进行申请资源所用的消息中承载的信息，对所述待处理数据进行申请资源所用的消息占用的资源信息，以及获取所述待处理数据所需的信息中的至少一种，确定所述待处理数据是否为中继数据；
    根据所述待处理数据为是否为中继数据，执行针对所述待处理数据的操作。
  2. 根据权利要求1所述的方法，其特征在于，根据所述待处理数据中承载的信息，确定所述待处理数据是否为中继数据，包括：
    根据所述待处理数据的物理层中的数据、媒体接入控制层MAC层中的协议数据单元PDU承载的信息、无线链路控制RLC层中PDU承载的信息、或适配层中的PDU中承载的信息，确定所述待处理数据是否为中继数据。
  3. 根据权利要求1或2所述的方法，其特征在于，根据所述待处理数据中承载的信息，确定所述待处理数据是否为中继数据，包括：
    在所述待处理数据包括的中继信息指示字段指示所述待处理数据为中继数据时，确定所述待处理数据为中继数据；或
    在所述待处理数据的适配层中携带远端终端的标识信息时，确定所述待处理数据为中继数据；或，
    在所述待处理数据的适配层中携带承载标识信息时，确定所述待处理数据为中继数据；或，
    在所述待处理数据的适配层中携带特定的承载标识信息时，确定所述待处理数据为中继数据。
  4. 根据权利要求3所述的方法，其特征在于，所述中继信息指示字段承载于物理层控制信道中，或物理层业务信道中。
  5. 根据权利要求4所述的方法，其特征在于，所述中继信息指示字段承载于通过物理控制信道的下行控制信息DCI或上行控制信息UCI中；或，
    所述中继信息指示字段承载于物理层业务信道中的物理业务信道数据的前端。
  6. 根据权利要求1或2所述的方法，其特征在于，根据对所述待处理 数据进行申请资源所用的消息中承载的信息，确定所述待处理数据是否为中继数据，包括：
    根据对所述待处理数据进行申请资源所用的缓存状态报告BSR中携带的信息，确定所述待处理数据是否为中继数据。
  7. 根据权利要求6所述的方法，其特征在于，根据对所述待处理数据进行申请资源所用的BSR中携带的信息，确定所述待处理数据是否为中继数据，包括：
    在所述BSR中携带用于指示申请的资源用于中继数据的中继数据指示信息，远端终端的标识信息，或中继特定的逻辑信道信息时，确定所述待处理数据为中继数据。
  8. 根据权利要求1、2或6所述的方法，其特征在于，根据所述待处理数据进行申请资源所用的消息占用的资源信息，确定所述待处理数据是否为中继数据，包括：
    根据对所述待处理数据进行申请资源所用的调度请求占用的时域资源、频域资源、码域资源和功率资源中的至少一种，确定所述待处理数据是否为中继数据。
  9. 根据权利要求8所述的方法，其特征在于，根据对所述待处理数据进行申请资源所用的调度请求占用的时域资源、频域资源、码域资源和功率资源中的至少一种，确定所述待处理数据是否为中继数据，包括：
    在所述调度请求占用的时域资源为中继特定的时域资源，和/或所述调度请求占用的频域资源为中继特定的频域资源，和/或所述调度请求占用的码域资源为中继特定的码域资源，和/或所述调度请求占用的空域资源为中继特定的空域资源，和/或所述调度请求占用的功率资源为中继特定的功率资源时，确定所述待处理数据为中继数据。
  10. 根据权利要求1、2、6或8所述的方法，其特征在于，根据获取所述待处理数据所需的信息，确定所述待处理数据是否为中继数据，包括：
    根据获取所述待处理数据所用的小区无线网络临时标识C-RNTI，确定所述待处理数据是否为中继数据。
  11. 根据权利要求10所述的方法，其特征在于，根据获取所述待处理数据所用的C-RNTI，确定所述待处理数据是否为中继数据，包括：
    在获取所述待处理数据所用的C-RNTI为中继特定的C-RNTI时，确定 所述待处理数据为中继数据。
  12. 根据权利要求1至11中任一项所述的方法，其特征在于，所述接收端为中继终端设备，根据所述待处理数据为是否为中继数据，执行针对所述待处理数据的操作，包括：
    在将所述待处理数据递交到适配层进行处理之前，确定所述待处理数据为中继数据时，将所述待处理数据递交到适配层进行处理，并将经过适配层处理后的所述待处理数据中继到远端终端或网络设备；或
    在将所述待处理数据递交到适配层进行处理之后，识别出所述待处理数据为中继数据时，对所述数据中继到远端终端或网络设备。
  13. 根据权利要求1至11中任一项所述的方法，其特征在于，所述接收端为网络设备，根据所述待处理数据为是否为中继数据，执行针对所述待处理数据的操作，包括：
    在将所述待处理数据递交到适配层进行处理之前，确定所述待处理数据为中继数据时，将所述待处理数据递交到适配层进行处理，并将经过适配层处理后的所述待处理数据递交到分组数据汇聚协议PDCP层进行处理；或
    在将所述待处理数据递交到适配层进行处理之后，识别出所述待处理数据为中继数据时，将所述待处理数据递交到PDCP层进行处理。
  14. 根据权利要求1至13中任一项所述的方法，其特征在于，根据所述待处理数据为是否为中继数据，执行针对所述待处理数据的操作，包括：
    在所述待处理数据为非中继数据时，将所述待处理数据递交到PDCP层进行处理。
  15. 根据权利要求1至14中任一项所述的方法，其特征在于，所述待处理数据属于层二报文。
  16. 一种数据处理设备，其特征在于，包括：
    获取单元，用于获取待处理数据；
    确定单元，用于根据所述待处理数据中承载的信息、对所述待处理数据进行申请资源所用的消息中承载的信息，对所述待处理数据进行申请资源所用的消息占用的资源信息，以及获取所述待处理数据所需的信息中的至少一种，确定所述待处理数据是否为中继数据；
    处理单元，用于根据所述待处理数据为是否为中继数据，执行针对所述待处理数据的操作。
  17. 根据权利要求16所述的设备，其特征在于，所述确定单元具体用于：
    根据所述待处理数据的物理层中的数据、媒体接入控制层MAC层中的协议数据单元PDU承载的信息、无线链路控制RLC层中PDU承载的信息、或适配层中的PDU中承载的信息，确定所述待处理数据是否为中继数据。
  18. 根据权利要求16或17所述的设备，其特征在于，所述确定单元具体用于：
    在所述待处理数据包括的中继信息指示字段指示所述待处理数据为中继数据时，确定所述待处理数据为中继数据；或
    在所述待处理数据的适配层中携带远端终端的标识信息时，确定所述待处理数据为中继数据；或，
    在所述待处理数据的适配层中携带承载标识信息时，确定所述待处理数据为中继数据；或，
    在所述待处理数据的适配层中携带特定的承载标识信息时，确定所述待处理数据为中继数据。
  19. 根据权利要求18所述的设备，其特征在于，所述中继信息指示字段承载于物理层控制信道中，或物理层业务信道中。
  20. 根据权利要求19所述的设备，其特征在于，所述中继信息指示字段承载于通过物理控制信道的下行控制信息DCI或上行控制信息UCI中；或，
    所述中继信息指示字段承载于物理层业务信道中的物理业务信道数据的前端。
  21. 根据权利要求16或17所述的设备，其特征在于，所述确定单元具体用于：
    根据对所述待处理数据进行申请资源所用的缓存状态报告BSR中携带的信息，确定所述待处理数据是否为中继数据。
  22. 根据权利要求21所述的设备，其特征在于，所述确定单元具体用于：
    在所述BSR中携带用于指示申请的资源用于中继数据的中继数据指示信息，远端终端的标识信息，或中继特定的逻辑信道信息时，确定所述待处理数据为中继数据。
  23. 根据权利要求16、17或21所述的设备，其特征在于，所述确定单元具体用于：
    根据对所述待处理数据进行申请资源所用的调度请求占用的时域资源、频域资源、码域资源和功率资源中的至少一种，确定所述待处理数据是否为中继数据。
  24. 根据权利要求23所述的设备，其特征在于，所述确定单元具体用于：
    在所述调度请求占用的时域资源为中继特定的时域资源，和/或所述调度请求占用的频域资源为中继特定的频域资源，和/或所述调度请求占用的码域资源为中继特定的码域资源，和/或所述调度请求占用的空域资源为中继特定的空域资源，和/或所述调度请求占用的功率资源为中继特定的功率资源时，确定所述待处理数据为中继数据。
  25. 根据权利要求16、17、21或23所述的设备，其特征在于，所述确定单元具体用于：
    根据获取所述待处理数据所用的小区无线网络临时标识C-RNTI，确定所述待处理数据是否为中继数据。
  26. 根据权利要求25所述的设备，其特征在于，所述确定单元具体用于：
    在获取所述待处理数据所用的C-RNTI为中继特定的C-RNTI时，确定所述待处理数据为中继数据。
  27. 根据权利要求16至26中任一项所述的设备，其特征在于，所述数据处理设备为中继终端设备，所述处理单元具体用于：
    在将所述待处理数据递交到适配层进行处理之前，确定所述待处理数据为中继数据时，将所述待处理数据递交到适配层进行处理，并将经过适配层处理后的所述待处理数据中继到远端终端或网络设备；或
    在将所述待处理数据递交到适配层进行处理之后，识别出所述待处理数据为中继数据时，对所述数据中继到远端终端或网络设备。
  28. 根据权利要求16至26中任一项所述的设备，其特征在于，所述数据处理设备为网络设备，所述处理单元具体用于：
    在将所述待处理数据递交到适配层进行处理之前，确定所述待处理数据为中继数据时，将所述待处理数据递交到适配层进行处理，并将经过适配层 处理后的所述待处理数据递交到PDCP层进行处理；或
    在将所述待处理数据递交到适配层进行处理之后，识别出所述待处理数据为中继数据时，将所述待处理数据递交到PDCP层进行处理。
  29. 根据权利要求16至28中任一项所述的设备，其特征在于，所述处理单元具体用于：
    在所述待处理数据为非中继数据时，将所述待处理数据递交到PDCP层进行处理。
  30. 根据权利要求16至29中任一项所述的设备，其特征在于，所述待处理数据属于层二报文。
PCT/CN2016/108895 2016-12-07 2016-12-07 数据处理方法和设备 Ceased WO2018103016A1 (zh)

Priority Applications (10)

Application Number Priority Date Filing Date Title
PCT/CN2016/108895 WO2018103016A1 (zh) 2016-12-07 2016-12-07 数据处理方法和设备
US16/466,007 US10959211B2 (en) 2016-12-07 2016-12-07 Data processing method and device
EP16923238.6A EP3547791B1 (en) 2016-12-07 2016-12-07 Data processing method and device
CN201680090848.5A CN109964535B (zh) 2016-12-07 2016-12-07 数据处理方法、设备和计算机可读介质
KR1020197018493A KR20190092458A (ko) 2016-12-07 2016-12-07 데이터 처리 방법과 장치
JP2019530393A JP7101675B6 (ja) 2016-12-07 2016-12-07 データ処理方法及び装置
EP21184574.8A EP3914038A1 (en) 2016-12-07 2016-12-07 Data processing method and device
CN202210308959.6A CN114978450A (zh) 2016-12-07 2016-12-07 数据处理方法、设备和计算机可读介质
TW106141706A TWI746710B (zh) 2016-12-07 2017-11-29 數據處理方法和設備
US17/171,926 US20210168765A1 (en) 2016-12-07 2021-02-09 Data Processing Method and Device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/108895 WO2018103016A1 (zh) 2016-12-07 2016-12-07 数据处理方法和设备

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US16/466,007 A-371-Of-International US10959211B2 (en) 2016-12-07 2016-12-07 Data processing method and device
US17/171,926 Continuation US20210168765A1 (en) 2016-12-07 2021-02-09 Data Processing Method and Device

Publications (1)

Publication Number Publication Date
WO2018103016A1 true WO2018103016A1 (zh) 2018-06-14

Family

ID=62490619

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/108895 Ceased WO2018103016A1 (zh) 2016-12-07 2016-12-07 数据处理方法和设备

Country Status (7)

Country Link
US (2) US10959211B2 (zh)
EP (2) EP3914038A1 (zh)
JP (1) JP7101675B6 (zh)
KR (1) KR20190092458A (zh)
CN (2) CN109964535B (zh)
TW (1) TWI746710B (zh)
WO (1) WO2018103016A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023005896A1 (zh) * 2021-07-28 2023-02-02 大唐移动通信设备有限公司 信息传输方法、装置、中继终端和网络侧设备

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111800866B (zh) * 2019-08-15 2023-09-19 维沃移动通信有限公司 资源请求方法、资源分配方法、装置、设备及介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014092497A1 (en) * 2012-12-14 2014-06-19 Lg Electronics Inc. Method and apparatus for supporting transmission efficiency in a wireless communication system
CN105657783A (zh) * 2015-05-29 2016-06-08 宇龙计算机通信科技(深圳)有限公司 一种终端直连通信方法及装置
CN105846882A (zh) * 2015-01-14 2016-08-10 北京三星通信技术研究有限公司 一种d2d通信的中继方法和设备
CN105992364A (zh) * 2015-03-02 2016-10-05 中兴通讯股份有限公司 资源处理方法及装置

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AR055163A1 (es) * 2005-09-13 2007-08-08 Iwics Inc Determinacion de la posicion de estaciones moviles en una red inalambrica
US8165058B2 (en) * 2007-03-01 2012-04-24 Mitsubishi Electric Research Laboratories, Inc. Protocol data units and header in multihop relay network
EP2351456B1 (en) * 2008-09-26 2014-03-12 Nokia Solutions and Networks Oy Control signaling in system supporting relayed connections
CA2755148C (en) * 2009-03-13 2015-06-30 Research In Motion Limited System and method for assigning resources to a relay
CN104471869B (zh) * 2012-05-14 2016-07-13 英派尔科技开发有限公司 中继数据的方法、无线通信网络和中继装置
CN106686558A (zh) * 2012-05-26 2017-05-17 华为技术有限公司 一种数据发送、转发方法、装置和系统
EP3177100A4 (en) 2014-07-31 2018-05-30 Sharp Kabushiki Kaisha Terminal apparatus, control method, and integrated circuit

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014092497A1 (en) * 2012-12-14 2014-06-19 Lg Electronics Inc. Method and apparatus for supporting transmission efficiency in a wireless communication system
CN105846882A (zh) * 2015-01-14 2016-08-10 北京三星通信技术研究有限公司 一种d2d通信的中继方法和设备
CN105992364A (zh) * 2015-03-02 2016-10-05 中兴通讯股份有限公司 资源处理方法及装置
CN105657783A (zh) * 2015-05-29 2016-06-08 宇龙计算机通信科技(深圳)有限公司 一种终端直连通信方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3547791A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023005896A1 (zh) * 2021-07-28 2023-02-02 大唐移动通信设备有限公司 信息传输方法、装置、中继终端和网络侧设备

Also Published As

Publication number Publication date
EP3547791B1 (en) 2021-08-11
TWI746710B (zh) 2021-11-21
JP2020503739A (ja) 2020-01-30
KR20190092458A (ko) 2019-08-07
JP7101675B2 (ja) 2022-07-15
EP3547791A4 (en) 2019-11-27
EP3547791A1 (en) 2019-10-02
EP3914038A1 (en) 2021-11-24
US20190394752A1 (en) 2019-12-26
JP7101675B6 (ja) 2022-09-30
CN109964535B (zh) 2022-04-01
CN114978450A (zh) 2022-08-30
US10959211B2 (en) 2021-03-23
CN109964535A (zh) 2019-07-02
TW201822582A (zh) 2018-06-16
US20210168765A1 (en) 2021-06-03

Similar Documents

Publication Publication Date Title
US11223414B2 (en) Reducing the processing complexity of relay transmission
EP3499922B1 (en) Method, device and computer-readable storage medium for applying qos based on user plane data mapping
US10264611B2 (en) Device and method of handling radio resource control connection resume procedure
WO2017206186A1 (zh) 中继传输的方法和装置
CN110324848A (zh) 信息处理方法以及相关装置
US20160316494A1 (en) Small data packet transmission method, base station, and user equipment
CN110505714B (zh) 多链接通信方法、设备和终端
CN107836135A (zh) 在无线通信系统中由终端发送和接收数据的方法和设备
EP3393173B1 (en) Terminal device and access network devices
CN108809594A (zh) 传输数据的方法、终端设备和网络设备
US20230276313A1 (en) Managing sidelink communication
WO2017166139A1 (zh) 中继传输的方法和装置
CN105723794B (zh) 一种接入网络的方法以及相关装置
CN115065988A (zh) 中继传输的方法、中继终端和远端终端
EP3457754B1 (en) Data transmission method and base station
JP2019504567A (ja) データ伝送方法および装置、ならびに関連デバイス
US20210168765A1 (en) Data Processing Method and Device
CN109155956A (zh) 一种数据传输方法、装置及系统
WO2023279296A1 (zh) 无线通信方法、第一终端和通信设备
HK40005727A (zh) 数据处理方法和设备
WO2019218119A1 (zh) 用于确定传输时延的方法、通信设备及可读存储介质

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: 16923238

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019530393

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20197018493

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2016923238

Country of ref document: EP

Effective date: 20190627