COMMUNICATION METHOD AND COMMUNICATIONS DEVICE IN DISTRIBUTED UNIT ARCHITECTURE

专利摘要:
this application provides a communication method, a communications device, and a chip in a distributed unit architecture - centralized unit. the method includes: receiving, through a centralized unit control plan entity (cu-cp) from an access network, an interface adjustment request message from a centralized unit user plan entity (cu-up) the access network, where the interface adjustment request message comprises information about a network slice supported by the cu-up; and send, through the cu-cp, an interface adjustment response message to the cu-up after receiving the interface adjustment request message. information about the network slice supported by the cu-up includes: an identity of a tracking area served by the cu-up and a network slice identifier corresponding to the tracking area, an identity of a cell served by the cu-up and a network slice identifier corresponding to the cell, or an identity of a public terrestrial mobile network served by the cu-up and a network slice identifier corresponding to the public terrestrial mobile network. the interface adjustment request message also comprises capacity information of the network slice supported by the cu-up.
公开号:BR112020016564A2
申请号:R112020016564-6
申请日:2019-01-04
公开日:2020-12-22
发明作者:Yinghao Jin；Feng Han；Hang Zhang；Wei Tan
申请人:Huawei Technologies Co., Ltd.；
IPC主号:

专利说明:

[0001] [0001] This application refers to the field of communications technologies and, in particular, a communication method and a communications device. BACKGROUND
[0002] [0002] With the development of communications technologies, a new network architecture is proposed, and the functions of a base station in an access network are separated. Some functions of the base station are implanted in a centralized unit (Centralized Unit, CU), and other functions are implanted in a distributed unit (Distributed Unit, DU). In some cases, CU is even more separate. For example, CU can include a CU control plan (CU-CP) and a CU user plan (CU-UP). In such a network architecture, how to ensure normal communication is a problem worth considering. SUMMARY
[0003] [0003] This application provides a communication method and a communications device, to ensure normal communication in the previous network architecture.
[0004] [0004] According to a first aspect, a communication method is provided and includes: receiving, by a centralized unit control plan entity CU-CP from an access network, an interface adjustment request message from an CU-UP centralized unit user plan entity of the access network, where the interface adjustment request message comprises information about a network slice supported by CU-UP; and send at
[0005] [0005] In this mode, CU-UP sends the interface adjustment request, so that CU-CP obtains the network slice supported by CU-UP. In this case, considering the network slice, CU-CP can select a suitable CU-UP for a session or a carrier with reference to the network slice supported by CU-UP, to avoid a session or carrier adjustment failure caused when CU-UP does not support a network slice corresponding to the session or the bearer, to avoid communication interruption, and to guarantee normal communication. In addition, CU-UP sends the interface adjustment request, so that CU-CP obtains the network slice supported by CU-UP as soon as possible. It is not necessary for CU-CP to start, just by adjusting a session or a carrier, obtaining the network slice supported by CU-UP, thus saving signal overloads, avoiding latency and also guaranteeing efficient and normal communication.
[0006] [0006] In a possible project, information about the network slice supported by CU-UP includes: an identity from a tracking area served by CU-UP and a network slice identifier corresponding to the tracking area, an identity from a cell served by CU-UP and a network slice identifier corresponding to the cell, or an identity of a public terrestrial mobile network served by CU-UP and a network slice identifier corresponding to the public terrestrial mobile network. In this case, the CU-CP can also understand a difference between network slices implanted in CU-UPs in a TA granularity, a cell granularity or an operator granularity, thus ensuring even more normal communication.
[0007] [0007] In a possible project, the interface adjustment request message also includes information on the network slice capacity supported by CU-UP. The network slice supported by CU-UP can include a network slice whose resource is isolated. The network slice supported by CU-UP may alternatively include a network slice whose resource is shared. The interface adjustment request message also includes capacity information of the network slice supported by CU-UP, so that CU-CP knows the capacity information of the network slice in detail, to avoid session rejection caused due to error in judgment of the capacity information, further avoid communication interruption, and guarantee the quality of the communication.
[0008] [0008] In a possible project, the CU-CP sends, to a central network device, information about a network slice supported by the access network, and the network slice supported by the access network includes a network slice supported by both CU-CP and CU-UP.
[0009] [0009] In a possible project, the method also includes: sending, through CU-CP, a load request message to CU-UP, where the load request message is used to request obtaining load information from network slice supported by CU-UP. Optionally, the load request message comprises an identifier of the network slice supported by CU-UP.
[0010] [0010] In a possible project, the interface adjustment request message also includes CU-UP service range information. Service band information includes at least one of the following: the identity of the cell served by CU-UP, the identity of the tracking area served by CU-UP, an identity of a DU distributed unit connected to CU-UP, or identity of the public terrestrial mobile network served by CU-UP. The information can help CU-CP to select the appropriate CU-UP to serve the UE and ensure normal communication.
[0011] [0011] In a possible project, the interface adjustment response message comprises information about a network slice supported by CU-CP.
[0012] [0012] In a possible project, the interface adjustment response message comprises capacity information of the network slice supported by CU-CP.
[0013] [0013] According to a second aspect, a communication method is provided, which includes: sending, through a CU-UP centralized user plan entity of an access network, an interface adjustment request message to an access network CU-CP centralized unit control plan entity, where the interface adjustment request message comprises information about a network slice supported by CU-UP; and receive a CU-CP interface adjustment response message via CU-UP.
[0014] [0014] In a possible project, information about the network slice supported by CU-UP includes: an identity of a tracking area served by CU-UP and a network slice identifier corresponding to the tracking area, an identity of a cell served by CU-UP and a network slice identifier corresponding to the cell, or an identity of a public terrestrial mobile network served by CU-UP and a network slice identifier corresponding to the public terrestrial mobile network.
[0015] [0015] In a possible project, the interface adjustment request message also includes information on the network slice capacity supported by CU-UP.
[0016] [0016] In a possible project, the method also includes: receiving, through CU-UP, a configuration message from a network management system, where the configuration message comprises information about the network slice supported by CU-UP . The network management system directly configures, for CU-UP, information about the network slice supported by CU-UP, to avoid a routing process in which information about the network slice supported by CU-UP is first configured for CU-CP and then forwarded to CU-UP, and reduce signaling overloads.
[0017] [0017] In a possible project, the method also includes: receiving, through CU-UP, a load request message from CU-CP, where the load request message is used to request to obtain slice load information support supported by CU-UP. In addition, optionally, a network slice identifier supported by CU-UP is carried in the load request message.
[0018] [0018] In a possible project, the interface adjustment request message also includes CU-UP service range information. Service band information includes at least one of the following: the identity of the cell served by CU-UP, the identity of the tracking area served by CU-UP, an identity of a DU distributed unit connected to CU-UP, or identity of the public terrestrial mobile network served by CU-UP.
[0019] [0019] According to a third aspect, a communications device is provided. The communications device is a CU-CP centralized unit control plan entity of an access network. The communications device includes a receiver, configured to receive an interface adjustment request message from a CU-UP centralized user plan entity of the access network, where the interface adjustment request message comprises information about a network slice supported by CU-UP. The communications device also includes a first transmitter, configured to send an interface adjustment response message to the CU-UP.
[0020] [0020] In a possible project, the information about the network slice supported by CU-UP includes: an identity of a tracking area served by CU-UP and a network slice identifier corresponding to the tracking area, an identity of a cell served by CU-UP and a network slice identifier corresponding to the cell, or an identity of a public terrestrial mobile network served by CU-UP and a network slice identifier corresponding to the public terrestrial mobile network.
[0021] [0021] In a possible project, the interface adjustment request message also includes information on the network slice capacity supported by CU-UP.
[0022] [0022] In a possible design, the device also includes a second transmitter. The second transmitter is configured to send information about a network slice supported by the access network to a central network device. The network slice supported by the access network includes a network slice supported by both CU-CP and CU-UP.
[0023] [0023] In a possible project, the first transmitter is still configured to send a load request message to CU-UP. The load request message is used to request the obtaining of load information for the network slice supported by CU-UP. In addition, optionally, a network slice identifier supported by CU-UP is carried in the load request message.
[0024] [0024] In a possible project, the interface adjustment request message also includes CU-UP service range information. Service band information includes at least one of the following: the identity of the cell served by CU-UP, the identity of the tracking area served by CU-UP, an identity of a DU distributed unit connected to CU-UP, or identity of the public terrestrial mobile network served by CU-UP.
[0025] [0025] According to a fourth aspect, a communications device is provided. The communications device is a CU-UP centralized user plan entity of an access network. The communications device includes a transmitter, configured to send an interface adjustment request message to a centralized CU-CP unit control plan entity of the access network. The interface adjustment request message comprises information about a network slice supported by CU-UP. The communications device also includes a first receiver, configured to receive a CU-CP interface adjustment response message.
[0026] [0026] In a possible project, the information about the network slice supported by CU-UP includes: an identity of a tracking area served by CU-UP and a network slice identifier corresponding to the tracking area, an identity of a cell served by CU-UP and a network slice identifier corresponding to the cell, or an identity of a public terrestrial mobile network served by CU-UP and a network slice identifier corresponding to the public terrestrial mobile network.
[0027] [0027] In a possible project, the interface adjustment request message also includes information on the network slice capacity supported by CU-UP.
[0028] [0028] In a possible project, the communications device also includes a second receiver. The second receiver is configured to receive a configuration message from a network management system. The configuration message comprises information about the network slice supported by CU-UP.
[0029] [0029] In a possible project, the first receiver is still configured to receive a load request message from CU-CP. The load request message is used to request the obtaining of load information for the network slice supported by CU-UP. In addition, optionally, a network slice identifier supported by CU-UP is carried in the load request message.
[0030] [0030] In a possible project, the interface adjustment request message also includes CU-UP service range information. Service band information includes at least one of the following: the identity of the cell served by CU-UP, the identity of the tracking area served by CU-UP, an identity of a DU distributed unit connected to CU-UP, or identity of the public terrestrial mobile network served by CU-UP.
[0031] [0031] According to a fifth aspect, a communication method is provided, and includes: receiving, by a centralized unit control plan entity CU-CP from an access network, a configuration message from a management system network, where the configuration message comprises information about a slice network supported by a CU-UP centralized unit user plan entity of the access network; receive a CU-UP interface adjustment request message from CU-CP; and sending, via CU-CP, an interface adjustment response message to CU-UP, where the interface adjustment response message comprises information about the network slice supported by CU-UP.
[0032] [0032] In a possible project, information about the network slice supported by CU-UP includes: an identity of a tracking area served by CU-UP and a network slice identifier corresponding to the tracking area, an identity of a cell served by CU-UP and a network slice identifier corresponding to the cell, or an identity of a public terrestrial mobile network served by CU-UP and a network slice identifier corresponding to the public terrestrial mobile network.
[0033] [0033] In a possible project, the CU-CP sends, to a central network device, information about a network slice supported by the access network, and the network slice supported by the access network includes a network slice supported by both CU-CP and CU-UP.
[0034] [0034] In a possible project, the method also includes:
[0035] [0035] In a possible project, information about a distributed unit that belongs to the access network and that is connected to CU-UP is later transported in the interface adjustment request message.
[0036] [0036] In accordance with a sixth aspect, a communication method is provided, which includes: sending, through a CU-UP centralized user plan entity of an access network, an interface adjustment request message to a CU-CP centralized unit control plan entity of the access network; and receiving, through CU-UP, a CU-CP interface adjustment response message, where the interface adjustment response message comprises information about a network slice supported by CU-UP.
[0037] [0037] In a possible project, information about the network slice supported by CU-UP includes: an identity of a tracking area served by CU-UP and a network slice identifier corresponding to the tracking area, an identity of a cell served by CU-UP and a network slice identifier corresponding to the cell, or an identity of a public terrestrial mobile network served by CU-UP and a network slice identifier corresponding to the public terrestrial mobile network.
[0038] [0038] In a possible project, the method also includes: receiving, through CU-UP, a configuration message from a network management system, where the configuration message comprises information about the network slice supported by CU-UP .
[0039] [0039] In a possible project, the method also includes: receiving, through CU-UP, a load request message from CU-CP, where the load request message is used to request obtaining load information from the slice support supported by CU-UP. In addition, optionally, a network slice identifier supported by CU-UP is carried in the load request message.
[0040] [0040] In a possible project, information about a distributed unit that belongs to the access network and that is connected to CU-UP is later transported in the interface adjustment request message.
[0041] [0041] According to a seventh aspect, a communication method is provided, and includes: receiving, by a centralized CU unit of an access network, an interface adjustment request message from a distributed DU unit of the access network , where the interface adjustment request message comprises information identifying an access network notification area to which a cell served by the DU belongs; and send, through CU, an interface adjustment response message to the DU.
[0042] [0042] In a possible project, CU includes a CU CU-CP control plan entity and a CU CU-UP user plan entity. The receipt by a CU of an interface adjustment request message from a DU includes: receiving, by CU-CP, of the DU interface adjustment request message.
[0043] [0043] In a possible project, information about CU-
[0044] [0044] In a possible project, the capacity information of the network slice supported by DU is still carried in the interface adjustment request message.
[0045] [0045] In accordance with an eighth aspect, a communication method is provided and includes: sending, through a DU distributed unit of an access network, an interface adjustment request message to a centralized CU unit of the access network, where the interface adjustment request message comprises information identifying an access network notification area to which a cell served by the DU belongs; and receive, through the DU, a response message from CU's interface adjustment.
[0046] [0046] In a possible project, the sending, by a DU, of an interface adjustment request message to a CU includes: sending, by the DU, of the interface adjustment request message to a control plan entity CU CU-CP.
[0047] [0047] In a possible project, the information about the CU-UP connected to the DU is later transported in the interface adjustment request message.
[0048] [0048] In a possible project, the capacity information of the network slice supported by the DU is still carried in the interface adjustment request message.
[0049] [0049] In accordance with a ninth aspect, a communication method is provided, which includes: sending, by a centralized CU unit of an access network, a command message of context release of EU user equipment to a distributed unit DU of the access network; and receiving, by CU, a full UE context release message sent by the DU, in which a UE context in the DU is carried in the full context release message.
[0050] [0050] In a possible project, the indication information is carried in the UE context release command message, and the indication information is used to indicate that the CU needs to set the UE from a connected state to an inactive state.
[0051] [0051] In a possible project, the indication information is carried in the UE context release command message, and the indication information is used to indicate that the CU needs the UE context in the DU.
[0052] [0052] In a possible project, the UE context in the DU includes at least one of the following: identification information corresponding to a DU-adjusted carrier for the UE, logical carrier configuration information, logical channel identification information carrier information, RLC layer configuration information, MAC layer configuration information, and carrier PHY layer configuration information, UE C-RNTI identification information, and information about a cell accessed by the UE in the DU or information about a cell accessible by the UE in the DU.
[0053] [0053] In accordance with a tenth aspect, a communication method is provided, and includes: receiving, by a DU distributed unit of an access network, a UE context release command message from user unit equipment. centralized CU of the access network; and send, through DU, a complete context release message from
[0054] [0054] In a possible project, the indication information is carried in the UE context release command message, and the indication information is used to indicate that the CU needs to set the UE from a connected state to an inactive state.
[0055] [0055] In a possible project, the indication information is carried in the UE context release command message, and the indication information is used to indicate that the CU needs the UE context in the DU.
[0056] [0056] In a possible project, the UE context in the DU includes at least one of the following: identification information corresponding to a DU-adjusted carrier for the UE, logical carrier configuration information, logical channel identification information carrier information, RLC layer configuration information, MAC layer configuration information, and carrier PHY layer configuration information, UE C-RNTI identification information, and information about a cell accessed by the UE in the DU or information about a cell accessible by the UE in the DU.
[0057] [0057] According to another aspect, a communications device is provided. The communications device can implement a function performed by CU-CP in the method according to the fifth aspect, a function performed by CU-UP in the method according to the sixth aspect, a function performed by CU in the method according to the seventh aspect aspect or the ninth aspect, or a function performed by DU in the method according to the eighth aspect or the tenth aspect. The communications device includes one or more units or corresponding modules to carry out the steps in the method according to any of the fifth aspect to the tenth aspect. In other words, a step can be performed by a unit or module. In some cases, units or modules to perform two stages can be combined alternatively. For example, two shipping steps can be performed by the same unit or module. The function can be implemented using hardware, or it can be implemented by hardware running the corresponding software.
[0058] [0058] According to another aspect, a communications device is provided. The communications device can implement a function performed by CU-CP in the method according to the first aspect or the fifth aspect, a function performed by CU-UP in the method according to the second aspect or the sixth aspect, a function performed by CU in the method according to the seventh aspect or the ninth aspect, or a function performed by DU in the method according to the eighth aspect or tenth aspect. The communications device includes a processor and a communications interface. The communications interface is connected to the processor, to perform a CU-CP, CU-UP, CU or DU operation in the methods in the previous aspects. Specifically, the communications interface can perform a send and / or receive operation.
[0059] [0059] In a possible design, the communications device includes a memory. The memory stores an instruction, and the instruction is executed by the processor. When the instruction is being executed by the processor, the communications interface is controlled to perform the operation of the CU-CP, CU-UP, CU or DU in the methods in the previous aspects.
[0060] [0060] According to another aspect, a chip is provided. The chip includes a processor and an interface circuit. The interface circuit is configured to exchange information with an external device, and the interface circuit is connected to the processor, to perform the operation of CU-CP, CU-UP, CU or DU in the methods in the previous aspects. Specifically, the interface circuit can perform a send and / or receive operation.
[0061] [0061] In a possible project, the chip includes a memory. The memory stores an instruction, and the instruction is executed by the processor. When the instruction is being executed by the processor, the interface circuit is controlled to perform the operation of CU-CP, CU-UP, CU or DU in the methods in the previous aspects.
[0062] [0062] According to another aspect, one embodiment of this application provides a computer-readable storage medium. The computer-readable storage medium stores an instruction, and when the instruction is executed on a computer, the computer is enabled to perform the methods in the previous aspects.
[0063] [0063] In another aspect, an embodiment of this application provides a computer program product including an instruction. When the computer program product is run on a computer, the computer is enabled to perform the methods in the previous aspects. BRIEF DESCRIPTION OF THE DRAWINGS
[0064] [0064] FIG. 1 is a schematic diagram of a network architecture for a communications system;
[0065] [0065] The network architectures and service scenarios described in this application are intended to describe technical solutions in this application clearly, but are not intended to limit the technical solutions provided in this application. A person skilled in the art may know that as network architectures evolve and a new service scenario emerges, the technical solutions provided in this order are also applicable to a similar technical problem.
[0066] [0066] It should be understood that the character "/" in this request indicates a relationship "or" between the associated objects.
[0067] [0067] FIG. 1 is a schematic diagram of a network architecture for a communications system. The communications system includes an access network and a central network. The access network can be a next generation radio access network (Next Generation Radio Access Network, NG-RAN), and the central network can be a central 5G network (5G Core Network, 5GC). The access network can include a base station (for example, a gNB), and the gNBs are connected via an interface (for example, an Xn interface). A gNB is connected to the 5GC via an interface (for example, an Ng interface). The core network may include an Access and Mobility management Function, AMF. The central network can also include a user plane function (UPF).
[0068] [0068] FIG. 2 is a schematic architecture diagram of a CU-DU used in a communications system. As shown in FIG. 2, a base station can include a centralized unit (Centralized Unit, CU) and a distributed unit (Distributed Unit, DU). The base station's functions are divided.
[0069] [0069] FIG. 3 is a schematic architecture diagram of a CU. As shown in FIG. 3, CU includes a CU control plan (CU-CP) and a CU user plan (CU-UP). CU-CP and CU-UP can be deployed on different physical devices. Alternatively, CU-CP and CU-UP can be deployed on the same physical device. CU-CP and CU-UP are connected via an interface (for example, an E1 interface). The CU-CP indicates that a base station is connected to a central network through an interface (for example, an Ng interface). The CU-CP is connected to the DU via an interface (for example, an F1-C interface) and the CU-UP is connected to the DU via an interface (for example, an F1-U interface). There may be a CU-CP, and there may be one or more CU-UPs. A plurality of CU-UPs can share a CU-CP. CU-CP mainly has a control plan function. CU-UP mainly has a user plan function. In a possible implementation, for a 5G base station, an RRC layer can be deployed on CU-CP, but an SDAP layer is not deployed on CU-CP. CU-CP can also have a PDCP layer control plan function. For example, CU-CP can process a signaling radio bearer, SRB. The SDAP layer can be deployed in CU-UP, but the RRC layer is not deployed in CU-UP. CU-UP can also have a PDCP layer user plan function, for example, processing a radio data carrier (DRB).
[0070] [0070] FIG. 4 is a schematic diagram of a network architecture for another communications system. The communications system includes a network management system and a base station. The network management system can be an operation, administration and maintenance entity (Operation Administration and Maintenance, OAM). The base station is a CU-DU architecture. CU can include a CU-CP and a CU-UP. For details, refer to the descriptions in FIG. 2 and FIG. 3. The network management system is connected to the CU-CP, to perform the network configuration on the CU-CP. The network management system is connected to a DU to perform network configuration on the DU. The network management system is connected to CU-UP to perform the network configuration on CU-UP. In some cases, the network management system is not connected to CU-UP. In this case, the network management system configures CU-UP using CU-CP.
[0071] [0071] With the development of communications technologies, a concept of a network slice (NS) is still proposed. The main types of network slice include: an enhanced mobile broadband service (enhanced mobile broadband, eMBB), a massive machine type communication service (mMTC), and an ultra-reliable, low-cost communications service. latency (ultra-reliable and low latency communications, URLLC). EMBB is mainly aimed at terminals that have high rate and mobility requirements, such as cell phones and multimedia devices. MMTC is mainly aimed at IoT devices that have large scale, low mobility and low rate requirements. The URLLC refers mainly to a service or device type with strict latency and reliability requirements, such as vehicle Internet and safety information. For example, a mobile phone user can access an eMBB-type network slice to download at high speed or watch 4K high-definition video. A sensor device can access a network slice of an mMTC type, to transmit a small data packet and update a system configuration. A user can simultaneously access one or more or all of the network segments, to meet a service requirement and obtain a better user experience.
[0072] [0072] FIG. 5 shows a method of communication according to a first embodiment of the present invention. As shown in FIG. 5, the method includes the following steps.
[0073] [0073] 501. A CU-UP sends an interface adjustment request message to a CU-CP, and the CU-CP receives the CU-UP interface adjustment request message. An interface requested to be adjusted in the interface adjustment request message can be an E1 interface.
[0074] [0074] The interface adjustment request message comprises information about a network slice supported by CU-UP. The information about the network slice supported by CU-UP can be an identifier of the network slice supported by CU-UP. The network slice identifier can be single-network slice selection assistance information, S-NSSAI. The network slice identifier can alternatively be an S-NSSAI list (S-NSSAI list).
[0075] [0075] The network slice can be partially implanted in a network.
[0076] [0076] Optionally, the information about the network slice supported by CU-UP includes an identity of a tracking area (tracking area, TA for short) served by CU-UP and a network slice identifier corresponding to the tracking area . The TA identity can be represented using a tracking area code (TAC) or a tracking area identity (tracking area identity / identifier, TAI). TAI may include a TAC and a PLMN. Alternatively, the information about the network slice supported by CU-UP includes a cell identity served by the (list of cells served by) CU-UP and a network slice identifier corresponding to the cell. Alternatively, the information about the network slice supported by CU-UP includes an identity of a public land mobile network (PLMN) served by CU-UP and a network slice identifier corresponding to the public land mobile network. Alternatively, information about the network slice supported by CU-UP includes an identity from a registration area (registration area, RA) served by CU-UP and a network slice identifier corresponding to the public terrestrial mobile network. The RA identity can be represented by means of a registration area code (RAC) or a registration area identity (registration area identity / identifier, RAI). Alternatively, information about the network slice supported by CU-UP includes an identity of a cell served by CU-UP (list of cells served by CU-UP) and a network slice identifier corresponding to a TAI to which the cell belongs.
[0077] [0077] The interface adjustment request message may also include CU-UP capacity information. Capacity information can be information about an available CU-UP resource and / or load information from CU-UP and / or information about a processing capacity (CU-UP). The available resource includes at least one of the following: a computing resource, a software resource, a storage resource, or a port resource (such as a number of available ports). The load information can include at least one of the following: a current load and a load that CU-UP can currently support. Capacity information can be a scalar value. When a network side adjusts a carrier or session to a terminal, the CU-CP can select a suitable CU-UP with reference to the capacity information. For example, a higher value corresponding to the CU-UP capacity information indicates a stronger processing capacity than CU-UP. In another case (for example, a plurality of CU-UPs all support a network slice corresponding to a session or a carrier that needs to be adjusted), a CU-CP selects, as a service CU-UP, a CU-UP whose capacity information corresponds to a higher value.
[0078] [0078] Optionally, the CU-UP capacity information can be indicated in a network slice granularity. That is, the CU-UP capacity information for each network slice is fed back to the network slice. The capacity information for CU-UP can be specifically capacity information for a network slice supported by CU-UP. The capacity information of the network slice supported by CU-
[0079] [0079] Resources from different network slices can be isolated from each other in CU-UP, and can be reported more accurately at a network slice granularity. This avoids a situation in which an inappropriate CU-UP is selected because a network slice is overloaded, even if the overall capacity of the CU-UP is sufficient. For example, a CU-UP 1 supports a network slice 1 and a network slice 2, and network slice 1 and network slice 2 use isolated resources, where a general available resource from network slice 1 is responsible for 20% of a general available resource from CU-UP, and a general available resource from slice 2 of the network accounts for 80% of the general available resource from CU-UP. It is assumed that a load from network slice 1 is high (for example, a remaining resource is responsible for 5% of the overall available resource of CU-UP), and a load from network slice 2 is low (for example, a remaining resource is responsible for 75% of the total available resource of CU-UP). If the capacity information is not indicated in a slice granularity, CU-CP considers that CU-UP 1 is still in a low-load state. If a user requests the adjustment of a session of network slice 1, CU-CP still selects CU-UP 1 to serve the user and, consequently, the session is rejected, communication is interrupted, and the quality of communication is affected. However, this case can be avoided when the capacity information is indicated in a network slice granularity.
[0080] [0080] CU-UP capacity information can be shown in Table 8. Table 8 IE Description Identification information Used to identify a specific CU-UP CU-UP by CU-CP Capacity information (list)> Slice identifier For example, an S- NSSAI list (S-NSSAI list) or S-
[0081] [0081] CU-UP can alternatively feed capacity information for each network slice for each supported PLMN. For example, when different operators share an access network device, for a network slice supported by each PLMN, CU-UP feeds the corresponding capacity information. An advantage of doing this is that, if a PLMN resource is independent, a misjudgment of the CU-CP can be avoided. For specific examples, see Table 9 and Table 10. Table 9 IE Description Identifying information Used to identify a specific CU-UP CU-UP by CU-CP Capacity information> Broadcast PLMN >> PLMN >> Slice information For example, an S- NSSAI list (S-NSSAI list) or S-
[0082] [0082] CU-UP can alternatively feed capacity information for each network slice for each tracking area, that is, feed the corresponding capacity information for a network slice supported by each tracking area. For specific examples, see Table 11 and Table 12. Table 11 IE Description Identifying information Used to identify a specific CU-UP CU-UP by CU-CP
[0083] [0083] Certainly, if a plurality of network slices share a resource, the previous capacity information can be CU-UP capacity information for the network slices that share the resource.
[0084] [0084] The CU-UP capacity information is carried in the interface adjustment request message, so that the CU-CP knows the CU-UP capacity. This facilitates the selection of a suitable CU-UP by CU-CP for the UE or a service, a PDU session, or a DRB requested by the UE. For example, when the UE requests the adjustment of a new session, a RAN side (including a CU-CP, a CU-UP, and a DU) needs to adjust a related session or bearer for the UE and allocate a resource for the session or carrier that needs to be adjusted.
[0085] [0085] The interface adjustment request message also includes CU-UP service range information. Service band information includes at least one of the following: the identity of the cell served by CU-UP, the identity of the tracking area served by CU-UP, an identity of a DU distributed unit connected to CU-UP, or identity of the public terrestrial mobile network served by CU-UP. The identity that is of the cell served by CU-UP and that is included in the service band information can be a cell identity or a cell identity list, and indicates that CU-UP can adjust carriers for terminals in those cells. The identity that is of the distributed DU unit connected to the CU-UP and that is included in the service band information can be a DU identity or a DU identity list, and indicates that the CU-UP can adjust carriers for terminals on these DUs. CU-UP has data plan interfaces with these DUs. The lane information can alternatively be a PLMN identity, and indicates that CU-UP can adjust carriers for terminals on these PLMNs. The lane information can alternatively be a tracking area identity (TAC identity or TAI identity) and indicates that CU-UP can adjust carriers for terminals in these tracking areas. Certainly, the range information can alternatively be a combination of the previous identities, for example, a PLMN + cell identity (cell), and indicate that CU-UP can configure carriers for and serve terminals that are within the cell's coverage and accessing PLMN. Certainly, the track information may alternatively be in another form, such as a TAC identity + PLMN identity + cell identity. The information can help CU-CP to select the appropriate CU-UP to serve the UE and ensure normal communication. For example, the UE is being served by cell 1 (for example, the UE is setting an RRC connection for cell 1 or has already set up a connection for cell 1). If the UE needs to adjust a session or carrier, the CU-CP needs to select a CU-UP whose service range includes cell 1. If the CU-CP does not select the CU-UP whose service range includes cell 1, it occurs a session adjustment failure.
[0086] [0086] 502. CU-CP sends an interface adjustment response message to CU-UP, where the interface adjustment response message is a response to the interface adjustment request message.
[0087] [0087] Optionally, information about a network slice supported by CU-CP is carried in the interface adjustment response message. The information about the network slice supported by CU-CP can be an identifier of the network slice supported by CU-CP. The network slice identifier can be S-NSSAI or an S-NSSAI list. In one case, the information about the network slice supported by CU-CP includes an identity from a tracking area served by CU-CP and a network slice identifier corresponding to the tracking area. Alternatively, the information about the network slice supported by the CU-CP includes a cell identity served by the CU-CP and a network slice identifier corresponding to the cell. Alternatively, information about the network slice supported by CU-CP includes an identity of a public terrestrial mobile network served by CU-CP and a network slice identifier corresponding to the public terrestrial mobile network.
[0088] [0088] The CU-CP capacity information is still carried in the interface adjustment response message. Optionally, the capacity information of the CU-CP can be indicated in a network slice granularity.
[0089] [0089] Before step 501, the communication method can also include step 503: A network management system sends configuration information to CU-UP, and CU-UP receives configuration information from the management system network. The information about the network slice supported by CU-UP is carried in the configuration information. The network management system can be OAM.
[0090] [0090] When notifying a central network (for example, a
[0091] [0091] Optionally, in the embodiment shown in FIG. 5, the capacity information can be sent alternatively using dedicated signaling. As shown in FIG. 5, the communication method can also include step 505: CU-UP sends capacity information to CU-CP, and CU-CP receives capacity information from CU-UP. For CU-UP capacity information, see the previous description. The capacity information of CU-UP can be the capacity information of the network slice supported by CU-UP. Prior to step 504, the communication method may also include step 506: CU-CP sends a capacity request message to CU-UP, and CU-UP receives the capacity request message from CU-CP. In this way, CU-CP can obtain capacity information from CU-UP in real time based on a requirement.
[0092] [0092] The embodiment shown in FIG. 5 can alternatively be extended to a configuration update process. Correspondingly, the interface adjustment request message in step 501 needs to be changed to a configuration update request message. The configuration update request message can be a CU-UP configuration update request message. The interface adjustment response message in step 502 needs to be changed to a configuration update response message. The configuration update response message can be a CU-UP configuration update response message. For content carried in the configuration update request message, see the content carried in the previous interface adjustment request message. For content carried in the configuration update response message, see the content carried in the previous interface adjustment response message.
[0093] [0093] FIG. 6 shows a method of communication according to a second embodiment of the present invention. As shown in FIG. 6, the method includes the following steps:
[0094] [0094] FIG. 7 shows a method of communication according to a third embodiment of the present invention. As shown in FIG. 7, the method includes the following steps:
[0095] [0095] A load status of a network slice supported and served by CU-UP (regardless of cells) can still be carried in the load request response, and an example is shown in Table 15. Table 15 IE Description identification Used to identify a specific CU-UP CU-UP by CU-CP Load information (list)> Slice identifier For example, an S- NSSAI list (S-NSSAI list) or S-
[0096] [0096] CU-UP can alternatively feed back the load information of each network slice for each supported PLMN. For example, when different operators share an access network device, for a network slice supported by each PLMN, CU-UP feeds the corresponding load information. An advantage of doing this is that, if a PLMN resource is independent, a misjudgment of the CU-CP can be avoided. For specific examples, see Table 16 and Table 17. Table 16 IE Description Identifying information Used to identify a specific CU-UP CU-UP by CU-
[0097] [0097] CU-UP can alternatively feed the load information of each network slice for each tracking area, that is, feed the corresponding load information for a network slice supported by each tracking area. For specific examples, see the
[0098] [0098] Certainly, if a plurality of network slices share a resource, the previous capacity information can be information about the CU-UP load for the network slice that shares the resource.
[0099] [0099] The embodiment shown in FIG. 7 can exist independently or can be combined with the previous modalities. For example, the embodiment shown in FIG. 7 is performed after step 502 in the embodiment shown in FIG. 5 or step 602 in the embodiment shown in FIG. 6.
[00100] [00100] FIG. 8 shows a method of communication according to a fourth embodiment of the present invention. As shown in FIG. 8, the method includes the following steps.
[00101] [00101] 801. A DU sends an interface adjustment request message to a CU, and the CU receives the interface adjustment request message from the DU. An interface requested to be adjusted in the interface adjustment request message can be an F1 interface.
[00102] [00102] The identification information of an access network notification area (RAN Notification Area, RNA) to which a cell served by the DU belongs, can be carried in the interface adjustment request message. The RNA identification information can be an RNA code (RNA Code). The RNA code can be a group of codes similar to a TAC. Alternatively, the RNA identification information may alternatively be an RNA identity (RNA Identifier / Identity, RNA ID). For example, RNA ID can be represented in the form of RNAC + PLMN. That is, the RNA ID can represent a cell's RNAC and PLMN. Alternatively, RNA ID can be represented in the form of RNAC + TAI. That is, the RNA ID can represent both the RNAC and a TAI of the cell. Certainly, the RNA identification information can alternatively be expressed in another way.
[00103] [00103] RNA identification information can be used to uniquely identify an RNA to which a cell belongs within a specific range. The cell can notify, by broadcasting the RNA identification information, a terminal of the RNA identification information to which the cell belongs. A plurality of cells can broadcast the same RNA identification information or can broadcast different RNA identification information. If the plurality of cells broadcast the same RNA identification information, those cells will belong to the same RNA. If the plurality of cells diffuse different RNA identification information, those cells belong to different RNAs. The RNA identification information in this document may also be referred to as identification information for a radio access network paging area (RAN).
[00104] [00104] RNA can include one or more cells. If the RNA includes a plurality of cells, the plurality of cells can belong to one network device, or it can belong to different network devices. The different network devices can be network devices from the same radio access technology (RAT), or they can be network devices from different RATs. For example, network devices can be eNBs on a 4.5G network, or they can be gNBs on a 5G network. When moving within the RNA, a terminal in an inactive state may not notify a network. Instead, the terminal only reselects a cell based on the mobility of the terminal and periodically updates the RNA. When the terminal in the inactive state moves to a cell outside the RNA, the terminal needs to notify the network and update the RNA. Updating the
[00105] [00105] An inactive state, also known as radio resource control, RRC, is a newly defined 5G communication state. The communication state can be understood as an independent communication state, that is, an independent state different from a connected RRC state (Connected / Active) and an idle RRC state (Idle), or it can be understood as a communication communication substation. a connected state or an idle mode. The terminal in the idle state can have at least one of the following characteristics: A. The context information of the terminal in an access layer (Access Stratum, AS) is reserved on both a terminal side and a radio access network side (radio access network, RAN). B. When the terminal changes from the inactive state to the connected RRC state, a link between a network device and a control plan network element of a central network does not need to be reactivated. For example, a link between one side of the base station and one side of the central network does not need to be reactivated. C. Terminal mobility is implemented through new cell selection instead of transfer.
[00106] [00106] In a CU-DU architecture, if CU determines to define a connected state (Connected) of a user to an inactive state (Inactive), CU allocates an RNA for the user. If the CU does not know the RNA ID of the cell served by the DU, the CU can indicate an area of RNA allocated to the user just by configuring the RNA as a cell identity list, that is, using the cell identity list.
[00107] [00107] One way in which the RNA information is carried in the interface adjustment request message can be shown in Table 20. In Table 20, the RNA information is an RNA served by the DU, and is not distinguished by the granularity of cell. Table 20 IE Description Type of message type message CU-CP ID The CU-CP identifier can be used to uniquely identify a CU-CP within an access network or within another RPAC or RPAI range RPA information corresponding to the station (list) base
[00108] [00108] The way in which the RNA information is carried in the interface adjustment request message can be shown in Table 21, Table 22 or Table
[00109] [00109] Optionally, DU capacity information can be carried in the interface adjustment request message. For DU capacity information, see the previous description of CU-UP capacity information. The capacity information can be information about an available DU resource and / or DU load information and / or information about a DU processing capacity. Optionally, DU capacity information can be indicated in a network slice granularity. That is, the DU capacity information for each network slice is fed back to the network slice. DU capacity information can be specifically capacity information for a network slice supported by DU. The capacity information of the network slice supported by the DU is available resource information and / or information of processing capacity and / or load information from the DU for the network slice supported in the DU.
[00110] [00110] 802. The CU sends an interface adjustment response message to the DU, and the DU receives the interface adjustment response message from the CU.
[00111] [00111] Optionally, the CU capacity information can be carried in the interface adjustment response message. For information on CU's capacity, see the previous description.
[00112] [00112] CU can use a CU-CP and CU-UP architecture. That is, CU includes a CU CU-CP control plan entity and a CU CU-UP user plan entity. In step 801, the fact that the DU sends the interface adjustment request message to CU specifically includes: The DU sends the interface adjustment request message to CU-CP. Correspondingly, the interface requested to be adjusted in the interface adjustment request message can be an F1-C interface.
[00113] [00113] Optionally, the identification information of a CU-UP connected to the DU can still be carried in the message of request for interface adjustment. The identification information of the CU-UP connected to the DU is carried in the interface adjustment request message sent to the CU-CP, so that the CU-CP obtains information about the CU-UP connected to the DU. In this way, CU-CP selects a suitable CU-UP to serve UE. For example, the UE obtains access from a DU 1 or is being served by DU 1 (for example, the UE is setting a RRC connection to DU 1 or has set a connection to DU 1). If the UE needs to adjust a session or a carrier, the CU-CP needs to select a CU-UP that has an F1-U connection to DU 1.
[00114] [00114] The embodiment shown in FIG. 8 can alternatively be extended to a configuration update process. Correspondingly, the interface tuning request message in step 801 needs to be changed to a configuration update request message. The configuration update request message can be a DU configuration update request message. The interface adjustment response message in step 802 needs to be changed to a configuration update response message. The configuration update response message can be a DU configuration update response message.
[00115] [00115] FIG. 9 shows a communication method according to a fifth embodiment of the present invention. As shown in FIG. 9, the method includes the following steps:
[00116] [00116] Optionally, the indication information is carried in the UE context release command message and the indication information is used to indicate that the CU needs to adjust the UE from a connected state to an inactive state. The indication information can be cause information (cause), or it can be an information element (IE).
[00117] [00117] Optionally, the indication information is carried in the UE context release command message, and the indication information is used to indicate that the CU needs the context of the UE in the DU. Specifically, referral information can be used to indicate that before excluding the context of the UE, the DU sends the context of the UE in the DU to CU. Referral information can be an information element (IE).
[00118] [00118] The context of the UE in the DU includes at least one of the following: identification information corresponding to a carrier adjusted by the DU for the UE, configuration information of the logical channel of the carrier, identification information of the logical channel of the carrier, information of RLC layer configuration, MAC layer configuration information, and carrier PHY layer configuration information, identification information for a UE cell radio network temporary identifier, C-RNTI, or information about a cell accessed by the UE in the DU or information about a cell accessible by the UE in the DU. The context can be in the form of a container, or in another form.
[00119] [00119] When CU decides to change a connected state from the UE to an inactive state, the CU needs to instruct a DU of origin in which the UE encamps to release the context of the UE. However, for the terminal in the idle state, when the UE needs to resume (resume) to the connected state, a new service base station or a new service DU obtains context information from the terminal from a CU source or a base station from camped fountain. Examples are as follows: (1) An inter-DU (inter-DU) and intra-CU (intra-CU) movement scenario. That is, the inactive UE has changed from a camped DU 1 source to a new DU 2 (new service DU), but the inactive UE does not move outside a service area of a camped CU 1 source. When the inactive UE expects to resume to a connected state, CU 1 requests that DU 2 adjust a context for the UE, for example, adjusting a setting for a related carrier (DRB and / or SRB), allocating a resource, and serving to the user. In this case, CU needs to notify DU 2 of the previous context information of DU 1 (for example, bearer configuration information), so that DU 2 performs different configuration based on the configuration; (2) An inter-DU (inter-DU) and inter-CU (inter-CU) movement scenario. That is, the inactive UE has changed from the source DU 1 camped to the new DU 2, and changed from the source CU 1 camped to a new CU 2 (a new service CU). When the inactive UE expects to return to the connected state, CU 2 and DU 2 set a context for the UE, for example, by setting a related carrier (DRB and / or SRB), and serving the user. In this case, CU 2 requests, from CU 1, previous context information (for example, bearer configuration information), including DU 1 and CU 1 context information, and needs to notify DU 2 of the previous configuration information DU 1, so that DU 2 performs different configuration based on the configuration; (3) An inter-access network (inter-RAN) movement scenario. That is, the inactive UE has changed from the DU 1 and CU 1 source camped to a gNB 2, and gNB 2 is not in a CU-DU architecture. When the inactive UE expects to return to the connected state, gNB 2 sets up a context for the UE, for example, setting a related carrier (DRB and / or SRB), and serving the user. In this case, gNB 2 requests, from CU 1, previous context information (for example, carrier configuration information) including DU 1 and CU 1 context information, so that gNB 2 performs different configuration based on configuration.
[00120] [00120] When the inactive state of the UE needs to be changed to the connected state, a new service node needs to obtain context information from a camping DU source, but a camping station or DU source base station has deleted a DU related context. Consequently, communication cannot be carried out normally. In this application, CU can obtain a context from the UE, and can store the context. In this way, an inactive user can obtain and use the context when another DU or base station resumes to a connected state, thus ensuring normal communication.
[00121] [00121] The previous one mainly describes the solutions in the modalities of this request from a perspective of interaction between communication devices. It can be understood that, in order to implement the foregoing functions, the communication devices include hardware structures and / or corresponding software modules to perform the various functions. A person skilled in the art should be easily aware that the steps of units and algorithms in the examples described with reference to the modalities disclosed in this specification can be implemented in a form of hardware or a combination of computer hardware and software in this application. Whether a function is performed by hardware or hardware driven by computer software depends on the specific application and a restricted design condition of the technical solutions. One skilled in the art may use different methods to implement the functions described for each particular application, but it should not be considered that such an implementation goes beyond the scope of this application.
[00122] [00122] In the modalities of this request, CU, DU, CU-CP, CU-UP, or the like can be divided into function units based on the examples of previous methods. For example, function units can be obtained by dividing based on the corresponding functions, or two or more functions can be integrated into one function unit. The integrated unit can be implemented in the form of hardware, or it can be implemented in the form of a software function unit. It should be noted that the division of unity in the modalities of this application is an example, and is only a logical division of function. There may be another way of dividing during the actual implementation.
[00123] [00123] FIG. 10 is a schematic diagram of a communications device according to a sixth embodiment of the present invention. FIG. 10 is a possible schematic structural diagram of the CU-CP in the previous modalities. As shown in FIG. 10, the communications device 1000 is a CU-CP centralized unit control plan entity of an access network. The communications device 1000 includes a receiver 103 configured to receive an interface adjustment request message from a CU-UP centralized unit user plan entity of the access network. The interface adjustment request message comprises information about a network slice supported by CU-UP. The communications device 1000 further includes a first transmitter 101, configured to send an interface adjustment response message to the CU-UP.
[00124] [00124] Information about the network slice supported by CU-UP includes: an identity of a tracking area served by CU-UP and a network slice identifier corresponding to the tracking area, an identity of a cell served by CU -UP and a cell slice identifier corresponding to the cell, or an identity of a public terrestrial mobile network served by CU-UP and a network slice identifier corresponding to the public terrestrial mobile network.
[00125] [00125] The interface adjustment request message also comprises capacity information of the network slice supported by CU-UP.
[00126] [00126] The communications device further includes a second transmitter 105. The second transmitter 105 is configured to send, to a central network device, information about a network slice supported by the access network. The network slice supported by the access network includes a network slice supported by both CU-CP and CU-UP. In this application, the first transmitter 101 and the second transmitter 105 can be the same transmitter, or they can be different transmitters.
[00127] [00127] The first transmitter 101 is further configured to send a load request message to CU-UP. The load request message is used to request the obtaining of load information for the network slice supported by CU-UP. Optionally, a network slice identifier supported by CU-UP is carried in the load request message.
[00128] [00128] The interface adjustment request message also includes CU-UP service range information. Service band information includes at least one of the following: the identity of the cell served by CU-UP, the identity of the tracking area served by CU-UP, an identity of a DU distributed unit connected to CU-UP, or identity of the public terrestrial mobile network served by CU-UP.
[00129] [00129] FIG. 11 is a schematic diagram of a communications device according to a seventh embodiment of the present invention. FIG. 11 is a possible schematic structural diagram of the CU-UP in the previous modalities. As shown in FIG. 11, the communications device 1100 is a CU-UP centralized unit user plan entity of an access network. Communications device 1100 includes a transmitter 113, configured to send an interface adjustment request message to a centralized CU-CP unit control plan entity of the access network. The interface adjustment request message comprises information about a network slice supported by CU-UP. The communications device 1100 further includes a first receiver 111, configured to receive a CU-CP interface response response message.
[00130] [00130] Information about the network slice supported by CU-UP includes: an identity of a tracking area served by CU-UP and a network slice identifier corresponding to the tracking area, an identity of a cell served by CU -UP and a cell slice identifier corresponding to the cell, or an identity of a public terrestrial mobile network served by CU-UP and a network slice identifier corresponding to the public terrestrial mobile network.
[00131] [00131] The interface adjustment request message also comprises capacity information of the network slice supported by CU-UP.
[00132] [00132] Communications device 1100 further includes a second receiver 115. The second receiver 115 is configured to receive a configuration message from a network management system, and the configuration message comprises information about the network slice supported by the CU-UP. In this application, the first receiver 111 and the second receiver 115 can be the same transmitter, or they can be different transmitters.
[00133] [00133] The first receiver 111 is further configured to receive a load request message from the CU-CP. The load request message is used to request the obtaining of load information for the network slice supported by CU-UP. In addition, optionally, a network slice identifier supported by CU-UP is carried in the load request message.
[00134] [00134] The interface adjustment request message also includes CU-UP service range information. Service band information includes at least one of the following: the identity of the cell served by CU-UP, the identity of the tracking area served by CU-UP, an identity of a DU distributed unit connected to CU-UP, or identity of the public terrestrial mobile network served by CU-UP.
[00135] [00135] FIG. 12 is a schematic diagram of a communications device according to an eighth embodiment of the present invention. As shown in FIG. 12, the communications device 1200 can perform a CU-CP, CU-UP, CU or DU operation in the method in any mode shown in FIG. 5 to FIG. 9. The communications device 1200 includes a processor and a communications interface 1203. The communications interface 1203 is connected to the processor, to perform the operation of the CU-CP, CU-UP, CU or DU in the aspects methods previous ones.
[00136] [00136] Optionally, the communication device 1200 also includes a memory 1205. Memory 1205 stores an instruction, and the instruction is executed by the processor. When the instruction is being executed by the processor, the communication interface 1203 is controlled to perform the operation of the CU-CP, CU-UP, CU or DU in the methods of the previous aspects.
[00137] [00137] FIG. 13 is a schematic diagram of a chip according to a ninth embodiment of the present invention. As shown in FIG. 13, chip 1300 includes a processor 1301 and an interface circuit 1303. Interface circuit 1303 is configured to exchange information with an external device, and interface circuit 1303 is connected to processor 1301, to perform a CU- operation. CP, CU-UP, CU or DU in the method in any modality shown in FIG. 5 to FIG. 9. Specifically, interface circuit 1303 can perform a send and / or receive operation. The 1300 chip can be a chip used in a communications device.
[00138] [00138] Optionally, chip 1300 also includes memory 1305. Memory 1305 stores an instruction, and the instruction is executed by processor 1301. When the instruction is being executed by processor 1301, interface circuit 1303 is controlled to perform the operation of CU-CP, CU-UP, CU or DU in the methods of the previous aspects.
[00139] [00139] In this order, information about a network slice can be represented using at least one of the following parameters:
[00140] [00140] In the modalities of this request, all network slices can represent the network slice information using at least one of the previous parameters. For example, network slice information can be represented using a network slice type, or it can be represented using a network slice type and service type, or it can be represented using a service type and tenant information. . This is not limited to the modalities of this application. How to represent the network slice information is not described in detail below. It is to be understood that if a terminal device, an access network device, or a central network device supports a plurality of network slices, the indication information of a network slice supported by the terminal device, the network device access, or the central network device can be represented as a list of at least one of the previous identifiers.
[00141] [00141] The technical solutions of this application can be applied to a 5th generation mobile communication system (the 5th Generation mobile communication technology, 5G) or a mobile communication system further developed, and can be applied to various forms of systems, including some functions on a base station, where the functions are separated into various forms.
[00142] [00142] In the modalities of this request, the sequence numbers of the processes do not mean execution sequences. The sequence of execution of the processes must be determined based on functions and the internal logic of the processes, and should not constitute any limitation to the processes for implementing the modalities of this request.
[00143] [00143] Furthermore, the term "and / or" in this specification describes only one association to describe associated objects and represents that there can be three relationships. For example, A and / or B can represent the following three cases: Only A exists, A and B exist, and only B exists. In addition, the "/" character in this specification generally represents a "or" relationship between associated objects.
[00144] [00144] All or some of the previous modalities can be implemented using software, hardware, firmware, or any combination thereof. When implemented using the software, the modalities can be implemented completely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instruction is loaded and executed on a computer, the procedures or functions according to the modalities of this order are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or another programmable device. The computer instruction can be stored on a computer-readable storage medium or it can be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired manner (for example, a coaxial cable, an optical fiber or a digital subscriber line (DSL)) or wireless (for example, infrared, radio and microwave). The computer-readable storage medium can be any usable medium accessible by a computer, or a data storage device, such as a server or a data center, integrating one or more usable media. The usable medium can be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), a semiconductor medium (for example, a Solid State solid state drive Disk (SSD)), or similar.
[00145] [00145] The objectives, technical solutions, and benefits of this application are further described in detail in the previous specific modalities. It should be understood that the preceding descriptions are merely specific to this application, but are not intended to limit the scope of protection of this application. Any modification, equivalent replacement, improvement or similar made based on the technical solutions of this order must fall within the scope of protection of this order.

