CN114885436A

CN114885436A - Control plane configuration method, base station and communication system

Info

Publication number: CN114885436A
Application number: CN202110159967.4A
Authority: CN
Inventors: 许森; 信金灿; 袁晶晶; 宋谱; 孙震强
Original assignee: China Telecom Corp Ltd
Current assignee: China Telecom Corp Ltd
Priority date: 2021-02-05
Filing date: 2021-02-05
Publication date: 2022-08-09
Anticipated expiration: 2041-02-05
Also published as: CN114885436B

Abstract

The disclosure provides a control plane configuration method, a base station and a communication system. The control plane configuration method comprises the following steps: a DU entity of a base station sends a broadcast message for indicating access schemes and resources used by different services in a random access process; the DU entity selects a first CU-CP entity of a base station for the user terminal according to an access scheme and resources used by the user terminal in the random access process, and sends an RRC message sent by the user terminal to the first CU-CP entity; the first CU-CP entity sends the NAS information included in the RRC information to a corresponding first CN-CP entity of the core network, so that the first CN-CP entity can configure a control plane connection relation; after receiving first user configuration confirmation information sent by a first CN-CP entity, a first CU-CP entity sends first user service configuration information to a DU entity; the DU entity sends RRC reconfiguration information to the user terminal so that the user terminal can complete service configuration; and the DU entity sends the configuration completion message to the first CU-CP entity according to the RRC reconfiguration completion message sent by the user terminal.

Description

Control plane configuration method, base station and communication system

Technical Field

The present disclosure relates to the field of communications, and in particular, to a control plane configuration method, a base station, and a communication system.

Background

At present, the 5G network supports a structure of CU (Centralized Unit)/DU (distributed Unit) split and CP (Control Plane)/UP (User Plane) split. The 5G network splits the baseband Unit into RU (Radio Unit), DU and CU, decoupling these functions gives operators great flexibility because they can deploy RU, DU and CU in different locations as needed. A CU consists of one CP and one UP. The configuration is similar to a 4G wireless Network, so that the integration of a 5G Network and a 4G LTE (Long Term Evolution) Network is easier, and in addition, the configuration also provides flexibility for the configuration of a 5G RAN (Radio Access Network). As known from the standards and architectures of 5G mobile communication, 5G has an extremely important concept: separating the UP functionality from the CP functionality allows independent extensibility, evolution, and flexible deployment, e.g., in a centralized or distributed (remote) location.

In the current architecture, from the UE (User Equipment) perspective, the entire network has only one control plane entity, but there may be multiple User plane entities. From the perspective of the core network, the base station also has only one control plane entity, and the related control plane signaling is an entity of the control plane issued to the base station through the core network control plane and is sent to the user by the control plane entity of the base station. From the perspective of network deployment, the location requirements of different types of services for the control plane entity are also different, for example, for services of the internet of things, since the services are relatively insensitive to the delay, the services are generally deployed at a centralized point with a higher location, so that the centralization of management is achieved, and for services of the delay sensitive type, the control plane is generally deployed at a location closer to the DU.

For a user, the network is currently indicated in an MSG5 message of random access, and information about a selected core network, slice configuration, and the like, and there is only one control plane logical entity in a current wireless network architecture because the user cannot indicate information about the selected core network and slice to the network in a 5G network due to the reasons of being limited by the size of an SRB (Signaling Radio Bearer) and having no service, and the like.

Disclosure of Invention

The inventor has noted that there are some problems to be solved in the future 6G network, such as the problems and limitations of 5G network in design and deployment, and one of them is to solve the problem of delay. The solidified protocol structure becomes a bottleneck for achieving lower latency. For a 5G wireless network, a protocol structure is layered, all services need to be processed layer by layer, and each layer of processing has a delay, thereby forming a bottleneck of service transmission delay. To further shorten the time delay of the air interface, it is necessary to break the structure. In combination with the development trend of services, the problems of end-to-end micro-service design, separation of data and signaling and the like of the 6G wireless network need to be considered in design, and further the deployment efficiency and the cost of the whole network are improved.

Based on the above background, in order to more effectively support the coexistence demand of the same wireless network for multiple services, reduce the transmission delay of the services and signaling, and improve the management and control level of the network, the current 5G wireless network architecture still has the following defects:

the base station side supports only a single control plane and cannot deploy multiple user plane entities as needed: the control surface delay is also one of Key Performance Indicators (KPIs) of network importance, but different services have different requirements for the position of the control surface, and meanwhile, a suitable control surface cannot be selected for different service coexistence scenarios.

The core network control plane can only establish contact with the control plane of one base station: because the index of the base station is the base station identifier, signaling from the core network to the base station can only use the identifier for indexing, and only one base station entity can be seen from the core network side, which limits the sending of control plane signaling, and leads to the control plane not being capable of performing virtualization configuration.

The DU side cannot select a reasonable control plane for the user based on traffic selection: since service selection is usually performed in a Radio Resource Control (RRC) layer, when an initial access procedure includes a user from an idle (idle) state to a connected (connected) state and from an inactive (inactive) state to a connected state, the UE sends network and service selection information to the base station after the SRB1 is established, but before this, the base station side cannot know what service the user selects and select a correct Control plane node for the user.

Based on the above requirement and reason analysis, the current 3GPP (3rd Generation Partnership Project) NR (New Radio over the air interface) protocol cannot meet the requirement of the next Generation network for flexible and dynamic configuration of the control plane.

Accordingly, the present disclosure provides a control plane configuration scheme, which can flexibly and dynamically configure a control plane, and meet the requirements of network deployment and optimization.

According to a first aspect of the embodiments of the present disclosure, there is provided a control plane configuration method, performed by a base station, including: the DU entity of the base station sends broadcast information to indicate the access scheme and resources used by different services in the random access process; the DU entity selects a first CU-CP entity of the base station for the user terminal according to an access scheme and resources used by the user terminal in a random access process, and sends an RRC message sent by the user terminal to the first CU-CP entity; the first CU-CP entity sends the NAS information included in the RRC information to a corresponding first CN-CP entity of a core network, so that the first CN-CP entity can configure a corresponding control plane connection relation; after receiving first user configuration confirmation information sent by the first CN-CP entity, the first CU-CP entity sends first user service configuration information to the DU entity; the DU entity completes service configuration according to the first user service configuration information, and sends RRC reconfiguration information to the user terminal according to the RRC configuration information sent by the first CU-CP entity so that the user terminal completes service configuration; and the DU entity sends a configuration completion message to the first CU-CP entity according to the RRC reconfiguration completion message sent by the user terminal.

In some embodiments, the broadcast message includes at least one of a service identification list set, a random access scheme, a time domain resource for random access, a frequency domain resource for random access, and a code domain resource for random access.

In some embodiments, the selecting, by the DU entity, the first CU-CP entity of the base station for the user terminal according to an access scheme and resources used by the user terminal during a random access procedure includes: the DU entity determines the service type preferentially used by the user according to the access scheme and the resources used by the user terminal in the random access process; and the DU entity determines that the control plane entity selected by the user is the first CU-CP entity according to the service type and the pre-configuration information.

In some embodiments, the pre-configuration information comprises at least one of an identity of the first CU-CP entity, service set information supported by the first CU-CP entity, the service set information comprising at least one of PLMN list information, TAC list information and slice list information.

In some embodiments, the sending, by the DU entity, the RRC message sent by the user terminal to the first CU-CP entity includes: after receiving the RRC message sent by the user terminal, the DU entity packages the RRC message into RRC container information for transparent transmission, wherein the RRC message comprises slice and core network option information; the DU entity transmits user initial context configuration information including the RRC container information to the first CU-CP entity.

In some embodiments, the user initial context configuration information further includes at least one of an identity of the user terminal in the DU entity, a C-RNTI allocated for the user terminal, and an identity of a cell in which the user terminal resides.

In some embodiments, the sending, by the first CU-CP entity, the NAS message included in the RRC message to the corresponding core network first CN-CP entity includes: the first CU-CP entity determines a core network entity, a PLMN and slice information selected by a user according to RRC container information included in the user initial context configuration information; the first CU-CP entity determines that user configuration information needs to be sent to the first CN-CP entity according to the connection relation between the first CU-CP entity and a core network control plane entity; and the first CU-CP entity sends the user configuration information to the first CN-CP entity, wherein the user configuration information comprises NAS information carried in the RRC container information.

In some embodiments, the user configuration information further includes at least one of a user identification, a user selected PLMN, or a slice identification assigned by the first CU-CP entity.

In some embodiments, the first user configuration confirmation information includes at least one of a user identifier allocated by the first CN-CP entity, a radio network capability configuration of a user, encapsulated NAS information, partial control plane indication information, main control plane indication information, a slice identifier list, and a service type list configured for the user by the first CN-CP entity, and the service type list includes at least one of a PDU session identifier, a service QoS identifier, and service QoS configuration information.

In some embodiments, the sending, by the first CU-CP entity, the first user service configuration information to the DU entity after receiving the first user configuration confirmation information sent by the first CN-CP entity includes: the first CU-CP entity determines the control plane configuration of the first CN-CP entity according to the main control plane indication information and part of control plane indication information in the first user configuration confirmation information; the first CU-CP entity determines the services and the slices supported by the first CN-CP entity according to the slice identifiers and the service types in the first user configuration confirmation information; the first CU-CP entity judges whether the business supported by the first CN-CP entity can be accepted or not; and if the first CU-CP entity can accept at least one of the services supported by the first CN-CP entity, sending the first user service configuration information to the DU entity.

In some embodiments, the first user traffic configuration information includes at least one of a user identification assigned by the first CU-CP entity, a radio network capability configuration of a user, an incremental configuration indication, and a primary control plane entity indication.

In some embodiments, the first CU-CP entity sends a first user configuration rejection message to the first CN-CP entity if the first CU-CP entity cannot accommodate the services supported by the first CN-CP entity.

