WO2020200038A1

WO2020200038A1 - Admission control method and device

Info

Publication number: WO2020200038A1
Application number: PCT/CN2020/081415
Authority: WO
Inventors: 王瑞; 彭文杰; 韩锋
Original assignee: 华为技术有限公司
Priority date: 2019-03-29
Filing date: 2020-03-26
Publication date: 2020-10-08
Also published as: CN111757559A

Abstract

Provided in embodiments of the present invention are an admission control method and device enabling release of a secondary node (SN) when the secondary node (SN) is no longer able to provide a service to a terminal apparatus. The admission control method comprises: a secondary node determining to release a first resource reserved for a terminal apparatus in a radio resource control (RRC) inactive mode, wherein the first resource is a resource dedicated to the terminal apparatus; and the secondary node sending a first message to notify a master node that the secondary node is unable to resume service provision for the terminal apparatus.

Description

Access control method and device

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office, the application number is 201910251469.5, and the application name is "Access Control Method and Apparatus" on March 29, 2019, the entire content of which is incorporated into this application by reference .

Technical field

This application relates to the communication field, and more specifically, to a method and device for admission control in the communication field.

Background technique

Currently, a terminal communication state is known, that is, a radio resource control (radio resource control, RRC) deactivated state, referred to as an inactive state. In this inactive state, the core network equipment, access equipment, and terminal equipment all retain the context information of the terminal equipment. The core network equipment and the access equipment have a dedicated signaling connection for the terminal equipment, but the terminal equipment and the access equipment There is no need to maintain RRC connections between devices.

In one possible manner, the terminal device can have a communication connection with at least two access devices at the same time and can send and receive data, which can be called (dual-connectivity, DC), or multiple connections. Among the at least two access devices, the access device responsible for interacting radio resource control messages with the terminal device and interacting with the core network control plane entity may be called a master node (MN), and other access devices The device may be referred to as a secondary base station (secondary node, SN).

Under the DC architecture, when the terminal device enters the Inactive state, the MN does not release the SN, so that the terminal device can quickly resume the data transmission carried by the SN when the terminal device returns to the RRC connected state. However, in the process of the terminal device transitioning from the inactive state to the RRC connected state, how to perform admission control on the recovery of the terminal device is an urgent problem to be solved.

Summary of the invention

The embodiment of the present application provides a method and device for admission control, which can release the secondary base station SN when the secondary base station SN cannot continue to serve the terminal equipment.

The first aspect provides a method of access control, including:

The secondary base station determines to release the first resource reserved for the terminal device in a radio resource control RRC deactivated state, where the first resource is a resource dedicated to the terminal device;

The secondary base station sends a first message to the primary base station, where the first message is used to notify the secondary base station that the service to the terminal device cannot be restored.

Therefore, in the dual-connected network architecture of the embodiment of the present application, when the terminal device enters the deactivated state and the secondary base station SN determines that it cannot continue to be the terminal device, the secondary base station SN may send a first message to the primary base station MN to notify The secondary base station SN cannot continue to serve the terminal equipment. Based on this, the embodiment of the present application introduces an admission control mechanism during the recovery of the secondary base station SN, so that the release of the secondary base station SN can be completed when the secondary base station SN cannot be successfully recovered.

With reference to the first aspect, in some implementation manners of the first aspect, before the secondary base station sends the first message to the primary base station, the method further includes:

The secondary base station receives a first request from the primary base station, where the first request is used to request the secondary base station to resume service to the terminal device.

As an example, the first request may be an SN recovery request, and the first message may be an SN recovery rejection message.

Therefore, when the terminal device enters the deactivated state and the secondary base station SN determines that it cannot continue to be the terminal device, when the SN receives the SN recovery request sent by the primary base station, it can send an SN recovery rejection message to the MN to notify SN cannot continue to serve terminal equipment.

With reference to the first aspect, in some implementations of the first aspect, the first message includes a cause value, and the cause value is used to identify that the secondary base station cannot restore the service to the terminal device.

With reference to the first aspect, in some implementation manners of the first aspect, the first resource includes at least one of the following:

The resources allocated or reserved by the secondary base station for the terminal device, the context of the terminal device reserved by the secondary base station, and the dedicated control plane of the terminal device on the interface between the secondary base station and the primary base station Connection and user plane connection, the dedicated user plane connection of the terminal device between the secondary base station and the core network.

Among them, the resources allocated or reserved by the secondary base station SN for the terminal device may be, for example, air interface transmission resources, NG-U interface transmission resources, Xn interface user plane transmission resources between the secondary base station and the primary base station, and Xn between the secondary base station and the primary base station. At least one of the interface control plane transmission resources.

The dedicated user plane connection between the secondary base station SN and the core network for the terminal device may include, for example, transport layer information (transport layer information), data transmission channel, and NG-U transport layer address information allocated by the secondary base station SN for the terminal device. At least one of the NG-U transport layer address information allocated by the core network to the terminal device.

The dedicated control plane connection of the terminal device on the interface between the secondary base station SN and the primary base station MN, for example, may include transport layer information, stream control transmission protocol (SCTP) connection, and UE allocated by the primary base station MN to the terminal device XnAP ID, at least one of the UE XnAP IDs allocated by the secondary base station to the terminal device. As an example, the interface between the secondary base station SN and the primary base station MN may be an Xn interface.

The dedicated user plane connection of the terminal device on the interface between the secondary base station SN and the primary base station MN, for example, can be the transmission layer information, the data transmission channel, the Xn-U transmission layer address information allocated by the secondary base station SN for the terminal device, the primary base station MN At least one of the Xn-U transport layer address information allocated to the terminal device.

In combination with the first aspect, some implementations of the first aspect further include:

The secondary base station sends the reserved context of the terminal device to the primary base station.

With reference to the first aspect, in some implementations of the first aspect, the context includes at least one of the following information:

The mapping relationship between the quality of service QoS flow carried by the secondary base station and the data radio bearer DRB, the secondary cell group SCG configuration, the configuration of the packet data convergence protocol PDCP carried by the secondary base station, and the PDCP context carried by the secondary base station, The security indication and security result of the packet data unit PDU session/QoS flow carried by the secondary base station, and the configuration of the SDAP corresponding to the PDU session/QoS flow carried by the secondary base station SN.

Optionally, the context of the terminal device may also include the terminal device-specific user plane connection between the secondary base station SN and the core network, and the terminal device-specific control plane connection and user on the interface between the secondary base station SN and the primary base station MN. At least one of surface connection.

With reference to the first aspect, in some implementation manners of the first aspect, the determination by the secondary base station to release the reserved first resource includes:

The secondary base station determines to release the first resource based on its own load of the secondary base station.

As an example, the secondary base station SN may determine whether to release the first resource according to its own load. In a possible situation, the secondary base station SN may determine to release the first resource when the load is too heavy and it cannot continue to serve the terminal device, or the secondary base station may determine not to release the first resource when the load is not too heavy. The time-assisted base station SN can continue to serve the terminal equipment, that is, it can resume the RRC connection with the terminal equipment.

Alternatively, in some embodiments, the secondary base station SN may also determine whether to release the first resource according to other factors, which is not specifically limited in comparison with the embodiments of the present application.

In the second aspect, a method of access control is provided, including:

The primary base station receives a first message from the secondary base station, where the first message is used to notify the secondary base station that it cannot resume service to the terminal device in the RRC deactivated state;

According to the first message, the primary base station determines that the secondary base station cannot resume service to the terminal device.

Therefore, in the dual-connected network architecture of the embodiment of the present application, when the terminal device enters the deactivated state and the secondary base station SN determines that it cannot continue to be the terminal device, the secondary base station SN may send a first message to the primary base station MN to notify The secondary base station SN cannot continue to serve the terminal equipment. Based on this, the embodiment of the present application introduces an admission control mechanism in the recovery process of the secondary base station SN, so that the release of the secondary base station SN can be completed when the secondary base station SN cannot be successfully recovered.

With reference to the second aspect, in some implementation manners of the second aspect, before the primary base station receives the first message from the secondary base station, the method further includes:

The primary base station sends a first request to the secondary base station, where the first request is used to request the secondary base station to resume service to the terminal device.

With reference to the second aspect, in some implementation manners of the second aspect, the first message includes a cause value, and the cause value is used to identify that the secondary base station refuses to restore the service to the terminal device.

In combination with the second aspect, some implementations of the second aspect further include:

The primary base station receives the context of the terminal device from the secondary base station.

With reference to the second aspect, in some implementations of the second aspect, the context includes at least one of the following information:

The mapping relationship between the QoS flow carried by the secondary base station and the data radio bearer DRB, the secondary cell group SCG configuration, the configuration of the packet data convergence protocol PDCP carried by the secondary base station, the PDCH context carried by the secondary base station, the The security indication and security result of the PDU session/QoS flow carried by the secondary base station, and the configuration of the SDAP corresponding to the PDU session/QoS flow carried by the secondary base station SN.

The primary base station releases a reserved second resource, where the second resource is a resource dedicated to the terminal device on an interface between the primary base station and the secondary base station.

As an example, the second resource may include at least one of a control plane connection, a user plane connection, and a transmission resource dedicated to the terminal device on the interface between the primary base station and the secondary base station.

The primary base station establishes an NG-U tunnel for carrying quality of service QoS flow/packet data unit PDU session, wherein, before releasing the second resource, the QoS flow/PDU session is carried on the NG-U tunnel of the secondary base station. -U tunnel.

The primary base station sends a second message to the terminal device, where the second message is used to notify the terminal device to release the configuration of the secondary base station, where the configuration of the secondary base station includes SCG configuration and secondary base station configuration At least one of measurement information and power configuration information.

Optionally, the second message is an RRC recovery message or an RRC reconfiguration message.

The primary base station receives a second request sent by the terminal device, where the second request is used to request the terminal device to return to the RRC connected state from the radio resource control RRC deactivated state.

With reference to the second aspect, in some implementation manners of the second aspect, the second request includes related information about whether the secondary base station can be restored, and is used to assist the primary base station in determining whether a restoration request can be sent to the secondary base station.

In a third aspect, a terminal device is provided, including:

A second message is received from the primary base station, where the second message is used to notify the terminal device to release the configuration of the secondary base station, where the configuration of the secondary base station includes SCG configuration, measurement information configured by the secondary base station, and power configuration At least one of the information;

The terminal device releases the configuration of the secondary base station.

Therefore, in the dual-connected network architecture in the embodiment of the present application, when the terminal device enters the deactivated state and the secondary base station SN determines that it cannot continue to be the terminal device, the secondary base station SN can notify the primary base station that the secondary base station SN cannot continue to be a terminal Device service, so that the terminal device releases the configuration of the secondary base station. Based on this, the embodiment of the present application introduces an admission control mechanism in the recovery process of the secondary base station SN, so that the release of the secondary base station SN can be completed when the secondary base station SN cannot be successfully recovered.

In a fourth aspect, a wireless communication device is provided. The device may be a secondary base station or a chip in the secondary base station. The device has the function of realizing the above-mentioned first aspect and various possible implementation modes. This function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

In a possible design, the device includes a transceiver module. Optionally, the device further includes a processing module. The transceiver module may be, for example, at least one of a transceiver, a receiver, and a transmitter. The transceiver module Can include radio frequency circuits or antennas. The processing module may be a processor. Optionally, the device further includes a storage module, and the storage module may be a memory, for example. When a storage module is included, the storage module is used to store instructions. The processing module is connected to the storage module, and the processing module can execute the instructions stored in the storage module or from other instructions, so that the device executes the above-mentioned first aspect and various possible implementation methods.

