WO2024168550A1 - 信息获取方法及装置 - Google Patents

信息获取方法及装置 Download PDF

Info

Publication number
WO2024168550A1
WO2024168550A1 PCT/CN2023/076025 CN2023076025W WO2024168550A1 WO 2024168550 A1 WO2024168550 A1 WO 2024168550A1 CN 2023076025 W CN2023076025 W CN 2023076025W WO 2024168550 A1 WO2024168550 A1 WO 2024168550A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
message
user location
location information
iab
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/076025
Other languages
English (en)
French (fr)
Inventor
刘晓菲
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to EP23921718.5A priority Critical patent/EP4668787A4/en
Priority to PCT/CN2023/076025 priority patent/WO2024168550A1/zh
Priority to CN202380008242.2A priority patent/CN118805389A/zh
Publication of WO2024168550A1 publication Critical patent/WO2024168550A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to an information acquisition method and device.
  • the IAB-node provides wireless access and wireless backhaul for access services to terminal devices.
  • the donor node (IAB-donor) provides wireless backhaul functions to the IAB-node and provides an interface between the terminal device and the core network device.
  • the IAB-node is connected to the IAB-donor through a wireless backhaul link, so that the terminal device served by the IAB-node is connected to the core network device.
  • the user location information of the IAB-node is not supported to be reported to the core network device. Therefore, how the core network device determines the user location information of the IAB-node is an urgent problem to be solved.
  • the embodiments of the present disclosure provide an information acquisition method and device thereof, which can be applied to a 5G system and is suitable for supporting scenarios of integrated access and backhaul IAB.
  • the core network device can determine the user location information of the second node.
  • an embodiment of the present disclosure provides an information acquisition method, which is executed by a core network device, and the method includes: the core network device receives first indication information sent by a first node or a second node, wherein the first node is a host node of the second node, and the first indication information is used to indicate user location information of the second node.
  • a core network device receives first indication information sent by a first node or a second node, wherein the first node is a host node of the second node, and the first indication information is used to indicate user location information of the second node.
  • the core network device can determine the user location information of the second node.
  • an embodiment of the present disclosure provides another information acquisition method, which is executed by a first node, and the method includes: sending first indication information to a core network device, wherein the first node is a host node of a second node, and the first indication information is used to indicate user location information of the second node.
  • an embodiment of the present disclosure provides another information acquisition method, which is executed by a fourth node, and the method includes: sending a first message to a first node, wherein the first message includes user location information for indicating a second node, and the first node is a host node of the second node.
  • an embodiment of the present disclosure provides another information acquisition method, which is executed by a second node, and the method includes: sending first indication information to a core network device, wherein the first indication information is used to indicate user location information of the second node.
  • an embodiment of the present disclosure provides a communication device, which has some or all of the functions of the core network device in the method described in the first aspect above.
  • the functions of the communication device may have some or all of the functions in the embodiments of the present disclosure, or may have the functions of implementing any one of the embodiments of the present disclosure alone.
  • the functions may be implemented by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform the corresponding functions in the above method.
  • the transceiver module is used to support communication between the communication device and other devices.
  • the communication device may also include a storage module, which is coupled to the transceiver module and the processing module, and stores computer programs and data necessary for the communication device.
  • the communication device includes: a transceiver module configured to receive first indication information sent by a first node or a second node, wherein the first node is a host node of the second node, and the first indication information is used to indicate user location information of the second node.
  • an embodiment of the present disclosure provides another communication device, which has the function of implementing some or all of the functions of the first node in the method example described in the second aspect above, such as the function of the communication device may have the functions in some or all of the embodiments in the present disclosure, or may have the function of implementing any one of the embodiments in the present disclosure alone.
  • the functions may be implemented by hardware, or may be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform the corresponding functions in the above method.
  • the transceiver module is used to support communication between the communication device and other devices.
  • the communication device may also include a storage module, which is coupled to the transceiver module and the processing module and stores computer programs and data necessary for the communication device.
  • the communication device includes: a transceiver module configured to send first indication information to a core network device, wherein the first node is a host node of a second node, and the first indication information is used to indicate user location information of the second node.
  • an embodiment of the present disclosure provides another communication device, which has the function of implementing some or all of the functions of the fourth node in the method example described in the third aspect above.
  • the function of the communication device may have the functions in some or all of the embodiments in the present disclosure, or may have the function of implementing any one of the embodiments in the present disclosure alone.
  • the functions may be implemented by hardware, or may be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform the corresponding functions in the above method.
  • the transceiver module is used to support communication between the communication device and other devices.
  • the communication device may also include a storage module, which is coupled to the transceiver module and the processing module and stores computer programs and data necessary for the communication device.
  • the communication device includes: a transceiver module configured to send a first message to a first node, wherein the first message includes user location information indicating a second node, and the first node is a host node of the second node.
  • an embodiment of the present disclosure provides another communication device, which has the function of implementing some or all of the functions of the second node in the method example described in the fourth aspect above, such as the function of the communication device may have the functions in some or all of the embodiments in the present disclosure, or may have the function of implementing any one of the embodiments in the present disclosure alone.
  • the functions may be implemented by hardware, or may be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform the corresponding functions in the above method.
  • the transceiver module is used to support communication between the communication device and other devices.
  • the communication device may also include a storage module, which is coupled to the transceiver module and the processing module and stores computer programs and data necessary for the communication device.
  • the communication device includes: a transceiver module configured to send first indication information to a core network device, wherein the first indication information is used to indicate user location information of the second node.
  • an embodiment of the present disclosure provides a communication device, which includes a processor.
  • the processor calls a computer program in a memory, the method described in the first aspect is executed.
  • an embodiment of the present disclosure provides a communication device, which includes a processor.
  • the processor calls a computer program in a memory, the method described in the second aspect is executed.
  • an embodiment of the present disclosure provides a communication device, which includes a processor.
  • the processor calls a computer program in a memory, the method described in the third aspect is executed.
  • an embodiment of the present disclosure provides a communication device, which includes a processor.
  • the processor calls a computer program in a memory, the method described in the fourth aspect is executed.
  • an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program so that the communication device executes the method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program so that the communication device executes the method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program so that the communication device executes the method described in the third aspect above.
  • an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program so that the communication device executes the method described in the fourth aspect above.
  • an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to execute the code instructions to enable the device to execute the method described in the first aspect above.
  • an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to execute the code instructions to enable the device to execute the method described in the second aspect above.
  • an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the third aspect above.
  • an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the fourth aspect above.
  • an embodiment of the present disclosure provides an information acquisition system, the system comprising the communication device described in aspect 5, the communication device described in aspect 6, the communication device described in aspect 7, and/or the communication device described in aspect 8; or, the system comprises the communication device described in aspect 9, the communication device described in aspect 10, the communication device described in aspect 11, and/or the communication device described in aspect 12; or, the system comprises the communication device described in aspect 13, the communication device described in aspect 14, the communication device described in aspect 15, and/or the communication device described in aspect 16; or, the system comprises the communication device described in aspect 17, the communication device described in aspect 18, the communication device described in aspect 19, and/or the communication device described in aspect 20.
  • an embodiment of the present disclosure provides a computer-readable storage medium for storing instructions used by the above-mentioned core network device.
  • the core network device executes the method described in the first aspect.
  • an embodiment of the present disclosure provides a readable storage medium for storing instructions used by the above-mentioned first node.
  • the first node executes the method described in the above-mentioned second aspect.
  • an embodiment of the present disclosure provides a readable storage medium for storing instructions used by the fourth node mentioned above.
  • the fourth node executes the method described in the third aspect mentioned above.
  • an embodiment of the present disclosure provides a readable storage medium for storing instructions used by the above-mentioned second node.
  • the second node executes the method described in the above-mentioned fourth aspect.
  • the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect above.
  • the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the second aspect above.
  • the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the third aspect above.
  • the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the fourth aspect above.
  • the present disclosure provides a computer program which, when executed on a computer, enables the computer to execute the method described in the first aspect.
  • the present disclosure provides a computer program which, when executed on a computer, enables the computer to execute the method described in the second aspect.
  • the present disclosure provides a computer program which, when executed on a computer, enables the computer to execute the method described in aspect 3 above.
  • the present disclosure provides a computer program which, when executed on a computer, enables the computer to execute the method described in the fourth aspect.
  • FIG1 is an architecture diagram of a communication system provided by an embodiment of the present disclosure.
  • FIG2 is a structural diagram of an IAB node provided in an embodiment of the present disclosure.
  • FIG3 is a schematic diagram of a backhaul link and an access link provided by an embodiment of the present disclosure
  • FIG4 is an architecture diagram of an exemplary communication system applicable to an embodiment of the present disclosure.
  • FIG5 is an architecture diagram of an exemplary communication system applicable to an embodiment of the present disclosure
  • FIG6 is an architecture diagram of an exemplary communication system applicable to an embodiment of the present disclosure.
  • FIG7 is a schematic diagram of an integrated access and backhaul IAB architecture provided by an embodiment of the present disclosure.
  • FIG8 is a schematic diagram of another integrated access and backhaul IAB architecture provided by an embodiment of the present disclosure.
  • FIG9 is a schematic diagram of an IAB-MT migration provided by an embodiment of the present disclosure.
  • FIG10 is a schematic diagram of another IAB-MT migration provided by an embodiment of the present disclosure.
  • FIG11 is a flow chart of an information acquisition method provided by an embodiment of the present disclosure.
  • FIG12 is a flow chart of another information acquisition method provided by an embodiment of the present disclosure.
  • FIG13a is a schematic diagram of a flow chart of another information acquisition method provided by an embodiment of the present disclosure.
  • FIG13b is a schematic diagram of a flow chart of another information acquisition method provided by an embodiment of the present disclosure.
  • FIG14a is a flow chart of another information acquisition method provided by an embodiment of the present disclosure.
  • FIG14b is a flow chart of another information acquisition method provided by an embodiment of the present disclosure.
  • FIG15 is a flow chart of another information acquisition method provided by an embodiment of the present disclosure.
  • FIG16 is a flow chart of another information acquisition method provided by an embodiment of the present disclosure.
  • FIG17 is a flow chart of another information acquisition method provided by an embodiment of the present disclosure.
  • FIG18 is a flow chart of another information acquisition method provided by an embodiment of the present disclosure.
  • FIG19 is a flow chart of another information acquisition method provided by an embodiment of the present disclosure.
  • FIG20 is a flow chart of another information acquisition method provided by an embodiment of the present disclosure.
  • FIG21 is a flow chart of another information acquisition method provided by an embodiment of the present disclosure.
  • FIG22 is a flow chart of another information acquisition method provided by an embodiment of the present disclosure.
  • FIG23 is a structural diagram of an information acquisition system provided by an embodiment of the present disclosure.
  • FIG24 is a structural diagram of another information acquisition system provided by an embodiment of the present disclosure.
  • FIG25 is a flow chart of another information acquisition method provided by an embodiment of the present disclosure.
  • FIG26 is a flow chart of another information acquisition method provided by an embodiment of the present disclosure.
  • FIG27 is a flow chart of another information acquisition method provided by an embodiment of the present disclosure.
  • FIG28 is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure.
  • FIG29 is a schematic diagram of the structure of another communication device provided in an embodiment of the present disclosure.
  • FIG30 is a schematic diagram of the structure of a chip provided in an embodiment of the present disclosure.
  • first, second, third, etc. may be used to describe various information in the disclosed embodiments, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information.
  • the words "if” and “if” as used herein may be interpreted as “at” or "when” or "in response to determination”.
  • FIG. 1 shows an IAB system, where the IAB node provides wireless access and wireless backhaul of access services for terminal devices.
  • the IAB donor node IAB host node
  • the IAB node provides wireless backhaul function to the IAB node and provides an interface between the terminal device and the core network device.
  • the IAB node is connected to the IAB donor node via a wireless backhaul link, so that the terminal device served by the IAB node is connected to the core network device.
  • the network architecture may not be limited to including terminal devices, wireless backhaul devices and host nodes.
  • core network devices or devices for carrying virtualized network functions may also be included.
  • the network architecture does not limit the number of terminal devices, wireless backhaul devices and host nodes, for example, it may also include multiple terminal devices, multiple wireless backhaul devices and multiple host nodes.
  • the wireless backhaul device may be an IAB node.
  • FIG2 shows a schematic diagram of the structure of an IAB node.
  • the IAB node in NR may include a mobile terminal (MT) and a distributed unit (DU).
  • MT can also be understood as a component similar to a terminal in the IAB node.
  • DU is relative to the centralized unit (CU) function of the network device. Therefore, it can also be considered that the IAB node includes MT function and DU function.
  • the MT function is referred to as MT or IAB-MT
  • the DU function is referred to as DU or IAB-DU. Since MT is similar to the function of an ordinary terminal, it can be understood that MT is used for the IAB node to communicate with the upper node (parent node).
  • the DU is used for the IAB node to communicate with the lower node (child node).
  • the parent node can be a base station or other IAB node
  • the child node can be a terminal or other IAB node.
  • the link for MT to communicate with the parent node is called the parent backhaul link
  • the link for DU to communicate with the subordinate IAB node is called the child backhaul link
  • the link for DU to communicate with the subordinate terminal is called the access link.
  • the IAB node can be connected to the host node through multiple levels of parent nodes.
  • the subordinate backhaul link is also called the access link, wherein the upper backhaul link includes the upper backhaul uplink (uplink, UL) and the upper backhaul downlink (downlink, DL), the subordinate backhaul link includes the subordinate backhaul UL and the subordinate backhaul DL, and the access link includes the access UL and the access DL, as shown in Figure 3.
  • the information acquisition method provided by the embodiments of the present disclosure can be applied to various communication systems including wireless backhaul equipment, such as NR system, LTE system, LTE-A system, worldwide interoperability for microwave access (WiMAX), or wireless local area networks (WLAN).
  • wireless backhaul equipment such as NR system, LTE system, LTE-A system, worldwide interoperability for microwave access (WiMAX), or wireless local area networks (WLAN).
  • the communication method provided by the embodiment of the present disclosure can be applied to the network architecture shown in Figure 1.
  • the terminal device is connected to the wireless backhaul device by wireless means, and the wireless backhaul device is connected to the host node by wireless means.
  • the terminal device and the wireless backhaul device, as well as the wireless backhaul device and the host node can communicate through the licensed spectrum (licensed spectrum), or through the unlicensed spectrum (unlicensed spectrum), or through both the licensed spectrum and the unlicensed spectrum.
  • the licensed spectrum can be a spectrum below 6 GHz, which is not limited here. It should be understood that Figure 1 is only an exemplary illustration and does not specifically limit the number of terminal devices and wireless backhaul devices included in the wireless communication system.
  • the wireless backhaul device regards the node that provides backhaul service to it as the only parent node.
  • the wireless backhaul device regards the host node as the parent node.
  • the wireless backhaul device receives the wireless bearer carrying uplink information from the terminal device, it transmits the wireless bearer to the host node, and then the host node sends the uplink information in the wireless bearer to the mobile gateway device (for example, the user plane function (UPF) in the 5G network).
  • the mobile gateway device for example, the user plane function (UPF) in the 5G network.
  • the wireless bearer carrying downlink information sent by the mobile gateway device is sent to the host node, and then sent to the terminal device via the wireless backhaul device in turn.
  • the IAB node is used in the embodiments of the present disclosure only for the purpose of description, and does not mean that the solution of the embodiments of the present disclosure is only used in the NR scenario.
  • the IAB node can generally refer to any node or device with a wireless backhaul function.
  • the use of the IAB node and the relay node in the implementation of the present disclosure should be understood to have the same meaning.
  • FIG. 4 is an example of a communication system including multiple terminal devices and multiple IAB nodes.
  • FIG. 4 takes two terminal devices and two IAB nodes as an example, wherein the two terminal devices are terminal device 1 and terminal device 2, and the two IAB nodes are IAB node 1 and IAB node 2.
  • Terminal device 1 and terminal device 2 can access IAB node 2, IAB node 2 is connected to IAB node 1 by wireless, and IAB node 1 is connected to host node by wireless.
  • IAB node 1 is the parent node of IAB node 2
  • host node is the parent node of IAB node 1.
  • IAB node 2 provides wireless access services for terminal device 1 and terminal device 2 through access links (illustrated by thick lines in FIG.
  • the wireless bearers sent by terminal device 1 and terminal device 2 are transmitted to the host node via IAB node 2 and IAB node 1 in turn, and then the host node sends the uplink information in the wireless bearer to the mobile gateway device.
  • the mobile gateway device can send a radio bearer for carrying downlink information to the host node, and then send it to the terminal device 1 and the terminal device 2 via the IAB node 1 and the IAB node 2 in sequence.
  • the radio bearer sent by any terminal device is transmitted to the host node via two IAB nodes in sequence, which can be understood as a multi-hop wireless backhaul scenario, which can ensure the coverage of the network.
  • Figure 5 is an example of a communication system including 1 terminal device and multiple IAB nodes.
  • Figure 5 takes 1 terminal device and 3 IAB nodes as an example, and the 3 IAB nodes are IAB node 1, IAB node 2 and IAB node 3.
  • the terminal device can access the host node through two paths. One of the paths passes through the terminal device, IAB node 2, IAB node 1 and the host node in sequence; the other path passes through the terminal device, IAB node 2, IAB node 3, IAB node 1 and the host node in sequence.
  • the terminal device accesses the host node through multiple paths, which can be understood as a multi-connection wireless backhaul scenario, which can ensure the reliability of service transmission.
  • the architecture shown in Figure 5 can be understood as a multi-hop + multi-connection networking scenario.
  • FIG. 6 is an example of a communication system including multiple terminal devices and multiple IAB nodes.
  • FIG. 6 takes two terminal devices and five IAB nodes as an example, wherein the two terminal devices are terminal device 1 and terminal device 2, and the five IAB nodes are IAB nodes 1 to IAB nodes 5.
  • the thick line in FIG. 6 indicates the access link, and the thin line indicates the backhaul link.
  • the terminal device 1 can be connected to the host node via IAB node 5, IAB node 2 and IAB node 1.
  • the terminal device 1 can also be connected to the host node via IAB node 4, IAB node 2 and IAB node 1.
  • the terminal device 1 can also be connected to the host node via IAB node 4, IAB node 3 and IAB node 1.
  • the terminal device 2 can be connected to the host node via IAB node 4, IAB node 3 and IAB node 1.
  • the terminal device 2 can be connected to the host node via IAB node 4, IAB node 3 and IAB node 1.
  • the terminal device 2 can be connected to the host node via IAB node 4, IAB node 2 and IAB node 1.
  • an F1 interface needs to be established between the DU of the IAB node and the CU of the IAB host, and the configuration of routing and bearer mapping is completed, so that data transmission between the IAB node and the target IAB host can be performed according to the configuration.
  • the name of the interface is not limited in the embodiment of the present disclosure. And in this article, the interface is called the F1 interface as an example.
  • the F1 interface can support user plane protocols (F1-U) and control plane protocols (F1-C).
  • the user plane protocols include one or more of the following protocol layers: General Packet Radio Service (GPRS) tunneling protocol user plane (GPRS tunneling protocol user plane, GTP-U) protocol layer, user datagram protocol (UDP) protocol layer, Internet protocol (IP) protocol layer, etc.
  • the control plane protocols include one or more of the following protocol layers: F1 application protocol (F1AP), stream control transport protocol (SCTP), IP protocol layer, etc.
  • Terminal device is a device that provides voice and/or data connectivity to users.
  • the terminal device involved in the present disclosure may be a terminal device or a terminal, or a hardware component inside the terminal device that can realize the functions of the terminal device.
  • the terminal device may be referred to as user equipment (UE), mobile station (MS), mobile terminal (MT), etc., and may include, for example, a handheld device with a wireless connection function, or a processing device connected to a wireless modem.
  • the terminal device may communicate with a core network device via a radio access network (RAN) and exchange voice and/or data with the RAN.
  • RAN radio access network
  • Some examples of terminal devices are: personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loops (WLANs), and wireless cellular networks.
  • WLL personal digital assistants
  • PDA personal digital assistants
  • RFID radio frequency identification
  • sensors satellite navigation systems such as the global positioning system (GPS), Beidou positioning system, laser scanners and other information sensing devices.
  • Terminal devices can also be wearable devices.
  • Wearable devices can also be called wearable smart devices. They are a general term for wearable devices that use wearable technology to intelligently design and develop wearable devices for daily wear, such as glasses, gloves, watches, clothing and shoes.
  • Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, and independent of smartphones to achieve complete or partial functions, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets, smart helmets, and smart jewelry for vital sign monitoring.
  • the terminal can also be a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a terminal device in a future evolved public land mobile network (PLMN), or a vehicle device in vehicle to everything (V2X), customer premises equipment (CPE), etc.
  • VR virtual reality
  • AR augmented reality
  • PLMN future evolved public land mobile network
  • V2X vehicle device in vehicle to everything
  • CPE customer premises equipment
  • the functions of the terminal device can be realized by hardware components inside the terminal device, and the hardware components can be processors and/or programmable chips inside the terminal device.
  • the chip can be realized by application-specific integrated circuit (ASIC) or programmable logic device (PLD).
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above-mentioned PLD can be any one of complex programmable logical device (CPLD), field-programmable gate array (FPGA), generic array logic (GAL), system on a chip (SOC) or any combination thereof.
  • Vehicle-mounted terminal devices are also called on-board units (OBU).
  • OBU on-board units
  • Donor node also known as donor base station, refers to a node through which core network devices can be accessed. It is a device in the communication system that connects terminal devices to the wireless network.
  • the donor node is generally connected to the core network device through a wired link (such as an optical fiber cable).
  • the donor node can be responsible for receiving data from the core network device and forwarding it to the wireless backhaul device, or receiving data from the wireless backhaul device and forwarding it to the core network device.
  • the donor node can generally be connected to the network by wire.
  • the host node may include a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a baseband unit (BBU), etc. It may also include an evolved base station (NodeB or eNB or e-NodeB, evolutionary Node B) in an evolved LTE system (LTE-Advanced, LTE-A), or it may also include a next generation node B (gNB) in a fifth generation mobile communication technology (5G) new radio (NR) system, etc.
  • RNC radio network controller
  • NB node B
  • BSC base station controller
  • BTS base transceiver station
  • HNB home NodeB
  • BBU baseband unit
  • the donor node may include a centralized unit (CU) (abbreviated as Donor-CU or gNB-CU in this disclosure) and a distributed unit (DU) (abbreviated as Donor-DU or gNB-DU in this disclosure).
  • the gNB-CU and the gNB-DU are connected through an F1 interface, and the F1 interface may further include a control plane interface (F1-C) and a user plane interface (F1-U).
  • the CU and the core network device are connected through a next generation (NG) interface.
  • NG next generation
  • the gNB-CU or Donor-CU may also exist in a form in which the user plane (UP) (abbreviated as CU-UP in this disclosure) and the control plane (CP) (abbreviated as CU-CP in this disclosure) are separated, that is, the gNB-CU or Donor-CU is composed of a CU-CP and a CU-UP.
  • UP user plane
  • CP control plane
  • a gNB-CU may include a gNB-CU-CP and at least one gNB-CU-UP.
  • a Donor-CU may include a Donor-CU-CP and at least one Donor-CU-UP.
  • the functions of the host node may be implemented by hardware components inside the host node, for example, a processor and/or a programmable chip inside the host node.
  • the chip may be implemented by an ASIC or a PLD.
  • the PLD may be any one of CPLD, FPGA, GAL, SOC or any combination thereof.
  • the core network equipment is used to implement functions such as mobility management, data processing, session management, policy and billing.
  • functions such as mobility management, data processing, session management, policy and billing.
  • the names of the devices that implement the core network equipment functions in systems with different access technologies may be different, and this disclosure does not limit this.
  • the logical network elements of 5GC include: access and mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), unified data management (UDM), application function (AF), etc.
  • Access and mobility management function mainly performs mobility management, access authentication/authorization, etc.
  • the mobility management network element can also be responsible for transmitting user policies between the terminal and the policy control function (PCF) network element.
  • PCF policy control function
  • UPF User plane function
  • used to indicate may include being used to indicate directly or indirectly.
  • the information may include that the information directly indicates A or indirectly indicates A, but it does not mean that the information must carry A.
  • the information indicated by the information is called the information to be indicated.
  • the information to be indicated there are many ways to indicate the information to be indicated, such as but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or the index of the information to be indicated.
  • the information to be indicated can also be indirectly indicated by indicating other information, wherein there is an association between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance.
  • the indication of specific information can also be achieved by means of the arrangement order of each information agreed in advance (such as specified by the protocol), thereby reducing the indication overhead to a certain extent.
  • the information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately, and the sending period and/or sending time of these sub-information can be the same or different.
  • the specific sending method is not limited in this disclosure. Among them, the sending period and/or sending time of these sub-information can be pre-defined, for example, pre-defined according to a protocol.
  • the first, second and various digital numbers are only used for the convenience of description and are not used to limit the scope of the embodiments of the present disclosure. For example, to distinguish different information.
  • the embodiments of the present disclosure list multiple implementation methods to clearly illustrate the technical solutions of the embodiments of the present disclosure.
  • the multiple embodiments provided by the embodiments of the present disclosure can be executed separately, or can be executed together with the methods of other embodiments of the embodiments of the present disclosure, or can be executed together with some methods in other related technologies separately or in combination; the embodiments of the present disclosure do not limit this.
  • IAB Integrated access and backhaul
  • NG-RAN NG radio access network
  • IAB-node The terminating node of NR backhaul on the network side is called IAB-donor, which is a gNB (base station of 5G network) with IAB function attached.
  • Backhaul can be performed through single hop or multi-hop.
  • NG-RAN supports IAB by wirelessly connecting the IAB-node to the gNB (called IAB-donor) that can serve the IAB-node.
  • the IAB-donor includes an IAB-donor-CU (central unit) and one or more IAB-donor-DU (distributed unit).
  • the IAB-donor may include an IAB-donor-CU-CP, multiple IAB-donor-CU-UPs and multiple IAB-donor-DUs.
  • the IAB-node is connected to the upstream IAB-node or IAB-donor-DU through the terminal function subset of the NR Uu interface (called the IAB-MT function in the IAB-node).
  • the IAB-node provides wireless backhaul to the downstream IAB-node and terminal devices through the network function of the NR Uu interface (called the IAB-DU function of the IAB-node).
  • the F1-C service between the IAB-node and the IAB-donor-CU is backhauled through the IAB-donor-DU and the optional intermediate hop IAB-node.
  • the F1-U service between the IAB-node and the IAB-donor-CU is backhauled through the IAB-donor-DU and the optional intermediate hop IAB-node.
  • the mobile IAB research work focuses on scenarios where vehicle-mounted mobile IAB nodes provide 5G coverage or capability enhancement for vehicle-mounted and/or surrounding terminal devices.
  • mobile IAB can perform one or more partial migrations.
  • the IAB-donor-CU connected to the IAB-node may change with the movement of the IAB-node, so it is necessary to perform the IAB-node migration process.
  • There are two types of migration processes partial migration (only IAB-MT migrates, and IAB-DU remains on the source IAB-donor) and full migration (IAB-MT and IAB-DU migrate from the source IAB-donor to the same target IAB-donor).
  • the migration process can also include other migrations besides the above two, such as IAB-DU migration.
  • Partial migration means that only the IAB-MT on the IAB-node migrates (also called switching) to a new IAB-donor, while the IAB-DU on the IAB-node still maintains the connection with the original IAB-donor (the connection needs to go through the IAB-donor-DU of the IAB-MT, that is, the corresponding transmission path needs to be established under the IAB-donor of the IAB-MT), and the terminal device context on the IAB-DU is also saved on the original IAB-donor.
  • the switching is shown in Figure 9.
  • the situation before the switching is shown in the left box in Figure 9. Before the migration, IAB-MT and IAB-DU are both connected to IAB-donor-CU1.
  • IAB-donor-CU1 is the donor that originally serves IAB-node. After a partial migration, IAB-donor-CU1 can be called F1 terminating IAB-donor-CU (or IAB-donor-CU of IAB-DU). At this time, the data of the terminal device will be transmitted between IAB-donor-CU1 through the F1 connection (only the data routing will pass through IAB-donor-DU2), that is, the context of the terminal device is saved on the F1 terminating IAB-donor, and IAB-MT has been switched to IAB-donor-CU2. The data of IAB-MT is transmitted through IAB-donor-CU2. IAB-donor-CU2 is called non-F1 terminating IAB-donor (or IAB-donor-CU of IAB-MT).
  • the F1-terminating IAB-donor (or IAB-DU's IAB-donor-CU) is IAB-donor-CU1
  • the non-F1 terminating IAB-donor is IAB-donor-CU2 (or IAB-MT's IAB-donor-CU).
  • IAB-MT may switch to a new IAB-donor (also called IAB-MT's target IAB-donor-CU), namely IAB-donor-CU3.
  • IAB-donor-CU2 will notify IAB-donor-CU1: IAB-MT has switched to a new IAB-donor-CU, namely IAB-donor-CU3. If IAB-donor-CU1 decides to perform the IAB transport migration management process to IAB-donor-CU3 (i.e., perform another partial migration), all traffic between IAB-DU and IAB-donor-CU1 will be migrated from the path under IAB-donor-CU2 to the path under IAB-donor-CU3.
  • the IAB-node provides wireless access and wireless backhaul for access services to terminal devices.
  • the donor node (IAB-donor) provides wireless backhaul functions to the IAB-node and provides an interface between the terminal device and the core network device.
  • the IAB-node is connected to the IAB-donor through a wireless backhaul link, so that the terminal device served by the IAB-node is connected to the core network device.
  • a terminal device accesses the network through an IAB-node
  • the relevant technology does not support the core network device connected to the terminal device to obtain the user location information of the IAB-node to assist the core network device of the terminal device in managing the location information of the terminal device. Therefore, how the core network device of the terminal device determines the user location information of the IAB-node is an urgent problem to be solved.
  • Figure 11 is a flow chart of an information acquisition method provided by an embodiment of the present disclosure.
  • the information acquisition method of the embodiment of the present disclosure can be executed by a core network device, or can also be executed by a network function in the core network device, for example, it can be executed by AMF.
  • the method may include but is not limited to the following steps:
  • S111 Receive first indication information sent by a first node or a second node, wherein the first node is a host node of the second node, and the first indication information is used to indicate user location information of the second node.
  • the core network device receives the first indication information sent by the first node, and the first indication information is used to indicate the user location information of the second node. Therefore, the core network device can determine the user location information of the second node.
  • the user location information of the second node may be the access network information where the second node resides, including but not limited to at least one of E-UTRA (Evolved-UMTS Terrestrial Radio Access) user location information, NR user location information, and information of a non-3GPP access network.
  • E-UTRA Evolved-UMTS Terrestrial Radio Access
  • the user location information of the second node may be the cell information where the second node resides, TAI (Tracking Area Identity), PSCell (Primary SCG (Secondary Cell Group) Cell) information, information used to identify a non-public network, and corresponding time information, for example: residing in a first cell at a first time, residing in a second cell at a second time, and so on.
  • the residing cell may be information of a cell that has already resided, or information of a cell that will reside in the future.
  • the user location information of the second node may also include the moving speed and/or movement trajectory of the second node.
  • the core network device receives the first indication information sent by the first node or the second node, including: receiving an NGAP message sent by the first node, wherein the NGAP message includes the first indication information; or receiving an NAS message sent by the second node, wherein the NAS message includes the first indication information.
  • the core network device receives the first indication information sent by the first node, and may receive a Next Generation Application Protocol (NGAP) message sent by the first node, wherein the NGAP message includes the first indication information.
  • NGAP Next Generation Application Protocol
  • the NGAP message is a UE-related message, including but not limited to an initial UE message, a UE context establishment feedback message, a UE context modification feedback message, a UE context release completion message, an RRC inactive transition report message, a PDU session resource release feedback message, a PDU session resource modification feedback message, a PDU resource notification message, and at least one of a PDU session resource modification indication message.
  • the NGAP message includes user location information of the terminal device, and the user location information of the terminal device includes first indication information.
  • the NGAP message includes user location information of the terminal device and first indication information.
  • the core network device receives the first indication information sent by the second node, and may receive a non-access stratum (NAS) message sent by the second node, wherein the NAS message includes the first indication information.
  • NAS non-access stratum
  • the second node may be an IAB node (IAB-node), and the first node may be a donor node (IAB-donor) of the second node.
  • IAB-node IAB node
  • IAB-donor donor node
  • the user location information of the second node is the user location information of the MT of the second node
  • the first node is the host node of the MT of the second node
  • the first node is the host node of the DU of the second node.
  • the second node may include a mobile terminal (MT) part and a distributed unit (DU) part.
  • MT mobile terminal
  • DU distributed unit
  • the user location information of the second node is the user location information of the MT of the second node.
  • the second node may perform partial migration or full migration, and the MT (IAB-MT) and DU (IAB-DU) of the second node may be connected to the same host node, or may be connected to different host nodes respectively.
  • the first node is a donor node (IAB-donor) of the second node.
  • the first node may be a donor node of the MT of the second node, or may also be a donor node of the DU of the second node.
  • the first node may be the host node of the MT and DU of the second node, and the embodiments of the present disclosure do not impose specific limitations on this.
  • the first node may include an IAB-donor-CU (central unit) and one or more IAB-donor-DUs (distributed units).
  • the first node may also be an IAB-donor-CU.
  • the core network device receives the first indication information sent by the first node or the second node, and can receive the first indication information sent by the first node or the second node at any time, and the first indication information is used to indicate the user location information of the second node.
  • the core network device may receive the first indication information sent by the first node or the second node through a non-terminal device related message, or the core network device may also receive the first indication information sent by the first node or the second node through a terminal device related message when the terminal device is connected to the core network device through the second node, and so on.
  • each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined and can be arbitrarily combined with other implementation modes or examples.
  • the core network device receives the first indication information sent by the first node or the second node, wherein the first node is the host node of the second node, and the first indication information is used to indicate the user location information of the second node.
  • the core network device can determine the user location information of the second node.
  • Figure 12 is a flowchart of another information acquisition method provided by an embodiment of the present disclosure.
  • the information acquisition method of the embodiment of the present disclosure can be executed by a core network device, or can also be executed by a network function in the core network device, for example, it can be executed by AMF.
  • the method may include but is not limited to the following steps:
  • S121 Receive first indication information sent by a first node or a second node, wherein the first node is a host node of the second node, and the first indication information is used to indicate user location information of the second node.
  • S121 can refer to the relevant description in the above embodiment, and will not be repeated here.
  • S122 Determine, based on the first indication information, that the additional user location information of the terminal device is the user location information of the second node, wherein a network connection is provided for the terminal device through the second node.
  • the terminal device can be connected to the core network device through the base station, and the base station can send the user location information (ULI) of the terminal device to the core network device.
  • the core network device can decide whether to allow the terminal device to perform specific operations at the location based on the user location information and provide services for the terminal device.
  • ULI is, for example, but not limited to, a cell identifier (Cell ID) and a tracking area identifier (TAI).
  • Cell ID cell identifier
  • TAI tracking area identifier
  • the terminal device is connected to the core network device through an IAB-node. Considering that the IAB-node is movable, the core network device needs to consider the user location information of the IAB-node when providing services to the terminal device.
  • the core network device when the core network device determines to provide a network connection for the terminal device through the second node, it can determine, according to the first indication information, that the additional user location information of the terminal device is the user location information of the second node. Thus, the core network device can consider the user location information of the second node as the additional user location information of the terminal device to provide accurate services to the terminal device and improve the service quality.
  • the core network device determines to provide a network connection for the terminal device through the second node. Upon receiving first indication information sent by the first node or the second node when the terminal device is connected to the core network device through the second node, the core network device determines to provide a network connection for the terminal device through the second node.
  • each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined and can be arbitrarily combined with other implementation modes or examples.
  • S121 to S122 can be implemented separately or in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S111 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • the core network device receives the first indication information sent by the first node or the second node, wherein the first node is the host node of the second node, and the first indication information is used to indicate the user location information of the second node; according to the first indication information, the additional user location information of the terminal device is determined to be the user location information of the second node, wherein the network connection is provided for the terminal device through the second node.
  • the core network device can provide accurate services for the terminal device according to the user location information and the additional user location information of the terminal device to improve the service quality.
  • Figure 13a is a flowchart of another information acquisition method provided by an embodiment of the present disclosure.
  • the information acquisition method of the embodiment of the present disclosure can be executed by a core network device, or can also be executed by a network function in the core network device, for example, it can be executed by AMF.
  • the method may include but is not limited to the following steps:
  • S131a Receive first indication information sent by a first node or a second node, wherein the first node is a host node of the second node, and the first indication information is used to indicate user location information of the second node.
  • S131a can refer to the relevant description in the above embodiment, which will not be repeated here.
  • S132a Receive second indication information sent by the first node or the second node, where the second indication information is used to indicate a cell identifier list under the second node.
  • S133a Determine, according to the cell identifier list of the second node and the user location information of the second node, an association relationship between the user location information of the second node and the cell identifier list of the second node.
  • S134a Determine additional user location information of the terminal device according to the service cell identifier and association relationship of the terminal device.
  • a core network device receives second indication information sent by a first node or a second node, and the second indication information indicates a cell identifier list under the second node.
  • the core network device can determine the cell identifier list under the second node.
  • the core network device receives the second indication information sent by the first node or the second node, including: receiving an NGAP message sent by the first node, wherein the NGAP message includes the second indication information; or receiving a NAS message sent by the second node, wherein the NAS message includes the second indication information.
  • the core network device receives the second indication information sent by the first node, and may receive an NGAP message sent by the first node, wherein the NGAP message includes the second indication information.
  • the core network device receives the second indication information sent by the second node, and may receive a NAS message sent by the second node, wherein the NAS message includes the second indication information.
  • the core network device receives the second indication information sent by the first node or the second node, and can determine the association between the user location information of the second node and the cell identification list under the second node based on the cell identification list under the second node in the second indication information and the user location information of the second node.
  • the core network device can determine the additional user location information of the terminal device according to the serving cell identifier and the association relationship of the terminal device.
  • the core network device can consider the user location information of the second node as the additional user location information of the terminal device, and provide accurate services for the terminal device to improve the service quality.
  • the core network device determines the association relationship between the user location information of the second node and the cell identification list under the second node.
  • the additional user location information of the terminal device can be determined to be the user location information of the second node. Therefore, the core network device can consider the user location information of the second node as the additional user location information of the terminal device to provide accurate services for the terminal device and improve the service quality.
  • each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined and can be arbitrarily combined with other implementation modes or examples.
  • S131 to S134 can be implemented separately or in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S111 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • the core network device receives the first indication information sent by the first node or the second node, wherein the first node is the host node of the second node, and the first indication information is used to indicate the user location information of the second node; receives the second indication information sent by the first node or the second node, wherein the second indication information is used to indicate the cell identification list under the second node; determines the association relationship between the user location information of the second node and the cell identification list according to the cell identification list under the second node and the user location information of the second node, and determines the additional user location information of the terminal device according to the service cell identification and the association relationship of the terminal device.
  • the core network device can consider the user location information of the second node as the additional user location information of the terminal device, so as to provide accurate services for the terminal device and improve the service quality.
  • Figure 13b is a flowchart of another information acquisition method provided by an embodiment of the present disclosure.
  • the information acquisition method of the embodiment of the present disclosure can be executed by a core network device, or can also be executed by a network function in the core network device, for example, it can be executed by AMF.
  • the method may include but is not limited to the following steps:
  • S131b Receive first indication information sent by the first node or the second node, wherein the first node is a host node of the second node, and the first indication information is used to indicate user location information of the second node.
  • S131b can refer to the relevant description in the above embodiment, which will not be repeated here.
  • S132b Receive second indication information sent by the first node or the second node, where the second indication information is used to indicate an identifier of the second node.
  • the identifier of the second node is used to identify the second node or the MT on the second node, and the identifier of the second node can be AMF UE NGAP ID, RAN UE NGAP ID, UE XnAP ID, F1AP UE ID, or GPSI (Generic Public Subscription Identifier), etc.
  • S133b Determine, according to the identifier of the second node and the user location information of the second node, an association relationship between the user location information of the second node and the identifier of the second node.
  • S134b Determine additional user location information of the terminal device according to the second node identifier and the association relationship provided by the terminal device.
  • the core network device receives second indication information sent by the first node or the second node, and the second indication information indicates the identifier of the second node.
  • the core network device can determine the identifier of the second node.
  • the core network device receives the second indication information sent by the first node or the second node, including: receiving an NGAP message sent by the first node, wherein the NGAP message includes the second indication information; or receiving a NAS message sent by the second node, wherein the NAS message includes the second indication information.
  • the core network device receives the second indication information sent by the first node, and may receive an NGAP message sent by the first node, wherein the NGAP message includes the second indication information.
  • the core network device receives the second indication information sent by the second node, and may receive a NAS message sent by the second node, wherein the NAS message includes the second indication information.
  • the core network device receives the second indication information sent by the first node or the second node, and can determine the association between the user location information of the second node and the identifier of the second node based on the identifier of the second node in the second indication information and the user location information of the second node.
  • the core network device can determine the additional user location information of the terminal device according to the identifier and association relationship of the second node provided by the terminal device.
  • the core network device can consider the user location information of the second node as the additional user location information of the terminal device, and provide accurate services for the terminal device to improve the service quality.
  • the core network device determines the association between the user location information of the second node and the identifier of the second node, and when the terminal device provides the identifier of the second node, the additional user location information of the terminal device can be determined as the user location information of the second node.
  • the core network device can consider the user location information of the second node as the additional user location information of the terminal device to provide accurate services for the terminal device and improve the service quality.
  • each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined and can be arbitrarily combined with other implementation modes or examples.
  • S131 to S134 can be implemented separately or in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S111 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • the core network device receives the first indication information sent by the first node or the second node, wherein the first node is the host node of the second node, and the first indication information is used to indicate the user location information of the second node; receives the second indication information sent by the first node or the second node, wherein the second indication information is used to indicate the identifier of the second node; determines the association relationship between the user location information of the second node and the identifier of the second node according to the identifier of the second node and the user location information of the second node; determines the additional user location information of the terminal device according to the identifier and the association relationship of the second node provided by the terminal device.
  • the core network device can consider the user location information of the second node as the additional user location information of the terminal device, so as to provide accurate services for the terminal device and improve the service quality.
  • Figure 14a is a flowchart of another information acquisition method provided by an embodiment of the present disclosure.
  • the information acquisition method of the embodiment of the present disclosure can be executed by a core network device, or can also be executed by a network function in the core network device, for example, it can be executed by AMF.
  • the method may include but is not limited to the following steps:
  • S141a Receive first indication information sent by a first node or a second node, wherein the first node is a host node of the second node, and the first indication information is used to indicate user location information of the second node.
  • S141a can refer to the relevant description in the above embodiment, which will not be repeated here.
  • S142a Receive second indication information sent by the first node or the second node, where the second indication information is used to indicate an association relationship between a cell identifier list under the second node and user location information of the second node.
  • S143a Determine additional user location information of the terminal device according to the service cell identifier and association relationship of the terminal device.
  • a core network device receives second indication information sent by a first node or a second node, and the second indication information indicates an association between a cell identification list under the second node and user location information of the second node.
  • the core network device can determine the association between the cell identification list under the second node and the user location information of the second node.
  • the core network device can determine the additional user location information of the terminal device according to the serving cell identifier and the association relationship of the terminal device.
  • the core network device can consider the user location information of the second node as the additional user location information of the terminal device, and provide accurate services for the terminal device to improve the service quality.
  • the core network device determines the association relationship between the user location information of the second node and the cell identification list under the second node.
  • the additional user location information of the terminal device can be determined to be the user location information of the second node. Therefore, the core network device can consider the user location information of the second node as the additional user location information of the terminal device to provide accurate services for the terminal device and improve the service quality.
  • the core network device receives the second indication information sent by the first node or the second node, including: receiving an NGAP message sent by the first node, wherein the NGAP message includes the second indication information; or receiving a NAS message sent by the second node, wherein the NAS message includes the second indication information.
  • the core network device receives the second indication information sent by the first node, and may receive an NGAP message sent by the first node, wherein the NGAP message includes the second indication information.
  • the core network device receives the second indication information sent by the second node, and may receive a NAS message sent by the second node, wherein the NAS message includes the second indication information.
  • each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined and can be arbitrarily combined with other implementation modes or examples.
  • S141 to S143 can be implemented separately or in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S111 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • the core network device receives the first indication information sent by the first node or the second node, wherein the first node is the host node of the second node, and the first indication information is used to indicate the user location information of the second node; receives the second indication information sent by the first node or the second node, wherein the second indication information is used to indicate the association relationship between the cell identification list under the second node and the user location information of the second node; determines the additional user location information of the terminal device according to the service cell identification and the association relationship of the terminal device.
  • the core network device can consider the user location information of the second node as the additional user location information of the terminal device, so as to provide accurate services for the terminal device and improve the service quality.
  • Figure 14b is a flowchart of another information acquisition method provided by an embodiment of the present disclosure.
  • the information acquisition method of the embodiment of the present disclosure can be executed by a core network device, or can also be executed by a network function in the core network device, for example, it can be executed by an AMF.
  • the method may include but is not limited to the following steps:
  • S141b Receive first indication information sent by the first node or the second node, wherein the first node is a host node of the second node, and the first indication information is used to indicate user location information of the second node.
  • S141b can refer to the relevant description in the above embodiment, which will not be repeated here.
  • S142b Receive second indication information sent by the first node or the second node, where the second indication information is used to indicate an association relationship between an identifier of the second node and user location information of the second node.
  • S143b Determine additional user location information of the terminal device according to the identifier and association relationship of the second node provided by the terminal device.
  • a core network device receives second indication information sent by a first node or a second node, and the second indication information indicates an association between an identifier of the second node and user location information of the second node.
  • the core network device can determine the association between the identifier of the second node and the user location information of the second node.
  • the core network device can determine the additional user location information of the terminal device according to the provided identifier and association relationship of the second node.
  • the core network device can consider the user location information of the second node as the additional user location information of the terminal device, and provide accurate services for the terminal device to improve the service quality.
  • the core network device determines the association between the user location information of the second node and the identifier of the second node, and when the terminal device provides the identifier of the second node, the additional user location information of the terminal device can be determined as the user location information of the second node.
  • the core network device can consider the user location information of the second node as the additional user location information of the terminal device to provide accurate services for the terminal device and improve the service quality.
  • the identifier of the second node is used to identify the second node or the MT on the second node, and the identifier of the second node can be AMF UE NGAP ID, RAN UE NGAP ID, UE XnAP ID, F1AP UE ID, or GPSI (Generic Public Subscription Identifier), etc.
  • the core network device receives the second indication information sent by the first node or the second node, including: receiving an NGAP message sent by the first node, wherein the NGAP message includes the second indication information; or receiving a NAS message sent by the second node, wherein the NAS message includes the second indication information.
  • the core network device receives the second indication information sent by the first node, and may receive an NGAP message sent by the first node, wherein the NGAP message includes the second indication information.
  • the core network device receives the second indication information sent by the second node, and may receive a NAS message sent by the second node, wherein the NAS message includes the second indication information.
  • each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined and can be arbitrarily combined with other implementation modes or examples.
  • S141 to S143 can be implemented separately or in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S111 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • the core network device receives the first indication information sent by the first node or the second node, wherein the first node is the host node of the second node, and the first indication information is used to indicate the user location information of the second node; receives the second indication information sent by the first node or the second node, wherein the second indication information is used to indicate the association relationship between the identifier of the second node and the user location information of the second node; and determines the additional user location information of the terminal device according to the identifier and the association relationship of the second node provided by the terminal device.
  • the core network device can consider the user location information of the second node as the additional user location information of the terminal device, so as to provide accurate services for the terminal device and improve the service quality.
  • Figure 15 is a flowchart of another information acquisition method provided by an embodiment of the present disclosure. It should be noted that the information acquisition method of the embodiment of the present disclosure can be executed by the first node. As shown in Figure 15, the method may include but is not limited to the following steps:
  • S151 Send first indication information to a core network device, wherein the first node is a host node of a second node, and the first indication information is used to indicate user location information of the second node.
  • the first node may send first indication information to the core network device, the first indication information being used to indicate the user location information of the second node.
  • the core network device supporting the connection of the terminal device obtains the user location information of the second node, wherein the terminal device accesses the network through the second node.
  • the user location information of the second node may be the access network information where the second node resides, including but not limited to E-UTRA (Evolved-UMTS Terrestrial Radio Access) user location information, NR user location information, and access information of a non-3GPP network.
  • E-UTRA Evolved-UMTS Terrestrial Radio Access
  • the user location information of the second node may be the cell information where the second node resides, TAI (Tracking Area Identity), PSCell (Primary SCG (Secondary Cell Group) Cell) information, information used to identify a non-public network, and corresponding time information, for example: residing in a first cell at a first time, residing in a second cell at a second time, and so on.
  • the resident cell may be information of a cell that has already resided, or information of a cell that will reside in the future.
  • the user location information of the second node may also include the moving speed and/or movement trajectory of the second node.
  • the first node sends the first indication information to the core network device, including: sending a NGAP message to the core network device, wherein the NGAP message includes the first indication information.
  • the NGAP message is a UE-related message, including but not limited to an initial UE message, a UE context establishment feedback message, a UE context modification feedback message, a UE context release completion message, an RRC inactive transition report message, a PDU session resource release feedback message, a PDU session resource modification feedback message, a PDU resource notification message, and at least one of a PDU session resource modification indication message.
  • the NGAP message includes user location information of the terminal device, and the user location information of the terminal device includes first indication information.
  • the NGAP message includes user location information of the terminal device and first indication information.
  • the first node sends the first indication information to the core network device, and may send an NGAP message to the core network device, wherein the NGAP message includes the first indication information.
  • the user location information of the second node is the user location information of the MT of the second node
  • the first node is the host node of the MT of the second node
  • the first node is the host node of the DU of the second node.
  • the second node may include a mobile terminal (mobile termination, MT) part and a distributed unit (distributed unit, DU) part.
  • MT mobile terminal
  • DU distributed unit
  • the user location information of the second node is the user location information of the MT of the second node.
  • the second node may perform partial migration or full migration, and the MT (IAB-MT) and DU (IAB-DU) of the second node may be connected to the same host node, or may be connected to different host nodes respectively.
  • the first node is a donor node (IAB-donor) of the second node.
  • the first node may be a donor node of the MT of the second node, or may also be a donor node of the DU of the second node.
  • the first node may be the host node of the MT and DU of the second node, and the embodiments of the present disclosure do not impose specific limitations on this.
  • the first node may include an IAB-donor-CU (central unit) and one or more IAB-donor-DUs (distributed units).
  • the first node may also be an IAB-donor-CU.
  • the first node sends the first indication information to the core network device, and the first indication information may be sent to the core network device at any time.
  • the first indication information is used to indicate the user location information of the second node.
  • the first node may send the first indication information to the core network device when there is no terminal device connected to the core network device through the second node, or the first node may also send the first indication information to the core network device when the terminal device is connected to the core network device through the second node, and so on.
  • each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined and can be arbitrarily combined with other implementation modes or examples.
  • the first node sends the first indication information to the core network device, wherein the first node is the host node of the second node, and the first indication information is used to indicate the user location information of the second node.
  • the core network device supporting the connection of the terminal device obtains the user location information of the second node, wherein the terminal device accesses the network through the second node.
  • Figure 16 is a flowchart of another information acquisition method provided by an embodiment of the present disclosure. It should be noted that the information acquisition method of the embodiment of the present disclosure can be executed by the first node. As shown in Figure 16, the method may include but is not limited to the following steps:
  • S161 Send first indication information to a core network device, wherein the first node is a host node of a second node, and the first indication information is used to indicate user location information of the second node.
  • S162 Send second indication information to the core network device.
  • the second indication information is used to indicate at least one of the following:
  • the first node may send second indication information to the core network device, where the second indication information is used to indicate the cell identifier list of the second node, thereby supporting the first node to report the cell identifier list of the second node to the core network device.
  • the first node may send second indication information to the core network device, where the second indication information is used to indicate the identifier of the second node, thereby supporting the first node to report the identifier of the second node to the core network device.
  • the first node may send second indication information to the core network device, and the second indication information is used to indicate the association relationship between the cell identification list under the second node and the user location information of the second node.
  • the first node may support reporting the association relationship between the cell identification list under the second node and the user location information of the second node to the core network device.
  • the first node may send second indication information to the core network device, and the second indication information is used to indicate the association relationship between the identifier of the second node and the user location information of the second node.
  • the first node may support reporting the association relationship between the identifier of the second node and the user location information of the second node to the core network device.
  • the identifier of the second node is used to identify the second node or the MT on the second node, and the identifier of the second node can be AMF UE NGAP ID, RAN UE NGAP ID, UE XnAP ID, F1AP UE ID, or GPSI (Generic Public Subscription Identifier), etc.
  • the first node sends the second indication information to the core network device, including: sending a NGAP message to the core network device, wherein the NGAP message includes the second indication information.
  • the first node sends the second indication information to the core network device, and may send an NGAP message to the core network device, wherein the NGAP message includes the second indication information.
  • each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined and can be arbitrarily combined with other implementation modes or examples.
  • S161 to S162 can be implemented separately or in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S151 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • the first node sends a first indication message to the core network device, wherein the first node is the host node of the second node, and the first indication message is used to indicate the user location information of the second node; and sends a second indication message to the core network device.
  • the first node is supported to report the user location information of the second node, and at least one of the cell identification list under the second node, the identification of the second node, the association relationship between the cell identification list under the second node and the user location information of the second node, and the association relationship between the identification of the second node and the user location information of the second node to the core network device.
  • Figure 17 is a flowchart of another information acquisition method provided by an embodiment of the present disclosure. It should be noted that the information acquisition method of the embodiment of the present disclosure can be executed by the first node. As shown in Figure 17, the method may include but is not limited to the following steps:
  • S171 Determine user location information of the second node.
  • the first node may determine the user location information of the second node.
  • the first node can determine the user location information of the second node by itself, thereby determining the user location information of the second node, or can also receive the user location information of the second node sent by the second node, thereby determining the user location information of the second node, or can also receive the user location information of the second node sent by other nodes, thereby determining the user location information of the second node, and so on.
  • the embodiments of the present disclosure do not impose specific restrictions on this.
  • S172 Send first indication information to the core network device, wherein the first node is a host node of the second node, and the first indication information is used to indicate user location information of the second node.
  • each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined and can be arbitrarily combined with other implementation modes or examples.
  • S171 to S172 can be implemented separately or in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S151 and/or S161 to S162 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • the first node sends the first indication information to the core network device, wherein the first node is the host node of the second node, and the first indication information is used to indicate the user location information of the second node.
  • the core network device supporting the connection of the terminal device obtains the user location information of the second node, wherein the terminal device accesses the network through the second node.
  • Figure 18 is a flowchart of another information acquisition method provided by an embodiment of the present disclosure. It should be noted that the information acquisition method of the embodiment of the present disclosure can be executed by the first node. As shown in Figure 18, the method may include but is not limited to the following steps:
  • S181 Receive a first message sent by a third node, where the first message is used to indicate user location information of a second node.
  • S182 Determine user location information of the second node according to the first message.
  • a first node may receive a first message sent by a third node, wherein the first message is used to indicate user location information of a second node.
  • the first node may determine user location information of the second node based on the user location information indicating the second node in the first message.
  • the first message can be used to indicate the user location information of the second node, but the first message is not limited to being used for other purposes, for example, it can also be used to indicate other information, and the embodiment of the present disclosure does not impose specific limitations on this.
  • the third node is a DU of the second node.
  • the third node is the DU of the second node.
  • the host node of the DU of the second node receives the first message sent by the DU of the second node, wherein the first message is used to indicate the user location information of the second node, and the host node of the DU of the second node can determine the user location information of the second node based on the user location information used to indicate the second node in the first message.
  • the third node is a host node for a MT of the second node.
  • the third node is the host node of the MT of the second node.
  • the host node of the DU of the second node receives a first message sent by the host node of the MT of the second node, wherein the first message includes user location information indicating the second node, and the host node of the DU of the second node can determine the user location information of the second node based on the user location information of the second node in the first message.
  • the host node of the DU of the second node when the DU of the second node migrates, and the DU of the second node migrates from the source host node to the target host node, the host node of the DU of the second node can be the source host node of the DU of the second node or the target host node of the DU of the second node.
  • the third node is the source host node of the DU of the second node.
  • the third node is the source host node of the DU of the second node.
  • the target host node of the DU of the second node receives a first message sent by the source host node of the DU of the second node, wherein the first message includes user location information indicating the second node, and the target host node of the DU of the second node can determine the user location information of the second node based on the user location information indicating the second node in the first message.
  • a first node determines user location information of a second node, including: saving the user location information of the second node, and determining an association between the user location information of the second node and the second node; if a terminal device accesses a core network device through the second node, the first node sends the user location information of the second node to the core network device through a message related to the terminal device.
  • the first message is at least one of the following:
  • the first message may be an F1 application protocol (F1 application protocol, F1AP) message.
  • F1 application protocol F1 application protocol, F1AP
  • the first message may be a radio resource control (RRC) message.
  • RRC radio resource control
  • the first message may be an Xn interface application protocol (Xn application protocol, XnAP) message.
  • Xn application protocol XnAP
  • the first message is a message for instructing the MT of the second node to perform handover.
  • the first message may be a message for instructing the MT of the second node to perform a handover.
  • the first message may be a message for notifying the IAB-MT of the handover.
  • the first message is a message related to the terminal device or a message unrelated to the terminal device.
  • the first message may be a message related to the terminal device, or the first message may also be a message unrelated to the terminal device.
  • the first message when the first message is a message unrelated to the terminal device, the first message also includes a cell identifier list and/or an identifier of the second node.
  • the first message when the first message is a message unrelated to the terminal device, the first message may further include a cell identifier list and/or an identifier of the second node.
  • the first message when the first message is an F1AP message, the first message is used to indicate user location information of the second node, and the user location information of the second node may be included in messages such as an F1 setup request (F1 SETUP REQUEST) message and/or a GNB-DU configuration update (GNB-DU CONFIGURATION UPDATE) message.
  • F1 setup request F1 SETUP REQUEST
  • GNB-DU CONFIGURATION UPDATE GNB-DU CONFIGURATION UPDATE
  • the first message when the first message is an F1AP message, the first message is used to indicate user location information of the second node, and the user location information of the second node may be included in a served cell information IE (served cell information IE).
  • a served cell information IE serving cell information IE
  • the F1AP message may be at least one of the following:
  • Terminal equipment context establishment feedback (UE CONTEXT SETUP RESPONSE) message
  • Terminal equipment context modification feedback (UE CONTEXT MODIFICATION RESPONSE) message
  • Terminal equipment inactivation notification (UE INACTIVITY NOTIFICATION) message.
  • the first message when the first message is an XnAP, the first message is used to indicate user location information of the second node, and the first message may be an IAB-MT migration completion indication message.
  • each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined and can be arbitrarily combined with other implementation modes or examples.
  • S181 to S182 can be implemented separately or in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S151 and/or S161 to S162 and/or S171 to S172 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • the first node receives the first message sent by the third node, wherein the first message is used to indicate the user location information of the second node; the user location information of the second node is determined according to the first message.
  • the first node can determine the user location information of the second node.
  • Figure 19 is a flowchart of another information acquisition method provided by an embodiment of the present disclosure. It should be noted that the information acquisition method of the embodiment of the present disclosure can be executed by the first node. As shown in Figure 19, the method may include but is not limited to the following steps:
  • S191 Determine an association relationship between a cell identifier list of a second cell and user location information of a second node, or determine an association relationship between an identifier of a second node and user location information of the second node.
  • the first node can determine the cell identification list of the second cell and the user location information of the second node by itself, and then establish an association relationship between the cell identification list and the user location information of the second node, thereby determining the association relationship between the cell identification list of the second cell and the user location information of the second node.
  • the first node can also receive the association relationship between the cell identification list and the user location information of the second node sent by other nodes, thereby determining the association relationship between the cell identification list of the second cell and the user location information of the second node.
  • the first node can determine the identifier of the second node and the user location information of the second node by itself, and then establish an association relationship between the identifier of the second node and the user location information of the second node, thereby determining the association relationship between the identifier of the second node and the user location information of the second node.
  • the first node can also receive the association relationship between the identifier of the second node and the user location information of the second node sent by other nodes, thereby determining the association relationship between the identifier of the second node and the user location information of the second node.
  • each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined and can be arbitrarily combined with other implementation modes or examples.
  • S191 can be implemented alone or in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S151 and/or S161 to S162 and/or S171 to S172 and/or S181 to S182 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • the first node determines the association between the cell identifier list of the second cell and the user location information of the second node.
  • the first node can determine the association between the cell identifier list of the second cell and the user location information of the second node.
  • Figure 20 is a flowchart of another information acquisition method provided by an embodiment of the present disclosure. It should be noted that the information acquisition method of the embodiment of the present disclosure can be executed by a third node. As shown in Figure 20, the method may include but is not limited to the following steps:
  • S201 Send a first message to a first node, where the first message is used to indicate user location information of a second node, and the first node is a host node of the second node.
  • the third node may send a first message to the first node, wherein the first message is used to indicate the user location information of the second node, thereby supporting the third node to send the user location information of the second node to the first node.
  • the first message can be used to indicate the user location information of the second node, but the first message is not limited to being used for other purposes, for example, it can also be used to indicate other information, and the embodiment of the present disclosure does not impose specific limitations on this.
  • the third node is a DU of the second node.
  • the third node is the DU of the second node.
  • the DU of the second node may send a first message to the host node of the DU of the second node, where the first message is used to indicate the user location information of the second node.
  • the third node is a host node for a MT of the second node.
  • the third node is the host node of the MT of the second node.
  • the host node of the MT of the second node may send a first message to the host node of the DU of the second node, where the first message is used to indicate the user location information of the second node.
  • the host node of the DU of the second node when the DU of the second node migrates, and the DU of the second node migrates from the source host node to the target host node, the host node of the DU of the second node can be the source host node of the DU of the second node or the target host node of the DU of the second node.
  • the third node is the source host node of the DU of the second node.
  • the third node is the source host node of the DU of the second node.
  • the source host node of the DU of the second node can send a first message to the target host node of the DU of the second node, and the first message is used to indicate the user location information of the second node.
  • the first message is at least one of the following:
  • the first message may be an F1 application protocol (F1 application protocol, F1AP) message.
  • F1 application protocol F1 application protocol, F1AP
  • the first message may be a radio resource control (RRC) message.
  • RRC radio resource control
  • the first message may be an Xn interface application protocol (Xn application protocol, XnAP) message.
  • Xn application protocol XnAP
  • the first message is a message for instructing the MT of the second node to perform handover.
  • the first message may be a message for instructing the MT of the second node to perform a handover.
  • the first message may be a message for notifying the IAB-MT of the handover.
  • the first message is a message related to the terminal device or a message unrelated to the terminal device.
  • the first message may be a message related to the terminal device, or the first message may also be a message unrelated to the terminal device.
  • the first message when the first message is a message unrelated to the terminal device, the first message also includes a cell identifier list and/or an identifier of the second node.
  • the first message when the first message is a message unrelated to the terminal device, the first message may further include a cell identifier list and/or an identifier of the second node.
  • the first message also includes a cell identifier list.
  • the first message when the first message is an F1AP message, the first message is used to indicate user location information of the second node, and the user location information of the second node may be included in messages such as an F1 setup request (F1 SETUP REQUEST) message and/or a GNB-DU configuration update (GNB-DU CONFIGURATION UPDATE) message.
  • F1 setup request F1 SETUP REQUEST
  • GNB-DU CONFIGURATION UPDATE GNB-DU CONFIGURATION UPDATE
  • the first message when the first message is an F1AP message, the first message is used to indicate user location information of the second node, and the user location information of the second node may be included in a served cell information IE (served cell information IE).
  • a served cell information IE serving cell information IE
  • the F1AP message may be at least one of the following:
  • Terminal equipment context establishment feedback (UE CONTEXT SETUP RESPONSE) message
  • Terminal equipment context modification feedback (UE CONTEXT MODIFICATION RESPONSE) message
  • Terminal equipment inactivation notification (UE INACTIVITY NOTIFICATION) message.
  • the first message when the first message is an XnAP, the first message is used to indicate user location information of the second node, and the first message may be an IAB-MT migration completion indication message.
  • each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined and can be arbitrarily combined with other implementation modes or examples.
  • the third node sends a first message to the first node, wherein the first message is used to indicate the user location information of the second node, and the first node is the host node of the second node.
  • the third node is supported to send the user location information of the second node to the first node.
  • Figure 21 is a flowchart of another information acquisition method provided by an embodiment of the present disclosure. It should be noted that the information acquisition method of the embodiment of the present disclosure can be executed by the second node. As shown in Figure 21, the method may include but is not limited to the following steps:
  • S211 Send first indication information to the core network device, where the first indication information is used to indicate user location information of the second node.
  • the second node may be an IAB-node, and the second node may send first indication information to the core network device, where the first indication information is used to indicate the user location information of the second node.
  • the second node is supported to report the user location information of the second node to the core network device.
  • the user location information of the second node may be the access network information where the second node resides, including but not limited to at least one of E-UTRA (Evolved-UMTS Terrestrial Radio Access) user location information, NR user location information, and information of a non-3GPP access network.
  • E-UTRA Evolved-UMTS Terrestrial Radio Access
  • the user location information of the second node may be the cell information where the second node resides, TAI (Tracking Area Identity), PSCell (Primary SCG (Secondary Cell Group) Cell) information, information used to identify a non-public network, and corresponding time information, for example: residing in a first cell at a first time, residing in a second cell at a second time, and so on.
  • the resident cell may be information of a cell that has already resided, or information of a cell that will reside in the future.
  • the user location information of the second node may also include the moving speed and/or movement trajectory of the second node.
  • the second node sends the first indication information to the core network device, including: sending a NGAP message to the core network device, wherein the NGAP message includes the first indication information.
  • the second node sends the first indication information to the core network device, and may send an NGAP message to the core network device, wherein the NGAP message includes the first indication information.
  • the NGAP message is a UE-related message, including but not limited to an initial UE message, a UE context establishment feedback message, a UE context modification feedback message, a UE context release completion message, an RRC inactive transition report message, a PDU session resource release feedback message, a PDU session resource modification feedback message, a PDU resource notification message, and at least one of a PDU session resource modification indication message.
  • the NGAP message includes user location information of the terminal device, and the user location information of the terminal device includes first indication information.
  • the NGAP message includes user location information of the terminal device and first indication information.
  • the user location information of the second node is user location information of the MT of the second node.
  • the second node may include a mobile terminal (mobile termination, MT) part and a distributed unit (distributed unit, DU) part.
  • MT mobile terminal
  • DU distributed unit
  • the user location information of the second node is the user location information of the MT of the second node.
  • each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined and can be arbitrarily combined with other implementation modes or examples.
  • the second node sends first indication information to the core network device, wherein the first indication information is used to indicate the user location information of the second node, thereby supporting the second node to report the user location information of the second node to the core network device.
  • Figure 22 is a flowchart of another information acquisition method provided by an embodiment of the present disclosure. It should be noted that the information acquisition method of the embodiment of the present disclosure can be executed by the second node. As shown in Figure 22, the method may include but is not limited to the following steps:
  • S221 Send first indication information to the core network device, where the first indication information is used to indicate user location information of the second node.
  • S222 Send second indication information to the core network device, where the second indication information is used to indicate a cell identifier list under the second node and/or an identifier of the second node.
  • the second node may send second indication information to the core network device, the second indication information being used to indicate the cell identification list under the second node and/or the identification of the second node.
  • the second node supports reporting the cell identification list to the core network device.
  • the identifier of the second node is used to identify the second node or the MT on the second node, and the identifier of the second node can be AMF UE NGAP ID, RAN UE NGAP ID, UE XnAP ID, F1AP UE ID, or GPSI (Generic Public Subscription Identifier), etc.
  • the second node sends the second indication information to the core network device, including: sending a NGAP message to the core network device, wherein the NGAP message includes the second indication information.
  • the second node sends the second indication information to the core network device, and may send an NGAP message to the core network device, wherein the NGAP message includes the second indication information.
  • each step can be independent, arbitrarily combined or exchanged in order, and the optional methods or optional examples can be arbitrarily combined and can be arbitrarily combined with other implementation modes or examples.
  • S221 to S222 can be implemented separately or in combination with any other steps in the embodiments of the present disclosure, for example, in combination with S211 in the embodiments of the present disclosure, and the embodiments of the present disclosure are not limited to this.
  • the second node sends first indication information to the core network device, wherein the first indication information is used to indicate the user location information of the second node, and sends second indication information to the core network device, wherein the second indication information is used to indicate the cell identification list under the second node and/or the identification of the second node.
  • the second node is supported to report the user location information of the second node and the cell identification list to the core network device.
  • Figure 23 is a structural diagram of an information acquisition system provided by an embodiment of the present disclosure. As shown in Figure 23, the system may include but is not limited to:
  • the core network device is configured to receive first indication information sent by a first node or a second node, wherein the first node is a host node of the second node, and the first indication information is used to indicate user location information of the second node.
  • the first node or the second node is configured to send first indication information to a core network device, wherein the first node is a host node of the second node, and the first indication information is used to indicate user location information of the second node.
  • the system may further include a third node configured to send a first message to the first node, wherein the first message is used to indicate user location information of the second node, and the first node is a host node of the second node;
  • the first node is further configured to determine user location information of the second node according to the first message.
  • the mobile IAB research work focuses on the scenarios where the vehicle-mounted mobile IAB nodes provide 5G coverage/capability enhancement for vehicle-mounted and/or surrounding terminals.
  • the base station serving the UE can send user location information (ULI) to the AMF through signaling, and the AMF can decide whether to allow the terminal to operate at its current location based on the user location information.
  • UMI user location information
  • 3GPP SA2 agrees that the IAB-donor serving the UE needs to provide the ULI of the IAB-MT of the IAB-node as an additional ULI.
  • the IAB-donor-CU serving the UE i.e., the IAB-donor-CU of the IAB-DU
  • the IAB-donor-CU serving the UE i.e., the IAB-donor-CU of the IAB-DU
  • various methods may be used to support providing an accurate additional ULI of a UE to a core network device in the following scenarios:
  • the IAB-MT is switched.
  • IAB-DU is migrated.
  • the IAB-donor-CU serving the UE may obtain the IAB-MT ULI from the IAB-donor-CU serving the IAB-MT, and send the IAB-MT ULI as an additional ULI of the UE to the core network device.
  • the IAB-donor-CU serving the UE may obtain the IAB-MT ULI from the IAB-donor-CU serving the IAB-DU, and send the IAB-MT ULI as an additional ULI of the UE to the core network device.
  • the IAB-donor-CU serving the UE can obtain the IAB-MT ULI from the IAB-DU, and send the IAB-MT ULI as an additional ULI of the UE to the core network device.
  • the first node performs: receiving a first ULI from a third node, and sending the ULI as an additional ULI of the UE to a core network device.
  • the first ULI is of a first subnode in the second node, and the UE accesses the network through the second node.
  • the first node receives a first ULI from a third node, further comprising receiving identification information of the third node corresponding to the first ULI from the third node.
  • the identification information of the second node may be an identification of the second node and/or an identification list of serving cells provided by the second node.
  • the first node is an IAB-donor-CU
  • the third node may be an IAB-donor-CU or an IAB-node
  • identification information of the first ULI and/or the corresponding second node is included in the XnAP message.
  • the identification information of the first ULI and/or the corresponding second node is included in an F1AP message or an RRC message.
  • Method 4 The IAB-DU or the IAB-donor-CU serving the IAB-DU sends the cell identifier list of the IAB-DU associated with the IAB-MT ULI to the AMF through the IAB-donor-CU serving the IAB-MT.
  • the AMF determines the additional ULI of the UE based on the cell identifier list associated with the IAB-MT ULI and the serving cell identifier obtained when the UE accesses.
  • the core network device performs: receiving identification information of a second node associated with a first ULI from a first node or a second node, and determining an additional ULI of a UE according to the information.
  • the UE accesses the network through the second node.
  • the second node is an IAB-node and the first node is an IAB-donor-CU.
  • the identification information of the second node associated with the first ULI is included in the NGAP message.
  • identification information of the second node associated with the first ULI is included in a NAS message.
  • the embodiments of the present disclosure provide the following exemplary embodiments.
  • the first node is taken as the host node of the IAB-DU (IAB-DU’s IAB-donor-CU) as an example for explanation.
  • Step 100 after a partial migration, IAB-MT's source IAB-donor-CU (i.e., IAB-MT's serving IAB-donor-CU) decides to perform IAB-MT switching.
  • IAB-MT's source IAB-donor-CU i.e., IAB-MT's serving IAB-donor-CU
  • step 101 the IAB-MT performs a switch from the IAB-MT's source IAB-donor-CU to the IAB-MT's target IAB-donor-CU.
  • Step 102a IAB-MT's source IAB-donor-CU sends IAB-MT's ULI (User Location Information) to IAB-DU's IAB-donor-CU.
  • IAB-MT's ULI User Location Information
  • Step 102b IAB-MT's target IAB-donor-CU sends IAB-MT's ULI (User Location Information) to IAB-DU's IAB-donor-CU.
  • IAB-MT's ULI User Location Information
  • Step 102a and step 102b may occur before, after or during step 101.
  • Step 102a and step 102b may be applied to the following embodiments (the following embodiments may be applied simultaneously or individually):
  • the ULI of the IAB-MT may serve as an additional ULI of the UE, wherein the UE accesses the network (i.e., connects to the AMF) through the IAB-node where the IAB-MT is located.
  • the ULI of the IAB-MT is included in the XnAP message, that is, the ULI of the IAB-MT is included in the XnAP message sent by the IAB-MT's source IAB-donor-CU to the IAB-DU's IAB-donor-CU; or the IAB-MT is included in the XnAP message sent by the IAB-MT's source IAB-donor-CU to the IAB-DU's IAB-donor-CU;
  • the XnAP message may be a message for notifying IAB-MT of handover;
  • the XnAP message is a non-UE related message
  • the XnAP message also includes a service cell identifier of the IAB-DU, wherein the IAB-DU and the IAB-MT are on the same IAB-node, and the service cell identifier of the IAB-DU is used for the IAB-DU’s IAB-donor-CU (i.e., the IAB-donor-CU serving the UE) to send the ULI of the IAB-MT to the AMF to which the UE is connected according to the cell identifier accessed by the UE.
  • IAB-donor-CU i.e., the IAB-donor-CU serving the UE
  • step 102c the IAB-DU sends the ULI of the IAB-MT to the IAB-DU’s IAB-donor-CU.
  • Step 102c may occur before, after or during step 101.
  • Step 102c may be applied to the following embodiments (the following embodiments may be applied simultaneously or individually):
  • the ULI of the IAB-MT may serve as an additional ULI of the UE, wherein the UE accesses the network (i.e., connects to the AMF) through the IAB-node where the IAB-MT is located.
  • the ULI of the IAB-MT is included in the F1AP message, i.e., the ULI of the IAB-MT is included in the F1AP message sent by the IAB-DU to the IAB-DU's IAB-donor-CU.
  • the F1AP message may be a message for notifying IAB-MT of handover.
  • the F1AP message is a non-UE related message or a UE related message.
  • the F1AP message if the F1AP message is a non-UE-related message, the F1AP message also includes a service cell identifier of the IAB-DU, wherein the IAB-DU and the IAB-MT are on the same IAB-node, and the service cell identifier of the IAB-DU is used for the IAB-DU’s IAB-donor-CU (i.e., the IAB-donor-CU serving the UE) to send the ULI of the IAB-MT to the AMF to which the UE is connected according to the cell identifier accessed by the UE.
  • IAB-donor-CU i.e., the IAB-donor-CU serving the UE
  • the ULI of the IAB-MT is included in messages such as the F1 SETUP REQUEST message and/or the GNB-DU CONFIGURATION UPDATE message.
  • the ULI of the IAB-MT is included in the served cell information IE.
  • the F1AP message may be an initial uplink RRC message transmission (INITIAL UL RRC MESSAGE TRANSFER) message, an RRC message transmission (UL RRC MESSAGE TRANSFER) message, a UE context establishment feedback (UE CONTEXT SETUP RESPONSE) message, a UE context modification feedback (UE CONTEXT MODIFICATION RESPONSE) message, and/or a UE inactivation notification (UE INACTIVITY NOTIFICATION) message and the like.
  • UE CONTEXT SETUP RESPONSE UE context establishment feedback
  • UE CONTEXT MODIFICATION RESPONSE UE context modification feedback
  • UE INACTIVITY NOTIFICATION UE INACTIVITY NOTIFICATION
  • Step 103 the IAB-DU’s IAB-donor-CU receives and saves the IAB-MT ULI, and uses the IAB-MT ULI as an additional ULI for the UE served by the IAB-node.
  • the IAB-DU’s IAB-donor-CU can determine the additional ULI of the UE through the cell identifier (e.g., one or more cell identifiers) received together with the IAB-MT ULI and the cell identifier actually accessed by the UE.
  • the cell identifier e.g., one or more cell identifiers
  • the IAB-DU’s IAB-donor-CU uses the IAB-MT ULI as an additional ULI of the UE.
  • the IAB-DU’s IAB-donor-CU sends the additional ULI of the UE to the AMF.
  • the AMF can provide more accurate services to the UE through the additional ULI.
  • 102a, 102b and 102c are optional, and one of 102a, 102b and 102c may be executed.
  • 102 a , 102 b , and 102 c may be executed before 101 .
  • the embodiments of the present disclosure provide the following exemplary embodiments.
  • the first node is taken as the target host node of the IAB-DU (IAB-DU’s Target IAB-donor-CU) as an example for explanation.
  • step 200 if the IAB-MT ULI is obtained, the IAB-DU's serving IAB-donor-CU saves the IAB-MT ULI.
  • step 201 if the IAB-DU's source IAB-donor-CU (i.e., the IAB-DU's serving IAB-donor-CU) decides to perform DU migration, the IAB-DU's source IAB-donor-CU sends an IAB-MT ULI to the IAB-DU's target IAB-donor-CU.
  • the IAB-DU's source IAB-donor-CU i.e., the IAB-DU's serving IAB-donor-CU
  • the IAB-DU's source IAB-donor-CU sends an IAB-MT ULI to the IAB-DU's target IAB-donor-CU.
  • the IAB-MT ULI is included in the XnAP message, that is, the ULI of the IAB-MT is included in the XnAP message sent by the IAB-DU's source IAB-donor-CU to the IAB-DU's target IAB-donor-CU, and the XnAP message can be an IAB-DU migration request message, an IAB transport migration request message or other XnAP messages.
  • the XnAP message also includes a service cell identifier of the IAB-DU, and the service cell identifier of the IAB-DU is used for the IAB-DU’s target IAB-donor-CU to send the ULI of the IAB-MT to the AMF connected to the UE according to the cell identifier accessed by the UE.
  • Step 201 IAB-DU’s target IAB-donor-CU receives and saves the IAB-MT ULI, and uses the IAB-MT ULI as an additional ULI for the UE served by the IAB-node.
  • the IAB-DU If a UE accesses the core network device (such as AMF) through the IAB-node, the IAB-DU’s target IAB-donor-CU sends the additional ULI of the UE to the AMF.
  • the AMF can provide more accurate services to the UE through the additional ULI.
  • the embodiments of the present disclosure provide the following exemplary embodiments.
  • 301a takes the first node as an IAB-MT as an example, and 301b to 301c take the first node as the host node of the IAB-MT (IAB-MT’s IAB-donor CU) as an example for explanation.
  • Step 300 IAB-MT’s target IAB-donor-CU sends IAB-MT ULI to AMF.
  • Step 301a The IAB-MT sends the cell identifier list of the IAB-DU to the AMF.
  • the IAB-MT and IAB-DU are on the same IAB-node.
  • Step 301b-1 IAB-DU’s IAB-donor-CU sends the cell identifier list of IAB-DU to IAB-MT’s IAB-donor-CU.
  • Step 301b-2 IAB-MT’s IAB-donor-CU sends the cell identifier list of IAB-DU to AMF.
  • AMF receives the information and associates the IAB-MT ULI with the cell identity list. If a UE accesses the core network device (such as AMF) through a cell in the IAB-node, AMF can determine the additional ULI of the UE based on the provided service cell ID and the cell identity list associated with the IAB-MT ULI. AMF can provide more accurate services to the UE through the additional ULI.
  • AMF can provide more accurate services to the UE through the additional ULI.
  • 301a and 301b-1 to 301b-2 are optional, and one of 301a and 301b-1 to 301b-2 may be executed.
  • the methods provided by the embodiments of the present disclosure are introduced from the perspectives of the core network device, the first node, the third node and the second node respectively.
  • the communication device 1 shown in Figure 28 may include a transceiver module 11 and a processing module.
  • the transceiver module may include a sending module and/or a receiving module, the sending module is used to implement a sending function, the receiving module is used to implement a receiving function, and the transceiver module can implement a sending function and/or a receiving function.
  • the communication device 1 can be a core network device, a first node, a third node or a second node, or a device in the core network device, the first node, the third node or the second node, or a device that can be matched and used with the core network device, the first node, the third node or the second node.
  • the transceiver module 11 is configured to receive first indication information sent by a first node or a second node, wherein the first node is a host node of the second node, and the first indication information is used to indicate user location information of the second node.
  • the device further includes a processing module 12 .
  • the processing module 12 is configured to determine, based on the first indication information, that the additional user location information of the terminal device is the user location information of the second node, wherein the network connection is provided for the terminal device through the second node.
  • the transceiver module 11 is further configured to receive second indication information sent by the first node or the second node, wherein the second indication information is used to indicate at least one of the following:
  • the processing module 12 is further configured to determine the association relationship between the user location information of the second node and the cell identifier list under the second node based on the cell identifier list under the second node and the user location information of the second node, wherein the second indication information is used to indicate the cell identifier list under the second node; or to determine the association relationship between the user location information of the second node and the identifier of the second node based on the identifier of the second node and the user location information of the second node, wherein the second indication information is used to indicate the identifier of the second node.
  • the processing module 12 is further configured to determine additional user location information of the terminal device based on the service cell identifier and association relationship of the terminal device; or to determine additional user location information of the terminal device based on the identifier and association relationship of the second node provided by the terminal device.
  • the user location information of the second node is the user location information of the MT of the second node
  • the first node is the host node of the MT of the second node
  • the first node is the host node of the DU of the second node.
  • the transceiver module 11 is further configured to receive an NGAP message sent by the first node, wherein the NGAP message includes the first indication information; or receive a NAS message sent by the second node, wherein the NAS message includes the first indication information.
  • the transceiver module 11 is further configured to receive an NGAP message sent by the first node, wherein the NGAP message includes the second indication information; or receive a NAS message sent by the second node, wherein the NAS message includes the second indication information.
  • the communication device 1 is applied to a first node: the device comprises: a transceiver module 11.
  • the transceiver module 11 is configured to send first indication information to the core network device, wherein the first node is a host node of the second node, and the first indication information is used to indicate user location information of the second node.
  • the transceiver module 11 is further configured to send second indication information to the core network device, wherein the second indication information is used to indicate at least one of the following:
  • the transceiver module 11 is further configured to send an NGAP message to the core network device, wherein the NGAP message includes first indication information.
  • the transceiver module 11 is further configured to send an NGAP message to the core network device, wherein the NGAP message includes second indication information.
  • the user location information of the second node is the user location information of the MT of the second node
  • the first node is the host node of the MT of the second node
  • the first node is the host node of the DU of the second node.
  • the apparatus comprises a processing module 12.
  • the processing module 12 is configured to determine user location information of the second node.
  • the transceiver module 11 is further configured to receive a first message sent by a third node, wherein the first message includes user location information indicating the second node.
  • the processing module 12 is further configured to determine user location information of the second node based on the first message.
  • the third node is a host node of a DU of the second node or a host node of a MT of the second node.
  • the third node is the source host node of the DU of the second node.
  • the first message is at least one of the following:
  • the first message is further used to instruct the MT of the second node to perform handover.
  • the first message is a message related to the terminal device or a message unrelated to the terminal device.
  • the first message when the first message is a message unrelated to the terminal device, the first message also includes a cell identifier list.
  • the processing module 12 is further configured to determine an association between a cell identifier list of the second cell and user location information of the second node, or determine an association between an identifier of the second node and user location information of the second node.
  • the communication device 1 is applied to a third node: the device comprises: a transceiver module 11.
  • the transceiver module 11 is configured to send a first message to the first node, wherein the first message is used to indicate the user location information of the second node, and the first node is a host node of the second node.
  • the third node is a host node of a DU of the second node or a host node of a MT of the second node.
  • the third node is the source host node of the DU of the second node.
  • the first message is at least one of the following:
  • the first message is further used to instruct the MT of the second node to perform handover.
  • the first message is a message related to the terminal device or a message unrelated to the terminal device.
  • the first message when the first message is a message unrelated to the terminal device, the first message also includes a list of cell identifiers under the second node or an identifier of the second node.
  • the first message also includes a list of cell identifiers of the second node or an identifier of the second node.
  • the communication device 1 is applied to a second node: the device comprises: a transceiver module 11.
  • the transceiver module 11 is configured to send first indication information to the core network device, wherein the first indication information is used to indicate the user location information of the second node.
  • the transceiver module 11 is further configured to send second indication information to the core network device, wherein the second indication information is used to indicate a cell identifier list under the second node and/or an identifier of the second node.
  • the transceiver module 11 is further configured to send an NGAP message to the core network device, wherein the NGAP message includes first indication information.
  • the transceiver module 11 is further configured to send an NGAP message to the core network device, wherein the NGAP message includes second indication information.
  • the user location information of the second node is user location information of the MT of the second node.
  • the communication device 1 provided in the above embodiments of the present disclosure achieves the same or similar beneficial effects as the information acquisition methods provided in some of the above embodiments, which will not be described in detail here.
  • the communication device 1000 may be a core network device, a first node, a third node, or a second node, or may be a chip, a chip system, or a processor that supports the core network device, the first node, the third node, or the second node to implement the above method.
  • the communication device 1000 may be used to implement the method described in the above method embodiment, and the details may refer to the description in the above method embodiment.
  • the communication device 1000 may include one or more processors 1001.
  • the processor 1001 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit.
  • the baseband processor may be used to process the communication protocol and the communication data
  • the central processing unit may be used to control the communication device (such as a network side device, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute a computer program, and process the data of the computer program.
  • the communication device 1000 may further include one or more memories 1002, on which a computer program 1004 may be stored, and the memory 1002 executes the computer program 1004, so that the communication device 1000 performs the method described in the above method embodiment.
  • data may also be stored in the memory 1002.
  • the communication device 1000 and the memory 1002 may be provided separately or integrated together.
  • the communication device 1000 may further include a transceiver 1005 and an antenna 1006.
  • the transceiver 1005 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., for implementing a transceiver function.
  • the transceiver 1005 may include a receiver and a transmitter, the receiver may be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function.
  • the communication device 1000 may further include one or more interface circuits 1007.
  • the interface circuit 1007 is used to receive code instructions and transmit them to the processor 1001.
  • the processor 1001 executes the code instructions to enable the communication device 1000 to execute the method described in the above method embodiment.
  • the communication device 1000 is a core network device: the transceiver 1005 is used to execute S111 in Figure 11; S121 in Figure 12; S131a and S132a in Figure 13a; S131b and S132b in Figure 13b; S141a and S142a in Figure 14a; S141b and S142b in Figure 14b; the processor 1001 is used to execute S122 in Figure 12; S133a and S134a in Figure 13a; S133b and S134b in Figure 13b; S143a in Figure 14a; S143b in Figure 14b.
  • the communication device 1000 is a first node: the transceiver 1005 is used to execute S151 in Figure 15; S161 and S162 in Figure 16; S172 in Figure 17; S181 in Figure 18; the processor 1001 is used to execute S171 in Figure 17; S182 in Figure 18; and S191 in Figure 19.
  • the communication device 1000 is a third node: the transceiver 1005 is used to execute S201 in FIG. 20 .
  • the communication device 1000 is a second node: the transceiver 1005 is used to execute S211 in FIG. 21 ; S221 and S222 in FIG. 22 .
  • the processor 1001 may include a transceiver for implementing receiving and sending functions.
  • the transceiver may be a transceiver circuit, an interface, or an interface circuit.
  • the transceiver circuit, interface, or interface circuit for implementing the receiving and sending functions may be separate or integrated.
  • the above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.
  • the processor 1001 may store a computer program 1003, which runs on the processor 1001 and enables the communication device 1000 to perform the method described in the above method embodiment.
  • the computer program 1003 may be fixed in the processor 1001, in which case the processor 1001 may be implemented by hardware.
  • the communication device 1000 may include a circuit that can implement the functions of sending or receiving or communicating in the aforementioned method embodiments.
  • the processor and transceiver described in the present disclosure may be implemented in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc.
  • the processor and transceiver may also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS N-type metal oxide semiconductor
  • PMOS P-type metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the communication device described in the above embodiment may be a core network device, a first node, a third node, or a second node, but the scope of the communication device described in the present disclosure is not limited thereto, and the structure of the communication device may not be limited by FIG. 29.
  • the communication device may be an independent device or may be part of a larger device.
  • the communication device may be:
  • the IC set may also include a storage component for storing data and computer programs;
  • ASIC such as modem
  • FIG. 30 is a structural diagram of a chip provided in an embodiment of the present disclosure.
  • the chip 1100 includes a processor 1101 and an interface 1103.
  • the number of the processor 1101 may be one or more, and the number of the interface 1103 may be multiple.
  • the interface 1103 is used to receive code instructions and transmit them to the processor.
  • the processor 1101 is used to run code instructions to execute the information acquisition method as described in some of the above embodiments.
  • the interface 1103 is used to receive code instructions and transmit them to the processor.
  • the processor 1101 is used to run code instructions to execute the information acquisition method as described in some of the above embodiments.
  • the interface 1103 is used to receive code instructions and transmit them to the processor.
  • the processor 1101 is used to run code instructions to execute the information acquisition method as described in some of the above embodiments.
  • the interface 1103 is used to receive code instructions and transmit them to the processor.
  • the processor 1101 is used to run code instructions to execute the information acquisition method as described in some of the above embodiments.
  • the chip 1100 further includes a memory 1102, and the memory 1102 is used to store necessary computer programs and data.
  • the embodiments of the present disclosure also provide an information acquisition system, which includes the communication device as a core network device, the communication device as a first node, the communication device as a third node and/or the communication device as a second node in the embodiment of FIG. 28 above, or the system includes the communication device as a core network device, the communication device as a first node, the communication device as a third node and/or the communication device as a second node in the embodiment of FIG. 29 above.
  • the present disclosure also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.
  • the present disclosure also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.
  • the computer program product includes one or more computer programs.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer program can 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 can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated.
  • the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.
  • a magnetic medium e.g., a floppy disk, a hard disk, a magnetic tape
  • an optical medium e.g., a high-density digital video disc (DVD)
  • DVD high-density digital video disc
  • SSD solid state disk
  • At least one in the present disclosure may also be described as one or more, and a plurality may be two, three, four or more, which is not limited in the present disclosure.
  • the technical features in the technical feature are distinguished by “first”, “second”, “third”, “A”, “B”, “C” and “D”, etc., and there is no order of precedence or size between the technical features described by the "first”, “second”, “third”, “A”, “B”, “C” and “D”.
  • the corresponding relationships shown in the tables in the present disclosure can be configured or predefined.
  • the values of the information in each table are only examples and can be configured as other values, which are not limited by the present disclosure.
  • the corresponding relationships shown in some rows may not be configured.
  • appropriate deformation adjustments can be made based on the above table, such as splitting, merging, etc.
  • the names of the parameters shown in the titles of the above tables can also use other names that can be understood by the communication device, and the values or representations of the parameters can also be other values or representations that can be understood by the communication device.
  • other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables.
  • the predefined in the present disclosure may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

Landscapes

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

Abstract

本公开实施例公开了信息获取方法及其装置，该方法包括：核心网设备接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。由此，核心网设备可以确定第二节点的用户位置信息。

Description

信息获取方法及装置 技术领域
本公开涉及通信技术领域，尤其涉及一种信息获取方法及装置。
背景技术
在集成接入与回传(integrated accessand backhaul，IAB)的网络架构中，IAB节点(IAB-node)为终端设备提供无线接入和接入业务的无线回传。宿主节点(IAB-donor)向IAB-node提供无线回传功能，并提供终端设备与核心网设备的接口。IAB-node通过无线回传链路连接到IAB-donor，从而使IAB-node所服务的终端设备与核心网设备进行连接。
相关技术中，不支持IAB-node的用户位置信息上报至核心网设备，因此，核心网设备如何确定IAB-node的用户位置信息为亟需解决的问题。
发明内容
本公开实施例提供一种信息获取方法及其装置，可以应用于5G系统，适用于支持集成接入与回传IAB的场景，核心网设备可以确定第二节点的用户位置信息。
第一方面，本公开实施例提供一种信息获取方法，所述方法由核心网设备执行，所述方法包括：核心网设备接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。
在该技术方案中，核心网设备接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。由此，核心网设备可以确定第二节点的用户位置信息。
第二方面，本公开实施例提供另一种信息获取方法，所述方法由第一节点执行，所述方法包括：向核心网设备发送第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。
第三方面，本公开实施例提供又一种信息获取方法，所述方法由第四节点执行，所述方法包括：向第一节点发送第一消息，其中，第一消息包括用于指示第二节点的用户位置信息，第一节点为第二节点的宿主节点。
第四方面，本公开实施例提供又一种信息获取方法，所述方法由第二节点执行，所述方法包括：向核心网设备发送第一指示信息，其中，第一指示信息用于指示第二节点的用户位置信息。
第五方面，本公开实施例提供一种通信装置，该通信装置具有实现上述第一方面所述的方法中核心网设备的部分或全部功能，比如通信装置的功能可具备本公开中的部分或全部实施例中的功能，也可以具备单独实施本公开中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括收发模块和处理模块，所述处理模块被配置为支持通信装置执行上述方法中相应的功能。所述收发模块用于支持通信装置与其他设备之间的通信。所述通信装置还可以包括存储模块，所述存储模块用于与收发模块和处理模块耦合，其保存通信装置必要的计算机程序和数据。
在一种实现方式中，所述通信装置包括：收发模块，被配置为接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。
第六方面，本公开实施例提供另一种通信装置，该通信装置具有实现上述第二方面所述的方法示例中第一节点的部分或全部功能，比如通信装置的功能可具备本公开中的部分或全部实施例中的功能，也可以具备单独实施本公开中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括收发模块和处理模块，处理模块被配置为支持通信装置执行上述方法中相应的功能。收发模块用于支持通信装置与其他设备之间的通信。通信装置还可以包括存储模块，存储模块用于与收发模块和处理模块耦合，其保存通信装置必要的计算机程序和数据。
在一种实现方式中，所述通信装置包括：收发模块，被配置为向核心网设备发送第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。
第七方面，本公开实施例提供又一种通信装置，该通信装置具有实现上述第三方面所述的方法示例中第四节点的部分或全部功能，比如通信装置的功能可具备本公开中的部分或全部实施例中的功能，也可以具备单独实施本公开中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括收发模块和处理模块，处理模块被配置为支持通信装置执行上述方法中相应的功能。收发模块用于支持通信装置与其他设备之间的通信。通信装置还可以包括存储模块，存储模块用于与收发模块和处理模块耦合，其保存通信装置必要的计算机程序和数据。
在一种实现方式中，所述通信装置包括：收发模块，被配置为向第一节点发送第一消息，其中，第一消息包括用于指示第二节点的用户位置信息，第一节点为第二节点的宿主节点。
第八方面，本公开实施例提供又一种通信装置，该通信装置具有实现上述第四方面所述的方法示例中第二节点的部分或全部功能，比如通信装置的功能可具备本公开中的部分或全部实施例中的功能，也可以具备单独实施本公开中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种实现方式中，该通信装置的结构中可包括收发模块和处理模块，处理模块被配置为支持通信装置执行上述方法中相应的功能。收发模块用于支持通信装置与其他设备之间的通信。通信装置还可以包括存储模块，存储模块用于与收发模块和处理模块耦合，其保存通信装置必要的计算机程序和数据。
在一种实现方式中，所述通信装置包括：收发模块，被配置为向核心网设备发送第一指示信息，其中，第一指示信息用于指示第二节点的用户位置信息。
第九方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第一方面所述的方法。
第十方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第二方面所述的方法。
第十一方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第三方面所述的方法。
第十二方面，本公开实施例提供一种通信装置，该通信装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第四方面所述的方法。
第十三方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；处理器执行所述计算机程序，以使该通信装置执行上述第一方面所述的方法。
第十四方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；处理器执行所述计算机程序，以使该通信装置执行上述第二方面所述的方法。
第十五方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；处理器执行所述计算机程序，以使该通信装置执行上述第三方面所述的方法。
第十六方面，本公开实施例提供一种通信装置，该通信装置包括处理器和存储器，该存储器中存储有计算机程序；处理器执行所述计算机程序，以使该通信装置执行上述第四方面所述的方法。
第十七方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行代码指令以使该装置执行上述第一方面所述的方法。
第十八方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行代码指令以使该装置执行上述第二方面所述的方法。
第十九方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行代码指令以使该装置执行上述第三方面所述的方法。
第二十方面，本公开实施例提供一种通信装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行代码指令以使该装置执行上述第四方面所述的方法。
第二十一方面，本公开实施例提供一种信息获取系统，该系统包括第五方面所述的通信装置、第六方面所述的通信装置、第七方面所述的通信装置和/或第八方面所述的通信装置，或者，该系统包括第九方面所述的通信装置、第十方面所述的通信装置、第十一方面所述的通信装置和/或第十二方面所述的通信装置，或者，该系统包括第十三方面所述的通信装置、第十四方面所述的通信装置、第十五方面所述的通信装置和/或第十六方面所述的通信装置，或者，该系统包括第十七方面所述的通信装置、第十八方面所述的通信装置、第十九方面所述的通信装置和/或第二十方面所述的通信装置。
第二十二方面，本公开实施例提供一种计算机可读存储介质，用于储存为上述核心网设备所用的指令，当所述指令被执行时，使所述核心网设备执行上述第一方面所述的方法。
第二十三方面，本公开实施例提供一种可读存储介质，用于储存为上述第一节点所用的指令，当所述指令被执行时，使所述第一节点执行上述第二方面所述的方法。
第二十四方面，本公开实施例提供一种可读存储介质，用于储存为上述第四节点所用的指令，当所述指令被执行时，使所述第四节点执行上述第三方面所述的方法。
第二十五方面，本公开实施例提供一种可读存储介质，用于储存为上述第二节点所用的指令，当所述指令被执行时，使所述第二节点执行上述第四方面所述的方法。
第二十六方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第二十七方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
第二十八方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第三方面所述的方法。
第二十九方面，本公开还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第四方面所述的方法。
第三十方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第三十一方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
第三十二方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第三方面所述的方法。
第三十三方面，本公开提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第四方面所述的方法。
附图说明
为了更清楚地说明本公开实施例或背景技术中的技术方案，下面将对本公开实施例或背景技术中所需要使用的附图进行说明。
图1为本公开实施例提供的通信系统的架构图；
图2为本公开实施例提供的IAB节点的结构图；
图3为本公开实施例提供的一种回传链路、接入链路的示意图；
图4为本公开实施例适用的一示例性的通信系统的架构图；
图5为本公开实施例适用的一示例性的通信系统的架构图；
图6为本公开实施例适用的一示例性的通信系统的架构图；
图7是本公开实施例提供的一种集成接入与回传IAB架构的示意图；
图8是本公开实施例提供的另一种集成接入与回传IAB架构的示意图；
图9是本公开实施例提供的一种IAB-MT迁移的示意图；
图10是本公开实施例提供的另一种IAB-MT迁移的示意图；
图11是本公开实施例提供的一种信息获取方法的流程图；
图12是本公开实施例提供的另一种信息获取方法的流程示意图；
图13a是本公开实施例提供的又一种信息获取方法的流程示意图；
图13b是本公开实施例提供的又一种信息获取方法的流程示意图；
图14a是本公开实施例提供的又一种信息获取方法的流程示意图；
图14b是本公开实施例提供的又一种信息获取方法的流程示意图；
图15是本公开实施例提供的又一种信息获取方法的流程示意图；
图16是本公开实施例提供的又一种信息获取方法的流程示意图；
图17是本公开实施例提供的又一种信息获取方法的流程示意图；
图18是本公开实施例提供的又一种信息获取方法的流程示意图；
图19是本公开实施例提供的又一种信息获取方法的流程示意图；
图20是本公开实施例提供的又一种信息获取方法的流程示意图；
图21是本公开实施例提供的又一种信息获取方法的流程示意图；
图22是本公开实施例提供的又一种信息获取方法的流程示意图；
图23是本公开实施例提供的一种信息获取系统的结构图；
图24是本公开实施例提供的另一种信息获取系统的结构图；
图25是本公开实施例提供的又一种信息获取方法的流程示意图；
图26是本公开实施例提供的又一种信息获取方法的流程示意图；
图27是本公开实施例提供的又一种信息获取方法的流程示意图；
图28为本公开实施例提供的一种通信装置的结构示意图；
图29是本公开实施例提供的另一种通信装置的结构示意图；
图30是本公开实施例提供的一种芯片的结构示意图。
具体实施方式
下面详细描述本公开的实施例，所述实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的元件或具有相同或类似功能的元件。下面通过参考附图描述的实施例是示例性的，旨在用于解释本公开，而不能理解为对本公开的限制。其中，在本公开的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开实施例和所附权利要求书中所使用的单数形式的“一种”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。
应当理解，尽管在本公开实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”及“若”可以被解释成为“在……时”或“当……时”或“响应于确定”。
下面详细描述本公开的实施例，实施例的示例在附图中示出，其中自始至终相同或类似的标号表示相同或类似的要素。下面通过参考附图描述的实施例是示例性的，旨在用于解释本公开，而不能理解为对本公开的限制。
图1示出了一种IAB系统，IAB节点为终端设备提供无线接入和接入业务的无线回传。IAB donor节点(IAB宿主节点)向IAB节点提供无线回传功能，并提供终端设备与核心网设备的接口。IAB节点通过无线回传链路连接到IAB donor节点，从而使IAB节点所服务的终端设备与核心网设备进行连接。
需要说明的是，在如图1所示的网络架构图中，尽管示出了终端设备、无线回传设备及宿主节点，但该网络架构可以并不限于包括终端设备、无线回传设备及宿主节点。例如，还可以包括核心网设备或用于承载虚拟化网络功能的设备等。另外，如图1所示的系统中，尽管示出了一个终端设备、一个无线回传设备及一个宿主节点，但该网络架构并不限制终端设备、无线回传设备及宿主节点的数量，例如，也可以包括多个终端设备、多个无线回传设备及多个宿主节点等。其中，无线回传设备可以是IAB节点。
图2示出了IAB节点的一种结构示意图。NR中的IAB节点可包括移动终端(mobile terminal，MT)与分布式单元(distributed unit，DU)两部分。MT也可以理解为在IAB节点中类似终端的一个组件。DU是相对网络设备的集中单元(centralized unit，CU)功能而言的。因此，也可认为IAB节点包括MT功能和DU功能，为了描述简便，在下文中，将MT功能称为MT或IAB-MT，将DU功能称为DU或IAB-DU。由于MT类似一个普通终端的功能，那么可以理解为MT用于IAB节点与上级节点(父节点)通信。DU用于IAB节点与下级节点(子节点)通信。应理解，父节点可以是基站或者其他IAB节点，子节点可以是终端或者其他IAB节点。MT与父节点通信的链路称为上级回传链路(parent backhaul link)，DU与下级IAB节点通信的链路称为下级回传链路(child backhaul link)，而DU与下属终端通信的链路称为接入链路。IAB节点可通过多级父节点连接至宿主节点。在一些实施例中，下级回传链路也被称为接入链路，其中，上级回传链路包括上级回传上行链路(uplink，UL)以及上级回传下行链路(downlink，DL)，下级回传链路包括下级回传UL和下级回传DL，接入链路包括接入UL和接入DL，如图3所示。
本公开实施例提供的信息获取方法可以应用于包括无线回传设备的各种通信系统，例如NR系统、LTE系统、LTE-A系统、全球微波互联接入(worldwideinteroperability for microwave access，WiMAX)，或无线局域网络(wireless localarea networks，WLAN)等。
示例性的，本公开实施例提供的通信方法可以应用于如图1所示的网络架构。在图1所示的网络架构中，终端设备通过无线的方式与无线回传设备相连，无线回传设备通过无线的方式与宿主节点相连。终端设备与无线回传设备之间以及无线回传设备与宿主节点之间均可以通过授权频谱(licensed spectrum)进行通信，也可以通过非授权频谱(unlicensed spectrum)进行通信，也可以同时通过授权频谱和非授权频谱进行通信，例如，该授权频谱可以为6GHz以下的频谱，在此不作限制。应理解，图1仅是一种示例性说明，并不对无线通信系统中包括的终端设备、无线回传设备的数量进行具体限定。在图1所示的网络架构中，无线回传设备将为其提供回传服务的节点视为唯一的父节点，例如，无线回传设备将宿主节点视为父节点。当无线回传设备接收终端设备的承载上行信息的无线承载后，将无线承载传输至宿主节点后，再由宿主节点将该无线承载中的上行信息发送至移动网关设备(例如5G网络中的用户面功能实体(user port function，UPF))。移动网关设备发送的承载下行信息的无线承载至宿主节点，然后依次经由无线回传设备发送至终端设备。
应理解，本公开实施例中采用IAB节点仅仅出于描述的需要，并不表示本公开实施例的方案仅用于NR的场景，在本公开实施例中，IAB节点可以泛指任何具有无线回传功能的节点或设备，本公开实施中的IAB节点和中继节点的使用应理解具有相同的含义。
作为一种示例，请参见图4，为包括多个终端设备和多个IAB节点的通信系统的一种示例。图4以包括2个终端设备和2个IAB节点为例，其中，这2个终端设备分别为终端设备1和终端设备2，这2个IAB节点分别为IAB节点1和IAB节点2。终端设备1和终端设备2可接入IAB节点2，IAB节点2通过无线方式与IAB节点1连接，IAB节点1通过无线方式与宿主节点连接。应理解，IAB节点1是IAB节点2的父节点，宿主节点是IAB节点1的父节点。IAB节点2通过接入链路(图4以粗线示意)为终端设备1和终端设备2提供无线接入服务。终端设备1和终端设备2发送的无线承载，依次经由IAB节点2和IAB节点1传输至宿主节点，再由宿主节点将该无线承载中的上行信息发送至移动网关设备。相反，移动网关设备可发送用于承载下行信息的无线承载至宿主节点，然后依次经由IAB节点1和IAB节点2，发送至终端设备1和终端设备2。从图4可以看出，任意一个终端设备发送的无线承载依次经过两个IAB节点传输至宿主节点，可以理解为多跳的无线回传场景，可保证网络的覆盖范围。
作为另一种示例，请参见图5，为包括1个终端设备和多个IAB节点的通信系统的一种示例。图5以包括1个终端设备和3个IAB节点为例，这3个IAB节点分别为IAB节点1、IAB节点2和IAB节点3。与图4的不同之处在于，图5中，终端设备可通过两条路径接入宿主节点。其中的一条路径依次经过终端设备、IAB节点2、IAB节点1和宿主节点；另一条路径依次经过终端设备、IAB节点2、IAB节点3、IAB节点1和宿主节点。终端设备通过多条路径接入宿主节点，可以理解为多连接无线回传场景，可保证业务传输的可靠性。那么相较于图4，图5所示的架构可以理解为多跳+多连接的组网场景。
作为另一种示例，请参见图6，为包括多个终端设备和多个IAB节点的通信系统的一种示例。图6以包括2个终端设备和5个IAB节点为例，其中，这2个终端设备分别为终端设备1和终端设备2，这,5个IAB节点分别为IAB节点1～IAB节点5。应理解，图6粗线示意接入链路，细线示意回传链路。其中，终端设备1可经由IAB节点5、IAB节点2和IAB节点1与宿主节点相连。终端设备1也可经由IAB节点4、IAB节点2和IAB节点1与宿主节点相连。或者终端设备1也可经由IAB节点4、IAB节点3和IAB节点1与宿主节点相连。终端设备2可经由IAB节点4、IAB节点3和IAB节点1与宿主节点相连。终端设备2可经由IAB节点4、IAB节点2和IAB节点1与宿主节点相连。
需要说明的是，图4～图6所示的网络结构只是示例，并不对本公开实施例适用的应用场景构成限定。例如，本公开实施例也可以适用于终端设备经过一个IAB节点与宿主节点进行通信的场景，在此不一一举例。
应理解，IAB节点的DU和IAB宿主的CU之间需要建立F1接口，并完成路由和承载映射的配置，以根据配置来进行IAB节点和目标IAB宿主之间的数据传输。本公开实施例对该接口的名称不作限制。且本文中以该接口称为F1接口为例。
F1接口可支持用户面协议(F1-U)和控制面协议(F1-C)，用户面协议包括以下协议层的一个或多个：通用分组无线服务(General Packet Radio Service，GPRS)隧道协议用户面(GPRS tunnelling protocol user plane，GTP-U)协议层，用户数据报协议(user data gram protocol，UDP)协议层、因特网协议(internet protocol，IP)协议层等；控制面协议包括以下协议层中的一个或多个：F1应用协议(F1 application protocol，F1AP)、流控传输协议(stream control transport protocol，SCTP)、IP协议层等。通过F1接口的控制面，IAB节点和IAB宿主之间可以进行执行接口管理、对IAB-DU进行管理，以及执行终端上下文相关的配置等。通过F1接口的用户面，IAB节点和IAB宿主之间可以执行用户面数据的传输、下行传输状态反馈等功能。
在介绍本公开实施例之前，首先对本公开实施例中的部分用语进行简单解释说明，以便于本领域技术人员理解。
1、终端设备，是一种向用户提供语音和/或数据连通性的设备。本公开涉及的终端设备可以为终端设备或终端，或者所述终端设备内部能够实现该终端设备功能的硬件部件。
在本公开实施例中，终端设备可以称为用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等，例如可以包括具有无线连接功能的手持式设备、或连接到无线调制解调器的处理设备。该终端设备可以经无线接入网(radioaccess network，RAN)与核心网设备进行通信，与RAN交换语音和/或数据。一些终端设备的举例为：个人通信业务(personal communication service，PCS)电话、无绳电话、会话发起协议(session initiation protocol，SIP)话机、无线本地环路(wireless local loop， WLL)站、个人数字助理(personal digital assistant，PDA)、条码、射频识别(radio frequencyidentification，RFID)、传感器、卫星导航系统，例如全球定位系统(global positioningsystem，GPS)、北斗定位系统，激光扫描器等信息传感设备等设备。
终端设备还可以可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能头盔、智能首饰等。该终端还可以是虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、未来演进的公用陆地移动通信网络(publicland mobile network，PLMN)中的终端设备、或者车联网(vehicle to everything，V2X)中的车辆设备,客户前置设备(customer premises equipment，CPE)等。
终端设备的功能可以通过终端设备内部的硬件部件来实现，所述硬件部件可以为所述终端设备内部的处理器和/或可编程的芯片。可选的，该芯片可以通过专用集成电路(application-specific integrated circuit，ASIC)实现，或可编程逻辑器件(programmable logic device，PLD)实现。上述PLD可以是复杂程序逻辑器件(complexprogrammable logical device，CPLD)，现场可编程门阵列(field-programmable gatearray，FPGA)，通用阵列逻辑(generic array logic，GAL)，片上系统(system on a chip，SOC)中的任一项或其任意组合。
而如上介绍的各种终端，如果位于车辆上(例如放置在车辆内或安装在车辆内)，都可以认为是车载终端设备，车载终端设备例如也称为车载单元(on-board unit，OBU)。
2、宿主节点(IAB-donor)，也可以称为宿主基站(Donor base station)，是指通过该节点可以接入核心网设备的节点，是通信系统中将终端设备接入到无线网络的设备，宿主节点一般通过有线链路(例如光纤线缆)连接到核心网设备。宿主节点可负责接收核心网设备的数据并转发给无线回传设备，或者接收无线回传设备的数据并转发给核心网设备。宿主节点一般可以通过有线的方式连接到网络。
作为一种示例，宿主节点可以包括无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(basetransceiver station,BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)等，也可以包括演进的LTE系统(LTE-Advanced，LTE-A)中的演进型基站(NodeB或eNB或e-NodeB，evolutional Node B)，或者也可以包括第五代移动通信技术(fifth generation，5G)新无线(new radio，NR)系统中的下一代节点B(nextgeneration node B，gNB)等。作为另一种示例，宿主节点可以包括集中单元(centralizedunit，CU)(本公开中简称为Donor-CU或者gNB-CU)和分布单元(distributed unit，DU)(本公开中简称为Donor-DU或者gNB-DU)。gNB-CU和gNB-DU通过F1接口相连，F1接口又可以进一步包括控制面接口(F1-C)和用户面接口(F1-U)。CU和核心网设备之间通过下一代(nextgeneration，NG)接口相连。其中，gNB-CU或者Donor-CU还可以是以用户面(User plane，UP)(本公开中简称为CU-UP)和控制面(Control plane，CP)(本公开中简称为CU-CP)分离的形态存在，即gNB-CU或者Donor-CU由CU-CP和CU-UP组成。一个gNB-CU可以包括一个gNB-CU-CP和至少一个gNB-CU-UP。或者，一个Donor-CU可以包括一个Donor-CU-CP和至少一个Donor-CU-UP。
该宿主节点的功能可以是由宿主节点内部的硬件部件实现，例如，所述宿主节点内部的处理器和/或可编程的芯片。例如，该芯片可以通过ASIC实现，或PLD实现。上述PLD可以是CPLD、FPGA、GAL、SOC中任一项或其任意组合。
3、核心网设备用于实现移动管理，数据处理，会话管理，策略和计费等功能。不同接入技术的系统中实现核心网设备功能的设备名称可以不同，本公开并不对此进行限定。以5G网络为例，5GC的逻辑网元包括：接入和移动性管理功能(access and mobility managementfunction，AMF)、会话管理功能(session management function，SMF)、用户面功能(user plane function，UPF)、策略控制功能(policy control function，PCF)、统一数据管理(unified data management，UDM)、应用功能(applicationfunction，AF)等。
4、接入和移动性管理功能(access and mobility managementfunction，AMF)，主要进行移动性管理、接入鉴权/授权等功能。此外，移动性管理网元还可以负责在终端与策略控制功能(policy control function，PCF)网元间传递用户策略。
5、用户面功能(user plane function，UPF)，作为和数据网络的接口，UPF完成用户面数据转发、基于会话/流级的计费统计，带宽限制等功能。
此外，为了便于理解本公开实施例，做出以下几点说明。
第一，本公开实施例中，“用于指示”可以包括用于直接指示和用于间接指示。当描述某一信息用于指示A时，可以包括该信息直接指示A或间接指示A，而并不代表该信息中一定携带有A。
将信息所指示的信息称为待指示信息，则具体实现过程中，对待指示信息进行指示的方式有很多种，例如但不限于，可以直接指示待指示信息，如待指示信息本身或者该待指示信息的索引等。也可以通过指示其他信息来间接指示待指示信息，其中该其他信息与待指示信息之间存在关联关系。还可以仅仅指示待指示信息的一部分，而待指示信息的其他部分则是已知的或者提前约定的。例如，还可以借助预先约定(例如协议规定)的各个信息的排列顺序来实现对特定信息的指示，从而在一定程度上降低指示开销。
待指示信息可以作为一个整体一起发送，也可以分成多个子信息分开发送，而且这些子信息的发送周期和/或发送时机可以相同，也可以不同。具体发送方法本公开不进行限定。其中，这些子信息的发送周期和/或发送时机可以是预先定义的，例如根据协议预先定义的。
第二，在本公开中第一、第二以及各种数字编号(例如，“宿主节点1”、“宿主节点2”)仅为描述方便进行的区分，并不用来限制本公开实施例的范围。例如，区分不同的信息等。
第三，本公开实施例列举了多个实施方式以对本公开实施例的技术方案进行清晰地说明。当然，本领域内技术人员可以理解，本公开实施例提供的多个实施例，可以被单独执行，也可以与本公开实施例中其他实施例的方法结合后一起被执行，还可以单独或结合后与其他相关技术中的一些方法一起被执行；本公开实施例并不对此进行限定。
集成接入与回传(Integrated access and backhaul，IAB)支持毫米波基站进行无线接入和回传，在部署密集网络时可有效减少新增光纤部署需求，使NG-RAN(NG无线接入网)中的无线中继成为可能。其中，中继节点称为IAB-node(IAB节点)，支持通过NR进行无线接入和回传。网络侧NR回传的终止节点称为IAB-donor(IAB宿主)，是一个附加了IAB功能的gNB(5G网络的基站)。回传可以通过单跳或多跳进行。
如图7和图8所示，NG-RAN通过IAB-node无线连接到能够服务IAB-node的gNB(称为IAB-donor)来支持IAB。其中，IAB-donor包括一个IAB-donor-CU(central unit，集中单元)和一个或多个IAB-donor-DU(distributed unit，分布式单元)。当gNB-CU-CP(central unit-control plane，控制集中单元)和gNB-CU-UP(central unit-user plane，用户面集中单元)分离时，IAB-donor可能包括一个IAB-donor-CU-CP、多个IAB-donor-CU-UP和多个IAB-donor-DU。其中，IAB-node通过NR Uu接口的终端功能子集(称为IAB-node中的IAB-MT功能)连接上游IAB-node或IAB-donor-DU。IAB-node通过NR Uu接口的网络功能(称为IAB-node的IAB-DU功能)，提供到下游IAB-node和终端设备的无线回传。IAB-node和IAB-donor-CU之间的F1-C业务通过IAB-donor-DU和可选的中间跳IAB-node进行回传。IAB-node和IAB-donor-CU之间的F1-U业务通过IAB-donor-DU和可选的中间跳IAB-node进行回传。
在版本R18IAB课题研究中，支持移动IAB(mobile IAB)的场景，移动IAB研究工作集中于车载移动IAB节点为车载和/或周边终端设备提供5G覆盖或能力增强的场景。
mobile IAB的特点：mobile IAB可以进行一次或多次部分迁移(partial migration)。
IAB-node连接的IAB-donor-CU可能随着IAB-node的移动改变，这样就需要执行IAB-node迁移(migration)过程。迁移过程包括两种，部分迁移(partial migration)(只有IAB-MT迁移，IAB-DU保持在源IAB-donor上)和全部迁移(full migration)(IAB-MT和IAB-DU由源IAB-donor迁移到同一个目标IAB-donor上)。当然，迁移过程还可以包括上述两种以外的其他迁移，例如IAB-DU迁移。
其中，Partial migration是指只有IAB-node上的IAB-MT迁移(也可以称为切换)到一个新的IAB-donor，而IAB-node上的IAB-DU还保持与原来的IAB-donor连接(连接需要通过IAB-MT的IAB-donor-DU，即在IAB-MT的IAB-donor下需要建立相应的传输路径)，而IAB-DU上的终端设备上下文也保存在原来的IAB-donor上。其切换如图9所示，切换前如图9中左边框中所示的，在迁移前，IAB-MT与IAB-DU均连接至IAB-donor-CU1，IAB-donor-CU1就是原来服务IAB-node的donor，在进行一次partial migration后，IAB-donor-CU1可以称为F1 terminating IAB-donor-CU(或者称为IAB-DU的IAB-donor-CU)，此时终端设备的数据会通过F1连接与IAB-donor-CU1之间传输(只是数据路由会经过IAB-donor-DU2)，即终端设备的上下文保存在F1 terminating IAB-donor上，而IAB-MT则已经切换到IAB-donor-CU2上，IAB-MT的数据通过IAB-donor-CU2传输，IAB-donor-CU2称为non-F1 terminating IAB-donor(或者称为IAB-MT的IAB-donor-CU)。
如果移动的mobile IAB node可以经历多次partial migration，在经过一次以上的partial migration后， F1-terminating IAB-donor(或可称为IAB-DU’s IAB-donor-CU)为IAB-donor-CU1，non-F1 terminating IAB-donor为IAB-donor-CU2(或可称为IAB-MT’s IAB-donor-CU)，而随着mobile IAB node的移动，如图10所示，IAB-MT可能切换到一个新的IAB-donor(也可称为IAB-MT’s target IAB-donor-CU)，即IAB-donor-CU3，在切换完成后，IAB-donor-CU2会通知IAB-donor-CU1:IAB-MT已经切换到一个新的IAB-donor-CU即IAB-donor-CU3，如果IAB-donor-CU1决定向IAB-donor-CU3执行IAB transport migration management流程(即再进行一次partial migration)，所有IAB-DU和IAB-donor-CU1之间的流量(traffic)会从IAB-donor-CU2下的路径迁移到IAB-donor-CU3下的路径。
在集成接入与回传(integrated accessand backhaul，IAB)的网络架构中，IAB节点(IAB-node)为终端设备提供无线接入和接入业务的无线回传。宿主节点(IAB-donor)向IAB-node提供无线回传功能，并提供终端设备与核心网设备的接口。IAB-node通过无线回传链路连接到IAB-donor，从而使IAB-node所服务的终端设备与核心网设备进行连接。
如果终端设备通过IAB-node接入网络，相关技术中，不支持终端设备连接的核心网设备获得IAB-node的用户位置信息以辅助终端设备的核心网设备管理终端设备的位置信息，因此，终端设备的核心网设备如何确定IAB-node的用户位置信息为亟需解决的问题。
请参见图11，图11是本公开实施例提供的一种信息获取方法的流程图。需要说明的是，本公开实施例的信息获取方法可由核心网设备执行，或者还可以由核心网设备中的网络功能执行，例如可由AMF执行。如图11所示，该方法可以包括但不限于如下步骤：
S111：接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。
可以理解的是，核心网设备接收到第一节点发送的第一指示信息，第一指示信息用于指示第二节点的用户位置信息。由此，核心网设备可以确定第二节点的用户位置信息。
示例性地，第二节点的用户位置信息，可以为第二节点的驻留的接入网信息，包括但不限E-UTRA(Evolved-UMTS Terrestrial Radio Access)用户位置信息、NR用户位置信息、非3GPP接入网络的信息中的至少一者，如果为3GPP接入网络信息(即E-UTRA用户位置信息或NR用户位置信息)，第二节点的用户位置信息可以为第二节点驻留的小区信息、TAI(Tracking Area Identity)、PSCell(Primary SCG(Secondary Cell Group)Cell)信息、用于标识非公共网络的信息，以及对应的时间信息，例如：第一时间驻留在第一小区、第二时间驻留在第二小区，等等。其中，驻留的小区可以是已经驻留的小区信息，或者将来会驻留的小区信息。
示例性地，第二节点的用户位置信息，还可以包括第二节点的移动速度和/或运动轨迹。
在一些实施例中，核心网设备接收第一节点或第二节点发送的第一指示信息，包括：接收第一节点发送的NGAP消息，其中，NGAP消息中包括第一指示信息；或者接收第二节点发送的NAS消息，其中，NAS消息中包括第一指示信息。本公开实施例中，核心网设备接收第一节点发送的第一指示信息，可以接收第一节点发送的下一代应用协议(NextGeneration Application Protocol，NGAP)消息，其中，NGAP消息中包括第一指示信息。
在一些实施例中，NGAP消息为UE相关的消息，包括但不限于初始UE消息、UE上下文建立反馈消息、UE上下文修改反馈消息、UE上下文释放完成消息、RRC非激活转换报告消息、PDU会话资源释放反馈消息、PDU会话资源修改反馈消息、PDU资源通知消息、PDU会话资源修改指示消息中的至少一个等。
在一些实施例中，NGAP消息中包括终端设备的用户位置信息，终端设备的用户位置信息中包括第一指示信息。
在一些实施例中，NGAP消息中包括终端设备的用户位置信息和第一指示信息。
本公开实施例中，核心网设备接收第二节点发送的第一指示信息，可以接收第二节点发送的非接入层(non-access stratum，NAS)消息，其中，NAS消息中包括第一指示信息。
本公开实施例中，第二节点可以为IAB节点(IAB-node)，第一节点可以为第二节点的宿主节点(IAB-donor)。
在一些实施例中，第二节点的用户位置信息为第二节点的MT的用户位置信息，第一节点为第二节点的MT的宿主节点，或者第一节点为第二节点的DU的宿主节点。
本公开实施例中，第二节点可以包括移动终端(mobiletermination，MT)部分与分布式单元(distributed unit，DU)部分。
其中，第二节点的用户位置信息为第二节点的MT的用户位置信息。
可以理解的是，第二节点可以进行部分迁移或全部迁移，第二节点的MT(IAB-MT)和DU(IAB-DU)可以连接相同的宿主节点，或者还可以分别连接不同的宿主节点。
本公开实施例中，第一节点为第二节点的宿主节点(IAB-donor)，第一节点可以为第二节点的MT的宿主节点，或者还可以为第二节点的DU的宿主节点。
可以理解的是，在第二节点的MT和DU连接相同的宿主节点的情况下，第一节点可以为第二节点的MT和DU的宿主节点，本公开实施例对此不作具体限制。
在一些实施例中，第一节点(IAB-donor)可以包括一个IAB-donor-CU(central unit，集中单元)和一个或多个IAB-donor-DU(distributed unit，分布式单元)。
在一些实施例中，第一节点还可以为IAB-donor-CU。
本公开实施例中，核心网设备接收第一节点或第二节点发送的第一指示信息，可以接收第一节点或第二节点在任一时刻发送的第一指示信息，第一指示信息用于指示第二节点的用户位置信息。
示例性地，核心网设备可以通过非终端设备相关的消息接收第一节点或第二节点发送的第一指示信息，或者核心网设备还可以通过终端设备相关的消息接收第一节点或第二节点在终端设备通过第二节点与核心网设备进行连接的情况下，发送的第一指示信息，等等。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或实施例任意组合。
通过实施本公开实施例，核心网设备接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。由此，核心网设备可以确定第二节点的用户位置信息。
请参见图12，图12是本公开实施例提供的另一种信息获取方法的流程图。需要说明的是，本公开实施例的信息获取方法可由核心网设备执行，或者还可以由核心网设备中的网络功能执行，例如可由AMF执行。如图12所示，该方法可以包括但不限于如下步骤：
S121：接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。
其中，S121的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S122：根据第一指示信息，确定终端设备的额外用户位置信息为第二节点的用户位置信息，其中，通过第二节点为终端设备提供网络连接。
可以理解的是，相关技术中，终端设备可以通过基站与核心网设备连接，基站可以向核心网设备发送终端设备的用户位置信息(user locationinformation，ULI)，核心网设备可以根据用户位置信息决定是否允许终端设备在该位置执行特定操作，为终端设备提供服务。其中，ULI例如但不限于是小区标识(Cell ID)、跟踪区标识(tracking areaidentity，TAI)。而对于通过移动(mobile)IAB接入的终端设备，终端设备通过IAB-node与核心网设备连接，考虑到IAB-node可移动，核心网设备在为终端设备提供服务时，需要考虑IAB-node的用户位置信息。
基于此，核心网设备在确定通过第二节点为终端设备提供网络连接的情况下，可以根据第一指示信息，确定终端设备的额外用户位置信息为第二节点的用户位置信息。由此，核心网设备可以考虑第二节点的用户位置信息作为该终端设备的额外用户位置信息，以为该终端设备提供精确的服务，提高服务质量。
在一些实施例中，核心网设备确定通过第二节点为终端设备提供网络连接，可以在接收到第一节点或第二节点在终端设备通过第二节点与核心网设备进行连接的情况下，发送的第一指示信息的情况下，确定核心网设备通过第二节点为终端设备提供网络连接。
需要说明的是，第一节点、第二节点、第二节点的用户位置信息以及第一指示信息的相关描述，可以参见上述实施例中的相关描述，此处不再赘述。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或实施例任意组合。
需要说明的是，本公开实施例中，S121至S122可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S111一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，核心网设备接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息；根据第一指示信息，确定终端设备的额外用户位置信息为第二节点的用户位置信息，其中，通过第二节点为终端设备提供网络连接。由此，核心网设备可以根据该终端设备的用户位置信息和额外用户位置信息，为该终端设备提供精确的服务，以提高服务质量。
请参见图13a，图13a是本公开实施例提供的又一种信息获取方法的流程图。需要说明的是，本公开实施例的信息获取方法可由核心网设备执行，或者还可以由核心网设备中的网络功能执行，例如可由AMF执行。如图13a所示，该方法可以包括但不限于如下步骤：
S131a：接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。
其中，S131a的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S132a：接收第一节点或第二节点发送的第二指示信息，其中，第二指示信息用于指示第二节点下的小区标识列表。
S133a：根据第二节点下的小区标识列表以及第二节点的用户位置信息，确定第二节点的用户位置信息与第二节点下的小区标识列表的关联关系。
S134a：根据终端设备的服务小区标识和关联关系，确定终端设备的额外用户位置信息。
本公开实施例中，核心网设备接收第一节点或第二节点发送的第二指示信息，第二指示信息指示第二节点下的小区标识列表，由此，核心网设备接收到第二指示信息后，可以确定第二节点下的小区标识列表。
在一些实施例中，核心网设备接收第一节点或第二节点发送的第二指示信息，包括：接收第一节点发送的NGAP消息，其中，NGAP消息中包括第二指示信息：或者接收第二节点发送的NAS消息，其中，NAS消息中包括第二指示信息。
本公开实施例中，核心网设备接收第一节点发送的第二指示信息，可以接收第一节点发送的NGAP消息，其中，NGAP消息中包括第二指示信息。
本公开实施例中，核心网设备接收第二节点发送的第二指示信息，可以接收第二节点发送的NAS消息，其中，NAS消息中包括第二指示信息。
本公开实施例中，核心网设备接收到第一节点或第二节点发送的第二指示信息，可以根据第二指示信息中的第二节点下的小区标识列表以及第二节点的用户位置信息，确定第二节点的用户位置信息与第二节点下的小区标识列表的关联关系。
本公开实施例中，核心网设备可以根据终端设备的服务小区标识和关联关系，确定终端设备的额外用户位置信息。由此，核心网设备可以考虑第二节点的用户位置信息作为该终端设备的额外用户位置信息，为该终端设备提供精确的服务，以提高服务质量。
其中，核心网设备确定第二节点的用户位置信息与第二节点下的小区标识列表的关联关系，在终端设备的服务小区标识在第二节点下的小区标识列表中的情况下，可以确定终端设备的额外用户位置信息为第二节点的用户位置信息。由此，核心网设备可以考虑第二节点的用户位置信息作为该终端设备的额外用户位置信息，以为该终端设备提供精确的服务，提高服务质量。
需要说明的是，第一节点、第二节点、第二节点的用户位置信息以及第一指示信息的相关描述，可以参见上述实施例中的相关描述，此处不再赘述。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或实施例任意组合。
需要说明的是，本公开实施例中，S131至S134可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S111一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，核心网设备接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息；接收第一节点或第二节点发送的第二指示信息，其中，第二指示信息用于指示第二节点下的小区标识列表；根据第二节点下的小区标识列表以及第二节点的用户位置信息，确定第二节点的用户位置信息与小区标识列表的关联关系，根据终端设备的服务小区标识和关联关系，确定终端设备的额外用户位置信息。由此，核心网设备可以考虑第二节点的用户位置信息作为该终端设备的额外用户位置信息，以为该终端设备提供精确的服务，提高服务质量。
请参见图13b，图13b是本公开实施例提供的又一种信息获取方法的流程图。需要说明的是，本公开实施例的信息获取方法可由核心网设备执行，或者还可以由核心网设备中的网络功能执行，例如可由AMF执行。如图13b所示，该方法可以包括但不限于如下步骤：
S131b：接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。
其中，S131b的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S132b：接收第一节点或第二节点发送的第二指示信息，其中，第二指示信息用于指示第二节点的标识。
示例地，第二节点的标识用于标识第二节点或第二节点上的MT，第二节点的标识可以是AMF UE NGAP ID、RAN UE NGAP ID、UE XnAP ID、F1AP UE ID、或GPSI(Generic Public Subscription Identifier，通用公共用户标识)等。
S133b：根据第二节点的标识以及第二节点的用户位置信息，确定第二节点的用户位置信息与第二节点的标识的关联关系。
S134b：根据终端设备提供的第二节点标识和关联关系，确定终端设备的额外用户位置信息。
本公开实施例中，核心网设备接收第一节点或第二节点发送的第二指示信息，第二指示信息指示第二节点的标识，由此，核心网设备接收到第二指示信息后，可以确定第二节点的标识。
在一些实施例中，核心网设备接收第一节点或第二节点发送的第二指示信息，包括：接收第一节点发送的NGAP消息，其中，NGAP消息中包括第二指示信息：或者接收第二节点发送的NAS消息，其中，NAS消息中包括第二指示信息。
本公开实施例中，核心网设备接收第一节点发送的第二指示信息，可以接收第一节点发送的NGAP消息，其中，NGAP消息中包括第二指示信息。
本公开实施例中，核心网设备接收第二节点发送的第二指示信息，可以接收第二节点发送的NAS消息，其中，NAS消息中包括第二指示信息。
本公开实施例中，核心网设备接收到第一节点或第二节点发送的第二指示信息，可以根据第二指示信息中的第二节点的标识以及第二节点的用户位置信息，确定第二节点的用户位置信息与第二节点的标识的关联关系。
本公开实施例中，核心网设备可以根据终端设备提供的第二节点的标识和关联关系，确定终端设备的额外用户位置信息。由此，核心网设备可以考虑第二节点的用户位置信息作为该终端设备的额外用户位置信息，为该终端设备提供精确的服务，以提高服务质量。
其中，核心网设备确定第二节点的用户位置信息与第二节点的标识的关联关系，在终端设备提供第二节点的标识的情况下，可以确定终端设备的额外用户位置信息为第二节点的用户位置信息。由此，核心网设备可以考虑第二节点的用户位置信息作为该终端设备的额外用户位置信息，以为该终端设备提供精确的服务，提高服务质量。
需要说明的是，第一节点、第二节点、第二节点的用户位置信息以及第一指示信息的相关描述，可以参见上述实施例中的相关描述，此处不再赘述。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或实施例任意组合。
需要说明的是，本公开实施例中，S131至S134可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S111一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，核心网设备接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息；接收第一节点或第二节点发送的第二指示信息，其中，第二指示信息用于指示第二节点的标识；根据第二节点的标识以及第二节点的用户位置信息，确定第二节点的用户位置信息与第二节点的标识的关联关系；根据终端设备提供的第二节点的标识和关联关系，确定终端设备的额外用户位置信息。由此，核心网设备可以考虑第二节点的用户位置信息作为该终端设备的额外用户位置信息，以为该终端设备提供精确的服务，提高服务质量。
请参见图14a，图14a是本公开实施例提供的又一种信息获取方法的流程图。需要说明的是，本公开实施例的信息获取方法可由核心网设备执行，或者还可以由核心网设备中的网络功能执行，例如可由AMF执行。如图14a所示，该方法可以包括但不限于如下步骤：
S141a：接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。
其中，S141a的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S142a：接收第一节点或第二节点发送的第二指示信息，其中，第二指示信息用于指示第二节点下的小区标识列表与第二节点的用户位置信息的关联关系。
S143a：根据终端设备的服务小区标识和关联关系，确定终端设备的额外用户位置信息。
本公开实施例中，核心网设备接收第一节点或第二节点发送的第二指示信息，第二指示信息指示第二节点下的小区标识列表与第二节点的用户位置信息的关联关系，由此，核心网设备接收到第二指示信息后，可以确定第二节点下的小区标识列表与第二节点的用户位置信息的关联关系。
本公开实施例中，核心网设备可以根据终端设备的服务小区标识和关联关系，确定终端设备的额外用户位置信息。由此，核心网设备可以考虑第二节点的用户位置信息作为该终端设备的额外用户位置信息，为该终端设备提供精确的服务，以提高服务质量。
其中，核心网设备确定第二节点的用户位置信息与第二节点下的小区标识列表的关联关系，在终端设备的服务小区标识在第二节点下的小区标识列表中的情况下，可以确定终端设备的额外用户位置信息为第二节点的用户位置信息。由此，核心网设备可以考虑第二节点的用户位置信息作为该终端设备的额外用户位置信息，以为该终端设备提供精确的服务，提高服务质量。
在一些实施例中，核心网设备接收第一节点或第二节点发送的第二指示信息，包括：接收第一节点发送的NGAP消息，其中，NGAP消息中包括第二指示信息：或者接收第二节点发送的NAS消息，其中，NAS消息中包括第二指示信息。
本公开实施例中，核心网设备接收第一节点发送的第二指示信息，可以接收第一节点发送的NGAP消息，其中，NGAP消息中包括第二指示信息。
本公开实施例中，核心网设备接收第二节点发送的第二指示信息，可以接收第二节点发送的NAS消息，其中，NAS消息中包括第二指示信息。
需要说明的是，第一节点、第二节点、第二节点的用户位置信息以及第一指示信息的相关描述，可以参见上述实施例中的相关描述，此处不再赘述。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或实施例任意组合。
需要说明的是，本公开实施例中，S141至S143可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S111一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，核心网设备接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息；接收第一节点或第二节点发送的第二指示信息，其中，第二指示信息用于指示第二节点下的小区标识列表与第二节点的用户位置信息的关联关系；根据终端设备的服务小区标识和关联关系，确定终端设备的额外用户位置信息。由此，核心网设备可以考虑第二节点的用户位置信息作为该终端设备的额外用户位置信息，以为该终端设备提供精确的服务，提高服务质量。
请参见图14b，图14b是本公开实施例提供的又一种信息获取方法的流程图。需要说明的是，本公开实施例的信息获取方法可由核心网设备执行，或者还可以由核心网设备中的网络功能执行，例如可由AMF执行。如图14b所示，该方法可以包括但不限于如下步骤：
S141b：接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。
其中，S141b的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S142b：接收第一节点或第二节点发送的第二指示信息，其中，第二指示信息用于指示第二节点的标识与第二节点的用户位置信息的关联关系。
S143b：根据终端设备提供的第二节点的标识和关联关系，确定终端设备的额外用户位置信息。
本公开实施例中，核心网设备接收第一节点或第二节点发送的第二指示信息，第二指示信息指示第二节点的标识与第二节点的用户位置信息的关联关系，由此，核心网设备接收到第二指示信息后，可以确定第二节点的标识和第二节点的用户位置信息的关联关系。
本公开实施例中，核心网设备可以根据提供的第二节点的标识和关联关系，确定终端设备的额外用户位置信息。由此，核心网设备可以考虑第二节点的用户位置信息作为该终端设备的额外用户位置信息，为该终端设备提供精确的服务，以提高服务质量。
其中，核心网设备确定第二节点的用户位置信息与第二节点的标识的关联关系，在终端设备提供第二节点的标识的情况下，可以确定终端设备的额外用户位置信息为第二节点的用户位置信息。由此，核心网设备可以考虑第二节点的用户位置信息作为该终端设备的额外用户位置信息，以为该终端设备提供精确的服务，提高服务质量。
示例地，第二节点的标识用于标识第二节点或第二节点上的MT，第二节点的标识可以是AMF UE NGAP ID、RAN UE NGAP ID、UE XnAP ID、F1AP UE ID、或GPSI(Generic Public Subscription Identifier，通用公共用户标识)等。
在一些实施例中，核心网设备接收第一节点或第二节点发送的第二指示信息，包括：接收第一节点发送的NGAP消息，其中，NGAP消息中包括第二指示信息：或者接收第二节点发送的NAS消息，其中，NAS消息中包括第二指示信息。
本公开实施例中，核心网设备接收第一节点发送的第二指示信息，可以接收第一节点发送的NGAP消息，其中，NGAP消息中包括第二指示信息。
本公开实施例中，核心网设备接收第二节点发送的第二指示信息，可以接收第二节点发送的NAS消息，其中，NAS消息中包括第二指示信息。
需要说明的是，第一节点、第二节点、第二节点的用户位置信息以及第一指示信息的相关描述，可以参见上述实施例中的相关描述，此处不再赘述。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或实施例任意组合。
需要说明的是，本公开实施例中，S141至S143可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S111一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，核心网设备接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息；接收第一节点或第二节点发送的第二指示信息，其中，第二指示信息用于指示第二节点的标识与第二节点的用户位置信息的关联关系；根据终端设备提供的第二节点的标识和关联关系，确定终端设备的额外用户位置信息。由此，核心网设备可以考虑第二节点的用户位置信息作为该终端设备的额外用户位置信息，以为该终端设备提供精确的服务，提高服务质量。
请参见图15，图15是本公开实施例提供的又一种信息获取方法的流程图。需要说明的是，本公开实施例的信息获取方法可由第一节点执行。如图15所示，该方法可以包括但不限于如下步骤：
S151：向核心网设备发送第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。
本公开实施例中，第一节点可以向核心网设备发送第一指示信息，第一指示信息用于指示第二节点的用户位置信息。由此，支持终端设备连接的核心网设备获得第二节点的用户位置信息，其中终端设备通过第二节点接入网络。
示例性地，第二节点的用户位置信息，可以为第二节点的驻留的接入网信息，包括但不限E-UTRA(Evolved-UMTS Terrestrial Radio Access)用户位置信息、NR用户位置信息、非3GPP网络的接入信息，如果为3GPP接入网络信息(即E-UTRA用户位置信息或NR用户位置信息)，第二节点的用户位置信息可以为第二节点驻留的小区信息、TAI(Tracking Area Identity)、PSCell(Primary SCG(Secondary Cell Group)Cell)信息、用于标识非公共网络的信息，以及对应的时间信息，例如：第一时间驻留在第一小区、第二时间驻留在第二小区，等等。其中，驻留的小区可以是已经驻留的小区信息，或者将来会驻留的小区信息。
示例性地，第二节点的用户位置信息，还可以包括第二节点的移动速度和/或运动轨迹。
在一些实施例中，第一节点向核心网设备发送第一指示信息，包括：向核心网设备发送NGAP消息，其中，NGAP消息中包括第一指示信息。
在一些实施例中，NGAP消息为UE相关的消息，包括但不限于初始UE消息、UE上下文建立反馈消息、UE上下文修改反馈消息、UE上下文释放完成消息、RRC非激活转换报告消息、PDU会话资源释放反馈消息、PDU会话资源修改反馈消息、PDU资源通知消息、PDU会话资源修改指示消息中的至少一个等。
在一些实施例中，NGAP消息中包括终端设备的用户位置信息，终端设备的用户位置信息中包括第一指示信息。
在一些实施例中，NGAP消息中包括终端设备的用户位置信息和第一指示信息。
本公开实施例中，第一节点向核心网设备发送第一指示信息，可以向核心网设备发送NGAP消息，其中，NGAP消息中包括第一指示信息。
在一些实施例中，第二节点的用户位置信息为第二节点的MT的用户位置信息，第一节点为第二节点的MT的宿主节点，或者第一节点为第二节点的DU的宿主节点。
本公开实施例中，第二节点可以包括移动终端(mobile termination，MT)部分与分布式单元(distributed unit，DU)部分。
其中，第二节点的用户位置信息为第二节点的MT的用户位置信息。
可以理解的是，第二节点可以进行部分迁移或全部迁移，第二节点的MT(IAB-MT)和DU(IAB-DU)可以连接相同的宿主节点，或者还可以分别连接不同的宿主节点。
本公开实施例中，第一节点为第二节点的宿主节点(IAB-donor)，第一节点可以为第二节点的MT的宿主节点，或者还可以为第二节点的DU的宿主节点。
可以理解的是，在第二节点的MT和DU连接相同的宿主节点的情况下，第一节点可以为第二节点的MT和DU的宿主节点，本公开实施例对此不作具体限制。
在一些实施例中，第一节点(IAB-donor)可以包括一个IAB-donor-CU(central unit，集中单元)和一个或多个IAB-donor-DU(distributed unit，分布式单元)。
在一些实施例中，第一节点还可以为IAB-donor-CU。
本公开实施例中，第一节点向核心网设备发送第一指示信息，可以在任一时刻向核心网设备发送第一指示信息，第一指示信息用于指示第二节点的用户位置信息。
示例性地，第一节点可以在没有终端设备通过第二节点与核心网设备连接的情况下，向核心网设备发送第一指示信息，或者第一节点还可以在终端设备通过第二节点与核心网设备进行连接的情况下，向核心网设备发送第一指示信息，等等。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或实施例任意组合。
通过实施本公开实施例，第一节点向核心网设备发送第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。由此，支持终端设备连接的核心网设备获得第二节点的用户位置信息，其中终端设备通过第二节点接入网络。
请参见图16，图16是本公开实施例提供的又一种信息获取方法的流程图。需要说明的是，本公开实施例的信息获取方法可由第一节点执行。如图16所示，该方法可以包括但不限于如下步骤：
S161：向核心网设备发送第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。
其中，S161的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
S162：向核心网设备发送第二指示信息。
其中，第二指示信息用于指示以下至少一项：
第二节点下的小区标识列表；
第二节点的标识；
第二节点下的小区标识列表与第二节点的用户位置信息的关联关系；
第二节点的标识与第二节点的用户位置信息的关联关系。
本公开实施例中，第一节点可以向核心网设备发送第二指示信息，第二指示信息用于指示第二节点下的小区标识列表。由此，支持第一节点将第二节点下的小区标识列表上报至核心网设备。
本公开实施例中，第一节点可以向核心网设备发送第二指示信息，第二指示信息用于指示第二节点的标识。由此，支持第一节点将第二节点的标识上报至核心网设备。
本公开实施例中，第一节点可以向核心网设备发送第二指示信息，第二指示信息用于指示第二节点下的小区标识列表与第二节点的用户位置信息的关联关系。由此，第一节点可以支持将第二节点下的小区标识列表与第二节点的用户位置信息的关联关系上报至核心网设备。
本公开实施例中，第一节点可以向核心网设备发送第二指示信息，第二指示信息用于指示第二节点的标识与第二节点的用户位置信息的关联关系。由此，第一节点可以支持将第二节点的标识与第二节点的用户位置信息的关联关系上报至核心网设备。
示例地，第二节点的标识用于标识第二节点或第二节点上的MT，第二节点的标识可以是AMF UE NGAP ID、RAN UE NGAP ID、UE XnAP ID、F1AP UE ID、或GPSI(Generic Public Subscription Identifier，通用公共用户标识)等。
在一些实施例中，第一节点向核心网设备发送第二指示信息，包括：向核心网设备发送NGAP消息，其中，NGAP消息中包括第二指示信息。
本公开实施例中，第一节点向核心网设备发送第二指示信息，可以向核心网设备发送NGAP消息，其中，NGAP消息中包括第二指示信息。
需要说明的是，第一节点、第二节点、第二节点的用户位置信息以及第一指示信息的相关描述，可以参见上述实施例中的相关描述，此处不再赘述。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或实施例任意组合。
需要说明的是，本公开实施例中，S161至S162可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S151一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，第一节点向核心网设备发送第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息；向核心网设备发送第二指示信息。由此，支持第一节点将第二节点的用户位置信息，以及第二节点下的小区标识列表、第二节点的标识、第二节点下的小区标识列表与第二节点的用户位置信息的关联关系、第二节点的标识与第二节点的用户位置信息的关联关系中的至少一者上报至核心网设备。
请参见图17，图17是本公开实施例提供的又一种信息获取方法的流程图。需要说明的是，本公开实施例的信息获取方法可由第一节点执行。如图17所示，该方法可以包括但不限于如下步骤：
S171：确定第二节点的用户位置信息。
本公开实施例中，第一节点可以确定第二节点的用户位置信息。
其中，第一节点可以自行确定第二节点的用户位置信息，由此，确定第二节点的用户位置信息，或者还可以接收第二节点发送的第二节点的用户位置信息，由此，确定第二节点的用户位置信息，或者还可以接收其他节点发送的第二节点的用户位置信息，由此，确定第二节点的用户位置信息，等等，本公开实施例对此不作具体限制。
S172：向核心网设备发送第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。
其中，S172的相关描述可以参见上述实施例中的相关描述，此处不再赘述。
需要说明的是，第一节点、第二节点、第二节点的用户位置信息以及第一指示信息的相关描述，可以参见上述实施例中的相关描述，此处不再赘述。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或实施例任意组合。
需要说明的是，本公开实施例中，S171至S172可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S151和/或S161至S162一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，第一节点向核心网设备发送第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。由此，支持终端设备连接的核心网设备获得第二节点的用户位置信息，其中终端设备通过第二节点接入网络。
请参见图18，图18是本公开实施例提供的又一种信息获取方法的流程图。需要说明的是，本公开实施例的信息获取方法可由第一节点执行。如图18所示，该方法可以包括但不限于如下步骤：
S181：接收第三节点发送的第一消息，其中，第一消息用于指示第二节点的用户位置信息。
S182：根据第一消息，确定第二节点的用户位置信息。
本公开实施例中，第一节点可以接收第三节点发送的第一消息，其中，第一消息用于指示第二节点的用户位置信息。由此，第一节点可以根据第一消息中的用于指示第二节点的用户位置信息，确定第二节点的用户位置信息。
需要说明的是，第一消息可以用于指示第二节点的用户位置信息，但是第一消息不限于用于其他目的，例如还可以用于指示其他信息，本公开实施例对此不作具体限制。
在一些实施例中，在第一节点为第二节点的DU的宿主节点的情况下，第三节点为第二节点的DU。
本公开实施例中，在第一节点为第二节点的DU的宿主节点的情况下，第三节点为第二节点的DU。
其中，第二节点的DU的宿主节点接收第二节点的DU发送的第一消息，其中，第一消息用于指示第二节点的用户位置信息，第二节点的DU的宿主节点可以根据第一消息中的用于指示第二节点的用户位置信息，确定第二节点的用户位置信息。
在一些实施例中，在第一节点为第二节点的DU的宿主节点的情况下，第三节点为第二节点的MT的宿主节点。
本公开实施例中，在第一节点为第二节点的DU的宿主节点的情况下，第三节点为第二节点的MT的宿主节点。
其中，第二节点的DU的宿主节点接收第二节点的MT的宿主节点发送的第一消息，其中，第一消息包括用于指示第二节点的用户位置信息，第二节点的DU的宿主节点可以根据第一消息中的第二节点的用户位置信息，确定第二节点的用户位置信息。
可以理解的是，第二节点的DU的宿主节点，在第二节点的DU发生迁移，第二节点的DU由源宿主节点迁移至目标宿主节点的情况下，第二节点的DU的宿主节点可以为第二节点的DU的源宿主节点或第二节点的DU的目标宿主节点。
在一些实施例中，在第一节点为第二节点的DU发生迁移后的目标宿主节点的情况下，第三节点为第二节点的DU的源宿主节点。
本公开实施例中，在第一节点为第二节点的DU发生迁移后的目标宿主节点的情况下，第三节点为第二节点的DU的源宿主节点。
其中，第二节点的DU的目标宿主节点接收第二节点的DU的源宿主节点发送的第一消息，其中，第一消息包括用于指示第二节点的用户位置信息，第二节点的DU的目标宿主节点可以根据第一消息中的用于指示第二节点的用户位置信息，确定第二节点的用户位置信息。
在本公开实施例中，第一节点确定第二节点的用户位置信息，包括：保存第二节点的用户位置信息，并确定第二节点的用户位置信息与第二节点的关联关系，如果终端设备通过第二节点接入核心网设备，第一节点将第二节点的用户位置信息通过与终端设备相关的消息发送给核心网设备。
在一些实施例中，第一消息为以下至少一项：
F1AP消息；
RRC消息；
XnAP消息。
本公开实施例中，第一消息可以为F1应用协议(F1 application protocol，F1AP)消息。
本公开实施例中，第一消息可以为无线资源控制(radioresource control，RRC)消息。
本公开实施例中，第一消息可以为Xn接口应用协议(Xn application protocol，XnAP)消息。
在一些实施例中，第一消息为用于指示第二节点的MT进行切换的消息。
本公开实施例中，第一消息可以为用于指示第二节点的MT进行切换的消息。例如，第一消息可以是用于通知IAB-MT切换的消息。
在一些实施例中，第一消息为与终端设备相关的消息或与终端设备无关的消息。
本公开实施例中，第一消息可以为与终端设备相关的消息，或者第一消息还可以为与终端设备无关的消息。
在一些实施例中，在第一消息为与终端设备无关的消息的情况下，第一消息中还包括小区标识列表和/或第二节点的标识。
本公开实施例中，在第一消息为与终端设备无关的消息的情况下，第一消息中还可包括小区标识列表和/或第二节点的标识。
在一些实施例中，在第一消息为F1AP消息的情况下，第一消息用于指示第二节点的用户位置信息，第二节点的用户位置信息可以被包括在F1建立请求(F1 SETUP REQUEST)消息、和/或GNB-DU配置更新(GNB-DU CONFIGURATION UPDATE)消息等消息中。
在一些实施例中，在第一消息为F1AP消息的情况下，第一消息用于指示第二节点的用户位置信息，第二节点的用户位置信息可以被包括在服务小区信息IE(served cell information IE)中。
在一些实施例中，在第一消息为F1AP消息，F1AP消息为与终端设备有关的消息的情况下，F1AP消息可以为以下至少一项：
初始上行链路RRC消息传输(INITIAL UL RRC MESSAGE TRANSFER)消息；
RRC消息传输(UL RRC MESSAGE TRANSFER)消息；
终端设备上下文建立反馈(UE CONTEXT SETUP RESPONSE)消息；
终端设备上下文修改反馈(UE CONTEXT MODIFICATION RESPONSE)消息；
终端设备非激活通知(UE INACTIVITY NOTIFICATION)消息。
在一些实施例中，在第一消息为XnAP的情况下，第一消息用于指示第二节点的用户位置信息，第一消息可以是IAB-MT迁移完成指示消息。
需要说明的是，第一节点、第二节点以及第二节点的用户位置信息的相关描述，可以参见上述实施例中的相关描述，此处不再赘述。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或实施例任意组合。
需要说明的是，本公开实施例中，S181至S182可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S151和/或S161至S162和/或S171至S172一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，第一节点接收第三节点发送的第一消息，其中，第一消息用于指示第二节点的用户位置信息；根据第一消息，确定第二节点的用户位置信息。由此，第一节点可以确定第二节点的用户位置信息。
请参见图19，图19是本公开实施例提供的又一种信息获取方法的流程图。需要说明的是，本公开实施例的信息获取方法可由第一节点执行。如图19所示，该方法可以包括但不限于如下步骤：
S191：确定第二小区下的小区标识列表与第二节点的用户位置信息的关联关系，或者确定第二节点的标识与第二节点的用户位置信息的关联关系。
本公开实施例中，第一节点可以自行确定第二小区下的小区标识列表，以及第二节点的用户位置信息，进而建立小区标识列表与第二节点的用户位置信息的关联关系，由此，确定第二小区下的小区标识列表与第二节点的用户位置信息的关联关系。或者第一节点还可以接收其他节点发送的小区标识列表与第二节点的用户位置信息的关联关系，由此，确定第二小区下的小区标识列表与第二节点的用户位置信息的关联关系。
本公开实施例中，第一节点可以自行确定第二节点的标识，以及第二节点的用户位置信息，进而建立第二节点的标识与第二节点的用户位置信息的关联关系，由此，确定第二节点的标识与第二节点的用户位置信息的关联关系。或者第一节点还可以接收其他节点发送的第二节点的标识与第二节点的用户位置信息的关联关系，由此，确定第二节点的标识与第二节点的用户位置信息的关联关系。
需要说明的是，第一节点、第二节点以及第二节点的用户位置信息的相关描述，可以参见上述实施例中的相关描述，此处不再赘述。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或实施例任意组合。
需要说明的是，本公开实施例中，S191可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S151和/或S161至S162和/或S171至S172和/或S181至S182一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，第一节点确定第二小区下的小区标识列表与第二节点的用户位置信息的关联关系。由此，第一节点可以确定第二小区下的小区标识列表与第二节点的用户位置信息的关联关系。
请参见图20，图20是本公开实施例提供的又一种信息获取方法的流程图。需要说明的是，本公开实施例的信息获取方法可由第三节点执行。如图20所示，该方法可以包括但不限于如下步骤：
S201：向第一节点发送第一消息，其中，第一消息用于指示第二节点的用户位置信息，第一节点为第二节点的宿主节点。
本公开实施例中，第三节点可以向第一节点发送第一消息，其中，第一消息用于指示第二节点的用户位置信息，由此，支持第三节点向第一节点发送第二节点的用户位置信息。
需要说明的是，第一消息可以用于指示第二节点的用户位置信息，但是第一消息不限于用于其他目的，例如还可以用于指示其他信息，本公开实施例对此不作具体限制。
在一些实施例中，在第一节点为第二节点的DU的宿主节点的情况下，第三节点为第二节点的DU。
本公开实施例中，在第一节点为第二节点的DU的宿主节点的情况下，第三节点为第二节点的DU。
其中，第二节点的DU可以向第二节点的DU的宿主节点发送第一消息，第一消息用于指示第二节点的用户位置信息。
在一些实施例中，在第一节点为第二节点的DU的宿主节点的情况下，第三节点为第二节点的MT的宿主节点。
本公开实施例中，在第一节点为第二节点的DU的宿主节点的情况下，第三节点为第二节点的MT的宿主节点。
其中，第二节点的MT的宿主节点可以向第二节点的DU的宿主节点发送第一消息，第一消息用于指示第二节点的用户位置信息。
可以理解的是，第二节点的DU的宿主节点，在第二节点的DU发生迁移，第二节点的DU由源宿主节点迁移至目标宿主节点的情况下，第二节点的DU的宿主节点可以为第二节点的DU的源宿主节点或第二节点的DU的目标宿主节点。
在一些实施例中，在第一节点为第二节点的DU发生迁移后的目标宿主节点的情况下，第三节点为第二节点的DU的源宿主节点。
本公开实施例中，在第一节点为第二节点的DU发生迁移后的目标宿主节点的情况下，第三节点为第二节点的DU的源宿主节点。
其中，第二节点的DU的源宿主节点可以向第二节点的DU的目标宿主节点发送第一消息，第一消息用于指示第二节点的用户位置信息。
在一些实施例中，第一消息为以下至少一项：
F1AP消息；
RRC消息；
XnAP消息。
本公开实施例中，第一消息可以为F1应用协议(F1 application protocol，F1AP)消息。
本公开实施例中，第一消息可以为无线资源控制(radioresource control，RRC)消息。
本公开实施例中，第一消息可以为Xn接口应用协议(Xn application protocol，XnAP)消息。
在一些实施例中，第一消息为用于指示第二节点的MT进行切换的消息。
本公开实施例中，第一消息可以为用于指示第二节点的MT进行切换的消息。第一消息可以是用于通知IAB-MT切换的消息。
在一些实施例中，第一消息为与终端设备相关的消息或与终端设备无关的消息。
本公开实施例中，第一消息可以为与终端设备相关的消息，或者第一消息还可以为与终端设备无关的消息。
在一些实施例中，在第一消息为与终端设备无关的消息的情况下，第一消息中还包括小区标识列表和/或第二节点的标识。
本公开实施例中，在第一消息为与终端设备无关的消息的情况下，第一消息中还可包括小区标识列表和/或第二节点的标识。
在一些实施例中，第一消息中还包括小区标识列表。
在一些实施例中，在第一消息为F1AP消息的情况下，第一消息用于指示第二节点的用户位置信息，第二节点的用户位置信息可以被包括在F1建立请求(F1 SETUP REQUEST)消息、和/或GNB-DU配置更新(GNB-DU CONFIGURATION UPDATE)消息等消息中。
在一些实施例中，在第一消息为F1AP消息的情况下，第一消息用于指示第二节点的用户位置信息，第二节点的用户位置信息可以被包括在服务小区信息IE(served cell information IE)中。
在一些实施例中，在第一消息为F1AP消息，F1AP消息为与终端设备有关的消息的情况下，F1AP消息可以为以下至少一项：
初始上行链路RRC消息传输(INITIAL UL RRC MESSAGE TRANSFER)消息；
RRC消息传输(UL RRC MESSAGE TRANSFER)消息；
终端设备上下文建立反馈(UE CONTEXT SETUP RESPONSE)消息；
终端设备上下文修改反馈(UE CONTEXT MODIFICATION RESPONSE)消息；
终端设备非激活通知(UE INACTIVITY NOTIFICATION)消息。
在一些实施例中，在第一消息为XnAP的情况下，第一消息用于指示第二节点的用户位置信息，第一消息可以是IAB-MT迁移完成指示消息。
需要说明的是，第一节点、第二节点以及第二节点的用户位置信息的相关描述，可以参见上述实施例中的相关描述，此处不再赘述。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或实施例任意组合。
通过实施本公开实施例，第三节点向第一节点发送第一消息，其中，第一消息用于指示第二节点的用户位置信息，第一节点为第二节点的宿主节点。由此，支持第三节点向第一节点发送第二节点的用户位置信息。
请参见图21，图21是本公开实施例提供的又一种信息获取方法的流程图。需要说明的是，本公开实施例的信息获取方法可由第二节点执行。如图21所示，该方法可以包括但不限于如下步骤：
S211：向核心网设备发送第一指示信息，其中，第一指示信息用于指示第二节点的用户位置信息。
本公开实施例中，第二节点可以IAB-node，第二节点可以向核心网设备发送第一指示信息，第一指示信息用于指示第二节点的用户位置信息。由此，支持第二节点将第二节点的用户位置信息上报至核心网设备。
示例性地，第二节点的用户位置信息，可以为第二节点的驻留的接入网信息，包括但不限E-UTRA(Evolved-UMTS Terrestrial Radio Access)用户位置信息、NR用户位置信息、非3GPP接入网络的信息中的至少一者，如果为3GPP接入网络信息(即E-UTRA用户位置信息或NR用户位置信息)，第二节点的用户位置信息可以为第二节点驻留的小区信息、TAI(Tracking Area Identity)、PSCell(Primary SCG(Secondary Cell Group)Cell)信息、用于标识非公共网络的信息，以及对应的时间信息，例如：第一时间驻留在第一小区、第二时间驻留在第二小区，等等。其中，驻留的小区可以是已经驻留的小区信息，或者将来会驻留的小区信息。
示例性地，第二节点的用户位置信息，还可以包括第二节点的移动速度和/或运动轨迹。
在一些实施例中，第二节点向核心网设备发送第一指示信息，包括：向核心网设备发送NGAP消息，其中，NGAP消息中包括第一指示信息。
本公开实施例中，第二节点向核心网设备发送第一指示信息，可以向核心网设备发送NGAP消息，其中，NGAP消息中包括第一指示信息。
在一些实施例中，NGAP消息为UE相关的消息，包括但不限于初始UE消息、UE上下文建立反馈消息、UE上下文修改反馈消息、UE上下文释放完成消息、RRC非激活转换报告消息、PDU会话资源释放反馈消息、PDU会话资源修改反馈消息、PDU资源通知消息、PDU会话资源修改指示消息中的至少一个等。
在一些实施例中，NGAP消息中包括终端设备的用户位置信息，终端设备的用户位置信息中包括第一指示信息。
在一些实施例中，NGAP消息中包括终端设备的用户位置信息和第一指示信息。
在一些实施例中，第二节点的用户位置信息为第二节点的MT的用户位置信息。
本公开实施例中，第二节点可以包括移动终端(mobile termination，MT)部分与分布式单元(distributed unit，DU)部分。
其中，第二节点的用户位置信息为第二节点的MT的用户位置信息。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或实施例任意组合。
通过实施本公开实施例，第二节点向核心网设备发送第一指示信息，其中，第一指示信息用于指示第二节点的用户位置信息。由此，支持第二节点将第二节点的用户位置信息上报至核心网设备。
请参见图22，图22是本公开实施例提供的又一种信息获取方法的流程图。需要说明的是，本公开实施例的信息获取方法可由第二节点执行。如图22所示，该方法可以包括但不限于如下步骤：
S221：向核心网设备发送第一指示信息，其中，第一指示信息用于指示第二节点的用户位置信息。
S222：向核心网设备发送第二指示信息，其中，第二指示信息用于指示第二节点下的小区标识列表和/或第二节点的标识。
本公开实施例中，第二节点可以向核心网设备发送第二指示信息，第二指示信息用于指示第二节点下的小区标识列表和/或第二节点的标识。由此，第二节点支持将小区标识列表上报至核心网设备。
示例地，第二节点的标识用于标识第二节点或第二节点上的MT，第二节点的标识可以是AMF UE NGAP ID、RAN UE NGAP ID、UE XnAP ID、F1AP UE ID、或GPSI(Generic Public Subscription Identifier，通用公共用户标识)等。
在一些实施例中，第二节点向核心网设备发送第二指示信息，包括：向核心网设备发送NGAP消息，其中，NGAP消息中包括第二指示信息。
本公开实施例中，第二节点向核心网设备发送第二指示信息，可以向核心网设备发送NGAP消息，其中，NGAP消息中包括第二指示信息。
需要说明的是，第二节点、第二节点的用户位置信息以及第一指示信息的相关描述，可以参见上述实施例中的相关描述，此处不再赘述。
在本实施方式或实施例中，在不矛盾的情况下，各步骤可以独立、任意组合或交换顺序，可选方式或可选例可以任意组合，且可以与其他实施方式或实施例任意组合。
需要说明的是，本公开实施例中，S221至S222可以单独被实施，也可以结合本公开实施例中的任何一个其他步骤一起被实施，例如结合本公开实施例中的S211一起被实施，本公开实施例并不对此做出限定。
通过实施本公开实施例，第二节点向核心网设备发送第一指示信息，其中，第一指示信息用于指示第二节点的用户位置信息，向核心网设备发送第二指示信息，其中，第二指示信息用于指示第二节点下的小区标识列表和/或第二节点的标识。由此，支持第二节点将第二节点的用户位置信息，以及小区标识列表上报至核心网设备。
请参见图23，图23是本公开实施例提供的一种信息获取系统的结构图。如图23所示，该系统可以包括但不限于：
核心网设备，被配置为接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。
第一节点或第二节点，被配置为向核心网设备发送第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。
如图24所示，在一些实施例中，该系统还可以包括第三节点，被配置为向第一节点发送第一消息，其中，第一消息用于指示第二节点的用户位置信息，第一节点为第二节点的宿主节点；
第一节点，还被配置为根据第一消息，确定第二节点的用户位置信息。
需要说明的是，在上述信息获取系统中，核心网设备、第一节点、第二节点、第三节点所执行方法的相关描述与上述实施例中的相关描述一致，可参见上面一些实施例中的详细描述，此处不再赘述。
在R18IAB课题研究中，支持移动IAB(mobile IAB)的场景，移动IAB研究工作集中于车载移动IAB节点为车载和/或周边终端提供5G覆盖/能力增强的场景。
相关技术中，服务UE(终端设备)的基站可以通过信令向AMF发送用户位置信息(ULI)，AMF可以根据该用户位置信息决定是否允许该终端在其当前位置操作。
而对于通过mobile IAB接入的UE，为了支持更好地UE位置管理，3GPP SA2同意服务UE的IAB-donor需要提供该IAB-node的IAB-MT的ULI作为额外的ULI。
如果IAB-node在执行了一次或多次partial migration之后(即IAB-MT和IAB-DU的serving IAB-donor-CU不同时)，服务UE的IAB-donor-CU(即IAB-DU的IAB-donor-CU)无法向核心网设备提供IAB-MT的ULI作为额外的ULI。
本公开实施例中，通过多种方法，可以支持在以下场景中向核心网设备提供UE准确的额外的ULI:
-当IAB-MT和IAB-DU所属的IAB-donor-CU不同时,IAB-MT发生了切换。
-当IAB-MT和IAB-DU所属的IAB-donor-CU不同时,IAB-DU发生了迁移。
方法1：服务UE的IAB-donor-CU可以从服务IAB-MT的IAB-donor-CU获得IAB-MT ULI，并将所述IAB-MT ULI作为UE的额外ULI发送给核心网设备。
方法2：服务UE的IAB-donor-CU可以从服务IAB-DU的IAB-donor-CU获得IAB-MT ULI，并将所述IAB-MT ULI作为UE的额外ULI发送给核心网设备。
方法3：服务UE的IAB-donor-CU可以从IAB-DU获得IAB-MT ULI，并将所述IAB-MT ULI作为UE的额外ULI发送给核心网设备。
示例性实施例中，第一节点执行：从第三节点接收第一ULI，并将所述ULI作为UE的额外的ULI，发送给核心网设备。
其中，所述第一ULI是第二节点中的第一子节点的，并且，UE通过第二节点接入网络。
在一些实施例中，第一节点从第三节点接收第一ULI，还包括从第三节点接收与所述第一ULI对应的第三节点的标识信息。
在一些实施例中，所述第二节点的标识信息可以是第二节点的标识、和/或第二节点提供的服务小区的标识列表。
在一些实施例中，所述第一节点是IAB-donor-CU,所述第三节点可以是IAB-donor-CU或IAB-node
在一些实施例中，如果所述第三节点是IAB-donor-CU，第一节点是IAB-donor-CU，所述第一ULI和/或对应的第二节点的标识信息被包括在XnAP消息中。
在一些实施例中，如果所述第三节点是IAB-node，第一节点是IAB-donor-CU，所述第一ULI和/或对应的第二节点的标识信息被包括在F1AP消息或RRC消息中。
方法4，IAB-DU或服务IAB-DU的IAB-donor-CU通过服务IAB-MT的IAB-donor-CU，将与IAB-MT ULI关联的IAB-DU的小区标识列表发送给AMF,AMF根据与IAB-MT ULI关联的小区标识列表和UE接入时获得服务小区标识，确定UE的额外的ULI。
示例性实施例中，核心网设备执行：从第一节点或第二节点接收与第一ULI关联的第二节点的标识信息，并根据所述信息，确定UE的额外的ULI。其中，所述UE通过第二节点接入网络。
在一些实施例中，所述第二节点是IAB-node，第一节点是IAB-donor-CU。
在一些实施例中，如果所述第一节点是IAB-donor-CU，所述与第一ULI关联的第二节点的标识信息被包括在NGAP消息中。
在一些实施例中，如果所述第二节点是IAB-node，所述与第一ULI关联的第二节点的标识信息被包括在NAS消息中。
需要说明的是，在上述方法中，核心网设备、第一节点、第二节点、第三节点所执行方法的相关描述与上述实施例中的相关描述一致，可参见上面一些实施例中的详细描述，此处不再赘述。
为方便理解本公开实施例，本公开实施例提供如下示例性实施例。
示例性实施例中，如图25所示，以第一节点为IAB-DU的宿主节点(IAB-DU’s IAB-donor-CU)为例进行说明。
步骤100，在一次partial migration之后，IAB-MT's source IAB-donor-CU(即IAB-MT's serving  IAB-donor-CU)决定执行IAB-MT切换。
步骤101，IAB-MT执行从IAB-MT's source IAB-donor-CU到IAB-MT's target IAB-donor-CU的切换。
步骤102a，IAB-MT's source IAB-donor-CU向IAB-DU's IAB-donor-CU发送IAB-MT的ULI(User Location Information)。
步骤102b，IAB-MT's target IAB-donor-CU向IAB-DU's IAB-donor-CU发送IAB-MT的ULI(User Location Information)。
其中，步骤102a和步骤102b可能发生在步骤101之前，之后或过程中。
对于步骤102a和步骤102b可以应用到以下实施例(以下实施例可以同时或单独应用)：
-在一些实施例中，所述IAB-MT的ULI可以作为UE的额外的ULI，其中，所述UE通过IAB-MT所在的IAB-node接入网络(即连接到AMF)。
-在一些实施例中，所述IAB-MT的ULI被包括在XnAP消息中，即所述IAB-MT的ULI被包括在IAB-MT's source IAB-donor-CU发送给IAB-DU's IAB-donor-CU的XnAP消息中；或者所述IAB-MT被包括在IAB-MT's source IAB-donor-CU发送给IAB-DU's IAB-donor-CU的XnAP消息中；
-更进一步，在一些实施例中，所述XnAP消息可以是用于通知IAB-MT切换的消息；
-更进一步，在一些实施例中，所述XnAP消息是非UE相关的消息；
-更进一步，在一些实施例中，所述XnAP消息中还包括IAB-DU的服务小区标识，其中，所述IAB-DU与所述IAB-MT在同一个IAB-node上，所述IAB-DU的服务小区标识，用于IAB-DU’s IAB-donor-CU(即服务UE的IAB-donor-CU)根据UE接入的小区标识向所述UE连接的AMF发送IAB-MT的ULI。
步骤102c，IAB-DU向IAB-DU’s IAB-donor-CU发送IAB-MT的ULI。
其中，步骤102c可能发生在步骤101之前，之后或过程中。
对于步骤102c可以应用到以下实施例(以下实施例可以同时或单独应用)：
-在一些实施例中，所述IAB-MT的ULI可以作为UE的额外的ULI，其中，所述UE通过IAB-MT所在的IAB-node接入网络(即连接到AMF)。
-在一些实施例中，所述IAB-MT的ULI被包括在F1AP消息中，即所述IAB-MT的ULI被包括在IAB-DU发送给IAB-DU's IAB-donor-CU的F1AP消息中。
-在一些实施例中，所述F1AP消息可以是用于通知IAB-MT切换的消息。
-在一些实施例中，所述F1AP消息是非UE相关的消息或UE相关的消息。
-在一些实施例中，如果所述F1AP消息是非UE相关的消息，所述F1AP消息中还包括IAB-DU的服务小区标识，其中，所述IAB-DU与所述IAB-MT在同一个IAB-node上，所述IAB-DU的服务小区标识，用于IAB-DU’s IAB-donor-CU(即服务UE的IAB-donor-CU)根据UE接入的小区标识向所述UE连接的AMF发送IAB-MT的ULI。
更进一步，在一些实施例中，所述IAB-MT的ULI被包括在F1 SETUP REQUEST消息、和/或GNB-DU CONFIGURATION UPDATE消息等消息中。
更进一步，在一些实施例中，所述IAB-MT的ULI被包括在served cell information IE中。
-在一些实施例中，如果所述F1AP消息是UE相关的消息，所述F1AP消息可以是初始上行链路RRC消息传输(INITIAL UL RRC MESSAGE TRANSFER)消息、RRC消息传输(UL RRC MESSAGE TRANSFER)消息、UE上下文建立反馈(UE CONTEXT SETUP RESPONSE)消息、UE上下文修改反馈(UE CONTEXT MODIFICATION RESPONSE)消息、和/或UE非激活通知(UE INACTIVITY NOTIFICATION)消息等消息中。
步骤103，IAB-DU’s IAB-donor-CU接收并保存所述IAB-MT ULI，并将所述IAB-MT ULI作为IAB-node服务的UE的额外的ULI。
在一些实施例中，如果IAB-DU’s IAB-donor-CU是通过非UE相关的消息接收IAB-MT ULI的，IAB-DU’s IAB-donor-CU可以通过与所述IAB-MT ULI一起接收的小区标识(例如一个或多个cell identify)和UE实际接入的cell identify，确定UE的额外的ULI。
在一些实施例中，如果IAB-DU’s IAB-donor-CU是通过UE相关的消息接收IAB-MT ULI的，IAB-DU’s IAB-donor-CU将所述IAB-MT ULI作为UE的额外的ULI。
基于此，IAB-DU’s IAB-donor-CU将所述UE的额外的ULI发送给AMF。AMF可以通过额外的ULI为UE提供更准确的服务。
在图25所示的实施例中，可选的，在一些实施方式中，102a、102b与102c为可选的，可以执行102a、102b与102c三者中的一者。
在图25所示的实施例中，可选的，在一些实施方式中，102a、102b与102c可以先于101执行。
其中，图25所示的各个步骤中的具体内容已在上述图11至图22中的实施例进行详细描述，可以参考上文中图11-图22对应的文字描述，此处不再赘述。
为方便理解本公开实施例，本公开实施例提供如下示例性实施例。
示例性实施例中，如图26所示，以第一节点为IAB-DU的目标宿主节点(IAB-DU’s Target IAB-donor-CU)为例进行说明。
步骤200，如果有获取到IAB-MT ULI，IAB-DU's serving IAB-donor-CU保存所述IAB-MT ULI。
步骤201，如果IAB-DU's source IAB-donor-CU(即IAB-DU's serving IAB-donor-CU)决定执行DU migration，IAB-DU's source IAB-donor-CU向IAB-DU's target IAB-donor-CU发送IAB-MT ULI。
-在一些实施例中，所述IAB-MT ULI被包括在XnAP消息中，即所述IAB-MT的ULI被包括在IAB-DU's source IAB-donor-CU发送给IAB-DU's target IAB-donor-CU的XnAP消息中，所述XnAP消息可以是IAB-DU迁移请求消息、IAB传输迁移请求消息或其他XnAP消息。
-更进一步，在一些实施例中，所述XnAP消息中还包括IAB-DU的服务小区标识，所述IAB-DU的服务小区标识，用于IAB-DU’s target IAB-donor-CU根据UE接入的小区标识向所述UE连接的AMF发送IAB-MT的ULI。
步骤201，IAB-DU’s target IAB-donor-CU接收并保存所述IAB-MT ULI，并将所述IAB-MT ULI作为IAB-node服务的UE的额外的ULI。
如果有UE通过IAB-node接入核心网设备(例如AMF),IAB-DU’s target IAB-donor-CU将所述UE的额外的ULI发送给AMF。AMF可以通过额外的ULI为UE提供更准确的服务。
其中，图26所示的各个步骤中的具体内容已在上述图11至图22中的实施例进行详细描述，可以参考上文中图11-图22对应的文字描述，此处不再赘述。
为方便理解本公开实施例，本公开实施例提供如下示例性实施例。
示例性实施例中，如图27所示，分别301a以第一节点为IAB-MT为例，301b至301c以第一节点为IAB-MT的宿主节点(IAB-MT’s IAB-donor CU)为例进行说明。
步骤300，IAB-MT’s target IAB-donor-CU向AMF发送IAB-MT ULI。
步骤301a，IAB-MT向AMF发送IAB-DU的小区标识列表。
其中，所述IAB-MT和IAB-DU在同一个IAB-node上。
步骤301b-1,IAB-DU’s IAB-donor-CU向IAB-MT’s IAB-donor-CU发送IAB-DU的小区标识列表。
步骤301b-2IAB-MT’s IAB-donor-CU向AMF发送IAB-DU的小区标识列表。
AMF接收所述信息，并将IAB-MT ULI与所述小区标识列表关联。如果有UE通过IAB-node中的小区接入核心网设备(例如AMF),AMF可以根据提供的服务小区ID和与IAB-MT ULI关联的小区标识列表，决定UE的额外的ULI,AMF可以通过额外的ULI为UE提供更准确的服务。
在图27所示的实施例中，可选的，在一些实施方式中，301a与301b-1至301b-2为可选的，可以执行301a与301b-1至301b-2两者中的一者。
其中，图27所示的各个步骤中的具体内容已在上述图11至图22中的实施例进行详细描述，可以参考上文中图11-图22对应的文字描述，此处不再赘述。
上述本公开提供的实施例中，分别从核心网设备、第一节点、第三节点和第二节点的角度对本公开实施例提供的方法进行了介绍。
请参见图28，为本公开实施例提供的一种通信装置1的结构示意图。图28所示的通信装置1可包括收发模块11和处理模块。收发模块可包括发送模块和/或接收模块，发送模块用于实现发送功能，接收模块用于实现接收功能，收发模块可以实现发送功能和/或接收功能。
通信装置1可以是核心网设备、第一节点、第三节点或第二节点，也可以是核心网设备、第一节点、第三节点或第二节点中的装置，还可以是能够与核心网设备、第一节点、第三节点或第二节点匹配使用的装置。
通信装置1，应用于核心网设备：该装置，包括：收发模块11。
收发模块11，被配置为接收第一节点或第二节点发送的第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。
在一些实施例中，该装置还包括处理模块12。
处理模块12，被配置为根据第一指示信息，确定终端设备的额外用户位置信息为第二节点的用户位置信息，其中，通过第二节点为终端设备提供网络连接。
在一些实施例中，收发模块11，还被配置为接收第一节点或第二节点发送的第二指示信息，其中，第二指示信息用于指示以下至少一项：
第二节点下的小区标识列表；
第二节点的标识；
第二节点下的小区标识列表与第二节点的用户位置信息的关联关系；
第二节点的标识与第二节点的用户位置信息的关联关系。
在一些实施例中，处理模块12，还被配置为根据第二节点下的小区标识列表以及第二节点的用户位置信息，确定第二节点的用户位置信息与第二节点下的小区标识列表的关联关系，其中，第二指示信息用于指示第二节点下的小区标识列表；或者根据第二节点的标识以及第二节点的用户位置信息，确定第二节点的用户位置信息与第二节点的标识的关联关系，其中第二指示信息用于指示第二节点的标识。
在一些实施例中，处理模块12，还被配置为根据终端设备的服务小区标识和关联关系，确定终端设备的额外用户位置信息；或者根据终端设备提供的第二节点的标识和关联关系，确定终端设备的额外用户位置信息。
在一些实施例中，第二节点的用户位置信息为第二节点的MT的用户位置信息，第一节点为第二节点的MT的宿主节点，或者第一节点为第二节点的DU的宿主节点。
在一些实施例中，收发模块11，还被配置为接收第一节点发送的NGAP消息，其中，NGAP消息中包括第一指示信息；或者接收第二节点发送的NAS消息，其中，NAS消息中包括第一指示信息。
在一些实施例中，收发模块11，还被配置为接收第一节点发送的NGAP消息，其中，NGAP消息中包括第二指示信息：或者接收第二节点发送的NAS消息，其中，NAS消息中包括第二指示信息。
通信装置1，应用于第一节点：该装置包括：收发模块11。
收发模块11，被配置为向核心网设备发送第一指示信息，其中，第一节点为第二节点的宿主节点，第一指示信息用于指示第二节点的用户位置信息。
在一些实施例中，收发模块11，还被配置为向核心网设备发送第二指示信息，其中，第二指示信息用于指示以下至少一项：
第二节点下的小区标识列表；
第二节点的标识；
第二节点下的小区标识列表与第二节点的用户位置信息的关联关系；
第二节点的标识与第二节点的用户位置信息的关联关系。
在一些实施例中，收发模块11，还被配置为向核心网设备发送NGAP消息，其中，NGAP消息中包括第一指示信息。
在一些实施例中，收发模块11，还被配置为向核心网设备发送NGAP消息，其中，NGAP消息中包括第二指示信息。
在一些实施例中，第二节点的用户位置信息为第二节点的MT的用户位置信息，第一节点为第二节点的MT的宿主节点，或者第一节点为第二节点的DU的宿主节点。
在一些实施例中，该装置包括处理模块12。处理模块12，被配置为确定第二节点的用户位置信息。
在一些实施例中，收发模块11，还被配置为接收第三节点发送的第一消息，其中，第一消息包括用于指示第二节点的用户位置信息。
在一些实施例中，处理模块12，还被配置为根据第一消息，确定第二节点的用户位置信息。
在一些实施例中，在第一节点为第二节点的DU的宿主节点的情况下，第三节点为第二节点的DU或者为第二节点的MT的宿主节点。
在一些实施例中，在第一节点为第二节点的DU发生迁移后的目标宿主节点的情况下，第三节点为第二节点的DU的源宿主节点。
在一些实施例中，第一消息为以下至少一项：
F1AP消息；
RRC消息；
XnAP消息。
在一些实施例中，第一消息还用于指示第二节点的MT进行切换。
在一些实施例中，第一消息为与终端设备相关的消息或与终端设备无关的消息。
在一些实施例中，在第一消息为与终端设备无关的消息的情况下，第一消息中还包括小区标识列表。
在一些实施例中，处理模块12，还被配置为确定第二小区下的小区标识列表与第二节点的用户位置信息的关联关系，或者确定第二节点的标识与第二节点的用户位置信息的关联关系。
通信装置1，应用于第三节点：该装置，包括：收发模块11。
收发模块11，被配置为向第一节点发送第一消息，其中，第一消息用于指示第二节点的用户位置信息，第一节点为第二节点的宿主节点。
在一些实施例中，在第一节点为第二节点的DU的宿主节点的情况下，第三节点为第二节点的DU或者为第二节点的MT的宿主节点。
在一些实施例中，在第一节点为第二节点的DU发生迁移后的目标宿主节点的情况下，第三节点为第二节点的DU的源宿主节点。
在一些实施例中，第一消息为以下至少一项：
F1AP消息；
RRC消息；
XnAP消息。
在一些实施例中，第一消息还用于指示第二节点的MT进行切换。
在一些实施例中，第一消息为与终端设备相关的消息或与终端设备无关的消息。
在一些实施例中，在第一消息为与终端设备无关的消息的情况下，第一消息中还包括第二节点下的小区标识列表或第二节点的标识。
在一些实施例中，第一消息中还包括第二节点下的小区标识列表或第二节点的标识。
通信装置1，应用于第二节点：该装置，包括：收发模块11。
收发模块11，被配置为向核心网设备发送第一指示信息，其中，第一指示信息用于指示第二节点的用户位置信息。
在一些实施例中，收发模块11，还被配置为向核心网设备发送第二指示信息，其中，第二指示信息用于指示第二节点下的小区标识列表和/或第二节点的标识。
在一些实施例中，收发模块11，还被配置为向核心网设备发送NGAP消息，其中，NGAP消息中包括第一指示信息。
在一些实施例中，收发模块11，还被配置为向核心网设备发送NGAP消息，其中，NGAP消息中包括第二指示信息。
在一些实施例中，第二节点的用户位置信息为第二节点的MT的用户位置信息。
关于上述实施例中的通信装置1，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
本公开上述实施例中提供的通信装置1，与上面一些实施例中提供的信息获取方法取得相同或相似的有益效果，此处不再赘述。
请参见图29，图29是本公开实施例提供的另一种通信装置1000的结构示意图。通信装置1000可以是核心网设备、第一节点、第三节点或第二节点，也可以是支持核心网设备、第一节点、第三节点或第二节点实现上述方法的芯片、芯片系统、或处理器等。该通信装置1000可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置1000可以包括一个或多个处理器1001。处理器1001可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，网络侧设备、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
可选的，通信装置1000中还可以包括一个或多个存储器1002，其上可以存有计算机程序1004，存储器1002执行所述计算机程序1004，使得通信装置1000执行上述方法实施例中描述的方法。可选的，存储器1002中还可以存储有数据。通信装置1000和存储器1002可以单独设置，也可以集成在一起。
可选的，通信装置1000还可以包括收发器1005、天线1006。收发器1005可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1005可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
可选的，通信装置1000中还可以包括一个或多个接口电路1007。接口电路1007用于接收代码指令并传输至处理器1001。处理器1001运行代码指令以使通信装置1000执行上述方法实施例中描述的方法。
通信装置1000为核心网设备：收发器1005用于执行图11中的S111；图12中的S121；图13a中的S131a和S132a；图13b中的S131b和S132b；图14a中的S141a和S142a；图14b中的S141b和S142b；处理器1001用于执行图12中的S122；图13a中的S133a和S134a；图13b中的S133b和S134b；图14a中的S143a；图14b中的S143b。
通信装置1000为第一节点：收发器1005用于执行图15中的S151；图16中的S161和S162；图17中的S172；图18中的S181；处理器1001用于执行图17中的S171；图18中的S182；图19中的S191。
通信装置1000为第三节点：收发器1005用于执行图20中的S201。
通信装置1000为第二节点：收发器1005用于执行图21中的S211；图22中的S221和S222。
在一种实现方式中，处理器1001中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器1001可以存有计算机程序1003，计算机程序1003在处理器1001上运行，可使得通信装置1000执行上述方法实施例中描述的方法。计算机程序1003可能固化在处理器1001中，该种情况下，处理器1001可能由硬件实现。
在一种实现方式中，通信装置1000可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本公开中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是核心网设备、第一节点、第三节点或第二节点，但本公开中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图29的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络侧设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，请参见图30，为本公开实施例中提供的一种芯片的结构图。
芯片1100包括处理器1101和接口1103。其中，处理器1101的数量可以是一个或多个，接口1103的数量可以是多个。
对于芯片用于实现本公开实施例中核心网设备的功能的情况：
接口1103，用于接收代码指令并传输至所述处理器。
处理器1101，用于运行代码指令以执行如上面一些实施例所述的信息获取方法。
对于芯片用于实现本公开实施例中第一节点的功能的情况：
接口1103，用于接收代码指令并传输至所述处理器。
处理器1101，用于运行代码指令以执行如上面一些实施例所述的信息获取方法。
对于芯片用于实现本公开实施例中第二节点的功能的情况：
接口1103，用于接收代码指令并传输至所述处理器。
处理器1101，用于运行代码指令以执行如上面一些实施例所述的信息获取方法。
对于芯片用于实现本公开实施例中第三节点的功能的情况：
接口1103，用于接收代码指令并传输至所述处理器。
处理器1101，用于运行代码指令以执行如上面一些实施例所述的信息获取方法。
可选的，芯片1100还包括存储器1102，存储器1102用于存储必要的计算机程序和数据。
本领域技术人员还可以了解到本公开实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本公开实施例保护的范围。
本公开实施例还提供一种信息获取系统，该系统包括前述图28实施例中作为核心网设备的通信装置、作为第一节点的通信装置、作为第三节点的通信装置和/或作为第二节点的通信装置，或者，该系统包括前述图29实施例中作为核心网设备的通信装置、作为第一节点的通信装置、作为第三节点的通信装置和/或作为第二节点的通信装置。
本公开还提供一种可读存储介质，其上存储有指令，该指令被计算机执行时实现上述任一方法实施例的功能。
本公开还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行所述计算机程序时，全部或部分地产生按照本公开实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解：本公开中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本公开实施例的范围，也表示先后顺序。
本公开中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本公开不做限制。在本公开实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
取决于语境，如在此所使用的词语“如果”及“若”可以被解释成为“在……时”或“当……时”或“响应于确定”。
本公开中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本公开并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本公开中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
本公开中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以所述权利要求的保护范围为准。

