Method and system for updating bearer configuration

Abstract

The application discloses a method and system for updating a bearer configuration, and relates to the field of wireless communication. The method for updating the bearer configuration comprises the following steps: a first control plane entity of a core network determines a second control plane entity of the core network involved in service change of a user; the first control plane entity of the core network sends a user information change request to a first control plane entity of a base station; the second control plane entity of the core network sends user configuration confirmation information to a second control plane entity of the base station; the first control plane entity of the base station sends first user service configuration information to a bottom layer entity of the base station; the second control plane entity of the base station sends second user service configuration information to the bottom layer entity of the base station; the second control plane entity of the base station sends RRC configuration information and corresponding SRB identification to the bottom layer entity of the base station; and the bottom layer entity of the base station sends the RRC configuration information to a terminal according to the SRB identification.

Description

Technical Field

[0001] This invention relates to the field of wireless communication, and in particular to a method and system for updating bearer configuration. Background Technology

[0002] Currently, 5G networks support an architecture that separates the Centralized Unit (CU) and Distributed Unit (DU) and the Control Plane (CP) and User Plane (UP). This decoupling of functions provides operators with significant flexibility, allowing them to deploy the Radio Unit (RU), DU, and CU in different locations as needed. The CU consists of a Control Plane (CP) and a User Plane (UP). This configuration is similar to 4G wireless networks, making the integration of 5G networks with 4G LTE networks easier. Furthermore, it provides flexibility for configuring the 5G Radio Access Network (RAN). According to 5G mobile communication standards and architecture, a crucial concept in 5G is separating UP and CP functions, allowing for independent scalability, evolution, and flexible deployment, such as in centralized or distributed (remote) locations.

[0003] In the current architecture, from the perspective of the UE (User Equipment), the entire network has only one control plane entity, but can have multiple user plane entities. From the core network's perspective, the base station also has only one control plane entity. Related control plane signaling is sent from the core network's control plane entity to the base station's control plane entity, and then from the base station's control plane entity to the user. From a network deployment perspective, different types of services have different location requirements for the control plane entity. For example, for IoT services, because they are relatively insensitive to latency, they are usually deployed at a higher, centralized location to achieve centralized management; while for latency-sensitive services, their control plane is usually deployed closer to the DU (User Unit).

[0004] For users, currently, information about their selected core network and slice configuration is indicated to the network side through the randomly accessed MSG5. Currently, due to limitations in the size of SRBs (Signalling Radio Bearers) and the lack of services, users in 5G networks cannot indicate information about their selected core network and slice to the network; therefore, the current wireless network architecture only has one control plane logical entity. Summary of the Invention

[0005] In future 6G networks, it is necessary to address the design and deployment limitations of 5G networks. For example, when further addressing latency issues, the fixed protocol structure becomes a bottleneck for achieving lower latency. For 5G wireless networks, the protocol structure is layered, with all services processed layer by layer. Each layer introduces latency, creating a bottleneck for service transmission latency. To further reduce air interface latency, this structure must be broken. Considering service development trends, 6G wireless network design needs to take into account end-to-end microservice design and the separation of data and signaling, thereby improving the overall network deployment efficiency and cost.

[0006] In 5G networks, because a base station has only one control plane, while it can be configured with multiple user planes, the core network only sends control plane signaling to the control plane node during service updates. The control plane node then reconfigures the user plane node, which in turn configures with the DU (User Controller). These operations introduce additional latency due to the difference in deployment locations between the control plane and user plane nodes. Furthermore, during reconfiguration or the addition of new services, core network entities send control plane signaling to the base station's single control plane entity.

[0007] Based on the above background, the inventors, after analysis, discovered that if it is necessary to effectively reduce control plane latency and reduce the latency of adding new services during the reconfiguration of services in a separate architecture, the current 5G wireless network architecture has the following defects when supporting multi-control plane scenarios.

[0008] 1) The ability to dynamically replace or add control plane nodes is not supported. Currently, the core network in the 5G architecture can only see one control plane node, and each base station has only one base station identifier. The base station and the core network cannot establish the necessary control plane connection. Furthermore, there is no mechanism on the base station side to guarantee that the F1 interface can be dynamically replaced or added. If the F1 interface is replaced, all user contexts need to be deleted, resulting in the loss of user control plane connections.

[0009] 2) Mismatch between the control plane and user plane locations leads to signaling configuration delays. Because the control plane may not be co-located with some user plane entities or may not be located in close proximity, configuring the user plane from the control plane may introduce more signaling delays, resulting in longer wait times for the bearer and ultimately affecting service rates and latency requirements.

[0010] 3) The target of RRC (Radio Resource Control) message transmission for the base station's underlying entity is ambiguous. If each DU supports the same SRB type, then according to the current method, the DU cannot determine which CU-CP to send the RRC message to. Therefore, the simplest way is to have the DU send the RRC message back to all connected CU-CPs, which inevitably leads to an overall reduction in efficiency and a waste of signaling resources.

[0011] Based on the above requirements and reasons analysis, when multiple control plane entities are introduced on the base station side, how to select and modify appropriate control plane entities for the bearer during the bearer update process, and reduce service interruptions and waiting caused by control plane latency, all require a new architectural approach to design in order to meet the needs of network deployment and optimization.

[0012] One technical problem that this invention aims to solve is: how to provide a new bearer configuration update process to support multi-control plane scenarios without affecting network performance.

[0013] According to a first aspect of some embodiments of the present invention, a method for updating bearer configuration is provided, comprising: a first control plane entity of a core network determining a second control plane entity of the core network involved in a service change message sent by a user's terminal; the first control plane entity of the core network sending a user information change request to a first control plane entity of a base station, wherein the user information change request includes changed service information; the second control plane entity of the core network sending user configuration confirmation information to a second control plane entity of the base station, wherein the user configuration confirmation information includes the changed service information; the first control plane entity of the base station sending first user service configuration information to a lower-level entity of the base station, wherein the first user service configuration information includes a first SRB list set; the second control plane entity of the base station sending second user service configuration information to a lower-level entity of the base station, wherein the second user service configuration information includes a second SRB list set, and the SRB types in the first SRB list set and the second SRB list set are different; when the second control plane entity of the base station receives a service configuration success message sent by a lower-level entity of the base station, the second control plane entity of the base station sending RRC configuration information and a corresponding SRB identifier to the lower-level entity of the base station; and the lower-level entity of the base station sending the RRC configuration information to the terminal according to the SRB identifier.