In some embodiments, the first user configuration rejection information comprises at least one of a user identity assigned by the first CU-CP entity, a user identity assigned by the first CN-CP entity, and a rejection reason.

In some embodiments, after receiving second user configuration confirmation information sent by a second CN-CP entity, a second CU-CP entity of the base station determines, according to main control plane indication information and part of control plane indication information in the second user configuration confirmation information, a control plane configuration of the second CN-CP entity; the second CU-CP entity determines the services and the slices supported by the second CN-CP entity according to the slice identifiers and the service types in the second user configuration confirmation information; the second CU-CP entity judges whether the services supported by the second CN-CP entity can be accepted or not; and if the second CU-CP entity can accept at least one of the services supported by the second CN-CP entity, sending second user service configuration information to the DU entity.

In some embodiments, the second user traffic configuration information comprises at least one of a subscriber identity assigned by the second CU-CP entity, a radio network capability configuration of a subscriber, and an incremental configuration indication.

In some embodiments, the second user configuration confirmation information includes at least one of a user identifier allocated by the second CN-CP entity, a radio network capability configuration of a user, partial control plane indication information, a slice identifier list, and a service type list configured for the user by the second CN-CP entity, where the service type list includes at least one of a PDU session identifier, a service QoS identifier, and service QoS configuration information.

In some embodiments, the second CU-CP entity sends a second user configuration rejection message to the second CN-CP entity if the second CN-CP entity cannot accommodate the service supported by the second CN-CP entity.

In some embodiments, the completing, by the DU entity, service configuration according to the first user service configuration information includes: after receiving the first user service configuration information sent by the first CU-CP entity, the DU entity records a user identifier distributed by the first CU-CP entity; the DU entity determines whether other control plane entities send user service configuration information according to the incremental configuration indication information in the first user service configuration information; if the incremental configuration indication information in the first user service configuration information indicates that no other control plane entity sends user service configuration information, the DU entity detects whether the service configured by the first CU-CP entity can be admitted; and if the DU entity can accommodate at least one of the services configured by the first CU-CP entity, sending a first service configuration success message to the first CU-CP entity.

In some embodiments, the first service provisioning success message includes at least one of a subscriber identity allocated by the DU entity, a subscriber identity allocated by the first CU-CP entity, a list of acceptable service identities allocated by the first CU-CP entity, and a list of unacceptable service identities allocated by the first CU-CP entity.

In some embodiments, if the DU entity cannot accommodate the service configured by the first CU-CP entity, service configuration failure information is sent to the first CU-CP entity.

In some embodiments, the service configuration failure information includes at least one of a user identifier allocated by the DU entity, a user identifier allocated by the first CU-CP entity, and a failure reason.

In some embodiments, if the incremental configuration indication information in the first user service configuration information indicates that the second CU-CP entity further sends user service configuration information, the DU entity starts a preconfigured timer to receive the second user service configuration information sent by the second CU-CP entity within a predetermined time range; after the DU entity receives second user service configuration information sent by the second CU-CP entity, recording a user identifier distributed by the second CU-CP entity; the DU entity detects whether the services configured by the first CU-CP entity and the second CU-CP entity can be admitted; and if the DU entity can accommodate at least one of the services configured by the first CU-CP entity and the second CU-CP entity, sending a second service configuration success message to the first CU-CP entity.

In some embodiments, the second service provisioning success message includes at least one of a subscriber identity assigned by the DU entity, a subscriber identity assigned by the first CU-CP entity, a subscriber identity assigned by the second CU-CP entity, a list of acceptable service identities assigned by the first CU-CP entity, a list of acceptable service identities assigned by the second CU-CP entity, a list of unacceptable service identities assigned by the first CU-CP entity, and a list of unacceptable service identities assigned by the second CU-CP entity.

In some embodiments, the completing, by the DU entity, service configuration according to the first user service configuration information includes: after receiving the second user service configuration information sent by the second CU-CP entity, the DU entity records the user identifier distributed by the second CU-CP entity; the DU entity determines that the first CU-CP entity sends user service configuration information according to increment configuration indication information in the second user service configuration information, and then the DU entity starts a preconfigured timer so as to receive the first user service configuration information sent by the first CU-CP entity within a preset time range; after the DU entity receives first user service configuration information sent by the first CU-CP entity, recording a user identifier distributed by the first CU-CP entity; the DU entity detects whether the services configured by the first CU-CP entity and the second CU-CP entity can be admitted; and if the DU entity can accommodate at least one of the services configured by the first CU-CP entity and the second CU-CP entity, sending a second service configuration success message to the first CU-CP entity.

In some embodiments, if the DU entity cannot accommodate the services configured by the first CU-CP entity and the second CU-CP entity, sending a service configuration failure message to the first CU-CP entity.

In some embodiments, the DU entity detects whether the traffic configured by the second CU-CP entity can be admitted; if the DU entity can accommodate at least one of the services configured by the second CU-CP entity, sending a service configuration success message to the second CU-CP entity; and if the DU entity can not accept the service configured by the second CU-CP entity, sending service configuration failure information to the second CU-CP entity.

In some embodiments, the second CU-CP entity performs, according to the service configuration success message sent by the DU entity, corresponding control plane configuration for the service admitted by the DU entity; and after receiving the service configuration failure information sent by the DU entity, the second CU-CP entity sends user configuration rejection information to the second CN-CP entity.

In some embodiments, the sending, by the DU entity, the RRC reconfiguration message to the user terminal according to the RRC configuration message sent by the first CU-CP entity includes: the first CU-CP entity generates a corresponding user RRC message according to the successfully configurable service type confirmed in the first service configuration success message or the second service configuration success message; the first CU-CP entity sends the generated user RRC message to the DU entity by using an RRC configuration message; and the DU entity sends RRC reconfiguration information to the user terminal according to the RRC configuration information.

In some embodiments, the RRC configuration message includes at least one of a user identifier allocated by the DU entity, a user identifier allocated by the first CU-CP entity, and a user RRC message, where the user RRC message includes at least one of a NAS message, service configuration information that a user can carry in the first CU-CP entity, AS layer encryption/decryption and integrity protection configuration of the user, and mobility parameter configuration information of the user.

In some embodiments, the first CU-CP entity sends user configuration rejection information to the first CN-CP entity after receiving the service configuration failure information sent by the DU entity.

In some embodiments, the sending, by the DU entity, the configuration complete message to the first CU-CP entity according to the RRC reconfiguration complete message sent by the user terminal includes: after receiving an RRC reconfiguration complete message sent by the user terminal, the DU entity sends a configuration complete message to the first CU-CP entity under the condition of only receiving first user service configuration information sent by the first CU-CP entity; and the first CU-CP entity sends the NAS feedback message carried in the RRC reconfiguration complete message to the first CN-CP entity.

In some embodiments, the DU entity determines whether service configuration failure information has been sent to the second CU-CP entity when receiving first user service configuration information sent by the first CU-CP entity and second user service configuration information sent by the second CU-CP entity; and if the service configuration failure information is not sent to the second CU-CP entity, the DU entity sends a configuration completion message to the first CU-CP entity and the second CU-CP entity.

In some embodiments, if service configuration failure information is sent to the second CU-CP entity, the DU entity sends a configuration complete message to the first CU-CP entity.

In some embodiments, the configuration complete message includes at least one of a ue id allocated by the DU entity, a ue id allocated by a base station control plane entity, and a NAS feedback message carried in an RRC reconfiguration complete message, where the NAS feedback message is sent only to the first CU-CP entity.

In some embodiments, a first CU-CP entity of the base station sends a first request to a preconfigured core network first CN-CP entity in an interface establishment procedure, where the first request includes at least one of an identifier of the base station, an identifier of the first CU-CP entity, and a service configuration information list of the base station, so that the first CN-CP entity determines a connection relationship with the first CU-CP entity according to the first request; and after receiving a first request response sent by the first CN-CP entity, the first CU-CP entity determines the connection relation with the first CN-CP entity according to the core network configurable list information included in the first request response.

In some embodiments, a second CU-CP entity of the base station sends a second request to a preconfigured core network second CN-CP entity in an interface establishment procedure, where the second request includes at least one of an identifier of the base station, an identifier of the second CU-CP entity, and a service configuration information list of the base station, so that the second CN-CP entity determines a connection relationship with the second CU-CP entity according to the second request; and after receiving a second request response sent by the second CN-CP entity, the second CU-CP entity determines the connection relation with the second CN-CP entity according to the core network configurable list information included in the second request response.

According to a second aspect of the embodiments of the present disclosure, there is provided a base station, including: a memory configured to store instructions; a processor coupled to the memory, the processor configured to perform a method implementing any of the embodiments described above based on instructions stored by the memory.

According to a third aspect of the embodiments of the present disclosure, there is provided a communication system including: a base station as in any one of the embodiments above; the user terminal is configured to determine an access scheme and resource information used in the random access process according to preset indication information and randomly access the base station after acquiring the access scheme and resource used in the random access process of different slices from a broadcast message sent by the base station; and the core network first CN-CP entity is configured to judge whether the service and the request supporting slice applied by the user terminal can be borne according to the service request message carried in the NAS message sent by the first CU-CP entity of the base station, and if the service and the request supporting slice applied by the user terminal can be borne, first user configuration confirmation information is sent to the first CU-CP entity.

In some embodiments, the communication system further comprises a core network second CN-CP entity, wherein: the first CN-CP entity is configured to send a service redistribution message to the second CN-CP entity if the first CN-CP entity can not bear at least one slice or service, and after receiving a service redistribution response message sent by the second CN-CP entity, the first user service configuration information is sent to the first CU-CP entity of the base station; and the second CN-CP entity is configured to determine whether all the allocated slice types can be supported according to the service reallocation message, if at least one of all the allocated slice types is supported, send a service reallocation response message for indicating that service reallocation is successful to the first CN-CP entity, and send second user service configuration information to a second CU-CP entity of the base station.

In some embodiments, the traffic re-assignment message comprises at least one of a user identity assigned by the first CN-CP entity, a list of PLMNs used by the user terminal, a list of slice types assigned to the second CN-CP entity, and a NAS message.

