WO2023179262A1

WO2023179262A1 - Cell information configuration method and apparatus, and readable storage medium and chip system

Info

Publication number: WO2023179262A1
Application number: PCT/CN2023/076905
Authority: WO
Inventors: 朱方园; 李岩
Original assignee: 华为技术有限公司
Priority date: 2022-03-25
Filing date: 2023-02-17
Publication date: 2023-09-28
Also published as: CN116846445A

Abstract

A cell information configuration method and apparatus, and a readable storage medium and a chip system, which relate to the technical field of communications and are used for configuring a TAC for a mobile relay that has mobility. In the present application, a TAC of a cell of a DU entity of a mobile relay is a TAC of a cell of an access network device that an MT entity of the mobile relay accesses. In this way, a network side can determine, according to a TAC of a mobile relay that a terminal device accesses, a cell of an access network device that the mobile relay accesses, and can then determine the location of the terminal device that accesses the mobile relay.

Description

Cell information configuration method, device, readable storage medium and chip system

Cross-references to related applications

This application requires the priority of a Chinese patent application submitted to the China Patent Office on March 25, 2022, with the application number 202210307059. The entire contents of which are incorporated herein by reference.

Technical field

The present application relates to the field of communication technology, and in particular to a cell information configuration method, device, readable storage medium and chip system.

Background technique

In order to improve network capacity and coverage, a relay node that supports wireless backhaul transmission is proposed to implement dense network deployment. Devices that support relay functions are referred to as relay devices (can also be called relays or relay nodes). Relay devices provide similar functions and services to ordinary base stations for terminals accessing their cells. Relay devices and terminals The communication link between them is called the access link. The relay device accesses a base station serving it in a terminal-like manner through a wireless interface. The base station is called a donor base station. The wireless interface link between the relay device and the donor base station is called a backhaul link. road (backhaul link).

In the fifth generation (the fifth generation, 5G) new radio (NR) research, integrated access and backhaul (integrated access and backhaul) that integrates wireless access links and wireless backhaul links are proposed. IAB) node. The IAB node can access the network through its mobile terminal (MT) function, and then the operations administration and maintenance (OAM) device configures cell information for the IAB node. The cell information can include the IAB node. Configured tracking area code (TAC). Existing IAB nodes are fixed relay devices on the ground. When a terminal device accesses the fixed IAB node, the network side can determine the location of the terminal device based on the TAC of the IAB node cell currently accessed by the terminal device.

With the development of technology, mobile relay devices are required in many application scenarios. For example, a mobile base station relay (also known as vehicle mounted relay (VMR)) is proposed based on the vehicle scenario. The VMR node can be configured in the vehicle and can move with the vehicle. The VMR can be in the vehicle Or the terminal equipment near the vehicle provides services. It can be understood that the VMR node is an IAB node with mobile capabilities. The VMR can also be called a mobile relay.

Similar to the existing IAB architecture, a VMR node can access a base station serving it through a wireless interface in a terminal-like manner. The base station can be called a donor base station. The link between the relay device and the donor base station is The wireless interface link is called the backhaul link. In addition, the VMR node can also access the network through its MT function, and then the OAM device configures cell information for the VMR node.

Currently, how to configure cell information for relay devices with mobile capabilities has become an urgent problem that needs to be solved.

Contents of the invention

This application provides a cell information configuration method, device, readable storage medium and chip system for configuring cell information for relay equipment with mobile capabilities.

In a first aspect, this application provides a method for configuring cell information, which method can be executed by a relay device with mobile capabilities or a unit, module or chip within the relay device. For easy understanding, in the embodiments of this application, the relay device with mobility capability is called a mobile relay. Mobile relay includes MT entities and distributed unit (DU) entities. This application takes the method being executed by the MT entity of the mobile relay as an example for illustration. The mobile relay is in a moving state, and is used to provide relay services between terminal equipment and access network equipment. The access network device may also be called the host base station of the mobile relay. The method includes:

The MT entity receives the first TAC from the access network device. The first TAC is the TAC of the first cell of the access network device to which the MT entity accesses. The MT entity sends the first TAC to the DU entity. The first TAC is the TAC of the cell that is the DU entity.

In order to illustrate the beneficial effects brought by this method, a comparison scheme is introduced below. In this comparison scheme, the TAC of the mobile relay is not determined based on the location information of the mobile relay. For example: the management device configures a fixed TAC for the mobile relay cell, such as TAC#1. The mobile relay is located at the first position, and the TAC included in the broadcast message sent by mobile relay 3 is TAC#1. When the mobile relay moves from the first position to the second position (for example, the cell corresponding to the first position is different from the cell corresponding to the second position), the TAC of mobile relay 3 does not change, and the broadcast message sent by mobile relay 3 The TAC included in is still TAC#1. Because for a terminal device that accesses the mobile relay, the TAC of the mobile relay that the terminal device accesses is always TAC#1. Therefore, even if the mobile relay has moved to the second position, the network side may still think that the mobile relay is at the first position, and then determine that the terminal device accessing the mobile relay is also near the first position. It can be seen that configuring a fixed TAC for the mobile relay will cause the network side to determine incorrect location information for the UE accessing the mobile relay.

In the embodiment of the present application, since the TAC of the cell of the DU entity of the mobile relay is the TAC of the cell of the access network device accessed by the MT entity of the mobile relay, the network side (such as network element, network side equipment) , device, etc.) can determine the cell of the access network device that the mobile relay is connected to based on the TAC of the mobile relay that the terminal device is connected to, and then can more accurately determine the terminal device that is connected to the mobile relay. Current location. It can be seen that the cell information configuration method provided by this application can configure cell configuration information for a relay with mobility capabilities.

In a possible implementation, the first TAC sent by the MT entity to the DU entity may be carried in the first message. For example, the MT entity sends the first message to the DU entity, and the first message includes the first TAC. The first TAC is used to instruct the DU entity to use the first TAC as the TAC of the cell of the DU entity. In this way, after receiving the first message, the DU entity can determine that the TAC of the cell of the DU entity needs to be updated to the first TAC.

In a possible implementation, when the MT entity determines that the mobile relay has moved, the MT entity sends the first TAC to the DU entity. Since the MT entity sends the TAC of the cell accessed by the MT entity to the DU entity after determining that the mobile relay has moved, the DU entity can be caused to update the TAC of the cell of the DU entity to the TAC of the cell accessed by the mobile relay after the movement. TAC of the cell, thereby achieving the effect of dynamically configuring TAC for the mobile relay, and then the network side can more accurately determine the current location of the terminal device based on the TAC of the mobile relay accessed by the terminal device.

In a possible implementation manner, the MT entity determines that the mobile relay has moved based on at least one of the TAC of the cell accessed by the MT entity, the cell identity, or the identity of the access network device. For example, the MT entity receives a second broadcast message from the second cell of the second access network device. The second broadcast message includes at least one of the third TAC, the identity of the second cell, or the identity of the second access device. . After the MT entity receives the second broadcast message, the MT entity receives the first broadcast message of the first cell of the first access network device, where the first broadcast message includes the second TAC of the first cell of the first access network device, the At least one of the identification of a cell or the identification of the first access network device. The MT entity determines that the MT entity moves when it determines that at least one of the following contents is satisfied: the second TAC is different from the third TAC, or the identity of the first cell is different from the identity of the second cell, or, the first The identifier of the access device is different from the identifier of the second access device.

It can be seen that the MT entity will receive broadcast messages in different cells, and then the MT entity can determine whether the MT entity has moved based on the information carried in the broadcast message, and then report the location information to the DU entity when it is determined that movement has occurred. .

It is worth noting that in this application, in order to compare at least one of the TAC, the cell identity or the identity of the access network device of the MT entity's access cell before and after the mobile relay moves, the MT entity can compare the mobile relay The MT entity stores at least one of the TAC of the access cell, the cell identity, or the identity of the access network device. For example, after receiving the second broadcast message, the MT entity may store the third TAC and the third TAC included in the second broadcast message. At least one of the identity of the second cell or the identity of the second access device.

On the other hand, the MT entity determines whether the mobile relay has moved based on at least one of the second TAC of the first cell of the first access network device, the identity of the first cell, or the identity of the first access network device, It can also prevent the MT entity from frequently reporting the TAC of the cell to which the MT entity accesses. For example, the MT entity is always in a mobile state, but it does not mean that the MT entity will report the TAC of the cell accessed by the MT entity to the DU entity whenever the MT entity moves. Instead, the movement of the mobile device needs to meet the preset movement range before reporting the MT entity to the DU entity. TAC of the accessed cell. For example, if the mobile device moves out of the cell it is currently accessed, the movement of the mobile device satisfies the preset movement range. When the MT entity determines that at least one of the TAC, cell identity, and access network equipment of the accessed cell changes, the MT entity may move out of the currently accessed cell. Therefore, the MT entity may At least one of the TAC of the cell where the entity accesses, the cell identity, and the access network equipment that the entity accesses determines that when the MT entity moves, the movement of the MT entity will satisfy the preset movement range to a large extent. Therefore, the MT entity moves according to the MT At least one of the TAC of the cell to which the entity accesses, the cell identifier, and the access network device to which the entity accesses determines that the MT entity reports the TAC of the cell to which the MT entity accesses when it is determined that the MT entity has moved.

In another possible implementation, a preset movement range can be set. When the MT entity determines that the movement of the MT entity satisfies the preset movement range, the MT entity reports location information. For example, the preset mobility range may include at least one of the following: a change in the TAC of the cell to which the MT entity is accessed, a change in the cell identity of the cell to which the MT entity is accessed, or a change in the cell to which the MT entity is accessed. Network equipment has changed.

For example, the preset mobility range includes: the TAC of the cell accessed by the MT entity changes. In this case, when the TAC of the cell that the MT entity determines to access changes, the MT entity may send the TAC of the cell that the MT entity accesses to the DU entity.

In another possible implementation, when the MT entity determines that the mobility of the intermediate mobile level does not meet the preset mobility range, the MT entity may not send the TAC of the cell accessed by the MT entity to the DU entity.

For example, the preset mobility range includes: the TAC of the cell accessed by the MT entity changes. In this case, when the MT entity determines that the TAC of the accessed cell has not changed, it is possible that the movement amount of the MT entity is small. In this case Under this condition, the MT entity may be allowed not to send the TAC of the cell to which the MT entity is connected to the DU entity. In this way, the MT entity may be prevented from frequently sending the TAC of the cell to which the MT entity is connected to the DU entity, and signaling consumption may be reduced.

For another example, the preset movement range includes: the identity of the access network device accessed by the MT entity changes. In this case, when the MT entity determines that the identity of the access network device has not changed, it is possible that the movement amount of the MT entity is small. In this case, the MT entity may be allowed not to send the received data of the MT entity to the DU entity. TAC of the incoming cell. In this way, the MT entity can avoid frequently reporting the location information of the MT entity, and the signaling consumption can be reduced.

In a possible implementation, the MT entity sends first indication information to the management device, and the first indication information is used to indicate that the management device does not need to configure a TAC for the DU entity's cell.

Since the management device no longer configures the TAC for the cell of the DU entity, other devices (such as the DU entity) can determine the TAC of the cell of the DU entity. It can also be understood that the MT entity sends the first indication information to the management device, so that the management device does not need to configure a TAC for the DU entity's cell. This step can lay the foundation for the subsequent DU entity to determine the TAC of the DU entity's cell.

In the second aspect, this application provides a method for configuring cell information, which method can be executed by a mobile relay or a unit, module or chip within the mobile relay. For easy understanding, in the embodiments of this application, the relay device with mobility capability is called a mobile relay. Mobile relay includes MT entity and DU entity. This application takes the method being executed by the DU entity of the mobile relay as an example for illustration. The mobile relay is in a moving state, and is used to provide relay services between terminal equipment and access network equipment. The method includes:

The DU entity receives the first TAC from the MT entity, where the first TAC is the TAC of the first cell of the access network device to which the MT entity accesses. The DU entity sends the first TAC to the access network device, where the TAC of the cell of the DU entity is the first TAC.

It should be noted that the access network device accessed by the MT entity and the access network device used to receive the first TAC from the DU entity may be the same access network device, or they may be two different access network devices. , this application does not limit it. In order to facilitate understanding, part of the content in this application is introduced by taking the two access network devices as the same access network device as an example.

Since the TAC of the cell of the DU entity of the mobile relay is the TAC of the cell of the access network equipment accessed by the MT entity of the mobile relay, the network side (such as network elements, network side equipment, devices, etc.) The TAC of the mobile relay to which the device is connected determines the cell of the access network device to which the mobile relay is connected, and then the terminal device in the cell of the DU entity that accesses the mobile relay is currently located can be determined more accurately. Location. It can be seen that the cell information configuration method provided by this application can configure cell configuration information for a relay with mobility capabilities.

In a possible implementation manner, after the DU entity receives the first TAC from the MT entity, the DU entity determines the first TAC as the TAC of the DU entity's cell. Since the DU entity determines the TAC of the cell of the DU entity as the TAC of the access network equipment accessed by the MT entity of the mobile relay, the network side (such as network elements, network side equipment, devices, etc.) can determine the TAC of the cell according to the terminal The TAC of the mobile relay to which the device is connected determines the cell of the access network device to which the mobile relay is connected, and then the terminal device in the cell of the DU entity that accesses the mobile relay is currently located can be determined more accurately. Location. It can be seen that the cell information configuration method provided by this application can configure cell configuration information for a relay with mobility capabilities.

In a possible implementation manner, the DU entity sends a third message to the access network device, where the third message includes the first TAC, and the third message is used to request activation of the cell of the DU entity. It can be seen that the DU entity is requesting the access network device to activate When activated to the cell of the DU entity, the first TAC is sent to the access network device, so that the TAC of the cell of the DU entity after activation by the access network device is the first TAC. In this way, when the DU entity initially activates the DU entity cell, the TAC of the DU entity's cell can be set to the TAC of the cell accessed by the MT entity, so that the network side (such as network elements, network side equipment, devices, etc.) The cell of the access network device to which the mobile relay is connected can be determined based on the TAC of the mobile relay to which the terminal device is connected, and then the terminal device to the cell of the DU entity of the mobile relay can be determined more accurately. Current location.

In a possible implementation, the DU entity sends first indication information to the management device, and the first indication information is used to indicate that the management device does not need to configure a TAC for the DU entity's cell.

Since the management device no longer configures the TAC for the cell of the DU entity, other devices (such as the DU entity) can determine the TAC of the cell of the DU entity. It can also be understood that the DU entity sends the first indication information to the management device, so that the management device does not need to configure a TAC for the DU entity's cell. This step lays the foundation for the DU entity to determine the TAC of the DU entity's cell.

In a third aspect, this application provides a method for configuring cell information, which method can be executed by a mobile relay or a unit, module or chip within the mobile relay. Mobile relay includes MT entity and DU entity. This application takes the method executed by a mobile relay as an example for illustration. The mobile relay is in a moving state, and is used to provide relay services between terminal equipment and access network equipment. The method includes:

The MT entity of the mobile relay receives the first TAC from the access network device. The first TAC is the TAC of the first cell of the access network device to which the MT entity accesses. The MT entity of the mobile relay sends the first TAC to the DU entity of the mobile relay. The DU entity of the mobile relay receives the first TAC from the MT entity. The DU entity sends the first TAC to the access network device. The TAC of the DU entity's cell is the first TAC.

In the fourth aspect, this application provides a method for configuring cell information, which method can be executed by a mobile relay or a unit, module or chip within the mobile relay. Mobile relay includes MT entity and DU entity. This application takes the method executed by a mobile relay as an example for illustration. The mobile relay is in a moving state, and is used to provide relay services between terminal equipment and access network equipment. The method includes:

The DU entity of the mobile relay sends second instruction information to the access network device, and the second instruction information instructs the access network device to configure TAC for the cell of the DU entity. The DU entity of the mobile relay receives the first TAC from the access network device, and the first TAC is used as the TAC of the cell serving as the DU entity. The first TAC is the TAC of the first cell of the access network device to which the MT entity of the mobile relay accesses. Wherein, the mobile relay is in a moving state, and the mobile relay is used to provide relay services between the terminal equipment and the access network equipment.

Since the mobile relay sends the second indication information to the access network device, the access network device can configure TAC for the cell of the DU entity. And since the TAC of the cell of the DU entity of the mobile relay is the TAC of the cell of the access network equipment accessed by the MT entity of the mobile relay, the network side (such as network elements, network side equipment, devices, etc.) can be based on end The TAC of the mobile relay accessed by the terminal device determines the cell of the access network device accessed by the mobile relay, and then can more accurately determine the current location of the terminal device in the cell of the DU entity accessed by the mobile relay. s position. It can be seen that the cell information configuration method provided by this application can configure cell configuration information for a relay with mobility capabilities.