Claims (42)

  1. 一种信息获取方法，其特征在于，所述方法由核心网设备执行，包括：
    接收第一节点或第二节点发送的第一指示信息，其中，所述第一节点为第二节点的宿主节点，所述第一指示信息用于指示所述第二节点的用户位置信息。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    根据所述第一指示信息，确定所述终端设备的额外用户位置信息为所述第二节点的用户位置信息，其中，通过所述第二节点为终端设备提供网络连接。
  3. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    接收所述第一节点或所述第二节点发送的第二指示信息，其中，所述第二指示信息用于指示以下至少一项：
    所述第二节点下的小区标识列表；
    所述第二节点的标识；
    所述第二节点下的小区标识列表与所述第二节点的用户位置信息的关联关系；
    所述第二节点的标识与所述第二节点的用户位置信息的关联关系。
  4. 如权利要求3所述的方法，其特征在于，所述方法还包括：
    根据所述第二节点下的小区标识列表以及所述第二节点的用户位置信息，确定所述第二节点的用户位置信息与所述第二节点下的小区标识列表的关联关系，其中，所述第二指示信息用于指示所述第二节点下的小区标识列表；或者
    根据所述第二节点的标识以及所述第二节点的用户位置信息，确定所述第二节点的用户位置信息与所述第二节点的标识的关联关系，其中，所述第二指示信息用于指示所述第二节点的标识。
  5. 如权利要求3或4所述的方法，其特征在于，所述方法还包括：
    根据终端设备的服务小区标识和所述关联关系，确定所述终端设备的额外用户位置信息；或者
    根据终端设备提供的第二节点的标识和所述关联关系，确定所述终端设备的额外用户位置信息。
  6. 如权利要求1至6中任一项所述的方法，其特征在于，所述第二节点的用户位置信息为所述第二节点的移动终端MT的用户位置信息，
    所述第一节点为所述第二节点的MT的宿主节点，或者所述第一节点为所述第二节点的分布式单元DU的宿主节点。
  7. 如权利要求1至6中任一项所述的方法，其特征在于，所述接收第一节点或第二节点发送的第一指示信息，包括：
    接收所述第一节点发送的下一代应用协议NGAP消息，其中，所述NGAP消息中包括所述第一指示信息；或者
    接收所述第二节点发送的非接入层NAS消息，其中，所述NAS消息中包括所述第一指示信息。
  8. 如权利要求3至6中任一项所述的方法，其特征在于，所述接收所述第一节点或所述第二节点发送的第二指示信息，包括：
    接收所述第一节点发送的NGAP消息，其中，所述NGAP消息中包括所述第二指示信息：或者
    接收所述第二节点发送的NAS消息，其中，所述NAS消息中包括所述第二指示信息。
  9. 一种信息获取方法，其特征在于，所述方法由第一节点执行，包括：
    向核心网设备发送第一指示信息，其中，所述第一节点为第二节点的宿主节点，所述第一指示信息用于指示所述第二节点的用户位置信息。
  10. 如权利要求9所述的方法，其特征在于，所述方法还包括：
    向所述核心网设备发送第二指示信息，其中，所述第二指示信息用于指示以下至少一项：
    所述第二节点下的小区标识列表；
    所述第二节点的标识；
    所述第二节点下的小区标识列表与所述第二节点的用户位置信息的关联关系；
    所述第二节点的标识与所述第二节点的用户位置信息的关联关系。
  11. 如权利要求9或10所述的方法，其特征在于，所述向核心网设备发送第一指示信息，包括：
    向所述核心网设备发送NGAP消息，其中，所述NGAP消息中包括所述第一指示信息。
  12. 如权利要求10所述的方法，其特征在于，所述向所述核心网设备发送第二指示信息，包括：
    向所述核心网设备发送NGAP消息，其中，所述NGAP消息中包括所述第二指示信息。
  13. 如权利要求9至12中任一项所述的方法，其特征在于，所述第二节点的用户位置信息为所述第二节点的MT的用户位置信息，
    所述第一节点为所述第二节点的MT的宿主节点，或者所述第一节点为所述第二节点的DU的宿主节点。
  14. 如权利要求9至13中任一项所述的方法，其特征在于，所述方法还包括：
    确定所述第二节点的用户位置信息。
  15. 如权利要求14所述的方法，其特征在于，所述确定所述第二节点的用户位置信息，包括：
    接收第三节点发送的第一消息，其中，所述第一消息用于指示所述第二节点的用户位置信息；
    根据所述第一消息，确定所述第二节点的用户位置信息。
  16. 如权利要求15所述的方法，其特征在于，所述第一节点为所述第二节点的DU的宿主节点，所述第三节点为所述第二节点的DU或为所述第二节点的MT的宿主节点。
  17. 如权利要求15所述的方法，其特征在于，所述第一节点为所述第二节点的DU发生迁移后的目标宿主节点，所述第三节点为所述第二节点的DU的源宿主节点。
  18. 如权利要求15至17中任一项所述的方法，其特征在于，所述第一消息为以下至少一项：
    F1应用协议F1AP消息；
    无线资源控制RRC消息；
    Xn接口应用协议XnAP消息。
  19. 如权利要求15至18中任一项所述的方法，其特征在于，所述第一消息还用于指示第二节点的MT进行切换。
  20. 如权利要求15至19中任一项所述的方法，其特征在于，所述第一消息为与终端设备无关的消息，所述第一消息包括小区标识列表。
  21. 如权利要求10至20中任一项所述的方法，其特征在于，所述方法还包括：
    确定所述第二节点下的小区标识列表与所述第二节点的用户位置信息的关联关系，或者确定所述第二节点的标识与所述第二节点的用户位置信息的关联关系。
  22. 一种信息获取方法，其特征在于，所述方法由第三节点执行，包括：
    向第一节点发送第一消息，其中，所述第一消息用于指示第二节点的用户位置信息，所述第一节点为所述第二节点的宿主节点。
  23. 如权利要求22所述的方法，其特征在于，在所述第一节点为所述第二节点的DU的宿主节点的情况下，所述第三节点为所述第二节点的DU或为所述第二节点的MT的宿主节点。
  24. 如权利要求22所述的方法，其特征在于，在所述第一节点为所述第二节点的DU发生迁移后的目标宿主节点的情况下，所述第三节点为所述第二节点的DU的源宿主节点。
  25. 如权利要求22至24中任一项所述的方法，其特征在于，所述第一消息为以下至少一项：
    F1AP消息；
    RRC消息；
    XnAP消息。
  26. 如权利要求22至25中任一项所述的方法，其特征在于，所述第一消息还用于指示第二节点的MT进行切换。
  27. 如权利要求22至26中任一项所述的方法，其特征在于，所述第一消息为与终端设备无关的消息，所述第一消息中还包括所述第二节点下的小区标识列表或所述第二节点的标识。
  28. 如权利要求22至26中任一项所述的方法，其特征在于，所述第一消息中还包括所述第二节点下的小区标识列表或所述第二节点的标识。
  29. 一种信息获取方法，其特征在于，所述方法由第二节点执行，包括：
    向核心网设备发送第一指示信息，其中，所述第一指示信息用于指示所述第二节点的用户位置信息。
  30. 如权利要求29所述的方法，其特征在于，所述方法还包括：
    向所述核心网设备发送第二指示信息，其中，所述第二指示信息用于指示以下至少一项：
    所述第二节点下的小区标识列表；
    所述第二节点的标识。
  31. 如权利要求29或30所述的方法，其特征在于，所述向核心网设备发送第一指示信息，包括：
    向所述核心网设备发送NGAP消息，其中，所述NGAP消息中包括所述第一指示信息。
  32. 如权利要求31所述的方法，其特征在于，所述向所述核心网设备发送第二指示信息，包括：
    向所述核心网设备发送NGAP消息，其中，所述NGAP消息中包括所述第二指示信息。
  33. 如权利要求29至32中任一项所述的方法，其特征在于，所述第二节点的用户位置信息为所述第二节点的MT的用户位置信息。
  34. 一种通信装置，其特征在于，所述装置包括：
    收发模块，被配置为接收第一节点或第二节点发送的第一指示信息，其中，所述第一节点为第二节点的宿主节点，所述第一指示信息用于指示所述第二节点的用户位置信息。
  35. 一种通信装置，其特征在于，所述装置包括：
    收发模块，被配置为向核心网设备发送第一指示信息，其中，所述装置为第二节点的宿主节点，所述第一指示信息用于指示所述第二节点的用户位置信息。
  36. 一种通信装置，其特征在于，所述装置包括：
    收发模块，被配置为向第一节点发送第一消息，其中，所述第一消息用于指示第二节点的用户位置信息，所述第一节点为所述第二节点的宿主节点。
  37. 一种通信装置，其特征在于，所述装置包括：
    收发模块，被配置为向核心网设备发送第一指示信息，其中，所述第一指示信息用于指示所述装置的用户位置信息。
  38. 一种通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求1至8中任一项所述的方法，或者，以使所述装置执行如权利要求9至21中任一项所述的方法，或者，以使所述装置执行如权利要求22至28中任一项所述的方法，或者，以使所述装置执行如权利要求29至33中任一项所述的方法。
  39. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使如权利要求1至8中任一项所述的方法被实现，或者，使如权利要求9至21中任一项所述的方法被实现，或者，使如权利要求22至28中任一项所述的方法被实现，或者，使如权利要求29至33中任一项所述的方法被实现。
  40. 一种信息获取系统，其特征在于，所述系统，包括：
    核心网设备，用于执行如权利要求1至8中任一项所述的方法；
    第一节点，用于执行如权利要求9至21中任一项所述的方法。
  41. 如权利要求40所述的系统，其特征在于，所述系统还包括：
    第二节点，用于执行如权利要求29至33中任一项所述的方法。
  42. 如权利要求40或41所述的系统，所述系统还包括：
    第三节点，用于执行如权利要求22至28中任一项所述的方法。
