Network reselection for a network sharing split architecture

Abstract

The present invention relates to methods, systems, and devices related to digital wireless communication, and more particularly, to techniques related to reselection of a network in a network sharing split architecture. In one exemplary aspect, a method for wireless communication includes a central node associated with a previous network receiving a reroute message from a distributed node, the reroute message indicating reselection of a network for a terminal from the previous network to a new network. The method further includes the central node associated with the previous network sending an allocation message to a central node associated with the new network.

Description

Technical Field

[0001] This patent document generally relates to wireless communication. Background Art

[0002] Mobile communication technologies are driving the world towards an increasingly interconnected and networked society. The rapid growth of mobile communication and technological advancements have led to a greater demand for capacity and connectivity. Other aspects such as energy consumption, device cost, spectral efficiency, and latency are also important for meeting the requirements of various communication scenarios. Currently, various technologies are being discussed, including new methods for providing higher quality services. Summary of the Invention

[0003] This document discloses methods, systems, and devices related to digital wireless communication, and more specifically, discloses techniques related to reselecting a network in a network-sharing split architecture.

[0004] In one exemplary aspect, a method for wireless communication includes a central node associated with a previous network receiving a reroute message from a distributed node, the reroute message indicating a reselection of a network for a terminal from the previous network to a new network. The method further includes the central node associated with the previous network sending an allocation message to a central node associated with the new network.

[0005] In another exemplary aspect, a method for wireless communication includes a distributed node reselecting a network associated with a terminal from a previous network to a new network. The method further includes the distributed node sending a first message to a central node associated with the previous network, the first message including a request for context information related to the terminal.

[0006] In another exemplary aspect, a method for wireless communication includes a central node associated with a new network receiving a reroute message from a distributed node, the reroute message indicating a reselection of a network for a terminal from the previous network to the new network. The method further includes the central node associated with the new network sending a first message to a central node associated with the previous network, the first message including a request for context information related to the terminal.

[0007] In another exemplary aspect, a method for wireless communication includes a distributed node reselecting a network associated with a terminal from a previous network to a new network. The method further includes the distributed node sending a reroute message to a central node associated with the new network, the reroute message requesting terminal context information associated with the terminal. The method further includes the distributed node receiving a reroute response message from the central node associated with the new network.

[0008] In another exemplary aspect, a wireless communication device is disclosed, including a processor. The processor is configured to implement the methods described herein.

[0009] In yet another exemplary aspect, the various techniques described herein may be embodied in processor-executable code stored on a computer-readable program medium.

[0010] Some embodiments may preferably implement the following solutions, which are written in clause form.

[0011] 1. A solution for wireless communication, comprising: receiving, by a central node associated with a previous network, a rerouting message from a distributed node, the rerouting message indicating a network for reselecting a terminal from the previous network for a new network; and sending, by the central node associated with the previous network, an allocation message to a central node associated with the new network.

[0012] 2. The solution according to clause 1, wherein the rerouting message is received via an F1 interface.

[0013] 3. The solution according to clause 1, wherein the allocation message is sent via an Xn interface.

[0014] 4. The solution according to clause 1, wherein the rerouting message includes an F1 Application Protocol Identifier (F1AP ID) assigned by the central node associated with the previous network to the terminal.

[0015] 5. The solution according to clause 1, wherein the rerouting message includes an F1AP ID assigned by the distributed node to the terminal.

[0016] 6. The solution according to clause 1, wherein the distributed node is configured to reselect a network for the terminal from the previous network for the new network based on a Radio Resource Control (RRC) resume completion message received from the terminal.

[0017] 7. The solution according to clause 1, wherein the reallocation message includes at least one of terminal context information and an RRC completion message sent by the terminal.

[0018] 8. The solution according to clause 1, wherein the new network is a Public Land Mobile Network (PLMN) reselected for the terminal, and wherein the new network is indicated in a selected PLMN identity field in the RRC resume completion message sent by the terminal.

[0019] 9. The solution according to clause 1, further comprising: receiving, by the central node associated with the previous network, an allocation response message from the central node associated with the new network; and sending, by the central node associated with the previous network, a rerouting response message to the distributed unit.

[0020] 10. The solution according to clause 9, wherein the allocation response message includes an XN Application Protocol Identifier (XNAP ID) and an F1AP ID.

[0021] 11. The solution according to clause 9, wherein the rerouting response message includes an F1AP ID assigned by a central node associated with the new network.

[0022] 12. A solution for wireless communication, comprising: a distributed node reselecting, from a previous network, a network associated with a terminal for the new network; and the distributed node sending a first message to a central node associated with the previous network, the first message including a request for context information related to the terminal.

[0023] 13. The solution according to clause 12, further comprising: the distributed node receiving a second message from the central node associated with the previous network, the second message including context information related to the terminal.

[0024] 14. The solution according to clause 13, wherein the second message includes any one of the following: a globally unique core network node identifier associated with the terminal, tracking information, international mobile station equipment identity information, a masked version of the international mobile station equipment identity information, and location reporting information.

