Mobile base station equipment, terminal equipment, user equipment and communication method

Abstract

The invention discloses mobile base station equipment, terminal equipment, user equipment and a communication method. Wherein the mobile base station equipment comprises a first base station entity, the first base station entity is a base station part in the mobile base station equipment, and the first base station entity supports all or part of functions of a base station; the flow of the first base station entity comprises at least one of the flow borne on a core network interface, the flow borne on an interface between base stations and the flow borne between network managers, and the flow of the first base station entity is transmitted by at least one backhaul protocol data unit PDU session on the first terminal entity; the first base station entity sends a first request message to a core network. According to the application, the technical problem that the existing 3GPP Rel-18 protocol cannot meet the deployment requirement for low-cost mobile access equipment is solved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of wireless communication, in particular to a mobile base station device, a terminal device, a user equipment and a communication method. BACKGROUND

[0002] In order to support the demand of mobile coverage, the related art needs to upgrade the existing network base station, and there are problems such as not supporting roaming function, the core network does not have authentication capability for mobile base station, etc., that is, the current 3GPP (Third Generation Partnership Project) Rel-18 protocol cannot meet the deployment requirements of low-cost mobile access equipment, and new standardization methods are needed to enhance the function to meet the network deployment and optimization requirements.

[0003] At present, there is no effective solution to the above problems. SUMMARY

[0004] The embodiments of the present application provide a mobile base station device, a terminal device, a user equipment and a communication method to at least solve the technical problem that the current 3GPP Rel-18 protocol cannot meet the deployment requirements of low-cost mobile access equipment.

[0005] According to an aspect of the embodiments of the present application, a mobile base station device is provided, and the mobile base station device comprises a first base station entity, wherein the first base station entity is a base station part in the mobile base station device, and the first base station entity supports all or part of the functions of the base station; the traffic of the first base station entity comprises at least one of the traffic carried on the interface with the core network, the traffic carried on the interface between base stations, and the traffic carried with the network management; the traffic of the first base station entity is transmitted by a backhaul protocol data unit (PDU) session on a first terminal entity; and the first base station entity sends a first request message to the core network, wherein the first request message comprises at least one of the base station identifier of the first base station entity, the public land mobile network (PLMN) of the cell in the first base station entity, the tracking area code (TAC), and the first indication information.

[0006] According to another aspect of the embodiments of the present application, a terminal device is further provided, and the terminal device comprises a first terminal entity in a mobile base station device, wherein the first terminal entity is a terminal part in the mobile base station device; the first terminal entity is connected to the network through a radio resource control (RRC) connection establishment process with a backhaul base station; and the first terminal entity establishes at least one backhaul protocol data unit (PDU) session bearer with the network.

[0007] According to a further aspect of the embodiments of the present application, a user equipment is also provided, wherein the user equipment in the RRC connected state is handed over from the first base station entity to the second base station entity or other wireless node, or the user equipment in the RRC idle or RRC inactive state is reselected to the second base station entity or other wireless node.

[0008] According to a further aspect of the embodiments of the present application, a communication method is also provided, applied to a first base station entity, wherein the first base station entity is a base station part in a mobile base station device, and the first base station entity supports all or part of base station functions; the method comprises: sending, by the first base station entity, a first request message to a core network, wherein the first request message comprises at least one of a base station identifier of the first base station entity, a public land mobile network (PLMN) of a cell in the first base station entity, a tracking area code (TAC), and first indication information; wherein the traffic of the first base station entity comprises at least one of traffic carried on an interface with the core network, traffic carried on an inter-base station interface, and traffic carried with a network management, and the traffic of the first base station entity is transmitted by at least one backhaul protocol data unit (PDU) session on the first terminal entity.

[0009] According to a further aspect of the embodiments of the present application, another communication method is also provided, applied to a first terminal entity, wherein the first terminal entity is a terminal part in a mobile base station device; the method comprises: connecting, by the first terminal entity, to a network through a radio resource control (RRC) connection establishment process with a backhaul base station, wherein the first terminal entity establishes at least one backhaul protocol data unit (PDU) session with the network.

[0010] In the embodiments of the present application, by adopting the above manner, the requirement of supporting low-cost mobile coverage is achieved without the need to upgrade the existing network base station, and the roaming function and service function of the mobile base station are supported, and the terminal is transparent, thereby solving the technical problem that the current 3GPP Rel-18 protocol cannot meet the deployment requirement of low-cost mobile access equipment. BRIEF DESCRIPTION OF DRAWINGS

[0011] The accompanying drawings, which are included to provide a further understanding of the present application, form a part of the present application and illustrate the illustrative embodiments of the present application and the explanation of the present application, and do not constitute improper limitations on the present application. In the drawings:

[0012] Figure 1 is a schematic diagram of an IAB network architecture provided according to the embodiments of the present application;

[0013] Figure 2 is a schematic diagram of an NCR architecture provided according to the embodiments of the present application;

[0014] Figure 3 is a schematic diagram of a mobile access device according to an embodiment of the present application;

[0015] Figure 4 is a schematic diagram of a mobile access device architecture taking MWAB as an example according to an embodiment of the present application;

[0016] Figure 5 is a hardware structure block diagram of a computer terminal (or electronic device) for implementing a communication method according to an embodiment of the present application. DETAILED DESCRIPTION

[0017] In order to enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor should be within the scope of protection of the present application.

[0018] It should be noted that the terms "first", "second", and the like in the specification and claims of the present application and the above-described drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or a chronological sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but can include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0019] In the related art, a plurality of extended support access devices are added in the 3GPP 5G system, which are IAB (Integrated Access and Backhaul) introduced in R16 and NCR (Network-Controlled Repeaters) devices in R18. The characteristics of IAB are as follows: IAB is introduced in 3GPP 5G Release 16, which enables the base station to provide wireless access and wireless backhaul connection for devices, thereby eliminating the need to install higher-cost wired backhaul. IAB refers to using a part of the access spectrum as backhaul.