In another possible design, when the device is a chip, the chip includes a transceiver module. Optionally, the chip also includes a processing module. The transceiver module may be, for example, an input/output interface or pin on the chip. Or circuits, etc. The processing module may be a processor, for example. The processing module can execute instructions so that the chip in the terminal executes the first aspect and any possible implementation communication methods. Optionally, the processing module may execute instructions in the storage module, and the storage module may be a storage module in the chip, such as a register, a cache, and the like. The storage module may also be located in the communication device but outside the chip, such as read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (random access memory) memory, RAM) etc.

Among them, the processor mentioned in any of the above can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more for controlling the above The integrated circuit of the program execution of the method of the first aspect and various possible implementation modes.

In a fifth aspect, a wireless communication device is provided. The device may be a main base station or a chip in the main base station. The device has the function of realizing the above-mentioned second aspect and various possible implementation manners. This function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

In a possible design, the device includes a transceiver module. Optionally, the device further includes a processing module. The transceiver module may be, for example, at least one of a transceiver, a receiver, and a transmitter. The transceiver module Can include radio frequency circuits or antennas. The processing module may be a processor. Optionally, the device further includes a storage module, and the storage module may be a memory, for example. When a storage module is included, the storage module is used to store instructions. The processing module is connected to the storage module, and the processing module can execute instructions stored in the storage module or from other instructions, so that the device executes the communication methods of the second aspect and various possible implementation manners.

In another possible design, when the device is a chip, the chip includes a transceiver module. Optionally, the device also includes a processing module. The transceiver module may be, for example, an input/output interface or pin on the chip. Or circuits, etc. The processing module may be a processor, for example. The processing module can execute instructions so that the chip in the terminal executes the second aspect and any possible implementation methods. Optionally, the processing module may execute instructions in the storage module, and the storage module may be a storage module in the chip, such as a register, a cache, and the like. The storage module may also be located in the communication device but outside the chip, such as read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (random access memory) memory, RAM) etc.

Among them, the processor mentioned in any of the above can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more for controlling the above The second aspect and various possible implementations are integrated circuits for program execution.

In a sixth aspect, a computer storage medium is provided, and program code is stored in the computer storage medium, and the program code is used to instruct the execution of the first aspect, the second aspect, the third aspect, or any of the possible implementations thereof. Method of instruction.

In a seventh aspect, a computer program product containing instructions is provided, which when running on a computer, causes the computer to execute the method in the first aspect, the second aspect, or the third aspect, or any possible implementation manner thereof.

In an eighth aspect, a communication system is provided. The communication system includes a device capable of implementing the methods and various possible designs of the foregoing first aspect, and the foregoing device capable of implementing the various methods and various possible designs of the foregoing second aspect. Functional device. Further, the communication system may also include the aforementioned terminal equipment.

In a ninth aspect, a processor is provided, configured to be coupled with a memory, and configured to execute the method in the first aspect, the second aspect, the third aspect, or any possible implementation manners thereof.

In a tenth aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is used to communicate with an external device or an internal device. The processor is used to implement the above-mentioned first or second or third aspects or The method in any possible implementation.

Optionally, the chip may further include a memory in which instructions are stored, and the processor is configured to execute instructions stored in the memory or instructions derived from other sources. When the instruction is executed, the processor is used to implement the method in the foregoing first aspect, second aspect, third aspect, or any possible implementation manner thereof.

Optionally, the chip can be integrated on the primary base station or the secondary base station.

Description of the drawings

Fig. 1 shows a schematic diagram of a network architecture to which an embodiment of the present application is applied.

Fig. 2 shows a schematic diagram of a network architecture provided by an embodiment of the present application.

FIG. 3 shows another schematic diagram of a network architecture applicable to the embodiments of the present application.

Fig. 4 shows a schematic diagram of a network architecture applying an embodiment of the present application.

Fig. 5 shows a schematic diagram of another network architecture applying an embodiment of the present application.

Fig. 6 shows a schematic diagram of another network architecture applying an embodiment of the present application.

Fig. 7 shows a schematic diagram of another network architecture applying an embodiment of the present application.

FIG. 8 shows a schematic flowchart of an admission control method provided by an embodiment of the present application.

FIG. 9 shows a schematic flowchart of another admission control method provided by an embodiment of the present application.

FIG. 10 shows a schematic flowchart of another admission control method provided by an embodiment of the present application.

FIG. 11 shows a schematic flowchart of another admission control method provided by an embodiment of the present application.

FIG. 12 shows a schematic flowchart of another admission control method provided by an embodiment of the present application.

FIG. 13 shows a schematic flowchart of another admission control method provided by an embodiment of the present application.

FIG. 14 shows a schematic flowchart of another method for admission control provided by an embodiment of the present application.

FIG. 15 shows a schematic flowchart of another admission control method provided by an embodiment of the present application.

FIG. 16 shows a schematic flowchart of another admission control method provided by an embodiment of the present application.

Fig. 17 shows a schematic diagram of a wireless communication apparatus provided by an embodiment of the present application.

FIG. 18 shows a schematic diagram of another wireless communication apparatus provided by an embodiment of the present application.

FIG. 19 shows a schematic structural diagram of a terminal device provided by this application.

FIG. 20 shows a schematic structural diagram of a network device provided by an embodiment of the present application.

detailed description

The technical solution in this application will be described below in conjunction with the drawings.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (time division duplex) , TDD), universal mobile telecommunication system (UMTS), the future 5th generation (5G) system or new radio (NR), etc.

The terminal equipment in the embodiments of this application may also be called: user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, Mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

The terminal device may be a device that provides voice/data connectivity to users, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and so on. At present, some examples of terminals are: mobile phones (mobile phones), tablets, notebook computers, palmtop computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, and augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving (self-driving), wireless terminals in remote medical surgery, and smart grid (smart grid) Wireless terminals, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocols , SIP) phone, wireless local loop (WLL) station, personal digital assistant (personal digital assistant, PDA), handheld device with wireless communication function, computing device or other processing device connected to wireless modem, vehicle Devices, wearable devices, terminal devices in the future 5G network or terminal devices in the future evolved public land mobile network (PLMN), etc., which are not limited in the embodiment of the present application.

As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices. It is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones. Use, such as various smart bracelets and smart jewelry for physical sign monitoring.

In addition, in the embodiments of this application, the terminal device may also be a terminal device in the Internet of Things (IoT) system. The IoT is an important part of the development of information technology in the future. Its main technical feature is to pass items through communication technology. Connect with the network to realize the intelligent network of human-machine interconnection and interconnection of things.

In addition, the access device in the embodiment of the present application may be a device used to communicate with a terminal device. The access device may also be called an access network device or a radio access network device, and may be an evolved base station in an LTE system. (evolved NodeB, eNB or eNodeB), it can also be a wireless controller in the cloud radio access network (cloud radio access network, CRAN) scenario, or the access device can be a relay station, access point, vehicle-mounted device, or wearable The equipment and the access equipment in the future 5G network or the access equipment in the future evolved PLMN network can be an access point (AP) in a WLAN, or a new radio system (NR) system The gNB in the embodiment of this application is not limited.

In addition, in the embodiment of the present application, the access device is a device in the RAN, or in other words, a RAN node that connects a terminal device to a wireless network. For example, as an example and not a limitation, as an access device, one can enumerate: gNB, transmission reception point (TRP), evolved Node B (evolved Node B, eNB), radio network controller (radio network controller, RNC), Node B (Node B, NB), Base Station Controller (BSC), Base Transceiver Station (BTS), Home Base Station (for example, home evolved NodeB, or home Node B, HNB) , Baseband unit (BBU), or wireless fidelity (wireless fidelity, Wifi) access point (AP), etc. In a network structure, a network device may include a centralized unit (CU) node, or a distributed unit (DU) node, or a RAN device including a CU node and a DU node, or a control plane CU node (CU). -CP node), user plane CU node (CU-UP node) and RAN equipment of DU node.

The access device provides services for the cell, and the terminal device communicates with the access device through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be corresponding to the access device (for example, a base station) A cell. A cell can belong to a macro base station or a base station corresponding to a small cell. The small cell here can include: metro cell, micro cell, pico cell, and micro cell. Femto cells, etc., these small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services.

In addition, the carrier in the LTE system or the 5G system can have multiple cells working at the same frequency at the same time. In some special scenarios, the concept of the above-mentioned carrier and the cell can also be considered equivalent. For example, in a carrier aggregation (CA) scenario, when a secondary carrier is configured for a terminal device, the carrier index of the secondary carrier and the cell identification (Cell ID) of the secondary cell working on the secondary carrier will be carried at the same time. In this case, the concept of carrier and cell can be regarded as equivalent. For example, the terminal equipment accessing a carrier is equivalent to accessing a cell.

Fig. 1 shows a schematic diagram of a network architecture to which an embodiment of the present application is applied. As shown in Figure 1, the terminal device can simultaneously perform dual-connectivity (DC) with two access devices. Among the two access devices, the access device that is responsible for interacting with the terminal device for radio resource control messages and interacting with the core network control plane entity is the master node (MN), and the other wireless access device It is a secondary base station (secondary node, SN).

Similarly, the terminal device can also have a communication connection with multiple access devices at the same time and can send and receive data, which can be called multi-connectivity or multi-connectivity (MC). Among the multiple access devices, there can be An access device is responsible for interacting radio resource control messages with the terminal device, and is responsible for interaction with the core network control plane entity. Then, the access device can be called MN, and the other access devices can be called SN.

In the embodiment of this application, the MN and the SN may be base stations of the same radio access type (RAT), or may be base stations of different RATs.

Fig. 2 shows a schematic diagram of a network architecture provided by an embodiment of the present application. As shown in Figure 2, the communication between the access device and the terminal device follows a certain protocol layer structure. For example, the control plane protocol layer structure may include the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, and the media interface. Access control (media access control, MAC) layer and physical layer and other protocol layer functions. The user plane protocol layer structure may include the functions of the PDCP layer, the RLC layer, the MAC layer, and the physical layer; in one implementation, the PDCP layer may also include the service data adaptation protocol (SDAP) Floor.

The functions of these protocol layers can be implemented by one node or multiple nodes; for example, in an evolution structure, the access device can include a centralized unit (CU) and a distributed unit (DU) , Multiple DUs can be centrally controlled by one CU.

As shown in Figure 2, CU and DU can be divided according to the protocol layers of the wireless network. For example, the functions of the PDCP layer and above protocol layers are set in the CU, and the protocol layers below the PDCP, such as the RLC layer and MAC layer, are set in the DU. In other words, the CU has functions above the PDCP layer (including PDCP, RRC, and SDAP), and the DU has functions below the PDCP layer (including RLC, MAC, and PHY).

This type of protocol layer division is just an example, it can also be divided in other protocol layers, for example, in the RLC layer, the functions of the RLC layer and above protocol layers are set in the CU, and the functions of the protocol layers below the RLC layer are set in the DU; Or, in a certain protocol layer, for example, part of the functions of the RLC layer and the functions of the protocol layer above the RLC layer are set in the CU, and the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer are set in the DU. In addition, it can also be divided in other ways, for example, by time delay, and functions that need to meet the delay requirement for processing time are set in the DU, and functions that do not need to meet the delay requirement are set in the CU.