[0025] 15. The solution according to clause 12, further comprising: the distributed node sending an initial uplink transmission message to a central node associated with the new network; and the distributed node receiving a terminal context establishment message from the central node associated with the new network.

[0026] 16. The solution according to clause 12, wherein the first message includes either an F1AP ID associated with the terminal by the central node associated with the previous network or an F1AP ID associated with the terminal by the distributed node.

[0027] 17. A solution for wireless communication, comprising: a central node associated with the new network receiving a rerouting message from a distributed node, the rerouting message indicating that the network of the terminal is reselected from a previous network for the new network; and the central node associated with the new network sending a first message to the central node associated with the previous network, the first message including a request for context information related to the terminal.

[0028] 18. The solution according to clause 17, further comprising: the central node associated with the new network receiving a second message from the central node associated with the previous network, the second message including context information related to the terminal.

[0029] 19. The solution according to clause 17 further includes: sending an initial terminal message from a central node associated with the new network to a core network node to reselect the terminal for the new network; and receiving an initial terminal response message from the core network node by the central node associated with the new network.

[0030] 20. The solution according to clause 19 further includes: forwarding the received initial terminal response message from the central node associated with the new network to a distributed node to complete the reselection of the network of the terminal.

[0031] 21. A solution for wireless communication includes: reselecting, by a distributed node, a network associated with a terminal from a previous network for a new network; sending, by the distributed node, a reroute message to a central node associated with the new network, the reroute message requesting terminal context information associated with the terminal; and receiving, by the distributed node, a reroute response message from the central node associated with the new network.

[0032] 22. The solution according to clause 21, wherein the reroute response message includes an XN Application Protocol Identifier (XNAP ID) and an F1 Application Protocol Identifier (F1AP ID) assigned by the central node associated with the new network for the terminal.

[0033] 23. The solution according to clause 18 further includes: receiving, by the distributed node, a terminal context establishment message including terminal context information from the central node associated with the new network.

[0034] 24. A device for wireless communication includes a processor configured to execute the solution of any one of clauses 1 to 23.

[0035] 25. A non-transitory computer-readable medium stores code that, when executed by a processor, causes the processor to implement the solution of any one of clauses 1 to 23.

[0036] Details of one or more implementations are set forth in the accompanying appendices, drawings, and the following description. Other features will be apparent from the specification, drawings, and claims. Description of the Drawings

[0037] Figure 1 A schematic diagram of a 5G structure.

[0038] Figure 2 A diagram of a predetermined protocol CU-DU architecture.

[0039] Figure 3 A schematic diagram of a logical connection in an access network element.

[0040] Figure 4A signaling procedure for supporting network sharing functions in a CU-DU split architecture.

[0041] Figure 5 A signaling procedure for reselection of a network in a network sharing scenario with a CU-DU split architecture according to a first exemplary embodiment.

[0042] Figure 6 A signaling procedure for reselection of a network in a network sharing scenario with a CU-DU split architecture according to a second exemplary embodiment.

[0043] Figure 7 A signaling procedure for reselection of a network in a network sharing scenario with a CU-DU split architecture according to a third exemplary embodiment.

[0044] Figure 8 A signaling procedure for reselection of a network in a network sharing scenario with a CU-DU split architecture according to a fourth exemplary embodiment.

[0045] Figure 9 A signaling procedure for reselection of a network in a network sharing scenario with a CU-DU split architecture according to a fifth exemplary embodiment.

[0046] Figure 10 A block diagram showing an example method for reselection of a network in a split network architecture.

[0047] Figure 11 An example of a wireless communication system is shown, to which the techniques according to one or more embodiments of the present technology can be applied.

[0048] Figure 12 A block diagram representation of a part of a hardware platform. Detailed implementation

[0049] The section headings used in this document are for ease of understanding only and do not limit the scope of the embodiments to the sections in which they are described. Further, although the embodiments are described with reference to 5G examples, the disclosed techniques can be applied to wireless systems using protocols other than 5G or 3GPP protocols.

[0050] The development of new generation wireless communication (5G New Radio (NR) communication) is part of the continuous evolution of mobile broadband to meet the growing network demands. NR will provide greater throughput to allow more users to connect simultaneously. Other aspects such as energy consumption, device cost, spectral efficiency, and latency are also important for meeting the requirements of various communication scenarios.

[0051] Overview

[0052] Figure 1It is a schematic diagram of the 5G architecture 100. In some embodiments, this schematic diagram may represent the 5G architecture specified by the 3GPP TS38.300 protocol. As Figure 1 shown, the architecture 100 may include a 5G core network (5GC or 5G Core) and a 5G access network. The 5G core network may include network elements related to the access and mobility management unit (AMF), the user plane function (UPF), and the 5G access network, where the 5G access network may include 5G enhanced eNB base stations (ng-eNB) or 5G base station (gNB) network elements. The interfaces between the network elements of the core network and the network elements of the access network may include the NG interface, and the interfaces between the network elements of the access network may include the Xn interface.

[0053] Figure 2 It is a diagram 200 of the CU-DU architecture for a predetermined protocol. As Figure 2 shown, the interfaces between the CUs of different access network elements may include the Xn interface, and the interfaces between the CU and the DU in the access network element may include the F1 interface.

