Mobile relay base station operation for new radios

Abstract

A user equipment (UE) configured to send a registration request to a base station of a network, the registration request comprising access node (AN) parameters, the access node (AN) parameters comprising an indication of whether the UE is intended to operate as a mobile base station relay; and receive a response to the registration request from the network. An access and mobility management function (AMF) configured to receive a message from a radio access network (RAN), the message comprising an indication of whether a user equipment (UE) is intended to operate as a mobile base station relay; and sending a response to the message to the RAN.

Description

Background Art

[0001] A mobile base station relay may act as a relay between a user equipment (UE) and a network. In some examples, a mobile base station relay may be mounted on a vehicle (e.g., a vehicle mounted relay (VMR)) and serve one or more UEs located inside or outside the vehicle. It has been recognized that enhancements to fifth generation (5G) systems are needed to support the operation of mobile base station relays for wireless access using new radio (NR). Summary of the invention

[0002] Some example embodiments are directed to a processor of a user equipment (UE) configured to perform operations including: sending a registration request to a base station of a network, the registration request including an access node (AN) parameter including an indication of whether the UE intends to operate as a mobile base station relay; and receiving a response to the registration request from the network.

[0003] Other exemplary embodiments relate to an access and mobility management function (AMF) configured to perform operations including: receiving a message from a radio access network (RAN) including an indication of whether a user equipment (UE) intends to operate as a mobile base station relay; and sending a response to the message to the RAN. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Figure 1 Exemplary network arrangements are shown according to various exemplary embodiments.

[0005] Figure 2 An exemplary mobile base station relay is shown in accordance with various exemplary embodiments.

[0006] Figure 3 An exemplary user equipment (UE) is shown in accordance with various exemplary embodiments.

[0007] Figure 4 An exemplary base station according to various exemplary embodiments is shown.

[0008] Figure 5 Exemplary network architectures are shown according to various exemplary embodiments.

[0009] Figure 6 A signaling diagram of a registration procedure according to various exemplary embodiments is shown.

[0010] Figure 7 A signaling diagram is shown when vehicle mounted relay (VMR) / mobile base station relay (MBSR) operation is not allowed according to various exemplary embodiments.

[0011] Figure 8A signaling diagram is shown for restricting the mobility of a mobile base station relay according to various exemplary embodiments.

[0012] Fig. 9 A signaling diagram for configuring mobile base station relay operations when a roaming state changes according to various exemplary embodiments is shown. DETAILED DESCRIPTION

[0013] The exemplary embodiments may be further understood with reference to the following description and associated drawings, wherein similar elements have the same reference numerals. The exemplary embodiments relate to mobile base station relay operations in a fifth generation (5G) new radio (NR) network.

[0014] The exemplary embodiments are described with reference to a user equipment (UE) configured to operate as a mobile base station relay. The term "mobile base station relay" may be used to refer to a mobile network node that acts as a relay between a UE and a network. In some deployment scenarios, a mobile base station relay may be installed on a mobile vehicle and serve one or more UEs located inside or outside the vehicle. This type of mobile base station relay may be referred to as a "vehicle-mounted relay (VMR)". Throughout this specification, the terms "mobile base station relay", "VMR" and "UE" may be used interchangeably to refer to the same device.

[0015] A mobile base relay may attempt to attach to a network and operate as a relay based on its location and movement. However, the mobile base relay may lack the authorization policy and / or configuration required to attach to the network and act as a relay. Therefore, in order to support mobile base relay deployment, a dynamic provisioning mechanism is needed that is configured to provide the mobile base relay with the authorization policy and / or configuration required to attach to the network and act as a relay.

[0016] A mobile base relay may have a home public land mobile network (HPLMN) and roam from its HPLMN to a visited PLMN (VPLMN). As will be described in more detail below, when an integrated access and backhaul (IAB) architecture is used, a mobile base relay may consist of a gNB-donor unit (DU) and an IAB-UE. In a roaming scenario, the IAB-UE may appear as a UE and therefore be able to access the VPLMN using UE procedures. It has been recognized that there is a need for technologies configured to support the gNB-DU component of a mobile base relay.

[0017] A mobile base station relay may serve one or more UEs that move with the mobile base station relay. For example, a UE may be deployed inside a vehicle with a VMR. When the mobile base station relay is no longer able to act as a relay (e.g., moved outside the service area, the service time is full, etc.), one or more UEs may then be served by a base station or another mobile base station relay. In addition, when the mobile base station relay moves to a new location, UEs outside the vehicle may benefit from utilizing the mobile base station relay. Therefore, in some scenarios, it may be beneficial for the UE to move from a serving mobile base station relay to a base station or a second different mobile base station relay. In other scenarios, it may be beneficial for the UE to move from a serving base station to a mobile base station relay. Therefore, a technology configured to support UE mobility between a base station relay and another node (e.g., another mobile base station relay, a base station, etc.) is required.

[0018] The exemplary embodiments introduce various technologies configured to support the deployment of mobile base station relays. The exemplary technologies relate to various different aspects of mobile base station relay operations, including but not limited to the various issues discussed in the examples provided above. For example, some exemplary embodiments relate to registration procedures for UEs to operate as mobile base station relays. Other exemplary embodiments include technologies for implementing authorization policies for mobile base station relay operations. Additional exemplary embodiments include technologies for implementing mobile base station relay operation policies associated with PLMNs. In addition, exemplary embodiments introduce technologies for efficient UE mobility between a mobile base station relay and another node (e.g., a base station, a mobile base station relay, etc.). Each of the exemplary embodiments described herein can be used independently of each other, in combination with a currently implemented mobile base station relay mechanism, a future specific implementation of a mobile base station relay mechanism, or independently of other mobile base station relay mechanisms.