[0014] In some embodiments, the first control plane entity of the core network determines the second control plane entity of the core network involved in the user's changed service based on the service change message sent by the user's terminal, including: the first control plane entity of the core network receiving the service change message sent by the user's terminal, wherein the service change message includes the changed service; and when the changed service is not within the management scope of the first control plane entity of the core network, the first control plane entity of the core network determines the second control plane entity of the core network involved in the user's changed service.

[0015] In some embodiments, the update method further includes: a first control plane entity of the core network sending a service change request to a second control plane entity of the core network, wherein the service change request includes information about the changed service; and if at least one of the changed services is received by the second control plane entity of the core network, the second control plane entity of the core network sending a service change request response message to the first control plane entity of the core network.

[0016] In some embodiments, a service change request includes: a user identifier assigned to the user by a first control plane entity of the core network; a user identifier assigned to the user by a second control plane entity of the core network; the user's PLMN (Public Land Mobile Network) list; a service list of the changed service, wherein information for each service in the service list includes the service slice type and Quality of Service (QoS) identifier; and the user's Non-Access Stratum (NAS) message.

[0017] In some embodiments, the update method further includes: if the changed services are not received by the second control plane entity of the core network, the second control plane entity of the core network sends a service change request rejection message to the first control plane entity of the core network.

[0018] In some embodiments, a user information change request includes: a user identifier assigned to the user by a first control plane entity of the core network; a user identifier assigned to the user by a first control plane entity of the base station; an encapsulated NAS message; a service list changed to a second control plane entity of the base station, wherein information for each service in the service list includes the service slice type, service identifier, and QoS identifier.

[0019] In some embodiments, the user configuration confirmation information includes: a user identifier assigned to the user by the second control plane entity of the core network; the user's radio network capability configuration; a partial control plane indication message, used to indicate whether the configuration information of all the user's control planes is located in the second control plane entity of the core network; a slice identifier list, including one or more slice identifiers; and a service type list configured for the user by the first control plane entity of the core network, wherein the service type list includes the identifier of the Protocol Data Unit Session (PDU Session), the QoS identifier of the service, and the QoS configuration information of the service.

[0020] In some embodiments, the first user service configuration information includes: a user identifier assigned to the user by the first control plane entity of the base station; the user's radio network capability configuration; a main control plane entity indicator, used to indicate whether the first control plane entity of the base station is a main control plane entity; a first SRB list set; an RRC message; and the SRB identifier used in the RRC message.

[0021] In some embodiments, the second user service configuration information includes: a user identifier assigned to the user by the second control plane entity of the base station; the user's radio network capability configuration; and a second SRB list set.

[0022] In some embodiments, the update method further includes: when the underlying entity of the base station receives at least one of the changed services, sending a service configuration success message to the first control plane entity and the second control plane entity of the base station; the underlying entity of the base station determines the first SRB list set supported by the first control plane entity of the base station and the second SRB list set supported by the second control plane entity of the base station.

[0023] In some embodiments, the service configuration success message includes: a user identifier assigned to the user by the base station underlying entity; a user identifier assigned to the user by the control plane entity of the base station receiving the service configuration success message; a list of service identifiers assigned by the control plane and accepted by the base station underlying entity, including the service identifier and the service QoS identifier; if there is a service that the control plane entity of the base station receiving the service configuration success message does not accept, the service configuration success message also includes: a list of unacceptable service identifiers assigned by the control plane, including the identifier of the unacceptable service, the QoS identifier, and the reason for the failure to accept.

[0024] In some embodiments, the RRC configuration information sent by the second control plane entity of the base station to the underlying entity of the base station includes: a user identifier assigned to the user by the second control plane entity of the base station; a user identifier assigned to the user by the underlying entity of the base station; an encapsulated RRC message; and an SRB identifier, used to indicate the type of SRB, wherein the type of SRB belongs to a second SRB list set.

[0025] In some embodiments, the underlying entity of the base station maps the RRC message in the RRC configuration information to the corresponding SRB resource according to the SRB identifier, and sends the RRC configuration information to the terminal.

[0026] In some embodiments, the update method further includes: the terminal configuring according to RRC configuration information; and the terminal sending an RRC configuration completion message to the underlying entity of the base station.

[0027] In some embodiments, the update method further includes: the underlying entity of the base station obtaining the RRC configuration complete message sent by the terminal; the underlying entity of the base station determining the corresponding control plane entity of the base station according to the SRB type of the RRC configuration complete message; and the underlying entity of the base station sending the RRC configuration complete message to the corresponding control plane entity of the base station.

[0028] In some embodiments, the underlying entity of the base station sends configuration response information to the control plane entity of the corresponding base station, and the configuration response information includes: a user identifier assigned to the user by the underlying entity of the base station; a user identifier assigned to the user by the control plane entity of the corresponding base station; an RRC configuration completion message; and an SRB identifier.

[0029] In some embodiments, the update method further includes: when the control plane entity of the corresponding base station is the first control plane entity of the base station and the RRC configuration completion message includes a NAS message, the first control plane entity of the base station sends the NAS message to the first control plane entity of the core network.

[0030] According to a second aspect of some embodiments of the present invention, a bearer configuration update system is provided, comprising: a first control plane entity of a core network configured to determine a second control plane entity of the core network involved in a service change by a user based on a service change message sent by a user's terminal; sending a user information change request to a first control plane entity of a base station, wherein the user information change request includes changed service information; the second control plane entity of the core network configured to send user configuration confirmation information to a second control plane entity of the base station, wherein the user configuration confirmation information includes the changed service information; the first control plane entity of the base station configured to send first user service configuration information to a lower-level entity of the base station, wherein the first user service configuration information includes a first SRB list set; the second control plane entity of the base station configured to send second user service configuration information to a lower-level entity of the base station, wherein the second user service configuration information includes a second SRB list set, and the SRB types in the first SRB list set and the second SRB list set are different; upon receiving a service configuration success message sent by a lower-level entity of the base station, sending RRC configuration information and a corresponding SRB identifier to the lower-level entity of the base station; and the lower-level entity of the base station configured to send the RRC configuration information to a terminal based on the SRB identifier.

[0031] In some embodiments, the first control plane entity of the core network is further configured to receive a service change message sent by a user's terminal, wherein the service change message includes a changed service; and if the changed service is not within the management scope of the first control plane entity of the core network, to determine the second control plane entity of the core network involved in the user's changed service.