[0054] Figure 3 It is a schematic diagram 300 of the logical connections in the access network element. As Figure 3 shown, the CU may be divided into a control plane CU (CU-C) and a user plane CU (CU-U). The interface between the DU and the CU-C may be the F1-C interface. The interface between the DU and the CU-U may include the F1-U interface. Different access network elements of the CU-C interface may be between the Xn-C interfaces. Different access network elements of the CU-U interface may be the Xn-U interface. The interface between the CU-C and the core network element may include the NG-C interface, and the interface between the CU-U and the core network element may include the NG-U interface.

[0055] The network sharing architecture allows multiple participating operators to share the resources of a single network according to a negotiated allocation mechanism. The shared network may include a radio access network. Network sharing may include the sharing of radio resources. The allocation mechanism may include planning according to a service level agreement.

[0056] In a scenario where network sharing is not supported, the DU device can only be connected to one CU device. However, in a scenario where network sharing is supported, the DU device can be connected to multiple different CU devices. For example, the DU device supports multiple carrier networks, and the DU device can be connected to multiple CU devices that support different carrier networks. The carrier networks supported by these CU devices may be different.

[0057] Figure 4 It is a signaling process 400 for supporting the network sharing function in the CU-DU separation architecture. As Figure 4As shown, this signaling process can support network sharing functions in a CU-DU split architecture. In this scenario, the gNB DU can support both Network A (PLMN A) and Network B (PLMN B) simultaneously. Therefore, it is labeled as gNB-DU(A / B) in Figure 4 it.

[0058] In step 401, the UE 420 can initiate a resume process. Initiating the resume process may include sending an RRC Resume request message to the gNB DU(A / B) 430 that supports network sharing. As described above, the gNB DU(A / B) 430 can support both Network A (PLMN A) and Network B (PLMN B) simultaneously.

[0059] In step 402, the gNB-DU(A / B) can send an initial UL RRC transfer message to select the first network (Network A). The gNB-DU associated with the UE 420 can select the gNB-CU(A) 440 associated with Network A.

[0060] In step 403, the new gNB-CU(A) 440 can send a retrieve UE context request message to the original gNB(A) 450.

[0061] In step 404, the original gNB(A) 450 can send a UE context response message to the new gNB-CU(A) 440. In steps 403 and 404, the new gNB CU(A) can obtain the UE context from the original gNB(A).

[0062] In step 405, the new gNB-CU(A) can generate an RRC Resume message and send it to the gNB-DU(A / B). The DL RRC transfer message can be sent to the gNB-DU(A / B) via the F1 interface.

[0063] In step 406, the gNB-DU(A / B) 430 can forward the RRC Resume message to the UE 420.

[0064] In step 407, the UE 420 can send an RRC Resume Complete message to the gNB-DU(A / B).

[0065] In step 408, after receiving the RRC Resume Complete message, the gNB-DU(A / B) associated with the UE NAS can select Network B (PLMN B). The gNB-DU is connected to multiple gNB-CUs via the F1 interface, and the gNB-DU can select a new CU.

[0066] However, the context associated with the UE may still not exist on the gNB-CU(A), and there is no flow message used to send the RRC Resume Complete message to the gNB-DU.

[0067] Therefore, the technical problem to be solved may include how to retrieve the UE context from the CU belonging to the previous network to the new CU belonging to the new network to reselect the network.

[0068] System Overview

[0069] This patent document relates to reselecting a network in a network sharing scenario under a CU-DU separation architecture.

[0070] In a first exemplary embodiment, the first step may include the gNB-DU sending a reroute message to the gNB-CU of the current network. This message may be a new message sent via the F1 interface (e.g., reroute RRC message (REROUTE RRCMESSAGE)). The parameters carried by this message may include one or a combination of the following: the F1AP ID assigned by the UE to the source gNB CU; the F1AP ID assigned by the UE in the gNB DU; reselection network CU device information; reselection network information; the RRC Resume Complete message sent by the UE. The gNB-DU of the current network may refer to the gNB-CU selected by the gNB-DU for the UE before receiving the RRC Resume Complete.

[0071] In a second step, the gNB-CU may send a reallocation message to the reselection network gNB-CU. The reallocation message may include a new Xn interface message (e.g., CU node reallocation (CU NODE REALLOCATION)). The reallocation message may include at least the following parameters: UE context information; the RRC Resume Complete message sent by the UE. The reselection network may refer to the PLMN information reselected by the UE and may be in the carrier network included in the selectedPLMN-Identity field in the RRC Resume complete message.

[0072] In a second exemplary embodiment, the first step may include the gNB-DU sending a reroute message to the gNB-CU of the reselection network. The message may be a new F1 message (e.g., a reroute RRC message (REROUTE RRC MESSAGE)). The parameters carried by the message may include one or a combination of the following: the base station where the UE context is located; the F1AP ID assigned by the UE at the base station where the context is located; the F1AP ID assigned by the UE in the gNB DU. Supplementary information such as the UE context ID, integrity protection, new cell identifier, new cell identifier for the UE context may be obtained, and this information is reported by the UE to the gNB-DU.