FIG. 3 shows another schematic diagram of a network architecture applicable to the embodiments of the present application. Compared with the architecture shown in Figure 2, the control plane (CP) and the user plane (UP) of the CU can also be separated and realized by dividing them into different entities, namely the control plane CU entity (CU-CP entity) and the user plane CU entity (CU-UP entity).

In the above network architecture, the signaling generated by the CU can be sent to the terminal device through the DU, or the signaling generated by the terminal device can be sent to the CU through the DU. The DU can directly pass the protocol layer encapsulation without analyzing the signaling and transparently transmit it to the terminal device or CU. If the following embodiments involve the transmission of such signaling between the DU and the terminal device, at this time, the sending or receiving of the signaling by the DU includes this scenario.

In the above embodiment, the CU is divided into network equipment on the RAN side of the access network. In addition, the CU may also be divided into network equipment on the CN side of the core network, which is not limited here.

The devices in the following embodiments of the present application may be located in terminal equipment or network equipment according to their realized functions. When the above CU-DU structure is adopted, the access device may be a CU node, or a DU node, or a RAN device including a CU node and a DU node.

Fig. 4 shows a schematic diagram of a network architecture applying an embodiment of the present application. The network architecture is a 5G wireless communication system. As shown in Figure 4, the overall architecture of the 5G wireless communication system (also known as 5G system, 5GS, 5G system, etc.) consists of 5G core network (also known as 5G Core, 5GCN, 5GC) and NG-RAN (also known as 5G-RAN) composition. Among them, 5GC is the core network of the 5G wireless communication system, and NG-RAN is the wireless access network of the 5G wireless communication system.

Specifically, as shown in FIG. 4, NG-RAN includes two types of RAN nodes (RAN nodes), namely gNB and ng-eNB. Among them, the gNB provides terminal devices with new radio (NR) user plane and control plane protocol stack terminations (Terminations). The ng-eNB provides terminal equipment with an evolved universal terrestrial radio access (evolved universal terrestrial radio access, E-UTRA) user plane and control plane protocol stack termination point. Among them, the core network equipment in the 5GC and the access equipment in the NG-RAN (for example, gNB, ng-eNB) perform data transmission through the NG interface. The Xn interface can be used for data transmission between gNB and gNB, between gNB and ng-eNB, and between ng-eNB and ng-eNB.

It should be noted that FIG. 4 exemplarily shows a schematic diagram of a network architecture, but the embodiment of the present application is not limited thereto. For example, the 5GC may also include more core network equipment, and the NG-RAN may also include base stations of other access technologies.

In the 5G wireless communication system shown in Figure 4, the following three specific multi-radio access types dual connectivity (multiple RATs dual connectivity, MR-DC) architecture are defined:

1) E-UTRA NR DC (referred to as EN-DC) architecture

This architecture can also be called option 3 series. As shown in FIG. 5, an LTE base station (such as LTE eNB) serves as the primary station MN, an NR base station (such as gNB) serves as a secondary station SN for DC, and the core network equipment is EPC.

In the implementation shown in Figure 5(a), the LTE eNB is connected to the EPC through the S1-C interface or the S1-U interface, and provides air interface transmission resources for data between the terminal device and the EPC.

In the implementation shown in Figure 5(b), the LTE eNB is connected to the EPC through the S1-C interface or the S1-U interface, and the gNB is connected to the EPC through the S1-U interface, which is the data transmission between the terminal equipment and the EPC Provide air interface transmission resources.

2) NR E-UTRA DC (NE-DC for short) architecture

This architecture can also be called option 4 series. As shown in Figure 6, the NR base station (such as gNB) serves as the primary station MN, the LTE base station (such as ng eNB) serves as the secondary station SN for DC, and the core network equipment is 5GC.

In the implementation shown in Figure 6(a), the gNB is connected to the 5GC through the NG-C interface or the NG-U interface to provide air interface transmission resources for data transmission between the terminal device and the 5GC.

In the implementation shown in Figure 6(b), gNB is connected to 5GC through NG-C interface or NG-U interface, ng-eNB is connected to 5GC through NG-U interface, providing data transmission between terminal equipment and 5GC Air interface transmission resources.

3) Next Generation E-UTRA NR DC (Next Generation E-UTRA NR DC, NG NE-DC for short) architecture

This architecture can also be called option 7 series. As shown in Figure 7, the LTE base station (such as ng-gNB) serves as the primary station MN, the NR base station (such as gNB) serves as the secondary station SN for DC, and the core network equipment is 5GC.

In the implementation shown in Fig. 7(a), the ng-eNB is connected to the 5GC through the NG-C interface or the NG-U interface to provide air interface transmission resources for data transmission between the terminal equipment and the 5GC.

In the implementation shown in Figure 7 (b), the ng-eNB is connected to the 5GC through the NG-C interface or the NG-U interface, and the gNB is connected to the 5GC through the NG-U interface to provide data transmission between the terminal equipment and the 5GC. Air interface transmission resources.

In addition, MN and SN may also be wireless access devices of the same standard. For example, MN and SN are both NR base stations or both LTE base stations. It should be noted that in the network architectures shown in FIG. 5 to FIG. 7, the primary station MN and the secondary station SN may perform data transmission through a wired connection or a wireless connection, which is not limited in the embodiment of the present application.

In the embodiment of the present application, since the terminal device can simultaneously receive services of multiple cells under one base station, the master base station MN may also be referred to as a master cell group (MCG). Similarly, the secondary base station SN may also be referred to as a secondary cell group (SCG).

The following describes the RRC connection state in this application.

There are three RRC connection states, namely RRC idle state, RRC connected state, and RRC inactive state.

In the RRC idle state, the terminal device deletes the context of the terminal device, but the core network device has the context of the terminal device, and the access device does not have the context of the terminal device. At the same time, there is no dedicated signaling connection for terminal equipment between the core network equipment and the access equipment, such as the NG connection related to the terminal equipment, or the UE-related S1 connection (UE associated S1 connection). In the embodiment of the present application, the context of the terminal device is, for example, the access stratum (AS) context of the terminal device, which is not limited in the embodiment of the present application.

When downlink data arrives, the core network device will initiate a paging (paging) for the terminal device in the tracking area (TA) of the terminal device. Among them, the tracking area can also be called a paging area. Then, the terminal device learns whether it needs to switch to the RRC connected state to receive downlink data by monitoring the paging channel.

When there is uplink data to be sent, the terminal device will actively trigger to enter the RRC connected state to send data.

In addition, when the terminal device moves in the RRC idle state, when it crosses the tracking area TA, a location area update (tracking area update, TAU) is required.

When the terminal device is in the RRC connected state, the core network device and the access device have the context of the terminal device. In addition, the RRC connection is maintained between the terminal device and the access device, and the terminal device can perform uplink and downlink transmission of data.

When the terminal device is in the RRC deactivated state, the terminal device and the access device store the AS context of the terminal device, and the core network device also has the terminal device context. In addition, there is a dedicated signaling connection for terminal equipment between the core network equipment and the access equipment, such as a UE-associated NG connection (UE associated NG connection). But terminal equipment and access equipment do not need to maintain RRC connections. In the embodiments of this application, the RRC deactivated state may also be referred to as the RRC deactivated state.

When downlink data arrives, the access device can initiate a paging, and the paging area can be an idle paging area (tracking area, TA) or a RAN-based notification area (RNA). When the terminal device moves in the RRC deactivated state, location updates are required across paging areas, such as TAU or RAN-based notification area update (RNAU).

It can be seen that for the core network equipment, the deactivated terminal equipment is similar to the connected terminal equipment. For the access equipment, the deactivated terminal equipment is similar to the idle state terminal equipment. There is no real-time RRC connection and data transmission. , Need to send downlink data for the terminal device through paging. For the deactivated state, since the dedicated connection between the core network device and the access device is not released, the AS context of the terminal device is stored on the access device side, which can speed up the recovery of the terminal device to the connected state and quickly perform data transmission.

It should be noted that for the NE-DC architecture in Figure 6, the NG EN-DC architecture in Figure 7 and the DC architecture where MN and SN are both NR base stations, since the base stations are all NG-RAN and are not The 5GC is connected, so when the terminal device is in the NE-DC, NG EN-DC, and NR-NR DC architecture, it can support the RRC deactivated state, that is, the RRC deactivated state.

The method and device for admission control provided by this application will be described in detail below with reference to the accompanying drawings.

The technical solution of the present application can be applied to a wireless communication system, and communication devices in the wireless communication system can have a wireless communication connection relationship. One of the communication devices may be, for example, the first access device (for example, the main base station MN), or a chip configured in the first access device (for example, the main base station MN), and the other of the communication devices may be, for example, the The second access device (for example, the secondary base station SN) or a chip configured in the second access device (for example, the secondary base station SN). In addition, the communication device also includes a terminal device, and the terminal device supports an RRC deactivated state.

In the following, description will be made with reference to FIGS. 8 to 14, taking the first access device as the primary base station MN and the second access device as the secondary base station SN as examples. For the implementation method of the chip in the primary base station MN and the chip in the secondary base station SN, reference may be made to the specific description of the primary base station MN and the secondary base station SN, and no repeated introduction will be made.

FIG. 8 is a schematic flowchart of an admission control method shown from the perspective of device interaction. As shown in FIG. 8, the admission control method may include steps 110 to 130.

110. The secondary base station determines to release the first resource reserved for the terminal device in the radio resource control RRC deactivated state. Wherein, the first resource is a resource dedicated to the terminal device.

In a possible manner, when the primary base station configures the terminal device in the RRC deactivated state, the primary base station MN may request to suspend the secondary base station SN. The suspended secondary base station SN may reserve resources for the terminal device in the RRC deactivated state, that is, the above-mentioned first resource. In the embodiments of this application, reservation may refer to reservation or preservation.

It should be noted that at the moment when the secondary base station performs step 110, that is, when it determines to release the first resource reserved for the terminal device in the RRC deactivated state, the terminal device may be in the RRC deactivated state, or may be transferred from the RRC deactivated state. For other connection states, this embodiment of the application does not limit this.

As an example, the first resource may include at least one of the following information:

The resources allocated or reserved by the secondary base station SN for the terminal equipment, the context of the terminal equipment reserved by the secondary base station SN, the dedicated user plane connection between the secondary base station SN and the core network, the secondary base station SN and the primary base station MN The dedicated control plane connection and user plane connection of the terminal device on the interface between the terminals are not specifically limited in the embodiment of the present application.

Among them, the resources allocated or reserved by the secondary base station SN for the terminal equipment may be, for example, air interface transmission resources, NG-U interface transmission resources, Xn interface user plane transmission resources between the secondary base station and the primary base station, and the secondary base station and the primary base station At least one of the Xn interface control plane transmission resources between.

The dedicated control plane connection of the terminal device on the interface between the secondary base station SN and the primary base station MN, for example, may include transport layer information, stream control transmission protocol (SCTP) connection, and the primary base station MN allocates terminal equipment At least one of the UE XnAP ID of the UE XnAP ID assigned by the secondary base station to the terminal device. As an example, the interface between the secondary base station SN and the primary base station MN may be an Xn interface.