[0032] In some embodiments, the first control plane entity of the core network is further configured to send a service change request to the second control plane entity of the core network, wherein the service change request includes information about the changed service; and if at least one of the changed services is received by the second control plane entity of the core network, the first control plane entity of the core network receives a service change request response message sent by the second control plane entity of the core network.

[0033] In some embodiments, the second control plane entity of the core network is further configured to send a service change request rejection message to the first control plane entity of the core network if the changed services are not received by the second control plane entity of the core network.

[0034] In some embodiments, the underlying entity of the base station is further configured to send a service configuration success message to a first control plane entity and a second control plane entity of the base station when at least one of the changed services is accepted; and to determine a first SRB list set supported by the first control plane entity of the base station and a second SRB list set supported by the second control plane entity of the base station.

[0035] In some embodiments, the RRC configuration information sent by the second control plane entity of the base station to the underlying entity of the base station includes: a user identifier assigned to the user by the second control plane entity of the base station; a user identifier assigned to the user by the underlying entity of the base station; an encapsulated RRC message; and an SRB identifier, used to indicate the type of SRB, wherein the type of SRB belongs to a second SRB list set.

[0036] In some embodiments, the underlying entity of the base station is further configured to map the RRC message in the RRC configuration information to the corresponding SRB resource according to the SRB identifier, and send the RRC configuration information to the terminal.

[0037] In some embodiments, the underlying entity of the base station is further configured to obtain an RRC configuration completion message sent by the terminal, wherein the RRC configuration completion message is sent by the terminal after configuration based on the RRC configuration information; determine the control plane entity of the corresponding base station based on the SRB type of the RRC configuration completion message; and send the RRC configuration completion message to the control plane entity of the corresponding base station.

[0038] In some embodiments, the first control plane entity of the base station is further configured to send a NAS message to the first control plane entity of the core network if the RRC configuration completion message includes a NAS message.

[0039] In some embodiments, the update system further includes: a terminal configured to configure according to RRC configuration information; and to send an RRC configuration complete message to the underlying entity of the base station.

[0040] Some embodiments of the above invention have the following advantages or beneficial effects. The method of the embodiments of the present invention can configure different control plane nodes for different users and services. Different control plane nodes can independently send RRC messages to the terminal and independently configure the bearer services in the DU. Furthermore, by adopting the method of configuring different SRB sets for different control planes, the DU can distinguish different types of RRC messages and thus determine the target base station control plane entity corresponding to the RRC message to be sent, avoiding signaling waste caused by group-return RRC messages. The above embodiments support the dynamic addition, deletion, and modification process of control plane entities triggered by the core network, which can effectively support the dynamic configuration process of services, and has minimal impact on the terminal, with good backward compatibility and deployment feasibility. The above embodiments are enhancements on existing protocols without introducing new protocol processes, and are relatively easy to implement.

[0041] Other features and advantages of the invention will become clear from the following detailed description of exemplary embodiments of the invention with reference to the accompanying drawings. Attached Figure Description

[0042] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0043] Figure 1 A schematic diagram of a wireless network architecture supporting multiple control planes according to some embodiments of the present invention is shown.

[0044] Figure 2 A flowchart illustrating a method for updating bearer configuration according to some embodiments of the present invention is shown.

[0045] Figure 3 A schematic diagram of the interaction process between the first control plane entity and the second control plane entity on the core network side is shown.

[0046] Figure 4 A schematic diagram of the configuration process according to some embodiments of the present invention is shown.

[0047] Figure 5 A signaling flow diagram of a bearer configuration update method according to some embodiments of the present invention is shown.

[0048] Figure 6 A flowchart illustrating a bearer configuration update method according to some embodiments of the present invention is shown.

[0049] Figure 7 A schematic diagram of the structure of a bearer configuration update system according to some embodiments of the present invention is shown.

[0050] Figure 8 A schematic diagram of a bearer configuration update device according to some embodiments of the present invention is shown.

[0051] Figure 9 A schematic diagram of a bearer configuration update device according to other embodiments of the present invention is shown. Detailed Implementation

[0052] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit the present invention or its application or use. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0053] Unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps described in these embodiments do not limit the scope of the invention.

[0054] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.

[0055] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0056] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0057] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0058] Figure 1 A schematic diagram of a multi-control plane wireless network architecture is shown according to some embodiments of the present invention. For example... Figure 1 As shown, the core network side has a core network control plane entity pool (CN-CP Pool) and a core network user plane entity pool (CN-UP Pool). The CN-CP Pool includes multiple core network control plane entities (CN-CP1 to CN-CPn), and the CN-UP Pool includes multiple core network user plane entities (CN-UP1 to CN-UPn). The base station side deploys multiple sets of base station control plane entities (CU-CP1 to CU-CP3) and user plane entities (CU-UP1 to CU-UP3). The base station's control plane entities are connected to the core network's control plane entities, and the base station's user plane entities are connected to the core network's user plane entities. Furthermore, each entity of the base station is connected to the base station's underlying entity (DU).

[0059] Figure 2 A flowchart illustrating a method for updating bearer configuration according to some embodiments of the present invention is shown. Figure 2 As shown, the method for updating the bearer configuration in this embodiment includes steps S202 to S214.

[0060] In step S202, the first control plane entity of the core network determines the second control plane entity of the core network involved in the service change sent by the user's terminal.

[0061] User-managed services include at least one of the following: added services, modified services, and deleted services.

[0062] In some embodiments, the first control plane entity of the core network receives a service change message sent by a user's terminal, wherein the service change message includes the changed service; if the changed service is not within the management scope of the first control plane entity of the core network, the first control plane entity of the core network determines the second control plane entity of the core network involved in the user's changed service.

[0063] In step S204, the first control plane entity of the core network sends a user information change request to the first control plane entity of the base station, wherein the user information change request includes the changed service information.

[0064] In some embodiments, a user information change request includes:

[0065] 1) The first control plane entity of the core network is the user identifier assigned to the user;

[0066] 2) The first control plane entity of the base station is the user identifier assigned to the user;

[0067] 3) Encapsulated NAS messages;

[0068] 4) Change the service list of the second control plane entity of the base station, and in the service list, the information of each service includes the service slice type, service identifier, and QoS identifier.

[0069] In step S206, the second control plane entity of the core network sends user configuration confirmation information to the second control plane entity of the base station, wherein the user configuration confirmation information includes changed service information.

[0070] In some embodiments, the user configuration confirmation information includes:

[0071] 1) The second control plane entity of the core network is the user identifier assigned to the user;

[0072] 2) User's wireless network capability configuration;

