WO2021062807A1 - 一种通信方法、装置以及系统 - Google Patents

一种通信方法、装置以及系统 Download PDF

Info

Publication number
WO2021062807A1
WO2021062807A1 PCT/CN2019/109732 CN2019109732W WO2021062807A1 WO 2021062807 A1 WO2021062807 A1 WO 2021062807A1 CN 2019109732 W CN2019109732 W CN 2019109732W WO 2021062807 A1 WO2021062807 A1 WO 2021062807A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
data plane
session management
management network
iab node
Prior art date
Application number
PCT/CN2019/109732
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 PCT/CN2019/109732 priority Critical patent/WO2021062807A1/zh
Priority to CN201980100816.2A priority patent/CN114503625B/zh
Priority to EP19947465.1A priority patent/EP4027673A4/en
Publication of WO2021062807A1 publication Critical patent/WO2021062807A1/zh
Priority to US17/709,247 priority patent/US20220225463A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • 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
    • H04W8/12—Mobility data transfer between location registers or mobility servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]

Definitions

  • the embodiments of the present application relate to the field of communication technologies, and in particular, to a communication method, device, and system.
  • the demands made by industrial manufacturers on the fifth-generation mobile communication technology are mainly concentrated in three aspects, namely: (1) Replacement of wired cables, that is, according to different usage scenarios, different The degree of use of wireless connections to replace wired connections, to enhance the flexibility of plant equipment deployment. As shown in Figure 1-1, some functional device combinations all use wireless connections, and some only partially use wireless connections.
  • IAB nodes are deployed around the production line. Integrate the data plane module on the IAB node or combine the IAB node and the data plane module on the same device. Among them, the data plane module has routing and forwarding functions. In this way, when local devices (for example, device 1 and device 2) exchange data, the data of device 1 can be forwarded to device 2 only after being processed by the data plane module, and no longer needs to be forwarded to the core network, thereby greatly reducing transmission delay.
  • local devices for example, device 1 and device 2
  • the control network element for example, the session management function (SMF) network element
  • the data plane module for example, to the data plane
  • the first interface for example, the N4 interface
  • the plane module issues forwarding rules), and the traditional N4 interface needs to be addressed through an IP address or fully qualified domain names (FQDN), that is, a wired connection to the 5G core network.
  • FQDN fully qualified domain names
  • the control network element of the 5G core network cannot address the data plane module through the traditional IP address or FQDN. It also cannot control and manage the data plane module.
  • the data plane module in the current 5G standard can directly register the data plane instance corresponding to the data plane module to the service interface or indirectly (for example, through the network management element (Operation, Administration and Maintenance, OAM)) In the Network Function Repository Function (NRF) (Step 5 or Step 6 in Figure 1-2).
  • the SMF network element In order for the SMF network element to select the data plane module through steps 1 and 2, the data plane instance with specific requirements can be obtained from the NRF (for example, in step 7, the notification message carries the user plane network element that meets the requirements of the SMF network element in step 1. List).
  • the data plane module directly registers with the NRF through the service interface, IP connectivity between the data plane module and the NRF is required, so that the data plane module can correctly address the NRF network element through the IP address or FQDN to complete the instance Register, but if the instance is integrated/co-located on the IAB node, the wireless backhaul network cannot still be addressed in the existing way.
  • the data plane module indirectly registering with NRF through OAM, because the integrated/co-located instance on the IAB node also does not have a direct IP path with OAM, this registration method cannot work either. If the data plane instance cannot be registered normally, the SMF network element cannot select the data plane normally, and it is not convenient for the SMF network element to manage and control the data plane instance in the future.
  • the embodiments of the present application provide a method, device, and system for managing a user plane network element, so as to implement an instance of the session management network element correctly addressing the data plane.
  • an embodiment of the present application provides a communication method, which includes: a session management network element determining information about a target data plane instance that includes a routing indication. Among them, the routing indication is used to determine the address of the target data plane instance.
  • the target data plane instance is associated with the wireless backhaul IAB node.
  • the session management network element sends an N4 session management request message and a first instruction to the IAB node through the mobility management network element that provides services for the IAB node or the host Donor node.
  • the first instruction is used to instruct the IAB node to send N4 session management to the target data plane instance. Request message.
  • the embodiment of the present application provides a communication method in which the session management network element determines the information of the target data plane instance, because the information of the target data plane instance includes routing instructions. Therefore, the session management network element can determine the address of the target data plane instance according to the routing instructions, so that the session management network element can correctly address the target data plane instance. Since the target data plane instance is associated with the IAB node, the session management network element can send an N4 session management request message to the IAB node to realize the management of the target data plane instance. This solution can realize the registration and management of the target data plane instance brought by the wireless N4 interface.
  • the method provided in the embodiment of the present application further includes: the session management network element determines the session management The context of the IAB node exists locally in the network element.
  • the session management network element sends the N4 session management request message and the first instruction to the IAB node through the mobility management network element, including: the session management network element generates a session management non-access layer NAS message according to the context of the IAB node, and the session management NAS layer message Including the N4 session management request message and the first instruction.
  • the session management network element sends a session management NAS layer message to the IAB node through the mobility management network element.
  • the presence of the context of the IAB node locally in the session management network element indicates that the terminal and the IAB node access the same mobility management network element.
  • the session management network element determines that the context of the local IAB node exists in the session management network element can use the session management network element to obtain the context of the local IAB node instead.
  • the context of the IAB node does not exist locally in the session management network element.
  • the method provided in the embodiment of the present application further includes: the session management network element sends a routing instruction to the mobility management network element, and the mobility management network element uses After determining according to the routing instructions that the mobility management network element locally has the context of the IAB node, the mobility management network element generates a mobility management NAS message according to the context of the IAB node, and sends the mobility management NAS message to the IAB node.
  • the mobility management NAS message includes an N4 session management request message and a first indication. In this way, when the context of the IAB node does not exist locally in the session management network element, the IAB node can be addressed through the mobility management network element, and an N4 session management request message can be sent to the IAB node.
  • the method provided in the embodiment of the present application further includes: the session management network element receives the instruction information from the mobility management network element.
  • the indication information is used to indicate that the mobility management network element has the context of the IAB node locally.
  • the method provided in the embodiment of the present application further includes: the session management network element obtains the mobility management of the IAB node from the user data management network element Information about the network element.
  • This method can be used in scenarios where the session management network element determines that the mobility management network element that provides services for the terminal does not have the context of the IAB node, so that it is convenient for the session management network element to determine the mobility that provides services for the IAB node from the user data management network element The address of the management network element.
  • the method provided in the embodiment of the present application may further include: the session management network element is determined to be The mobility management network element provided by the terminal does not have the context of the IAB node.
  • the session management network element determines that the mobility management network element that provides services for the terminal does not have the context of the IAB node, including: the session management network element sends a query request to the mobility management network element that provides services for the terminal news. Among them, the query request message is used to query whether the mobility management network element that provides services for the terminal has the context of the IAB node. The session management network element receives a response message from the mobility management network element that provides services for the terminal. The response message is used to indicate that the mobility management network element that provides services for the terminal does not have the context of the IAB node.
  • the query request message carries indication information for querying whether the mobility management network element that provides services for the terminal has the context of the IAB node.
  • the response message carries confirmation information, which is used to indicate that the mobility management network element that provides services for the terminal does not have the context of the IAB node.
  • the session management network element sending the N4 session management request message and the first instruction to the IAB node through the Donor node further includes: the session management network element sending a routing instruction to the Donor node, and the Donor node is used to follow the routing instruction Send a first message to the IAB node, where the first message includes an N4 session management request message and a first instruction. This facilitates the addressing of the IAB node through the host node.
  • the method provided in the embodiment of the present application further includes: the session management network element receives the N4 session management response message from the target data plane instance through the IAB node. This facilitates the session management network element to determine whether the target data plane instance successfully manages the N4 session.
  • the method provided in the embodiment of the present application further includes: the session management network element obtains information of one or more data plane instances from the network storage network element, and the one or more data plane instances include target data ⁇ Surface examples.
  • the method provided in the embodiment of the present application further includes: the session management network element receives one or more data plane instances of the data plane module through a network management network element, or a Donor node, or a mobility management network element.
  • Information, one or more data plane instances include target data plane instances.
  • one or more data plane instances are transparently transmitted at the Donor node or mobility management network element, or one or more data plane instances are sent after being processed by the Donor node or mobility management network element To session management network element or network storage network element.
  • the IAB node and the data plane module corresponding to the target data plane instance are located in the same device; or, the IAB node has a data plane module corresponding to the target data plane instance.
  • an embodiment of the present application provides a communication method, which includes: wirelessly backhauling an IAB node to receive an N4 session management request message and a first instruction from a session management network element.
  • the first indication is used to instruct the IAB node to send an N4 session management request message to the target data plane instance.
  • the IAB node sends an N4 session management request message to the target data plane instance according to the first instruction, and the N4 session management request message is used to instruct to manage the session context of the target data plane instance.
  • the method provided in the embodiment of the present application further includes: the IAB node receives the N4 session management response message sent by the target data plane instance.
  • the IAB node sends a second instruction and an N4 session management response message to the Donor node or the mobility management network element, and the second instruction is used to instruct to send the N4 session management response message to the session management network element.
  • the method provided in the embodiment of the present application further includes: the IAB node sends a first message including information of one or more data plane instances corresponding to the data plane module to the first device.
  • the information of one or more data plane instances includes the information of the target data plane instance, and the information of any data plane instance includes routing instructions.
  • the first message is used to instruct the first device to register one or more information with the session management network element or the network storage network element. Information about multiple data plane instances.
  • the routing indication is used for the session management network element to determine the address of any data plane instance.
  • Any data plane instance is associated with an IAB node, and the first device includes any one of the following: a network management network element or a Donor node, or a mobility management network element.
  • the method provided in this embodiment of the application further includes: the first message includes the payload container Payload Container, the payload container includes information about one or more data plane instances, and the type of the payload container is used to indicate The first device registers the information of one or more data plane instances with the session management network element or the network storage network element.
  • the method provided in the embodiment of the present application further includes: the first message further includes a registration instruction, and the registration instruction is used to instruct the first device to register one or more with the session management network element or the network storage network element. Information about a data plane instance.
  • the method provided in the embodiment of the present application further includes: a predefined operation interface is provided between the IAB node and the first device, and the predefined operation interface is used to instruct the first device to communicate with the session management network element Or the network storage network element registers the information of one or more data plane instances, and the IAB node sends the first message to the first device through a predefined operation interface.
  • the method provided in the embodiment of the present application further includes: the information of one or more data plane instances is transparently transmitted at the Donor node or the mobility management network element, or one or more data plane instances After being processed by the Donor node or the mobility management network element, the information is sent to the session management network element or the network storage network element.
  • the method provided in the embodiment of the present application further includes: the IAB node and the data plane module corresponding to the data plane instance are located in the same device; or, the IAB node has a data plane module corresponding to the data plane instance .
  • an embodiment of the present application provides a communication method.
  • the method includes: a mobility management network element that provides services for an IAB node receives an N4 session management request message and a first instruction from the session management network element, where the first instruction is used for Instruct the IAB node to send an N4 session management request message to the target data plane instance; the mobility management network element sends an N4 session management request message and the first instruction to the IAB node.
  • the method provided in this embodiment of the present application further includes: the mobility management network element receives a route from the session management network element Indication, the routing indication is used to determine the address of the target data plane instance; the target data plane instance AB node is associated; the mobility management network element determines that the mobility management network element locally has the context of the IAB node according to the routing indication, and the mobility management network element The context generates a mobility management NAS message; the mobility management network element sends an N4 session management request message and a first instruction to the IAB node. It includes: the mobility management network element sends a mobility management NAS message to the IAB node, and the mobility management NAS message includes an N4 session management request message and a first instruction.
  • the method provided in the embodiment of the present application further includes: mobility management The network element receives a query request message from the session management network element, and the query request message is used to query whether the mobility management network element has the context of the IAB node. If the mobility management network element has the context of the IAB node, the mobility management network element sends a response message indicating that the mobility management network element has the context of the IAB node to the session management network element. If the mobility management network element does not have the context of the IAB node, the mobility management network element sends a response message indicating that the mobility management network element does not have the context of the IAB node to the session management network element.
  • the method provided in the embodiment of the present application further includes: the mobility management network element receives a first message, the first message includes information about one or more data plane instances of the data plane module, and the first message uses To instruct the mobility management network element to register the information of one or more data plane instances with the session management network element or the NRF network element; the information of any data plane instance includes routing instructions; the information of one or more data plane instances includes the target data plane Instance information; the mobility management network element registers the information of one or more data plane instances with the session management network element or the network storage network element according to the first message.
  • the information of one or more data plane instances is transparently transmitted at the mobility management network element, or the information of one or more data plane instances is processed by the mobility management network element and then sent to the session management network. Yuan or network storage network element.
  • the method provided in the embodiment of the present application further includes: the mobility management network element receives an N4 session management response message and a second instruction from the data plane instance through an IAB node or a Donor node, and the second instruction is used for Instruct to send the N4 session management response message to the session management network element; the mobility management network element sends the N4 session management response message to the session management network element.
  • an embodiment of the present application provides a communication device, which can implement the first aspect or any one of the possible implementations of the first aspect, and therefore can also implement the first aspect.
  • the communication device of this type may be a session management network element, or may be a device that can support the session management network element to implement the first aspect or any one of the possible implementation manners of the first aspect. For example, it is applied to a chip in a session management network element.
  • This kind of communication device can implement the above method through software, hardware, or through hardware executing corresponding software.
  • the communication device includes: a processing unit configured to determine information of a target data plane instance, the information of the target data plane instance includes routing instructions, and the routing instructions are used to determine the address of the target data plane instance;
  • the target data plane instance is associated with the wireless backhaul IAB node;
  • the communication unit is used to send the N4 session management request message and the first instruction to the IAB node through the mobility management network element or the host Donor node that provides services for the IAB node. To instruct the IAB node to send an N4 session management request message to the target data plane instance.
  • the communication unit is configured to send the N4 session management request message and the first indication to the IAB node through the mobility management network element, and the processing unit is further configured to determine that the device locally has the context of the IAB node; processing unit , Is also used to generate a session management non-access layer NAS message according to the context of the IAB node.
  • the session management NAS layer message includes an N4 session management request message and a first indication; correspondingly, the communication unit is also used to send messages to the mobile management network element
  • the IAB node sends a session management NAS layer message.
  • the processing unit is used to determine that the context of the IAB node does not exist locally in the device, and the communication unit is also used to send routing instructions to the mobility management network element, and the mobility management network element is used to determine the mobility according to the routing instructions.
  • the mobility management network element After the management network element has the context of the IAB node locally, the mobility management network element generates the mobility management NAS message according to the context of the IAB node, and sends the mobility management NAS message to the IAB node.
  • the mobility management NAS message includes the N4 session management request message and the first One instruction.
  • the communication unit provided in the embodiment of the present application is also used to receive instruction information from the mobility management network element.
  • the indication information is used to indicate that the mobility management network element has the context of the IAB node locally.
  • the communication unit is configured to before sending a routing instruction to the mobility management network element, the communication unit is also configured to obtain the mobility management network element information of the IAB node from the user data management network element.
  • the processing unit before the communication unit obtains the information of the mobility management network element of the IAB node from the user data management network element, the processing unit is also used to determine that the mobility management network element that provides services for the terminal does not have IAB The context of the node.
  • the communication unit is further configured to send a query request to the mobility management network element that provides services for the terminal news.
  • the query request message is used to query whether the mobility management network element that provides services for the terminal has the context of the IAB node.
  • the session management network element receives a response message from the mobility management network element that provides services for the terminal.
  • the response message is used to indicate that the mobility management network element that provides services for the terminal does not have the context of the IAB node.
  • the query request message carries indication information for querying whether the mobility management network element that provides services for the terminal has the context of the IAB node.
  • the response message carries confirmation information, which is used to indicate that the mobility management network element that provides services for the terminal does not have the context of the IAB node.
  • the communication unit configured to send the N4 session management request message and the first instruction to the IAB node through the Donor node, further includes: sending a routing instruction to the Donor node, and the Donor node is configured to send the N4 session management request message to the IAB node according to the routing instruction.
  • the first message is sent, and the first message includes the N4 session management request message and the first instruction.
  • the communication unit is further configured to receive the N4 session management response message from the target data plane instance through the IAB node.
  • the communication unit is further configured to obtain information of one or more data plane instances from the network storage network element, and the one or more data plane instances include the target data plane instance.
  • the communication unit is also used to receive information about one or more data plane instances of the data plane module through the network management network element, or the Donor node, or the mobility management network element, and one or more data planes
  • the instance includes the target data plane instance.
  • one or more data plane instances are transparently transmitted at the Donor node or mobility management network element, or one or more data plane instances are sent after being processed by the Donor node or mobility management network element To device or network storage network element.
  • the IAB node and the data plane module corresponding to the target data plane instance are located in the same device; or, the IAB node has a data plane module corresponding to the target data plane instance.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a session management network element or a chip in the session management network element.
  • the communication device may include: a communication unit and a processing unit.
  • the communication unit may be a communication interface.
  • the communication device may also include a storage unit.
  • the storage unit may be a memory.
  • the storage unit is used to store computer program code, and the computer program code includes instructions.
  • the processing unit may be a processor. The processing unit executes the instructions stored in the storage unit, so that the session management network element implements the first aspect or a communication method described in any possible implementation manner of the first aspect.
  • the processing unit may be a processor, and the communication unit may be collectively referred to as a communication interface.
  • the communication interface may be an input/output interface, pin or circuit, and so on.
  • the processing unit executes the computer program code stored in the storage unit, so that the session management network element implements the communication method described in the first aspect or any one of the possible implementations of the first aspect, and the storage unit may be the
  • the storage unit (for example, register, cache, etc.) in the chip may also be a storage unit (for example, read-only memory, random access memory, etc.) located outside the chip in the session management network element.
  • the processor, the communication interface and the memory are coupled with each other.
  • the embodiments of the present application provide a communication device, which can implement the second aspect or any one of the communication methods described in the second aspect, and therefore can also implement the second aspect. Aspect or the beneficial effects in any possible implementation manner of the second aspect.
  • the communication device of this type may be an IAB node, or a device that can support the IAB node to implement the second aspect or any one of the possible implementation manners of the second aspect. For example, it is applied to the chip in the IAB node.
  • This kind of communication device can implement the above method through software, hardware, or through hardware executing corresponding software.
  • a communication device provided in an embodiment of the present application includes: a processing unit, configured to process information; and a communication unit, configured to receive an N4 session management request message and a first instruction from a session management network element, the first instruction Used to instruct the communication unit to send an N4 session management request message to the target data plane instance; the communication unit is used to send an N4 session management request message to the target data plane instance according to the first instruction, and the N4 session management request message is used to instruct to manage the target data The session context of the face instance.
  • the communication unit is further configured to receive the N4 session management response message sent by the target data plane instance; the IAB node sends the second instruction to the Donor node or the mobility management network element, and the N4 session management response message, The second indication is used to indicate to send an N4 session management response message to the session management network element.
  • the communication unit is further configured to send a first message to the first device, where the first message includes information about one or more data plane instances corresponding to the data plane module, and one or more data plane instances
  • the information includes the information of the target data plane instance, the information of any data plane instance includes routing instructions, and the first message is used to instruct the first device to register information about one or more data plane instances with the session management network element or the network storage network element
  • the routing indication is used for the session management network element to determine the address of any data plane instance; any data plane instance is associated with the device, and the first device includes any one of the following: a network management network element or a Donor node, or a mobility management network element.
  • the first message includes the payload container Payload Container
  • the payload container includes information about one or more data plane instances
  • the type of the payload container is used to instruct the first device to send a message to the session management network element or network
  • the storage network element registers the information of one or more data plane instances.
  • the first message further includes a registration instruction, and the registration instruction is used to instruct the first device to register information about one or more data plane instances with the session management network element or the network storage network element.
  • the predefined operation interface is used to instruct the first device to send a message to the session management network element or the network storage network element.
  • Register the information of one or more data plane instances, and the communication unit is configured to send the first message to the first device through a predefined operation interface.
  • the information of one or more data plane instances is transparently transmitted at the Donor node or the mobility management network element, or the information of one or more data plane instances is transmitted by the Donor node or the mobility management network element. After the meta is processed, it is sent to the session management network element or the network storage network element.
  • the IAB node and the data plane module corresponding to the data plane instance are located in the same device; or, the IAB node has a data plane module corresponding to the data plane instance.
  • an embodiment of the present application provides a communication device.
  • the communication device may be an IAB node or a chip in the IAB node.
  • the communication device may include: a communication unit and a processing unit.
  • the communication unit may be a communication interface.
  • the communication device may also include a storage unit.
  • the storage unit may be a memory.
  • the storage unit is used to store computer program code, and the computer program code includes instructions.
  • the processing unit may be a processor. The processing unit executes the instructions stored in the storage unit, so that the IAB node implements the second aspect or a communication method described in any possible implementation manner of the second aspect.
  • the processing unit may be a processor, and the communication unit may be collectively referred to as a communication interface.
  • the communication interface may be an input/output interface, pin or circuit, and so on.
  • the processing unit executes the computer program code stored in the storage unit, so that the IAB node implements the communication method described in the second aspect or any one of the possible implementations of the second aspect.
  • the storage unit may be in the chip
  • the storage unit (for example, register, cache, etc.) in the IAB node may also be a storage unit (for example, read-only memory, random access memory, etc.) located outside the chip in the IAB node.
  • the processor, the communication interface and the memory are coupled with each other.
  • the embodiments of the present application provide a communication device that can implement the third aspect or any one of the communication methods described in the possible implementation of the third aspect. Therefore, the third aspect can also be implemented. Aspect or the beneficial effects in any possible implementation manner of the third aspect.
  • the communication device may be a mobility management network element, or a device that can support the mobility management network element to implement the third aspect or any one of the possible implementation manners of the third aspect. For example, it is applied to chips in mobile management network elements.
  • This kind of communication device can implement the above method through software, hardware, or through hardware executing corresponding software.
  • an embodiment of the present application provides a communication device, including: a processing unit for processing information; a communication unit for receiving an N4 session management request message and a first instruction from a session management network element, and the first instruction is used for To instruct the IAB node to send the N4 session management request message to the target data plane instance; the communication unit is also used to send the N4 session management request message and the first instruction to the IAB node.
  • the communication unit is also used to send the N4 session management request message and the first instruction to the IAB node, the communication unit is also used to receive routing instructions from the session management network element, and the routing instructions are used to The address of the target data plane instance is determined; the AB node of the target data plane instance is associated; the processing unit is used to generate a mobility management NAS message according to the context of the IAB node after determining that the device locally has the context of the IAB node according to the routing instruction; To send a mobility management NAS message to the IAB node, the mobility management NAS message includes an N4 session management request message and a first instruction.
  • the communication unit is further configured to receive a first message, the first message includes information about one or more data plane instances of the data plane module, and the first message is used to instruct the device to send a message to the session management network element.
  • the NRF network element registers the information of one or more data plane instances; the information of any data plane instance includes routing instructions; the information of one or more data plane instances includes the information of the target data plane instance; A message that registers information about one or more data plane instances with the session management network element or the network storage network element through the communication unit.
  • the information of one or more data plane instances is transparently transmitted at the mobility management network element, or the information of one or more data plane instances is processed by the mobility management network element and then sent to the session management network. Yuan or network storage network element.
  • the communication unit is configured to receive the N4 session management response message and the second instruction from the target data plane instance through the IAB node or the Donor node, and the second instruction is used to instruct to send N4 to the session management network element.
  • Session management response message the communication unit is used to send an N4 session management response message to the session management network element.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a mobility management network element or a chip in the mobility management network element.
  • the communication device may include: a communication unit and a processing unit.
  • the communication unit may be a communication interface.
  • the communication device may also include a storage unit.
  • the storage unit may be a memory.
  • the storage unit is used to store computer program code, and the computer program code includes instructions.
  • the processing unit may be a processor. The processing unit executes the instructions stored in the storage unit, so that the mobility management network element implements a communication method described in the third aspect or any one of the possible implementation manners of the third aspect.
  • the processing unit may be a processor, and the communication unit may be collectively referred to as a communication interface.
  • the communication interface may be an input/output interface, pin or circuit, and so on.
  • the processing unit executes the computer program code stored in the storage unit to enable the mobility management network element to implement the communication method described in the third aspect or any one of the possible implementations of the third aspect.
  • the storage unit may be the The storage unit (for example, register, cache, etc.) in the chip may also be a storage unit (for example, read-only memory, random access memory, etc.) located outside the chip in the mobility management network element.
  • the processor, the communication interface and the memory are coupled with each other.
  • the embodiments of the present application provide a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program or instruction.
  • the computer program or instruction runs on a computer, the computer executes the first aspect, or
  • the communication method is described in any possible implementation of the first aspect.
  • an embodiment of the present application provides a computer-readable storage medium in which a computer program or instruction is stored.
  • the computer program or instruction runs on a computer, the computer can execute the second aspect, or The communication method described in any possible implementation of the second aspect.
  • the embodiments of the present application provide a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program or instruction.
  • the computer program or instruction runs on the computer, the computer can execute the third aspect, or The communication method described in any possible implementation of the third aspect.
  • the embodiments of the present application provide a computer program product including instructions.
  • the instructions run on a computer, the computer executes the communication method described in the first aspect or any one of the possible implementations of the first aspect. .
  • an embodiment of the present application provides a computer program product including instructions.
  • the instructions run on a computer, the computer executes the communication described in the second aspect or any one of the possible implementations of the second aspect. method.
  • the embodiments of the present application provide a computer program product including instructions.
  • the instructions run on a computer, the computer executes the communication described in the third aspect or any one of the possible implementations of the third aspect. method.
  • an embodiment of the present application provides a communication device.
  • the communication device includes a processor and a storage medium.
  • the storage medium stores instructions. When the instructions are executed by the processor, they implement various aspects such as the first aspect or the first aspect. Possible implementations describe the communication method.
  • an embodiment of the present application provides a communication device.
  • the communication device includes a processor and a storage medium.
  • the storage medium stores instructions. When the instructions are executed by the processor, they can implement various aspects such as the second aspect or the second aspect. Possible implementations describe the communication method.
  • an embodiment of the present application provides a communication device that includes a processor and a storage medium.
  • the storage medium stores instructions.
  • the instructions When executed by the processor, they can implement various aspects such as the third aspect or the third aspect. Possible implementations describe the communication method.
  • an embodiment of the present application provides a communication device, including: at least one processor and a communication interface, the at least one processor and the communication interface are interconnected through a line, the at least one processor is coupled to the memory, and the memory is used for To store a computer program or instruction, at least one processor is used to execute the computer program or instruction in the memory, so that the communication device executes the communication method described in the first aspect or various possible implementation manners of the first aspect.
  • an embodiment of the present application provides a communication device, including: at least one processor and a communication interface, the at least one processor and the communication interface are interconnected through a line, the at least one processor is coupled to the memory, and the memory is To store a computer program or instruction, at least one processor is used to execute the computer program or instruction in the memory, so that the communication device executes the communication method described in the second aspect or various possible implementation manners of the second aspect.
  • an embodiment of the present application provides a communication device, including: at least one processor and a communication interface, the at least one processor and the communication interface are interconnected through a line, the at least one processor is coupled to the memory, and the memory is used for To store a computer program or instruction, at least one processor is used to execute the computer program or instruction in the memory, so that the communication device executes the communication method described in the third aspect or various possible implementation manners of the third aspect.
  • the device described in any one of the sixteenth aspect, the seventeenth aspect, and the eighteenth aspect may further include: a memory.
  • an embodiment of the present application provides a chip.
  • the chip includes at least one processor and a communication interface.
  • the communication interface is coupled to the at least one processor.
  • the at least one processor is used to run a computer program or instruction to implement the first aspect. Or a communication method described in the various possible implementations of the first aspect.
  • the communication interface is used to communicate with modules other than the chip.
  • an embodiment of the present application provides a chip that includes at least one processor and a communication interface, the communication interface is coupled to at least one processor, and the at least one processor is used to run computer programs or instructions to implement the second aspect Or a communication method described in the various possible implementations of the second aspect.
  • the communication interface is used to communicate with other modules outside the chip.
  • an embodiment of the present application provides a chip.
  • the chip includes at least one processor and a communication interface.
  • the communication interface is coupled to the at least one processor.
  • the at least one processor is used to run a computer program or instruction to implement the third Aspect or various possible implementations of the third aspect.
  • the communication interface is used to communicate with other modules outside the chip.
  • the chip provided in the embodiment of the present application may further include a memory, and the memory is used to store computer programs or instructions.
  • an embodiment of the present application provides a communication device.
  • the communication device includes one or more modules for implementing the methods of the first, second, and third aspects.
  • the one or more The module may correspond to the steps of the method of the first aspect, the second aspect, and the third aspect described above.
  • an embodiment of the present application provides a communication device, including: at least one processor, at least one processor coupled with a memory, the memory is used to store computer programs or instructions, and at least one processor is used to execute the The computer program or instruction causes the communication device to execute the communication method described in the first aspect or various possible implementation manners of the first aspect.
  • an embodiment of the present application provides a communication device, including: at least one processor, at least one processor is coupled with a memory, the memory is used to store computer programs or instructions, and at least one processor is used to execute the The computer program or instruction causes the communication device to execute the communication method described in the second aspect or various possible implementation manners of the second aspect.
  • an embodiment of the present application provides a communication device, including: at least one processor, at least one processor coupled with a memory, the memory is used to store computer programs or instructions, and at least one processor is used to execute the The computer program or instruction causes the communication device to execute the communication method described in the third aspect or various possible implementation manners of the third aspect.
  • an embodiment of the present application provides a communication system, which includes: the communication device described in the fourth aspect or various possible implementation manners of the fourth aspect, and the fifth aspect or the fifth aspect The communication device described in the various possible implementations.
  • the communication system may further include: the communication device described in the sixth aspect or various possible implementation manners of the sixth aspect.
  • Figure 1-1 is a schematic diagram 1 of a scenario provided by an embodiment of the application.
  • Figure 1-2 is a UPF instance registration process provided by an embodiment of this application.
  • Figure 2 is a second schematic diagram of a scenario provided by an embodiment of the application.
  • FIG. 3a is a diagram 1 of a communication system architecture provided by an embodiment of this application.
  • FIG. 3b is a diagram 2 of a communication system architecture provided by an embodiment of this application.
  • FIG. 3c is a third diagram of a communication system architecture provided by an embodiment of this application.
  • FIG. 3d is a fourth diagram of a communication system architecture provided by an embodiment of this application.
  • FIG. 4a is a schematic diagram of a 5G network architecture provided by an embodiment of this application.
  • FIG. 4b is a schematic diagram of another 5G network architecture provided by an embodiment of this application.
  • FIG. 4c is a schematic diagram of yet another 5G network architecture provided by an embodiment of this application.
  • FIG. 5 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • 6 to 15 are schematic flowcharts of a communication method provided by an embodiment of this application.
  • FIG. 16 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 17 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • FIG. 18 is a schematic structural diagram of a chip provided by an embodiment of the application.
  • words such as “first” and “second” are used to distinguish the same items or similar items that have substantially the same function and effect.
  • the first message and the second message are only for distinguishing different messages, and the sequence of them is not limited.
  • words such as “first” and “second” do not limit the quantity and execution order, and words such as “first” and “second” do not limit the difference.
  • At least one refers to one or more, and “multiple” refers to two or more.
  • “And/or” describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
  • the following at least one item (a)” or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
  • at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .
  • Fig. 2 shows a network deployment method in which the method provided in an embodiment of the present application is suitable for industrial scenarios. As shown in Fig. 2, it includes: a local data network, a 5G core network, and a host that communicates with the 5G core network. Node and the IAB node that accesses the host node.
  • the IAB node is deployed near the production line, and the data plane module is integrated behind the IAB node or the IAB node and the data plane module are set on the same device, so that when the local devices (for example, device 1 and device 2) exchange data, the device 1’s Data can be forwarded to device 2 after being processed by the data plane module, and no longer needs to be forwarded to the core network, thereby greatly reducing transmission delay.
  • the local devices for example, device 1 and device 2
  • the device 1’s Data can be forwarded to device 2 after being processed by the data plane module, and no longer needs to be forwarded to the core network, thereby greatly reducing transmission delay.
  • an embodiment of the present application provides a communication system.
  • the communication system includes: an IAB node 10, a session management network element 20, and a data plane module 30 located inside the IAB node 10.
  • one data plane module 30 may correspond to one or more data plane instances.
  • the communication system may further include: a network storage network element 80.
  • the NRF network element 80 can store information about one or more data plane instances. Specifically, for the information of the data plane instance, reference may be made to the description in the following embodiments, which will not be repeated here.
  • the network storage network element 80 may be omitted.
  • the communication system may further include: a mobility management network element 40 or a Donor node 40 or one or more input and output devices (input output devices, IO devices) 60 or network management Network element 70.
  • the IO device may be a terminal.
  • the IAB node 10 may register information of one or more data plane instances with the network storage network element 80 or the session management network element 20 through the mobility management network element 40 or the Donor node 40 or the network management network element 70.
  • the IAB node 10 and the session management network element 20 can communicate indirectly.
  • the IAB node 10 communicates with the session management network element 20 through the mobility management network element 40 or the Donor node 50.
  • first interface between the mobility management network element 40 and the host node 50.
  • the first interface may be an N2 interface.
  • the second interface may be an N11 interface.
  • the name of the interface between each network element in the embodiment of the present application is only an example.
  • the third interface may be a Uu port.
  • the fourth interface may be a service interface for providing the registration function of data plane instance information.
  • the mobility management network element 40 and the session management network element 20 also have a service-oriented interface for providing the function of registering data plane instance information.
  • FIG. 3b another communication system is provided for this embodiment of the application.
  • the data plane module 30 in Fig. 3a can be located inside the IAB node 10, that is, the IAB node 10 has a data plane.
  • the module 30 or the data plane module 30 is integrated in the IAB node 10.
  • the data plane module 30 and the IAB node 10 are located in the same device 00.
  • the N4 interface between the session management network element 20 and the IAB node 10 can be implemented indirectly.
  • the terminal and the IAB node can access the same mobility management network element 40, that is, the mobility management network element selected by the terminal and the mobility management network element selected by the IAB node are the same.
  • the terminal and the IAB node can access different mobility management network elements 40, that is, the mobility management network element selected by the terminal and the mobility management network element selected by the IAB node are different.
  • the terminal and the IAB node can access different session management network elements, that is, the session management network element selected by the terminal and the session management network element selected by the IAB node are different.
  • the terminal and the IAB node can access the same session management network element, that is, the session management network element selected by the terminal and the session management network element selected by the IAB node are the same.
  • the IAB node When the IAB node adopts a separate architecture, in conjunction with Fig. 3a, as shown in Fig. 3c, if the data plane module 50 is located inside the IAB node 10, as shown in Fig. 3c, the IAB node includes: the mobile termination of the IAB node. MT) and the distributed unit (DU) of the IAB node, the data plane module 30, and the distributed user plane (Centralized Unit-User Plane, CU-UP). That is to enhance the function of the existing IAB node, each functional module is used as an internal module of the IAB node, the MT, DU data plane module 30 and the CU-UP have internal interfaces between each other, and any modules can communicate with each other through the internal interface.
  • MT mobile termination of the IAB node.
  • DU distributed unit
  • CU-UP distributed user plane
  • the DU of the IAB node is similar to the DU of the gNB, and is used to provide access services to its attached subnodes (for example, terminals or other IAB nodes), that is, the function of the Uu interface.
  • the DU can provide a wireless connection function for the terminal or the next-level IAB node.
  • the MT has part of the functions of the terminal so that the IAB node 10 and the host node 40 can communicate through the Uu interface; the CU-UP is a functional module for processing user plane data in the centralized module of the base station.
  • the MT of the IAB node is similar to the terminal, and is used to provide data backhaul for the child nodes attached under the DU of the IAB node, and return the data of the child nodes attached under the DU of the IAB node to the host node.
  • the physical layer (PHY)/media access control (MAC) layer/radio link control (RLC) layer functions corresponding to the terminal Located on the DU of the IAB node that the terminal accesses.
  • the packet data convergence protocol (PDCP) protocol layer corresponding to the terminal/service data adaptation protocol (SDAP)/radio resource control (RRC) layer functions are located in the IAB that the terminal accesses On the CU of the node.
  • PDCP packet data convergence protocol
  • SDAP terminal/service data adaptation protocol
  • RRC radio resource control
  • a user plane channel with terminal granularity needs to be established.
  • the establishment method refer to the N3 tunnel establishment process, which will not be repeated here.
  • CU-UP is an internal module of the IAB.
  • the user with terminal granularity needs to be established. ⁇ Channel.
  • the communication system shown in FIGS. 3a to 3d may be applied to the current 5G network architecture and other network architectures that will appear in the future, which is not specifically limited in the embodiment of the present application.
  • the communication system shown in Figures 3a to 3d is applicable to the 5G network architecture as an example.
  • the communication system shown in Figures 3a to 3d is applicable to the 5G network architecture shown in Figure 4a or Figure 4b.
  • the communication system shown in Figures 3a to 3d is applicable to the 5G network architecture shown in Figure 4a or Figure 4b.
  • the mobility management network element 40 and the session management network element 30 may belong to the 5G core network
  • the network elements in the (5G core network, 5GC), the host node 50 and the IAB node 10 may be network elements in the 5G access network.
  • the network element or entity corresponding to the above-mentioned network management network element 70 may be an operation management and maintenance (operation, administration and maintenance, OAM) network element (also referred to as operation management). Maintain network elements).
  • OAM operation, administration and maintenance
  • Maintain network elements may be a session management function (SMF) network element in the 5G network architecture as shown in FIG. 4a or FIG. 4b.
  • the mobility management network element 40 may be an access and mobility management function (Access and Mobility Management Function, AMF) network element.
  • the host node 50 or the IAB node 10 may be an access network (AN) device or a radio access network (RAN) device.
  • the network element or entity corresponding to the data plane module 30 may be a user plane function (UPF) network element in the 5G network architecture as shown in FIG. 4a or FIG. 4b.
  • the network element or entity corresponding to the network storage network element 80 may be a network repository function (NRF) network element in the 5G network architecture as shown in FIG. 4a or FIG. 4b.
  • UPF user plane function
  • NRF network repository function
  • the 5G network architecture may also include: Policy Control Function (PCF) network elements, application function (AF) network elements, and data network (DN) , Authentication server function or authentication server function (authentication server function, AUSF) network element, unified database (Unified Data Repository, UDR) (not shown in Figure 4a or Figure 4b), unified data management (Unified Data Management, UDM) , Network Slice Selection Function (NSSF) network elements, Network Exposure Function (NEF) network elements, etc., which are not specifically limited in the embodiment of the present application.
  • PCF Policy Control Function
  • AF application function
  • DN data network
  • AUSF authentication server function
  • UDR Unified Data Repository
  • UDM Unified Data Management
  • NSSF Network Slice Selection Function
  • NEF Network Exposure Function
  • the terminal communicates with the AMF network element through a Next Generation Network (Next Generation, N1) interface (N1 for short).
  • the access device communicates with the AMF network element through the N2 interface (N2 for short).
  • the access device communicates with the UPF network element through the N3 interface (N3 for short).
  • the UPF network element communicates with the DN through the N6 interface (N6 for short).
  • Any two UPF network elements communicate through the N9 interface (abbreviated as N9).
  • the UPF network element communicates with the SMF network element through the N4 interface (N4 for short).
  • the AMF network element communicates with the SMF network element through the N11 interface (N11 for short).
  • the AMF network element communicates with the UDM network element through the N8 interface (N8 for short).
  • the SMF network element communicates with the PCF network element through the N7 interface (N7 for short).
  • the SMF network element communicates with the UDM network element through the N10 interface (N10 for short).
  • the AMF network element communicates with the AUSF network element through the N12 interface (N12 for short).
  • the AMF network element communicates with the NSSF network element through the N22 interface (N22 for short).
  • the AUSF network element communicates with the UDM network element through the N13 interface (N13 for short).
  • the UDM network element communicates with the UDR network element.
  • the PCF network element communicates with the UDR network element
  • the BSF network element communicates with the PCF network element and the SMF network element.
  • Fig. 4b shows an architecture based on a service-oriented interface in a 5G network architecture.
  • the difference between this architecture and Fig. 4a is that the control plane network elements in the 5GC in Fig. 4b can also interact with a service-oriented interface.
  • AMF network elements, AUSF network elements, SMF network elements, UDM network elements, UDR network elements, NRF network elements, NEF network elements, NSSF network elements, or PCF network elements interact with each other using service-oriented interfaces.
  • the service-oriented interface provided by the AMF network element to the outside may be Namf.
  • the service-oriented interface provided by the SMF network element to the outside may be Nsmf.
  • the service-oriented interface provided by the UDM network element to the outside may be Nudm.
  • the service-oriented interface provided by the UDR network element to the outside may be Nudr.
  • the service-oriented interface provided by the PCF network element to the outside may be Npcf.
  • the service-oriented interface provided by the NEF network element to the outside may be Nnef.
  • the service-oriented interface provided by the NRF network element to the outside may be Nnrf.
  • the service-oriented interface provided by the NSSF network element to the outside may be Nnssf.
  • the name of the interface between the network elements in FIG. 4a or FIG. 4b is only an example, and the name of the interface may be other names in a specific implementation, which is not specifically limited in the embodiment of the present application.
  • the access device, AF network element, AMF network element, SMF network element, AUSF network element, UDM network element, UPF network element, and PCF network element in Figure 4a or Figure 4b are just one name, and the name pair
  • the equipment itself does not constitute a limitation.
  • the network elements corresponding to the access equipment, AF network elements, AMF network elements, SMF network elements, AUSF network elements, UDM network elements, UPF network elements, and PCF network elements can also be other The name of this application does not specifically limit this.
  • the UDM network element may also be replaced with a user home server (home subscriber server, HSS) or user subscription database (user subscription database, USD) or a database entity, etc., which will be uniformly explained here and will not be repeated in the following .
  • HSS home subscriber server
  • USD user subscription database
  • the terminal, (R)AN, UPF, and DN in Figure 4a or Figure 4b are generally called user layer network functional entities.
  • the data traffic of the terminal can pass through the packet data unit (PDU) established between the terminal and the DN.
  • Session Session
  • Session is transmitted, and the transmission will pass through two network functions (entities) (R)AN and UPF; and the other parts are called control layer network functions and entities, which are mainly responsible for authentication and authentication, registration management, Functions such as session management, mobility management, and policy control enable reliable and stable transmission of user-level traffic.
  • the PDU session involved in the embodiments of this application refers to a connection (association between the UE and a Data Network that provides a PDU connectivity service) between the terminal and the data network to provide a PDU connection service.
  • Figures 4a and 4b show the system architecture of the terminal accessing the 5G network through the 3GPP access technology.
  • Figure 4c shows the terminal using multiple access technologies (for example, 3GPP access technology and non-3GPP access technology) in an embodiment of this application.
  • a schematic diagram of the architecture of the access network for example, the architecture of the terminal using 3GPP access technology and non-3GPP access technology.
  • the terminal can be connected to the access and mobility management function network element through 3GPP access technology and non-3GPP access technology.
  • a terminal when a terminal uses a non-3GPP access technology to access an AMF network element, it can access the AMF network element through a non-3GPP interworking function (N3IWF) entity.
  • N3IWF non-3GPP interworking function
  • the terminal selects the same AMF network element.
  • different AMF network elements can be selected.
  • the SMF network element is selected by the AMF network element, and different sessions (for example, PDU sessions) can select different SMF network elements, but the same SMF network element should be selected for the same session.
  • the SMF network element can select a UPF network element for the session, and a session can have multiple UPF network elements, so the SMF network element may select multiple UPF network elements to create a tunnel connection for a session.
  • the AUSF network element and the authentication storage function (ARPF)/UDM network element constitute the home public land mobile network (HPLMN).
  • HPLMN home public land mobile network
  • the terminal accesses the network through different access technologies, it can Having different visited public land mobile networks (VPLMN) may also have the same visited public land mobile network.
  • VPN visited public land mobile networks
  • the functions of each network element shown in FIG. 4c can be referred to the above-mentioned embodiments, and details are not described herein again in this application.
  • the access device (also referred to as an access network device) may include a host node and one or more IAB nodes.
  • the 3GPP access technology in the embodiment of the present application may be an access technology that complies with 3GPP standard specifications, for example, the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) access technology.
  • 3rd Generation Partnership Project 3rd Generation Partnership Project
  • the access network adopting the 3GPP access technology is called the radio access network (Radio Access Network, RAN).
  • the terminal can use the 3GPP access technology to access the wireless network through the access network equipment in the 5G system.
  • the access network device may be a base station.
  • the access network equipment in the 5G system is called Next Generation Node Basestation (gNB), evolved Node B (evolved Node B, eNB), and so on.
  • gNB Next Generation Node Basestation
  • eNB evolved Node B
  • eNB evolved Node B
  • the non-3GPP may be a wireless access technology that is not defined in the 3GPP standard specifications, for example, it is called a non-3rd Generation Partnership Project (non3rd Generation Partnership Project, non3GPP) access technology.
  • the non-3GPP access technology can be an untrusted non3GPP access technology or a trusted non3GPP access technology.
  • Non-3GPP access technologies may include: Wireless fidelity (Wi-Fi), Worldwide Interoperability for Microwave Access (WiMAX), Code Division Multiple Access (CDMA), Wireless Local Area Network ( Wireless Local Area Networks, WLAN), fixed network technology or wired technology, etc.
  • the terminal can access the network through the air interface technology represented by Wireless Fidelity (WIFI).
  • WIFI Wireless Fidelity
  • the access network device may be an access point (Access Point, AP).
  • FIGS 3a-3d are network architectures applied to embodiments of the present application. The functions of the various parts involved in the network architecture or the network elements in the 5G network are described below as examples.
  • the backhaul node in the embodiment of the present application may also be called a wireless backhaul node, a wireless backhaul device, a relay node (RN) or an IAB node (IAB node).
  • the IAB node may provide a wireless access service for the terminal, and the terminal's uplink data (for example, including uplink user plane data and uplink control plane signaling) is transmitted to the IAB node through the wireless access link. Then, the IAB node transmits the uplink data of the terminal or the uplink data from the child node to the host node 40 through the wireless backhaul link.
  • the downlink data of the terminal (including downlink user plane data and downlink control plane signaling) is sent by the donor node 40 to the IAB node through the wireless backhaul link, and then transmitted by the IAB node 10 to the terminal through the wireless access link.
  • the host node 40 is also called an IAB donor (IAB donor) or a donor backhaul node or a donor base station.
  • IAB donor IAB donor
  • the following embodiments will take the Donor node as an example for description.
  • the Donor node may be an evolved donor base station (Donor eNodeB, DeNB).
  • the donor node may be a next-generation donor base station (Donor gNodeB, DgNB).
  • Terminals can include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to wireless modems; they can also include subscriber units, cellular Telephone (cellular phone), smart phone (smart phone), wireless data card, personal digital assistant (personal digital assistant, PDA) computer, tablet computer, wireless modem (modem), handheld device (handheld), laptop computer ( laptop computer), cordless phone or wireless local loop (wireless local loop, WLL) station, machine type communication (MTC) terminal, user equipment (UE), mobile station (mobile station) , MS), terminal device (terminal device) or relay user equipment, etc.
  • the relay user equipment may be, for example, a 5G residential gateway (RG).
  • RG 5G residential gateway
  • the terminals in the embodiments of the present application may be terminals in various vertical industry application fields such as ports, smart factories, railway transportation, logistics, drones, and unmanned vehicles.
  • Mobile Robot Mobile Robot
  • Automated Guided Vehicle AGV
  • driverless cars control equipment and sensors on trains, and controls deployed in factories as shown in Figure 1-1 or Figure 2.
  • Equipment and sensors Sensors, etc.
  • the terminal may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for using wearable technology to intelligently design everyday wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a kind of hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones.
  • the terminal can also be a sensor device used in a factory.
  • the access device is used to provide network access functions for authorized terminals in a specific area, and can use transmission tunnels of different quality according to the level of the terminal and service requirements.
  • Access equipment can manage wireless resources, provide access services for terminal equipment, and then complete the forwarding of control signals and terminal equipment data between the terminal equipment and the core network.
  • the access equipment can also be understood as a base station in a traditional network. For example, it can be responsible for functions such as radio resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • QoS quality of service
  • the access device can be a device in a wireless network.
  • Access equipment may also be referred to as wireless access equipment or network equipment.
  • the terminal is connected to the radio access network (RAN) node of the wireless network.
  • some examples of access devices are: The Next Generation Node B (gNB) in the fifth generation (5G) system, the transmission reception point (TRP), and the LTE system Evolved Node B (evolved Node B, eNB), radio network controller (RNC), Node B (Node B, NB), base station controller (BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (BBU), or wireless fidelity (wireless fidelity, Wifi) access point (access point, AP) etc.
  • 5G Fifth Generation Node B
  • TRP transmission reception point
  • LTE LTE system
  • Evolved Node B evolved Node B
  • RNC
  • the network device may include a centralized unit (CU) node, or a distributed unit (DU) node, or a RAN device including a CU node and a DU node.
  • the access device can also be a wireless backhaul device, a vehicle-mounted device, a wearable device, and a network device in a future 5G network or a network device in a future evolved PLMN network.
  • 3G Third generation
  • Node B Node B
  • Mobility management network element which belongs to the core network network element, is mainly responsible for the signaling processing part, such as: access control, mobility management, attachment and detachment, and gateway selection functions.
  • the AMF network element When the AMF network element provides services for the session in the terminal, it will provide storage resources of the control plane for the session to store the session identifier, the SMF network element identifier associated with the session identifier, and so on.
  • the mobility management network element may be an AMF network element.
  • the mobility management network element may still be an AMF network element, or may also have other names, which is not limited in this application.
  • Untrusted non-3GPP Access Network (Untrusted non-3GPP Access Network) equipment
  • this network element allows the terminal and the 3GPP core network to use non-3GPP technology for interconnection and intercommunication, including non-3GPP technology such as wireless fidelity (WirelessFidelity, Wi-Fi), Worldwide Interoperability for Microwave Access (WiMAX), Code Division Multiple Access (CDMA) networks, etc., compared to trusted non-3GPP access network equipment Direct access to the 3GPP core network.
  • the network element needs to communicate with the 3GPP core network through a secure tunnel established by a security gateway.
  • the security gateway is for example: Evolved Packet Data Gateway (ePDG) or non-3GPP interworking function (Non-3GPP InterWorking Function, N3IWF) network element.
  • ePDG Evolved Packet Data Gateway
  • N3IWF Non-3GPP InterWorking Function
  • the session management network element is responsible for user plane network element selection, user plane network element redirection, internet protocol (IP) address allocation, bearer establishment, modification and release, and QoS control. Session management, terminal Internet protocol (IP) address allocation and management, selection of end points that can manage user plane functions, policy control and charging function interfaces, and downlink data notifications.
  • IP internet protocol
  • IP terminal Internet protocol
  • the session management network element may be an SMF network element.
  • the session management network element may still be an SMF network element, or may also have other names, which is not limited in this application.
  • the data plane module is responsible for the forwarding and receiving of user data in the terminal. It can receive user data from the data network and transmit it to the terminal device through the access network device; the data plane module can also receive user data from the terminal via the access network device and forward it to the data network.
  • the transmission resources and scheduling functions of the data plane module that provide services for the terminal are managed and controlled by the session management network element.
  • the data plane module can be a UPF network element or a UPF module.
  • the data plane module may still be a UPF network element or a UPF module, or may also have other names, which are not limited by this application.
  • the authentication server function network element mainly provides authentication functions and supports authentication of 3GPP access and Non-3GPP access.
  • 3GPP TS 33.501 3GPP TS 33.501.
  • the authentication server function network element may still be an AUSF network element, or may also have other names, which is not limited in this application.
  • NEF network elements mainly support the secure interaction between 3GPP networks and third-party applications. NEF can safely expose network capabilities and events to third parties to enhance or improve application service quality. 3GPP networks can also safely follow the third party. The three parties obtain relevant data to enhance the intelligent decision-making of the network; at the same time, the network element supports the restoration of structured data from the unified database or the storage of structured data in the unified database.
  • the UDR network element is mainly responsible for storing structured data.
  • the stored content includes contract data and policy data, structured data exposed to the outside, and application-related data.
  • the AF network element mainly supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side.
  • NRF Network storage network element, used to maintain real-time information of all network function services in the network.
  • NRF stores the information of deployed network function (NF) components, such as NF component identification and network address, supported network slice identification, or data plane instance information, etc.
  • NF network function
  • the network storage network element may still be an NRF network element, or may also have other names, which is not limited by this application.
  • network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform).
  • FIG. 5 shows a schematic diagram of the hardware structure of a communication device in an embodiment of the present application.
  • the structure of the session management network element 20, the IAB node 10, and the mobility management network element 40 can refer to the structure shown in FIG. 5.
  • the communication device includes a processor 51, a communication line 54 and at least one communication interface (in FIG. 5, the communication interface 53 is only used as an example for illustration).
  • the communication device may further include a memory 52.
  • the processor 51 may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more programs for controlling the execution of the program of this application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line 54 may include a path to transmit information between the aforementioned components.
  • the communication interface 53 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 52 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types that can store information and instructions
  • the dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk 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 codes in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.
  • the memory can exist independently and is connected to the processor through the communication line 54. The memory can also be integrated with the processor.
  • the memory 52 is used to store computer-executable instructions for executing the solution of the present application, and the processor 51 controls the execution.
  • the processor 51 is configured to execute computer-executable instructions stored in the memory 52, so as to implement a communication method provided in the following embodiments of the present application.
  • the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.
  • the processor 51 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 5.
  • the communication device may include multiple processors, such as the processor 51 and the processor 55 in FIG. 5.
  • processors can be a single-CPU (single-CPU) processor or a multi-core (multi-CPU) processor.
  • the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).
  • the specific structure of the execution body of a communication method is not particularly limited in the embodiment of this application, as long as the program recorded with the code of a communication method of the embodiment of this application can be run according to this application.
  • the communication method of the application embodiment can be used for communication.
  • the execution subject of the communication method provided in the embodiment of the application may be a functional module that can call and execute the program in the session management network element, or it may be applied to the session.
  • the communication device in the management network element for example, a chip.
  • the execution subject of the communication method provided by the embodiments of the present application may be a functional module in the IAB node that can call and execute the program, or a communication device, such as a chip, applied to the IAB node.
  • the execution subject of the communication method provided by the embodiment of the present application may be a functional module in the mobility management network element that can call and execute the program, or a communication device, such as a chip, applied to the mobility management network element.
  • the following embodiments are described by taking an example that the execution subject of a communication method is an IAB node, a mobility management network element, and a session management network element.
  • a communication method provided by an embodiment of the present application includes:
  • Step 601 The session management network element 20 determines the information of the target data plane instance.
  • the information of the target data plane instance includes routing instructions (for example, N4 Routing Indicator). Wherein, the route indication is used for the session management network element 20 to determine the address of the target data plane instance.
  • the target data plane instance is associated with the IAB node 10.
  • the session management network element 20 has a data plane instance set.
  • the data plane instance set at least includes information of one or more data plane instances corresponding to the data plane module 30.
  • the data plane instance set may also have information about instances of modules other than the data plane module.
  • the information of the one or more data plane instances can be registered to the session management network element 20 by the IAB node 10 through the Donor node 50 or the OAM network element 60 or the AMF network element.
  • the session management network element 20 in the embodiment of the present application may obtain information about one or more data plane instances from the NRF network element. For the specific process, see step 600 below.
  • step 601 in the embodiment of the present application can be implemented in the following manner: the session management network element 20 determines the information of the target data plane instance from the information of one or more data plane instances according to preset conditions.
  • the preset conditions are DNN, S-NSSAI, area ID of the session management network element 20, load and other information.
  • the Area ID of the session management network element 20 represents the identifier of the area managed by the session management network element.
  • DNN can reflect the type of service transmitted by the user plane of the terminal. To a certain extent, it can reflect the entrance location of the DN. Other conditions also reflect the service or location information.
  • the session management network element 20 refers to these factors and comprehensively selects the data plane that can support these services and the optimal location (short delay). The instance serves as the target data plane instance.
  • the address of the target data plane instance may be the address of the IAB node 10 or the identifier of the IAB node 10 (for example, a subscriber permanent identifier (SUPI)).
  • the association of the target data plane instance with the IAB node 10 can be understood as: the data plane module 30 corresponding to the target data plane instance is located inside the IAB node 10, or the data plane module 30 and the IAB node 10 corresponding to the target data plane instance are located in the same device.
  • the data plane module 30 in the embodiment of the present application has the functions of routing and forwarding.
  • the session management network element 20 may first determine the address or identifier of the IAB node 10 when addressing the target data plane instance. Then, the following step 602 is performed.
  • Step 602 The session management network element 20 sends an N4 session management request message and a first instruction to the mobility management network element 40 or the Donor node 50 that provides services for the IAB node 10, so that the mobility management network element 40 or the Donor node 50 receives the session
  • the N4 session management request message and the first instruction of the management network element 20 The first instruction is used to instruct the IAB node 10 to send an N4 session management request message to the target data plane instance.
  • the mobility management network element 40 or the Donor node 50 may also provide services for other devices. Or the mobility management network element 40 or the Donor node 50 only provides services for the IAB node 10, which is not limited in the embodiment of the present application.
  • the first indication may also be used to indicate the identifier of the data plane instance, or the session management network element 20 may also send the identifier of the target data plane instance to the IAB node.
  • This facilitates the IAB node 10 to determine to send the N4 session management request message to the target data plane instance associated with the identifier of the target data plane instance.
  • the N4 session management request message in the embodiment of the present application may be an N4 session establishment request message, and the N4 session establishment request message is used for request.
  • the N4 session management request message in the embodiment of the present application may be an N4 session deletion request message.
  • the N4 session management request message in the embodiment of the present application may be an N4 session modification (or update) request message,
  • the session management network element 20 establishes a connection with the target data plane instance through the N4 session establishment request, and the subsequent session management network element 20 issues user plane execution instructions and policy rules through the N4 interface.
  • the session management network element 20 modifies the policy rules and user plane execution instructions issued to the target data plane instance through the N4 session modification request message.
  • the session management network element 20 can delete the connection established between the session management network element 20 and the target data plane instance through the N4 session deletion request message.
  • the N4 session management request message in the embodiment of the present application mainly refers to the session management request message for the target data plane instance, and the N4 session management request message may also adopt other names.
  • Nx represents the interface between the session management network element 20 and the data plane module 30.
  • Step 603 The mobility management network element 40 or the Donor node 50 sends the N4 session management request message and the first instruction to the IAB node 10, so that the IAB node 10 receives the N4 session management request message from the mobility management network element 40 or the Donor node 50 and First instructions.
  • Step 604 The IAB node 10 sends an N4 session management request message to the target data plane instance according to the first instruction, and the N4 session management request message is used to instruct to manage the session context of the data plane instance.
  • the data plane module 30 to which the target data plane instance belongs in the embodiment of the present application can be integrated in the IAB node 10 as shown in FIG. 3a or FIG. 3c, that is, the IAB node 10 has the data plane module 30 to which the target data plane instance belongs.
  • the IAB node 10 may also belong to the same device as the data plane module 30 to which the target data plane instance belongs.
  • the IAB node 10 and the data plane module 30 corresponding to the target data plane instance are located in the same device as an example.
  • step 604 in the embodiment of the present application can be implemented in the following manner: the unit (MT part/DU part) in the IAB node 10 /CU-UP)
  • the N4 session management request message can be sent to the data plane module 30 through the internal interface.
  • the MT part can send the N4 session management request message to the data plane module 30 through the internal interface.
  • the MT part can send an N4 session management request message to the DU through an internal interface, and then the DU sends an N4 session management request message to the data plane module 30.
  • the transmission is through the E1 interface, the MT part can send the N4 session management request message to the CU-UP through the internal interface, and the CU-UP sends the N4 session management request message to the data plane module 30.
  • step 604 in the embodiment of the present application can be implemented in the following manner: the IAB node 10 can pass the interface Ny to The data plane module 30 sends an N4 session management request message.
  • the embodiment of the present application provides a communication method.
  • the session management network element determines the information of the target data plane instance, the information of the target data plane instance includes routing instructions. Therefore, the session management network element can determine the address of the target data plane instance according to the routing instructions, so that the session management network element can correctly address the target data plane instance. Since the target data plane instance is associated with the IAB node, the session management network element can send an N4 session management request message to the IAB node to realize the management of the target data plane instance. This solution can realize the registration and management of the target data plane instance brought by the wireless N4 interface.
  • the method provided in the embodiment of the present application may further include:
  • Step 605 The IAB node 10 sends a first message to the OAM network element/Donor node 50/mobility management network element 40, so that the network management network element 70/Donor node 50/mobility management network element 40 receives the first message.
  • the first message includes information about one or more data plane instances of the data plane module 30.
  • the first message is used to instruct the network management network element 70/Donor node 50/mobility management network element 40 to register information of one or more data plane instances with the network storage network element 80 or the session management network element 20.
  • the information of any data plane instance in the information of one or more data plane instances includes routing instructions; the routing instructions are used by the session management network element 20 to determine the address of any data plane instance; any data plane instance is associated with an IAB node .
  • the information of any data plane instance may also include any one or more of the following information: type information used to indicate the data plane instance, or configuration information of the data plane instance.
  • the type information used to indicate the data plane instance may be a data plane type (for example, a UPF type).
  • the configuration information of the data plane instance may include any one or more of the following information: such as DNN, S-NSSAI, SMF Area ID and other information.
  • the first message itself has the meaning or function of instructing the network management network element 70/Donor node 50/mobility management network element 40 to register one or more first data plane instances with the network storage network element 80
  • the registration indication may not be carried in the first message. Of course, the registration indication may also be carried in the first message.
  • the first message carries Registration instructions. The registration instruction is used to instruct the network management network element 70/Donor node 50/mobility management network element 40 to register information of one or more data plane instances with the network storage network element 80.
  • the IAB node 10 can display or implicitly instruct the network management network element 70/Donor node 50/mobility management network element 40 to register one or more data plane instances with the network storage network element 80 or the session management network element 20. information.
  • Example 1-1) New IE type (display indication).
  • the first message includes a payload container (Payload Container), which may also be referred to as an instance registration container (Register Container).
  • the Payload Container includes the information of one or more data plane instances, and the type of the Payload Container is used to instruct the first device to register the information of one or more data plane instances with the session management network element 20 or the NRF network element. That is, if the information of one or more data plane instances needs to be transmitted in the Payload Container, the type of Payload Container that needs to be defined is used to instruct the first device to register one or more data plane instances with the session management network element 20 or the NRF network element Information.
  • the first message includes a load container and a field for indicating the type of the load container.
  • the first message has the function of carrying a load container.
  • the first message is a NAS message.
  • Example 1-2 new IE field (display indication).
  • the first message includes a registration indication and information of one or more data plane instances.
  • the registration indication is used to instruct the first device to register one or more data plane instances with the session management network element 20 or the network storage network element 80.
  • Example 1-3 implicit indication.
  • step 605 in the embodiment of the present application can be implemented in the following manner: the IAB node 10 sends a first message to the first device through a predefined operation interface, so that the first device performs a predefined operation The interface receives the first message.
  • Example 1-1) to Example 1-3 can be indicated separately or combined.
  • Step 606 The network management network element 70/Donor node 50/mobility management network element 40 registers information of one or more data plane instances with the network storage network 80 or the session management network element 20 according to the first message. In this way, the network storage network 80 or the session management network element 20 receives information about one or more data plane instances of the data plane module, and the one or more data plane instances include the target data plane instance.
  • FIG. 7 only illustrates the process in which the IAB node sends the first message to the mobility management network element 40, and the mobility management network element 40 registers the information of one or more data plane instances with the network storage network 80.
  • Example 2-1 A process in which the IAB node 10 registers the information of one or more data plane instances with the network storage network 80 through the network management network element 70.
  • the IAB node 10 sends information about one or more data plane instances to the network management network element 70 through the user plane connection with the network management network element 70.
  • step 606 in the embodiment of the present application can be implemented in the following manner: the network management network element 70 can directly send to the network storage network 80 Load container.
  • step 606 in the embodiment of the present application can be implemented in the following manner: the network management network element 70 is based on the definition between the network management network element 70 and the network storage network 80 Interface construction instance registration information. Among them, the instance registration information includes information about one or more data plane instances.
  • the network management network element 70 sends instance registration information to the network storage network 80. That is, one or more data plane instances are processed by the mobility management network element and sent to the session management network element 20 or the network storage network element 80.
  • Example 2-2 A process in which the IAB node 10 registers the information of one or more data plane instances with the session management network element 50 or the network storage network 80 through the mobility management network element 40.
  • the first message may be an N1 NAS message.
  • Step 606 in the embodiment of the present application can be implemented in the following manner:
  • the interface defined between the management network element 40 and the network storage network 80 sends load containers to the network storage network 80.
  • the mobility management network element 40 sends the fourth message to the network storage network 80 through the interface defined between the mobility management network element 40 and the network storage network 80.
  • the fourth message carries the load container.
  • the mobility management network element 40 sends the load container to the session management network element 20 through the interface defined between the mobility management network element 40 and the session management network element 20, or sends a third message to the session management network element 20.
  • the third message includes the load container.
  • step 606 in the embodiment of the present application can be implemented in the following manner: the mobility management network element 40 is defined between the mobility management network element 40 and the network storage network 80 The interface of ”sends a fourth message to the network storage network 80. At this time, the fourth message carries information about one or more data plane instances.
  • the mobility management network element 40 sends the third message to the session management network element 20 through an interface defined between the mobility management network element 40 and the session management network element 20. Wherein, the third message carries information about one or more data plane instances.
  • Example 2-3 A process in which the IAB node 10 registers the information of one or more data plane instances with the session management network element 50 or the network storage network 80 through the host node 50.
  • the first message may be an F1 message or an E1 message.
  • the step 605 provided in the embodiment of the present application can be implemented in the following manner: the IAB node 10 sends an F1 message or an E1 message to the Donor node 50, so that The Donor node 50 receives the F1 message or the E1 message.
  • the F1 message or the E1 message carries the registration indication and the load container.
  • the F1 message or E1 message carries a load container.
  • the Donor node 50 sends a second message to the mobility management network element 40 according to the registration instruction or the load container, so that the mobility management network element 40 receives the second message from the Donor node 50.
  • the second message carries the load container and the third instruction.
  • the third instruction is used to instruct the mobility management network element 40 to register information about one or more data plane instances with the session management network element 20 or the network storage network 80.
  • the mobility management network element 40 sends the load container to the session management network element 20 or the network storage network 80 according to the second message.
  • Example 2-3 Regarding the process of registering information of one or more data plane instances with the session management network element 20 or the network storage network 80 after the mobility management network element 40 receives the load container in Example 2-3, refer to the description in Example 2-2 above. I won't repeat them here.
  • the method may further include:
  • Step 600 The session management network element 10 obtains information about one or more data plane instances from the network storage network element 80, and the one or more data plane instances include the target data plane instance.
  • step 600 in the embodiment of the present application, reference may be made to the specific implementation of step 1201 below, which will not be repeated here.
  • step 602 Since the context of the IAB node exists or does not exist locally in the session management network element 20, the specific implementation of step 602 is different, so the following will be introduced separately:
  • Example 3-1) The context of the IAB node exists locally in the session management network element 20.
  • the method provided in the embodiment of the present application may further include:
  • Step 607 The session management network element 20 determines that the context of the IAB node locally exists in the session management network element.
  • step 602 provided in the embodiment of the present application can be specifically implemented in the following manner:
  • Step 6021 the session management network element 20 generates a session management non-access stratum (NAS) message according to the context of the IAB node.
  • the session management NAS layer message includes an N4 session management request message and a first instruction.
  • Step 6022 the session management network element 20 sends a session management NAS layer message to the IAB node through the mobility management network element 40, so that the mobility management network element 40 receives the session management NAS layer message from the session management network element 20.
  • step 603 can be specifically implemented in the following manner: the mobility management network element 40 sends a session management NAS layer message to the IAB node 10, so that the IAB node 10 receives the session management NAS layer message.
  • the solution shown in FIG. 7 can be applied to the scenario of a single mobility management network element and a single session management network element, that is, the mobility management network element selected by the terminal and the session management network element and the IAB node 10 are selected.
  • the mobility management network element and the session management network element are the same.
  • the terminal and the session management network element 20 use session management (SM) NAS messages to interact.
  • SM session management
  • the mobility management network element 40 forwards the session management-related NAS messages to the session management network element 20, and subsequently
  • the session management network element 20 sends the corresponding response message to the mobility management network element 40, and the mobility management network element 40 forwards it to the terminal through the NAS message.
  • the terminal and the mobility management network element 40 use mobility management (Mobility Management, MM) NAS messages to interact. Specifically, after the mobility management network element 40 receives the MM NAS message, it directly processes it, and the corresponding response message is also directly passed through The NAS forwards to the terminal.
  • mobility management Mobility Management
  • Example 3-2 The context of the IAB node does not exist locally in the session management network element 20.
  • Step 608 The session management network element 20 determines that the context of the IAB node does not exist locally in the session management network element.
  • the method provided in this embodiment of the present application may further include before step 603:
  • Step 609 The session management network element 20 sends a routing instruction to the mobility management network element 40, so that the mobility management network element 40 receives the routing instruction from the session management network element 20.
  • the routing instruction may be carried in the same message as the N4 session management request message and the first instruction and sent to the mobility management network element 40.
  • Step 610 After the mobility management network element 40 determines that the mobility management network element locally has the context of the IAB node according to the routing instruction, the mobility management network element 40 generates a mobility management NAS message according to the context of the IAB node.
  • the mobility management NAS message includes an N4 session management request message and a first indication.
  • the mobility management network element 40 may also send confirmation information to the session management network element 20.
  • the confirmation information is used to indicate that the mobility management network element has the context of the IAB node locally.
  • step 610 provided in the embodiment of the present application can also be replaced in the following manner: the mobility management network element 40 directly generates a mobility management NAS message according to the routing instruction, that is, the mobility management network element 40 does not need to determine whether there is a context of an IAB node.
  • the session management network element 20 can determine according to the confirmation information that the mobility management network element 40 can provide services for the IAB node.
  • step 603 in the embodiment of the present application may be specifically implemented in the following manner: the mobility management network element 40 sends a mobility management NAS message to the IAB node 10.
  • the session management network element selected by the terminal is different from the session management network element selected by the IAB node 10
  • the mobile management network element selected by the terminal Unlike the mobility management network element selected by the IAB node 10, in a possible embodiment, as shown in FIG. 8, the method provided in the embodiment of the present application may further include before step 609:
  • Step 611 The session management network element 20 obtains the information of the mobility management network element of the IAB node 10 from the user data management network element.
  • the user data management network element may be a UDM network element or a UDR network element.
  • the information of the mobility management network element 40 may be the address or identification or location of the mobility management network element 40.
  • the method provided by the embodiment of the present application may further include: the session management network element 20 provides a first mobility management network element (for example, the first mobility management network element is a mobility management network that provides services for the terminal). Element) to send indication information for verifying whether the first mobility management network element locally has the context of the IAB node. If the first mobility management network element does not have the context of the IAB node locally, the first mobility management network element sends a message to the session management network. The element sends an indication for indicating that the first mobility management network element does not have the context of the IAB node locally, so that the session management network element can perform step 611 to determine the information of the mobility management network element accessed by the IAB node.
  • the session management network element 20 provides a first mobility management network element (for example, the first mobility management network element is a mobility management network that provides services for the terminal). Element) to send indication information for verifying whether the first mobility management network element locally has the context of the IAB node. If the first mobility management network element does not have the
  • step 611 can be implemented in the following manner:
  • the information (such as identifier, location, etc.) of the mobility management network element 40 can be queried through the existing UDM query interface; (2) ) If the routing instructions are other identifiers of the IAB node 10 (other identifiers can be, for example, those that can uniquely identify the IAB node), the existing UDM query method can be enhanced to directly query the user data management network element for the mobile management network element through the routing instruction (3) If the routing indication is the other identifier of the IAB node 10, the session management network element 20 can first determine the SUPI of the IAB node 10 according to the other identifiers of the IAB node 10, and then use SUPI to manage the network element from the user data Obtain the information of the mobility management network element 40.
  • SUPI the identifier of the IAB node 10
  • the session management network element 20 has a mapping relationship between the other identifiers of the IAB node 10 and the SUPI, and the session management network element 20 can determine the SUPI of the IAB node 10 according to the mapping relationship. Or the user data management network element has the mapping relationship, and the session management network element 20 sends other identifiers of the IAB node 10 to the user data management network element to obtain the SUPI of the IAB node 10 from the user data management network element.
  • step 611 can be omitted.
  • the method provided in the embodiment of the present application further includes: the session management network element 20 sends The Donor node 50 sends a routing instruction, so that the Donor node 50 receives the routing instruction from the session management network element 20.
  • the Donor node 50 sends the N4 session management request message and the first instruction to the IAB node 20 according to the routing instruction.
  • the Donor node 50 sends an F1/E1 message to the IAB node 20 according to the routing instruction.
  • the F1/E1 message includes the N4 session management request message and the first indication.
  • the session management network element 20 sends a routing instruction to the Donor node 50 through the mobility management network element 40. It should be understood that the routing instruction and the N4 session management request message and the first instruction may be carried in the same message and sent to the Donor node 50 by the session management network element 20 through the mobility management network element 40.
  • the method provided in this embodiment of the present application may further include:
  • Step 612 The target data plane instance sends an N4 session management response message to the IAB node 10, so that the IAB node 10 receives the N4 session management response message sent by the target data plane instance.
  • the N4 session management response message may include: confirmation information (for example, ACK), indicating the result of the operation, taking the establishment request as an example, informing the session management network element of which strategies and execution instructions are successfully deployed and which cannot be deployed.
  • Step 613 The IAB node 10 sends the second instruction and the N4 session management response message to the Donor node 50 or the mobility management network element 40, so that the Donor node 50 or the mobility management network element 40 receives the second instruction and the N4 session management response message .
  • the second instruction is used to instruct to send an N4 session management response message to the session management network element 20.
  • Step 614 The Donor node 50 or the mobility management network element 40 sends an N4 session management response message to the session management network element 20 according to the second instruction, so that the session management network element 20 receives the N4 session management from the data plane instance through the IAB node 10. Response message.
  • step 614 can be implemented in the following manner: the Donor node 50 sends F1 to the mobility management network element 40 according to the second instruction Message or E1 message, so that the mobility management network element 40 receives the F1 message or the E1 message.
  • the F1 message or E1 message includes the third indication and the N4 session management response message.
  • the mobility management network element 40 sends an N4 session management response message to the session management network element 20 according to the third instruction.
  • the third instruction is used to instruct the session management network element 20 to send an N4 session management response message.
  • the content of the third instruction may be the same as the content of the second instruction.
  • the content of the third instruction may be different from that of the second instruction.
  • the second instruction is used to instruct the Donor node 50 to send the N4 session management response message of the data plane instance to the session management network element 20.
  • the third instruction is used to instruct the mobility management network element 40 to send the N4 session management response message of the data plane instance to the session management network element 20.
  • the data plane module 30 is the UPF module
  • the data plane instance is the UPF instance
  • the session management network element 20 is the SMF network element
  • the network management network element 70 is the OAM network element
  • the network storage network element 80 is the NRF network element.
  • Step 901 The IAB node and the OAM network element establish a user plane connection.
  • the IAB node as a terminal establishes a user plane connection with the OAM network element through a session establishment request.
  • the IAB node can obtain various IAB node-related configuration information from the OAM network element through the user plane connection.
  • the user plane connection will always be maintained for the IAB node to upload status information, etc.
  • the status information can be running status, such as load.
  • Step 902 The IAB node sends the UPF instance information to the OAM network element through the user plane connection, so that the OAM network element receives the UPF instance information from the IAB node through the user plane connection.
  • the IAB node sends user plane data (User plane data) to the OAM network element through the user plane connection.
  • user plane data User plane data
  • the information of the UPF instance specifically includes: Indication (that is, the above-mentioned first indication), which instructs the OAM network element to receive the information of the UPF instance and actively register the information of the UPF instance to the NRF network element.
  • the information of the UPF instance includes: network function type (NF type), used to determine the type of the UPF instance as UPF; N4 routing indicator (that is, the above-mentioned routing indicator), used for the SMF network element to correctly address the UPF Instance.
  • NF type network function type
  • N4 routing indicator that is, the above-mentioned routing indicator
  • UPF Provisioning Information other configuration information of the UPF instance, such as DNN, S-NSSAI, SMF Area ID and other information.
  • Step 903 The OAM network element constructs UPF instance registration information according to the interface defined between the OAM network element and the NRF network element.
  • the registration information includes: NF Type, N4 Routing Indicator and UPF Provisioning Information.
  • Step 904 The OAM network element sends registration information to the NRF network element, so that the NRF network element receives the registration information from the OAM network element.
  • the UPF instance information can be registered with the NRF network element.
  • the NRF network element in FIG. 9 can also be replaced with an SMF network element. After the NRF network element is replaced by the SMF network element, that is, the IAB node registers the data plane instance with the SMF network element through the OAM network element.
  • the data plane module is the UPF module
  • the data plane instance is the UPF instance
  • the session management network element is the SMF network element.
  • Figure 10 takes the IAB node to register with the NRF network element or SMF network element through the AMF network element.
  • the data plane instance is described in detail as an example.
  • the data plane instance registration process involved in the communication method of this application is shown in Figure 10, and the method includes:
  • Step 1001. The IAB node sends a N1 NAS message to the AMF network element, so that the AMF network element receives the N1 NAS message from the IAB node.
  • the N1 NAS message includes indication and UPF instance information. Indication is used to instruct the AMF network element to send the information of the UPF instance to the NRF network element or the SMF network element through the corresponding servicing interface.
  • the content in the UPF instance registration container is transparently transmitted at the AMF network element, that is, the AMF network element does not parse the specific content of the UPF instance registration container. That is, the N1 NAS message includes Indication and UPF instance registration container (UPF Register Container).
  • the N1 NAS message includes indication and UPF instance information.
  • the AMF network element uses option 1 (including step 1002a or step 1002b) to send the information of the UPF instance to the NRF network element or the SMF network element. If the AMF network element resolves the UPF instance, the AMF network element uses method 2 (including step 1003 and step 1004a, or step 1003 and step 1004b) to send the information of the UPF instance to the NRF network element or the SMF network element.
  • Step 1002a The AMF network element sends an N11 message (Message, Msg) to the SMF network element according to the Indication, so that the SMF network element receives the N11 message from the AMF network element.
  • the N11 message carries the UPF instance registration container.
  • the AMF network element registers the information of the UPF instance with the SMF network element.
  • the SMF network element does not have a service interface that provides this function. It is necessary to add a service interface that provides this function between the AMF network element and the SMF network element ( Namely N11 interface, referred to as N11).
  • Step 1002b The AMF network element sends a network function management registration message (NF Management NF register) to the NRF network element according to the Indication, so that the SMF network element receives the network function management registration message from the AMF network element.
  • the network function management registration message carries the UPF instance registration container.
  • the AMF network element Since the AMF network element registers the UPF instance information with the NRF network element, the current NRF network element does not have a service interface that provides this function. It is necessary to add a service interface that provides this function between the AMF network element and the NRF network element.
  • Step 1003 The AMF network element constructs UPF instance registration information according to Indication. If the AMF network element registers the information of the UPF instance with the SMF network element, the UPF instance registration information is the N11 message. If the AMF network element registers the information of the UPF instance with the NRF network element, the UPF instance registration information is NF Management NF register.
  • Step 1004a The AMF network element sends an N11 message to the SMF network element, so that the SMF network element receives the N11 message from the AMF network element, where the N11 message includes NF Type, N4 Routing Indicator, and UPF Provisioning Information.
  • Step 1004b The AMF network element sends the NF Management NF register to the NRF network element, so that the SMF network element receives the NF Management NF register from the AMF network element.
  • NF Management NF register includes NF Type, N4 Routing Indicator and UPF Provisioning Information.
  • Option2 can perceive the specific information of the UPF instance and support the proxy registration function. If it is to register with the SMF network element, it needs to register through the new interface; if it is to register with the NRF network element, Then directly call the service interface to register the information of the UPF instance.
  • the solution for the AMF network element or OAM network element to directly register the information of the UPF instance with the SMF network element is applicable to the scenario of a single AMF network element/single SMF network element, if multiple AMF network elements or multiple SMF network elements are involved. , You need to register the UPF instance information with the NRF network element.
  • the data plane module is the UPF module
  • the data plane instance is the UPF instance
  • the session management network element is the SMF network element.
  • Figure 11 takes the IAB node to register data with the NRF network element or SMF network element through the host node.
  • the plane instance is described in detail as an example.
  • the registration process of the data plane instance involved in the communication method of this application is shown in Figure 11, and the method includes:
  • Step 1101. The IAB node sends the UPF instance registration information to the Donor node through the F1 message or the E1 message, so that the Donor node receives the F1 message or the E1 message from the IAB node.
  • the F1 message or the E1 message mainly includes Indication1 and UPF Register Container.
  • Indication1 indicates that the Donor node receives the information of the UPF instance and forwards the information of the UPF instance to the AMF network element.
  • the Donor node does not parse the specific content in the UPF Register Container.
  • the Donor node can parse the information of the UPF instance.
  • Step 1102 The Donor node sends an N2 NGAP message to the AMF network element according to Indication1, so that the AMF network element receives the N2 NGAP message from the Donor node.
  • the N2 NGAP message carries UPF Register Container and Indication2.
  • Indication2 is used to instruct the AMF network element to send the UPF Register Container to the SMF network element or the NRF network element.
  • Indication2 can be exactly the same as Indication1. In this case, different network elements process the instructions according to their own processing logic after receiving the instructions.
  • the AMF network element adopts option 3 (including step 1103a or step 1103b) to send the information of the UPF instance to the NRF network element or the SMF network element. If the AMF network element resolves the UPF instance, the AMF network element adopts method 4 (including step 1104 and step 1105a, or step 1104 and step 1105b) to send the information of the UPF instance to the NRF network element or the SMF network element.
  • Step 1103a is the same as step 1002a.
  • Step 1103b is the same as step 1002b.
  • Step 1104 The AMF network element constructs UPF instance registration information according to Indication2. It is the same as the description at step 1003, and will not be repeated here.
  • Step 1105a is the same as step 1004a.
  • Step 1105b is the same as step 1004b.
  • the method includes:
  • Step 1201 The terminal sends a session establishment request (session establishment request) message to the SMF network element, so that the SMF network element receives the session establishment request message from the terminal.
  • the session establishment request message is used to request the SMF network element to establish a session for the terminal.
  • the session establishment request message carries single network slice selection assistance information (S-NSSAI), data network name (DNN), session identifier, or request type (Request type) At least one of them is not specifically limited in the embodiment of the present application.
  • the session establishment request message may also carry the original session identifier.
  • FIG. 12 takes the session establishment process as an example.
  • the session establishment request message can be replaced by the session modification request message.
  • step 1201 For the specific implementation of step 1201, reference may be made to the description in the prior art, which will not be repeated here.
  • Step 1202a The SMF network element sends a network function discovery request (Nnrf_NFDiscovery_Request) to the NRF network element through the Nnrf servicing interface, so that the NRF network element receives the Nnrf_NFDiscovery_Request from the SMF network element.
  • Nnrf_NFDiscovery_Request carries constraint conditions.
  • the constraint conditions are information such as dedicated DNN and location.
  • the location here may be the location of the terminal or the location of the DN access point.
  • Step 1203a The NRF network element sends a network function discovery response (Nnrf_NFDiscovery_Response) through the Nnrf servicing interface SMF network element, so that the SMF network element receives the Nnrf_NFDiscovery_Response from the NRF network element.
  • Nnrf_NFDiscovery_Response carries information about one or more first UPF instances.
  • the information of any UPF entity includes N4 routing instructions.
  • step 1202a can be replaced by the following step 1202b
  • step 1203a can be replaced by the following step 1203b.
  • Step 1202b The SMF network element sends a network function management status subscription request (Nnrf_NFManagement_NFStatusSubscribe) to the NRF network element through the Nnrf service interface, so that the NRF network element receives the Nnrf_NFManagement_NFStatusSubscribe from the SMF network element.
  • Nnrf_NFManagement_NFStatusSubscribe a network function management status subscription request
  • Nnrf_NFManagement_NFStatusSubscribe carries constraint conditions.
  • Step 1203b The NRF network element sends a network function management status notification (Nnrf_NFManagement_NFStatusNotify) through the Nnrf service interface SMF network element, so that the SMF network element receives the Nnrf_NFManagement_NFStatusNotify.
  • Nnrf_NFManagement_NFStatus Notify carries information about one or more first UPF instances.
  • the information of any UPF entity includes N4 routing instructions.
  • step 1202b-step 1203b requires the SMF network element to subscribe to the NRF network element first.
  • the NRF network element will actively notify the SMF network element .
  • step 1202a-step 1203a the NRF network element directly responds to the query request of the SMF network element.
  • Step 1204 The SMF network element selects an optimal UPF instance from one or more UPF instances.
  • the SMF network element selects the best UPF instance according to the restriction conditions such as DNN, load, location and other information and selection strategy/algorithm. If the selected UPF instance includes N4 Routing Indicator, and it is verified that the SMF network element locally has an IAB node context based on this information, an N4 session establishment message is sent through a NAS message.
  • the restriction conditions such as DNN, load, location and other information and selection strategy/algorithm.
  • Step 1205 The SMF network element transmits the communication N1N2 message (Namf_Communication_N1N2MessageTransfer) to the AMF network element through the Namf service interface, so that the AMF network element receives the Namf_Communication_N1N2MessageTransfer.
  • N1N2 message Namf_Communication_N1N2MessageTransfer
  • Namf_Communication_N1N2MessageTransfer carries Indication3 and N4 session establishment request, and the Indication3 is used to instruct the IAB node to submit the N4 session establishment request to the UPF instance selected by the SMF network element.
  • the IAB node first submits the N4 session establishment request to the UPF module. If the UPF module has multiple UPF instances, the UPF module sends the N4 session establishment request to the UPF instance selected by the SMF network element.
  • Step 1206 The AMF network element sends a N1 NAS message (that is, a session management NAS message) to the IAB node, so that the IAB node receives the N1 NAS message from the AMF network element.
  • the N1 NAS message includes Indication3 and N4 session establishment requests.
  • Step 1207 The IAB node sends the N4 session establishment request to the UPF instance selected by the SMF network element according to Indication3.
  • Step 1208 The IAB node receives the N4 session establishment response message from the UPF instance.
  • Step 1209 The IAB node sends a N1 NAS message to the AMF network element, so that the AMF network element receives the N1 NAS message.
  • the N1 NAS message includes the N4 session establishment response message and Indication4.
  • Indication4 is used to indicate to send an N4 session establishment response message to the SMF network element.
  • Step 1210 The AMF network element sends the N11 message to the SMF network element according to Indication4, so that the SMF network element receives the N11 message.
  • the N11 message includes the N4 session establishment response message.
  • step 1210 The process of establishing a terminal session after step 1210 can refer to the description of the prior art.
  • Figure 12 is mainly for the scenarios of a single AMF network element and a single SMF network element.
  • the process reflects the process of establishing an N4 session through N1, but the N4 session establishment request involved in Figure 12 can be replaced by an N4 session modification request or an N4 session deletion request .
  • the N4 session establishment response message can be replaced by the N4 session modification response message or the N4 session deletion response message.
  • Figure 13 shows the process of addressing the UPF instance by the SMF network element when the SMF network elements selected by the terminal and the IAB node are different for a single AMF network element and multiple SMF network element scenarios.
  • the difference from Fig. 12 is that there is no IAB node context locally in the SMF network element.
  • the method includes:
  • Step 1301 to step 1304 are the same as step 1201 to step 1204, and will not be repeated here.
  • the SMF network element selects the best UPF instance according to the restriction conditions such as DNN, load, location and other information and selection strategy/algorithm. If the selected UPF instance includes N4 Routing Indicator, and according to this information, it is verified that there is no IAB node context locally in the SMF network element, then step 1305 is executed.
  • Step 1305 The SMF network element sends an N11 message to the AMF network element, so that the AMF network element receives the N11 message from the SMF network element.
  • the N11 message includes: Indication3, N4 routing instructions, and N4 session establishment request.
  • Step 1306 The AMF network element checks that there is an IAB node context locally according to Indication3, and then constructs a mobility management NAS message. Among them, the mobility management NAS message carries Indication3 and the N4 session establishment request.
  • Step 1307 The AMF network element sends a mobility management NAS message to the IAB node, so that the AMF network element receives the mobility management NAS message.
  • Step 1308-Step 1311 are the same as Step 1207-Step 1210, and are the same as the above description, and will not be repeated here.
  • Figure 14 is mainly for the scenario of multiple AMF network elements and multiple SMF network elements.
  • the AMF network element and SMF network element selected by the terminal and the IAB node are different.
  • the process of the SMF network element addressing the UPF instance The difference between this method and the embodiment shown in FIG. 13 lies in:
  • Step 1401 to step 1404 are the same as step 1301 to step 1304, and will not be repeated here.
  • the SMF network element selects the best UPF instance according to the restriction conditions such as DNN, load, location and other information and selection strategy/algorithm. If the selected UPF instance includes N4 Routing Indicator, and according to this information, it is verified that there is no IAB node context locally in the SMF network element, then step 1405 is executed.
  • Step 1405 The SMF network element queries the UDM network element for the information of the MT-AMF network element (AMF network element serving the IAB node). For example, the SMF network element provides the N4 Routing Indicator to the UDM network element.
  • Step 1406 After obtaining the information of the MT-AMF network element serving the IAB node, the SMF network element sends an N4 session message to the AMF network element through the servicing interface, instructing the MT-AMF network element to construct a NAS message.
  • the MT-AMF network element receives the N4 Routing Indicator (for example, SUPI) and verifies that there is an IAB node context locally After that, construct the mobility management NAS message and pass it to the IAB node.
  • N4 Routing Indicator for example, SUPI
  • Step 1407-step 1412 are the same as steps 1306-step 1311, and are the same as the above description, and will not be repeated here.
  • Figure 15 mainly establishes an N4 session through F1/E1+N2, but the N4 session message transfer process is also applicable to the N4 session modification and deletion process.
  • the key differences from Embodiment 12 are as follows:
  • Steps 1501-step 1504 are the same as steps 1201-step 1204, and will not be repeated here.
  • the SMF network element constructs a message sent to the Donor node, and the Donor node forwards it to the IAB node.
  • Step 1505 The SMF network element constructs a message to be sent to the Donor node.
  • the message sent to the Donor node includes: indication 1, N4 session establishment request message, and N4 Routing Indicator.
  • Step 1506 The SMF network element transmits the communication N1N2 message (Namf_Communication_N1N2MessageTransfer) to the AMF network element through the Namf service interface, so that the AMF network element receives the Namf_Communication_N1N2MessageTransfer.
  • the communication N1N2 message carries the message constructed by the SMF network element and sent to the Donor node.
  • Step 1507 The AMF network element sends an N2 message to the host node, so that the host node receives the N2 message from the AMF network element.
  • the N2 message carries the message constructed by the SMF network element and sent to the Donor node.
  • the N2 message directly carries the indication 1, the N4 session establishment request message, and the N4 Routing Indicator.
  • Step 1508 The host node determines the address of the UPF instance selected by the SMF network element according to the N4 Routing Indicator.
  • Step 1509 The host node sends an F1/E1 message to the IAB node, so that the IAB node receives the F1/E1 message.
  • the F1/E1 message carries indication 1, N4 session establishment request message.
  • Step 1510 The IAB node sends an N4 session establishment request message to the UPF instance selected by the SMF network element according to the instruction 1, so that the UPF instance selected by the SMF network element receives the N4 session establishment request message.
  • Step 1511 The IAB node receives the N4 session establishment response message from the UPF instance.
  • Step 1512 The IAB node sends an F1/E1 message to the host node, so that the host node receives the F1/E1 message.
  • the F1/E1 message carries an indication 4, N4 session establishment response message.
  • indication 4 that is, the above-mentioned second indication
  • Step 1513 The host node sends an N2 message to the AMF network element according to the instruction 4, so that the AMF network element receives the N2 message.
  • the N2 message carries indication 4 and an N4 session establishment response message.
  • the N2 message carries indication 5 and a response message for N4 session establishment.
  • indication 5 is used to instruct the AMF network element to send an N4 session establishment response message to the SMF network element.
  • Step 1514 The AMF network element sends the N11 message to the SMF network element according to the instruction 4 or the instruction 5, so that the SMF network element receives the N11 message.
  • the N11 message carries the N4 session establishment response message.
  • each network element such as a session management network element, a mobility management network element, an IAB node, etc.
  • each network element such as a session management network element, a mobility management network element, an IAB node, etc.
  • each network element includes hardware structures and/or software modules corresponding to each function in order to realize the above functions.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiments of the present application can divide the functional units according to the above-mentioned method examples, session management network elements, mobility management network elements, and IAB nodes.
  • each functional unit can be divided corresponding to each function, or two or more functions can be integrated.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 16 shows a communication device involved in the foregoing embodiment, and the communication device may include: a communication unit 102 and a processing unit 101.
  • the communication device is a session management network element, or a chip applied to the session management network element.
  • the communication unit 102 is configured to support the communication device to execute step 601 in FIG. 6 by the session management network element in the foregoing embodiment.
  • the communication unit 102 is configured to support the communication device to perform the action sent by the session management network element in step 602 in the foregoing embodiment.
  • the communication unit 102 is further configured to support the communication device to execute the receiving action performed by the session management network element in step 606 and step 614 in the foregoing embodiment, or step 600 and step 611.
  • the processing unit 101 is further configured to support the communication device to execute step 607 and step 6021 in the foregoing embodiment.
  • the communication unit 102 is further configured to support the communication device to execute the sending action performed by the session management network element in step 6022 in step 609 in the foregoing embodiment.
  • the communication device is a mobility management network element, or a chip applied to a mobility management network element.
  • the communication unit 102 is configured to support the communication device to perform the action received by the mobility management network element in step 602 in the foregoing embodiment.
  • the communication unit 102 is configured to support the communication device to perform the action sent by the mobility management network element in step 603 in the foregoing embodiment.
  • the communication unit 102 is also used for the communication device to execute the actions received by the mobility management network element in step 605, step 6022, and step 609 in the foregoing embodiment.
  • the communication unit 102 is also used for the communication device to execute the actions sent by the mobility management network element in step 606 and step 614 in the foregoing embodiment.
  • the processing unit 101 is further used for the communication device to execute step 610 in the foregoing embodiment.
  • the communication unit 102 is also used for the communication device to execute the action received by the mobility management network element in step 613 in the foregoing embodiment.
  • the communication device is the Donor node 50 or a chip applied to the Donor node 50.
  • the communication unit 102 is configured to support the communication device to perform the action sent by the Donor node 50 in step 603 in the foregoing embodiment.
  • the communication unit 102 is configured to support the communication device to perform the action received by the Donor node 50 in step 602 of the foregoing embodiment.
  • the communication unit 102 is also used for the communication device to execute the action received by the Donor node 50 in step 605 in the foregoing embodiment.
  • the communication unit 102 is also used for the communication device to execute the actions sent by the Donor node 50 in step 606 and step 614 in the foregoing embodiment.
  • the communication unit 102 is also used for the communication device to execute the action received by the Donor node 50 in step 613 in the foregoing embodiment.
  • the communication device is an IAB node 10, or a chip applied to the IAB node 10.
  • the communication unit 102 is configured to support the communication device to perform the action received by the IAB node 10 in step 603 in the foregoing embodiment.
  • the communication unit 102 is also configured to support the communication device to perform the action sent by the IAB node 10 in step 604 in the above-mentioned embodiment.
  • the communication unit 102 is also used for the communication device to execute the actions sent by the IAB node 10 in step 605 and step 613 in the foregoing embodiment. In a possible embodiment, the communication unit 102 is also used for the communication device to execute the action received by the IAB node 10 in step 612 in the foregoing embodiment.
  • the communication device is a network management network element, or a chip applied to a network management network element.
  • the communication unit 102 is configured to support the communication device to perform the action received by the network management network element in step 605 in the foregoing embodiment.
  • the communication unit 102 is also used to support the communication device to perform the action sent by the network management network element in step 606 in the foregoing embodiment.
  • FIG. 17 shows a schematic diagram of a possible logical structure of the communication device involved in the foregoing embodiment.
  • the communication device includes: a processing module 112 and a communication module 113.
  • the processing module 112 is used to control and manage the actions of the communication device.
  • the processing module 112 is used to perform information/data processing steps on the communication device.
  • the communication module 113 is used to support the communication device to send or receive information/data.
  • the communication device may further include a storage module 111 for storing program codes and data that can be used by the communication device.
  • the communication device is a session management network element, or a chip applied to the session management network element.
  • the communication module 113 is used to support the communication device to execute step 601 in FIG. 6 by the session management network element in the foregoing embodiment.
  • the communication module 113 is configured to support the communication device to perform the action sent by the session management network element in step 602 in the foregoing embodiment.
  • the communication module 113 is further configured to support the communication device to execute the receiving action performed by the session management network element in step 606 and step 614 in the foregoing embodiment, or step 600 and step 611.
  • the processing module 112 is further configured to support the communication device to execute step 607 and step 6021 in the foregoing embodiment.
  • the communication module 113 is further configured to support the communication device to execute the sending action performed by the session management network element in step 6022 in the foregoing embodiment in step 609.
  • the communication device is a mobility management network element, or a chip applied to a mobility management network element.
  • the communication module 113 is used to support the communication device to perform the action received by the mobility management network element in step 602 in the foregoing embodiment.
  • the communication module 113 is configured to support the communication device to perform the action sent by the mobility management network element in step 603 in the foregoing embodiment.
  • the communication module 113 is also used for the communication device to execute the actions received by the mobility management network element in step 605, step 6022, and step 609 in the foregoing embodiment.
  • the communication module 113 is also used for the communication device to execute the actions sent by the mobility management network element in step 606 and step 614 in the foregoing embodiment.
  • the processing module 112 is also used for the communication device to execute step 610 in the foregoing embodiment.
  • the communication module 113 is also used for the communication device to execute the action received by the mobility management network element in step 613 in the foregoing embodiment.
  • the communication device is the Donor node 50 or a chip applied to the Donor node 50.
  • the communication module 113 is configured to support the communication device to perform the action sent by the Donor node 50 in step 603 in the foregoing embodiment.
  • the communication module 113 is configured to support the communication device to perform the actions received by the Donor node 50 in step 602 of the foregoing embodiment.
  • the communication module 113 is also used for the communication device to execute the action received by the Donor node 50 in step 605 in the foregoing embodiment.
  • the communication module 113 is also used for the communication device to execute the actions sent by the Donor node 50 in step 606 and step 614 in the foregoing embodiment.
  • the communication module 113 is also used for the communication device to execute the action received by the Donor node 50 in step 613 in the foregoing embodiment.
  • the communication device is an IAB node 10, or a chip applied to the IAB node 10.
  • the communication module 113 is configured to support the communication device to perform the action received by the IAB node 10 in step 603 in the foregoing embodiment.
  • the communication module 113 is also used to support the communication device to perform the action sent by the IAB node 10 in step 604 in the foregoing embodiment.
  • the communication module 113 is also used for the communication device to execute the actions sent by the IAB node 10 in step 605 and step 613 in the foregoing embodiment. In a possible embodiment, the communication module 113 is also used for the communication device to execute the action received by the IAB node 10 in step 612 in the foregoing embodiment.
  • the communication device is a network management network element, or a chip applied to a network management network element.
  • the communication module 113 is configured to support the communication device to perform the action received by the network management network element in step 605 in the foregoing embodiment.
  • the communication module 113 is also used to support the communication device to execute the action sent by the network management network element in step 606 in the foregoing embodiment.
  • the processing module 112 may be a processor or a controller, for example, a central processing unit, a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic devices, transistor logic devices, Hardware components or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination that implements computing functions, for example, a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on.
  • the communication module 113 may be a transceiver, a transceiver circuit, or a communication interface.
  • the storage module 111 may be a memory.
  • the processing module 112 is the processor 51 or the processor 55
  • the communication module 113 is the communication interface 53
  • the storage module 111 is the memory 42
  • the communication device involved in this application may be the communication device shown in FIG. 5.
  • FIG. 18 is a schematic structural diagram of a chip 150 provided by an embodiment of the present application.
  • the chip 150 includes one or more (including two) processors 1510 and a communication interface 1530.
  • the chip 150 further includes a memory 1540.
  • the memory 1540 may include a read-only memory and a random access memory, and provides operation instructions and data to the processor 1510.
  • a part of the memory 1540 may also include a non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the memory 1540 stores the following elements, execution modules or data structures, or their subsets, or their extended sets.
  • the corresponding operation is executed by calling the operation instruction stored in the memory 1540 (the operation instruction may be stored in the operating system).
  • One possible implementation manner is that the structures of the chips used in the IAB node, the Donor node, the mobility management network element, the session management network element, and the network management network element are similar, and different devices can use different chips to achieve their respective functions.
  • the processor 1510 controls the processing operations of any one of the IAB node, the Donor node, the mobility management network element, the session management network element, and the network management network element.
  • the processor 1510 may also be referred to as a central processing unit (CPU).
  • the memory 1540 may include a read-only memory and a random access memory, and provides instructions and data to the processor 1510. A part of the memory 1540 may also include NVRAM.
  • the memory 1540, the communication interface 1530, and the memory 1540 are coupled together by a bus system 1520, where the bus system 1520 may include a power bus, a control bus, and a status signal bus in addition to a data bus.
  • various buses are marked as the bus system 1520 in FIG. 18.
  • the method disclosed in the foregoing embodiments of the present application may be applied to the processor 1510 or implemented by the processor 1510.
  • the processor 1510 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor 1510 or instructions in the form of software.
  • the above-mentioned processor 1510 may be a general-purpose processor, a digital signal processing (digital signal processing, DSP), an ASIC, an off-the-shelf programmable gate array (field-programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistors. Logic devices, discrete hardware components.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory 1540, and the processor 1510 reads the information in the memory 1540, and completes the steps of the foregoing method in combination with its hardware.
  • the communication interface 1530 is used to perform the receiving and sending of the IAB node, the Donor node, the mobility management network element, the session management network element, and the network management network element in the embodiment shown in Figure 6 to Figure 15. step.
  • the processor 1510 is configured to perform the processing steps of the IAB node, the Donor node, the mobility management network element, the session management network element, and the network management network element in the embodiments shown in FIGS. 6-15.
  • the above communication unit may be a communication interface of the device for receiving signals from other devices.
  • the communication unit is a communication interface used by the chip to receive signals or send signals from other chips or devices.
  • a computer-readable storage medium is provided, and instructions are stored in the computer-readable storage medium.
  • the instructions are executed, the functions of the mobility management network element as shown in Figure 6 to Figure 15 are realized.
  • a computer-readable storage medium is provided, and instructions are stored in the computer-readable storage medium.
  • the instructions are executed, the functions of the session management network element shown in Figure 6 to Figure 15 are realized.
  • a computer-readable storage medium is provided, and instructions are stored in the computer-readable storage medium.
  • the instructions are executed, the functions of the IAB node as shown in Fig. 6 to Fig. 15 are realized.
  • a computer-readable storage medium is provided, and instructions are stored in the computer-readable storage medium.
  • the instructions are executed, the functions of the network management network element shown in Figure 6 to Figure 15 are realized.
  • a computer program product including instructions.
  • the computer program product includes instructions. When the instructions are executed, the functions of the network management network element shown in Figure 6 to Figure 15 are realized.
  • a computer program product including instructions.
  • the computer program product includes instructions. When the instructions are executed, the functions of the IAB node as shown in Figure 6 to Figure 15 are realized.
  • a computer program product including instructions.
  • the computer program product includes instructions. When the instructions are executed, the functions of the Donor node as shown in Figs. 6 to 15 are realized.
  • a computer program product including instructions.
  • the computer program product includes instructions. When the instructions are executed, the functions of the session management network element shown in Figure 6 to Figure 15 are realized.
  • a computer program product including instructions.
  • the computer program product includes instructions. When the instructions are executed, the functions of the mobility management network element shown in Figs. 6 to 15 are realized.
  • a chip is provided.
  • the chip is used in a network management network element.
  • the chip includes at least one processor and a communication interface.
  • the communication interface is coupled to the at least one processor. The function of the network management network element.
  • a chip is provided.
  • the chip is applied to a Donor node.
  • the chip includes at least one processor and a communication interface.
  • the communication interface is coupled to the at least one processor. The function of the Donor node in the middle.
  • a chip is provided.
  • the chip is applied to an IAB node.
  • the chip includes at least one processor and a communication interface.
  • the communication interface is coupled to the at least one processor. The function of the IAB node in the middle.
  • a chip is provided.
  • the chip is applied to a mobile management network element.
  • the chip includes at least one processor and a communication interface.
  • the communication interface is coupled to the at least one processor.
  • Figure 15 shows the functions of the mobile management network element.
  • a chip is provided.
  • the chip is used in a session management network element.
  • the chip includes at least one processor and a communication interface.
  • the communication interface is coupled to the at least one processor.
  • An embodiment of the present application provides a communication system, which includes: a session management network element and an IAB node.
  • the session management network element is used to perform any steps performed by the session management network element in Figs. 6-8
  • the IAB node is used to perform any steps performed by the IAB node in Figs. 6-8.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer programs or instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, network equipment, user equipment, or other programmable devices.
  • the computer program or instruction may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer program or instruction may be transmitted from a website, a computer, or The server or data center transmits to another website site, computer, server or data center through wired or wireless means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that integrates one or more available media.
  • the usable medium may be a magnetic medium, such as a floppy disk, a hard disk, and a magnetic tape; it may also be an optical medium, such as a digital video disc (digital video disc, DVD); and it may also be a semiconductor medium, such as a solid state drive (solid state drive). , SSD).