PCT/CN2023/076025 2023-02-14 2023-02-14 信息获取方法及装置 Ceased WO2024168550A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP23921718.5A EP4668787A4 (en) 2023-02-14 2023-02-14 METHOD AND APPARATUS FOR ACQUIRING INFORMATION
PCT/CN2023/076025 WO2024168550A1 (zh) 2023-02-14 2023-02-14 信息获取方法及装置
CN202380008242.2A CN118805389A (zh) 2023-02-14 2023-02-14 信息获取方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/076025 WO2024168550A1 (zh) 2023-02-14 2023-02-14 信息获取方法及装置

Publications (1)

Publication Number Publication Date
WO2024168550A1 true WO2024168550A1 (zh) 2024-08-22

Family

ID=92421571

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/076025 Ceased WO2024168550A1 (zh) 2023-02-14 2023-02-14 信息获取方法及装置

Country Status (3)

Country Link
EP (1) EP4668787A4 (zh)
CN (1) CN118805389A (zh)
WO (1) WO2024168550A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113810215A (zh) * 2020-06-12 2021-12-17 华为技术有限公司 一种中继通信方法及相关设备
CN113873587A (zh) * 2020-06-30 2021-12-31 华为技术有限公司 一种用于iab网络通信的方法及相关设备
CN115053565A (zh) * 2020-02-17 2022-09-13 中兴通讯股份有限公司 自接入回传网络中的宿主间拓扑自适应
US20220330196A1 (en) * 2019-12-20 2022-10-13 Vivo Mobile Communication Co., Ltd. Tau method and device based on mobile iab node

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021031044A1 (zh) * 2019-08-16 2021-02-25 华为技术有限公司 Iab节点的接入方法、iab节点和通信系统
CN120281645A (zh) * 2020-06-12 2025-07-08 华为技术有限公司 一种中继通信方法及相关设备
EP4258763A4 (en) * 2020-12-07 2024-01-17 Beijing Xiaomi Mobile Software Co., Ltd. METHOD AND DEVICE FOR POSITIONING USER EQUIPMENT BASED ON INTEGRATED ACCESS AND TERRESTRIAL LINK
CN115633390B (zh) * 2022-10-27 2023-08-29 广州爱浦路网络技术有限公司 基于iab基站的移动网络接入调控方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220330196A1 (en) * 2019-12-20 2022-10-13 Vivo Mobile Communication Co., Ltd. Tau method and device based on mobile iab node
CN115053565A (zh) * 2020-02-17 2022-09-13 中兴通讯股份有限公司 自接入回传网络中的宿主间拓扑自适应
CN113810215A (zh) * 2020-06-12 2021-12-17 华为技术有限公司 一种中继通信方法及相关设备
CN113873587A (zh) * 2020-06-30 2021-12-31 华为技术有限公司 一种用于iab网络通信的方法及相关设备

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
EP4668787A1 (en) 2025-12-24
CN118805389A (zh) 2024-10-18
EP4668787A4 (en) 2026-04-01