[0073] 3) Partial control plane indication message, used to indicate whether the configuration information of all user control planes is located in the second control plane entity of the core network; this message uses a boolean type, for example, so that different values ​​can be used to indicate different things.

[0074] 4) A list of slice identifiers, including one or more slice identifiers;

[0075] 5) The first control plane entity of the core network is a list of service types configured for users, and the list of service types includes the identifier of the PDU Session, the QoS identifier of the service (e.g., the uplink and downlink QoS identifiers of the corresponding service), and the QoS configuration information of the service (e.g., the uplink and downlink QoS configuration information of the corresponding service).

[0076] In step S208, the first control plane entity of the base station sends first user service configuration information to the underlying entity of the base station, wherein the first user service configuration information includes a first SRB list set.

[0077] In some embodiments, the first user service configuration information includes:

[0078] 1) The first control plane entity of the base station assigns a user identifier to the user, and the user identifier and the user identifier assigned to the user by the underlying entity of the base station can determine the unique index information of the user;

[0079] 2) User's wireless network capability configuration;

[0080] 3) The main control plane entity indicator is used to indicate whether the first control plane entity of the base station is the main control plane entity. The main control plane entity is used to configure basic parameters such as NAS and mobility, while other non-main control plane entities are configured incrementally. The main control plane entity indicator is, for example, a Boolean type so that different indications are given when different values ​​are taken.

[0081] 4) A first set of SRB lists, where each element is, for example, an enumeration type to indicate different SRB types;

[0082] 5) RRC message;

[0083] 6) The SRB identifier used in RRC messages.

[0084] In step S210, the second control plane entity of the base station sends second user service configuration information to the underlying entity of the base station. The second user service configuration information includes a second SRB list set, and the SRB types in the first SRB list set and the second SRB list set are different.

[0085] In some embodiments, the second user service configuration information includes:

[0086] 1) The second control plane entity of the base station assigns a user identifier to the user, and the user identifier and the user identifier assigned to the user by the underlying entity of the base station can determine the unique index information of the user;

[0087] 2) User's wireless network capability configuration;

[0088] 3) A second set of SRB lists, where each element is, for example, an enumeration type to indicate different SRB types.

[0089] Thus, the underlying entities of the base station can determine the mapping relationship with the base station control plane entities based on the SRB set information.

[0090] In step S212, when the second control plane entity of the base station receives the service configuration success message sent by the underlying entity of the base station, the second control plane entity of the base station sends RRC configuration information and the corresponding SRB identifier to the underlying entity of the base station.

[0091] In some embodiments, the RRC configuration information sent by the second control plane entity of the base station to the underlying entity of the base station includes:

[0092] 1) The second control plane entity of the base station is the user identifier assigned to the user;

[0093] 2) The underlying entity of the base station is the user identifier assigned to the user;

[0094] 3) Encapsulated RRC messages, for example, encapsulated as transparent containers for transmission;

[0095] 4) An SRB identifier, used to indicate the type of the SRB, and the type of the SRB belongs to the second SRB list set, the SRB identifier being, for example, an integer type.

[0096] In step S214, the underlying entity of the base station sends the RRC configuration information to the terminal based on the SRB identifier. The terminal can then configure itself according to the RRC configuration information.

[0097] Therefore, the terminal can determine the SRB type of the RRC message to be used based on the SRB type of the received RRC message or the SRB type corresponding to the service. Consequently, the base station's underlying entity can determine the base station control plane entity to which the RRC message needs to be forwarded based on the SRB type of the RRC message.

[0098] The method described in the above embodiments can configure different control plane nodes for different users and services. Different control plane nodes can independently send RRC messages to the terminal and independently configure the bearer services in the DU. Furthermore, by configuring different SRB sets for different control planes, the DU can distinguish different types of RRC messages and thus determine the target base station control plane entity corresponding to the RRC message to be sent, avoiding signaling waste caused by group-return RRC messages. The above embodiments support the dynamic addition, deletion, and modification process of control plane entities triggered by the core network, effectively supporting the dynamic configuration process of services with minimal impact on the terminal, and exhibiting good backward compatibility and deployment feasibility. The above embodiments enhance existing protocols without introducing new protocol processes, making implementation relatively simple.

[0099] The following is for reference. Figure 3 Describe the interaction flow between the first control plane entity and the second control plane entity on the core network side.

[0100] Figure 3A schematic diagram illustrating the interaction flow between the first control plane entity and the second control plane entity on the core network side is shown. Figure 3 As shown, the interaction process of this embodiment includes steps S302 to S304.

[0101] In step S302, the first control plane entity of the core network sends a service change request to the second control plane entity of the core network, wherein the service change request includes information about the changed service.

[0102] In some embodiments, a business change request includes:

[0103] 1) The first control plane entity of the core network is the user identifier assigned to the user;

[0104] 2) The second control plane entity of the core network is the user identifier assigned to the user;

[0105] 3) The user's PLMN list;

[0106] 4) A list of services to be changed, and for each service in the list, information including the service slice type and QoS identifier;

[0107] 5) The user's NAS message, the content of which is the same as the user's service change request.

[0108] In step S304, if at least one of the changed services is received by the second control plane entity of the core network, the second control plane entity of the core network sends a service change request response message to the first control plane entity of the core network.

[0109] In some embodiments, the business change request response message includes:

[0110] 1) The first control plane entity of the core network is the user identifier assigned to the user;

[0111] 2) The second control plane entity of the core network is the user identifier assigned to the user;

[0112] 3) If the second control plane entity of the core network rejects some of the changed services, the service change request response message also includes a list of rejected service information, which includes the slice type, QoS identifier and reason for rejection of the rejected service.

[0113] In some embodiments, the interaction process further includes step S306.

[0114] In step S306, if none of the changed services are received by the second control plane entity of the core network, the second control plane entity of the core network sends a service change request rejection message to the first control plane entity of the core network.

[0115] In some embodiments, the business change request rejection message includes:

[0116] 1) The first control plane entity of the core network is the user identifier assigned to the user;

[0117] 2) The second control plane entity of the core network is the user identifier assigned to the user;

[0118] 3) Reasons for refusal.

[0119] Through the above embodiments, multiple control plane entities in the core network can interact to confirm service changes.

[0120] The following is for reference. Figure 4 Describe the configuration process of the underlying entity of the base station when it accepts at least one of the changed services.

[0121] Figure 4 A schematic diagram of a configuration process according to some embodiments of the present invention is shown. For example... Figure 4 As shown, the configuration process of this embodiment includes steps S402 to S404.