[0019] Figure 1An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a mobile base station relay 110 and a UE 112. The mobile base station relay can be an electronic component (e.g., a VMR) installed to a vehicle or any other type of electronic component configured to communicate with a network. It will be understood by those skilled in the art that the UE 112 can be any type of electronic component configured to communicate via a network, such as a mobile phone, a tablet computer, a desktop computer, a smart phone, a tablet phone, an embedded device, a wearable device, an Internet of Things (IoT) device, etc. In some examples, the mobile base station relay 110 and the UE 112 can be the same type of device. In other examples where the mobile base station relay 110 is a VMR, the UE 112 can be deployed inside or outside the vehicle. It should also be understood that the actual network arrangement may include any number of mobile base station relays and any number of UEs used by any number of users. Therefore, the example of the mobile base station relay 110 and the single UE 112 is provided for illustrative purposes only.

[0020] The mobile base station relay 110 and the UE 112 may be configured to communicate with one or more networks. In the example of the network arrangement 100, the network with which the mobile base station relay 110 and the UE 112 may wirelessly communicate is a 5G NR radio access network (RAN) 120. However, it should be understood that the UE 110 may also communicate with other types of networks (e.g., 5G cloud RAN, next generation RAN (NG-RAN), traditional cellular networks, wireless local area networks (WLAN), etc.), and the mobile base station relay 110 and the UE 112 may also communicate with each other and / or with other networks via a wired connection. Therefore, the mobile base station relay 110 and the UE 112 may each have a 5G NR chipset for communicating with the NR RAN 120, and optionally any other suitable type of chipset for communicating with other types of networks.

[0021] In various examples provided below, mobile base relay 110 may act as a relay between UE 112 and 5G NR RAN 120 / core network 130. Thus, in some examples, UE 112 may send uplink data to 5G NR RAN 120 by first sending one or more signals to mobile base relay 110. Mobile base relay 110 may then communicate with 5G NR RAN 120 over the air (e.g., via gNB 120A) on behalf of UE 112. Similarly, downlink data intended for UE 111 may be sent over the air by gNB 120A to mobile base relay 110, which may then relay the downlink data to UE 112 over the air. However, UE 112 may also be served by gNB 120A.

[0022] 5G NR RAN 120 may be part of a cellular network that may be deployed by a network operator (e.g., Verizon, AT&T, Sprint, T-Mobile, etc.). 5G NR RAN 120 may include cells and base stations configured to transmit and receive traffic from UEs (and relays) equipped with appropriate cellular chipsets. In this example, 5G NR RAN 120 includes gNB 120A. However, reference to gNB is provided for illustrative purposes only, and exemplary embodiments may be utilized with any appropriate type of access node (e.g., Node B, eNodeB, HeNB, eNB, gNB, gNodeB, macro cell, micro cell, small cell, femto cell, etc.).

[0023] Those skilled in the art will appreciate that the mobile base relay 110 and / or the UE 112 may perform any association procedure to connect to the 5G NR RAN 120. For example, as described above, the 5G NR RAN 120 may be associated with a particular network operator, where the mobile base relay 110 and / or its user has a contract and credential information (e.g., stored on a SIM card, etc.). Upon detecting the presence of the 5G NR RAN 120, the mobile base relay 110 may send corresponding credential information in order to associate with the 5G NR RAN 120. More specifically, the mobile base relay may be associated with a particular base station (e.g., gNB 120A).

[0024] The network arrangement 100 includes a cellular core network 130. The cellular core network 130 can be viewed as an interconnected collection of components that manage the operation and traffic of a cellular network. In this example, these components may include an access and mobility management function (AMF) 131, a unified data management (UDM) 132, and a user plane function (UPF) 133. AMF 131 is generally responsible for connection and mobility management in 5G NR RAN 120. Those skilled in the art will appreciate that AMF 131 is a control plane function and can perform operations related to registration management and connection management. For example, AMF 131 can perform operations related to registration management between a mobile base station relay 110 and a network. UDM 132 can process subscription-related information to support various network services. UPF 133 can perform operations related to packet data unit (PDU) session management. For example, UPF 133 can facilitate the connection between a UE and an edge data network.

[0025] Each of the AMF 131, UDM 132, and UPF 133 may be equipped with one or more communication interfaces to communicate with other networks and / or network components (e.g., network functions, RAN, UE, etc.). Those skilled in the art will appreciate that in an actual network arrangement, the AMF 131, UDM 132, and UPF 133 may reside in various physical and / or virtual locations relative to the network arrangement 100. These locations may include the 5G NR RAN 120, the core network 130, as a separate component outside of these locations, etc. In addition, references to a single AMF 131, UDM 132, and UPF 133 are provided for illustrative purposes only, and an actual network arrangement may include any appropriate number of AMFs and UDMs.

[0026] The cellular core network 130 also manages traffic flowing between the cellular network and the Internet 140. The IMS 150 may be generally described as an architecture for delivering multimedia services to the UE 112 using the IP protocol. The IMS 150 may communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 112. The network service backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network service backbone 160 may be generally described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that may be used to extend the functionality of the UE 112 to communicate with various networks.