Similar Documents

Publication Publication Date Title
US20230189091A1 (en) Iab node configuration method and communication apparatus
CN109996306B (zh) 通信方法和通信设备
EP4138457B1 (en) Radio access network node, core network node, and methods therefor
US20210168654A1 (en) Methods and apparatuses for transmitting control-plane messages in cells using different radio access technologies
JP7523537B2 (ja) 無線通信方法、端末機器及びネットワーク機器
CN113676972A (zh) 无线接入网节点及其方法
CN109804667A (zh) 无线接入网节点、无线终端及其方法
CN115499890A (zh) 中继通信的方法、装置和系统
US20190380088A1 (en) Terminal device, base station, control device, method, and recording medium
CN106341907A (zh) 一种数据传输方法、装置和系统
EP3435728B1 (en) User device and communication method
WO2024168550A1 (zh) 信息获取方法及装置
WO2023220941A1 (zh) 一种数据前转信息的传输方法及其装置
CN118317289A (zh) 通信方法、装置和系统
WO2024138458A1 (zh) 连接建立方法及装置
EP4718911A1 (en) Unified tci states in a cell using non-unified tci states
US20230379005A1 (en) Wireless communication method and apparatus
WO2024065195A1 (zh) 一种迁移类型确定方法及其装置
WO2024087074A1 (zh) 传输配置方法、装置、设备及存储介质
WO2024065098A1 (zh) 一种迁移的方法及装置
WO2024164281A1 (zh) 长期凭证发送方法和装置
WO2024077423A1 (zh) 一种集成接入与回传iab节点服务处理方法及装置
WO2024197935A1 (zh) 信息获取方法及装置
WO2025168036A1 (zh) 通信方法及装置
CN120786342A (zh) 一种通信方法、装置及可读存储介质

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202380008242.2

Country of ref document: CN

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

Ref document number: 23921718

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202517087032

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2023921718

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 202517087032

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 2023921718

Country of ref document: EP

Effective date: 20250915

WWP Wipo information: published in national office

Ref document number: 2023921718

Country of ref document: EP