权利要求:
Claims (29)
[1]
1. Communication method, characterized by the fact that it comprises: receiving, by a centralized unit control plan entity CU-CP from an access network, an interface adjustment request message from a user plan entity of CU-UP centralized unit of the access network, where the interface adjustment request message comprises information about a network slice supported by CU-UP; and send, via CU-CP, an interface adjustment response message to CU-UP after receiving the interface adjustment request message.
[2]
2. Communication method, according to claim 1, characterized by the fact that the information about the network slice supported by CU-UP comprises an identity of a public terrestrial mobile network served by CU-UP and a slice identifier corresponding to the public terrestrial mobile network.
[3]
3. Communication method, according to claim 1 or 2, characterized by the fact that: the interface adjustment request message also comprises CU-UP service band information, and the service band information comprises a cell identity served by CU-UP.
[4]
4. Communication method according to any one of claims 1 to 3, characterized in that an interface requested to be adjusted in the interface adjustment request message is an E1 interface.
[5]
5. Communication method, according to the claim
2, characterized by the fact that the network slice identifier is assistance information for selecting a unique network slice S-NSSAI or an S-NSSAI list.
[6]
6. Communication method according to any one of claims 1 to 5, characterized by the fact that the interface adjustment request message also comprises CU-UP capacity information.
[7]
7. Communication method, according to claim 6, characterized by the fact that the capacity information comprises at least one of the following: information about an available resource from CU-UP, load information from CU-UP, or information about a processing capacity of CU-ACIMA; and the available resource comprises at least one of the following: a computing resource, a software resource, a storage resource, or a port resource.
[8]
8. Communication method, according to claim 6 or 7, characterized by the fact that the CU-UP capacity information is indicated in a network slice granularity.
[9]
9. Communication method, according to any one of claims 1 to 8, characterized by the fact that the CU-CP sends, to a central network, information about a network slice supported by the access network; and the network slice supported by the access network comprises a network slice supported by both CU-CP and CU-UP.
[10]
10. Communication method according to any one of claims 1 to 8, characterized by the fact that the CU-CP receives an F1 interface adjustment request message from a DU distributed unit of the access network, and the communication message F1 interface adjustment request comprises identification information of an RNA access network notification area to which a cell served by the DU belongs.
[11]
11. Communication method according to claim 10, characterized by the fact that the RNA identification information comprises an RNA code.
[12]
12. Communication method, according to claim 10, characterized by the fact that the RNA identification information comprises an RNA code and a PLMN identity.
[13]
13. Communication method according to any one of claims 10 to 12, characterized by the fact that the information on the RNA is distinguished by the cell granularity.
[14]
14. Communication method, characterized by the fact that it comprises: sending, through a CU-UP centralized unit user plan entity of an access network, an interface adjustment request message to a control plan entity CU-CP centralized unit of the access network, in which the interface adjustment request message comprises information about a network slice supported by CU-UP; and receive a CU-CP interface adjustment response message via CU-UP.
[15]
15. Communications device, characterized by the fact that the communications device is a CU-CP centralized unit control plan entity of an access network, and comprises: a receiver, configured to receive an adjustment request message interface of a CU-UP centralized unit user plan entity of the access network, where the interface adjustment request message comprises information about a network slice supported by CU-UP; and a first transmitter, configured to send an interface adjustment response message to CU-UP.
[16]
16. Communications device according to claim 15, characterized in that the communications device further comprises a second transmitter, the second transmitter is configured to send information about a supported network slice to a central network device by the access network, and the network slice supported by the access network comprises a network slice supported by both CU-CP and CU-UP.
[17]
17. Communications device, characterized by the fact that the communications device is a user plan entity of a CU-UP centralized unit of an access network, and comprises: a transmitter, configured to send an adjustment message interface to a CU-CP centralized unit control plan entity of the access network, where the interface adjustment request message comprises information about a network slice supported by CU-UP; and a first receiver, configured to receive a CU-CP interface adjustment response message.
[18]
18. Communication method, characterized by the fact that it comprises: receiving, by a centralized unit control plan entity CU-CP from an access network, a message requesting a configuration update from a user plan entity of CU-UP centralized unit of the access network, in which the configuration update request message comprises information about a network slice supported by CU-UP; and send, via CU-CP, a configuration update response message to CU-UP after receiving the configuration update request message.
[19]
19. Communication method, characterized by the fact that it comprises: sending, through a CU-UP centralized user plan entity of an access network, a configuration update request message to a control plan entity CU-CP centralized access network unit, in which the configuration update request message comprises information about a network slice supported by CU-UP; and receive a CU-CP configuration update response message via CU-UP.
[20]
20. Communications device, characterized by the fact that the communications device is a centralized CU-CP unit control plan entity of an access network, and comprises: a receiver, configured to receive an update request message. configuration of a CU-UP centralized unit user plan entity of the access network, where the configuration update request message comprises information about a network slice supported by CU-UP; and a first transmitter, configured to send a configuration update response message to CU-UP.
[21]
21. Communications device, characterized by the fact that the communications device is a user plan entity of a CU-UP centralized unit of an access network, and comprises: a transmitter, configured to send an update request message. configuration for a CU-CP centralized unit control plan entity of the access network, where the configuration update request message comprises information about a network slice supported by CU-UP; and a first receiver, configured to receive a CU-CP configuration update response message.
[22]
22. Communication method, characterized by the fact that it comprises: receiving, by a centralized CU unit of an access network, an interface adjustment request message from a distributed DU unit of the access network, in which the request message interface setting comprises information identifying an access network notification area to which a cell served by the DU belongs; and send, through CU, an interface adjustment response message to the DU.
[23]
23. Communication method, characterized by the fact that it comprises: sending, through a DU distributed unit of an access network, an interface adjustment request message to a centralized CU unit of the access network, in which the request message interface setting comprises information identifying an access network notification area to which a cell served by the DU belongs; and receive, through the DU, a response message from CU's interface adjustment.
[24]
24. Communications device, characterized by the fact that the communications device is a centralized CU unit of an access network, and comprises: a receiver, configured to receive an interface adjustment request message from a distributed DU unit of the network access, where the interface adjustment request message comprises information identifying an access network notification area to which a cell served by the DU belongs; and a transmitter, configured to send an interface adjustment response message to the DU.
[25]
25. Communications device, characterized by the fact that the communications device is a centralized DU unit of an access network, and comprises: a transmitter, configured to send an interface adjustment request message to a centralized CU unit of the network access, where the interface adjustment request message comprises information identifying an access network notification area to which a cell served by the DU belongs; and a receiver, configured to receive a CU interface tuning response message.
[26]
26. Communications device, characterized by the fact that it is configured to carry out the method as defined in any one of claims 1 to 14, 18, 19, 22 or 23.
[27]
27. Computer-readable storage medium, characterized by the fact that the computer-readable storage medium stores an instruction, and when the instruction is executed on a computer, the computer is enabled to perform the method as defined in any of the claims 1 to 14, 18, 19, 22 or 23.
[28]
28. Communications device, characterized by the fact that it comprises a processor and a memory, in which the memory stores an instruction, the instruction is executed by the processor, and when the instruction is being executed by the processor, the processor performs the method as defined in any of claims 1 to 14, 18, 19, 22 or 23.
[29]
29. Chip, characterized by the fact that the chip comprises a processor and an interface circuit, and the interface circuit is connected to the processor, to carry out the method as defined in any of claims 1 to 14, 18, 19, 22 or 23.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112020016564A2|2020-12-22|COMMUNICATION METHOD AND COMMUNICATIONS DEVICE IN DISTRIBUTED UNIT ARCHITECTURE - CENTRALIZED UNIT