[0122] In step S402, if the underlying entity of the base station accepts at least one of the changed services, it sends a service configuration success message to the first control plane entity and the second control plane entity of the base station.

[0123] In some embodiments, the service configuration success message includes:

[0124] 1) The underlying entity of the base station assigns a user identifier to the user;

[0125] 2) The control plane entity of the base station that receives the service configuration success message is the user identifier assigned to the user;

[0126] 3) The list of service identifiers assigned by this control plane to the underlying entity of the base station, including the service identifier and the service QoS identifier;

[0127] In some embodiments, if there is a service that the control plane entity of the base station receiving the service configuration success message does not accept, the service configuration success message may further include:

[0128] 4) A list of unacceptable service identifiers assigned by this control plane, including the identifier of the unacceptable service, the QoS identifier of the unacceptable service, and the reason for the failure to accept the service.

[0129] In step S404, the underlying entity of the base station determines the first SRB list set supported by the first control plane entity of the base station and the second SRB list set supported by the second control plane entity of the base station.

[0130] In some embodiments, the configuration process further includes step S406.

[0131] In step S406, the underlying entity of the base station maps the RRC message in the RRC configuration information to the corresponding SRB resource according to the SRB identifier, and sends the RRC configuration information to the terminal.

[0132] In some embodiments, a terminal configuration process is also included, as shown in steps S408 to S410.

[0133] In step S408, the terminal is configured according to the RRC configuration information.

[0134] In step S410, the terminal sends an RRC configuration complete message to the underlying entity of the base station.

[0135] In some embodiments, the underlying entity of the base station responds to the terminal's RRC configuration completion message, as shown in steps S412 to S414.

[0136] In step S412, the underlying entity of the base station determines the corresponding control plane entity of the base station based on the SRB type of the RRC configuration completion message.

[0137] In step S414, the underlying entity of the base station sends the RRC configuration complete message to the control plane entity of the corresponding base station.

[0138] In some embodiments, the underlying entity of the base station sends configuration response information to the control plane entity of the corresponding base station, and the configuration response information includes:

[0139] 1) The underlying entity of the base station is the user identifier assigned to the user;

[0140] 2) The corresponding base station control plane entity is the user identifier assigned to the user;

[0141] 3) RRC configuration complete message;

[0142] 4) SRB identifier.

[0143] In some embodiments, when the control plane entity of the corresponding base station is the first control plane entity of the base station and the RRC configuration completion message includes a NAS message, the first control plane entity of the base station sends the NAS message to the first control plane entity of the core network.

[0144] The following is for reference. Figure 5 This invention describes a signaling flow for the bearer configuration update method.

[0145] Figure 5 A schematic diagram of the signaling flow for a bearer configuration update method according to some embodiments of the present invention is shown. Figure 5As shown, the signaling flow of this embodiment includes steps S502 to S530.

[0146] In step S502, the UE sends a NAS Message to CN-CP1 (the first control plane entity of the core network) as a service change message, which includes the service that the user wants to change.

[0147] In step S504, CN-CP1 sends a CPconfiguration request to CN-CP2 (the second control plane entity of the core network) as a service change request, which includes information about the changed services.

[0148] In step S506, if CN-CP2 confirms that at least some of the services can be changed, it sends a CP configuration response as a service change request response message to CN-CP1, which includes a list of services accepted by CN-CP2 and a list of services rejected.

[0149] In step S508, CN-CP1 sends a UE contextModification request as a user information change request to CU-CP1 (the first control plane entity of the base station), which includes the changed service information and NAS message.

[0150] In step S510, CN-CP2 sends UE contextModification as user configuration confirmation information to CU-CP2 (the second control plane entity of the base station), which includes the changed service information.

[0151] In step S512, CU-CP1 sends UE context Modification as the first user service configuration information to DU (the underlying entity of the base station), which includes the first SRB list set.

[0152] In step S514, DU confirms the SRB supported by CU-CP1 and sends a UE contextModification Response to CU-CP1 as a service configuration success message.

[0153] In step S516, the DU sends RRC Connection Reconfig as RRC configuration information to the UE.

[0154] In step S518, the UE sends an RRC Connection Reconfig Complete message to the DU, which is a response to the service configuration corresponding to CU-CP1.

[0155] In step S520, DU confirms that the response to RRC Connection Reconfig Complete is for CU-CP1 based on the SRB type corresponding to RRC Connection Reconfig Complete, and therefore sends a UL RRC Message to CU-CP1.

[0156] In step S522, CU-CP2 sends Initial UE context Setup to DU as the second user service configuration information, which includes a second SRB list set, the SRB types in this set being different from the SRB types in the first SRB list set.

[0157] In step S524, if the changed service is acceptable, DU confirms the SRB supported by CU-CP2 and sends an Initial UE context Response to CU-CP2 as a service configuration success message.

[0158] In step S526, the DU sends RRC Connection Reconfig as RRC configuration information to the UE.

[0159] In step S528, the UE sends an RRC Connection Reconfig Complete message to the DU, which is a response to the service configuration of CU-CP2.

[0160] In step S530, DU confirms that the response to RRC Connection Reconfig Complete is for CU-CP2 based on the SRB type corresponding to RRC Connection Reconfig Complete, and therefore sends a UL RRC Message to CU-CP2.

[0161] The following describes an example application of the bearer configuration update method of the present invention, using an application scenario as an example.

[0162] Figure 6 A flowchart illustrating a bearer configuration update method according to some embodiments of the present invention is shown. Figure 6 As shown, the bearer configuration update method in this embodiment includes steps S602 to S626. This embodiment only shows some steps in the signaling interaction process, not all steps.

[0163] In scenarios with multiple control plane nodes, the UE and network have already established a default bearer using control plane entity CP1. Since the terminal needs to request a vertical industry service, it requires the use of control plane entity CP2, which is deployed in a different location. Core network control plane entity CN-CP1 is primarily responsible for the default bearer, while core network control plane entity CN-CP2 is primarily responsible for the vertical industry service. Furthermore, CP2 primarily uses SRB5, on which no NAS layer messages are transmitted, but its scheduling priority is higher than other SRBs.

[0164] In step S602, CN-CP1 determines, based on the service request message sent by the user's terminal, that the service type the user needs to update is a vertical industry URLLC service, and that this service is not within the management scope of CN-CP1. Since this service request message involves a service change, it can be considered a service change message.