In some embodiments, the traffic re-assignment response message includes at least one of a subscriber identity assigned by the second CN-CP entity, and a list of slice types for which assignment fails, wherein each slice type includes at least one of a slice identity and a reason for assignment failure.

In some embodiments, the second CN-CP entity is configured to send a traffic re-allocation rejection message to the first CN-CP entity if all slice types are not supported.

In some embodiments, the service re-assignment rejection message includes at least one of a subscriber identity assigned by the second CN-CP entity and an assignment failure reason.

In some embodiments, the first CN-CP entity is configured to, after receiving a first request sent by the first CU-CP entity, store a base station identifier and a first CU-CP entity identifier carried in the first request, determine unique address identification information of the first CU-CP entity according to the base station identifier and the first CU-CP entity identifier, and determine a connection relationship between the first CN-CP entity and the first CU-CP entity according to the determined unique address identification information; and the first CU-CP entity is also configured to generate first core network configurable list information under the condition that the service configuration information list of the base station carried in the first request can be accepted, and send a first request response to the first CU-CP entity.

In some embodiments, the first core network configurable list information comprises at least one of PLMN identities accepted by the first CN-CP entity, accepted TAC information and accepted slice set information; the first request response includes at least one of identification information of the base station, a first CU-CP entity identification, a first CN-CP entity identification, and first core network configurable list information.

In some embodiments, the second CN-CP entity is configured to, after receiving a second request sent by the second CU-CP entity, store a base station identifier and a second CU-CP entity identifier carried in the second request, determine unique address identification information of the second CU-CP entity according to the base station identifier and the second CU-CP entity identifier, and determine a connection relationship between the second CN-CP entity and the second CU-CP entity according to the determined unique address identification information; and the second CU-CP entity is also configured to generate second core network configurable list information under the condition that the service configuration information list of the base station carried in the second request can be accepted, and send a second request response to the second CU-CP entity.

In some embodiments, the second core network configurable list information comprises a PLMN identity accepted by the second CN-CP entity, accepted TAC information and accepted slice set information; the second request response includes at least one of identification information of the base station, a second CU-CP entity identification, a second CN-CP entity identification, and second core network configurable list information.

According to a fourth aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, in which computer instructions are stored, and when executed by a processor, implement the method according to any one of the embodiments described above.

Other features of the present disclosure and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.

Drawings

In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and for those skilled in the art, other drawings can be obtained according to the drawings without inventive exercise.

Fig. 1 is a flowchart illustrating a control plane configuration method according to an embodiment of the present disclosure;

fig. 2 is a flowchart illustrating a control plane configuration method according to another embodiment of the disclosure;

fig. 3 is a schematic structural diagram of a base station according to an embodiment of the present disclosure;

fig. 4 is a schematic structural diagram of a communication system according to an embodiment of the present disclosure;

fig. 5 is a schematic structural diagram of a communication system according to another embodiment of the present disclosure;

fig. 6 is a flowchart illustrating a control plane configuration method according to another embodiment of the disclosure;

fig. 7 is a flowchart illustrating a control plane configuration method according to another embodiment of the disclosure;

fig. 8 is a flowchart illustrating a control plane configuration method according to another embodiment of the disclosure;

fig. 9 is a flowchart illustrating a control plane configuration method according to yet another embodiment of the present disclosure.

Detailed Description

The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.

The relative arrangement of the components and steps, the numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless specifically stated otherwise.

Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description.

Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.

In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.

Fig. 1 is a flowchart illustrating a control plane configuration method according to an embodiment of the present disclosure. In some embodiments, the following control plane configuration method flow is performed by the base station.

In step 101, a first CU-CP entity of a base station sends a first request to a pre-configured Core Network (Core Network, abbreviated as CN) first CN-CP entity in an interface establishment procedure, so that the first CN-CP entity determines a connection relationship with the first CU-CP entity according to the first request.

The first request includes at least one of:

-identification information of the base station: using fixed or variable-length bit information

-control plane entity identity of the base station: the entity identification and the base station identification form unique identification information of the control plane entity of the base station by adopting fixed or variable length bits

-base station service configuration information list information, wherein each base station service configuration information comprises at least one of:

PLMN identity: indicating PLMN (Public Land Mobile Network) information supported by the control plane entity

TAC information: information indicating a Tracking Area (TAC) supported by the control plane

Slice set information: including one or more slice ID information that can be used to index corresponding services

In some embodiments, the first CU-CP entity sends the first request through an interface establishment request or an interface modification request through an interface between the base station and the core network control plane according to the pre-configuration information. The pre-configuration information is configured by the network manager. The configuration information configures which core network control plane entities the first CU-CP entity needs to establish a corresponding connection with.

After receiving a first request sent by a first CU-CP entity, a first CN-CP entity stores a base station identifier and a first CU-CP entity identifier carried in the first request, determines unique address identification information of the first CU-CP entity according to the base station identifier and the first CU-CP entity identifier, and determines the connection relation between the first CN-CP entity and the first CU-CP entity according to the determined unique address identification information. And the first CN-CP entity generates first core network configurable list information under the condition that the first CN-CP entity can accept the service configuration information list of the base station carried in the first request, and sends a first request response to the first CU-CP entity.

In some embodiments, the first core network configurable list information comprises at least one of:

-acceptable PLMN identity: indicating PLMN information supported by the control plane entity

Acceptable TAC information: indicating TAC information supported by the control plane

Acceptable slice set information: including one or more slice ID information

In some embodiments, the first request response comprises at least one of:

-identification information of base stations

-control plane entity identity of base station

-identification information of a first CN-CP entity of the core network, such as GUAMI information

Core network configurable list information

In step 102, after receiving the first request response sent by the first CN-CP entity, the first CU-CP entity determines the connection relationship with the first CN-CP entity according to the core network configurable list information included in the first request response.

If the base station further includes its control plane entity, the connection relationship is also determined according to the flow of the above embodiment and the corresponding core network control plane entity. For example, the second CU-CP entity in the base station determines the connection relationship with the second CN-CP entity of the core network through the above-described embodiment procedure.

Fig. 2 is a flowchart illustrating a control plane configuration method according to another embodiment of the disclosure. In some embodiments, the following control plane configuration method flow is performed by the base station.

In step 201, the DU entity of the base station sends a broadcast message to indicate the access schemes and resources used by different services during the random access procedure.

In some embodiments, the broadcast message may include the following:

-set of service identity lists: optionally, one or more slice identifier lists, the slices using the same access resource configuration

-a random access scheme: optional values, in enumerated form, indicating the use of a random access scheme, e.g. two or four steps

Time domain resources for random access: an optional value, in the form of a bitmap, each bit indicating a slot in the time domain

Frequency domain resources for random access: selectable value, in the form of bitmap, each bit indicating physical resources of a certain granularity in the frequency domain

Code domain resources for random access: an optional value indicating the code domain configuration of the random access that can be used

After acquiring access schemes and resources used by different slices in the random access process from broadcast messages sent by the base station, the user terminal determines the access schemes and resource information used in the random access process according to the preset indication information and randomly accesses the base station. And the user terminal performs the operation according to the common random access mode when the selected service is not in any service set list.

In step 202, the DU entity selects a first CU-CP entity of the base station for the ue according to the access scheme and resources used by the ue during the random access procedure, and sends an RRC message sent by the ue to the first CU-CP entity.

In some embodiments, the DU entity determines the service type preferentially used by the user according to the access scheme and resources used by the user terminal in the random access procedure. The DU entity determines that the control plane entity selected by the user is the first CU-CP entity according to the service type and the pre-configuration information.

For example, the preconfigured information includes at least one of:

-identification information of the first CU-CP entity

-service set information supported by the first CU-CP entity, the service set information comprising at least one of:

PLMN list information

TAC List information

Slice set information

In some embodiments, after receiving the RRC message sent by the user terminal, the DU entity encapsulates the RRC message into RRC container (container) information for transparent transmission, where the RRC message includes slice and core network option information. The DU entity transmits user initial context configuration information including RRC container information to the first CU-CP entity.

For example, the user initial context configuration information includes at least one of:

the identity of the user terminal at the DU entity: for uniquely identifying the user in the interface between the base station DU entity and the first CU-CP entity of the base station

-C-RNTI allocated for the user terminal: this value is allocated by the base station DU entity

-identity of the user terminal camping on the cell: cell identification using user camping

-encapsulated user RRC message: RRC container encapsulation is employed.

In step 203, the first CU-CP entity sends a NAS (Non-access stratum) message included in the RRC message to the corresponding first CN-CP entity of the core network, so that the first CN-CP entity configures a corresponding control plane connection relationship.

In some embodiments, the first CU-CP entity determines the user selected core network entity, PLMN and slice information from the RRC container information included in the user initial context configuration information. And the first CU-CP entity determines that the user configuration information needs to be sent to the first CN-CP entity according to the connection relation between the first CU-CP entity and the core network control plane entity. And the first CU-CP entity sends the user configuration information to the first CN-CP entity, wherein the user configuration information comprises NAS information carried in the RRC container information.

For example, the user configuration information includes at least one of:

-subscriber identity assigned by the first CU-CP entity of the base station

-encapsulated NAS layer message: adopting NAS information carried in the encapsulated user RRC message

-user selected PLMN or slice identity

In step 204, the first CU-CP entity sends the first user service configuration information to the DU entity after receiving the first user configuration confirmation information sent by the first CN-CP entity.

In some embodiments, the first CN-CP entity of the core network determines whether the service and the requested supporting slice applied by the user terminal can be borne according to the service request message carried in the NAS message sent by the first CU-CP entity of the base station, and sends the first user configuration confirmation message to the first CU-CP entity if the service and the requested supporting slice applied by the user terminal can be borne.

In some embodiments, the first user configuration confirmation information comprises at least one of:

-subscriber identity assigned by a first CN-CP entity of the core network

-wireless network capability configuration of the user

