WO2021163977A1 - 一种网络设备切换的方法及装置 - Google Patents

一种网络设备切换的方法及装置 Download PDF

Info

Publication number
WO2021163977A1
WO2021163977A1 PCT/CN2020/076080 CN2020076080W WO2021163977A1 WO 2021163977 A1 WO2021163977 A1 WO 2021163977A1 CN 2020076080 W CN2020076080 W CN 2020076080W WO 2021163977 A1 WO2021163977 A1 WO 2021163977A1
Authority
WO
WIPO (PCT)
Prior art keywords
access network
network device
message
positioning
terminal device
Prior art date
Application number
PCT/CN2020/076080
Other languages
English (en)
French (fr)
Inventor
张宏平
曾清海
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2020/076080 priority Critical patent/WO2021163977A1/zh
Priority to CN202080096062.0A priority patent/CN115066930B/zh
Publication of WO2021163977A1 publication Critical patent/WO2021163977A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02Services making use of location information
    • H04W4/029Location-based management or tracking services

Definitions

  • This application relates to the field of communication technology, and in particular to a method and device for switching network equipment.
  • the mobility management of connected terminal devices is controlled by network devices.
  • the network device can control which cell the terminal device switches to and how to switch.
  • the terminal device can disconnect the connection with the source access network device and access the target access network device by interacting with the source access network device or the target access network device.
  • the terminal device needs to obtain the positioning reference signal sent by the access network device, and the access network device needs to obtain the positioning measurement result of the terminal device from the terminal device.
  • This application provides a method and device for switching network equipment, which can ensure the continuity of positioning in a switching scenario.
  • this application provides a method for switching network devices, the method including:
  • the source access network device sends a handover request message to the target access network device; wherein the handover request message is used to request the terminal device to be switched to the target access network device, and the terminal device is in a location-based management component or location-based The location management component (location management component, LMC); and the handover request message includes first indication information, and the first indication information is used to indicate that the source access network device continues to perform on the terminal device The said LMC-based positioning;
  • LMC location management component
  • the source access network device receives the handover request confirmation message sent by the target access network device; the source access network device sends an indication message to the terminal device; wherein, the indication message is used to indicate the The terminal device switches to the target access network device; the source access network device receives a first message sent by the target access network device, and the first message includes the positioning measurement result of the terminal device.
  • the technical solution provided by this application can be applied to a scenario where a terminal device switches from a source access network device to a target access network device, which not only ensures that the terminal device can complete the switching, but also ensures the continuity of positioning.
  • the source access network device can make the target access network device know that the source access network device continues to perform the pairing when receiving the first indication information LMC-based positioning of terminal equipment. Further, after the target access network device receives the location measurement result sent by the terminal device, it can send the location measurement result to the source access network device.
  • the method before the source access network device sends a handover request message to the target access network device, the method further includes: when any one or more of the following conditions is satisfied, the The source access network device determines to continue to perform the LMC-based positioning of the terminal device on the source access network device:
  • the target access network device does not support the LMC-based positioning; or, the target access network device does not meet the positioning service quality QoS requirements of the terminal device; or, the positioning type of the LMC-based positioning is The location request RI-LR triggered by the radio access network.
  • the method before the source access network device sends the handover request message to the target access network device, the method further includes: the source access network device receives the target access network device's sending The second message; wherein, the second message includes whether the target access network device supports the LMC-based positioning and/or the positioning QoS information supported by the target access network device.
  • the method further includes: the source access network device according to the positioning measurement result Determine the location information of the terminal device.
  • the method further includes:
  • the source access network device sends a third message to the target access network device, where the third message is used to indicate that the LMC-based positioning has ended; the source access network device receives the target access Context release message sent by the network device; or,
  • the source access network device sends a fourth message to the target access network device, where the fourth message is used to indicate that the context of the terminal device has been released.
  • the second message is any one of an Xn establishment request message, an Xn establishment response message, or an access network node configuration update message.
  • this application provides a method for switching network devices, the method including:
  • the target access network device receives a handover request message sent by the source access network device; wherein the handover request message is used to request the terminal device to be switched to the target access network device, and the terminal device is in a location-based management component LMC And the handover request message includes first indication information, the first indication information is used to indicate that the source access network device continues to perform the LMC-based positioning of the terminal device;
  • the target access network device sends a handover request confirmation message to the source access network device; the target access network device receives a fifth message sent by the terminal device, and the fifth message includes the terminal The positioning measurement result of the device; the target access network device sends a first message to the source access network device, and the first message includes the positioning measurement result of the terminal device.
  • the method before the target access network device receives the handover request message sent by the source access network device, the method further includes: the target access network device sends the source access network device to the source access network device. Send a second message; wherein, the second message includes whether the target access network device supports the LMC-based positioning and/or the positioning QoS information supported by the target access network device.
  • the method further includes:
  • the target access network device receives a third message sent by the source access network device, where the third message is used to indicate that the LMC-based positioning has ended; the target access network device connects to the source The network-connected device sends a context release message; or,
  • the target access network device receives a fourth message sent by the source access network device, where the fourth message is used to indicate that the context of the terminal device has been released.
  • the second message is any one of an Xn establishment request message, an Xn establishment response message, or an access network node configuration update message.
  • this application provides a method for switching network devices, the method including:
  • the source access network device sends a handover request message to the target access network device; wherein, the handover request message is used to request the terminal device to be switched to the target access network device, and the terminal device is in the position management component based on the LMC. Positioning status, and the handover request message includes the LMC-based positioning information;
  • the source access network device receives a handover request confirmation message sent by the target access network device, where the handover request confirmation message includes second indication information, and the second indication information is used to indicate the source access network
  • the device continues to perform the LMC-based positioning of the terminal device;
  • the source access network device sends an instruction message to the terminal device, where the instruction message is used to instruct the terminal device to switch to the target access network device; the source access network device receives the target access network device; A first message sent by a network access device, where the first message includes a positioning measurement result of the terminal device.
  • the LMC-based positioning information includes one or more of the positioning context information of the terminal device, the positioning service quality QoS requirement of the terminal device, or the positioning type.
  • the method further includes: the source access network device according to the positioning measurement result Determine the location information of the terminal device.
  • the method further includes:
  • the source access network device sends a third message to the target access network device, where the third message is used to indicate that the LMC-based positioning has ended; the source access network device receives the target access Context release message sent by the network device; or,
  • the source access network device sends a fourth message to the target access network device, where the fourth message is used to indicate that the context of the terminal device has been released.
  • the present application provides a method for handover of a network device, and the method includes:
  • the target access network device receives a handover request message sent by the source access network device; wherein the handover request message is used to request the terminal device to be switched to the target access network device, and the terminal device is in a location-based management component LMC Locating status of, and the handover request message includes the LMC-based positioning information;
  • the target access network device sends a handover request confirmation message to the source access network device, where the handover request confirmation message includes second indication information, and the second indication information is used to instruct the source access network device Continue to perform the LMC-based positioning of the terminal device;
  • the target access network device receives a fifth message sent by the terminal device, where the fifth message includes the positioning measurement result of the terminal device; and the target access network device sends a message to the source access network device Send a first message, and the first message includes the positioning measurement result of the terminal device.
  • the method before the target access network device sends a handover request confirmation message to the source access network device, the method further includes: when any one or more of the following conditions is satisfied , The target access network device determines to continue to perform the LMC-based positioning of the terminal device on the source access network device;
  • the target access network device does not support the LMC-based positioning; or, the target access network device does not meet the positioning service quality QoS requirements of the terminal device; or, the positioning type of the LMC-based positioning is The location request RI-LR triggered by the radio access network.
  • the method further includes:
  • the target access network device receives a third message sent by the source access network device, where the third message is used to indicate that the LMC-based positioning has ended; the target access network device connects to the source The network-connected device sends a context release message; or,
  • the target access network device receives a fourth message sent by the source access network device, where the fourth message is used to indicate that the context of the terminal device has been released.
  • the present application provides a method for switching network equipment, the method including:
  • the source access network device sends a handover request message to the target access network device; wherein, the handover request message is used to request the terminal device to be switched to the target access network device, and the terminal device is in the position management component based on the LMC. Positioning status, and the handover request message includes the LMC-based positioning information;
  • the source access network device receives a handover request confirmation message sent by the target access network device; the source access network device sends an indication message to the terminal device, and the indication message is used to instruct to switch to the target access network device.
  • Network access equipment
  • the LMC-based positioning information includes the positioning context information of the terminal device, the positioning service quality QoS requirements of the terminal device, the positioning type, and the identification ID of the source access network device , Any one or more of the location association identification ID allocated by the source access network device or the interface application protocol identification ID allocated by the LMC.
  • the method further includes: the source access network device receives the location information of the terminal device sent by the target access network device; the source access network device receives the The context release message sent by the target access network device.
  • the present application provides a method for switching network equipment, the method including:
  • the target access network device receives a handover request message sent by the source access network device; wherein the handover request message is used to request the terminal device to be switched to the target access network device, and the terminal device is in a location-based management component LMC Locating status of, and the handover request message includes the LMC-based positioning information;
  • the target access network device sends a handover request confirmation message to the source access network device; the target access network device receives the location information of the terminal device sent by the LMC.
  • the LMC-based positioning information includes the positioning context information of the terminal device, the positioning service quality QoS requirements of the terminal device, the positioning type, and the identification ID of the source access network device , Any one or more of the location association identification ID allocated by the source access network device or the interface application protocol identification ID allocated by the LMC.
  • the method further includes: the target access network device sends the location information of the terminal device to the source access device; the target access network device sends the location information of the terminal device to the source access device; The networked device sends a context release message.
  • the present application provides a method for switching network equipment, the method including:
  • the location management component LMC receives a request message sent from a target access network device; wherein the request message includes a location association identification ID allocated by the source access network device and/or an interface application protocol identification ID allocated by the LMC;
  • the LMC sends a response message to the target access network device.
  • the method further includes: the LMC receives a fifth message sent by the terminal device, and the fifth message includes the positioning measurement result of the terminal device; The location measurement result of the terminal device determines the location information of the terminal device; the LMC sends the location information of the terminal device to the target access network device.
  • this application provides a communication device for executing the first aspect or the method in any possible implementation manner of the first aspect.
  • the communication device includes a corresponding unit capable of executing the method in the first aspect or any possible implementation of the first aspect.
  • this application provides a communication device for executing the third aspect or the method in any possible implementation manner of the third aspect.
  • the communication device includes a corresponding unit capable of executing the third aspect or the method in any possible implementation manner of the third aspect.
  • this application provides a communication device for executing the fifth aspect or the method in any possible implementation manner of the fifth aspect.
  • the communication device includes a corresponding unit capable of executing the fifth aspect or the method in any possible implementation manner of the fifth aspect.
  • the communication devices described in the eighth, ninth, and tenth aspects above include source access network equipment.
  • this application provides a communication device for executing the second aspect or the method in any possible implementation manner of the second aspect.
  • the communication device includes a corresponding unit capable of executing the second aspect or the method in any possible implementation manner of the second aspect.
  • this application provides a communication device for executing the fourth aspect or the method in any possible implementation manner of the fourth aspect.
  • the communication device includes a corresponding unit capable of executing the fourth aspect or the method in any possible implementation manner of the fourth aspect.
  • this application provides a communication device for executing the sixth aspect or the method in any possible implementation manner of the sixth aspect.
  • the communication device includes a corresponding unit capable of executing the method in the sixth aspect or any possible implementation manner of the sixth aspect.
  • the communication devices described in the eleventh, twelfth, and thirteenth aspects above include target access network equipment.
  • this application provides a communication device for executing the seventh aspect or the method in any possible implementation manner of the seventh aspect.
  • the communication device includes a corresponding unit capable of executing the method in the seventh aspect or any possible implementation manner of the seventh aspect.
  • the communication device includes an LMC.
  • the present application provides a communication device, the communication device includes a processor, a memory, and a transceiver, the transceiver is used to receive signals or send signals; the memory is used to store program codes;
  • the processor is configured to invoke the program code to execute the method described in the first aspect or various possible implementation manners of the first aspect; or, the processor is configured to invoke the program code to execute the method described in the first aspect or various possible implementations of the first aspect;
  • the present application provides a communication device, the communication device includes a processor, a memory, and a transceiver, the transceiver is used for receiving signals or sending signals; the memory is used for storing program codes;
  • the processor is configured to invoke the program code to execute the method described in the second aspect or various possible implementation manners of the second aspect; or, the processor is configured to invoke the program code to execute the method described in the The method described in the fourth aspect or various possible implementation manners of the fourth aspect; or, the processor is configured to invoke the program code to execute the method described in the sixth aspect or various possible implementation manners of the sixth aspect Methods.
  • the present application provides a communication device, the communication device includes a processor and an interface circuit; the interface circuit is configured to receive code instructions;
  • the processor is configured to run the code instructions to enable the communication device to execute the method described in the first aspect or various possible implementation manners of the first aspect; or, the processor is configured to run the code instructions to Make the communication device execute the method described in the third aspect or various possible implementation manners of the third aspect; or, the processor is used to run the code instructions to make the communication device execute the fifth aspect or The methods described in the various possible implementations of the fifth aspect.
  • the present application provides a communication device, the communication device includes a processor and an interface circuit; the interface circuit is configured to receive code instructions;
  • the processor is configured to run the code instructions to enable the communication device to execute the method described in the second aspect or various possible implementation manners of the second aspect; or, the processor is configured to run the code instructions to Make the communication device execute the method as described in the fourth aspect or various possible implementation manners of the fourth aspect; or, the processor is used to run the code instructions to make the communication device execute the method as described in the sixth aspect or The methods described in the various possible implementations of the sixth aspect.
  • the present application provides a communication device, the communication device includes a processor and an interface circuit; the interface circuit is configured to receive code instructions; the processor is configured to run the code instructions to enable the communication
  • the apparatus executes the methods described in the seventh aspect or various possible implementation manners of the seventh aspect.
  • this application provides a computer-readable storage medium for storing instructions or computer programs.
  • the instructions or the computer program are executed, the first aspect or the first aspect
  • the methods described in the various possible implementation manners of one aspect are implemented; or, when the instructions or the computer program are executed, the methods described in the third aspect or various possible implementation manners of the third aspect are made Is implemented; or, when the instructions or the computer program are executed, the methods described in the fifth aspect or various possible implementation manners of the fifth aspect are implemented.
  • the present application provides a computer-readable storage medium for storing instructions or computer programs.
  • the second aspect or The methods described in the various possible implementations of the second aspect are implemented; or, when the instructions or the computer program are executed, the fourth aspect or the various possible implementations of the fourth aspect are The method is implemented; or, when the instruction or the computer program is executed, the method described in the sixth aspect or various possible implementation manners of the sixth aspect is implemented.
  • the present application provides a computer-readable storage medium for storing instructions or computer programs.
  • the instructions or the computer program are executed, the seventh aspect or The methods described in the various possible implementation manners of the seventh aspect are implemented.
  • the present application provides a computer program product.
  • the computer program product includes an instruction or a computer program.
  • the instruction or the computer program is executed, the first aspect or various aspects of the first aspect are Possible implementations
  • the methods described in the possible implementation manners are implemented; or, when the instructions or the computer program are executed, the methods described in the third aspect or various possible implementation manners of the third aspect are implemented; or, When the instructions or the computer program are executed, the methods described in the fifth aspect or various possible implementation manners of the fifth aspect are realized.
  • the present application provides a computer program product, the computer program product includes instructions or computer programs, when the instructions or the computer program are executed, the second aspect or various aspects of the second aspect Possible implementations The methods described in the possible implementation manners are implemented; or, when the instructions or the computer program are executed, the methods described in the fourth aspect or various possible implementation manners of the fourth aspect are implemented; or, When the instructions or the computer program are executed, the methods described in the sixth aspect or various possible implementation manners of the sixth aspect are implemented.
  • the present application provides a computer program product.
  • the computer program product includes an instruction or a computer program.
  • the seventh aspect or the seventh aspect is Possible implementations The method described is implemented.
  • this application provides a computer program for executing the methods described in the first aspect or various possible implementations of the first aspect; or, for executing the third aspect or each of the third aspects.
  • this application provides a computer program for executing the methods described in the second aspect or various possible implementations of the second aspect; or, for executing each of the fourth aspect or the fourth aspect The method described in one possible implementation manner; or, used to implement the method described in the sixth aspect or various possible implementation manners of the sixth aspect.
  • this application provides a computer program for executing the methods described in the seventh aspect or various possible implementation manners of the seventh aspect.
  • the present application provides a communication system, including a source access network device and a target access network device, the source access network device is configured to execute the method described in the first aspect, and the target access The network device is used to perform the method described in the second aspect; or, the source access network device is used to perform the method described in the third aspect, and the target access network device is used to perform the method described in the fourth aspect. Or, the source access network device is used to perform the method described in the fifth aspect, and the target access network device is used to perform the method described in the sixth aspect.
  • FIG. 1 is a schematic diagram of a positioning architecture based on wireless communication provided by an embodiment of the present application
  • FIG. 2 is a schematic diagram of the architecture of a radio access network (NG RAN) provided by an embodiment of the present application;
  • NG RAN radio access network
  • FIG. 3 is a schematic diagram of a protocol stack involved in the interaction of different network elements according to an embodiment of the present application
  • FIG. 4 is a schematic flowchart of a positioning method provided by an embodiment of the present application.
  • Figure 5a is a schematic diagram of a network architecture provided by an embodiment of the present application.
  • Figure 5b is a schematic diagram of a network architecture provided by an embodiment of the present application.
  • FIG. 5c is a schematic diagram of a network architecture provided by an embodiment of the present application.
  • FIG. 6a is a schematic diagram of a protocol stack involved in the interaction of different network elements according to an embodiment of the present application.
  • FIG. 6b is a schematic diagram of a protocol stack involved in the interaction of different network elements according to an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a handover method provided by an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a method for switching network equipment provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of interaction between base stations according to an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of a method for switching network equipment provided by an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of a method for switching network equipment provided by an embodiment of the present application.
  • FIG. 12 is a schematic flowchart of a method for switching network equipment provided by an embodiment of the present application.
  • FIG. 13 is a schematic flowchart of a method for switching network equipment provided by an embodiment of the present application.
  • FIG. 14 is a schematic flowchart of a method for switching network equipment provided by an embodiment of the present application.
  • FIG. 15 is a schematic flowchart of a method for switching network equipment provided by an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • At least one (item) refers to one or more
  • multiple refers to two or more than two
  • at least two (item) refers to two or three and three
  • “and/or” is used to describe the association relationship of associated objects, which means that there can be three kinds of relationships.
  • a and/or B can mean: there is only A, only B, and both A and B. In this case, A and B can be singular or plural.
  • the character “/” generally indicates that the associated objects before and after are in an "or” relationship.
  • the following at least one item (a) or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
  • At least one of a, b, or c can mean: a, b, c, "a and b", “a and c", “b and c", or "a and b and c" ", where a, b, and c can be single or multiple.
  • FIG. 1 is a schematic diagram of a positioning architecture based on wireless communication provided by an embodiment of this application.
  • the positioning architecture mainly includes three parts: radio access network (RAN), terminal equipment and core network.
  • the core network includes location management function (LMF), access and mobility management function (AMF), service location protocol (service location protocol, SLP), and evolution service mobile location center (evolved serving mobile location centre, E-SMLC) etc.
  • LMF location management function
  • AMF access and mobility management function
  • service location protocol service location protocol
  • SLP service location protocol
  • E-SMLC evolution service mobile location center
  • the LMF is responsible for supporting different types of location services related to the target terminal device, including the positioning of the terminal device and the delivery of auxiliary data to the terminal device.
  • the LMF and the access network device interact through the new radio (NR) positioning protocol annex (NR positioning protocol annex, NRPPa) messages to obtain positioning reference signals (PRS) and sounding reference Signal (sounding reference signal, SRS) configuration information, cell timing, cell location information, etc.
  • NR positioning protocol annex NR positioning protocol annex, NRPPa
  • PRS positioning reference signals
  • SRS sounding reference Signal
  • the LMF and the terminal device use long term evolution (LTE) positioning protocol (LTE positioning protocol, LPP) messages for UE capability information transfer, auxiliary information transfer, measurement information transfer, and so on.
  • LTE long term evolution
  • AMF can receive location service requests related to the target terminal device from the 5th generation core network location services (5GC LCS) entity; or, AMF itself can also initiate some location services on behalf of the target terminal device, and The location service request is sent to LMF. And after the AMF obtains the location information of the terminal device, it returns the location information of the terminal device to the 5GC LCS entity.
  • 5GC LCS 5th generation core network location services
  • the RAN includes access network equipment.
  • the access network equipment may be a next generation node B (gNB) or a next generation evolved node B (ng-eNB). ), or access network equipment in future 6G communications.
  • the gNB and the ng-eNB are connected through the Xn interface (or Xn-C interface), and the LMF and the ng-eNB/gNB are connected through the NG-C (note2) interface.
  • the access network device may be any device with a wireless transceiver function, including but not limited to the base station shown above.
  • the base station may also be a base station in a future communication system such as a sixth-generation communication system.
  • the access network device may also be an access node, a wireless relay node, a wireless backhaul node, etc. in a wireless fidelity (WiFi) system.
  • the access network device may also be a radio controller in a cloud radio access network (cloud radio access network, CRAN) scenario.
  • the access network device may also be a wearable device or a vehicle-mounted device.
  • the access network device may also be a small station, a transmission reception point (TRP) (or may also be referred to as a transmission point), etc. It can be understood that the access network device may also be a base station in a public land mobile network (PLMN) that will evolve in the future. For ease of description, the following will take the access network device as a base station as an example to introduce the method or network architecture involved in the embodiments of the present application.
  • TRP transmission reception point
  • PLMN public land mobile network
  • a base station such as a gNB
  • a base station may be composed of a centralized unit (CU) and a distributed unit (DU). That is, the functions of the base station in the access network are split, part of the functions of the base station are deployed in a CU, and the remaining functions are deployed in the DU. And multiple DUs share one CU, which can save costs and facilitate network expansion.
  • CU centralized unit
  • DU distributed unit
  • the segmentation of CU and DU can be divided according to the protocol stack.
  • the radio resource control (RRC) layer, the service data adaptation protocol (SDAP), and the packet data convergence protocol (packet data convergence protocol) can be segmented.
  • PDCP radio resource control
  • RLC radio link control
  • MAC media access control
  • CU and DU can be connected through F1 interface.
  • CU represents that gNB is connected to the core network through an NG interface (or NG-C interface), and CU represents that gNB is connected to other gNB through an Xn interface.
  • a CU can also be divided into a CU-control plane (CP) and a CU-user plan (UP) (not shown in FIG. 1).
  • CU-CP is responsible for the control plane function, mainly including RRC and PDCP corresponding to the control plane, namely PDCP-C.
  • PDCP-C is mainly responsible for encryption and decryption of control plane data, integrity protection, data transmission, etc.
  • CU-UP is responsible for user plane functions, mainly including SDAP and PDCP corresponding to the user plane, namely PDCP-U.
  • CU-CP and CU-UP can be connected through the E1 interface. It is understandable that the types of base stations shown above are only examples, and in specific implementation, there may be other types of base stations, etc., which are not limited in the embodiment of the present application.
  • the terminal equipment can measure downlink signals from NG RAN and other sources to support positioning.
  • the gNB/ng-eNB can provide measurement information for the target terminal device and send the measurement information to the LMF.
  • terminal equipment may also be referred to as user equipment (user equipment, UE), terminal, and so on.
  • a terminal device is a device with a wireless transceiver function, which can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on the water, such as a ship, etc.; it can also be deployed in the air, for example, Airplanes, balloons, or satellites.
  • Terminal devices can be mobile phones, tablets, computers with wireless transceiver functions, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, industrial control (industrial control) Wireless terminals in ), wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, and wireless terminals in transportation safety , Wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • VR virtual reality
  • AR augmented reality
  • industrial control industrial control
  • Wireless terminals in wireless terminals in self-driving
  • wireless terminals in remote medical wireless terminals in smart grid
  • wireless terminals in transportation safety Wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • the terminal device may also be a terminal device in a future 6G network or a terminal device in a future evolved PLMN, etc.
  • the terminal device and the terminal device can also be connected via device-to-device (D2D), vehicle-to-everything (V2X) or machine-to-device.
  • D2D device-to-device
  • V2X vehicle-to-everything
  • M2M Machine to machine
  • other technologies perform communication, and the embodiment of the present application does not limit the communication method between the terminal device and the terminal device.
  • the terminal device as the UE as an example to introduce the method or network architecture involved in the embodiments of the present application.
  • Figure 3 is a schematic diagram of the protocol stack involved in the interaction between the LMF and the UE.
  • the UE and the NG RAN are connected through the NR-Uu interface or the LTE-Uu interface.
  • the protocol stack used by the UE to interact with the NG RAN includes from top to bottom: LPP, non-access layer (non-access layer) -access stratum, NAS), radio resource control (radio resource control, RRC), packet data convergence protocol (packet data convergence protocol, PDCP), radio link control (radio link control, RLC), medium access control (medium access) control, MAC), layer (layer, L)1.
  • the protocol stack used by the NG RAN to interact with the UE includes from top to bottom: RRC, PDCP, RLC, MAC, and L1.
  • the NG RAN and AMF are connected through the NG-C interface.
  • the protocol stack used to interact with the AMF on the NG RAN side includes from top to bottom: NG interface application protocol (NGAP), stream control transmission protocol (stream control) transmission protocol, SCTP), internet protocol (IP), L2, L1.
  • NGAP NG interface application protocol
  • stream control stream control transmission protocol
  • SCTP stream control transmission protocol
  • IP internet protocol
  • L2 L1 internet protocol
  • the protocol stack used by the AMF side to interact with NGRAN includes from top to bottom: NAS, NGAP, SCTP, IP, L2, and L1.
  • the AMF and LMF are connected through the NLs interface.
  • the protocol stack used by the AMF side to interact with the LMF includes from top to bottom: Hypertext Transfer Protocol 2.0 ((hypertext transfer protocol, HTTP/2), transport layer security (transport layer) security, TLS), transmission control protocol (transmission control protocol, TCP), IP, L2, L1.
  • the protocol stack used to interact with AMF on the LMF side includes from top to bottom: LPP, HTTP/2, TLS, TCP, IP , L2, L1.
  • the information exchange between the LMF and the UE is carried by the LPP message, which is transmitted through the Uu interface and the NG-C interface.
  • the LPP message will be encapsulated in non-access stratum (NAS) signaling, and the base station will forward it after receiving the UE’s NAS signaling (that is, the base station does not know that the UE sent the LPP message)
  • NAS non-access stratum
  • the AMF obtains the LPP message after parsing the NAS signaling and sends it to the LMF.
  • the LPP message sent from the LMF side is encapsulated in the NAS signaling.
  • the base station After the base station receives the NAS signaling of the UE, it is directly transferred to the UE (that is, the base station does not know the LPP message contained in the received NAS signaling).
  • the information exchange between the LMF and the base station is carried by the NRPPa message, which is transmitted through the NG-C interface.
  • the information exchange between the LMF and the base station mentioned here can be understood as: the LMF needs to obtain some information from the base station, or the base station needs to obtain some information from the LMF, instead of simply forwarding the information.
  • an embodiment of the present application also provides a schematic flowchart of a positioning method. As shown in FIG. 4, the method at least includes:
  • the location initiator sends a location service request (location service request) to the AMF, where the location service request is used to request the location of the target UE.
  • location service request location service request
  • the above step 401 can also be replaced with: the serving AMF of the target UE needs to obtain the location of the target UE due to some reasons (such as emergency calls).
  • positioning may include the following four positioning types (or referred to as positioning scenarios):
  • the location request (mobile originated location request, MO-LR) initiated by the terminal is that the UE initiates a request to obtain its own location information;
  • the location request (MT-LR) terminated by the terminal is a request initiated by a third party to obtain the location information of the UE;
  • the network-induced location request (NI-LR) triggered by the network is the UE's serving core network (such as AMF) initiating a request to obtain the location information of the UE;
  • the location request (RAN Induced Location Request, RI-LR) triggered by the radio access network is a request initiated by the UE's access network (such as a base station) to obtain the location information of the UE.
  • the positioning requester in step 401 in the method shown in FIG. 4 is only an example.
  • the positioning initiator may also be referred to as a positioning client (client).
  • client positioning client
  • the above-mentioned third parties may include Internet servers such as bicycle sharing software servers and so on.
  • the AMF sends a page to make the UE enter the connected state; and the AMF sends a location service request to the LMF.
  • the LMF initiates a positioning process. For example, the LMF obtains the positioning capability of the UE from the UE; obtains positioning measurement or auxiliary information from the serving base station (NG-RAN as shown in Figure 4); obtains the position or positioning measurement result from the UE; or sends positioning auxiliary information to the UE, etc. .
  • the serving base station NG-RAN as shown in Figure 4
  • obtains the position or positioning measurement result from the UE or sends positioning auxiliary information to the UE, etc.
  • the positioning capability of the UE, the positioning measurement result obtained from the UE, and the positioning assistance information may be included in the LPP message.
  • the positioning measurement or assistance information obtained from the serving base station may be included in the NRPPa message.
  • the LMF determines the location of the UE based on the positioning measurement result of the UE or the base station; and sends the location of the UE to the AMF in a location service response message.
  • the AMF sends the location of the UE to the positioning initiator; or uses the location of the UE for emergency calls.
  • the positioning function (such as the function of the LMF) can be placed in the access network, which is called a location management component or a location management component (LMC).
  • LMC location management component
  • 5a, 5b, and 5c are schematic diagrams of a network architecture provided by an embodiment of the present application.
  • LMC can be used as a function inside the base station without introducing a new interface.
  • the LMC can be used as a logical node to connect to the base station through a new interface.
  • the new interface may be called itf, etc.
  • the embodiment of the present application does not limit the name of the new interface.
  • the LMC may be connected to a centralized unit (CU) in the base station.
  • CU centralized unit
  • the LMC is connected to multiple base stations through a new interface.
  • Figure 6a and Figure 6b show the protocol stack involved when the LMC interacts with the UE.
  • the LMC and the UE are connected through the interface NR-Uu, and the protocol stack on the UE side includes from top to bottom: LPP, RRC, PDCP, RLC, MAC, L1; gNB/
  • the protocol stack on the LMC side includes from top to bottom: LPP, RRC, PDCP, RLC, MAC, L1.
  • the protocol stack on the UE side includes from top to bottom: LPP, RRC, PDCP, RLC, MAC, L1; the base station faces the UE From top to bottom, the protocol stack includes: RRC, PDCP, RLC, MAC, L1; from top to bottom, the protocol stack facing the LMC from the base station side includes: XPAP, SCTP, IP, L2, L1; the protocol stack on the LMC side is from top to bottom The following includes: LPP, XPAP, SCTP, IP, L2, L1.
  • the interface between the base station and the LMC in Figure 6b is "XP"
  • the interface protocol between the base station and the LMC is "XPAP”.
  • the name of the interface between the base station and the LMC and the corresponding interface protocol may also be in other forms, which are not limited in this application.
  • the message interaction between LMC and UE can still use the LPP protocol, but it is different from the positioning architecture shown in Figure 1, the protocol stack between UE and LMF
  • the LPP message between the LMC and the UE is encapsulated in a radio resource control (radio resource control, RRC) message.
  • RRC radio resource control
  • the switching method includes:
  • the source base station sends an RRC reconfiguration message to the UE in the connected state, which includes parameters such as measurement object, report configuration, and measurement identifier.
  • the UE measures multiple cells according to the RRC reconfiguration (RRC reconfiguration) message, and forms a report to report various events to the currently connected source base station. For example, the signal strength of the current serving cell is lower than a threshold. And the signal of the target cell is higher than the threshold.
  • RRC reconfiguration RRC reconfiguration
  • the source base station determines whether the UE needs to be handed over (handover decision), and if it is determined that the UE needs to be handed over, the source base station sends a handover request (handover request) message to the target base station.
  • handover decision determines whether the UE needs to be handed over
  • handover request sends a handover request (handover request) message to the target base station.
  • the target base station sends a handover request acknowledgment (handover request ACK) message to the source base station; optionally, the target base station may (target gNB) determine whether to allow UE access (admission control) according to its own connection number and other conditions.
  • the handover request confirmation message may include parameters such as a new cell-radio network temporary identifier (C-RNTI), security-related algorithms of the target base station, etc.
  • the source base station After receiving the handover request confirmation message sent by the target base station, the source base station sends an RRC reconfiguration message (ie, handover command) to the UE.
  • the RRC reconfiguration message may include the handover request confirmation message in 704.
  • the RRC reconfiguration message in the NR system may also include related information of the target cell and related configuration parameters required by the UE to access the target cell.
  • the RRC reconfiguration message contains the information of the target cell.
  • the information of the target cell may include the physical cell identifier (PCI) of the target cell and the frequency information corresponding to the target cell (such as the frequency point corresponding to the target cell), etc. .
  • PCI physical cell identifier
  • the UE initiates random access (random access) to the target base station according to the foregoing RRC reconfiguration information.
  • the UE disconnects from the source base station.
  • the UE may experience a brief interruption in data transmission and reception.
  • the UE sends an RRC reconfiguration complete (RRC reconfiguration complete) message to the target base station.
  • RRC reconfiguration complete RRC reconfiguration complete
  • the target base station sends a context release message to the source base station to instruct the source base station to release the context of the UE.
  • the embodiment of the present application provides a method for switching network devices, which effectively solves the problem of how to ensure the continuity of positioning in a switching scenario.
  • the method for switching network devices provided in the embodiments of the present application can be applied to various communication systems, and can also be applied to the various network architectures introduced in the foregoing embodiments.
  • the method can be applied to access network equipment, and the types of the access network equipment may include the various types introduced in the foregoing embodiments.
  • the access network device involved in the embodiment of the present application may include a source access network device and a target access network device.
  • a source access network device as a source base station and a target access network device as a target base station will be taken as an example to illustrate the method provided in the embodiment of the present application.
  • the source base station or the target base station may determine to continue to perform positioning at the source base station.
  • FIG. 8 is a schematic flowchart of a method for switching network equipment provided by an embodiment of the present application. As shown in Figure 8, the method for switching network devices at least includes:
  • the source base station sends a handover request message to the target base station.
  • the target base station receives the handover request message.
  • the handover request message is used to request the UE to be handed over to the target base station, and the UE is in a positioning state based on LMC. That is, when the source base station sends the handover request message to the target base station, the UE is in the RRC connected state, and the source base station is performing LMC-based positioning on the UE. As for which step of the positioning process the source base station and the UE are in, the embodiment of the present application does not limit it.
  • the source base station sends the handover request message to the target base station it can be understood as: before the source base station sends the handover request message to the target base station, or at the same time when the source base station sends the handover request message to the target base station. Understandably, for the description of the positioning state of the source base station and the UE when the source base station sends the handover request message, the following embodiments are also applicable.
  • the handover request message includes first indication information, and the first indication information is used to instruct to continue to perform the LMC-based positioning of the UE at the source base station, or to instruct the positioning not to migrate to the target base station.
  • the specific form of the first indication information is not limited in the embodiment of the present application.
  • an embodiment of the present application also provides a method for how the source base station determines whether to continue positioning.
  • base station 1 and base station 2 can exchange their LMC information with each other.
  • base station 1 and base station 2 can exchange their LMC information with each other when the interface is established.
  • base station 1 may be a source base station and base station 2 is a target base station; or, base station 1 may be a target base station and base station 2 is a source base station.
  • the target base station sends a second message to the source base station, and correspondingly, the source base station receives the second message sent by the target base station.
  • the second message includes whether the target base station supports LMC-based positioning and/or positioning quality of service (QoS) information supported by the target base station.
  • the positioning QoS information may include one or more of positioning delay, positioning accuracy, or QoS level.
  • the second message may be any one of an Xn establishment request message, an Xn establishment response message, or an access network node configuration update message.
  • the Xn establishment request message and the Xn establishment response message are messages during the establishment of the Xn interface between two base stations; when the configuration of a base station changes, the base station can notify the other base station through an access network node configuration update message.
  • the source base station may also determine the target base station according to LMC information sent by multiple base stations. For example, if the current UE has positioning based on LMC, when there are multiple candidate base stations to choose from, the source base station can preferentially select those target base stations that support LMC and meet the positioning QoS requirements to ensure the continuity of positioning.
  • the source base station determines to continue to perform the LMC-based positioning of the UE at the source base station: if the target base station does not support the LMC-based positioning; Or, the target base station does not meet the positioning service quality QoS requirements of the terminal device; or, the positioning type of the LMC-based positioning is RI-LR.
  • the positioning delay required by the positioning QoS of the UE is 300 milliseconds, but the target base station can only meet the delay of 500 milliseconds.
  • the originator of the LMC-based positioning is the source base station, the source base station may determine to continue to go to the source base station to perform positioning of the UE, so as to obtain the location information of the UE.
  • the target base station sends a handover request confirmation message to the source base station, and correspondingly, the source base station receives the handover request confirmation message sent by the target base station.
  • the source base station sends an RRC message to the UE; correspondingly, the UE receives the RRC message.
  • the RRC message is used to instruct the UE to switch to the target base station.
  • the RRC message may be an RRC reconfiguration message.
  • the UE can initiate a random access procedure and send an RRC reconfiguration complete message to the target base station. It can be understood that for the specific description of the UE initiating the random access process and sending the RRC reconfiguration complete message to the target base station, reference may be made to the method shown in FIG. 7, which will not be described in detail here.
  • the target base station will immediately send a context release message to the source base station to trigger the source base station to release the context of the UE.
  • the target base station may delay (that is, delay to step 808) or not send the context release message, that is, continue to maintain the connection between the UE's target base station and the source base station, so that the source The base station can obtain the positioning measurement result of the UE even after the handover. It can be understood that the following embodiments are applicable to the steps performed by the UE after receiving the RRC message.
  • the UE sends a fifth message to the target base station, and correspondingly, the target base station receives the fifth message.
  • the fifth message includes the positioning measurement result of the UE.
  • the fifth message may include an LPP message, and further, the LPP message includes a positioning measurement result, and the LPP message may be encapsulated in an RRC message (that is, encapsulated in the fifth message).
  • the target base station sends a first message to the source base station, and correspondingly, the source base station receives the first message sent by the target base station.
  • the first message includes the positioning measurement result of the terminal device.
  • the first message includes the LPP message in step 804, that is, the target base station forwards the LPP message or the positioning measurement result included in the fifth message in step 804 to the source base station.
  • the XnAP message may be used to transfer LPP messages between base stations, and the XnAP message may be an XnAP message associated with the UE, that is, an XnAP message sent through a UE connection between base stations. And the XnAP message may include the UE Xn interface application protocol identifier allocated by the source base station and the target base station respectively. That is, the first message may be a newly introduced XnAP message, and the XnAP message includes an LPP message.
  • the XnAP message is a general XnAP message used to transmit LPP messages, and may not be limited to only transmitting LPP messages including positioning measurement results.
  • the method for transferring LPP messages between base stations may not be coupled with the foregoing steps, that is, it may exist as an independent embodiment.
  • the source base station determines the location information of the terminal device according to the positioning measurement result.
  • the location of the UE can be used.
  • the source base station can send the location of the UE to the AMF.
  • the foregoing step 806 may also have different processing modes.
  • the deployment of the LMC is shown in Fig. 5a.
  • the source base station can directly determine the location information of the UE according to the positioning measurement result.
  • the deployment of the LMC is shown in Fig. 5b or Fig. 5c.
  • the source base station may also send the positioning measurement result to the LMC, and the LMC performs the measurement according to the positioning measurement.
  • the location information of the UE is determined.
  • the base station is used as an example for description in the following.
  • the method further includes:
  • the source base station sends a third message to the target base station, and correspondingly, the target base station receives the third message.
  • the third message is used to indicate that the LMC-based positioning has ended.
  • the third message is an XnAP message.
  • the source base station can send an XnAP message to the target base station through the Xn interface, and the XnAP message is used to indicate that positioning for the UE is over, so as to trigger the target base station to send context release to the source base station. information.
  • the target base station sends a context release message to the source base station, and correspondingly, the source base station receives the context release message sent by the target base station.
  • the foregoing steps 807 and 808 may also be replaced with: the source base station sends a fourth message to the target base station, and correspondingly, the target base station receives the fourth message.
  • the fourth message is used to indicate that the context of the terminal device has been released. That is, after the source base station obtains the location information of the UE, it can directly release the context of the UE and notify the target base station that the context of the UE has been released.
  • the target base station when the target base station does not support LMC-based positioning, by continuing to perform positioning at the source base station, the continuity of positioning is ensured. Specifically, through the exchange of respective LMC information between the base stations, it can be used for the source base station to select the target base station, and for the source base station to determine whether to continue to perform positioning at the source base station. And by carrying the first indication information in the handover request message, the source base station can promptly notify the target base station to adopt a reasonable way to handle positioning. And by delaying or not sending the context release message by the source base station, the source base station can obtain the positioning measurement result of the UE even after the handover.
  • step 801 and step 802 in FIG. 8 can also be replaced with:
  • the source base station sends a handover request message to the target base station.
  • the target base station receives the handover request message.
  • the handover request message is used to request the UE to be handed over to the target base station, the UE is in an LMC-based positioning state, and the handover request message includes the LMC-based positioning information.
  • the LMC-based positioning information includes one or more of positioning context information of the UE, positioning service quality QoS requirements of the UE, or positioning type.
  • the LMC-based positioning information may enable the target base station to determine whether to perform positioning at the target base station.
  • the LMC-based positioning information may be used to instruct the target base station to continue positioning.
  • the source base station receives a handover request confirmation message sent by the target base station, where the handover request confirmation message includes second indication information, where the second indication information is used to instruct the source base station to continue performing the LMC-based positioning of the UE .
  • the embodiment of the present application also provides a method for how the target base station determines whether to continue positioning. For example, before the target base station sends the handover request confirmation message to the source base station, the method further includes:
  • the target base station determines to continue to perform the LMC-based positioning of the terminal device at the source base station: the target base station does not support the LMC-based positioning; or, the target The base station does not meet the positioning service quality QoS requirements of the terminal equipment; or, the positioning type of the LMC-based positioning is the positioning request RI-LR triggered by the radio access network.
  • step 1003-step 1008 in FIG. 10 For the specific implementation of step 1003-step 1008 in FIG. 10, reference may be made to FIG. 8, which will not be described in detail here.
  • the target base station when the target base station does not support LMC-based positioning, by continuing to perform positioning at the source base station, the continuity of positioning is ensured. Specifically, through the exchange of respective LMC information between the base stations, it can be used for the source base station to select the target base station, and for the target base station to determine whether to continue positioning at the source base station. And by carrying the second indication information in the handover request confirmation message, the target base station can promptly notify the source base station to use a reasonable method to handle positioning. And by delaying or not sending the context release message by the target base station, the source base station can obtain the positioning measurement result of the UE even after the handover.
  • the target base station may perform positioning.
  • FIG. 11 is a schematic flowchart of a method for switching a network device according to an embodiment of the present application. This method can be applied to the deployment of the LMC shown in FIG. 5c, that is, the LMC is used as a logical node and is respectively connected to the source base station and the target base station through a new interface. As shown in FIG. 11, the method for switching network equipment includes at least:
  • the source base station sends a handover request message to the target base station.
  • the target base station receives the handover request message.
  • the handover request message is used to request the UE to be handed over to the target base station, the UE is in an LMC-based positioning state, and the handover request message includes the LMC-based positioning information.
  • the LMC-based positioning information includes the positioning context information of the terminal device, the positioning service quality QoS requirements of the terminal device, the positioning type, the identification ID of the source access network device, the positioning association identification ID allocated by the source base station or the LMC allocation Any one or more of the IDs in the application protocol ID.
  • the target base station sends a handover request confirmation message to the source base station, and correspondingly, the source base station receives the handover request confirmation message sent by the target base station.
  • the source base station sends an RRC message to the terminal device; correspondingly, the terminal device receives the RRC message.
  • the RRC message is used to instruct the terminal device to switch to the target base station.
  • the RRC message may include an RRC reconfiguration message.
  • the UE initiates a random access (random access) process to the target base station according to the foregoing RRC reconfiguration information. After successfully completing the random access procedure, the UE sends an RRC reconfiguration complete (RRC reconfiguration complete) message to the target base station.
  • RRC reconfiguration complete RRC reconfiguration complete
  • the target base station will immediately send a context release message to the source base station to trigger the source base station to release the context of the UE.
  • the target base station can be delayed (that is, after sending the location information of the UE to the source base station) or not send the context release message, that is Continue to maintain the connection between the target base station and the source base station of the UE, so that after the target base station obtains the location information of the UE, it can be sent to the source base station.
  • the target base station sends a request message (relocation request) to the LMC, and correspondingly, the LMC receives the request message.
  • the request message includes the location association identification ID allocated by the source access network device and/or the interface application protocol identification ID allocated by the LMC.
  • the request message may also include the identification ID of the source base station.
  • the LMC can determine which source base station allocates the location association identification ID.
  • the LMC can determine the location context of the UE, thereby finding the location context when the source base station performs positioning to ensure that the LMC continues Perform positioning.
  • the LMC sends a response message to the target base station, and correspondingly, the target base station receives the response message.
  • the terminal device sends a fifth message to the LMC, and correspondingly, the LMC receives the fifth message; the fifth message includes the positioning measurement result of the UE.
  • the LMC determines the location information of the UE according to the positioning measurement result of the UE.
  • the LMC sends the location information of the UE to the target base station, and correspondingly, the target base station receives the location information of the UE.
  • the target base station may also send the location information of the UE to the source base station, and correspondingly, the source base station receives the location information of the UE.
  • a new XnAP message can be introduced. This XnAP message can be used to transfer UE location information between base stations.
  • the XnAP message can be the XnAP message associated with the UE or It is the XnAP message sent through the UE connection between the base stations. That is, the first message may be a newly introduced XnAP message associated with a UE, and the XnAP message includes the location information of the UE.
  • the target base station sends the location information of the UE to the source base station.
  • the target base station may send a context release message to the source base station.
  • the source base station receives the context release message and releases the context of the UE.
  • the target base station may send the location information of the UE to the UE.
  • the target base station after receiving the RRC reconfiguration complete message, can send a context release message to the source base station.
  • the instruction information indicates to continue positioning at the source base station.
  • the source base station and the target base station can default/appoint to perform positioning at the target base station.
  • the source base station and the target base station can also default/appoint to continue positioning at the source base station, while in method two, the target base station can also be instructed to perform positioning at the target base station through indication information. Therefore, the method shown in FIG. 11 should not be understood as a limitation of the present application.
  • the technical solution provided by this application by carrying the positioning association ID allocated by the source base station or the interface application protocol identifier allocated by the LMC in the handover request message, the LMC can find the corresponding positioning context, so that the positioning can continue. And by carrying the positioning type in the handover request message, the XnAP message is introduced between the base stations for the target base station to send the location information of the UE to the source base station, thereby realizing the continuity of positioning.
  • the source base station or the target base station may determine to stop performing positioning.
  • this application may include the following embodiments:
  • the method for switching network devices includes:
  • the source base station determines to stop continuing to perform LMC-based positioning.
  • the condition that the source base station determines to stop continuing to perform LMC-based positioning of the UE may include any one or more of the following: the target base station does not support LMC-based positioning, the source base station decides to stop positioning; or, the target base station LMC-based positioning is supported, but the current UE positioning QoS requirements are not supported, the source base station decides to stop positioning; or, if the positioning type is the positioning for the UE initiated by the source base station (i.e., RI-LR positioning), then after the handover, the UE If the location information is no longer useful, the source base station decides to stop positioning; or, the current handover based on N2 or AMF change; or, the positioning type is MT-LR or NI-LR, then the source base station decides to stop positioning.
  • the positioning type is the positioning for the UE initiated by the source base station (i.e., RI-LR positioning)
  • the target base station cannot send the location of the UE to the serving AMF of the source base station.
  • the target base station and the source base station are connected to different LMCs, but LMC relocation is not supported. It can be understood that the following embodiments are also applicable to the conditions under which the source base station determines to stop positioning.
  • the source base station sends a sixth message to the UE.
  • the UE receives the sixth message; the sixth message is used to instruct to stop performing LMC-based positioning.
  • the sixth message may include an LPP message, and further, the LPP message may include an abort message. That is, the sixth message may be used to instruct the UE to stop continuing to perform LMC-based positioning, so that the UE releases positioning-related configuration, such as positioning reference signal configuration.
  • the UE stops performing LMC-based positioning and releases related configurations.
  • the source base station sends a handover request message to the target base station, and correspondingly, the target base station receives the handover request message.
  • the target base station sends a handover request confirmation message to the source base station, and correspondingly, the source base station receives the handover request confirmation message.
  • the source base station sends an RRC reconfiguration message to the UE, and correspondingly, the UE receives the RRC reconfiguration message.
  • the method for switching network devices includes:
  • the source base station determines to stop continuing to perform LMC-based positioning.
  • the source base station sends a handover request message to the target base station, and correspondingly, the target base station receives the handover request message.
  • the handover request message includes an LPP message for stopping positioning.
  • the LPP message may include an abort message.
  • the abort message can be used as an information element in the form of a byte stream in the handover request message. It can be understood that the source base station can determine the conditions for stopping the positioning as in the method shown in FIG. 12, which will not be described in detail here.
  • the target base station sends a handover request confirmation message to the source base station, and correspondingly, the source base station receives the handover request confirmation message.
  • the handover request confirmation message includes an LPP message for stopping positioning.
  • the abort message may be encapsulated in the RRC reconfiguration message in the handover request confirmation message, and then sent to the source base station.
  • the source base station reads the RRC reconfiguration message in the handover request confirmation message, and then sends the RRC reconfiguration message to the UE, and correspondingly, the UE receives the RRC reconfiguration message.
  • the RRC reconfiguration message includes an LPP message used to stop positioning, such as an abort message.
  • the UE stops performing LMC-based positioning and releases related configurations.
  • the source base station decides to stop positioning; and the source base station generates an LPP message for stopping positioning, such as an abort message, and then sends a handover request message to the target base station, and the handover request message carries the abort message.
  • the target base station encapsulates the abort message in an RRC reconfiguration message, the RRC reconfiguration message is included in the handover request confirmation message and sent to the source base station, and then the source base station sends the RRC reconfiguration message to the UE.
  • the UE stops positioning according to the abort message in the RRC reconfiguration message, and releases the related configuration.
  • the method for switching network devices at least includes:
  • a source base station sends a handover request message to a target base station, and correspondingly, the target base station receives the handover request message.
  • the handover request message includes third indication information
  • the third indication information is used to instruct to stop positioning based on the LMC.
  • the third indication information may be 1 bit, such as 0 or 1 for stopping positioning.
  • the target base station sends a handover request confirmation message to the source base station, and correspondingly, the source base station receives the handover request confirmation message.
  • the handover request confirmation message includes an RRC reconfiguration message
  • the RRC reconfiguration message includes third indication information.
  • the source base station reads the RRC reconfiguration message in the handover request confirmation message, and then sends the RRC reconfiguration message to the UE, and correspondingly, the UE receives the RRC reconfiguration message.
  • the RRC reconfiguration message includes third indication information.
  • the UE stops performing LMC-based positioning according to the third indication information in the RRC reconfiguration message, and releases related configurations.
  • the source base station decides to stop positioning; and the source base station sends a handover request message to the target base station, the handover request message carries third indication information, and the third indication information is used to instruct to stop positioning.
  • the third indication information is included in the RRC reconfiguration message
  • the RRC reconfiguration message is included in the handover request confirmation message, and then the source base station sends the RRC reconfiguration message to the UE.
  • the UE stops positioning according to the third indication information in the RRC reconfiguration message, and releases the related configuration.
  • the method for switching network devices at least includes:
  • the source base station sends a handover request message to a target base station, and correspondingly, the target base station receives the handover request message.
  • the handover request message includes LMC-based positioning information.
  • the LMC-based positioning information includes any one or more of the UE's positioning context, positioning QoS information, or positioning type.
  • the LMC-based positioning information may be used to instruct the target base station to determine whether to stop performing the LMC-based positioning according to the LMC-based positioning information.
  • the condition for the target base station to determine to stop LMC-based positioning may include any one or more of the following: the target base station does not support LMC-based positioning, then the target base station decides to stop positioning; or, the target base station supports LMC-based positioning but does not Support the current UE's positioning QoS requirements, the target base station decides to stop positioning; or, the positioning type is the positioning for the UE initiated by the source base station (i.e. RI-LR positioning). After the handover, the UE's location information is no longer useful, then the target The base station decides to stop positioning.
  • the target base station sends a handover request confirmation message to the source base station, and correspondingly, the source base station receives the handover request confirmation message.
  • the handover request confirmation message includes an RRC reconfiguration message
  • the RRC reconfiguration message includes fourth indication information
  • the fourth indication information is used to instruct to stop positioning based on the LMC.
  • the source base station reads the RRC reconfiguration message in the handover request confirmation message, and then sends the RRC reconfiguration message to the UE, and correspondingly, the UE receives the RRC reconfiguration message.
  • the RRC reconfiguration message includes fourth indication information.
  • the UE stops performing LMC-based positioning according to the fourth indication information in the RRC reconfiguration message, and releases related configurations.
  • the source base station or the target base station decides whether to stop positioning, and informs the other party whether to stop positioning by carrying indication information in a handover request message or a handover request confirmation message.
  • the indication information or abort message is carried in the RRC reconfiguration message to instruct the UE to stop positioning measurement.
  • FIG. 16 is a schematic structural diagram of a communication device provided by an embodiment of the present application. As shown in FIG. 16, the communication device includes a sending unit 1601, a receiving unit 1602, and a processing unit 1603.
  • the sending unit 1601 is configured to send a handover request message to the target access network device; wherein the handover request message is used to request the terminal device to be switched to the target access network device, and the terminal device is in a location-based The positioning state of the management component LMC; and the handover request message includes first indication information, the first indication information is used to instruct to continue to perform the LMC-based positioning of the terminal device on the communication device;
  • the receiving unit 1602 is configured to receive a handover request confirmation message sent by the target access network device
  • the sending unit 1601 is further configured to send a radio resource control RRC message to the terminal device; wherein, the RRC message is used to instruct the terminal device to switch to the target access network device;
  • the receiving unit 1602 is further configured to receive a first message sent by the target access network device, where the first message includes the positioning measurement result of the terminal device.
  • the processing unit 1603 is configured to determine to continue to perform the LMC-based positioning of the terminal device on the communication device when any one or more of the following conditions are met:
  • the target access network device does not support the LMC-based positioning; or, the target access network device does not meet the positioning service quality QoS requirements of the terminal device; or, the positioning type of the LMC-based positioning is radio access network triggering Location request RI-LR.
  • the receiving unit 1602 is further configured to receive a second message sent by the target access network device; wherein, the second message includes whether the target access network device supports the LMC-based Positioning and/or positioning QoS information supported by the target access network device.
  • the processing unit 1603 is further configured to determine the location information of the terminal device according to the positioning measurement result.
  • the sending unit 1601 is further configured to send a third message to the target access network device, where the third message is used to indicate that the LMC-based positioning has ended; the receiving unit 1602 also It is used to receive the context release message sent by the target access network device.
  • the sending unit 1601 is further configured to send a fourth message to the target access network device, where the fourth message is used to indicate that the context of the terminal device has been released.
  • the second message is any one of an Xn establishment request message, an Xn establishment response message, or an access network node configuration update message.
  • the sending unit 1601 is configured to send a handover request message to the target access network device; where the handover request message is used to request the terminal device to be switched to the target access network device, The terminal device is in a positioning state based on the positioning management component LMC, and the handover request message includes the LMC-based positioning information;
  • the receiving unit 1602 is configured to receive a handover request confirmation message sent by the target access network device, where the handover request confirmation message includes second indication information, and the second indication information is used to instruct the communication apparatus to continue to perform the operation of the terminal device.
  • the positioning based on LMC;
  • the sending unit 1601 is further configured to send a radio resource control RRC message to the terminal device, where the RRC message is used to instruct the terminal device to switch to the target access network device;
  • the receiving unit 1602 is further configured to receive a first message sent by the target access network device, where the first message includes the positioning measurement result of the terminal device.
  • the LMC-based positioning information includes one or more of the positioning context information of the terminal device, the positioning service quality QoS requirement of the terminal device, or the positioning type.
  • the processing unit 1603 is configured to determine the location information of the terminal device according to the positioning measurement result.
  • the sending unit 1601 is further configured to send a third message to the target access network device, where the third message is used to indicate that the LMC-based positioning has ended;
  • the receiving unit 1602 is also configured to receive a context release message sent by the target access network device.
  • the sending unit 1601 is further configured to send a fourth message to the target access network device, where the fourth message is used to indicate that the context of the terminal device has been released.
  • the sending unit 1601 is configured to send a handover request message to the target access network device; where the handover request message is used to request the terminal device to be switched to the target access network device, The terminal device is in a positioning state based on the positioning management component LMC, and the handover request message includes the LMC-based positioning information;
  • the receiving unit 1602 is configured to receive a handover request confirmation message sent by the target access network device
  • the sending unit 1601 is also used to send a radio resource control RRC message to the terminal device, where the RRC message is used to instruct handover to the target access network device.
  • the LMC-based positioning information includes the positioning context information of the terminal device, the positioning service quality QoS requirements of the terminal device, the positioning type, the identification ID of the source access network device, and the communication device Any one or more of the assigned location association identification ID or the interface application protocol identification ID assigned by the LMC.
  • the receiving unit 1602 is further configured to receive the location information of the terminal device sent by the target access network device;
  • the receiving unit 1602 is also configured to receive a context release message sent by the target access network device.
  • the processing unit 1603 may be one or more processors, and the sending unit 1601 may be a transmitter.
  • the receiving unit 1602 may be a receiver, or the sending unit 1601 and the receiving unit 1602 can be integrated into a device, such as a transceiver.
  • the processing unit 1603 can be one or more processors, the sending unit 1601 can be an output interface, and the receiving unit 1602 can be an input interface, or the sending unit 1601 and the receiving unit 1602 are integrated into one unit, for example Input and output interface.
  • the receiving unit 1602 is configured to receive a handover request message sent by the source access network device; where the handover request message is used to request the terminal device to be switched to the communication device, and the terminal The device is in a positioning state based on the positioning management component LMC; and the handover request message includes first indication information, the first indication information is used to instruct to continue to perform the LMC-based positioning of the terminal device on the source access network device ;
  • the sending unit 1601 is configured to send a handover request confirmation message to the source access network device
  • the receiving unit 1602 is further configured to receive a fifth message sent by the terminal device, where the fifth message includes the positioning measurement result of the terminal device;
  • the sending unit 1601 is further configured to send a first message to the source access network device, where the first message includes the positioning measurement result of the terminal device.
  • the sending unit 1601 is further configured to send a second message to the source access network device; wherein, the second message includes whether the communication device supports the LMC-based positioning and/or Positioning QoS information supported by the communication device.
  • the receiving unit 1602 is further configured to receive a third message sent by the source access network device, and the third message is used to indicate that the LMC-based positioning has ended; the sending unit 1601, It is also used to send a context release message to the source access network device.
  • the receiving unit 1602 is further configured to receive a fourth message sent by the source access network device, where the fourth message is used to indicate that the context of the terminal device has been released.
  • the second message is any one of an Xn establishment request message, an Xn establishment response message, or an access network node configuration update message.
  • the receiving unit 1602 is configured to receive a handover request message sent by the source access network device; where the handover request message is used to request the terminal device to be switched to the communication device, and the terminal The device is in a positioning state based on the positioning management component LMC, and the handover request message includes the LMC-based positioning information;
  • the sending unit 1601 is configured to send a handover request confirmation message to the source access network device, where the handover request confirmation message includes second indication information, and the second indication information is used to instruct the source access network device to continue executing the terminal
  • the receiving unit 1602 is further configured to receive a fifth message sent by the terminal device, where the fifth message includes the positioning measurement result of the terminal device;
  • the sending unit 1601 is further configured to send a first message to the source access network device, where the first message includes the positioning measurement result of the terminal device.
  • the processing unit 1603 is configured to determine to continue to perform the LMC-based positioning of the terminal device on the source access network device when any one or more of the following conditions are met:
  • the communication device does not support the LMC-based positioning; or, the communication device does not meet the positioning service quality QoS requirements of the terminal equipment; or, the positioning type of the LMC-based positioning is the positioning request RI-LR triggered by the radio access network .
  • the receiving unit 1602 is further configured to receive a third message sent by the source access network device, where the third message is used to indicate that the LMC-based positioning has ended;
  • the sending unit is also used to send a context release message to the source access network device.
  • the receiving unit 1602 is further configured to receive a fourth message sent by the source access network device, where the fourth message is used to indicate that the context of the terminal device has been released.
  • the receiving unit 1602 is configured to receive a handover request message sent by the source access network device; where the handover request message is used to request the terminal device to be switched to the communication device, and the terminal The device is in a positioning state based on the positioning management component LMC, and the handover request message includes the LMC-based positioning information;
  • the sending unit 1601 is configured to send a handover request confirmation message to the source access network device
  • the receiving unit 1602 is also configured to receive the location information of the terminal device sent by the LMC.
  • the LMC-based positioning information includes the positioning context information of the terminal device, the positioning service quality QoS requirements of the terminal device, the positioning type, the identification ID of the source access network device, and the source access Any one or more of the location association identification ID allocated by the networked device or the interface application protocol identification ID allocated by the LMC.
  • the sending unit 1601 is also used to send the location information of the terminal device to the source access device; the sending unit 1601 is also used to send a context release message to the source access network device .
  • the processing unit 1603 may be one or more processors, and the sending unit 1601 may be a transmitter.
  • the receiving unit 1602 may be a receiver, or the sending unit 1601 and the receiving unit 1602 can be integrated into a device, such as a transceiver.
  • the processing unit 1603 can be one or more processors, the sending unit 1601 can be an output interface, and the receiving unit 1602 can be an input interface, or the sending unit 1601 and the receiving unit 1602 are integrated into one unit, for example Input and output interface.
  • the receiving unit 1602 is configured to receive a request message sent from the target access network device; wherein, the request message includes the location association identification ID and/or assigned by the source access network device. Or the interface application protocol identification ID assigned by the LMC;
  • the processing unit 1603 is configured to determine the location context of the terminal device based on the location association identification ID and/or the interface application protocol identification ID;
  • the sending unit 1601 is configured to send a response message to the target access network device.
  • the receiving unit 1602 is further configured to receive a fifth message sent by the terminal device, where the fifth message includes the positioning measurement result of the terminal device;
  • the processing unit 1603 is further configured to determine the location information of the terminal device according to the positioning measurement result of the terminal device;
  • the sending unit 1601 is also used to send the location information of the terminal device to the target access network device.
  • the processing unit 1603 may be one or more processors, the sending unit 1601 may be a transmitter, and the receiving unit 1602 may be a receiver. , Or the sending unit 1601 and the receiving unit 1602 are integrated into one device, such as a transceiver.
  • the processing unit 1603 can be one or more processors or processing circuits, etc.
  • the sending unit 1601 can be an output interface
  • the receiving unit 1602 can be an input interface
  • the sending unit 1601 and the receiving unit 1602 are integrated In a unit, such as input/output interface or interface circuit, etc.
  • FIG. 17 is a schematic structural diagram of a communication device 170 provided by an embodiment of the present application, which can be used to implement the function of the network device in the foregoing method. It can be understood that the network device may be a source access network device; or a target access network device; or an LMC.
  • the apparatus 170 includes at least one processor 1720, configured to implement the function of the network device in the method provided in the embodiment of the present application. Specifically, the processor 1720 can implement the functions of the processing unit shown in FIG. 16.
  • the device 170 may also include a transceiver 1710. The transceiver is used to communicate with other devices through the transmission medium.
  • the processor 1720 uses the transceiver 1710 to send and receive data, and is used to implement the functions of the receiving unit and/or the sending unit shown in FIG. 16.
  • the device 170 may also include at least one memory 1730 for storing program instructions and/or data.
  • the memory 1730 and the processor 1720 are coupled.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 1720 may operate in cooperation with the memory 1730.
  • the processor 1720 may execute program instructions stored in the memory 1730. At least one of the at least one memory may be included in the processor.
  • the embodiment of the present application does not limit the specific connection medium between the transceiver 1710, the processor 1720, and the memory 1730.
  • the memory 1730, the processor 1720, and the transceiver 1710 are connected by a bus 1740.
  • the bus is represented by a thick line in FIG. 17, and the connection mode between other components is only for schematic illustration , Is not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and so on. For ease of representation, only one thick line is used in FIG. 17, but it does not mean that there is only one bus or one type of bus.
  • the disclosed system, device, and method can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments of the present application.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of this application is essentially or the part that contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium. It includes several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disks or optical disks and other media that can store program codes. .
  • this application also provides a computer program, which is used to perform the operations and/or processing performed by the source access network device in the network device switching method provided in this application.
  • This application also provides a computer program, which is used to perform operations and/or processing performed by the target access network device in the network device switching method provided in this application.
  • This application also provides a computer program for executing operations and/or processing performed by the LMC in the method for switching network devices provided by this application.
  • This application also provides a computer-readable storage medium that stores computer instructions.
  • the computer instructions run on the computer, the computer can execute the method for switching network devices provided by this application. The operation and/or processing performed by the connected device.
  • This application also provides a computer-readable storage medium that stores computer instructions.
  • the computer instructions run on the computer, the computer can execute the method for switching network devices provided in this application to be accessed by the target. Operations and/or processing performed by the network equipment.
  • This application also provides a computer-readable storage medium that stores computer instructions, which when the computer instructions run on the computer, cause the computer to execute the network device switching method provided in this application by the LMC Operation and/or processing.
  • the present application also provides a computer program product, the computer program product including computer code or instructions, when the computer code or instructions run on a computer, the method for switching network devices in the method embodiment of the present application is implemented.
  • This application also provides a wireless communication system, including the source access network device and the target access network device in the embodiment of this application.