The dedicated user plane connection of the terminal device on the interface between the secondary base station SN and the primary base station MN, for example, can be the transmission layer information, the data transmission channel, the Xn-U transmission layer address information allocated by the secondary base station SN for the terminal device, the primary At least one of the Xn-U transport layer address information allocated by the base station MN to the terminal device. Wherein, the transport layer address information may include at least one of IP address, port number, and GTP tunnel identifier.

Optionally, the context of the terminal device stored by the secondary base station SN, for example, the AS context, may include at least one of the following information:

The mapping relationship between the PDU session/QoS flow carried by the secondary base station SN and the data radio bearer DRB, the configuration of the secondary cell group SCG, the configuration of the packet data convergence protocol PDCP carried by the secondary base station SN, the PDCP context carried by the secondary base station SN, the secondary base station The configuration of the SDAP corresponding to the PDU session/QoS flow carried by the SN, the security indication and the security result of the PDU session/QoS flow carried by the secondary base station SN, etc., are not specifically limited in the embodiment of the present application.

Optionally, the context of the terminal device may also include the terminal device-specific user plane connection between the secondary base station SN and the core network, and the terminal device-specific control plane connection and user on the interface between the secondary base station SN and the primary base station MN. At least one of surface connection, etc., which is not limited in the embodiment of the present application. Then, at this time, the first resource may refer to the context of the terminal device reserved by the secondary base station SN.

In the embodiment of the present application, the secondary base station SN may determine to release the reserved first resource dedicated to the terminal device when the terminal device is in the RRC deactivated state. It is understandable that the secondary base station SN determines to release the first resource, which can also be referred to as the secondary base station SN determining not to continue to serve the terminal device or the secondary base station SN does not have the ability to continue to serve the terminal device.

Alternatively, in some embodiments, the secondary base station SN may also determine whether to release the first resource according to other factors, which is not specifically limited in comparison with the embodiments of the present application. For example, when the configuration of the secondary base station SN is changed so that the secondary base station SN cannot accept the terminal device, it may be determined to release the first resource.

120. The secondary base station SN sends a first message to the primary base station MN, where the first message is used to notify the secondary base station SN that the service to the terminal device cannot be restored.

Correspondingly, the primary base station MN receives the first message.

In the embodiment of the present application, the primary base station MN may be the base station that configures the terminal equipment to enter the RRC deactivated state, or may be the base station where the terminal equipment is restored. It should be noted that the base station that configures the terminal device to enter the RRC deactivated state and the base station restored by the terminal device may be the same base station or different base stations. As an example, the movement of the terminal device may cause a difference between the base station configured to enter the RRC deactivated state and the base station restored by the terminal device.

In a possible implementation manner, the first message may carry a cause value, and the cause value may indicate that the secondary base station is overloaded, or it may indicate that the secondary base station cannot restore service to the terminal device.

Optionally, the secondary base station SN may also send the context of the terminal device on the secondary base station side to the primary base station MN. In an implementation manner, the first message may carry the context of the terminal device on the secondary base station side. It is understandable that the context of the terminal device on the secondary base station side can also be sent to the MN through a message different from the first message.

130. According to the first message, the primary base station determines that the secondary base station cannot resume service to the terminal device.

Optionally, the primary base station may release the reserved second resource after determining that the secondary base station cannot restore service to the terminal device. Wherein, the second resource is a resource dedicated to the terminal device on the interface between the primary base station and the secondary base station.

In a possible design, the transmission resources dedicated to the terminal equipment on the interface between the primary base station and the secondary base station may be, for example, the user plane transmission resources of the interface between the secondary base station and the primary base station, and the transmission resources between the secondary base station and the primary base station. At least one of the interface control plane transmission resources.

Specifically, the dedicated control plane connection and user plane connection of the terminal device on the interface between the primary base station and the secondary base station can be referred to the above description, and for the sake of brevity, it will not be repeated here.

Correspondingly, when the secondary base station SN sends the context of the terminal device on the secondary base station side, the primary base station MN can acquire the context on the secondary base station side. The primary base station MN can obtain the configuration information of the terminal device by the secondary base station SN according to the context. Optionally, after the secondary base station SN is released, the primary base station can reconfigure the terminal device delta according to the configuration information, or send the configuration information to the new secondary base station for use in the new secondary base station Reference for configuration.

Optionally, the primary base station MN may also establish an NG-U tunnel for carrying quality of service QoS flows/packet data unit PDU sessions, where, before the primary base station MN releases the second resource, the QoS flow/PDU session is carried on On the NG-U tunnel of the secondary base station MN. In other words, MN#1 can also perform path switch. In this way, it is possible to transfer the NG-U tunnel originally carried on the SN's QoS flow/PDU session (session) to the MN.

9 is a schematic flowchart of another admission control method from the perspective of device interaction, where the primary base station that configures the terminal device to enter the RRC deactivated state is the same as the primary base station that the terminal device requests to recover, such as both It is MN#1. It should be understood that FIG. 9 shows the steps or operations of the admission control method, but these steps or operations are only examples, and the embodiment of the present application may also perform other operations or variations of each operation in FIG. 9. In addition, the various steps in FIG. 9 may be performed in a different order from that presented in FIG. 9, and it is possible that not all the operations in FIG. 9 are to be performed.

201. MN#1 determines to configure the terminal device in the RRC deactivated state.

202. MN#1 sends an RRC connection release message to the terminal device, which is used to configure the terminal device in the RRC deactivated state.

203. MN#1 sends a request message to the SN, which is used to inform the SN that the terminal device has entered the RRC deactivated state and request to suspend the SN.

Optionally, the SN may release part of the configuration of the terminal device based on the request message, such as the RLC layer and the following configuration.

It should be noted that in the embodiment of the present application, the order of steps 202 and 203 can be interchanged, that is, the order of 202 and 203 is not limited.

204. The SN sends an acknowledgement (acknowledge, ACK) in response to the request message in step 203 to MN#1.

Optionally, the ACK may carry the context of the terminal device on the SN side. Specifically, the context can be referred to the description in FIG. 8. For brevity, details are not repeated here.

205. The terminal device sends a resume request (resume request) to MN#1, which is used to request to resume from the RRC deactivated state to the RRC connected state. Optionally, the recovery request may carry related information about whether the SN can be recovered, which is used to assist MN#1 in determining whether the recovery request can be sent to the SN.

206. MN#1 sends an SN resume request (SN resume request) to the SN, which is used to request the SN to resume service to the terminal device. The SN recovery request may be an example of the first request.

Optionally, the SN recovery request may be an SN modification request (SN modification request), which carries indication information, which is used to instruct the SN to generate or update the SCG configuration for the terminal device, so that the SN is informed that the message indicates that the SN is requested to recover .

Optionally, 207, SN determines that the load is too heavy.

Specifically, the SN can determine whether it can continue to provide services for the terminal device according to its own load. When the SN determines that it is overloaded, it cannot continue to provide services for the terminal device. At this time, the SN determines to release the first resource dedicated to the terminal device. Specifically, the first resource can be referred to the description in FIG. 8. For brevity, details are not repeated here.

Optionally, when the SN determines that there is no overload, the SN determines to continue to provide services for the terminal device, that is, there is no need to release the first resource.

In the embodiment of the present application, the sequence of 206 and 207 is not limited. In other words, step 207 may also occur before step 206.

208. The SN sends an SN resume reject (SN resume reject) message to MN#1, which is used to indicate that the request for continued service to the terminal device is rejected. Here, the SN recovery rejection message corresponds to an example of the first message in FIG. 8.

Optionally, the SN recovery rejection message carries a reason value, indicating that the SN is overloaded, that is, it indicates that the SN cannot recover the service to the terminal device.

Optionally, when the SN restoration request is an SN modification request, the SN restoration rejection message may be an SN modification confirmation message or an SN modification failure message. Different from the prior art, MN#1 receives an SN recovery rejection message (such as an SN modification confirmation message or an SN modification failure message), and needs to know that the message does not indicate a modification failure, but that the SN cannot successfully recover. The effect is equivalent to SN is released. Optionally, in this embodiment of the present application, the SN modification confirmation message or the SN modification failure message includes a reason value, which indicates that the SN refuses to continue serving the terminal device.

Optionally, when the ACK does not include the context of the terminal device on the SN side, the SN recovery rejection message may also include the context of the terminal device on the SN side.

In the embodiment of the present application, the SN releases the first resource reserved for the terminal device at the same time or after sending the SN recovery rejection message, and the first resource is a resource dedicated to the terminal device.

Correspondingly, MN#1 receives the SN recovery rejection message, and according to the message, determines that the SN cannot continue to serve the terminal device. At this time, MN#1 can release the second resource, which is a dedicated resource of the terminal device on the interface between MN#1 and the SN. Specifically, the second resource can be referred to the description in FIG. 8. For brevity, details are not repeated here.

Optionally, MN#1 may also establish an NG-U tunnel for carrying quality of service QoS flow/packet data unit PDU session, wherein, before releasing the second resource, the QoS flow/PDU session is carried in all On the NG-U tunnel of the secondary base station.

Optionally, when the SN determines to continue serving the terminal device, the SN sends an SN recovery confirmation message to MN#1 to indicate that it can continue to serve the terminal device. Optionally, when the SN recovery request message is an SN modification request message, the SN recovery confirmation message may be an SN modification confirmation message.

209. MN#1 sends configuration information to the terminal device.

Optionally, when MN#1 receives the SN restoration rejection message, the configuration information may include indication information for informing the terminal device to release the SN-related configuration. As an example, the SN-related configuration specifically includes at least one of the following information: SCG configuration, SN configuration measurement information, power configuration information, and so on.

Optionally, the configuration information can be carried in the RRC recovery message or carried in the RRC reconfiguration message.

Therefore, in the dual-connected network architecture of the embodiment of the present application, when the terminal device enters the deactivated state and the secondary base station SN determines that it cannot continue to be the terminal device, when the SN receives the SN recovery request, it can send the SN to the MN Send an SN recovery rejection message to notify the SN that it cannot continue to serve the terminal device. Based on this, the embodiment of the present application introduces an admission control mechanism in the recovery process of the secondary base station SN, so that the release of the secondary base station SN can be completed when the secondary base station SN cannot be successfully recovered.