Landscapes

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

Abstract

本申请实施例提供一种用户面网元的管理方法、装置以及系统，涉及通信技术领域，用以实现会话管理网元正确寻址数据面实例。该方法包括：会话管理网元确定目标数据面实例的信息，所述目标数据面实例的信息包括路由指示，所述路由指示用于确定所述目标数据面实例的地址；所述目标数据面实例与无线回传IAB节点关联；所述会话管理网元通过为所述IAB节点提供服务的移动管理网元或宿主Donor节点向所述IAB节点发送N4会话管理请求消息和第一指示，所述第一指示用于指示所述IAB节点向所述目标数据面实例发送所述N4会话管理请求消息。

Description

一种通信方法、装置以及系统 技术领域
本申请实施例涉及通信技术领域，尤其涉及一种通信方法、装置以及系统。
背景技术
目前工业制造的厂商们对第五代移动通信技术(5th-Generation，5G)提出的诉求主要集中在三个方面，分别是：(1)、替代有线线缆，即根据使用场景的不同，不同程度采用无线连接替换有线连接，提升工厂设备部署的灵活性。如图1-1所示，有的功能设备组合之间全部使用无线连接，有的仅部分使用无线连接。(2)、安全的垂直/水平通讯，通讯需求包含对等设备以及不同层级设备间的安全设备通讯。如图1-1所示，例如传感器之间的通讯属于对等设备之间的通讯，而传感器和上级控制器的通讯则属于不同层级之间的通讯的。(3)、低时延、高可靠的设备通讯，根据闭环控制的业务要求，无线通讯需要满足时延和可靠性要求，针对5G蜂窝通讯，理想通讯时延为1毫秒(millisecond，ms)级。
基于上述基本诉求，可以基于接入回传一体化(integrated access and backhaul，IAB)技术设计了适用于工业场景的网络部署方式，如图1-1所示，在产线周围部署IAB节点，在IAB节点上集成数据面模块或者将IAB节点和数据面模块合并设置在同一个设备上。其中，数据面模块具有路由和转发的功能。这样本地设备(例如，设备1和设备2)进行数据交换时，设备1的数据仅仅经过数据面模块处理后即可转发给设备2，不再需要转发给核心网，从而大大减少传输时延。
但是按照现有技术，5G核心网的控制网元(例如，会话管理功能(session management function，SMF)网元)仍需要通过第一接口(例如，N4接口)管理数据面模块(例如，向数据面模块下发转发规则)，而且传统的N4接口需要通过IP地址或者完全合格域名(fully qualified domain names，FQDN)进行寻址，也就是通过有线连接5G核心网。然而如果数据面模块部署在IAB节点后，无法再通过有线连接保持与5G核心网的连通性，也就是说5G核心网的控制网元无法通过传统的IP地址或者FQDN寻址该数据面模块，同样也无法控制管理该数据面模块。
如图1-2所示，目前5G标准中数据面模块可以直接通过服务化接口或者间接(例如通过网管网元(Operation，Administration and Maintenance，OAM))将数据面模块对应的数据面实例注册到网络功能库(Network Function Repository Function，NRF)中(如图1-2中的步骤5或步骤6)。以便于SMF网元通过步骤1和步骤2选择数据面模块，可以从NRF中获取特定要求的数据面实例(例如，步骤7，通知消息中携带符合步骤1中SMF网元需求的用户面网元列表)。
但是，数据面模块通过服务化接口直接向NRF注册时，需要数据面模块和NRF之间存在IP连通性，这样数据面模块可以通过IP地址或者FQDN正确寻址到NRF网元，从而完成实例的注册，但是如果实例集成/合设在IAB节点上，无线化的回传网络，无法仍按照现有方式进行寻址。至于数据面模块间接通过OAM向NRF注册的方式，因为集成/合设在IAB节点上实例同样没有与OAM的直接IP通路，所以该种注册方 式也无法工作。如果数据面实例无法正常注册，SMF网元无法正常的选择数据面，后续也不便于SMF网元对数据面实例进行管理和控制。
发明内容
本申请实施例提供一种用户面网元的管理方法、装置以及系统，用以实现会话管理网元正确寻址数据面实例。
为了达到上述目的，本申请实施例提供如下技术方案：
第一方面，本申请实施例提供一种通信方法，该方法包括：会话管理网元确定包括路由指示的目标数据面实例的信息。其中，路由指示用于确定目标数据面实例的地址。目标数据面实例与无线回传IAB节点关联。会话管理网元通过为IAB节点提供服务的移动管理网元或宿主Donor节点向IAB节点发送N4会话管理请求消息和第一指示，第一指示用于指示IAB节点向目标数据面实例发送N4会话管理请求消息。
本申请实施例提供一种通信方法，该方法中会话管理网元确定目标数据面实例的信息，由于目标数据面实例的信息中包括路由指示。因此，会话管理网元可以根据路由指示确定目标数据面实例的地址，以使得会话管理网元正确寻址目标数据面实例。由于目标数据面实例与IAB节点关联，因此会话管理网元可以向IAB节点发送N4会话管理请求消息，以实现对目标数据面实例的管理。该方案可以实现N4接口无线化后带来的目标数据面实例注册和管理。
在一种可能的实现方式中，会话管理网元通过移动管理网元向IAB节点发送N4会话管理请求消息和第一指示之前，本申请实施例提供的方法还包括：会话管理网元确定会话管理网元本地存在IAB节点的上下文。会话管理网元通过移动管理网元向IAB节点发送N4会话管理请求消息和第一指示，包括：会话管理网元根据IAB节点的上下文生成会话管理非接入层NAS消息，该会话管理NAS层消息包括N4会话管理请求消息和第一指示。会话管理网元通过移动管理网元向IAB节点发送会话管理NAS层消息。会话管理网元本地存在IAB节点的上下文表示终端和IAB节点接入同一个移动管理网元。会话管理网元确定会话管理网元本地存在IAB节点的上下文可以使用会话管理网元获取本地的IAB节点的上下文替代。
在一种可能的实现方式中，会话管理网元的本地不存在IAB节点的上下文，本申请实施例提供的方法还包括：会话管理网元向移动管理网元发送路由指示，移动管理网元用于根据路由指示确定移动管理网元本地具有IAB节点的上下文后，移动管理网元根据IAB节点的上下文生成移动性管理NAS消息，向IAB节点发送移动性管理NAS消息。其中，移动性管理NAS消息包括N4会话管理请求消息和第一指示。这样在会话管理网元本地不存在IAB节点的上下文时，可以通过移动管理网元寻址IAB节点，并向IAB节点发送N4会话管理请求消息。
在一种可能的实现方式中，本申请实施例提供的方法还包括：会话管理网元接收来自移动管理网元的指示信息。该指示信息用于指示移动管理网元本地具有IAB节点的上下文。
在一种可能的实现方式中，会话管理网元向移动管理网元发送路由指示之前，本申请实施例提供的方法还包括：会话管理网元从用户数据管理网元处获取IAB节点的移动管理网元的信息。该方法可以使用于会话管理网元确定为终端提供服务的移动管 理网元处不具有IAB节点的上下文的场景，这样便于会话管理网元从用户数据管理网元处确定为IAB节点提供服务的移动管理网元的地址。
在一种可能的实现方式中，本申请实施例提供的方法在会话管理网元从用户数据管理网元处获取IAB节点的移动管理网元的信息之前，还可以包括：会话管理网元确定为终端提供服务的移动管理网元处不具有IAB节点的上下文。
在一种可能的实现方式中，会话管理网元确定为终端提供服务的移动管理网元处不具有IAB节点的上下文，包括：会话管理网元向为终端提供服务的移动管理网元发送查询请求消息。其中，查询请求消息用于查询为终端提供服务的移动管理网元是否具有IAB节点的上下文。会话管理网元接收来自为终端提供服务的移动管理网元的响应消息。该响应消息用于表示为终端提供服务的移动管理网元处不具有IAB节点的上下文。
示例性的，查询请求消息中携带指示信息，用于查询为终端提供服务的移动管理网元是否具有IAB节点的上下文。响应消息中携带确认信息，用于表示为终端提供服务的移动管理网元处不具有IAB节点的上下文。
在一种可能的实现方式中，会话管理网元通过Donor节点向IAB节点发送N4会话管理请求消息和第一指示还包括：会话管理网元向Donor节点发送路由指示，Donor节点用于根据路由指示向IAB节点发送第一消息，第一消息包括N4会话管理请求消息和第一指示。这样便于通过宿主节点寻址IAB节点。
在一种可能的实现方式中，本申请实施例提供的方法还包括：会话管理网元通过IAB节点接收来自目标数据面实例的N4会话管理响应消息。这样便于会话管理网元确定目标数据面实例是否成功管理N4会话。
在一种可能的实现方式中，本申请实施例提供的方法还包括：会话管理网元从网络存储网元处获取一个或多个数据面实例的信息，一个或多个数据面实例包括目标数据面实例。
在一种可能的实现方式中，本申请实施例提供的方法还包括：会话管理网元通过网管网元、或Donor节点、或移动管理网元接收数据面模块的一个或多个数据面实例的信息，一个或多个数据面实例包括目标数据面实例。通过接收数据面模块的一个或多个数据面实例的信息，可以将数据面模块的一个或多个数据面实例的信息注册在会话管理网元。
在一种可能的实现方式中，一个或多个数据面实例在Donor节点、或移动管理网元处透传，或者，一个或多个数据面实例由Donor节点、或移动管理网元处理后发送至会话管理网元或网络存储网元。
在一种可能的实现方式中，IAB节点和目标数据面实例对应的数据面模块位于同一个设备中；或者，IAB节点中具有目标数据面实例对应的数据面模块。
第二方面，本申请实施例提供一种通信方法，该方法包括：无线回传IAB节点接收来自会话管理网元的N4会话管理请求消息和第一指示。其中，第一指示用于指示IAB节点向目标数据面实例发送N4会话管理请求消息。IAB节点根据第一指示，向目标数据面实例发送N4会话管理请求消息，N4会话管理请求消息用于指示管理目标数据面实例的会话上下文。
在一种可能的实现方式中，本申请实施例提供的方法还包括：IAB节点接收目标数据面实例发送的N4会话管理响应消息。IAB节点向Donor节点或移动管理网元发送第二指示，以及N4会话管理响应消息，第二指示用于指示向会话管理网元发送N4会话管理响应消息。
在一种可能的实现方式中，本申请实施例提供的方法还包括：IAB节点向第一设备发送包括数据面模块对应的一个或多个数据面实例的信息的第一消息。一个或多个数据面实例的信息包括目标数据面实例的信息，任一个数据面实例的信息包括路由指示，第一消息用于指示第一设备向会话管理网元或者网络存储网元注册一个或多个数据面实例的信息。路由指示用于会话管理网元确定任一个数据面实例的地址。任一个数据面实例与IAB节点关联，第一设备包括以下任一个：网管网元或Donor节点、或移动管理网元。
在一种可能的实现方式中，本申请实施例提供的方法还包括：第一消息中包括负荷容器Payload Container，Payload Container中包括一个或多个数据面实例的信息，Payload Container的类型用于指示第一设备向会话管理网元或者网络存储网元注册一个或多个数据面实例的信息。
在一种可能的实现方式中，本申请实施例提供的方法还包括：第一消息中还包括注册指示，注册指示用于指示第一设备向会话管理网元或者网络存储网元注册一个或多个数据面实例的信息。
在一种可能的实现方式中，本申请实施例提供的方法还包括：IAB节点和第一设备之间具有预定义的操作接口，预定义的操作接口用于指示第一设备向会话管理网元或者网络存储网元注册一个或多个数据面实例的信息，IAB节点通过预定义的操作接口向第一设备发送第一消息。
在一种可能的实现方式中，本申请实施例提供的方法还包括：一个或多个数据面实例的信息在Donor节点、或移动管理网元处透传，或者，一个或多个数据面实例的信息由Donor节点、或移动管理网元处理后发送至会话管理网元或网络存储网元。
在一种可能的实现方式中，本申请实施例提供的方法还包括：IAB节点和数据面实例对应的数据面模块位于同一个设备中；或者，IAB节点中具有数据面实例对应的数据面模块。
第三方面，本申请实施例提供一种通信方法，该方法包括：为IAB节点提供服务的移动管理网元接收来自会话管理网元的N4会话管理请求消息和第一指示，第一指示用于指示IAB节点向目标数据面实例发送N4会话管理请求消息；移动管理网元向IAB节点发送N4会话管理请求消息和第一指示。
在一种可能的实现方式中，移动管理网元向IAB节点发送N4会话管理请求消息和第一指示之前，本申请实施例提供的方法还包括：移动管理网元接收来自会话管理网元的路由指示，路由指示用于确定目标数据面实例的地址；目标数据面实例AB节点关联；移动管理网元根据路由指示确定移动管理网元本地具有IAB节点的上下文后，移动管理网元根据IAB节点的上下文生成移动性管理NAS消息；移动管理网元向IAB节点发送N4会话管理请求消息和第一指示。包括：移动管理网元向IAB节点发送移动性管理NAS消息，移动性管理NAS消息包括N4会话管理请求消息和第一指示。
在一种可能的实现方式中，本申请实施例提供的方法在为IAB节点提供服务的移动管理网元接收来自会话管理网元的N4会话管理请求消息和第一指示之前，还包括：移动管理网元接收来自会话管理网元的查询请求消息，该查询请求消息用于查询移动管理网元处是否具有IAB节点的上下文。如果移动管理网元处具有IAB节点的上下文，移动管理网元向会话管理网元发送用于指示移动管理网元处具有IAB节点的上下文的响应消息。如果移动管理网元处不具有IAB节点的上下文，移动管理网元向会话管理网元发送用于指示移动管理网元处不具有IAB节点的上下文的响应消息。
在一种可能的实现方式中，本申请实施例提供的方法还包括：移动管理网元接收第一消息，第一消息包括数据面模块的一个或多个数据面实例的信息，第一消息用于指示移动管理网元向会话管理网元或NRF网元注册一个或多个数据面实例的信息；任一个数据面实例的信息包括路由指示；一个或多个数据面实例的信息包括目标数据面实例的信息；移动管理网元根据第一消息，向会话管理网元或网络存储网元注册一个或多个数据面实例的信息。
在一种可能的实现方式中，一个或多个数据面实例的信息在移动管理网元处透传，或者，一个或多个数据面实例的信息由移动管理网元处理后发送至会话管理网元或网络存储网元。
在一种可能的实现方式中，本申请实施例提供的方法还包括：移动管理网元通过IAB节点或Donor节点接收来自数据面实例的N4会话管理响应消息和第二指示，第二指示用于指示将N4会话管理响应消息发送至会话管理网元；移动管理网元向会话管理网元发送N4会话管理响应消息。
第四方面，本申请实施例提供一种通信装置，该一种通信装置可以实现第一方面或第一方面的任意一种可能的实现方式中描述的一种通信方法，因此也可以实现第一方面或第一方面任意一种可能的实现方式中的有益效果。该一种通信装置可以为会话管理网元，也可以为可以支持会话管理网元实现第一方面或第一方面的任意一种可能的实现方式中的装置。例如应用于会话管理网元中的芯片。该一种通信装置可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
一种示例，本申请实施例提供的通信装置，包括：处理单元，用于确定目标数据面实例的信息，目标数据面实例的信息包括路由指示，路由指示用于确定目标数据面实例的地址；目标数据面实例与无线回传IAB节点关联；通信单元，用于通过为IAB节点提供服务的移动管理网元或宿主Donor节点向IAB节点发送N4会话管理请求消息和第一指示，第一指示用于指示IAB节点向目标数据面实例发送N4会话管理请求消息。
在一种可能的实现方式中，通信单元，用于通过移动管理网元向IAB节点发送N4会话管理请求消息和第一指示之前，处理单元还用于确定装置本地存在IAB节点的上下文；处理单元，还用于根据IAB节点的上下文生成会话管理非接入层NAS消息，会话管理NAS层消息包括N4会话管理请求消息和第一指示；相应的，通信单元，还用于通过移动管理网元向IAB节点发送会话管理NAS层消息。
在一种可能的实现方式中，处理单元，用于确定装置本地不存在IAB节点的上下文，通信单元，还用于向移动管理网元发送路由指示，移动管理网元用于根据路由指 示确定移动管理网元本地具有IAB节点的上下文后，移动管理网元根据IAB节点的上下文生成移动性管理NAS消息，向IAB节点发送移动性管理NAS消息，移动性管理NAS消息包括N4会话管理请求消息和第一指示。
在一种可能的实现方式中，本申请实施例提供的通信单元，还用于接收来自移动管理网元的指示信息。该指示信息用于指示移动管理网元本地具有IAB节点的上下文。
在一种可能的实现方式中，通信单元，用于向移动管理网元发送路由指示之前，通信单元，还用于从用户数据管理网元处获取IAB节点的移动管理网元的信息。
在一种可能的实现方式中，通信单元从用户数据管理网元处获取IAB节点的移动管理网元的信息之前，处理单元，还用于确定为终端提供服务的移动管理网元处不具有IAB节点的上下文。
在一种可能的实现方式中，处理单元确定为终端提供服务的移动管理网元处不具有IAB节点的上下文的情况下，通信单元还用于向为终端提供服务的移动管理网元发送查询请求消息。其中，查询请求消息用于查询为终端提供服务的移动管理网元是否具有IAB节点的上下文。会话管理网元接收来自为终端提供服务的移动管理网元的响应消息。该响应消息用于表示为终端提供服务的移动管理网元处不具有IAB节点的上下文。
示例性的，查询请求消息中携带指示信息，用于查询为终端提供服务的移动管理网元是否具有IAB节点的上下文。响应消息中携带确认信息，用于表示为终端提供服务的移动管理网元处不具有IAB节点的上下文。
在一种可能的实现方式中，通信单元，用于通过Donor节点向IAB节点发送N4会话管理请求消息和第一指示还包括：向Donor节点发送路由指示，Donor节点用于根据路由指示向IAB节点发送第一消息，第一消息包括N4会话管理请求消息和第一指示。
在一种可能的实现方式中，通信单元，还用于通过IAB节点接收来自目标数据面实例的N4会话管理响应消息。
在一种可能的实现方式中，通信单元，还用于从网络存储网元处获取一个或多个数据面实例的信息，一个或多个数据面实例包括目标数据面实例。
在一种可能的实现方式中，通信单元，还用于通过网管网元、或Donor节点、或移动管理网元接收数据面模块的一个或多个数据面实例的信息，一个或多个数据面实例包括目标数据面实例。
在一种可能的实现方式中，一个或多个数据面实例在Donor节点、或移动管理网元处透传，或者，一个或多个数据面实例由Donor节点、或移动管理网元处理后发送至装置或网络存储网元。
在一种可能的实现方式中，IAB节点和目标数据面实例对应的数据面模块位于同一个设备中；或者，IAB节点中具有目标数据面实例对应的数据面模块。
另一种示例，本申请实施例提供一种通信装置，该通信装置可以是会话管理网元，也可以是会话管理网元内的芯片。该通信装置可以包括：通信单元和处理单元。当该通信装置是会话管理网元时，该通信单元可以为通信接口。该通信装置还可以包括存储单元。该存储单元可以是存储器。该存储单元，用于存储计算机程序代码，计算机 程序代码包括指令。该处理单元可以是处理器。该处理单元执行该存储单元所存储的指令，以使该会话管理网元实现第一方面或第一方面的任意一种可能的实现方式中描述的一种通信方法。当该通信装置是会话管理网元内的芯片时，该处理单元可以是处理器，该通信单元可以统称为：通信接口。例如，通信接口可以为输入/输出接口、管脚或电路等。该处理单元执行存储单元所存储的计算机程序代码，以使该会话管理网元实现第一方面或第一方面的任意一种可能的实现方式中描述的一种通信方法，该存储单元可以是该芯片内的存储单元(例如，寄存器、缓存等)，也可以是该会话管理网元内的位于该芯片外部的存储单元(例如，只读存储器、随机存取存储器等)。
可选的，处理器、通信接口和存储器相互耦合。
第五方面，本申请实施例提供一种通信装置，该一种通信装置可以实现第二方面或第二方面的任意一种可能的实现方式中描述的一种通信方法，因此也可以实现第二方面或第二方面任意一种可能的实现方式中的有益效果。该一种通信装置可以为IAB节点，也可以为可以支持IAB节点实现第二方面或第二方面的任意一种可能的实现方式中的装置。例如应用于IAB节点中的芯片。该一种通信装置可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
一种示例，本申请实施例提供的一种通信装置，包括：处理单元，用于处理信息；通信单元，用于接收来自会话管理网元的N4会话管理请求消息和第一指示，第一指示用于指示通信单元向目标数据面实例发送N4会话管理请求消息；通信单元，用于根据第一指示，向目标数据面实例发送N4会话管理请求消息，N4会话管理请求消息用于指示管理目标数据面实例的会话上下文。
在一种可能的实现方式中，通信单元，还用于接收目标数据面实例发送的N4会话管理响应消息；IAB节点向Donor节点或移动管理网元发送第二指示，以及N4会话管理响应消息，第二指示用于指示向会话管理网元发送N4会话管理响应消息。
在一种可能的实现方式中，通信单元，还用于向第一设备发送第一消息，第一消息包括数据面模块对应的一个或多个数据面实例的信息，一个或多个数据面实例的信息包括目标数据面实例的信息，任一个数据面实例的信息包括路由指示，第一消息用于指示第一设备向会话管理网元或者网络存储网元注册一个或多个数据面实例的信息；路由指示用于会话管理网元确定任一个数据面实例的地址；任一个数据面实例与装置关联，第一设备包括以下任一个：网管网元或Donor节点、或移动管理网元。
在一种可能的实现方式中，第一消息中包括负荷容器Payload Container，Payload Container中包括一个或多个数据面实例的信息，Payload Container的类型用于指示第一设备向会话管理网元或者网络存储网元注册一个或多个数据面实例的信息。
在一种可能的实现方式中，第一消息中还包括注册指示，注册指示用于指示第一设备向会话管理网元或者网络存储网元注册一个或多个数据面实例的信息。
在一种可能的实现方式中，本申请实施例的通信装置和第一设备之间具有预定义的操作接口，预定义的操作接口用于指示第一设备向会话管理网元或者网络存储网元注册一个或多个数据面实例的信息，通信单元，用于通过预定义的操作接口向第一设备发送第一消息。
在一种可能的实现方式中，一个或多个数据面实例的信息在Donor节点、或移动 管理网元处透传，或者，一个或多个数据面实例的信息由Donor节点、或移动管理网元处理后发送至会话管理网元或网络存储网元。
在一种可能的实现方式中，IAB节点和数据面实例对应的数据面模块位于同一个设备中；或者，IAB节点中具有数据面实例对应的数据面模块。
另一种示例，本申请实施例提供一种通信装置，该通信装置可以是IAB节点，也可以是IAB节点内的芯片。该通信装置可以包括：通信单元和处理单元。当该通信装置是IAB节点时，该通信单元可以为通信接口。该通信装置还可以包括存储单元。该存储单元可以是存储器。该存储单元，用于存储计算机程序代码，计算机程序代码包括指令。该处理单元可以是处理器。该处理单元执行该存储单元所存储的指令，以使该IAB节点实现第二方面或第二方面的任意一种可能的实现方式中描述的一种通信方法。当该通信装置是IAB节点内的芯片时，该处理单元可以是处理器，该通信单元可以统称为：通信接口。例如，通信接口可以为输入/输出接口、管脚或电路等。该处理单元执行存储单元所存储的计算机程序代码，以使该IAB节点实现第二方面或第二方面的任意一种可能的实现方式中描述的一种通信方法，该存储单元可以是该芯片内的存储单元(例如，寄存器、缓存等)，也可以是该IAB节点内的位于该芯片外部的存储单元(例如，只读存储器、随机存取存储器等)。
可选的，处理器、通信接口和存储器相互耦合。
第六方面，本申请实施例提供一种通信装置，该一种通信装置可以实现第三方面或第三方面的任意一种可能的实现方式中描述的一种通信方法，因此也可以实现第三方面或第三方面任意一种可能的实现方式中的有益效果。该一种通信装置可以为移动管理网元，也可以为可以支持移动管理网元实现第三方面或第三方面的任意一种可能的实现方式中的装置。例如应用于移动管理网元中的芯片。该一种通信装置可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
一种示例，本申请实施例提供一种通信装置，包括：处理单元，用于处理信息；通信单元，用于接收来自会话管理网元的N4会话管理请求消息和第一指示，第一指示用于指示IAB节点向目标数据面实例发送N4会话管理请求消息；通信单元，还用于向IAB节点发送N4会话管理请求消息和第一指示。
在一种可能的实现方式中，通信单元，还用于向IAB节点发送N4会话管理请求消息和第一指示之前，通信单元，还用于接收来自会话管理网元的路由指示，路由指示用于确定目标数据面实例的地址；目标数据面实例AB节点关联；处理单元，用于根据路由指示确定装置本地具有IAB节点的上下文后，根据IAB节点的上下文生成移动性管理NAS消息；通信单元，用于向IAB节点发送移动性管理NAS消息，移动性管理NAS消息包括N4会话管理请求消息和第一指示。
在一种可能的实现方式中，通信单元，还用于接收第一消息，第一消息包括数据面模块的一个或多个数据面实例的信息，第一消息用于指示装置向会话管理网元或NRF网元注册一个或多个数据面实例的信息；任一个数据面实例的信息包括路由指示；一个或多个数据面实例的信息包括目标数据面实例的信息；处理单元，用于根据第一消息，通过通信单元向会话管理网元或网络存储网元注册一个或多个数据面实例的信息。
在一种可能的实现方式中，一个或多个数据面实例的信息在移动管理网元处透传，或者，一个或多个数据面实例的信息由移动管理网元处理后发送至会话管理网元或网络存储网元。
在一种可能的实现方式中，通信单元，用于通过IAB节点或Donor节点接收来自目标数据面实例的N4会话管理响应消息和第二指示，第二指示用于指示向会话管理网元发送N4会话管理响应消息；通信单元，用于向会话管理网元发送N4会话管理响应消息。
另一种示例，本申请实施例提供一种通信装置，该通信装置可以是移动管理网元，也可以是移动管理网元内的芯片。该通信装置可以包括：通信单元和处理单元。当该通信装置是移动管理网元时，该通信单元可以为通信接口。该通信装置还可以包括存储单元。该存储单元可以是存储器。该存储单元，用于存储计算机程序代码，计算机程序代码包括指令。该处理单元可以是处理器。该处理单元执行该存储单元所存储的指令，以使该移动管理网元实现第三方面或第三方面的任意一种可能的实现方式中描述的一种通信方法。当该通信装置是移动管理网元内的芯片时，该处理单元可以是处理器，该通信单元可以统称为：通信接口。例如，通信接口可以为输入/输出接口、管脚或电路等。该处理单元执行存储单元所存储的计算机程序代码，以使该移动管理网元实现第三方面或第三方面的任意一种可能的实现方式中描述的一种通信方法，该存储单元可以是该芯片内的存储单元(例如，寄存器、缓存等)，也可以是该移动管理网元内的位于该芯片外部的存储单元(例如，只读存储器、随机存取存储器等)。
可选的，处理器、通信接口和存储器相互耦合。
第七方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有计算机程序或指令，当计算机程序或指令在计算机上运行时，使得计算机执行如第一方面、或第一方面的任一种可能的实现方式中描述通信方法。
第八方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有计算机程序或指令，当计算机程序或指令在计算机上运行时，使得计算机执行如第二方面、或第二方面的任一种可能的实现方式中描述的通信方法。
第九方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有计算机程序或指令，当计算机程序或指令在计算机上运行时，使得计算机执行如第三方面、或第三方面的任一种可能的实现方式中描述的通信方法。
第十方面，本申请实施例提供一种包括指令的计算机程序产品，当指令在计算机上运行时，使得计算机执行如第一方面或第一方面的任意一种可能的实现方式中描述的通信方法。
第十一方面，本申请实施例提供一种包括指令的计算机程序产品，当指令在计算机上运行时，使得计算机执行如第二方面或第二方面的任意一种可能的实现方式中描述的通信方法。
第十二方面，本申请实施例提供一种包括指令的计算机程序产品，当指令在计算机上运行时，使得计算机执行如第三方面或第三方面的任意一种可能的实现方式中描述的通信方法。
第十三方面，本申请实施例提供一种通信装置，该通信装置包括处理器和存储介 质，存储介质存储有指令，指令被处理器运行时，实现如第一方面或第一方面的各种可能的实现方式描述的通信方法。
第十四方面，本申请实施例提供一种通信装置，该通信装置包括处理器和存储介质，存储介质存储有指令，指令被处理器运行时，实现如第二方面或第二方面的各种可能的实现方式描述的通信方法。
第十五方面，本申请实施例提供一种通信装置，该通信装置包括处理器和存储介质，存储介质存储有指令，指令被处理器运行时，实现如第三方面或第三方面的各种可能的实现方式描述的通信方法。
第十六方面，本申请实施例提供一种通信装置，包括：至少一个处理器和通信接口，所述至少一个处理器和通信接口通过线路互联，所述至少一个处理器与存储器耦合，存储器用于存储计算机程序或指令，至少一个处理器用于执行存储器中的该计算机程序或指令，使得所述通信装置执行第一方面或第一方面的各种可能的实现方式中描述的通信方法。
第十七方面，本申请实施例提供一种通信装置，包括：至少一个处理器和通信接口，所述至少一个处理器和通信接口通过线路互联，所述至少一个处理器与存储器耦合，存储器用于存储计算机程序或指令，至少一个处理器用于执行存储器中的该计算机程序或指令，使得所述通信装置执行第二方面或第二方面的各种可能的实现方式中描述的通信方法。
第十八方面，本申请实施例提供一种通信装置，包括：至少一个处理器和通信接口，所述至少一个处理器和通信接口通过线路互联，所述至少一个处理器与存储器耦合，存储器用于存储计算机程序或指令，至少一个处理器用于执行存储器中的该计算机程序或指令，使得所述通信装置执行第三方面或第三方面的各种可能的实现方式中描述的通信方法。
在一种可能的实现方式中，第十六方面、第十七方面、第十八方面任一方面描述的装置中还可以包括：存储器。
第十九方面，本申请实施例提供一种芯片，该芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，至少一个处理器用于运行计算机程序或指令，以实现第一方面或第一方面的各种可能的实现方式中所描述的一种通信方法。通信接口用于与所述芯片之外的其它模块进行通信。
第二十方面，本申请实施例提供一种芯片，该芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，至少一个处理器用于运行计算机程序或指令，以实现第二方面或第二方面的各种可能的实现方式中所描述的一种通信方法。通信接口用于与芯片之外的其它模块进行通信。
第二十一方面，本申请实施例提供一种芯片，该芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，至少一个处理器用于运行计算机程序或指令，以实现第三方面或第三方面的各种可能的实现方式中所描述的一种通信方法。通信接口用于与芯片之外的其它模块进行通信。
本申请实施例提供的芯片还可以包括存储器，存储器用于存储计算机程序或指令。
第二十二方面，本申请实施例提供了一种通信装置，该通信装置包括一个或者多 个模块，用于实现上述第一方面、第二方面、第三方面的方法，该一个或者多个模块可以与上述第一方面、第二方面、第三方面的方法的步骤相对应。
第二十三方面，本申请实施例提供一种通信装置，包括：至少一个处理器，至少一个处理器和存储器耦合，存储器用于存储计算机程序或指令，至少一个处理器用于执行存储器中的该计算机程序或指令，使得所述通信装置执行第一方面或第一方面的各种可能的实现方式中描述的通信方法。
第二十四方面，本申请实施例提供一种通信装置，包括：至少一个处理器，至少一个处理器和存储器耦合，存储器用于存储计算机程序或指令，至少一个处理器用于执行存储器中的该计算机程序或指令，使得所述通信装置执行第二方面或第二方面的各种可能的实现方式中描述的通信方法。
第二十五方面，本申请实施例提供一种通信装置，包括：至少一个处理器，至少一个处理器和存储器耦合，存储器用于存储计算机程序或指令，至少一个处理器用于执行存储器中的该计算机程序或指令，使得所述通信装置执行第三方面或第三方面的各种可能的实现方式中描述的通信方法。
第二十六方面，本申请实施例提供一种通信系统，该通信系统包括：第四方面或第四方面的各种可能的实现方式中描述的通信装置，以及第五方面或第五方面的各种可能的实现方式中描述的通信装置。
在一种可选的实现方式中，该通信系统还可以包括：第六方面或第六方面的各种可能的实现方式中描述的通信装置。
具体的该通信系统中各个通信装置的所执行的具体步骤可以参考相应地方的描述，此处不再赘述。
本申请中第二方面至第二十六方面及其各种实现方式的有益效果，可以参考第一方面及其各种实现方式中的有益效果分析，此处不再赘述。
附图说明
图1-1为本申请实施例提供的一种场景示意图一；
图1-2为本申请实施例提供的一种UPF实例注册过程；
图2为本申请实施例提供的一种场景示意图二；
图3a为本申请实施例提供的一种通信系统架构图一；
图3b为本申请实施例提供的一种通信系统架构图二；
图3c为本申请实施例提供的一种通信系统架构图三；
图3d为本申请实施例提供的一种通信系统架构图四；
图4a为本申请实施例提供的一种5G网络架构示意图；
图4b为本申请实施例提供的另一种5G网络架构示意图；
图4c为本申请实施例提供的再一种5G网络架构示意图；
图5为本申请实施例提供的一种通信设备的结构示意图；
图6-图15为本申请实施例提供的一种通信方法的流程示意图；
图16为本申请实施例提供的一种通信装置的结构示意图；
图17为本申请实施例提供的另一种通信装置的结构示意图；
图18为本申请实施例提供的一种芯片的结构示意图。
具体实施方式
为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。例如，第一消息和第二消息仅仅是为了区分不同的消息，并不对其先后顺序进行限定。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
需要说明的是，本申请中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。
本申请实施例描述的系统架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。本申请实施例中以提供的方法应用于NR系统或5G网络中为例进行说明。
如图2所示，图2示出了本申请实施例提供的方法适用于工业场景的网络部署方式，如图2所示，包括：本地数据网络、5G核心网，与5G核心网通信的宿主节点以及接入该宿主节点的IAB节点。其中，IAB节点部署在产线附近，IAB节点后面集成数据面模块或者IAB节点和数据面模块设置于同一个设备，这样本地设备(例如，设备1和设备2)进行数据交换时，设备1的数据可以经过数据面模块处理后即可转发给设备2，不再需要转发给核心网，从而大大减少传输时延。
如图3a所示，本申请实施例提供一种通信系统，该通信系统包括：IAB节点10、会话管理网元20、位于IAB节点10内部的数据面模块30。其中，一个数据面模块30可以对应一个或多个数据面实例。
在一种可选的实现方式中，如图3a所示，该通信系统还可以包括：网络存储网元80。其中，NRF网元80可以存储一个或多个数据面实例的信息。具体的，数据面实例的信息可以参考下述实施例中的描述，此处不再赘述。当一个或多个数据面实例的信息由IAB节点10注册在会话管理网元20处时，该网络存储网元80可以省略。
在一种可能的实现方式中，如图3a所示，该通信系统还可以包括：移动管理网元40或Donor节点40或一个或多个输入输出设备(input output device，IO设备)60或网管网元70。例如，IO设备可以为终端。
其中，IAB节点10可以通过移动管理网元40或Donor节点40或网管网元70向网络存储网元80或会话管理网元20注册一个或多个数据面实例的信息。
其中，IAB节点10和会话管理网元20可以间接通信。例如，IAB节点10通过移动管理网元40或Donor节点50与会话管理网元20通信。
其中，移动管理网元40和宿主节点50之间具有第一接口。例如，在5G网络中该第一接口可以为N2接口。移动管理网元40和会话管理网元20之间具有第二接口。例如，在5G网络中该第二接口可以为N11接口。本申请实施例中各个网元之间接口的名称仅是一种示例。宿主节点50和IAB节点10之间具有第三接口。例如，第三接口可以为Uu口。
网络存储网元80和移动管理网元40之间具有第四接口。该第四接口可以为用于提供数据面实例信息的注册功能的服务化接口。移动管理网元40和会话管理网元20之间还具有用于提供注册数据面实例信息功能的服务化接口。NRF网元80和网管网元70之间具有接口。
应理解，当数据面模块30位于IAB节点10内部时，可以间接实现图3a中IAB节点10和会话管理网元20之间具有N4接口。
如图3b所示，为本申请实施例提供另一种通信系统，图3b与图3a的区别在于：在图3a中数据面模块30可以位于IAB节点10内部，即IAB节点10中具有数据面模块30，或者IAB节点10中集成有数据面模块30。而在图3b中数据面模块30和IAB节点10位于同一个设备00中。
应理解，在图3b中IAB节点10所在的设备00时，可以间接实现会话管理网元20和IAB节点10之间具有N4接口。
在图3a或图3b所示的通信系统中，终端和IAB节点可以接入同一个移动管理网元40，即终端选择的移动管理网元和IAB节点选择的移动管理网元相同。或者终端和IAB节点可以接入不同的移动管理网元40，即终端选择的移动管理网元和IAB节点选择的移动管理网元不相同。终端和IAB节点可以接入不同的会话管理网元，即终端选择的会话管理网元和IAB节点选择的会话管理网元不相同。终端和IAB节点可以接入相同的会话管理网元，即终端选择的会话管理网元和IAB节点选择的会话管理网元相同。
当IAB节点采用分离架构时，结合图3a，如图3c所示，如果数据面模块50位于IAB节点10内部时，则如图3c所示，IAB节点包括：IAB节点的移动终端(mobile termination，MT)和IAB节点的分布式单元(distributed unit，DU)、数据面模块30以及分布式用户面(Centralized Unit-User Plane，CU-UP)。即增强现有IAB节点功能，各功能模块都作为IAB节点的内部模块，MT、DU数据面模块30以及CU-UP彼此之间具有内部接口，任意模块之间均可以通过内部接口进行互通。
对IAB节点而言，IAB节点的DU类似于gNB的DU，用于为其下附着的子节点(例如：终端或者其他IAB节点)提供接入服务，即Uu接口的功能。例如，DU可以 为终端或下一级的IAB节点提供无线连接的功能。MT具备终端的部分功能使得IAB节点10和宿主节点40之间能够通过Uu接口进行通讯；CU-UP为基站集中式模块中处理用户面数据的功能模块。
IAB节点的MT类似于终端，用于为IAB节点的DU下附着的子节点提供数据回传，将IAB节点的DU下附着的子节点的数据回传到宿主节点。其中，在终端接入IAB节点的场景下，终端对应的物理层(physical layer，PHY)/媒体接入控制(Medium Access Control，MAC)层/无线链路控制(radio link control，RLC)层功能位于终端接入的IAB节点的DU上。终端对应的分组数据汇聚协议(packet data convergence protocol，PDCP)协议层/业务数据适配协议(service data adaptation protocol，SDAP)/无线资源控制(radio resource control，RRC)层功能位于终端接入的IAB节点的CU上。其中，当IAB节点面向其父节点时，可以被看作为终端，即MT的角色。当IAB面向其子节点(子节点可能是另一IAB节点，或者接入该IAB节点的终端)时，其可被看作接入设备，即作为DU的角色。
另一种示例，当IAB节点采用分离架构时，结合图3b，如图3d所示，MT和DU之间具有内部接口，但数据面模块30需要和IAB节点之间建立新的接口y，用来承载原来N4接口传输的内容。例如，如图3d所示，DU和CU-UP之间具有F1-U接口。此时需要CU-UP和IAB节点10建立新的接口x，用来承载原来E1接口传输的内容。
图3d中，CU-UP和数据面模块30交互用户面数据之前，需要建立终端粒度的用户面通道，建立方式可以参考N3隧道建立流程，此处不再赘述。在数据面模块30和IAB节点设置于同一个设备的场景下，区别于图3d，CU-UP是IAB的内部模块，IAB和数据面模块30交互用户面数据之前，需要先建立终端粒度的用户面通道。
可选的，图3a～图3d所示的通信系统可以应用于目前的5G网络架构以及未来出现的其它的网络架构，本申请实施例对此不作具体限定。
下述将以如图3a～图3d所示的通信系统适用于5G网络架构为例，例如，以图3a～图3d所示的通信系统适用于如图4a或图4b所示的5G网络架构为例：
示例性的，以图3a～图3d所示的通信系统应用于目前的非漫游5G网络架构中的基于接口的架构为例，移动管理网元40、会话管理网元30可以为属于5G核心网(5G core network，5GC)中的网元，宿主节点50、IAB节点10可以为5G接入网中的网元。
示例性的，如图4a或图4b所示，上述的网管网元70所对应的网元或者实体可以为运行管理和维护(operation，administration and maintenance，OAM)网元(也可以称为运行管理维护网元)。比如会话管理网元30所对应的网元或者实体可以为如图4a或图4b所示的5G网络架构中的会话管理功能(Session Management Function，SMF)网元。移动管理网元40可以为接入和移动性管理功能(Access and Mobility Management Function，AMF)网元。宿主节点50或IAB节点10可以为接入网络(access network，AN)设备或者无线接入网络(radio access network，RAN)设备。数据面模块30所对应的网元或者实体可以为如图4a或图4b所示的5G网络架构中的用户面功能(user plane function，UPF)网元。网络存储网元80所对应的网元或者实体可以为如图4a或图4b所示的5G网络架构中的网络功能库(network repository function，NRF)网元。
此外，如图4a或图4b所示，5G网络架构还可以包括：策略控制功能(Policy Control  Function，PCF)网元、应用功能(application function，AF)网元、数据网络(data network，DN)、鉴权服务器功能或认证服务器功能(authentication server function，AUSF)网元、统一数据库(Unified Data Repository，UDR)(图4a或图4b中未示出)、统一数据管理(Unified Data Management，UDM)、网络切片选择功能(Network Slice Selection Function，NSSF)网元、网络暴露功能(Network Exposure Function，NEF)网元等，本申请实施例对此不作具体限定。
其中，如图4a所示，终端通过下一代网络(Next generation，N1)接口(简称N1)与AMF网元通信。接入设备通过N2接口(简称N2)与AMF网元通信。接入设备通过N3接口(简称N3)与UPF网元通信。UPF网元通过N6接口(简称N6)与DN通信。任意两个UPF网元之间通过N9接口(简称N9)通信。UPF网元通过N4接口(简称N4)与SMF网元通信。AMF网元通过N11接口(简称N11)与SMF网元通信。AMF网元通过N8接口(简称N8)与UDM网元通信。SMF网元通过N7接口(简称N7)与PCF网元通信。SMF网元通过N10接口(简称N10)与UDM网元通信。AMF网元通过N12接口(简称N12)与AUSF网元通信。AMF网元通过N22接口(简称N22)与NSSF网元通信。AUSF网元通过N13接口(简称N13)与UDM网元通信。UDM网元与UDR网元通信。PCF网元与UDR网元通信，BSF网元与PCF网元和SMF网元通信。
如图4b示出了5G网络架构中基于服务化接口的架构，该架构与图4a的区别在于，在图4b中5GC中的控制面网元也可以采用服务化接口进行交互。例如，AMF网元、AUSF网元、SMF网元、UDM网元、UDR网元、NRF网元、NEF网元、NSSF网元或者PCF网元采用服务化接口进行交互。比如，AMF网元对外提供的服务化接口可以为Namf。SMF网元对外提供的服务化接口可以为Nsmf。UDM网元对外提供的服务化接口可以为Nudm。UDR网元对外提供的服务化接口可以为Nudr。PCF网元对外提供的服务化接口可以为Npcf。NEF网元对外提供的服务化接口可以为Nnef。NRF网元对外提供的服务化接口可以为Nnrf。NSSF网元对外提供的服务化接口可以为Nnssf。应理解，图4b中各种服务化接口的名称的相关描述可以参考23501标准中的5G系统架构(5G system architecture)图，在此不予赘述。
需要说明的是，图4a或图4b中的各个网元之间的接口名字只是一个示例，具体实现中接口名字可能为其他名字，本申请实施例对此不作具体限定。
需要说明的是，图4a或图4b的接入设备、AF网元、AMF网元、SMF网元、AUSF网元、UDM网元、UPF网元和PCF网元等仅是一个名字，名字对设备本身不构成限定。在5G网络以及未来其它的网络中，接入设备、AF网元、AMF网元、SMF网元、AUSF网元、UDM网元、UPF网元和PCF网元所对应的网元也可以是其他的名字，本申请实施例对此不作具体限定。例如，该UDM网元还有可能被替换为用户归属服务器(home subscriber server，HSS)或者用户签约数据库(user subscription database，USD)或者数据库实体，等等，在此进行统一说明，后续不再赘述。
图4a或图4b中的终端、(R)AN、UPF和DN一般被称为用户层网络功能实体，终端的数据流量可以通过终端和DN之间建立的分组数据单元(packet data unit，PDU)会话(Session)进行传输，传输会经过(R)AN和UPF这两个网络功能(实体)；而其他 的部分则被称为控制层网络功能和实体，主要负责认证和鉴权、注册管理、会话管理、移动性管理以及策略控制等功能，从而实现用户层流量可靠稳定的传输。本申请实施例中涉及到的PDU会话指在终端与数据网络之间提供PDU连接服务的一种连接(association between the UE and a Data Network that provides a PDU connectivity service)。
图4a和图4b为终端通过3GPP接入技术接入5G网络的系统架构，图4c出了本申请一实施例中终端使用多个接入技术(例如3GPP接入技术和非3GPP接入技术)接入网络的架构示意图，例如，终端使用3GPP接入技术和non-3GPP接入技术的架构。如图4c所示，终端可以通过3GPP接入技术和non-3GPP接入技术连接到接入和移动性管理功能网元。
具体的，如图4c所示，终端在使用non-3GPP接入技术接入AMF网元时，可以通过非3GPP互通功能(non-3GPP interworking function，N3IWF)实体接入AMF网元。当3GPP与non-3GPP属于相同PLMN时，终端选择相同AMF网元。当3GPP与non-3GPP属于不同PLMN时，可以选择不同的AMF网元。
SMF网元由AMF网元选择，不同的会话(例如，PDU会话)可以选择不同的SMF网元，但相同的会话要选择相同的SMF网元。SMF网元可以为会话选择UPF网元，一个会话可以有多个UPF网元，所以SMF网元可能会选择多个UPF网元为某会话创建隧道连接。
其中，AUSF网元和鉴权存储功能(authetnication repository function，ARPF)/UDM网元构成归属公共陆地移动网(home public land mobile network，HPLMN)，终端通过不同的接入技术接入网络时，可以具有不同的受访地公用陆地移动网(visited public land mobile network，VPLMN)，也可以具有相同的受访地公用陆地移动网。具体的，图4c中所示的各个网元的功能可以参见上述实施例，本申请在此不再赘述。
应理解，在无线回传系统中，该接入设备(也可以称为接入网设备)可以包括宿主节点以及一个或多个IAB节点。
本申请实施例中的3GPP接入技术可以为符合3GPP标准规范的接入技术，例如，第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)接入技术。例如，5G系统中采用的接入技术。采用3GPP接入技术的接入网络称为无线接入网络(Radio Access Network，RAN)。例如，终端可以使用3GPP接入技术通过5G系统中的接入网设备接入无线网络中。其中，接入网设备可以为基站。例如，5G系统中的接入网设备称为下一代基站节点(Next Generation Node Basestation，gNB)、演进型节点B(evolved Node B，eNB)等。
non-3GPP可以为不在3GPP标准规范中定义的无线接入技术，例如称为非第三代合作伙伴计划(non 3rd Generation Partnership Project，non3GPP)接入技术。非3GPP接入技术可以是非可信non3GPP接入技术，也可以是可信non3GPP接入技术。非3GPP接入技术可以包括：无线保真(Wirelessfidelity，Wi-Fi)、全球微波互联接入(Worldwide Interoperability for Microwave Access，WiMAX)、码分多址(Code Division Multiple Access，CDMA)、无线局域网(Wireless Local Area Networks，WLAN)，固网技术或者有线技术等。终端可以通过以无线保真(Wireless Fidelity，WIFI)为代表的空口技 术接入网络。其中，接入网设备可以为接入点(Access Point，AP)。
图3a-图3d是应用于本申请实施例的网络架构。下面对该网络架构中涉及的各个部分或网元在5G网络中的功能为例分别进行说明。
(1)、本申请实施例中的回传节点又可以称为无线回传节点、无线回传设备、中继节点(relay node，RN)或IAB节点(IAB node)。为便于描述，本申请实施例以IAB节点为例进行说明。IAB节点可以为终端提供无线接入服务，该终端的上行数据(例如，包括上行用户面数据和上行控制面信令)通过无线接入链路传输至IAB节点。然后，由IAB节点将终端的上行数据或者来自子节点的上行数据通过无线回传链路传输到宿主节点40。该终端的下行数据(包括下行用户面数据和下行控制面信令)由宿主节点40通过无线回传链路发送至IAB节点，再由IAB节点10通过无线接入链路传输至终端。
(2)、宿主节点40又称为IAB宿主(IAB donor)或者宿主回传节点或者宿主基站。下述实施例将以Donor节点为例进行描述。在4G网络中，该Donor节点可以为演进型宿主基站(Donor eNodeB，DeNB)。在5G网络中，该宿主节点可以为下一代宿主基站(Donor gNodeB，DgNB)。
(3)、终端(terminal)可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备；还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication，MTC)终端、用户设备(user equipment，UE)，移动台(mobile station，MS)，终端设备(terminal device)或者中继用户设备等。其中，中继用户设备例如可以是5G家庭网关(residential gateway，RG)。为方便描述，本申请中，上面提到的设备统称为终端。
应理解，本申请实施例中的终端可以为港口、智能工厂、铁路交通、物流、无人机、无人驾驶汽车等多种垂直行业应用领域中的终端。例如：移动机器人(Mobile Robot)、自动导引车(Automated Guided Vehicle，AGV)，无人驾驶汽车，列车上的控制设备和传感器、如图1-1或图2所示的工厂中部署的控制设备和传感器(Sensor)等。
作为示例，在本申请实施例中，该终端还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。如图1-1或图2所示，该终端还可以为应用于工厂的传感器设备。
(4)、接入设备用于为特定区域的授权终端提供入网功能，并能够根据终端的级 别，业务的需求等使用不同质量的传输隧道。接入设备能够管理无线资源，为终端设备提供接入服务，进而完成控制信号和终端设备数据在终端设备和核心网之间的转发，接入设备也可以理解为传统网络中的基站。例如，可以负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。
接入设备可以是无线网络中的设备。接入设备也可以称为无线接入设备或者网络设备。例如将终端接入到无线网络的无线接入网(radio access network，RAN)节点。目前，一些接入设备的举例为：第五代(5th generation，5G)系统中的下一代节点B(The Next Generation Node B，gNB)、传输接收点(transmission reception point，TRP)、LTE系统中的演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)，或无线保真(wireless fidelity，Wifi)接入点(access point，AP)等。在一种网络结构中，网络设备可以包括集中单元(centralized unit，CU)节点、或分布单元(distributed unit，DU)节点、或包括CU节点和DU节点的RAN设备。接入设备还可以是无线回传设备，车载设备，可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等。在第三代(3rd generation，3G)系统中，称为节点B(Node B)等。
(5)、移动管理网元，属于核心网网元，主要负责信令处理部分，例如：接入控制、移动性管理、附着与去附着以及网关选择等功能。AMF网元为终端中的会话提供服务的情况下，会为该会话提供控制面的存储资源，以存储会话标识、与会话标识关联的SMF网元标识等。
在5G通信系统中，该移动管理网元可以是AMF网元。在未来通信系统中，移动管理网元仍可以是AMF网元，或者，还可以有其它的名称，本申请不做限定。
(6)、不可信的非3GPP接入网(Untrusted non-3GPP Access Network)设备，该网元允许终端和3GPP核心网之间采用非3GPP技术互连互通，其中非3GPP技术例如：无线保真(WirelessFidelity，Wi-Fi)、全球微波互联接入(Worldwide Interoperability for Microwave Access，WiMAX)、码分多址(Code Division Multiple Access，CDMA)网络等，相对于可信的非3GPP接入网设备可以直接接入3GPP核心网，该网元需要通过安全网关建立的安全隧道来与3GPP核心网互连互通，其中安全网关例如：演进型分组数据网关(Evolved Packet Data Gateway，ePDG)或者非3GPP互通功能(Non-3GPP InterWorking Function，N3IWF)网元。
(7)、会话管理网元，负责用户面网元选择，用户面网元重定向，因特网协议(internet protocol，IP)地址分配，承载的建立、修改和释放以及QoS控制。会话管理、终端的网络互连协议(internet protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
在5G通信系统中，该会话管理网元可以是SMF网元。在未来通信系统中，会话管理网元仍可以是SMF网元，或者，还可以有其它的名称，本申请不做限定。
(8)、数据面模块，负责终端中用户数据的转发和接收。可以从数据网络接收用户数据，通过接入网设备传输给终端设备；数据面模块还可以通过接入网设备从终端 接收用户数据，转发到数据网络。数据面模块中为终端提供服务的传输资源和调度功能由会话管理网元管理控制的。
在5G通信系统中，该数据面模块可以是UPF网元或UPF模块。在未来通信系统中，数据面模块仍可以是UPF网元或UPF模块，或者，还可以有其它的名称，本申请不做限定。
(9)、认证服务器功能网元，主要提供认证功能，支持3GPP接入和Non-3GPP接入的认证，具体可参考3GPP TS 33.501。
在未来通信系统中，认证服务器功能网元仍可以是AUSF网元，或者，还可以有其它的名称，本申请不做限定。
(10)、NEF网元，主要支持3GPP网络和第三方应用安全的交互，NEF能够安全的向第三方暴露网络能力和事件，用于加强或者改善应用服务质量，3GPP网络同样可以安全的从第三方获取相关数据，用以增强网络的智能决策；同时该网元支持从统一数据库恢复结构化数据或者向统一数据库中存储结构化数据。
(11)、UDR网元，主要负责存储结构化数据，存储的内容包括签约数据和策略数据、对外暴露的结构化数据和应用相关的数据。
(12)、AF网元，主要支持与3GPP核心网交互来提供服务，例如影响数据路由决策，策略控制功能或者向网络侧提供第三方的一些服务。
(13)、网络存储网元，用于维护网络中所有网络功能服务的实时信息。NRF保存有部署的网络功能(Network function，NF)组件的信息，例如NF组件的标识和网络地址、支持的网络切片的标识、或者数据面实例的信息等，NRF向其它NF提供NF组件的注册和发现等服务。
在未来通信系统中，网络存储网元仍可以是NRF网元，或者，还可以有其它的名称，本申请不做限定。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。
如图5所示，图5示出了本申请实施例中的一种通信设备的硬件结构示意图。会话管理网元20、IAB节点10、移动管理网元40的结构可以参考图5所示的结构。该通信设备包括处理器51，通信线路54以及至少一个通信接口(图5中仅是示例性的以包括通信接口53为例进行说明)。
可选的，该通信设备还可以包括存储器52。
处理器51可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路54可包括一通路，在上述组件之间传送信息。
通信接口53，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。
存储器52可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者 可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路54与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器52用于存储执行本申请方案的计算机执行指令，并由处理器51来控制执行。处理器51用于执行存储器52中存储的计算机执行指令，从而实现本申请下述实施例提供的一种通信方法。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器51可以包括一个或多个CPU，例如图5中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信设备可以包括多个处理器，例如图5中的处理器51和处理器55。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在本申请实施例中，一种通信方法的执行主体的具体结构，本申请实施例并未特别限定，只要可以通过运行记录有本申请实施例的一种通信方法的代码的程序，以根据本申请实施例的一种通信方法进行通信即可，例如，本申请实施例提供的一种通信方法的执行主体可以是会话管理网元中能够调用程序并执行程序的功能模块，或者为应用于会话管理网元中的通信装置，例如，芯片。本申请实施例提供的一种通信方法的执行主体可以是IAB节点中能够调用程序并执行程序的功能模块，或者为应用于IAB节点中的通信装置，例如，芯片。本申请对此不进行限定。本申请实施例提供的一种通信方法的执行主体可以是移动管理网元中能够调用程序并执行程序的功能模块，或者为应用于移动管理网元中的通信装置，例如，芯片。下述实施例以一种通信方法的执行主体为IAB节点、移动管理网元、会话管理网元为例进行描述。
需要指出的是，本申请各实施例之间可以相互借鉴或参考，例如，相同或相似的步骤，方法实施例和装置实施例之间，均可以相互参考，不予限制。
结合图3a～图3d，如图6所示，本申请实施例提供的一种通信方法包括：
步骤601、会话管理网元20确定目标数据面实例的信息。该目标数据面实例的信息包括路由指示(例如，N4 Routing Indicator)。其中，该路由指示用于会话管理网元20确定目标数据面实例的地址。该目标数据面实例与IAB节点10关联。
本申请实施例中会话管理网元20处具有数据面实例集合。该数据面实例集合中至少包括数据面模块30对应的一个或多个数据面实例的信息。当然，该数据面实例集合中还可以具有处数据面模块以外的其他模块的实例的信息。
该一个或多个数据面实例的信息可以由IAB节点10通过Donor节点50或OAM网元60或AMF网元注册至会话管理网元20，具体过程详见下述步骤605以及步骤 606中Donor节点50或OAM网元60或AMF网元向会话管理网元20注册一个或多个数据面实例的信息的过程。另一方面，本申请实施例中会话管理网元20可以从NRF网元处获取一个或多个数据面实例的信息，具体过程详见下述步骤600。
相应的，本申请实施例中的步601可以通过以下方式实现：会话管理网元20根据预设条件，从一个或多个数据面实例的信息中确定目标数据面实例的信息。例如，预设条件为DNN、S-NSSAI、会话管理网元20的区域标识(Area ID)、负载等信息。会话管理网元20的Area ID表示会话管理网元管理的区域的标识。
应理解，数据面实例每处理一个终端的用户面的数据，会耗费UPF实例的各种资源(计算，存储和网络)，负载会相应提高，DNN能够反映终端的用户面传输的业务类型，同样一定程度上能够反映DN的入口位置，其他的条件同样反应业务，或反应位置信息，会话管理网元20参考这些因素，综合选择能够支持这些业务，以及位置最优的(时延短)数据面实例作为目标数据面实例。
示例性的，目标数据面实例的地址可以为IAB节点10的地址，或者IAB节点10的标识(例如，永久身份标识(subscriber permanent identifier，SUPI))。该目标数据面实例与IAB节点10关联可以理解为：目标数据面实例对应的数据面模块30位于IAB节点10内部，或者目标数据面实例对应的数据面模块30和IAB节点10位于同一个设备。本申请实施例中的数据面模块30具有路由和转发的功能。当数据面模块30和IAB节点10位于同一个设备时，会话管理网元20在寻址目标数据面实例时，可以先确定IAB节点10的地址或标识。然后执行下述步骤602。
步骤602、会话管理网元20向为IAB节点10提供服务的移动管理网元40或Donor节点50发送N4会话管理请求消息和第一指示，以使得移动管理网元40或Donor节点50接收来自会话管理网元20的N4会话管理请求消息和第一指示。该第一指示用于指示IAB节点10向目标数据面实例发送N4会话管理请求消息。
应理解，移动管理网元40或Donor节点50除了为IAB节点10提供服务外，还可以为其他设备提供服务。或者移动管理网元40或Donor节点50仅为IAB节点10提供服务，本申请实施例对此不作限定。
示例性的，第一指示还可以用于指示数据面实例的标识，或者会话管理网元20还可以向IAB节点发送目标数据面实例的标识。这样便于IAB节点10确定向目标数据面实例的标识关联的目标数据面实例发送N4会话管理请求消息。本申请实施例中的N4会话管理请求消息可以为N4会话建立请求消息，N4会话建立请求消息用于请求。或者，本申请实施例中的N4会话管理请求消息可以为N4会话删除请求消息。或者，本申请实施例中的N4会话管理请求消息可以为N4会话修改(或更新)请求消息，
应理解，会话管理网元20通过N4会话建立请求与目标数据面实例建立连接，后续会话管理网元20通过N4接口下发用户面执行指令和策略规则。会话管理网元20通过N4会话修改请求消息修改下发到目标数据面实例的策略规则和用户面执行指令。会话管理网元20通过N4会话删除请求消息可以删除会话管理网元20与目标数据面实例建立的连接。
本申请实施例中的N4会话管理请求消息主要指针对目标数据面实例的会话管理请求消息，该N4会话管理请求消息还可以采用其他名称。例如，Nx会话管理请求消 息。Nx表示会话管理网元20和数据面模块30之间的接口。
步骤603、移动管理网元40或Donor节点50向IAB节点10发送N4会话管理请求消息和第一指示，以使得IAB节点10接收来自移动管理网元40或Donor节点50的N4会话管理请求消息和第一指示。
步骤604、IAB节点10根据第一指示，向目标数据面实例发送N4会话管理请求消息，N4会话管理请求消息用于指示管理数据面实例的会话上下文。
本申请实施例中的目标数据面实例所属的数据面模块30可以如图3a或图3c所示集成在IAB节点10内，也即IAB节点10内具有目标数据面实例所属的数据面模块30。当然，如图3b或图3d所示，该IAB节点10也可以和目标数据面实例所属的数据面模块30属于同一个设备。后续图6-图8中以IAB节点10和目标数据面实例对应的数据面模块30位于同一个设备中为例。
如图3c所示，当IAB节点10内具有目标数据面实例所属的数据面模块30时，本申请实施例中的步骤604可以通过以下方式实现：IAB节点10内的单元(MT部分/DU部分/CU-UP)可以通过内部接口向数据面模块30发送N4会话管理请求消息。
举例说明，如果通过NAS传，MT部分可以通过内部接口向数据面模块30发送N4会话管理请求消息。如果F1传输，MT部分可以通过内部接口向DU发送N4会话管理请求消息，然后由DU向数据面模块30发送N4会话管理请求消息。如果通过E1接口传输，MT部分可以通过内部接口向CU-UP发送N4会话管理请求消息，由CU-UP向数据面模块30发送N4会话管理请求消息。
如图3d所示，IAB节点10也可以和目标数据面实例所属的数据面模块30属于同一个设备时，本申请实施例中的步骤604可以通过以下方式实现：IAB节点10可以通过接口Ny向数据面模块30发送N4会话管理请求消息。
本申请实施例提供一种通信方法，该方法在会话管理网元确定目标数据面实例的信息后，由于目标数据面实例的信息中包括路由指示。因此，会话管理网元可以根据路由指示确定目标数据面实例的地址，以使得会话管理网元正确寻址目标数据面实例。由于目标数据面实例与IAB节点关联，因此会话管理网元可以向IAB节点发送N4会话管理请求消息，以实现对目标数据面实例的管理。该方案可以实现N4接口无线化后带来的目标数据面实例注册和管理。
在一种可能的实施例中，如图7所示，本申请实施例提供的方法在步骤601之前还可以包括：
步骤605、IAB节点10向OAM网元/Donor节点50/移动管理网元40发送第一消息，以使得网管网元70/Donor节点50/移动管理网元40接收第一消息。该第一消息包括数据面模块30的一个或多个数据面实例的信息。该第一消息用于指示网管网元70/Donor节点50/移动管理网元40向网络存储网元80或会话管理网元20注册一个或多个数据面实例的信息。
其中，一个或多个数据面实例的信息中任一个数据面实例的信息包括路由指示；路由指示用于会话管理网元20确定任一个数据面实例的地址；任一个数据面实例与IAB节点关联。
在一种可能的实现方式中，任一个数据面实例的信息中还可以包括以下信息中的 任一个或多个：用于指示数据面实例的类型信息，或，数据面实例的配置信息。
例如，用于指示数据面实例的类型信息可以为数据面类型(例如，UPF类型)。例如，数据面实例的配置信息可以包括以下信息中的任一个或多个：如DNN、S-NSSAI、SMF Area ID等信息。
应理解，如果第一消息本身具有用于指示网管网元70/Donor节点50/移动管理网元40向网络存储网元80注册一个或多个第一数据面实例的信息的含义或功能，则第一消息中可以不携带注册指示，当然，第一消息中也可以携带注册指示。如果第一消息不具有用于指示网管网元70/Donor节点50/移动管理网元40向网络存储网元80注册一个或多个数据面实例的信息的含义或功能，则第一消息中携带注册指示。该注册指示用于指示网管网元70/Donor节点50/移动管理网元40向网络存储网元80注册一个或多个数据面实例的信息。
本申请实施例中IAB节点10可以显示指示或隐式指示网管网元70/Donor节点50/移动管理网元40向网络存储网元80或会话管理网元20注册一个或多个数据面实例的信息。
示例1-1)、新的IE类型(显示指示)。
作为第一种可能的实现方式，第一消息中包括负荷容器(Payload Container)，也可以称为实例注册容器(Register Container)。其中，Payload Container中包括一个或多个数据面实例的信息，Payload Container的类型用于指示第一设备向会话管理网元20或者NRF网元注册一个或多个数据面实例的信息。即如果需要在Payload Container中传输一个或多个数据面实例的信息，则需要定义的Payload Container的类型用于指示第一设备向会话管理网元20或者NRF网元注册一个或多个数据面实例的信息。或者第一消息中包括负荷容器和用于指示负荷容器的类型的字段。
本申请实施例中第一消息具有携带负荷容器的功能。或者第一消息为NAS消息。
示例1-2)、新的IE字段(显示指示)。
作为第二种可能的实现方式，第一消息中包括注册指示和一个或多个数据面实例的信息，注册指示用于指示第一设备向会话管理网元20或者网络存储网元80注册一个或多个数据面实例的信息。
示例1-3)、隐式指示。
如果定义了专用的操作接口(如服务化接口)，则指示可以解释成接口本身，因为定义了操作接口，实际上也定义操作的逻辑，这样就不再需要显式的指示。例如，IAB节点10和第一设备之间具有预定义的操作接口，所述预定义的操作接口用于指示所述第一设备向会话管理网元20或者网络存储网元80注册一个或多个数据面实例的信息，因此，本申请实施例中的步骤605可以通过以下方式实现：IAB节点10通过预定义的操作接口向第一设备发送第一消息，以使得第一设备通过预定义的操作接口接收第一消息。
需要说明的是示例1-1)～示例1-3)可以单独指示，也可以结合。
步骤606、网管网元70/Donor节点50/移动管理网元40根据第一消息，向网络存储网络80或者会话管理网元20注册一个或多个数据面实例的信息。以使得网络存储网络80或者会话管理网元20接收数据面模块的一个或多个数据面实例的信息，所述 一个或多个数据面实例包括所述目标数据面实例。
应理解，图7中仅示例出了IAB节点向移动管理网元40发送第一消息，以及移动管理网元40向网络存储网络80注册一个或多个数据面实例的信息的过程。
示例2-1、IAB节点10通过网管网元70向网络存储网络80注册一个或多个数据面实例的信息的过程。
具体的，IAB节点10和网管网元70之间具有用户面连接，IAB节点10通过与网管网元70之间的用户面连接向网管网元70发送一个或多个数据面实例的信息。
示例性的，如果IAB节点10采用示例1-1)指示网管网元70向网络存储网络80注册一个或多个数据面实例的信息，则一个或多个数据面实例的信息在网管网元70处透传，即网管网元70不解析负荷容器的内容，作为一种可能的实现方式，本申请实施例中的步骤606可以通过以下方式实现：网管网元70可以直接向网络存储网络80发送负荷容器。
如果IAB节点10采用示例1-2)或示例1-3)指示网管网元70向网络存储网络80注册一个或多个数据面实例的信息，或者网管网元70可以解析负荷容器，得到一个或多个数据面实例的信息，则作为另一种可能的实现方式，本申请实施例中的步骤606可以通过以下方式实现：网管网元70根据网管网元70和网络存储网络80之间定义的接口构建实例注册信息。其中，实例注册信息包括一个或多个数据面实例的信息。网管网元70向网络存储网络80发送实例注册信息。也即一个或多个数据面实例由移动管理网元处理后发送至会话管理网元20或网络存储网元80。
示例2-2、IAB节点10通过移动管理网元40向会话管理网元50或网络存储网络80注册一个或多个数据面实例的信息的过程。
此时，第一消息可以为N1 NAS消息。
作为一种可能的实现方式，如果IAB节点10采用示例1-1)指示移动管理网元40向网络存储网络80或会话管理网元20注册一个或多个数据面实例的信息，且一个或多个数据面实例的信息在移动管理网元40处透传，即移动管理网元40不解析负荷容器的内容，本申请实施例中的步骤606可以通过以下方式实现：移动管理网元40通过移动管理网元40和网络存储网络80之间定义的接口向网络存储网络80发送负荷容器。或者移动管理网元40通过移动管理网元40和网络存储网络80之间定义的接口向网络存储网络80发送第四消息。第四消息中携带负荷容器。或者移动管理网元40通过移动管理网元40和会话管理网元20之间定义的接口向会话管理网元20发送负荷容器，或者向会话管理网元20发送第三消息。第三消息中包括负荷容器。
作为一种可能的实现方式，如果IAB节点10采用示例1-1)～示例1-3)指示移动管理网元40向网络存储网络80或会话管理网元20注册一个或多个数据面实例的信息，且移动管理网元40可以感知负荷容器中的内容，则本申请实施例中的步骤606可以通过以下方式实现：移动管理网元40通过移动管理网元40和网络存储网络80之间定义的接口向网络存储网络80发送第四消息，此时第四消息中携带一个或多个数据面实例的信息。或者，移动管理网元40通过移动管理网元40和会话管理网元20之间定义的接口向会话管理网元20发送第三消息。其中，第三消息中携带一个或多个数据面实例的信息。
示例2-3、IAB节点10通过宿主节点50向会话管理网元50或网络存储网络80注册一个或多个数据面实例的信息的过程。此时，第一消息可以为F1消息或E1消息。
相应的，以一个或多个数据面实例的信息位于负荷容器中为例，本申请实施例提供的步骤605可以通过以下方式实现：IAB节点10向Donor节点50发送F1消息或E1消息，以使得Donor节点50接收F1消息或E1消息。其中，F1消息或E1消息中携带注册指示和负荷容器。或者F1消息或E1消息中携带负荷容器。Donor节点50根据注册指示或负荷容器向移动管理网元40发送第二消息，以使得移动管理网元40接收来自Donor节点50的第二消息。该第二消息中携带负荷容器和第三指示。该第三指示用于指示移动管理网元40向会话管理网元20或网络存储网络80注册一个或多个数据面实例的信息。移动管理网元40根据第二消息向会话管理网元20或网络存储网络80发送负荷容器。
关于示例2-3中移动管理网元40接收到负荷容器之后向会话管理网元20或网络存储网络80注册一个或多个数据面实例的信息的过程，可以参考上述示例2-2中的描述，此处不再赘述。
需要说明的是，如果一个或多个数据面实例的信息由IAB节点10通过示例2-1～示例2-3注册在网络存储网元处，则如图7所示，本申请实施例提供的方法在步骤601之前还可以包括：
步骤600、会话管理网元10从网络存储网元80处获取一个或多个数据面实例的信息，一个或多个数据面实例包括目标数据面实例。
本申请实施例中的步骤600的具体实现方式可以参考下述步骤1201的具体实现，此处不再赘述。
由于会话管理网元20本地存在或不存在IAB节点的上下文，使得步骤602的具体实现存在差异，因此下述将分别介绍：
示例3-1)、会话管理网元20本地存在IAB节点的上下文。
在一种可能的实施例中，如图7所示，本申请实施例提供的方法在步骤602之前还可以包括：
步骤607、会话管理网元20确定会话管理网元本地存在IAB节点的上下文。
相应的，如图7所示，作为一种可能的实现方式，本申请实施例提供的步骤602具体可以通过以下方式实现：
步骤6021、会话管理网元20根据IAB节点的上下文生成会话管理非接入层(Non-access stratum，NAS)消息。其中，会话管理NAS层消息包括N4会话管理请求消息和第一指示。
步骤6022、会话管理网元20通过移动管理网元40向IAB节点发送会话管理NAS层消息，以使得移动管理网元40接收来自会话管理网元20的会话管理NAS层消息。
相应的，步骤603可以通过以下方式具体实现：移动管理网元40向IAB节点10发送会话管理NAS层消息，以使得IAB节点10接收会话管理NAS层消息。
可以理解的是，如图7所示的方案可以适用于对单个移动管理网元和单个会话管理网元的场景，即终端所选择的移动管理网元以及会话管理网元和IAB节点10所选择的移动管理网元以及会话管理网元相同。
终端和会话管理网元20之间使用会话管理(session Manage，SM)NAS消息进行交互，具体地，移动管理网元40接收到会话管理相关的NAS消息后会转发给会话管理网元20，后续的会话管理网元20将对应的响应消息发送给移动管理网元40，由移动管理网元40通过NAS消息转发给终端。
终端和移动管理网元40之间使用移动性管理(Mobility Manage，MM)NAS消息进行交互，具体地，移动管理网元40接收到MM NAS消息后，直接进行处理，对应的响应消息也直接通过NAS转发给终端。
示例3-2)、会话管理网元20本地不存在IAB节点的上下文。
步骤608、会话管理网元20确定会话管理网元本地不存在IAB节点的上下文。
相应的，如图8所示，作为一种可能的实现方式，本申请实施例提供的方法在步骤603之前还可以包括：
步骤609、会话管理网元20向移动管理网元40发送路由指示，以使得移动管理网元40接收来自会话管理网元20的路由指示。
作为一种可选的实现：该路由指示可以和N4会话管理请求消息和第一指示携带在同一个消息中发送至移动管理网元40。
步骤610、移动管理网元40根据路由指示确定移动管理网元本地具有IAB节点的上下文后，移动管理网元40根据IAB节点的上下文生成移动性管理NAS消息。其中，移动性管理NAS消息包括N4会话管理请求消息和第一指示。
作为一种可选的实现方式，移动管理网元40根据路由指示确定移动管理网元本地具有IAB节点的上下文后，移动管理网元40还可以向会话管理网元20发送确认信息。该确认信息用于表示移动管理网元本地具有IAB节点的上下文。或者，本申请实施例提供的步骤610还可以通过以下方式替换：移动管理网元40根据路由指示直接生成移动性管理NAS消息，也即移动管理网元40无需判断是否存在IAB节点的上下文。接收到该确认信息之后，会话管理网元20便可以根据确认信息确定此移动管理网元40可以为IAB节点提供服务。
相应的，作为一种可能的实现方式，本申请实施例中的步骤603可以通过以下方式具体实现：移动管理网元40向IAB节点10发送移动性管理NAS消息。
需要说明的是，针对于多个移动管理网元和多个会话管理网元的场景，即终端选择的会话管理网元和IAB节点10选择的会话管理网元不同，终端选择的移动管理网元和IAB节点10选择的移动管理网元也不同，则在一种可能的实施例中，如图8所示，本申请实施例提供的方法在步骤609之前还可以包括：
步骤611、会话管理网元20从用户数据管理网元处获取IAB节点10的移动管理网元的信息。示例性的，用户数据管理网元可以为UDM网元或者UDR网元。
例如，移动管理网元40的信息可以为移动管理网元40的地址或者标识或者位置。
应理解，本申请实施例提供的方法在步骤611之前，还可以包括：会话管理网元20向第一移动管理网元(例如，该第一移动管理网元为为终端提供服务的移动管理网元)发送用于校验第一移动管理网元本地是否存在IAB节点的上下文的指示信息，如果第一移动管理网元本地不具有IAB节点的上下文，则第一移动管理网元向会话管理网元发送用于指示第一移动管理网元本地不具有IAB节点的上下文的指示，这样会话 管理网元便可以执行步骤611，以确定该IAB节点所接入的移动管理网元的信息。
具体的，步骤611可以通过以下方式实现：
(1)、如果路由指示的实际值为IAB节点10的标识(例如，SUPI)，则可以通过现有的UDM查询接口查询移动管理网元40的的信息(如标识、位置等)；(2)如果路由指示为IAB节点10的其他标识(其他标识例如可以为能够唯一标识IAB节点的标识)，可以增强现有的UDM查询方法，直接通过路由指示向用户数据管理网元查询移动管理网元的信息；(3)如果路由指示为IAB节点10的其他标识，则会话管理网元20可以先根据IAB节点10的其他标识，确定IAB节点10的SUPI，然后利用SUPI从用户数据管理网元处获取移动管理网元40的信息。
其中，会话管理网元20中具有IAB节点10的其他标识和SUPI之间的映射关系，会话管理网元20根据映射关系，可以确定IAB节点10的SUPI。或者用户数据管理网元具有该映射关系，会话管理网元20向用户数据管理网元发送IAB节点10的其他标识，以从用户数据管理网元处获取IAB节点10的SUPI。
可以理解的是，如果针对单个移动管理网元和多个会话管理网元的场景，该场景下终端选择的会话管理网元和IAB节点10选择的会话管理网元不同，则步骤611可以省略。
作为一种可能的实施例，如果会话管理网元20通过Donor节点50向IAB节点10发送N4会话管理请求消息和第一指示，则本申请实施例提供的方法还包括：会话管理网元20向Donor节点50发送路由指示，以使得Donor节点50接收来自会话管理网元20的路由指示。相应的，Donor节点50根据路由指示向IAB节点20发送N4会话管理请求消息和第一指示。例如，Donor节点50根据路由指示向IAB节点20发送F1/E1消息。其中，F1/E1消息中包括N4会话管理请求消息和第一指示。
具体的，会话管理网元20通过移动管理网元40向Donor节点50发送路由指示。应理解，路由指示和N4会话管理请求消息和第一指示可以携带在同一个消息中由会话管理网元20通过移动管理网元40发送至Donor节点50。
作为一种可能的实施例，结合图7或图8，本申请实施例提供的方法在步骤604之后还可以包括：
步骤612、目标数据面实例向IAB节点10发送N4会话管理响应消息，以使得IAB节点10接收目标数据面实例发送的N4会话管理响应消息。例如，N4会话管理响应消息可以包括：确认信息(例如，ACK)，指示操作结果，以建立请求为例，通知会话管理网元哪些策略和执行指令成功部署，哪些无法部署。
步骤613、IAB节点10向Donor节点50或移动管理网元40发送第二指示，以及N4会话管理响应消息，以使得Donor节点50或移动管理网元40接收第二指示，以及N4会话管理响应消息。其中，第二指示用于指示向会话管理网元20发送N4会话管理响应消息。
步骤614、Donor节点50或移动管理网元40根据第二指示，向会话管理网元20发送N4会话管理响应消息，以使得会话管理网元20通过IAB节点10接收来自数据面实例的N4会话管理响应消息。
示例性的，如果由Donor节点50向会话管理网元20发送数据面实例的N4会话 管理响应消息，则步骤614可以通过以下方式实现：Donor节点50根据第二指示向移动管理网元40发送F1消息或E1消息，以使得移动管理网元40接收F1消息或E1消息。其中，该F1消息或E1消息中包括第三指示以及N4会话管理响应消息。移动管理网元40根据第三指示向会话管理网元20发送N4会话管理响应消息。
其中，第三指示用于指示会话管理网元20发送N4会话管理响应消息。第三指示的内容可以和第二指示的内容相同。当然，该第三指示的内容和可以和第二指示不同。例如，第二指示用于指示Donor节点50向会话管理网元20发送数据面实例的N4会话管理响应消息。第三指示用于指示移动管理网元40向会话管理网元20发送数据面实例的N4会话管理响应消息。
如图9所示，以数据面模块30为UPF模块，数据面实例为UPF实例、会话管理网元20为SMF网元、网管网元70为OAM网元，网络存储网元80为NRF网元为例，详细介绍本申请通信方法中涉及到的IAB节点10通过OAM网元向NRF网元注册数据面实例的过程，如图9所示，该方法包括：
步骤901、IAB节点和OAM网元建立用户面连接。
例如，IAB节点作为终端通过会话建立请求和OAM网元建立用户面连接。
用户面连接建立后，此时IAB节点可以通过用户面连接从OAM网元中获取各种IAB节点相关的配置信息，同时该用户面连接会一直维护，用于IAB节点上传状态信息等。例如，状态信息可以为运行状态，如负载。
步骤902、IAB节点通过用户面连接向OAM网元发送UPF实例的信息，以使得OAM网元通过用户面连接接收来自IAB节点的UPF实例的信息。
例如，IAB节点通过用户面连接向OAM网元发送用户面数据(User plane data)。
其中，UPF实例的信息具体包含：Indication(即上述第一指示)，指示OAM网元接收UPF实例的信息，并主动将该UPF实例的信息注册到NRF网元中。其中，UPF实例的信息包括：网络功能类型(NF type)，用于确定该UPF实例的类型为UPF；N4路由指示(Routing Indicator)(即上述路由指示)，用于SMF网元正确寻址UPF实例。UPF Provisioning Information，UPF实例的其他的配置信息，如DNN、S-NSSAI、SMF Area ID等信息。
关于Indication的具体指示方式可以参考第一指示的具体内容，此处不再赘述。
步骤903、OAM网元按照OAM网元和NRF网元之间定义的接口构建UPF实例注册信息。
其中，注册信息中包含：NF Type，N4 Routing Indicator和UPF Provisioning Information。
步骤904、OAM网元向NRF网元发送注册信息，以使得NRF网元接收来自OAM网元的注册信息。通过步骤904便可以实现向NRF网元注册该UPF实例信息。
可以理解的是，图9中的NRF网元也可以替换为SMF网元。当NRF网元被SMF网元替换后，也即IAB节点通过OAM网元向SMF网元注册数据面实例。
如图10所示，以数据面模块为UPF模块，数据面实例为UPF实例、会话管理网元为SMF网元为例，图10以IAB节点通过AMF网元向NRF网元或SMF网元注册数据面实例为例详细描述，本申请通信方法中涉及到的数据面实例注册过程，如图10 所示，该方法包括：
步骤1001、IAB节点向AMF网元发送N1 NAS消息，以使得AMF网元接收来自IAB节点的N1 NAS消息。其中，N1 NAS消息中包括Indication和UPF实例的信息。Indication用于指示AMF网元通过相应的服务化接口向NRF网元或SMF网元发送UPF实例的信息。
一方面，如果UPF实例的信息位于UPF实例注册容器中，此时UPF实例注册容器中的内容在AMF网元处透传，即AMF网元不解析UPF实例注册容器的具体内容。也即N1 NAS消息包括Indication和UPF实例注册容器(UPF Register Container)。
另一方面，如果AMF网元可以感知UPF实例内容的情况下，则N1 NAS消息包括Indication和UPF实例的信息。
如果AMF网元不解析UPF实例，则AMF网元采用方式(Option)1(包括步骤1002a或步骤1002b)向NRF网元或SMF网元发送UPF实例的信息。如果AMF网元解析UPF实例，则AMF网元采用方式2(包括步骤1003和步骤1004a，或者，步骤1003和步骤1004b)向NRF网元或SMF网元发送UPF实例的信息。
Option 1：
步骤1002a、AMF网元根据Indication向SMF网元发送N11消息(Message，Msg)，以使得SMF网元接收来自AMF网元的N11消息。其中N11消息中携带UPF实例注册容器。
应理解，AMF网元向SMF网元注册UPF实例的信息，目前SMF网元不存在提供此功能的服务化接口，需要在AMF网元和SMF网元之间增加提供此功能的服务化接口(即N11接口，简称N11)。
步骤1002b、AMF网元根据Indication向NRF网元发送网络功能管理注册消息(NF Management NF register)，以使得SMF网元接收来自AMF网元的网络功能管理注册消息。其中网络功能管理注册消息中携带UPF实例注册容器。
由于AMF网元向NRF网元注册UPF实例的信息时，目前NRF网元不存在提供此功能的服务化接口，需要在AMF网元和NRF网元之间增加提供此功能的服务化接口。
Option 2：
步骤1003、AMF网元根据Indication构建UPF实例注册信息。如果AMF网元向SMF网元注册UPF实例的信息，则UPF实例注册信息即为N11消息。如果AMF网元向NRF网元注册UPF实例的信息，则UPF实例注册信息即为NF Management NF register。
步骤1004a、AMF网元向SMF网元发送N11消息，以使得SMF网元接收来自AMF网元的N11消息，其中，N11消息包括NF Type，N4 Routing Indicator和UPF Provisioning Information。
步骤1004b、AMF网元向NRF网元发送NF Management NF register，以使得SMF网元接收来自AMF网元的NF Management NF register。其中，NF Management NF register包括NF Type，N4 Routing Indicator和UPF Provisioning Information。
Option2与Option1的关键区别是：AMF网元能够感知UPF实例的具体信息，并 支持代理注册功能，如果是向SMF网元注册，则需要通过新增接口进行注册；如果是向NRF网元注册，则直接调用服务化接口代为注册UPF实例的信息。
应理解，AMF网元或OAM网元直接向SMF网元注册UPF实例的信息的方案适用于单AMF网元/单SMF网元的场景，如果涉及多个AMF网元或者多个SMF网元场景，则需要向NRF网元注册UPF实例的信息。
如图11所示，以数据面模块为UPF模块，数据面实例为UPF实例、会话管理网元为SMF网元为例，图11以IAB节点通过宿主节点向NRF网元或SMF网元注册数据面实例为例详细描述，本申请通信方法中涉及到的数据面实例注册过程，如图11所示，该方法包括：
步骤1101、IAB节点通过F1消息或者E1消息向Donor节点发送UPF实例注册信息，以使得Donor节点接收来自IAB节点的F1消息或者E1消息。其中，F1消息或者E1消息中主要包含Indication1和UPF Register Container。其中，Indication1，指示Donor节点接收UPF实例的信息，并将UPF实例的信息转发给AMF网元。UPF Register Container中的内容可以参考图10中的描述，此处不再赘述。这里Donor节点不解析UPF Register Container中的具体内容。
应理解，如果UPF实例的信息未携带在UPF Register Container时，则Donor节点可以解析UPF实例的信息。
步骤1102、Donor节点根据Indication1，向AMF网元发送N2 NGAP消息，以使得AMF网元接收来自Donor节点的N2 NGAP消息。其中，N2 NGAP消息中携带UPF Register Container以及Indication2。其中，Indication2用于指示AMF网元向SMF网元或者NRF网元发送UPF Register Container。
Indication2可以和Indication1完全相同，此时不同网元接收到指示后按照各自的处理逻辑进行处理。
如果AMF网元不解析UPF实例的信息，则AMF网元采用方式(Option)3(包括步骤1103a或步骤1103b)向NRF网元或SMF网元发送UPF实例的信息。如果AMF网元解析UPF实例，则AMF网元采用方式4(包括步骤1104和步骤1105a，或者，步骤1104和步骤1105b)向NRF网元或SMF网元发送UPF实例的信息。
Option3：
步骤1103a、同步骤1002a。步骤1103b、同步骤1002b。
Option4：
步骤1104、AMF网元根据Indication2构建UPF实例注册信息。同步骤1003处的描述，此处不再赘述。
步骤1105a，同步骤1004a。步骤1105b，同步骤1004b。
如图12所示，以数据面模块为UPF模块，数据面实例为UPF实例、描述SMF网元寻址UPF实例的过程，该方法包括：
步骤1201、终端向SMF网元发送会话建立请求(session establishment request)消息，以使得SMF网元接收来自终端的会话建立请求消息。该会话建立请求消息用于请求SMF网元为终端建立会话。
可选的，会话建立请求消息中携带单个网络切片选择辅助信息(single network slice  selection assistance information，S-NSSAI)和数据网络名称(data network name，DNN)，会话标识，或请求类型(Request type)中的至少一个，本申请实施例对此不作具体限定。此外，会话建立请求消息中还可以携带原会话标识。
可以理解的是，图12以会话建立流程为例，对于会话修改流程，则会话建立请求消息可以由会话修改请求消息替代。
关于步骤1201的具体实现可以参考现有技术中的描述，此处不再赘述。
步骤1202a、SMF网元通过Nnrf服务化接口向NRF网元发送网络功能发现请求(Nnrf_NFDiscovery_Request)，以使得NRF网元接收来自SMF网元的Nnrf_NFDiscovery_Request。其中，Nnrf_NFDiscovery_Request中携带约束条件。例如，约束条件为专用DNN、位置等信息。例如，此处的位置可以为终端的位置或者DN接入点的位置。
步骤1203a、NRF网元通过Nnrf服务化接口SMF网元发送网络功能发现响应(Nnrf_NFDiscovery_Response)，以使得SMF网元接收来自NRF网元的Nnrf_NFDiscovery_Response。其中，Nnrf_NFDiscovery_Response中携带一个或多个第一UPF实例的信息。任一个UPF实体的信息包括N4路由指示。
上述步骤1202a可以通过下述步骤1202b替换，步骤1203a可以通过下述步骤1203b替换。
步骤1202b、SMF网元通过Nnrf服务化接口向NRF网元发送网络功能管理状态订阅请求(Nnrf_NFManagement_NFStatusSubscribe)，以使得NRF网元接收来自SMF网元的Nnrf_NFManagement_NFStatusSubscribe。
其中，Nnrf_NFManagement_NFStatusSubscribe中携带约束条件。
步骤1203b、NRF网元通过Nnrf服务化接口SMF网元发送网络功能管理状态通知(Nnrf_NFManagement_NFStatus Notify)，以使得SMF网元接收Nnrf_NFManagement_NFStatus Notify。其中，Nnrf_NFManagement_NFStatus Notify中携带一个或多个第一UPF实例的信息。任一个UPF实体的信息包括N4路由指示。
步骤1202b-步骤1203b与步骤1202a-步骤1203a的区别在于，步骤1202b-步骤1203b需要SMF网元先向NRF网元进行订阅，当有新的UPF实例上线时，NRF网元会主动通知SMF网元。而步骤1202a-步骤1203a是NRF网元直接响应SMF网元的查询请求。
步骤1204、SMF网元从一个或多个UPF实例中选择最优UPF实例。
例如，SMF网元根据限制条件如DNN、负载、位置等信息以及选择策略/算法选择最优UPF实例。如果选择的UPF实例包含N4 Routing Indicator，且根据该信息校验SMF网元本地存在IAB节点上下文，则通过NAS消息发送N4会话建立消息。
步骤1205、SMF网元通过Namf服务化接口向AMF网元传输通信N1N2消息(Namf_Communication_N1N2MessageTransfer)，以使得AMF网元接收Namf_Communication_N1N2MessageTransfer。
其中，Namf_Communication_N1N2MessageTransfer中携带Indication3和N4会话建立请求，该Indication3用于指示IAB节点将N4会话建立请求后递交给SMF网元所选择的UPF实例。
应理解，IAB节点先将N4会话建立请求递交给UPF模块，如果UPF模块有多个UPF实例，则UPF模块将N4会话建立请求发送至SMF网元所选择的UPF实例。
步骤1206、AMF网元向IAB节点发送N1 NAS消息(即会话管理NAS消息)，以使得IAB节点接收来自AMF网元的N1 NAS消息。其中，N1 NAS消息中包括Indication3和N4会话建立请求。
步骤1207、IAB节点根据Indication3将N4会话建立请求发送给SMF网元所选择的UPF实例。
步骤1208、IAB节点接收来自UPF实例的N4会话建立响应消息。
步骤1209、IAB节点向AMF网元发送N1 NAS消息，以使得AMF网元接收N1 NAS消息。其中，N1 NAS消息中包括N4会话建立响应消息以及Indication4。其中，Indication4用于指示向SMF网元发送N4会话建立响应消息。
步骤1210、AMF网元根据Indication4向SMF网元发送N11消息，以使得SMF网元接收N11消息。其中，N11消息中包括N4会话建立响应消息。
步骤1210之后终端会话建立过程可以参考现有技术的描述。
图12主要针对单AMF网元和单SMF网元的场景，流程体现了通过N1建立N4会话的流程，但是图12中涉及到的N4会话建立请求可以使用N4会话修改请求或N4会话删除请求替代。相应的，N4会话建立响应消息可以使用N4会话修改响应消息或N4会话删除响应消息替代。
如图13所示，图13示出了针对单AMF网元和多SMF网元场景，该场景下终端和IAB节点选择的SMF网元不同时，SMF网元寻址UPF实例的过程，该方法与图12的区别在于SMF网元本地不存在IAB节点上下文，该方法包括：
步骤1301-步骤1304，同步骤1201-步骤1204，此处不再赘述。
SMF网元根据限制条件如DNN、负载、位置等信息以及选择策略/算法选择最优UPF实例。如果选择的UPF实例包含N4 Routing Indicator，且根据该信息校验SMF网元本地不存在IAB节点上下文，则执行步骤1305。
步骤1305、SMF网元向AMF网元发送N11消息，以使得AMF网元接收来自SMF网元的N11消息。其中，N11消息包括：Indication3、N4路由指示和N4会话建立请求。
步骤1306、AMF网元根据Indication3检验本地存在IAB节点上下文后，构建移动性管理NAS消息。其中，移动性管理NAS消息中携带Indication3、和N4会话建立请求。
步骤1307、AMF网元向IAB节点发送移动性管理NAS消息，以使得AMF网元接收移动性管理NAS消息。
步骤1308-步骤1311，同步骤1207-步骤1210，同上述描述，此处不再赘述。
如图14所示，图14主要针对多AMF网元和多SMF网元的场景，该场景下终端和IAB节点选择的AMF网元和SMF网元均不同，SMF网元寻址UPF实例的过程，该方法与图13所示的实施例的区别在于：
步骤1401-步骤1404，同步骤1301-步骤1304，此处不再赘述。
SMF网元根据限制条件如DNN、负载、位置等信息以及选择策略/算法选择最优 UPF实例。如果选择的UPF实例包含N4 Routing Indicator，且根据该信息校验SMF网元本地不存在IAB节点上下文，则执行步骤1405。
步骤1405、SMF网元向UDM网元查询MT-AMF网元(为IAB节点服务的AMF网元)的信息。例如，SMF网元向UDM网元提供N4 Routing Indicator。
步骤1406、SMF网元获取到为IAB节点服务的MT-AMF网元信息后，通过服务化接口向该AMF网元发送N4会话消息，指示该MT-AMF网元构建NAS消息。
目前AMF和SMF之间不存在传递其他终端会话信息的服务化接口，需要添加新的服务化接口；然后MT-AMF网元接收N4 Routing Indicator(例如，SUPI)后，校验本地存在IAB节点上下文后，构建移动性管理NAS消息传递给IAB节点。
步骤1407-步骤1412，同步骤1306-步骤1311，同上述描述，此处不再赘述。
如图15所示，图15主要通过F1/E1+N2建立N4会话，但是N4会话消息的传递过程同样适用于N4会话修改和删除流程。与实施例12的关键区别如下：
步骤1501-步骤1504，同步骤1201-步骤1204，此处不再赘述。
具体的，如果步骤1504中SMF网元选择的UPF实例包含N4 Routing Indicator信息，则SMF网元构建发送给Donor节点的消息，由Donor节点转发给IAB节点。
步骤1505、SMF网元构建发送给Donor节点的消息。例如，发送给Donor节点的消息包括：指示1、N4会话建立请求消息以及N4 Routing Indicator。
步骤1506、SMF网元通过Namf服务化接口向AMF网元传输通信N1N2消息(Namf_Communication_N1N2MessageTransfer)，以使得AMF网元接收Namf_Communication_N1N2MessageTransfer。其中，通信N1N2消息中携带SMF网元构建的发送给Donor节点的消息。
步骤1507、AMF网元向宿主节点发送N2消息，以使得宿主节点接收来自AMF网元的N2消息。其中，N2消息中携带SMF网元构建的发送给Donor节点的消息。或者N2消息中直接携带指示1、N4会话建立请求消息以及N4 Routing Indicator。
步骤1508、宿主节点根据N4 Routing Indicator确定SMF网元选择的UPF实例的地址。
步骤1509、宿主节点向IAB节点发送F1/E1消息，以使得IAB节点接收F1/E1消息。其中，F1/E1消息中携带指示1、N4会话建立请求消息。
步骤1510、IAB节点根据指示1向SMF网元选择的UPF实例发送N4会话建立请求消息，以使得SMF网元选择的UPF实例接收N4会话建立请求消息。
步骤1511、IAB节点接收来自UPF实例的N4会话建立响应消息。
步骤1512、IAB节点向宿主节点发送F1/E1消息，以使得宿主节点接收F1/E1消息。其中，F1/E1消息中携带指示4、N4会话建立响应消息。其中，指示4(即上述第二指示)用于指示向SMF网元发送N4会话建立响应消息。
步骤1513、宿主节点根据指示4向AMF网元发送N2消息，以使得AMF网元接收N2消息。其中，N2消息中携带指示4以及N4会话建立响应消息。或者N2消息中携带指示5以及用于N4会话建立响应消息。其中，指示5用于指示AMF网元向SMF网元发送N4会话建立响应消息。
步骤1514、AMF网元根据指示4或指示5向SMF网元发送N11消息，以使得 SMF网元接收N11消息。其中，N11消息中携带N4会话建立响应消息。
步骤1514之后终端会话建立过程可以参考现有技术的描述。
上述主要从各个网元之间交互的角度对本申请实施例的方案进行了介绍。可以理解的是，各个网元，例如会话管理网元、移动管理网元、IAB节点等为了实现上述功能，其包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例会话管理网元、移动管理网元、IAB节点进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
上面结合图6至图15，对本申请实施例的方法进行了说明，下面对本申请实施例提供的执行上述方法的通信装置进行描述。本领域技术人员可以理解，方法和装置可以相互结合和引用，本申请实施例提供的通信装置可以执行上述通信方法中由会话管理网元、移动管理网元、IAB节点执行的步骤。
在采用集成的单元的情况下，图16示出了上述实施例中所涉及的一种通信装置，该通信装置可以包括：通信单元102和处理单元101。
一种示例，该通信装置为会话管理网元，或者为应用于会话管理网元中的芯片。在这种情况下，通信单元102，用于支持该通信装置执行上述实施例中由会话管理网元执行图6中的步骤601。通信单元102用于支持该通信装置执行上述实施例中的步骤602中由会话管理网元发送的动作。
在一种可能的实施例中，通信单元102，还用于支持通信装置执行上述实施例中的步骤606、步骤614中由会话管理网元执行的接收的动作，或者步骤600、步骤611。
在一种可能的实施例中，处理单元101，还用于支持通信装置执行上述实施例中的步骤607、步骤6021。在一种可能的实施例中，通信单元102，还用于支持通信装置执行上述实施例中的步骤6022、步骤609中由会话管理网元执行的发送的动作。
另一种示例，该通信装置为移动管理网元，或者为应用于移动管理网元中的芯片。在这种情况下，通信单元102，用于支持该通信装置执行上述实施例中的步骤602中由移动管理网元接收的动作。通信单元102，用于支持该通信装置执行上述实施例中的步骤603中由移动管理网元发送的动作。
在一种可能的实施例中，该通信单元102还用于该通信装置执行上述实施例中的步骤605、步骤6022、步骤609中由移动管理网元接收的动作。
在一种可能的实施例中，该通信单元102还用于该通信装置执行上述实施例中的步骤606、步骤614中由移动管理网元发送的动作。
在一种可能的实施例中，处理单元101还用于该通信装置执行上述实施例中的步 骤610。
在一种可能的实施例中，该通信单元102还用于该通信装置执行上述实施例中的步骤613中由移动管理网元接收的动作。
再一种示例，该通信装置为Donor节点50，或者为应用于Donor节点50中的芯片。通信单元102，用于支持该通信装置执行上述实施例中的步骤603中由Donor节点50发送的动作。通信单元102用于支持该通信装置执行上述实施例的步骤602中由Donor节点50接收的动作。
在一种可能的实施例中，该通信单元102还用于该通信装置执行上述实施例中的步骤605中由Donor节点50接收的动作。
在一种可能的实施例中，该通信单元102还用于该通信装置执行上述实施例中的步骤606、步骤614中由Donor节点50发送的动作。
在一种可能的实施例中，该通信单元102还用于该通信装置执行上述实施例中的步骤613中由Donor节点50接收的动作。
又一种示例，该通信装置为IAB节点10，或者为应用于IAB节点10中的芯片。通信单元102，用于支持该通信装置执行上述实施例中的步骤603中由IAB节点10接收的动作。通信单元102还用于支持该通信装置执行上述实施例中的步骤604中由IAB节点10发送的动作。
在一种可能的实施例中，该通信单元102还用于该通信装置执行上述实施例中的步骤605、步骤613中由IAB节点10发送的动作。在一种可能的实施例中，该通信单元102还用于该通信装置执行上述实施例中的步骤612中由IAB节点10接收的动作。
再一种示例，该通信装置为网管网元，或者为应用于网管网元中的芯片。通信单元102，用于支持该通信装置执行上述实施例中的步骤605中由网管网元接收的动作。通信单元102还用于支持该通信装置执行上述实施例中的步骤606中由网管网元发送的动作。
在采用集成的单元的情况下，图17示出了上述实施例中所涉及的通信装置的一种可能的逻辑结构示意图。该通信装置包括：处理模块112和通信模块113。处理模块112用于对通信装置的动作进行控制管理，例如，处理模块112用于执行在通信装置进行信息/数据处理的步骤。通信模块113用于支持通信装置进行信息/数据发送或者接收的步骤。
在一种可能的实施例中，通信装置还可以包括存储模块111，用于存储通信装置可的程序代码和数据。
一种示例，该通信装置为会话管理网元，或者为应用于会话管理网元中的芯片。在这种情况下，通信模块113，用于支持该通信装置执行上述实施例中由会话管理网元执行图6中的步骤601。通信模块113用于支持该通信装置执行上述实施例中的步骤602中由会话管理网元发送的动作。
在一种可能的实施例中，通信模块113，还用于支持通信装置执行上述实施例中的步骤606、步骤614中由会话管理网元执行的接收的动作，或者步骤600、步骤611。
在一种可能的实施例中，处理模块112，还用于支持通信装置执行上述实施例中的步骤607、步骤6021。在一种可能的实施例中，通信模块113，还用于支持通信装 置执行上述实施例中的步骤6022、步骤609中由会话管理网元执行的发送的动作。
另一种示例，该通信装置为移动管理网元，或者为应用于移动管理网元中的芯片。在这种情况下，通信模块113，用于支持该通信装置执行上述实施例中的步骤602中由移动管理网元接收的动作。通信模块113，用于支持该通信装置执行上述实施例中的步骤603中由移动管理网元发送的动作。
在一种可能的实施例中，该通信模块113还用于该通信装置执行上述实施例中的步骤605、步骤6022、步骤609中由移动管理网元接收的动作。
在一种可能的实施例中，该通信模块113还用于该通信装置执行上述实施例中的步骤606、步骤614中由移动管理网元发送的动作。
在一种可能的实施例中，处理模块112还用于该通信装置执行上述实施例中的步骤610。
在一种可能的实施例中，该通信模块113还用于该通信装置执行上述实施例中的步骤613中由移动管理网元接收的动作。
再一种示例，该通信装置为Donor节点50，或者为应用于Donor节点50中的芯片。通信模块113，用于支持该通信装置执行上述实施例中的步骤603中由Donor节点50发送的动作。通信模块113用于支持该通信装置执行上述实施例的步骤602中由Donor节点50接收的动作。
在一种可能的实施例中，该通信模块113还用于该通信装置执行上述实施例中的步骤605中由Donor节点50接收的动作。
在一种可能的实施例中，该通信模块113还用于该通信装置执行上述实施例中的步骤606、步骤614中由Donor节点50发送的动作。
在一种可能的实施例中，该通信模块113还用于该通信装置执行上述实施例中的步骤613中由Donor节点50接收的动作。
又一种示例，该通信装置为IAB节点10，或者为应用于IAB节点10中的芯片。通信模块113，用于支持该通信装置执行上述实施例中的步骤603中由IAB节点10接收的动作。通信模块113还用于支持该通信装置执行上述实施例中的步骤604中由IAB节点10发送的动作。
在一种可能的实施例中，该通信模块113还用于该通信装置执行上述实施例中的步骤605、步骤613中由IAB节点10发送的动作。在一种可能的实施例中，该通信模块113还用于该通信装置执行上述实施例中的步骤612中由IAB节点10接收的动作。
再一种示例，该通信装置为网管网元，或者为应用于网管网元中的芯片。通信模块113，用于支持该通信装置执行上述实施例中的步骤605中由网管网元接收的动作。通信模块113还用于支持该通信装置执行上述实施例中的步骤606中由网管网元发送的动作。
其中，处理模块112可以是处理器或控制器，例如可以是中央处理器单元，通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，数字信号处理器和微处理器的组合等等。 通信模块113可以是收发器、收发电路或通信接口等。存储模块111可以是存储器。
当处理模块112为处理器51或处理器55，通信模块113为通信接口53时，存储模块111为存储器42时，本申请所涉及的通信装置可以为图5所示的通信设备。
图18是本申请实施例提供的芯片150的结构示意图。芯片150包括一个或两个以上(包括两个)处理器1510和通信接口1530。
可选的，该芯片150还包括存储器1540，存储器1540可以包括只读存储器和随机存取存储器，并向处理器1510提供操作指令和数据。存储器1540的一部分还可以包括非易失性随机存取存储器(non-volatile random access memory，NVRAM)。
在一些实施方式中，存储器1540存储了如下的元素，执行模块或者数据结构，或者他们的子集，或者他们的扩展集。
在本申请实施例中，通过调用存储器1540存储的操作指令(该操作指令可存储在操作系统中)，执行相应的操作。
一种可能的实现方式中为：IAB节点、Donor节点、移动管理网元、会话管理网元、网管网元所用的芯片的结构类似，不同的装置可以使用不同的芯片以实现各自的功能。
处理器1510控制IAB节点、Donor节点、移动管理网元、会话管理网元、网管网元中任一个的处理操作，处理器1510还可以称为中央处理单元(central processing unit，CPU)。
存储器1540可以包括只读存储器和随机存取存储器，并向处理器1510提供指令和数据。存储器1540的一部分还可以包括NVRAM。例如应用中存储器1540、通信接口1530以及存储器1540通过总线系统1520耦合在一起，其中总线系统1520除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见，在图18中将各种总线都标为总线系统1520。
上述本申请实施例揭示的方法可以应用于处理器1510中，或者由处理器1510实现。处理器1510可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1510中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1510可以是通用处理器、数字信号处理器(digital signal processing，DSP)、ASIC、现成可编程门阵列(field-programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1540，处理器1510读取存储器1540中的信息，结合其硬件完成上述方法的步骤。
一种可能的实现方式中，通信接口1530用于执行图6-图15所示的实施例中的IAB节点、Donor节点、移动管理网元、会话管理网元、网管网元的接收和发送的步骤。处理器1510用于执行图6-图15所示的实施例中的IAB节点、Donor节点、移动管理网元、会话管理网元、网管网元的处理的步骤。
以上通信单元可以是该装置的一种通信接口，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该通信单元是该芯片用于从其它芯片或装置接收信号或发送信号的通信接口。
一方面，提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当指令被运行时，实现如图6-图15中移动管理网元的功能。
另一方面，提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当指令被运行时，实现如图6-图15中会话管理网元的功能。
一方面，提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当指令被运行时，实现如图6-图15中IAB节点的功能。
另一方面，提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当指令被运行时，实现如图6-图15中网管网元的功能。
一方面，提供一种包括指令的计算机程序产品，计算机程序产品中包括指令，当指令被运行时，实现如图6-图15中网管网元的功能。
又一方面，提供一种包括指令的计算机程序产品，计算机程序产品中包括指令，当指令被运行时，实现如图6-图15中IAB节点的功能。
又一方面，提供一种包括指令的计算机程序产品，计算机程序产品中包括指令，当指令被运行时，实现如图6-图15中Donor节点的功能。
一方面，提供一种包括指令的计算机程序产品，计算机程序产品中包括指令，当指令被运行时，实现如图6-图15中会话管理网元的功能。
又一方面，提供一种包括指令的计算机程序产品，计算机程序产品中包括指令，当指令被运行时，实现如图6-图15中移动管理网元的功能。
一方面，提供一种芯片，该芯片应用于网管网元中，芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，处理器用于运行指令，以实现如图6-图15中网管网元的功能。
又一方面，提供一种芯片，该芯片应用于Donor节点中，芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，处理器用于运行指令，以实现如图6-图15中Donor节点的功能。
又一方面，提供一种芯片，该芯片应用于IAB节点中，芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，处理器用于运行指令，以实现如图6-图15中IAB节点的功能。
又一方面，提供一种芯片，该芯片应用于移动管理网元中，芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，处理器用于运行指令，以实现如图6-图15中移动管理网元的功能。
又一方面，提供一种芯片，该芯片应用于会话管理网元中，芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，处理器用于运行指令，以实现如图6-图15中会话管理网元的功能。
本申请实施例提供一种通信系统，该通信系统包括：会话管理网元和IAB节点。其中，会话管理网元用于执行图6-图8中的任一个由会话管理网元执行的步骤，IAB节点用于执行图6-图8中的任一个由IAB节点执行的步骤。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序或指令可以从一个网站站点、计算机、服务器或数据中心通过有线或无线方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，数字视频光盘(digital video disc，DVD)；还可以是半导体介质，例如，固态硬盘(solid state drive，SSD)。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看附图、公开内容、以及所附权利要求书，可理解并实现公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包括这些改动和变型在内。

Claims (45)

  1. 一种通信方法，其特征在于，所述方法包括：
    会话管理网元确定目标数据面实例的信息，所述目标数据面实例的信息包括路由指示，所述路由指示用于确定所述目标数据面实例的地址；所述目标数据面实例与无线回传IAB节点关联；
    所述会话管理网元通过为所述IAB节点提供服务的移动管理网元或宿主Donor节点向所述IAB节点发送N4会话管理请求消息和第一指示，所述第一指示用于指示所述IAB节点向所述目标数据面实例发送所述N4会话管理请求消息。
  2. 根据权利要求1所述的方法，其特征在于，所述会话管理网元通过移动管理网元向所述IAB节点发送N4会话管理请求消息和第一指示之前，所述方法还包括：
    所述会话管理网元获取本地的所述IAB节点的上下文；
    所述会话管理网元通过移动管理网元向所述IAB节点发送N4会话管理请求消息和第一指示，包括：
    所述会话管理网元根据所述IAB节点的上下文生成会话管理非接入层NAS消息，所述会话管理NAS层消息包括所述N4会话管理请求消息和第一指示；
    所述会话管理网元通过移动管理网元向所述IAB节点发送所述会话管理NAS层消息。
  3. 根据权利要求1所述的方法，其特征在于，所述会话管理网元的本地不存在所述IAB节点的上下文，所述方法还包括：
    所述会话管理网元向所述移动管理网元发送所述路由指示，所述移动管理网元用于根据所述路由指示确定移动管理网元本地具有所述IAB节点的上下文后，所述移动管理网元根据所述IAB节点的上下文生成移动性管理NAS消息，向所述IAB节点发送所述移动性管理NAS消息，所述移动性管理NAS消息包括所述N4会话管理请求消息和所述第一指示。
  4. 根据权利要求3所述的方法，其特征在于，所述会话管理网元向所述移动管理网元发送所述路由指示之前，所述方法还包括：
    所述会话管理网元从用户数据管理网元处获取所述IAB节点的移动管理网元的信息。
  5. 根据权利要求1所述的方法，其特征在于，所述会话管理网元通过Donor节点向所述IAB节点发送N4会话管理请求消息和第一指示还包括：
    所述会话管理网元向所述Donor节点发送所述路由指示，所述Donor节点用于根据所述路由指示向所述IAB节点发送第一消息，所述第一消息包括所述N4会话管理请求消息和所述第一指示。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元通过所述IAB节点接收来自所述目标数据面实例的N4会话管理响应消息。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元从网络存储网元处获取一个或多个数据面实例的信息，所述一个或多个数据面实例包括所述目标数据面实例。
  8. 根据权利要求1-6任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元通过网管网元、或所述Donor节点、或所述移动管理网元接收所述数据面模块的所述一个或多个数据面实例的信息，所述一个或多个数据面实例包括所述目标数据面实例。
  9. 根据权利要求8所述的方法，其特征在于，所述一个或多个数据面实例在所述Donor节点、或所述移动管理网元处透传，或者，所述一个或多个数据面实例由所述Donor节点、或所述移动管理网元处理后发送至所述会话管理网元或网络存储网元。
  10. 一种通信方法，其特征在于，所述方法包括：
    无线回传IAB节点接收来自会话管理网元的N4会话管理请求消息和第一指示，所述第一指示用于指示所述IAB节点向目标数据面实例发送所述N4会话管理请求消息；
    所述IAB节点根据所述第一指示，向所述目标数据面实例发送所述N4会话管理请求消息，所述N4会话管理请求消息用于指示管理所述目标数据面实例的会话上下文。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    所述IAB节点接收所述目标数据面实例发送的N4会话管理响应消息；
    所述IAB节点向Donor节点或移动管理网元发送第二指示，以及所述N4会话管理响应消息，所述第二指示用于指示向所述会话管理网元发送所述N4会话管理响应消息。
  12. 根据权利要求10或11所述的方法，其特征在于，所述方法还包括：
    所述IAB节点向第一设备发送第一消息，所述第一消息包括所述数据面模块对应的一个或多个数据面实例的信息，所述一个或多个数据面实例的信息包括所述目标数据面实例的信息，任一个数据面实例的信息包括路由指示，所述第一消息用于指示所述第一设备向所述会话管理网元或者网络存储网元注册所述一个或多个数据面实例的信息；所述路由指示用于所述会话管理网元确定所述任一个数据面实例的地址；所述任一个数据面实例与所述IAB节点关联，所述第一设备包括以下任一个：网管网元或Donor节点、或移动管理网元。
  13. 根据权利要求12所述的方法，其特征在于，所述第一消息中包括负荷容器Payload Container，所述Payload Container中包括所述一个或多个数据面实例的信息，所述Payload Container的类型用于指示所述第一设备向所述会话管理网元或者网络存储网元注册所述一个或多个数据面实例的信息。
  14. 根据权利要求12所述的方法，其特征在于，所述第一消息中还包括注册指示，所述注册指示用于指示所述第一设备向所述会话管理网元或者网络存储网元注册所述一个或多个数据面实例的信息。
  15. 根据权利要求12所述的方法，其特征在于，所述IAB节点和所述第一设备之间具有预定义的操作接口，所述预定义的操作接口用于指示所述第一设备向所述会话管理网元或者网络存储网元注册所述一个或多个数据面实例的信息，所述IAB节点通过所述预定义的操作接口向所述第一设备发送第一消息。
  16. 根据权利要求12-15任一项所述的方法，其特征在于，所述一个或多个数据 面实例的信息在所述Donor节点、或所述移动管理网元处透传，或者，所述一个或多个数据面实例的信息由所述Donor节点、或所述移动管理网元处理后发送至所述会话管理网元或所述网络存储网元。
  17. 一种通信方法，其特征在于，所述方法包括：
    为IAB节点提供服务的移动管理网元接收来自会话管理网元的N4会话管理请求消息和第一指示，所述第一指示用于指示所述IAB节点向目标数据面实例发送所述N4会话管理请求消息；
    所述移动管理网元向所述IAB节点发送所述N4会话管理请求消息和所述第一指示。
  18. 根据权利要求17所述的方法，其特征在于，所述移动管理网元向所述IAB节点发送所述N4会话管理请求消息和第一指示之前，所述方法还包括：
    所述移动管理网元接收来自所述会话管理网元的路由指示，所述路由指示用于确定所述目标数据面实例的地址；所述目标数据面实例所述AB节点关联；
    所述移动管理网元根据所述路由指示确定移动管理网元本地具有所述IAB节点的上下文后，所述移动管理网元根据所述IAB节点的上下文生成移动性管理NAS消息；
    所述移动管理网元向所述IAB节点发送所述N4会话管理请求消息和第一指示，包括：
    所述移动管理网元向所述IAB节点发送所述移动性管理NAS消息，所述移动性管理NAS消息包括所述N4会话管理请求消息和所述第一指示。
  19. 根据权利要求17或18所述的方法，其特征在于，所述方法还包括：
    所述移动管理网元接收第一消息，所述第一消息包括所述数据面模块的一个或多个数据面实例的信息，所述第一消息用于指示所述移动管理网元向所述会话管理网元或NRF网元注册所述一个或多个数据面实例的信息；任一个数据面实例的信息包括路由指示；一个或多个数据面实例的信息包括所述目标数据面实例的信息；
    所述移动管理网元根据所述第一消息，向所述会话管理网元或网络存储网元注册所述一个或多个数据面实例的信息。
  20. 根据权利要求19所述的方法，其特征在于，所述一个或多个数据面实例的信息在所述移动管理网元处透传，或者，所述一个或多个数据面实例的信息由所述移动管理网元处理后发送至所述会话管理网元或网络存储网元。
  21. 根据权利要求19所述的方法，其特征在于，所述方法还包括：
    所述移动管理网元通过所述IAB节点或Donor节点接收来自目标数据面实例的N4会话管理响应消息和第二指示，所述第二指示用于指示向所述会话管理网元发送所述N4会话管理响应消息；
    所述移动管理网元向所述会话管理网元发送所述N4会话管理响应消息。
  22. 一种通信装置，其特征在于，包括：
    处理单元，用于确定目标数据面实例的信息，所述目标数据面实例的信息包括路由指示，所述路由指示用于确定所述目标数据面实例的地址；所述目标数据面实例与无线回传IAB节点关联；
    通信单元，用于通过为所述IAB节点提供服务的移动管理网元或宿主Donor节点 向所述IAB节点发送N4会话管理请求消息和第一指示，所述第一指示用于指示所述IAB节点向所述目标数据面实例发送所述N4会话管理请求消息。
  23. 根据权利要求22所述的装置，其特征在于，所述通信单元，用于通过移动管理网元向所述IAB节点发送N4会话管理请求消息和第一指示之前，所述处理单元还用于获取所述装置的本地的所述IAB节点的上下文；
    所述处理单元，还用于根据所述IAB节点的上下文生成会话管理非接入层NAS消息，所述会话管理NAS层消息包括所述N4会话管理请求消息和第一指示；
    相应的，所述通信单元，还用于通过移动管理网元向所述IAB节点发送所述会话管理NAS层消息。
  24. 根据权利要求22所述的装置，其特征在于，所述通信单元，还用于向所述移动管理网元发送所述路由指示，所述移动管理网元用于根据所述路由指示确定移动管理网元本地具有所述IAB节点的上下文后，所述移动管理网元根据所述IAB节点的上下文生成移动性管理NAS消息，向所述IAB节点发送所述移动性管理NAS消息，所述移动性管理NAS消息包括所述N4会话管理请求消息和所述第一指示。
  25. 根据权利要求24所述的装置，其特征在于，所述通信单元，用于向所述移动管理网元发送所述路由指示之前，所述通信单元，还用于从用户数据管理网元处获取所述IAB节点的移动管理网元的信息。
  26. 根据权利要求22所述的装置，其特征在于，所述通信单元，用于通过Donor节点向所述IAB节点发送N4会话管理请求消息和第一指示还包括：向所述Donor节点发送所述路由指示，所述Donor节点用于根据所述路由指示向所述IAB节点发送第一消息，所述第一消息包括所述N4会话管理请求消息和所述第一指示。
  27. 根据权利要求22-26任一项所述的装置，其特征在于，所述通信单元，还用于通过所述IAB节点接收来自所述目标数据面实例的N4会话管理响应消息。
  28. 根据权利要求22-27任一项所述的装置，其特征在于，所述通信单元，还用于从网络存储网元处获取一个或多个数据面实例的信息，所述一个或多个数据面实例包括所述目标数据面实例。
  29. 根据权利要求22-27任一项所述的装置，其特征在于，所述通信单元，还用于通过网管网元、或所述Donor节点、或所述移动管理网元接收所述数据面模块的所述一个或多个数据面实例的信息，所述一个或多个数据面实例包括所述目标数据面实例。
  30. 根据权利要求29所述的装置，其特征在于，所述一个或多个数据面实例在所述Donor节点、或所述移动管理网元处透传，或者，所述一个或多个数据面实例由所述Donor节点、或所述移动管理网元处理后发送至所述装置或网络存储网元。
  31. 一种通信装置，其特征在于，包括：处理单元，用于处理信息；
    通信单元，用于接收来自会话管理网元的N4会话管理请求消息和第一指示，所述第一指示用于指示所述通信单元向目标数据面实例发送所述N4会话管理请求消息；
    通信单元，用于根据所述第一指示，向所述目标数据面实例发送所述N4会话管理请求消息，所述N4会话管理请求消息用于指示管理所述目标数据面实例的会话上下文。
  32. 根据权利要求31所述的装置，其特征在于，所述通信单元，还用于接收所述目标数据面实例发送的N4会话管理响应消息；
    所述通信单元，还用于向Donor节点或移动管理网元发送第二指示，以及所述N4会话管理响应消息，所述第二指示用于指示向所述会话管理网元发送所述N4会话管理响应消息。
  33. 根据权利要求31或32所述的装置，其特征在于，所述通信单元，还用于向第一设备发送第一消息，所述第一消息包括所述数据面模块对应的一个或多个数据面实例的信息，所述一个或多个数据面实例的信息包括所述目标数据面实例的信息，任一个数据面实例的信息包括路由指示，所述第一消息用于指示所述第一设备向所述会话管理网元或者网络存储网元注册所述一个或多个数据面实例的信息；所述路由指示用于所述会话管理网元确定所述任一个数据面实例的地址；所述任一个数据面实例与所述装置关联，所述第一设备包括以下任一个：网管网元或Donor节点、或移动管理网元。
  34. 根据权利要求33所述的装置，其特征在于，所述第一消息中包括负荷容器Payload Container，所述Payload Container中包括所述一个或多个数据面实例的信息，所述Payload Container的类型用于指示所述第一设备向所述会话管理网元或者网络存储网元注册所述一个或多个数据面实例的信息。
  35. 根据权利要求33所述的装置，其特征在于，所述第一消息中还包括注册指示，所述注册指示用于指示所述第一设备向所述会话管理网元或者网络存储网元注册所述一个或多个数据面实例的信息。
  36. 根据权利要求33所述的装置，其特征在于，所述装置和所述第一设备之间具有预定义的操作接口，所述预定义的操作接口用于指示所述第一设备向所述会话管理网元或者网络存储网元注册所述一个或多个数据面实例的信息，所述通信单元，用于通过所述预定义的操作接口向所述第一设备发送第一消息。
  37. 根据权利要求31-36任一项所述的装置，其特征在于，所述一个或多个数据面实例的信息在所述Donor节点、或所述移动管理网元处透传，或者，所述一个或多个数据面实例的信息由所述Donor节点、或所述移动管理网元处理后发送至所述会话管理网元或所述网络存储网元。
  38. 一种通信装置，其特征在于，包括：处理单元，用于处理信息；
    通信单元，用于接收来自会话管理网元的N4会话管理请求消息和第一指示，所述第一指示用于指示所述IAB节点向目标数据面实例发送所述N4会话管理请求消息；
    所述通信单元，还用于向所述IAB节点发送所述N4会话管理请求消息和所述第一指示。
  39. 根据权利要求38所述的装置，其特征在于，所述通信单元，还用于向所述IAB节点发送所述N4会话管理请求消息和所述第一指示之前，所述通信单元，还用于接收来自所述会话管理网元的路由指示，所述路由指示用于确定所述目标数据面实例的地址；所述目标数据面实例所述AB节点关联；
    所述处理单元，用于根据所述路由指示确定所述装置本地具有所述IAB节点的上下文后，根据所述IAB节点的上下文生成移动性管理NAS消息；
    所述通信单元，用于向所述IAB节点发送所述移动性管理NAS消息，所述移动性管理NAS消息包括所述N4会话管理请求消息和所述第一指示。
  40. 根据权利要求38或39所述的装置，其特征在于，所述通信单元，还用于接收第一消息，所述第一消息包括所述数据面模块的一个或多个数据面实例的信息，所述第一消息用于指示所述装置向所述会话管理网元或NRF网元注册所述一个或多个数据面实例的信息；任一个数据面实例的信息包括路由指示；一个或多个数据面实例的信息包括所述目标数据面实例的信息；
    所述处理单元，用于根据所述第一消息，通过所述通信单元向所述会话管理网元或网络存储网元注册所述一个或多个数据面实例的信息。
  41. 根据权利要求40所述的装置，其特征在于，所述一个或多个数据面实例的信息在所述移动管理网元处透传，或者，所述一个或多个数据面实例的信息由所述移动管理网元处理后发送至所述会话管理网元或网络存储网元。
  42. 根据权利要求41所述的装置，其特征在于，所述通信单元，用于通过所述IAB节点或Donor节点接收来自目标数据面实例的N4会话管理响应消息和第二指示，所述第二指示用于指示向所述会话管理网元发送所述N4会话管理响应消息；
    所述所述通信单元，用于向所述会话管理网元发送所述N4会话管理响应消息。
  43. 一种可读存储介质，其特征在于，所述可读存储介质中存储有指令，当所述指令被执行时，实现如权利要求1-9任一项所述的通信方法，或者，如权利要求10-16任一项所述的通信方法，或者，如权利要求17-21任一项所述的通信方法。
  44. 一种芯片，其特征在于，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行计算机程序或指令，以实现如权利要求1-9任一项所述的通信方法，或者，如权利要求10-16任一项所述的通信方法，或者，如权利要求17-21任一项所述的通信方法，所述通信接口用于与所述芯片之外的其它模块进行通信。
  45. 一种通信装置，其特征在于，包括：处理器和通信接口，其中，所述通信接口用于执行如权利要求1-9任一项所述的通信方法中在所述会话管理网元中进行消息收发的操作；所述处理器运行指令以执行如权利要求1-9任一项所述的通信方法中在所述会话管理网元中进行处理或控制的操作；
    或者，
    所述通信接口用于执行如权利要求10-16任一项所述的通信方法中在所述IAB节点中进行消息收发的操作；所述处理器运行指令以执行如权利要求10-16任一项所述的通信方法中在所述IAB节点中进行处理或控制的操作；或者，
    所述通信接口用于执行如权利要求17-21任一项所述的通信方法中在所述移动管理网元中进行消息收发的操作；所述处理器运行指令以执行如权利要求17-21任一项所述的通信方法中在所述移动管理网元中进行处理或控制的操作。
PCT/CN2019/109732 2019-09-30 2019-09-30 一种通信方法、装置以及系统 WO2021062807A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2019/109732 WO2021062807A1 (zh) 2019-09-30 2019-09-30 一种通信方法、装置以及系统
CN201980100816.2A CN114503625B (zh) 2019-09-30 2019-09-30 一种通信方法、装置以及系统
EP19947465.1A EP4027673A4 (en) 2019-09-30 2019-09-30 COMMUNICATION METHOD, DEVICE AND SYSTEM
US17/709,247 US20220225463A1 (en) 2019-09-30 2022-03-30 Communications method, apparatus, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/109732 WO2021062807A1 (zh) 2019-09-30 2019-09-30 一种通信方法、装置以及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/709,247 Continuation US20220225463A1 (en) 2019-09-30 2022-03-30 Communications method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2021062807A1 true WO2021062807A1 (zh) 2021-04-08

Family

ID=75336731

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/109732 WO2021062807A1 (zh) 2019-09-30 2019-09-30 一种通信方法、装置以及系统

Country Status (4)

Country Link
US (1) US20220225463A1 (zh)
EP (1) EP4027673A4 (zh)
CN (1) CN114503625B (zh)
WO (1) WO2021062807A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022067818A1 (zh) * 2020-09-30 2022-04-07 华为技术有限公司 一种数据传输方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109698760A (zh) * 2017-10-23 2019-04-30 华为技术有限公司 一种流量处理方法和用户面装置以及终端设备
US20190222489A1 (en) * 2018-04-09 2019-07-18 Intel Corporation NETWORK DATA ANALYTICS FUNCTION (NWDAF) INFLUENCING FIFTH GENERATION (5G) QUALITY OF SERVICE (QoS) CONFIGURATION AND ADJUSTMENT
CN110149665A (zh) * 2018-02-14 2019-08-20 华为技术有限公司 一种网元的选择方法及装置
WO2019169612A1 (en) * 2018-03-08 2019-09-12 Zte Corporation Methods and system for carrying out a handover of a mobile communication device between different access networks
CN110248376A (zh) * 2018-03-08 2019-09-17 华为技术有限公司 一种链路维护的方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109698760A (zh) * 2017-10-23 2019-04-30 华为技术有限公司 一种流量处理方法和用户面装置以及终端设备
CN110149665A (zh) * 2018-02-14 2019-08-20 华为技术有限公司 一种网元的选择方法及装置
WO2019169612A1 (en) * 2018-03-08 2019-09-12 Zte Corporation Methods and system for carrying out a handover of a mobile communication device between different access networks
CN110248376A (zh) * 2018-03-08 2019-09-17 华为技术有限公司 一种链路维护的方法及装置
US20190222489A1 (en) * 2018-04-09 2019-07-18 Intel Corporation NETWORK DATA ANALYTICS FUNCTION (NWDAF) INFLUENCING FIFTH GENERATION (5G) QUALITY OF SERVICE (QoS) CONFIGURATION AND ADJUSTMENT

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
3GPP TS 33.501
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System (5GS); Stage 2 (Release 16)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.501, vol. SA WG2, no. V16.2.0, 24 September 2019 (2019-09-24), pages 1 - 391, XP051784669 *

Also Published As

Publication number Publication date
CN114503625B (zh) 2023-08-25
EP4027673A1 (en) 2022-07-13
US20220225463A1 (en) 2022-07-14
CN114503625A (zh) 2022-05-13
EP4027673A4 (en) 2022-10-19

Similar Documents

Publication Publication Date Title
US20210084443A1 (en) Methods of joint registration and de-registration for proximity services and internet of things services
WO2022020770A1 (en) Computing workload management in next generation cellular networks
CN112385201A (zh) 核心网络辅助的服务发现
CN109792457B (zh) 存储和检索设备的网络上下文
JP7264284B2 (ja) ネットワークノード、Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ、及びこれらの方法
JP2023532404A (ja) エッジデータネットワークおよび５ｇネットワークにおけるサービス機能チェイニングサービス
EP4106480A1 (en) Communication method and apparatus
WO2020199868A1 (zh) 一种网络接入方法和装置
JP7389243B2 (ja) ＱｏＳマッピング
CN112911631A (zh) 业务服务质量监测方法、设备及系统
WO2023032529A1 (en) METHOD OF COMMUNICATION APPARATUS, METHOD OF gNB-CU-CP APPARATUS, METHOD OF AMF APPARATUS, METHOD OF SMF APPARATUS, METHOD OF gNB-DU APPARATUS, METHOD OF UPF APPARATUS, COMMUNICATION APPARATUS, gNB-CU-CP APPARATUS, AMF APPARATUS, SMF APPARATUS, gNB-DU APPARATUS AND UPF APPARATUS
WO2022253083A1 (zh) 一种公私网业务的隔离方法、装置及系统
KR20200082409A (ko) 무선 통신 시스템에서 규칙 정보를 전송하는 방법 및 장치.
WO2022021435A1 (zh) 数据传输方法、设备及存储介质
US20220225463A1 (en) Communications method, apparatus, and system
WO2022067816A1 (zh) 一种网络边缘计算方法及通信装置
CN113329448A (zh) 一种通信的方法及装置
WO2023051422A1 (zh) 通信方法及相关设备
US20240098628A1 (en) Method and Apparatus for Relay Service Code Management
WO2022259830A1 (en) Method of user equipment (ue) and user equipment (ue)
WO2024027299A1 (zh) 消息路由方法和装置
US11985536B2 (en) UE-driven packet flow description management
WO2023116560A1 (zh) 通信的方法与装置
WO2024117117A1 (en) Method performed by first core network node, method of user equipment, first core network node, and user equipment
WO2024029421A1 (en) Method of access and mobility management function (amf), method of user equipment (ue), amf, and ue

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019947465

Country of ref document: EP

Effective date: 20220407