In a possible implementation, before the DU entity of the mobile relay receives the first TAC from the access network device, the DU entity of the mobile relay sends the identifier of the MT entity to the access network device; the identifier of the MT entity is used to Determine the first TAC.

The mobile relay may send the identity of the MT entity to the access network device, so that the access network device can query the TAC of the cell to which the MT entity accesses based on the identity of the MT entity.

In a possible implementation, the DU entity of the mobile relay sends the second indication information to the access network device, including: the DU entity of the mobile relay sends a second message to the access network device, and the second message requests activation of the DU The second message includes the second indication information of the entity's cell.

In this way, when the access network device activates the cell of the DU entity for the DU entity, it may allocate a TAC to the cell of the DU entity. In this way, when the DU entity's cell is initially activated, its TAC can be configured as the TAC of the cell accessed by the MT entity. Therefore, the network side (such as network elements, network side equipment, devices, etc.) can access according to the terminal equipment. The TAC of the mobile relay determines the cell of the access network device to which the mobile relay is connected, and then the current location of the terminal device connected to the cell of the DU entity of the mobile relay can be determined relatively accurately. It can be seen that the cell information configuration method provided by this application can configure cell configuration information for a relay with mobility capabilities.

In a possible implementation, the second message does not contain TAC. Since the access network device can allocate TAC to the cell of the DU entity, the second message does not need to carry the TAC, which can reduce the amount of data in the second message.

In addition, the second message for requesting to activate the cell of the DU entity does not include the TAC, which can also be understood as an indication message. That is, when the access network device receives the second message for requesting to activate the cell of the DU entity, when it determines that the If the TAC is not included in the second message, the TAC may be allocated to the cell of the DU entity.

In another possible implementation, when the second message for requesting activation of the cell of the DU entity includes a TAC, the access network device may not need to allocate a TAC to the cell of the DU entity. This implementation is only an optional implementation. In another possible implementation, when the second message for requesting activation of the cell of the DU entity includes a TAC, the access network device may also ignore the TAC and re-allocate a TAC to the cell of the DU entity.

In a fifth aspect, this application provides a method for configuring cell information, which method can be executed by an access network device or a unit, module or chip within the access network device. This application takes the method executed by the access network device as an example for illustration. The method includes:

The access network device receives a third message from the DU entity of the mobile relay. The third message is used to request activation of the cell of the DU entity. The third message includes the first TAC, and the TAC of the cell of the DU entity is the first TAC. The access network device returns a response message of the third message to the DU entity of the mobile relay, where the response message of the third message is used to indicate that the cell of the DU entity has been activated. Wherein, the mobile relay is in a moving state, and the mobile relay is used to provide relay services between the terminal equipment and the access network equipment.

In a possible implementation, the first TAC is the TAC of the first cell of the access network device to which the MT entity of the mobile relay accesses. Since the TAC of the cell of the DU entity of the mobile relay is the TAC of the cell of the access network equipment accessed by the MT entity of the mobile relay, the network side (such as network elements, network side equipment, devices, etc.) The TAC of the mobile relay to which the device is connected determines the cell of the access network device to which the mobile relay is connected, and can then be compared Accurately determine the current location of the terminal equipment in the cell that accesses the DU entity of the mobile relay. It can be seen that the cell information configuration method provided by this application can configure cell configuration information for a relay with mobility capabilities.

In a sixth aspect, the present application provides a method for configuring cell information. The present application provides a method for configuring cell information. The method can be executed by an access network device or a unit, module or chip within the access network device. This application takes the method executed by the access network device as an example for illustration. The method includes:

The access network device obtains the first TAC, which is the TAC of the first cell of the access network device to which the MT entity of the mobile relay accesses. The access network device sends the first TAC to the DU entity of the mobile relay, where the first TAC is used as the TAC of the cell serving as the DU entity. Wherein, the mobile relay is in a moving state, and the mobile relay is used to provide relay services between the terminal equipment and the access network equipment.

In a possible implementation, the access network device receives the identity of the MT entity. The access network device obtains the first TAC according to the identification of the MT entity.

Relevant beneficial effects and descriptions can be found in the relevant content of the fourth aspect mentioned above, and will not be described again.

In a possible implementation, the access network device receives second indication information, and the second indication information instructs the access network device to configure a TAC for the cell of the DU entity.

In a possible implementation, the access network device receives a second message from the DU entity of the mobile relay, and the second message requests activation of the cell of the DU entity. The second message may include the first indication information and/or the identity of the MT entity. Relevant beneficial effects and descriptions can be found in the relevant content of the fourth aspect mentioned above, and will not be described again.

In a possible implementation, the second message does not contain TAC. Relevant beneficial effects and descriptions can be found in the relevant content of the fourth aspect mentioned above, and will not be described again.

In a possible implementation, before the access network device sends the first TAC to the DU entity of the mobile relay, the access network device determines that the mobile relay has moved.

Relevant beneficial effects and descriptions are similar to those related to the first aspect in which the MT entity determines that the mobile relay has moved, and will not be described again.

In a possible implementation, the access network device determines that the mobile relay has moved based on at least one of the TAC, cell identity, geographical area information, or movement distance of the cell accessed by the MT entity of the mobile relay.

In a seventh aspect, a communication device is provided. The communication device may be the above-mentioned mobile relay or management device. The communication device may include a communication unit and a processing unit to perform any one of the methods in the first to sixth aspects. any implementation. The communication unit is used to perform functions related to sending and receiving. Optionally, the communication unit includes a receiving unit and a sending unit. In one design, the communication device is a communication chip, the processing unit may be one or more processors or processor cores, and the communication unit may be an input/output circuit or port of the communication chip.

In another design, the communication unit may be a transmitter and a receiver, or the communication unit may be a transmitter and a receiver.

Optionally, the communication device further includes various modules that can be used to perform any one of the implementation methods of any one of the above-mentioned first to sixth aspects.

In an eighth aspect, a communication device is provided. The communication device may be the above-mentioned mobile relay or management device. The communication device may include a processor and a memory. Optionally, a transceiver is also included, the memory is used to store computer programs or instructions, and the processor is used to call and run the computer program or instructions from the memory. When the processor executes the computer program or instructions in the memory, the The communication device performs any one of the implementation methods of any one of the above-mentioned first to sixth aspects.

Optionally, there are one or more processors and one or more memories.

Optionally, the memory can be integrated with the processor, or the memory can be provided separately from the processor.

Optionally, the transceiver may include a transmitter (transmitter) and a receiver (receiver).

In a ninth aspect, a communication device is provided. The communication device may be the above-mentioned mobile relay or management device, and the communication device may include a processor. The processor is coupled to a memory and may be used to execute any one of the first to sixth aspects and the method in any possible implementation manner of the first to sixth aspects. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

In one implementation, when the communication device is a wireless communication device, the communication interface may be a transceiver or an input/output interface. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input/output interface may be an input/output circuit.

In another implementation, when the communication device is a chip or a chip system, the communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or chip system, etc. . A processor may also be embodied as a processing circuit or logic circuit.

In a tenth aspect, a system is provided, which includes the above-mentioned mobile relay and management equipment. Mobile relay may include DU entities and MT entities.

In an eleventh aspect, a computer program product is provided. The computer program product includes: a computer program (which can also be called a code, or an instruction). When the computer program is run, it causes the computer to perform any one of the possibilities in the first aspect. The method in the implementation mode, or causing the computer to execute the method in the implementation mode of any one of the above-mentioned first to sixth aspects.

In a twelfth aspect, a computer-readable storage medium is provided. The computer-readable medium stores a computer program (which may also be called a code, or an instruction). When run on a computer, the computer-readable medium causes the computer to execute any of the above-mentioned aspects of the first aspect. A method in a possible implementation, or causing the computer to execute any of the implementations of the first to sixth aspects above Methods.

In a thirteenth aspect, a chip system is provided, which may include a processor. The processor is coupled to a memory and may be used to execute any one of the first to sixth aspects, and any method in any possible implementation manner of any one of the first to sixth aspects. Optionally, the chip system also includes a memory. Memory is used to store computer programs (also called codes, or instructions). The processor is used to call and run the computer program from the memory, so that the device installed with the chip system executes any one of the first to sixth aspects, and any one of the first to sixth aspects possible. Methods in the implementation.

In a fourteenth aspect, a communication device is provided. The communication device may be the above-mentioned mobile relay or management device. The communication device may include: an interface circuit and a processing circuit. Interface circuits may include input circuits and output circuits. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, so that the method in any one of the first to sixth aspects and any possible implementation manner of the first to sixth aspects is implemented.

In a specific implementation process, the above-mentioned processing device may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, and various logic circuits. The input signal received by the input circuit may be received and input by, for example, but not limited to, the receiver, and the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by the transmitter, and the input circuit and the output A circuit may be the same circuit that functions as an input circuit and an output circuit at different times. This application does not limit the specific implementation methods of the processor and various circuits.

In one implementation, when the communication device is a wireless communication device, the wireless communication device may be a terminal such as a smartphone or a wireless access network device such as a base station. The interface circuit may be a radio frequency processing chip in the wireless communication device, and the processing circuit may be a baseband processing chip in the wireless communication device.

In yet another implementation manner, the communication device may be a part of a wireless communication device, such as an integrated circuit product such as a system chip or a communication chip. The interface circuit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or chip system, etc. The processing circuitry may be logic circuitry on the chip.

Description of the drawings

Figure 1a is a schematic diagram of a possible application scenario applicable to the embodiment of the present application;

Figure 1b is a schematic diagram of a network architecture to which embodiments of the present application may be applicable;

Figure 1c is a schematic diagram of a possible system architecture applicable to the embodiment of the present application;

Figure 1d is a schematic diagram of a possible system architecture applicable to the embodiment of the present application;

Figure 2 is a schematic flow chart of another possible cell information configuration method provided by the embodiment of the present application;

Figure 3a is a schematic flow chart of another possible cell information configuration method provided by the embodiment of the present application;

Figure 3b is a schematic flow chart of another possible cell information configuration method provided by the embodiment of the present application;

Figure 4a is a schematic flow chart of another possible cell information configuration method provided by the embodiment of the present application;

Figure 4b is a schematic flow chart of another possible cell information configuration method provided by the embodiment of the present application;

Figure 5 is a schematic flow chart of another possible cell information configuration method provided by the embodiment of the present application;

Figure 6a is a schematic flow chart of another possible cell information configuration method provided by the embodiment of the present application;

Figure 6b is a schematic flow chart of another possible cell information configuration method provided by the embodiment of the present application;

Figure 7 is a schematic flow chart of another possible cell information configuration method provided by the embodiment of the present application;

Figure 8 is a possible structural schematic diagram of the device provided by the embodiment of the present application;

Figure 9 is another possible structural schematic diagram of the device provided by the embodiment of the present application;

Figure 10 is a possible structural schematic diagram of the device provided by the embodiment of the present application.

Detailed ways

The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

Figure 1a exemplarily shows a schematic diagram of a possible application scenario applicable to the embodiment of the present application. As shown in Figure 1a, this scenario includes one or more access network devices. In Figure 1a, the access network device includes a base station. 1 and base station 2 are taken as examples for illustration. Base station 1 includes cell 101 and cell 102, and base station 2 includes cell 103.

As shown in Figure 1a, this scenario includes mobile relay 3. Mobile relay 3 needs to perform cell selection when accessing the network, and subsequently initiates random access in the cell. The access network equipment corresponding to the cell accessed by mobile relay 3 can be called a host base station. In Figure 1a, mobile relay 3 is used as a vehicle-mounted relay for illustration. Figure 1a shows a possible driving path of the mobile relay 3. According to the driving path, the mobile relay 3 can sequentially access the cell 101 of the base station 1, the cell 102 of the base station 1 and the cell 103 of the base station 2. .

On the other hand, mobile relay can provide access services for other terminal devices. In Figure 1a, the terminal device is user equipment (UE) as an example. As shown in Figure 1a, the UE can access the cell of mobile relay 3. The UE may be a terminal device of a passenger riding on a vehicle in which the mobile relay 3 is deployed. Of course, it may also be a terminal device located at other locations, which is not limited by the embodiment of this application. Any two UEs among the three UEs shown in Figure 1a may be the same or different, and are not limited in this embodiment of the present application.

Since mobile relay 3 has mobile capabilities, if the solution of configuring a fixed TAC (such as TAC#1) for mobile relay 3 is adopted, the following problems will occur:

The mobile relay 3 is located at a first location (the first location is, for example, a location within the coverage area of the cell 101 of the base station 1), and the TAC included in the broadcast message sent by the mobile relay 3 is TAC#1. When the mobile relay moves from the cell 101 of base station 1 to a second location (the second location is, for example, a location within the coverage area of cell 102 of base station 1 or cell 103 of base station 2), the TAC of mobile relay 3 does not change. , the TAC included in the broadcast message sent by the mobile relay 3 is still TAC#1. Because for a UE accessing mobile relay 3, the TAC of mobile relay 3 accessed by the UE is TAC#1. Therefore, even if the mobile relay has moved to the second position, the network side may still think that the mobile relay 3 is at the first position, and then determine that the UE accessing the mobile relay 3 is also near the first position. It can be seen that configuring a fixed TAC for mobile relay 3 will cause the network side to determine incorrect location information for UEs accessing the mobile relay.

To address this problem, the embodiment of the present application aims to use the TAC of mobile relay 3 as the TAC of the cell of the access network that mobile relay 3 accesses. Therefore, when the UE accesses the cell of mobile relay 3, the UE can obtain TAC to mobile relay 3's cell. Then, the network side can more accurately determine the current location of the terminal device based on the TAC of the mobile relay accessed by the terminal device. It can be seen that the solution provided by the embodiment of this application can configure TAC for the mobile relay.

The communication systems mentioned in the embodiments of this application include but are not limited to: fifth generation mobile networks or 5th generation wireless systems (5G), or communication systems or communication networks after 5G, etc., such as new wireless (new radio, NR) system, etc.

According to the application scenario shown in Figure 1a, Figure 1b takes 5G as an example to illustrate a schematic diagram of a network architecture that may be applicable to the embodiment of the present application. Each device involved in the embodiment of the present application will be introduced below in conjunction with Figure 1b.

(1) Access network equipment.

Please refer to Figure 1b. In Figure 1b, the access network equipment including the base station 1 in Figure 1a is taken as an example for illustration. The relevant content of base station 2 in Figure 1a is similar to that of base station 1 and will not be described again. In the embodiment of this application, the mobile relay can access the access network equipment. The access network equipment can also be called a host node. In English, it can also be called a donor base station, or a donor macro station.

Access network equipment is a device in the communication system that connects terminal side equipment to the wireless network. The core network can be accessed through this node. Access network equipment is connected to the core network (such as 5G Core Network (5GC)) through wired links (such as fiber optic cables). The access network device can be responsible for receiving data from the core network and forwarding it to the wireless backhaul device, or receiving data from the wireless backhaul device and forwarding it to the core network. The access network device may be connected to the network in a wired manner, for example.

As an example, the access network equipment may include a radio network controller (RNC), a node B (Node B, NB), a base station controller (base station controller, BSC), and a base transceiver station (base transceiver station). , BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), base band unit (base band unit, BBU), etc., may also include evolved LTE systems (LTE-Advanced, LTE-A). Evolutionary base station (NodeB or eNB or e-NodeB, evolutionary Node B), or it can also include the next generation Node B (next) in the fifth generation (5G) new wireless (new radio, NR) system. generation node B, gNB), etc.

Please continue to refer to Figure 1b. As another example, the access network equipment may include a gNB-centralized unit (CU) and a gNB-distributed unit (DU). gNB-CU and gNB-DU are connected through the F1 interface. The CU and the core network are connected through the next generation (NG) interface.

Among them, gNB-DU includes the functions of the physical layer (PHY)/medium access control (MAC)/radio link control (RLC) layer, which are used for the access network equipment. The relay equipment attached below provides access services. gNB-DU can connect to gNB-CU through the F1 interface. The gNB-DU can also be connected to the terminal device (such as UE111) or the MT function of the relay device (such as the MT of mobile relay 3) through the Uu interface.

gNB-CU is used to control radio resource control (RRC) for all relay devices and terminal devices under it. For example, it can store the context of relay devices and terminal devices. gNB-CU can connect with the DU function of other relay devices (such as the DU of mobile relay 3 and the DU of mobile relay 4) through the F1 interface.

The function of the access network device may be implemented by hardware components inside the access network device, for example, a processor and/or a programmable chip inside the access network device. Optionally, the chip can be implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The above-mentioned PLD can be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), a system on a chip (system on a chip) , SOC) or any combination thereof.

(2)Mobile relay.