Figure 10 is a schematic flowchart of another admission control method from the perspective of device interaction, in which the primary base station (for example, MN#1) that configures the terminal device to enter the RRC deactivated state, and the terminal device request recovery The main base station (such as MN#2) is different. It should be understood that FIG. 10 shows the steps or operations of the admission control method, but these steps or operations are only examples, and the embodiment of the present application may also perform other operations or variations of each operation in FIG. 10. In addition, the various steps in FIG. 10 may be performed in a different order from that presented in FIG. 10, and it is possible that not all operations in FIG. 10 are to be performed.

301. MN#1 determines to configure the terminal device in the RRC deactivated state.

302. MN#1 sends an RRC connection release message to the terminal device, which is used to configure the terminal device in the RRC deactivated state.

303. MN#1 sends a request message to the SN, which is used to inform the SN that the terminal device has entered the RRC deactivated state and request to suspend the SN.

304. The SN sends an acknowledgement (acknowledge, ACK) in response to the request message in step 303 to MN#1.

Specifically, steps 301 to 304 can refer to steps 201 to 204 in FIG.

305. The terminal device sends a resume request (resume request) to MN#2, which is used to request to resume from the RRC deactivated state to the RRC connected state. Optionally, the recovery request can carry related information about whether the SN can be recovered, which is used to assist MN#2 in determining whether the recovery request can be sent to the SN. It can be understood that after the terminal device moves from MN#1 to MN#2, it will send a recovery request to MN#2.

306, MN#2 requests context from MN#1.

Here, the context is the context of the terminal device saved on the MN#1 side.

As an example, the context includes at least one of the following information:

The mapping relationship between the QoS flow carried by MN#1 and the data radio bearer DRB, the MCG configuration of the primary cell group, the PDCP configuration of the packet data convergence protocol carried by MN#1, the PDCP context carried by MN#1, and the PDCP context carried by MN#1 The SDAP configuration corresponding to the PDU session/QoS flow, the security indication and the security result of the PDU session/QoS flow carried by MN#1, etc., are not specifically limited in the embodiment of the present application.

Optionally, MN#2 may also instruct MN#1 to request restoration of SN.

307. MN#1 sends the context of the terminal device on the MN side to MN#2.

Optionally, MN#1 may also send the SN identification and the terminal device identification to the terminal device. In some embodiments, the terminal device identifier may be the terminal device identifier on the Xn interface assigned to the terminal device by the SN. As an example, when the terminal device is a UE, the terminal device identifier may be SN UE XnAP ID.

Optionally, MN#1 may also send indication information to MN#1 to indicate to MN#2 that MN#1 has suspended the SN for the terminal device.

308. MN#2 sends an SN resume request (SN resume request) to the SN, which is used to request the SN to resume service to the terminal device.

Optionally, the SN recovery request may include a terminal device identification, which is used by the SN to identify the terminal device. As an example, the terminal device identifier may be the identifier on the Xn interface allocated by the SN for the terminal device.

Optionally, 309, SN determines that the load is too heavy.

310. The SN sends an SN resume reject (SN resume reject) message to MN#2, which is used to indicate that the request for continued service to the terminal device is rejected.

311. MN#2 sends configuration information to the terminal device.

Specifically, in steps 309 to 311, the interaction process between SN and MN#2 can be referred to the description in the interaction process between SN and MN#1 in steps 207 to 209 in FIG. 8. For the sake of brevity, details are not repeated here.

Figure 11 is a schematic flowchart of another admission control method from the perspective of device interaction, where the primary base station that configures the terminal device to enter the RRC deactivated state is the same as the primary base station that the terminal device requests to recover, such as both It is MN#1. It should be understood that FIG. 11 shows the steps or operations of the admission control method, but these steps or operations are only examples, and the embodiment of the present application may also perform other operations or variations of each operation in FIG. 11. In addition, the steps in Fig. 11 can be performed in a different order from that presented in Fig. 11, and it is possible that not all the operations in Fig. 11 are to be performed.

401. MN#1 determines to configure the terminal device in the RRC deactivated state.

402. MN#1 sends an RRC connection release message to the terminal device, which is used to configure the terminal device in the RRC deactivated state.

403. MN#1 sends a request message to the SN, which is used to inform the SN that the terminal device has entered the RRC deactivated state and request to suspend the SN.

404. The SN sends an acknowledgement (acknowledge, ACK) in response to the request message in step 403 to MN#1.

Specifically, steps 401 to 404 can refer to steps 201 to 204 in FIG.

Optionally, 405, SN determines that the load is too heavy.

Specifically, the SN can determine whether it can continue to provide services for the terminal device according to its own load. When the SN determines that it is overloaded, it cannot continue to provide services for the terminal device and can execute 406. At this time, the SN determines to release the first resource dedicated to the terminal device. Specifically, the first resource can be referred to the description in FIG. 8. For brevity, details are not repeated here.

Optionally, when the SN determines that there is no overload, the SN determines to continue to provide services for the terminal device, that is, there is no need to release the first resource. At this time, the SN does not need to send a message to MN#1. In other words, when the MN receives the recovery request of the terminal device, if the SN has not sent an SN release request message for requesting the release of the first resource dedicated to the terminal device to MN#1, MN#1 can consider that SN can continue to be Terminal equipment service.

In one implementation, when the ACK in step 404 includes the context of the terminal device on the SN side, if MN#1 receives the recovery request sent by the terminal device, and does not receive the SN release request message actively sent by the SN, then MN#1 can restore the SN according to the context of the terminal device on the SN side in the ACK.

406. The SN sends an SN release request message to MN#1 for requesting the release of the first resource dedicated to the terminal device. The SN requests the release of the first resource, which means that the SN cannot continue to provide services for the terminal device. That is to say, in this embodiment of the application, when the SN determines that it cannot continue to provide services for the terminal device, it can actively send an SN release request message to MN#1. Here, the SN release request message corresponds to an example of the first message in FIG. 8.

Optionally, when the context of the terminal device on the SN side is not included in the ACK, the SN release request message may also include the context of the terminal device on the SN side.

In the embodiment of the present application, the SN releases the first resource reserved for the terminal device at the same time or after sending the SN release request message, and the first resource is a resource dedicated to the terminal device.

Correspondingly, MN#1 receives the SN release request message, and according to the message, determines that the SN cannot continue to serve the terminal device. At this time, MN#1 can release the second resource, which is a resource dedicated to the terminal device on the interface between MN#2 and the SN.

Specifically, the second resource can be referred to the description in FIG. 8. For brevity, details are not repeated here.

407. MN#1 sends an SN release confirmation message to the SN.

Optionally, the MN may also establish an NG-U tunnel for carrying quality of service QoS flows/packet data unit PDU sessions, wherein, before releasing the second resource, the QoS flow/PDU session is carried on the auxiliary On the NG-U tunnel of the base station.

408: The terminal device sends a resume request (resume request) to MN#1, which is used to request to resume from the RRC deactivated state to the RRC connected state. Optionally, the recovery request may carry related information about whether the SN can be recovered, which is used to assist MN#1 in determining whether the recovery request can be sent to the SN.

409. MN#1 sends configuration information to the terminal device.

Here, the configuration information can refer to the description of the configuration information in step 209 in FIG.

Therefore, in the dual-connected network architecture of the embodiment of the present application, when the terminal device enters the deactivated state, and the secondary base station SN determines that it cannot continue to be the terminal device, the SN can actively send an SN release request message to the MN to indicate SN cannot continue to serve terminal equipment. Based on this, the embodiment of the present application introduces an admission control mechanism in the recovery process of the secondary base station SN, so that the release of the secondary base station SN can be completed when the secondary base station SN cannot be successfully recovered.

Figure 12 is a schematic flowchart of another admission control method from the perspective of device interaction, in which the primary base station (such as MN#1) that configures the terminal device to enter the RRC deactivated state, and the terminal device request recovery The main base station (such as MN#2) is different. It should be understood that FIG. 12 shows the steps or operations of the admission control method, but these steps or operations are only examples, and the embodiment of the present application may also perform other operations or variations of each operation in FIG. 12. In addition, the various steps in FIG. 12 may be performed in a different order from that presented in FIG. 12, and it is possible that not all operations in FIG. 12 are to be performed.

501. MN#1 determines to configure the terminal device in the RRC deactivated state.

502. MN#1 sends an RRC connection release message to the terminal device, which is used to configure the terminal device in the RRC deactivated state.

503. MN#1 sends a request message to the SN, which is used to inform the SN that the terminal device has entered the RRC deactivated state and request to suspend the SN.

504. The SN sends an acknowledgement (acknowledge, ACK) in response to the request message in step 503 to MN#1.

Specifically, steps 501 to 504 can refer to steps 201 to 204 in FIG. 9, and for the sake of brevity, details are not repeated here.

Optionally, 505, SN determines that the load is too heavy.

506. The SN sends an SN release request message to MN#1 to request the release of the first resource dedicated to the terminal device.

507, MN#1 sends an SN release confirmation message to the SN.

Specifically, steps 505 to 507 can be referred to the descriptions of steps 405 to 407 in FIG. 11, and for brevity, details are not repeated here.

508: The terminal device sends a resume request (resume request) to MN#2, which is used to request to resume from the RRC deactivated state to the RRC connected state. Optionally, the recovery request may carry related information about whether the SN can be recovered, which is used to assist MN#2 in determining whether the recovery request can be sent to the SN.

509, MN#2 requests context from MN#1.

510. MN#1 sends the context of the terminal device on the MN side to MN#2.

Specifically, steps 509 and 510 can be referred to 306 and 307 in FIG. 10, and for the sake of brevity, details are not repeated here.

Optionally, MN#1 may notify MN#2 that the suspended SN has been released.

511. MN#2 sends configuration information to the terminal device.

FIG. 13 is a schematic flowchart of another admission control method from the perspective of device interaction, in which the primary base station that configures the terminal device to enter the RRC deactivated state is the same as the primary base station that the terminal device requests to recover, such as both It is MN#1. It should be understood that FIG. 13 shows the steps or operations of the admission control method, but these steps or operations are only examples, and the embodiment of the present application may also perform other operations or variations of each operation in FIG. 13. In addition, the various steps in FIG. 13 may be performed in a different order from that presented in FIG. 13, and it is possible that not all operations in FIG. 13 are to be performed.

601, MN#1 determines to configure the terminal device in the RRC deactivated state.

602. MN#1 sends an RRC connection release message to the terminal device, which is used to configure the terminal device in the RRC deactivated state.

603. MN#1 sends a request message to the SN, which is used to inform the SN that the terminal device has entered the RRC deactivated state and request to suspend the SN.

604. The SN sends an acknowledgement (acknowledge, ACK) in response to the request message in step 603 to MN#1.

Specifically, steps 601 to 604 may refer to steps 201 to 204 in FIG. 9, and for brevity, details are not repeated here.

605, SN informs MN#1 of its own load information.

Optionally, the SN can periodically send load information to MN#1. Or, the SN can send load information to MN#1 based on an event trigger. As an example, the specific event may be sending updated load information to MN#1 when the load information changes. Where the load information changes, it can be a change from a low load to a high load, or a change from a high load to a low load. As another example, the load information may be a quantified numerical interval, or a simple level indicator (for example, high, medium, low), etc., which is not limited in the embodiment of the present application.

606: The terminal device sends a recovery request to MN#1 for requesting to recover from the RRC deactivated state to the RRC connected state. Optionally, the recovery request may carry related information about whether the SN can be recovered, which is used to assist MN#1 in determining whether the recovery request can be sent to the SN.

607, MN#1 judges whether it is overloaded according to the SN load information received in 605.

Optionally, step 607 may be performed after step 606, that is, after receiving the recovery request from the terminal device, the MN determines whether to send the SN recovery request message or the SN release request message to the SN based on the load information of the SN.

Specifically, when it is determined that the SN is not overloaded, step 608a and step 609a are executed, and the RRC connection state of the terminal device with MN#1 and SN will be restored.

608a, MN#1 sends an SN recovery request to the SN.

609a, SN sends SN recovery confirmation to MN#1.

Specifically, steps 608a and 609a can refer to the process of restoring SN in the prior art, which will not be described in detail here.

When it is determined that the SN is overloaded, the MN can actively trigger the SN release process, that is, perform step 608b and step 609b.

608b, MN#1 sends an SN release request to the SN to request the release of the SN. If the SN is released, the SN cannot continue to provide services for the terminal device. Specifically, the SN can release the first resource dedicated to the terminal device. Specifically, the first resource can be referred to the description in FIG. 8. For brevity, details are not repeated here.

In the embodiment of this application, MN#1 may release the second resource when or after sending the SN release request to the SN. The second resource is a resource dedicated to the terminal device on the interface between the MN and the SN. Specifically, the second resource can be referred to the description in FIG. 8. For brevity, details are not repeated here.

609b, SN sends SN release confirmation to MN#1.

Optionally, when the SN side terminal device context is not included in the ACK, the SN release confirmation may include the SN side terminal device context.

610. MN#1 sends configuration information to the terminal device.

Therefore, in the dual-connected network architecture of the embodiment of the present application, when the terminal device enters the deactivated state, the secondary base station sends its own load information to the primary base station, and the primary base station determines that the secondary base station is overloaded and cannot continue to serve as the terminal device. In the case of SN, actively send an SN release request message to the SN to instruct to release the SN, so that the SN does not need to continue to serve the terminal device. Based on this, the embodiment of the present application introduces an admission control mechanism in the recovery process of the secondary base station SN, so that the release of the secondary base station SN can be completed when the secondary base station SN cannot be successfully recovered.

14 is a schematic flowchart of another admission control method from the perspective of device interaction, in which the primary base station (for example, MN#1) that configures the terminal device to enter the RRC deactivated state, and the terminal device request recovery The main base station (such as MN#2) is different. It should be understood that FIG. 14 shows the steps or operations of the admission control method, but these steps or operations are only examples, and the embodiment of the present application may also perform other operations or variations of each operation in FIG. 14. In addition, the various steps in FIG. 14 may be performed in a different order from that presented in FIG. 14, and it is possible that not all operations in FIG. 14 are to be performed.

701. MN#1 determines to configure the terminal device in the RRC deactivated state.

702. MN#1 sends an RRC connection release message to the terminal device, which is used to configure the terminal device in the RRC deactivated state.

703. MN#1 sends a request message to the SN, which is used to inform the SN that the terminal device has entered the RRC deactivated state and request to suspend the SN.

704. The SN sends an acknowledgement (acknowledge, ACK) in response to the request message in step 703 to MN#1.

Specifically, steps 701 to 704 can be referred to steps 201 to 204 in FIG. 9, for the sake of brevity, details are not repeated here.

705. SN informs MN#1 of its own load information.

Specifically, for step 705, refer to the description of step 605 in FIG. 13, and for brevity, details are not repeated here.

706: The terminal device sends a recovery request to MN#2 for requesting to recover from the RRC deactivated state to the RRC connected state. Optionally, the recovery request may carry related information about whether the SN can be recovered, which is used to assist MN#2 in determining whether the recovery request can be sent to the SN.

707, MN#2 requests context from MN#1.

708, MN#1 judges whether it is overloaded according to the SN load information received in 705.

Specifically, when it is determined that the SN is not overloaded, steps 709a to 711a are executed, and the RRC connection state of the terminal device with MN#1 and SN will be restored.

709a, MN#1 sends the terminal device context to MN#2.

710a, MN#2 sends an SN recovery request to the SN.

711a, SN sends SN recovery confirmation to MN#2.

When it is determined that the SN is overloaded, the MN can actively trigger the SN release process, that is, perform step 710b and step 711b.

710b, MN#1 sends an SN release request to the SN to request the release of the SN.

711b, SN sends SN release confirmation to MN#1.

In some embodiments, steps 706 and 707 may be performed before 709b to 711b (or 709a to 711a). That is, when MN#2 requests a context from MN#1, MN#1 can determine that the terminal device requests to restore to the RRC connected state. At this time, MN#1 can judge whether SN is overloaded. If MN#1 determines that the SN is overloaded, it actively triggers the SN release process, that is, steps 709b to 711b are executed. If the SN is not overloaded, steps 709a to 711a are executed.

In some embodiments, steps 706 and 707 may be performed after 709b to 711b. That is, when MN#1 determines that the SN is overloaded, it will actively trigger the SN release process, that is, execute 710b and step 711b. After that, if MN#2 requests context from MN#1, MN#1 can execute 709b.

709b, MN#1 sends the terminal device context to MN#2. Optionally, at this time, MN#1 may also notify MN#2 that the suspended SN has been released. Optionally, a cause value can be carried in it, which indicates that the SN is overloaded.

Specifically, for 710b and 711b, refer to the description of steps 608b and 609b in FIG. 13, for the sake of brevity, details are not repeated here.

712. MN#1 sends configuration information to the terminal device.

Figure 15 is a schematic flow chart of another admission control method from the perspective of device interaction, where the primary base station that configures the terminal device to enter the RRC deactivated state is the same as the primary base station that the terminal device requests to recover, such as both It is MN#1. It should be understood that FIG. 15 shows the steps or operations of the admission control method, but these steps or operations are only examples, and the embodiment of the present application may also perform other operations or variations of each operation in FIG. 15. In addition, the various steps in FIG. 15 may be performed in a different order from that presented in FIG. 15, and it is possible that not all operations in FIG. 15 are to be performed.

801. MN#1 determines to configure the terminal device in the RRC deactivated state.

802. MN#1 sends an RRC connection release message to the terminal device, which is used to configure the terminal device in the RRC deactivated state.

803. MN#1 sends a request message to the SN, which is used to inform the SN that the terminal device has entered the RRC deactivated state and request to suspend the SN.

804. The SN sends an acknowledgement (acknowledge, ACK) in response to the request message in step 803 to MN#1.

Specifically, steps 801 to 804 can be referred to steps 201 to 204 in FIG. 9, for the sake of brevity, details are not repeated here.

805. The terminal device sends a resume request (resume request) to MN#1, which is used to request to resume from the RRC deactivated state to the RRC connected state. Optionally, the recovery request may carry related information about whether the SN can be recovered, which is used to assist MN#1 in determining whether the recovery request can be sent to the SN.

806. MN#1 sends configuration information to the terminal device.

Optionally, the configuration information is used to configure the terminal device to establish an MCG RLC bearer, and associate the above MCG RLC bearer with the PDU session/QoS flow carried on the SN. Optionally, MN#1 is based on the mapping relationship between the PDU session/QoS flow carried by the secondary base station SN in the terminal device context received in step 804 and the data radio bearer DRB, without changing the above mapping relationship, and establishes a link for the above DRB. A corresponding MCG RLC bearer, and is associated with the above DRB identifier. It can be understood that the effect achieved by the above approach is to retain the mapping relationship between the PDU session/QoS flow carried by the SN and the DRB, and replace the SCG RLC bearer associated with the original DRB with the MCG RLC bearer. In the downstream direction, the PDU session/QoS data carried by the original SN still passes through the data transmission channel between NG-U and SN, and is processed by SN's SDAP and PDCP. The difference is that the above-mentioned data processed through SN and MN#1 The interface between them is further sent to the terminal device through the MCG RLC bearer. The upstream direction is similar.

807. MN#1 sends an SN recovery instruction to the SN, which is used to instruct the SN to resume service to the terminal device.

Optionally, the recovery indication is also used to instruct the SN to start the PDU session/QoS flow carried on the SN and the corresponding SDAP and PDCP uplink and downlink data transmission. Optionally, the recovery indication message also includes the mapping relationship between the PDU session/QoS flow and the MCG RLC bearer carried on the SN. Optionally, the recovery indication message also includes transport layer address information used for MN#1 to receive downlink data to be carried on the MCG RLC bearer.

808. The SN sends an SN recovery response, such as an SN recovery confirmation message, to MN#1. Optionally, the recovery confirmation message further includes the transport layer address information used for the SN to receive the uplink data that will carry the MCG RLC bearer. Optionally, the recovery confirmation message also includes the configuration of the SCG, which is used for the terminal device to update the configuration on the SN side.

Optionally, 809, MN#1 sends the configuration of the SCG received from the SN to the terminal device for the terminal device to update the configuration on the SN side.

Therefore, in the dual-connection network architecture in the embodiment of the present application, when the terminal device enters the deactivated state and resumes the RRC connection, the primary base station MN only retains the SDAP and PDCP processing on the secondary base station SN, and does not use the secondary base station SN. Instead, it allocates physical wireless transmission resources on the primary base station MN (such as MCG RLC bearer) for all the PDU session/QoS flow carried on the SN, thereby reducing the recovery on the secondary base station SN. The overhead of the terminal equipment service ensures that the secondary base station SN can resume the service to the terminal equipment. Based on this, the embodiment of the present application introduces the process of reconfiguring the SCG RLC bearer into the MCG RLC bearer during the process of the terminal device resuming the DC operation, thereby ensuring that the secondary base station SN can recover successfully. In addition, a reconfiguration operation in the recovery process is introduced, so that the secondary base station SN can complete the configuration update on the secondary base station SN based on its own situation (for example, load).

16 is a schematic flowchart of another admission control method from the perspective of device interaction, in which the primary base station (such as MN#1) that configures the terminal device to enter the RRC deactivated state, and the terminal device request recovery The main base station (such as MN#2) is different. It should be understood that FIG. 16 shows the steps or operations of the admission control method, but these steps or operations are only examples, and the embodiment of the present application may also perform other operations or variations of each operation in FIG. 16. In addition, the steps in FIG. 16 may be performed in a different order from that presented in FIG. 16, and it is possible that not all the operations in FIG. 16 are to be performed.

901. MN#1 determines to configure the terminal device in the RRC deactivated state.

902. MN#1 sends an RRC connection release message to the terminal device, which is used to configure the terminal device in an RRC deactivated state.

903. MN#1 sends a request message to the SN, which is used to inform the SN that the terminal device has entered the RRC deactivated state and request to suspend the SN.

904. The SN sends an acknowledgement (acknowledge, ACK) in response to the request message in step 903 to MN#1.

Specifically, steps 901 to 904 can be referred to steps 201 to 204 in FIG. 9, for the sake of brevity, details are not repeated here.

905: The terminal device sends a resume request (resume request) to MN#2, which is used to request to resume from the RRC deactivated state to the RRC connected state. Optionally, the recovery request may carry related information about whether the SN can be recovered, which is used to assist MN#2 in determining whether the recovery request can be sent to the SN.

906, MN#2 requests context from MN#1.

907. MN#1 sends the context of the terminal device on the MN side to MN#2.

Specifically, steps 906 and 907 may refer to steps 306 and 307 in FIG. 10, and for the sake of brevity, details are not repeated here.

Optionally, MN#1 may notify MN#2 of the identification information of the suspended SN and the identification allocated by the SN for the terminal device. As an example, when the terminal device is a UE, the identification may be UE XnAP ID.

908, MN#2 sends configuration information to the terminal device.

Here, for the configuration information, reference may be made to the description of the configuration information in step 806 in FIG. 15. For the sake of brevity, details are not repeated here.

909. MN#2 sends an SN recovery instruction to the SN, which is used to instruct the SN to resume service to the terminal device. For the SN recovery instruction here, reference may be made to the description of the SN recovery instruction in step 807 in FIG. 15. For brevity, details are not repeated here. Optionally, the SN recovery instruction message further includes an identifier assigned by the SN to the terminal device, which is used by the SN to identify the terminal device. As an example, when the terminal device is a UE, the identifier may be the UE XnAP ID.

910. The SN sends an SN recovery response, such as an SN recovery confirmation message, to MN#2. Here, the configuration information can refer to the description of the SN recovery confirmation message in step 807 in FIG. 15, for the sake of brevity, it will not be repeated here.

Optionally, 911, MN#2 sends the configuration of the SCG received from the SN to the terminal device for the terminal device to update the configuration on the SN side.

Therefore, in the embodiment of the present application, in the dual-connection network architecture, when the terminal device enters the deactivated state and resumes the RRC connection, the primary base station MN only retains the SDAP and PDCP processing on the secondary base station SN, and does not use the secondary base station SN. Instead, it allocates physical wireless transmission resources on the primary base station MN (such as MCG RLC bearer) for all the PDU session/QoS flow carried on the SN, thereby reducing the recovery on the secondary base station SN. The overhead of the terminal equipment service ensures that the secondary base station SN can resume the service to the terminal equipment. Based on this, the embodiment of the present application introduces the process of reconfiguring the SCG RLC bearer into the MCG RLC bearer during the process of the terminal device resuming the DC operation, thereby ensuring that the secondary base station SN can recover successfully. In addition, a reconfiguration operation in the recovery process is introduced, so that the secondary base station SN can complete the configuration update on the secondary base station SN based on its own conditions (such as load).

It is understandable that, in the foregoing embodiments of the present application, the method implemented by the primary base station can also be implemented by components (such as chips or circuits) that can be used in the primary base station, and the method implemented by the secondary base station can also be implemented by the secondary base station. Components (such as chips or circuits) are implemented.

According to the foregoing method, FIG. 17 is a schematic diagram of a wireless communication apparatus 1000 provided in an embodiment of this application.

Wherein, the device 1000 may be a secondary base station, or a chip or circuit, such as a chip or circuit that can be provided in the secondary base station. The device 1000 may include a processing unit 1010 (that is, an example of a processor) and a transceiver unit 1030.

Optionally, the transceiver unit 1030 may be implemented by a transceiver or a transceiver-related circuit or interface circuit.

Optionally, the device may further include a storage unit 1020. In one possible manner, the storage unit 1020 is used to store instructions. Optionally, the storage unit may also be used to store data or information. The storage unit 1020 may be realized by a memory.

In a possible design, the processing unit 1010 may be used to execute the instructions stored in the storage unit 1020, so that the apparatus 1000 implements the steps performed by the secondary base station in the foregoing method.

Further, the processing unit 1010, the storage unit 1020, and the transceiver unit 1030 can communicate with each other through internal connection paths to transfer control and/or data signals. For example, the storage unit 1020 is used to store a computer program, and the processing unit 1010 can be used to call and run the calculation program from the storage unit 1020 to control the transceiver unit 1030 to receive and/or send signals to complete the above method. The steps of the secondary base station. The storage unit 1020 may be integrated in the processing unit 1010, or may be provided separately from the processing unit 1010.

Optionally, if the apparatus 1000 is a communication device, the transceiver unit 1030 may include a receiver and a transmitter. The receiver and transmitter may be the same or different physical entities. When they are the same physical entity, they can be collectively called a transceiver.

Optionally, if the device 1000 is a chip or a circuit, the transceiver unit 1030 may include an input interface and an output interface.

As an implementation manner, the function of the transceiver unit 1030 may be implemented by a transceiver circuit or a dedicated chip for transceiver. The processing unit 1010 may be implemented by a dedicated processing chip, a processing circuit, a processing unit, or a general-purpose chip.

As another implementation manner, a general-purpose computer may be considered to implement the communication device (for example, a secondary base station) provided in the embodiment of the present application. That is, the program code for realizing the functions of the processing unit 1010 and the transceiver unit 1030 is stored in the storage unit 1020. The general processing unit implements the functions of the processing unit 1010 and the transceiver unit 1030 by executing the code in the storage unit 1020.

In an implementation manner, the processing unit 1010 is configured to determine to release a first resource reserved for a terminal device in a radio resource control RRC deactivated state, where the first resource is a resource dedicated to the terminal device.

The transceiver unit 1030 is configured to send a first message to the primary base station, where the first message is used to notify the secondary base station that the service to the terminal device cannot be restored.

Optionally, the transceiver unit 1030 is further configured to receive a first request from the primary base station, where the first request is used to request the secondary base station to resume service to the terminal device.

Optionally, the first message includes a cause value, and the cause value is used to identify that the secondary base station cannot restore service to the terminal device.

Optionally, the first resource includes at least one of the following:

Optionally, the transceiver unit 1030 is further configured to send the reserved context of the terminal device to the primary base station.

Optionally, the context includes at least one of the following information:

Optionally, the processor 1010 may specifically determine to release the first resource based on its own load.

Each unit in the above embodiments may also be referred to as a module or circuit or component.

Among them, the functions and actions of the modules or units in the device 1000 listed above are only exemplary. When the device 1000 is configured in or is a secondary base station, the modules or units in the device 1000 can be used to execute the above methods. Actions or processing procedures performed by the secondary base station.

For the concepts related to the technical solutions provided by the embodiments of the present application and related concepts, explanations, detailed descriptions, and other steps involved in the device 1000, please refer to the descriptions of these contents in the foregoing method or other embodiments, which are not repeated here.

According to the foregoing method, FIG. 18 is a schematic diagram of a wireless communication apparatus 1100 provided in an embodiment of this application.

Wherein, the device 1100 may be a main base station, or may be a chip or a circuit, for example, a chip or a circuit that may be set in an access device. The apparatus 1100 may include a processing unit 1110 (ie, an example of a processor) and a transceiver unit 1130.

Optionally, the device may further include a storage unit 1120. In one possible manner, the storage unit 1120 is used to store instructions. Optionally, the storage unit may also be used to store data or information. The storage unit 1120 may be realized by a memory.

In a possible design, the processing unit 1110 is used to execute the instructions stored in the storage unit 1120, so that the device 1100 implements the steps performed by the master base station (for example, MN#1 or MN#2) in the above method.

Further, the processing unit 1110, the storage unit 1120, and the transceiver unit 1130 may communicate with each other through internal connection paths, and transmit control and/or data signals. For example, the storage unit 1120 is used to store a computer program, and the processing unit 1110 can be used to call and run the calculation program from the storage unit 1120 to control the transceiver unit 1130 to receive and/or send signals to complete the above method. Steps for terminal equipment. The storage unit 1120 may be integrated in the processing unit 1110, or may be provided separately from the processing unit 1110.

Optionally, if the apparatus 1100 is a communication device (for example, a main base station), the transceiver unit 1130 includes a receiver and a transmitter. The receiver and transmitter may be the same or different physical entities. When they are the same physical entity, they can be collectively called a transceiver.

Optionally, if the device 1100 is a chip or a circuit, the transceiver unit 1130 includes an input interface and an output interface.

As an implementation manner, the function of the transceiver unit 1130 may be implemented by a transceiver circuit or a dedicated chip for transceiver. The processing unit 1110 may be implemented by a dedicated processing chip, a processing circuit, a processing unit, or a general-purpose chip.

As another implementation manner, a general-purpose computer may be considered to implement the communication device (for example, the main base station) provided in the embodiment of the present application. That is, the program code for realizing the functions of the processing unit 1110 and the transceiver unit 1130 is stored in the storage unit 1120, and the general processing unit implements the functions of the processing unit 1110 and the transceiver unit 1130 by executing the code in the storage unit 1120.

In an implementation manner, the transceiver unit 1130 is configured to receive a first message, and the first message is used to notify the secondary base station that the service to the terminal device cannot be restored, wherein the terminal device is in radio resource control RRC deactivation state.

The processing unit 1110 is configured to determine, according to the first message, that the secondary base station cannot restore the service to the terminal device.

Optionally, the transceiver unit 1130 is further configured to send a first request to the secondary base station, where the first request is used to request the secondary base station to resume service to the terminal device.

Optionally, the first message includes a cause value, and the cause value is used to identify that the secondary base station refuses to restore the service to the terminal device.

Optionally, the transceiver unit 1130 is further configured to receive the context of the terminal device by the primary base station from the secondary base station.

Optionally, the context includes at least one of the following information:

Optionally, the processing unit 1110 is further configured to release a reserved second resource by the primary base station, where the second resource is a resource dedicated to the terminal device on the interface between the primary base station and the secondary base station.

Optionally, the processing unit 1110 is further configured for the primary base station to establish an NG-U tunnel for carrying quality of service QoS flows/packet data unit PDU sessions, wherein, before releasing the second resource, the QoS flow/ The PDU session is carried on the NG-U tunnel of the secondary base station.

Optionally, the transceiver unit 1130 is further configured to send a second message to the terminal device, where the second message is used to notify the terminal device to release the configuration of the secondary base station, where the configuration of the secondary base station includes At least one of SCG configuration, measurement information configured by the secondary base station, and power configuration information.

The functions and actions of the modules or units in the device 1100 listed above are only exemplary. When the device 1100 is configured in or is a master base station, the modules or units in the device 1100 can be used to execute the above methods. Each action or processing procedure executed by the primary base station (for example, MN#1 or MN#2), here, in order to avoid redundant description, detailed descriptions thereof are omitted.

For the concepts related to the technical solutions provided by the embodiments of the present application and related concepts, explanations, detailed descriptions, and other steps involved in the device 1100, please refer to the descriptions of these contents in the foregoing method or other embodiments, which are not repeated here.

FIG. 19 is a schematic structural diagram of a terminal device 1200 provided by this application. The terminal device 1200 can perform the actions performed by the terminal device in the foregoing method embodiments.

For ease of description, FIG. 19 only shows the main components of the terminal device. As shown in FIG. 19, the terminal device 1200 includes a processor, a memory, a control circuit, an antenna, and an input and output device.

The processor is mainly used to process the communication protocol and communication data, and to control the entire terminal device, execute the software program, and process the data of the software program, for example, to support the terminal device to execute the above-mentioned transmission precoding matrix instruction method embodiment The described action. The memory is mainly used to store software programs and data, for example, to store the codebook described in the above embodiments. The control circuit is mainly used for the conversion of baseband signals and radio frequency signals and the processing of radio frequency signals. The control circuit and the antenna together can also be called a transceiver, which is mainly used to send and receive radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, and keyboards, are mainly used to receive data input by users and output data to users.

When the terminal device is turned on, the processor can read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor performs baseband processing on the data to be sent and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then sends the radio frequency signal to the outside in the form of electromagnetic waves through the antenna. When data is sent to the terminal device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data.

Those skilled in the art can understand that, for ease of description, FIG. 19 only shows a memory and a processor. In actual terminal devices, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, etc., which is not limited in the embodiment of the present application.

For example, the processor may include a baseband processor and a central processing unit. The baseband processor is mainly used to process communication protocols and communication data. The central processing unit is mainly used to control the entire terminal device, execute software programs, and process software programs. data. The processor in FIG. 19 integrates the functions of the baseband processor and the central processing unit. Those skilled in the art can understand that the baseband processor and the central processing unit may also be independent processors and are interconnected by technologies such as buses. Those skilled in the art can understand that the terminal device may include multiple baseband processors to adapt to different network standards, the terminal device may include multiple central processors to enhance its processing capabilities, and various components of the terminal device may be connected through various buses. The baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit can also be expressed as a central processing circuit or a central processing chip. The function of processing the communication protocol and communication data can be built in the processor, or can be stored in the storage unit in the form of a software program, and the processor executes the software program to realize the baseband processing function.

Exemplarily, in the embodiment of the present application, the antenna and control circuit with the transceiver function may be regarded as the transceiver unit 1210 of the terminal device 1200, and the processor with the processing function may be regarded as the processing unit 1220 of the terminal device 1200. As shown in FIG. 19, the terminal device 1200 includes a transceiver unit 1210 and a processing unit 1220. The transceiver unit may also be referred to as a transceiver, a transceiver, a transceiver, and so on. Optionally, the device for implementing the receiving function in the transceiver unit 1210 can be regarded as the receiving unit, and the device for implementing the sending function in the transceiver unit 1210 as the sending unit, that is, the transceiver unit includes a receiving unit and a sending unit. Exemplarily, the receiving unit may also be called a receiver, a receiver, a receiving circuit, etc., and the sending unit may be called a transmitter, a transmitter, or a transmitting circuit, etc.

FIG. 20 is a schematic structural diagram of a network device 1300 provided by an embodiment of the application, which may be used to implement the function of an access device (for example, a primary base station or a secondary base station) in the foregoing method. The network equipment 1300 includes one or more radio frequency units, such as a remote radio unit (RRU) 1310 and one or more baseband units (BBU) (also referred to as digital units, digital units, DU) 1320. The RRU 1310 may be called a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, etc., and it may include at least one antenna 1311 and a radio frequency unit 1312. The RRU 1310 part is mainly used for receiving and sending of radio frequency signals and conversion of radio frequency signals and baseband signals, for example, for sending the signaling messages described in the foregoing embodiments to terminal equipment. The BBU 1320 part is mainly used for baseband processing, control of base stations, and so on. The RRU 1310 and the BBU 1320 may be physically set together, or may be physically separated, that is, a distributed base station.

The BBU 1320 is the control center of the base station, and may also be called a processing unit, which is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, and spreading. For example, the BBU (processing unit) 1320 may be used to control the base station 40 to execute the operation procedure of the network device in the foregoing method embodiment.

In an example, the BBU 1320 may be composed of one or more single boards, and multiple single boards may jointly support a radio access network of a single access standard (such as an LTE system or a 5G system), and may also support different connections. Enter the standard wireless access network. The BBU 1320 further includes a memory 1321 and a processor 1322. The memory 1321 is used to store necessary instructions and data. For example, the memory 1321 stores the codebook in the above-mentioned embodiment. The processor 1322 is used to control the base station to perform necessary actions, for example, to control the base station to execute the operation procedure of the network device in the foregoing method embodiment. The memory 1321 and the processor 1322 may serve one or more boards. In other words, the memory and the processor can be set separately on each board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits can be provided on each board.

In a possible implementation manner, with the development of system-on-chip (SoC) technology, all or part of the functions of part 1320 and part 1310 can be realized by SoC technology, for example, a base station function chip To achieve, the base station function chip integrates a processor, a memory, an antenna interface and other devices, the program of the base station related functions is stored in the memory, and the processor executes the program to realize the relevant functions of the base station. Optionally, the base station function chip can also read a memory external to the chip to implement related functions of the base station.

It should be understood that the structure of the network device illustrated in FIG. 20 is only a possible form, and should not constitute any limitation in the embodiment of the present application. This application does not exclude the possibility of other base station structures that may appear in the future.

According to the method provided in the embodiment of the present application, the embodiment of the present application also provides a communication system, which includes the aforementioned primary base station and secondary base station. Further, the communication system may also include the aforementioned terminal equipment.

It should be understood that, in the embodiment of the present application, the processor may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), and dedicated integration Circuit (application specific integrated circuit, ASIC), ready-made programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.

It should also be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electronic Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of random access memory (RAM) are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (DRAM), and synchronous dynamic random access memory (DRAM). Access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory Take memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).

The foregoing embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented by software, the above-mentioned embodiments may be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server or data center via wired (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that includes one or more sets of available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium. The semiconductor medium may be a solid state drive.

An embodiment of the present application also provides a wireless communication system, which includes the above-mentioned primary base station and secondary base station. Further, the above-mentioned terminal device may also be included in the system.

The embodiments of the present application also provide a computer-readable medium on which a computer program is stored, and when the computer program is executed by a computer, the steps performed by the primary base station or the steps performed by the secondary base station in any of the foregoing embodiments are implemented.

The embodiments of the present application also provide a computer program product, which, when executed by a computer, realizes the steps performed by the primary base station or the steps performed by the secondary base station in any of the foregoing embodiments.

The embodiment of the present application also provides a system chip, which includes a communication unit and a processing unit. The processing unit may be a processor, for example. The communication unit may be, for example, an input/output interface, a pin, or a circuit. The processing unit can execute computer instructions so that the chip in the communication device executes the steps performed by the primary base station or the steps performed by the secondary base station provided in the above embodiments of the present application.

Optionally, the computer instructions are stored in a storage unit.

The various embodiments in this application can be used independently or in combination, which is not limited here.

In addition, various aspects or features of the present application can be implemented as methods, devices, or products using standard programming and/or engineering techniques. The term "article of manufacture" as used in this application encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (for example, hard disks, floppy disks, or tapes, etc.), optical disks (for example, compact discs (CDs), digital versatile discs (digital versatile discs, DVDs) Etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.). In addition, various storage media described herein may represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.

It should be understood that in the embodiments shown below, the first and the second are only to facilitate the distinction between different objects, and should not constitute any limitation to the application. For example, distinguish different messages, different requests, etc.

It should also be understood that in the embodiments shown below, "pre-acquisition" may include being indicated by network device signaling or pre-defined, for example, protocol definition. Among them, "pre-defined" can be realized by pre-saving corresponding codes, tables or other methods that can be used to indicate related information in the equipment (for example, including terminal equipment and network equipment). This application does not make any specific implementation methods. limited.

It should also be understood that the “saving” involved in the embodiments of the present application may refer to being stored in one or more memories. The one or more memories may be provided separately, or integrated in an encoder or decoder, a processor, or a communication device. The one or more memories may also be partly provided separately, and partly integrated in the decoder, processor, or communication device. The type of the memory may be any form of storage medium, which is not limited in this application.

It should also be understood that the "protocol" in the embodiments of the present application may refer to a standard protocol in the communication field, for example, it may include the LTE protocol, the NR protocol, and related protocols applied to future communication systems, which are not limited in this application.

It should also be understood that “and/or” describes the association relationship of the associated objects, which means that there can be three types of relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone. This situation. The character "/" generally indicates that the associated objects are in an "or" relationship. "At least one" refers to one or more than one; "At least one of A and B", similar to "A and/or B", describes the association relationship of associated objects, indicating that there can be three relationships, for example, A and B At least one of them can mean: A alone exists, A and B exist at the same time, and B exists alone.

A person of ordinary skill in the art may be aware that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the above-described system, device, and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program code .

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A method for admission control, characterized in that it includes:

The secondary base station determines to release the first resource reserved for the terminal device in a radio resource control RRC deactivated state, where the first resource is a resource dedicated to the terminal device;

The secondary base station sends a first message to the primary base station, where the first message is used to notify the secondary base station that the service to the terminal device cannot be restored.
The method according to claim 1, wherein before the secondary base station sends the first message to the primary base station, the method further comprises:

The secondary base station receives a first request from the primary base station, where the first request is used to request the secondary base station to resume service to the terminal device.
The method according to claim 1 or 2, wherein the first message includes a cause value, and the cause value is used to identify that the secondary base station cannot restore the service to the terminal device.
The method according to any one of claims 1-3, wherein the first resource includes at least one of the following:

The resources allocated or reserved by the secondary base station for the terminal device, the context of the terminal device reserved by the secondary base station, and the dedicated control plane of the terminal device on the interface between the secondary base station and the primary base station Connection and user plane connection, the dedicated user plane connection of the terminal device between the secondary base station and the core network.
The method according to any one of claims 1 to 4, further comprising:

The secondary base station sends the reserved context of the terminal device to the primary base station.
The method according to claim 4 or 5, wherein the context includes at least one of the following information:

The mapping relationship between the quality of service QoS flow carried by the secondary base station and the data radio bearer DRB, the secondary cell group SCG configuration, the configuration of the packet data convergence protocol PDCP carried by the secondary base station, and the PDCP context carried by the secondary base station, The security indication and security result of the PDU session/QoS flow of the packet data unit carried by the secondary base station, and the configuration of the service data adaptation protocol SDAP corresponding to the PDU session/QoS flow carried by the secondary base station.
The method according to any one of claims 1-6, wherein the determining by the secondary base station to release the first resource reserved for the terminal device in the radio resource control RRC deactivated state comprises:

The secondary base station determines to release the first resource based on its own load of the secondary base station.
A method for admission control, characterized in that it includes:

The primary base station receives a first message from the secondary base station, where the first message is used to notify the secondary base station that it cannot resume service to the terminal device in the RRC deactivated state;

According to the first message, the primary base station determines that the secondary base station cannot resume service to the terminal device.
The method according to claim 8, wherein before the primary base station receives the first message from the secondary base station, the method further comprises:

The primary base station sends a first request to the secondary base station, where the first request is used to request the secondary base station to resume service to the terminal device.
The method according to claim 8 or 9, wherein the first message includes a cause value, and the cause value is used to identify that the secondary base station refuses to restore the service to the terminal device.
The method according to any one of claims 8-10, further comprising:

The primary base station receives the context of the terminal device from the secondary base station.
The method according to claim 11, wherein the context includes at least one of the following information:

The mapping relationship between the QoS flow carried by the secondary base station and the data radio bearer DRB, the secondary cell group SCG configuration, the configuration of the packet data convergence protocol PDCP carried by the secondary base station, the PDCH context carried by the secondary base station, the The security indication and security result of the PDU session/QoS flow carried by the secondary base station, and the configuration of the SDAP corresponding to the PDU session/QoS flow carried by the secondary base station SN.
The method according to any one of claims 8-12, further comprising:

The primary base station releases a reserved second resource, where the second resource is a resource dedicated to the terminal device on an interface between the primary base station and the secondary base station.
The method according to any one of claims 8-13, further comprising:

The primary base station establishes an NG-U tunnel for carrying quality of service QoS flow/packet data unit PDU session, wherein, before releasing the second resource, the QoS flow/PDU session is carried on the NG-U tunnel of the secondary base station. -U tunnel.
The method according to any one of claims 8-14, further comprising:

The primary base station sends a second message to the terminal device, where the second message is used to notify the terminal device to release the configuration of the secondary base station, where the configuration of the secondary base station includes SCG configuration and secondary base station configuration At least one of measurement information and power configuration information.
A wireless communication device, characterized by comprising: a unit for executing the method according to any one of claims 1 to 7.
A wireless communication device, characterized by comprising: a unit for executing the method according to any one of claims 8 to 15.
A wireless communication system, characterized by comprising the wireless communication device according to claim 16 and the wireless communication device according to claim 17.
A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, and when the computer program runs on a computer,

Cause the computer to execute the method according to any one of claims 1 to 7, or

The computer is caused to execute the method according to any one of claims 8 to 15.
A chip system, characterized by comprising: a processor, used to call and run a computer program from a memory,

Enable the communication device installed with the chip system to execute the method according to any one of claims 1 to 7; or

The communication device installed with the chip system is caused to execute the method according to any one of claims 8 to 15.