Landscapes

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

Abstract

本申请提供了一种网络设备切换的方法及装置,该方法可以应用于终端设备从源接入网设备切换到目标接入网设备的场景下,既保证了该终端设备能够完成切换,又保证了定位的连续性。具体的,该源接入网设备通过在切换请求消息中包括第一指示信息,可使得该目标接入网设备在接收到该第一指示信息时,得知该源接入网设备继续执行对终端设备的基于LMC的定位。其中,该切换请求消息用于请求将终端设备切换到该目标接入网设备。进一步的,该目标接入网设备在接收到该终端设备发送的定位测量结果后,便可以将该定位测量结果发送给该源接入网设备。

Description

一种网络设备切换的方法及装置 技术领域
本申请涉及通信技术领域,特别涉及一种网络设备切换的方法及装置。
背景技术
在移动通信系统中,连接态终端设备的移动性管理由网络设备控制。例如,网络设备可以控制终端设备切换到哪个小区以及如何进行切换等。具体的,终端设备通过与源接入网设备或目标接入网设备交互,可以断开与源接入网设备之间的连接,以及接入目标接入网设备。
同时,在移动通信系统中,在定位过程中,不仅需要终端设备的参与,还需要接入网设备以及核心网设备参与。例如,终端设备需要获取接入网设备发送的定位参考信号,以及接入网设备需要从终端设备获取该终端设备的定位测量结果等。
因此,在切换场景下,如果终端设备处于定位状态,则如何保证定位的连续性是需要解决的问题。
发明内容
本申请提供了一种网络设备切换的方法及装置,可在切换场景下,保证定位的连续性。
第一方面,本申请提供一种网络设备切换的方法,所述方法包括:
源接入网设备向目标接入网设备发送切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述目标接入网设备,所述终端设备处于基于定位管理组件或定位管理组件(location management component,LMC)的定位状态;且所述切换请求消息中包括第一指示信息,所述第一指示信息用于指示继续在所述源接入网设备执行对所述终端设备的所述基于LMC的定位;
以及所述源接入网设备接收所述目标接入网设备发送的切换请求确认消息;所述源接入网设备向所述终端设备发送指示消息;其中,所述指示消息用于指示所述终端设备切换到所述目标接入网设备;所述源接入网设备接收所述目标接入网设备发送的第一消息,所述第一消息中包括所述终端设备的定位测量结果。
本申请提供的技术方案:可以应用于终端设备从源接入网设备切换到目标接入网设备的场景下,既保证了该终端设备能够完成切换,又保证了定位的连续性。具体地,该源接入网设备通过在切换请求消息中包括第一指示信息,可使得该目标接入网设备在接收到该第一指示信息时,得知该源接入网设备继续执行对终端设备的基于LMC的定位。进一步的,该目标接入网设备在接收到该终端设备发送的定位测量结果后,便可以将该定位测量结果发送给该源接入网设备。
在一种可能的实现方式中,所述源接入网设备向目标接入网设备发送切换请求消息之前,所述方法还包括:在满足如下条件中的任一项或多项时,所述源接入网设备确定继续在所述源接入网设备执行对所述终端设备的所述基于LMC的定位:
所述目标接入网设备不支持所述基于LMC的定位;或者,所述目标接入网设备不满足所述终端设备的定位服务质量QoS要求;或者,所述基于LMC的定位的定位类型为无 线接入网触发的定位请求RI-LR。
在一种可能的实现方式中,所述源接入网设备向目标接入网设备发送切换请求消息之前,所述方法还包括:所述源接入网设备接收所述目标接入网设备发送的第二消息;其中,所述第二消息中包括所述目标接入网设备是否支持所述基于LMC的定位和/或所述目标接入网设备支持的定位QoS信息。
在一种可能的实现方式中,所述源接入网设备接收所述目标接入网设备发送的第一消息之后,所述方法还包括:所述源接入网设备根据所述定位测量结果确定所述终端设备的位置信息。
在一种可能的实现方式中,所述源接入网设备接收所述目标接入网设备发送的第一消息之后,所述方法还包括:
所述源接入网设备向所述目标接入网设备发送第三消息,所述第三消息用于指示所述基于LMC的定位已结束;所述源接入网设备接收所述目标接入网设备发送的上下文释放消息;或者,
所述源接入网设备向所述目标接入网设备发送第四消息,所述第四消息用于指示所述终端设备的上下文已被释放。
在一种可能的实现方式中,所述第二消息为Xn建立请求消息、Xn建立响应消息或接入网节点配置更新消息中的任一项。
第二方面,本申请提供一种网络设备切换的方法,所述方法包括:
目标接入网设备接收源接入网设备发送的切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述目标接入网设备,所述终端设备处于基于定位管理组件LMC的定位状态;且所述切换请求消息中包括第一指示信息,所述第一指示信息用于指示继续在所述源接入网设备执行对所述终端设备的所述基于LMC的定位;
以及所述目标接入网设备向所述源接入网设备发送切换请求确认消息;所述目标接入网设备接收所述终端设备发送的第五消息,所述第五消息中包括所述终端设备的定位测量结果;所述目标接入网设备向所述源接入网设备发送第一消息,所述第一消息中包括所述终端设备的定位测量结果。
在一种可能的实现方式中,所述目标接入网设备接收源接入网设备发送的切换请求消息之前,所述方法还包括:所述目标接入网设备向所述源接入网设备发送第二消息;其中,所述第二消息中包括所述目标接入网设备是否支持所述基于LMC的定位和/或所述目标接入网设备支持的定位QoS信息。
在一种可能的实现方式中,所述目标接入网设备向所述源接入网设备发送第一消息之后,所述方法还包括:
所述目标接入网设备接收所述源接入网设备发送的第三消息,所述第三消息用于指示所述基于LMC的定位已结束;所述目标接入网设备向所述源接入网设备发送上下文释放消息;或者,
所述目标接入网设备接收所述源接入网设备发送的第四消息,所述第四消息用于指示所述终端设备的上下文已被释放。
在一种可能的实现方式中,所述第二消息为Xn建立请求消息、Xn建立响应消息或接入网节点配置更新消息中的任一项。
第三方面,本申请提供一种网络设备切换的方法,所述方法包括:
源接入网设备向目标接入网设备发送切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述目标接入网设备,所述终端设备处于基于定位管理组件LMC的定位状态,且所述切换请求消息中包括所述基于LMC的定位信息;
所述源接入网设备接收所述目标接入网设备发送的切换请求确认消息,所述切换请求确认消息中包括第二指示信息,所述第二指示信息用于指示所述源接入网设备继续执行对所述终端设备的所述基于LMC的定位;
以及所述源接入网设备向所述终端设备发送指示消息,所述指示消息用于指示所述终端设备切换到所述目标接入网设备;所述源接入网设备接收所述目标接入网设备发送的第一消息,所述第一消息中包括终端设备的定位测量结果。
在一种可能的实现方式中,所述基于LMC的定位信息包括所述终端设备的定位上下文信息、所述终端设备的定位服务质量QoS要求或定位类型中的一项或多项。
在一种可能的实现方式中,所述源接入网设备接收所述目标接入网设备发送的第一消息之后,所述方法还包括:所述源接入网设备根据所述定位测量结果确定所述终端设备的位置信息。
在一种可能的实现方式中,所述源接入网设备接收所述目标接入网设备发送的第一消息之后,所述方法还包括:
所述源接入网设备向所述目标接入网设备发送第三消息,所述第三消息用于指示所述基于LMC的定位已结束;所述源接入网设备接收所述目标接入网设备发送的上下文释放消息;或者,
所述源接入网设备向所述目标接入网设备发送第四消息,所述第四消息用于指示所述终端设备的上下文已被释放。
第四方面,本申请提供一种网络设备的切换方法,所述方法包括:
目标接入网设备接收源接入网设备发送的切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述目标接入网设备,所述终端设备处于基于定位管理组件LMC的定位状态,且所述切换请求消息中包括所述基于LMC的定位信息;
所述目标接入网设备向所述源接入网设备发送切换请求确认消息,所述切换请求确认消息中包括第二指示信息,所述第二指示信息用于指示所述源接入网设备继续执行对所述终端设备的所述基于LMC的定位;
以及所述目标接入网设备接收所述终端设备发送的第五消息,所述第五消息中包括所述终端设备的定位测量结果;所述目标接入网设备向所述源接入网设备发送第一消息,所述第一消息中包括所述终端设备的定位测量结果。
在一种可能的实现方式中,所述目标接入网设备向所述源接入网设备发送切换请求确认消息之前,所述方法还包括:在满足如下条件中的任一项或多项时,所述目标接入网设备确定继续在所述源接入网设备执行对所述终端设备的所述基于LMC的定位;
所述目标接入网设备不支持所述基于LMC的定位;或者,所述目标接入网设备不满足所述终端设备的定位服务质量QoS要求;或者,所述基于LMC的定位的定位类型为无线接入网触发的定位请求RI-LR。
在一种可能的实现方式中,所述目标接入网设备向所述源接入网设备发送第一消息之后,所述方法还包括:
所述目标接入网设备接收所述源接入网设备发送的第三消息,所述第三消息用于指示 所述基于LMC的定位已结束;所述目标接入网设备向所述源接入网设备发送上下文释放消息;或者,
所述目标接入网设备接收所述源接入网设备发送的第四消息,所述第四消息用于指示所述终端设备的上下文已被释放。
第五方面,本申请提供一种网络设备切换的方法,所述方法包括:
源接入网设备向目标接入网设备发送切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述目标接入网设备,所述终端设备处于基于定位管理组件LMC的定位状态,且所述切换请求消息中包括所述基于LMC的定位信息;
以及所述源接入网设备接收所述目标接入网设备发送的切换请求确认消息;所述源接入网设备向终端设备发送指示消息,所述指示消息用于指示切换到所述目标接入网设备。
在一种可能的实现方式中,所述基于LMC的定位信息包括所述终端设备的定位上下文信息、所述终端设备的定位服务质量QoS要求、定位类型、所述源接入网络设备的标识ID、所述源接入网设备分配的定位关联标识ID或LMC分配的接口应用协议标识ID中的任一项或多项。
在一种可能的实现方式中,所述方法还包括:所述源接入网设备接收所述目标接入网设备发送的所述终端设备的位置信息;所述源接入网设备接收所述目标接入网设备发送的上下文释放消息。
第六方面,本申请提供一种网络设备切换的方法,所述方法包括:
目标接入网设备接收源接入网设备发送的切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述目标接入网设备,所述终端设备处于基于定位管理组件LMC的定位状态,且所述切换请求消息中包括所述基于LMC的定位信息;
以及所述目标接入网设备向所述源接入网设备发送切换请求确认消息;所述目标接入网设备接收所述LMC发送的所述终端设备的位置信息。
在一种可能的实现方式中,所述基于LMC的定位信息包括所述终端设备的定位上下文信息、所述终端设备的定位服务质量QoS要求、定位类型、所述源接入网络设备的标识ID、所述源接入网设备分配的定位关联标识ID或LMC分配的接口应用协议标识ID中的任一项或多项。
在一种可能的实现方式中,所述方法还包括:所述目标接入网设备向所述源接入设备发送所述终端设备的位置信息;所述目标接入网设备向所述源接入网设备发送上下文释放消息。
第七方面,本申请提供一种网络设备切换的方法,所述方法包括:
定位管理组件LMC接收来自目标接入网设备发送的请求消息;其中,所述请求消息中包括源接入网设备分配的定位关联标识ID和/或所述LMC分配的接口应用协议标识ID;
基于所述定位关联标识ID和/或所述接口应用协议标识ID确定终端设备的定位上下文;
所述LMC向所述目标接入网设备发送响应消息。
在一种可能的实现方式中,所述方法还包括:所述LMC接收所述终端设备发送的第五消息,所述第五消息中包括所述终端设备的定位测量结果;所述LMC根据所述终端设备的定位测量结果确定所述终端设备的位置信息;所述LMC向所述目标接入网设备发送所述终端设备的位置信息。
第八方面,本申请提供一种通信装置,用于执行第一方面或第一方面的任意可能的实现方式中的方法。具体的,所述通信装置包括具有执行第一方面或第一方面的任意可能的实现方式中的方法的相应单元。
第九方面,本申请提供一种通信装置,用于执行第三方面或第三方面的任意可能的实现方式中的方法。具体的,所述通信装置包括具有执行第三方面或第三方面的任意可能的实现方式中的方法的相应单元。
第十方面,本申请提供一种通信装置,用于执行第五方面或第五方面的任意可能的实现方式中的方法。具体的,所述通信装置包括具有执行第五方面或第五方面的任意可能的实现方式中的方法的相应单元。
可选的,上述第八方面、第九方面和第十方面所述的通信装置包括源接入网设备。
第十一方面,本申请提供一种通信装置,用于执行第二方面或第二方面的任意可能的实现方式中的方法。具体的,所述通信装置包括具有执行第二方面或第二方面的任意可能的实现方式中的方法的相应单元。
第十二方面,本申请提供一种通信装置,用于执行第四方面或第四方面的任意可能的实现方式中的方法。具体的,所述通信装置包括具有执行第四方面或第四方面的任意可能的实现方式中的方法的相应单元。
第十三方面,本申请提供一种通信装置,用于执行第六方面或第六方面的任意可能的实现方式中的方法。具体的,所述通信装置包括具有执行第六方面或第六方面的任意可能的实现方式中的方法的相应单元。
可选的,上述第十一方面、第十二方面和第十三方面所述的通信装置包括目标接入网设备。
第十四方面,本申请提供一种通信装置,用于执行第七方面或第七方面的任意可能的实现方式中的方法。具体的,所述通信装置包括具有执行第七方面或第七方面的任意可能的实现方式中的方法的相应单元。
可选的,该通信装置包括LMC。
第十五方面,本申请提供一种通信装置,所述通信装置包括处理器、存储器和收发器,所述收发器,用于接收信号或者发送信号;所述存储器,用于存储程序代码;
所述处理器,用于调用所述程序代码执行如第一方面或第一方面的各种可能的实现方式所述的方法;或者,所述处理器,用于调用所述程序代码执行如第三方面或第三方面的各种可能的实现方式所述的方法;或者,所述处理器,用于调用所述程序代码执行如第五方面或第五方面的各种可能的实现方式所述的方法。
第十六方面,本申请提供一种通信装置,所述通信装置包括处理器、存储器和收发器,所述收发器,用于接收信号或者发送信号;所述存储器,用于存储程序代码;
所述处理器,用于调用所述程序代码执行如第二方面或第二方面的各种可能的实现方式所述的方法;或者,所述处理器,用于调用所述程序代码执行如第四方面或第四方面的各种可能的实现方式所述的方法;或者,所述处理器,用于调用所述程序代码执行如第六方面或第六方面的各种可能的实现方式所述的方法。
第十七方面,本申请提供一种通信装置,所述通信装置包括处理器和接口电路;所述接口电路,用于接收代码指令;
所述处理器用于运行所述代码指令以使所述通信装置执行如第一方面或第一方面的 各种可能的实现方式所述的方法;或者,所述处理器用于运行所述代码指令以使所述通信装置执行如第三方面或第三方面的各种可能的实现方式所述的方法;或者,所述处理器用于运行所述代码指令以使所述通信装置执行如第五方面或第五方面的各种可能的实现方式所述的方法。
第十八方面,本申请提供一种通信装置,所述通信装置包括处理器和接口电路;所述接口电路,用于接收代码指令;
所述处理器用于运行所述代码指令以使所述通信装置执行如第二方面或第二方面的各种可能的实现方式所述的方法;或者,所述处理器用于运行所述代码指令以使所述通信装置执行如第四方面或第四方面的各种可能的实现方式所述的方法;或者,所述处理器用于运行所述代码指令以使所述通信装置执行如第六方面或第六方面的各种可能的实现方式所述的方法。
第十九方面,本申请提供一种通信装置,所述通信装置包括处理器和接口电路;所述接口电路,用于接收代码指令;所述处理器用于运行所述代码指令以使所述通信装置执行如第七方面或第七方面的各种可能的实现方式所述的方法。
第二十方面,本申请提供一种计算机可读存储介质,所述计算机可读存储介质用于存储指令或计算机程序,当所述指令或所述计算机程序被执行时,使得第一方面或第一方面的各种可能的实现方式所述的方法被实现;或者,当所述指令或所述计算机程序被执行时,使得第三方面或第三方面的各种可能的实现方式所述的方法被实现;或者,当所述指令或所述计算机程序被执行时,使得第五方面或第五方面的各种可能的实现方式所述的方法被实现。
第二十一方面,本申请提供一种计算机可读存储介质,所述计算机可读存储介质用于存储指令或计算机程序,当所述指令或所述计算机程序被执行时,使得第二方面或第二方面的各种可能的实现方式所述的方法被实现;或者,当所述指令或所述计算机程序被执行时,使得第四方面或第四方面的各种可能的实现方式所述的方法被实现;或者,当所述指令或所述计算机程序被执行时,使得第六方面或第六方面的各种可能的实现方式所述的方法被实现。
第二十二方面,本申请提供一种计算机可读存储介质,所述计算机可读存储介质用于存储指令或计算机程序,当所述指令或所述计算机程序被执行时,使得第七方面或第七方面的各种可能的实现方式所述的方法被实现。
第二十三方面,本申请提供一种计算机程序产品,所述计算机程序产品包括指令或计算机程序,当所述指令或所述计算机程序被执行时,使得第一方面或第一方面的各种可能的实现方式所述的方法被实现;或者,当所述指令或所述计算机程序被执行时,使得第三方面或第三方面的各种可能的实现方式所述的方法被实现;或者,当所述指令或所述计算机程序被执行时,使得第五方面或第五方面的各种可能的实现方式所述的方法被实现。
第二十四方面,本申请提供一种计算机程序产品,所述计算机程序产品包括指令或计算机程序,当所述指令或所述计算机程序被执行时,使得第二方面或第二方面的各种可能的实现方式所述的方法被实现;或者,当所述指令或所述计算机程序被执行时,使得第四方面或第四方面的各种可能的实现方式所述的方法被实现;或者,当所述指令或所述计算机程序被执行时,使得第六方面或第六方面的各种可能的实现方式所述的方法被实现。
第二十五方面,本申请提供一种计算机程序产品,所述计算机程序产品包括指令或计 算机程序,当所述指令或所述计算机程序被执行时,使得第七方面或第七方面的各种可能的实现方式所述的方法被实现。
第二十六方面,本申请提供一种计算机程序,用于执行第一方面或第一方面的各种可能的实现方式所述的方法;或者,用于执行第三方面或第三方面的各种可能的实现方式所述的方法;或者,用于执行第五方面或第五方面的各种可能的实现方式所述的方法。
第二十七方面,本申请提供一种计算机程序,用于执行第二方面或第二方面的各种可能的实现方式所述的方法;或者,用于执行第四方面或第四方面的各种可能的实现方式所述的方法;或者,用于执行第六方面或第六方面的各种可能的实现方式所述的方法。
第二十八方面,本申请提供一种计算机程序,用于执行第七方面或第七方面的各种可能的实现方式所述的方法。
第二十九方面,本申请提供一种通信系统,包括源接入网设备和目标接入网设备,所述源接入网设备用于执行第一方面所述的方法,所述目标接入网设备用于执行第二方面所述的方法;或者,所述源接入网设备用于执行第三方面所述的方法,所述目标接入网设备用于执行第四方面所述的方法;或者,所述源接入网设备用于执行第五方面所述的方法,所述目标接入网设备用于执行第六方面所述的方法。
附图说明
图1是本申请实施例提供的一种基于无线通信的定位架构示意图;
图2是本申请实施例提供的一种无线接入网络(radio access network,NG RAN)的架构示意图;
图3是本申请实施例提供的一种不同网元交互时涉及的协议栈的示意图;
图4是本申请实施例提供的一种定位方法的流程示意图;
图5a是本申请实施例提供的一种网络架构示意图;
图5b是本申请实施例提供的一种网络架构示意图;
图5c是本申请实施例提供的一种网络架构示意图;
图6a是本申请实施例提供的一种不同网元交互时涉及的协议栈的示意图;
图6b是本申请实施例提供的一种不同网元交互时涉及的协议栈的示意图;
图7是本申请实施例提供的一种切换方法的流程示意图;
图8是本申请实施例提供的一种网络设备切换的方法流程示意图;
图9是本申请实施例提供的一种基站之间的交互示意图;
图10是本申请实施例提供的一种网络设备切换的方法流程示意图;
图11是本申请实施例提供的一种网络设备切换的方法流程示意图;
图12是本申请实施例提供的一种网络设备切换的方法流程示意图;
图13是本申请实施例提供的一种网络设备切换的方法流程示意图;
图14是本申请实施例提供的一种网络设备切换的方法流程示意图;
图15是本申请实施例提供的一种网络设备切换的方法流程示意图;
图16是本申请实施例提供的一种通信装置的结构示意图;
图17是本申请实施例提供的一种通信装置的结构示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚,下面将结合附图对本申请作进一步地详细描述。
本申请的说明书、权利要求书及附图中的术语“第一”和“第二”等是用于区别不同对象,而不是用于描述特定顺序。此外,术语“包括”和“具有”以及它们任何变形,意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元,而是可选地还包括没有列出的步骤或单元,或可选地还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。
在本文中提及“实施例”意味着,结合实施例描述的特定特征、结构或特性可以包含在本申请的至少一个实施例中。在说明书中的各个位置出现该短语并不一定均是指相同的实施例,也不是与其它实施例互斥的独立的或备选的实施例。本领域技术人员显式地和隐式地理解的是,本文所描述的实施例可以与其它实施例相结合。
在本申请中,“至少一个(项)”是指一个或者多个,“多个”是指两个或两个以上,“至少两个(项)”是指两个或三个及三个以上,“和/或”,用于描述关联对象的关联关系,表示可以存在三种关系,例如,“A和/或B”可以表示:只存在A,只存在B以及同时存在A和B三种情况,其中A,B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达,是指这些项中的任意组合,包括单项(个)或复数项(个)的任意组合。例如,a,b或c中的至少一项(个),可以表示:a,b,c,“a和b”,“a和c”,“b和c”,或“a和b和c”,其中a,b,c可以是单个,也可以是多个。
图1是本申请实施例提供的一种基于无线通信的定位架构示意图,如图1所示,该定位架构中主要包括:无线接入网络radio access network,RAN)、终端设备和核心网三部分。具体地,核心网包括定位管理功能(location management function,LMF)、接入和移动性管理功能(access and mobility management function,AMF)、服务定位协议(service location protocol,SLP)以及演进服务移动定位中心(evolved serving mobile location centre,E-SMLC)等。
其中,LMF负责支持有关目标终端设备的不同类型的位置服务,包括对终端设备的定位和向终端设备传递辅助数据。例如,LMF与接入网设备之间通过新无线(new radio,NR)定位协议附加协议(NR positioning protocol annex,NRPPa)消息进行交互,从而获取定位参考信号(positioning reference signals,PRS)、探测参考信号(sounding reference signal,SRS)配置信息、小区定时、小区位置信息等等。又例如,LMF与终端设备之间通过长期演进(long term evolution,LTE)定位协议(LTE positioning protocol,LPP)消息进行UE能力信息传递、辅助信息传递、测量信息传递等等。
AMF可以从第五代核心网络定位服务(5th generation core network location services,5GC LCS)实体接收与目标终端设备相关的位置服务请求;或者,AMF本身也可代表目标终端设备启动一些位置服务,并将位置服务请求发送给LMF。以及该AMF得到终端设备的位置信息后,将终端设备的位置信息返回给5GC LCS实体。
具体的,RAN包括接入网设备,如图2所示,该接入网设备可以是下一代节点B(next generation node B,gNB)、下一代演进型基站(next generation evolved nodeB,ng-eNB)、或者未来6G通信中的接入网设备。gNB和ng-eNB之间通过Xn接口(或Xn-C接口)连接,以及LMF与ng-eNB/gNB之间通过NG-C(note2)接口连接。
接入网设备可以是任意一种具有无线收发功能的设备,包括但不限于以上所示的基站。该基站还可以是未来通信系统如第六代通信系统中的基站。可选的,该接入网设备还可以为无线局域网(wireless fidelity,WiFi)系统中的接入节点、无线中继节点、无线回传节点等。可选的,该接入网设备还可以是云无线接入网络(cloud radio access network,CRAN)场景下的无线控制器。可选的,该接入网设备还可以是可穿戴设备或车载设备等。可选的,该接入网设备还可以是小站,传输接收节点(transmission reception point,TRP)(或也可以称为传输点)等。可理解,该接入网设备还可以是未来演进的公共陆地移动网络(public land mobile network,PLMN)中的基站等等。为便于描述,下文中将以接入网设备为基站为例,介绍本申请实施例所涉及的方法或网络架构。
进一步的,在一些部署中,如图2所示,基站(如gNB)可以由集中式单元(centralized unit,CU)和分布式单元(distributed unit,DU)构成。即对接入网中的基站的功能进行拆分,将基站的部分功能部署在一个CU,将剩余功能部署在DU。且多个DU共用一个CU,可以节省成本,以及易于网络扩展。
例如,CU和DU的切分可以按照协议栈切分,将无线资源控制(radio resource control,RRC)层、服务数据适应协议(service data adaptation protocol,SDAP)以及分组数据汇聚协议(packet data convergence protocol,PDCP)层部署在CU,其余的无线链路控制(radio link control,RLC)层、介质访问控制(media access control,MAC)层以及物理层部署在DU。CU和DU之间可以通过F1接口连接。CU代表gNB通过NG接口(或NG-C接口)和核心网连接,CU代表gNB通过Xn接口和其他gNB连接。
又例如,CU还可以划分为CU-控制面(control plane,CP)和CU-用户面(user plan,UP)(图1中未示出)。其中CU-CP负责控制面功能,主要包含RRC和控制面对应的PDCP即PDCP-C。PDCP-C主要负责控制面数据的加解密,完整性保护,数据传输等。CU-UP负责用户面功能,主要包含SDAP和用户面对应的PDCP即PDCP-U。其中,CU-CP和CU-UP可以通过E1接口连接。可以理解的是,以上所示出的基站的类型仅为示例,在具体实现中,还可能存在其他类型的基站等,本申请实施例不作限定。
具体的,终端设备可以测量来自NG RAN和其他来源的下行链路信号以支持定位。gNB/ng-eNB可以为目标终端设备提供测量信息,并将该测量信息发送给LMF。
可以理解的是,该终端设备也可称为用户设备(user equipment,UE)、终端等。终端设备是一种具有无线收发功能的设备,可以部署在陆地上,包括室内或室外、手持、穿戴或车载;也可以部署在水面上,如轮船上等;还可以部署在空中,例如部署在飞机、气球或卫星上等。终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality,VR)终端设备、增强现实(augmented reality,AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。
可理解,该终端设备还可以是未来6G网络中的终端设备或者未来演进的PLMN中的终端设备等。可选的,图1所示的通信系统中,终端设备与终端设备之间还可以通过设备到设备(device to device,D2D)、车与任何事物(vehicle-to-everything,V2X)或机器到机器(machine to machine,M2M)等技术进行通信,本申请实施例对于终端设备与终端 设备之间的通信方法不作限定。
为便于描述,下文中将以终端设备为UE为例,介绍本申请实施例所涉及的方法或网络架构。
基于图1所示的定位架构,不同网元之间的信息交互如下所示:
图3为LMF与UE交互所涉及的协议栈示意图。如图3所示,UE和NG RAN之间通过NR-Uu接口或LTE-Uu接口连接,UE侧用于与NG RAN交互的协议栈从上至下依次包括:LPP、非接入层(non-access stratum,NAS)、无线资源控制(radio resource control,RRC)、包数据汇聚协议(packet data convergence protocol,PDCP)、无线链路控制(radio link control,RLC)、媒体接入控制(medium access control,MAC)、层(layer,L)1。NG RAN侧用于与UE交互的协议栈从上至下依次包括:RRC、PDCP、RLC、MAC、L1。NG RAN与AMF之间通过NG-C接口连接,NG RAN侧用于与AMF交互的协议栈从上至下依次包括:NG接口应用协议(NG application protocol,NGAP)、流控制传输协议(stream control transmission protocol,SCTP)、网际互连协议(internet protocol,IP)、L2、L1。AMF侧用于与NG RAN交互的协议栈从上至下依次包括:NAS、NGAP、SCTP、IP、L2、L1。AMF与LMF之间通过NLs接口连接,AMF侧用于与LMF交互的协议栈从上至下依次包括:超文本传输协议2.0((hyper text transfer protocol,HTTP/2)、传输层安全(transport layer security,TLS)、传输控制协议(transmission control protocol,TCP)、IP、L2、L1。LMF侧用于与AMF交互的协议栈从上至下依次包括:LPP、HTTP/2、TLS、TCP、IP、L2、L1。
从图3所示的协议栈可以看出:LMF与UE之间的信息交换通过LPP消息承载,该LPP消息通过Uu口和NG-C接口传输。例如,在UE侧LPP消息将被封装于非接入层(non-access stratum,NAS)信令中,基站侧接收到UE的NAS信令(即基站不知道UE发的是LPP消息)后转给AMF,该AMF解析该NAS信令后获得LPP消息并将其发送给LMF。类似的,从LMF侧发出的LPP消息被封装于NAS信令中,基站接收到UE的NAS信令之后直接转到UE(即基站不知道收到的NAS信令包含的LPP消息)。LMF与基站之间的信息交换通过NRPPa消息承载,该NRPPa消息通过NG-C接口传输。这里所说的LMF与基站之间的信息交换可以理解为:LMF需要从基站获取一些信息,或者基站需要从LMF获取一些信息等,而不是单纯地转发信息。
进一步的,基于图1所示的定位架构,本申请实施例还提供了一种定位方法的流程示意图,如图4所示,该方法至少包括:
401、定位发起方向AMF发送位置服务请求(location service request),该位置服务请求用于请求获取目标UE的位置。
或者,上述步骤401还可以替换为:目标UE的服务AMF由于一些原因(比如紧急呼叫)等需要获取目标UE的位置。
可选的,根据定位发起方的不同,定位可以包括以下四种定位类型(或者称为定位场景):
1)终端发起的定位请求(mobile originated location request,MO-LR),是UE自己发起请求来获取自己的位置信息;
2)终端终止的定位请求(mobile terminated location request,MT-LR),是第三方发起请求来获取UE的位置信息;
3)网络触发的定位请求(network induced location request,NI-LR),是UE的服务核心网(如AMF)发起请求来获取到该UE的位置信息;
4)无线接入网触发的定位请求(RAN Induced Location Request,RI-LR),是UE的接入网(如基站)发起请求来获取该UE的位置信息。图4所示的方法中步骤401中的定位请求方仅为示例。
可以理解的是,定位发起方也可以称为定位客户(client)。上述第三方可以包括因特网服务器如共享单车软件的服务器等等。
402、如果UE处于空闲态,则AMF发送寻呼使UE进入连接态;以及AMF向LMF发送定位服务请求。
403、LMF发起定位过程。例如,LMF从UE获取UE的定位能力;从服务基站(如图4所示的NG-RAN)获取定位测量或辅助信息;从UE获取位置或定位测量结果;或发送定位辅助信息给UE等等。
其中,UE的定位能力、从UE获取的定位测量结果以及定位辅助信息可以包含于LPP消息中。从服务基站获取的定位测量或辅助信息可以包含于NRPPa消息。
404、LMF基于UE或基站的定位测量结果确定UE的位置;并在定位服务响应(location service response)消息中将UE的位置发送给AMF。
405、AMF将UE的位置发送给定位发起方;或者将UE的位置用于紧急呼叫。
通过以上可以看出:LMF与UE之间的消息交互需要经过AMF和接入网设备,导致时延较大。
因此,为了减少时延,可以将定位功能(如LMF的功能)放到接入网,称之为定位管理组件或定位管理组件(location management component,LMC)。图5a、图5b和图5c分别是本申请实施例提供的一种网络架构示意图。如图5a所示,LMC可以作为基站内部的一个功能,不需要引入新的接口。如图5b所示,LMC可以作为逻辑节点,通过新的接口与基站连接。例如,该新的接口可以称为itf等,本申请实施例对于该新的接口的名称不作限定。进一步的,LMC可以与基站中的集中式单元(centralized unit,CU)连接。如图5c所示,LMC作为一个逻辑节点,通过新的接口分别与多个基站连接。
图6a、图6b示出了LMC与UE交互时所涉及的协议栈。如图6a所示,LMC作为基站内部的一个功能时,LMC与UE通过接口NR-Uu连接,UE侧的协议栈从上至下包括:LPP、RRC、PDCP、RLC、MAC、L1;gNB/LMC侧的协议栈从上至下包括:LPP、RRC、PDCP、RLC、MAC、L1。如图6b所示,LMC作为一个逻辑节点经过接口可以与一个或多个基站连接时,UE侧的协议栈从上至下包括:LPP、RRC、PDCP、RLC、MAC、L1;基站侧面向UE的协议栈从上至下包括:RRC、PDCP、RLC、MAC、L1;基站侧面向LMC的协议栈从上至下包括:XPAP、SCTP、IP、L2、L1;LMC侧的协议栈从上至下包括:LPP、XPAP、SCTP、IP、L2、L1。
可理解,图6b中基站与LMC之间的接口为“XP”,基站与LMC之间的接口协议为“XPAP”。然而,在实际应用中,基站与LMC之间的接口的名称以及对应的接口协议还可以是其他形式,对此,本申请不做限制。
基于图6a和图6b示出的协议栈,可以看出:LMC与UE之间的消息交互仍然可以使用LPP协议,但是不同于图1所示的定位架构中,UE与LMF之间的协议栈,在图5a-图5c所示的网络架构中,LMC与UE之间的LPP消息封装于无线资源控制(radio resource  control,RRC)消息中。
以上详细介绍了本申请实施例所涉及的定位以及定位网络架构,以下详细介绍本申请实施例所涉及的切换方法。如图7所示,该切换方法包括:
可选地,701、源基站(source gNB)发送RRC重配置消息给连接态的UE,其中包含测量对象、报告配置、测量标识等参数。
可选地,702、UE根据RRC重配置(RRC reconfiguration)消息对多个小区进行测量,形成报告上报(measure report)各类事件给当前连接的源基站,如当前服务小区的信号强度低于门限且目标小区信号高于门限。
703、源基站确定UE是否需要切换(handover decision),如确定该UE需要切换,则该源基站发送切换请求(handover request)消息给目标基站。
704、目标基站发送切换请求确认(handover request ACK)消息给源基站;可选地,目标基站可以(target gNB)根据自身连接数等情况确定是否允许UE的接入(admission control)。可选地,该切换请求确认消息中可以包括新的小区无线网络临时标识(cell-radio network temporary identifier,C-RNTI)、目标基站安全相关算法等参数
705、源基站在收到目标基站发来的切换请求确认消息后,发送RRC重配置消息(即切换命令)给UE。可选地,该RRC重配置消息中可以包括上述704中的切换请求确认消息。以及NR系统中该RRC重配置消息中还可以包括目标小区的相关信息以及UE接入该目标小区所需的相关配置参数。例如,RRC重配置消息中包含目标小区的信息,该目标小区的信息可以包括目标小区的物理小区标识(physical cell identifier,PCI)以及目标小区对应的频率信息(如目标小区对应的频点)等。
706、UE根据上述RRC重配置信息向目标基站发起随机接入(random access)。可选地,UE断开与源基站的连接,在成功接入目标基站之前,UE可能收发数据会出现短暂的中断。
可选地,707、UE发送RRC重配置完成(RRC reconfiguration complete)消息给目标基站。
可选地,708、目标基站发送上下文释放消息(context release)给源基站,以指示源基站释放该UE的上下文。
从上可以看出:在UE对目标基站发起随机接入时,UE会断开与源基站的连接。该情况下,如何保证定位的连续性是需要解决的问题。
因此,本申请实施例提供了一种网络设备切换的方法,有效解决了在切换场景下,如何保证定位的连续性的问题。本申请实施例所提供的网络设备切换的方法可应用于各类通信系统,以及还可应用于前述实施例中所介绍的各个网络架构。
具体的,该方法可应用于接入网设备,该接入网设备的类型可包括前述实施例中所介绍的各个类型。可以理解的是,本申请实施例所涉及的接入网设备可以包括源接入网设备和目标接入网设备。下文中,将以源接入网设备为源基站为例,目标接入网设备为目标基站为例来说明本申请实施例所提供的方法。
以下将按照实施方法的不同详细介绍本申请实施例所提供的网络设备切换的方法。
方法一、
该方法一中UE从源基站切换到目标基站时,为保证定位的连续性,可以由该源基站或该目标基站确定继续在源基站执行定位。
图8是本申请实施例提供的一种网络设备切换的方法流程示意图。如图8所示,该网络设备切换的方法至少包括:
801、源基站向目标基站发送切换请求消息。相应的,目标基站接收该切换请求消息。
其中,该切换请求消息用于请求将UE切换到目标基站,且该UE处于基于LMC的定位状态。也就是说,在源基站向目标基站发送切换请求消息时,该UE处于RRC连接态,且源基站正在对该UE执行基于LMC的定位。至于该源基站与该UE处于定位过程的哪个步骤,本申请实施例不作限定。可选的,源基站向目标基站发送切换请求消息时,可以理解为:该源基站向目标基站发送切换请求消息之前,或者,该源基站向目标基站发送切换请求消息的同时。可理解地,对于该源基站发送切换请求消息时,该源基站与该UE所处的定位状态的说明,以下各个实施例同样适用。
可选地,该切换请求消息中包括第一指示信息,该第一指示信息用于指示继续在该源基站执行对该UE的基于LMC的定位,或者用于指示定位不迁移到目标基站。对于该第一指示信息的具体形式,本申请实施例不作限定。
在一种可能的实现方式中,本申请实施例还提供了一种源基站如何确定是否继续执行定位的方法。如图9所示,基站1和基站2可以相互交互各自的LMC信息,具体的,该基站1和基站2可以在接口建立时,相互交互各自的LMC信息。其中,基站1可以是源基站,基站2是目标基站;或者,基站1可以是目标基站,基站2是源基站。应用于图8所示的方法,即该源基站向目标基站发送切换请求消息之前,目标基站与源基站可以通过图9所示的方法相互交互各自的LMC信息。例如,目标基站向源基站发送第二消息,相应的,该源基站接收该目标基站发送的第二消息。
其中,该第二消息中包括该目标基站是否支持基于LMC的定位和/或该目标基站支持的定位服务质量(quality of service,QoS)信息。可选的,该定位QoS信息可以包括定位时延、定位精度或QoS等级中的一项或多项。可选的,该第二消息可以为Xn建立请求消息、Xn建立响应消息或接入网节点配置更新消息中的任一项。其中Xn建立请求消息和Xn建立响应消息是两个基站间Xn接口建立过程中的消息;当一个基站的配置发生改变时,该基站可以通过接入网节点配置更新消息通知另一个基站。可选的,源基站还可以根据多个基站所发送的LMC信息,来确定目标基站。例如,当前UE有基于LMC的定位,则当有多个候选基站可以选择时,源基站可以优先选择那些支持LMC,并且满足定位QoS要求的目标基站,以保证定位的连续性。
可选的,在满足如下条件中的任一项或多项时,该源基站确定继续在该源基站执行对该UE的该基于LMC的定位:如该目标基站不支持该基于LMC的定位;或者,该目标基站不满足该终端设备的定位服务质量QoS要求;或者,该基于LMC的定位的定位类型为RI-LR。例如,UE的定位QoS要求的定位时延是300毫秒,但是,目标基站只能满足500毫秒的时延。又例如,基于LMC的定位的发起方为该源基站,则该源基站可以确定继续走该源基站执行对UE的定位,以获得该UE的位置信息。
802、目标基站向源基站发送切换请求确认消息,相应的,该源基站接收该目标基站发送的切换请求确认消息。
803、该源基站向UE发送RRC消息;相应的,该UE接收该RRC消息。
其中,该RRC消息用于指示该UE切换到该目标基站。如图8所示,该RRC消息可以为RRC重配置消息。
该UE接收到该RRC消息之后,该UE便可以发起随机接入过程,以及发送RRC重配置完成消息给目标基站。可理解,对于UE发起随机接入过程,以及发送RRC重配置完成消息给目标基站的具体说明,可以参考图7所示的方法,这里不再详述。
需要说明的是,一般的,目标基站在收到RRC重配置完成消息后,会立即给源基站发送上下文释放消息,以触发源基站释放该UE的上下文。可选的,在本申请实施例中,目标基站可以延迟(即延迟到步骤808)或不发送上下文释放消息,也就是继续维持该UE的目标基站和源基站之间的连接,从而可以使得源基站即使在切换后也能获取到UE的定位测量结果。可理解,对于UE接收到RRC消息之后所执行的步骤,以下各个实施例均适用。
804、UE向目标基站发送第五消息,相应的,该目标基站接收该第五消息。该第五消息中包括该UE的定位测量结果。
可选的,该第五消息可以包括LPP消息,进一步的,该LPP消息包含定位测量结果,该LPP消息可以封装于RRC消息中(即封装在第五消息中)。
可选地,805、目标基站向源基站发送第一消息,相应的,该源基站接收该目标基站发送的第一消息。
其中,该第一消息中包括该终端设备的定位测量结果。可选的,第一消息包括步骤804中的LPP消息,即该目标基站将步骤804中的第五消息中包括的LPP消息或者定位测量结果转发给源基站。
当前,由于基站之间不支持交互LPP消息,因此可以引入一个新的XnAP消息,比如,消息名为LPP TRANSPORT。该XnAP消息可以用于基站之间传递LPP消息,该XnAP消息可以是UE关联的XnAP消息,也就是通过基站间的UE连接发送的XnAP消息。以及该XnAP消息中可以包括源基站和目标基站分别分配的UE Xn接口应用协议标识。也就是说,该第一消息可以为新引入的一个XnAP消息,该XnAP消息中包括LPP消息。该XnAP消息是一个通用的用于传递LPP消息的XnAP消息,可以不局限于只传递包括定位测量结果的LPP消息。基站间传递LPP消息的方法,可以不与上述步骤耦合,即,可以是一个独立的实施例而存在。
可选地,806、该源基站根据该定位测量结果确定该终端设备的位置信息。
可选的,根据定位发起方的不同,在上述步骤806之后可以有不同的处理方式。例如,对于RI-LR定位,则源基站中确定了UE的位置之后,可以使用该UE的位置。又例如,源基站接收到的定位请求来自于AMF,则该源基站便可以将该UE的位置发送给该AMF。
可选的,根据LMC的部署方式的不同,上述步骤806也可以有不同的处理方式。例如,LMC的部署如图5a所示,LMC作为源基站内部的功能,则该源基站可以直接根据定位测量结果确定该UE的位置信息。又例如,LMC的部署如图5b或如图5c所示,则该源基站接收到该UE的定位测量结果时,该源基站还可以将该定位测量结果发送给LMC,该LMC根据该定位测量结果确定该UE的位置信息。为便于描述,不论LMC的部署方式如何,下文中均以基站为例进行描述。
在一种可能的实现方式中,该源基站接收该目标基站发送的第一消息之后,该方法还包括:
807、该源基站向该目标基站发送第三消息,相应的,目标基站接收该第三消息。
其中,该第三消息用于指示该基于LMC的定位已结束。可选的,该第三消息为XnAP 消息,如源基站可以通过Xn接口向目标基站发送XnAP消息,该XnAP消息用于指示针对该UE的定位结束了,以触发目标基站向源基站发送上下文释放消息。
808、该目标基站向该源基站发送上下文释放消息,相应的,该源基站接收该目标基站发送的上下文释放消息。
可选的,上述步骤807和808还可以替换为:该源基站向该目标基站发送第四消息,相应的,该目标基站接收该第四消息。其中,该第四消息用于指示该终端设备的上下文已被释放。也就是说,源基站获得UE的位置信息之后,可以直接释放该UE的上下文,以及通知目标基站,该UE的上下文已被释放。
本申请所提供的技术方案:在目标基站不支持基于LMC的定位时,通过继续在源基站执行定位,保证了定位的连续性。具体的,通过基站间交互各自的LMC信息,可以用于源基站选择目标基站,以及用于源基站确定是否继续在该源基站执行定位。以及源基站通过在切换请求消息携带第一指示信息,可以及时通知目标基站采用合理的方式来处理定位。以及源基站通过延迟或不发送上下文释放消息,可以使得源基站即使在切换后也能获取到UE的定位测量结果。
图8示出的方法是以源基站确定继续执行定位为例来说明的,如图10所示,图10示出的方法是以目标基站确定继续执行定位为例来说明的。因此,图8中的步骤801和步骤802,还可以替换为:
1001、源基站向目标基站发送切换请求消息。相应的,目标基站接收该切换请求消息。
其中,该切换请求消息用于请求将UE切换到该目标基站,该UE处于基于LMC的定位状态,且该切换请求消息中包括该基于LMC的定位信息。可选的,该基于LMC的定位信息包括该UE的定位上下文信息、该UE的定位服务质量QoS要求或定位类型中的一项或多项。可选的,通过该基于LMC的定位信息可使得目标基站确定是否在该目标基站执行定位。或者,该基于LMC的定位信息可以用于指示目标基站继续执行定位。
1002、该源基站接收该目标基站发送的切换请求确认消息,该切换请求确认消息中包括第二指示信息,该第二指示信息用于指示该源基站继续执行对该UE的该基于LMC的定位。
在一种可能的实现方式中,本申请实施例还提供了一种目标基站如何确定是否继续执行定位的方法。如该目标基站向该源基站发送切换请求确认消息之前,该方法还包括:
在满足如下条件中的任一项或多项时,该目标基站确定继续在该源基站执行对该终端设备的该基于LMC的定位:该目标基站不支持该基于LMC的定位;或者,该目标基站不满足该终端设备的定位服务质量QoS要求;或者,该基于LMC的定位的定位类型为无线接入网触发的定位请求RI-LR。
对于图10中的步骤1003-步骤1008的具体实现方式,可以参考图8,这里不再一一详述。
可理解,对于图10所示的方法中,未详尽描述的方法可参考图8。
本申请所提供的技术方案:在目标基站不支持基于LMC的定位时,通过继续在源基站执行定位,保证了定位的连续性。具体的,通过基站间交互各自的LMC信息,可以用于源基站选择目标基站,以及用于目标基站确定是否继续在该源基站执行定位。以及目标基站通过在切换请求确认消息携带第二指示信息,可以及时通知源基站采用合理的方式来处理定位。以及目标基站通过延迟或不发送上下文释放消息,可以使得源基站即使在切换 后也能获取到UE的定位测量结果。
方法二、
该方法二中UE从源基站切换到目标基站时,为保证定位的连续性,可以由目标基站执行定位。
图11是本申请实施例提供的一种网络设备切换的方法流程示意图。该方法可以应用图5c所示的LMC的部署,即该LMC作为一个逻辑节点,通过新的接口分别与源基站和目标基站连接。如图11所示,该网络设备切换的方法至少包括:
1101、源基站向目标基站发送切换请求消息。相应的,目标基站接收该切换请求消息。
其中,该切换请求消息用于请求将UE切换到该目标基站,该UE处于基于LMC的定位状态,且该切换请求消息中包括该基于LMC的定位信息。该基于LMC的定位信息包括该终端设备的定位上下文信息、该终端设备的定位服务质量QoS要求、定位类型、该源接入网络设备的标识ID、该源基站分配的定位关联标识ID或LMC分配的接口应用协议标识ID中的任一项或多项。
1102、目标基站向源基站发送切换请求确认消息,相应的,该源基站接收该目标基站发送的切换请求确认消息。
1103、该源基站向该终端设备发送RRC消息;相应的,该终端设备接收该RRC消息。
其中,该RRC消息用于指示该终端设备切换到该目标基站。可选的,该RRC消息可以包括RRC重配置消息。
然后,UE根据上述RRC重配置信息向目标基站发起随机接入(random access)过程。在成功完成随机接入过程后,UE发送RRC重配置完成(RRC reconfiguration complete)消息给目标基站。
需要说明的是,一般的,目标基站在收到RRC重配置完成消息后,会立即给源基站发送上下文释放消息,以触发源基站释放该UE的上下文。可选的,在本申请实施例中,定位类型为NI-LR或RI-LR时,目标基站可以延迟(即延迟到向源基站发送UE的位置信息后)或不发送上下文释放消息,也就是继续维持该UE的目标基站和源基站之间的连接,从而可以在目标基站获取到UE的位置信息后,能发送给源基站。
1104、目标基站向LMC发送请求消息(relocation request),相应的,该LMC接收该请求消息。其中,该请求消息中包括源接入网设备分配的定位关联标识ID和/或所述LMC分配的接口应用协议标识ID。
可选的,该请求消息中还可以包括源基站的标识ID。基于该源基站的标识ID和该源基站分配的定位关联标识ID,该LMC可以确定该定位关联标识ID是由哪个源基站分配的。由此,基于该源基站分配的定位关联标识ID和/或该LMC分配的接口应用协议标识ID,LMC可以确定UE的定位上下文,从而找到源基站执行定位时的定位上下文,以确保该LMC继续执行定位。
1105、LMC向目标基站发送响应消息,相应的,该目标基站接收该响应消息。
1106、终端设备向LMC发送第五消息,相应的,该LMC接收该第五消息;该第五消息中包括该UE的定位测量结果。
1107、LMC根据该UE的定位测量结果确定该UE的位置信息。
1108、LMC将该UE的位置信息发送给目标基站,相应的,该目标基站接收该UE的位置信息。
可选的,定位类型为NI-LR或RI-LR时,该目标基站还可以将该UE的位置信息发送给源基站,相应的,该源基站接收该UE的位置信息。当前,由于基站之间不支持交互UE的位置信息,因此可以引入一个新的XnAP消息,该XnAP消息可以用于基站之间传递UE的位置信息,该XnAP消息可以是UE关联的XnAP消息,也就是通过基站间的UE连接发送的XnAP消息。也就是说,该第一消息可以为新引入的一个UE关联的XnAP消息,该XnAP消息中包括UE的位置信息。通过该XnAP消息,目标基站将UE的位置信息发送给源基站。该情况下,在目标基站向源基站发送该UE的位置信息之后,该目标基站便可以向源基站发送上下文释放消息。相应的,该源基站接收该上下文释放消息,释放该UE的上下文。
可选的,定位类型为MO-LR时,该目标基站可以将该UE的位置信息发送给该UE。
该情况下,目标基站在接收到RRC重配置完成消息之后,便可以向源基站发送上下文释放消息。
可以理解的是,方法一中不论是源基站确定继续在该源基站执行定位,还是目标基站确定继续在该源基站执行定位,均通过指示信息指示继续在源基站执行定位。而方法二中,源基站和目标基站可以默认/约定在目标基站执行定位。同理,方法一中源基站和目标基站也可以默认/约定在源基站继续执行定位,而方法二中也可以通过指示信息指示在目标基站执行定位。因此,不应将图11所示的方法理解为对本申请的限定。
本申请所提供的技术方案:通过在切换请求消息中携带源基站分配的定位关联ID或LMC分配的接口应用协议标识,LMC可以找到对应的定位上下文,从而使得定位能继续进行。以及通过在切换请求消息中携带定位类型,在基站间引入XnAP消息用于目标基站发送UE的位置信息给源基站,从而实现定位的连续性。
方法三、
该方法三中UE从源基站切换到目标基站时,源基站或目标基站可以确定停止执行定位。对于方法三,本申请可分别包括以下几个实施例:
实施例一、
如图12所示,该网络设备切换的方法包括:
1201、源基站确定停止继续执行基于LMC的定位。
可选的,该源基站确定停止继续执行对UE的基于LMC的定位的条件可以包括以下任一项或多项:目标基站不支持基于LMC的定位,则源基站决定停止定位;或者,目标基站支持基于LMC的定位,但是不支持当前UE的定位QoS要求,则源基站决定停止定位;或者,定位类型是源基站发起的针对该UE的定位(即RI-LR定位),则切换后,UE的位置信息不再有用,则源基站决定停止定位;或者,当前是基于N2的切换或AMF改变的切换;或者,定位类型是MT-LR或NI-LR,则源基站决定停止定位。例如,当前是基于AMF改变的切换,则切换后,目标基站无法将UE的位置发送给源基站的服务AMF。或者,目标基站与源基站连接到不同的LMC,但是不支持LMC重定向(relocation)。可理解,对于源基站确定停止定位的条件,以下实施例同样适用。
1202、源基站向UE发送第六消息,相应的,该UE接收该第六消息;该第六消息用于指示停止执行基于LMC的定位。
可选的,该第六消息可以包括LPP消息,进一步的,该LPP消息可以包括abort消息。也就是说,该第六消息可以用于指示UE停止继续执行基于LMC的定位,从而使得该UE 释放与定位相关的配置,比如定位参考信号的配置等。
1203、UE停止执行基于LMC的定位,释放相关的配置。
1204、源基站向目标基站发送切换请求消息,相应的,该目标基站接收该切换请求消息。
1205、目标基站向源基站发送切换请求确认消息,相应的,该源基站接收该切换请求确认消息。
1206、源基站向UE发送RRC重配置消息,相应的,该UE接收该RRC重配置消息。
可以理解的是,对于上述1202以及上述1206的先后顺序之外,本申请实施例对于上述1202至上述1205的先后顺序不作限定。
实施例二、
如图13所示,该网络设备切换的方法包括:
1301、源基站确定停止继续执行基于LMC的定位。
1302、源基站向目标基站发送切换请求消息,相应的,该目标基站接收该切换请求消息。
其中,该切换请求消息中包括用于停止定位的LPP消息。如该LPP消息可以包括abort消息。例如,该abort消息可以作为切换请求消息中的一个字节流形式的信元。可理解,对于该源基站确定停止定位的条件可如图12中的方法,这里不再详述。
1303、目标基站向源基站发送切换请求确认消息,相应的,该源基站接收该切换请求确认消息。
其中,该切换请求确认消息中包括用于停止定位的LPP消息。例如,目标基站接收到切换请求消息中所包括的abort消息后,可以将该abort消息封装于切换请求确认消息里的RRC重配置消息中,然后发送给源基站。
1304、源基站读取切换请求确认消息中的RRC重配置消息,然后向UE发送该RRC重配置消息,相应的,该UE接收该RRC重配置消息。其中,该RRC重配置消息中包括用于停止定位的LPP消息,比如abort消息。
1305、UE停止执行基于LMC的定位,释放相关的配置。
本申请所提供的技术方案:由源基站来决定停止定位;以及该源基站生成一个用于停止定位的LPP消息,比如abort消息,然后向目标基站发送切换请求消息,该切换请求消息中携带该abort消息。接着,该目标基站将该abort消息封装在RRC重配置消息中,该RRC重配置消息包含在切换请求确认消息中发送给源基站,然后该源基站将该RRC重配置消息发送给UE。UE收到该RRC重配置消息后,根据该RRC重配置消息中的abort消息停止定位,并释放相关的配置。
实施例三、
如图14所示,该网络设备切换的方法至少包括:
1401、源基站向目标基站发送切换请求消息,相应的,该目标基站接收该切换请求消息。
其中,该切换请求消息中包括第三指示信息,该第三指示信息用于指示停止基于LMC的定位。例如,该第三指示信息可以为1bit,如以0或1表示停止定位。
1402、目标基站向源基站发送切换请求确认消息,相应的,该源基站接收该切换请求确认消息。其中,该切换请求确认消息中包括RRC重配置消息,该RRC重配置消息中包 括第三指示信息。
1403、源基站读取切换请求确认消息中的RRC重配置消息,然后向UE发送该RRC重配置消息,相应的,该UE接收该RRC重配置消息。其中,该RRC重配置消息中包括第三指示信息。
1404、UE根据RRC重配置消息中的第三指示信息停止执行基于LMC的定位,释放相关的配置。
本申请所提供的技术方案:由源基站来决定停止定位;以及该源基站向目标基站发送切换请求消息,该切换请求消息中携带第三指示信息,该第三指示信息用于指示停止定位。该第三指示信息包含于RRC重配置消息中,该RRC重配置消息包含在切换请求确认消息中,然后源基站将该RRC重配置消息发送给UE。UE收到该RRC重配置消息后,根据该RRC重配置消息中的第三指示信息停止定位,并释放相关的配置。
实施例四、
如图15所示,该网络设备切换的方法至少包括:
1501、源基站向目标基站发送切换请求消息,相应的,该目标基站接收该切换请求消息。
其中,该切换请求消息中包括基于LMC的定位信息,如该基于LMC的定位信息包括UE的定位上下文、定位QoS信息或定位类型中的任一项或多项。具体的,该基于LMC的定位信息可用于指示目标基站根据该基于LMC的定位信息确定是否停止执行基于LMC的定位。例如,目标基站确定停止基于LMC的定位的条件可包括以下任一项或多项:目标基站不支持基于LMC的定位,则目标基站决定停止定位;或者,目标基站支持基于LMC的定位,但是不支持当前UE的定位QoS要求,则目标基站决定停止定位;或者,定位类型是源基站发起的针对该UE的定位(即RI-LR定位),切换后,UE的位置信息不再有用,则目标基站决定停止定位。
1502、目标基站向源基站发送切换请求确认消息,相应的,该源基站接收该切换请求确认消息。其中,该切换请求确认消息中包括RRC重配置消息,该RRC重配置消息中包括第四指示信息,该第四指示信息用于指示停止基于LMC的定位。
1503、源基站读取切换请求确认消息中的RRC重配置消息,然后向UE发送该RRC重配置消息,相应的,该UE接收该RRC重配置消息。其中,该RRC重配置消息中包括第四指示信息。
1504、UE根据RRC重配置消息中的第四指示信息停止执行基于LMC的定位,释放相关的配置。
本申请所提供的技术方案:源基站或目标基站决定是否停止定位,通过在切换请求消息或切换请求确认消息中携带指示信息通知对方是否停止定位。在空口,通过在RRC重配置消息里携带指示信息或abort消息用于指示UE停止定位测量。
以上对本申请的实施例进行了详细介绍,以下介绍本申请的通信装置。
图16是本申请实施例提供的一种通信装置的结构示意图,如图16所示,该通信装置包括发送单元1601、接收单元1602和处理单元1603。
在一个实施例中,发送单元1601,用于向目标接入网设备发送切换请求消息;其中,该切换请求消息用于请求将终端设备切换到该目标接入网设备,该终端设备处于基于定位管理组件LMC的定位状态;且该切换请求消息中包括第一指示信息,该第一指示信息用 于指示继续在该通信装置执行对该终端设备的该基于LMC的定位;
接收单元1602,用于接收该目标接入网设备发送的切换请求确认消息;
该发送单元1601,还用于向该终端设备发送无线资源控制RRC消息;其中,该RRC消息用于指示该终端设备切换到该目标接入网设备;
该接收单元1602,还用于接收该目标接入网设备发送的第一消息,该第一消息中包括该终端设备的定位测量结果。
在一种可能的实现方式中,处理单元1603,用于在满足如下条件中的任一项或多项时,确定继续在该通信装置执行对该终端设备的该基于LMC的定位:
该目标接入网设备不支持该基于LMC的定位;或者,该目标接入网设备不满足该终端设备的定位服务质量QoS要求;或者,该基于LMC的定位的定位类型为无线接入网触发的定位请求RI-LR。
在一种可能的实现方式中,该接收单元1602,还用于接收该目标接入网设备发送的第二消息;其中,该第二消息中包括该目标接入网设备是否支持该基于LMC的定位和/或该目标接入网设备支持的定位QoS信息。
在一种可能的实现方式中,该处理单元1603,还用于根据该定位测量结果确定该终端设备的位置信息。
在一种可能的实现方式中,该发送单元1601,还用于向该目标接入网设备发送第三消息,该第三消息用于指示该基于LMC的定位已结束;该接收单元1602,还用于接收该目标接入网设备发送的上下文释放消息。
在一种可能的实现方式中,该发送单元1601,还用于向该目标接入网设备发送第四消息,该第四消息用于指示该终端设备的上下文已被释放。
在一种可能的实现方式中,该第二消息为Xn建立请求消息、Xn建立响应消息或接入网节点配置更新消息中的任一项。
复用图16,在另一个实施例中,发送单元1601,用于向目标接入网设备发送切换请求消息;其中,该切换请求消息用于请求将终端设备切换到该目标接入网设备,该终端设备处于基于定位管理组件LMC的定位状态,且该切换请求消息中包括该基于LMC的定位信息;
接收单元1602,用于接收该目标接入网设备发送的切换请求确认消息,该切换请求确认消息中包括第二指示信息,该第二指示信息用于指示该通信装置继续执行对该终端设备的该基于LMC的定位;
该发送单元1601,还用于向该终端设备发送无线资源控制RRC消息,该RRC消息用于指示该终端设备切换到该目标接入网设备;
该接收单元1602,还用于接收该目标接入网设备发送的第一消息,该第一消息中包括终端设备的定位测量结果。
在一种可能的实现方式中,该基于LMC的定位信息包括该终端设备的定位上下文信息、该终端设备的定位服务质量QoS要求或定位类型中的一项或多项。
在一种可能的实现方式中,处理单元1603,用于根据该定位测量结果确定该终端设备的位置信息。
在一种可能的实现方式中,该发送单元1601,还用于向该目标接入网设备发送第三消息,该第三消息用于指示该基于LMC的定位已结束;
该接收单元1602,还用于接收该目标接入网设备发送的上下文释放消息。
在一种可能的实现方式中,该发送单元1601,还用于向该目标接入网设备发送第四消息,该第四消息用于指示该终端设备的上下文已被释放。
复用图16,在另一个实施例中,发送单元1601,用于向目标接入网设备发送切换请求消息;其中,该切换请求消息用于请求将终端设备切换到该目标接入网设备,该终端设备处于基于定位管理组件LMC的定位状态,且该切换请求消息中包括该基于LMC的定位信息;
接收单元1602,用于接收该目标接入网设备发送的切换请求确认消息;
该发送单元1601,还用于向终端设备发送无线资源控制RRC消息,该RRC消息用于指示切换到该目标接入网设备。
在一种可能的实现方式中,该基于LMC的定位信息包括该终端设备的定位上下文信息、该终端设备的定位服务质量QoS要求、定位类型、该源接入网络设备的标识ID、该通信装置分配的定位关联标识ID或LMC分配的接口应用协议标识ID中的任一项或多项。
在一种可能的实现方式中,该接收单元1602,还用于接收该目标接入网设备发送的该终端设备的位置信息;
该接收单元1602,还用于接收该目标接入网设备发送的上下文释放消息。
在以上各个实施例中,当上述通信装置是源接入网设备或源接入网设备中实现上述功能的部件时,处理单元1603可以是一个或多个处理器,发送单元1601可以是发送器,接收单元1602可以是接收器,或者发送单元1601接收单元1602集成于一个器件,例如收发器。
当上述通信装置是芯片时,处理单元1603可以是一个或多个处理器,发送单元1601可以是输出接口,接收单元1602可以是输入接口,或者发送单元1601和接收单元1602集成于一个单元,例如输入输出接口。
可理解,对于以上各个实施例中所示的各个单元的实现还可参照图8-图15所示的方法实施例的相应描述。
复用图16,在另一个实施例中,接收单元1602,用于接收源接入网设备发送的切换请求消息;其中,该切换请求消息用于请求将终端设备切换到该通信装置,该终端设备处于基于定位管理组件LMC的定位状态;且该切换请求消息中包括第一指示信息,该第一指示信息用于指示继续在该源接入网设备执行对该终端设备的该基于LMC的定位;
发送单元1601,用于向该源接入网设备发送切换请求确认消息;
该接收单元1602,还用于接收该终端设备发送的第五消息,该第五消息中包括该终端设备的定位测量结果;
该发送单元1601,还用于向该源接入网设备发送第一消息,该第一消息中包括该终端设备的定位测量结果。
在一种可能的实现方式中,该发送单元1601,还用于向该源接入网设备发送第二消息;其中,该第二消息中包括该通信装置是否支持该基于LMC的定位和/或该通信装置支持的定位QoS信息。
在一种可能的实现方式中,该接收单元1602,还用于接收该源接入网设备发送的第三消息,该第三消息用于指示该基于LMC的定位已结束;该发送单元1601,还用于向该源接入网设备发送上下文释放消息。
在一种可能的实现方式中,该接收单元1602,还用于接收该源接入网设备发送的第四消息,该第四消息用于指示该终端设备的上下文已被释放。
在一种可能的实现方式中,该第二消息为Xn建立请求消息、Xn建立响应消息或接入网节点配置更新消息中的任一项。
复用图16,在另一个实施例中,接收单元1602,用于接收源接入网设备发送的切换请求消息;其中,该切换请求消息用于请求将终端设备切换到该通信装置,该终端设备处于基于定位管理组件LMC的定位状态,且该切换请求消息中包括该基于LMC的定位信息;
发送单元1601,用于向该源接入网设备发送切换请求确认消息,该切换请求确认消息中包括第二指示信息,该第二指示信息用于指示该源接入网设备继续执行对该终端设备的该基于LMC的定位;
该接收单元1602,还用于接收该终端设备发送的第五消息,该第五消息中包括该终端设备的定位测量结果;
该发送单元1601,还用于向该源接入网设备发送第一消息,该第一消息中包括该终端设备的定位测量结果。
在一种可能的实现方式中,处理单元1603,用于在满足如下条件中的任一项或多项时,确定继续在该源接入网设备执行对该终端设备的该基于LMC的定位:
该通信装置不支持该基于LMC的定位;或者,该通信装置不满足该终端设备的定位服务质量QoS要求;或者,该基于LMC的定位的定位类型为无线接入网触发的定位请求RI-LR。
在一种可能的实现方式中,该接收单元1602,还用于接收该源接入网设备发送的第三消息,该第三消息用于指示该基于LMC的定位已结束;
该发送单元,还用于向该源接入网设备发送上下文释放消息。
在一种可能的实现方式中,该接收单元1602,还用于接收该源接入网设备发送的第四消息,该第四消息用于指示该终端设备的上下文已被释放。
复用图16,在另一个实施例中,接收单元1602,用于接收源接入网设备发送的切换请求消息;其中,该切换请求消息用于请求将终端设备切换到该通信装置,该终端设备处于基于定位管理组件LMC的定位状态,且该切换请求消息中包括该基于LMC的定位信息;
发送单元1601,用于向该源接入网设备发送切换请求确认消息;
该接收单元1602,还用于接收该LMC发送的该终端设备的位置信息。
在一种可能的实现方式中,该基于LMC的定位信息包括该终端设备的定位上下文信息、该终端设备的定位服务质量QoS要求、定位类型、该源接入网络设备的标识ID、该源接入网设备分配的定位关联标识ID或LMC分配的接口应用协议标识ID中的任一项或多项。
在一种可能的实现方式中,该发送单元1601,还用于向该源接入设备发送该终端设备的位置信息;该发送单元1601,还用于向该源接入网设备发送上下文释放消息。
在以上各个实施例中,当上述通信装置是目标接入网设备或目标接入网设备中实现上述功能的部件时,处理单元1603可以是一个或多个处理器,发送单元1601可以是发送器,接收单元1602可以是接收器,或者发送单元1601接收单元1602集成于一个器件,例如 收发器。
当上述通信装置是芯片时,处理单元1603可以是一个或多个处理器,发送单元1601可以是输出接口,接收单元1602可以是输入接口,或者发送单元1601和接收单元1602集成于一个单元,例如输入输出接口。
可理解,对于以上各个实施例中所示的各个单元的实现还可参照图8-图15所示的方法实施例的相应描述。
复用图16,在另一个实施例中,接收单元1602,用于接收来自目标接入网设备发送的请求消息;其中,该请求消息中包括源接入网设备分配的定位关联标识ID和/或该LMC分配的接口应用协议标识ID;
处理单元1603,用于基于该定位关联标识ID和/或该接口应用协议标识ID确定终端设备的定位上下文;
发送单元1601,用于向该目标接入网设备发送响应消息。
在一种可能的实现方式中,该接收单元1602,还用于接收该终端设备发送的第五消息,该第五消息中包括该终端设备的定位测量结果;
该处理单元1603,还用于根据该终端设备的定位测量结果确定该终端设备的位置信息;
该发送单元1601,还用于向该目标接入网设备发送该终端设备的位置信息。
在以上各个实施例中,当上述通信装置是LMC或LMC中实现上述功能的部件时,处理单元1603可以是一个或多个处理器,发送单元1601可以是发送器,接收单元1602可以是接收器,或者发送单元1601接收单元1602集成于一个器件,例如收发器。
当上述通信装置是芯片时,处理单元1603可以是一个或多个处理器或处理电路等等,发送单元1601可以是输出接口,接收单元1602可以是输入接口,或者发送单元1601和接收单元1602集成于一个单元,例如输入输出接口或接口电路等等。
可理解,对于以上各个实施例中所示的各个单元的实现还可参照图11所示的方法实施例的相应描述。
作为示例,当图16所示的通信装置的处理单元用处理器实现,接收单元和发送单元集成于一个单元,用收发器实现时,如图17所示。图17是本申请实施例提供的一种通信装置170的结构示意图,可用于实现上述方法中网络设备的功能。可理解,该网络设备可以为源接入网设备;或者目标接入网设备;或者LMC。
装置170包括至少一个处理器1720,用于实现本申请实施例提供的方法中网络设备的功能。具体的,该处理器1720可实现图16所示的处理单元的功能。装置170还可以包括收发器1710。收发器用于通过传输介质和其它设备进行通信。处理器1720利用收发器1710收发数据,并用于实现图16所示的接收单元和/或发送单元的功能。
装置170还可以包括至少一个存储器1730,用于存储程序指令和/或数据。存储器1730和处理器1720耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接,可以是电性,机械或其它的形式,用于装置、单元或模块之间的信息交互。处理器1720可能和存储器1730协同操作。处理器1720可能执行存储器1730中存储的程序指令。所述至少一个存储器中的至少一个可以包括于处理器中。
本申请实施例中不限定上述收发器1710、处理器1720以及存储器1730之间的具体连接介质。本申请实施例在图17中以存储器1730、处理器1720以及收发器1710之间通 过总线1740连接,总线在图17中以粗线表示,其它部件之间的连接方式,仅是进行示意性说明,并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示,图17中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
需要说明的是,本申请实施例对于处理器的类型,不作限定。以及对于存储器的类型,也不作限定。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统、装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另外,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接,也可以是电的,机械的或其它的形式连接。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分,或者该技术方案的全部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(read-only memory,ROM)、随机存取存储器(random access memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
此外,本申请还提供一种计算机程序,所述计算机程序用于执行本申请提供的网络设备切换的方法中由源接入网设备执行的操作和/或处理。
本申请还提供一种计算机程序,所述计算机程序用于执行本申请提供的网络设备切换的方法中由目标接入网设备执行的操作和/或处理。
本申请还提供一种计算机程序,所述计算机程序用于执行本申请提供的网络设备切换的方法中由LMC执行的操作和/或处理。
本申请还提供一种计算机可读存储介质,所述计算机可读存储介质中存储有计算机指令,当计算机指令在计算机上运行时,使得计算机执行本申请提供的网络设备切换的方法中由源接入网设备执行的操作和/或处理。
本申请还提供一种计算机可读存储介质,所述计算机可读存储介质中存储有计算机指令,当计算机指令在计算机上运行时,使得计算机执行本申请提供的网络设备切换的方法由目标接入网设备执行的操作和/或处理。
本申请还提供一种计算机可读存储介质,所述计算机可读存储介质中存储有计算机指令,当计算机指令在计算机上运行时,使得计算机执行本申请提供的网络设备切换的方法 由LMC执行的操作和/或处理。
本申请还提供一种计算机程序产品,所述计算机程序产品包括计算机代码或指令,当所述计算机代码或指令在计算机上运行时,本申请方法实施例的网络设备切换的方法被实现。
本申请还提供一种无线通信系统,包括本申请实施例中的源接入网设备和目标接入网设备。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应以所述权利要求的保护范围为准。

Claims (54)

  1. 一种网络设备切换的方法,其特征在于,所述方法包括:
    源接入网设备向目标接入网设备发送切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述目标接入网设备,所述终端设备处于基于定位管理组件LMC的定位状态;所述切换请求消息中包括第一指示信息,所述第一指示信息用于指示继续在所述源接入网设备执行对所述终端设备的所述基于LMC的定位;
    所述源接入网设备接收所述目标接入网设备发送的切换请求确认消息;
    所述源接入网设备向所述终端设备发送指示消息;其中,所述指示消息用于指示所述终端设备切换到所述目标接入网设备;
    所述源接入网设备接收所述目标接入网设备发送的第一消息,所述第一消息中包括所述终端设备的定位测量结果。
  2. 根据权利要求1所述的方法,其特征在于,所述源接入网设备向目标接入网设备发送切换请求消息之前,所述方法还包括:
    在满足如下条件中的任一项或多项时,所述源接入网设备确定继续在所述源接入网设备执行对所述终端设备的所述基于LMC的定位:
    所述目标接入网设备不支持所述基于LMC的定位;
    或者,所述目标接入网设备不满足所述终端设备的定位服务质量QoS要求;
    或者,所述基于LMC的定位的定位类型为无线接入网触发的定位请求RI-LR。
  3. 根据权利要求2所述的方法,其特征在于,所述源接入网设备向目标接入网设备发送切换请求消息之前,所述方法还包括:
    所述源接入网设备接收所述目标接入网设备发送的第二消息;其中,所述第二消息包括所述目标接入网设备是否支持所述基于LMC的定位和/或所述目标接入网设备支持的定位QoS信息。
  4. 根据权利要求1-3任一项所述的方法,其特征在于,所述源接入网设备接收所述目标接入网设备发送的第一消息之后,所述方法还包括:
    所述源接入网设备根据所述定位测量结果确定所述终端设备的位置信息。
  5. 根据权利要求1-4任一项所述的方法,其特征在于,所述源接入网设备接收所述目标接入网设备发送的第一消息之后,所述方法还包括:
    所述源接入网设备向所述目标接入网设备发送第三消息,所述第三消息用于指示所述基于LMC的定位已结束;
    所述源接入网设备接收所述目标接入网设备发送的上下文释放消息;
    或者,
    所述源接入网设备向所述目标接入网设备发送第四消息,所述第四消息用于指示所述终端设备的上下文已被释放。
  6. 根据权利要求3-5任一项所述的方法,其特征在于,所述第二消息为Xn建立请求消息、Xn建立响应消息或接入网节点配置更新消息中的任一项。
  7. 一种网络设备切换的方法,其特征在于,所述方法包括:
    目标接入网设备接收源接入网设备发送的切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述目标接入网设备,所述终端设备处于基于定位管理组件LMC 的定位状态;且所述切换请求消息中包括第一指示信息,所述第一指示信息用于指示继续在所述源接入网设备执行对所述终端设备的所述基于LMC的定位;
    所述目标接入网设备向所述源接入网设备发送切换请求确认消息;
    所述目标接入网设备接收所述终端设备发送的第五消息,所述第五消息中包括所述终端设备的定位测量结果;
    所述目标接入网设备向所述源接入网设备发送第一消息,所述第一消息中包括所述终端设备的定位测量结果。
  8. 根据权利要求7所述的方法,其特征在于,所述目标接入网设备接收源接入网设备发送的切换请求消息之前,所述方法还包括:
    所述目标接入网设备向所述源接入网设备发送第二消息;其中,所述第二消息中包括所述目标接入网设备是否支持所述基于LMC的定位和/或所述目标接入网设备支持的定位QoS信息。
  9. 根据权利要求7或8所述的方法,其特征在于,所述目标接入网设备向所述源接入网设备发送第一消息之后,所述方法还包括:
    所述目标接入网设备接收所述源接入网设备发送的第三消息,所述第三消息用于指示所述基于LMC的定位已结束;
    所述目标接入网设备向所述源接入网设备发送上下文释放消息;
    或者,
    所述目标接入网设备接收所述源接入网设备发送的第四消息,所述第四消息用于指示所述终端设备的上下文已被释放。
  10. 根据权利要求8或9所述的方法,其特征在于,所述第二消息为Xn建立请求消息、Xn建立响应消息或接入网节点配置更新消息中的任一项。
  11. 一种网络设备切换的方法,其特征在于,所述方法包括:
    源接入网设备向目标接入网设备发送切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述目标接入网设备,所述终端设备处于基于定位管理组件LMC的定位状态,且所述切换请求消息中包括所述基于LMC的定位信息;
    所述源接入网设备接收所述目标接入网设备发送的切换请求确认消息,所述切换请求确认消息中包括第二指示信息,所述第二指示信息用于指示所述源接入网设备继续执行对所述终端设备的所述基于LMC的定位;
    所述源接入网设备向所述终端设备发送指示消息,所述指示消息用于指示所述终端设备切换到所述目标接入网设备;
    所述源接入网设备接收所述目标接入网设备发送的第一消息,所述第一消息中包括终端设备的定位测量结果。
  12. 根据权利要求11所述的方法,其特征在于,所述基于LMC的定位信息包括所述终端设备的定位上下文信息、所述终端设备的定位服务质量QoS要求或定位类型中的一项或多项。
  13. 根据权利要求11或12所述的方法,其特征在于,所述源接入网设备接收所述目标接入网设备发送的第一消息之后,所述方法还包括:
    所述源接入网设备根据所述定位测量结果确定所述终端设备的位置信息。
  14. 根据权利要求11-13任一项所述的方法,其特征在于,所述源接入网设备接收所 述目标接入网设备发送的第一消息之后,所述方法还包括:
    所述源接入网设备向所述目标接入网设备发送第三消息,所述第三消息用于指示所述基于LMC的定位已结束;
    所述源接入网设备接收所述目标接入网设备发送的上下文释放消息;
    或者,
    所述源接入网设备向所述目标接入网设备发送第四消息,所述第四消息用于指示所述终端设备的上下文已被释放。
  15. 一种网络设备的切换方法,其特征在于,所述方法包括:
    目标接入网设备接收源接入网设备发送的切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述目标接入网设备,所述终端设备处于基于定位管理组件LMC的定位状态,且所述切换请求消息中包括所述基于LMC的定位信息;
    所述目标接入网设备向所述源接入网设备发送切换请求确认消息,所述切换请求确认消息中包括第二指示信息,所述第二指示信息用于指示所述源接入网设备继续执行对所述终端设备的所述基于LMC的定位;
    所述目标接入网设备接收所述终端设备发送的第五消息,所述第五消息中包括所述终端设备的定位测量结果;
    所述目标接入网设备向所述源接入网设备发送第一消息,所述第一消息中包括所述终端设备的定位测量结果。
  16. 根据权利要求15所述的方法,其特征在于,所述目标接入网设备向所述源接入网设备发送切换请求确认消息之前,所述方法还包括:
    在满足如下条件中的任一项或多项时,所述目标接入网设备确定继续在所述源接入网设备执行对所述终端设备的所述基于LMC的定位:
    所述目标接入网设备不支持所述基于LMC的定位;
    或者,所述目标接入网设备不满足所述终端设备的定位服务质量QoS要求;
    或者,所述基于LMC的定位的定位类型为无线接入网触发的定位请求RI-LR。
  17. 根据权利要求15或16所述的方法,其特征在于,所述目标接入网设备向所述源接入网设备发送第一消息之后,所述方法还包括:
    所述目标接入网设备接收所述源接入网设备发送的第三消息,所述第三消息用于指示所述基于LMC的定位已结束;
    所述目标接入网设备向所述源接入网设备发送上下文释放消息;
    或者,
    所述目标接入网设备接收所述源接入网设备发送的第四消息,所述第四消息用于指示所述终端设备的上下文已被释放。
  18. 一种网络设备切换的方法,其特征在于,所述方法包括:
    源接入网设备向目标接入网设备发送切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述目标接入网设备,所述终端设备处于基于定位管理组件LMC的定位状态,所述切换请求消息包括所述基于LMC的定位信息;
    所述源接入网设备接收所述目标接入网设备发送的切换请求确认消息;
    所述源接入网设备向终端设备发送指示消息,所述指示消息用于指示切换到所述目标接入网设备。
  19. 根据权利要求18所述的方法,其特征在于,所述基于LMC的定位信息包括所述终端设备的定位上下文信息、所述终端设备的定位服务质量QoS要求、定位类型、所述源接入网络设备的标识ID、所述源接入网设备分配的定位关联标识ID或LMC分配的接口应用协议标识ID中的任一项或多项。
  20. 根据权利要求18或19所述的方法,其特征在于,所述方法还包括:
    所述源接入网设备接收所述目标接入网设备发送的所述终端设备的位置信息;
    所述源接入网设备接收所述目标接入网设备发送的上下文释放消息。
  21. 一种网络设备切换的方法,其特征在于,所述方法包括:
    目标接入网设备接收源接入网设备发送的切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述目标接入网设备,所述终端设备处于基于定位管理组件LMC的定位状态,且所述切换请求消息中包括所述基于LMC的定位信息;
    所述目标接入网设备向所述源接入网设备发送切换请求确认消息;
    所述目标接入网设备接收所述LMC发送的所述终端设备的位置信息。
  22. 根据权利要求21所述的方法,其特征在于,所述基于LMC的定位信息包括所述终端设备的定位上下文信息、所述终端设备的定位服务质量QoS要求、定位类型、所述源接入网络设备的标识ID、所述源接入网设备分配的定位关联标识ID或LMC分配的接口应用协议标识ID中的任一项或多项。
  23. 根据权利要求21或22所述的方法,其特征在于,所述方法还包括:
    所述目标接入网设备向所述源接入设备发送所述终端设备的位置信息;
    所述目标接入网设备向所述源接入网设备发送上下文释放消息。
  24. 一种网络设备切换的方法,其特征在于,所述方法包括:
    定位管理组件LMC接收来自目标接入网设备发送的请求消息;其中,所述请求消息中包括源接入网设备分配的定位关联标识ID和/或所述LMC分配的接口应用协议标识ID;
    基于所述定位关联标识ID和/或所述接口应用协议标识ID确定终端设备的定位上下文;
    所述LMC向所述目标接入网设备发送响应消息。
  25. 根据权利要求24所述的方法,其特征在于,所述方法还包括:
    所述LMC接收所述终端设备发送的第五消息,所述第五消息中包括所述终端设备的定位测量结果;
    所述LMC根据所述终端设备的定位测量结果确定所述终端设备的位置信息;
    所述LMC向所述目标接入网设备发送所述终端设备的位置信息。
  26. 一种通信装置,其特征在于,所述装置包括:
    发送单元,用于向目标接入网设备发送切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述目标接入网设备,所述终端设备处于基于定位管理组件LMC的定位状态;所述切换请求消息包括第一指示信息,所述第一指示信息用于指示继续在所述通信装置执行对所述终端设备的所述基于LMC的定位;
    接收单元,用于接收所述目标接入网设备发送的切换请求确认消息;
    所述发送单元,还用于向所述终端设备发送指示消息;其中,所述指示消息用于指示所述终端设备切换到所述目标接入网设备;
    所述接收单元,还用于接收所述目标接入网设备发送的第一消息,所述第一消息中包 括所述终端设备的定位测量结果。
  27. 根据权利要求26所述的装置,其特征在于,所述装置还包括:
    处理单元,用于在满足如下条件中的任一项或多项时,确定继续在所述通信装置执行对所述终端设备的所述基于LMC的定位:
    所述目标接入网设备不支持所述基于LMC的定位;
    或者,所述目标接入网设备不满足所述终端设备的定位服务质量QoS要求;
    或者,所述基于LMC的定位的定位类型为无线接入网触发的定位请求RI-LR。
  28. 根据权利要求27所述的装置,其特征在于,
    所述接收单元,还用于接收所述目标接入网设备发送的第二消息;其中,所述第二消息包括所述目标接入网设备是否支持所述基于LMC的定位和/或所述目标接入网设备支持的定位QoS信息。
  29. 根据权利要求27或28所述的装置,其特征在于,
    所述处理单元,还用于根据所述定位测量结果确定所述终端设备的位置信息。
  30. 根据权利要求26-29任一项所述的装置,其特征在于,
    所述发送单元,还用于向所述目标接入网设备发送第三消息,所述第三消息用于指示所述基于LMC的定位已结束;
    所述接收单元,还用于接收所述目标接入网设备发送的上下文释放消息;
    或者,
    所述发送单元,还用于向所述目标接入网设备发送第四消息,所述第四消息用于指示所述终端设备的上下文已被释放。
  31. 根据权利要求28-30任一项所述的装置,其特征在于,所述第二消息为Xn建立请求消息、Xn建立响应消息或接入网节点配置更新消息中的任一项。
  32. 一种通信装置,其特征在于,所述装置包括:
    接收单元,用于接收源接入网设备发送的切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述通信装置,所述终端设备处于基于定位管理组件LMC的定位状态;且所述切换请求消息中包括第一指示信息,所述第一指示信息用于指示继续在所述源接入网设备执行对所述终端设备的所述基于LMC的定位;
    发送单元,用于向所述源接入网设备发送切换请求确认消息;
    所述接收单元,还用于接收所述终端设备发送的第五消息,所述第五消息中包括所述终端设备的定位测量结果;
    所述发送单元,还用于向所述源接入网设备发送第一消息,所述第一消息中包括所述终端设备的定位测量结果。
  33. 根据权利要求32所述的装置,其特征在于,
    所述发送单元,还用于向所述源接入网设备发送第二消息;其中,所述第二消息中包括所述通信装置是否支持所述基于LMC的定位和/或所述通信装置支持的定位QoS信息。
  34. 根据权利要求32或33所述的装置,其特征在于,
    所述接收单元,还用于接收所述源接入网设备发送的第三消息,所述第三消息用于指示所述基于LMC的定位已结束;
    所述发送单元,还用于向所述源接入网设备发送上下文释放消息;
    或者,
    所述接收单元,还用于接收所述源接入网设备发送的第四消息,所述第四消息用于指示所述终端设备的上下文已被释放。
  35. 根据权利要求33或34所述的装置,其特征在于,所述第二消息为Xn建立请求消息、Xn建立响应消息或接入网节点配置更新消息中的任一项。
  36. 一种通信装置,其特征在于,所述装置包括:
    发送单元,用于向目标接入网设备发送切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述目标接入网设备,所述终端设备处于基于定位管理组件LMC的定位状态,且所述切换请求消息中包括所述基于LMC的定位信息;
    接收单元,用于接收所述目标接入网设备发送的切换请求确认消息,所述切换请求确认消息中包括第二指示信息,所述第二指示信息用于指示所述通信装置继续执行对所述终端设备的所述基于LMC的定位;
    所述发送单元,还用于向所述终端设备发送指示消息,所述指示消息用于指示所述终端设备切换到所述目标接入网设备;
    所述接收单元,还用于接收所述目标接入网设备发送的第一消息,所述第一消息中包括终端设备的定位测量结果。
  37. 根据权利要求36所述的装置,其特征在于,所述基于LMC的定位信息包括所述终端设备的定位上下文信息、所述终端设备的定位服务质量QoS要求或定位类型中的一项或多项。
  38. 根据权利要求36或37所述的装置,其特征在于,所述装置还包括:
    处理单元,用于根据所述定位测量结果确定所述终端设备的位置信息。
  39. 根据权利要求36-38任一项所述的装置,其特征在于,
    所述发送单元,还用于向所述目标接入网设备发送第三消息,所述第三消息用于指示所述基于LMC的定位已结束;
    所述接收单元,还用于接收所述目标接入网设备发送的上下文释放消息;
    或者,
    所述发送单元,还用于向所述目标接入网设备发送第四消息,所述第四消息用于指示所述终端设备的上下文已被释放。
  40. 一种通信装置,其特征在于,所述装置包括:
    接收单元,用于接收源接入网设备发送的切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述通信装置,所述终端设备处于基于定位管理组件LMC的定位状态,且所述切换请求消息中包括所述基于LMC的定位信息;
    发送单元,用于向所述源接入网设备发送切换请求确认消息,所述切换请求确认消息中包括第二指示信息,所述第二指示信息用于指示所述源接入网设备继续执行对所述终端设备的所述基于LMC的定位;
    所述接收单元,还用于接收所述终端设备发送的第五消息,所述第五消息中包括所述终端设备的定位测量结果;
    所述发送单元,还用于向所述源接入网设备发送第一消息,所述第一消息中包括所述终端设备的定位测量结果。
  41. 根据权利要求40所述的装置,其特征在于,所述装置还包括:
    处理单元,用于在满足如下条件中的任一项或多项时,确定继续在所述源接入网设备 执行对所述终端设备的所述基于LMC的定位:
    所述通信装置不支持所述基于LMC的定位;
    或者,所述通信装置不满足所述终端设备的定位服务质量QoS要求;
    或者,所述基于LMC的定位的定位类型为无线接入网触发的定位请求RI-LR。
  42. 根据权利要求40或41所述的装置,其特征在于,
    所述接收单元,还用于接收所述源接入网设备发送的第三消息,所述第三消息用于指示所述基于LMC的定位已结束;
    所述发送单元,还用于向所述源接入网设备发送上下文释放消息;
    或者,
    所述接收单元,还用于接收所述源接入网设备发送的第四消息,所述第四消息用于指示所述终端设备的上下文已被释放。
  43. 一种通信装置,其特征在于,所述装置包括:
    发送单元,用于向目标接入网设备发送切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述目标接入网设备,所述终端设备处于基于定位管理组件LMC的定位状态,且所述切换请求消息中包括所述基于LMC的定位信息;
    接收单元,用于接收所述目标接入网设备发送的切换请求确认消息;
    所述发送单元,还用于向终端设备发送指示消息,所述指示消息用于指示切换到所述目标接入网设备。
  44. 根据权利要求43所述的装置,其特征在于,所述基于LMC的定位信息包括所述终端设备的定位上下文信息、所述终端设备的定位服务质量QoS要求、定位类型、所述源接入网络设备的标识ID、所述通信装置分配的定位关联标识ID或LMC分配的接口应用协议标识ID中的任一项或多项。
  45. 根据权利要求43或44所述的装置,其特征在于,
    所述接收单元,还用于接收所述目标接入网设备发送的所述终端设备的位置信息;
    所述接收单元,还用于接收所述目标接入网设备发送的上下文释放消息。
  46. 一种通信装置,其特征在于,所述装置包括:
    接收单元,用于接收源接入网设备发送的切换请求消息;其中,所述切换请求消息用于请求将终端设备切换到所述通信装置,所述终端设备处于基于定位管理组件LMC的定位状态,且所述切换请求消息中包括所述基于LMC的定位信息;
    发送单元,用于向所述源接入网设备发送切换请求确认消息;
    所述接收单元,还用于接收所述LMC发送的所述终端设备的位置信息。
  47. 根据权利要求46所述的装置,其特征在于,所述基于LMC的定位信息包括所述终端设备的定位上下文信息、所述终端设备的定位服务质量QoS要求、定位类型、所述源接入网络设备的标识ID、所述源接入网设备分配的定位关联标识ID或LMC分配的接口应用协议标识ID中的任一项或多项。
  48. 根据权利要求46或47所述的装置,其特征在于,
    所述发送单元,还用于向所述源接入设备发送所述终端设备的位置信息;
    所述发送单元,还用于向所述源接入网设备发送上下文释放消息。
  49. 一种通信装置,其特征在于,所述装置包括:
    接收单元,用于接收来自目标接入网设备发送的请求消息;其中,所述请求消息中包 括源接入网设备分配的定位关联标识ID和/或所述LMC分配的接口应用协议标识ID;
    处理单元,用于基于所述定位关联标识ID和/或所述接口应用协议标识ID确定终端设备的定位上下文;
    发送单元,用于向所述目标接入网设备发送响应消息。
  50. 根据权利要求49所述的装置,其特征在于,
    所述接收单元,还用于接收所述终端设备发送的第五消息,所述第五消息中包括所述终端设备的定位测量结果;
    所述处理单元,还用于根据所述终端设备的定位测量结果确定所述终端设备的位置信息;
    所述发送单元,还用于向所述目标接入网设备发送所述终端设备的位置信息。
  51. 一种通信装置,其特征在于,包括处理器、存储器和收发器;
    所述收发器,用于接收信号或者发送信号;
    所述存储器,用于存储程序代码;
    所述处理器,用于执行所述程序代码,以使所述通信装置执行如权利要求1-25任一项所述的方法。
  52. 一种通信装置,其特征在于,包括处理器和接口电路;
    所述接口电路,用于接收代码指令并传输至所述处理器;所述处理器运行所述代码指令以执行如权利要求1-25任一项所述的方法。
  53. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质用于存储指令,当所述指令被执行时,使如权利要求1-25任一项所述的方法被实现。
  54. 一种计算机程序产品,其特征在于,所述计算机程序产品包括指令,当所述指令被执行时,使如权利要求1-25任一项所述的方法被实现。
PCT/CN2020/076080 2020-02-20 2020-02-20 一种网络设备切换的方法及装置 WO2021163977A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2020/076080 WO2021163977A1 (zh) 2020-02-20 2020-02-20 一种网络设备切换的方法及装置
CN202080096062.0A CN115066930B (zh) 2020-02-20 2020-02-20 一种网络设备切换的方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/076080 WO2021163977A1 (zh) 2020-02-20 2020-02-20 一种网络设备切换的方法及装置

Publications (1)

Publication Number Publication Date
WO2021163977A1 true WO2021163977A1 (zh) 2021-08-26

Family

ID=77390354

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/076080 WO2021163977A1 (zh) 2020-02-20 2020-02-20 一种网络设备切换的方法及装置

Country Status (2)

Country Link
CN (1) CN115066930B (zh)
WO (1) WO2021163977A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190053010A1 (en) * 2017-08-14 2019-02-14 Qualcomm Incorporated Systems and methods for 5g location support using service based interfaces
CN110121892A (zh) * 2017-01-09 2019-08-13 高通股份有限公司 用于在第五代无线网络中支持控制平面位置的系统及方法
WO2019192389A1 (en) * 2018-04-03 2019-10-10 Huawei Technologies Co., Ltd. Distributed location management function
CN110636571A (zh) * 2018-06-25 2019-12-31 电信科学技术研究院有限公司 一种终端ue位置服务lcs的确定方法、设备及可读存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110121892A (zh) * 2017-01-09 2019-08-13 高通股份有限公司 用于在第五代无线网络中支持控制平面位置的系统及方法
US20190053010A1 (en) * 2017-08-14 2019-02-14 Qualcomm Incorporated Systems and methods for 5g location support using service based interfaces
WO2019192389A1 (en) * 2018-04-03 2019-10-10 Huawei Technologies Co., Ltd. Distributed location management function
CN110636571A (zh) * 2018-06-25 2019-12-31 电信科学技术研究院有限公司 一种终端ue位置服务lcs的确定方法、设备及可读存储介质

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CMCC: "Study on local NR positioning in NG-RAN", 3GPP DRAFT; RP-190754 NEW STUDY ITEM PROPOSAL ON LOCAL NR POSITIONING IN NG-RAN_CLEAR, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. TSG RAN, no. Shenzhen, China; 20190318 - 20190321, 21 March 2019 (2019-03-21), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051690719 *
ERICSSON: "Positioning Server Functionality and the NG-RAN", 3GPP DRAFT; R3-197289, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Reno, NV, USA; 20191118 - 20191122, 8 November 2019 (2019-11-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051820841 *
QUALCOMM INCORPORATED: "TP for TR 38.856: Impact of UE Mobility", 3GPP DRAFT; R3-195823_[TP FOR TR 38.856 IMPACT OF UE MOBILITY], 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Chongqing, China; 20191014 - 20191018, 4 October 2019 (2019-10-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051810036 *

Also Published As

Publication number Publication date
CN115066930B (zh) 2023-12-15
CN115066930A (zh) 2022-09-16

Similar Documents

Publication Publication Date Title
WO2021203443A1 (zh) 一种定位信息上报的方法及通信装置
JP6908720B2 (ja) コアネットワーク制御プレーンデバイス選択方法および装置
US20230156564A1 (en) Communication path switching method, apparatus, and system
WO2020135850A1 (zh) 通信方法和装置
TWI724775B (zh) 傳輸協定選擇方法及使用者設備
WO2018098609A1 (zh) 一种通信方法及装置
WO2020048422A1 (zh) 定位消息的传输处理方法、设备及终端
JP2021517430A (ja) 通信方法、装置、及びシステム
KR20220021332A (ko) 모바일 네트워크에서 에지 컴퓨팅 서비스 지속성을 지원하기 위한 방법 및 장치
JP5844735B2 (ja) 位置特定プロセス終了方法及び装置
US20210258275A1 (en) Low latency messaging service for the 5gc
US11510257B2 (en) Communications method and apparatus
WO2021047454A1 (zh) 位置信息获取、位置服务配置方法和通信设备
US20230362748A1 (en) Wireless communication method, communication apparatus, and communication system
WO2020164620A1 (zh) 一种终端信息的通信处理方法和相关设备
WO2021163977A1 (zh) 一种网络设备切换的方法及装置
US10827403B2 (en) Data transmission method, user equipment, base station, and system
KR20230124693A (ko) 포지셔닝 설정 방법 및 전자 장치
WO2022110209A1 (zh) 定位方法、通信装置及通信系统
WO2023045843A1 (zh) 定位方法、终端、网络侧设备和存储介质
WO2021146924A1 (zh) 一种定位方法及对应装置
WO2023213183A1 (zh) 一种通信控制方法及通信装置
WO2022042476A1 (zh) 一种定位方法及相关装置
WO2022082708A1 (zh) 通信方法及其相关装置
WO2024082849A1 (zh) 一种通信方法及装置

Legal Events

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

Ref document number: 20920533

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20920533

Country of ref document: EP

Kind code of ref document: A1