[0165] In step S604, CN-CP1 sends a service change request to CN-CP2 via the interface. The service change request includes the user identifier assigned by CN-CP1, the user identifier assigned by CN-CP2, the list of PLMNs used by the user, the list of services that CP2 needs to add (including slice type and service QoS identifier), and a forwarded NAS message (the content of which is the same as the service request message sent by the terminal).

[0166] In step S606, CN-CP2 determines whether the changed service is acceptable. If acceptable, it sends a service change request response message to CN-CP1, including: the user identifier assigned by CN-CP1 and the user identifier assigned by CN-CP2.

[0167] In step S608, CN-CP1 sends a user information change request to the base station control plane entity CU-CP1, including: the user identifier assigned by CN-CP1, the user identifier assigned by CU-CP1, the encapsulated NAS message, and the service list to be changed to other base station control plane entities.

[0168] In step S610, after CN-CP2 sends a service change request response to CN-CP1, CN-CP2 sends user configuration confirmation information to the base station control plane entity CU-CP2, including: the user identifier assigned by CN-CP2, the user's radio network capability configuration, a partial control plane indication message whose value indicates that all control plane configuration information of the user is located in CP2, a slice identifier list (including one or more slice identifiers), and a list of service types configured by CN-CP1 for the user (including the identifier of PDUSession, the QoS identifier of the service, and the QoS configuration information of the service).

[0169] In step S612, after receiving a user information change request, if the message contains service list information that has been changed to other base station control plane nodes, CU-CP1 generates first user service configuration information and sends it to the base station underlying entity DU. The first user service configuration information includes: the user identifier assigned by CU-CP1, the user's radio network capability configuration, and a main control plane entity indication, the value of which indicates that CU-CP1 is the main control plane entity.

[0170] If the message does not contain information about the service list that has been changed to other base station control plane nodes, no further action will be taken.

[0171] In step S614, after receiving the user configuration confirmation information, the base station control plane entity CU-CP2 determines that the added configuration information can be accepted by CU-CP2, and then generates second user service configuration information and sends it to DU, including: the user identifier assigned by CU-CP2, the user's radio network capability configuration, RRC message, second SRB list set (SRB#5), and SRB ID with a value of 5.

[0172] In step S616, after receiving the user service configuration information sent by CU-CP1 and CU-CP2, the DU determines whether the services added in the above information are acceptable. If so, it sends a service configuration success message to the corresponding base station control plane entity and simultaneously determines the SRB list information supported by the base station control plane entity. The service configuration success message includes: the identifier assigned to the user by the DU (the identifier assigned between the underlying entity and the base station control plane entity that sent the message), the identifier assigned to the user by the base station control plane entity (the user identifier assigned by the destination control plane entity of the message), a list of acceptable service identifiers assigned by this control plane, a list of unacceptable service identifiers assigned by this control plane (optional, including the reason for failure), and whether to only respond to the indication of the base station control plane entity (optional, if yes, it means that the DU only sends response information to the base station control plane entity).

[0173] In step S618, when CU-CP2 receives the service configuration success message, it generates the user's RRC configuration information and sends it to DU through the interface between CU-CP2 and DU. The RRC configuration information carried by this SRB type does not affect the configuration results of other similar SRB RRC messages. The RRC configuration information includes: the identifier assigned to the user by CU-CP2, the identifier assigned to the user by DU, the RRC message (encapsulated in a transparent container for transmission), and the SRB identifier (an integer type, the value of which indicates the type of SRB, which should belong to the second SRB list).

[0174] In step S620, after receiving the RRC configuration information sent by CU-CP2, DU maps the RRC message to the resource of the corresponding SRB according to the SRB identifier, and sends the RRC configuration information to the terminal.

[0175] In step S622, the terminal completes the configuration of relevant parameters and services based on the received RRC configuration information and sends an RRC configuration completion message to the DU. The terminal determines whether to perform only incremental operations for new bearer changes based on the SRB type of the RRC message in the RRC configuration information, so as not to affect the configuration of other services, measurements, etc.

[0176] In step S624, after receiving the RRC configuration complete message from the terminal, the DU determines, based on its SRB type, which base station control plane entity the configuration response information containing the RRC message needs to be sent to. The configuration response information includes: the user identifier assigned by the DU, the user identifier assigned by the base station control plane entity, the RRC message, and the SRB identifier.

[0177] In step S626, after receiving the configuration response information, the base station control plane entity confirms that the configuration on the user side has been successful. If the base station control plane entity receiving the configuration response information is CU-CP1 and the RRC message contains a NAS message, then CU-CP1 needs to send the user's NAS message to CN-CP1.

[0178] The following is for reference. Figure 7 An embodiment of the configuration update system of the present invention is described.

[0179] Figure 7 A schematic diagram of the structure of a bearer configuration update system according to some embodiments of the present invention is shown. Figure 7As shown, the system 70 of this embodiment includes: a first control plane entity 710 of the core network, configured to determine the second control plane entity of the core network involved in the service change sent by the user's terminal; send a user information change request to the first control plane entity of the base station, wherein the user information change request includes changed service information; a second control plane entity 720 of the core network, configured to send user configuration confirmation information to the second control plane entity of the base station, wherein the user configuration confirmation information includes changed service information; and a first control plane entity 730 of the base station, configured to send a first user service configuration to the underlying entity of the base station. The system includes a first user service configuration information set, wherein the first user service configuration information includes a first SRB list set; the second control plane entity 740 of the base station is configured to send the second user service configuration information to the underlying entity of the base station, wherein the second user service configuration information includes a second SRB list set, and the SRB types in the first SRB list set and the second SRB list set are different; upon receiving a service configuration success message sent by the underlying entity of the base station, the system sends RRC configuration information and the corresponding SRB identifier to the underlying entity of the base station; the underlying entity 750 of the base station is configured to send the RRC configuration information to the terminal according to the SRB identifier.

[0180] In some embodiments, the first control plane entity 710 of the core network is further configured to receive a service change message sent by a user's terminal, wherein the service change message includes a changed service; and if the changed service is not within the management scope of the first control plane entity of the core network, determine the second control plane entity of the core network involved in the user's changed service.

[0181] In some embodiments, the first control plane entity 710 of the core network is further configured to send a service change request to the second control plane entity of the core network, wherein the service change request includes information about the changed service; and if at least one of the changed services is received by the second control plane entity of the core network, the core network receives a service change request response message sent by the second control plane entity of the core network.

[0182] In some embodiments, the second control plane entity 720 of the core network is further configured to send a service change request rejection message to the first control plane entity of the core network if the changed services are not received by the second control plane entity of the core network.

