WO2019091307A1 - 通信方法和装置 - Google Patents

通信方法和装置 Download PDF

Info

Publication number
WO2019091307A1
WO2019091307A1 PCT/CN2018/112883 CN2018112883W WO2019091307A1 WO 2019091307 A1 WO2019091307 A1 WO 2019091307A1 CN 2018112883 W CN2018112883 W CN 2018112883W WO 2019091307 A1 WO2019091307 A1 WO 2019091307A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
registration
relay
information
request message
Prior art date
Application number
PCT/CN2018/112883
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 EP18877235.4A priority Critical patent/EP3687259B1/en
Publication of WO2019091307A1 publication Critical patent/WO2019091307A1/zh
Priority to US15/930,449 priority patent/US20200275258A1/en

Links

Images

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • 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
    • 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/0289—Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • 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
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • 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
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to a communication method and apparatus.
  • IoT terminals for example, sensors
  • IoT terminals are widely used in measurement, construction, agriculture, logistics, smart cities, and homes.
  • the IoT terminal directly accesses the communication network.
  • the way in which existing IoT terminals access the communication network is likely to cause network congestion.
  • the embodiment of the present application provides a communication method and apparatus to avoid network congestion caused by an IoT terminal accessing a communication network.
  • a communication method includes: obtaining, by a terminal device, a relay mode of the terminal device; the terminal device transmitting, to the relay device, registration information and relay mode information of the terminal device, The relay device is enabled to send a registration request message to the AN node based on the relay mode information and the registration information of the terminal device, which increases the flexibility of the terminal device registration, thereby avoiding network congestion caused when the terminal device accesses the communication network.
  • the relay mode corresponding to the relay mode information may include a long-term relay mode or a temporary relay mode.
  • the registration information includes identifier information of the terminal device and/or identifier information of a core network node that is registered by the terminal device; or, the registration The information is a registration request message.
  • the registration request message may carry the identification information of the terminal device for requesting registration of the terminal device; the identification information of the terminal device is used to identify the terminal device, and may be a permanent identifier, for example, an IMSI, or may be a temporary identifier, for example, 5G-GUTI, or 5G-TMSI; the identification information of the relay device is used to identify the relay device, and may be a permanent identifier or a temporary identifier.
  • the terminal device obtains a relay mode of the terminal device, including: the terminal device according to the Obtaining a relay mode of the terminal device in an idle state of the terminal device; or obtaining, by the terminal device, a relay mode of the terminal device according to a pre-configured association relationship; or The location of the terminal device is obtained, and the relay mode of the terminal device is obtained.
  • the method for obtaining the relay mode in the present application is not limited to the above manner, and may further include dynamically setting a relay mode or the like through a human-machine interaction interface, which is not limited.
  • the method further includes: the terminal device receiving the The registration area information of the terminal device and/or the registration update timer duration, so that the relay device and the terminal device can simultaneously initiate a registration process caused by moving out of the registration area, thereby implementing the relay device by sending a registration request message.
  • the registration update timers have the same duration, so that the relay device and the terminal device can initiate periodic registration updates at the same time, and the relay device can implement simultaneous registration of the relay device and the terminal device by sending a registration request message.
  • a communication method comprising: a relay device receiving registration information from a terminal device and relay mode information of the terminal device; the relay device according to the relay mode information and The registration information sends a registration request message to the access network AN node.
  • the registration request message can be used to request registration of one or more devices (for example, a relay device and a terminal device, or at least two terminal devices), which increases flexibility of terminal device registration, thereby avoiding terminal device access. Network congestion caused by communication networks.
  • the relay device initiates the registration process of multiple devices through one registration request message, the signaling overhead is greatly reduced, and the wireless resources are saved.
  • the registration information includes the identifier information of the terminal device and/or the identifier information of a core network node that is registered by the terminal device, where the registration information is For the relay device to generate a registration request message; or the registration information is a registration request message, the registration request message is used to request registration of the terminal device, and may include identification information of the terminal device, and the registration request message may be used at this time.
  • the relay device generates a new registration request message, which may also be used by the relay device to directly send the registration request message to the AN node.
  • the registration request when the relay mode corresponding to the relay mode information is a long-term relay mode, the registration request The message is used to request registration of the relay device and the terminal device.
  • the registration request message enables registration of the relay device and the terminal device at the same time, which reduces signaling load and saves radio resources.
  • the registration request message includes the identifier information of the core network node that is registered by the relay device, and/or the relay device
  • the identification information may be used by the core network node that receives the registration request message to obtain the subscription information or the context information of the relay device, and the like; the registration request message includes the identifier information of the core network node that is further included in the terminal device registration.
  • the identification information of the terminal device may be used to obtain the subscription information or context information of the terminal device, and the core network node that receives the registration request message.
  • the method further includes: the relay device sending the identifier of the relay device to the AN node
  • the information and/or the identification information of the core network node registered by the relay device may be used by the AN node to determine the core network node, that is, the target core network node of the relay device, so that the AN node sends a registration request message to the core.
  • the network node completes the registration process of the terminal device and the relay device.
  • the registration request message includes a registration type and/or relay device indication information;
  • the relay device indication information is used to indicate the relay device, and may be used by the core network node to page the terminal device.
  • the paging message carries the identifier information of the relay device, so that the terminal can be quickly paged.
  • the registration type is used to indicate registration of at least two devices, and may be used by the core network node to check the registration request message. If the verification fails, the core network node sends a registration rejection message to the relay device.
  • the method further includes: the relay device receives a registration accept message, and the registration accepts The message includes: the registration area information of the relay device and the registration area information of the terminal device, and the registration area corresponding to the registration area information of the relay device is the same as the registration area corresponding to the registration area information of the terminal device.
  • the registration acceptance message includes: a registration update timer duration of the terminal device and a registration update timer duration of the relay device, and a registration update timer duration of the terminal device is the same as a registration update timer duration of the relay device, so that The relay device and the terminal device can simultaneously initiate periodic registration updates, thereby implementing a registration request message. And is currently registered relay device and the terminal device.
  • the registration request The message is used to request registration of the terminal device.
  • the registration request message implements completion of registration by the terminal device through the relay device.
  • the registration request message may also be used to request registration with other terminal devices, and other terminal devices also communicate with the AN node through the relay device. For example, if the relay device receives the registration request message sent by multiple terminal devices at the same time or within a preset time period, the relay device may generate a new registration request message according to the received registration request message, and send the message to the AN node, thereby further saving. Wireless resources.
  • the method further includes: the relay device sending the identifier information of the terminal device to the AN node, and/or The identification information of the core network node registered by the terminal device is used by the AN node to determine the core network node, that is, the target core network node of the terminal device, so that the AN node sends a registration request message to the core network node to complete the terminal device. registration process.
  • a communication method comprising: an access network AN node receiving a registration request message from a relay device; the AN node transmitting the to the corresponding core network node of the relay device Registration request message.
  • the registration request message may be used to request registration of at least two devices (for example, a relay device and a terminal device, or at least two terminal devices), which not only increases the flexibility of the terminal device registration, but also reduces the letter.
  • the overhead is saved, and the wireless resources are saved, thereby avoiding network congestion caused when the terminal device accesses the communication network.
  • the terminal device or the at least two terminal devices can communicate with the AN node through the relay device.
  • the registration request message includes the identifier information of the core network node that is registered by the relay device and/or the identifier information of the relay device, and may be used. And obtaining, by the core network node, the subscription information or the context information of the relay device, where the registration request message further includes the identifier information of the core network node registered by the terminal device and/or the identifier information of the terminal device, which may be used for the core.
  • the network node acquires subscription information or context information of the terminal device.
  • the registration request message includes a registration type and/or relay device indication information, where the relay The device indication information is used to indicate the relay device, and may be used by the core network node to page the terminal device, for example, the paging message carries the identification information of the relay device, so that the terminal device can be quickly paged;
  • the registration type is used to indicate registration of at least two devices, and may be used for the core network node to verify the registration request message. If the verification fails, the core network node sends a registration rejection message to the relay device.
  • a fourth aspect provides a communication method, the method comprising: receiving, by a core network node, a registration request message from an access network AN node, where the registration request message is used to request registration of a relay device and a terminal device; The core network node registers the relay device and the terminal device according to the registration request message; the core network node sends a registration accept message to the relay device, the method not only increases the registration of the terminal device. Flexibility also reduces signaling overhead and saves radio resources, thereby avoiding network congestion caused by terminal devices accessing the communication network.
  • the registration request message includes the identifier information of the core network node that is registered by the relay device and/or the identifier information of the relay device, and may be used. And obtaining, by the core network node, the subscription information or the context information of the relay device, where the registration request message further includes the identifier information of the core network node registered by the terminal device and/or the identifier information of the terminal device, which may be used for the core.
  • the network node acquires subscription information or context information of the terminal device.
  • the method further includes: obtaining, by the core network node, a core network node that is registered by the terminal device Context information of the terminal device; and/or, the core network node acquires context information of the relay device from a core network node registered by the relay device.
  • the registration accept message includes: the registration area information of the relay device, and the terminal device Registering the area information, and the registration area corresponding to the registration area information of the relay device is the same as the registration area corresponding to the registration area information of the terminal device, so that the relay device and the terminal device can simultaneously initiate the removal due to the removal of the registration area.
  • a registration process in which a registration request message is implemented to implement simultaneous registration of the relay device and the terminal device; or, the registration update timer duration of the terminal device and the registration update timer duration of the relay device, and the terminal
  • the registration update timer duration of the device is the same as the registration update timer duration of the relay device, so that the relay device and the terminal device can simultaneously initiate periodic registration updates, thereby implementing a registration request message to implement the relay device and the terminal. Register the device at the same time.
  • the registration request message further includes a registration type and/or relay device indication information, where
  • the relay device indication information is used to indicate the relay device, and may be used by the core network node to page the terminal device, for example, the paging message carries the identification information of the relay device, so that the terminal device can be quickly paged.
  • the registration type is used to indicate registration of at least two devices, and may be used for the core network node to verify the registration request message. If the verification fails, the core network node sends a registration rejection message to the relay device.
  • a communication apparatus comprising means or means for performing the steps of the method of any of the above first aspect or of the above first aspect.
  • the communication device can be a terminal device, such as a remote UE, or it can be at least one processing element or chip.
  • a communication apparatus comprising means or means for performing the steps of the method of any of the above second aspect or of the second aspect.
  • the communication device may be a relay device, such as a relay UE, or it may be at least one processing element or chip.
  • a communication apparatus comprising means or means for performing the steps of the method of any of the third aspect or the third aspect above.
  • the communication device can be an AN node or can be at least one processing element or chip.
  • a communication apparatus comprising means or means for performing the steps of the method of any of the fourth aspect or the fourth aspect above.
  • the communication device can be a core network node, such as an AMF, or it can be at least one processing element or chip.
  • a communication apparatus comprising: a processor for storing a program, the processor calling a program stored in the memory to perform the method of any one of the first aspect or the first aspect above .
  • the communication device may be a terminal device, for example, a terminal device that communicates with an AN node through a relay device, or a terminal device that is out of coverage of the wireless network, or may be at least one processing element or chip.
  • a communication apparatus including a processor and a memory, the memory is configured to store a program, and the processor calls a program stored in the memory to execute the method in any one of the second aspect or the second aspect above.
  • the communication device may be a relay device, such as a relay UE, or it may be at least one processing element or chip.
  • a communication device comprising: a processor for storing a program, the processor calling a program stored in the memory to perform the implementation of any of the third aspect or the third aspect above method.
  • the communication device can be an AN node, such as a base station, or can be at least one processing element or chip.
  • a communication apparatus comprising a processor and a memory, wherein the memory is used to store a program, and the processor calls a program stored in the memory to perform the fourth aspect or any of the above fourth aspect.
  • the communication device may be a core network node, which may have mobility management functions, such as an AMF node or MME, or at least one processing element or chip.
  • a program for performing any of the methods of the above first aspect when executed by a processor.
  • a computer readable storage medium comprising the program of the thirteenth aspect is provided.
  • a computer readable storage medium comprising the program of the fifteenth aspect is provided.
  • a program for performing any of the methods of the above third aspect when executed by a processor.
  • a computer readable storage medium comprising the program of the seventeenth aspect is provided.
  • a program for performing any of the methods of the above fourth aspect when executed by a processor.
  • a computer readable storage medium comprising the program of the nineteenth aspect is provided.
  • a system comprising the communication device of the fifth aspect to the eighth aspect.
  • 1A is a schematic diagram of a communication system
  • 1B is a schematic structural diagram of a 5G communication system
  • FIG. 2 is a schematic diagram of a communication method according to a first embodiment of the present application.
  • FIG. 3 is a schematic diagram of a communication method according to a second embodiment of the present application.
  • FIG. 4 is a schematic diagram of a communication method according to a third embodiment of the present application.
  • FIG. 5 is a schematic diagram of a communication method according to a fourth embodiment of the present application.
  • FIG. 6 is a schematic diagram of a communication method according to a fifth embodiment of the present application.
  • FIG. 7 is a flowchart of a communication method according to a sixth embodiment of the present application.
  • FIG. 8 is a flowchart of a communication method according to a seventh embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a communication apparatus according to an eighth embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a communication apparatus according to a ninth embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a communication apparatus according to a tenth embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of a communication apparatus according to an eleventh embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a communication apparatus according to a twelfth embodiment of the present application.
  • the embodiments of the present application can be applied to a Long Term Evolution (LTE) network, a Universal Mobile Telecommunications System (UMTS), a Global System for Mobile Communications (GSM), and a fifth generation (5rd).
  • LTE Long Term Evolution
  • UMTS Universal Mobile Telecommunications System
  • GSM Global System for Mobile Communications
  • 5rd fifth generation
  • the generation, 5G) communication system, the non-third generation partnership project (3GPP) communication system, or the next generation communication system, the embodiment of the present application is not limited.
  • Figure 1A provides a schematic diagram of a communication system.
  • the embodiment of the present application can be applied to the communication system.
  • the communication system can be a device to device (D2D) communication system.
  • D2D device to device
  • embodiments of the present application can also be applied to non-D2D communication systems.
  • the communication system includes a network side device, a terminal device, and a relay device.
  • the network side device may include a core network node and an access network (AN) node.
  • the terminal device can communicate with the operator service network or the internet through the relay device and the network side device.
  • the terminal device may include various handheld devices with wireless communication functions, in-vehicle devices, wired devices (WD), computing devices or other processing devices connected to the wireless modem, and various forms of terminals, mobile stations (mobile Station, MS), terminal, user equipment (UE), soft terminal, etc.
  • a remote UE an IoT terminal.
  • the terminal device is used as a wearable device as an example for description.
  • the relay device can perform radio resource connection management by establishing a radio resource control (RRC) connection and a non-access stratum (NAS) connection with the base station.
  • RRC radio resource control
  • NAS non-access stratum
  • the relay device may be a terminal device or a base station having a relay function.
  • a device that relays signals of a terminal device is referred to as a relay device.
  • the terminal device associated with the wearable device is exemplified as a relay device.
  • the AN node may be a base station, for example, a Base Transceiver Station (BTS) in GSM, and a Base Station (NodeB) in UMTS.
  • BTS Base Transceiver Station
  • NodeB Base Station
  • the AN node may communicate with the core network node through the base station control device, or may be in LTE.
  • the evolved base station evolved Node B, eNB or e-NodeB
  • the gNB of the 5G system etc.; obviously, it may be a device having a base station function in a subsequent system, and is not limited.
  • the core network node may be a GPRS service support node (SGSN) in UMTS or GSM, or may be a mobility management entity (MME) in the LTE system, or may be in a 5G system. Access and Mobility Management Function (AMF) entities, or other devices or nodes with the same or similar functions, are not limited.
  • the core network node may be a physical entity network element or a virtual network element, which is not limited herein.
  • the direct transmission link may be a communication link between the terminal device and a network side device (for example, an AN node), for example, a through link established between the terminal device and the AN node.
  • a network side device for example, an AN node
  • the non-direct transmission link may be a communication link between the relay device and the terminal device, for example, a relay link.
  • FIG. 1B is a schematic diagram of a 5G communication system.
  • a brief introduction to the various components of the network is given in conjunction with FIG. 1B as follows:
  • Access and mobility management function (AMF) node responsible for mobility management and access management, etc., can be used to implement mobility management entity (MME) functions other than session management. other functions.
  • MME mobility management entity
  • Session management function (SMF) node establishes a session for a terminal device, assigns a session identification (ID), and manages or terminates the session.
  • ID session identification
  • UPF node Provides functions such as session and bearer management, and IP address allocation.
  • PCF node Assigns a security policy to a network entity (for example, an access network node or a UPF node).
  • a network entity for example, an access network node or a UPF node.
  • Unified device management (UDM) node stores subscription information of users.
  • DN Data network
  • Application function (AF) node Provides application layer services.
  • the AMF node, the SMF node, the UPF node, the PCF node and the UDM node belong to the core network node.
  • the core network node registered by the terminal device may be referred to as the old/source core network node of the terminal device, or the core network node registered by the terminal device at one time; the core network node registered by the relay device may be referred to as The old core network node of the device or the core network node registered by the relay device at the time is not limited.
  • a plurality means two or more; “and/or”, describing the association relationship of the associated objects, indicating that there may be three relationships, for example, A and/or B, which may represent: separate There are three cases in which A and B exist at the same time, and B exists separately.
  • the character "/" generally indicates that the contextual object is an "or" relationship.
  • the registration request message, the registration acceptance message, and the like may be replaced with the service interface information having the same or similar functions, which is not limited.
  • a schematic diagram of a communication method provided by the first embodiment of the present application may be performed by a terminal device, as described below.
  • the relay mode includes a long-term relay mode or a temporary relay mode.
  • the long-term relay mode may refer to that after the terminal device ends communication with the network-side device by using the relay device, the relay relationship between the terminal device and the relay device continues to be maintained.
  • the long-term relay mode may also mean that the relay relationship between the terminal device and the relay device continues to be maintained when the terminal device is in an idle state.
  • the long-term relay mode may also refer to a non-direct transmission chain in which the terminal device still resides between the terminal device and the relay device after the communication between the terminal device and the network-side device is ended or when the terminal device is in an idle state.
  • the relay device is the in-vehicle device of the user and the terminal device is the WD of the user, the relay device and the terminal device may be in a long-term relay mode.
  • the temporary relay mode may refer to a termination of a relay relationship between the terminal device and the relay device after the terminal device ends communication with the network device through the relay device.
  • the temporary relay mode may also mean that the relay relationship between the terminal device and the relay device ends when the terminal device is in an idle state.
  • the temporary relay mode may also mean that the terminal device resides on the direct transmission link after the terminal device ends communication with the network side device through the relay device or when the terminal device is in an idle state.
  • data or signaling may be retransmitted to the network side device (for example, an AN node) through the relay device.
  • the terminal device may be the WD of the user, and the relay device may be the terminal device of other users, and the two may be in a temporary relay mode.
  • the foregoing step 201 may specifically be: reading the relay mode information of the terminal device from the memory.
  • step 201 can also adopt the following implementation manner:
  • the relay mode is the long-term relay mode. Specifically, if the terminal device is in the idle state, the device stays on the non-direct transmission link to listen for the message. Then the relay mode is the long-term relay mode.
  • the relay mode is the temporary relay mode. Specifically, if the terminal device is in the idle state, it stays on the direct transmission link to listen for the message. Then the relay mode is the temporary relay mode.
  • the idle mode of the terminal device may be configured by the network device (for example, an AN node) or by the human device interaction interface of the terminal device, and is not limited.
  • Manner 2 Obtain a relay mode of the terminal device according to the pre-configured association relationship.
  • the relay mode of the terminal device is obtained according to whether the terminal device and the relay device belong to the same user. For example, when the terminal device and the relay device belong to the same user, the relay mode is the long-term relay mode; or, when the terminal device and the relay device belong to different users, the relay mode is the temporary relay mode.
  • the association relationship between the UE (as the relay device) and the WD (as the terminal device) that are pre-configured with the same user is the long-term relay mode; the WD (as the terminal device) of the user and the UE of other users (as the relay device) are pre-configured.
  • the relationship between them is a temporary relay mode.
  • the association relationship may be pre-configured by the network side device or pre-configured by the human device interaction interface of the terminal device.
  • Manner 3 According to the location of the terminal device, obtain a relay mode of the terminal device.
  • the relay mode of the terminal device when the terminal device is located within the preset area, the relay mode of the terminal device is a long-term relay mode; or, when the terminal device is outside the preset area, the relay mode of the terminal device is Temporary relay mode.
  • the relay mode of the terminal device when the terminal device is located in an office or a home, the relay mode of the terminal device is a long-term relay mode; otherwise, the relay mode of the terminal device is a temporary relay mode.
  • the relay mode information may be sent to the relay device in a display or implicit manner.
  • the terminal device implements by transmitting at least one bit to the relay device.
  • the at least one bit is set to the first preset value, indicating that the relay mode of the terminal device is a long-term relay mode; when the at least one bit is set to a second preset value, indicating that the terminal device is in the middle
  • the success mode is the temporary relay mode.
  • the terminal device implements by sending a preset message to the relay device. Specifically, when the terminal device sends the preset message to the relay device, it indicates that the relay mode of the terminal device is a long-term relay mode; when the terminal device does not send the preset message to the relay device, indicating the terminal The relay mode of the device is the temporary relay mode.
  • the registration information may include at least one of the following registration parameters: identifier information of the terminal device, and identifier information of the core network node registered by the terminal device.
  • the registration information may also be a registration request message.
  • the identifier information of the terminal device is used to identify the terminal device, and may be a permanent identifier, for example, an International Mobile Subscriber Identity (IMSI), or may be a temporary identifier, for example, a 5G global unique temporary UE identifier.
  • IMSI International Mobile Subscriber Identity
  • 5G-GUTI 5G Globally Unique Temporary UE Identity, 5G-GUTI
  • 5G-TMSI 5G Temporary Mobile Station Identifier
  • the identifier information of the core network node is used to identify the core network node, and may be an identifier that is allocated by the operator to identify the core network node.
  • the identifier of the AMF is a Globally Unique AMF Identifier (GUAMI). IP address or name.
  • GUIMI Globally Unique AMF Identifier
  • IP address or name IP address or name.
  • the registration parameter may be carried in a registration request message or other message and sent to the relay device, which is not limited.
  • the registration request message may be sent by the terminal device when the registration process is initiated.
  • the registration process can be triggered by the terminal device moving out of the registration area or by periodically registering the update.
  • the registration information is encapsulated in the same message with the relay mode information of the terminal device and sent to the relay device.
  • the registration information includes the above registration parameters
  • the registration request message carries a registration parameter
  • the registration request message and the relay mode information are carried in the D2D message.
  • the registration information is a registration request message
  • the D2D message may carry a registration request message and relay mode information.
  • the registration information and the relay mode information of the terminal device may also be separately sent to the relay device.
  • the relay mode information is first sent to the relay device, and then the registration information is sent, and is not limited.
  • the method provided in this embodiment obtains a relay mode of the terminal device by using the terminal device, and sends the registration information and the relay mode information of the terminal device to the relay device, so that the relay device can be based on the relay mode information of the terminal device.
  • the registration information is sent to the AN node, which not only increases the flexibility of the terminal device registration, but also avoids network congestion caused when the terminal device accesses the communication network. For example, when the registration request message is used to request to perform on at least two devices. When registering, reduce signaling overhead and save wireless resources.
  • the method further includes: establishing, by the terminal device, the connection with the foregoing relay device, for example, a relay link.
  • the terminal device determines to access via the relay link. Then, the terminal device can select a relay device as a relay device of the terminal device, and establish a connection with the relay device, so that the relay device provides a relay service for the terminal device.
  • the connection can be a D2D connection.
  • the signal coverage difference may include: the signal strength of the AN node at the above location is lower than a preset level threshold, and/or the signal quality of the AN node at the above location is lower than a preset quality threshold.
  • the method further includes: the terminal device saves a relay relationship between the terminal device and the relay device.
  • the foregoing relay relationship may be the identifier information of the relay device.
  • the terminal device saves the identifier information of the relay device, indicating that the terminal device and the relay device are in a long-term relay mode.
  • the foregoing relay relationship may also be a correspondence between the identification information of the relay device and the identification information of the terminal device.
  • the foregoing relay relationship may also be relay mode information of the terminal device.
  • the terminal device saves the identifier information of the relay device and the relay mode information of the terminal device.
  • the foregoing method may further include: deleting, by the terminal device, the foregoing relay relationship. For example, after the data transmission on the connection established between the terminal device and the foregoing relay device is completed, the relay relationship may be deleted.
  • the method further includes: receiving, by the terminal device, the registration area information of the terminal device from the relay device and/or the registration update timer duration.
  • the registration area corresponding to the registration area information of the terminal device and the registration area of the relay device may be the same; the registration update timer duration of the terminal device may be the same as the registration update timer duration of the relay device.
  • the registration area information and/or the registration update timer duration of the terminal device may be carried in the registration accept message and sent to the terminal device, or may be carried in other messages, and is not restricted.
  • the registration area information may include a cell identifier list, or a track area (TA) identifier list, or a registration area identifier list.
  • the registration update timer duration can be used to set the registration update timer.
  • the registration area and the registration update timer may be used to initiate the registration process.
  • the terminal device may initiate a registration process.
  • FIG. 3 a schematic diagram of a communication method provided by a second embodiment of the present application is specifically as follows.
  • the relay device receives registration information from the terminal device and relay mode information of the terminal device.
  • the terminal device can communicate with the AN node by using a non-direct transmission link between the terminal device and the relay device.
  • the relay device sends a registration request message to the AN node according to the relay mode information and the registration information.
  • the registration request message may be carried in an RRC message and sent to the AN node.
  • the AN node may send the registration request message to the core network node.
  • the step 302 can be performed periodically. Specifically, the step 302 is performed with the registration update period as a cycle. In other words, the step 302 is triggered by the registration update timer.
  • the period may be a registration update period of the relay device, or a registration update period of the terminal device, or a registration update period of the relay device, a registration update period of the terminal device, and a period obtained by the preset method, which are not limited.
  • step 302 may also be performed under the trigger of step 301, for example, immediately after receiving the registration information; or when the relay device initiates the registration process, that is, when the registration process of the relay device is executed, the terminal is simultaneously implemented. Registration of equipment is not restricted.
  • the registration request message may include the following two situations:
  • the first case when the relay mode corresponding to the relay mode information is the long-term relay mode, the registration request message is used to request registration of the relay device and the terminal device.
  • the step 302 includes: when the relay mode corresponding to the relay mode information is the long-term relay mode, the relay device generates the registration request message according to the registration information of the terminal device, and sends the registration request message to the terminal device.
  • the registration request message carries the identification information of the terminal device and the identification information of the relay device.
  • the registration request message may include the identifier information of the core network node registered by the relay device and the identifier information of the core network node registered by the terminal device; or the identifier information of the core network node registered by the relay device and The identification information of the terminal device; or the identification information of the core network node registered by the terminal device and the identification information of the relay device; or the identification information of the relay device and the identification information of the terminal device; or the core network registered by the relay device
  • the identifier information of the core network node registered by the relay device may be used by the AN node to determine the target core network node of the relay device. For example, when the core network node registered by the relay device is available, and the location of the relay device is within the service range of the core network node registered by the relay device, the AN node uses the core network node registered by the relay device as the relay device. The target core network node; otherwise, the AN node may select a core network node serving the location of the relay device as the target core network node of the relay device. Further, the AN node may send a registration request message to the target core network node.
  • the identification information of the relay device and/or the identification information of the core network node registered by the relay device may be included in the registration request message.
  • the relay device may also send the identifier information of the relay device and/or the identifier information of the core network node registered by the relay device to the AN node through other messages, which is not limited herein.
  • the relay device may carry the identifier information of the relay device and the identifier information of the core network node that is registered by the relay device in the RRC message, that is, the registration request message is carried in the same RRC and sent to the AN node.
  • the RRC message may not include the identifier information of the core network node registered by the relay device, but only the identifier information of the relay device (for example, the permanent identifier of the relay device, or 5G-GUTI).
  • the AN node The location of the relay device may be obtained according to the identifier of the relay device, and then the target core network node is selected for the relay device according to the location of the relay device. Among them, how to select the target core network node belongs to the prior art, and will not be described again.
  • the registration request message includes a registration type and/or relay device indication information.
  • the registration type may be used to indicate that the registration request message is used to request registration of the relay device and the terminal device, or to register at least two devices.
  • the relay device indication information can be used to indicate which of the plurality of devices is the relay device.
  • the registration request message includes the relay device indication information, and belongs to the display indication manner.
  • the registration request message includes an identifier of the terminal device, an identifier of the relay device, and relay device indication information.
  • the relay device indication information is set to a preset value (for example, 1), it indicates that the device corresponding to the identifier located at the front end of the message is a relay device.
  • the relay device indication information may be an identification of the relay device.
  • the relay device may be indicated in an implicit manner, for example, by identifying the relay device by the identifier of the terminal device and the storage location of the identifier of the relay device in the registration request message.
  • the identity of the relay device can be stored at the location of the registration request message front end (closer to the message header of the registration request message).
  • the registration operation of the relay device and the terminal device is implemented by the registration request message, and the registration operation of the relay device and the terminal device is not required, thereby further saving the signaling overhead caused by the registration process, and the wireless resource is greatly saved.
  • the second case when the relay mode corresponding to the relay mode information is the temporary relay mode, the registration request message is used to request registration for the terminal device.
  • the registration request message is only used to request registration for the terminal device, or the registration request message is only used to request registration for at least one terminal device.
  • the relay device when the relay mode corresponding to the relay mode information is the temporary relay mode, and the registration information is a registration request message, the relay device sends a registration request message received from the terminal device to the AN node, or the relay device. Sending a second registration request message to the AN node according to the first registration request message sent by the terminal device.
  • the registration information is a registration message
  • both the terminal device 1 and the terminal device 2 communicate with the AN node through the relay device, and the relay mode between the terminal device 1 and the relay device is a temporary relay mode, and the terminal device 2
  • the relay mode between the relay devices is a temporary relay mode, and after receiving the first registration request message of the terminal device 1 and the second registration request message sent by the terminal device 2, the relay device is configured according to the first registration.
  • the request message and the second registration request message generate a third registration request message.
  • the third registration request message may carry the identification information of the terminal device 1 and the identification information of the terminal device 2, or the core network node registered by the terminal device 1
  • the identification information and the identification information of the core network node registered by the terminal device 2 are not limited.
  • the relay device when the relay mode corresponding to the relay mode information is the temporary relay mode, and the registration information is not the registration request message, the relay device generates a registration request message according to the registration information.
  • the registration information is a registration parameter
  • both the terminal device 1 and the terminal device 2 communicate with the AN node through the relay device, and the relay mode between the terminal device 1 and the relay device is a temporary relay mode, and the terminal device 2
  • the relay mode between the relay devices is a temporary relay mode
  • the relay device after receiving the registration information sent by the terminal device 1 and the terminal device 2, the relay device generates the registration information according to the terminal device 1 and the terminal device 2 Registration request message.
  • the registration request message may carry the registration information sent by the terminal device 1 and the terminal device 2. That is, the registration request message is used to request registration of the terminal device 1 and the terminal device 2, which avoids the problem of large signaling overhead caused by each terminal device independently performing the registration process.
  • the relay device may further send the identifier information of the terminal device and/or the identifier information of the core network node registered by the terminal device to the AN node.
  • the identification information of the terminal device and/or the identification information of the core network node registered by the terminal device may be obtained by the relay device by parsing the registration request message sent by the terminal device.
  • the identification information of the core network node registered by the terminal device may be used by the AN node to determine the target core network node of the terminal device. For example, when the core network node registered by the terminal device is available, and the terminal device is located in the service range of the core network node registered by the terminal device, the AN node sends a registration request message to the core network node registered by the terminal device; otherwise, the AN node selects A core network node that provides a service for the location of the terminal device serves as a target core network node of the terminal device. Further, the AN node may send a registration request message to the target core network node.
  • the identification information of the terminal device may be used by the AN node to obtain the location of the terminal device, and determine the target core network node for the terminal device according to the location of the terminal device. Among them, how to select the target core network node belongs to the prior art, and will not be described again.
  • the relay device sends the identifier information of the terminal device and/or the identifier information of the core network node that is registered by the terminal device in the same RRC message to the AN node; or the relay device identifies the identifier information of the terminal device and/or Or the identifier information of the core network node that is registered by the terminal device, and the foregoing registration request message is carried in the same RRC and sent to the AN node.
  • the second case can implement the registration process of at least one terminal device through the relay device, which not only avoids registration failure caused by poor network signal coverage, but also implements registration when multiple terminal devices are connected through one relay device. At the same time, the signaling load can be further reduced, and the radio resources and the power of the terminal device can be saved.
  • the relay device receives the registration information from the terminal device and the relay mode information of the terminal device, and sends a registration request message to the AN node according to the relay mode information and the registration information, and the relay device passes the registration.
  • the request message can initiate a registration process of one or more devices (for example, a relay device and a terminal device, or at least two terminal devices), which not only increases the flexibility of the terminal device registration, but also avoids the terminal device accessing the communication network.
  • the resulting network congestion for example, when the registration request message is used to request registration of at least two devices, reducing signaling overhead and saving radio resources.
  • the method further includes: the relay device receives the registration accept message.
  • the registration acceptance message may include:
  • the registration area information of the relay device and the registration area information of the terminal device, and the registration area corresponding to the registration area information of the relay device may be the same as the registration area corresponding to the registration area information of the terminal device; and/or,
  • the registration update timer duration of the terminal device and the registration update timer duration of the relay device, and the registration update timer duration of the terminal device and the registration update timer duration of the relay device may be the same.
  • the method may further include: the relay device sends the registration area information of the terminal device and/or the registration update timer duration to the terminal device.
  • the relay device may directly send the registration accept message to the terminal device, or carry the registration area information of the terminal device and/or the registration update timer duration in other messages and send the message to the terminal device, which is not limited.
  • the registration area information For the registration area, the registration area information, and the registration update timer duration, refer to the related description in the embodiment shown in FIG. 2, and details are not described herein.
  • FIG. 4 a schematic diagram of a communication method provided by the third embodiment of the present application is specifically as follows.
  • the AN node receives a registration request message from the relay device.
  • the registration request message may be used to request registration of the relay device and the terminal device, and the terminal device may communicate with the AN node by using the relay device, and the relay device and the terminal device may adopt a long-term relay.
  • the mode see the related description in Figure 2, will not be described again.
  • the registration request message may also be used to request registration of at least two terminal devices, and the at least two terminal devices may communicate with the AN node through the relay device, and the relay device and the at least two terminal devices may
  • the temporary relay mode is adopted, as described in the related description in FIG. 2, and details are not described herein again.
  • the first case the registration request message is used to request registration of the relay device and the terminal device.
  • the registration request message may include the identifier information of the core network node registered by the relay device and/or the identifier information of the relay device.
  • the registration request message may further include the identifier information and/or the terminal of the core network node registered by the terminal device. Identification information of the device.
  • the registration request message includes a registration type and/or a relay device indication information, where the relay device indication information is used to indicate the relay device, and may refer to the related description in the embodiment shown in FIG. 3; It is used to indicate that at least two devices are registered, for example, the registration type is specifically used to indicate registration of the relay device and the terminal device.
  • the relay device indication information is used to indicate the relay device, and may refer to the related description in the embodiment shown in FIG. 3; It is used to indicate that at least two devices are registered, for example, the registration type is specifically used to indicate registration of the relay device and the terminal device.
  • the second case the registration request message is used to request registration of at least two terminal devices.
  • the registration request message may include the identification information of the core network node registered by the at least two terminal devices and/or the identification information of the at least two terminal devices; the registration request message may also include the core of the device registration of the two terminal devices. The identification information of the network node and the identification information of the remaining devices in the two terminal devices.
  • the registration request message includes a registration type, and the registration type is used to indicate that the registration is performed on the at least two devices.
  • the registration type is specifically used to indicate that the registration is performed on the at least two terminal devices.
  • the AN node sends a registration request message to the core network node.
  • the core network node may be a core network node corresponding to the relay device.
  • the AN node may receive the identifier information of the relay device and/or the identifier information of the core network node registered by the relay device from the relay device, or obtain the identifier information of the relay device by parsing the registration request message and/or Or the identification information of the core network node that is registered by the relay device, and then determining the core network node corresponding to the relay device according to the identification information of the relay device and/or the identification information of the core network node registered by the relay device, which can be referred to The related description in the embodiment shown in FIG. 3 will not be described again.
  • the core network node may be a core network node corresponding to any one of the at least two terminal devices.
  • the core network node may be a core network node corresponding to any one of the at least two terminal devices.
  • the AN node may receive the identifier information of the terminal device and/or the identifier information of the core network node registered by the terminal device from the relay device, or obtain the identifier information of the terminal device and/or the terminal by parsing the registration request message.
  • the identifier information of the core network node that is registered by the device, and then the core network node corresponding to the terminal device is determined according to the identifier information of the terminal device and/or the identifier information of the core network node that is registered by the terminal device, as shown in the embodiment shown in FIG. The related description will not be described again.
  • the AN node receives a registration request message from the relay device, where the registration request message is used to request registration of multiple devices (for example, a relay device and a terminal device, or at least two terminal devices).
  • the AN node sends the registration request message to the core network node, which not only increases the flexibility of the terminal device registration, but also avoids network congestion caused when the terminal device accesses the communication network, for example, when the registration request message is used to request at least two When devices register, the signaling overhead is reduced and wireless resources are saved.
  • FIG. 5 a schematic diagram of a communication method according to a fourth embodiment of the present application is specifically described below.
  • the core network node receives a registration request message from the AN node.
  • the registration request message is used to request registration of the relay device and the terminal device.
  • the terminal device can communicate with the AN node through the relay device, and the long-term relay mode can be adopted between the relay device and the terminal device. Referring to the related description in FIG. 2, details are not described herein.
  • the registration request message may carry a registration type and/or a relay indication information, where the relay indication information may be used by the core network node to simultaneously carry the terminal device and the identifier information of the relay device in the paging message, to further For details, refer to the related description in the embodiment shown in FIG. 3, and details are not described herein again.
  • core network node For the core network node, refer to the description of the target core network node of the relay device in the embodiment shown in FIG. 3, and details are not described herein.
  • the core network node registers the relay device and the terminal device according to the registration request message.
  • step 502 may include: the core network node checks the registration request message according to the registration type; when the registration request message verification fails, the core network node sends the registration to the relay device. The message is rejected; when the registration request message is verified successfully, step 503 is performed.
  • the registration type indicates that the registration request message is used to request registration of the terminal device and the relay device
  • the registration request message carries the identification information of the core network node registered by the relay device and/or the relay device
  • the registration information, and the registration request message further carries the identification information of the core network node registered by the terminal device and/or the identification information of the terminal device, and the registration request message is successfully verified; otherwise, the registration request message verification fails.
  • the registration request message verification fails.
  • the core network node sends a registration accept message to the relay device.
  • the registration acceptance message may include:
  • the registration area information of the relay device and the registration area information of the terminal device wherein the registration area corresponding to the registration area information of the relay device may be the same as the registration area corresponding to the registration area information of the terminal device;
  • the registration update timer duration of the terminal device and the registration update timer duration of the relay device wherein the registration update timer duration of the terminal device may be the same as the registration update timer duration of the relay device.
  • the registration area information For the registration area information, the registration area, the registration update timer duration, and the like, refer to the related description in the embodiment shown in FIG. 2 or 3, and details are not described herein.
  • the core network node may also obtain the context information of the terminal device from the core network node registered by the terminal device.
  • the core network node sends an information request (information request) message to the core network node that is registered by the terminal device, where the information request carries the identifier of the terminal device; correspondingly, the core network node registered by the terminal device goes to the target core network node.
  • An information response message is sent, the information response message carries the context information of the terminal device, and the target core network node receives the information response message, so as to obtain the context information of the terminal device.
  • the context information may be a UE context in the prior art, or may be part of the information in the UE context, and is not limited.
  • the core network node may also obtain context information of the relay device from the core network node registered by the relay device.
  • the manner in which the core network node obtains the context information of the relay device may be the manner in which the context information of the terminal device is obtained, and details are not described herein.
  • the core network node receives a registration request message from the AN node, where the registration request message is used to request registration of the relay device and the terminal device; and the core network node processes the relay device and the terminal device according to the registration request message.
  • the registration not only increases the flexibility of the terminal device registration, but also avoids network congestion caused when the terminal device accesses the communication network. For example, when the registration request message is used to request registration of at least two devices, the signaling overhead is reduced. , saving wireless resources.
  • FIG. 6 a schematic diagram of a communication method provided by a fifth embodiment of the present application is specifically as follows.
  • the core network node receives a registration request message from the AN node.
  • the registration request message is used to request registration of at least two terminal devices.
  • the registration request message may carry a registration type. For details, refer to the related description in the embodiment shown in FIG.
  • core network node For the core network node, refer to the description of the target core network node of the terminal device in the embodiment shown in FIG. 3, and details are not described herein.
  • the core network node registers at least two terminal devices according to the registration request message.
  • step 602 may include: the core network node checks the registration request message according to the registration type; when the registration request message verification fails, the core network node sends the registration to the relay device. If the registration request message is successfully verified, step 603 is executed, and the implementation is similar to step 502, and details are not described herein.
  • the core network node sends a registration accept message to the relay device.
  • the at least two terminal devices can communicate with the AN node through the relay device, and the temporary relay mode can be adopted between the at least the terminal device and the relay device.
  • the temporary relay mode can be adopted between the at least the terminal device and the relay device.
  • the registration acceptance message may include:
  • the registration area information of the at least two terminal devices where the registration area corresponding to the registration area information of the at least two terminal devices may be the same; or
  • the registration update timer duration of the at least two terminal devices wherein the registration update timer durations of the at least two terminal devices may be the same.
  • the registration area information For the registration area information, the registration area, the registration update timer duration, and the like, refer to the related description in the embodiment shown in FIG. 2 or 3, and details are not described herein.
  • the relay device may separately send the registration accept message to the at least two terminal devices, and may also send part of the content carried in the registration accept message to the terminal device, without limitation.
  • the core network node may also obtain the terminal from the core network node registered by the any terminal device.
  • the context information of the device For the context information, refer to the related description in the embodiment shown in FIG. 5, and details are not described herein.
  • the core network node receives a registration request message from the AN node, where the registration request message is used to request registration of at least two terminal devices; and the core network node performs at least two terminal devices according to the registration request message.
  • Registration not only increases the flexibility of terminal device registration, but also avoids network congestion caused when the terminal device accesses the communication network. For example, when the registration request message is used to request registration of at least two devices, the signaling overhead is reduced. Save on wireless resources.
  • FIG. 7 is a flowchart of a communication method according to a sixth embodiment of the present application.
  • the method is exemplified by a 5G system, and is specifically as follows.
  • the terminal device sends a D2D message to the relay device.
  • the D2D message carries the registration request message and the relay mode information, and may also carry the identifier information of the AMF node registered by the terminal device.
  • the registration request message is used to request registration of the terminal device, and the registration request message may carry the identification information of the terminal device.
  • the relay device When the relay mode corresponding to the relay mode information is the temporary relay mode, the relay device sends an RRC message to the AN node.
  • the RRC message carries the registration request message, and may also carry the identifier information of the AMF node registered by the terminal device.
  • the AN node sends a registration request message to the target AMF node of the terminal device.
  • the target AMF node may be determined by the AN node according to the identifier information of the terminal device or the identifier information of the AMF node that is registered by the terminal device. For details, refer to the description of the target core network node of the terminal device in the embodiment shown in FIG. Let me repeat.
  • steps 704-706 may not be performed.
  • the target AMF node sends a UE context request to the AMF node registered by the terminal device.
  • the AMF node registered by the terminal device sends a UE context response to the target AMF node.
  • the UE context response carries the context information of the terminal device.
  • context information refer to the related description in the embodiment shown in FIG. 5, and details are not described herein.
  • the target AMF node acquires subscription information of the terminal device from the UDM.
  • the signing information belongs to the prior art and will not be described again.
  • the target AMF node allocates identifier information of the terminal device.
  • the identifier information may be a temporary identifier of the terminal device, for example, 5G-GUTI, 5G-TMSI, and may be referred to the related description in the embodiment shown in FIG. 2, and details are not described herein.
  • the target AMF node allocates mobility management (MM) parameters of the terminal device.
  • MM mobility management
  • the MM parameter may include a registration area and/or a registration update timer duration.
  • step 707 and step 708 are optional steps.
  • steps 707 and 708 may be performed.
  • step 707 may be performed; or, if the expiration time of the registration area is reached, Step 708 is performed to allocate a registration area of the terminal device.
  • the target AMF node sends a registration accept message to the relay device.
  • the registration accept message may carry the identifier information allocated in step 707 or the MM parameter allocated in step 708.
  • the relay device sends a D2D message to the terminal device.
  • the D2D message carries the registration acceptance message.
  • steps 704-708 can be interchanged and is not limited.
  • the relay mode information, the relay mode, the temporary relay mode, and the identification information can be referred to the foregoing method embodiments, and details are not described herein.
  • the terminal device sends the registration request message and the relay mode information of the terminal device to the relay device.
  • the relay mode corresponding to the relay mode information is the temporary relay mode
  • the relay device sends the relay mode to the AN node.
  • Registering the request message, and the AN node sends the registration request message to the target AMF node, where the relay device sends the registration request message based on the relay mode of the terminal device, which not only increases the flexibility of the terminal device registration, but also avoids the terminal device connection. Network congestion caused by entering the communication network. For example, when a plurality of terminal devices are registered by one relay device, the signaling load can be further reduced.
  • FIG. 8 is a flowchart of a communication method according to a seventh embodiment of the present application.
  • the method is exemplified by a 5G system, and is specifically as follows.
  • the terminal device sends a D2D message to the relay device.
  • the D2D message carries registration information and relay mode information.
  • the relay device When the relay mode corresponding to the relay mode information is the long-term relay mode, the relay device sends an RRC message to the AN node according to the registration information.
  • the RRC message carries the registration request message, and may also carry the identifier information of the AMF node registered by the relay device.
  • the registration request message is used to request registration of the terminal device and the relay device, and the registration request message may carry the identification information of the terminal device and the identification information of the relay device.
  • the AN node sends a registration request message to the target AMF node.
  • the target AMF node may be determined by the AN node according to the identifier information of the relay device or the identifier information of the AMF node that is registered by the relay device. For details, refer to the related core network node of the relay device in the embodiment shown in FIG. Description, no longer repeat them.
  • steps 804-806 may not be performed.
  • steps 807-809 may not be performed.
  • the target AMF node sends a first UE context request to the AMF node registered by the terminal device.
  • the AMF node registered by the terminal device sends a first UE context response to the target AMF node.
  • the first UE context response carries the context information of the terminal device.
  • the target AMF node acquires subscription information of the terminal device from the UDM.
  • the target AMF node sends a second UE context request to the AMF node registered by the relay device.
  • the AMF node registered by the relay device sends a second UE context response to the target AMF node.
  • the second UE context response carries context information of the relay device.
  • the target AMF node acquires subscription information of the relay device from the UDM.
  • steps 806 and 809 can be performed simultaneously, that is, the target AMF node passes the same message or the service interface information.
  • the subscription information of the relay device and the subscription information of the terminal device are obtained from the UDM.
  • the target AMF node allocates identifier information of the terminal device, and identifier information of the relay device.
  • the identification information of the terminal device may be a temporary identifier of the terminal device, and the identifier information of the relay device may be a temporary identifier of the relay device.
  • the identifier information of the relay device may be a temporary identifier of the relay device.
  • the target AMF node allocates MM parameters of the terminal device.
  • the MM parameter may include a registration area and/or a registration update timer duration.
  • the target AMF node allocates an MM parameter of the relay device.
  • the MM parameter of the terminal device and the MM parameter of the relay device may be the same.
  • the registration area of the relay device may be the same as the registration area of the terminal device; the registration update timer duration of the terminal device and the relay device
  • the registration update timer can also be the same.
  • steps 810-812 are all optional steps. For example, if the target AMF node of the terminal device is not the AMF node registered by the terminal device, the identification information of the terminal device in step 810 is performed, and step 811 is performed. In the case where the target AMF node of the relay device is not the AMF node registered by the relay device, the identification information of the assigned relay device in step 810 is performed, and step 812 is performed.
  • step 810 For example, in a case where the target AMF node of the terminal device is the AMF node registered by the terminal device, if the expiration time of the temporary identifier of the terminal device is reached, the identification information of the terminal device is allocated in step 810; or, if the registration area is reached. For the expiration time, step 811 is performed to allocate the registration area of the terminal device.
  • steps 811 and 812 can be performed simultaneously, ie the terminal device and the relay device are assigned the same MM parameters.
  • the target AMF node sends a registration accept message to the relay device.
  • the registration accepting message may carry the identifier information of the terminal device allocated in step 810 or the MM parameter of the terminal device allocated in step 811; and may also carry the identifier information of the relay device allocated in step 810 and the allocation in step 812. MM parameters of the relay device.
  • the relay device sends a D2D message to the terminal device.
  • the D2D message may include related information of the terminal device carried in the registration accept message, for example, identification information of the terminal device, or an MM parameter of the terminal device, and may also include the registration accept message.
  • the registration information, the relay mode information, the long-term relay mode, the registration area, the registration update timer duration, and the identification information can be referred to the foregoing method embodiments, and details are not described herein.
  • the terminal device sends the registration information and the relay mode information of the terminal device to the relay device.
  • the relay mode corresponding to the relay mode information is the long-term relay mode
  • the relay device sends a registration request to the AN node.
  • the registration request message is used to request registration of the terminal device and the relay device
  • the AN node sends the registration request message to the target AMF node, which not only increases the flexibility of the terminal device registration, but also avoids the terminal device accessing the communication.
  • Network congestion caused by the network for example, the registration process of the terminal device and the relay device is initiated by a registration request, which reduces signaling overhead and saves radio resources.
  • the eighth embodiment of the present application provides a schematic diagram of a communication device 900, which can be used to perform the steps of the terminal device in the foregoing method embodiment.
  • the communication device 900 can be a chip or system on a terminal device or a terminal device.
  • the communication device 900 includes a processing unit 901 and a transceiver unit 902.
  • the processing unit 901 is configured to acquire a relay mode of the terminal device.
  • the transceiver unit 902 is configured to send registration information and relay mode information of the terminal device to the relay device.
  • the registration information includes the identifier information of the terminal device and/or the identifier information of the core network node that is registered by the terminal device; or the registration information is a registration request message.
  • processing unit 901 is further configured to:
  • processing unit 901 is further configured to:
  • the relay mode of the terminal device is a long-term relay mode
  • the relay mode of the terminal device is a temporary relay mode.
  • processing unit 901 is further configured to:
  • the relay mode of the terminal device is a long-term relay mode
  • the relay mode of the terminal device is a temporary relay mode.
  • the transceiver unit 902 is further configured to:
  • the registration area corresponding to the registration area information of the terminal device may be the same as the registration area of the relay device; the registration update timer duration of the terminal device may be the same as the registration update timer duration of the relay device. .
  • the processing unit 901 may be at least one processor
  • the transceiver unit 902 may be a transceiver or a communication interface, or may be implemented in the form of a software function module.
  • the apparatus provided in this embodiment obtains the relay mode of the terminal device, and sends the registration information and the relay mode information of the terminal device to the relay device, so that the relay device can be based on the relay mode information and the registration information of the terminal device.
  • Sending a registration request message to the AN node not only increases the flexibility of the terminal device registration, but also avoids network congestion caused when the terminal device accesses the communication network.
  • a ninth embodiment of the present application provides a schematic diagram of a communication device 1000, which can be used to perform the steps of the relay device in the foregoing method embodiment.
  • the communication device 1000 can be a chip or system on a chip within a relay device or a relay device.
  • the communication device 1000 includes a transceiver unit 1001 and a processing unit 1002.
  • the transceiver unit 1001 is configured to receive registration information from the terminal device and relay mode information of the terminal device.
  • the processing unit 1002 is configured to send a registration request message to the access network AN node according to the relay mode information and the registration information.
  • the registration information includes the identifier information of the terminal device and/or the identifier information of the core network node that is registered by the terminal device; or the registration information is a registration request message.
  • the registration request message is used to request registration of the relay device and the terminal device.
  • the registration request message includes identification information of a core network node registered by the relay device and/or identification information of the relay device; the registration request message further includes a core registered by the terminal device Identification information of the network node and/or identification information of the terminal device.
  • the transceiver unit 1001 is further configured to: send the identifier information of the relay device and/or the identifier information of the core network node registered by the relay device to the AN node.
  • the registration request message includes a registration type and/or relay device indication information
  • the relay device indication information is used to indicate the relay device; the registration type is used to indicate that at least two devices are registered.
  • the transceiver unit 1001 is further configured to:
  • the registration acceptance message includes:
  • the registration area information of the relay device and the registration area information of the terminal device, and the registration area corresponding to the registration area information of the relay device is the same as the registration area corresponding to the registration area information of the terminal device; and or,
  • the duration of the registration update timer of the terminal device and the duration of the registration update timer of the relay device, and the registration update timer duration of the terminal device is the same as the registration update timer duration of the relay device.
  • the registration request message is used to request registration of the terminal device.
  • the transceiver unit 1001 is further configured to: send the identifier information of the terminal device and/or the identifier information of the core network node registered by the terminal device to the AN node.
  • the processing unit 1002 may be at least one processor
  • the transceiver unit 1001 may be a transceiver, or a communication interface, or may be implemented in the form of a software function module.
  • the apparatus provided in this embodiment receives a registration information from a terminal device and relay mode information of the terminal device, and sends a registration request message to the AN node according to the relay mode information and the registration information, where the registration request message can be used for the request.
  • Registering one or more devices not only increases the flexibility of terminal device registration, but also avoids network congestion caused when the terminal device accesses the communication network. For example, when the registration request message is used to request registration of at least two devices, signaling overhead is reduced, and radio resources are saved.
  • a tenth embodiment of the present application provides a schematic diagram of a communication device 1100, which can be used to perform the steps of an AN node in each method implementation.
  • Communication device 1100 can be a chip or system on a chip within an AN node or an AN node.
  • the communication device 1100 includes a receiving unit 1101 and a transmitting unit 1102.
  • the receiving unit 1101 is configured to receive a registration request message from the relay device, where the registration request message is used to request registration of at least two devices.
  • the at least two devices may include a relay device and a terminal device, and the terminal device may communicate with the AN node by using the relay device; the at least two devices may also be at least two terminal devices, and the at least two terminal devices pass one A temporary relay mode may be adopted between the relay device and the AN node, the communication relay device, and the at least two terminal devices.
  • the sending unit 1102 is configured to send the registration request message to a corresponding core network node of the relay device.
  • the registration request message includes the identifier information of the core network node that is registered by the relay device, and/or the identifier information of the relay device, and the identifier information of the core network node that is registered by the terminal device. / or identification information of the terminal device.
  • the registration request message includes a registration type and/or relay device indication information, where the relay device indication information is used to indicate the relay device, and the registration type is used to indicate at least two The device is registered.
  • the foregoing unit may be implemented in the form of hardware.
  • the receiving unit 1101 may be a transceiver
  • the sending unit 1102 may be a communication interface, or may be implemented in the form of a software functional module.
  • the device provided in this embodiment receives the registration request message from the relay device, where the registration request message is used to request registration of the relay device and the terminal device, or the registration request message is used to request to the at least two terminal devices.
  • the registration request message is sent to the core network node, which not only increases the flexibility of the terminal device registration, but also avoids network congestion caused when the terminal device accesses the communication network, for example, when the registration request message is used to request at least two When devices register, the signaling overhead is reduced and wireless resources are saved.
  • the eleventh embodiment of the present application provides a schematic diagram of a communications apparatus 1200, which may be used to perform the steps performed by a core network node, a target core network node, or a target AMF node in the foregoing method embodiments.
  • Communication device 1200 can be a core network node, such as an AMF node or MME, or a chip or system on a chip within a core network node.
  • the communication device 1200 may include: a transceiver unit 1201 and a processing unit 1202.
  • the transceiver unit 1201 is configured to receive a registration request message from the AN node, where the registration request message is used to request registration of at least two devices.
  • the at least two devices may include a relay device and a terminal device, and the terminal device may communicate with the AN node through the relay device.
  • the at least two devices may also be at least two terminal devices, and the at least two terminal devices may use a temporary relay mode between the communication relay device and the at least two terminal devices by using one relay device and the at least two terminal devices, see The related description in FIG. 2 will not be described again.
  • the processing unit 1202 is configured to register the relay device and the terminal device according to the registration request message.
  • the transceiver unit 1201 is further configured to send a registration accept message to the relay device.
  • the registration request message includes the identifier information of the core network node that is registered by the relay device, and/or the identifier information of the relay device, and the identifier information of the core network node that is registered by the terminal device. / or identification information of the terminal device.
  • the transceiver unit 1201 is further configured to:
  • the registration accept message includes:
  • the registration area information of the relay device and the registration area information of the terminal device, and the registration area corresponding to the registration area information of the relay device is the same as the registration area corresponding to the registration area information of the terminal device; and or,
  • the duration of the registration update timer of the terminal device and the duration of the registration update timer of the relay device, and the registration update timer duration of the terminal device is the same as the registration update timer duration of the relay device.
  • the registration request message further includes a registration type and/or relay device indication information, where the relay device indication information is used to indicate the relay device, and the registration type is used to indicate at least two Devices are registered.
  • the processing unit 1202 may be at least one processor
  • the transceiver unit 1201 may be a transceiver, or a communication interface, or may be implemented in the form of a software function module. .
  • the device provided in this embodiment receives the registration request message from the AN node, where the registration request message is used to request registration of the relay device and the terminal device; and the registration of the relay device and the terminal device according to the registration request message increases not only
  • the flexibility of the terminal device registration can also avoid the network congestion caused when the terminal device accesses the communication network. For example, when the registration request message is used to request registration of at least two devices, the signaling overhead is reduced, and the radio resources are saved.
  • a twelfth embodiment of the present application provides a schematic diagram of a communication device 1300 including at least one processor 1301 and a memory 1302, a communication bus 1303, and at least one communication interface 1304.
  • the device 1300 can be any device in the embodiment of the present application, and the device 1300 can be used to perform the method provided by the embodiment of the present application.
  • the processor 1301 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 program of the present application.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the memory 1302 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 information that can store information and instructions.
  • ROM read-only memory
  • RAM random access memory
  • Type of dynamic storage device or Electrostatic Erasable Programmable Read-Only Memory (EEPROM), Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, optical disc Storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other medium accessed by the device, but is not limited thereto.
  • the memory can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • Communication bus 1303 can include a path for communicating information between the components.
  • any device such as a transceiver can be used for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), WALN, and the like.
  • RAN Radio Access Network
  • WALN Wireless Local Area Network
  • the memory 1303 is used to store program codes, and the processor 1301 is configured to execute program codes stored in the memory 1302.
  • the processor 1301 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • apparatus 1300 can include multiple processors, such as processor 1301 and processor 1305 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 device shown in FIG. 13 may be a component of a terminal device or a terminal device, and one or more software modules are stored in a memory of the device shown in FIG.
  • the apparatus shown in FIG. 13 can implement the steps performed by the terminal device in the embodiments of the present application by executing the program code in the memory by the processor.
  • the device shown in FIG. 13 may be a component of a relay device or a relay device, and one or more software modules are stored in the memory of the device shown in FIG.
  • the apparatus shown in FIG. 13 can implement the steps performed by the relay device in the embodiments of the present application by the processor executing the program code in the memory.
  • the apparatus shown in FIG. 13 may be an integral part of an AN node or an AN node, and one or more software modules are stored in the apparatus memory shown in FIG.
  • the apparatus shown in FIG. 13 can implement the steps performed by the AN node in various embodiments of the present application by the processor executing program code in the memory.
  • the apparatus shown in FIG. 13 may be a component of a core network node or a core network node, and one or more software modules are stored in a memory of the apparatus shown in FIG.
  • the apparatus shown in FIG. 13 can implement the steps performed by the core network node or the target AMF node in the embodiments of the present application by the processor executing the program code in the memory.
  • the embodiment of the present application further provides a computer storage medium, which is stored with program code, and the program, when executed by the processor, can be used to execute the steps of the terminal device in the foregoing method embodiments.
  • the embodiment of the present application further provides a computer storage medium storing program code, which, when executed by the processor, can be used to execute the steps of the relay device in the foregoing method embodiments.
  • the embodiment of the present application further provides a computer storage medium storing program code, which, when executed by the processor, can be used to execute the steps of the AN node in each of the foregoing method embodiments.
  • the embodiment of the present application further provides a computer storage medium storing program code, which, when executed by the processor, can be used to execute the steps of the core network node or the target AMF node in the foregoing method embodiments.
  • the embodiment of the present application also provides a computer program product.
  • the computer program product comprises computer software instructions executable by a processor to implement the method of the terminal device in the various method embodiments described above.
  • the embodiment of the present application also provides a computer program product.
  • the computer program product includes computer software instructions executable by a processor to implement the method of relaying devices in the various method embodiments described above.
  • the embodiment of the present application also provides a computer program product.
  • the computer program product includes computer software instructions executable by a processor to implement the methods of the AN nodes in the various method embodiments described above.
  • the embodiment of the present application also provides a computer program product.
  • the computer program product includes computer software instructions executable by a processor to implement a method of a core network node or a target AMF node in the various method embodiments described above.
  • the embodiment of the present application further provides a communication system including the communication device shown in FIGS. 9-12.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