The mobile relay in the embodiment of this application can be understood as a relay device with mobile capabilities. For example, mobile relays may include relay devices deployed on movable objects such as aircraft, high-speed trains, vehicles, and drones, or the mobile relay itself may be a relay device with mobile capabilities. In order to facilitate understanding, part of the content in the embodiment of the present application is shown by taking the mobile relay as a relay device deployed on the vehicle as an example (such as the aforementioned Figure 1a). In the embodiment of the present application, the mobile relay deployed on the vehicle can be Called VMR.

As shown in Figure 1b, similar to the network equipment gNB in 5G, it adopts an architecture that separates the centralized unit (CU) and the distributed unit (DU). The mobile relay can include two parts: MT and DU. In Figure 1b, the mobile relay includes the mobile relay 3 in Figure 1a and the mobile relay 4, and the mobile relay 3 and the mobile relay 4 are currently accessing the base station 1 for illustration.

The MT of mobile relay is similar to the function of user equipment (UE), communicating with the parent node through the Uu interface and providing data backhaul. For example, the MT of mobile relay 3 is connected to the DU of the parent node (base station 1) through the Uu interface.

The DU of mobile relay is similar to the function of DU in gNB, including the functions of PHY/MAC/RLC layer, communicating with sub-nodes and providing access services to sub-nodes. For example, the DU of mobile relay 3 can provide services for sub-nodes (terminal devices (such as UE112) or other relays (such as mobile relay 4)) through the Uu interface. UE 112 in Figure 1b may be a UE that accesses the cell of mobile relay 3 when mobile relay 3 accesses cell 1 or cell 2 of base station 1 in Figure 1a.

Mobile relay 4 is similar to mobile relay 3. The MT of mobile relay 3 can be connected to the DU of the parent node (mobile relay 3) through the Uu interface. For example, the DU of mobile relay 4 can provide services for terminal equipment (such as UE113) or other relays through the Uu interface.

It is worth noting that, for simplicity of description, in the embodiment of this application, the MT of the mobile relay is called the MT function of the mobile relay, the MT entity of the mobile relay, or the MT entity; the DU of the mobile relay is called the mobile relay. Relay DU function, mobile relay DU entity, or DU entity. In addition, the MT entity and DU entity of mobile relay are just an example of naming. In future communication systems or networks, the MT entity and DU entity can also be replaced by modules with equivalent functions, or there can be other names. This article There are no restrictions on this application.

The mobile relay in the embodiment of the present application may also have other names, such as mobile relay node, mobile relay device, relay node, relay device, etc. The embodiment of the present application does not limit its name. For ease of understanding, In the embodiment of this application, mobile relay is taken as an example.

(3)Terminal equipment.

An end device is a device that provides voice and/or data connectivity to a user. The terminal-side device involved in this application may be a terminal device or a terminal, or a hardware component inside the terminal device that can implement the functions of the terminal device. In Figure 1b, the terminal equipment includes UE111, UE112 and UE113 as an example for illustration.

In the embodiment of this application, the terminal side device may be called user equipment (UE), mobile station (MS), mobile terminal (MT), etc., and may include, for example, a handheld device with a wireless connection function. device, or a processing device connected to a wireless modem. The terminal can communicate with the core network via the radio access network (RAN) and exchange voice and/or data with the RAN. Some examples of terminal devices are: personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (personal digital assistant, PDA), barcode, radio frequency identification (RFID), sensors, satellite navigation systems, such as global positioning system (global positioning system, GPS), Beidou positioning system, laser scanners and other information sensing equipment and other equipment.

The terminal side device can also be a wearable device. Wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, they are also implemented through software support, data interaction, and cloud interaction. Present powerful functions. Broadly defined wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones. Used, such as various types of smart bracelets, smart helmets, smart jewelry, etc. for physical sign monitoring. The terminal can also be a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in self-driving (self driving), or remote surgery Wireless terminals in remote medical surgery, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, and smart home Wireless terminals, terminal equipment in the future evolved public land mobile network (PLMN), or vehicle equipment in the Internet of Vehicles (vehicle to everything, V2X), customer premises equipment (CPE) )wait.

The functions of the terminal-side device can be implemented through hardware components inside the terminal device, and the hardware components can be processors and/or programmable chips inside the terminal device. For example, the chip can be implemented by ASIC, or PLD. The above-mentioned PLD can be any one of CPLD, FPGA, GAL, SOC or any combination thereof.

The various terminals introduced above can be considered as vehicle-mounted terminal equipment if they are located on the vehicle (for example, placed or installed in the vehicle).

It is worth noting that Figure 1b may also include other equipment, such as core network equipment or equipment used to carry virtualized network functions, etc., which are not limited by the embodiment of this application. In addition, the network architecture shown in Figure 1b does not limit the number of terminal equipment, mobile relays and access network equipment.

Based on the contents shown in Figures 1a and 1b, Figures 1c and 1d exemplarily illustrate two possible system architecture diagrams applicable to the embodiments of the present application. Figures 1c and 1d are introduced by taking the application of the embodiment of the present application to the 5G network architecture as an example. There are many possible 5G network architectures. Figures 1c and 1d are two possible 5G network architectures provided by the embodiment of the present application. Schematic diagram. As shown in Figure 1c, the network architecture usually includes the following devices, network elements, and networks:

(1)Terminal equipment. For the relevant content of terminal equipment, please refer to the relevant introduction of terminal equipment in Figure 1a and Figure 1b.

(2) Access network equipment. In Figure 1c and Figure 1d, access network equipment including (wireless) access network (radio access network, (R)AN) network elements are used as examples for demonstration. For the relevant content of the access network equipment, please refer to the relevant introduction of the access network equipment in Figure 1a and Figure 1b. One or more mobile relays may be deployed between the terminal device and the access network device, such as mobile relay 3 in Figure 1a above.

(3) User plane network element: used for packet routing and forwarding and quality of service (QoS) processing of user plane data, interconnecting protocol data unit (PDU) sessions with data networks, and packet routing And forwarding, for example, supports uplink classifier on traffic and then forwards it to the data network, supports branching points to support multi-homed PDU sessions, and packet inspection, etc.

As shown in Figure 1c, in the 5G communication system, the user plane network element can be a user plane function (UPF) network element, for example, it can include an intermediate user plane function (I-UPF) network element. element, or at least one of the anchor user plane function (PDU Session anchor user plane function, PSA-UPF) network elements. In future communication systems, user plane network elements can still be UPF network elements, or they can have other names, which are not limited in this application.

(4) Data network (DN) network element: used to provide a network for transmitting data.

As shown in Figure 1c, in the 5G communication system, the data networks can be DN1 and DN2. In future communication systems, the data network may still be a DN, or may have other names, which are not limited in this application.

(5) Mobility management network element: mainly used for mobility management and access management, etc., and can be used to implement other functions besides session management in the mobility management entity (MME) function, such as, Legal interception, access authorization/authentication, mobility status management, assigning user temporary identities, authenticating and authorizing users and other functions.

As shown in Figure 1c, in the 5G communication system, the access and mobility management can be an access and mobility management function (AMF) network element. In future communication systems, access and mobility management can still be AMF network elements, or they can have other names, which are not limited in this application.

(6) Session management network element: mainly used for session management, network interconnection protocol (IP) address allocation and management of terminal equipment, selection of endpoints for manageable user plane functions, policy control and charging function interfaces, and downlink Data notification, bearer establishment, modification and release, and quality of service (QoS) control, etc.

As shown in Figure 1c, in the 5G communication system, the session management network element can be a session management function (SMF) network element, for example, it can include an intermediate session management function (I-SMF) network element. element, or at least one of the anchor session management function (A-SMF) network elements. In future communication systems, the session management network element can still be an SMF network element, or it can also have other names, which is not limited in this application.

(7) Policy control network element: A unified policy framework used to guide network behavior, providing policy rule information for control plane functional network elements (such as AMF, SMF network elements, etc.).

As shown in Figure 1c, in the 5G communication system, the policy control network element may be a policy control function (PCF) network element. In future communication systems, the policy control network element can still be a PCF network element, or it can also have other names, which is not limited in this application.

(8) Authentication service network element: used for authentication services, generating keys to implement two-way authentication of terminal devices, and supporting a unified authentication framework.

As shown in Figure 1c, in the 5G communication system, the authentication service network element may be an authentication server function (AUSF) network element. In future communication systems, the authentication service function network element can still be an AUSF network element, or it can also have other names, which is not limited in this application.

(9) Data management network element.

As shown in Figure 1c, in the 5G communication system, the data management network element can be a unified data management (UDM) network element, which can be used to process terminal device identification, access authentication, registration and mobility management wait. In future communication systems, unified data management can still be a UDM network element, or it can also have other names, which is not limited in this application.

As shown in Figure 1c, in the 5G communication system, the data management network element can also be a unified database (Unified Data Repository, UDR). Responsible for the access function of contract data, policy data, application data and other types of data. For example, PCF can obtain policy decision-related or corresponding contract information from UDR. In future communication systems, the unified database can still be UDR, or it can also have other names, which is not limited in this application.

(10) Application network element: used for data routing that affects applications, access network open function network elements, and interacts with the policy framework for policy control, etc.

As shown in Figure 1c, in the 5G communication system, the application network element may be an application function (AF) network element 107. In future communication systems, application network elements can still be AF network elements, or they can have other names, which are not limited in this application.

(11) Network storage network element: used to maintain real-time information of all network function services in the network.

In the 5G communication system, the network storage network element may be a network registration function (network repository function, NRF) network element. In future communication systems, network storage network elements can still be NRF network elements, or they can have other names, which are not limited in this application.

(12) Network slice selection network element: used to provide network slice selection function.

As shown in Figure 1c, in the 5G communication system, the network slice selection network element can be a Network Slice Selection Function (NSSF) network element. In future communication systems, the network slice selection network element can still be an NSSF. A network element may also have other names, which are not limited in this application.

(13) Network capability opening network element: used to provide network customization functions.

As shown in Figure 1c, in the 5G communication system, the network capability opening network element can be a network capability exposure function (NEF) network element. In future communication systems, the network capability opening network element can still be an NEF network element. Yuan, or it can also have other names, which are not limited in this application.

The communication system architecture applicable to the embodiments of this application may also include other network elements, such as network analysis function network elements and service communication function network elements.

Among them, the network analysis function network element is used to provide network slicing instance-level data analysis functions. For example, you can obtain data, then use the data for training and analysis, and make corresponding inferences based on the analysis results. In the 5G communication system, the network analysis function network element may be a network analytics function (NWDAF) network element.

In Figure 1c, Nnssf, Nausf, Nnef, Npcf, Nudm, Naf, Namf, Nsmf, Nnrf, N1, N2, N3, N4, and N6 are interface serial numbers. The meaning of these interface serial numbers can be found in the meaning defined in the 3GPP standard protocol, and is not limited here.

It can be understood that the above network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform). The above network elements or functions can be divided into one or more services. Furthermore, there may also be services that exist independently of network functions. In this application, instances of the above functions, or instances of services included in the above functions, or service instances that exist independently of network functions can be called service instances.

It should be noted that the embodiments of the present application are not limited to the above-mentioned system architecture, and can also be applied to other future communication systems, such as the sixth generation communication (the 6th generation, 6G) system architecture, etc. Moreover, the names of each network element used in the above embodiments of the present application may maintain the same functions in future communication systems, but the names will change.

Exemplarily, FIG. 1d illustrates a schematic diagram of a 5G network architecture based on a service-oriented architecture provided by an embodiment of the present application.

For the introduction of the functions of the network element in Figure 1d, please refer to the introduction of the functions of the corresponding network element in Figure 1c, and will not be described again. The main difference between Figure 1d and Figure 1c is that the interfaces between various network elements in Figure 1d are point-to-point interfaces, not service-oriented interfaces.

In the architecture shown in Figure 1d, the interface names and functions between each network element are as follows:

N7: The interface between PCF and SMF, used to deliver protocol data unit (PDU) session granularity and business data flow granularity control policy.

N15: The interface between PCF and AMF, used to deliver UE policies and access control related policies.

N5: The interface between AF and PCF, used for issuing application service requests and reporting network events.

N4: The interface between SMF and UPF. It is used to transfer information between the control plane and the user plane, including controlling the distribution of forwarding rules, QoS control rules, traffic statistics rules, etc. for the user plane and reporting of user plane information.

N9: The interface between two UPFs.

N11: The interface between SMF and AMF, used to transfer PDU session tunnel information between RAN and UPF, transfer control messages sent to UE, transfer radio resource control information sent to RAN, etc.

N2: The interface between AMF and RAN, used to transmit wireless bearer control information from the core network side to the RAN.

N1: The interface between AMF and UE, independent of access, used to deliver QoS control rules to UE, etc.

N8: The interface between AMF and UDM, used for AMF to obtain access and mobility management-related subscription data and authentication data from UDM, and for AMF to register UE's current mobility management-related information with UDM.

N10: The interface between SMF and UDM, used for SMF to obtain session management-related subscription data from UDM, and for SMF to register UE current session-related information with UDM.

N12: The interface between AMF and AUSF, used by AMF to initiate the authentication process to AUSF, which can carry SUCI as the signing identifier.

N14: The interface between two AMFs.

N13: The interface between UDM and AUSF, used by AUSF to obtain the user authentication vector from UDM to perform the authentication process.

N22: The interface between NSSF and AMF, used for AMF to receive slice selection information from NSSF.

The system architecture applicable to the embodiments of the present application may also include other network elements, such as management equipment. The management equipment is not shown in the above-mentioned Figures 1c and 1d. In the embodiment of this application, the management device may include a device with management capabilities for mobile relays. For example, the management device may be an operations administration and maintenance (OAM) device, which may have the functions of operation, maintenance, and management. For example, the management device may Mobile relay operations, maintenance and management. The management device in the embodiment of the present application can establish a connection with one or more network elements in the system architecture shown in Figure 1c and Figure 1d. For example, the management device can establish a connection with an NEF network element, an AMF network element, etc.

Based on the content shown in Figure 1a, Figure 1b, Figure 1c and Figure 1d as well as the above other content, the embodiment of this application provides a possible implementation:

The DU entity of the mobile relay may obtain the first TAC, and then send the first TAC to the access network device. Correspondingly, the access network device receives the first TAC. The first TAC is the TAC of the first cell of the access network device to which the MT entity of the mobile relay accesses. The TAC of the DU entity's cell is the first TAC.

There are many ways for the DU entity to obtain the first TAC. For example, the DU entity can query or receive the first TAC from the MT entity. For another example, the DU entity can also query the first TAC from the access network device.

It can be seen that since the DU entity can obtain the TAC of the cell of the access network device that the MT entity of the mobile relay accesses, the DU entity can use the TAC of the cell of the access network device that the MT entity accesses as the DU. The TAC of the entity's cell. Further, the DU entity may also send the TAC of the cell of the access network device that the MT entity accesses to the access network device, so that the access network device side can learn the TAC of the cell of the DU entity.

A further introduction will be given below with reference to the accompanying drawings.

Based on the content shown in at least one of the above-mentioned Figure 1a, Figure 1b, Figure 1c or Figure 1d and the other above-mentioned content, Figure 2 exemplarily shows a flow chart of yet another cell information configuration method provided by an embodiment of the present application. .

The mobile relay involved in the embodiment of the present application may be the mobile relay 3 in Figure 1a and Figure 1b, or the mobile relay 4 in Figure 1b. As shown in Figure 1b, the mobile relay in the embodiment of the present application The relay includes MT entities and DU entities. The mobile relay is in a mobile state, which can also be understood as the mobile relay has the ability to move, or the mobile relay has the ability to move. The ability to move. Mobile relay is used to provide relay services between terminal equipment and access network equipment. The solution on the MT entity side in the embodiment of the present application can also be executed by the unit, module or chip inside the MT entity. The solution on the DU entity side in the embodiment of the present application can also be executed by the unit, module or chip inside the DU entity.

The access network equipment involved in the embodiment of the present application is base station 1 or base station 2 in Figure 1a, or is base station 1 in Figure 1b, or is the access network equipment in Figure 1c or Figure 1d. The solution on the access network device side in the embodiment of the present application can also be executed by units, modules or chips inside the access network device.

As shown in Figure 2, the method includes:

Step 201: The DU entity sends first indication information to the management device. The first indication information is used to indicate that the management device does not need to configure TAC for the cell of the DU entity.

Correspondingly, the management device receives the first indication information.

In this embodiment of the present application, when the management device receives the first indication information, when configuring the cell configuration information for the DU entity's cell, the management device may not configure the TAC of the DU entity's cell for the DU entity's cell. This can reduce the workload of managing the device.

On the other hand, since the management device no longer configures the TAC for the cell of the DU entity, other devices (such as the DU entity) can determine the TAC of the cell of the DU entity. It can also be understood that the DU entity sends the first indication information to the management device, so that the management device does not need to configure a TAC for the DU entity's cell. This step lays the foundation for the DU entity to determine the TAC of the DU entity's cell.