[0073] The network reselection gNB-CU may refer to the PLMN-Identity field selected in the RRCResumecomplete message at the operator network and at the gNB-CU device to which the gNB-DU is connected.

[0074] In the second step, the gNB-CU may reselect a network base station to obtain the UE context from the base station where the UE context is located. The network reselection gNB-CU may obtain the UE context information via the XN interface by retrieving the UE context message.

[0075] Example Embodiment 1

[0076] Figure 5 A signaling procedure for reselecting a network in a network sharing scenario with a CU-DU split architecture according to a first exemplary embodiment.

[0077] Steps 501 - 506 may be similar to steps 401 - 406 described with respect to Figure 4 The UE 520 may send an RRCResumeRequest UE 520 to the gNB DU supporting network sharing, where the DU may support both network A (PLMN A) and network B (PLMN B) simultaneously. The DU may not know that the UE 520 will reselect a network for this UE 520 of network A which is selected to support the GNB CU (A). The gNB-CU (A) 540 may obtain the context information of the UE 520 from the original gNB 550. The gNB-CU (A) 540 may generate an RRCResume message and send the message to the UE 520.

[0078] In step 507, the UE 520 may send an RRC Resume Complete message to the gNB-DU(A / B) 530. In this message, the UE 520 may select Network B. In the selectedPLMN-Identity IE of this message, the non-access stratum of the UE 520 may select Network B (PLMN B).

[0079] In step 508, the gNB-DU(A / B) 530 may reselect a new network for the UE 520 by selecting the gNB-CU(B) associated with Network B. The gNB DU(A / B) 530 may be connected to multiple gNB CUs supporting different networks simultaneously. When establishing an F1 connection between the gNB CU and the gNB DU, the network information supported by the gNB CU (e.g., gNB-CU(A) supports Network A, gNB CU(B) supports Network B) can be obtained through interactive information. Based on the above information, the gNB DU may select gNB CU(B) because this CU has accessed the reselection network.

[0080] In step 509, the gNB-DU may send a routing message to the gNB-CU(A) 540. Since the gNB CU(A) may include the saved context of the UE 520, the gNB DU may send an F1 interface message, requesting the gNB CU(A) to forward the saved context of the UE 520 to the gNB CU(B). This message may be a new F1 message, such as a rerouted RRC message.

[0081] The parameters carried by this message include one or a combination of the following: the F1AP ID allocated by the UE 520 in the gNB CU(A); the F1AP ID allocated by the UE 520 in the gNB DU; reselection CU information, here it is gNB CU(B); the network information of the reselection CU, here it is PLMN B; and the RRC Resume Complete message sent by the UE 520.

[0082] In step 510, the gNB-CU may send a CU Node Reallocation (UE context) message to the new gNB-CU(B) 650. If the CU supports the CU inter-redirection process, the gNB-CU(A) may send a message to the gNB-CU(B), and this message may include a new incoming message through the Xn interface, such as a CU NODE REALLOCATION (CU Node Reallocation) message.

[0083] The parameters carried by the message include one or a combination of the following: the F1AP ID allocated by the UE 520 in the gNB CU (A); the F1AP ID allocated by the UE in the gNB DU; the UE context content obtained from the original gNB; the UE GUAMI information obtained from the original gNB; the tracing information obtained from the original gNB; the IMEI information, masked IMEISV, this information from the original gNB Location Reporting Information, the information obtained from the original cogNB; and the RRC Resume Complete message sent by the UE 520.

[0084] Step 511 may include sending an initial UE message from the new gNB-CU (B) 560 to the AMF 570.

[0085] Step 512 may include sending an initial context establishment request from the AMF to the new gNB-CU (B).

[0086] In step 513, the new gNB-CU (B) 560 may send a UE CONTEXT SETUPREQUEST (UE context establishment request) message to the gNB-DU (A / B) 530. After the core network is registered, the gNB may send a UE context establishment request message to the DU to complete the registration process.

[0087] Example Embodiment 2

[0088] Figure 6 A signaling process for reselection of a network in a network sharing scenario with a CU-DU split architecture according to a second exemplary embodiment.

[0089] Steps 601-610 may be similar to steps 501-510 described with respect to Figure 5 as described.

[0090] Considering that the relocation function may not be a mandatory system function and not all CUs may support it. Therefore, after the gNB DU sends a reREROUTE RRC MESSAGE (routing RRC message), if the gNB CU (B) does not support the network reselection function, this process may not be executed.

[0091] In step 611, gNB-CU(B) 660 may send a response message to the new gNB-CU(A) 640. If gNB CU(B) supports reselection of network functions, it can respond successfully. New xn interface messages such as the CU NODEREALLOCATION RESPONSE message may be used. This message may include the XNAP ID and F1AP ID assigned by gNB CU(B) to UE 620.

[0092] If gNB CU(B) 660 does not support reselection of network functions, or if the process fails, a failure response may be returned. New XN interface messages such as the CU NODE REALLOCATION FAILURE message may be used.