[0027] Figure 2 An exemplary mobile base station relay 110 is shown in accordance with various exemplary embodiments. Figure 1 The mobile base relay 110 is described with reference to the network arrangement 100 of FIG. The mobile base relay 110 may include a processor 205, a memory arrangement 210, a transceiver 215, and other components 220. The other components 220 may include, for example, audio input / output (I / O) devices, power sources, data acquisition devices, ports for electrically connecting the mobile base relay 110 to other electronic devices, and the like.

[0028] The processor 205 may be configured to execute a plurality of engines of the mobile base station relay 110. For example, the engines may include a relay engine 225. The relay engine 225 may perform various operations related to operating as a relay between one or more UEs and a 5G NR network.

[0029] The relay engine 225 described above is provided as an application (e.g., program) executed by the processor 205 for illustrative purposes only. The functionality associated with the relay engine 225 may also be represented as a separate combined component of the mobile base station relay 110, or may be a modular component coupled to the mobile base station relay 110, such as an integrated circuit with or without firmware. For example, an integrated circuit may include an input circuit for receiving a signal and a processing circuit for processing the signal and other information. The engine may also be embodied as an application or a separate application. In addition, in some devices, the functionality described for the processor 205 is shared between two or more processors (such as a baseband processor and an application processor). The exemplary embodiments may be implemented in any of these or other configurations of the mobile base station relay.

[0030] The memory arrangement 210 may be a hardware component configured to store data related to operations performed by the mobile base station relay 110. The transceiver 215 may be a hardware component configured to establish a connection with the UE 112, the 5G NR-RAN 120, etc. Thus, the transceiver 215 may operate on a plurality of different frequencies or channels (e.g., a set of contiguous frequencies).

[0031] Figure 3 An exemplary UE 112 is shown according to various exemplary embodiments. Figure 1 100 is used to describe the UE 112. The UE 112 may include a processor 305, a memory arrangement 310, a display device 315, an input / output (I / O) device 320, a transceiver 325, and other components 330. The other components 330 may include, for example, an audio input device, an audio output device, a power source, a data acquisition device, a port for electrically connecting the UE 112 to other electronic devices, etc.

[0032] The processor 305 may be configured to execute multiple engines of the UE 112. For example, these engines may include a mobile base station relay engine 335. The mobile base station relay engine 335 may perform various operations related to establishing and maintaining a connection with a 5G NR network via a base station relay 110. The mobile base station relay engine 335 described above is provided as an application (e.g., a program) executed by the processor 305 for illustrative purposes only. The functionality associated with the mobile base station relay engine 335 may also be represented as a separate combined component of the UE 112, or may be a modular component coupled to the UE 112, such as an integrated circuit with or without firmware. For example, an integrated circuit may include an input circuit for receiving a signal and a processing circuit for processing a signal and other information. The engine may also be embodied as an application or a separate application. In addition, in some UEs, the functionality described for the processor 305 is shared between two or more processors (such as a baseband processor and an application processor). The exemplary implementation scheme may be implemented in any of these or other configurations of the UE.

[0033] The memory arrangement 310 may be a hardware component configured to store data related to operations performed by the UE 112. The display device 315 may be a hardware component configured to display data to a user, and the I / O device 320 may be a hardware component that enables user input. The display device 315 and the I / O device 320 may be separate components or may be integrated together (such as a touch screen). The transceiver 325 may be a hardware component configured to establish a connection with the 5G NR-RAN 120, LTE-RAN (not shown), traditional RAN (not shown), WLAN (not shown), etc. Thus, the transceiver 325 can operate on a variety of different frequencies or channels (e.g., a set of continuous frequencies).

[0034] Figure 4 An exemplary base station 400 is shown according to various exemplary embodiments. Base station 400 may represent a gNB 120A or any other suitable type of network access node.

[0035] The base station 400 may include a processor 405, a memory arrangement 410, an input / output (I / O) device 415, a transceiver 420, and other components 425. The other components 425 may include, for example, an antenna panel, a data acquisition device, a port for electrically connecting the base station 400 to other electronic devices and / or a power source, and the like.

[0036] Processor 405 may be configured to execute multiple engines of base station 400. For example, the engines may include a mobile base relay engine 430. Mobile base relay engine 430 may perform various operations related to registration of a mobile base relay and communicating with one or more UEs via the mobile base relay.

[0037] The above-described mobile base station relay engine 430 as an application (e.g., program) executed by the processor 405 is merely exemplary. The functionality associated with the mobile base station relay engine 430 may also be represented as a separate combined component of the base station 400, or may be a modular component coupled to the base station 400, such as an integrated circuit with or without firmware. For example, an integrated circuit may include input circuits for receiving signals and processing circuits for processing signals and other information. In addition, in some base stations, the functionality described for the processor 405 is shared between multiple processors (e.g., baseband processors, application processors, etc.). The exemplary embodiments may be implemented in any of these or other configurations of the base station.

[0038] The memory arrangement 410 may be a hardware component configured to store data related to operations performed by the base station 400. The I / O device 415 may be a hardware component or port that enables a user to interact with the base station 400. The transceiver 420 may be a hardware component configured to exchange data with the mobile base station relay 110, the UE 112, and any other device in the network arrangement 100. The transceiver 420 may operate on a plurality of different frequencies or channels (e.g., a set of contiguous frequencies).

[0039] Figure 5 Exemplary network architectures according to various exemplary embodiments are shown. The following description will provide a general overview of the various components of the exemplary architectures 500 and 550. The description of the architectures 500 and 550 will be followed by a more detailed description of specific operations performed by the components with respect to the exemplary embodiments.