On the other hand, since the management device side does not need to configure a TAC for the DU entity's cell in this embodiment, the management device side may no longer store the relationship between the DU entity and the TAC of the DU entity's cell, thereby saving storage space.

Step 201 is an optional step and may not be executed. In a possible implementation, a rule may be preset at the management device. The preset rule instructs the management device to no longer configure TAC for the cell of the DU entity when configuring cell configuration information for the DU entity of the mobile relay. In another possible implementation, the management device can also configure TAC for the cell of the DU entity of the mobile relay. In this case, after the management device delivers the configured TAC to the DU entity along with other cell configuration information, the DU entity The TAC from the management device can be ignored, that is, even if the DU entity receives the TAC of the cell of the DU entity from the management device, the DU entity does not store the TAC sent from the management device, and the DU entity uses the TAC of the cell accessed by the MT entity as the TAC of the cell of this DU entity.

It is worth noting that the information interaction between the mobile relay and the management device in the embodiment of the present application can be the information interaction between the MT entity of the mobile relay and the management device, or it can also be the information interaction between the DU entity of the mobile relay and the management device. The information exchange between them is not limited by this application. The subsequent content is similar and will not be described again.

For example, in the above step 201, the mobile relay sending the first indication information to the management device may be the MT entity of the mobile relay sending the first indication information to the management device, or the DU entity of the mobile relay sending the first indication to the management device. information. In the drawings of the embodiment of the present application, the DU entity of the mobile relay sends the first instruction information to the management device as an example for illustration, but this does not mean that in the embodiment of the present application, only the DU entity of the mobile relay can send the first instruction information to the management device. Instruction information, the MT entity in the embodiment of the present application may also send the first instruction information to the management device.

Step 202: The access network device sends a first broadcast message, where the first broadcast message includes a first TAC, and the first TAC is the TAC of the first cell of the access network device.

Correspondingly, the mobile relay MT entity receives the first TAC from the access network device. For example, the access network device may be the access network device currently accessed by the MT entity.

In the embodiment of this application, the MT entity of the mobile relay accesses the cell of the access network device. In step 202, move The relay MT entity can access the first cell of the access network device by performing steps such as cell selection.

The TAI in the embodiment of this application may include the TAC and the public land mobile network (public land mobile network, PLMN) identifier, and may also be understood to mean that the TAC is included in the TAI. For example, the first TAC may be included in the TAI of the first cell.

Step 203: The MT entity of the mobile relay sends the first message to the DU entity. The first message includes the first TAC.

Correspondingly, the DU entity of the mobile relay receives the first message from the MT entity of the mobile relay.

In a possible implementation, the first TAC may also be used to instruct the DU entity to use the first TAC as the TAC of the DU entity's cell.

It should be noted that in the existing technology, the MT entity of the mobile relay accesses the network, and the DU entity of the mobile relay provides functions and services similar to those of ordinary base stations for terminal equipment in the cell that accesses the DU entity. OAM is a mobile Cell configuration cell configuration information of the relayed DU entity. There is no relationship between the cell configuration information of the DU entity and the cell configuration information of the cell accessed by the MT entity. That is to say, in the existing technology, the DU entity of the mobile relay does not need to care about the TAC of the access network device accessed by the MT entity of the mobile relay.

Moreover, in the current existing solution, the MT entity of the mobile relay will not send the first TAC to the DU entity of the mobile relay. That is to say, after the MT entity of the mobile relay obtains the first TAC, since the first TAC will not be sent to the DU entity of the mobile relay, the DU entity of the mobile relay cannot determine that the MT entity of the mobile relay is currently connected. Enter the TAC information. That is to say, when the MT entity of the mobile relay obtains the first TAC, since the MT entity of the mobile relay does not send the first TAC to the DU entity of the mobile relay, it can be considered that the DU entity of the mobile relay cannot obtain it. First TAC.

In the embodiment of this application, in order for the DU entity of the mobile relay to obtain the TAC of the access network device accessed by the MT entity, in a possible implementation, the MT entity of the mobile relay sends the first TAC to the DU entity of the mobile relay, so that the DU entity of the mobile relay obtains the TAC of the access network device accessed by the MT entity.

Step 204: The DU entity of the mobile relay sends the first TAC to the access network device.

Correspondingly, the access network device receives the first TAC.

It is worth noting that the access network device accessed by the MT entity (such as the access network device that sends the first broadcast message to the MT entity) and the access network device used to receive the first TAC from the DU entity (such as step 204 The access network device that receives the first TAC) may be the same access network device, or may be two different access network devices. This application does not limit it. For ease of understanding, part of the content in the embodiments of this application is The two access network devices are the same access network device and are introduced as an example.

It can be seen from the solution provided in Figure 2 that when the MT entity of the mobile relay accesses the first cell, the MT entity can obtain the first TAC from the first broadcast message received from the access network device, and then the MT entity The entity may send the first TAC to the DU entity. Compared with the method in which the DU entity has to obtain the TAC of the first cell of the access network device accessed by the MT entity through other means, this method can reduce the workload of the DU entity. Moreover, since the TAC of the cell of the DU entity of the mobile relay can be the TAC of the cell of the access network device accessed by the MT entity of the mobile relay, the network side can be more accurate based on the TAC of the mobile relay accessed by the terminal device. Determine the current location of the terminal device.

Based on the content shown in at least one of the above-mentioned FIG. 1a, FIG. 1b, FIG. 1c, FIG. 1d, or FIG. 2 and the above-mentioned other content, FIG. 3a and FIG. 3b exemplarily introduce two possible cell information configuration methods. For easy understanding, FIG. 3a and FIG. 3b are exemplified based on the embodiment shown in FIG. 2 . In practical applications, in the scheme introduced in Figure 3a and Figure 3b, the mobile The DU entity of the mobile relay can also obtain the TAC of the cell accessed by the MT entity of the mobile relay through other methods.

As shown in Figure 3a, the method includes:

Step 301: The access network device sends a first broadcast message. The first broadcast message includes a first TAC, and the first TAC is the TAC of the first cell of the access network device.

Step 302: The MT entity may send the first message to the DU entity. The first message includes the first TAC.

In step 302, the first TAC in the first message is used as the TAC of the cell of the DU entity. In a possible implementation, the first TAC in the first message may also be used to instruct the DU entity to use the first TAC as the TAC of the cell of the DU entity.

Step 303: The DU entity of the mobile relay sends a third message to the access network device. The third message is used to request activation of the cell of the DU entity of the mobile relay. The third message includes the first TAC.

Step 303 can be used as a possible implementation of the above step 204.

After step 302 and before step 303, the DU entity may also determine the first TAC as the TAC of the cell of the DU entity.

In a possible implementation, the DU entity of the mobile relay can select a suitable access network device as the host base station, and then the DU entity of the mobile relay can send the third message to the CU entity of the access network device. The access network device accessed by the MT entity and the access network device used to receive the first TAC from the DU entity (such as the access network device that received the third message in step 303) may be the same access network device or Different access network equipment is not limited in this application.

The third message may also carry part or all of other information other than the first TAC in the cell configuration information supported by the mobile relay. For example, the third message may also include a DU indicating that the management device is the mobile relay. Information such as the cell identifier of the entity's cell configuration. The third message can be an F1 setup request, which can be written as F1setup request in English.

Step 304: The access network device sends a response message of the third message to the DU entity of the mobile relay.

The response message of the third message may carry the activated cell configuration information. For example, the response message of the third message may carry the cell identifier of the cell of the activated mobile relay DU entity, and the activated cell identifier of the mobile relay DU entity may include the identifier of the access network device. .

The response message of the third message can be F1 setup response, which can be written as F1setup response in English. Step 304 is an optional step and may or may not be executed.

Step 305: The mobile relay sends the third broadcast message.

In this embodiment of the present application, the mobile relay may send a broadcast message, such as the third broadcast message in step 406. The broadcast message sent by the mobile relay is used to send cell information corresponding to the cell of the mobile relay to the terminal device. The terminal device that receives the broadcast message can choose to access the cell and access the network through the mobile relay.

It is worth mentioning that in the embodiment of the present application, the mobile relay may send a broadcast message by the MT entity of the mobile relay, or the DU entity of the mobile relay may send a broadcast message. There is no limitation in the embodiment of the present application. Subsequent It will not be repeated in the content. The drawings in the embodiments of this application take the example that the broadcast message sent by the mobile relay is sent by the DU entity of the mobile relay. This does not mean that the broadcast message sent by the mobile relay in the embodiment of this application can only be sent by the DU entity. Sent by the entity or by the MT entity. For example, in step 305, the DU entity of the mobile relay sends the third broadcast message or the MT entity of the mobile relay sends the third broadcast message.

The third broadcast message may include the first TAC and/or the cell identity of the DU entity of the mobile relay. When the third broadcast message includes the first TAC, since the mobile relay can perform cell broadcast within the service range of the mobile relay, the terminal device located within the service range of the mobile relay can make the broadcast message received The mobile relay is accessed, and the accessed terminal device can determine that the TAC of the mobile relay is the first TAC according to the third broadcast message. Figure 3a shows an example of a terminal device receiving the third broadcast message.

It can be seen from the implementation shown in Figure 3a that the DU entity of the mobile relay can carry the TAC of the cell of the access network device accessed by the MT entity of the mobile relay in the message requesting activation of the cell of the DU entity. In this way, There is no need for the access network device to obtain the TAC of the cell of the access network device that the MT entity of the mobile relay accesses through other means. The access network device can directly determine the TAC of the cell of the access network device that the received MT entity accesses. is the TAC of the DU entity cell, thereby avoiding the signaling consumption caused by the access network device querying the TAC of the cell of the access network device accessed by the mobile relay MT entity through other means. On the other hand, since the TAC of the cell of the access network device that the MT entity of the mobile relay accesses is the cell TAC of the DU entity of the mobile relay, when the mobile relay initially activates the cell, the TAC of the cell can be configured as The TAC of the cell of the access network device that the MT entity of the mobile relay accesses enables the network side to determine the actual location of the terminal device that accesses the mobile relay, improving the efficiency and efficiency of the network's mobility management of the terminal device. Accuracy.

The embodiment shown in Figure 3b is introduced below. Please refer to Figure 3b. As shown in Figure 3b, the method includes:

Step 401: The MT entity of the mobile relay determines that the mobile relay has moved.

In the embodiment of the present application, when the mobile relay moves, it can be understood that both the MT entity of the mobile relay and the DU entity of the mobile relay move. The method for the mobile relay to determine that the mobile relay has moved may be that the MT entity of the mobile relay determines that the MT entity has moved, or the MT entity of the mobile relay determines that the mobile relay has moved.

In a possible implementation, in step 401, when the MT entity of the mobile relay determines that the movement of the mobile relay satisfies the preset movement range, the MT entity of the mobile relay determines that the mobile relay has moved.

In this embodiment of the present application, the preset movement range may include at least one of the following content 1, content 2, content 3, content 4 or content 5.

Content 1: The TAC of the cell accessed by the MT entity of the mobile relay changes.

Content 2: The cell identity of the cell accessed by the MT entity of the mobile relay changes.

Content 3: The access network equipment accessed by the MT entity of the mobile relay changes.

Content 4: The geographical area information of the mobile relay changes.

Content 5: The moving distance of the mobile relay is greater than the preset distance.

The following is introduced respectively through case 1, case 2, case 3, case 4 and case 5.

It is worth noting that the following situations 1 to 5 are respectively introduced when the preset movement range includes one of the above content 1, content 2, content 3, content 4 and content 5. When the preset movement range includes multiple items (such as two items) in the above content 1, content 2, content 3, content 4 and content 5: the MT entity of the mobile relay can determine that the movement of the mobile relay satisfies the preset It is determined that the movement of the mobile relay satisfies the preset movement range when at least one of the multiple items within the movement range is determined; alternatively, the MT entity of the mobile relay may determine that the movement of the mobile relay satisfies multiple items within the preset movement range. When each item is selected, the mobile relay movement is determined to meet the preset movement range. The method is more flexible and can be flexibly set according to the actual situation.

Case 1: The preset mobility range includes: the TAC of the cell accessed by the MT entity of the mobile relay changes.

The TAC of the cell accessed by the mobile relay changes, which may mean that the cell accessed by the MT entity of the mobile relay changes. The TAC of the zone changes. For example, the MT entity of the mobile relay receives the second broadcast message, and the second broadcast message includes the second TAC. The second TAC is the TAC of the second cell. The MT entity may store a second TAC. Since the mobile relay has moved, after the MT entity of the mobile relay receives the second broadcast message, the MT entity of the mobile relay may also receive the first broadcast message, and the first broadcast message includes the first TAC. The first TAC is the TAC of the first cell. When the first TAC and the second TAC are different, the MT entity of the mobile relay determines that the mobile relay has moved, or that the mobile relay has moved within a preset movement range, or that the movement of the mobile relay satisfies the preset movement range. Set the movement range.

Case 2: The preset mobility range includes: the cell identity of the cell accessed by the MT entity of the mobile relay changes.

The cell identity of the cell accessed by the mobile relay changes, which may mean that the cell identity of the cell accessed by the MT entity of the mobile relay changes. For example, the MT entity of the mobile relay receives the second broadcast message, and the second broadcast message includes cell identification #1. Cell ID #1 is the cell ID of the second cell. Since the mobile relay has moved, after the MT entity of the mobile relay receives the second broadcast message, the MT entity of the mobile relay may also receive the first broadcast message, where the first broadcast message includes cell identification #2. Cell ID #2 is the cell ID of the first cell. When the cell identifier #2 is different from the cell identifier #1, the MT entity of the mobile relay determines that the mobile relay has moved, or that the mobile relay has moved within the preset movement range, or that the mobile relay has moved. Meet the preset movement range.

Case 3: The preset mobility range includes: the access network equipment accessed by the MT entity of the mobile relay changes.

The access network equipment connected to the mobile relay changes, which may mean that the access network equipment connected to the MT entity of the mobile relay changes. For example, the MT entity of the mobile relay receives the second broadcast message, and the second broadcast message includes the identification #1 of the access network device. Since the mobile relay has moved, after the MT entity of the mobile relay receives the second broadcast message, the MT entity of the mobile relay may also receive the first broadcast message. The first broadcast message includes the identification of the access network device# 2. When the identifier #2 of the access network device is different from the identifier #1 of the access network device, the MT entity of the mobile relay determines that the mobile relay has moved, or that the mobile relay has moved within the preset movement range. , or it is said that the movement of the mobile relay satisfies the preset movement range.

Case 4: The preset movement range includes: the geographical area information of the mobile relay changes.

The information on the geographical area of the mobile relay changes, which may mean that the information on the geographical area where the MT entity of the mobile relay is located changes. For example, when the mobile relay is located at the location corresponding to geographical area information #1, the MT entity of the mobile relay initiates a positioning process and obtains the current geographical location of the mobile relay from the core network as geographical area information #1. Since the mobile relay has moved, when the MT entity of the mobile relay initiates the positioning process again, the current geographical location of the mobile relay obtained from the core network may be geographical area information #2. When the geographical area information #2 is different from the geographical area information #1, the MT entity of the mobile relay determines that the mobile relay has moved, or that the mobile relay has moved within the preset movement range, or that the mobile relay has moved. The movement meets the preset movement range.

Case 5, the preset movement range includes: the movement distance of the mobile relay is greater than the preset distance.

The moving distance of the mobile relay is greater than the preset distance, which may mean that the moving distance of the MT entity of the mobile relay is greater than the preset distance. The preset distance may be an experience value, and the preset distance may be related to the preset movement range. For example, when the moving distance of the mobile relay is greater than the preset distance, the mobile relay is likely to have moved out of the currently accessed access network device (or the cell of the currently accessed access network device, or the current corresponding TAC, or the geographic area to which it currently belongs).

For example, the preset distance can be set to 1000 meters. The MT entity of the mobile relay can query and find out that the moving distance of the mobile relay is greater than the preset distance by triggering the positioning process, or the MT entity of the mobile relay can infer that the moving distance of the mobile relay is greater than the preset distance (such as inference based on historical data). ), or the detection device on other equipment detects that the moving distance of the mobile relay is greater than the preset distance and notifies the MT entity of the mobile relay, or it is inferred by other equipment The moving distance out of the mobile relay is greater than the preset distance and the MT entity of the mobile relay is notified. When the MT entity of the mobile relay determines that the moving distance of the mobile relay is greater than the preset distance, it determines that the mobile relay has moved, or that the mobile relay has moved within the preset movement range, or that the mobile relay has moved The movement satisfies the preset movement range.

In another possible implementation, when the MT entity of the mobile relay determines that the movement of the mobile relay does not meet the preset movement range, the MT entity of the mobile relay may not send the access of the MT entity to the DU entity. TAC of the cell where the network device is located. Alternatively, the MT entity of the mobile relay may attribute such a situation to a situation where the mobile relay determines that the mobile relay has not moved, or that the mobile relay has not moved within a preset movement range.