[0093] In step 612, the new gNB-CU(A) 640 may send a transfer response message to gNB-DU(A / B) 630. After receiving the feedback message from gNB CU(B), gNB CU(A) may send a message to the DU. This message may include information fed back from gNB CU(B), such as the F1AP ID information assigned by gNB CU(B).

[0094] Example Embodiment 3

[0095] Figure 7 For a signaling process for reselection of a network in a network sharing scenario with a CU-DU split architecture according to a third exemplary embodiment. Steps 701-708 may be similar to steps 501-508 described with respect to Figure 5 Those described.

[0096] In step 709, gNB-DU(A / B) 730 may request to receive the UE context on gNB-CU(A) by sending a retrieve UE context request to the new gNB-CU(A) 740. The gNB-DU may determine to hand over UE 720 to network B and the gNB CU(B) base station.

[0097] At this time, the UE context on gNB-CU(A) may need to be sent to the gNB CU(B) base station. The gNB-DU may actively obtain the UE context from the CU. New F1 interface messages such as the RETRIEVE UECONTEXT REQUEST message may be used. Any one of the F1AP ID assigned by UE 720 in gNB CU(A) and the F1AP ID assigned by UE 720 in gNB DU may be included in this message.

[0098] In step 710, the new gNB CU (A) 740 may send the UE context to the gNB-DU (A / B) 730 via a retrieved UE context response message. The message may include the UE context content obtained from the original gNB; the GUAMI information of the UE, which may be obtained from the original gNB; the tracing information obtained from the original gNB; the IMEI information, the masked IMEISV information obtained from the original gNB; and the location reporting information obtained from the original gNB.

[0099] In step 711, the gNB-DU (A / B) 730 may reselect the network for the gNB-CU (B) base station and send an initial UL RRC transfer message to the new gNB-CU (B) 760. The gNB-DU may reuse the existing message Initial UL RRC Message Transfer, but the content included may be the RRC ResumeCompleteIE and may also include the UE context.

[0100] Steps 712 - 714 may include the gNB-DU completing the reselection of the network.

[0101] In step 712, the new gNB-CU (B) 760 may send an initial UE message to the AMF 770.

[0102] In step 713, the AMF 770 may send an initial context establishment request to the new gNB-CU (B). The core network may return a response message to the network to complete the reselection of the gNB-CU (B).

[0103] In step 714, the new gNB-CU (B) may send a UE context establishment request to the gNB-DU (A / B) 730.

[0104] Example Embodiment 4

[0105] Figure 8 It is a signaling process for reselection of a network in a network sharing scenario with a CU-DU separation architecture according to a fourth exemplary embodiment. The fourth exemplary embodiment may include reselection of network devices to actively obtain the UE context.

[0106] Steps 801 - 808 may be similar to steps 501 - 508 described with respect to Figure 5 what is described.

[0107] In step 809, gNB-DU (A / B) 830 may directly send a reselection message to the reselection network via a rerouted RRC message (RRC ResumeComplete) of the new gNB-CU (B) 860. After determining that the UE 820 needs to select a new network, the gNB-DU may select a new network access device for the UE 820. For example, it may be a gNB CU (B) base station. The gNB-DU may need to notify the gNB CU (B) base station of the UE context to be saved on the gNB-CU (A). A new F1 interface message such as REROUTE RRC MESSAGE (rerouted RRC message) may be used.

[0108] The parameters carried by this message include one or a combination of the following: the base station where the UE context is located, here it is gNB CU (A), the F1AP ID allocated by the UE 820 in the gNB CU (A), and the F1AP ID allocated by the UE 820 in the gNB DU. Supplementary information such as integrity protection, new cell identifier, new cell identifier for the UE context can be obtained, and this information is reported by the UE 820 to the gNB-DU.

[0109] Steps 810 - 811 may include reselection of the network base station to obtain the UE context from the base station where the UE context is located. In this example, the gNB CU (B) base station may obtain the UE context from the gNB CU (A) base station. Using the information obtained in step 809, the gNB CU (B) base station may obtain the UE context using the RETRIEVE UE CONTEXT procedure.

[0110] Steps 812 - 814 may include the gNB-DU completing the reselection of the network. The core network may return a response message and complete the reselection of the network for the gNB-CU (B).

[0111] Example Embodiment 5

[0112] Figure 9 A signaling procedure for reselection of a network in a network sharing scenario with a CU-DU split architecture according to a fifth exemplary embodiment.

[0113] In Exemplary Embodiment 5, the gNB-DU 930 may directly send a reselection message to the reselection network and obtain a response message.

[0114] In some embodiments, the relocation function may not be a mandatory system function and not all CUs may support it. Therefore, after the gNB DU may send a REROUTE RRC MESSAGE, if the gNB CU (B) does not support the reselection of network functions, this process may not be executable.

[0115] In step 910, the gNB-CU (B) may receive a REROUTE RRC message response from the gNB-DU (A / B). If the gNB CU (B) supports the reselection of network functions, it can respond successfully. New Xn interface messages such as a REROUTE RRC MESSAGE RESPONSE message may be used. This message may include the XNAP ID and F1AP ID assigned by the gNB CU (B) to the UE 920.