---

KR20210123434A|2021-10-13|Communication method, source base station, target base station, core network device, and terminal device

---

US10757624B2|2020-08-25|Communication method, access network device, and core network device

---

KR20190089959A|2019-07-31|Target cell access method and apparatus

---

BR112019018044A2|2020-04-07|communication method and communications device

---

US9973987B2|2018-05-15|Selection of anchor controllers for access points within a network environment

---

US10582381B2|2020-03-03|Implementing radio access network slicing in a mobile network

---

CN110012437B|2021-02-23|Method, device and system for sending multicast message

---

BR112019011017A2|2019-10-08|access control method performed by a user equipment, user equipment, method performed by a network node, and, network node.

---

CN109936861B|2021-08-03|Communication method, access network equipment, terminal equipment and core network equipment

---

US20210289405A1|2021-09-16|First base station, second base station, terminal apparatus, method, program, and recording medium

---

KR102365459B1|2022-02-23|Communication method and communication device in centralized unit-decentralized unit architecture

---

WO2020156182A1|2020-08-06|Method and apparatus for updating serving cell information

---

JP7031944B2|2022-03-08|Communication method, source base station, target base station, core network device, and terminal device

---

WO2020200122A1|2020-10-08|Communication method and apparatus

---

WO2022001483A1|2022-01-06|Information sending method, nr cell access method, access network device, mobile terminal, and storage medium