In a possible implementation, when the preset movement range includes one of the above content 1, content 2, content 3, content 4 and content 5: when the MT entity of the mobile relay determines that the mobile relay If the movement does not meet the content in the preset movement range, the MT entity of the mobile relay determines that the movement of the mobile relay does not meet the preset movement range.

For example, the preset mobility range includes: the TAC of the cell accessed by the mobile relay changes. In this case, when the MT entity of the mobile relay determines that the TAC of the accessed cell has not changed, it is possible that the movement amount of the mobile relay is small. In this case, the MT entity of the mobile relay determines that the TAC of the mobile relay has not changed. If the mobility does not meet the preset mobility range, the MT entity of the mobile relay can be allowed not to send the TAC of the cell of the access network device that the MT entity accesses to the DU entity. In this way, the MT entity of the mobile relay can be prevented from frequently sending the TAC to the DU entity. The TAC of the cell of the access network device accessed by the relay MT entity reduces signaling consumption.

In yet another possible implementation, when the preset movement range includes multiple contents in the above content 1, content 2, content 3, content 4 and content 5: when the MT entity of the mobile relay determines that the mobile relay If the movement of the mobile relay does not satisfy each item in the preset movement range, the MT entity of the mobile relay determines that the movement of the mobile relay does not meet the preset movement range. In other words, as long as any item in the preset movement range is met, the mobile relay can determine that its movement satisfies the preset movement range.

For example, the preset mobility range includes: the TAC of the cell that the MT entity of the mobile relay accesses changes, and the access network equipment that the MT entity of the mobile relay accesses changes. In this case, when the MT entity of the mobile relay determines that the TAC of the accessed cell has not changed, and the access network equipment accessed by the MT entity of the mobile relay has not changed, the MT entity of the mobile relay determines that the mobile relay MT entity If the movement of the relay does not meet the preset movement range, the MT entity of the mobile relay may be allowed not to send the TAC of the cell of the access network device accessed by the MT entity to the DU entity. For another example, when the MT entity of the mobile relay determines that the TAC of the accessed cell has changed, but the access network equipment accessed by the MT entity of the mobile relay has not changed, the MT entity of the mobile relay can also be allowed to send a request to the DU. The entity sends the TAC of the cell of the access network device accessed by the MT entity. This situation can be attributed to the mobility of the mobile relay and satisfies the preset mobility range.

In yet another possible implementation, when the preset movement range includes multiple contents in the above content 1, content 2, content 3, content 4 and content 5: when the MT entity of the mobile relay determines that the mobile relay If the movement of the mobile relay does not meet at least one of the preset movement ranges, the MT entity of the mobile relay determines that the movement of the mobile relay does not meet the preset movement range. The MT entity of the mobile relay may not report the MT entity access to the DU entity. The TAC of the cell where the access network equipment enters. In this case, the MT entity of the mobile relay may determine that the movement of the mobile relay satisfies the preset movement range when determining that the movement of the mobile relay satisfies each of the multiple items within the preset movement range.

For example, the preset mobility range includes: the TAC of the cell that the MT entity of the mobile relay accesses changes, and the access network equipment that the MT entity of the mobile relay accesses changes. In this case, when the MT entity of the mobile relay determines that the TAC of the accessed cell has changed, but the access network equipment accessed by the MT entity of the mobile relay has not changed, the MT entity of the mobile relay may be allowed not to change. Send to the DU entity the cell of the access network device that the MT entity accesses. TAC. For another example, when the MT entity of the mobile relay determines that the TAC of the cell accessed by the MT entity of the mobile relay has changed, and the access network equipment accessed by the MT entity of the mobile relay has changed, the MT of the mobile relay is allowed to The entity sends the TAC of the cell of the access network device accessed by the MT entity to the DU entity.

Step 402: The MT entity of the mobile relay sends a first message to the DU entity of the mobile relay. The first message includes the first TAC.

In step 402, the first TAC in the first message may be used to instruct the DU entity to use the first TAC as the TAC of the cell of the DU entity.

Since the MT entity of the mobile relay determines that the mobile relay has moved in step 401, the first message carries the TAC of the cell of the access network device accessed by the moved MT entity of the mobile relay.

Step 402 may be a possible implementation of the above step 203.

In the embodiment of the present application, when the mobile relay moves within the coverage area of the same access network device, for example, in the above step 401, the MT entity of the mobile relay determines that the mobile relay moves from the second cell of the access network device to The first district. For the sake of distinction, the TAC of the second cell is called the second TAC in the embodiment of this application. When the MT entity of the mobile relay accesses the second cell, the TAC of the cell of the DU entity may be the second TAC, and the DU entity of the mobile relay may have reported the DU entity's TAC to the access network device. The TAC of the cell is the second TAC of the second cell. Therefore, after the MT entity of the mobile relay moves from the second cell of the access network device to the first cell, the DU entity of the mobile relay can instruct the access network device to The TAC of the cell of the DU entity is updated from the second TAC to the first TAC. For example, the following step 403 can be performed.

Step 403: The DU entity of the mobile relay sends a configuration update message to the access network device. The configuration update message is used to update the TAC of the cell of the DU entity of the mobile relay to the first TAC.

Correspondingly, the access network device receives the configuration update message from the DU entity of the mobile relay.

In the embodiment of this application, the English configuration update message may be gNB-DU configuration update, and there is no limit if it is not applied.

The access network device side should store the TAC of the cell of the DU entity of the mobile relay corresponding to the position before the mobile relay moves, and the TAC of the cell of the DU entity of the mobile relay corresponding to the position before the mobile relay moves. Different from the first TAC. After receiving the configuration update message, the access network device updates the TAC of the cell of the DU entity of the mobile relay to the first TAC.

For example, the mobile relay is initially located at location 1, which is within the coverage of the second cell of the access network device, and the mobile relay accesses the second cell at location 1. The DU entity of the mobile relay The TAC of the cell is the TAC corresponding to position 1, and the TAC of the cell of the DU entity of the mobile relay stored on the access network device side is the TAC associated with position 1. After that, the mobile relay moved to location 2. Location 2 is located within the coverage of the first cell of the access network device. The mobile relay reported the first TAC to the access network device so that the access network device Update the mobile relay's TAC associated with location 1 to the first TAC associated with location 2.

In another possible implementation, after step 403, the access network device sends a response message to the configuration update message to the mobile relay. The response message of the configuration update message may indicate that the cell configuration information update of the DU entity of the mobile relay is completed.

In the embodiment of this application, the response message of the configuration update may be gNB-DU configuration update acknowledge, There are no restrictions if you don’t apply.

After step 403, the mobile relay may perform step 404.

Step 404: The mobile relay sends the third broadcast message.

In this embodiment of the present application, the third broadcast message may include the identity of the cell of the first TAC and/or the DU entity of the mobile relay. For the content of step 404, please refer to the relevant content of step 305, which will not be described again.

It can be seen from Figure 3b that when the MT entity of the mobile relay determines that the mobile relay has moved within the preset movement range, the MT entity of the mobile relay can send the MT entity of the mobile relay to the DU entity of the mobile relay. The TAC of the cell of the access network device currently accessed, so that the DU entity of the mobile relay determines the TAC of the cell of the access network device accessed by the MT entity after the mobile relay moves as the cell of the DU entity of the mobile relay TAC, which can achieve the effect of keeping the TAC of the DU entity of the mobile relay updated as it moves.

On the other hand, when the mobile relay moves but the host base station remains unchanged, the DU entity of the mobile relay can request the access network device to update the TAC of the cell of the DU entity of the mobile relay, thereby maintaining the host base station. The accuracy of the cell configuration information of the DU entity of the mobile base station stored on the mobile base station.

It is worth noting that since the mobile relay in the embodiment of the present application has mobility capabilities, when the mobile relay moves from one access network device to another access network device, the new access network device accessed after the move The solution implemented in can also refer to the solution shown in Figure 3a above, and will not be described again. The contents shown in Figure 3a and Figure 3b above can also be used in combination. For example, in the solution shown in Figure 3a above, step 401 can also be included before step 302.

Based on the content shown in at least one of the above-mentioned FIG. 1a, FIG. 1b, FIG. 1c, FIG. 1d, or FIG. 2 and the above-mentioned other content, FIG. 4a exemplarily shows a flow chart of yet another possible cell information configuration method.

As shown in Figure 4a, the method includes:

Step 501: The MT entity of the mobile relay receives the broadcast message a1 from access network device one.

The broadcast message a1 includes at least one of the TAC of cell 1 of access network device one, the identity of cell 1, or the identity of access network device one. The TAC of cell 1 is, for example, TAC#2.

The broadcast message a1 may also include indication information that the cell corresponding to the broadcast message a1 supports mobile relay.

Step 502: The MT entity of the mobile relay performs cell selection and selects cell 1 for access.

In a possible implementation, the MT entity of the mobile relay can select a cell that supports the DU entity of the mobile relay for access based on the indication information carried in the broadcast message of whether to support mobile relay, such as the MT entity of the mobile relay. Select cell 1 for access.

Step 503: The MT entity of the mobile relay establishes an RRC connection with the access network device.

In step 503, the MT entity of the mobile relay may send an RRC connection establishment request message to the access network device. The RRC connection establishment request message may carry indication information indicating that the RRC connection is initiated by the mobile relay. The RRC connection establishment request message may include an RRC connection setup request.

Further, the access network device may send an RRC establishment completion message to the MT entity of the mobile relay. The RRC establishment completion message is used to indicate that the RRC connection is successfully established.

Step 504: The MT entity of the mobile relay sends a registration request message to the core network device.

Correspondingly, the core network device receives the registration request message.

Core network equipment may include AMF. The registration request message may carry indication information indicating that the registered network is a mobile relay, and then the core network device verifies the identity of the mobile relay. The registration request message may include N2message.

Step 505: The MT entity of the mobile relay is successfully registered.

In the embodiment of this application, the process of registering the MT entity of the access network device with the network is similar to the process of registering the terminal device with the network device, and will not be elaborated here.

Step 506: The MT entity of the mobile relay initiates session establishment. The network allocates an IP address to the MT entity of the mobile relay. The mobile relay can use the IP address to interact with the management device.

Step 507: The mobile relay sends message a2 to the management device. Message a2 is used to obtain cell configuration information.

Correspondingly, the management device receives message a2 from the mobile relay.

Message a2 includes first indication information, and the first indication information is used to indicate that the management device does not need to configure TAC for the cell of the DU entity.

For the relevant content of step 507, please refer to the relevant description of step 201, and will not be described again here.

Step 508: The management device may send a response message to message a2 to the mobile relay, where the response message to message a2 carries cell configuration information. The response message for message a2 does not include TAC.

Correspondingly, the mobile relay may receive cell configuration information from the management device.

In this embodiment of the present application, in step 507, the message a2 sent by the mobile relay to the management device may be the message a2 sent by the MT entity of the mobile relay to the management device. In the above step 508, the management device may send a response message of message a2 to the mobile relay. The management device may send a response message of message a2 to the MT entity of the mobile relay. For another example, in the above step 507, the mobile relay sending message a2 to the management device may be the DU entity of the mobile relay sending message a2 to the management device. In the above step 508, the management device may send a response message of message a2 to the mobile relay. The management device may send a response message of message a2 to the DU entity of the mobile relay. In the drawings of the embodiment of this application, the DU entity of the mobile relay sends message a2 to the management device, and the management device sends a response message of message a2 to the DU entity of the mobile relay as an example. For relevant content, please refer to the above description and will not be repeated again.

Step 509: The MT entity of the mobile relay sends message a3 to the DU entity of the mobile relay. Message a3 includes TAC#2.

Correspondingly, the DU entity of the mobile relay receives message a3.

Step 509 can be after step 508 or before step 508. For example, it can be after step 502 or at any time before step 510. It can also be understood that the MT entity sends message a3 to the DU entity after accessing cell 1. .

For the relevant content of step 509, please refer to the relevant description of the aforementioned step 302. For the relevant content of the message a3, please refer to the relevant introduction of the aforementioned first message (for example, the message a3 can be the aforementioned first message), which will not be described again here.

Step 510: The DU entity of the mobile relay determines TAC#2 as the TAC of the DU entity's cell.

Step 511: The DU entity of the mobile relay sends message a4 to the access network device. The message a4 is used to request activation of the cell of the DU entity of the mobile relay. Message a4 can carry TAC#2. The access network device may be access network device 1 to which the MT entity of the mobile relay accesses.

For the relevant content of step 511, please refer to the relevant description of the aforementioned step 303. For the relevant content of the message a4, please refer to the relevant introduction of the aforementioned third message (for example, the message a4 can be the aforementioned third message), which will not be described again here.

Step 512: The access network device sends a response message of message a4 to the DU entity of the mobile relay.

For the relevant content of step 512, please refer to the relevant description of step 304, which will not be described again.

Step 513: The mobile relay sends broadcast message a5.

In a possible implementation, the broadcast message a5 includes TAC#2. For the relevant content of step 513, please refer to the relevant description of step 305, which will not be described again.

Step 514: The MT entity of the mobile relay receives the broadcast message a6, where the access network equipment included in the broadcast message a6 At least one of the TAC of cell 2 of device 1, the identity of cell 2, or the identity of access network device 1. The TAC of cell 2 is, for example, TAC#3.

The mobile relay may be in a moving state. When the mobile relay moves from cell 1 to cell 2, the mobile relay may receive the broadcast message a6. Then the mobile relay needs to perform cell selection again. For example, cell 2 can be selected as a new cell, and the mobile relay can access cell 2.

Step 515: The MT entity of the mobile relay determines that the mobile relay has moved.

In step 515, the MT entity of the mobile relay may determine that the mobile relay has moved based on at least one of the above content 1, content 2, content 3, content 4 or content 5.

The MT entity in the mobile relay responds to the above content 1 (the TAC of the cell accessed by the mobile relay MT entity changes), content 2 (the cell identity of the cell accessed by the mobile relay MT entity changes) or If at least one of the contents 3 (the access network equipment accessed by the MT entity of the mobile relay changes) determines that the MT entity of the mobile relay has moved, the mobile relay may use the broadcast received in step 514. The information carried in message a6 determines that the mobile relay has moved. In this case, step 515 needs to be executed after step 514.

The MT entity in the mobile relay determines according to at least one of the above content 4 (the information of the geographical area of the MT entity in the mobile relay changes) or content 5 (the moving distance of the MT entity in the mobile relay is greater than the preset distance). When the mobile relay moves, there is no sequence relationship between step 515 and step 514. For example, step 515 may be performed first and then step 514, which is not limited in the embodiment of this application.

For the relevant content of step 515, please refer to the relevant description of step 401, which will not be described again.

Step 516: The MT entity of the mobile relay sends message a7 to the DU entity of the mobile relay. The message a7 includes the TAC of the cell of the access network device accessed by the MT entity of the mobile relay: TAC#3.

For the relevant content of step 516, please refer to the relevant description of step 402, which will not be described again.

Step 517: The DU entity of the mobile relay determines TAC#3 as the TAC of the DU entity's cell.

Step 518: The DU entity of the mobile relay sends a configuration update message to the access network device 1. The configuration update message is used to update the TAC of the cell of the DU entity of the mobile relay from TAC#2 to TAC#3.

For the relevant content of step 518, please refer to the relevant description of step 403, which will not be described again.

Step 519: The mobile relay sends broadcast message a8.

In a possible implementation, the broadcast message a8 may include TAC#3. For the content of step 519, please refer to the relevant content of the aforementioned step 404, and will not be described again.

It can be seen from the embodiment shown in Figure 4a that the mobile relay accesses cell 1 of access network device 1, and the DU entity of the mobile relay determines that the TAC of the cell of the DU entity is the TAC of cell 1. When the mobile relay moves and accesses cell 2 of access network device 1, the MT entity of the mobile relay sends the TAC of cell 2 to the DU entity of the mobile relay, and the DU entity of the mobile relay determines the cell of the DU entity. The TAC is the TAC of cell 2. If the mobile relay subsequently moves again and moves to a cell different from cell 2 of access network device 1, the MT entity of the mobile relay can again send the TAC of the cell accessed by the MT entity to the DU entity so that the DU entity The entity updates the TAC of the cell of the DU entity. This solution is similar to the solution provided in steps 514 to 519 and will not be described again. Through this solution, during the movement of the mobile relay, the TAC of the cell of the DU entity of the mobile relay can be dynamically updated, so that the network side can more accurately determine the terminal based on the TAC of the mobile relay accessed by the terminal device. The current location of the device.

Please refer to Figure 4b below. As shown in Figure 4b, the method includes:

Step 601: The MT entity of the mobile relay receives the broadcast message a1 from access network device one.