-encapsulated NAS message: in the RRC Container mode, the NAS message includes the slice type configured for the user at all the core network control plane entities

-partial control plane indication message: adopting a Boolean type, if yes, indicating the first CN-CP entity of the core network only undertakes part of control plane information of the user, if no, indicating that all control plane configuration information of the user is positioned at the first CN-CP entity of the core network

-the primary control plane indicates: the first CN-CP entity of the core network is taken as a main control plane and is used for receiving NAS information by default

-slice identification list: including one or more slice identifiers

-a list of service types configured by the core network first CN-CP entity for the user, the list comprising at least one of:

identification of PDU sessions

QOS tag identification of the service: including uplink and downlink QOS identification of the service

QOS configuration information of the service: including uplink and downlink QOS configuration information for the service

In some embodiments, the first CU-CP entity determines the control plane configuration of the first CN-CP entity according to the main control plane indication information and the part of the control plane indication information in the first user configuration confirmation information. And the first CU-CP entity determines the services and the slices supported by the first CN-CP entity according to the slice identifier and the service type in the first user configuration confirmation information. The first CU-CP entity determines whether the services supported by the first CN-CP entity can be admitted. And if the first CU-CP entity can accommodate at least one of the services supported by the first CN-CP entity, sending the first user service configuration information to the DU entity.

For example, the first user service configuration information includes at least one of:

-subscriber identity assigned by the base station first CU-CP entity: uniquely determining the unique index information of the user between the first CU-CP entity of the base station and the DU entity of the base station together with the identity allocated by the DU entity of the base station

-wireless network capability configuration of the user

-incremental configuration indication: and the enumeration type indicates that a plurality of control plane entities send the same configuration information identifier.

-the master control plane entity indicates: and if so, the boolean value indicates that the first CU-CP entity of the base station is a main control plane entity and is used for configuring parameters such as basic NAS, mobility and the like, and the configuration of the remaining control planes is performed in an incremental configuration manner.

In some embodiments, the first CU-CP entity sends the first user configuration rejection message to the first CN-CP entity if the first CU-CP entity cannot accommodate the services supported by the first CN-CP entity.

For example, the first user configuration rejection information includes at least one of:

-subscriber identity assigned by a first CN-CP entity of the core network

Reason for rejection

In some embodiments, after receiving second user configuration confirmation information sent by a second CN-CP entity of a core network, a second CU-CP entity of a base station determines a control plane configuration of the second CN-CP entity according to main control plane indication information and part of control plane indication information in the second user configuration confirmation information. And the second CU-CP entity determines the services and the slices supported by the second CN-CP entity according to the slice identifier and the service type in the second user configuration confirmation information. The second CU-CP entity determines whether the services supported by the second CN-CP entity can be admitted. And if the second CU-CP entity can accommodate at least one of the services supported by the second CN-CP entity, sending the second user service configuration information to the DU entity.

For example, the second user service configuration information includes at least one of:

-subscriber identity assigned by the base station second CU-CP entity: uniquely determining the unique index information of the user between the second CU-CP entity of the base station and the DU entity of the base station together with the identity allocated by the DU entity of the base station

-wireless network capability configuration of the user

For example, the second user configuration confirmation information includes at least one of:

-subscriber identity allocated by a second CN-CP entity of the core network

-wireless network capability configuration of the user

-partial control plane indication message: adopting a Boolean type, if yes, indicating that the second CN-CP entity of the core network only bears the control plane information of the part of the user, and if no, indicating that all the control plane configuration information of the user is positioned at the second CN-CP entity of the core network

-slice identification list: including one or more slice identifiers

-a list of service types configured by the second CN-CP entity of the core network for the user, the list including at least one of the following:

identification of PDU Session

It should be noted here that the first CN-CP entity of the core network determines whether the service requested by the user terminal and the requested supporting slice can be carried according to the service request message carried in the NAS message sent by the first CU-CP entity of the base station. And if the at least one slice or service cannot be carried, the first CN-CP entity sends a service reallocation message to the second CN-CP entity.

And the second CN-CP entity determines whether all the distributed slice types can be supported or not according to the service redistribution message, and if at least one of all the slice types is supported, the second CN-CP entity sends a service redistribution response message for indicating successful service redistribution to the first CN-CP entity and sends the second user service configuration information to the second CU-CP entity of the base station.

And after receiving the service redistribution response message sent by the second CN-CP entity, the first CN-CP entity sends the first user service configuration information to the first CU-CP entity of the base station.

In some embodiments, the second CU-CP entity sends the second user configuration rejection message to the second CN-CP entity if the second CU-CP entity cannot accommodate the services supported by the second CN-CP entity.

In step 205, the DU entity completes service configuration according to the first user service configuration information, and sends an RRC reconfiguration message to the user terminal according to the RRC configuration message sent by the first CU-CP entity, so that the user terminal completes service configuration.

In some embodiments, after receiving the first user service configuration information sent by the first CU-CP entity, the DU entity records the user identifier allocated by the first CU-CP entity. And the DU entity determines whether other control plane entities send the user service configuration information according to the increment configuration indication information in the first user service configuration information. If the incremental configuration indication information in the first user service configuration information indicates that no other control plane entity sends the user service configuration information, the DU entity detects whether the service configured by the first CU-CP entity can be admitted. And if the DU entity can accommodate at least one of the services configured by the first CU-CP entity, sending a first service configuration success message to the first CU-CP entity.

For example, the first service provisioning success message includes the following:

the identity of the base station DU entity for this user: identities allocated between the DU entity and the base station control plane entity sending the message

-the identity allocated by the base station control plane entity for the user: user identification allocated to message sending destination control plane entity

-list of acceptable service identities assigned to this control plane: the part must be selected

Identification of the service: such as PDU Session identification

-list of unacceptable service identities assigned to this control plane: the part is optional

Identification of the service: such as PDU Session identification

Reason for failure

In some embodiments, if the DU entity cannot accommodate the service configured by the first CU-CP entity, the service configuration failure information is sent to the first CU-CP entity.

For example, the service configuration failure information includes at least one of the following:

Reason for rejection

In some embodiments, if the incremental configuration indication information in the first user service configuration information indicates that there is still the second CU-CP entity to send the user service configuration information, the DU entity starts a preconfigured timer to receive the second user service configuration information sent by the second CU-CP entity within a predetermined time range. And after the DU entity receives second user service configuration information sent by the second CU-CP entity, recording the user identification distributed by the second CU-CP entity. The DU entity detects whether the services configured by the first CU-CP entity and the second CU-CP entity can be admitted. And if the DU entity can accommodate at least one of the services configured by the first CU-CP entity and the second CU-CP entity, sending a second service configuration success message to the first CU-CP entity.

For example, the second service provisioning success message includes the following:

Identification of the service: such as PDU Session identification

Reason for failure

-list of acceptable other control plane allocated traffic identities: this part is optional for feedback to the primary control plane entity

Identification of the service: such as PDU Session identification

-list of unacceptable service identities assigned to this control plane: this part is optional for feedback to the primary control plane entity

Identification of the service: such as PDU Session identification

Reason for failure

In some embodiments, after receiving the second user service configuration information sent by the second CU-CP entity, the DU entity records the user identifier allocated by the second CU-CP entity. And the DU entity determines that the first CU-CP entity sends the user service configuration information according to the increment configuration indication information in the second user service configuration information, and then the DU entity starts a pre-configured timer so as to receive the first user service configuration information sent by the first CU-CP entity within a preset time range. And after the DU entity receives the first user service configuration information sent by the first CU-CP entity, recording the user identification distributed by the first CU-CP entity. The DU entity detects whether the services configured by the first CU-CP entity and the second CU-CP entity can be admitted. And if the DU entity can accommodate at least one of the services configured by the first CU-CP entity and the second CU-CP entity, sending a second service configuration success message to the first CU-CP entity.

In some embodiments, if the DU entity cannot accommodate the services configured by the first CU-CP entity and the second CU-CP entity, the service configuration failure information is sent to the first CU-CP entity.

In some embodiments, the DU entity also detects whether the services configured by the second CU-CP entity can be admitted. And if the DU entity can accommodate at least one of the services configured by the second CU-CP entity, sending a service configuration success message to the second CU-CP entity. And if the DU entity can not accommodate the service configured by the second CU-CP entity, sending the service configuration failure information to the second CU-CP entity.

In some embodiments, the second CU-CP entity performs corresponding control plane configuration for the service admitted by the DU entity according to the service configuration success message sent by the DU entity. And after receiving the service configuration failure information sent by the DU entity, the second CU-CP entity sends the user configuration rejection information to the second CN-CP entity.

In some embodiments, the first CU-CP entity generates a corresponding user RRC message according to the successfully configurable service type confirmed in the first service configuration success message or the second service configuration success message. The first CU-CP entity transmits the generated user RRC message to the DU entity using an RRC configuration message. And the DU entity sends RRC reconfiguration information to the user terminal according to the RRC configuration information.

For example, the RRC configuration message includes at least one of:

-encapsulating a user RRC message, the RRC reconfiguration message comprising at least one of:

NAS messages

Service configuration information that the user can carry in the first CU-CP entity of the base station

AS (Access Stratum) layer encryption/decryption and integrity protection configuration for a user

Mobility parameter configuration information of the user, including handover and measurement parameter information, etc

In some embodiments, the first CU-CP entity sends the user configuration rejection message to the first CN-CP entity after receiving the service configuration failure message sent by the DU entity.

In step 206, the DU entity sends a configuration complete message to the first CU-CP entity according to the RRC reconfiguration complete message sent by the user terminal.

In some embodiments, after receiving the RRC reconfiguration complete message sent by the user terminal, the DU entity sends a configuration complete message to the first CU-CP entity in case of receiving only the first user service configuration information sent by the first CU-CP entity. And the first CU-CP entity sends the NAS feedback message carried in the RRC reconfiguration complete message to the first CN-CP entity.