---

WO2020216099A1|2020-10-29|Communication method and related device

---

WO2020063521A1|2020-04-02|Capability reporting method and apparatus

---

WO2021134175A1|2021-07-08|Roaming method and apparatus, and system

---

CN114208296A|2022-03-18|Communication method and related equipment

同族专利:

---

公开号 | 公开日

---

JP6988004B2|2022-01-05|

---

CN109151871A|2019-01-04|

---

CA3091172A1|2019-08-22|

---

KR20200113268A|2020-10-06|

---

JP2021513803A|2021-05-27|

---

US20200374947A1|2020-11-26|

---

EP3751886A1|2020-12-16|

---

CN110167051A|2019-08-23|

---

WO2019157885A1|2019-08-22|

---

CN109151871B|2019-08-13|

---

EP3751886A4|2021-03-17|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

CN107371155B|2016-05-13|2021-08-31|华为技术有限公司|Communication security processing method, device and system|

---

CN106162730B|2016-07-12|2019-11-15|上海华为技术有限公司|A kind of method of communication, equipment and system|CN113923647A|2019-01-16|2022-01-11|华为技术有限公司|Cell registration method and terminal equipment|

---

CN111491327B|2019-01-25|2021-10-26|华为技术有限公司|Communication method and system|

---

CN111491370B|2019-01-29|2022-02-18|华为技术有限公司|Communication method, network element, system and storage medium|

