WO2019047180A1 - 一种传输方法及设备 - Google Patents

一种传输方法及设备 Download PDF

Info

Publication number
WO2019047180A1
WO2019047180A1 PCT/CN2017/101122 CN2017101122W WO2019047180A1 WO 2019047180 A1 WO2019047180 A1 WO 2019047180A1 CN 2017101122 W CN2017101122 W CN 2017101122W WO 2019047180 A1 WO2019047180 A1 WO 2019047180A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
base station
identifier information
home base
information
Prior art date
Application number
PCT/CN2017/101122
Other languages
English (en)
French (fr)
Inventor
于映辉
王燕
单宝堃
Original Assignee
华为技术有限公司
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
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP17924345.6A priority Critical patent/EP3672351B1/en
Priority to CN201780093648.XA priority patent/CN110999511B/zh
Priority to PCT/CN2017/101122 priority patent/WO2019047180A1/zh
Publication of WO2019047180A1 publication Critical patent/WO2019047180A1/zh
Priority to US16/810,046 priority patent/US11388647B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • 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
    • H04W74/00—Wireless channel access, e.g. scheduled or random access
    • H04W74/08—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access]
    • H04W74/0833—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access] using a random access procedure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • 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
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the field of Internet of Things communication technologies, and in particular, to a transmission method and device.
  • IoT Internet of Things
  • the 20-bit coverage enhancement of the IoT air interface single-hop can meet the coverage requirements in most scenarios, but in some special scenarios, such as in a multi-layer distributed scenario such as a building, if the base station is located at the top of the building, it is close to the base station. IoT devices on the floor can be served, but IoT devices on floors far from the base station may not be serviced. There are also some scenes, such as some gas meters, etc., which are deeper and may not be able to reach by one hop. In these scenarios, the deployment of wired backhaul links is also difficult. In this case, using a low-power wireless access node as a multi-hop relay is a possible solution.
  • the network architecture of the two-hop relay can be as shown in FIG. 1 .
  • the network architecture includes a relay node (RN), a base station (eNodeB, eNB), a home base station (donor eNB, DeNB), and a mobility management entity (MME) or service.
  • the gateway serving gate way (S-GW)) is connected through the Un interface between the RN and the DeNB.
  • S-GW serving gate way
  • the X2 and S1 protocols are supported on the air interface of the Un.
  • the RN in the LTE network is a combination of the network functions of one base station and one UE.
  • the RN is used to implement multi-hop relay in the NB-IoT network, it is also feasible, but based on the existing network functions, The RN also needs to assume the network function of the DeNB of the last-hop relay node. Therefore, the network function of the RN in the NB-IoT network is more complicated than the network function of the RN in the LTE network, and cannot meet the requirements of simple deployment.
  • the NB-IoT network requires RNs, so it is urgent to introduce a relay node with simple network functions.
  • the present application provides a transmission method and device for improving data transmission efficiency after accessing multiple relay nodes in an NB-IoT network.
  • a method of transmitting comprising:
  • the first device receives a first radio resource control (RRC) message sent by the second device, where the first RRC message includes first data and identification information, where the first data is data to be sent to the network device.
  • RRC radio resource control
  • the first device is a first relay node that accesses the home base station
  • the second device is a second relay node or a terminal device
  • the identifier information is identifier information of the terminal device or a relay node.
  • the first device sends the first data to the home base station of the first device by using a second RRC message And the identification information.
  • the network functions of the first device and the second device are simplified, and the transmission efficiency of data after accessing the plurality of relay nodes in the NB-IoT network is improved.
  • the method before the first device sends the first data and the identifier information to the home base station of the first device by using the second RRC message, the method further includes: the first device according to the identifier Determining, by the second RRC message, the first data and the identifier information of the first base station of the first device by using the second RRC message .
  • the destination of the data to be transmitted can be known, so that the data transmission efficiency can be improved.
  • the first data is a non-access-stratum protocol data unit (NAS PDU) sent by the terminal device to the network device.
  • NAS PDU non-access-stratum protocol data unit
  • the second relay node is a relay node that is accessed by the terminal device.
  • the method before the first device receives the first RRC message sent by the second device, the method further includes: the first device according to the strength and/or quality of the air interface wireless signal of the home base station Or the configured serving cell information, the cell of the home base station is determined as a serving cell, the first device initiates a random access to the serving cell, and establishes an RRC connection with the home base station, where the first device Receiving configuration information sent by the home base station, and configuring its own cell according to the configuration information.
  • the configuration is completed, and the transmission efficiency of the data after accessing the multiple relay nodes in the NB-IoT network is supported.
  • the method before the first device receives the first RRC message sent by the second device, the method further includes: the first device receiving the RRC connection request message initiated by the second device, and The second device establishes an RRC connection.
  • the first RRC message when the identifier information is the identifier information of the relay node, the first RRC message further includes a relay indication, where the relay indication is used to notify the network device and/or the home base station
  • the second device is a relay node.
  • a transmission method including:
  • the second device obtains the first data and the identifier information, where the first data is data to be sent to the network device, and the identifier information is identifier information of the terminal device or identifier information of the relay node, where the The second device is the second relay node or the terminal device, and the second device sends a first RRC message to the first device, where the first RRC message includes the first data and the identifier information;
  • the first device is a first relay node that accesses the home base station.
  • the network functions of the first device and the second device are simplified, and the transmission efficiency of data after accessing the plurality of relay nodes in the NB-IoT network is improved.
  • the second device when the second device is the second relay node, the second device acquires the first data, and the second device acquires the second relay node to generate the second relay node.
  • the first data, or the second device receives the first data sent by the terminal device.
  • the second relay node is a relay node that is accessed by the terminal device.
  • the second device when the second device is the terminal device, the second device acquires the first data, and the second device acquires the first data generated by the terminal device itself.
  • a third aspect provides a transmission device, including: a receiving unit and a sending unit;
  • the receiving unit is configured to receive a first RRC message sent by the second device, where the first RRC message includes first data and identifier information, where the first data is data to be sent to a network device, and the transmitting device is The first device is the first relay node that accesses the home base station, the second device is the second relay node or the terminal device, and the second device accesses the first device.
  • the identifier information is the identifier information of the terminal device or the identifier information of the relay node, and the sending unit is configured to send, by using the second RRC message, the first received by the receiving unit to the home base station of the first device. A data and the identification information.
  • the first data is a NAS PDU that is sent by the terminal device to the network device.
  • a processing unit configured to send, by the sending unit, the first data and the received by the receiving unit to the home base station of the first device by using a second RRC message Before the identifier information, the home base station of the first device corresponding to the identifier information is determined according to the identifier information received by the receiving unit.
  • the second relay node is a relay node that is accessed by the terminal device.
  • the processing unit is further configured to: determine, according to the strength and/or quality of the air interface radio signal of the home base station, or the configured serving cell information, a cell of the home base station as a serving cell. ;
  • the receiving unit is further configured to receive configuration information sent by the home base station;
  • the processing unit is further configured to configure its own cell according to the configuration information received by the receiving unit.
  • the receiving unit before the receiving unit receives the first RRC message sent by the second device, the receiving unit is further configured to receive the RRC connection request message initiated by the second device;
  • the processing unit is further configured to establish an RRC connection with the second device.
  • the first RRC message when the identifier information is the identifier information of the relay node, the first RRC message further includes a relay indication, where the relay indication is used to notify the network device and/or the home base station
  • the second device is a relay node.
  • a fourth aspect provides a multi-way relay transmission device, including: a sending unit and a processing unit;
  • the processing unit is configured to acquire first data and identification information, where the first data is data to be sent to a network device, and the identifier information is identifier information of the terminal device or identifier information of a relay node.
  • the transmission device is the second relay node or the terminal device;
  • the sending unit is configured to send a first RRC message to the first device, where the first RRC message includes the first data acquired by the processing unit and the identifier information; the first device is configured to access the home base station Relay node.
  • the processing unit is specifically configured to: when the transmission device is the second relay node, acquire first data generated by the second relay node itself; or
  • the processing unit controls the receiving unit to receive the first data sent by the terminal device.
  • the processing unit is specifically configured to acquire first data generated by the terminal device when the transmission device is a terminal device.
  • the present application provides a transmission device, including: a communication interface, a processor, and a memory; the memory is configured to store a software program, and the processor is configured to read a software program stored in the memory, Transmitting and transmitting data by the communication interface, and implementing the first aspect, any one of the possible implementation manners of the first aspect method.
  • the present application provides a transmission device, including: a communication interface, a processor, and a memory; the memory is configured to store a software program, and the processor is configured to read a software program stored in the memory,
  • the communication interface transmits and receives data, and implements the method described in any one of the second aspect and the second aspect.
  • the application provides a communication system, including a first device, a second device, and a home base station; the first device is a first relay node that accesses a home base station, and the second device is the The second relay node is either a terminal device;
  • the second device acquires the first data and the identifier information, where the first data is data to be sent to the network device, and the identifier information is identifier information of the terminal device or identifier information of the relay node; Sending a first RRC message to the first device, where the first RRC message includes the first data and the identifier information;
  • the first device receives the first RRC message sent by the second device, and sends the first data and the identifier information to the home base station of the first device by using a second RRC message.
  • the present application provides a computer readable storage medium comprising computer readable instructions which, when read and executed by a computer, cause the computer to perform the method of any of the first aspects.
  • the present application provides a computer readable storage medium comprising computer readable instructions which, when read and executed by a computer, cause the computer to perform the method of any one of the second aspects.
  • the application provides a computer program product comprising computer readable instructions which, when read and executed by a computer, cause the computer to perform the method of any of the first aspects.
  • the application provides a computer program product comprising computer readable instructions which, when read and executed by a computer, cause the computer to perform the method of any one of the second aspects.
  • FIG. 1 is a schematic structural diagram of a network architecture provided by the present application.
  • FIG. 2 is a schematic structural diagram of a communication network system provided by the present application.
  • FIG. 3 is a schematic flowchart diagram of a transmission method provided by the present application.
  • FIG. 4 is a schematic structural diagram of a network architecture provided by the present application.
  • FIG. 5 is a schematic structural diagram of a protocol stack provided by the present application.
  • 6a is a schematic structural diagram of a protocol stack provided by the present application.
  • 6b is a schematic structural diagram of a protocol stack provided by the present application.
  • FIG. 7 is a schematic flowchart of an RN startup according to the present application.
  • FIG. 8 is a schematic flowchart of a RN startup according to the present application.
  • FIG. 9 is a schematic flowchart of a UE accessing an RN according to the present application.
  • FIG. 10 is a schematic structural diagram of a transmission device provided by the present application.
  • FIG. 11 is a schematic structural diagram of a transmission device provided by the present application.
  • the application provides a transmission method that can be applied to a communication network system.
  • FIG. 2 is a structural diagram of a possible communication network system provided by the present application.
  • the communication network system includes a terminal device, a plurality of relay nodes, a home base station, and a network device.
  • the terminal device may be a device with wireless transceiving function that can be deployed on land, including indoors or outdoors, handheld, wearable or on-board; it can also be deployed on the water surface (such as a ship, etc.); it can also be deployed in the air (for example, an aircraft, Balloons and satellites, etc.).
  • the terminal device may be a mobile phone, an Internet of Things (IoT) terminal device, a tablet (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, augmented reality (augmented reality, AR) terminal equipment, wireless terminal in industrial control, wireless terminal in self driving, wireless terminal in remote medical, wireless terminal in smart grid, A wireless terminal in a transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, and the like.
  • IoT Internet of Things
  • WiP tablet
  • AR augmented reality
  • the embodiment of the present application does not limit the application scenario.
  • a terminal device may also be referred to as a user equipment (UE), an access terminal device, a UE unit, a UE station, a mobile station, a mobile station, a remote station, a remote terminal device, a mobile device, a UE terminal device, a terminal device, Wireless communication device, UE proxy or UE device, and the like.
  • UE user equipment
  • One or more relay nodes are located between the terminal device and the home base station, providing nodes for the wireless access link and the wireless backhaul link.
  • the home base station is a network element for connecting a terminal device, a relay node, and a network device, and may be any device having a wireless transceiver function. Including but not limited to: a base station (NodeB), an evolved base station (eNodeB), a base station (gNB) in the fifth generation (5G) communication system, a base station or network device in a future communication system, and wireless fidelity ( An access node, a wireless relay node, a wireless backhaul node, etc. in a wireless-fidelity, WiFi) system.
  • NodeB NodeB
  • eNodeB evolved base station
  • gNB base station
  • 5G fifth generation
  • a base station or network device in a future communication system
  • wireless fidelity An access node, a wireless relay node, a wireless backhaul node, etc. in a wireless-fidelity, WiFi
  • the network device is connected to the home base station, and the network device prefers the core network, and may also be other devices, such as a ciotserving gateway node (C-SGN), a mobility management entity (MME), and a service gateway ( Serving gateway (S-GW), public data network gateway (P-GW) P-GW, home subscriber server (HSS) HSS, serving GPRS support node (serving gprs support node, SGSN) SGSN, access and mobility management function AMF, user plane function (UPF), 5G core network (NGC), operations management (administration and maintenance) OAM or Remote server, etc.
  • C-SGN ciotserving gateway node
  • MME mobility management entity
  • S-GW service gateway
  • P-GW public data network gateway
  • HSS home subscriber server
  • serving GPRS support node serving gprs support node
  • SGSN serving gprs support node
  • NNC 5G core network
  • OAM operations management
  • the term “plurality” in the present application means two or more, and in view of this, “a plurality” may also be understood as “at least two” in the present application.
  • the character "/”, unless otherwise specified, generally indicates that the contextual object is an "or" relationship.
  • a flowchart of a transmission method provided by the present application includes:
  • Step 301 The second device acquires the first data and the identifier information.
  • the first data is data to be sent to the network device
  • the identification information is identification information of the terminal device or identification information of the relay node
  • the second device is the second relay node or the terminal device.
  • the terminal device accesses one of the second relay nodes, and then accesses the first device after passing through multiple second relay nodes, and the first device is connected.
  • the first relay node that enters the home base station.
  • the second device may obtain the first data generated by the second relay node for the second device, or may be configured by the second device for receiving the second relay node.
  • One data When the second device obtains the first data generated by the second device, the second relay node may notify the network device by using the first device during the process of booting the network, and request the data for acquiring the configuration information of the second relay node, or Data interaction is performed by the first device and the network device during the running of the node.
  • the first data is data that is sent by the terminal device to the network device.
  • the second device acquires the first data, where the second device obtains the first data generated by the terminal device, and the first data may be that the terminal device is finally sent to the terminal device.
  • Network equipment When the second device is the terminal device, the second device acquires the first data, where the second device obtains the first data generated by the terminal device, and the first data may be that the terminal device is finally sent to the terminal device. Network equipment.
  • the first data may be a non-access-stratum protocol data unit (NAS PDU) sent by the terminal device to the network device.
  • NAS PDU non-access-stratum protocol data unit
  • Step 302 The second device sends a first radio resource control (RRC) message.
  • RRC radio resource control
  • the second device After acquiring the first data and the identifier information, the second device sends a first RRC message to the first device, where the first RRC message includes the first data and the identifier information.
  • FIG. 4 exemplarily shows a network architecture supporting two relay nodes provided by the present application.
  • the present application describes two relay nodes as an example, and a network with more than two relay nodes.
  • the architecture is similar to the two relay nodes, and this application is not described here.
  • the relay node (RN) 1 is the first device
  • the RN2 is the second device
  • the DeNB is the home base station.
  • the RN1 and the RN2 support the air interface connection.
  • the RN1 and the RN2 are connected.
  • the inter-base-station interface protocol (such as Xn, X2) and the interface protocol between the base station and the core network (such as NG, S1) may not be supported. This structure may enable the function of the network structure to which the transmission method provided by the present application is applicable. It's even simpler.
  • FIG. 5 is a schematic diagram of a protocol stack supported by each device in the network structure shown in FIG. 4.
  • the UE supports a NAS layer, an RRC layer, a Packet Data Convergence Protocol (PDCP) layer, and a wireless layer.
  • RN1 and RN2 support the RRC layer, the RLC layer, the MAC layer, and the PHY layer in the UE-oriented air interface, where the PDCP layer is optional.
  • the RN supports the RRC layer, the RLC layer, the MAC layer, and the PHY layer in an air interface facing the upper RN or the DeNB, where the PDCP layer is optional.
  • the DeNB supports the RRC, PDCP layer, RLC layer, MAC layer, and PHY layer in the RN-oriented air interface.
  • the DeNB supports the S1-AP/NG-AP layer, the SCTP layer, the IP layer, and the layer 2 (L2) on the interface facing the core network.
  • Layer 1 (L1) The interface of the core network facing the DeNB supports the S1-AP/NG-AP layer, the SCTP layer, the IP layer, the L2, and the L1, and the core network supports the NAS layer.
  • the supported protocol stack is different from the protocol stack supported by the RN shown in FIG. 5, as shown in FIG. 6a and FIG. 6b.
  • the NAS is supported. Layer, RRC layer, PDCP layer, RLC layer, MAC layer, and PHY layer, protocols supported by the air interface of the upper RN1 or DeNB The stack is the same as that in Figure 5 and will not be described.
  • Step 701 The RN1 sends a random access request message.
  • the RN1 selects one of the one or more cells of the DeNB as the serving cell according to the strength and/or quality of the air interface radio signal of the DeNB or the configured serving cell information. RN1 initiates a random access request in the cell.
  • Step 702 The DeNB sends a random access response message.
  • the RN1 receives the random access response message fed back by the DeNB, and carries the resource required by the RN1 to send the RRC connection request in the random access response message.
  • Step 703 The RN1 sends an RRC setup request message.
  • the RN1 sends an RRC connection request message or a new signaling with a similar setup request function to the DeNB, where the request message includes one of the following information: identification information for indicating the identity of the RN2: a random number (40 bits, or other bits) Number), or S-Temporary Mobile Subscriber Identity (S-TMSI) of RN1.
  • the reason for the access may be indicated as being initiated by the RN1; or the indication information of the node access and the terminal access may be distinguished, and is not limited to the access reason.
  • the identity of the home node of the access node/access user the information is used to help the DeNB identify that the RN is a hop relay node. For a Relay node directly connected to the DeNB, the identity of the home node is the DeNB id or the id of its serving cell on the DeNB, that is, the full network identifier (ECGI) of the serving cell.
  • ECGI full network identifier
  • Step 704 Optionally, the DeNB acquires configuration information of the RN1 from the OAM.
  • the DeNB obtains configuration information of the RN1 node from the OAM, and the OAM may be a remote OAM or a local OAM.
  • the DeNB may consider the RN1 as a cell under it, and then request configuration information for the cell. This step may occur before step 705 or after step 705.
  • the DeNB can also generate configuration information of the RN1 node by itself, and then step 704 is not required.
  • Step 705 The DeNB sends an RRC setup message.
  • the DeNB sends an RRC Connection Setup message or new signaling with a similar setup function to the RN.
  • DeNB can query the RN for the radiocapability of the node, then the DeNB stores the radio capabilities of the multi-hop RN node it serves, and establishes a suitable radio link for the RN based on the capability information.
  • the DeNB maintains the backhaul link in a long connection state and does not perform active release. Only when the backhaul link fails to be available, such as a radio link failure, the DeNB performs connection release, and connection re-establishment operations.
  • the DeNB may send the configuration information to the RN1 node in an RRC connection setup message or a new signaling having a similar setup function, and the RN1 node configures its own cell based on the configuration information.
  • the configuration information includes a cell identifier, a system message, and the like, and may be: a global cell identifier (Cell Global Identifier) CGI, a physical cell identity (PCI), a cell's key configuration information: a system (super) frame number, System message scheduling information, access control enable indication, deployment mode, system message change label, downlink frequency information, and so on. Access information of the serving cell and scheduling information of other system message blocks.
  • Wireless common resource related configuration information UE timers and constants, UL frequency points, etc. Cell selection and reselection, neighbor cell configuration information, and the like. Access control information, etc., ACB, EAB, AB access information, etc. System time information. RN1 can configure its own cell based on the received configuration information.
  • the node configuration information of the RN1 may be acquired after the RRC connection establishment of the RN1 is completed, and then acquired by the DeNB and sent by the DeNB to the RN1.
  • Step 706 The RN1 sends an RRC setup complete message.
  • the RN1 sends an RRC Connection Setup Complete message or a new signaling with a similar setup confirmation function to the DeNB.
  • the NAS PDU may not be included in the message.
  • step 707 and step 708 need to be performed on the backhaul link, otherwise step 707 and step 708 are not performed on the backhaul link.
  • Step 707 The DeNB sends a downlink RRC message.
  • the DeNB After the RN1 completes the connection establishment, the DeNB sends the configuration information acquired by the OAM to the RN1 node by using a downlink RRC message to configure the RN1 as the configuration information of the cell of the DeNB, where the configuration information of the RN1 may include the system message of the cell, etc.
  • the included message has been described in the above step 705 and will not be described again.
  • a possible implementation method is that the configuration information of the cell is from OAM to
  • the MME transmits the IP packet and then transmits it to the DeNB in the NAS PDU mode at the MME.
  • the DeNB sends the configuration information to the RN1 using a downlink transmission message.
  • Step 708, RN1 completes startup.
  • the RN1 configures its own cell based on the received configuration information and completes the startup.
  • the process described in the foregoing step is the process of starting the RN1.
  • the following describes the process of starting the RN2 that accesses the RN1 through the process shown in FIG.
  • Step 801 The RN2 sends a random access request message.
  • the RN2 selects one of the one or more cells in the RN1 as the serving cell according to the strength and/or quality of the air interface radio signal of the RN1 or the configured serving cell information, and the RN2 sends a random access request message to the RN1.
  • Step 802 The RN1 sends a random access response message.
  • the RN2 receives the random access response message fed back by the RN1, and carries the resource required by the RN2 to send the RRC connection request in the random access response message.
  • Step 803 The RN2 sends an RRC setup request message.
  • the RN2 sends an RRC Connection Request message or a new signaling with a similar setup request function to the RN1, where the request message includes one of the following information: identification information for indicating the identity of the RN2: a random number (40 bits, or other bits) Number), or S-Temporary Mobile Subscriber Identity (S-TMSI) of RN1.
  • identification information for indicating the identity of the RN2 a random number (40 bits, or other bits) Number), or S-Temporary Mobile Subscriber Identity (S-TMSI) of RN1.
  • S-TMSI S-Temporary Mobile Subscriber Identity
  • the reason for the access may be indicated as being initiated by the RN2; or the indication information of the node access and the terminal access may be distinguished, and is not limited to the access reason.
  • the identity of the home node of the access node/access user, the information is used to help the DeNB identify that the RN2 is the hop relay node.
  • the identity of the home node is the DeNB id or the id of its serving cell on the DeNB, that is, the evolved-universal mobile communication system of the serving cell, the global radio access network cell global identifier (evolved universal mobile) Telecommunications system terrestrial radio access network cell global identifier (ECGI).
  • the global radio access network cell global identifier evolved universal mobile Telecommunications system terrestrial radio access network cell global identifier (ECGI).
  • Step 804 RN1 sends an uplink RRC message.
  • RN1 After receiving the connection establishment request sent by RN2, RN1 identifies the cause value or the RN indication information. It is the access of the next hop RN2, and the RN1 forwards the setup message of the RN1 through the uplink RRC message on the established wireless backhaul link between the RN1 and the DeNB. The RN1 may also obtain the access request of the RN2 after the RRC setup complete message of the RN2. At this time, after receiving the connection establishment complete message sent by the RN2, the RN1 identifies the next hop by the cause value or the RN indication information. For the access of the RN2, the RN1 forwards the setup message of the RN2 through the RRC message on the established wireless backhaul link between the RN1 and the DeNB.
  • the RN2 setup message forwarded on the backhaul link includes: an access reason, a home node identifier of the access node/access terminal, and a cell identifier.
  • Step 805 Optionally, the DeNB acquires configuration information of the RN2 from the OAM.
  • the DeNB acquires the access request information of the RN2 from the RN1 node, and obtains the configuration information of the RN2 node from the OAM, where the OAM can be the remote OAM, or the local DUA can treat the RN2 as a cell under it, and then request configuration for the cell. information.
  • the DeNB may also generate configuration information of the RN2 node by itself, and then step 805 is not required.
  • Step 806 The DeNB sends a downlink RRC message.
  • the DeNB sends the configuration information of the RN2 by using the downlink RRC message on the backhaul link that has been established with the RN1.
  • the configuration information of the cell includes the system information of the cell, and the content of the eNB is described in the foregoing steps, and details are not described herein.
  • a possible implementation method is that the configuration information of the cell is from OAM to
  • the MME transmits the IP packet and then transmits it to the DeNB in the NAS PDU mode at the MME.
  • the DeNB sends the configuration information to the RN1 using a downlink transmission message.
  • Step 807 The RN1 sends an RRC setup message.
  • RN1 After receiving the configuration information, RN1 sends an RRC connection setup message or new signaling with similar setup function to RN2. For RN2, RN1 may query RN2 for the radio capabilities of the node, then RN1 stores the radio capabilities of the multi-hop RN it serves, and establishes a suitable radio link for RN2 based on the capability information. Or the RN1 reports the acquired radio capability of the RN2 of the next hop to the DeNB for storage. When the RN1 needs to acquire the radio capability of the RN2 of the next hop, it requests from the DeNB. RN1 establishes a suitable radio link for RN2 based on the capability information.
  • the DeNB maintains the backhaul link in a long connection state and does not perform active release because it is a function of the wireless backhaul. Only when the backhaul link fails to be available, such as a radio link failure, the DeNB performs connection release, and connection re-establishment operations.
  • the RN1 may send the cell configuration information to the RN2 in an RRC connection setup message or a new signaling having a similar setup function, and the RN2 configures its own cell function based on the configuration information.
  • the configuration information of the cell includes a cell identifier, a system message, and the like.
  • Step 808 The RN2 sends an RRC setup complete message.
  • the RN2 sends an RRC Connection Setup Complete message or a new signaling with a similar setup confirmation function to the RN1.
  • the NAS PDU may not be included in the message. If the RN2 supports the NAS layer, the message may include a special NAS PDU indicating the establishment completion confirmation function for the RN2.
  • Step 809 RN1 sends a downlink RRC message.
  • the RN1 After the RN2 completes the establishment of the RRC connection, the RN1 passes the configuration information acquired from the DeNB through a downlink RRC.
  • the message is sent to the RN2 node as the configuration information of the RN2 as a cell of the RN1, and the configuration information including the RN2 may include the system message of the cell, etc., and the specifically included message has been described in the foregoing steps, and is not described herein.
  • Step 810 RN2 completes the startup.
  • the RN2 configures its own cell based on the received configuration information and completes the startup.
  • the DeNB needs to maintain the routing information of RN1 and RN2 in the process of starting RN1 and RN2. Specifically, the DeNB may start to establish the routing table 1 for the RN1 after the foregoing step 704 or step 706. The DeNB may begin to establish an update to the routing table 1 of RN1 after step 805 or step 809. The DeNB may begin to establish routing table 2 for RN2 after step 806 or step 808.
  • the routing information that the DeNB can maintain mainly includes the following information: the home node id: the information is reported by the RN node at the time of access or forwarded by the serving RN to the DeNB, and is used by the DeNB to maintain the hop count information of the RN. If the information of the home node id is the DeNB id or the id of a non-RN cell of the DeNB, the DeNB knows that the RN is its directly serving RN and is a 2-hop RN, such as RN1. If the home node id is an RN served by a certain DeNB, the DeNB knows that the RN is a hop of 3 hops or more, such as RN2.
  • the RN indicates information: the information is used to indicate whether the access is an RN access or a normal UE access.
  • the indication manner may be a special cause value, such as a cause value set to RN access, and the like. Or 1 sign to indicate. For example, 1 bit, 1 is the RN access, 0 is the UE access; or vice versa, 0 is the UE access, 1 is the RN access, and the like.
  • Another possible indication is that if there is an RN indication, the RN is accessed, and if there is no indication, the UE is accessed.
  • RN UE id/UE id This information is the C-RNTI allocated by the DeNB or the RN node of the previous hop when the DeNB or RN accesses the backhaul link as the UE identity.
  • the DeNB wants to maintain the routing information of the RN2 under the RN1, the RN1 needs to carry the allocated RN2 UE id to the DeNB.
  • the C-RNTI that RN1 and RN2 need to allocate RN2 to the UE is carried on the backhaul link to the previous hop RN node, such as RN1, and the home base station, such as the DeNB.
  • the content of the routing table 1 of the RN1 established on the DeNB may be as shown in Table 1, indicating that the RN1 is connected to the DeNB through a wireless backhaul link.
  • routing table 2 established on RN2 can be as shown in Table 2, indicating that RN2 is connected through a wireless backhaul link. Received on RN1.
  • the routing table 1 on the DeNB is updated as shown in Table 3.
  • the DeNB can learn that the previous hop node of the RN2 is the RN1, and the last hop node of the RN1 is the DeNB.
  • RN2 When a UE accesses RN2, RN2 maintains a routing table 3, indicating that the UE is accessed from RN2.
  • the specific content is shown in Table 4, where the UE id is assumed to be C-RNTI3.
  • the routing table 2 is updated as shown in Table 5, indicating that the UE is connected from the RN2 and connected to the DeNB via the RN1:
  • the routing table 1 on the DeNB is updated as shown in Table 6.
  • the DeNB can learn that the UE accesses the DeNB via RN2 and RN1.
  • the DeNB and the RN can correctly route data from different RNs to implement correct routing of data on multiple RNs.
  • the UE may access RN1 or RN2, and then send data to the network device through RN1 or the RN2.
  • the process of the UE accessing the RN2, as shown in FIG. 9, specifically includes:
  • Step 901 The UE sends a random access request message.
  • the UE selects one of the one or more cells of the RN2 as the serving cell according to the strength and/or quality of the air interface radio signal of the RN2, and the UE initiates random access to the RN2.
  • Step 902 The RN2 sends a random access response message.
  • the UE receives the random access response message fed back by the RN2, and carries the resource required for the UE to send the RRC connection request in the random access response message.
  • Step 903 The UE sends an RRC setup request message.
  • This step 903 may further include steps 903a to 903e.
  • the UE initiates RRC by using the resource scheduled by the RN2.
  • a connection establishment request where the RRC connection setup message carries a UE NAS id (40 bit random number, or S-TMSI), and establishes a cause value, a capability of the UE, and the like.
  • the RN2 may send an uplink RRC message, such as an uplink transmission message, or a newly defined RRC signaling, to establish the NAS id of the UE, and establish the uplink RRC message.
  • the cause value or the early transmission uplink data is sent to the RN1, and the RN1 sends the uplink RRC message on the wireless backhaul link that has been established with the DeNB, and sends the NAS id, the establishment cause value, or the early transmission uplink data of the UE to the DeNB.
  • the DeNB sends signaling to the MME to acquire capability information of the UE.
  • the DeNB sends the capability information of the UE to the RN1 through the downlink RRC signaling, for example, the new RRC signaling or the downlink transmission message, and the RN1 sends the RN1 to the RN2 through the downlink RRC message.
  • the RN2 sends an RRC setup message to send the capability information of the UE to the UE.
  • Step 904 The RN2 sends an RRC setup message.
  • the RN2 After obtaining the capability of the UE, the RN2 establishes an RRC connection for the UE, and sends an RRC setup message to the UE. At this time, the capability information of the UE may be sent to the UE by using an RRC setup message.
  • Step 905 The UE sends an RRC setup complete message.
  • the UE may send the NAS PDU to be transmitted to the RN2 node in the RRC setup complete message sent to the RN2, so that the RN2 node sends the NAS PDU to the DeNB through the RN1.
  • the RN2 may send the first RRC message to the RN1, where the message includes the first data and the identifier information.
  • the first RRC message may be an uplink transmission message, or may be a newly defined RRC signaling, and may further include information such as a UE NAS id, a establishment cause value, and the like. If the information has been transmitted in the foregoing steps 903a and 903b, the The step may not include the two pieces of information, and may also include the two pieces of information.
  • the first RRC message may also include a C-RNTI allocated by the RN2 for the UE, and the RN1 updates the routing table.
  • Step 303 The first device receives the first RRC message.
  • the RN1 may determine, by using the identifier information of the second device carried in the first RRC message, the DeNB of the RN1 corresponding to the identifier information, where the purpose is to select The first data carried in the first RRC message is sent to whom.
  • the first RRC message may further include a relay indication, where the relay indication is used to notify the network device and/or the home base station.
  • the second device is a relay node, and the relay indicates a cause value in a flow that can be initiated by the RN.
  • Step 304 The first device sends a second RRC message.
  • the RN2 When the RN2 determines that the first data needs to be forwarded to the DeNB, the RN2 forwards the first data and the identifier information to the DeNB by using the second RRC message, for example, may be an uplink data transmission message.
  • the DeNB After receiving the first data and the identifier information, the DeNB initiates the S1 initial UE information to the MME, and establishes a mapping relationship between the air interface of the UE and the S1 according to the received identifier information.
  • the specific parameters may include: the RN node id, the UE. Id and S1AP id.
  • the RN node id and the UE id are described in the above process.
  • the S1AP id indicates the MME UE S1AP ID or the eNB UE S1AP ID, or another ID that identifies the UE's connection at the S1 port.
  • the DeNB When the DeNB receives a downlink NAS PDU on the S1AP connection of the MME, the DeNB selects a route of the next hop RN for the UE according to the mapping relationship between the air interface of the UE and the S1 and the routing table information.
  • the DeNB sends a downlink RRC message to the RN1 on the radio link, where the RRC message may be a downlink transmission message or a newly defined RRC signaling. If the radio link is a backhaul link, the downlink data packet needs to be included.
  • the RN Node id is not included in the downlink transmission message, and the UE id, including from DL NAS PDU of the MME.
  • the RN1 searches for a local routing table, finds a corresponding air interface link or a backhaul link, and sends a downlink RRC message to the link.
  • the RRC message may be a downlink transmission message or a new one. Defining RRC signaling, if the radio link is a backhaul link, including the downlink data packet needs to reach the RN node id and the UE id of the RN; if the link is a radio access link, transmitting the downlink transmission message
  • the RN Node id is not included, and the UE id includes the DL NAS PDU from the MME.
  • the RN2 sends a line transfer message to the UE, including the NAS PDU from the MME.
  • the RN2 may initiate a connection release message, and the RN2 sends an RRC connection release request message to the serving node RN1, which carries the UE id information to be released; the RN1 forwards the connection release message, which carries the RN node id and UE id information to the DeNB.
  • the DeNB searches for a mapping table between the UE and the S1 port, finds a corresponding S1AP connection that needs to be released, and requests a release from the MME to request a release message from the MME.
  • the DeNB receives the release command from the MME, and the DeNB sends an RRC release message to the RN1, and the RN1 carries the RN node id and the UE id indication of the link to be released.
  • the node also needs to notify its serving node and the DeNB and MME of the serving node to delete the corresponding backhaul link and the S1 connection.
  • the name of the RRC message on the backhaul link at this time may be changed to RRC connection release, which is a notification message, not a request message.
  • the name of the release message at the S1 port may also change, and the request information is changed to a notification message.
  • the serving RN node updates its routing table
  • the DeNB updates its air interface and S1 port mapping relationship table and the routing table of the UE.
  • the above embodiment indicates that the first device receives the first RRC message sent by the second device, where the first RRC message includes the first data and the identifier information, and then the first device sends the first RRC message to the home base station of the first device by using the second RRC message.
  • a data and identification information Since the first device and the second device use RRC messages to transmit data, the network functions of the first device and the second device are simplified, and the transmission efficiency of data after accessing the plurality of relay nodes in the NB-IoT network is improved.
  • FIG. 10 is a schematic structural diagram of a transmission device provided by the present application.
  • the transmission device 1000 may be the first device, the second device, or the first device, the chip in the second device, or the like, as shown in FIG.
  • the transmission device 1000 can be used to perform the method described in the above embodiments, and to perform any of the transmission methods in the above embodiments.
  • the transmission device 1000 includes at least one processor 1001, at least one communication interface 1004, and optionally a memory 1003.
  • the processor 1001 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the programs in this application.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the memory 1003 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compressed discs, lasers Disc, optical disc, digital versatile disc, Blu-ray disc, etc.), magnetic storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of an instruction or data structure and accessible by a computer. , but not limited to this.
  • the memory 1003 may be independent and connected to the processor 1001 via a bus.
  • the memory 1003 can also be integrated with the processor 1001.
  • the memory 1003 is configured to store application code for executing the present application, and is controlled by the processor 1001 for execution.
  • the processor 1001 is configured to execute application code stored in the memory 1003.
  • the processor 1001 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • the transmission device 1000 may include multiple processors, such as the processor 1001 and the processor 1008 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the first device in FIG. 3 may be the transmission device shown in FIG. 10, and one or more software modules are stored in the memory of the transmission device.
  • the transmission device can implement the software module through the processor and the program code in the memory, and implement the flow executed by the first device in any embodiment of the present application.
  • the second device in FIG. 3 may be the transmission device shown in FIG. 10, in which one or more software modules are stored in the memory of the transmission device.
  • the transmission device can implement the software module through the processor and the program code in the memory, and implement the process performed by the second device in any embodiment of the present application.
  • the application may divide the function module into the transmission device according to the above method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the present application is schematic, and is only a logical function division, and may be further divided in actual implementation.
  • FIG. 11 is a schematic structural diagram of a transmission device involved in the foregoing embodiment, where the transmission device is the first device or the second device,
  • the transmission device includes a receiving unit 1101, a processing unit 1102, and a transmitting unit 1103.
  • the present application further provides a communication system, including a first device, a second device, and a home base station; the first device is a first relay node that accesses a home base station, and the second device is the second device. Following a node or a terminal device;
  • the second device acquires the first data and the identifier information, where the first data is data to be sent to the network device, and the identifier information is identifier information of the terminal device or identifier information of the relay node; Sending a first RRC message to the first device, where the first RRC message includes the first data and the identifier information;
  • the first device receives the first RRC message sent by the second device, and sends the first data and the identifier information to the home base station of the first device by using a second RRC message.
  • the present application also provides a communication system including a first relay node, a plurality of second relay nodes, a terminal device, and a home base station;
  • the terminal device After the terminal device accesses the cascaded multiple second relay nodes, the terminal device accesses the first relay node;
  • the first relay node is connected to the home base station.
  • the present application also provides a computer storage medium for storing computer software instructions for use in the transmission device shown in FIG. 10 or FIG. 11 above, which includes program code for performing the above-described method embodiments.
  • the application also provides a computer program product.
  • the computer program product includes computer software instructions that are loadable by a processor to implement the methods of the above method embodiments.