In some embodiments, the DU entity determines whether service configuration failure information has been sent to the second CU-CP entity in case of receiving first user service configuration information sent by the first CU-CP entity and second user service configuration information sent by the second CU-CP entity. And if the service configuration failure information is not sent to the second CU-CP entity, the DU entity sends a configuration completion message to the first CU-CP entity and the second CU-CP entity. And if the service configuration failure information is sent to the second CU-CP entity, the DU entity sends a configuration completion message to the first CU-CP entity.

For example, the configuration complete message includes at least one of:

-NAS feedback message: transmitting only to the first control plane entity of the base station

In some embodiments, after receiving the configuration completion message, the first CU-CP entity sends the NAS feedback message carried in the configuration completion message to the first CN-CP entity of the core network.

Fig. 3 is a schematic structural diagram of a base station according to an embodiment of the present disclosure. As shown in fig. 3, the base station includes a memory 31 and a processor 32.

The memory 31 is used for storing instructions, the processor 32 is coupled to the memory 31, and the processor 32 is configured to execute the method according to any one of fig. 1 to fig. 2 based on the instructions stored in the memory.

As shown in fig. 3, the base station further comprises a communication interface 33 for information interaction with other devices. Meanwhile, the base station also comprises a bus 34, and the processor 32, the communication interface 33 and the memory 31 are communicated with each other through the bus 34.

The memory 31 may comprise a high-speed RAM memory, and may also include a non-volatile memory (e.g., at least one disk memory). The memory 31 may also be a memory array. The storage 31 may also be partitioned and the blocks may be combined into virtual volumes according to certain rules.

Further, the processor 32 may be a central processing unit CPU, or may be an application specific integrated circuit ASIC, or one or more integrated circuits configured to implement embodiments of the present disclosure.

The present disclosure also relates to a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the instructions, when executed by a processor, implement a method according to any one of fig. 1 to 2.

Fig. 4 is a schematic structural diagram of a communication system according to an embodiment of the present disclosure. As shown in fig. 4, the communication system includes a base station 41, a user terminal 42, and a core network first CN-CP entity 43. The base station 41 is the base station according to any of the embodiments in fig. 3. The base station 41 includes therein a DU entity 411 and a first CU-CP entity 412.

The ue 42 is configured to, after acquiring the access schemes and resources used by different slices in the random access procedure from the broadcast message sent by the base station 41, determine the access schemes and resource information used in the random access procedure according to the preset indication information and randomly access the base station 41.

The core network first CN-CP entity 43 is configured to determine whether the service and the requested supporting slice requested by the user terminal can be carried according to the service request message carried in the NAS message sent by the first CU-CP entity 412, and send first user configuration confirmation information to the first CU-CP entity 412 if the service and the requested supporting slice requested by the user terminal can be carried.

In some embodiments, the first CN-CP entity 43 is configured to, after receiving the first request sent by the first CU-CP entity 412, store the base station identifier and the first CU-CP entity identifier carried in the first request, determine unique address identification information of the first CU-CP entity 412 according to the base station identifier and the first CU-CP entity identifier, and determine the connection relationship between the first CN-CP entity 43 and the first CU-CP entity 412 according to the determined unique address identification information. The first CN-CP entity 43 is further configured to generate first core network configurable list information if the service configuration information list of the base station carried in the first request can be accepted, and send a first request response to the first CU-CP entity 412.

Acceptable slice set information: including one or more slice ID information

In some embodiments, the first request response comprises at least one of:

-identification information of base stations

-first CU-CP entity identity of base station

Core network configurable list information

Fig. 5 is a schematic structural diagram of a communication system according to another embodiment of the present disclosure. Fig. 5 differs from fig. 4 in that in the embodiment shown in fig. 5 the communication system further comprises a core network second CN-CP entity 44.

The first CN-CP entity 43 is configured to send a traffic re-allocation message to the second CN-CP entity 44 if it cannot carry at least one slice or traffic.

In some embodiments, the traffic reallocation message includes at least one of:

-a subscriber identity assigned by a first CN-CP entity of the core network, which identity is subsequently used in conjunction with an identity assigned by a second CN-CP entity to identify different subscriber distinctions at the interface

PLMN list used by the user

-a list of slice types allocated to the control plane entity

User NAS message

The second CN-CP entity 44 is configured to determine whether all the allocated slice types can be supported according to the service re-allocation message, and if at least one of all the slice types is supported, send a service re-allocation response message indicating that the service re-allocation is successful to the first CN-CP entity 43, and send second user service configuration information to the second CU-CP entity 413 of the base station 41.

In some embodiments, the traffic re-allocation response message comprises at least one of:

-subscriber identity allocated by a second CN-CP entity of the core network

-assigning a list of failed slice types, each slice type comprising at least one of:

section identification

Reason for assignment failure

The first CN-CP entity 43 sends the first user service configuration information to the first CU-CP entity 412 of the base station 41 after receiving the service re-allocation response message sent by the second CN-CP entity 44.

In some embodiments, the second CN-CP entity 44 is configured to send a traffic re-allocation reject message to the first CN-CP entity 43 if all slice types are not supported.

For example, the service reallocation rejection message includes at least one of:

-subscriber identity allocated by a second CN-CP entity of the core network

Reasons for dispensing failure

In some embodiments, the second CN-CP entity 44 is configured to, after receiving the second request sent by the second CU-CP entity 413, store the base station identifier and the second CU-CP entity identifier carried in the second request, determine unique address identification information of the second CU-CP entity according to the base station identifier and the second CU-CP entity identifier, and determine the connection relationship between the second CN-CP entity 44 and the second CU-CP entity 413 according to the determined unique address identification information. The second CN-CP entity 44 is further configured to generate second core network configurable list information in case that the service configuration information list of the base station carried in the second request can be accepted, and send a second request response to the second CU-CP entity 413.

In some embodiments, the second core network configurable list information comprises at least one of:

Acceptable slice set information: including one or more slice ID information

In some embodiments, the second request response comprises at least one of:

-identification information of base stations

-second CU-CP entity identity of base station

-identification information of a second CN-CP entity of the core network, such as GUAMI information

Core network configurable list information

The present disclosure is illustrated below by specific examples.

The first embodiment is as follows:

the present embodiment describes a connection establishment procedure between two control plane entities of a core network and two control plane entities of a base station, where the control plane entities of the core network are CN-CP1 and CN-CP2, the control plane entities of the base station are CU-CP1 and CU-CP2, CN-CP1 and CU-CP1 both support only URLLC (Ultra-reliable and Low Latency Communication) services, and CN-CP2 and CU-CP2 both support only eMBB (enhanced Mobile broadband) services.

As shown in fig. 6, in step 601, the CU-CP1 entity determines an interface between the base station and the core network control plane through the pre-configuration information, and sends a first request message to the CN-CP1 entity through an interface establishment request or an interface modification request, where the pre-configuration information is configured by the network manager, and the configuration information configures which core network control plane entities the CU-CP1 entity needs to establish corresponding connections with. The first request information includes the following information:

-identification information of the base station: 36 bit length

-control plane entity identity of the base station: 6 bit length

-base station service configuration information list information comprising the following:

PLMN identity: PLMN1

TAC information: TAC1

Slice set information: slice1 is eMBB only

In step 602, after receiving the first request message sent by the CU-CP1 entity, the CN-CP1 entity stores the base station id and the control plane id information carried in the message, determines the unique address id information of the base station CU-CP1 entity according to the base station id and the control plane id information, and determines the connection relationship between the CN-CP1 entity and the CU-CP1 entity based on the address id information.

In step 603, the CN-CP1 entity determines whether the base station service configuration information list information is acceptable, and if so, generates core network configurable list information. The core network configurable list information includes the following:

-acceptable PLMN identity: PLMN1

Acceptable TAC information: TAC1

Acceptable slice set information: slice1

In step 604, the CN-CP1 entity generates first request response information and transmits the first request response information to the CU-CP1 entity through an interface setup or modify request response message, wherein the first request response information includes the following information:

-identification information of base stations

-control plane entity identity of base station

Identification information of CN-CP1 GUAMI as defined in TS38.413

Core network configurable list information

In step 605, after receiving the first request response message, the CU-CP1 entity determines configuration information that can be used with the CN-CP 1.

As shown in fig. 7, in step 701, the CU-CP2 entity determines, according to the pre-configuration information configured by the network manager, to send a second request message to the CN-CP2 entity through an interface between the base station and the core network control plane, where the CU-CP2 entity needs to establish a corresponding connection with which core network control plane entities. The second request information includes:

-identification information of the base station: 36 bit length

-control plane entity identity of the base station: 6 bit length

-the base station service configuration information list information comprises the following:

PLMN identity: PLMN1

TAC information: TAC1

Slice set information: slice2 is URLLC only

In step 702, after receiving the second request message sent by the CU-CP2 entity, the CN-CP2 entity stores the base station identifier and the control plane identifier information carried in the message, determines the unique address identifier information as the base station CU-CP2 entity according to the base station identifier and the control plane identifier information, and determines the connection relationship between the CN-CP2 entity and the CU-CP2 entity based on the address identifier information.

In step 703, the CN-CP2 entity determines whether the base station service configuration information list information is acceptable, and if so, generates core network configurable list information. The core network configurable list information comprises:

-acceptable PLMN identity: PLMN1

Acceptable TAC information: TAC1

Acceptable slice set information: slice2

In step 704, the CN-CP2 entity generates a second request response and sends it to the CU-CP2 entity, wherein the content of the second request response includes the following information:

-identification information of base stations

-control plane entity identity of base station

Identification information of CN-CP2 GUAMI as defined in TS38.413

Core network configurable list information

In step 705, after receiving the second request response message, the CU-CP2 entity determines configuration information that can be used with the CN-CP2 according to the response message.

Example two:

the embodiment mainly describes a process for establishing a control plane entity of a base station and URLLC service selected by a user, wherein core network entities are CN-CP1 and CN-CP2, and the control plane entity of the base station is CU-CP1 and CU-CP2, wherein CN-CP1 and CU-CP1 only support URLLC service, and CN-CP2 and CU-CP2 only support eMBB service. For the URLLC base station, the 2-step RACH access method and the specially configured frequency domain resources are indicated in SIB 1.

As shown in fig. 8, in step 801, the base station sends a broadcast message, where in the broadcast message SIB1, the access and resource usage scheme used by the URLLC service in the random access process is referred to, and the service set list includes the following combinations:

-set of service identity lists: slice2

-a random access scheme: two-step random access scheme

Frequency domain resources for random access: 40 RB sets, wherein 2 RB sets with the highest frequency point are used sets

In step 802, after the user terminal reads the access scheme and the used resource used by different slices in the random access process from the broadcast message of the base station, the access scheme and the used resource information used by the user in the random access process are determined according to the slice or service preference information indicated by the user high layer to the access layer as URLLC, wherein if the selected service is not in any service set list, the access scheme and the used resource information are performed according to the normal random access mode.

In step 803, the user initiates a random access procedure to the base station side, and the base station DU entity determines the service type preferentially used by the user and the CU-CP1 selected by the user by detecting the scheme and the used resources used by the user in the random access procedure.

After receiving the RRC message containing the slice and the core network selection sent by the user, the base station DU entity encapsulates the RRC message into container information for transparent transmission, and sends the container information to the CU-CP1 through the user initial context configuration information. Wherein the user initial context configuration information comprises the following information:

identification of the user at the base station DU

-C-RNTI allocated for users

Cell identity where the user is camping

-encapsulated user RRC message

In step 804, after receiving the initial context configuration information of the user, the CU-CP1 determines the core network entity, PLMN and slice information selected by the user according to the encapsulated RRC message of the user, and determines the CN-CP1 to which the configuration information of the user needs to be sent according to the connection relationship between the CU-CP1 and the core network control plane entity. Wherein the configuration information of the user comprises:

CU-CP1 assigned user identification

-encapsulated NAS layer message:

-user selected PLMN or slice identity

In step 805, after receiving the configuration information of the user, the CN-CP1 decodes the encapsulated NAS layer message, determines that the service requested by the user and the slice supported by the request can be carried by the CN-CP1 according to the service request information carried in the NAS message, and the CN-CP1 sends first user configuration confirmation information to the CU-CP1, where the first user configuration confirmation information includes:

-user identity assigned by CN-CP1

-wireless network capability configuration of the user

-encapsulated NAS message:

-partial control plane indication message:

-primary control plane indication

-slice identification list

-CN-CP1 configures a service type list for the user, the list including:

identification of PDU Session

QOS identification of services

QOS configuration information of the service

After receiving the user configuration confirmation message, the CU-CP1 determines the control plane configuration for the user according to the main control plane indication information and part of the control plane in the message at step 806. And determining the service and the slice supported on the control plane entity according to the slice identifier and the service type, judging whether the slice and the service QOS can be admitted by the CU-CP1, and if all the services can be admitted, the CU-CP1 sends first user service configuration information to the base station DU entity. The first user service configuration information comprises the following information:

CU-CP1 assigned user identification

-wireless network capability configuration of the user

-incremental configuration indication

-primary control plane entity indication

In step 807, after receiving the user service configuration information sent by the CU-CP1, the base station DU entity records the user identifier allocated by the CU-CP1, and uses the identifier to uniquely mark the user information in subsequent signaling, and determines that it is not necessary to wait for other control plane entities to send the user service configuration information according to the incremental configuration instruction, and performs admission judgment on the service configuration of the user, and if all services can be admitted, sends a service configuration success message to the CU-CP 1. Wherein the service configuration success message includes:

the identity of the base station DU entity for the user

-identity allocated by the base station control plane entity for the user

-list of acceptable service identities for this control plane allocation:

identification of the service

QOS identification of services

In step 808, after receiving the successful service configuration, the CU-CP1 generates an RRC message according to the successfully configurable service type determined in the message, and sends the RRC message to the base station DU entity through the downlink RRC configuration message. And if the CU-CP1 receives the service configuration rejection message, feeding back user configuration rejection information to the CN-CP 1. Wherein the RRC configuration message comprises the following:

the identity of the base station DU entity for the user

-identity allocated by the base station control plane entity for the user

-encapsulating a user RRC message, the RRC reconfiguration message comprising the following:

NAS messages

Service configuration information that the user can carry in the CU-CP1

AS layer encryption/decryption and integrity protection configuration for the user

In step 809, the base station DU entity sends an RRC reconfiguration message to the user according to the RRC configuration message sent by CU-CP 1.

In step 810, the ue completes configuration of related parameters and services according to the received RRC reconfiguration message, and sends an RRC reconfiguration complete message to the base station DU entity.

In step 811, the base station DU entity sends a configuration complete message to the CU-CP1 after receiving the RRC reconfiguration complete message fed back by the user. Wherein the configuration completion message includes the following information:

the identity of the base station DU entity for the user

-identity allocated by the base station control plane entity for the user

NAS feedback messages carried by the user

In step 812, after receiving the configuration completion message, the CU-CP1 forwards the NAS feedback message carried by the user to the CN-CP 1.

Example three:

the main difference between this embodiment and the second embodiment is that in the second embodiment, the CN-CP1 can support the service requested by the user, and in this embodiment, a part of the service requested by the user is carried by the CN-CP1, and another part is carried by the CN-CP 2.

As shown in fig. 9, in step 901, a base station transmits a broadcast message, wherein the broadcast message indicates access schemes and resources used by different services in a random access procedure

In step 902, after the user terminal reads the access scheme and the used resource used by different slices in the random access process from the base station broadcast message, the access scheme and the used resource information used by the user in the random access process are determined according to the slice or service priority selection information indicated by the user high layer to the access layer, wherein if the selected service is not in any service set list, the access scheme and the used resource information are accessed according to the normal random access mode.

In step 903, the user initiates a random access procedure to the base station side, and the base station DU entity determines the service type preferentially used by the user and the CU-CP1 that needs to be selected by the user by detecting the scheme and the used resource used by the user in the random access procedure.

identification of the user at the base station DU

-C-RNTI allocated for users

Cell identity where the user is camping

-encapsulated user RRC message

In step 904, after receiving the initial context configuration information of the user, the CU-CP1 determines the core network entity, PLMN and slice information selected by the user according to the encapsulated RRC message of the user, and determines the CN-CP1 to which the configuration information of the user needs to be sent according to the connection relationship between the CU-CP1 and the core network control plane entity. Wherein the configuration information of the user comprises:

CU-CP1 assigned user identification

-encapsulated NAS layer message:

-user selected PLMN or slice identity

In step 905, after receiving the configuration information of the user, the CN-CP1 decodes the encapsulated NAS layer message, determines that part of the service requested by the user and the slice supported by the request cannot be carried by CN-CP1 according to the service request information carried in the NAS message, and sends the service reallocation message to CN-CP2 through the interface between the core network control plane entities by CN-CP 1. Wherein the service reallocation message comprises:

-user identity assigned by CN-CP1

PLMN list for use by a user terminal

List of slice types assigned to CN-CP2

-NAS messages

In step 906, the CN-CP2 determines whether all the assigned slice types can be supported according to the traffic re-assignment message, and if so, sends a traffic re-assignment response message indicating that the traffic re-assignment is successful to the CN-CP 1. Wherein the service reallocation response message includes:

-user identity assigned by CN-CP2

-list of slice types failing in allocation

In step 907, the CN-CP1 transmits first user configuration confirmation information to the CU-CP1 after receiving the service re-allocation response message transmitted by the CN-CP2, wherein the first user configuration confirmation information includes:

-user identity assigned by CN-CP1

-wireless network capability configuration of the user

-encapsulated NAS message:

-partial control plane indication message:

-primary control plane indication

-slice identification list

-CN-CP1 configures a service type list for the user, the list including:

identification of PDU Session

QOS identification of services

QOS configuration information of the service

In step 908, the CN-CP2 sends the second user traffic configuration information to the CU-CP 2. Wherein the second user service configuration information includes:

-user identity assigned by CN-CP2

-wireless network capability configuration of the user

-partial control plane indication message:

-slice identification list

-primary control plane indication

-CN-CP2 configures a service type list for the user, the list including:

identification of PDU Session

QOS identification of services

QOS configuration information of the service

After receiving the user configuration confirmation information, the CU-CP1 determines the control plane configuration for the user according to the main control plane indication information and part of the control plane in the message in step 909. And determining the service and the slice supported on the control plane entity according to the slice identifier and the service type, judging whether the slice and the service QOS can be admitted by the CU-CP1, and if all the services can be admitted, the CU-CP1 sends first user service configuration information to the base station DU entity. The first user service configuration information comprises the following information:

-CU-CP1 assigned user identification

-wireless network capability configuration of the user

-incremental configuration indication

-primary control plane entity indication

After receiving the user configuration confirmation message, the CU-CP2 determines the control plane configuration for the user according to the main control plane indication information and part of the control plane in the message at step 910. And determining the service and the slice supported on the control plane entity according to the slice identifier and the service type, judging whether the slice and the service QOS can be admitted by the CU-CP2, and if all the services can be admitted, the CU-CP2 sends second user service configuration information to the base station DU entity. Wherein the second user service configuration information includes the following:

CU-CP2 assigned user identification

-wireless network capability configuration of the user

-incremental configuration indication

In step 911, after receiving the user service configuration information sent by the CU-CP1, the base station DU entity records the user identifier allocated by the CU-CP1 and uses the identifier to uniquely mark the user information in subsequent signaling, and when it is determined that it is necessary to wait for the CU-CP2 to send the user service configuration information according to the incremental configuration indication, the DU entity starts a preconfigured timer so as to receive the second user service configuration information sent by the CU-CP2 within a 20ms range.

And the DU entity performs admission judgment on the received first user service configuration information and the second user service configuration information, and sends a service configuration success message to the CU-CP1 if all services can be admitted. Wherein the service configuration success message includes:

the identity of the base station DU entity for the user

-identity allocated by the base station control plane entity for the user

-list of acceptable service identities assigned to this control plane:

identification of the service

QOS identification of services

In step 912, the DU entity checks whether the service configured by the CU-CP2 can be admitted, and if so, sends a service configuration success message to the CU-CP2, so that the CU-CP2 can perform subsequent control plane configuration.

In step 913, after receiving the successful service configuration, CU-CP1 generates an RRC message according to the successfully configurable service type determined in the message, and sends the RRC message to the base station DU entity through a downlink RRC configuration message. Wherein the RRC configuration message comprises the following:

the identity of the base station DU entity for the user

-identity allocated by the base station control plane entity for the user

NAS messages

Service configuration information that the user can carry in the CU-CP1

In step 914, the base station DU entity sends an RRC reconfiguration message to the user according to the RRC configuration message sent by CU-CP 1.

In step 915, the ue completes configuration of related parameters and services according to the received RRC reconfiguration message, and sends an RRC reconfiguration complete message to the base station DU entity.

In step 916, the base station DU entity sends a configuration complete message to CU-CP1 after receiving the RRC reconfiguration complete message fed back by the user. Wherein the configuration completion message includes the following information:

the identity of the base station DU entity for the user

-identity allocated by the base station control plane entity for the user

NAS feedback messages carried by the user

In step 917, after receiving the configuration complete message, the CU-CP1 forwards the NAS feedback message carried by the user to the CN-CP 1.

In step 918, the base station DU entity also sends a configuration complete message to the CU-CP2 after receiving the RRC reconfiguration complete message fed back by the user.

Through implementing this disclosure, can obtain at least one in following beneficial effect:

1) the scheme of the present disclosure can support different control plane nodes configured for different users and services, thereby realizing effective reduction of control plane delay, maintaining the characteristic that the network architecture is transparent to users, and avoiding the influence on the user protocol stack.

2) The scheme of the invention can enable the user to implicitly indicate the selected control plane node to the bottom entity of the base station which does not contain the high-level protocol station in the random access process without adding extra display indication information, thereby reducing the signaling overhead of an air interface.

3) The scheme of the present disclosure supports the addition, deletion and modification processes of the dynamic control plane entity triggered by the core network, and can effectively support the dynamic configuration process of the service.

4) The scheme related by the disclosure has the advantages of small change to the user terminal, good backward compatibility and deployment feasibility. The scheme is enhanced on the existing protocol, a new protocol process is not introduced, and the realization difficulty is low.

In some embodiments, the functional units described above can be implemented as general purpose processors, Programmable Logic Controllers (PLCs), Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable Logic devices, discrete Gate or transistor Logic devices, discrete hardware components, or any suitable combination thereof for performing the functions described in this disclosure.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The description of the present disclosure has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to practitioners skilled in this art. The embodiment was chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.

Claims

1. A control plane configuration method, performed by a base station, comprising:

the DU entity of the base station sends broadcast information to indicate the access scheme and resources used by different services in the random access process;

the DU entity selects a first CU-CP entity of the base station for the user terminal according to an access scheme and resources used by the user terminal in a random access process, and sends an RRC message sent by the user terminal to the first CU-CP entity;

the first CU-CP entity sends the NAS message included in the RRC message to a corresponding first CN-CP entity of a core network, so that the first CN-CP entity configures a corresponding control plane connection relation;

after receiving first user configuration confirmation information sent by the first CN-CP entity, the first CU-CP entity sends first user service configuration information to the DU entity;

the DU entity completes service configuration according to the first user service configuration information, and sends RRC reconfiguration information to the user terminal according to the RRC configuration information sent by the first CU-CP entity so that the user terminal completes service configuration;

and the DU entity sends a configuration completion message to the first CU-CP entity according to the RRC reconfiguration completion message sent by the user terminal.

2. The method of claim 1, wherein,

the broadcast message includes at least one of a service identifier list set, a random access scheme, a time domain resource of random access, a frequency domain resource of random access, and a code domain resource of random access.

3. The configuration method of claim 1, wherein the selecting, by the DU entity, the first CU-CP entity of the base station for the user terminal according to an access scheme and resources used by the user terminal in a random access procedure comprises:

the DU entity determines the service type preferentially used by the user according to the access scheme and the resources used by the user terminal in the random access process;

and the DU entity determines that the control plane entity selected by the user is the first CU-CP entity according to the service type and the pre-configuration information.

4. The method of claim 3, wherein,

the pre-configuration information comprises at least one of an identity of the first CU-CP entity, service set information supported by the first CU-CP entity, the service set information comprising at least one of PLMN list information, TAC list information, and slice list information.

5. The method of claim 1, wherein the DU entity transmitting the RRC message transmitted by the user terminal to the first CU-CP entity comprises:

after receiving the RRC message sent by the user terminal, the DU entity packages the RRC message into RRC container information for transparent transmission, wherein the RRC message comprises slice and core network option information;

the DU entity transmits user initial context configuration information including the RRC container information to the first CU-CP entity.

6. The method of claim 5, wherein the user initial context configuration information further comprises at least one of an identity of the user terminal in the DU entity, a C-RNTI allocated for the user terminal, and an identity of a cell in which the user terminal resides.

7. The method of claim 6, wherein the first CU-CP entity sending a NAS message included in the RRC message to a corresponding core network first CN-CP entity comprises:

the first CU-CP entity determines a core network entity, a PLMN and slice information selected by a user according to RRC container information included in the user initial context configuration information;

the first CU-CP entity determines that user configuration information needs to be sent to the first CN-CP entity according to the connection relation between the first CU-CP entity and a core network control plane entity;

and the first CU-CP entity sends the user configuration information to the first CN-CP entity, wherein the user configuration information comprises NAS information carried in the RRC container information.

8. The method of claim 7, wherein the user configuration information further comprises at least one of a user identification, a user selected PLMN, or a slice identification assigned by the first CU-CP entity.

9. The method of claim 1, wherein,

the first user configuration confirmation information comprises at least one item of user identification distributed by the first CN-CP entity, wireless network capability configuration of a user, encapsulated NAS information, part control plane indication information, main control plane indication information, a slice identification list and a service type list configured for the user by the first CN-CP entity, wherein the service type list comprises at least one item of PDU session identification, service QoS identification and service QoS configuration information.

10. The method of claim 9, wherein the first CU-CP entity sending first user service configuration information to the DU entity after receiving first user configuration confirmation information sent by the first CN-CP entity comprises:

the first CU-CP entity determines the control plane configuration of the first CN-CP entity according to the main control plane indication information and part of control plane indication information in the first user configuration confirmation information;

the first CU-CP entity determines the services and the slices supported by the first CN-CP entity according to the slice identifiers and the service types in the first user configuration confirmation information;

the first CU-CP entity judges whether the business supported by the first CN-CP entity can be accepted or not;

and if the first CU-CP entity can accept at least one of the services supported by the first CN-CP entity, sending the first user service configuration information to the DU entity.

11. The method of claim 10, wherein,

the first user service configuration information comprises at least one of a user identification allocated by the first CU-CP entity, wireless network capability configuration of a user, increment configuration indication and main control plane entity indication.

12. The method of claim 10, further comprising:

and if the first CU-CP entity can not accept the service supported by the first CN-CP entity, sending first user configuration rejection information to the first CN-CP entity.

13. The method of claim 12, wherein,

the first user configuration rejection information comprises at least one of a user identifier allocated by the first CU-CP entity, a user identifier allocated by the first CN-CP entity and a rejection reason.

14. The method of claim 10, further comprising:

after receiving second user configuration confirmation information sent by a second CN-CP entity, a second CU-CP entity of the base station determines the control plane configuration of the second CN-CP entity according to main control plane indication information and part of control plane indication information in the second user configuration confirmation information;

the second CU-CP entity determines the service and the slice supported by the second CN-CP entity according to the slice identifier and the service type in the second user configuration confirmation information;

the second CU-CP entity judges whether the services supported by the second CN-CP entity can be accepted or not;

and if the second CU-CP entity can accept at least one of the services supported by the second CN-CP entity, sending second user service configuration information to the DU entity.

15. The method of claim 14, wherein,

the second user service configuration information comprises at least one of a user identification, a wireless network capability configuration and an incremental configuration indication of the user allocated by the second CU-CP entity.

16. The method of claim 14, wherein,

the second user configuration confirmation information comprises at least one item of user identification distributed by the second CN-CP entity, wireless network capability configuration of a user, part control plane indication information, a slice identification list and a service type list configured for the user by the second CN-CP entity, wherein the service type list comprises at least one item of PDU conversation identification, service QoS identification and service QoS configuration information.

17. The method of claim 14, further comprising:

and if the second CU-CP entity can not accept the service supported by the second CN-CP entity, sending second user configuration rejection information to the second CN-CP entity.

18. The method of claim 14, wherein the completing, by the DU entity, service configuration according to the first user service configuration information comprises:

after receiving the first user service configuration information sent by the first CU-CP entity, the DU entity records a user identifier distributed by the first CU-CP entity;

the DU entity determines whether other control plane entities send user service configuration information according to the increment configuration indication information in the first user service configuration information;

if the incremental configuration indication information in the first user service configuration information indicates that no other control plane entity sends user service configuration information, the DU entity detects whether the service configured by the first CU-CP entity can be admitted;

and if the DU entity can accommodate at least one of the services configured by the first CU-CP entity, sending a first service configuration success message to the first CU-CP entity.

19. The method of claim 18, wherein,

the first service configuration success message comprises at least one of a subscriber identity allocated by the DU entity, a subscriber identity allocated by the first CU-CP entity, an acceptable service identity list allocated by the first CU-CP entity, and an unacceptable service identity list allocated by the first CU-CP entity.

20. The method of claim 18, further comprising:

and if the DU entity can not accept the service configured by the first CU-CP entity, sending service configuration failure information to the first CU-CP entity.