---

CN111526030B|2019-02-03|2021-12-14|华为技术有限公司|Information processing method and device|

---

CN112020106B|2019-05-28|2021-11-26|华为技术有限公司|Communication method and related equipment|

---

CN110366276A|2019-07-03|2019-10-22|中国联合网络通信集团有限公司|Serviceization framework base station|

---

US20210112565A1|2019-10-15|2021-04-15|Altiostar Networks, Inc.|End to end slicing in wireless communications systems|

---

WO2021127896A1|2019-12-23|2021-07-01|华为技术有限公司|Communication method and communication apparatus|

---

US11026149B1|2020-01-31|2021-06-01|Dish Wireless Llc|Systems and methods for reducing slice access failures|

---

WO2021189496A1|2020-03-27|2021-09-30|华为技术有限公司|Method and device for use in data transmission of network slice|

---

CN113939044A|2020-06-29|2022-01-14|华为技术有限公司|Communication method and device|

法律状态:
2021-12-14| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

CN201810152264.7|2018-02-14|

---

CN201810152264.7A|CN110167051A|2018-02-14|2018-02-14|Communication means, communication equipment under centralized unit-distributed unit framework|

---

PCT/CN2019/070363|WO2019157885A1|2018-02-14|2019-01-04|Communication method and device under centralized unit-distributed unit architecture|

---