Abstract

一种传输方法及设备，该方法包括第一设备接收第二设备发送的第一RRC消息，该第一RRC消息包括第一数据和标识信息，然后第一设备通过第二RRC消息向第一设备的归属基站发送第一数据和标识信息。由于第一设备和第二设备采用RRC消息来发送数据，简化了第一设备和第二设备的网络功能，改善了NB-IoT网络中接入多个中继节点之后的数据的传输效率。

Description

一种传输方法及设备 技术领域
本申请涉及物联网通信技术领域，尤其涉及一种传输方法及设备。
背景技术
随着无线通信的快速发展，人们早已不满足与仅限于人与人的通信，物联网(internet of things，IoT)技术应运而生，并且其市场需求增长迅猛。IoT设备多是比较小巧、电池供电的系统，如智能抄表系统，需要对水、电煤气等使用情况进行周期性监测并上报，这些设备通常部署在地下室、墙壁中等无线信号覆盖很差的地方。所以在IoT通信系统设计时，将覆盖增强作为一个基本的设计需求，在空口单跳方面要求达到20dB的覆盖增强。
该IoT空口单跳的20dB的覆盖增强，能满足大部分场景下的覆盖要求，但是在一些特殊的场景下，比如对于楼宇等多层分布的场景下，如果基站位于楼顶，则靠近基站近的楼层的IoT设备可以被服务到，但是离基站比较远的楼层的IoT设备可能无法被服务到。还有一些场景，比如一些煤气表等在比较深的底下，也可能一跳无法到达。而在这些场景中，有线的回程链路的部署也比较困难，这种情况下，采用低功耗的无线接入节点作为多跳中继是一种可能的解决方法。
目前在长期演进(long term evolution，LTE)标准中，已经可以支持两跳的中继传输方案，该两跳中继的网络架构可以如图1所示。从图1中可以看出，该网络架构包括中继节点(relay node，RN)、基站(eNodeB，eNB)、归属基站(donor eNB，DeNB)和移动管理实体(mobility management entity，MME)或业务网关(serving gate way，S-GW)，RN到DeNB之间是通过Un接口来连接的，在Un的空口上，支持X2和S1协议。目前LTE网络中的RN是一个基站和一个UE的网络功能的结合，如果在NB-IoT网络中通过该RN来实现多跳中继，也是可行的，但在现有的网络功能的基础上，RN还需要承担上一跳中继节点的DeNB的网络功能，因此，在NB-IoT网络中的RN的网络功能要比LTE网络中搞得RN的网络功能更加复杂，不能满足有简单部署要求的NB-IoT网络对于RN的要求，因此亟需引入一种网络功能简单的中继节点。
发明内容
本申请提供一种传输方法及设备，用以改善NB-IoT网络中接入多个中继节点之后的数据的传输效率。
第一方面，提供一种传输方法，包括：
第一设备接收第二设备发送的第一无线资源控制(radio resource control，RRC)消息，所述第一RRC消息包括第一数据和标识信息，所述第一数据为待发送给网络设备的数据；所述第一设备为接入归属基站的第一中继节点，所述第二设备为第二中继节点或者为终端设备，所述标识信息为所述终端设备的标识信息或者中继节点的标识信息；所述第一设备通过第二RRC消息向所述第一设备的归属基站发送所述第一数据 和所述标识信息。
由于第一设备和第二设备采用RRC消息来发送数据，简化了第一设备和第二设备的网络功能，改善了NB-IoT网络中接入多个中继节点之后的数据的传输效率。
一种可能的设计中，在所述第一设备通过第二RRC消息向第一设备的归属基站发送所述第一数据和所述标识信息之前，还包括：所述第一设备根据所述标识信息，确定与所述标识信息所对应的所述第一设备的归属基站，所述第一设备通过第二RRC消息向所述第一设备的归属基站发送所述第一数据和所述标识信息。
通过标识信息得到与该标识信息所对应的第一设备的归属基站，可以获知数据需要传输的目的地，从而可以改善数据的传输效率。
一种可能的设计中，所述第一数据为所述终端设备发送给网络设备的非接入层协议数据单元(non-access-stratumprotocol data unit，NAS PDU)。
一种可能的设计中，所述第二中继节点为所述终端设备接入的中继节点。
一种可能的设计中，所述第一设备接收第二设备发送的第一RRC消息之前，所述方法还包括：所述第一设备根据所述归属基站的空口无线信号的强度和/或质量，或者配置的服务小区信息，将所述归属基站的一个小区确定为服务小区，所述第一设备向所述服务小区发起随机接入，与所述归属基站建立RRC连接，所述第一设备接收所述归属基站发送的配置信息，并根据所述配置信息配置自身的小区。
通过向归属基站注册，并获取归属基站发送的配置信息，从而完成自身的配置，为改善NB-IoT网络中接入多个中继节点之后的数据的传输效率提供支持。
一种可能的设计中，所述第一设备接收第二设备发送的第一RRC消息之前，所述方法还包括：所述第一设备接收所述第二设备发起的RRC连接请求消息，并与所述第二设备建立RRC连接。
一种可能的设计中，当所述标识信息为中继节点的标识信息，所述第一RRC消息还包括中继指示，所述中继指示用于向网络设备和/或所述归属基站通知所述第二设备为中继节点。
第二方面，提供一种传输方法，包括：
第二设备获取第一数据和标识信息，其中，所述第一数据为待发送给网络设备的数据，所述标识信息为所述终端设备的标识信息或者中继节点的标识信息，所述第二设备为第二中继节点或者为所述终端设备，所述第二设备向第一设备发送第一RRC消息，所述第一RRC消息包括所述第一数据和所述标识信息；所述第一设备为接入归属基站的第一中继节点。
由于第一设备和第二设备采用RRC消息来发送数据，简化了第一设备和第二设备的网络功能，改善了NB-IoT网络中接入多个中继节点之后的数据的传输效率。
一种可能的设计中，当所述第二设备为所述第二中继节点时，所述第二设备获取第一数据，包括：所述第二设备获取所述第二中继节点自己生成的第一数据，或者所述第二设备接收所述终端设备发送的第一数据。
一种可能的设计中，所述第二中继节点为所述终端设备接入的中继节点。
一种可能的设计中，当所述第二设备为终端设备时，所述第二设备获取第一数据，包括：所述第二设备获取终端设备自己生成的第一数据。
第三方面，提供一种传输设备，包括：接收单元和发送单元；
所述接收单元，用于接收第二设备发送的第一RRC消息，所述第一RRC消息包括第一数据和标识信息，所述第一数据为待发送给网络设备的数据；所述传输设备为第一设备，所述第一设备为接入归属基站的第一中继节点，所述第二设备为第二中继节点或者为所述终端设备，所述第二设备接入第一设备，所述标识信息为所述终端设备的标识信息或者中继节点的标识信息；所述发送单元，用于通过第二RRC消息向所述第一设备的归属基站发送所述接收单元接收的第一数据和所述标识信息。
一种可能的设计中，所述第一数据为所述终端设备发送给网络设备的NAS PDU。
一种可能的设计中，还包括处理单元；所述处理单元，用于在所述发送单元通过第二RRC消息向所述第一设备的归属基站发送所述接收单元接收的第一数据和所述标识信息之前，根据所述接收单元接收的标识信息，确定与所述标识信息所对应的所述第一设备的归属基站。
一种可能的设计中，所述第二中继节点为所述终端设备接入的中继节点。
一种可能的设计中，所述处理单元还用于：根据所述归属基站的空口无线信号的强度和/或质量，或者配置的服务小区信息，将所述归属基站的一个小区确定为服务小区；
向所述服务小区发起随机接入，与所述归属基站建立RRC连接；
所述接收单元还用于接收所述归属基站发送的配置信息；
所述处理单元还用于根据所述接收单元接收的所述配置信息配置自身的小区。
一种可能的设计中，所述接收单元接收第二设备发送的第一RRC消息之前，所述接收单元还用于接收所述第二设备发起的RRC连接请求消息；
所述处理单元还用于与所述第二设备建立RRC连接。
一种可能的设计中，当所述标识信息为中继节点的标识信息，所述第一RRC消息还包括中继指示，所述中继指示用于向网络设备和/或所述归属基站通知所述第二设备为中继节点。
第四方面，提供一种多路中继的传输设备，包括：发送单元和处理单元；
所述处理单元，用于获取第一数据和标识信息，其中，所述第一数据为待发送给网络设备的数据，所述标识信息为所述终端设备的标识信息或者中继节点的标识信息，所述传输设备为所述第二中继节点或者为所述终端设备；
所述发送单元，用于向第一设备发送第一RRC消息，所述第一RRC消息包括所述处理单元获取的第一数据和所述标识信息；所述第一设备为接入归属基站的中继节点。
一种可能的设计中，还包括接收单元；
所述处理单元具体用于，当所述传输设备为所述第二中继节点时，获取第二中继节点自己生成的第一数据；或者
所述处理单元控制所述接收单元接收所述终端设备发送的第一数据。
一种可能的设计中，所述处理单元具体用于，当所述传输设备为终端设备时，获取终端设备自己生成的第一数据。
第五方面，本申请提出了一种传输设备，包括：通信接口、处理器和存储器；所述存储器用于存储软件程序，所述处理器用于读取所述存储器中存储的软件程序，通过所述通信接口收发数据，并实现第一方面、第一方面任一种可能的实现方式所述的 方法。
第六方面，本申请提出了一种传输设备，包括：通信接口、处理器和存储器；所述存储器用于存储软件程序，所述处理器用于读取所述存储器中存储的软件程序，通过所述通信接口收发数据，并实现第二方面、第二方面任一种可能的实现方式所述的方法。
第七方面，本申请提供了一种通信系统，包括第一设备、第二设备和归属基站；所述第一设备为接入归属基站的第一中继节点，所述第二设备为所述第二中继节点或者为终端设备；
所述第二设备获取第一数据和标识信息，其中，所述第一数据为待发送给网络设备的数据，所述标识信息为所述终端设备的标识信息或者中继节点的标识信息；以及向所述第一设备发送第一RRC消息，所述第一RRC消息包括所述第一数据和所述标识信息；
所述第一设备接收所述第二设备发送的第一RRC消息；并通过第二RRC消息向所述第一设备的归属基站发送所述第一数据和所述标识信息。
第八方面，本申请提供一种计算机可读存储介质，包括计算机可读指令，当计算机读取并执行所述计算机可读指令时，使得计算机执行如第一方面任意一项所述的方法。
第九方面，本申请提供一种计算机可读存储介质，包括计算机可读指令，当计算机读取并执行所述计算机可读指令时，使得计算机执行如第二方面任意一项所述的方法。
第十方面，本申请提供一种计算机程序产品，包括计算机可读指令，当计算机读取并执行所述计算机可读指令，使得计算机执行如第一方面任意一项所述的方法。
第十一方面，本申请提供一种计算机程序产品，包括计算机可读指令，当计算机读取并执行所述计算机可读指令，使得计算机执行如第二方面任意一项所述的方法。
附图说明
图1为本申请提供的一种网络架构的结构示意图；
图2为本申请提供的一种通信网络系统的结构示意图；
图3为本申请提供的一种传输方法的流程示意图；
图4为本申请提供的一种网络架构的结构示意图；
图5为本申请提供的一种协议栈的结构示意图；
图6a为本申请提供的一种协议栈的结构示意图；
图6b为本申请提供的一种协议栈的结构示意图；
图7为本申请提供的一种RN启动的流程示意图；
图8为本申请提供的一种RN启动的流程示意图；
图9为本申请提供的一种UE接入RN的流程示意图；
图10为本申请提供的一种传输设备的结构示意图；
图11为本申请提供的一种传输设备的结构示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。
本申请提供了一种传输方法，该方法可以应用于通信网络系统中。请参考图2所示，为本申请提供的一种可能的通信网络系统的结构图。如图2所示，该通信网络系统包括终端设备、多个中继节点、归属基站和网络设备。
终端设备可以是一种具有无线收发功能的设备可以部署在陆地上，包括室内或室外、手持、穿戴或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。所述终端设备可以是手机(mobile phone)、物联网(IoT)终端设备、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual Reality，VR)终端设备、增强现实(augmented Reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。本申请的实施例对应用场景不做限定。终端设备有时也可以称为用户设备(user equipment，UE)、接入终端设备、UE单元、UE站、移动站、移动台、远方站、远程终端设备、移动设备、UE终端设备、终端设备、无线通信设备、UE代理或UE装置等。
一个或多个中继节点位于终端设备和归属基站之间，提供无线接入链路和无线回程链路的节点。
归属基站为用于连接终端设备、中继节点和网络设备的网元，其可以是任意一种具有无线收发功能的设备。包括但不限于：基站(NodeB)、演进型基站(eNodeB)、第五代(the fifth generation，5G)通信系统中的基站(gNB)、未来通信系统中的基站或网络设备、无线保真(wireless-fidelity，WiFi)系统中的接入节点、无线中继节点、无线回传节点等。
网络设备与归属基站连接，该网络设备首选核心网，还可以是其它设备，比如物联网服务网关(ciotserving gateway node，C-SGN)、移动性管理实体(mobility management entity，MME)、服务网关(serving gateway，S-GW)、公用数据网网关(public data network gateway，P-GW)P-GW、归属签约用户服务器(home subscriber server，HSS)HSS、服务GPRS支持节点(serving gprs support node，SGSN)SGSN、接入和移动管理功能(access and mobility management function)AMF、用户面功能(user planefunction，UPF)、5G核心网(nextgen core，NGC)，运营管理维护(operations，administration and maintenance)OAM或者远端的服务器等。
需要说明的是，本本申请中的术语“多个”是指两个或两个以上，鉴于此，本申请中也可以将“多个”理解为“至少两个”。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，字符“/”，如无特殊说明，一般表示前后关联对象是一种“或”的关系。
下面将结合附图对本申请提供的一种传输方法进行具体说明。
参加图3，本申请提供的一种传输方法的流程图，包括：
步骤301、第二设备获取第一数据和标识信息。
在本申请中，该第一数据为待发送给网络设备的数据，该标识信息为终端设备的标识信息或者中继节点的标识信息，该第二设备为第二中继节点或者终端设备。本申请中可以存在多个第二中继节点的情况，终端设备接入其中一个第二中继节点，然后再经过多个第二中继节点后接入第一设备，该第一设备为接入归属基站的第一中继节点。
当上述第二设备第二中继节点时，该第二设备获取第一数据可以为第二设备获取第二中继节点自己生成的第一数据，也可以为第二设备接收终端设备发送的第一数据。该第二设备获取自己生成的第一数据时，可以是该第二中继节点在开机接入网络的过程中通过第一设备通知网络设备，用于请求获取自身配置信息的数据，或者在中继节点运行过程中通过第一设备和网络设备进行数据交互。该第二设备接收终端设备发送的第一数据时，该第一数据是终端设备发送给网络设备的数据。
当上述第二设备为终端设备时，该第二设备获取第一数据，具体为第二设备获取终端设备自己生成的第一数据，该第一数据可以是终端设备是经由第一设备最终发送给网络设备的。
需要说明的是，在本申请中，该第一数据可以为终端设备发送给网络设备的非接入层协议数据单元(non-access-stratumprotocol data unit，NAS PDU)。
步骤302、第二设备发送第一无线资源控制(radio resource control，RRC)消息。
第二设备在获取第一数据和标识信息之后，向第一设备发送第一RRC消息，该第一RRC消息中包括该第一数据和标识信息。
图4示例性的示出了本申请提供的一种支持2个中继节点的网络架构，为了便于描述，本申请以2个中继节点为例进行描述，多于2个中继节点的网络架构于2个中继节点类似，本申请不在赘述。
如图4所示，中继节点(relay node，RN)1为第一设备、RN2为第二设备，DeNB为归属基站，其中，RN1和RN2之间支持空口连接，可选的，RN1和RN2之间可以不支持基站间接口协议(如Xn、X2)和基站与核心网间的接口协议(如NG、S1)等，这种结构可以使得本申请提供的传输方法所适用的网络结构的功能更加简单。
图5为图4所示的网络结构中各设备所支持的协议栈的架构，如图5所示，UE支持NAS层、RRC层、分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路层控制协议(Radio Link Control，RLC)层、介质访问控制(Media Access Control，MAC)层和物理(Physical，PHY)层。RN1和RN2在面向UE的空口支持RRC层、RLC层、MAC层和PHY层，其中PDCP层是可选的。该RN在面向上一级RN或者DeNB的空口支持RRC层、RLC层、MAC层和PHY层，其中PDCP层是可选的。DeNB在面向RN的空口支持RRC、PDCP层、RLC层、MAC层和PHY层，DeNB在面向核心网的接口支持S1-AP/NG-AP层、SCTP层、IP层、层2(L2)、层1(L1)。核心网面向DeNB的接口支持S1-AP/NG-AP层、SCTP层、IP层、L2、L1，此外核心网支持NAS层。
在RN作为UE接入时，其支持的协议栈与图5中所示的RN支持的协议栈不同，具体的如图6a及图6b所示，RN2和RN1作为UE接入时，其支持NAS层、RRC层、PDCP层、RLC层、MAC层和PHY层，其上一级RN1或者DeNB的空口支持的协议 栈和图5中的的相同，不在赘述。
基于上述描述，下面将具体的描述第一设备和第二设备启动的流程，如图7所示，具体为：
步骤701、RN1发送随机接入请求消息。
RN1根据DeNB的空口无线信号的强度和/或质量，或者配置的服务小区信息，选择DeNB的一个或多个小区中的一个小区作为服务小区。RN1在该小区发起随机接入请求。
步骤702、DeNB发送随机接入响应消息。
RN1接收DeNB反馈的随机接入响应消息，在该随机接入响应消息中携带该RN1发送RRC连接请求需要的资源。
步骤703、RN1发送RRC建立请求消息。
RN1向DeNB发送RRC连接请求消息或者具有类似建立请求功能的新的信令，在该请求消息中，包括如下信息之一：用于标示RN2身份的标识信息：随机数(40比特，或者其他位数)，或者RN1的(S-Temporary Mobile Subscriber Identity)S-TMSI。接入原因，可以指示为RN1启动；或者可以区分节点接入和终端接入的指示信息，不限于接入原因。该接入节点/接入用户的归属节点的标识，该信息用于帮助DeNB识别该RN是第几跳中继节点。对于直接连接到DeNB的Relay节点，其归属节点的标识即为DeNB id或者DeNB上其服务小区的id，即服务小区的全网标识(ECGI)。
步骤704、可选的，DeNB向OAM获取RN1的配置信息。
DeNB向OAM获取RN1节点的配置信息，该OAM可以为远端OAM，或者本地OAM，DeNB可以将RN1视为其下的一个小区，然后为该小区请求配置信息。该步骤可以发生在步骤705之前，也可以发生在步骤705之后。
DeNB也可以自己生成RN1节点的配置信息，则无需执行步骤704。
步骤705、DeNB发送RRC建立消息。
DeNB向RN发送RRC连接建立消息或者具有类似建立功能的新的信令。对于RN节点DeNB可以向RN询问节点的无线能力(radiocapability)，然后DeNB存储其服务的多跳RN节点的无线能力，基于该能力信息为RN建立合适的无线链路。可选的，对于该无线链路，由于是承担无线回程的功能，DeNB维护该回程链路位于长连接态，不进行主动释放。只有当该回程链路发生无线链路失败等不可用的情况时，DeNB进行连接释放，和连接重建立等操作。
当DeNB在步骤705之前获取RN1的节点配置信息后，DeNB可以在RRC连接建立消息或者具有类似建立功能的新的信令中将配置信息发送给RN1节点，RN1节点基于此配置信息配置自己的小区功能。其中该配置信息包括小区标识，系统消息等，具体的可以为：全局小区标识(Cell Global Identifier)CGI，物理小区标识(Physical Cell identity)PCI，小区的关键配置信息：系统(超)帧号，系统消息的调度信息，接入控制使能指示，部署模式，系统消息变更标签，下行频点信息等。本服务小区的接入信息以及其他系统消息块的调度信息等。无线公共资源相关配置信息，UE定时器和常量，UL频点等。小区选择和和重选，邻小区配置信息等。接入控制信息等，ACB，EAB,AB接入信息等。系统时间信息。RN1可以基于接收到的配置信息，配置自己的小区。
此外，RN1的节点配置信息，可以在RN1的RRC连接建立完成之后，如步骤707再进行获取并由DeNB发送给RN1.
步骤706、RN1发送RRC建立完成消息。
RN1向DeNB发送RRC连接建立完成消息或者具有类似建立确认功能的新的信令，在该消息中，可选的由于RN1作为节点启动，没有NAS层，所以在该消息中可以不包括NAS PDU。
当DeNB在步骤705之后获取RN1的配置信息时，回程链路上就需要执行步骤707和步骤708，否则回程链路上不执行步骤707和步骤708。
步骤707、DeNB发送下行RRC消息。
RN1完成连接建立后，DeNB将从OAM获取的配置信息，通过一条下行RRC消息把RN1作为DeNB的一个小区的配置信息发送给RN1节点，其中包括RN1的配置信息可以包括小区的系统消息等，具体包括的消息已在上述步骤705中描述，不在赘述。
当协议栈结构为图6b时，也就是RN1上支持NAS层配置，并且该NAS层配置用于RN1的回程链路的传输时，一种可能的实现方法是，该小区的配置信息从OAM到MME通过IP包方式传输，然后在MME以NAS PDU方式传输到DeNB。DeNB使用下行传输消息把该配置信息发送给RN1。
步骤708、RN1完成启动。
RN1基于接收到的配置信息配置自己的小区，并完成启动。
上述步骤中描述的流程为RN1启动的流程，下面将通过图8所示的流程来描述接入该RN1的RN2的启动流程，具体包括：
步骤801、RN2发送随机接入请求消息。
RN2根据RN1的空口无线信号的强度和/或质量，或者配置的服务小区信息，选择RN1中的一个或多个小区中的一个小区作为服务小区，RN2向RN1发送随机接入请求消息。
步骤802、RN1发送随机接入响应消息。
RN2接收RN1反馈的随机接入响应消息，在该随机接入响应消息中携带RN2发送RRC连接请求需要的资源。
步骤803、RN2发送RRC建立请求消息。
RN2向RN1发送RRC连接请求消息或者具有类似建立请求功能的新的信令，在该请求消息中，包括如下信息之一：用于标示RN2身份的标识信息：随机数(40比特，或者其他位数)，或者RN1的(S-Temporary Mobile Subscriber Identity)S-TMSI。接入原因，可以指示为RN2启动；或者可以区分节点接入和终端接入的指示信息，不限于接入原因。该接入节点/接入用户的归属节点的标识，该信息用于帮助DeNB识别该RN2是第几跳中继节点。对于直接连接到DeNB的Relay节点，其归属节点的标识即为DeNB id或者DeNB上其服务小区的id，即服务小区的演进型-通用移动通信系统陆地无线接入网小区全局标识(evolved universal mobile telecommunications systemterrestrial radio access network cell global identifier，ECGI)。
步骤804、RN1发送上行RRC消息。
RN1收到RN2发送的连接建立请求后，通过原因值，或者RN指示信息识别出来 是下一跳的RN2的接入，则RN1在已经建立好的RN1和DeNB之间的无线回程链路上，通过上行RRC消息转发RN1的建立消息。RN1也可以在RN2的RRC建立完成消息之后，才获取RN2的接入请求，此时RN1基于收到RN2发送的连接建立完成消息后，通过原因值，或者RN指示信息识别出来是下一跳的RN2的接入，则RN1在已经建立好的RN1和DeNB之间的无线回程链路上，通过RRC消息转发RN2的建立消息。该回程链路上转发的RN2建立消息中包括：接入原因、该接入节点/接入终端的归属节点标识，小区标识。
步骤805、可选的，DeNB向OAM获取RN2的配置信息。
DeNB从RN1节点获取RN2的接入请求信息，向OAM获取RN2节点的配置信息，该OAM可以为远端OAM，或者本地，DeNB可以将RN2视为其下的一个小区，然后为该小区请求配置信息。
DeNB也可以自己生成RN2节点的配置信息，则无需执行步骤805。
步骤806、DeNB发送下行RRC消息。
DeNB在和RN1已经建立完成的回程链路上使用下行RRC消息发送RN2的配置信息，其中小区的配置信息包括小区的系统消息等，具体包括的内容已在上述步骤中描述，不再赘述。
当协议栈结构为图6b时，也就是RN1上支持NAS层配置，并且该NAS层配置用于RN1的回程链路的传输时，一种可能的实现方法是，该小区的配置信息从OAM到MME通过IP包方式传输，然后在MME以NAS PDU方式传输到DeNB。DeNB使用下行传输消息把该配置信息发送给RN1。
步骤807、RN1发送RRC建立消息。
RN1收到该配置信息后，RN1发送RRC连接建立消息或者具有类似建立功能的新的信令到RN2。对于RN2，RN1可以向RN2询问节点的无线能力，然后RN1存储其服务的多跳RN的无线能力，基于该能力信息为RN2建立合适的无线链路。或者RN1将获取的其下一跳的RN2的无线能力上报到DeNB保存。当RN1需要获取下一跳的RN2的无线能力时，向DeNB请求。RN1基于该能力信息为RN2建立合适的无线链路。
对于该无线链路，由于是承担无线回程的功能，DeNB维护该回程链路位于长连接态，不进行主动释放。只有当该回程链路发生无线链路失败等不可用的情况时，DeNB进行连接释放，和连接重建立等操作。
RN1可以在RRC连接建立消息或者具有类似建立功能的新的信令中将小区配置信息发送给RN2，RN2基于此配置信息配置自己的小区功能。其中小区的配置信息包括小区标识，系统消息等。
步骤808、RN2发送RRC建立完成消息。
RN2向RN1发送RRC连接建立完成消息或者具有类似建立确认功能的新的信令，在该消息中，由于RN2作为节点启动，没有NAS层，所以在该消息中可以不包括NAS PDU。如果RN2支持NAS层，则该消息中可能包括一个特殊的NAS PDU，说明用于RN2的建立完成确认功能。
步骤809、RN1发送下行RRC消息。
RN2完成RRC连接建立后，RN1将从DeNB获取的配置信息，通过一条下行RRC 消息把RN2作为RN1的一个小区的配置信息发送给RN2节点，其中包括RN2的配置信息可以包括小区的系统消息等，具体包括的消息已在上述步骤中描述，不在赘述。
步骤810、RN2完成启动。
RN2基于接收到的配置信息配置自己的小区，并完成启动。
为了更好的管理多个中继节点的路由功能，在上述RN1和RN2启动的过程中，DeNB还需要维护RN1和RN2的路由信息。具体的，DeNB可以在上述步骤704或者步骤706之后开始建立对于RN1的路由表1。DeNB可以在步骤805或步骤809之后开始建立对于RN1的路由表1的更新。DeNB可以在步骤806或步骤808之后开始建立对于RN2的路由表2。
DeNB可以维护的路由信息主要可以包括下述信息：归属节点id：该信息由RN节点在接入时上进行上报或者由其服务RN进行转发到DeNB，用于DeNB维护RN的跳数信息。如果归属节点id的信息是DeNB id或者DeNB的某个非RN的小区的id，则DeNB知道该RN是其直接服务的RN，是一个2跳RN，如RN1。如果归属节点id是某个DeNB服务的RN，则DeNB知道该RN是3跳或者3跳以上的RN，如RN2。
RN指示信息：该信息是用来指示该接入是RN接入还是普通UE接入。该指示方式可以是通过特殊的原因值，比如原因值设置为RN接入等。或者1个标示来指示。比如，1个比特，1是RN接入，0是UE接入；或者反之，0是UE接入，1是RN接入等。还有一种可能的指示方式是，如果有RN指示标示存在，则为RN接入，如果没有该指示域的存在，则为UE接入。
RN节点id：该信息是DeNB从OAM配置信息中的获取。如果RN节点支持NAS层，如图6所述，DeNB无法直接从NAS PDU中获取其配置信息时，基站从MME到DeNB间的更新消息中更新的小区配置中获取该信息。假定RN节点上只支持一个小区，该RN节点id为该小区的全球标示，也即ECGI信息，在本申请中，假定RN1的ECGI＝ECGI1，RN2的ECGI＝ECGI2；基于该信息，DeNB和上一跳的RN节点可以识别多跳的中间的路由节点.
RN UE id/UE id：该信息是DeNB或者RN作为UE身份在回程链路上接入时，DeNB或者上一跳的RN节点分配的C-RNTI。当DeNB要维护RN1下的RN2的路由信息时，RN1需要把分配的RN2UE id携带给DeNB。当UE接入时，RN1和RN2需要把RN2分配给UE的C-RNTI在回程链路上携带给上一跳RN节点.比如RN1，以及归属基站，比如DeNB。在本申请中，假定RN1的C-RNTI＝C-RNTI1，RN2的C-RNTI＝C-RNTI2，基于该信息，DeNB和上一跳RN节点可以识别空口的链路。如果接入的是一个UE，则该UE id为UE在其服务小区上被分配的C-RNTI，在该实施例中假定UE id＝C-RNTI3；在无线链路和回程链路没有变更的情况下，该RN UE id和UE id只需要携带一次，以建立路由信息。当链路更新后，需要重新携带该信息，以更新路由信息。
DeNB上建立的RN1的路由表1的内容可以如表1所示，说明RN1是通过无线回程链路连接到DeNB上的。
表1
归属节点id RN指示 RN节点id RN UE id/UE id
DeNB RN ECGI1 C-RNTI1
RN2上建立的路由表2的内容可以如表2所示，说明RN2是通过无线回程链路连 接到RN1上的。
表2
归属节点id RN指示 RN节点id RN UE id/UE id
ECGI1 RN ECGI2 C-RNTI2
当DeNB完成对于RN2的配置后，DeNB上的路由表1更新为如表3所示，DeNB可以获知RN2的上一跳节点是RN1，而RN1的上一跳节点是DeNB。
表3
归属节点id RN指示 RN节点id RN UE id/UE id
DeNB RN ECGI1 C-RNTI1
ECGI1 RN ECGI2 C-RNTI2
当有一个UE在RN2接入时，RN2会维护一个路由表3，表明UE是从RN2接入的，其具体的内容如表4所示，其中UE id假定为C-RNTI3。
表4
归属节点id RN指示 RN节点id RN UE id/UE id
ECGI2 UE NULL C-RNTI3
当UE接入后，路由表2更新为如表5所示，表明UE是从RN2接入，经由RN1连接到DeNB：
表5
归属节点id RN指示 RN节点id RN UE id/UE id
ECGI1 RN ECGI2 C-RNTI2
ECGI2 UE NULL C-RNTI3
当UE接入后，DeNB上的路由表1更新为如表6所示，DeNB可以获知UE经由RN2，RN1接入到DeNB.
归属节点id RN指示 RN节点id RN UE id/UE id
DeNB RN ECGI1 C-RNTI1
ECGI1 RN ECGI2 C-RNTI2
ECGI2 UE NULL C-RNTI3
基于上述路由信息管理，DeNB和RN之间可以正确的路由来自于不同的RN的数据，实现数据在多个RN上的正确路由。
在上述RN1和RN2启动之后，UE可以接入RN1或者RN2，然后通过RN1或这RN2向网络设备发送数据。下面将描述UE接入RN2的流程，如图9所示，具体包括：
步骤901、UE发送随机接入请求消息。
UE根据RN2的空口无线信号的强度和/或质量，选择RN2的一个或者多个小区中的一个小区作为服务小区，UE向RN2发起随机接入。
步骤902、RN2发送随机接入响应消息。
UE接收RN2反馈的随机接入响应消息，在该随机接入响应消息中携带UE发送RRC连接请求需要的资源。
步骤903、UE发送RRC建立请求消息。
该步骤903还可以包括步骤903a至步骤903e。UE使用RN2调度的资源发起RRC 连接建立请求，其中在RRC连接建立消息中携带UE NAS id(40bit随机数，或者S-TMSI)，建立原因值，UE的能力等信息。当RN2需要获取UE其他的能力信息时，RN2可以在和RN1已经建立的无线回程链路上发送上行RRC消息，比如上行传输消息，也可以是新定义的RRC信令将UE的NAS id、建立原因值或早传上行数据发送到RN1，RN1在通过与DeNB已经建立的无线回程链路上发送上行RRC消息，将UE的NAS id、建立原因值或早传上行数据发送到DeNB。DeNB向MME发送信令获取UE的能力信息。DeNB将该UE的能力信息通过下行RRC信令，比如新的RRC信令或者下行传输消息发送给RN1，RN1再通过下行RRC消息发送给RN2。RN2再发送RRC建立消息将UE的能力信息发送给UE。
步骤904、RN2发送RRC建立消息。
RN2在获得UE的能力之后，为UE建立RRC连接，向UE发送RRC建立消息，此时可以通过RRC建立消息将UE的能力信息发送给UE。
步骤905、UE发送RRC建立完成消息。
如果UE不支持数据早传，则UE可以在向RN2发送的RRC建立完成消息中将需要传输的NAS PDU发送给RN2节点，以使RN2节点将该NAS PDU通过RN1发送给DeNB。
RN2可以向RN1发送第一RRC消息，该消息中包括第一数据和标识信息，具体的流程可以见步骤301。该第一RRC消息可以是上行传输消息，也可以是新定义的RRC信令，其中还可以包括UE NAS id、建立原因值等信息，如果该信息已在上述步骤903a、903b中传输，则该步骤可以不包括这两个信息，也可以包括这两个信息。该第一RRC消息中还可能包括RN2为UE分配的C-RNTI，用于RN1更新路由表。
步骤303、第一设备接收第一RRC消息。
可选的，RN1在接收到RN2发的第一RRC消息之后，可以通过第一RRC消息中携带的该第二设备的标识信息确定与该标识信息所对应的RN1的DeNB，这里的目的是选择向谁发送该第一RRC消息中携带的第一数据。
可选的，当上述第一消息中的标识信息为中继节点的标识信息时，该第一RRC消息中还可以包括中继指示，该中继指示用于向网络设备和/或归属基站通知该第二设备为中继节点，该中继指示可以为上述RN启动的流程中的原因值。
步骤304、第一设备发送第二RRC消息。
RN2在确定出需要向DeNB转发第一数据时，RN2通过第二RRC消息向DeNB转发该第一数据以及标识信息，比如可以为上行数据传输消息。
DeNB在接收到该第一数据和标识信息之后，DeNB向MME发起S1初始UE信息，根据接收到的标识信息，建立UE的空口与S1的映射关系，具体的参数可以包括：RN节点id，UE id和S1AP id。其中，RN节点id和UE id已在上述流程中描述。S1AP id指示的是MME UE S1AP ID或者eNB UE S1AP ID，或者具有识别UE在S1口的连接的其他的ID。
当DeNB接收到MME的S1AP连接上的一个下行NAS PDU时，DeNB根据已经建立的UE的空口与S1的映射关系以及路由表信息，为UE选择下一跳RN的路由。DeNB在无线链路上向RN1发送下行RRC消息，该RRC消息可以是下行传输消息，也可以是新定义的RRC信令，如果该无线链路是回程链路，其中包括该下行数据包需 要达到RN的RN节点id和UE id，以及来自MME的DL NAS PDU；如果该链路是无线接入链路，则在发送下行传输消息中不包括RN Node id，以及UE id，包括来自于MME的DL NAS PDU。
RN1基于接收到的RN Node id和UE id，查找本地的路由表，找到对应空口链路或者回程链路，向该链路发送下行RRC消息，该RRC消息可以是下行传输消息，也可以是新定义的RRC信令，如果该无线链路是回程链路，其中包括该下行数据包需要达到RN的RN节点id和UE id；如果该链路是无线接入链路，则在发送下行传输消息中不包括RN Node id，以及UE id，包括来自于MME的DL NAS PDU。RN2向UE发送行传输消息，其中包括来自于MME的NAS PDU。
当UE的数据传输结束后，RN2可以发起连接释放消息，RN2向其服务节点RN1发送RRC连接释放请求消息，其中携带要求释放的UE id信息；RN1转发该连接释放消息，其中携带RN node id和UE id信息到DeNB。DeNB查找UE和S1口的映射关系表格，找到对应的需要释放的S1AP连接，向MME的释放请求，请求来自于MME的释放消息。
DeNB接收来自MME的释放命令，DeNB向RN1，RN1向RN2发送RRC释放消息，其中携带需要释放的链路的RN node id和UE id标示。
需要注意的是，如果RN2先发起RRC连接释放，则该节点也需要通知其服务节点以及服务节点的DeNB和MME去删除对应的回程链路和S1连接。此时的回程链路上的RRC消息的名称可能变更为RRC连接释放，是一个通知信息，而不是一个请求信息。而在S1口的释放消息的名称也可能会变更，有请求信息变更为一个通知信息。当收到该信息后，服务RN节点更新其路由表，DeNB更新其空口和S1口映射关系表以及UE的路由表。
以上实施例表明，第一设备接收第二设备发送的第一RRC消息，该第一RRC消息包括第一数据和标识信息，然后第一设备通过第二RRC消息向第一设备的归属基站发送第一数据和标识信息。由于第一设备和第二设备采用RRC消息来发送数据，简化了第一设备和第二设备的网络功能，改善了NB-IoT网络中接入多个中继节点之后的数据的传输效率。
基于相同的技术构思，图10所示为本申请提供的传输设备的结构示意图。该传输设备1000可以是图3所示的第一设备、第二设备，或者还可以是第一设备、第二设备内的芯片等。该传输设备1000可用于执行上述实施例所描述的方法，以及执行上述实施例中任一传输方法。该传输设备1000包括至少一个处理器1001，至少一个通信接口1004，可选地，还包括存储器1003。
处理器1001可以是一个通用中央处理器(CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请中程序执行的集成电路。
存储器1003可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光 碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器1003可以是独立存在，通过总线与处理器1001相连接。存储器1003也可以和处理器1001集成在一起。
其中，所述存储器1003用于存储执行本申请的应用程序代码，并由处理器1001来控制执行。所述处理器1001用于执行所述存储器1003中存储的应用程序代码。
在具体实现中，作为一种实施例，处理器1001可以包括一个或多个CPU，例如图10中的CPU0和CPU1。
在具体实现中，作为一种实施例，该传输设备1000可以包括多个处理器，例如图10中的处理器1001和处理器1008。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
示例性的，图3中的第一设备可以为图10所示的传输设备，传输设备的存储器中存储了一个或多个软件模块。传输设备可以通过处理器以及存储器中的程序代码来实现软件模块，实现本申请任一实施例中第一设备执行的流程。
图3中的第二设备可以为图10所示的传输设备，传输设备的存储器中存储了一个或多个软件模块。传输设备可以通过处理器以及存储器中的程序代码来实现软件模块，实现本申请任一实施例中第二设备执行的流程。
本申请可以根据上述方法示例对传输设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，在采用对应各个功能划分各个功能模块的情况下，图11示出了上述实施例中所涉及的一种传输设备可能的结构示意图，在该传输设备为第一设备或第二设备时，该传输设备包括接收单元1101、处理单元1102和发送单元1103。
前述实施例中的传输方法中的各种变化方式和具体实例同样适用于本实施例的传输设备，通过前述对传输方法的详细描述，本领域技术人员可以清楚的知道本实施例中传输设备的实施方法，所以为了说明书的简洁，在此不再详述。
本申请还提供了一种通信系统，包括第一设备、第二设备和归属基站；所述第一设备为接入归属基站的第一中继节点，所述第二设备为所述第二中继节点或者为终端设备；
所述第二设备获取第一数据和标识信息，其中，所述第一数据为待发送给网络设备的数据，所述标识信息为所述终端设备的标识信息或者中继节点的标识信息；以及向所述第一设备发送第一RRC消息，所述第一RRC消息包括所述第一数据和所述标识信息；
所述第一设备接收所述第二设备发送的第一RRC消息；并通过第二RRC消息向所述第一设备的归属基站发送所述第一数据和所述标识信息。
本申请还提供了一种通信系统，包括第一中继节点、多个第二中继节点、终端设备和归属基站；
所述终端设备接入级联的多个第二中继节点之后，又接入第一中继节点；
所述第一中继节点与所述归属基站连接。
本申请还提供了一种计算机存储介质，用于储存为上述图10或图11所示的传输设备所用的计算机软件指令，其包含用于执行上述方法实施例所设计的程序代码。
本申请还提供了计算机程序产品。该计算机程序产品包括计算机软件指令，该计算机软件指令可通过处理器进行加载来实现上述方法实施例中的方法。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (23)

  1. 一种传输方法，其特征在于，包括：
    第一设备接收第二设备发送的第一无线资源控制RRC消息，所述第一RRC消息包括第一数据和标识信息，所述第一数据为待发送给网络设备的数据；所述第一设备为接入归属基站的第一中继节点，所述第二设备为第二中继节点或者为所述终端设备，所述标识信息为所述终端设备的标识信息或者中继节点的标识信息；
    所述第一设备通过第二RRC消息向所述第一设备的归属基站发送所述第一数据和所述标识信息。
  2. 根据权利要求1所述的方法，其特征在于，所述第一数据为所述终端设备发送给网络设备的非接入层协议数据单元NAS PDU。
  3. 根据权利要求1所述的方法，其特征在于，在所述第一设备通过第二RRC消息向所述第一设备的归属基站发送所述第一数据和所述标识信息之前，还包括：
    所述第一设备根据所述标识信息，确定与所述标识信息所对应的所述第一设备的归属基站。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述第一设备接收第二设备发送的第一RRC消息之前，所述方法还包括：
    所述第一设备根据所述归属基站的空口无线信号的强度和/或质量，或者配置的服务小区信息，将所述归属基站的一个小区确定为服务小区；
    所述第一设备向所述服务小区发起随机接入，与所述归属基站建立RRC连接；
    所述第一设备接收所述归属基站发送的配置信息，并根据所述配置信息配置自身的小区。
  5. 根据权利要求1至3任一项所述的方法，其特征在于，所述第一设备接收第二设备发送的第一RRC消息之前，所述方法还包括：
    所述第一设备接收所述第二设备发起的RRC连接请求消息，并与所述第二设备建立RRC连接。
  6. 根据权利要求1至3任一项所述的方法，其特征在于，当所述标识信息为中继节点的标识信息，所述第一RRC消息还包括中继指示，所述中继指示用于向网络设备和/或所述归属基站通知所述第二设备为中继节点。
  7. 一种传输方法，其特征在于，包括：
    第二设备获取第一数据和标识信息，其中，所述第一数据为待发送给网络设备的数据，所述标识信息为所述终端设备的标识信息或者中继节点标识信息，所述第二设备为第二中继节点或者为所述终端设备；
    所述第二设备向第一设备发送第一无线资源控制RRC消息，所述第一RRC消息包括所述第一数据和所述标识信息；所述第一设备为接入归属基站的第一中继节点。
  8. 根据权利要求7所述的方法，其特征在于，当所述第二设备为所述第二中继节点时，所述第二设备获取第一数据，包括：
    所述第二设备获取所述第二中继节点自己生成的第一数据；或者
    所述第二设备接收所述终端设备发送的第一数据。
  9. 根据权利要求7所述的方法，其特征在于，当所述第二设备为终端设备时，所述第二设备获取第一数据，包括：
    所述第二设备获取终端设备自己生成的第一数据。
  10. 一种传输设备，其特征在于，包括：接收单元和发送单元；
    所述接收单元，用于接收第二设备发送的第一无线资源控制RRC消息，所述第一RRC消息包括第一数据和标识信息，所述第一数据为待发送给网络设备的数据；所述传输设备为第一设备，所述第一设备为接入归属基站的第一中继节点，所述第二设备为第二中继节点或者为所述终端设备，所述第二设备接入第一设备，所述标识信息为所述终端设备的标识信息或者中继节点的标识信息；
    所述发送单元，用于通过第二RRC消息向所述第一设备的归属基站发送所述接收单元接收的第一数据和所述标识信息。
  11. 根据权利要求10所述的传输设备，其特征在于，所述第一数据为所述终端设备发送给网络设备的非接入层协议数据单元NAS PDU。
  12. 根据权利要求10所述的传输设备，其特征在于，还包括处理单元；
    所述处理单元，用于在所述发送单元通过第二RRC消息向所述第一设备的归属基站发送所述接收单元接收的第一数据和所述标识信息之前，根据所述接收单元接收的标识信息，确定与所述标识信息对应的所述第一设备的归属基站。
  13. 根据权利要求10至12任一项所述的传输设备，其特征在于，所述处理单元还用于：根据所述归属基站的空口无线信号的强度和/或质量,或者配置的服务小区信息，将所述归属基站的一个小区确定为服务小区；
    向所述服务小区发起随机接入，与所述归属基站建立RRC连接；
    所述接收单元还用于接收所述归属基站发送的配置信息；
    所述处理单元还用于根据所述接收单元接收的所述配置信息配置自身的小区。
  14. 根据权利要求10至12任一项所述的传输设备，其特征在于，所述接收单元接收第二设备发送的第一RRC消息之前，所述接收单元还用于接收所述第二设备发起的RRC连接请求消息；
    所述处理单元还用于与所述第二设备建立RRC连接。
  15. 根据权利要求10至12任一项所述的传输设备，其特征在于，当所述标识信息为中继节点的标识信息，所述第一RRC消息还包括中继指示，所述中继指示用于向网络设备和/或所述归属基站通知所述第二设备为中继节点。
  16. 一种传输设备，其特征在于，包括：发送单元和处理单元；
    所述处理单元，用于获取第一数据和标识信息，其中，所述第一数据为待发送给网络设备的数据，所述标识信息为所述终端设备的标识信息或者中继节点的标识信息，所述传输设备为所述第二中继节点或者为所述终端设备；
    所述发送单元，用于向第一设备发送第一无线资源控制RRC消息，所述第一RRC消息包括所述处理单元获取的第一数据和所述标识信息；所述第一设备为接入归属基站的中继节点。
  17. 根据权利要求16所述的传输设备，其特征在于，还包括接收单元；
    所述处理单元具体用于，当所述传输设备为所述第二中继节点时，获取所述第二中继节点自己生成的第一数据；或者
    所述处理单元控制所述接收单元接收所述终端设备发送的第一数据。
  18. 根据权利要求16所述的传输设备，其特征在于，所述处理单元具体用于，当 所述传输设备为终端设备时，获取终端设备自己生成的第一数据。
  19. 一种计算机可读存储介质，其特征在于，包括计算机可读指令，当计算机读取并执行所述计算机可读指令时，使得计算机执行如权利要求1-6任意一项所述的方法。
  20. 一种计算机可读存储介质，其特征在于，包括计算机可读指令，当计算机读取并执行所述计算机可读指令时，使得计算机执行如权利要求7-9任意一项所述的方法。
  21. 一种计算机程序产品，其特征在于，包括计算机可读指令，当计算机读取并执行所述计算机可读指令，使得计算机执行如权利要求1-6任意一项所述的方法。
  22. 一种计算机程序产品，其特征在于，包括计算机可读指令，当计算机读取并执行所述计算机可读指令，使得计算机执行如权利要求7-9任意一项所述的方法。
  23. 一种通信系统，其特征在于，包括第一设备、第二设备和归属基站；所述第一设备为接入归属基站的第一中继节点，所述第二设备为所述第二中继节点或者为终端设备；
    所述第二设备获取第一数据和标识信息，其中，所述第一数据为待发送给网络设备的数据，所述标识信息为所述终端设备的标识信息或者中继节点的标识信息；以及向所述第一设备发送第一无线资源控制RRC消息，所述第一RRC消息包括所述第一数据和所述标识信息；
    所述第一设备接收所述第二设备发送的第一RRC消息；并通过第二RRC消息向所述第一设备的归属基站发送所述第一数据和所述标识信息。
PCT/CN2017/101122 2017-09-08 2017-09-08 一种传输方法及设备 WO2019047180A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP17924345.6A EP3672351B1 (en) 2017-09-08 2017-09-08 Transmission method and device
CN201780093648.XA CN110999511B (zh) 2017-09-08 2017-09-08 一种传输方法及设备
PCT/CN2017/101122 WO2019047180A1 (zh) 2017-09-08 2017-09-08 一种传输方法及设备
US16/810,046 US11388647B2 (en) 2017-09-08 2020-03-05 Transmission method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/101122 WO2019047180A1 (zh) 2017-09-08 2017-09-08 一种传输方法及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/810,046 Continuation US11388647B2 (en) 2017-09-08 2020-03-05 Transmission method and device

Publications (1)

Publication Number Publication Date
WO2019047180A1 true WO2019047180A1 (zh) 2019-03-14

Family

ID=65635168

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/101122 WO2019047180A1 (zh) 2017-09-08 2017-09-08 一种传输方法及设备

Country Status (4)

Country Link
US (1) US11388647B2 (zh)
EP (1) EP3672351B1 (zh)
CN (1) CN110999511B (zh)
WO (1) WO2019047180A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112867094A (zh) * 2020-12-31 2021-05-28 深圳市泰和安科技有限公司 一种具有自组网功能的无线消防报警系统和实现方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016164808A1 (en) * 2015-04-08 2016-10-13 InterDigitial Patent Holdings, Inc. Realizing mobile relays for device-to-device (d2d) communications
WO2017065895A1 (en) * 2015-10-16 2017-04-20 Qualcomm Incorporated System and method for device-to-device communication with evolved machine type communication
CN106954233A (zh) * 2016-01-07 2017-07-14 中兴通讯股份有限公司 一种窄带物联网用户核心网选择的方法和通信设备

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8855138B2 (en) * 2008-08-25 2014-10-07 Qualcomm Incorporated Relay architecture framework
WO2010099705A1 (zh) * 2009-03-06 2010-09-10 中国移动通信集团公司 中继节点网络接入的方法、系统及网络设备
KR101268251B1 (ko) * 2009-03-17 2013-05-28 한국전자통신연구원 릴레이를 포함하는 무선 통신 시스템의 데이터 전송 방법
US20100260126A1 (en) * 2009-04-13 2010-10-14 Qualcomm Incorporated Split-cell relay packet routing
EP2517524A1 (en) * 2009-12-22 2012-10-31 Fujitsu Limited Transmission in a communication system using relay nodes
CN101883427B (zh) * 2010-07-07 2013-09-18 新邮通信设备有限公司 一种长期演进技术的后续演进系统中的定位方法
GB2484347A (en) * 2010-10-08 2012-04-11 Nec Corp Initiating energy saving mode based on the activity of mobile communications equipment over an LTE-A interface
CN102469536B (zh) * 2010-11-05 2015-12-09 大唐移动通信设备有限公司 类型信息上报及中继节点类型确定方法、系统和设备
CN102098723B (zh) * 2011-02-12 2014-01-29 大唐移动通信设备有限公司 为移动中继节点配置施主基站或施主小区的方法和设备
WO2014169451A1 (zh) * 2013-04-17 2014-10-23 华为技术有限公司 数据传输方法和装置
WO2014205772A1 (zh) * 2013-06-28 2014-12-31 华为技术有限公司 一种无线网络的建立方法、设备及系统
TWI559721B (zh) * 2013-08-09 2016-11-21 宏達國際電子股份有限公司 雙連結中分配無線網路暫時識別的方法
US10039086B2 (en) * 2013-11-11 2018-07-31 Electronics And Telecommunications Research Institute Communication method and apparatus in network environment where terminal may have dual connectivity to multiple base stations
BR112016020504A2 (pt) * 2014-03-07 2018-07-03 Huawei Technologies Co., Ltd. “nó de retransmissão rn, enób doador denb e método de comunicação”.
BR112017008293B1 (pt) * 2014-10-23 2023-11-21 Huawei Technologies Co., Ltd Nó de serviço, método para processar mensagens de controle de recurso de rádio em uma rede de comunicação, e nó de âncora
US10148340B1 (en) * 2016-03-30 2018-12-04 Sprint Communications Company L.P. Multi-core communication system to serve wireless relays and user equipment
US9949146B1 (en) * 2016-04-07 2018-04-17 Sprint Communications Company L.P. Control over data services that are delivered over a wireless access point
US10028186B1 (en) * 2017-03-24 2018-07-17 Sprint Communications Company L.P. Wireless communication system to redirect use equipment (UE) from a wireless relay to a donor base station

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016164808A1 (en) * 2015-04-08 2016-10-13 InterDigitial Patent Holdings, Inc. Realizing mobile relays for device-to-device (d2d) communications
WO2017065895A1 (en) * 2015-10-16 2017-04-20 Qualcomm Incorporated System and method for device-to-device communication with evolved machine type communication
CN106954233A (zh) * 2016-01-07 2017-07-14 中兴通讯股份有限公司 一种窄带物联网用户核心网选择的方法和通信设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP3672351A4 *
VEOLIA: "New WID on Multi hop relay for IoT & MTC for utilities use cases for LTE", 3GPP TSG RAN MEETING #77 RP-171882, 4 September 2017 (2017-09-04), XP051324449 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112867094A (zh) * 2020-12-31 2021-05-28 深圳市泰和安科技有限公司 一种具有自组网功能的无线消防报警系统和实现方法

Also Published As

Publication number Publication date
US20200213931A1 (en) 2020-07-02
CN110999511B (zh) 2022-10-11
EP3672351A4 (en) 2020-08-19
CN110999511A (zh) 2020-04-10
US11388647B2 (en) 2022-07-12
EP3672351A1 (en) 2020-06-24
EP3672351B1 (en) 2022-05-25

Similar Documents

Publication Publication Date Title
KR101870850B1 (ko) D2d 관련 정보 지시 및 d2d 송신 자원 확정 방법 및 장치
CN109417695A (zh) 一种通信路径转换方法及设备
TW201828656A (zh) 對資料封包進行映射的方法及使用所述方法的相關裝置
JP2018514139A (ja) Ｄ２ｄ中継ノードの確定方法、使用方法及び装置
JP7039712B2 (ja) ノードおよび通信方法
KR102327021B1 (ko) 네트워크 슬라이스를 통한 서비스 제공 방법 및 장치
US20230156848A1 (en) Communication method applied to integrated access and backhaul iab system and communication apparatus
US20210392538A1 (en) Method and device for configuring node to transmit and receive data
WO2019201245A1 (zh) 一种通信方法及装置
US20230171651A1 (en) Logical channel lch configuration method, communication apparatus, and communication system
WO2020061867A1 (zh) 一种数据传输方法和装置
KR102402481B1 (ko) 액세스 방법 및 기기
US20130294330A1 (en) Mobile relay station and handover method thereof
US20170223751A1 (en) Interface establishing method and apparatus
US11388647B2 (en) Transmission method and device
TW202110208A (zh) 在海上網路的網路節點之間轉送資料的方法及設備
US20240031972A1 (en) User equipment, base station, and amf system
CN112205025B (zh) 小区建立的方法和装置
TW201611632A (zh) 裝置及方法
WO2023005471A1 (zh) 一种上行资源确定和配置方法及装置
JP7394198B1 (ja) 配信サーバ、配信サーバの制御方法、及び配信サーバの制御プログラム
EP4152821A1 (en) Handover method and apparatus
WO2023134354A1 (zh) 一种通信方法及设备
WO2023008409A1 (ja) 通信制御方法及びコアネットワーク装置
WO2023008410A1 (ja) 通信制御方法及び基地局

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017924345

Country of ref document: EP

Effective date: 20200317