Step 602: The MT entity of the mobile relay performs cell selection and selects cell 1 for access.

Step 603: The MT entity of the mobile relay establishes an RRC connection with the access network device.

Step 604: The MT entity of the mobile relay sends a registration request message to the core network device.

Step 605: The MT entity of the mobile relay is successfully registered.

Step 606: The MT entity of the mobile relay initiates session establishment. The network allocates an IP address to the MT entity of the mobile relay. The mobile relay can use the IP address to interact with the management device.

Step 607: The mobile relay sends message a2 to the management device.

Step 608: The management device may send a response message of message a2 to the mobile relay.

Step 609: The MT entity of the mobile relay sends message a3 to the DU entity of the mobile relay.

Step 610: The DU entity of the mobile relay determines TAC#2 as the TAC of the DU entity's cell.

Step 611: The DU entity of the mobile relay sends message a4 to the access network device.

Step 612: The access network device sends a response message of message a4 to the DU entity of the mobile relay.

Step 613: The mobile relay sends broadcast message a5.

For steps 601 to 613, please refer to the aforementioned steps 501 to 513, and will not be described again.

Since the mobile relay has the mobility capability, the mobile relay may be in a mobile state, for example, it may move to the coverage area of the cell of the access network device 2. After the mobile relay moves from the coverage area of access network device one to the coverage area of the cell of access network device two, it may perform the following:

Step 614: The MT entity of the mobile relay receives the broadcast message a9.

The broadcast message a9 includes at least one of the TAC of cell 3 of access network device 2, the identity of cell 3, or the identity of access network device 2. The TAC of cell 3 is, for example, TAC#4.

The mobile relay may be in a moving state. When the mobile relay moves from cell 1 of access network device 1 to cell 3 of access network device 2, the mobile relay may receive broadcast message a9. Then the mobile relay needs to perform cell selection again. For example, cell 3 can be selected as a new cell, and the mobile relay can access cell 3.

It is worth noting that when the MT entity of the mobile relay switches from access network device 1 to access network device 2, the MT entity of the mobile relay may be in the RRC connected state. The MT entity of the mobile relay in the RRC connected state switches from the cell of the access network device one to the cell of the access network device two, and establishes an RRC connection with the access network device two. This step is not shown in Figure 4b.

Step 615: The MT entity of the mobile relay determines that the mobile relay has moved.

For the relevant content of step 615, please refer to the relevant description of step 515, which will not be described again.

Step 616: The MT entity of the mobile relay sends message a10 to the DU entity of the mobile relay. The message a10 includes the TAC of the cell of the access network device accessed by the MT entity of the mobile relay: TAC#4.

For the relevant content of step 616, please refer to the relevant description of step 302, which will not be described again.

Step 617: The DU entity of the mobile relay determines TAC#4 as the TAC of the DU entity's cell.

Step 618: The DU entity of the mobile relay sends message a11 to the access network device 2 currently accessed by the MT entity of the mobile relay. The message a11 is used to request activation of the cell of the DU entity of the mobile relay. Message a11 may include TAC#4.

For the content of step 618, please refer to the relevant content of the aforementioned step 303, and will not be described again.

Step 619: Access network device two sends a response message of message a11 to the DU entity of the mobile relay.

For the content of step 619, please refer to the relevant content of step 304, and will not be described again.

Step 620: The mobile relay sends broadcast message a12.

In a possible implementation, the broadcast message a12 includes TAC#4.

For the content of step 620, please refer to the relevant content of step 305, and will not be described again.

It can be seen from the embodiment shown in Figure 4b that the MT entity of the mobile relay accesses cell 1 of access network device 1, and the DU entity of the mobile relay determines that the TAC of the cell of the DU entity is the TAC of cell 1. When the mobile relay moves and accesses cell 3 of access network device 2, the MT entity of the mobile relay sends the TAC of cell 3 to the DU entity of the mobile relay, and the DU entity of the mobile relay determines the cell of the DU entity. The TAC is the TAC of cell 3. If the mobile relay subsequently moves again, if it moves to an access network device different from the second access network device, the relevant solution is similar to the solution provided in steps 614 to 620 and will not be described again. If the mobile relay subsequently moves again and moves to another cell of the access network device 2, the relevant solutions are similar to those provided in steps 514 to 519 and will not be described again. Through this solution, during the movement of the mobile relay, the TAC of the cell of the DU entity of the mobile relay will also be dynamically updated, so that the network side can more accurately determine the cell based on the TAC of the mobile relay accessed by the terminal device. The current location of the terminal device.

Based on the content shown in Figure 1a, Figure 1b, Figure 1c and Figure 1d as well as the above other content, the embodiment of the present application provides another possible implementation:

The access network device may obtain the first TAC, and then the access network device sends the first TAC to the DU entity of the mobile relay. Correspondingly, the DU entity of the mobile relay receives the first TAC. The first TAC is the TAC of the first cell of the access network device to which the MT entity of the mobile relay accesses. The TAC of the DU entity's cell is the first TAC.

There are many ways for the access network device to obtain the first TAC. For example, the access network device can query the TAC of the cell of the access network device that the MT entity of the mobile relay accesses (for example, the access network device obtains the first TAC according to the MT The entity's identity is used to query the TAC of the cell of the access network device that the MT entity accesses).

It can be seen that since the access network device can obtain the TAC of the cell of the access network device that the MT entity of the mobile relay accesses, then the access network device can obtain the TAC of the access network device that the MT entity of the mobile relay accesses. The TAC of the cell is set to the TAC of the cell of the DU entity, so that the network side can more accurately determine the current location of the terminal device based on the TAC of the mobile relay accessed by the terminal device.

Based on the embodiment shown in at least one of Figure 1a, Figure 1b, Figure 1c or Figure 1d and the other contents mentioned above, Figure 5 exemplarily shows another cell information configuration method provided by the embodiment of the present application. Process diagram. As shown in Figure 5, the method includes:

Step 701: The mobile relay sends first instruction information to the management device.

Since the management device no longer configures the TAC for the cell of the DU entity, other devices (such as the access network device) can determine the TAC of the cell of the DU entity. It can also be understood that the DU entity sends the first indication information to the management device, so that the management device does not need to configure a TAC for the DU entity's cell. This step lays the foundation for the access network device to determine the TAC of the DU entity's cell.

Step 701 is an optional step. For the relevant content of step 701, please refer to the relevant content of the aforementioned step 201, and will not be described again.

Step 702: The DU entity of the mobile relay sends the identifier of the MT entity to the access network device.

Correspondingly, the access network device can receive the identity of the MT entity.

When the DU entity of the mobile relay interacts with the access network device, the mobile relay can send the identifier of the MT entity to the access network device, so that the access network device can query the access of the MT entity based on the identifier of the MT entity. community TAC.

In the embodiment of this application, the identity of the MT entity can be understood as the identity of the MT function of the mobile relay that has successfully accessed the network. The identity of the MT entity can be a Generic Public Subscription Identifier (GPSI) or a permanent user identity (Subscription). Permanent Identifier (SUPI), Mobile Subscriber International Integrated Services Digital Network Identifier (mobile subscriber international ISDN/PSTN number, MSISDN), etc. Among them, ISDN is the abbreviation of integrated service digital network (ISDN). PSTN is the abbreviation of public switched telephone network (PSTN).

Step 702 is an optional step.

Step 703: The DU entity of the mobile relay sends second indication information to the access network device. The second indication information instructs the access network device to configure TAC for the cell of the DU entity.

Correspondingly, the access network device may receive the second indication information.

In a possible implementation, after the access network device receives the second indication information, the TAC may be configured for the DU entity. For example, when the access network device does not receive the second indication information from the DU entity of the mobile relay, the TAC may not be configured for the cell of the DU entity, so that the access network device can configure the TAC when necessary. The DU entity's cell is configured with TAC, which can reduce the workload of the access network equipment.

It is worth noting that in this embodiment of the present application, step 702 and step 703 may be one step. For example, the DU entity of the mobile relay may carry the identity of the MT entity and the second indication information in one message. Step 703 is an optional step.

Step 704: The access network device obtains the first TAC, which is the TAC of the first cell of the access network device to which the MT entity of the mobile relay accesses.

Since the MT entity of the mobile relay accesses the first cell of the access network device, the access network device side stores the identity of the MT entity of the mobile relay and the first cell of the MT entity that accesses the access network device. The corresponding relationship between the TACs of the cells, and then the access network device can query the TAC of the first cell of the access network device that the MT entity accesses from the corresponding relationship.

For example, since the MT entity of the mobile relay accesses the first cell of the access network device, the context of the MT entity of the mobile relay stored by the access network device includes an indication of the MT of the mobile relay. The TAC of the first cell where the entity accesses the access network device. The access network device can query the context of the MT entity according to the identity of the MT entity to find out the TAC of the MT entity of the mobile relay accessing the access network device. TAC of the first cell.

It is worth noting that there are many ways for the access network device to obtain the first TAC. For example, the access network device side stores the indication information for indicating the DU entity and the third TAC accessed by the MT entity including the mobile relay of the DU entity. The corresponding relationship between the TAC of a cell. In this case, the access network device can query the corresponding relationship based on the instruction information for the DU entity when determining that the DAC needs to be configured for the cell of the DU entity of the mobile relay. The TAC of the first cell accessed by the MT entity including the mobile relay of the DU entity. The indication information for the DU entity may be information that can indicate the DU entity, such as an identifier of the DU entity. In this implementation manner, the MT entity of the mobile relay does not need to send the identity of the MT entity to the access network device.

Step 705: The access network device sends the first TAC to the DU entity of the mobile relay, where the first TAC is used as the TAC of the cell serving as the DU entity.

Correspondingly, the DU entity of the mobile relay receives the first TAC.

In a possible implementation, before step 705, it may also include: the access network device determines that the first TAC is the TAC of the cell of the DU entity. For example, the access network device can store the TAC of the cell of the DU entity as the first TAC. This situation.

Based on the embodiments shown in at least one of Figure 1a, Figure 1b, Figure 1c, Figure 1d or Figure 5 and the other contents mentioned above, Figures 6a and 6b exemplarily illustrate the processes of two cell information configuration methods. Schematic diagram.

As shown in Figure 6a, the method includes:

Step 801: The MT entity of the mobile relay accesses the first cell of the access network device.

Step 802: The DU entity of the mobile relay sends a second message to the access network device currently accessed by the MT entity of the mobile relay. The second message is used to request activation of the cell of the DU entity of the mobile relay.

In a possible implementation, the second message does not include TAC.

In another possible implementation, the second message may include the above-mentioned MT entity identification and/or second indication information. For relevant content, please refer to the relevant content of step 702 and step 703, which will not be described again here.

Step 803: The access network device obtains the TAC of the first cell accessed by the MT entity of the mobile relay: the first TAC.

In step 803, the access network device may determine the obtained first TAC as the TAC of the cell of the DU entity of the mobile relay.

The second message may carry part or all of other information other than the first TAC in the cell configuration information supported by the mobile relay. For example, the second message may also include a DU entity whose management device is the mobile relay. The cell identifier and other information configured in the cell. The second message can be an F1 setup request, which can be written as F1setup request in English.

Step 804: The access network device sends a response message of the second message to the DU entity of the mobile relay.

The response message of the second message may carry the activated cell configuration information. For example, the response message of the second message may carry the TAC of the cell of the activated mobile relay DU entity: the first TAC. In a possible implementation, the response message of the second message may also include the cell identity of the cell of the DU entity of the mobile relay after activation, and the cell identity of the cell of the activated DU entity of the mobile relay may include the The identification of the access network device.

The response message of the third message can be F1 setup response, which can be written as F1setup response in English.

Step 805: The mobile relay sends the third broadcast message.

The third broadcast message may include the first TAC and/or the cell identity of the DU entity of the mobile relay. When the third broadcast message includes the first TAC, since the mobile relay can perform cell broadcast within the service range of the mobile relay, the terminal device located within the service range of the mobile relay can make the broadcast message received The mobile relay is accessed, and the accessed terminal device can determine that the TAC of the mobile relay is the first TAC according to the third broadcast message. Figure 6a shows an example of a terminal device receiving the third broadcast message.

It can be seen from the implementation shown in Figure 6a that when the DU entity of the mobile relay requests the access network device to activate the cell of the DU entity, the access network device can access the MT entity of the mobile relay. The TAC of the cell of the network device is determined to be the TAC of the cell of the DU entity, and the TAC of the cell of the DU entity is sent to the DU entity. In this way, when the mobile relay initially activates the cell, the TAC of the cell can be configured as the MT of the mobile relay. The TAC of the cell of the access network device that the entity accesses enables the network side to determine the actual location of the terminal device that accesses the mobile relay, thereby improving the efficiency and accuracy of the network's mobility management of the terminal device.

The embodiment shown in Figure 6b will be introduced below. In Figure 6b, the first cell where the mobile relay moves and accesses the access network device after the movement is taken as an example for introduction. Refer to Figure 6b. As shown in Figure 6b, the method includes:

Step 901: The MT entity of the mobile relay accesses the first cell of the access network device.

Step 902: The access network device determines that the mobile relay has moved.

In a possible implementation, a preset movement range can be set in advance. In step 902, when the access network device determines that the movement of the mobile relay satisfies the preset movement range, the access network device determines that the mobile relay has moved.

For example, when the access network device needs to determine whether the mobile relay has moved, the preset movement range corresponding to the access network device may include at least one of the above content 1 or content 2.

When the preset movement range includes any of the above content 1 or content 2: the access network device can determine that the movement of the mobile relay satisfies the content within the preset movement range. The relay movement satisfies the preset movement range, or in other words, the access network equipment determines that the mobile relay has moved.

When the preset movement range includes the above content 1 and content 2: when determining that the movement of the mobile relay satisfies at least one of the multiple items within the preset movement range, the access network device may determine that the movement of the mobile relay satisfies The preset movement range; alternatively, the access network device can determine that the movement of the mobile relay satisfies the preset movement range when determining that the movement of the mobile relay satisfies each of the multiple items within the preset movement range, in a more flexible manner. It can be set flexibly according to the actual situation.

The following introduces respectively through situations 6 to 7. Among them, case 6 is introduced by taking the preset movement range including the above content 1 as an example, and case 7 is introduced by taking the preset movement range including the above content 2 as an example.

Case 6: The preset mobility range includes: the TAC of the cell accessed by the MT entity of the mobile relay changes.

For example, the MT entity of the mobile relay moves from the second cell of the access network device to the first cell of the access network device. When the access network device queries that the TAC of the cell accessed by the MT entity of the mobile relay has changed, for example, it queries based on the MT entity's identity that the cell accessed by the MT entity changes from the TAC of the second cell to the TAC of the first cell. , then the access network equipment determines that the mobile relay has moved, or the access network equipment determines that the mobile relay has moved within the preset movement range, or the access network equipment determines that the movement of the mobile relay satisfies the preset movement range. .

Case 7: The preset mobility range includes: the cell identity of the cell accessed by the MT entity of the mobile relay changes.

For example, when the access network device queries that the cell identity of the cell accessed by the MT entity of the mobile relay has changed, the access network device determines that the mobile relay has moved, or the access network device determines that the mobile relay has moved. A movement that satisfies the preset movement range occurs, or the access network device determines that the movement of the mobile relay satisfies the preset movement range.

In another possible implementation, when the access network device determines that the movement of the mobile relay does not meet the preset movement range, the access network device may not perform the following step 904, that is, the access network device may not send a message to the DU entity of the mobile relay. The TAC of the cell currently accessed by the MT entity sending the mobile relay: the first TAC. Or the access network device may attribute such a situation to the situation where the mobile relay determines that the mobile relay has not moved, or that the mobile relay has not moved within a preset movement range.

In a possible implementation, in the case where the preset movement range includes any one of the above content 1 and content 2: when the access network device determines that the movement of the mobile relay does not meet the content in the preset movement range , the access network device determines that the movement of the mobile relay does not meet the preset movement range.

In yet another possible implementation, in the case where the preset movement range includes the above content 1 and content 2: when the access network device determines that the movement of the mobile relay does not meet each of the contents in the preset movement range, Then the access network device determines that the movement of the mobile relay does not meet the preset movement range.

In another possible implementation, in the case where the preset movement range includes the above content 1 and content 2: when the access network device determines that the movement of the mobile relay does not meet at least one of the contents in the preset movement range, Then the access network device determines that the movement of the mobile relay does not meet the preset movement range, and the access network device may not send the TAC of the cell of the access network device to which the MT entity accesses to the DU entity. In this case, the access network device may determine that the movement of the mobile relay satisfies the preset movement range when determining that the movement of the mobile relay satisfies each of the multiple items within the preset movement range.

In the embodiment of this application, the access network equipment determines that the mobile relay has moved. For relevant content, please refer to the aforementioned mobile The relevant content of the steps in which the relay MT entity determines that the mobile relay moves will not be described again here.

Step 903: The access network device obtains the first TAC.

For the relevant content of step 903, please refer to the relevant content of step 704, which will not be described again.

Step 904: The access network device sends the first TAC to the DU entity of the mobile relay.

Correspondingly, the DU entity of the mobile relay receives the first TAC.

In the case where the DU entity's cell has been configured with a TAC before, in step 904, the access network device may carry the first TAC through a message, which may be, for example, a base station-CU configuration update message. The base station-CU configuration update message may be used to update the TAC of the cell of the DU entity. In the embodiment of this application, the base station-CU configuration update message can be written in English as gNB-CU configuration update.

In step 904, after receiving the first TAC, the DU entity determines that the first TAC is the TAC of the cell of the DU entity.

For the relevant content of step 904, please refer to the relevant content of the aforementioned step 705, which will not be described again.

Step 905: The mobile relay sends the third broadcast message.

In a possible implementation, the third broadcast message may include the identity of the cell of the first TAC and/or DU entity. For the relevant content of step 905, please refer to the relevant content of the aforementioned step 805, which will not be described again.

It can be seen from Figure 6b that when the access network device determines that the mobile relay has moved within the preset movement range, the access network device can send the DU entity of the mobile relay the information currently accessed by the MT entity of the mobile relay. The TAC of the cell of the access network device, so that the DU entity of the mobile relay uses the TAC of the cell of the access network device that the MT entity after the mobile relay moves to access as the TAC of the cell of the DU entity of the mobile relay. , which can achieve the effect of keeping the TAC of the DU entity of the mobile relay updated as it moves.

It is worth noting that since the mobile relay in the embodiment of the present application has mobility capabilities, when the mobile relay moves from one access network device to another access network device, the new access network device accessed after the move The solution implemented in can also refer to the solution shown in Figure 6a above, and will not be described again.

Based on the content shown in at least one of the above-mentioned Fig. 1a, Fig. 1b, Fig. 1c, Fig. 1d, Fig. 5, Fig. 6a or Fig. 6b and the other above-mentioned content. Figure 7 exemplarily shows a schematic flowchart of yet another possible cell information configuration method. In Figure 7, the mobile relay moves from cell 1 to cell 2 of the access network device. The TAC of the cell is TAC#2 and the TAC of the cell is TAC#3.

As shown in Figure 7, the method includes:

Step 1001: The MT entity of the mobile relay receives the broadcast message b1 from the access network device one.

The broadcast message b1 includes at least one of the TAC of cell 1 of access network device one, the identity of cell 1, or the identity of access network device one. The TAC of cell 1 is, for example, TAC#2.

The broadcast message b1 may also include indication information that the cell corresponding to the broadcast message b1 supports mobile relay.

Step 1002: The MT entity of the mobile relay performs cell selection and selects cell 1 for access.

Step 1003: The MT entity of the mobile relay establishes an RRC connection with the access network device.

Step 1004: The MT entity of the mobile relay sends a registration request message to the core network device.

Step 1005: The MT entity of the mobile relay is successfully registered.

Step 1006: The MT entity of the mobile relay initiates session establishment. The network allocates an IP address to the MT entity of the mobile relay. The mobile relay can use the IP address to interact with the management device.

Step 1007: The mobile relay sends message b2 to the management device. Message b2 is used to obtain cell configuration information.

Correspondingly, the management device receives the message b2 from the mobile relay.

Message b2 includes first indication information, and the first indication information is used to indicate that the management device does not need to configure TAC for the cell of the DU entity.

Step 1008: The management device may send a response message to message b2 to the mobile relay, where the response message to message b2 carries cell configuration information. The response message for message b2 does not include TAC.

For the solution of the above steps 1001 to 1008, please refer to the relevant content of the foregoing steps 501 to 508, which will not be described again here.

Similarly, message b2 may be sent by the MT entity of the mobile relay, and the response message to message b2 may be sent by the management device to the MT entity of the mobile relay. Message b2 may also be sent by the DU entity of the mobile relay, and the response message to message b2 may also be sent by the management device to the DU entity of the mobile relay. In the drawings of the embodiment of this application, the DU entity of the mobile relay sends message b2 to the management device, and the management device sends a response message of message b2 to the DU entity of the mobile relay as an example. For relevant content, please refer to the above description and will not be repeated again.

Step 1009: The DU entity of the mobile relay sends message b4 to the access network device 1 accessed by the MT entity of the mobile relay. The message b4 is used to request activation of the cell of the DU entity of the mobile relay. Message b4 does not need to carry TAC.

For the relevant content of step 1009, please refer to the relevant description of the aforementioned step 802. For the relevant content of the message b4, please refer to the relevant introduction of the aforementioned second message (for example, the message b4 can be the aforementioned second message), which will not be described again here.

Step 1010: Access network device one obtains the TAC of the cell of access network device one that the MT entity of the mobile relay accesses: TAC #2.

For the relevant content of step 1010, please refer to the relevant description of step 803, and the relevant content will not be described again here.

Step 1011: The access network device sends a response message of message b4 to the DU entity of the mobile relay.

For the relevant content of step 1011, please refer to the relevant description of step 804, which will not be described again.

Step 1012: The mobile relay sends broadcast message b5.

In a possible implementation, the broadcast message b5 includes TAC#2 and/or the cell identity of the cell of the DU entity. For the relevant content of step 1012, please refer to the relevant description of step 805, which will not be described again.

Step 1013: The MT entity of the mobile relay accesses the cell 2 of the access network device one.

The TAC of cell 2 is, for example, TAC#3.

The mobile relay may be in a mobile state. When the mobile relay moves from cell 1 to cell 2, the mobile relay needs to re-select a cell. For example, cell 2 can be selected as a new cell, and the mobile relay can access cell 2.

Step 1014: The access network device determines that the mobile relay has moved.

In step 1014, after the access network device determines that the mobile relay has moved, the access network device can determine the TAC of the cell accessed by the moved MT entity of the mobile relay (for related content, please refer to the related information in step 704). Description), and determine the TAC of the cell that the MT entity of the mobile relay accesses after moving as the current TAC of the cell of the DU entity.