Landscapes

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

Abstract

本申请实施例公开了一种通信方法和装置。该方法包括：终端设备获得终端设备的中继模式；终端设备向中继设备发送注册信息和终端设备的中继模式信息，可以使得中继设备能够基于该终端设备的中继模式信息和注册信息向AN节点发送注册请求消息，增加了终端设备注册的灵活性，从而可以避免终端设备接入通信网络时造成的网络拥塞。

Description

通信方法和装置 技术领域
本申请实施例涉及通信领域，尤其涉及一种通信方法和装置。
背景技术
随着物联网(Internet of Things,IoT)以及移动通信技术的发展，IoT终端(例如，传感器)在测量、建筑、农业、物流、智慧城市、家庭等领域得到广泛使用。在现有技术中，IoT终端直接接入通信网络。然而，由于IoT终端的部署越来越密集，现有IoT终端接入通信网络的方式容易造成网络拥塞。
发明内容
本申请实施例提供一种通信方法及装置，用以避免因IoT终端接入通信网络而造成的网络拥塞。
第一方面，提供了一种通信方法，所述方法包括：终端设备获得所述终端设备的中继模式；所述终端设备向中继设备发送注册信息和所述终端设备的中继模式信息，使得中继设备能够基于该终端设备的中继模式信息和注册信息向AN节点发送注册请求消息，增加了终端设备注册的灵活性，从而可以避免终端设备接入通信网络时造成的网络拥塞。
其中，中继模式信息对应的中继模式可以包括长期中继模式或临时中继模式。
结合第一方面，在第一方面的第一种实现方式中，所述注册信息包括所述终端设备的标识信息和/或所述终端设备注册的核心网节点的标识信息；或，所述注册信息为注册请求消息。其中，注册请求消息可以携带有终端设备的标识信息，用于请求对终端设备进行注册；终端设备的标识信息用于标识终端设备，可以为永久标识，例如，IMSI，也可以为临时标识，例如，5G-GUTI，或5G-TMSI；中继设备的标识信息用于标识中继设备，可以为永久标识，也可以为临时标识。
结合第一方面或第一方面的第一种实现方式，在第一方面的第二种实现方式中，所述终端设备获得所述终端设备的中继模式，包括：所述终端设备根据所述终端设备的空闲态驻留方式，获得所述终端设备的中继模式；或，所述终端设备根据预先配置的关联关系，获得所述终端设备的中继模式；或，所述终端设备根据所述终端设备的位置，获得所述终端设备的中继模式。本申请获得中继模式的方法不限于上述方式，还可以包括通过人机交互接口动态设置中继模式等，不予限制。
结合第一方面或第一方面的第一或第二种实现方式，在第一方面的第三种实现方式中，所述方法还包括：所述终端设备接收来自所述中继设备的所述终端设备的注册区域信息和/或注册更新定时器时长，以使得中继设备与终端设备能够同时发起由于移出注册区域而引发的注册流程，进而实现中继设备通过发送一条注册请求消息来实现中继设备和终端设备的同时注册；其中，所述终端设备的注册区域信息对应的注册区域与所述中继设备的注册区域相 同；所述终端设备的注册更新定时器时长与所述中继设备的注册更新定时器时长相同，以使得中继设备和终端设备能够同时发起周期性的注册更新，进而中继设备可以通过发送一条注册请求消息来实现中继设备和终端设备的同时注册。
第二方面，提供了一种通信方法，所述方法包括：中继设备接收来自终端设备的注册信息和所述终端设备的中继模式信息；所述中继设备根据所述中继模式信息和所述注册信息，向接入网AN节点发送注册请求消息。该注册请求消息可以用于请求对一个或多个设备(例如，中继设备和终端设备，或至少两个终端设备)进行注册，增加了终端设备注册的灵活性，从而可以避免终端设备接入通信网络时造成的网络拥塞。此外，当中继设备通过一条注册请求消息发起多个设备的注册流程时，大大减少了信令开销，节省了无线资源。
结合第二方面，在第二方面的第一种实现方式中，所述注册信息包括所述终端设备的标识信息和/或所述终端设备注册的核心网节点的标识信息，此时该注册信息用于中继设备生成注册请求消息；或，所述注册信息为注册请求消息，该注册请求消息用于请求对终端设备进行注册，可以包含终端设备的标识信息，此时该注册请求消息可以用于中继设备生成一个新的注册请求消息，也可以用于中继设备将该注册请求消息直接发送给AN节点。
结合第二方面或第二方面的第一种实现方式，在第二方面的第二种实现方式中，当所述中继模式信息对应的中继模式为长期中继模式时，所述注册请求消息用于请求对所述中继设备和所述终端设备进行注册。通过该注册请求消息能够实现同时对中继设备和终端设备进行注册，降低了信令负荷，节省了无线资源。
结合第二方面的第二种实现方式，在第二方面的第三种实现方式中，所述注册请求消息包含所述中继设备注册的核心网节点的标识信息和/或所述中继设备的标识信息，可以用于接收到该注册请求消息的核心网节点获取中继设备的签约信息或上下文信息等；所述注册请求消息包含还包含所述终端设备注册的核心网节点的标识信息和/或所述终端设备的标识信息，可以用于接收到该注册请求消息的核心网节点获取终端设备的签约信息或上下文信息等。
结合第二方面的第二或第三种实现方式，在第二方面的第四种实现方式中，所述方法还包括：所述中继设备向所述AN节点发送所述中继设备的标识信息和/或所述中继设备注册的核心网节点的标识信息，可以用于AN节点确定核心网节点，即中继设备的目标核心网节点，以便于AN节点将注册请求消息发送给该核心网节点，完成终端设备和中继设备的注册流程。
结合第二方面的第二至第四种实现方式中任一种，在第二方面的第五种实现方式中，所述注册请求消息包含注册类型和/或中继设备指示信息；其中，所述中继设备指示信息用于指示所述中继设备，可以用于核心网节点对终端设备进行寻呼，例如，寻呼消息携带中继设备的标识信息，以便能够快速地寻呼到该终端设备；所述注册类型用于指示对至少两个设备进行注册，可以用于核心网节点对注册请求消息进行校验，若校验不通过，则核心网节点向中继设备发送注册拒绝消息。
结合第二方面的第二至第五种实现方式中任一种，在第二方面的第六种实现方式中，所述方法还包括：所述中继设备接收注册接受消息，所述注册接受消息包含：所述中继设备的注册区域信息和所述终端设备的注册区域信息，且所述中继设备的注册区域信息对应的注册区域与所述终端设备的注册区域信息对应的注册区域相同，以使得中继设备与终端设备能够同时发起由于移出注册区域而引发的注册流程，进而实现一条注册请求消息实现中继设备和 终端设备的同时注册；和/或，所述注册接受消息包含：所述终端设备的注册更新定时器时长和所述中继设备的注册更新定时器时长，且所述终端设备的注册更新定时器时长与所述中继设备的注册更新定时器时长相同，以使得中继设备和终端设备能够同时发起周期性的注册更新，进而实现一条注册请求消息实现中继设备和终端设备的同时注册。
结合第二方面或第二方面的第一种实现方式，在第二方面的第七种实现方式中，当所述中继模式信息对应的中继模式为临时中继模式时，所述注册请求消息用于请求对所述终端设备进行注册。所述注册请求消息实现了终端设备通过中继设备完成注册。此外，所述注册请求消息还可以用于请求对其它终端设备进行注册，其它终端设备也是通过所述中继设备与AN节点通信。例如，中继设备同时或者预设时间段内收到多个终端设备发送的注册请求消息，则可以根据接收到的注册请求消息生成一条新的注册请求消息，并发送给AN节点，进一步节省了无线资源。
结合第二方面的第七种实现方式，在第二方面的第八种实现方式中，所述方法还包括：所述中继设备向所述AN节点发送所述终端设备的标识信息和/或所述终端设备注册的核心网节点的标识信息，用于AN节点确定核心网节点，即终端设备的目标核心网节点，以便于AN节点将注册请求消息发送给该核心网节点，完成终端设备的注册流程。
第三方面，提供了一种通信方法，所述方法包括：接入网AN节点接收来自中继设备的注册请求消息；所述AN节点向所述中继设备的对应的核心网节点发送所述注册请求消息。其中，所述注册请求消息可以用于请求对至少两个设备(例如，中继设备和终端设备，或，至少两个终端设备)进行注册，不但增加了终端设备注册的灵活性，还减少信令开销，节省无线资源，从而避免了终端设备接入通信网络时造成的网络拥塞。其中，该终端设备或该至少两个终端设备可以通过中继设备与AN节点通信。
结合第三方面，在第三方面的第一种实现方式中，所述注册请求消息包含所述中继设备注册的核心网节点的标识信息和/或所述中继设备的标识信息，可以用于核心网节点获取中继设备的签约信息或上下文信息等；所述注册请求消息还包含所述终端设备注册的核心网节点的标识信息和/或所述终端设备的标识信息，可以用于核心网节点获取终端设备的签约信息或上下文信息等。
结合第三方面或第三方面的第一种实现方式，在第三方面的第二种实现方式中，所述注册请求消息包含注册类型和/或中继设备指示信息；其中，所述中继设备指示信息用于指示所述中继设备，可以用于核心网节点对终端设备进行寻呼，例如，寻呼消息携带中继设备的标识信息，以便能够快速地寻呼到该终端设备；所述注册类型用于指示对至少两个设备进行注册，可以用于核心网节点校验注册请求消息，若校验失败，则核心网节点向中继设备发送注册拒绝消息。
第四方面，提供了一种通信方法，所述方法包括：核心网节点接收来自接入网AN节点的注册请求消息，所述注册请求消息用于请求对中继设备和终端设备进行注册；所述核心网节点根据所述注册请求消息，对所述中继设备和所述终端设备进行注册；所述核心网节点向所述中继设备发送注册接受消息，该方法不但增加了终端设备注册的灵活性，还减少信令开销，节省无线资源，从而避免了终端设备接入通信网络时造成的网络拥塞。
结合第四方面，在第四方面的第一种实现方式中，所述注册请求消息包含所述中继设备注册的核心网节点的标识信息和/或所述中继设备的标识信息，可以用于核心网节点获取中继设备的签约信息或上下文信息等；所述注册请求消息还包含所述终端设备注册的核心网节 点的标识信息和/或所述终端设备的标识信息，可以用于核心网节点获取终端设备的签约信息或上下文信息等。
结合第四方面或第四方面的第一种实现方式，在第四方面的第二种实现方式中，所述方法还包括：所述核心网节点从所述终端设备注册的核心网节点获取所述终端设备的上下文信息；和/或，所述核心网节点从所述中继设备注册的核心网节点获取所述中继设备的上下文信息。
结合第四方面或第四方面的上述任一种实现方式，在第四方面的第三种实现方式中，所述注册接受消息包含：所述中继设备的注册区域信息和所述终端设备的注册区域信息，且所述中继设备的注册区域信息对应的注册区域与所述终端设备的注册区域信息对应的注册区域相同，以使得中继设备与终端设备能够同时发起由于移出注册区域而引发的注册流程，进而实现一条注册请求消息实现中继设备和终端设备的同时注册；或者，所述终端设备的注册更新定时器时长和所述中继设备的注册更新定时器时长，且所述终端设备的注册更新定时器时长与所述中继设备的注册更新定时器时长相同，以使得中继设备和终端设备能够同时发起周期性的注册更新，进而实现一条注册请求消息实现中继设备和终端设备的同时注册。
结合第四方面或第四方面的上述任一种实现方式，在第四方面的第四种实现方式中，所述注册请求消息还包含注册类型和/或中继设备指示信息；其中，所述中继设备指示信息用于指示所述中继设备，可以用于核心网节点对终端设备进行寻呼，例如，寻呼消息携带中继设备的标识信息，以便能够快速地寻呼到该终端设备；所述注册类型用于指示对至少两个设备进行注册，可以用于核心网节点校验注册请求消息，若校验失败，则核心网节点向中继设备发送注册拒绝消息。
第五方面，提供了一种通信装置，包括用于执行以上第一方面或以上第一方面的任一实现方式中的方法中各个步骤的单元或者手段(means)。该通信装置可以是终端设备，例如，远端UE，也可以是至少一个处理元件或芯片。
第六方面，提供了一种通信装置，包括用于执行以上第二方面或以上第二方面的任一实现方式中的方法中各个步骤的单元或者手段(means)。该通信装置可以是中继设备，例如，中继UE，也可以是至少一个处理元件或芯片。
第七方面，提供了一种通信装置，包括用于执行以上第三方面或以上第三方面的任一实现方式中的方法中各个步骤的单元或者手段(means)。该通信装置可以是AN节点，也可以是至少一个处理元件或芯片。
第八方面，提供了一种通信装置，包括用于执行以上第四方面或以上第四方面的任一实现方式中的方法中各个步骤的单元或者手段(means)。该通信装置可以是核心网节点，例如，AMF，也可以是至少一个处理元件或芯片。
第九方面，提供了一种通信装置，包括处理器和存储器，存储器用于存储程序，处理器调用存储器存储的程序，以执行以上第一方面或以上第一方面的任一实现方式中的方法。该通信装置可以是终端设备，例如，通过中继设备与AN节点通信的终端设备，或在无线网络覆盖范围外的终端设备，也可以是至少一个处理元件或芯片。
第十方面，提供了一种通信装置，包括处理器和存储器，存储器用于存储程序，处理器调用存储器存储的程序，以执行以上第二方面或以上第二方面的任一实现方式中的方法。该通信装置可以是中继设备，例如，中继UE，也可以是至少一个处理元件或芯片。
第十一方面，提供了一种通信装置，包括处理器和存储器，存储器用于存储程序，处理 器调用存储器存储的程序，以执行以上第三方面或以上第三方面的任一实现方式中的方法。该通信装置可以是AN节点，例如，基站，也可以是至少一个处理元件或芯片。
第十二方面，提供了一种通信装置，包括处理器和存储器，存储器用于存储程序，处理器调用存储器存储的程序，以执行以上第四方面或以上第四方面的任一实现方式中的方法。该通信装置可以是核心网节点，该核心网节点可以具备移动性管理功能，例如，AMF节点或MME，也可以是至少一个处理元件或芯片。
第十三方面，提供了一种程序，该程序在被处理器执行时用于执行以上第一方面的任一方法。
第十四方面，提供了一种计算机可读存储介质，包括第十三方面的程序。
第十五方面，提供了一种程序，该程序在被处理器执行时用于执行以上第二方面的任一方法。
第十六方面，提供了一种计算机可读存储介质，包括第十五方面的程序。
第十七方面，提供了一种程序，该程序在被处理器执行时用于执行以上第三方面的任一方法。
第十八方面，提供了一种计算机可读存储介质，包括第十七方面的程序。
第十九方面，提供了一种程序，该程序在被处理器执行时用于执行以上第四方面的任一方法。
第二十方面，提供了一种计算机可读存储介质，包括第十九方面的程序。
第二十一方面，提供了一种系统，包括第五方面至第八方面的通信装置。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图进行简单地介绍，显而易见地，下面描述中的附图是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1A为一种通信系统的示意图；
图1B为一种5G通信系统的架构示意图；
图2为本申请第一实施例提供的一种通信方法的示意图；
图3为本申请第二实施例提供的一种通信方法的示意图；
图4为本申请第三实施例提供的一种通信方法的示意图；
图5为本申请第四实施例提供的一种通信方法的示意图；
图6为本申请第五实施例提供的一种通信方法的示意图；
图7为本申请第六实施例提供的一种通信方法的流程图；
图8为本申请第七实施例提供的一种通信方法的流程图；
图9为本申请第八实施例提供的一种通信装置的结构示意图；
图10为本申请第九实施例提供的一种通信装置的结构示意图；
图11为本申请第十实施例提供的一种通信装置的结构示意图；
图12为本申请第十一实施例提供的一种通信装置的结构示意图；
图13为本申请第十二实施例提供的一种通信装置的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
本申请实施例可以应用于长期演进(Long Term Evolution，LTE)网络，通用移动通讯系统(Universal Mobile Telecommunications System，UMTS)，全球移动通信系统(Global system for mobile communications，GSM)，第五代(5rd generation，5G)通信系统，非第三代合作伙伴计划(3rd generation partnership project,3GPP)通信系统，或者下一代通信系统，本申请实施例不予限制。
图1A提供了一种通信系统的示意图。本申请实施例可以应用于该通信系统，具体地，该通信系统可以为一种设备到设备(device to device，D2D)的通信系统。当然，本申请的实施例还可以应用于非D2D的通信系统。
如图1A所示，该通信系统包括网络侧设备，终端设备以及中继设备。其中，网络侧设备可以包括核心网节点和接入网(access network，AN)节点。终端设备可以通过中继设备和网络侧设备与运营商服务网络或者internet进行通信。
下面结合图1A对本申请中涉及的设备和部分用语进行简单介绍如下：
终端设备，可以包括各种具有无线通信功能的手持设备、车载设备、穿戴设备(wired device，WD)、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的终端，移动台(mobile station，MS)，终端(terminal)，用户设备(user equipment，UE)，软终端等等。例如，远端(remote)UE,IoT终端。本申请实施例中，以终端设备为穿戴设备为例进行举例说明。
中继(relay)设备，可以通过与基站建立无线资源控制(radio resource control，RRC)连接和非接入层(non-access stratum，NAS)连接，进行无线承载的连接管理。例如，中继设备可以为具有中继功能的终端设备或者基站。本申请中，将对终端设备的信号进行中继的设备称之为中继设备。在本申请中，以穿戴设备关联的终端设备为中继设备进行举例说明。
AN节点，可以是基站，例如，GSM中的基站(Base Transceiver Station，BTS)，UMTS中的基站(NodeB)，此时，AN节点可以通过基站控制设备与核心网节点通信；也可以是LTE中的演进型基站(evolved Node B，eNB或e-NodeB)，或，5G系统的gNB等；显然，也可以是后续系统中具备基站功能的设备，不予限制。
核心网节点，可以是UMTS或GSM中的GPRS业务支撑节点(serving GPRS support node，SGSN)，还可以是LTE系统中的移动性管理实体(mobility management entity，MME)，也可以是5G系统中的接入和移动性管理功能(Access and Mobility Management Function，AMF)实体，或其它具备相同或相似功能的设备或节点，不予限制。在本申请中，核心网节点即可以是物理上的实体网元，也可以是虚拟的网元，在此不做限定。
直传链路可以是终端设备与网络侧设备(例如，AN节点)之间的通信链路，例如，终端设备与AN节点之间建立的直通链路。终端设备与AN节点之间不通过中继设备建立的链路。
非直传链路可以是中继设备与终端设备之间的通信链路，例如，中继链路。
本申请实施例的方法可以应用在5G通信系统中，图1B为一种5G通信系统的架构示意图。结合图1B对对该网络中的各个组成部分进行简单介绍如下：
接入和移动管理功能(access and mobility management function，AMF)节点：负责 移动性管理和接入管理等，可以用于实现移动性管理实体(mobility management entity，MME)功能中除会话管理之外的其它功能。
会话管理功能(session management function，SMF)节点：为终端设备建立会话，分配会话标识(ID)，以及管理或终止会话。
用户面功能(User plane function，UPF)节点：提供会话和承载管理，IP地址分配等功能。
策略控制功能(Policy Control Function，PCF)节点：为网络实体(例如，接入网节点或UPF节点)分配安全策略。
统一设备管理(unified device management，UDM)节点：存储用户的签约信息。
数据网络(data network，DN)：提供外部数据网络服务。
应用功能(application function，AF)节点：提供应用层服务。
其中，AMF节点，SMF节点，UPF节点，PCF节点和UDM节点均属于核心网节点。
在本申请中，终端设备注册的核心网节点可以称之为终端设备的旧/源核心网节点，或终端设备上一次注册的核心网节点；中继设备注册的核心网节点可以称之为中继设备的旧核心网节点，或中继设备上一次注册的核心网节点，不予限制。
在本申请中，“多个”是指两个或两个以上；“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
需要说明的是，本申请中提及的示例性地不代表是最优的；本申请中提及的第一、第二等仅用于区分不同的信息、消息或其他对象，不代表顺序关系；此外，本申请中各实施例之间可以相互参考和借鉴，相同或相似的步骤或名词均不再一一赘述。
在本申请中，若AN节点与核心网节点之间采用服务化方式实现，那么注册请求消息，注册接受消息等均可以替换成具有相同或相似功能的服务化接口信息，不予限制。
在本申请中，各实施例中的步骤执行先后顺序没有严格的限定，可以互相调换或调整。
如图2所示，本申请第一实施例提供的一种通信方法的示意图，该方法可以由终端设备执行，具体如下所述。
201、获得终端设备的中继模式。
其中，中继模式包括长期中继模式或临时中继模式。
具体地，长期中继模式可以指在终端设备通过中继设备与网络侧设备的通信结束后，该终端设备与该中继设备之间的中继关系继续保持。长期中继模式也可以指在终端设备处于空闲态时，该终端设备与该中继设备之间的中继关系继续保持。长期中继模式还可以指终端设备通过中继设备与网络侧设备的通信结束后或终端设备处于空闲态时，终端设备仍驻留在该终端设备与该中继设备之间的非直传链路上。例如，当中继设备为用户的车载设备，终端设备为该用户的WD时，中继设备和终端设备之间可以为长期中继模式。
具体地，临时中继模式可以指在终端设备通过中继设备与网络侧设备的通信结束后，该终端设备与该中继设备之间的中继关系结束。临时中继模式也可以指终端设备处于空闲态时，该终端设备与该中继设备之间的中继关系结束。临时中继模式还可以指在终端设备通过中继设备与网络侧设备的通信结束后或终端设备处于空闲态时，终端设备驻留在直传链路 上。进一步地，当终端设备存在待传输的数据或信令时，可以重新通过该中继设备将数据或信令发送给网络侧设备(例如，AN节点)。例如，终端设备可以为用户的WD，中继设备可以为其它用户的终端设备，两者之间可以为临时中继模式。
其中，当中继模式信息预先存储在终端设备的存储器中时，上述步骤201具体可以为从该存储器中读取该终端设备的中继模式信息。
此外，步骤201还可以采用如下实现方式：
方式一、根据终端设备的空闲态驻留方式，获得该终端设备的中继模式。
例如，若终端设备在空闲态时驻留在非直传链路，则中继模式为长期中继模式，具体的，若终端设备在空闲态时驻留在非直传链路上监听消息，则中继模式为长期中继模式。
再例如，若该终端设备在空闲态时驻留在直传链路，则中继模式为临时中继模式，具体的，若终端设备在空闲态时驻留在直传链路上监听消息，则中继模式为临时中继模式。
其中，终端设备的空闲态驻留方式可以通过网络侧设备(例如，AN节点)进行配置，也可以通过终端设备的人机交互接口配置，不予限制。
方式二、根据预先配置的关联关系，获得终端设备的中继模式。
具体地，根据终端设备和中继设备是否属于同一用户，获得终端设备的中继模式。例如，当终端设备与中继设备属于同一用户时，中继模式为长期中继模式；或，当终端设备与中继设备属于不同用户时，中继模式为临时中继模式。
下面以WD和UE进行举例说明：
预先配置同一用户的UE(作为中继设备)与WD(作为终端设备)之间的关联关系为长期中继模式；预先配置用户的WD(作为终端设备)与其它用户的UE(作为中继设备)之间的关联关系为临时中继模式。
其中，该关联关系可以通过网络侧设备预先配置，也可以通过终端设备的人机交互接口预先配置。
方式三、根据终端设备的位置，获得该终端设备的中继模式。
具体地，当终端设备位于预设区域范围之内时，该终端设备的中继模式为长期中继模式；或者，当终端设备位于预设区域范围之外时，该终端设备的中继模式为临时中继模式。例如，当终端设备位于办公室或家中时，该终端设备的中继模式为长期中继模式；否则，该终端设备的中继模式为临时中继模式。
202、向中继设备发送注册信息和终端设备的中继模式信息。
其中，中继模式信息可以通过显示或隐式的方式发送给中继设备。
以一种显示的发送方式为例，终端设备通过发送至少一个比特位给中继设备来实现。当该至少一个比特位设置为第一预设值时，表明该终端设备的中继模式为长期中继模式；当该至少一个比特位设置为第二预设值时，表明该终端设备的中继模式为临时中继模式。
以一种隐式的发送方式为例，终端设备通过发送预设的消息给中继设备来实现。具体地，当终端设备发送该预设的消息给中继设备时，表明该终端设备的中继模式为长期中继模式；当终端设备不发送该预设的消息给中继设备，表明该终端设备的中继模式为临时中继模式。
其中，注册信息可以包括以下至少一种注册参数：终端设备的标识信息、终端设备注册的核心网节点的标识信息。该注册信息也可以是注册请求消息。
具体地，终端设备的标识信息用于标识该终端设备，可以为永久标识，例如，国际移动用户识别码(International Mobile Subscriber Identity，IMSI)；也可以为临时标识，例如， 5G全球唯一临时UE标识(5G Globally Unique Temporary UE Identity，5G-GUTI)、5G临时移动台标识符(5G Temporary Mobile Station Identifier，5G-TMSI)。
具体地，核心网节点的标识信息用于标识核心网节点，可以是运营商分配的用于识别核心网节点的标识，例如，AMF的标识为全球唯一AMF标识(Globally Unique AMF Identifier，GUAMI)，IP地址或名称。需要指出的是，当终端设备的标识信息中的部分比特为该终端设备注册的核心网节点的标识信息时，例如，5G-GUTI包含AMF标识(GUAMI)，上述注册信息可以仅包含终端设备的标识信息。
具体地，当注册信息为注册参数时，该注册参数可以携带在注册请求消息或其它消息中发送给中继设备，不予限制。其中，该注册请求消息可以是终端设备在发起注册流程时发送的。该注册流程可以由终端设备移出注册区域，或周期性注册更新触发的。
可选地，注册信息与终端设备的中继模式信息封装在同一个消息中发送给中继设备。例如，假设注册信息包括上述注册参数，注册请求消息携带注册参数，该注册请求消息和中继模式信息携带在D2D消息中。再例如，假设注册信息为注册请求消息，D2D消息可以携带注册请求消息和中继模式信息。注册信息与终端设备的中继模式信息也可以分别发送给中继设备，例如，先将中继模式信息发送给中继设备，再发送注册信息，不予限制。
本实施例提供的方法，通过终端设备获得终端设备的中继模式，并向中继设备发送注册信息和终端设备的中继模式信息，使得中继设备能够基于该终端设备的中继模式信息和注册信息向AN节点发送注册请求消息，不但增加了终端设备注册的灵活性，还可以避免终端设备接入通信网络时造成的网络拥塞，例如，当注册请求消息用于请求对至少两个设备进行注册时，减少信令开销，节省无线资源。
可选地，在步骤201之前，还包括：终端设备与上述中继设备建立连接，例如：中继链路。
在一个示例中，当AN节点在终端设备所处位置的信号覆盖差时，该终端设备确定通过中继链路接入。然后，终端设备可以选择一个中继设备作为该终端设备的中继设备，并与该中继设备建立连接，以便于该中继设备为该终端设备提供中继服务。在一种可能的实现方式中，该连接可以是D2D连接。
其中，信号覆盖差可以包括：AN节点在上述位置的信号强度低于预设电平门限，和/或，AN节点在上述位置的信号质量低于预设质量门限。
可选地，上述方法还包括：终端设备保存该终端设备与该中继设备之间的中继关系。
其中，上述中继关系可以为中继设备的标识信息，例如：终端设备保存该中继设备的标识信息，表明该终端设备与该中继设备之间为长期中继模式。
上述中继关系也可以为中继设备的标识信息与终端设备的标识信息之间的对应关系。
上述中继关系还可以为终端设备的中继模式信息，例如，终端设备保存中继设备的标识信息以及该终端设备的中继模式信息。
当终端设备的中继模式为临时中继模式时，上述方法还可以包括：终端设备删除上述中继关系。例如，在终端设备与上述中继设备建立的连接上的数据传输完毕后，可以删除上述中继关系。
可选地，在步骤202之后，还包括：终端设备接收来自中继设备的该终端设备的注册区 域信息和/或注册更新定时器时长。
其中，终端设备的注册区域信息对应的注册区域与中继设备的注册区域可以相同；终端设备的注册更新定时器时长与中继设备的注册更新定时器时长可以相同。
具体的，该终端设备的注册区域信息和/或注册更新定时器时长可以携带在注册接受消息中发送给终端设备，也可以携带在其它消息中发送，不予限制。
其中，该注册区域信息可以包括小区标识列表，或跟踪区(track area，TA)标识列表，或注册区标识列表。注册更新定时器时长可以用于设置注册更新定时器。
需要指出的是，注册区域和注册更新定时器均可以用于发起注册流程，示例性地，当终端设备移出注册区域，或者，终端设备的注册更新定时器超时时，终端设备可以发起注册流程。
如图3所示，本申请第二实施例提供的通信方法的示意图，具体如下所述。
301、中继设备接收来自终端设备的注册信息和终端设备的中继模式信息。
其中，中继模式信息和注册信息，可以参见步骤202中的相关描述，不再赘述。
其中，终端设备可以通过该终端设备与中继设备之间的非直传链路与AN节点进行通信。
302、中继设备根据中继模式信息和注册信息，向AN节点发送注册请求消息。
其中，该注册请求消息可以携带在RRC消息中发送给AN节点。
相应地，AN节点在接收到步骤302中的注册请求消息后，可以将该注册请求消息发送给核心网节点。
其中，步骤302可以周期地执行，具体地，以注册更新周期为周期执行步骤302，换言之，由注册更新定时器触发执行步骤302。该周期可以为中继设备的注册更新周期，或终端设备的注册更新周期，或根据中继设备的注册更新周期，终端设备的注册更新周期以及预设方法获得的周期，不予限制。
此外，步骤302也可以在步骤301的触发下执行，例如，在接收到注册信息后立即执行；还可以在中继设备发起注册流程时执行，即在执行中继设备的注册流程时同时实现终端设备的注册，不予限制。
其中，注册请求消息可以包含下面两种情况：
第一种情况：当中继模式信息对应的中继模式为长期中继模式时，该注册请求消息用于请求对中继设备和终端设备进行注册。
可选地，在上述第一种情况下，步骤302包括：当中继模式信息对应的中继模式为长期中继模式时，中继设备根据终端设备的注册信息生成该注册请求消息，并发送给AN节点。例如，该注册请求消息携带终端设备的标识信息和中继设备的标识信息。
在上述第一种情况下，注册请求消息可以包含中继设备注册的核心网节点的标识信息和终端设备注册的核心网节点的标识信息；或者，中继设备注册的核心网节点的标识信息和终端设备的标识信息；或者，终端设备注册的核心网节点的标识信息和中继设备的标识信息；或者，中继设备的标识信息和终端设备的标识信息；或者，中继设备注册的核心网节点的标识信息，终端设备注册的核心网节点的标识信息，中继设备的标识信息和终端设备的标识信息。
其中，中继设备注册的核心网节点的标识信息可以用于AN节点确定中继设备的目标核 心网节点。例如，当中继设备注册的核心网节点可用，且中继设备所处位置在该中继设备注册的核心网节点的服务范围内时，AN节点将中继设备注册的核心网节点作为中继设备的目标核心网节点；否则，AN节点可以选择为该中继设备所处位置提供服务的核心网节点作为该中继设备的目标核心网节点。进一步地，AN节点可以将注册请求消息发送给该目标核心网节点。
中继设备的标识信息和/或上述中继设备注册的核心网节点的标识信息可以包含在注册请求消息中。当然，中继设备也可以通过其他消息向AN节点发送中继设备的标识信息和/或上述中继设备注册的核心网节点的标识信息，在此不做限定。
具体地，中继设备可以将中继设备的标识信息以及中继设备注册的核心网节点的标识信息携带在RRC消息中，即与上述注册请求消息携带在同一个RRC中发送给AN节点。
上述RRC消息也可以不包含中继设备注册的核心网节点的标识信息，而是仅携带中继设备的标识信息(例如，中继设备的永久标识，或5G-GUTI)，此时，AN节点可根据该中继设备的标识获得该中继设备所处位置，进而根据该中继设备所处位置为该中继设备选择目标核心网节点。其中，如何选择目标核心网节点属于现有技术，不再赘述。
可选地，在上述第一种情况下，该注册请求消息包含注册类型和/或中继设备指示信息。其中，该注册类型可以用于指示该注册请求消息用于请求对中继设备和终端设备进行注册，或者，对至少两个设备进行注册。该中继设备指示信息可以用于指示多个设备中哪一个设备是中继设备。
在一种可能的实现方式中，注册请求消息包含该中继设备指示信息，属于显示指示方式。例如，注册请求消息包含终端设备的标识，中继设备的标识，以及中继设备指示信息。当中继设备指示信息设置为预设值(例如，1)时，表明位于消息前端的标识所对应的设备为中继设备。再例如，中继设备指示信息可以是中继设备的标识。
在另一种可能的实现方式中，可以采用隐式的方式指示中继设备，例如：通过终端设备的标识以及中继设备的标识在注册请求消息中的存放位置来识别中继设备。例如，可以将位于注册请求消息前端(更靠近注册请求消息的消息头)的位置存放中继设备的标识。
上述第一种情况通过注册请求消息同时实现中继设备和终端设备的注册操作，不需要分别对中继设备和终端设备进行注册操作，进一步节省注册流程导致的信令开销，大大节省了无线资源。
第二种情况：当中继模式信息所对应的中继模式为临时中继模式时，该注册请求消息用于请求为终端设备进行注册。
在这种情况下，该注册请求消息仅用于请求为终端设备进行注册，或者，该注册请求消息仅用于请求为至少一个终端设备进行注册。
具体的，当中继模式信息所对应的中继模式为临时中继模式，且注册信息是注册请求消息时，中继设备将从终端设备接收的注册请求消息发送给AN节点，或，中继设备根据终端设备发送的第一注册请求消息向AN节点发送第二注册请求消息。
例如，假设注册信息为注册消息，终端设备1和终端设备2均通过中继设备与AN节点通信，且终端设备1与中继设备之间的中继模式为临时中继模式，终端设备2与中继设备之间的中继模式为临时中继模式，中继设备在接收到终端设备1的第一注册请求消息和终端设备2发送的第二注册请求消息后，中继设备根据第一注册请求消息和第二注册请求消息生成第三注册请求消息，具体地，该第三注册请求消息可以携带终端设备1的标识信息和终端设 备2的标识信息，或者终端设备1注册的核心网节点的标识信息和终端设备2注册的核心网节点的标识信息，不予限制。
具体的，当中继模式信息所对应的中继模式为临时中继模式，且注册信息不是注册请求消息时，中继设备根据注册信息生成注册请求消息。
例如，假设注册信息为注册参数，终端设备1和终端设备2均通过中继设备与AN节点通信，且终端设备1与中继设备之间的中继模式为临时中继模式，终端设备2与中继设备之间的中继模式为临时中继模式，中继设备在接收到终端设备1和终端设备2发送的注册信息后，中继设备根据终端设备1和终端设备2发送的注册信息生成注册请求消息。具体地，该注册请求消息可以携带终端设备1和终端设备2发送的注册信息。即该注册请求消息用于请求对终端设备1和终端设备2进行注册，避免了每个终端设备独立进行注册流程而造成的信令开销大等问题。
可选地，中继设备还可以向AN节点发送终端设备的标识信息和/或终端设备注册的核心网节点的标识信息。
例如，终端设备的标识信息和/或终端设备注册的核心网节点的标识信息可以由中继设备通过解析终端设备发送的注册请求消息而获得。
终端设备注册的核心网节点的标识信息可以用于AN节点确定终端设备的目标核心网节点。例如，当终端设备注册的核心网节点可用，且终端设备位于该终端设备注册的核心网节点的服务范围内时，AN节点向终端设备注册的核心网节点发送注册请求消息；否则，AN节点选择为该终端设备所处位置提供服务的核心网节点作为该终端设备的目标核心网节点。进一步地，AN节点可以将注册请求消息发送给该目标核心网节点。
终端设备的标识信息可以用于AN节点获得该终端设备所处位置，并根据终端设备所处位置为该终端设备确定目标核心网节点。其中，如何选择目标核心网节点属于现有技术，不再赘述。
可选地，中继设备将终端设备的标识信息和/或终端设备注册的核心网节点的标识信息携带在同一个RRC消息发送给AN节点；或者，中继设备将终端设备的标识信息和/或终端设备注册的核心网节点的标识信息，以及上述注册请求消息携带在同一个RRC中发送给AN节点。
上述第二种情况能够实现至少一个终端设备通过中继设备完成其注册流程，不但避免了由于网络信号覆盖差等造成的注册失败问题，还实现了当多个终端设备通过一个中继设备进行注册时，可以更进一步的降低信令负荷，节省无线资源以及终端设备的电量。
本实施例提供的方法，中继设备接收来自终端设备的注册信息和终端设备的中继模式信息，并根据中继模式信息和注册信息，向AN节点发送注册请求消息，中继设备通过该注册请求消息能够发起一个或多个设备(例如，中继设备和终端设备，或至少两个终端设备)的注册流程，不但增加了终端设备注册的灵活性，还可以避免终端设备接入通信网络时造成的网络拥塞，例如，当注册请求消息用于请求对至少两个设备进行注册时，减少信令开销，节省无线资源。
可选地，在步骤302之后，还包括：中继设备接收注册接受消息。
其中，注册接受消息可以包含：
中继设备的注册区域信息和终端设备的注册区域信息，且中继设备的注册区域信息对应的注册区域与终端设备的注册区域信息对应的注册区域可以相同；和/或，
终端设备的注册更新定时器时长和中继设备的注册更新定时器时长，且终端设备的注册更新定时器时长与中继设备的注册更新定时器时长可以相同。
进一步地，还可以包括：中继设备向终端设备发送终端设备的注册区域信息和/或注册更新定时器时长。
具体地，中继设备可以直接向终端设备发送该注册接受消息，或者将终端设备的注册区域信息和/或注册更新定时器时长携带在其它消息中发送给终端设备，不予限制。
其中，注册区域，注册区域信息，注册更新定时器时长等均可以参见图2所示实施例中的相关描述，不再赘述。
如图4所示，本申请第三实施例提供的一种通信方法的示意图，具体如下所述。
401、AN节点接收来自中继设备的注册请求消息。
其中，注册请求消息可以用于请求对该中继设备和终端设备进行注册，该终端设备可以通过该中继设备与AN节点进行通信，该中继设备与该终端设备之间可以采用长期中继模式，参见图2中的相关描述，不再赘述。
该注册请求消息也可以用于请求对至少两个终端设备进行注册，该至少两个终端设备可以通过该中继设备与AN节点进行通信，该中继设备与该至少两个终端设备之间可以采用临时中继模式，参见图2中的相关描述，不再赘述。
下面分别针对注册请求消息的两种不同情况，对注册请求消息的内容进行说明：
第一种情况：注册请求消息用于请求对该中继设备和终端设备进行注册。
其中，该注册请求消息可以包含中继设备注册的核心网节点的标识信息和/或中继设备的标识信息；该注册请求消息还可以包含终端设备注册的核心网节点的标识信息和/或终端设备的标识信息。
可选地，该注册请求消息包含注册类型和/或中继设备指示信息；其中，中继设备指示信息用于指示该中继设备，可以参见图3所示实施例中的相关描述；注册类型用于指示对至少两个设备进行注册，例如，该注册类型具体用于指示对中继设备和终端设备进行注册。
第二种情况：注册请求消息用于请求对至少两个终端设备进行注册。
其中，该注册请求消息可以包含至少两个终端设备注册的核心网节点的标识信息和/或至少两个终端设备的标识信息；该注册请求消息也可以包含两个终端设备中部分设备注册的核心网节点的标识信息，以及两个终端设备中剩余部分设备的标识信息。
可选地，该注册请求消息包含注册类型；注册类型用于指示对至少两个设备进行注册，例如，该注册类型具体用于指示对至少两个终端设备进行注册。
402、AN节点向核心网节点发送注册请求消息。
针对步骤401中的第一种情况，核心网节点可以为中继设备对应的核心网节点。
具体的，AN节点可以从中继设备接收该中继设备的标识信息和/或该中继设备注册的核心网节点的标识信息，也可以通过解析注册请求消息获得该中继设备的标识信息和/或该中继设备注册的核心网节点的标识信息，然后根据中继设备的标识信息和/或该中继设备注册的核心网节点的标识信息确定中继设备对应的核心网节点，可以参见图3所示实施例中的相关描述，不再赘述。
针对步骤401中的第二种情况，核心网节点可以为至少两个终端设备中任一终端设备对应的核心网节点，可以参见图3所示实施例中的相关描述，不再赘述。
具体地，AN节点可以从中继设备接收该终端设备的标识信息和/或该终端设备注册的核心网节点的标识信息，也可以通过解析注册请求消息获得该终端设备的标识信息和/或该终端设备注册的核心网节点的标识信息，然后根据终端设备的标识信息和/或该终端设备注册的核心网节点的标识信息确定终端设备对应的核心网节点，可以参见图3所示实施例中的相关描述，不再赘述。
本实施例提供的方法，AN节点接收来自中继设备的注册请求消息，该注册请求消息用于请求对多个设备(例如，中继设备和终端设备，或，至少两个终端设备)进行注册；AN节点向核心网节点发送该注册请求消息，不但增加了终端设备注册的灵活性，还可以避免终端设备接入通信网络时造成的网络拥塞，例如，当注册请求消息用于请求对至少两个设备进行注册时，减少信令开销，节省无线资源。
如图5所示，本申请第四实施例提供的一种通信方法的示意图，具体如下所述。
501、核心网节点接收来自AN节点的注册请求消息。
其中，注册请求消息用于请求对中继设备和终端设备进行注册。该终端设备可以通过该中继设备与AN节点进行通信，该中继设备与该终端设备之间可以采用长期中继模式，参见图2中的相关描述，不再赘述。
其中，该注册请求消息可以携带注册类型和/或中继指示信息，该中继指示信息可以用于核心网节点在寻呼消息中同时携带该终端设备和该中继设备的标识信息，以更加准确地对终端设备进行寻呼，具体可以参见图3所示实施例中的相关描述，不再赘述。
其中，核心网节点可以参见图3所示实施例中中继设备的目标核心网节点的相关描述，不再赘述。
502、核心网节点根据注册请求消息，对中继设备和终端设备进行注册。
具体的，当注册请求消息包括注册类型时，步骤502可以包括：核心网节点根据注册类型，对注册请求消息进行校验；当注册请求消息校验失败时，核心网节点向中继设备发送注册拒绝消息；当注册请求消息校验成功时，执行步骤503。
在一个示例中，当注册类型指示上述注册请求消息用于请求对终端设备和中继设备进行注册时，若注册请求消息携带中继设备注册的核心网节点的标识信息和/或中继设备的标识信息，且该注册请求消息还携带终端设备注册的核心网节点的标识信息和/或终端设备的标识信息，则注册请求消息检验成功；否则，注册请求消息校验失败。
在另一个示例中，当注册类型指示上述注册请求消息用于请求对一个设备进行注册时，若注册请求消息携带中继设备的标识信息和终端设备的标识信息，则注册请求消息校验失败。
503、核心网节点向中继设备发送注册接受消息。
其中，注册接受消息可以包含：
中继设备的注册区域信息和终端设备的注册区域信息，其中，该中继设备的注册区域信息对应的注册区域与该终端设备的注册区域信息对应的注册区域可以相同；或者，
终端设备的注册更新定时器时长和中继设备的注册更新定时器时长，其中，该终端设备的注册更新定时器时长与该中继设备的注册更新定时器时长可以相同。
其中，注册区域信息，注册区域，注册更新定时器时长等均可以参见上述图2或3所示实施例中的相关描述，不再赘述。
需要指出的是，当该核心网节点与终端设备注册的核心网节点不同时，该核心网节点还可以从终端设备注册的核心网节点获取该终端设备的上下文信息。
具体的，核心网节点向终端设备注册的核心网节点发送信息请求(information request)消息，该information request消息携带该终端设备的标识；相应地，终端设备注册的核心网节点向该目标核心网节点发送信息响应(information response)消息，该information response消息携带该终端设备的上下文信息，目标核心网节点接收information response消息，从而获得该终端设备的上下文信息。
其中，上下文信息可以为现有技术中的UE context，也可以是UE context中的部分信息，不予限制。
当该核心网节点与中继设备注册的核心网节点不同时，该核心网节点还可以从中继设备注册的核心网节点获取该中继设备的上下文信息。具体的，核心网节点获取该中继设备的上下文信息可以采用上述获取终端设备的上下文信息的方式，不再赘述。
本实施例提供的方法，核心网节点接收来自AN节点的注册请求消息，该注册请求消息用于请求对中继设备和终端设备进行注册；核心网节点根据注册请求消息对中继设备和终端设备进行注册，不但增加了终端设备注册的灵活性，还可以避免终端设备接入通信网络时造成的网络拥塞，例如，当注册请求消息用于请求对至少两个设备进行注册时，减少信令开销，节省无线资源。
如图6所示，本申请第五实施例提供的一种通信方法的示意图，具体如下所述。
601、核心网节点接收来自AN节点的注册请求消息。
其中，注册请求消息用于请求对至少两个终端设备进行注册。该注册请求消息可以携带注册类型，可以参见图3所示实施例中的相关描述，不再赘述。
其中，核心网节点可以参见图3所示实施例中终端设备的目标核心网节点的相关描述，不再赘述。
602、核心网节点根据注册请求消息，对至少两个终端设备进行注册。
具体的，当注册请求消息包括注册类型时，步骤602可以包括：核心网节点根据注册类型，对注册请求消息进行校验；当注册请求消息校验失败时，核心网节点向中继设备发送注册拒绝消息；当注册请求消息校验成功时，执行步骤603，其实现与步骤502类似，不再赘述。
603、核心网节点向中继设备发送注册接受消息。
其中，该至少两个终端设备可以通过该中继设备与AN节点进行通信，该至少终端设备与该中继设备之间可以采用临时中继模式，参见图2中的相关描述，不再赘述。
其中，注册接受消息可以包含：
至少两个终端设备的注册区域信息，其中，该至少两个终端设备的注册区域信息对应的注册区域可以相同；或者，
至少两个终端设备的注册更新定时器时长，其中，该至少两个终端设备的注册更新定时器时长可以相同。
其中，注册区域信息，注册区域，注册更新定时器时长等均可以参见上述图2或3所示实施例中的相关描述，不再赘述。
进一步地，中继设备在接收到注册接受消息后，可以分别将该注册接受消息发送给该至 少两个终端设备，也可以将注册接受消息中携带的部分内容发送给终端设备，不予限制。
需要指出的是，当该核心网节点与该至少终端设备中任一终端设备注册的核心网节点不同时，该核心网节点还可以从该任一终端设备注册的核心网节点获取该任一终端设备的上下文信息。上下文信息可以参见图5所示实施例中的相关描述，不再赘述。
本实施例提供的方法，核心网节点接收来自AN节点的注册请求消息，该注册请求消息用于请求对对至少两个终端设备进行注册；核心网节点根据注册请求消息对至少两个终端设备进行注册，不但增加了终端设备注册的灵活性，还可以避免终端设备接入通信网络时造成的网络拥塞，例如，当注册请求消息用于请求对至少两个设备进行注册时，减少信令开销，节省无线资源。
如图7所示，本申请第六实施例提供的一种通信方法的流程图，该方法以5G系统为例，具体如下所述。
701、终端设备向中继设备发送D2D消息。
其中，D2D消息携带有注册请求消息和中继模式信息，还可以携带有终端设备注册的AMF节点的标识信息。
其中，该注册请求消息用于请求对终端设备进行注册，该注册请求消息可以携带有终端设备的标识信息。
702、当中继模式信息对应的中继模式为临时中继模式时，中继设备向AN节点发送RRC消息。
其中，该RRC消息携带上述注册请求消息，还可以携带终端设备注册的AMF节点的标识信息。
703、AN节点向终端设备的目标AMF节点发送注册请求消息。
其中，目标AMF节点可以由AN节点根据终端设备的标识信息或终端设备注册的AMF节点的标识信息来确定，具体可以参见图3所示实施例中终端设备的目标核心网节点的相关描述，不再赘述。
其中，当终端设备的目标AMF节点为终端设备注册的AMF节点时，可以不执行步骤704-706。
704、目标AMF节点向终端设备注册的AMF节点发送UE上下文请求。
705、终端设备注册的AMF节点向目标AMF节点发送UE上下文响应。
其中，UE上下文响应携带终端设备的上下文信息，上下文信息可以参见图5所示实施例中的相关描述，不再赘述。
706、目标AMF节点从UDM获取终端设备的签约信息。
其中，签约信息属于现有技术，不再赘述。
707、目标AMF节点分配终端设备的标识信息。
其中，该标识信息可以是终端设备的临时标识，例如，5G-GUTI，5G-TMSI，可以参见图2所示实施例中的相关描述，不再赘述。
708、目标AMF节点分配终端设备的移动性管理(mobility management，MM)参数。
其中，该MM参数可以包括注册区域和/或注册更新定时器时长。
需要说明的是，步骤707和步骤708均为可选步骤。例如，在终端设备的目标AMF节点不是终端设备注册的AMF节点的情况下，可以执行步骤707和708。再例如，在终端设 备的目标AMF节点是终端设备注册的AMF节点的情况下，若达到终端设备的临时标识的失效时间，则可以执行步骤707；或者，若达到注册区域的失效时间，则可以执行步骤708，以分配终端设备的注册区域。
709、目标AMF节点向中继设备发送注册接受消息。
其中，注册接受消息可以携带步骤707中分配的标识信息或步骤708中分配的MM参数。
710、中继设备向终端设备发送D2D消息。
其中，该D2D消息携带有上述注册接受消息。
需要指出的是，步骤704-708之间的执行先后顺序可以互换，不予限制。此外，中继模式信息，中继模式，临时中继模式，以及标识信息等均可以参见上述方法实施例，不再赘述。
本实施例提供的方法，终端设备向中继设备发送注册请求消息和终端设备的中继模式信息，当中继模式信息对应的中继模式为临时中继模式时，中继设备向AN节点发送该注册请求消息，进而AN节点向目标AMF节点发送该注册请求消息，该方法中继设备基于终端设备的中继模式发送注册请求消息，不但增加了终端设备注册的灵活性，还可以避免终端设备接入通信网络时造成的网络拥塞。例如，当多个终端设备通过一个中继设备进行注册时，可以更进一步的降低信令负荷。
如图8所示，本申请第七实施例提供的一种通信方法的流程图，该方法以5G系统为例，具体如下所述。
801、终端设备向中继设备发送D2D消息。
其中，D2D消息携带有注册信息和中继模式信息。
802、当中继模式信息对应的中继模式为长期中继模式时，中继设备根据注册信息向AN节点发送RRC消息。
其中，RRC消息携带有注册请求消息，还可以携带有中继设备注册的AMF节点的标识信息。
其中，该注册请求消息用于请求对终端设备和中继设备进行注册，该注册请求消息可以携带有终端设备的标识信息和中继设备的标识信息。
803、AN节点向目标AMF节点发送注册请求消息。
其中，目标AMF节点可以由AN节点根据中继设备的标识信息或中继设备注册的AMF节点的标识信息来确定，具体可以参见图3所示实施例中中继设备的目标核心网节点的相关描述，不再赘述。
其中，当目标AMF节点为终端设备注册的AMF节点时，可以不执行步骤804-806。
当目标AMF节点为中继设备注册的AMF节点时，可以不执行步骤807-809。
804、目标AMF节点向终端设备注册的AMF节点发送第一UE上下文请求。
805、终端设备注册的AMF节点向目标AMF节点发送第一UE上下文响应。
其中，第一UE上下文响应携带有终端设备的上下文信息。
806、目标AMF节点从UDM获取终端设备的签约信息。
807、目标AMF节点向中继设备注册的AMF节点发送第二UE上下文请求。
808、中继设备注册的AMF节点向目标AMF节点发送第二UE上下文响应。
其中，第二UE上下文响应携带中继设备的上下文信息。
809、目标AMF节点从UDM获取中继设备的签约信息。
需要指出的是，当目标AMF节点不是终端设备注册的AMF节点，也不是中继设备注册的AMF节点时，步骤806和809可以同时执行，即目标AMF节点通过同一条消息或服务化接口信息，从UDM中获取中继设备的签约信息和终端设备的签约信息。
810、目标AMF节点分配终端设备的标识信息，以及中继设备的标识信息。
其中，终端设备的标识信息可以为终端设备的临时标识，中继设备的标识信息可以为中继设备的临时标识，可以参见图2所实施例中的相关描述，不再赘述。
811、目标AMF节点分配终端设备的MM参数。
其中，MM参数可以包括注册区域和/或注册更新定时器时长。
812、目标AMF节点分配中继设备的MM参数。
其中，终端设备的MM参数和中继设备的MM参数可以相同，例如，该中继设备的注册区域与该终端设备的注册区域可以相同；该终端设备的注册更新定时器时长与该中继设备的注册更新定时器时长也可以相同。
需要指出的是，步骤810-812均为可选步骤，例如，在终端设备的目标AMF节点不是终端设备注册的AMF节点的情况下，执行步骤810中分配终端设备的标识信息，以及步骤811。在中继设备的目标AMF节点不是中继设备注册的AMF节点的情况下，执行步骤810中分配中继设备的标识信息，以及步骤812。
再例如，在终端设备的目标AMF节点是终端设备注册的AMF节点的情况下，若达到终端设备的临时标识的失效时间，则执行步骤810中分配终端设备的标识信息；或者，若达到注册区域的失效时间，则执行步骤811，以分配终端设备的注册区域。
此外，步骤811和812可以同时执行，即为终端设备和中继设备分配相同的MM参数。
813、目标AMF节点向中继设备发送注册接受消息。
其中，注册接受消息可以携带有步骤810中分配的终端设备的标识信息或步骤811中分配的终端设备的MM参数；还可以携带有步骤810中分配的中继设备的标识信息和步骤812中分配的中继设备的MM参数。
814、中继设备向终端设备发送D2D消息。
其中，该D2D消息可以包含注册接受消息所携带的终端设备的相关信息，例如，终端设备的标识信息，或，终端设备的MM参数；也可以包含该注册接受消息。
需要指出的是，上述步骤804-812之间的执行顺序可以互换，不予限制。
此外，注册信息，中继模式信息，长期中继模式，注册区域，注册更新定时器时长，以及标识信息等均可以参见上述各方法实施例，不再赘述。
本实施例提供的方法，终端设备向中继设备发送注册信息和终端设备的中继模式信息，当中继模式信息对应的中继模式为长期中继模式时，中继设备向AN节点发送注册请求消息，该注册请求消息用于请求对终端设备和中继设备进行注册，进而AN节点向目标AMF节点发送该注册请求消息，不但增加了终端设备注册的灵活性，还可以避免终端设备接入通信网络时造成的网络拥塞，例如，通过一条注册请求发起终端设备和中继设备的注册流程，减少了信令开销，节省了无线资源。
如图9所示，本申请第八实施例提供了一种通信装置900的示意图，可以用于执行上述方法实施例中终端设备的步骤。通信装置900可以为终端设备或终端设备内的芯片或片上系 统。通信装置900包括处理单元901和收发单元902。
处理单元901，用于获取终端设备的中继模式。
收发单元902，用于向中继设备发送注册信息和所述终端设备的中继模式信息。
可选地，所述注册信息包括所述终端设备的标识信息和/或所述终端设备注册的核心网节点的标识信息；或，所述注册信息为注册请求消息。
可选地，处理单元901还用于：
根据所述终端设备的空闲态驻留方式，获得所述终端设备的中继模式；或，
根据预先配置的关联关系，获得所述终端设备的中继模式；或，
根据所述终端设备的位置，获得所述终端设备的中继模式。
可选地，处理单元901还用于：
若所述终端设备在空闲态时驻留在非直传链路，则所述终端设备的中继模式为长期中继模式；或者，
若所述终端设备在空闲态时驻留在直传链路，则所述终端设备的中继模式为临时中继模式。
可选地，处理单元901还用于：
当所述终端设备位于预设区域范围之内时，所述终端设备的中继模式为长期中继模式；或者，
当所述终端设备位于预设区域范围之外时，所述终端设备的中继模式为临时中继模式。
可选地，收发单元902还用于：
接收来自所述中继设备的所述终端设备的注册区域信息和/或注册更新定时器时长。
其中，所述终端设备的注册区域信息对应的注册区域与所述中继设备的注册区域可以相同；所述终端设备的注册更新定时器时长与所述中继设备的注册更新定时器时长可以相同。
需要指出的是，上述单元既可以采用硬件的形式实现，例如，处理单元901可以为至少一个处理器，收发单元902可以为收发器或通信接口；也可以采用软件功能模块的形式实现。
本实施例提供的装置，通过获得终端设备的中继模式，并向中继设备发送注册信息和终端设备的中继模式信息，使得中继设备能够基于该终端设备的中继模式信息和注册信息向AN节点发送注册请求消息，不但增加了终端设备注册的灵活性，还可以避免终端设备接入通信网络时造成的网络拥塞。
如图10所示，本申请第九实施例提供了一种通信装置1000的示意图，可以用于执行上述方法实施例中中继设备的步骤。通信装置1000可以为中继设备或中继设备内的芯片或片上系统。具体地，通信装置1000包括：收发单元1001和处理单元1002。
收发单元1001，用于接收来自终端设备的注册信息和所述终端设备的中继模式信息。
处理单元1002，用于根据所述中继模式信息和所述注册信息，向接入网AN节点发送注册请求消息。
可选地，所述注册信息包括所述终端设备的标识信息和/或所述终端设备注册的核心网节点的标识信息；或，所述注册信息为注册请求消息。
可选地，当所述中继模式信息对应的中继模式为长期中继模式时，所述注册请求消息用于请求对中继设备和所述终端设备进行注册。
进一步可选地，所述注册请求消息包含所述中继设备注册的核心网节点的标识信息和/ 或所述中继设备的标识信息；所述注册请求消息还包含所述终端设备注册的核心网节点的标识信息和/或所述终端设备的标识信息。
进一步可选地，收发单元1001还用于：向所述AN节点发送所述中继设备的标识信息和/或所述中继设备注册的核心网节点的标识信息。
进一步可选地，所述注册请求消息包含注册类型和/或中继设备指示信息；
其中，所述中继设备指示信息用于指示所述中继设备；所述注册类型用于指示对至少两个设备进行注册。
进一步可选地，收发单元1001还用于：
接收注册接受消息，所述注册接受消息包含：
所述中继设备的注册区域信息和所述终端设备的注册区域信息，且所述中继设备的注册区域信息对应的注册区域与所述终端设备的注册区域信息对应的注册区域相同；和/或，
所述终端设备的注册更新定时器时长和所述中继设备的注册更新定时器时长，且所述终端设备的注册更新定时器时长与所述中继设备的注册更新定时器时长相同。
可选地，当所述中继模式信息对应的中继模式为临时中继模式时，所述注册请求消息用于请求对所述终端设备进行注册。
进一步可选地，收发单元1001还用于：向所述AN节点发送所述终端设备的标识信息和/或所述终端设备注册的核心网节点的标识信息。
需要指出的是，上述单元既可以采用硬件的形式实现，例如，处理单元1002可以为至少一个处理器，收发单元1001可以为收发器，或通信接口；也可以采用软件功能模块的形式实现。
本实施例提供的装置，通过接收来自终端设备的注册信息和终端设备的中继模式信息，并根据中继模式信息和注册信息，向AN节点发送注册请求消息，该注册请求消息可以用于请求对一个或多个设备(例如，中继设备和终端设备，或至少两个终端设备)进行注册，不但增加了终端设备注册的灵活性，还可以避免终端设备接入通信网络时造成的网络拥塞，例如，当注册请求消息用于请求对至少两个设备进行注册时，减少信令开销，节省无线资源。
如图11所示，本申请第十实施例提供了一种通信装置1100的示意图，可以用于执行上述各方法实施中AN节点的步骤。通信装置1100可以为AN节点或AN节点内的芯片或片上系统。具体，通信装置1100包括接收单元1101和发送单元1102。
接收单元1101，用于接收来自中继设备的注册请求消息，所述注册请求消息用于请求对至少两个设备进行注册。
其中，该至少两个设备可以包括中继设备和终端设备，终端设备可以通过中继设备与AN节点通信；该至少两个设备还可以为至少两个终端设备，该至少两个终端设备通过一个中继设备与AN节点，通信中继设备与该至少两个终端设备之间可以采用临时中继模式，参见图2中的相关描述，不再赘述。
发送单元1102，用于向所述中继设备的对应的核心网节点发送所述注册请求消息。
可选地，所述注册请求消息包含所述中继设备注册的核心网节点的标识信息和/或所述中继设备的标识信息，还包含所述终端设备注册的核心网节点的标识信息和/或所述终端设备的标识信息。
可选地，所述注册请求消息包含注册类型和/或中继设备指示信息；其中，所述中继设 备指示信息用于指示所述中继设备；所述注册类型用于指示对至少两个设备进行注册。
需要指出的是，上述单元既可以采用硬件的形式实现，例如，接收单元1101可以为收发器，发送单元1102可以为通信接口；也可以采用软件功能模块的形式实现。
本实施例提供的装置，通过接收来自中继设备的注册请求消息，该注册请求消息用于请求对中继设备和终端设备进行注册，或，该注册请求消息用于请求对至少两个终端设备进行注册；向核心网节点发送该注册请求消息，不但增加了终端设备注册的灵活性，还可以避免终端设备接入通信网络时造成的网络拥塞，例如，当注册请求消息用于请求对至少两个设备进行注册时，减少信令开销，节省无线资源。
如图12所示，本申请第十一实施例提供了一种通信装置1200的示意图，可以用于执行上述各方法实施例中核心网节点，目标核心网节点或目标AMF节点执行的步骤。通信装置1200可以为核心网节点，例如，AMF节点或MME，或核心网节点内的芯片或片上系统。具体地，通信装置1200可以包括：收发单元1201和处理单元1202
收发单元1201，用于接收来自AN节点的注册请求消息，所述注册请求消息用于请求对至少两个设备进行注册。
其中，该至少两个设备可以包括中继设备和终端设备，终端设备可以通过中继设备与AN节点通信。该至少两个设备还可以为至少两个终端设备，该至少两个终端设备通过一个中继设备与AN节点，通信中继设备与该至少两个终端设备之间可以采用临时中继模式，参见图2中的相关描述，不再赘述。
处理单元1202，用于根据所述注册请求消息，对所述中继设备和所述终端设备进行注册。
收发单元1201，还用于向所述中继设备发送注册接受消息。
可选地，所述注册请求消息包含所述中继设备注册的核心网节点的标识信息和/或所述中继设备的标识信息，还包含所述终端设备注册的核心网节点的标识信息和/或所述终端设备的标识信息。
可选地，收发单元1201还用于：
从所述终端设备注册的核心网节点获取所述终端设备的上下文信息；和/或，
从所述中继设备注册的核心网节点获取所述中继设备的上下文信息。
可选地，所述注册接受消息包含：
所述中继设备的注册区域信息和所述终端设备的注册区域信息，且所述中继设备的注册区域信息对应的注册区域与所述终端设备的注册区域信息对应的注册区域相同；和/或，
所述终端设备的注册更新定时器时长和所述中继设备的注册更新定时器时长，且所述终端设备的注册更新定时器时长与所述中继设备的注册更新定时器时长相同。
可选地，所述注册请求消息还包含注册类型和/或中继设备指示信息；其中，所述中继设备指示信息用于指示所述中继设备；所述注册类型用于指示对至少两个设备进行注册。
需要指出的是，上述单元既可以采用硬件的形式实现，例如，处理单元1202可以为可以为至少一个处理器，收发单元1201可以为收发器，或通信接口；也可以采用软件功能模块的形式实现。
本实施例提供的装置，通过接收来自AN节点的注册请求消息，该注册请求消息用于请求对中继设备和终端设备进行注册；根据注册请求消息对中继设备和终端设备进行注册，不 但增加了终端设备注册的灵活性，还可以避免终端设备接入通信网络时造成的网络拥塞，例如，当注册请求消息用于请求对至少两个设备进行注册时，减少信令开销，节省无线资源。
如图13所示，本申请第十二实施例提供了一种通信装置1300的示意图，包括至少一个处理器1301和存储器1302，还可以包括通信总线1303，以及至少一个通信接口1304。该装置1300可以是本申请实施例中的任何一个设备，该装置1300可用于执行本申请实施例提供的方法。
处理器1301，可以是一个通用中央处理器(CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
存储器1302，可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由该装置存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
通信总线1303，可包括一通路，在上述组件之间传送信息。
通信接口1304，可使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(RAN)，WALN等。
其中，存储器1303用于存储程序代码，处理器1301用于执行存储器1302中存储的程序代码。
示例性地，处理器1301可以包括一个或多个CPU，例如图13中的CPU0和CPU1。
示例性地，装置1300可以包括多个处理器，例如，图13中的处理器1301和处理器1305。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
示例性的，图13所示的装置可以为终端设备或终端设备的组成部分，图13所示的装置的存储器中存储了一个或多个软件模块。图13所示的装置可以通过处理器执行存储器中的程序代码来实现本申请各实施例中由终端设备执行的步骤。
示例性的，图13所示的装置可以为中继设备或中继设备的组成部分，图13所示的装置的存储器中存储了一个或多个软件模块。图13所示的装置可以通过处理器执行存储器中的程序代码来实现本申请各实施例中由中继设备执行的步骤。
示例性的，图13所示的装置可以为AN节点或AN节点的组成部分，图13所示的装置的存储器中存储了一个或多个软件模块。图13所示的装置可以通过处理器执行存储器中的程序代码来实现本申请各实施例中由AN节点执行的步骤。
示例性的，图13所示的装置可以为核心网节点或核心网节点的组成部分，图13所示的装置的存储器中存储了一个或多个软件模块。图13所示的装置可以通过处理器执行存储器中的程序代码来实现本申请各实施例中由核心网节点或目标AMF节点执行的步骤。
本申请实施例还提供了一种计算机存储介质，储存有程序代码，该程序在被处理器执行时可以用于执行上述各方法实施例中终端设备的步骤。
本申请实施例还提供了一种计算机存储介质，储存有程序代码，该程序在被处理器执行时可以用于执行上述各方法实施例中中继设备的步骤。
本申请实施例还提供了一种计算机存储介质，储存有程序代码，该程序在被处理器执行时可以用于执行上述各方法实施例中AN节点的步骤。
本申请实施例还提供了一种计算机存储介质，储存有程序代码，该程序在被处理器执行时可以用于执行上述各方法实施例中核心网节点或目标AMF节点的步骤。
本申请实施例还提供了一种计算机程序产品。该计算机程序产品包括计算机软件指令，该计算机软件指令可通过处理器执行，以实现上述各方法实施例中终端设备的方法。
本申请实施例还提供了一种计算机程序产品。该计算机程序产品包括计算机软件指令，该计算机软件指令可通过处理器执行，以实现上述各方法实施例中中继设备的方法。
本申请实施例还提供了一种计算机程序产品。该计算机程序产品包括计算机软件指令，该计算机软件指令可通过处理器执行，以实现上述各方法实施例中AN节点的方法。
本申请实施例还提供了一种计算机程序产品。该计算机程序产品包括计算机软件指令，该计算机软件指令可通过处理器执行，以实现上述各方法实施例中核心网节点或目标AMF节点的方法。
本申请实施例还提供了一种通信系统，包含图9-12所示的通信装置。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。

Claims (30)

  1. 一种通信方法，其特征在于，所述方法包括：
    终端设备获得所述终端设备的中继模式；
    所述终端设备向中继设备发送注册信息和所述终端设备的中继模式信息。
  2. 根据权利要求1所述的方法，其特征在于，
    所述注册信息包括所述终端设备的标识信息和/或所述终端设备注册的核心网节点的标识信息；或，
    所述注册信息为注册请求消息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述终端设备获得所述终端设备的中继模式，包括：
    所述终端设备根据所述终端设备的空闲态驻留方式，获得所述终端设备的中继模式；或，所述终端设备根据预先配置的关联关系，获得所述终端设备的中继模式；或，
    所述终端设备根据所述终端设备的位置，获得所述终端设备的中继模式。
  4. 根据权利要求3所述的方法，其特征在于，所述终端设备根据所述终端设备的空闲态驻留方式，获得所述终端设备的中继模式，包括：
    若所述终端设备在空闲态时驻留在非直传链路，则所述终端设备的中继模式为长期中继模式；或者，
    若所述终端设备在空闲态时驻留在直传链路，则所述终端设备的中继模式为临时中继模式。
  5. 根据权利要求3所述的方法，其特征在于，所述终端设备根据所述终端设备的位置，获得所述终端设备的中继模式，包括：
    当所述终端设备位于预设区域范围之内时，所述终端设备的中继模式为长期中继模式；或者，
    当所述终端设备位于预设区域范围之外时，所述终端设备的中继模式为临时中继模式。
  6. 根据权利要求1-5中任意一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收来自所述中继设备的所述终端设备的注册区域信息和/或注册更新定时器时长；
    其中，所述终端设备的注册区域信息对应的注册区域与所述中继设备的注册区域相同；所述终端设备的注册更新定时器时长与所述中继设备的注册更新定时器时长相同。
  7. 一种通信方法，其特征在于，所述方法包括：
    中继设备接收来自终端设备的注册信息和所述终端设备的中继模式信息；
    所述中继设备根据所述中继模式信息和所述注册信息，向接入网AN节点发送注册请求 消息。
  8. 根据权利要求7所述的方法，其特征在于，
    所述注册信息包括所述终端设备的标识信息和/或所述终端设备注册的核心网节点的标识信息；或，
    所述注册信息为注册请求消息。
  9. 根据权利要求7或8所述的方法，其特征在于，当所述中继模式信息对应的中继模式为长期中继模式时，所述注册请求消息用于请求对所述中继设备和所述终端设备进行注册。
  10. 根据权利要求9所述的方法，其特征在于，所述注册请求消息包含所述中继设备注册的核心网节点的标识信息和/或所述中继设备的标识信息；
    所述注册请求消息还包含所述终端设备注册的核心网节点的标识信息和/或所述终端设备的标识信息。
  11. 根据权利要求9或10所述的方法，其特征在于，所述方法还包括：
    所述中继设备向所述AN节点发送所述中继设备的标识信息和/或所述中继设备注册的核心网节点的标识信息。
  12. 根据权利要求9-11任一项所述的方法，其特征在于，所述注册请求消息包含注册类型和/或中继设备指示信息；
    其中，所述中继设备指示信息用于指示所述中继设备；所述注册类型用于指示对至少两个设备进行注册。
  13. 根据权利要求9-12中任意一项所述的方法，其特征在于，所述方法还包括：
    所述中继设备接收注册接受消息，所述注册接受消息包含：
    所述中继设备的注册区域信息和所述终端设备的注册区域信息，且所述中继设备的注册区域信息对应的注册区域与所述终端设备的注册区域信息对应的注册区域相同；或者，
    所述终端设备的注册更新定时器时长和所述中继设备的注册更新定时器时长，且所述终端设备的注册更新定时器时长与所述中继设备的注册更新定时器时长相同。
  14. 根据权利要求7或8所述的方法，其特征在于，当所述中继模式信息对应的中继模式为临时中继模式时，所述注册请求消息用于请求对所述终端设备进行注册。
  15. 根据权利要求14所述的方法，其特征在于，所述方法还包括：
    所述中继设备向所述AN节点发送所述终端设备的标识信息和/或所述终端设备注册的核心网节点的标识信息。
  16. 一种通信装置，其特征在于，包括：
    处理单元，用于获取终端设备的中继模式；
    收发单元，用于向中继设备发送注册信息和所述终端设备的中继模式信息。
  17. 根据权利要求16所述的通信装置，其特征在于，
    所述注册信息包括所述终端设备的标识信息和/或所述终端设备注册的核心网节点的标识信息；或，
    所述注册信息为注册请求消息。
  18. 根据权利要求16或17所述的通信装置，其特征在于，所述处理单元还用于：
    根据所述终端设备的空闲态驻留方式，获得所述终端设备的中继模式；或，
    根据预先配置的关联关系，获得所述终端设备的中继模式；或，
    根据所述终端设备的位置，获得所述终端设备的中继模式。
  19. 根据权利要求18所述的通信装置，其特征在于，所述处理单元还用于：
    若所述终端设备在空闲态时驻留在非直传链路，则所述终端设备的中继模式为长期中继模式；或者，
    若所述终端设备在空闲态时驻留在直传链路，则所述终端设备的中继模式为临时中继模式。
  20. 根据权利要求18所述的通信装置，其特征在于，所述处理单元还用于：
    当所述终端设备位于预设区域范围之内时，所述终端设备的中继模式为长期中继模式；或者，
    当所述终端设备位于预设区域范围之外时，所述终端设备的中继模式为临时中继模式。
  21. 根据权利要求16-20中任意一项所述的通信装置，其特征在于，所述收发单元还用于：
    接收来自所述中继设备的所述终端设备的注册区域信息和/或注册更新定时器时长；
    其中，所述终端设备的注册区域信息对应的注册区域与所述中继设备的注册区域相同；所述终端设备的注册更新定时器时长与所述中继设备的注册更新定时器时长相同。
  22. 一种通信装置，其特征在于，包括：
    收发单元，用于接收来自终端设备的注册信息和所述终端设备的中继模式信息；
    处理单元，用于根据所述中继模式信息和所述注册信息，向接入网AN节点发送注册请求消息。
  23. 根据权利要求22所述的通信装置，其特征在于，
    所述注册信息包括所述终端设备的标识信息和/或所述终端设备注册的核心网节点的标识信息；或，
    所述注册信息为注册请求消息。
  24. 根据权利要求22或23所述的通信装置，其特征在于，当所述中继模式信息对应的中继模式为长期中继模式时，所述注册请求消息用于请求对中继设备和所述终端设备进行注 册。
  25. 根据权利要求24所述的通信装置，其特征在于，所述注册请求消息包含所述中继设备注册的核心网节点的标识信息和/或所述中继设备的标识信息；
    所述注册请求消息还包含所述终端设备注册的核心网节点的标识信息和/或所述终端设备的标识信息。
  26. 根据权利要求24或25所述的通信装置，其特征在于，所述收发单元还用于：
    向所述AN节点发送所述中继设备的标识信息和/或所述中继设备注册的核心网节点的标识信息。
  27. 根据权利要求24-26任一项所述的通信装置，其特征在于，所述注册请求消息包含注册类型和/或中继设备指示信息；
    其中，所述中继设备指示信息用于指示所述中继设备；所述注册类型用于指示对至少两个设备进行注册。
  28. 根据权利要求24-27中任意一项所述的通信装置，其特征在于，所述收发单元还用于：
    接收注册接受消息，所述注册接受消息包含：
    所述中继设备的注册区域消息和所述终端设备的注册区域信息，且所述中继设备的注册区域信息对应的注册区域与所述终端设备的注册区域信息对应的注册区域相同；或者，
    所述终端设备的注册更新定时器时长和所述中继设备的注册更新定时器时长，且所述终端设备的注册更新定时器时长与所述中继设备的注册更新定时器时长相同。
  29. 根据权利要求22或23所述的通信装置，其特征在于，当所述中继模式信息对应的中继模式为临时中继模式时，所述注册请求消息用于请求对所述终端设备进行注册。
  30. 根据权利要求29所述的通信装置，其特征在于，所述收发单元还用于：
    向所述AN节点发送所述终端设备的标识信息和/或所述终端设备注册的核心网节点的标识信息。
PCT/CN2018/112883 2017-11-13 2018-10-31 通信方法和装置 WO2019091307A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18877235.4A EP3687259B1 (en) 2017-11-13 2018-10-31 Communication method and device
US15/930,449 US20200275258A1 (en) 2017-11-13 2020-05-13 Communications method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711113391.8A CN109788507B (zh) 2017-11-13 2017-11-13 通信方法和装置
CN201711113391.8 2017-11-13

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/930,449 Continuation US20200275258A1 (en) 2017-11-13 2020-05-13 Communications method and apparatus

Publications (1)

Publication Number Publication Date
WO2019091307A1 true WO2019091307A1 (zh) 2019-05-16

Family

ID=66438243

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/112883 WO2019091307A1 (zh) 2017-11-13 2018-10-31 通信方法和装置

Country Status (4)

Country Link
US (1) US20200275258A1 (zh)
EP (1) EP3687259B1 (zh)
CN (1) CN109788507B (zh)
WO (1) WO2019091307A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110445882A (zh) * 2019-09-19 2019-11-12 腾讯科技（深圳）有限公司 通信连接方法、装置、计算机设备及存储介质
WO2021168858A1 (zh) * 2020-02-29 2021-09-02 华为技术有限公司 一种通信方法及装置
CN113472474A (zh) * 2020-03-30 2021-10-01 维沃移动通信有限公司 一种信息传输方法、用户终端和接入网网元
CN114650581A (zh) * 2020-12-18 2022-06-21 维沃移动通信有限公司 中继通信方法及装置
WO2022170563A1 (zh) * 2021-02-10 2022-08-18 华为技术有限公司 一种通信方法、装置及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080165776A1 (en) * 2007-01-08 2008-07-10 Zhifeng Tao Relay Tunneling in Wireless Multi-User Multi-Hop Relay Networks
CN101990324A (zh) * 2009-07-30 2011-03-23 华为技术有限公司 中继系统中的主动式用户终端选择方法及基站
CN101997593A (zh) * 2009-08-17 2011-03-30 上海交通大学 自适应中继方式择优选择方法和中继节点
CN103476140A (zh) * 2013-09-05 2013-12-25 北京邮电大学 蜂窝系统中d2d和固定中继两种协作多播模式的选择方法

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003134552A (ja) * 2001-10-23 2003-05-09 Ntt Docomo Inc 位置情報管理方法、中継装置、位置情報管理装置および移動通信システム
KR20070038657A (ko) * 2005-10-06 2007-04-11 삼성전자주식회사 다중 홉 릴레이 방식을 사용하는 광대역 무선 접속 통신시스템에서 중계국 기능 교섭 장치 및 방법
CN101291320B (zh) * 2007-04-18 2011-07-13 中兴通讯股份有限公司 Ip多媒体子系统集中业务重注册的实现方法
JP5212913B2 (ja) * 2009-03-02 2013-06-19 日本電気株式会社 Ｖｐｎ接続システム、及びｖｐｎ接続方法
CN102149205B (zh) * 2010-02-09 2016-06-15 中兴通讯股份有限公司 一种中继节点的状态管理方法及系统
CN102448073B (zh) * 2010-09-30 2016-03-30 株式会社日立制作所 混合型中继节点、基站以及混合型中继方法
JP5769008B2 (ja) * 2011-06-07 2015-08-26 日本電気株式会社 通信処理システム、位置登録方法、移動中継局およびその制御方法と制御プログラム
US9820254B2 (en) * 2011-08-09 2017-11-14 Mitsubishi Electric Corporation Mobile communication system
JP5895415B2 (ja) * 2011-09-19 2016-03-30 株式会社リコー 通信システム、通信装置、プログラム及び割当装置
CN103209468B (zh) * 2012-01-17 2016-05-18 华为终端有限公司 无线传输的方法、接入点和站点
CN103152444B (zh) * 2013-03-25 2016-08-03 华为技术有限公司 中继方式的网络地址转换及报文传输方法及装置、系统
CN104618891B (zh) * 2013-11-04 2018-10-19 华为终端（东莞）有限公司 一种通信方法、终端及核心网实体
WO2016006859A1 (ko) * 2014-07-07 2016-01-14 엘지전자 주식회사 기기간 통신을 지원하는 무선 접속 시스템에서 릴레이 단말의 d2d 신호 송수신 방법 및 장치
CN106028427A (zh) * 2015-04-03 2016-10-12 中兴通讯股份有限公司 终端节电方法及装置
WO2016186995A1 (en) * 2015-05-15 2016-11-24 Kyocera Corporation Establishing data relay operation between a relay user equipment (relay-ue) device and an out-of-coverage user equipment (ue) device
KR101943990B1 (ko) * 2015-06-29 2019-01-30 삼성전자주식회사 무선 통신 시스템에서 통신을 수행하는 방법 및 이를 위한 장치
WO2017022039A1 (ja) * 2015-07-31 2017-02-09 日本電気株式会社 通信システム、装置、端末、通信制御方法並びにプログラム
ES2794566T3 (es) * 2015-08-07 2020-11-18 Samsung Electronics Co Ltd Terminal y procedimiento de comunicación del mismo
CN107333221B (zh) * 2016-04-28 2020-11-13 阿尔卡特朗讯 一种用于控制终端通信的方法与设备
US10560915B2 (en) * 2016-05-02 2020-02-11 Lg Electronics Inc. Method for performing location registration by remote UE in wireless communication system, and apparatus therefor

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080165776A1 (en) * 2007-01-08 2008-07-10 Zhifeng Tao Relay Tunneling in Wireless Multi-User Multi-Hop Relay Networks
CN101990324A (zh) * 2009-07-30 2011-03-23 华为技术有限公司 中继系统中的主动式用户终端选择方法及基站
CN101997593A (zh) * 2009-08-17 2011-03-30 上海交通大学 自适应中继方式择优选择方法和中继节点
CN103476140A (zh) * 2013-09-05 2013-12-25 北京邮电大学 蜂窝系统中d2d和固定中继两种协作多播模式的选择方法

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
CN109788507A (zh) 2019-05-21
US20200275258A1 (en) 2020-08-27
EP3687259B1 (en) 2023-04-05
EP3687259A4 (en) 2020-09-09
EP3687259A1 (en) 2020-07-29
CN109788507B (zh) 2021-10-22

Similar Documents

Publication Publication Date Title
US11832134B2 (en) Inter-communications-system moving method, device, and system
US11641601B2 (en) Method, apparatus and device for allowing terminal to move between 4G and 5G networks
WO2019091307A1 (zh) 通信方法和装置
CN109600802B (zh) 数据传输方法、相关设备及系统
US10986543B2 (en) Method and device for determining a bearer identifier, and storage medium therefor
KR20190010884A (ko) 무선 통신 방법 및 장치
EP3799489A1 (en) Paging area update by a lightly connected wireless device
US11082893B2 (en) Session migration method and device applied to a UE tracking area update
KR20200097336A (ko) 세션 확립을 위한 방법 및 장치
WO2018137152A1 (zh) 短消息传输方法、设备和系统
EP3739918B1 (en) Method and apparatus for transmitting downlink data
US20220248290A1 (en) Communication Method and Communications Apparatus
US20220295279A1 (en) User equipment, intra-core network apparatus, and communication control method
CN112840687A (zh) Ue能力传输和存储
JP7350066B2 (ja) 無線通信の方法及び機器
WO2019076308A1 (zh) 终端设备的状态的确定方法、装置及设备
CN110859012A (zh) 一种速率控制的方法、装置和系统
US20190110323A1 (en) Access method, apparatus, device, and system
WO2019136925A1 (zh) 一种数据传输方法及装置、计算机存储介质
US11991516B2 (en) Session migration method and apparatus
WO2023245412A1 (zh) 上行定位参考信号的配置方法、装置、设备及存储介质
CN115413063A (zh) 建立连接的方法、装置和系统
CN118077298A (zh) 会话标识管理方法
KR20190058284A (ko) 네트워크에서의 단말의 등록 취소 방법 및 이를 수행하는 단말
WO2016184182A1 (zh) 管理用户资源的方法、msc及系统

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018877235

Country of ref document: EP

Effective date: 20200423

NENP Non-entry into the national phase

Ref country code: DE