[0040] Those skilled in the art will appreciate that components of the exemplary architectures 500 and 550 may reside in a manner relative to Figure 1 The network arrangement 100 may be in various physical and / or virtual locations. These locations may include: within an access network (e.g., 5G NR RAN 120), within a core network 130, as part of a Figure 1 Individual components outside the described positions, etc.

[0041] exist Figure 5In the example, various components are shown as being connected via interfaces labeled Nx (e.g., N1, N2, N3), Uu, PC5, Xn, and F1. Those skilled in the art will appreciate that each of these interfaces is defined in the 3GPP specifications. Exemplary architectures 500 and 550 use these interfaces in the manner in which they are defined in the 3GPP specifications and may be modified according to the exemplary embodiments described herein. In addition, it should be understood that these interfaces do not require direct wired or wireless connections, for example, these interfaces may communicate via intermediate hardware and / or software components. In addition, it should be understood that these interfaces do not require direct wired or wireless connections, for example, these interfaces may communicate via intermediate hardware and / or software components. To provide an example, UE 112 may exchange signals with gNB 120A over the air. However, in architecture 500, UE 112 is shown as having a connection with AMF 131. The interface is not a direct communication link between UE 110 and AMF 131, but a connection facilitated by intermediate hardware and software components. Therefore, throughout this specification, the terms “connection” and “interface” may be used interchangeably to describe the different interfaces between various components in the exemplary architectures 500 and 550 .

[0042] The exemplary architectures 500 and 550 are described with reference to integrated access and backhaul (IAB). Those skilled in the art will appreciate that IAB refers to a concept in which a terminal device uses the same access technology to access a base station and the base station itself uses the same access technology to access a wireless backhaul. In some examples, the mobile base station relay 110 may be considered an IAB node.

[0043] The exemplary architecture is also described with reference to the logical architecture of a gNB including a central unit (CU) and a distributed unit (DU). The term "gNB-CU" may refer to a logical node connected to the core network and one or more gNB-DUs. The term "gNB-DU" may refer to a logical node connected to the gNB-CU. However, references to the terms "gNB-CU" and "gNB-DU" are provided for illustrative purposes only. Different entities may refer to similar concepts by different names.

[0044] The architecture 500 includes a core network 130 (e.g., 5G core (5GC)), a gNB 120A, a donor gNB 505, a UE 112, and a mobile base station relay 110. The UE 112 may be connected to the gNB 120A via a Uu interface and to the AMF 131 via an N1 interface. The gNB 120A may be connected to the UPF 133 via an N3 interface and to the AMF 131 via an N2 interface.

[0045] The mobile base station relay 110 may be connected to the donor gNB 505 via a Uu interface and to the AMF 131 via an N1 interface. The donor gNB 505 may be connected to the UPF 133 via an N3 interface and to the AMF 131 via an N2 interface. In addition, the donor gNB 505 may be connected to the gNB 120A via an Xn interface. Those skilled in the art will appreciate that the term "donor" may refer to a node configured to serve a relay node. Thus, in the architecture 500, the donor gNB 505 may serve the mobile base station relay 110.

[0046] UE 112 may be connected to mobile base station relay 110 via a Uu interface and / or a PC5 interface. Thus, UE 112 may be connected to core network 130 via gNB 120A and / or mobile base station relay 110.

[0047] The architecture 550 includes the AMF 131, the donor gNB CU 555 of the gNB 120A, and the mobile base station relay 110 including the VMR UE 560 and the VMR relay DU 561. The AMF 131 may be connected to the UE 112 via an N1 interface and to the VMR UE 560 via an N1 interface. The donor gNB CU 555 may control the VMR DU 561 via an F1 interface. The VMR UE 560 may be connected to the donor gNB CU via a Uu interface. The UE 112 may be connected to the VMR DU 561 via a Uu interface.

[0048] According to one aspect, an exemplary embodiment is directed to a UE registering with a network to operate as a mobile base relay (eg, VMR, etc.). Figure 6 A signaling diagram 600 of a registration procedure according to various exemplary embodiments is shown. The signaling diagram 600 includes a mobile base station relay 110, a 5G NR RAN 120, an AMF 131 and a UDM 132.

[0049] In 605, the mobile base station relay 110 sends a registration request to the 5G NR RAN 120. For example, the UE may send a registration request to the gNB 120A indicating that the UE wants to operate as a mobile base station relay (MBSR), a VMR, etc.

[0050] The registration request may include access node (AN) parameters. In some embodiments, the AN parameters may include an IAB indication indicating that the mobile base station relay 110 intends to operate as an IAB node. In addition, the AN parameters may include a VMR / MBSR indication indicating that the mobile base station relay 110 is a VMR / MBSR node attempting to attach to the 5G system. Therefore, the UE can inform the network that the UE is a stationary IAB node, a normal UE, or a mobile base station relay (VMR, MBSR, etc.). In the absence of a VMR / MBSR indication, the network may not know whether the requesting node (e.g., the mobile base station relay 110) is capable of mobile base station relay operations.

[0051] In 610, the 5G NR RAN 120 selects an AMF. The 5G NR RAN 120 may select an AMF for the mobile base station relay 110 that supports mobile base station relay operation. In this example, the 5G NR RAN 120 selects the AMF 131.

[0052] To provide an example in the context of architecture 550, when establishing a radio resource control (RRC) connection, the mobile base station relay 110 may transmit a VMR / MBSR indication to the donor gNB CU 555 of the gNB 120A. The donor gNB CU 555 may select an AMF that supports mobile IAB and / or MBSR. The donor GNB CU may include the VMR / MBSR indication in the N2 Initial UE 110 message so that the AMF may perform MBSR authorization.