For the relevant content of step 1014, please refer to the relevant description of step 902, which will not be described again.

Step 1015: The access network device sends message b7 to the DU entity of the mobile relay. The message b7 includes TAC#3. It can also be understood that TAC#3 in message b7 is used to indicate that the TAC of the cell of the DU entity is TAC#3.

Message b7 can be a configuration update message. The configuration update message may be used to update the TAC of the cell of the DU entity. The configuration update message can be written in English as gNB-CU configuration update.

For the relevant content of step 1015, please refer to the relevant description of step 904, which will not be described again.

Step 1016: The mobile relay sends broadcast message b8.

In a possible implementation, the broadcast message b8 may include TAC#3 and/or the cell identity of the cell of the DU entity. For the content of step 1016, please refer to the relevant content of step 905, and will not be described again.

It can be seen from the embodiment shown in Figure 7 that the mobile relay accesses cell 1 of access network device 1, and the access network device determines that the TAC of the cell of the DU entity is the TAC of cell 1. When the mobile relay moves and accesses cell 2 of access network device 1, the access network device sends the TAC of cell 2 to the DU entity of the mobile relay to notify the DU entity that the TAC of the cell of the DU entity is the cell. 2 TAC. If the mobile relay subsequently moves again and moves to a cell of access network device 1 that is different from cell 2, the access network device can again send the TAC of the cell accessed by the MT entity to the DU entity so that the DU entity can be updated. TAC of the cell of the DU entity. This solution is similar to the solution provided in steps 1013 to 1016 and will not be described again. Through this solution, during the movement of the mobile relay, the TAC of the cell of the DU entity of the mobile relay can be dynamically updated, so that the network side can more accurately determine the terminal based on the TAC of the mobile relay accessed by the terminal device. The current location of the device.

It is worth noting that when the mobile relay moves from one access network device to another access network device, such as from access network device one to access network device two, the MT entity of the mobile relay moves from access network device to access network device two. When network device 1 switches to access network device 2, the MT entity of the mobile relay may be in the RRC connected state. The MT entity of the mobile relay in the RRC connected state switches from the cell of the access network device one to the cell of the access network device two, and establishes an RRC connection with the access network device two. Afterwards, the solution executed by the mobile relay and access network equipment may be similar to the solution from step 1009 to step 1012 in Figure 7, which will not be described again.

It should be noted that in the embodiment of the present application, when a certain network element (for example, network element A) receives information from another network element (for example, network element B), it may mean that network element A directly receives information from network element B. Receiving information may also refer to network element A receiving information from network element B via other network elements (for example, network element C). When network element A receives information from network element B via network element C, network element C can transparently transmit the information or process the information, for example, carry the information in different messages for transmission or filter the information. , and only sends the filtered information to network element A. Similarly, in various embodiments of the present application, when network element A sends information to network element B, it may mean that network element A sends information directly to network element B, or it may mean that network element A sends information to network element B via other network elements (for example, network C). element) sends information to network element B.

The terms "system" and "network" in the embodiments of this application may be used interchangeably. "At least one" means one or more, and "plurality" means two or more. "And/or" describes the association of associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the related objects are in an "or" relationship. "At least one of the following" or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items). For example, at least one of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple .

And, unless otherwise specified, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the order, timing, priority or importance of multiple objects. degree.

It should be noted that the names of the above messages are only as examples. With the evolution of communication technology, any of the above messages may change its name. However, no matter how its name changes, as long as its meaning is the same as the meaning of the above message in this application. , all fall within the protection scope of this application.

According to the foregoing method, Figure 8 is a schematic structural diagram of a device provided by an embodiment of the present application. As shown in Figure 8, the communication The device may be a mobile relay MT entity, a mobile relay DU entity or an access network device, or may be a chip or circuit, such as a chip or circuit that may be provided in a mobile relay MT entity, such as a chip or circuit that may be provided in a mobile relay DU entity. Chips or circuits, such as chips or circuits that can be installed in access network equipment. The communication device can be used to execute the mobile relay MT entity, mobile relay in any of the related solutions in Figure 2, Figure 3a, Figure 3b, Figure 4a, Figure 4b, Figure 5, Figure 6a, Figure 6b or Figure 7. Method on the DU entity side or access network equipment side.

The communication device 1801 includes a processor 1802 and a transceiver 1803.

Further, the communication device 1801 may include a memory 1804. The dotted line on the memory 1804 in the figure further indicates that the memory is optional.

Furthermore, the communication device 1801 may further include a bus system, wherein the processor 1802, the memory 1804, and the transceiver 1803 may be connected through the bus system.

It should be understood that the above-mentioned processor 1802 may be a chip. For example, the processor 1802 can be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), or It can be a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or a microcontroller unit, MCU), or a programmable logic device (PLD) or other integrated chip.

During the implementation process, each step of the above method can be completed by instructions in the form of hardware integrated logic circuits or software in the processor 1802 . The steps of the methods disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware processor, or executed by a combination of hardware and software modules in the processor 1802. The software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field. The storage medium is located in the memory 1804. The processor 1802 reads the information in the memory 1804 and completes the steps of the above method in combination with its hardware.

It should be noted that the processor 1802 in the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. During the implementation process, each step of the above method embodiment can be completed through an integrated logic circuit of hardware in the processor or instructions in the form of software. The above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. . Each method, step and logical block diagram disclosed in the embodiment of this application can be implemented or executed. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory 1804 in the embodiment of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. For relevant descriptions of the memory in the embodiments of the present application, please refer to the foregoing content and will not be described again here.

When the communication device 1801 is the MT entity of the above-mentioned mobile relay, the processor 1802 is configured to execute through the transceiver 1803:

Receive a first TAC from the access network device, where the first TAC is the TAC of the first cell of the access network device to which the MT entity accesses. A first TAC is sent to the DU entity; the first TAC is for the TAC of the cell that is the DU entity.

In a possible implementation, when the communication device 1801 is the above-mentioned mobile relay MT entity, the processor 1802 is configured to execute through the transceiver 1803: send a first message to the DU entity, where the first message includes the first TAC, the first The TAC is used to instruct the DU entity to use the first TAC as the TAC of the cell of the DU entity.

In a possible implementation, when the communication device 1801 is the above-mentioned mobile relay MT entity, the processor 1802 is configured to execute through the transceiver 1803: before sending the first TAC to the DU entity, determine that the mobile relay has moved.

In a possible implementation, when the communication device 1801 is the above-mentioned mobile relay MT entity, the processor 1802 is configured to execute through the transceiver 1803: according to the TAC, cell identity, access network equipment, geographical area information, or movement distance At least one of determines that the mobile relay has moved.

In a possible implementation, when the communication device 1801 is the above-mentioned mobile relay MT entity, the processor 1802 is configured to execute through the transceiver 1803: receiving a second broadcast message, where the second broadcast message includes the second TAC, the second cell The identifier or the identifier of the access network equipment corresponding to the second cell. After receiving the second broadcast message, the MT entity receives the first broadcast message, where the first broadcast message includes the first TAC, the identity of the first cell, or the identity of the access network device corresponding to the first cell. When it is determined that at least one of the following contents is satisfied, it is determined that the mobile relay has moved:

The first TAC is different from the second TAC;

The identity of the first cell is different from the identity of the second cell; or,

The access network equipment corresponding to the first cell is different from the access network equipment corresponding to the second cell.

In a possible implementation, when the communication device 1801 is the above-mentioned mobile relay MT entity, the processor 1802 is configured to execute through the transceiver 1803: after receiving the second broadcast message, store the second TAC, the identity of the second cell, or The identifier of the access network equipment corresponding to the second cell.

In a possible implementation, when the communication device 1801 is the above-mentioned mobile relay MT entity, the processor 1802 is configured to execute through the transceiver 1803: send the first indication information to the management device, and the first indication information is used to instruct the management device There is no need to configure TAC for the DU entity's cell.

When the communication device 1801 is the above-mentioned mobile relay DU entity, the processor 1802 is configured to perform through the transceiver 1803: receiving the first TAC from the MT entity, where the first TAC is the TAC of the first cell of the access network device accessed by the MT entity. . Send the first TAC to the access network device, where the TAC of the cell of the DU entity is the first TAC.

In a possible implementation, when the communication device 1801 is the above-mentioned mobile relay DU entity, the processor 1802 is configured to execute through the transceiver 1803: send a third message to the access network device, where the third message includes the first TAC, The third message is used to request activation of the cell of the DU entity.

In a possible implementation, when the communication device 1801 is the above-mentioned mobile relay DU entity, the processor 1802 is configured to execute through the transceiver 1803: after receiving the first TAC from the MT entity, determine the first TAC as the DU entity. The TAC of the community.

In a possible implementation, when the communication device 1801 is the above-mentioned mobile relay DU entity, the processor 1802 is configured to execute through the transceiver 1803: send the first indication information to the management device, and the first indication information is used to instruct the management device There is no need to configure TAC for the DU entity's cell.

When the communication device 1801 is the above-mentioned access network device, the processor 1802 is configured to perform through the transceiver 1803: receiving a third message from the DU entity of the mobile relay, the third message is used to request activation of the cell of the DU entity, the third message The TAC of the cell including the first TAC and DU entity is the first TAC. A response message of the third message is returned to the DU entity of the mobile relay, where the response message of the third message is used to indicate that the cell of the DU entity has been activated. Among them, mobile relay is in The mobile relay is used to provide relay services between terminal equipment and access network equipment.

In another possible implementation, when the communication device 1801 is the above-mentioned mobile relay, such as a DU entity of the mobile relay, the processor 1802 is configured to execute through the transceiver 1803: send the second indication information to the access network device, The second indication information instructs the access network device to configure TAC for the cell of the DU entity. A first TAC is received from the access network device, the first TAC is for the TAC of the cell that is the DU entity. Wherein, the mobile relay is in a moving state, and the mobile relay is used to provide relay services between the terminal equipment and the access network equipment.

In a possible implementation, when the communication device 1801 is the above-mentioned mobile relay, the processor 1802 is configured to execute through the transceiver 1803: before receiving the first TAC from the access network device, send the MT entity to the access network device The identity of the MT entity is used to determine the first TAC.

In a possible implementation, when the communication device 1801 is the above-mentioned mobile relay, the processor 1802 is configured to execute through the transceiver 1803: sending a second message to the access network device, where the second message requests activation of the cell of the DU entity, The second message includes second indication information.

In another possible implementation, when the communication device 1801 is the above-mentioned access network device, the processor 1802 is configured to execute through the transceiver 1803: obtain the first TAC, where the first TAC is an access point accessed by the MT entity of the mobile relay. The TAC of the first cell of the network-connected device. The first TAC is sent to the DU entity of the mobile relay, and the first TAC is for the TAC of the cell serving as the DU entity. Wherein, the mobile relay is in a moving state, and the mobile relay is used to provide relay services between the terminal equipment and the access network equipment.