[0116] Figure 10 Block diagram 1000 shows a method for reselection of a network in a network sharing split architecture. The method may include receiving a reroute message from a distributed node, the message indicating a reselection of a network for a terminal from a previous network to a new network (block 1002). A central node associated with the previous network (e.g., the new gNB CU (A) 540 as described) may receive the reroute message from the distributed node (e.g., the gNB DU (A / B) 530 as described). The routing message may include the reroute RRC message 509 as described. Figure 5 as Figure 5 described Figure 5 The routing message may include the reroute RRC message 509 as described.

[0117] The method may further include sending an assignment message to a central node associated with the new network (block 1004). A central node associated with the previous network (e.g., the new gNB CU (A) 540 as described) may send an assignment message to a central node associated with the new network (e.g., the gNB CU (B) 560 as described). The assignment message may include the CU node reassignment message 510 as described. Figure 5 as Figure 5 described Figure 5 The assignment message may include the CU node reassignment message 510 as described.

[0118] In some embodiments, the reroute message is received via the F1 interface.

[0119] In some embodiments, the assignment message is sent via the Xn interface.

[0120] In some embodiments, the reroute message includes an F1 Application Protocol Identifier (F1AP ID) assigned by a central node associated with the previous network to the terminal.

[0121] In some embodiments, the rerouting message includes an F1AP ID assigned by the distributed node to the terminal.

[0122] In some embodiments, the distributed node is configured to reselect, based on a radio resource control (RRC) resume complete message received from the terminal, a network for the terminal from a previous network to a new network.

[0123] In some embodiments, the reassignment message includes at least one of terminal context information and an RRC complete message sent by the terminal.

[0124] In some embodiments, the new network is a public land mobile network (PLMN) reselected for the terminal, and the new network is indicated in a selected PLMN identity field in the RRC resume complete message sent by the terminal.

[0125] In some embodiments, the method includes receiving, by a central node associated with the previous network, an allocation response message from a central node associated with the new network; and sending, by the central node associated with the previous network, a rerouting response message to the distributed unit.

[0126] In some embodiments, the allocation response message includes an XN application protocol identifier (XNAP ID) and an F1AP ID.

[0127] In some embodiments, the rerouting response message includes an F1AP ID assigned by the central node associated with the new network.

[0128] In another embodiment, a method for wireless communication may include reselecting, by a distributed node, a network associated with a terminal from a previous network to a new network. The distributed node (e.g., gNB DU (A / B) 630 as Figure 6 described) may reselect the network in step 608 as Figure 6 described.

[0129] The method may further include sending, by the distributed node, a first message to a central node associated with the previous network, the first message including a request for context information related to the terminal. The first message may include a rerouting RRC message 609 as Figure 6 described. As Figure 6 described, the central node associated with the previous network may include a new gNB CU (A) 640.

[0130] In some embodiments, the method includes receiving, by the distributed node, a second message from a central node associated with the previous network, the second message including context information related to the terminal.

[0131] In some embodiments, the second message includes any one of the following: a globally unique core network node identifier associated with the terminal, tracking information, international mobile station equipment identity information, a masked version of the international mobile station equipment identity information, and location reporting information.

[0132] In some embodiments, the method includes sending, by a distributed node, an initial uplink transfer message to a central node associated with a new network; and receiving, by the distributed node, a terminal context establishment message from the central node associated with the new network.

[0133] In some embodiments, the first message includes either the F1AP ID associated with the terminal by the central node associated with the previous network or the F1AP ID associated with the terminal by the distributed node.

[0134] In another embodiment, a method for wireless communication may include receiving, by a central node associated with a new network, a reroute message from a distributed node, the reroute message indicating a re-selection of a network for the terminal from a previous network for the new network. The reroute message may include a reroute RRC message (RRCRESUMECOMPLETE) 809 as Figure 8 described.

[0135] The method may further include sending, by the central node associated with the new network, a first message to the central node associated with the previous network, the first message including a request for context information related to the terminal. The first message may include a retrieve UE context request 810 as Figure 8 described.

[0136] In some embodiments, the method includes receiving, by a central node associated with a new network, a second message from the central node associated with the previous network, the second message including context information related to the terminal.

[0137] In some embodiments, the method includes sending, by a central node associated with a new network, an initial terminal message to a core network node to re-select the terminal for the new network; and receiving, by the central node associated with the new network, an initial terminal response message from the core network node.

[0138] In some embodiments, the method includes forwarding, by the central node associated with the new network, the received initial terminal response message to the distributed node to complete the re-selection of the network for the terminal.

[0139] In another embodiment, a method for wireless communication may include re-selecting, by a distributed node, a network associated with the terminal from a previous network for the new network. The distributed node (e.g., gNB DU (A / B) 930 as Figure 9 described) may be at a time such as Figure 9In step 908, reselect for gNB CU (B).

[0140] The method may further include a distributed node sending a reroute message to a central node associated with a new network, requesting terminal context information associated with a terminal. The reroute message may include, for example, Figure 9 the reroute RRC message (RRC RESUME MESSAGE) 909 as described.