[0020] 5G promises high bandwidth capabilities from the millimeter-wave band, but a challenge lies in the limited coverage of high-frequency deployments and the need for denser base station layouts, significantly increasing deployment costs. A major factor contributing to this cost is the need for underground fiber optic deployment. The IAB (Integrated Base Station) architecture, which dedicates a portion of its radio spectrum to backhaul connections for base stations instead of fiber, has emerged as an attractive solution for cost-effective dense deployment. A key advantage of the IAB is its flexibility and ability to deploy new radio (NR) cells very densely without proportionally increasing the density of the transmission network. The IAB-node protocol architecture uses a Layer 2 architecture, separating the CU (Central Unit) and DU (Distributed Unit) components, as follows... Figure 1 As shown, the clock synchronization uses OTA (over-the-air) clock synchronization.

[0021] The technical characteristics of NCR are as follows:

[0022] 1) The NCR structure is a repeater controlled by the wireless network gNB (gNodeB, i.e., 5G base station). The NCR consists of two main functional blocks, such as... Figure 2 As shown, they are NCR-MT (Mobile Terminal) and NCR-Fwd (Forwarding). The NCR-MT module uses the 5G (NR (New Radio)) network Uu interface to establish communication with the gNB through the C-link control link, and can complete the exchange of control information (such as beamforming, UL / DL (Uplink / Downlink) switching and on / off conversion, and NCR-Fwd module management). The NCR-MT module provides control and status signaling exchange with the gNB through C-link, and fulfills its responsibilities by supporting a subset of UE (User Equipment) functions.

[0023] 2) C-link characteristics: In NCR, the characteristics of C-link and IAB in transmission and reception are as follows: C-link's DL and IAB link DL can be executed simultaneously or in TDM (Time Division Multiplexing) mode; C-link's UL and IAB link UL can be performed in TDM mode; gNB controls multiplexing simultaneously when considering NCR capability, and the simultaneous transmission of UL in C-link and IAB depends on the NCR capability.

[0024] 3) NCR-Fwd Features: In the NCR module, this module amplifies and forwards the UL / DL RF (Radio Frequency Signal) between the gNB and UE via the IAB and access link. The NCR-Fwd module is implemented using two sets of planar antennas: one set for the IAB link and the other for the access link, along with an RF amplifier. The NCR-Fwd module primarily focuses on signal amplification and (analog) beamforming, eliminating the need for advanced digital receivers or transmitter chains. The performance requirements for the beamforming antenna are not as high as those for macro base stations or IAB node antennas; cost-effectiveness and ease of manufacturing are key priorities.

[0025] 4) Both NCR-MT and NCR-Fwd can operate in the same or different frequency bands. NCR-MT requires at least one carrier to operate within the frequency band relayed by NCR-Fwd, using that band as a baseline. When NCR-MT and NCR-Fwd operate in the same frequency band, C-link and IAB will encounter similar large-scale channel characteristics, thus simplifying IAB control between gNB and NCR-Fwd.

[0026] Both of the above solutions have some problems. For example, IAB needs to support a CU / DU separation architecture, and the macro base stations it serves need to support some core network functions, resulting in high upgrade costs for the existing network and high implementation costs for IAB. NCR only supports fixed deployment, and from the UE's perspective, NCR is a transparent repeater, lacking L2 / L3 processing capabilities. Specifically, existing solutions in related technologies currently have the following problems:

[0027] 1) Upgrading existing base stations is required: Both IAB and NCR require upgrading existing base stations to support NCR and IAB access functions, which will lead to a large number of existing base stations being upgraded, resulting in relatively high costs;

[0028] 2) Roaming function not supported: IAB and NCR can only access the network of their home operator. In some mobile scenarios, the base station may move to the network coverage of other operators. Therefore, a function that supports roaming scenarios is required.

[0029] 3) The core network lacks authentication capabilities for mobile base stations: The current protocol does not have authentication capabilities for mobile base stations. Therefore, mobile base stations do not know whether they are legitimate base stations. Once authentication fails, the core network is unclear about its interoperability with mobile devices and the core network.

[0030] Based on the above analysis of needs and reasons, the current 3GPP Rel-18 protocols cannot meet the deployment requirements for low-cost mobile access devices. Therefore, in order to support mobile scenarios without upgrading existing 5G base stations, a new coverage extension scheme is needed, which requires enhanced functionality through new standardization methods to meet the needs of network deployment and optimization.

[0031] To address the aforementioned issues, this application provides relevant solutions, which are detailed below.

[0032] According to an embodiment of this application, an embodiment of a mobile access device is provided. Figure 3 This is a schematic diagram of a mobile access device according to an embodiment of this application, such as... Figure 3 As shown, the device includes: a first terminal entity (i.e., terminal equipment) and at least one base station entity, wherein the base station entity includes at least: the first base station entity.

[0033] The first base station entity is the base station portion of the mobile base station equipment, supporting all or part of the base station functions; the traffic of the first base station entity includes at least one of the following: traffic carried on the core network interface (such as NG TRAFFIC), traffic carried on the inter-base station interface (such as Xn TRAFFIC), and traffic carried on the network management interface (such as OAM TRAFFIC), and is transmitted by at least one backhaul PDU session on the first terminal entity.

[0034] The first terminal entity is the terminal part in the mobile base station equipment. It connects to the network through the RRC connection establishment process with the backhaul base station (gNB). The first terminal entity supports at least one RRC (Radio Resource Control) state among the RRC connected state, RRC idle state, and RRC inactive state. The first terminal entity establishes at least one PDU session bearer with the network.

[0035] Specifically, when the first terminal entity is in an idle or inactive state, the first base station entity stops or suspends providing services to the second terminal, or the first backhaul base station entity suspends or releases the interface connection with the core network; when the first terminal entity is in a connected state, the first terminal entity and the first core network entity establish at least one session bearer.

[0036] When the first base station entity establishes an interface with the core network to interact, it sends a first indication information to the core network and / or receives a second indication information from the core network. The first indication information is used to indicate that the first base station entity is a mobile base station device, and the second indication information is used to indicate that the first base station entity is a mobile base station device, or that the authentication of the first base station entity as a mobile base station device is successful or unsuccessful.