[0183] In some embodiments, the underlying entity 750 of the base station is further configured to send a service configuration success message to the first control plane entity and the second control plane entity of the base station when accepting at least one of the changed services; and to determine the first SRB list set supported by the first control plane entity of the base station and the second SRB list set supported by the second control plane entity of the base station.

[0184] In some embodiments, the RRC configuration information sent by the second control plane entity 740 of the base station to the underlying entity of the base station includes: a user identifier assigned to the user by the second control plane entity of the base station; a user identifier assigned to the user by the underlying entity of the base station; an encapsulated RRC message; and an SRB identifier, used to indicate the type of SRB, wherein the type of SRB belongs to a second SRB list set.

[0185] In some embodiments, the underlying entity 750 of the base station is further configured to map the RRC message in the RRC configuration information to the corresponding SRB resource according to the SRB identifier, and send the RRC configuration information to the terminal.

[0186] In some embodiments, the underlying entity 750 of the base station is further configured to obtain an RRC configuration completion message sent by the terminal, wherein the RRC configuration completion message is sent by the terminal after configuring according to the RRC configuration information; determine the control plane entity of the corresponding base station according to the SRB type of the RRC configuration completion message; and send the RRC configuration completion message to the control plane entity of the corresponding base station.

[0187] In some embodiments, the first control plane entity 730 of the base station is further configured to send a NAS message to the first control plane entity of the core network if the RRC configuration completion message includes a NAS message.

[0188] In some embodiments, the update system 70 further includes: a terminal 760 configured to configure according to RRC configuration information; and to send an RRC configuration completion message to the underlying entity of the base station.

[0189] Figure 8 A schematic diagram of a bearer configuration update apparatus according to some embodiments of the present invention is shown. The bearer configuration update apparatus can be any one of the following: a first control plane entity of the core network, a second control plane entity of the core network, a first control plane entity of the base station, a second control plane entity of the base station, a lower-level entity of the base station, or a terminal. Figure 8 As shown, the bearer configuration update apparatus 80 of this embodiment includes: a memory 810 and a processor 820 coupled to the memory 810. The processor 820 is configured to execute the bearer configuration update method of any of the foregoing embodiments based on instructions stored in the memory 810.

[0190] The memory 810 may include, for example, system memory, fixed non-volatile storage media, etc. The system memory may store, for example, the operating system, application programs, boot loader, and other programs.

[0191] Figure 9A schematic diagram of a bearer configuration update apparatus according to other embodiments of the present invention is shown. The bearer configuration update apparatus can be any one of the following: a first control plane entity of the core network, a second control plane entity of the core network, a first control plane entity of the base station, a second control plane entity of the base station, a lower-level entity of the base station, or a terminal. Figure 9 As shown, the configuration update device 90 of this embodiment includes a memory 910 and a processor 920, and may also include an input / output interface 930, a network interface 940, a storage interface 950, etc. These interfaces 930, 940, 950, and the memory 910 and processor 920 can be connected, for example, via a bus 960. The input / output interface 930 provides a connection interface for input / output devices such as a display, mouse, keyboard, and touchscreen. The network interface 940 provides a connection interface for various networked devices. The storage interface 950 provides a connection interface for external storage devices such as SD cards and USB flash drives.

[0192] Embodiments of the present invention also provide a computer-readable storage medium having a computer program stored thereon, characterized in that the program, when executed by a processor, implements any of the aforementioned methods for updating the bearer configuration.

[0193] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0194] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0195] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0196] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0197] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for updating a carrying configuration, comprising: The first control plane entity of the core network determines the second control plane entity of the core network involved in the service change message sent by the user's terminal; The first control plane entity of the core network sends a user information change request to the first control plane entity of the base station, wherein the user information change request includes changed service information; The second control plane entity of the core network sends user configuration confirmation information to the second control plane entity of the base station, wherein the user configuration confirmation information includes the changed service information; The first control plane entity of the base station sends first user service configuration information to the underlying entity of the base station, wherein the first user service configuration information includes a first signaling radio bearer (SRB) list set. The second control plane entity of the base station sends second user service configuration information to the underlying entity of the base station. The second user service configuration information includes a second SRB list set, and the SRB types in the first SRB list set and the second SRB list set are different. When the second control plane entity of the base station receives a service configuration success message sent by the underlying entity of the base station, the second control plane entity of the base station sends Radio Resource Control (RRC) configuration information and the corresponding SRB identifier to the underlying entity of the base station. The underlying entity of the base station sends the RRC configuration information to the terminal based on the SRB identifier.

2. The update method according to claim 1, wherein, The first control plane entity of the core network determines the second control plane entity of the core network involved in the service change message sent by the user's terminal, including: The first control plane entity of the core network receives a service change message sent by a user's terminal, wherein the service change message includes the changed service; If the changed service is not within the management scope of the first control plane entity of the core network, the first control plane entity of the core network determines the second control plane entity of the core network involved in the user's changed service.

3. The updating method according to claim 2 further includes: The first control plane entity of the core network sends a service change request to the second control plane entity of the core network, wherein the service change request includes information about the service to be changed; If at least one of the changed services is received by the second control plane entity of the core network, the second control plane entity of the core network sends a service change request response message to the first control plane entity of the core network.

4. The updating method according to claim 3, wherein, The business change request includes: The first control plane entity of the core network is the user identifier assigned to the user. The second control plane entity of the core network is the user identifier assigned to the user. The user's list of Public Land Mobile Networks (PLMNs); The changed service list includes information for each service, such as the slice type and Quality of Service (QoS) identifier. The user's non-access stratum NAS message.

5. The updating method according to claim 3 further includes: If none of the modified services are received by the second control plane entity of the core network, the second control plane entity of the core network sends a service change request rejection message to the first control plane entity of the core network.

6. The update method according to claim 1, wherein, The user information change request includes: The first control plane entity of the core network is the user identifier assigned to the user. The first control plane entity of the base station is the user identifier assigned to the user. Encapsulated NAS messages; The service list of the second control plane entity of the base station is changed, and the information of each service in the service list includes the slice type, service identifier, and QoS identifier of the service.

7. The updating method according to claim 1, wherein, The user configuration confirmation information includes: The second control plane entity of the core network is the user identifier assigned to the user. The user's wireless network capability configuration; A partial control plane indication message is used to indicate whether the configuration information of all control planes of the user is located in the second control plane entity of the core network; A list of slice identifiers, including one or more slice identifiers; The first control plane entity of the core network is the service type list configured by the user, and the service type list includes the identifier of the Protocol Data Unit Session (PDU Session), the QoS identifier of the service, and the QoS configuration information of the service.