[0141] The method may further include a distributed node receiving a reroute response message from a central node associated with a new network. The reroute response message may include, for example, Figure 9 the reroute RRC message response 910 as described.

[0142] In some embodiments, the reroute response message includes an XN application protocol identifier (XNAP ID) and an F1 application protocol identifier (F1AP ID) assigned by the central node associated with the new network for the terminal.

[0143] In some embodiments, the method includes a distributed node receiving a terminal context establishment message including terminal context information from a central node associated with a new network.

[0144] Figure 11 An example of a wireless communication system is shown, which may apply techniques according to one or more embodiments of the present technology. The wireless communication system 1100 may include one or more base stations (BSs) 1105a, 1105b, one or more wireless devices 1110a, 1110b, 1110c, 1110d, and a core network 1125. The base stations 1105a, 1105b may provide wireless services to the wireless devices 1110a, 1110b, 1110c, and 1110d in one or more wireless sectors. In some implementations, the base stations 1105a, 1105b include directional antennas to generate two or more directional beams to provide wireless coverage in different sectors.

[0145] The core network 1125 can communicate with one or more base stations 1105a, 1105b. The core network 1125 provides connections to other wireless communication systems and wired communication systems. The core network can include one or more service subscription databases to store information related to the subscribed wireless devices 1110a, 1110b, 1110c, and 1110d. The first base station 1105a can provide wireless services based on a first radio access technology, while the second base station 1105b can provide wireless services based on a second radio access technology. The base stations 1105a and 1105b can be co-located or can be separately installed on-site according to the deployment scenario. The wireless devices 1110a, 1110b, 1110c, and 1110d can support multiple different radio access technologies. In some embodiments, the base stations 1105a, 1105b can be configured to implement some of the technologies described in this document. The wireless devices 1110a to 1110d can be configured to implement some of the technologies described in this document.

[0146] In some implementations, a wireless communication system can include multiple networks using different wireless technologies. Dual-mode or multi-mode wireless devices include two or more wireless technologies that can be used to connect to different wireless networks.

[0147] Figure 12 A block diagram representation of a part of a hardware platform. A hardware platform 1205 such as a network device or a base station or a wireless device (or UE) can include processor electronics 1210 such as a microprocessor that implements one or more of the technologies presented in this document. The hardware platform 1205 can include transceiver electronics 1215 for transmitting and / or receiving wired or wireless signals through one or more communication interfaces such as antennas 1220 or wired interfaces. The hardware platform 1205 can use defined protocols to implement other communication interfaces for sending and receiving data. The hardware platform 1205 can include one or more memories (not explicitly shown) configured to store information such as data and / or instructions. In some implementations, the processor electronics 1210 can include at least a part of the transceiver electronics 1215. In some embodiments, at least some of the disclosed technologies, modules or functions, central nodes, distributed nodes, terminals or network nodes are implemented using the hardware platform 1205.

[0148] From the foregoing, it can be understood that the specific embodiments of the disclosed technology herein are for illustrative purposes, but can be variously modified without departing from the scope of the invention. Therefore, the disclosed technology of the invention is not limited except as by the appended claims.

[0149] The disclosed embodiments and other embodiments, modules, and functional operations described in this document can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware (including the structures disclosed in this document and their structural equivalents), or in a combination of one or more of them. The disclosed embodiments and other embodiments can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by, or to control the operation of, a data processing apparatus. The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a storage device, a composition of matter affecting a machine-readable propagated signal, or a combination of one or more of them. The term “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including, by way of example, a programmable processor, a computer, or multiple processors or computers. In addition to hardware, the apparatus can also include code that creates an execution environment for the computer programs being discussed, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal that is generated to encode information for transmission to a suitable receiver apparatus.

[0150] A computer program (also called a program, software, software application, script, or code) can be written in any form of programming language, including a compiled or interpreted language, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program need not correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program being discussed, or in multiple coordinated files (e.g., files that store one or more modules, subroutines, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

[0151] The processes and logical flows described in this document can be performed by one or more programmable processors that execute one or more computer programs by operating on input data and generating output to perform functions. The processes and logical flows can also be performed by, and the apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit).

[0152] For example, a processor suitable for executing a computer program includes general and special-purpose microprocessors, as well as any one or more processors of any type of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more storage devices for storing instructions and data. Generally, a computer will also include or be operatively coupled to receive data from or transfer data to one or more mass storage devices (such as, for example, magnetic disks, magneto-optical disks, or optical disks) for storing data. However, a computer need not have such devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including, for example, semiconductor memory devices such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in, special-purpose logic circuitry.

[0153] Although this patent document contains many details, these details should not be construed as limiting the scope of any invention or of what may be claimed, but rather as descriptions of features of particular embodiments of a possible invention. Certain features that are described in the context of separate embodiments in this patent document can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented separately in multiple embodiments or in any suitable sub-combination. Moreover, although the above features may be described as acting in certain combinations and even initially claimed as such, in some cases, one or more features from a claimed combination can be deleted from the claimed combination, and the claimed combination can be directed to a sub-combination or a variant of a sub-combination.