In a possible implementation, when the communication device 1801 is the above-mentioned access network device, the processor 1802 is configured to execute through the transceiver 1803: receiving the identity of the MT entity. Obtain the first TAC according to the identification of the MT entity.

In a possible implementation, when the communication device 1801 is the above-mentioned access network device, the processor 1802 is configured to perform through the transceiver 1803: receiving second indication information, and the second indication information indicates that the access network device is a DU entity. The cell is configured with TAC.

In a possible implementation, when the communication device 1801 is the above-mentioned access network device, the processor 1802 is configured to execute through the transceiver 1803: receive a second message from the DU entity of the mobile relay, and the second message requests activation of the DU. For the entity's cell, the second message does not contain TAC.

In a possible implementation, when the communication device 1801 is the above-mentioned access network device, the processor 1802 is configured to execute through the transceiver 1803: before sending the first TAC to the DU entity of the mobile relay, determine that the mobile relay has moved .

In a possible implementation, when the communication device 1801 is the above-mentioned access network device, the processor 1802 is configured to execute through the transceiver 1803: according to the TAC, cell identity, and geographical area of the cell accessed by the MT entity of the mobile relay At least one of the information or the moving distance determines that the mobile relay has moved.

For the concepts, explanations, detailed descriptions and other steps involved in the communication device 1801 related to the technical solutions provided by the embodiments of this application, please refer to the descriptions of these contents in the foregoing methods or other embodiments, and will not be described again here.

According to the foregoing method, Figure 9 is a schematic structural diagram of a device provided by an embodiment of the present application. As shown in Figure 9, a communication device 1901 may include a communication interface 1903 and a processor 1902. Further, the communication device 1901 may include a memory 1904. The dotted line on memory 1904 in the figure further indicates that the memory is optional. The communication interface 1903 is used to input and/or output information; the processor 1902 is used to execute computer programs or instructions, so that the communication device 1901 implements the above-mentioned Figure 2, Figure 3a, Figure 3b, Figure 4a, Figure 4b, Figure 5, Figure Interested parties in any of Figure 6a, Figure 6b or Figure 7 The method on the mobile relay MT entity or mobile relay DU entity side in the case, or the communication device 1901 implements the above-mentioned Figure 2, Figure 3a, Figure 3b, Figure 4a, Figure 4b, Figure 5, Figure 6a, Figure 6b or Figure 7 Methods on the access network device side in any of the related solutions. In this embodiment of the present application, the communication interface 1903 can implement the solution implemented by the transceiver 1803 of Figure 8, the processor 1902 can implement the solution implemented by the processor 1802 of Figure 8, and the memory 1904 can implement the memory 1804 of Figure 8. The implemented solution will not be described again here.

Based on the above embodiments and the same concept, Figure 10 is a schematic diagram of a device provided by an embodiment of the present application. As shown in Figure 10, the communication device 2001 can be a mobile relay MT entity, a mobile relay DU entity or an access network device. It may also be a chip or circuit, such as a chip or circuit that may be provided in a mobile relay MT entity, a mobile relay DU entity or an access network device.

The communication device 2001 includes a processing unit 2002 and a communication unit 2003. Further, the communication device 2001 may or may not include the storage unit 2004. The memory unit 2004 in the figure is dotted to further indicate that the memory is optional.

The communication unit 2003 is used to input and/or output information; the processing unit 2002 is used to execute computer programs or instructions, so that the communication device 2001 implements the above-mentioned Figure 2, Figure 3a, Figure 3b, Figure 4a, Figure 4b, Figure 5, Figure 6a, Figure 6b or the method on the mobile relay DU entity side in any of the related solutions in Figure 6b or Figure 7, or the communication device 2001 implements the above-mentioned Figure 2, Figure 3a, Figure 3b, Figure 4a, Figure 4b , the method on the access network device side in any of the related solutions in Figure 5, Figure 6a, Figure 6b or Figure 7. In the embodiment of the present application, the communication unit 2003 can implement the solution implemented by the transceiver 1803 of Figure 8. The processing unit 2002 can implement the solution implemented by the processor 1802 of Figure 8. The storage unit 2004 can implement the memory of Figure 8. The solution implemented by 1804 will not be described again here.

According to the method provided by the embodiment of the present application, the present application also provides a computer program product. The computer program product includes: computer program code or instructions. When the computer program code or instructions are run on a computer, the computer causes the computer to execute Figure 2 , the method of any one of the embodiments shown in any one of Figure 3a, Figure 3b, Figure 4a, Figure 4b, Figure 5, Figure 6a, Figure 6b or Figure 7 .

According to the method provided by the embodiment of the present application, the present application also provides a computer-readable storage medium. The computer-readable medium stores program code. When the program code is run on a computer, it causes the computer to execute Figures 2 and 3a. , the method of any one of the embodiments shown in any one of Figure 3b, Figure 4a, Figure 4b, Figure 5, Figure 6a, Figure 6b or Figure 7 .

According to the method provided by the embodiment of the present application, the present application also provides a chip system, and the chip system may include a processor. The processor is coupled to the memory and can be used to execute any one of the embodiments shown in any one of Figure 2, Figure 3a, Figure 3b, Figure 4a, Figure 4b, Figure 5, Figure 6a, Figure 6b or Figure 7 method. Optionally, the chip system also includes a memory. Memory is used to store computer programs (also called codes, or instructions). The processor is used to call and run the computer program from the memory, so that the device equipped with the chip system executes any one of Figure 2, Figure 3a, Figure 3b, Figure 4a, Figure 4b, Figure 5, Figure 6a, Figure 6b or Figure 7 The method of any one of the embodiments shown in the item.

According to the method provided by the embodiment of the present application, the present application also provides a system, which includes the aforementioned one or more mobile relays and access network equipment. Mobile relay includes MT entity and DU entity.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. A computer program product includes one or more computer instructions. When computer instructions are loaded and executed on a computer, processes or functions according to embodiments of the present application are generated in whole or in part. A computer can be a general purpose computer, a special purpose computer, a computer network, or Other programmable devices. Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, e.g., computer instructions may be transmitted from a website, computer, server or data center via a wired link (e.g. Coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means to transmit to another website, computer, server or data center. Computer-readable storage media can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or other integrated media that contains one or more available media. Usable media may be magnetic media (e.g., floppy disks, hard disks, tapes), optical media (e.g., high-density digital video discs (DVD)), or semiconductor media (e.g., solid state disks (SSD) )wait.

It should be noted that part of this patent application document contains content protected by copyright. The copyright owner retains copyright except in making copies of the contents of the patent document or records in the Patent Office.

The second communication device in the above device embodiments corresponds to the second communication device or the first communication device in the first communication device and method embodiments, and corresponding steps are performed by corresponding modules or units, such as communication units (transceivers). To perform the step of receiving or sending in the method embodiment, other steps except sending and receiving may be executed by the processing unit (processor). For the functions of specific units, please refer to the corresponding method embodiments. There can be one or more processors.

The terms "component", "module", "system", etc. used in this specification are used to refer to computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to, a process, a processor, an object, an executable file, a thread of execution, a program and/or a computer running on a processor. Through the illustrations, both applications running on the computing device and the computing device may be components. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers. Additionally, these components can execute from various computer-readable media having various data structures stored thereon. A component may, for example, be based on a signal having one or more data packets (eg, data from two components interacting with another component, such as a local system, a distributed system, and/or a network, such as the Internet, which interacts with other systems via signals) Communicate through local and/or remote processes.

Those of ordinary skill in the art will appreciate that the various illustrative logical blocks and steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, or a combination of computer software and electronic hardware. accomplish. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

A unit described as a separate component may or may not be physically separate. A component shown as a unit may or may not be a physical unit, that is, it may be located in one place, or it may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in various embodiments of the present application may be integrated into one processing unit, or each unit may The unit physically exists alone, or two or more units can be integrated into one unit. Functions may be stored in a computer-readable storage medium when implemented in the form of software functional units and sold or used as independent products.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the present application, and all of them should be covered. within the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A cell information configuration method, characterized in that it is suitable for mobile relays, the mobile relays are in a moving state, and the mobile relays are used to provide relay services between terminal equipment and access network equipment, The mobile relay includes a mobile terminal MT entity and a distribution unit DU entity, and the method includes:

The MT entity receives the first tracking area code TAC from the access network device, where the first TAC is the TAC of the first cell of the access network device to which the MT entity accesses;

The MT entity sends the first TAC to the DU entity; the first TAC is used as the TAC of the cell of the DU entity.
The method of claim 1, wherein the MT entity sends the first TAC to the DU entity, including:

The MT entity sends a first message to the DU entity. The first message includes the first TAC. The first TAC is used to instruct the DU entity to use the first TAC as the DU entity. The TAC of the community.
The method according to claim 1 or 2, characterized in that before the MT entity sends the first TAC to the DU entity, it further includes:

The MT entity determines that the mobile relay has moved.
A cell information configuration method, characterized in that it is suitable for mobile relays, the mobile relays are in a moving state, and the mobile relays are used to provide relay services between terminal equipment and access network equipment, The mobile relay includes a mobile terminal MT entity and a distribution unit DU entity, and the method includes:

The DU entity receives a first tracking area code TAC from the MT entity, where the first TAC is the TAC of the first cell of the access network device accessed by the MT entity;

The DU entity sends a first TAC to the access network device, where the TAC of the cell of the DU entity is the first TAC.
The method of claim 4, further comprising:

The DU entity sends first indication information to the management device, where the first indication information is used to indicate that the management device does not need to configure TAC for the cell of the DU entity.
A cell information configuration method, characterized in that it is suitable for mobile relays, the mobile relays are in a moving state, and the mobile relays are used to provide relay services between terminal equipment and access network equipment, The mobile relay includes a mobile terminal MT entity and a distribution unit DU entity, and the method includes:

The DU entity of the mobile relay sends second indication information to the access network device, and the second indication information instructs the access network device to configure a tracking area code TAC for the cell of the DU entity;

The DU entity of the mobile relay receives the first TAC from the access network device, and the first TAC is used as the TAC of the cell of the DU entity; the first TAC is the TAC of the mobile relay. The TAC of the first cell of the access network device to which the MT entity accesses.
The method according to claim 6, characterized in that before the DU entity of the mobile relay receives the first TAC from the access network device, it further includes:

The DU entity of the mobile relay sends the identifier of the MT entity to the access network device; the identifier of the MT entity is used to determine the first TAC.
The method according to claim 6 or 7, characterized in that the method further includes:

The DU entity of the mobile relay sends first indication information to the management device, where the first indication information is used to indicate that the management device does not need to configure TAC for the cell of the DU entity.
A cell information configuration method, characterized by including:

The access network device obtains the first tracking area code TAC, where the first TAC is the TAC of the first cell of the access network device that the mobile terminal MT entity of the mobile relay accesses;

The access network device sends the first TAC to the distributed unit DU entity of the mobile relay, where the first TAC is used as the TAC of the cell of the DU entity;

Wherein, the mobile relay is in a moving state, and the mobile relay is used to provide relay services between terminal equipment and the access network equipment.
The method of claim 9, wherein the access network device obtains the first TAC, including:

The access network device receives the identification of the MT entity;

The access network device obtains the first TAC according to the identification of the MT entity.
The method according to claim 9 or 10, characterized in that the method further includes:

The access network device receives second indication information, and the second indication information instructs the access network device to configure a TAC for the cell of the DU entity.
The method according to any one of claims 9-11, characterized in that before the access network device sends the first TAC to the DU entity of the mobile relay, it further includes:

The access network device receives a second message from the DU entity of the mobile relay, the second message requests activation of a cell of the DU entity, and the second message does not include a TAC.
The method according to any one of claims 9-12, characterized in that before the access network device sends the first TAC to the DU entity of the mobile relay, it further includes:

The access network device determines that the mobile relay has moved.
A mobile terminal MT entity, characterized in that the MT entity is located in a mobile relay, and the mobile relay also includes a distribution unit DU entity; the mobile relay is in a moving state, and the mobile relay is used for Provide relay services between terminal equipment and access network equipment;

The MT entity includes a processor and a communication interface, the processor is configured to execute through the communication interface:

Receive a first tracking area code TAC from the access network device, where the first TAC is the TAC of the first cell of the access network device to which the MT entity accesses;

The first TAC is sent to the DU entity; the first TAC is for the TAC of a cell that is the DU entity.
The MT entity of claim 14, wherein the processor is configured to execute through the communication interface:

A first message is sent to the DU entity, where the first message includes the first TAC, where the first TAC is used to instruct the DU entity to use the first TAC as the TAC of the cell of the DU entity.
The MT entity of claim 14 or 15, wherein the processor is further configured to execute through the communication interface:

It is determined that the mobile relay moves.
A distribution unit DU entity, characterized in that the DU entity is located in a mobile relay, and the mobile relay also includes a mobile terminal MT entity; the mobile relay is in a moving state, and the mobile relay is used for Provide relay services between terminal equipment and access network equipment;

The DU entity includes a processor and a communication interface, the processor is configured to execute through the communication interface:

Receive a first tracking area code TAC from the MT entity, where the first TAC is the TAC of the first cell of the access network device accessed by the MT entity;

Send a first TAC to the access network device, where the TAC of the cell of the DU entity is the first TAC.
The DU entity of claim 17, wherein the processor is further configured to execute through the communication interface:

Send first indication information to the management device, where the first indication information is used to indicate that the management device does not need to configure TAC for the cell of the DU entity.
A distribution unit DU entity, characterized in that the mobile relay is in a moving state, and the mobile relay is used to provide relay services between terminal equipment and access network equipment, and the mobile relay includes Mobile terminal MT entity and distribution unit DU entity:

The DU entity of the mobile relay includes a processor and a communication interface, the processor is configured to execute through the communication interface:

Send second instruction information to the access network device, where the second instruction information instructs the access network device to configure a tracking area code TAC for the cell of the DU entity;

Receive a first TAC from the access network device, the first TAC is used as the TAC of the cell of the DU entity; the first TAC is the access to which the MT entity of the mobile relay accesses. The TAC of the first cell of the network-connected device.
The DU entity of claim 19, wherein the processor is further configured to execute through the communication interface:

Send the identifier of the MT entity to the access network device; the identifier of the MT entity is used to determine the first TAC.
The DU entity of claim 19 or 20, wherein the processor is further configured to execute through the communication interface:

Send first indication information to the management device, where the first indication information is used to indicate that the management device does not need to configure TAC for the cell of the DU entity.
An access network device, characterized by including a processor and a communication interface, the processor being configured to execute through the communication interface:

Obtain a first tracking area code TAC, where the first TAC is the TAC of the first cell of the access network device to which the mobile terminal MT entity of the mobile relay accesses;

sending the first TAC to the distributed unit DU entity of the mobile relay, the first TAC being a TAC of the cell of the DU entity;

Wherein, the mobile relay is in a moving state, and the mobile relay is used to provide relay services between terminal equipment and the access network equipment.
The access network device according to claim 22, wherein the processor is configured to use the communication interface to Oral execution:

Receive the identification of the MT entity;

Obtain the first TAC according to the identification of the MT entity.
The access network device according to claim 22 or 23, wherein the processor is further configured to execute through the communication interface:

Receive second indication information, where the second indication information instructs the access network device to configure a TAC for the cell of the DU entity.
The access network device according to any one of claims 22 to 24, wherein the processor is further configured to execute through the communication interface:

A second message is received from the DU entity of the mobile relay, the second message requests activation of a cell of the DU entity, and the second message does not include a TAC.
The access network device according to any one of claims 22 to 25, characterized in that the processor is also used to:

It is determined that the mobile relay moves.
A communication device, characterized by including a processor and a memory,

The memory is used to store computer programs or instructions;

The processor is used to execute computer programs or instructions in the memory, so that the method described in any one of claims 1-3 is executed, so that the method described in any one of claims 4-5 is executed, The method described in any one of claims 6-8 is performed, or the method described in any one of claims 9-13 is performed.
A communication device, characterized by comprising a processing module and a communication module, the processing module being configured to perform the method as claimed in any one of claims 1-3 through the communication module, or to perform the method as claimed in claim 4- 5, or perform the method as described in any one of claims 6-8, or perform the method as described in any one of claims 9-13.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer-executable instructions, and when called by a computer, the computer-executable instructions cause any one of claims 1-3 to The method is executed, so that the method described in any one of claims 4-5 is executed, the method described in any one of claims 6-8 is executed, or the method described in any one of claims 9-13 is executed. The method described is executed.
A chip system, characterized by including a communication interface and a processor:

The communication interface is used to input and/or output signaling or data;

The processor is configured to execute a computer executable program, so that the device installed with the chip system performs the method as described in any one of claims 1-3, or performs the method as described in any one of claims 4-5. The method described in any one of claims 6-8, or the method described in any one of claims 9-13.