[0037] The first base station entity is also used to send a first request message or a second request message to the core network. The first request message includes at least one of the following: the base station identifier of the first base station entity, the PLMN of the cell in the first base station entity, the tracking area code (TAC), and the first indication information. The second request message is used to release the interface with the core network.

[0038] The aforementioned mobile base station equipment can be installed on a moving object and can provide services to user equipment inside or outside the moving object.

[0039] This application proposes a mobile base station device that achieves the goal of supporting low-cost mobile coverage without upgrading existing base stations. It also supports roaming and service functions of the mobile base station and is transparent to the terminal, thereby solving the technical problem that the current 3GPP Rel-18 protocol cannot meet the deployment requirements for low-cost mobile access devices.

[0040] The mobile access device in the embodiments of this application will be further described below.

[0041] In this embodiment, the first terminal entity supports some or all user equipment (UE) functions, including at least one of 5G or 6G functions; the first terminal entity supports communication with the first backhaul base station and can access the network through the RRC connection establishment process; specifically, the first terminal entity performs authorization and / or authentication with the first core network, and after being authorized or authenticated, the first terminal entity establishes at least one session with the network to carry the user backhaul.

[0042] The aforementioned first base station entity provides wireless access for user equipment and supports some or all of the base station functions of 5G or subsequent evolution technologies, wherein the wireless access technology includes at least one of 5G or 6G technologies.

[0043] The first terminal entity and the first base station entity may adopt or connect to the same or different core networks or PLMNs (Public Land Mobile Networks). The core network includes at least one of 5G or 6G core network control plane entities and / or user plane entities.

[0044] In some embodiments of this application, the first terminal entity sends user capability indication information to the first core network entity, wherein the user capability indication information includes at least one of the following: mobile base station equipment indication information, multi-cell indication, or multi-base station indication; the mobile base station equipment indication information is used to indicate that the first terminal entity supports mobile base station equipment, and the multi-cell indication or multi-base station indication is used to indicate that the mobile base station equipment supports at least two cells or base stations during the handover process.

[0045] After receiving the user capability indication information, the first core network entity sends the user capability of the first terminal entity to the first backhaul base station. That is, the user capability indication information is sent by the first core network entity to the first backhaul base station, where the first backhaul base station is the backhaul base station of the first terminal entity and is used to have an RRC connection with the first terminal entity.

[0046] In some embodiments of this application, the first terminal entity sends a NAS (Non-Access-stratum) message to the first core network entity to notify the first core network entity to establish at least one session bearer. The NAS message includes: QoS (Quality of Service) requirements or suggestions used by one or more session bearers. The session bearer is used to carry signaling for the interface between the base station and the core network, the interface between base stations, or the interface of the operation and maintenance management center.

[0047] In this embodiment of the application, the operation and maintenance management center can be implemented using Operations and Maintenance Center (OMC) and / or Operation Administration and Maintenance (OAM).

[0048] At least one PDU (Protocol Data Unit) session is established between the first core network entity and the first backhaul base station. The at least one PDU session is used to carry signaling between the first base station entity and the first core network entity or the second core network entity for the interface between the base station and the core network, the interface between base stations, or the interface of the operation and maintenance management center. The first core network entity or the second core network entity is used to establish signaling and data between the first base station entity and the first core network entity or the second core network entity. The core network entity to which the first base station entity is connected is determined according to the network management configuration or according to the location information of the first base station entity or the first terminal entity.

[0049] In some embodiments of this application, the first backhaul base station configures multiple DRBs (Data Radio Bearers) for the first terminal entity via RRC messages. The bearers of signaling for the interface between the base station and the core network, the interface between base station values, or the interface of the operation and maintenance management center are mapped to at least one of the DRBs.

[0050] The first terminal entity notifies the first base station entity to establish a connection with the operation and maintenance management center through the internal interface in the mobile base station equipment. Based on at least one of the following information: the location of the first terminal entity, the base station identifier or cell identifier of the first backhaul base station, the PLNM adopted by the first core network entity, and the pre-configuration information, the Internet Protocol address (IP address) and port address of the operation and maintenance management center are determined.

[0051] Subsequently, the first base station entity establishes an IP connection with the OAM using the Internet Protocol address and port address or pre-configured information notified by the first terminal entity to the operation and maintenance management center;

[0052] Specifically, the first base station entity establishes a connection with the operation and maintenance management center using the Internet Protocol address and port address notified by the first terminal entity, and obtains relevant information on cell establishment and configuration from the OAM of the operation and maintenance management center. The relevant information includes: the cell's broadcast message MIB (Master Information Block) / SIB (System Information Block) message configuration, the cell's private parameter configuration, the Internet Protocol address and port address belonging to the second core network entity, and the PLMN list of the second core network entity. The connection between the first base station entity and the operation and maintenance management center is transmitted through the PDU session bearer on the first terminal entity.

[0053] The first base station entity can establish an SCTP (Stream Control Transmission Protocol) connection with the network entity based on its own Internet Protocol address (or Internet Protocol address and port address) and the Internet Protocol address (or Internet Protocol address and port address) of the network entity. The Internet Protocol address of the first base station entity can be the Internet Protocol address of the first terminal entity or the Internet Protocol address configured by OAM. The network entity includes the second core network entity or the backhaul base station. The SCTP connection is established on the bearer established between the first terminal entity and the first core network entity.

[0054] In some embodiments of this application, a first base station entity initiates a first request message to a second core network entity. The first request message includes at least one of the following: first indication information, base station identifier of the first base station entity, PLMN of the cell in the first base station entity, and TAC (Tracking Area Code). The first indication information indicates to the core network that the device is a mobile base station device or location information. The PLMN and TAC of the cell in the first base station entity are determined by the configuration of the cell's broadcast message master information block (MIB) / system information block (SIB) message.

[0055] The aforementioned first request message can be an NG SETUP REQUEST or NG RANCONFIGURATION UPDATE message in a 5G system, or an interface establishment request or interface update request message between a base station and the core network in a 6G system.

[0056] The aforementioned location information can be used to indicate the radio node served by the core network user equipment, including at least one of cell identifier, TAI information, and geographic location information.