[0154] Likewise, although operations are depicted in the drawings in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed to achieve a desired result. Additionally, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.

[0155] Only some implementations and examples have been described, and other implementations, improvements, and variations are possible based on what is described and illustrated in this patent document.

Claims

1. A method for wireless communication, comprising: Receiving, by a central node associated with a previous network, a rerouting message from a distributed node, the rerouting message indicating a network for reselecting a terminal from the previous network for a new network; and Directly sending, by the central node associated with the previous network, an allocation message to a central node associated with the new network, Wherein the allocation message includes terminal context information and a radio resource control (RRC) completion message received from the terminal.

2. The method according to claim 1, wherein the rerouting message is received via an F1 interface.

3. The method according to claim 1, wherein the allocation message is sent via an Xn interface.

4. The method according to claim 1, wherein the rerouting message includes an F1 application protocol identifier (F1AP ID) assigned by the central node associated with the previous network to the terminal.

5. The method according to claim 1, wherein the rerouting message includes an F1AP ID assigned by the distributed node to the terminal.

6. The method according to claim 1, wherein the distributed node is configured to reselect a network for the terminal from the previous network for the new network based on a radio resource control (RRC) resume completion message received from the terminal.

7. The method according to claim 1, wherein the new network is a public land mobile network (PLMN) reselected for the terminal, and wherein the new network is indicated in a selected PLMN identification field in an RRC resume completion message sent by the terminal.

8. The method according to claim 1, further comprising: Receiving, by the central node associated with the previous network, an allocation response message from the central node associated with the new network; And Sending, by the central node associated with the previous network, a rerouting response message to the distributed node.

9. The method according to claim 8, wherein the allocation response message includes an XN application protocol identifier (XNAP ID) and an F1AP ID.

10. The method according to claim 8, wherein the rerouting response message includes an F1AP ID assigned by the central node associated with the new network.

11. A method for wireless communication, comprising: Reselecting, by a distributed node, a network associated with a terminal from a previous network for a new network; Sending, by the distributed node, a first message to a central node associated with the previous network, the first message including a request for context information related to the terminal, After reselecting, sending, by the distributed node, an initial uplink radio resource control (RRC) transfer message to a central node associated with the new network, the initial uplink RRC transfer message including terminal context information and a radio resource control (RRC) completion message received from the terminal; And After sending the initial uplink RRC transfer message, receiving, by the distributed node, a terminal context establishment message from the central node associated with the new network.

12. The method according to claim 11 further comprises: receiving, by the distributed node, a second message from the central node associated with the previous network, the second message including the context information related to the terminal.

13. The method according to claim 12, wherein the second message includes any one of the following: a globally unique core network node identifier associated with the terminal, tracking information, international mobile station equipment identity information, a masked version of the international mobile station equipment identity information, and location reporting information.

14. The method according to claim 12, wherein the terminal context establishment message is received by the central node associated with the new network from an access and mobility management unit (AMF).

15. The method according to claim 11, wherein the first message includes either an F1AP ID associated with the terminal by the central node associated with the previous network or an F1AP ID associated with the terminal by the distributed node.

16. A method for wireless communication, comprising: receiving, by a central node associated with a new network, a rerouting message from a distributed node, the rerouting message indicating a re-selection of a network for a terminal from a previous network for the new network, the distributed node being in the same network as the previous network and the distributed node being in the same network as the new network; and sending, by the central node associated with the new network, a first message to a central node associated with the previous network, the first message including a request for context information related to the terminal; sending, by the central node associated with the new network, a terminal context establishment message including terminal context information to the distributed node.

17. The method according to claim 16 further comprises: receiving, by the central node associated with the new network, a second message from the central node associated with the previous network, the second message including the context information related to the terminal.

18. The method according to claim 16 further comprises: sending, by the central node associated with the new network, an initial terminal message to a core network node to re-select the terminal for the new network; and receiving, by the central node associated with the new network, an initial terminal response message from the core network node.

19. The method according to claim 18 further comprises: forwarding, by the central node associated with the new network, the received initial terminal response message to the distributed node to complete the re-selection of the network for the terminal.

20. A method for wireless communication, comprising: re-selecting, by a distributed node, a network associated with a terminal from a previous network for a new network, the distributed node being in the same network as the previous network and the distributed node being in the same network as the new network; sending, by the distributed node, a rerouting message to a central node associated with the new network, the rerouting message requesting terminal context information associated with the terminal; and The distributed node receives a rerouting response message from the central node associated with the new network. The distributed node receives a terminal context establishment message including terminal context information from the central node associated with the new network.

21. The method according to claim 20, wherein the rerouting response message includes an XN application protocol identifier XNAP ID and an F1 application protocol identifier F1AP ID assigned by the central node associated with the new network to the terminal.

22. An apparatus for wireless communication, comprising a processor and a memory, the processor being configured to read instructions from the memory to perform the method according to any one of claims 1 to 21.

23. A non-transitory computer-readable medium having code stored thereon, which when executed by a processor causes the processor to implement the method according to any one of claims 1 to 21.

Images