21. The method of claim 19, wherein,

the service configuration failure information includes at least one of a user identifier allocated by the DU entity, a user identifier allocated by the first CU-CP entity, and a failure reason.

22. The method of claim 18, further comprising:

if the incremental configuration indication information in the first user service configuration information indicates that the second CU-CP entity also sends user service configuration information, the DU entity starts a preconfigured timer so as to receive the second user service configuration information sent by the second CU-CP entity within a predetermined time range;

after the DU entity receives second user service configuration information sent by the second CU-CP entity, recording a user identifier distributed by the second CU-CP entity;

the DU entity detects whether the services configured by the first CU-CP entity and the second CU-CP entity can be admitted;

and if the DU entity can accommodate at least one of the services configured by the first CU-CP entity and the second CU-CP entity, sending a second service configuration success message to the first CU-CP entity.

23. The method of claim 22, wherein,

the second service configuration success message includes at least one of a subscriber identity allocated by the DU entity, a subscriber identity allocated by the first CU-CP entity, a subscriber identity allocated by the second CU-CP entity, an acceptable service identity list allocated by the first CU-CP entity, an acceptable service identity list allocated by the second CU-CP entity, an unacceptable service identity list allocated by the first CU-CP entity, and an unacceptable service identity list allocated by the second CU-CP entity.

24. The method of claim 22, wherein the completing, by the DU entity, service configuration according to the first user service configuration information comprises:

after receiving the second user service configuration information sent by the second CU-CP entity, the DU entity records the user identifier distributed by the second CU-CP entity;

the DU entity determines that the first CU-CP entity sends user service configuration information according to increment configuration indication information in the second user service configuration information, and then the DU entity starts a preconfigured timer so as to receive the first user service configuration information sent by the first CU-CP entity within a preset time range;

after the DU entity receives first user service configuration information sent by the first CU-CP entity, recording a user identifier distributed by the first CU-CP entity;

25. The method of claim 24, further comprising:

and if the DU entity can not accommodate the services configured by the first CU-CP entity and the second CU-CP entity, sending service configuration failure information to the first CU-CP entity.

26. The method of claim 24, further comprising:

the DU entity detects whether the services configured by the second CU-CP entity can be accepted or not;

if the DU entity can accommodate at least one of the services configured by the second CU-CP entity, sending a service configuration success message to the second CU-CP entity;

and if the DU entity can not accept the service configured by the second CU-CP entity, sending service configuration failure information to the second CU-CP entity.

27. The method of claim 26, further comprising:

the second CU-CP entity performs corresponding control plane configuration on the service admitted by the DU entity according to the service configuration success message sent by the DU entity;

and after receiving the service configuration failure information sent by the DU entity, the second CU-CP entity sends user configuration rejection information to the second CN-CP entity.

28. The method of claim 26, wherein the DU entity sending the RRC reconfiguration message to the user terminal according to the RRC configuration message sent by the first CU-CP entity comprises:

the first CU-CP entity generates a corresponding user RRC message according to the successfully configurable service type confirmed in the first service configuration success message or the second service configuration success message;

the first CU-CP entity sends the generated user RRC message to the DU entity by using an RRC configuration message;

and the DU entity sends RRC reconfiguration information to the user terminal according to the RRC configuration information.

29. The method of claim 28, wherein the RRC configuration message comprises at least one of a user identifier assigned by the DU entity, a user identifier assigned by the first CU-CP entity, and a user RRC message, wherein the user RRC message comprises at least one of a NAS message, service configuration information that a user can carry in the first CU-CP entity, AS layer encryption/decryption and integrity protection configuration of the user, and mobility parameter configuration information of the user.

30. The method of claim 28, further comprising:

and after receiving the service configuration failure information sent by the DU entity, the first CU-CP entity sends user configuration rejection information to the first CN-CP entity.

31. The method of claim 28, wherein the DU entity transmits a configuration complete message to the first CU-CP entity according to the RRC reconfiguration complete message transmitted by the user terminal comprises:

after receiving an RRC reconfiguration complete message sent by the user terminal, the DU entity sends a configuration complete message to the first CU-CP entity under the condition of only receiving first user service configuration information sent by the first CU-CP entity;

and the first CU-CP entity sends the NAS feedback message carried in the RRC reconfiguration complete message to the first CN-CP entity.

32. The method of claim 31, further comprising:

the DU entity judges whether service configuration failure information is sent to the second CU-CP entity or not under the condition that first user service configuration information sent by the first CU-CP entity and second user service configuration information sent by the second CU-CP entity are received;

and if the service configuration failure information is not sent to the second CU-CP entity, the DU entity sends a configuration completion message to the first CU-CP entity and the second CU-CP entity.

33. The method of claim 32, further comprising:

and if the service configuration failure information is sent to the second CU-CP entity, the DU entity sends a configuration completion message to the first CU-CP entity.

34. The method of claim 33, wherein,

the configuration completion message includes at least one of a user identifier allocated by the DU entity, a user identifier allocated by a base station control plane entity, and a NAS feedback message carried in the RRC reconfiguration completion message, where the NAS feedback message is sent only to the first CU-CP entity.

35. The method of any of claims 1-34, further comprising:

a first CU-CP entity of the base station sends a first request to a first CN-CP entity of a preconfigured core network in an interface establishing process, wherein the first request comprises at least one item of identification of the base station, identification of the first CU-CP entity and a service configuration information list of the base station, so that the first CN-CP entity determines a connection relation with the first CU-CP entity according to the first request;

and after receiving a first request response sent by the first CN-CP entity, the first CU-CP entity determines the connection relation with the first CN-CP entity according to the core network configurable list information included in the first request response.

36. The method of claim 35, further comprising:

a second CU-CP entity of the base station sends a second request to a second CN-CP entity of a preconfigured core network in an interface establishing process, wherein the second request comprises at least one of an identifier of the base station, an identifier of the second CU-CP entity and a service configuration information list of the base station, so that the second CN-CP entity determines a connection relation with the second CU-CP entity according to the second request;

and after receiving a second request response sent by the second CN-CP entity, the second CU-CP entity determines the connection relation with the second CN-CP entity according to the core network configurable list information included in the second request response.

37. A base station, comprising:

a memory configured to store instructions;

a processor coupled to the memory, the processor configured to perform implementing the method of any of claims 1-36 based on instructions stored by the memory.

38. A communication system, comprising:

the base station of claim 37;

the user terminal is configured to determine an access scheme and resource information used in the random access process according to preset indication information and randomly access the base station after acquiring the access scheme and resource used in the random access process of different slices from a broadcast message sent by the base station;

and the core network first CN-CP entity is configured to judge whether the service and the request supporting slice applied by the user terminal can be borne according to the service request message carried in the NAS message sent by the first CU-CP entity of the base station, and if the service and the request supporting slice applied by the user terminal can be borne, first user configuration confirmation information is sent to the first CU-CP entity.

39. The communication system of claim 38, further comprising a core network second CN-CP entity, wherein:

the first CN-CP entity is configured to send a service redistribution message to the second CN-CP entity if the first CN-CP entity can not bear at least one slice or service, and after receiving a service redistribution response message sent by the second CN-CP entity, the first user service configuration information is sent to the first CU-CP entity of the base station;

and the second CN-CP entity is configured to determine whether all the allocated slice types can be supported according to the service reallocation message, if at least one of all the allocated slice types is supported, send a service reallocation response message for indicating that service reallocation is successful to the first CN-CP entity, and send second user service configuration information to a second CU-CP entity of the base station.

40. The communication system of claim 39,

the service reallocation message comprises at least one of a user identifier allocated by the first CN-CP entity, a PLMN list used by the user terminal, a slice type list allocated to the second CN-CP entity and a NAS message.

41. The communication system of claim 39,

the service reallocation response message includes at least one of a user identifier allocated by the second CN-CP entity and a slice type list of allocation failure, wherein each slice type includes at least one of a slice identifier and a reason for allocation failure.

42. The communication system of claim 39,

the second CN-CP entity is configured to send a traffic re-allocation reject message to the first CN-CP entity if all slice types are not supported.

43. The communication system of claim 42,

the service re-allocation rejection message includes at least one of a subscriber identity allocated by the second CN-CP entity and an allocation failure reason.

44. The communication system of claim 38,

the first CN-CP entity is configured to store a base station identifier and a first CU-CP entity identifier carried in a first request after receiving the first request sent by the first CU-CP entity, determine unique address identifier information of the first CU-CP entity according to the base station identifier and the first CU-CP entity identifier, and determine the connection relation between the first CN-CP entity and the first CU-CP entity according to the determined unique address identifier information; and the CU-CP entity is also configured to generate first core network configurable list information under the condition that the service configuration information list of the base station carried in the first request can be accepted, and send a first request response to the first CU-CP entity.

45. The communication system of claim 44,

the first core network configurable list information comprises at least one of PLMN identification accepted by the first CN-CP entity, accepted TAC information and accepted slice set information;

the first request response includes at least one of identification information of the base station, a first CU-CP entity identification, a first CN-CP entity identification, and first core network configurable list information.

46. The communication system of claim 39,

the second CN-CP entity is configured to store a base station identifier and a second CU-CP entity identifier carried in a second request after receiving the second request sent by the second CU-CP entity, determine unique address identifier information of the second CU-CP entity according to the base station identifier and the second CU-CP entity identifier, and determine the connection relation between the second CN-CP entity and the second CU-CP entity according to the determined unique address identifier information; and the second CU-CP entity is also configured to generate second core network configurable list information under the condition that the service configuration information list of the base station carried in the second request can be accepted, and send a second request response to the second CU-CP entity.

47. The communication system of claim 46,

the second core network configurable list information comprises PLMN identification accepted by a second CN-CP entity, accepted TAC information and accepted slice set information;

the second request response includes at least one of identification information of the base station, a second CU-CP entity identification, a second CN-CP entity identification, and second core network configurable list information.

48. A computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions which, when executed by a processor, implement the method of any one of claims 1-36.