[0057] After receiving the first request message (such as an interface establishment request or an interface update request message), the second core network can determine whether the first base station entity is a mobile base station device based on the first indication information or the account opening information queried from the unified data management function UDM. Then, it returns the corresponding interface establishment response or interface update response message to the first base station entity.

[0058] If the interface establishment request or interface update request message contains the first indication information, the interface establishment response or interface update response message contains the second indication information or does not carry other indication information; if the interface establishment request or interface update request message does not contain the first indication information, the interface establishment response or interface update response message contains the first indication information or the second indication information, wherein the second indication information indicates that the device is a mobile base station device or that the device has passed or failed the mobile base station device authentication.

[0059] Upon receiving an interface establishment response or interface update response message, the first base station entity determines, based on the second instruction information or the interface establishment response or interface update response message itself, that the first base station entity's information has been successfully authenticated for the mobile base station equipment in the second core network.

[0060] In some embodiments of this application, when the first backhaul base station instructs the first terminal entity to return from the connected state to the idle state or the inactive state through an RRC reconfiguration message or an RRC release message, the first terminal entity notifies the first base station entity of status information, wherein the status information includes at least one of the following: connected state, idle state, and inactive state.

[0061] According to the instruction information of the first terminal entity, the first base station entity deletes the SCTP connection with the second core network entity and stops sending broadcast messages or shuts down the cell. The instruction information is triggered after the first terminal entity changes from a connected state to an idle state or an inactive state, or switches to another backhaul base station or cell.

[0062] Specifically, when the status information received by the first base station entity from the first terminal entity is in an idle or inactive state, the first base station entity deletes the SCTP connection with the second core network entity and stops sending broadcast messages or shuts down the cell.

[0063] During the movement of the first terminal entity or mobile base station equipment, the first terminal entity can re-establish or update the backhaul PDU session.

[0064] When the status information received by the first base station entity from the first terminal entity changes from idle or inactive to connected, the first base station entity attempts to establish a connection with the second core network entity and simultaneously starts cell broadcast messages.

[0065] In some embodiments of this application, the first terminal entity may also notify the first base station entity to configure the second base station entity or the second cell of the first base station when or before triggering a handover across UPF (User Plane Function) or AMF (Access and Mobility Management Function), wherein the second base station entity is a base station in a new logical mobile base station device.

[0066] During the movement of the first base station entity or mobile base station equipment, the first base station entity will switch or reselect user equipment camped under the first cell of the first base station to the second base station entity or the second cell of the first base station entity; the second base station entity or the second cell of the first base station entity is a new logical base station or cell in the mobile base station equipment.

[0067] The second base station entity or a new logical base station is connected to the second core network or the third core network; the second core network and the third core network may be the same or different.

[0068] It should be noted that during the relocation of the mobile base station equipment, when the PDU session between the first terminal equipment and the first backhaul base station is re-established, the first base station entity located at the same location may need to update the IP address used for its traffic.

[0069] The second base station entity may initiate an interface establishment request message to the second core network entity. This interface establishment request message includes: first indication information, the base station identifier of the second base station entity, and at least one of the PLMN and TAC of the cell in the second base station entity. The PLMN and TAC of the cell in the second base station entity are determined by the cell's broadcast message MIB / SIB configuration. Alternatively, the second base station entity may initiate an interface update request message to the second core network entity. This interface update request message includes: first indication information, the base station identifier of the first base station entity, the second cell identifier of the first base station, and at least one of the PLMN and TAC of the second cell in the first base station entity. The PLMN and TAC of the cell in the first base station entity are determined by the cell's broadcast message MIB / SIB configuration.

[0070] The first base station entity will switch users camped on the first cell of the first base station to the second base station or the second cell of the first base station. After completing the cross-UPF or AMF handover, the first base station entity or the first cell of the first base station is deleted, related broadcast messages and data transmission services are stopped, and the connection or cell configuration between the first base station entity and the second core network is deleted. That is, after the user equipment handover is completed, the first base station entity sends a second request message to the second core network to release the interface between the first base station entity and the core network, and the first base station entity stops providing services to the user equipment.

[0071] Specifically, a user equipment in an RRC connected state is switched from the first base station entity to the second base station entity or other wireless nodes, or a user equipment in an RRC idle or RRC inactive state is reselected to the second base station entity or other wireless nodes; after the switch or reselection, the user equipment connects to the third core network.

[0072] The aforementioned user equipment is connected to the first base station entity or mobile base station equipment. The wireless access standard of the user equipment includes 5G or 6G wireless access. The user equipment is connected to the second core network through the first base station entity. The second core network and the third core network may be the same or different.

[0073] When a user equipment in an RRC connection state receives an RRC reconfiguration request message or a handover command from a first base station entity, the reconfiguration request message or handover command includes at least one of the following: PCI, cell identifier, frequency point, and wireless standard of the second base station entity or other wireless node; after receiving the RRC reconfiguration request message or handover command, the user equipment connects to the second base station entity or other wireless node and then connects to the third core network.

[0074] User equipment in RRC idle state or RRC inactive state reselects to the second base station entity or other radio node, performs a mobile registration update process based on the TAC information of the second base station entity or other radio node, and connects to the third core network after the reselection is completed.

[0075] The above solution will be further explained below with specific examples.

[0076] Case 1

[0077] This embodiment mainly describes the architecture of a mobile access device and its connected core network equipment and backhaul equipment, such as... Figure 4 As shown, the mobile access device MWAB (Multi-Wireless Access Backhaul) includes: WAB-gNB (i.e., the first base station entity mentioned above) and WAB-MT (i.e., the first terminal entity mentioned above). WAB-MT is connected to the core network CN1 (i.e., the first core network mentioned above) and PLMN is 1, while WAB-gNB is connected to the core network CN2 (i.e., the second core network mentioned above) and PLMN is 2. BACKHUAL gNB is a base station (i.e., the first backhaul base station mentioned above) used to connect to the mobile access device.

[0078] This case study describes the connection process between WAB-gNB and the core network, as follows:

[0079] 1) MWAB includes two entities: MWAB-MT and MWAB-gNB. MWAB-MT (the first terminal entity) supports all UE functions and communication with BH gNB (the first backhaul base station). MWAB-gNB (the first base station entity) supports 5G functions.