[0053] In 615, the 5G NR RAN 120 sends a registration request to the AMF 131. For example, the request may be sent over the N2 interface and include an establishment cause. In addition, the AMF 131 may provide the IAB indication and the VMR / MBSR indication provided by the mobile base station relay 110 in the AN parameters.

[0054] In 620, AMF 131 sends a Nudm_SDM_Get service operation to UDM 132. Those skilled in the art will appreciate that a network function may use the Nudm_SDM_Get service operation to retrieve subscriber data from the UDM. The Nudm_SDM_Get service operation may include a network function ID and a subscription data type (e.g., VMR, MBSR, etc.).

[0055] In 625, UDM 132 sends a Nudm_SDM_Get response to AMF 131. In this example, UDM 132 checks the subscription information of mobile base station relay 110 and provides a VMR / MBSR operation allowed indication to AMF 131 as part of the access and mobile subscription data provided in the response message. In addition, UDM 132 may provide an IAB operation allowed indication.

[0056] In 630, the AMF 131 and the 5G NR RAN 120 establish a UE context for the mobile base station relay 110. In one example, the AMF 131 and the 5G NR RAN 120 may establish an appropriate UE context for the mobile base station 110 to operate as a VMR / MBSR. In another example, the AMF 131 and the 5G NR RAN 120 may modify the UE context for the mobile base station relay 110 if the functionality was not previously authorized. In 635, the 5G NR RAN 120 transmits a registration accept message to the mobile base station relay 110. In this example, the registration accept message may indicate that VMR / MBSR operation is allowed and that IAB operation is allowed.

[0057] In another aspect, example embodiments include techniques for implementing a mobile base station relay operation strategy associated with a PLMN. Figure 7 A signaling diagram 700 is shown when VMR / MBSR operation is not allowed according to various exemplary embodiments. The signaling diagram 700 includes a mobile base station relay 110, a HPLMN 702, and a VPLMN 704.

[0058] First, assume a scenario where the mobile base relay 110 is connected to the HPLMN 702 and is moving towards the VPLMN 704. However, while this example is described with reference to a PLMN, those skilled in the art will appreciate that similar signaling exchanges may be used when the mobile base relay is moving between registration areas (RAs).

[0059] In 705, the mobile base relay 110 sends a registration request to the VPLMN 704. The registration request may indicate that the request is for an initial registration or a mobility registration. In addition, the request may include a VMR / MBSR indication indicating that the mobile base relay 110 wants to attach to the VPLMN 704 and operate as a mobile base relay.

[0060] At 710, the VPLMN 704 may send a registration accept message to the mobile base relay 110. However, in this example, the mobile base relay is not authorized to operate in the VPLMN 704. Therefore, the registration accept message may include an indication that VMR / MBSR operation is not allowed. Therefore, the rejection message may be configured to let the UE know whether the UE can operate as a mobile base relay, a normal UE, or both.

[0061] In response to the registration accept message, the mobile base station relay 110 may operate as a normal UE within the VPLMN 704, but is not allowed to operate as a mobile base station relay. For example, the mobile base station relay 110 may connect to the VPLMN 704 as a UE for operations, administration and maintenance (OAM) or emergency services.

[0062] In some embodiments, a backoff timer may be triggered in response to an indication that VMR / MBSR operation is not permitted. When the backoff timer expires, mobile base relay 110 may send a registration request to VPLMN 704 requesting operation as a VMR / MBSR. In other embodiments, location-based conditions may be used to trigger subsequent registration requests from mobile base relay 110 to VPLMN 704. For example, location-based conditions may include, but are not limited to, one or more of the following factors: a change in serving cells within VPLMN 704, a change in signal strength or quality from a serving cell, a change in location, or a predicted change in location. When a condition is identified, mobile base relay 110 may send a registration request to VPLMN 704 requesting operation as a VMR / MBSR.

[0063] As described above, there may be scenarios where the mobile base relay 110 is not authorized to operate as a VMR / MBSR in the PLMN but may be connected to the PLMN as a UE for other services (e.g., OAM, emergency, etc.). According to some aspects, exemplary embodiments introduce techniques in which the mobile base relay 110 may store information regarding whether the mobile base relay 110 is permitted to operate as a VMR / MBSR.

[0064] In some embodiments, mobile base relay 110 may store information about PLMNs and allowed VMR / MBSR operations. Mobile base relay 110 may consider this information when selecting a PLMN during a PLMN search. For example, since mobile base relay 110 may prefer to attach to a PLMN that allows VMR / MBSR operations, mobile base relay 110 may consider this information when selecting between multiple PLMNs. Without this information, mobile base relay 110 may be able to register with a PLMN as a UE, but may not know whether VMR / MBSR operations are permitted on that PLMN.

[0065] In other embodiments, mobile base relay 110 may store information about PLMNs and PLMNs that do not allow VMR / MBSR operation. Mobile base relay 110 may consider this information when selecting a PLMN during a PLMN search. For example, since mobile base relay 110 may prefer to attach to a PLMN that allows VMR / MBSR operation, mobile base relay 110 may consider this information when selecting between multiple PLMNs. Without this information, mobile base relay 110 may attempt to register on a PLMN that does not support VMR / MBSR operation, which may result in delays in the initiation or resumption of VMR / MBSR operation.