8. The updating method according to claim 1, wherein, The first user service configuration information includes: The first control plane entity of the base station is the user identifier assigned to the user. The user's wireless network capability configuration; The main control plane entity indicator is used to indicate whether the first control plane entity of the base station is a main control plane entity. First SRB list set; RRC message; The SRB identifier used in the RRC message.

9. The updating method according to claim 1, wherein, The second user service configuration information includes: The second control plane entity of the base station is the user identifier assigned to the user. The user's wireless network capability configuration; Second SRB list set.

10. The updating method according to claim 1, further comprising: When the underlying entity of the base station accepts at least one of the changed services, it sends a service configuration success message to the first control plane entity and the second control plane entity of the base station. The underlying entity of the base station determines the first SRB list set supported by the first control plane entity of the base station, and the second SRB list set supported by the second control plane entity of the base station.

11. The updating method according to claim 10, wherein: The successful service configuration message includes: The underlying entity of the base station is the user identifier assigned to the user. The control plane entity of the base station that receives the service configuration success message is the user identifier assigned to the user. The base station underlying entity receives a list of service identifiers assigned by this control plane, including the service identifier and the service QoS identifier. In the event that the control plane entity of the base station receiving the service configuration success message does not accept a service, the service configuration success message further includes: A list of unacceptable service identifiers assigned by this control plane, including the identifier of the unacceptable service, the QoS identifier, and the reason for the failure to accept the service.

12. The updating method according to claim 1, wherein, The RRC configuration information sent by the second control plane entity of the base station to the underlying entity of the base station includes: The second control plane entity of the base station is the user identifier assigned to the user. The underlying entity of the base station is the user identifier assigned to the user; Encapsulated RRC message; An SRB identifier is used to indicate the type of an SRB, and the type of the SRB belongs to a second SRB list set.

13. The updating method according to claim 12, wherein, The underlying entity of the base station maps the RRC message in the RRC configuration information to the corresponding SRB resource according to the SRB identifier, and sends the RRC configuration information to the terminal.

14. The updating method according to claim 1, further comprising: The terminal is configured according to the RRC configuration information; The terminal sends an RRC configuration complete message to the underlying entity of the base station.

15. The updating method according to claim 14, further comprising: The underlying entity of the base station obtains the RRC configuration complete message sent by the terminal; The underlying entity of the base station determines the corresponding control plane entity of the base station based on the SRB type of the RRC configuration completion message. The underlying entity of the base station sends the RRC configuration complete message to the control plane entity of the corresponding base station.

16. The updating method according to claim 15, wherein, The underlying entity of the base station sends configuration response information to the control plane entity of the corresponding base station, and the configuration response information includes: The underlying entity of the base station is the user identifier assigned to the user; The control plane entity of the corresponding base station is the user identifier assigned to the user. RRC configuration complete message; SRB designation.

17. The updating method according to claim 15, further comprising: If the control plane entity of the corresponding base station is the first control plane entity of the base station, and the RRC configuration completion message includes a NAS message, the first control plane entity of the base station sends the NAS message to the first control plane entity of the core network.

18. A configuration update system, comprising: The first control plane entity of the core network is configured to determine the second control plane entity of the core network involved in the service change sent by the user's terminal; Send a user information change request to the first control plane entity of the base station, wherein the user information change request includes changed service information; The second control plane entity of the core network is configured to send user configuration confirmation information to the second control plane entity of the base station, wherein the user configuration confirmation information includes the changed service information; The first control plane entity of the base station is configured to send first user service configuration information to the underlying entity of the base station, wherein the first user service configuration information includes a first SRB list set. The second control plane entity of the base station is configured to send second user service configuration information to the underlying entity of the base station, wherein the second user service configuration information includes a second SRB list set, and the SRB types in the first SRB list set and the second SRB list set are different; upon receiving a service configuration success message sent by the underlying entity of the base station, it sends RRC configuration information and the corresponding SRB identifier to the underlying entity of the base station. The underlying entity of the base station is configured to send the RRC configuration information to the terminal based on the SRB identifier.

19. The update system according to claim 18, wherein, The first control plane entity of the core network is further configured to receive service change messages sent by user terminals, wherein the service change messages include changed services; and, if the changed services are not within the management scope of the first control plane entity of the core network, to determine the second control plane entity of the core network involved in the user's changed services.

20. The update system according to claim 19, wherein, The first control plane entity of the core network is further configured to send a service change request to the second control plane entity of the core network, wherein the service change request includes information about the changed service; and if at least one of the changed services is received by the second control plane entity of the core network, receive a service change request response message sent by the second control plane entity of the core network.

21. The update system according to claim 19, wherein, The second control plane entity of the core network is further configured to send a service change request rejection message to the first control plane entity of the core network if none of the changed services are received by the second control plane entity of the core network.

22. The update system according to claim 18, wherein, The underlying entity of the base station is further configured to send a service configuration success message to the first control plane entity and the second control plane entity of the base station when at least one of the changed services is accepted. Determine the first SRB list set supported by the first control plane entity of the base station, and the second SRB list set supported by the second control plane entity of the base station.

23. The update system according to claim 18, wherein, The RRC configuration information sent by the second control plane entity of the base station to the underlying entity of the base station includes: The second control plane entity of the base station is the user identifier assigned to the user. The underlying entity of the base station is the user identifier assigned to the user; Encapsulated RRC message; An SRB identifier is used to indicate the type of an SRB, and the type of the SRB belongs to a second SRB list set.

24. The update system according to claim 23, wherein, The underlying entity of the base station is further configured to map the RRC message in the RRC configuration information to the corresponding SRB resource according to the SRB identifier, and send the RRC configuration information to the terminal.

25. The update system according to claim 18, wherein, The underlying entity of the base station is further configured to obtain an RRC configuration completion message sent by the terminal, wherein the RRC configuration completion message is sent by the terminal after configuration based on the RRC configuration information; determine the control plane entity of the corresponding base station based on the SRB type of the RRC configuration completion message; and send the RRC configuration completion message to the control plane entity of the corresponding base station.

26. The update system according to claim 25, wherein the first control plane entity of the base station is further configured to send the NAS message to the first control plane entity of the core network if the RRC configuration completion message includes a NAS message.

27. The update system according to claim 18, further comprising: The terminal is configured to be configured according to the RRC configuration information; Send an RRC configuration complete message to the underlying entity of the base station.

Images