[0080] 2) The MWAB-MT (first terminal entity) sends user capability indication information to AMF1 / SMF1 (first core network entity). The user capability indication information includes at least: MWAB indication information (i.e., mobile base station equipment indication information) and multiple bearer indications. MWAB is used to indicate that the terminal supports MWAB. Multiple bearer indications indicate that during the handover process, the MWAB-MT can configure at least two bearers to carry different NG interfaces respectively.

[0081] 3) AMF1 / SMF1 (first core network entity) sends the user capabilities of MWAB-MT (first terminal entity) to BHgNB (first backhaul base station); BHgNB is the backhaul base station of MWAB-MT, and BHgNB establishes an RRC connection with MWAB-MT;

[0082] 4) MWAB-MT (first terminal entity) sends a NAS message to AMF1 / SMF1 (first core network entity) to notify AMF1 / SMF1 (first core network entity) to establish at least one session bearer. The NAS message includes: the QoS requirements or suggestions used by one or more session bearers. The session bearer is used to carry signaling between the base station and the core network, between base station values, or between the operation and maintenance management center.

[0083] 5) Two PDU sessions are established between AMF1 / SMF1 (first core network entity) and BH gNB (first backhaul base station). PDU session #1 is used for signaling of the NG interface between MWAB-gNB (first base station entity) and AMF2 / SMF2 (second core network entity). AMF2 / SMF2 (second core network entity) is used to establish signaling and data between MWAB-gNB (first base station entity) and AMF2 / SMF2 (second core network entity).

[0084] 6) The BH gNB (first backhaul base station) configures two DRBs for the MWAB-MT (first terminal entity) via RRC messages and maps the bearer used to carry NG interface signaling to one of the DRBs;

[0085] Case 2

[0086] This case study describes the connection process between WAB-gNB (the first base station entity) and the core network. The specific process is as follows:

[0087] 1) The MWAB-MT (first terminal entity) notifies the first base station to establish a connection with the operation and maintenance management center, and can determine the IP address and port address of the operation and maintenance management center based on the location of the first terminal entity, the base station identifier or cell identifier of the BACKHUAL gNB (first backhaul base station), and the PLMN information used by AMF1 / SMF1 (first core network entity).

[0088] 2) The MWAB-gNB (first base station entity) establishes a connection with the operation and maintenance management center using the IP address and port address notified by the MWAB-MT (first terminal entity), and obtains cell establishment and configuration related information from the operation and maintenance management center. The configuration related information includes the cell's broadcast message MIB / SIB message configuration, the cell's private parameter configuration, the IP address and port address of the home AMF2 / SMF2, and the PLMN list of AMF2 / SMF2.

[0089] 3) The MWAB-gNB (first base station entity) establishes an SCTP connection with AMF2 / SMF2 (second core network entity) based on its own IP address and port address, as well as the IP address and port address of its home AMF2 / SMF2 (second core network entity). The SCTP connection uses the bearer established between MWAB-MT (first terminal entity) and AMF1 / SMF1 (first core network entity).

[0090] 4) The MWAB-gNB (first base station entity) initiates an interface establishment request or interface update request message to AMF2 / SMF2 (second core network entity). The interface establishment request or interface update message includes first indication information, which indicates that the device is a MWAB.

[0091] 5) After receiving an interface establishment request or interface update request message, AMF2 / SMF2 (second core network entity) determines whether MWAB-gNB is a MWAB based on the first indication information or the account opening information queried from UDM. The second indication information is included in the interface establishment response message or interface update response message. The second indication information indicates that the device is a MWAB or that the device has passed MWAB authentication.

[0092] Case 3

[0093] This embodiment mainly describes the core network interface processing procedure when transitioning from the connected state to the idle state. The specific process is as follows:

[0094] 1) If the BACKHUAL gNB (first backhaul base station) instructs the MWAB-MT (first terminal entity) to return from the connected state to the idle state or the inactive state through the RRC release message, then the MWAB-MT (first terminal entity) will notify the MWAB-gNB (first base station entity) of the status information, wherein the status information is the idle state;

[0095] 2) When the status information received by MWAB-gNB (the first base station entity) is in an idle state, MWAB-gNB (the first base station entity) deletes the SCTP connection with AMF2 / SMF2 (the second core network entity), and the first base station stops sending broadcast messages or shuts down the cell.

[0096] 3) When MWAB-MT (first terminal entity) changes from idle state to connected state, MWAB-gNB (first base station entity) attempts to establish a connection with AMF2 / SMF2 (second core network entity) and starts cell broadcast messages.

[0097] This application proposes a mobile access solution that supports backhaul to the target core network in roaming scenarios. Compared to traditional NCR and IAB solutions, this solution does not require upgrading existing macro base stations and supports establishing the NG interface between the base station and the core network through the roaming network, connecting the home core network and the mobile base station, thus supporting flexible architecture configuration. This application clearly defines the state and interface configuration of the base station entity in different states of the terminal entity within the mobile base station, thereby ensuring the interoperability process between the base station, terminal, and core network and avoiding interoperability failures caused by different implementations. This application does not involve any impact on the terminal, as it is a network-side solution with good forward compatibility and is easy to deploy and implement.

[0098] According to an embodiment of this application, a communication method embodiment is also provided, applied to a first base station entity in a mobile base station device, wherein the mobile base station device includes: a first terminal entity and at least one base station entity, the base station entity including at least: a first base station entity, the first base station entity being a base station portion in the mobile base station device, the first base station entity supporting all or part of the functions of a base station; the method includes the following steps:

[0099] The first base station entity sends a first request message or a second request message to the core network. The first request message includes at least one of the following: the base station identifier of the first base station entity, the public land mobile network (PLMN) of the cell in the first base station entity, the tracking area code (TAC), and first indication information. The second request message is used to release the interface between the first base station entity and the core network.

[0100] The traffic of the first base station entity includes at least one of the following: traffic carried on the core network interface, traffic carried on the inter-base station interface, and traffic carried on the network management interface. The traffic of the first base station entity is transmitted by at least one backhaul protocol data unit (PDU) session on the first terminal entity.