[0066] The above examples may be used to implement an authorization policy for acting as a 5G VMR / MBSR node (e.g., an IAB node with mobility functionality). The authorization policy may include providing an indication of whether a node (e.g., a mobile base station relay 110) attempting to register with the network can perform IAB, VMR, and / or MBSR operations. The authorization policy may also include the PLMNs in which the node is authorized to perform VMR / MBSR operations. This may be configured by using a list of operator PLMNs (OPLMNs) for roaming guidance (SoR) for VMR / MBSR operations and normal UE operations.

[0067] In some embodiments, the mobile base station relay 110 may have operational requirements for OAM, layer 2 (L2) relay or PC5 discovery, mobility assistance and control between relays. It has been recognized that two types of policies are required for these operations, namely UE routing selection policy (URSP) and proximity service (ProSe) policy. For URSP, if the 5GC supports VMR / MBSR operation for the UE (e.g., mobile base station relay 110), the mobile base station relay 110 can follow the procedures from 3GPP TS23.50 and the policy framework for UE URSEP policy from 3GPP TS23.505. For PC5 policy, the mobile base station relay 110 can follow the ProSe policy for ProSe-related policy from 3GPP TS 23.304. Therefore, for VMR / MBSR (e.g., IAB node) mobility, the PDU operation policy for the 5GC connection may include session parameters (e.g., PDU session type, data network name (DNN), session and service continuity (SSC) mode, single network slice selection assistance information (S-NSSAI), access type preference), which will be used for connectivity between the mobile base station relay 110 and the 5GC for relaying traffic to and from the UE.

[0068] The exemplary embodiments also introduce techniques for implementing next hop policies. In conventional cases, when roaming, the VPLMN, RAN and / or OAM may not have next hop parameters defined for the roaming mobile base station relay 110. However, it would be beneficial for the HPLMN to provide an operational policy for HPLMN and VPLMN operations.

[0069] In some embodiments, the HPLMN may configure the mobile base station relay 110 with radio parameters for IAB, VMR, and / or MBR operations. These radio parameters may include frequencies that allow IAB, VMR, and / or MBSR operations in geographic areas where IAB / VMR / MBSR nodes are allowed to operate. This may include a tracking area (TA) or a registration area (RA) in which the operation is valid. In addition, the HPLMN may provide quality of service (QoS) mapping entries for services that may be supported by the mobile base station relay 110 and provided to the served UEs.

[0070] The exemplary embodiment introduces a VMR / MBSR policy container, which may be provided to the mobile base station 110 to inform the mobile base station 110 of relevant policies for VMR / MBSR operations. The VMR / MBSR policy container may include authorization policy information, operation policy information, radio parameters for IAB / VMR / MBSR operations, QoS mapping information, and any other relevant policies. The authorization policy information may include information for acting as a 5G VMR / MBSR node (e.g., an IAB node with mobility functionality), such as an indication of whether the current node can perform IAB / VMR / MBSR operations, PLMNs where the IAB is authorized to perform VMR / MBSR operations in mobility and configurable by the SoR during roaming (a list of OPLMNs for UE VMR / MBSR operations or UE normal operations). The operation policy information may include information for 5GC connections, such as information for CMR / MBSR mobility, PDU session parameters to be used for connectivity between VMR / MBSR and 5GC for relaying UE traffic. The radio parameters for IAB / VMR / MBSR operation may include radio parameters with a geographical area in which the IAB / VMR / MBSR node is allowed to operate, and may also include a tracking area / registration area in which the operation will be valid. The QoS mapping information may include QS mapping entries for services that can be supported and provided to the served UE.

[0071] The exemplary embodiments also introduce techniques for limiting the mobility of mobile base station relay 110 to the VPLMN. Figure 8 A signaling diagram 800 is shown for limiting the mobility of a moving base relay 110 in accordance with various exemplary embodiments.

[0072] The signaling diagram 800 includes the mobile base station relay 110, the HPLMN 802, and the VPLMN 804. First, a scenario in which the mobile base station relay is connected to the HPLMN 802 and moves to the VPLMN 804 is assumed.

[0073] In 805, mobile base station relay 110 may send a registration request to VPLMN 804. For example, mobile base station relay 110 may perform a mobility update after moving from HPLMN 802 to VPLMN 804.

[0074] In 810, VPLMN 804 may send a registration reject message to mobile base station relay 110. Alternatively, VPLMN 804 may send a deregistration request to mobile base station 110.

[0075] In one example, when the target gNB belongs to a VPLMN and / or TA / RA that does not support VMR / MBSR operation or does not allow VMR / MBSR operation, the AMF of the VPLMN 804 may reject the registration request or transmit a deregistration request with rejection reasons #11, #13, and / or #15 to the mobile base station relay 110. Subsequently, the mobile base station relay 110 may search for other cells and / or PLMNs.

[0076] In another example, the mobile base station relay 110 may release the f1 interface and remain connected as a normal UE. This may be defined in the VMR / MBSR policy as to whether in certain TA / RA / PLMN or geographical areas, the VMR / MBSR UE may operate as a normal UE when returning to an area where mobile base station relay operation is allowed.

[0077] The exemplary embodiments also introduce techniques for performing mobile base station relay configuration when roaming status changes. Fig. 9 A signaling diagram 900 is shown for configuring mobile base station relay operations when a roaming state changes according to various exemplary embodiments.

[0078] The signaling diagram 900 includes a mobile base station relay 110, a donor gNB of the HPLMN (H-donor gNB) 901, a donor gNB of the VPLMN (V-donor gNB) 902, the HPLMN 903, and an AMF of the VPLMN (V-AMF) 904. First, a scenario in which the mobile base station relay 110 is connected to the HPLMN 903 is assumed.