[0101] And, the first base station entity sends a first indication information to the core network and / or receives a second indication information from the core network, wherein the first indication information is used to indicate that the first base station entity is a mobile base station device, and the second indication information is used to indicate that the first base station entity is a mobile base station device, or that the authentication of the first base station entity as a mobile base station device is successful or unsuccessful.

[0102] Specifically, the first terminal entity supports at least one Radio Resource Control (RRC) state in the connected state, idle state, and inactive state, and the first terminal entity establishes at least one session bearer with the core network.

[0103] It should be noted that the communication method provided in this embodiment is a communication method with... Figure 3The method embodiment corresponding to the mobile base station equipment shown is illustrated here. Therefore, the relevant explanations and descriptions of the mobile base station equipment described above also apply to the embodiments of this application, and will not be repeated here.

[0104] According to an embodiment of this application, another communication method embodiment is also provided, applied to a first terminal entity in a mobile base station device, wherein the mobile base station device includes: a first terminal entity and at least one base station entity, the base station entity at least includes: a first base station entity, and the first terminal entity is a terminal portion in the mobile base station device; the method includes the following steps:

[0105] The first terminal entity connects to the network through a Radio Resource Control (RRC) connection establishment process with the backhaul base station, wherein the first terminal entity establishes at least one PDU session bearer with the network.

[0106] In addition, the first terminal entity notifies the first base station entity of the status information of the first terminal entity, wherein the status information includes at least one of the following: connected status, idle status, and inactive status;

[0107] The first terminal entity supports at least one Radio Resource Control (RRC) state among connected state, idle state, and inactive state. When the first terminal entity is in idle state or inactive state, the first base station entity stops or suspends providing services to the second terminal, or the first backhaul base station entity suspends or releases the NG interface connection.

[0108] It should be noted that the communication method provided in this embodiment is a communication method with... Figure 3 The method embodiment corresponding to the mobile base station equipment shown is illustrated here. Therefore, the relevant explanations and descriptions of the mobile base station equipment described above also apply to the embodiments of this application, and will not be repeated here.

[0109] It should be noted that the steps shown in the embodiments of this application can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the embodiments, in some cases the steps shown or described may be performed in a different order than that shown here.

[0110] The method embodiments provided in this application can be executed on a mobile terminal, computer terminal, or similar computing device. Figure 5 A hardware structure block diagram of a computer terminal (or electronic device) for implementing a communication method is shown. Figure 5As shown, the computer terminal 50 (or electronic device) may include one or more processors 502 (shown as 502a, 502b, ..., 502n in the figure) 502 (processor 502 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 504 for storing data, and a transmission device 506 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 5 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 50 may also include... Figure 5 The more or fewer components shown, or having the same Figure 5 The different configurations shown.

[0111] It should be noted that the aforementioned one or more processors 502 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be wholly or partially integrated into any other element within the computer terminal 50 (or electronic device). As involved in the embodiments of this application, the data processing circuits serve as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0112] The memory 504 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the communication method in the embodiments of this application. The processor 502 executes various functional applications and data processing by running the software programs and modules stored in the memory 504, thereby realizing the above-mentioned communication method. The memory 504 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 504 may further include memory remotely located relative to the processor 502, and these remote memories can be connected to the computer terminal 50 via a network. Examples of the above-mentioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0113] The transmission device 506 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the computer terminal 50. In one example, the transmission device 506 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 506 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0114] The display can be, for example, a touchscreen liquid crystal display (LCD) that allows a user to interact with the user interface of the computer terminal 50 (or electronic device).

[0115] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0116] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0117] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0118] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0119] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0120] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0121] The above are merely preferred embodiments of this application. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A mobile base station apparatus, characterized by comprising: The mobile base station device comprises a first base station entity, The first base station entity is a base station part of the mobile base station device, and the first base station entity supports all or part of the functions of a base station; The traffic of the first base station entity comprises at least one of traffic carried on a core network interface, traffic carried on an inter-base station interface, and traffic carried between an operation and maintenance management center, and the traffic of the first base station entity is transmitted by at least one backhaul protocol data unit (PDU) session on the first terminal entity. The first base station entity sends a first request message to the core network, wherein the first request message comprises at least one of a base station identifier of the first base station entity, a public land mobile network (PLMN) of a cell in the first base station entity, a tracking area code (TAC), and first indication information.

2. The mobile base station device of claim 1, wherein The mobile base station device comprises a first terminal entity and at least one base station entity, wherein the base station entity comprises at least the first base station entity. The mobile base station device is installed on a moving object and is configured to provide services for user equipment inside or outside the moving object.

3. The mobile base station device of claim 2, wherein The first terminal entity and the first base station entity are connected to the same or different core network or PLMN, and the core network comprises at least one of a 5G or 6G core network control plane entity and / or a user plane entity.

4. The mobile base station device of claim 1, wherein The first base station entity establishes an IP connection with an operation and maintenance management center using the IP address and port address of the operation and maintenance management center or preconfigured information notified by the first terminal entity.

5. The mobile base station device of claim 4, wherein The first base station entity obtains cell establishment and configuration related information from the operation and maintenance management center, wherein the related information comprises cell broadcast message master information block (MIB) / system information block (SIB) message configuration, private parameter configuration of the cell, IP address and port address of a home second core network entity, and a PLMN list of the second core network entity, and the connection between the first base station entity and the operation and maintenance management center is transmitted through a PDU session on the first terminal entity.

6. The mobile base station device of claim 1, wherein The first base station entity establishes a stream control transmission protocol (SCTP) connection with a network entity according to its own IP address and the IP address of the network entity, wherein the network entity comprises a second core network entity or a backhaul base station.

7. The mobile base station device of claim 1, wherein The first base station entity sends the first request message to the second core network entity, wherein the first request message comprises at least one of the first indication information, a base station identifier of the first base station entity, a PLMN of a cell in the first base station entity, and a tracking area code (TAC), and the first indication information is used to indicate a mobile base station to the core network.