[0079] In 905, the HPLMN 903 sends a downlink non-access stratum (NAS) transfer message to the H-donor gNB 901. The message may include SoR information including an information element (IE) indicating that VMR / MBSR operation allowed in roaming will be added. In 910, the H-donor gNB may transmit a downlink NAS transfer message including the SoR information and an IE indicating that VMR / MBSR operation allowed in roaming will be added.

[0080] In 915, the mobile base station relay 110 moves to the geographic area served by the VPLMN. In 920, the mobile base station relay 110 performs a PLMN search for the VPLMN based on the SoR information received from the H-donor gNB 901.

[0081] In 925, the mobile base station relay 110 sends a registration request to the V-donor gNB 902. In 930, the V-donor gNB 902 sends a registration request to the V-AMF 904. In 935, the V-AMF 904 may send a registration accept message to the V-donor gNB 902. The registration accept message may include the "VMR / MBSR PLMN List / TA" IE described herein. This IE may allow the mobile base station relay to be shared between multiple operators.

[0082] In 940, the V-Donor gNB 902 sends a Registration Accept message to the mobile base station relay 110. In 945, the mobile base station relay 110 broadcasts a new PLMN list to serve the UE.

[0083] Example

[0084] In a first embodiment, a method performed by a user equipment (UE) comprises: sending a registration request to a base station of a network, the registration request comprising an access node (AN) parameter, the access node (AN) parameter comprising an indication of whether the UE intends to operate as a mobile base station relay; and receiving a response to the registration request from the network.

[0085] In a second embodiment, the method according to the first embodiment, wherein the indication is provided to a donor centralized unit (CU) of the base station when a radio resource control (RRC) connection is established by the UE.

[0086] In a third embodiment, according to the method of the first embodiment, the response is a registration accept message, the registration accept message including an indication that mobile base station relay operation is not permitted.

[0087] In a fourth embodiment, the method according to the third embodiment further includes: starting a backoff timer in response to the indication included in the registration acceptance message; and sending a second registration request to the base station of the network, wherein the second registration request includes the indication of whether the UE intends to operate as a mobile base station relay.

[0088] In a fifth embodiment, the method according to the third embodiment further includes: identifying a location-based condition after receiving the registration acceptance message; and sending a second registration request to the base station of the network, the second registration request including the indication of whether the UE intends to operate as a mobile base station relay, wherein sending the second registration request is triggered based on identifying the location-based condition.

[0089] In a sixth embodiment, the method according to the first embodiment further includes: storing information associated with one or more public land mobile networks (PLMNs), the information including an indication for each of the one or more PLMNs indicating whether mobile base station relay operation is allowed or not.

[0090] In a seventh embodiment, the method according to the first embodiment further comprises: receiving radio parameters for mobile base station relay operation, the radio parameters comprising an operating frequency and a geographical area where the mobile base station relay operation is allowed.

[0091] In an eighth embodiment, the method according to the first embodiment further comprises: receiving at least one of a radio parameter for a mobile base station relay operation, a tracking area (TA) or a registration area (RA) allowing a mobile base station relay operation.

[0092] In a ninth embodiment, the method according to the first embodiment further comprises: receiving a quality of service (QoS) mapping entry for services that the UE can support when operating as the mobile base station relay and serving other UEs.

[0093] In a tenth embodiment, the method according to the first embodiment further includes: receiving a policy container, wherein the policy container includes information for one or more of the following items: an authorization policy for operating as a mobile base station relay, an operation policy for a fifth generation (5G) core (5GC) connection, radio parameters for mobile base station relay operation, and quality of service (QoS) mapping entries for services that the UE can support when operating as the mobile base station relay and serving other UEs.

[0094] In an eleventh embodiment, according to the method of the first embodiment, the response to the registration request is a registration reject message, the registration reject message including one or more rejection reasons indicating that the network does not support or allow mobile base station relay operation.

[0095] In a twelfth embodiment, according to the method of the first embodiment, the response to the registration request is a deregistration request message, the deregistration request message indicating that the network does not support or allow mobile base station relay operation.

[0096] In a thirteenth embodiment, according to the method of the first embodiment, wherein the response to the registration request is a registration reject message or a deregistration request, the method further comprising releasing an F1 interface based on the response, wherein the UE remains connected to the network.

[0097] In a fourteenth embodiment, the method according to the first embodiment further comprises: receiving an information element (IE) from a home public land mobile network (HPLMN), the IE comprising an indication of allowing mobile base station relay operation in a roaming scenario.

[0098] In a fifteenth embodiment, the method according to the first embodiment further comprises: a registration accept message including an information element (IE) indicating a list of public land mobile networks (PLMNs) supporting mobile base station relay operations.

[0099] In a sixteenth embodiment, one or more processors are configured to perform any of the methods described in the first to fifteenth embodiments.

[0100] In a seventeenth embodiment, a user equipment (UE) comprises: a transceiver configured to communicate with a base station; and one or more processors, the one or more processors being communicatively coupled to the transceiver and configured to perform any of the methods described in the first to fifteenth embodiments.

[0101] In an eighteenth embodiment, a method comprises: receiving a message from a radio access network (RAN), the message comprising an indication of whether a user equipment (UE) intends to operate as a mobile base station relay; and sending a response to the message to the RAN.

[0102] In a nineteenth embodiment, the method according to the eighteenth embodiment, wherein the message is an N2 initial UE message.