8. The mobile base station device according to claim 7, wherein the first request message comprises an NG SETUP REQUEST or an NG RAN CONFIGURATION UPDATE message in a 5G system, or an interface setup request or an interface update request message between a base station and a core network in a 6G system.

9. The mobile base station device according to claim 1, wherein the first base station entity deletes an SCTP connection with the second core network entity and stops transmitting a broadcast message or closes a cell according to indication information of the first terminal entity, the indication information being triggered when the first terminal entity transitions from a connected state to an idle state or an inactive state, or switches to another backhaul base station or cell.

10. The mobile base station device according to claim 9, wherein the first base station entity attempts to establish a connection with the second core network entity and starts a cell broadcast message when state information of the first terminal entity transitions from the idle state or the inactive state to a connected state.

11. The mobile base station device according to claim 1, wherein the first base station entity switches or reselects a user equipment residing in a first cell of the first base station entity to a second base station entity or a second cell of the first base station entity during movement of the first base station entity or the mobile base station device, the second base station entity or the second cell of the first base station entity being a new logical base station or cell in the mobile base station device.

12. The terminal device according to claim 1, wherein the terminal device comprises a first terminal entity in the mobile base station device, the first terminal entity being a terminal part in the mobile base station device, the first terminal entity connecting to a network through a radio resource control (RRC) connection setup procedure with a backhaul base station, the first terminal entity establishing at least one backhaul protocol data unit (PDU) session bearer with the network, the first terminal entity supporting at least one of 5G or 6G functions.

14. The terminal device according to claim 12, wherein the first terminal entity supports at least one of an RRC connected state, an RRC idle state, and an RRC inactive state.

15. The terminal device according to claim 14, wherein the first terminal entity and a first core network entity establish at least one session bearer when the first terminal entity is in a connected state, traffic of the first base station entity being transmitted by at least one backhaul PDU session on the first terminal entity, the traffic of the first base station entity including at least one of traffic carried on a core network interface, traffic carried on an inter-base station interface, and traffic carried with an operation and maintenance management center.

16. The terminal device according to claim 12, wherein ​ 12. A terminal device, comprising: ​ ​ ​ ​ 13. The terminal device according to claim 12, characterized by ​ ​ ​ ​ ​ ​ ​ The first terminal entity sends user capability indication information to a first core network entity, wherein the user capability indication information comprises at least one of the following: mobile base station device indication information, multi-cell indication, or multi-base station indication, the mobile base station device indication information is used to indicate that the first terminal entity supports a mobile base station device, and the multi-cell indication or multi-base station indication is used to represent that the mobile base station device supports at least two cells or base stations in a handover process.

17. The terminal device of claim 16, wherein, The first terminal entity receives an RRC message sent by the first backhaul base station, wherein the RRC message is used to configure a plurality of DRBs for the first terminal entity, and map a bearer carrying signaling of an interface between a base station and a core network, an interface between base stations, an interface between base stations and a core network, or an interface between an operation and maintenance management center to at least one of the DRBs.

18. The terminal device of claim 12, wherein The first terminal entity sends a non-access stratum (NAS) message to the first core network entity to inform the first core network entity to establish at least one session bearer, wherein the NAS message comprises quality of service (QoS) requirements or suggestions of one or more session bearers, and the session bearers are used to carry signaling of an interface between a base station and a core network, an interface between base stations, an interface between base stations and a core network, or an interface between an operation and maintenance management center.

19. The terminal device of claim 12, wherein The first terminal entity receives an RRC message sent by the first backhaul base station, wherein the RRC message is used to configure a plurality of DRBs for the first terminal entity, and map a bearer carrying signaling of an interface between a base station and a core network, an interface between base stations, an interface between base stations and a core network, or an interface between an operation and maintenance management center to at least one of the DRBs.

20. The terminal device of claim 12, wherein The first terminal entity informs the first base station entity to establish a connection with an operation and maintenance management center through an internal interface in the mobile base station device.

21. The terminal device of claim 12, wherein The first terminal entity informs the first base station entity of state information in a case where the first backhaul base station indicates the first terminal entity to return from a connected state to an idle state or an inactive state through an RRC reconfiguration message or an RRC release message, wherein the state information comprises at least one of the following: an RRC connected state, an RRC idle state, and an RRC inactive state.

22. The terminal device of claim 12, wherein The first terminal entity can reestablish or update a backhaul PDU session in a process of moving the first terminal entity or the mobile base station device.

23. The terminal device of claim 12, wherein The first terminal entity informs the first base station entity to configure a second base station entity or a second cell of the first base station before or when a cross-user plane function (UPF) or access and mobility management function (AMF) handover is triggered, wherein the second base station entity is a base station in a new logical mobile base station device. 24.A user equipment, comprising: a user equipment in an RRC connected state is handed over from a first base station entity to a second base station entity or other wireless node, or a user equipment in an RRC idle or RRC inactive state is reselected to a second base station entity or other wireless node. 25.The user equipment of claim 24, wherein: the user equipment is connected to a first base station entity or a mobile base station device; and the radio access technology of the user equipment comprises at least one of 5G or 6G radio access.

26. A method of communication, comprising: applying to the first base station entity, wherein the first base station entity is a base station part in the mobile base station device, and the first base station entity supports all or part of base station functions; the method comprises: the first base station entity sends a first request message to a core network, wherein the first request message comprises at least one of a base station identifier of the first base station entity, a public land mobile network (PLMN) of a cell in the first base station entity, a tracking area code (TAC), and first indication information; wherein the traffic of the first base station entity comprises at least one of traffic carried on an interface with the core network, traffic carried on an inter-base station interface, and traffic carried with a network management, and the traffic of the first base station entity is transmitted by at least one backhaul protocol data unit (PDU) session on the first terminal entity.

27. The method of claim 26, wherein, the mobile base station device comprises the first terminal entity and at least one base station entity, wherein the base station entity comprises at least the first base station entity; and the mobile base station device is installed on a moving object to provide services for user equipment inside or outside the moving object.

28. The method of claim 27, wherein, the first terminal entity and the first base station entity adopt or connect to the same or different core network or PLMN, and the core network comprises at least one of a 5G or 6G core network control plane entity and / or user plane entity.