[0103] In a twentieth embodiment, the method according to the eighteenth embodiment further comprises: receiving a Nudm_SDM_Get response from a unified data management (UDM) indicating whether the UE is permitted to operate as a mobile base station relay.

[0104] In a twenty-first embodiment, the method according to the eighteenth embodiment further includes: triggering establishment of a UE context for the UE or modification of the UE context, wherein the UE context includes an indication that the UE is authorized to be a mobile base station relay.

[0105] In a twenty-second embodiment, the method according to the eighteenth embodiment, wherein the response to the message is a registration accept message, and the registration accept message includes an information element (IE) indicating a list of public land mobile networks (PLMNs) that support mobile base station relay operation.

[0106] In a twenty-third embodiment, one or more processors are configured to perform any of the methods described in accordance with the eighteenth to twenty-second embodiments.

[0107] In a twenty-fourth embodiment, an access and mobility function (AMF) of a core cellular network, wherein the access and mobility function (AMF) is configured to perform any of the methods described in the eighteenth to twenty-second embodiments.

[0108] Those skilled in the art will appreciate that the exemplary embodiments described above may be implemented with any suitable software configuration or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, etc. The exemplary embodiments of the above methods may be embodied as a program comprising lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, may be executed on a processor or microprocessor.

[0109] Although this patent application describes various combinations of various embodiments each having different features, those skilled in the art will understand that any feature of an embodiment may be combined with features of other embodiments in any manner not publicly denied or with features that are not functionally or logically inconsistent with the operation or function of the device of the embodiments disclosed in the present invention.

[0110] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0111] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is intended to cover modifications and variations of the present disclosure, provided that these modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. A processor of a user equipment (UE), the processor being configured to perform operations, the operations comprising: sending a registration request to a base station of a network, the registration request including an access node (AN) parameter, the access node (AN) parameter including an indication of whether the UE intends to operate as a mobile base station relay; and A response to the registration request is received from the network.

2. The processor of claim 1, wherein the indication is provided to a donor centralized unit (CU) of the base station when a radio resource control (RRC) connection is established by the UE.

3. The processor of claim 1, wherein the response is a registration accept message including an indication that mobile base station relay operation is not permitted.

4. The processor of claim 3, the operations further comprising: starting a back-off timer in response to the indication included in the registration accept message; as well as A second registration request is sent to the base station of the network, the second registration request including the indication of whether the UE intends to operate as a mobile base station relay.

5. The processor of claim 3, the operations further comprising: identifying a location-based condition after receiving the registration accept message; as well as and sending a second registration request to the base station of the network, the second registration request including the indication of whether the UE intends to operate as a mobile base station relay, wherein sending the second registration request is triggered based on identifying the location-based condition.

6. The processor of claim 1, the operations further comprising: Information associated with one or more public land mobile networks (PLMNs) is stored, the information including an indication for each of the one or more PLMNs indicating whether mobile base station relay operations are permitted or not permitted.

7. The processor of claim 1 , the operations further comprising: Radio parameters for mobile base relay operation are received, the radio parameters including operating frequencies and geographic regions in which mobile base relay operation is permitted.

8. The processor of claim 1, the operations further comprising: At least one of a radio parameter for a mobile base station relay operation, a tracking area (TA) or a registration area (RA) allowing the mobile base station relay operation is received.

9. The processor of claim 1, the operations further comprising: Quality of Service (QoS) map entries are received for services that the UE can support when operating as the mobile base station relay and serving other UEs.

10. The processor of claim 1, the operations comprising: A policy container is received, the policy container including information for one or more of: an authorization policy for operating as a mobile base station relay, an operation policy for a fifth generation (5G) core (5GC) connection, radio parameters for mobile base station relay operation, and quality of service (QoS) mapping entries for services that the UE can support when operating as the mobile base station relay and serving other UEs.

11. The processor of claim 1 , wherein the response to the registration request is a registration reject message, the registration reject message including one or more reject reasons indicating that the network does not support or allow mobile base station relay operations.

12. The processor of claim 1, wherein the response to the registration request is a deregistration request message indicating that the network does not support or allow mobile base station relay operations.

13. The processor of claim 1 , wherein the response to the registration request is a registration rejection message or a deregistration request, the operations further comprising: The F1 interface is released based on the response, wherein the UE remains connected to the network.

14. The processor of claim 1, the operations further comprising: An information element (IE) is received from a home public land mobile network (HPLMN), the IE including an indication that mobile base station relay operation is allowed in a roaming scenario.

15. The processor of claim 1, the operations further comprising: A Registration Accept message including an Information Element (IE) indicating a list of Public Land Mobile Networks (PLMNs) that support mobile base station relay operations.

16. An access and mobility management function (AMF), the access and mobility management function (AMF) being configured to perform operations, the operations comprising: receiving a message from a radio access network (RAN), the message including an indication of whether a user equipment (UE) intends to operate as a mobile base station relay; as well as A response to the message is sent to the RAN.

17. The AMF according to claim 16, wherein the message is an N2 Initial UE message.

18. The AMF of claim 16, wherein the operations further comprise: A Nudm_SDM_Get response is received from a unified data management (UDM) indicating whether the UE is permitted to operate as a mobile base station relay.

19. The AMF of claim 16, wherein the operations further comprise: triggering establishment of a UE context for the UE or modification of the UE context, the UE context including an indication that the UE is authorized to be a mobile base station relay.

20. The AMF of claim 16, wherein the response to the message is a Registration Accept message, the Registration Accept message including an Information Element (IE) indicating a list of Public Land Mobile Networks (PLMNs) that support mobile base station relay operations.

Images