29. The method of claim 26, wherein, the method further comprises: the first base station entity establishes an IP connection with an operation and maintenance management center by using an internet protocol address and a port address of the operation and maintenance management center notified by the first terminal entity or preconfigured information.

30. The method of claim 29, wherein, the method further comprises: the first base station entity acquires related information of cell establishment and configuration from the operation and maintenance management center, wherein the related information comprises cell broadcast message master information block (MIB) / system information block (SIB) message configuration, private parameter configuration of the cell, internet protocol address and port address of a second core network entity, and a public land mobile network (PLMN) list of the second core network entity, and the connection between the first base station entity and the operation and maintenance management center is transmitted by a PDU session on the first terminal entity.

31. The method of claim 26, wherein, the method further comprises: the first base station entity establishes a stream control transmission protocol (SCTP) connection with a network according to its own internet protocol address and an internet protocol address of a network entity, wherein the network entity comprises a second core network entity or a backhaul base station.

32. The method of claim 26, wherein, the method further comprises: The first base station entity sends the first request message to a second core network entity, wherein the first request message comprises: the first indication information, a base station identifier of the first base station entity, at least one of a PLMN and a tracking area code (TAC) of a cell in the first base station entity; and the first indication information is used to indicate a mobile base station to the core network.

33. The method of claim 32, wherein, The first request message comprises: an NG SETUP REQUEST or an NG RAN CONFIGURATION UPDATE in a 5G system, or an interface establishment request or an interface update request message between a base station and a core network in a 6G system.

34. The method of claim 26, wherein, The method further comprises: The first base station entity deletes an SCTP connection with the second core network entity and stops sending a broadcast message or closes a cell according to indication information of the first terminal entity, wherein the indication information is triggered when the first terminal entity changes from a connected state to an idle state or an inactive state, or switches to another backhaul base station or cell.

35. The method of claim 34, wherein, The method further comprises: The first base station entity attempts to establish a connection with the second core network entity and starts a cell broadcast message when state information of the first terminal entity changes from the idle state or the inactive state to a connected state.

36. The method of claim 26, wherein, The method further comprises: During movement of the first base station entity or the mobile base station device, the first base station entity switches or reselects a user equipment residing in a first cell of the first base station entity to a second base station entity or a second cell of the first base station entity; the second base station entity or the second cell of the first base station entity is a new logical base station or cell in the mobile base station device.

37. A method of communication, comprising: The method is applied to a first terminal entity, wherein the first terminal entity is a terminal part in a mobile base station device; the method comprises: The first terminal entity is connected to a network through a radio resource control (RRC) connection establishment process with a backhaul base station, wherein the first terminal entity establishes at least one backhaul protocol data unit (PDU) session bearer with the network.

38. The method of claim 37, wherein, The first terminal entity supports part or all of user equipment (UE) functions, wherein the UE functions comprise at least one of 5G or 6G functions.

39. The method of claim 37, wherein, The first terminal entity supports at least one of an RRC connected state, an RRC idle state, and an RRC inactive state.

40. The method of claim 39, wherein, When the first terminal entity is in a connected state, the first terminal entity and a first core network entity establish at least one session bearer; Traffic of the first base station entity is transmitted by at least one backhaul protocol data unit (PDU) session on the first terminal entity, wherein the traffic of the first base station entity comprises at least one of traffic carried on a core network interface, traffic carried on an inter-base station interface, and traffic carried between an operation and maintenance management center.

41. The method of claim 37, wherein, The method further comprises: The first terminal entity sends user capability indication information to a first core network entity, wherein the user capability indication information comprises at least one of the following: mobile base station device indication information, a multi-cell indication, or a multi-base station indication, the mobile base station device indication information being used to indicate that the first terminal entity supports a mobile base station device, and the multi-cell indication or the multi-base station indication being used to represent that the mobile base station device supports at least two cells or base stations in a handover process.

42. The method of claim 41, wherein, The first terminal entity sends user capability indication information to a first core network entity, wherein the user capability indication information comprises at least one of the following: mobile base station device indication information, a multi-cell indication, or a multi-base station indication, the mobile base station device indication information being used to indicate that the first terminal entity supports a mobile base station device, and the multi-cell indication or the multi-base station indication being used to represent that the mobile base station device supports at least two cells or base stations in a handover process.

43. The method of claim 37, wherein, The method further comprises: The first terminal entity sends a non-access stratum (NAS) message to the first core network entity to inform the first core network entity to establish at least one session bearer, wherein the NAS message comprises quality of service (QoS) requirements or suggestions used by one or more session bearers, and the session bearers are used to carry signaling of interfaces between base stations and the core network, interfaces between base stations and the core network, interfaces between base stations and the core network, or interfaces between operation and maintenance management centers.

44. The method of claim 37, wherein, The method further comprises: The first terminal entity receives an RRC message sent by the first backhaul base station, wherein the RRC message is used to configure a plurality of DRBs for the first terminal entity, and to map bearers used to carry signaling of interfaces between base stations and the core network, interfaces between base stations and the core network, interfaces between base stations and the core network, or interfaces between operation and maintenance management centers to at least one DRB.

45. The method of claim 37, wherein, The method further comprises: The first terminal entity informs the first base station entity to establish a connection with an operation and maintenance management center through an internal interface in the mobile base station device.

46. The method of claim 37, wherein, The method further comprises: In a case where the first backhaul base station indicates the first terminal entity to return from a connected state to an idle state or an inactive state through an RRC reconfiguration message or an RRC release message, the first terminal entity informs the first base station entity of state information, wherein the state information comprises at least one of the following: an RRC connected state, an RRC idle state, and an RRC inactive state.

47. The method of claim 37, wherein, The method further comprises: During movement of the first terminal entity or the mobile base station device, the first terminal entity re-establishes or updates a backhaul PDU session.

48. The method of claim 37, wherein, The method further comprises: When a cross-user plane function (UPF) or an access and mobility management function (AMF) handover is triggered or before the handover, the first terminal entity informs the first base station entity to configure a second base station entity or a second cell of the first base station, wherein the second base station entity is a base station in a new logical mobile base station device.

Images