WO2018219229A1 - 通信方法和网络设备 - Google Patents

通信方法和网络设备 Download PDF

Info

Publication number
WO2018219229A1
WO2018219229A1 PCT/CN2018/088480 CN2018088480W WO2018219229A1 WO 2018219229 A1 WO2018219229 A1 WO 2018219229A1 CN 2018088480 W CN2018088480 W CN 2018088480W WO 2018219229 A1 WO2018219229 A1 WO 2018219229A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
slice
information
network slice
resource
Prior art date
Application number
PCT/CN2018/088480
Other languages
English (en)
French (fr)
Inventor
赵祺阳
李旭
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2018219229A1 publication Critical patent/WO2018219229A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14—Spectrum sharing arrangements between different networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/02—Resource partitioning among network components, e.g. reuse partitioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information

Definitions

  • the present application relates to the field of communications and, more particularly, to communication methods and network devices.
  • Network slicing technology has been proposed as a key technology for future communication system research, enabling future networks to support a wide range of services to serve the various industries of society.
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable and low-latency
  • mMTC massive machine type of communication
  • the existing communication system places all network services in a common transmission pipeline, and will not be able to meet the quality of service (QoS) requirements of different services in different networks in the future. Therefore, in the research of the next generation 5G communication system, network slicing technology came into being.
  • the radio resource may include a spectrum resource, a site resource, and the like
  • the radio protocol may include a physical system (Numerology), a protocol stack parameter configuration, and the like of the radio link.
  • a base station generally allows all users accessing the network to share radio resources and uniformly control and configure protocol parameters.
  • the network splicing scheme proposes to isolate the radio resources and protocols of the RAN according to the slice, including but not limited to, using exclusive spectrum resources for each slice and independent wireless protocol configuration, thereby ensuring the service quality obtained by using the sliced service.
  • the spectrum is a very scarce and expensive resource for operators, and the traffic, the number of users, and the quality of service requirements on the slice in the mobile network can be dynamic, random, and fast changing in time and space. Therefore, how to maximize the scheduling and utilization of spectrum resources while ensuring the isolation of the slice service pipeline becomes a challenge for network slice radio resource management.
  • the present application provides a communication method, which can flexibly allocate network resources required for accessing a radio access network to a network slice to improve communication efficiency.
  • a communication method for managing a network device of a radio access network to determine a network slice
  • the network device configures, for the network slice, a network resource required for accessing the radio access network, where the network resource includes at least one of a network function module and a spectrum resource, where the network function module includes a shared network.
  • the network resource includes at least one of a network function module and a spectrum resource, where the network function module includes a shared network.
  • a functional module and/or a proprietary network function module the spectrum resource comprising a shared spectrum resource and/or a proprietary spectrum resource.
  • the network device for managing the radio access network is independent of the service network of the network slice, and configures the network required for accessing the radio access network for the network slice according to the lifecycle management information of the network slice. Resources, so that the network slice can be flexibly allocated to the network resources required for accessing the radio access network, thereby improving communication efficiency.
  • the network device may configure a shared network resource for the network slice. Therefore, multiple network slices can be used to share network resources, thereby avoiding waste or congestion of network resources, thereby flexibly allocating network resources required for accessing the radio access network to the network slice, and improving communication efficiency.
  • the network device configures, for the network slice, network resources required for accessing the radio access network, including: a location occupied by the spectrum resource of the network device on a spectrum resource, or The proportion of occupancy between the shared spectrum resource of the network slice and the proprietary spectrum resource.
  • the network device may flexibly configure a plurality of network slices to share spectrum resources, or flexibly configure an occupation ratio between the shared spectrum resources of the network slice and the dedicated spectrum resources, thereby operating the network slice,
  • the network resources of the radio access network are dynamically adjusted, the utilization of network resources is improved, and the flexibility of configuring the radio access network is improved.
  • the configuring, by the network device, the network resource required for accessing the radio access network includes: configuring, by the network device, a connection relationship between a shared network function module of the network slice and a proprietary network function module.
  • the network device can flexibly configure the occupation ratio between the shared network function module and the proprietary network function module, thereby dynamically adjusting the wireless access network when the network slice is running and the user traffic changes.
  • Network resources improve the utilization of network resources and increase the flexibility of configuring wireless access networks.
  • the network device configures, for the network slice, network resources required for accessing the radio access network, where the network device is configured according to at least one of the following information:
  • the network slice configures network resources required for accessing the radio access network: status information of the network slice, user information of the network slice, and service information of the network slice.
  • the network device can flexibly configure the shared network resource or the dedicated network resource of the radio access network according to the state information of the network slice, the user information of the network slice, and the service information of the network slice, thereby being flexible.
  • the network slice is allocated network resources required for accessing the radio access network to improve communication efficiency.
  • the network device configures, for the network slice, network resources required for accessing the radio access network, where the network device configures the user according to the user information of the network slice.
  • the first user of the network slice uses the shared network resource or dedicated network resource of the network slice.
  • the network device configures the first user to use the shared network resource or the dedicated network resource according to the user information of the network slice, thereby configuring the network resource of the wireless access network for the network slice according to the user granularity, and improving the network resource. usage efficiency.
  • the network device configures, for the network slice, network resources required for accessing the radio access network, where the network device configures according to service information of the network slice.
  • the first type of service of the network slice uses the shared network resource or the dedicated network resource of the network slice.
  • the network device configures the first type of service to use the shared network resource or the dedicated network resource according to the service information of the network slice, thereby configuring the network resource of the wireless access network for the network slice according to the service type granularity, and improving the network. Resource utilization efficiency.
  • the lifecycle management information of the network slice includes at least one of the following: creation information of the network slice, deletion information of the network slice, expansion information of the network slice, and the The volumetric information of the network slice, the subscription information of the network slice, and the quality of service QoS information of the network slice.
  • the network device may receive lifecycle management information of the network slice from a network slice orchestrator.
  • a network device for performing the method of any of the above first aspect or any of the possible implementations of the first aspect.
  • the network device comprises means for performing the method of any of the above-described first aspect or any of the possible implementations of the first aspect.
  • a network device comprising: a communication interface, a memory, a processor, and a bus system.
  • the communication interface, the memory and the processor are connected by the bus system, the memory is for storing instructions, the processor is configured to execute instructions stored by the memory to control the communication interface to receive signals and/or transmit signals, and When the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of the first aspect or any of the possible implementations of the first aspect.
  • a computer readable medium for storing a computer program comprising instructions for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • FIG. 1 is a schematic diagram of an application environment of an embodiment of the present application.
  • FIG. 2 is a schematic flowchart diagram of a communication method according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of functions of a RAN slice controller according to an embodiment of the present application.
  • FIG. 4 is a schematic flow chart of a communication method according to another embodiment of the present application.
  • FIG. 5 is a schematic flowchart diagram of a communication method according to another embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a network device according to still another embodiment of the present application.
  • Network slice A logical network that has different network capabilities and network characteristics customized according to different service requirements on a physical or virtual network infrastructure.
  • the network slice can be a complete end-to-end network including a terminal, an access network, a transmission network, a core network, and an application server, and can provide telecommunication services and have certain network capabilities; the network slice can also be the above terminal and access network. Any combination of the transport network, the core network, and the application server, for example, the network slice only includes the access network and the core network.
  • a network slice may have one or more of the following characteristics: the access network may or may not slice.
  • the access network may be shared by multiple network slices. The characteristics of different network slices and the network function modules that make up them may be different.
  • the network slice may also be referred to as a network slice instance or slice.
  • Network function module It is a processing function in the network, which defines functional behaviors and interfaces.
  • the network function modules can be implemented by dedicated hardware or by running software on dedicated hardware. Implemented as a virtual function on a common hardware platform. Therefore, from the perspective of implementation, the network function modules can be divided into physical network function modules and virtual network function modules. From the perspective of use, the network function module can be divided into a dedicated network function module and a shared network function module. Specifically, for multiple (sub)network slice instances, different network function modules can be independently used.
  • the function modules are called proprietary network function modules, and can also share the same network function module. This network function module is called a shared network function module.
  • NS-LCM Network Slice Lifecycle Management
  • NS-LCM can be used to be responsible for lifecycle management of network slices, for example, including creation, combination, update, deletion (termination) of network slices.
  • at least one of the following functions may be included: (1) the requirement of receiving a service, for example, the number of devices that need to be supported/served, the delay and throughput of the data flow, the coverage, and the economic parameters (eg, charging method) (2) Converting the demand of the service into a demand for the network. For example, if the user's demand is the number of devices and the coverage, the corresponding network demand is the throughput/delay of the network connection, the number of base stations required, etc.
  • NSD Network Slice Descriptor
  • NS-ID Network Slice Identifier
  • KPI key performance indicator
  • the network function module may be a function of large granularity, such as mobility management, connection management, access control, or the like, or may be an atomic function, such as a Packet Data Convergence Protocol (PDCP).
  • PDCP Packet Data Convergence Protocol
  • the network slice logical topology can be used to indicate the connection mode, interface, KPI requirements (which can include bandwidth, delay, throughput) and the like between the network function modules of the network slice.
  • NSO Network Slice Orchestrator It manages network slices mainly from the network layer.
  • the NSO can orchestrate network resources based on the network slicing requirements generated by the NS-LCM and the actual network resources.
  • the network resources may include link resources, storage resources, computing resources, or other network resources as described above.
  • the user involved in the embodiment of the present application may include a user who uses the terminal device.
  • the user involved in the embodiment of the present application may also include a terminal device connected to the network slice.
  • the terminal device may include various handheld devices having wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem, and various forms of user equipment (User Equipment, UE), mobile stations. (Mobile Station, MS), terminal, terminal device, and the like.
  • the embodiment of the present application provides a method for supporting dynamic allocation, configuration, and sharing of network resources in a wireless access network. It can realize the isolation of the resources between the slices and the reliability of the service quality while realizing the sharing of the spectrum resources, the access network function modules, the radio access technology and the parameter configuration of multiple network slices, thereby improving the utilization of the radio resources and The quality of service of the slicing business, as well as the flexibility and consistency of functional configuration.
  • the application environment introduces a radio access network slice controller (hereinafter referred to as a RAN slice controller) in the network slice management system.
  • a radio access network slice controller hereinafter referred to as a RAN slice controller
  • the RAN slice controller can include, but is not limited to, the following features:
  • the northbound interface of the RAN slice controller is connected to the network slice orchestrator for receiving the instruction of the slice lifecycle management, including but not limited to the time, area, service, user, and service level of the slice operation. Wait.
  • the southbound interface of the RAN slice controller is connected to the functional modules on each protocol layer of the RAN, and is used for flexibly configuring functions, parameters, and resources used by the slice, and request information for the terminal to initiate service access network slice.
  • the RAN slice controller is connected to the slice controller of the other part of the interface network, and the network controller interface is used for deploying, deleting, and maintaining the RAN slice controller, and configuring the RAN service node responsible for management.
  • the interface between the RAN slice controller and the sub-controllers such as the core network, the transmission network, and the backbone network is used to coordinate the consistency of the service quality of the slice service between the various parts of the network, and maintain the end-to-end service pipeline.
  • a base station may be classified into a centralized unit (CU) and a distributed unit (DU).
  • the CU and DU can be softwareized or virtualized, and the RAN function requiring flexible combination will run in a CU composed of a general-purpose server, such as Radio Link Control (RLC), Packet Data Convergence Protocol (Packet Data). Convergence Protocol (PDCP), Radio Resource Control (RRC) and other high-level functions; and RAN functions that are strongly related to hardware and have high real-time requirements will run in DUs composed of proprietary hardware platforms, such as physics. Physical layer (PHY), media access control layer (MAC) and other low-level functions.
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • RRC Radio Resource Control
  • RAN functions that are strongly related to hardware and have high real-time requirements will run in DUs composed of proprietary hardware platforms, such as physics.
  • Physical layer (PHY) media access control layer (MAC) and other low-level functions.
  • the base station in this embodiment of the present application describes the communication method in the embodiment of the present application by using the CU-DU architecture.
  • the method of the embodiment of the present application is not limited to any one of the CU-DU architectures.
  • the method of the embodiment of the present application may also not be applied to the CU-DU architecture.
  • the base station in this embodiment of the present application may also include various forms of macro base stations, micro base stations, relay stations, access points, and the like.
  • the names of devices with base station functionality may vary.
  • an evolved NodeB eNB or eNodeB
  • 3G 3rd Generation
  • the RAN slice controller can dynamically deploy, delete, and configure the RAN function module on the CU through the southbound interface to flexibly combine to form a service pipeline of the RAN slice; and perform spectrum resources on the RAN physical layer module on the DU. Allocate and dynamically adjust physical parameters such as waveform, codec, modem, etc. to adapt to the demand for service quality of the slice service.
  • the RAN slice controller may be deployed in the edge cloud data center to control one or more CUs and DUs, that is, physically one or more cells (for example, a remote end) Wireless Radio Unit (RRU)).
  • RRU Wireless Radio Unit
  • the application environment may further include a Transport Network (TN) slice controller and a Centralized Unit (CN) slice controller.
  • TN Transport Network
  • CN Centralized Unit
  • the TN slice controller is used to manage the transmission network part
  • the CN slice controller is used to manage the core network part.
  • FIG. 2 is a schematic flowchart of a communication method 200 according to an embodiment of the present application.
  • Method 200 describes a method of configuring a network slice to access network resources of a wireless access network.
  • Method 200 can be applied and is not limited to the application environment of FIG.
  • the network device in method 200 can be a RAN slice controller.
  • Method 200 includes:
  • a network device for managing a radio access network determines a network slice.
  • the network device may be a RAN slice controller.
  • the network slice may be a network slice of a network resource of a radio access network to be configured.
  • the network device may autonomously determine a network slice that needs to configure or adjust network resources of the radio access network according to the running state of the network slice.
  • the network device can determine the network slice based on the received information.
  • the network device may receive first indication information, where the first indication information includes lifecycle management information of the network slice or access request information of a user and a service of the network slice; Determining the first indication information to determine the network slice.
  • the network device may receive lifecycle management information of the network slice from a network slice orchestrator.
  • the network device may receive access request information of the prime number user and the service from the terminal device accessing the network slice.
  • the lifecycle management information of the network slice includes at least one of: operation information of the network slice, subscription information of the network slice, and quality of service QoS information of the network slice.
  • the operation information of the network slice includes at least one of the following: the creation information of the network slice, the deletion information of the network slice, the expansion information of the network slice, and the volume reduction information of the network slice.
  • the subscription information of the network slice may include, for example, the area, time, level, and security of the network slice; the QoS information of the network slice may include, for example, throughput, delay, number of connections, reliability, and mobility of the network slice.
  • the network device configures, for the network slice, network resources required for accessing the radio access network, where the network resource includes at least one of: a network function module and a spectrum resource, where the network function module includes Sharing network function modules and/or proprietary network function modules, the spectrum resources including shared spectrum resources and/or proprietary spectrum resources.
  • the manner in which the spectrum resources are divided among different slices includes multiple modes.
  • a set of Resource Blocks (RBs) within a carrier may be configured for the same network slice, which uses the same access technology, ie, includes the same basic parameter set (Numerology Block).
  • RBs Resource Blocks
  • multiple different carriers may be configured for the same network slice, and different access technologies may be used, so that the slice can flexibly select network resources according to channel characteristics, traffic states, and access technologies of different frequency bands.
  • the network function module may include a RAN function module.
  • the RAN function module may include MAC layer user scheduling, HARQ, RLC layer transmission mode, PDCP layer header compression, encryption and decryption, state maintenance of RRC layer user access and handover, and the like.
  • the functional modules of the RAN are neither completely independent of the slice, nor are they completely unified as in the existing LTE system. The number of functional modules of each layer of the protocol stack is determined by the difference in its function itself.
  • FIG. 3 is a functional diagram of a RAN slice controller.
  • the RAN slice controller deploys three layers of functional modules in the base station, and each layer deploys multiple sub-function modules according to service characteristics.
  • the service function chain (SFC) is mapped into different slices by establishing flexible connections of different layer function modules of the data plane.
  • the RAN slice controller may allocate a part of the carrier to multiple slices, and one slice may span multiple carriers, and perform corresponding physical layer parameter configuration according to service characteristics.
  • the network device for managing the radio access network is independent of the service network of the network slice, and configures the network required for accessing the radio access network for the network slice according to the lifecycle management information of the network slice. Resources, so that the network slice can be flexibly allocated to the network resources required for accessing the radio access network, thereby improving communication efficiency.
  • the network device may configure a shared network resource for the network slice. Therefore, multiple network slices can be used to share network resources, thereby avoiding waste or congestion of network resources, thereby flexibly allocating network resources required for accessing the radio access network to the network slice, and improving communication efficiency.
  • the network resources of the radio access network allocated for the network slice may be flexibly and dynamically adjusted after the allocation, and the network resources of the radio access network allocated for the network slice are not fixed. Therefore, the utilization of network resources can be improved.
  • the network resources configured for the network slice include shared network resources.
  • the shared network resource may refer to a network resource shared by multiple network slices.
  • the network resource configured for the network slice may also include a network slice-specific network resource.
  • a proprietary network resource can refer to a network resource that is exclusive to a network slice.
  • the configuring, by the network device, a network resource required for accessing the radio access network where the network device configures a location occupied by a shared spectrum resource of the network slice on a spectrum resource, or The proportion of occupancy between the shared spectrum resource of the network slice and the proprietary spectrum resource.
  • the configuring, by the network slice, network resources required for accessing the radio access network includes: configuring, by the network device, between a shared network function module and a proprietary network function module of the network slice Connection relationship.
  • the configuring, by the network slice, network resources required for accessing the radio access network includes: configuring a shared control channel for a network slice that uses shared spectrum resources.
  • the RAN slice controller can configure network resources for sharing by multiple network slices.
  • different services or different users in the slice can be specified according to the size of the shared network resource and the number of slices that are run. It is also possible to run newly created slices on top of shared network resources and dynamically adjust the ratio of shared to dedicated network resources. Therefore, it is possible to flexibly and dynamically configure each slice, service, and user to use shared or proprietary network function modules or spectrum resources to ensure the reliability of the service while supporting the support of the slice function.
  • the network device may configure a shared network resource for the network slice. Therefore, multiple network slices can be used to share network resources, thereby avoiding waste or congestion of network resources, thereby flexibly allocating network resources required for accessing the radio access network to the network slice, and improving communication efficiency.
  • the configuring, by the network device, network resources required for accessing the radio access network includes: configuring, by the network device, an occupation between a shared network resource of the network slice and a proprietary network resource. proportion.
  • the network device can flexibly configure the occupation ratio between the shared network resource and the private network resource, so as to dynamically adjust the network resource of the wireless access network when the network slice is running and the user traffic changes. , improve the utilization of network resources, and improve the flexibility of configuring the wireless access network.
  • the configuring, by the network device, the network resources required for accessing the radio access network the network device, configured to access the network slice according to at least one of the following information: Network resources required by the radio access network: status information of the network slice, user information of the network slice, and service information of the network slice.
  • the status information of the network slice may include running status information of the network slice or other information indicating a network slice status.
  • some users of the network slice may be attempted to use the access technology on certain carriers to determine the optimal resource allocation to the slice through the running state.
  • the basic function of the user is configured to be processed by using a single module, and the characteristic function of the user is processed by using a separate module, thereby improving the utilization of network resources.
  • the user information may include, but is not limited to, the user has access to the slice instance information, the carrier information supported by the user, the air interface standard information supported by the user, the modulation and coding mode information supported by the user, the scheduling mechanism information supported by the user, and the user support.
  • Reliability mode information user-supported encryption mode information, user-supported mobility state information, user-supported connectivity state information, user-supported energy state information, and the like.
  • the RAN slice controller can flexibly differentiate the configuration of slices, services, and users using shared or independent modules according to the functions required for each slice.
  • an autopilot service and telemedicine service have common requirements for low latency and high reliability, and the same RLC layer transmission mode can be used; however, their mobility requirements are very different, and different RRC layers can be used.
  • the slice controller can configure it to use the same RRC layer, simplifying the complexity of wireless bearer maintenance, and improving the reliability of user switching.
  • the network device can flexibly configure the shared network resource or the dedicated network resource of the radio access network according to the state information of the network slice, the user information of the network slice, and the service information of the network slice, thereby being flexible.
  • the network slice is allocated network resources required for accessing the radio access network to improve communication efficiency.
  • the configuring, by the network device, the network resource required for accessing the radio access network includes: configuring, by the network device, the first user of the network slice according to user information of the network slice A shared network resource or a dedicated network resource of the network slice is used.
  • some low-level slices and users can share other slice resources according to the user's service level or the life cycle of the network slice to ensure important slice and user QoS.
  • the network device configures the first user to use the shared network resource or the dedicated network resource according to the user information of the network slice, thereby configuring the network resource of the wireless access network for the network slice according to the user granularity, and improving the network resource. usage efficiency.
  • the configuring, by the network device, the network resource required for accessing the radio access network includes: configuring, by the network device, the first type of the network slice according to the service information of the network slice.
  • the service uses the shared network resources or dedicated network resources of the network slice.
  • the network device configures the first type of service to use the shared network resource or the dedicated network resource according to the service information of the network slice, thereby configuring the network resource of the wireless access network for the network slice according to the service type granularity, and improving the network. Resource utilization efficiency.
  • FIG. 4 is a schematic flowchart diagram of a communication method 400 according to an embodiment of the present application.
  • Method 400 describes the process by which the RAN slice controller configures the RAN network resources of the network slice.
  • the network device in method 300 can be the RAN slice controller in method 400.
  • Steps S402 to S405 are to deploy/delete functional modules on the CU, and to configure logical mappings between the interfaces and the slices.
  • Steps S406 to S409 are to allocate spectrum resources to the slices and schedule the users. These two parts can be triggered by steps S402 and S406, respectively, or can be triggered by step S401.
  • the user in FIG. 4 is represented by a UE.
  • the network slice orchestrator sends lifecycle management information of the network slice to the RAN controller.
  • the lifecycle management information of the network slice may include: operation information of the slice, such as establishment, deletion, and update of the network slice; type information of the network slice; subscription information of the network slice, for example, area of the network slice, time, level, security Network QoS information, such as network slice throughput, latency, number of connections, reliability, mobility.
  • the RAN slice controller checks the mapping relationship between the existing NF and the slice to the CU on the base station.
  • the S402 portion may also be periodically self-triggered by the RAN slice controller.
  • the NF may include a RAN function module.
  • the mapping relationship may include the following information of the NF: function description information of the NF, tunable parameter information of the NF, service slice information of the NF, and interface capability information of the NF.
  • the RAN slice controller determines to establish a new NF or reuse an existing NF according to the existing NF support capability for the slice, and determines a connection relationship between the NFs to form an SFC of the network slice.
  • the RAN slice controller starts or deletes the NF on the CU, and can be pushed or reclaimed by the mirror warehouse to the CU.
  • the RAN slice controller sends a parameter configuration request to each NF on the CU, and the slice service flow can be processed by a logical channel constructed by the SFC configured by the RAN controller.
  • the parameter configuration request of the NF may include at least one of the following: a slice instance number: used to identify a slice to which the service package belongs, and interface information of the NF, used to establish a logical link connection between the NFs, for example, a port of the NF.
  • the letter may include the ID, IP, port information, etc. of the NF; the service flow rule information is used for buffering, processing, and forwarding the different sliced service flows;
  • the RAN slice controller checks the mapping relationship between the allocated spectrum resources and the slice to the DU on the base station.
  • the S406 portion may also be periodically self-triggered by the RAN slice controller.
  • the mapping relationship between the spectrum resource and the slice may include at least one of the following: carrier information; slice instance information; air interface information, for example, subcarrier spacing, TTI length, etc.; control channel frequency information, scheduling information, and the like.
  • the RAN slice controller configures physical parameters corresponding to the carriers on the DU, and configures a mapping relationship between the RAN slice controller and the corresponding slice.
  • the physical parameter of the carrier may include at least one of the following: subcarrier range information, scheduling period information, priority information, and air interface information.
  • the base station DU selects a control channel of the slice according to the spectrum information allocated by the slice.
  • the DU may adopt two schemes: 1) each slice uses an independent control channel; 2) each slice on the same carrier or air interface system uses a shared control channel.
  • the base station notifies the user of the control channel information through the sliced public broadcast channel. The user then listens to the scheduling information on the designated control channel.
  • the base station DU sends a scheduling request to the user.
  • the included scheduling information is resource allocation information in units of spectrum information.
  • the spectrum information may include frequency point information, subcarrier range information, and scheduling period information.
  • the scheduling information included may be resource allocation information in units of slice information, and the user may obtain the scheduling information of the corresponding slice by parsing the slice information.
  • S410 Perform uplink/downlink transmission between the user and the base station DU.
  • the RAN slice controller can receive slice lifecycle management information for the network slice orchestrator from the northbound interface. And converting the slice service level protocol in the lifecycle management information of the network slice into a configuration parameter of the RAN radio resource and the function module, and assigning a shared or dedicated slice to the slice according to the existing wireless resource allocation and the function module mapping state in the network.
  • FIG. 5 is a schematic flowchart diagram of a communication method 500 according to an embodiment of the present application.
  • Method 500 describes the process by which the RAN slice controller configures the RAN network resources of the network slice based on user information or traffic information.
  • the network device in method 300 may be the RAN slice controller in method 500.
  • the user in FIG. 5 is represented by a UE.
  • the user may send a service access request to the RAN slice controller through a common control channel.
  • the service access request may include slice information, such as a slice type, a slice instance, service information, for example, subscription information, QoS information, and user information.
  • slice information such as a slice type, a slice instance, service information, for example, subscription information, QoS information, and user information.
  • the user information may include, but is not limited to, the user has access to the slice instance information, and the user may support carrier information, air interface information, modulation and coding mode information, scheduling mechanism information, reliability mode information, encryption mode information, and mobility status. Information, connectivity status information, energy status information, etc.
  • the RAN slice controller queries the base station CU for connection state information of the user or the service.
  • connection state information may include a function module responsible for processing in each layer of the RAN for each service flow of the user, a number of users being processed by each module, a size of the service flow, and a size of calculation and storage resources occupied.
  • the RAN slice controller queries the configuration and description files of each functional module to obtain user and service information that can be supported by the RAN slice controller.
  • the RAN slice controller updates the service function chain of the user and the service flow according to the capability and status information of the user and the function module. For example, when the user has accessed multiple slices, the connectivity of the original slice can be used to manage its connectivity; when the reliability of the new slice is high, a new RLC function can be created to manage its retransmission mechanism.
  • the RAN slice controller configures service flow rules of each functional module on the base station CU according to the service function chain. That is, after the service flow enters the base station, the processing, storage, and forwarding mechanism of the module constitutes a logical channel of the service flow.
  • the RAN slice controller queries the scheduling information of the user and the service on the base station, including the number of users, the size of the service flow, and the information about the slice instance.
  • the S507 and the RAN slice controller are configured according to the occupation of each physical resource and the corresponding air interface standard, and apply a scheduling algorithm to update the physical resource allocation of each user or service, or adjust the air interface standard configuration.
  • the air interface format configuration may include at least one of the following: a carrier frequency point, a subcarrier range, a scheduling period, a slice type, a slice instance, a service type, and a user identifier.
  • the base station DU After receiving the scheduling instruction, the base station DU broadcasts control channel information to the user whose access resource is modified through the public broadcast channel, and the user monitors the scheduling information on the updated control channel.
  • the base station DU schedules the user on each physical resource according to the scheduling mechanism indicated by the RAN slice controller, and sends a scheduling instruction to the user.
  • S510 Perform uplink/downlink transmission between the user and the base station DU.
  • the RAN slice controller increases the resource scheduling of different services and users in the slice, so that the network can configure the shared or proprietary wireless resources and function modules according to the difference of services and users.
  • the user is configured to use the network resources of the corresponding sharing level for users of different service levels; and according to the number of user access network slices, configure the flexible use of the partially accessed functional modules to enhance reliability.
  • FIG. 6 is a schematic block diagram of a network device 600 according to an embodiment of the present application. It should be understood that the network device 600 is capable of performing the various steps performed by the network device in the methods of FIGS. 1 through 5, and to avoid repetition, it will not be described in detail herein.
  • the network device includes a RAN slice controller, and the network device 600 includes: a determining unit 610 and a processing unit 620.
  • the determining unit 610 is configured to determine a network slice, where the processing unit 620 is configured to configure, for the network slice, network resources required for accessing the radio access network, where the network resource includes at least one of the following: : a network function module and a spectrum resource, wherein the network function module comprises a shared network function module and/or a proprietary network function module, the spectrum resource comprising a shared spectrum resource and/or a proprietary spectrum resource.
  • FIG. 7 is a schematic block diagram of a network device 700 according to an embodiment of the present application. It should be understood that the network device 700 is capable of performing the various steps performed by the network device in the methods of FIGS. 1 through 5, and to avoid repetition, it will not be described in detail herein.
  • the network device includes a RAN slice controller, and the network device 700 includes:
  • a memory 710 configured to store a program
  • a communication interface 720 configured to communicate with other devices
  • a processor 730 configured to execute a program in the memory 710, the processor 730 is configured to determine a network slice when the program is executed, and configure, for the network slice, a required access to the wireless access network a network resource, the network resource comprising at least one of: a network function module and a spectrum resource, wherein the network function module comprises a shared network function module and/or a proprietary network function module, the spectrum resource comprises a shared spectrum resource and/or Or proprietary spectrum resources.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种通信方法和网络设备。该通信方法包括：用于管理无线接入网的网络设备确定网络切片；网络设备为网络切片配置接入无线接入网所需的网络资源，网络资源包括以下至少一项：网络功能模块和频谱资源，其中网络功能模块包括共享网络功能模块和/或专有网络功能模块，频谱资源包括共享频谱资源和/或专有频谱资源。本申请实施例提供的方法能够灵活地为网络切片分配接入无线接入网所需的网络资源，以提高通信效率。

Description

通信方法和网络设备
本申请要求于2017年6月1日提交中国专利局、申请号为201710405617.5、申请名称为“通信方法和网络设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及通信方法和网络设备。
背景技术
网络切片技术已经被提出作为未来通信系统研究的关键技术，使能未来网络支持丰富的业务以服务于社会的各个行业。例如以虚拟现实、增强现实为代表的增强移动宽带(Enhanced Mobile Broadband,eMBB)业务，自动驾驶、工业控制等为代表的极低时延和高可靠(Ultra-Reliable and Low-Latency,URLLC)业务，和以智能物流、传感器等为代表的海量物联网(massive machine type of communication,mMTC)业务，将极大的拓展通信系统的服务范围。
现有的通信系统将所有的网络业务置于一个公共的传输管道，将无法满足未来网络中不同业务差异巨大的服务质量(Quality of Service,QoS)需求。因此在下一代5G通信系统的研究中，网络切片技术应运而生。在5G无线接入网(Radio Access Network,RAN)部分，所述无线资源可包括频谱资源、站点资源等，所述无线协议可包括无线链路的物理制式(Numerology)、协议栈参数配置等。现有无线通信系统中，通常基站会使所有接入网络的用户共享无线资源，并统一控制和配置协议参数。网络切片的方案提出，将RAN的无线资源和协议根据切片隔离，包括但不限于每个切片使用独占的频谱资源，独立的无线协议配置，从而保障使用切片的业务获得所签约的服务质量。然而，频谱对于运营商来说是非常稀缺昂贵的资源，而移动网络中切片上的业务流量、用户数目、服务质量需求等在时间和空间上可以是动态、随机、快速变化的。因此如何最大化的调度和利用频谱资源，同时保证切片业务管道的隔离性，成为网络切片无线资源管理的一个挑战。
发明内容
本申请提供一种通信方法，能够灵活地为网络切片分配接入无线接入网所需的网络资源，以提高通信效率。
第一方面，提供了一种通信方法，用于管理无线接入网的网络设备确定网络切片；
所述网络设备为所述网络切片配置接入所述无线接入网所需的网络资源，所述网络资源包括以下至少一项：网络功能模块和频谱资源，其中所述网络功能模块包括共享网络功能模块和/或专有网络功能模块，所述频谱资源包括共享频谱资源和/或专有频谱资源。
在本申请实施例中，用于管理无线接入网的网络设备独立于网络切片的业务网之外， 根据网络切片的生命周期管理信息，为网络切片配置接入无线接入网所需的网络资源，从而能够灵活地为网络切片分配接入无线接入网所需的网络资源，提高通信效率。
在本申请实施例中，所述网络设备可以为网络切片配置共享的网络资源。从而实现多个网络切片共享网络资源，避免造成网络资源浪费或拥塞，从而能够灵活地为网络切片分配接入无线接入网所需的网络资源，提高通信效率。
在一种可能的实现方式中，所述网络设备为所述网络切片配置接入所述无线接入网所需的网络资源，包括：所述网络设备频谱资源在频谱资源上占用的位置、或所述网络切片的共享频谱资源与专有频谱资源之间的占用比例。
在本申请实施例中，网络设备可以灵活地配置多个网络切片共享频谱资源、或者灵活地配置网络切片的共享频谱资源与专有频谱资源之间的占用比例，从而在网络切片的运行状态、用户流量变化时，动态地调整无线接入网的网络资源，提高了网络资源的利用率，以及提高了配置无线接入网的灵活度。
所述为所述网络切片配置接入所述无线接入网所需的网络资源，包括：所述网络设备配置所述网络切片的共享网络功能模块和专有网络功能模块之间的连接关系。
在本申请实施例中，网络设备可以灵活地配置共享网络功能模块与专有网络功能模块之间的占用比例，从而在网络切片的运行状态、用户流量变化时，动态地调整无线接入网的网络资源，提高了网络资源的利用率，以及提高了配置无线接入网的灵活度。
在一种可能的实现方式中，所述网络设备为所述网络切片配置接入所述无线接入网所需的网络资源，包括：所述网络设备根据以下信息的至少一项，为所述网络切片配置接入所述无线接入网所需的网络资源：所述网络切片的状态信息、所述网络切片的用户信息、所述网络切片的业务信息。
在本申请实施例中，网络设备可以根据网络切片的状态信息、网络切片的用户信息、网络切片的业务信息情况对无线接入网的共享网络资源或专用网络资源进行灵活地配置，从而能够灵活地为网络切片分配接入无线接入网所需的网络资源，提高通信效率。
一种可能的实现方式中，所述网络设备为所述网络切片配置接入所述无线接入网所需的网络资源，包括：所述网络设备根据所述网络切片的用户信息，配置所述网络切片的第一用户使用所述网络切片的共享网络资源或专用网络资源。
在本申请实施例中，网络设备根据网络切片的用户信息，配置第一用户使用共享网络资源或专用网络资源，从而根据用户粒度为网络切片配置无线接入网的网络资源，提高了网络资源的利用效率。
在一种可能的实现方式中，所述网络设备为所述网络切片配置接入所述无线接入网所需的网络资源，包括：所述网络设备根据所述网络切片的业务信息，配置所述网络切片的第一类型业务使用所述网络切片的共享网络资源或专用网络资源。
在本申请实施例中，网络设备根据网络切片的业务信息，配置第一类型业务使用共享网络资源或专用网络资源，从而根据业务类型粒度为网络切片配置无线接入网的网络资源，提高了网络资源的利用效率。
在一种可能的实现方式中，所述网络切片的生命周期管理信息包括以下至少一项：所述网络切片的创建信息、所述网络切片的删除信息、所述网络切片的扩容信息、所述网络切片的缩容信息、所述网络切片的签约信息、所述网络切片的服务质量QoS信息。
在一种可能的实现方式中，所述网络设备可以从网络切片编排器接收所述网络切片的生命周期管理信息。
第二方面，提供了一种网络设备，用于执行上述第一方面或第一方面的任意可能的实现方式中的方法。具体地，该网络设备包括用于执行上述第一方面或第一方面的任意可能的实现方式中的方法的单元。
第三方面，提供了一种网络设备，该网络设备包括：通信接口、存储器、处理器和总线系统。其中，该通信接口、该存储器和该处理器通过该总线系统相连，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，以控制该通信接口接收信号和/或发送信号，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第四方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
附图说明
图1是本申请实施例的应用环境的示意图。
图2是本申请实施例的通信方法的流程示意图。
图3是本申请实施例的RAN切片控制器的功能示意图。
图4是本申请另一实施例的通信方法的流程示意图。
图5是本申请另一实施例的通信方法的流程示意图。
图6是本申请实施例的网络设备的结构示意图。
图7是本申请又一实施例的网络设备的结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
在介绍本申请的通信方法、装置和系统之前，为了便于理解本申请的内容，先描述本文中出现的一些术语。
网络切片(Network slice)：指在物理或者虚拟的网络基础设施之上，根据不同的服务需求定制化有不同网络能力和网络特性的逻辑网络。网络切片可以是一个包括了终端、接入网、传输网、核心网和应用服务器的完整的端到端网络，能够提供电信服务，具有一定网络能力；网络切片也可以是上述终端、接入网、传输网、核心网和应用服务器的任意组合，例如，网络切片只包含接入网和核心网。网络切片可能具有如下一个或多个特性：接入网可能切片，也可能不切片。接入网可能是多个网络切片共用的。不同的网络切片的特性和组成它们的网络功能模块可能是不一样。
在本申请实施例中，网络切片也可以称为网络切片实例或切片。
网络功能模块(Network function,NF)：是网络中的一种处理功能，定义了功能性的行为和接口，网络功能模块可以通过专用硬件实现，也可以通过在专用硬件上运行软件实现，也可以在通用的硬件平台上以虚拟功能的形式实现。因此，从实现的角度，可以将网络功能模块分为物理网络功能模块和虚拟网络功能模块。而从使用的角度，网络功能模块可以分为专属网络功能模块和共享网络功能模块，具体地，对于多个(子)网络切片实例而言， 可以独立地使用不同的网络功能模块，这种网络功能模块称为专属网络功能模块，也可以共享同一个网络功能模块，这种网络功能模块称为共享网络功能模块。
网络切片生命周期管理器(Network Slice Lifecycle Management,NS-LCM)，NS-LCM可以用于主要负责网络切片的生命周期管理，例如，包括网络切片的创建、组合、更新、删除(终结)等。具体地，可以包括以下功能中的至少一项：(1)接收业务的需求，例如，需要支持/服务的设备数量、数据流的时延和吞吐量、覆盖范围、经济参数(例如收费方式)等；(2)将业务的需求转换为对网络的需求，例如，如果用户的需求是设备数量以及覆盖范围，则对应的网络需求是网络连接的吞吐量/时延、所需的基站数量等；(3)生成网络切片描述符(Network Slice Descriptor，NSD)，对网络切片的组成进行描述，例如，网络切片身份标识(Network Slice Identifier，NS-ID)、网络功能模块、网络切片逻辑拓扑(连接方式、接口、关键性能指标(Key Performance Indicator，KPI)需求)等。具体地，该网络功能模块可以是大颗粒度的功能，例如移动性管理、连接管理、接入控制等功能，也可以是原子功能，例如分组数据汇聚协议(Packet Data Convergence Protocol，简称为PDCP)层的稳健的头压缩(Robust Header Compression，ROHC)、加/解密、重排序等功能，无线链路控制(Radio Link Control，RLC)层的自动重传请求(Automatic Repeat-Request，ARQ)、报文分片、重排序等功能，媒体接入控制(Medium Access Control，MAC)层的混合自动重传请求(Hybrid Automatic Repeat-Request，HARQ)、复用/解复用等功能。该网络切片逻辑拓扑可以用于表示该网络切片的网络功能模块之间的连接方式、接口、KPI需求(可以包括带宽、时延、吞吐量)等等。
网络切片编排器(Network Slice Orchestrator，NSO)：其主要从网络层面对网络切片进行管理。NSO可以基于NS-LCM生成的网络切片需求和实际所拥有的网络资源，对网络资源进行编排。该网络资源可以包括链路资源、存储资源、计算资源或上述的其他网络资源。
在一些实施例中，本申请实施例涉及到的用户可以包括使用终端设备的用户。在另一些实施例中，本申请实施例涉及到的用户也可以包括连接到网络切片的终端设备。上述终端设备可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的用户设备(User Equipment，UE)，移动台(Mobile Station，MS)，终端(terminal)，终端设备(terminal device)等等。
本申请实施例提出一种无线接入网中，用以支持网络切片动态分配、配置和共享网络资源的方法。其可以在实现多个网络切片共享频谱资源、接入网功能模块、无线接入技术和参数配置的同时，保障切片间资源的隔离性和服务质量的可靠性，从而提高无线资源的利用率和切片业务的服务质量，以及功能配置的灵活性和一致性。
首先结合图1，介绍本申请实施例的一种可能的应用环境。如图1所示，该应用环境在网络切片管理系统中引入了无线接入网切片控制器(以下称为RAN切片控制器)。RAN切片控制器可以包括但不限于以下功能：
1)对于无线接入网部分，RAN切片控制器的北向接口与网络切片编排器连接，用于接收切片生命周期管理的指令，包括但不限于切片运行的时间、区域、业务、用户、服务等级等。
2)RAN切片控制器的南向接口与RAN的各个协议层上的功能模块连接，用于对切 片所使用的功能、参数、资源进行灵活配置，以及终端发起业务接入网络切片的请求信息。
3)RAN切片控制器的东西向接口网络其他部分的切片控制器连接，网络控制器接口，用于对RAN切片控制器进行部署、删除、维护，并配置其负责管理的RAN业务节点。
4)RAN切片控制器与核心网、传输网、骨干网等子控制器间的接口用于协调切片业务在各部分网络间服务质量的一致性，维护端到端的业务管道。
作为一种可能的实现方式，在未来的C-RAN网络架构中，基站可以分为集中式单元(Centralized Unit,CU)和分布式单元(Distributed Unit,DU)。CU和DU可软件化或虚拟化，需要灵活组合的RAN功能将运行在由通用服务器所组成的CU中，例如无线链路层控制协议(Radio Link Control，RLC),分组数据汇聚协议(Packet Data Convergence Protocol,PDCP),无线资源控制(Radio Resource Control，RRC)等高层功能；而与硬件强相关并且实时性要求较高的RAN功能将运行在由专有硬件平台所组成的DU中，例如物理层(physical layer，PHY),媒体介入控制层(Media Access Control，MAC)等底层功能。
需要说明的是，本申请实施例中的基站以CU-DU架构对本申请实施例的通信方法进行说明。但本申请实施例的方法并不局限于任何一种的CU-DU架构。本申请实施例的方法也可以不应用于CU-DU架构中。例如，本申请实施例的基站也可包括各种形式的宏基站，微基站，中继站，接入点等等。在采用不同的无线接入技术的系统中，具有基站功能的设备的名称可能会有所不同。例如在LTE网络中，称为演进的节点B(evolved NodeB，eNB或eNodeB)，在第三代(3rd Generation，3G)网络中，称为节点B(Node B)等等。
可选地，RAN切片控制器可以通过南向接口对CU上的RAN功能模块进行动态部署、删除和配置，使其灵活组合形成RAN切片的业务管道；对DU上的RAN物理层模块进行频谱资源分配，并动态调整波形、编解码、调制解调等物理参数，使其适配切片业务对服务质量的需求。
可选地，RAN切片控制器作为独立于业务切片的控制功能模块，可以部署在边缘云数据中心内，控制一个或多个CU和DU，即物理上的一个或多个小区(例如，远端无线单元(Remote Radio Unit,RRU))。
图1中，除RAN切片控制器之外，该应用环境还可以包括传输网(Transport Network,TN)切片控制器以及核心网(Centralized Unit,CN)切片控制器。其中，TN切片控制器用于管理传输网部分，CN切片控制器用于管理核心网部分。
上文介绍了本申请实施例的应用环境，下文将结合附图，介绍本申请实施例的通信方法和网络设备。
图2是本申请实施例的通信方法200的示意性流程图。方法200描述了为网络切片配置接入无线接入网的网络资源的方法。方法200可以适用且不限于图1的应用环境。方法200中的网络设备可以是RAN切片控制器。方法200包括：
S201，用于管理无线接入网的网络设备确定网络切片。
可选地，上述网络设备可以是RAN切片控制器。上述网络切片可以为待配置无线接入网的网络资源的网络切片。
可选地，网络设备可以根据网络切片的运行状态，自主确定需要配置或调整无线接入网的网络资源的网络切片。或者，网络设备可以根据接收到的信息，确定网络切片。例如， 所述网络设备可以接收第一指示信息，所述第一指示信息包括所述网络切片的生命周期管理信息或所述网络切片的用户和业务的接入请求信息；所述网络设备根据所述第一指示信息，确定所述网络切片。
可选地，所述网络设备可以从网络切片编排器接收所述网络切片的生命周期管理信息。
可选地，所述网络设备可以从接入网络切片的终端设备接收素数用户和业务的接入请求信息。
可选地，所述网络切片的生命周期管理信息包括以下至少一项：所述网络切片的操作信息、所述网络切片的签约信息、所述网络切片的服务质量QoS信息。其中，所述网络切片的操作信息包括以下至少一项：所述网络切片的创建信息、所述网络切片的删除信息、所述网络切片的扩容信息、所述网络切片的缩容信息。其中，网络切片的签约信息，例如可以包括网络切片的区域，时间，等级，安全；网络切片的QoS信息例如可以包括网络切片的吞吐量，时延，连接数，可靠性，移动性。
S202，所述网络设备为所述网络切片配置接入所述无线接入网所需的网络资源，所述网络资源包括以下至少一项：网络功能模块和频谱资源，其中所述网络功能模块包括共享网络功能模块和/或专有网络功能模块，所述频谱资源包括共享频谱资源和/或专有频谱资源。
可选地，频谱资源在不同切片间的资源划分方式包括多种方式。例如，可以为同一网络切片配置一个载波内一定数量的资源块(Resource Block，RB)集合，其使用相同的接入技术，即包括相同的基础参数集(Numerology Block)。或者，也可以为同一网络切片配置多个不同的载波，并使用不同的接入技术，从而实现切片可根据不同频段的信道特性、流量状态和接入技术对网络资源进行灵活选择。
可选地，上述网络功能模块可以包括RAN功能模块。例如，RAN功能模块可以包括MAC层用户调度、HARQ，RLC层传输模式，PDCP层包头压缩、加解密，RRC层用户接入和切换的状态维护等等。本申请实施例中，RAN的功能模块对于切片既不是完全独立隔离的，也不是像现有LTE系统一样完全统一的。各层协议栈功能模块的数量由其功能本身的差异性决定。
作为一个示例，图3是RAN切片控制器的功能示意图。如图3所示，RAN切片控制器在基站中部署了三层功能模块，每一层根据业务特性部署了多个子功能模块。通过建立数据面不同层功能模块的灵活连接，从而映射成不同切片的业务功能链(Service Function Chain,SFC)。可选地，对于空口频谱资源，RAN切片控制器可将载波的一部分分给多个切片，同时一个切片可以跨多个载波，并根据业务特性做相应的物理层参数配置。
在本申请实施例中，用于管理无线接入网的网络设备独立于网络切片的业务网之外，根据网络切片的生命周期管理信息，为网络切片配置接入无线接入网所需的网络资源，从而能够灵活地为网络切片分配接入无线接入网所需的网络资源，提高通信效率。
在本申请实施例中，所述网络设备可以为网络切片配置共享的网络资源。从而实现多个网络切片共享网络资源，避免造成网络资源浪费或拥塞，从而能够灵活地为网络切片分配接入无线接入网所需的网络资源，提高通信效率。
在本申请实施例中，为网络切片分配的无线接入网的网络资源在分配之后，可以灵活 地、动态地进行调整，为网络切片分配的无线接入网的网络资源不是固定不变的，因此，可以提高网络资源的利用率。
作为一个示例，为所述网络切片配置的所述网络资源包括共享网络资源。该共享网络资源可以指多个网络切片共用的网络资源。
作为一个示例，为所述网络切片配置的所述网络资源也可以包括网络切片专有网络资源。专有网络资源可以指网络切片独占的网络资源。
可选地，所述为所述网络切片配置接入所述无线接入网所需的网络资源，包括：所述网络设备配置所述网络切片的共享频谱资源在频谱资源上占用的位置、或所述网络切片的共享频谱资源与专有频谱资源之间的占用比例。
可选地，所述为所述网络切片配置接入所述无线接入网所需的网络资源，包括：所述网络设备配置所述网络切片的共享网络功能模块和专有网络功能模块之间的连接关系。
可选地，所述为所述网络切片配置接入所述无线接入网所需的网络资源，包括：为使用共享频谱资源的网络切片配置共享的控制信道。
例如，RAN切片控制器可配置网络资源供多个网络切片共享。同时可以根据共享网络资源的大小和所运行的切片数量，指定切片内的不同业务或不同用户使用。还可以使新建立的切片运行在共享网络资源之上，并动态调整共享与专用网络资源的比例。从而能够灵活、动态配置各切片、业务和用户使用共享或专有的网络功能模块或频谱资源，在保障切片功能特性的支持同时提高业务的可靠性。
在本申请实施例中，所述网络设备可以为网络切片配置共享的网络资源。从而实现多个网络切片共享网络资源，避免造成网络资源浪费或拥塞，从而能够灵活地为网络切片分配接入无线接入网所需的网络资源，提高通信效率。
作为一个示例，所述为所述网络切片配置接入所述无线接入网所需的网络资源，包括：所述网络设备配置所述网络切片的共享网络资源与专有网络资源之间的占用比例。
在本申请实施例中，网络设备可以灵活地配置共享网络资源与专有网络资源之间的占用比例，从而在网络切片的运行状态、用户流量变化时，动态地调整无线接入网的网络资源，提高了网络资源的利用率，以及提高了配置无线接入网的灵活度。
作为一个示例，所述为所述网络切片配置接入所述无线接入网所需的网络资源，包括：所述网络设备根据以下信息的至少一项，为所述网络切片配置接入所述无线接入网所需的网络资源：所述网络切片的状态信息、所述网络切片的用户信息、所述网络切片的业务信息。
例如，所述网络切片的状态信息可以包括所述网络切片的运行状态信息或其他指示网络切片状态的信息。
例如，可以使网络切片的部分用户尝试使用某些载波上的接入技术，通过运行状态决策出最优的资源分配给该切片使用
例如，可以根据用户和功能模块的能力和网络切片的状态信息，配置用户的基础功能使用单一模块进行处理，用户的特性功能使用独立模块进行处理，从而提高了网络资源的利用率。
例如，用户信息可以包括但不局限于：用户已接入切片实例信息，用户支持的载波信息、用户支持的空口制式信息、用户支持的调制编码模式信息、用户支持的调度机制信息、 用户支持的可靠性模式信息、用户支持的加密模式信息，用户支持的移动性状态信息，用户支持的连接性状态信息，用户支持的能量状态信息等。
例如，RAN切片控制器可以根据各个切片所需要的功能，灵活差异化配置切片、业务、用户使用共享或独立的模块。例如，一个自动驾驶业务和远程医疗业务对低时延和高可靠性有共同的要求，可使用相同的RLC层传输模式；但他们对移动性的要求有很大不同，可使用不同的RRC层负责用户切换。另外，对于接入多个网络切片的用户，切片控制器可配置其使用相同的RRC层，简化无线承载维护的复杂性，并提高用户切换时的可靠性。
在本申请实施例中，网络设备可以根据网络切片的状态信息、网络切片的用户信息、网络切片的业务信息情况对无线接入网的共享网络资源或专用网络资源进行灵活地配置，从而能够灵活地为网络切片分配接入无线接入网所需的网络资源，提高通信效率。
作为一个示例，所述为所述网络切片配置接入所述无线接入网所需的网络资源，包括：所述网络设备根据所述网络切片的用户信息，配置所述网络切片的第一用户使用所述网络切片的共享网络资源或专用网络资源。
例如，可以根据用户的服务等级，或网络切片的生命周期，使部分低等级切片和用户共享其它切片资源，以保障重要切片和用户的QoS。
在本申请实施例中，网络设备根据网络切片的用户信息，配置第一用户使用共享网络资源或专用网络资源，从而根据用户粒度为网络切片配置无线接入网的网络资源，提高了网络资源的利用效率。
作为一个示例，所述为所述网络切片配置接入所述无线接入网所需的网络资源，包括：所述网络设备根据所述网络切片的业务信息，配置所述网络切片的第一类型业务使用所述网络切片的共享网络资源或专用网络资源。
在本申请实施例中，网络设备根据网络切片的业务信息，配置第一类型业务使用共享网络资源或专用网络资源，从而根据业务类型粒度为网络切片配置无线接入网的网络资源，提高了网络资源的利用效率。
下面结合具体例子，更加详细地描述本申请实施例，应注意，以下实施例仅仅是为了帮助本领域技术人员理解本申请实施例，而非要将本申请实施例限于所例示的具体场景。本领域技术人员根据所给出的例子，显然可以进行各种等价的修改或变化，这样的修改或变化也落入本申请实施例的范围内。
图4是本申请实施例的通信方法400的流程示意图。方法400描述了RAN切片控制器配置网络切片的RAN网络资源的过程。其中，方法300中的网络设备可以是方法400中的RAN切片控制器。步骤S402～S405为CU上的功能模块部署/删除，配置接口和与切片的逻辑映射，步骤S406～S409为对切片分配频谱资源，并对用户进行调度。这两部分可以分别由步骤S402和S406触发，也可由步骤S401共同触发。其中，图4中的用户用UE表示。
方法400的内容如下所示：
S401、网络切片编排器向RAN控制器发送网络切片的生命周期管理信息。
例如，网络切片的生命周期管理信息可以包括：切片的操作信息，例如网络切片的建立，删除，更新；网络切片的类型信息；网络切片的签约信息，例如网络切片的区域，时 间，等级，安全；网络切片的QoS信息，例如，网络切片的吞吐量，时延，连接数，可靠性，移动性。
S402、RAN切片控制器向基站上的CU检查已有NF和切片的映射关系。
可选地，S402部分也可由RAN切片控制器周期性自我触发。
可选地，NF可以包括RAN功能模块。上述映射关系可以包括NF的以下信息：NF的功能描述信息、NF的可调参数信息、NF的业务切片信息，NF的接口能力信息。
S403、RAN切片控制器根据已有NF对切片的支持能力，决策建立新的NF或复用已有的NF，并确定NF间的连接关系以构成网络切片的SFC。
S404、RAN切片控制器在CU上启动或删除NF，可以由镜像仓库向CU推送或回收。
S405、RAN切片控制器向CU上的各NF发出参数配置请求，切片业务流可以通过RAN控制器所配置的SFC构建的逻辑通道处理。
可选地，NF的参数配置请求可以包括以下至少一项：切片实例编号：用于识别业务包所属的切片；NF的接口信息，用于建立NF间的逻辑链路连接，例如，NF的端口信可以包括NF的ID,IP,端口信息等；业务流规则信息，用于对不同切片业务流的缓存、处理和转发；
S406、RAN切片控制器向基站上的DU检查已分配频谱资源和切片的映射关系。
可选地，S406部分也可以由RAN切片控制器周期性自我触发。
可选地，频谱资源和切片的映射关系可以包括以下至少一项：载波信息；切片实例信息；空口制式信息，例如，子载波间隔,TTI长度等；控制信道频点信息，调度信息等。
S407、RAN切片控制器配置DU上对应各载波的物理参数，并且配置其与对应切片的映射关系。
可选地，上述载波的物理参数可以包括以下至少一项:子载波范围信息、调度周期信息、优先级信息、空口制式信息。
S408、基站DU根据切片分配的频谱信息，选择该切片的控制信道。
可选地，DU可以采用两种方案：1)各切片使用独立控制信道；2)相同载波或空口制式上的各切片使用共享控制信道。基站将控制信道信息通过切片的公共广播信道通知用户。用户则在指定的控制信道上监听调度信息。
S409、基站DU向用户发送调度请求。
可选地，当各切片采用独立控制信道时，所包含的调度信息是以频谱信息为单位的资源分配信息。例如，频谱信息可以包括频点信息，子载波范围信息，调度周期信息。
可选地，当各切片在相同载波的空口制式上共享控制信道时，所包含的调度信息可以是以切片信息为单位的资源分配信息，用户可以通过解析切片信息，获取对应切片的调度信息。
S410、用户和基站DU之间进行上/下行传输。
在图4的例子中，RAN切片控制器可以从北向接口接收网络切片编排器的切片生命周期管理信息。并且将网络切片的生命周期管理信息中的切片业务等级协议转换为RAN无线资源和功能模块的配置参数，并根据网络中已有的无线资源分配和功能模块映射状态，为切片分配共享的或专有的无线资源和网络功能模块。并可以根据切片的运行状态，动态调整共享资源的大小和位置，以及共享与专有资源的占用比例。
图5是本申请实施例的通信方法500的流程示意图。方法500描述了RAN切片控制器根据用户信息或业务信息配置网络切片的RAN网络资源的过程。其中，方法300中的网络设备可以是方法500中的RAN切片控制器。其中，图5中的用户用UE表示。
S501、网络切片建立完成后，用户可以通过公共控制信道向RAN切片控制器发送业务接入请求。
可选地，业务接入请求可以包括切片信息，例如切片类型，切片实例；业务信息，例如，签约信息，QoS信息；用户信息。
其中，用户信息可以包括但不局限于：用户已接入切片实例信息，用户可支持载波信息、空口制式信息、调制编码模式信息、调度机制信息、可靠性模式信息、加密模式信息，移动性状态信息，连接性状态信息，能量状态信息等。
S502、RAN切片控制器向基站CU查询该用户或业务的连接状态信息。
例如，上述连接状态信息可以包括对于该用户各业务流在RAN各层中负责处理的功能模块，各模块正在处理的用户数量和业务流大小，所占用的计算、存储资源大小。
S503、RAN切片控制器查询各功能模块的配置、描述文件获得其所能支持的用户、业务信息。
S504、RAN切片控制器根据用户和功能模块的能力、状态信息，更新对该用户、业务流的业务功能链。例如当用户已接入多个切片，可使用原切片的RRC功能管理其连接性；当新切片的可靠性要求较高，可创建新的RLC功能管理其重传机制等。
S505、RAN切片控制器根据业务功能链，配置基站CU上各功能模块的业务流规则。即业务流进入基站后，模块的处理、存储、转发机制，构成该业务流的逻辑通道。
S506、RAN切片控制器查询基站DU上用户、业务的调度信息，包括各物理资源上用户数量、业务流大小、切片实例信息。
S507、RAN切片控制器根据各物理资源的占用情况，以及对应的空口制式配置，应用调度算法更新各用户、业务的物理资源分配，或调整空口制式配置。
其中，空口制式配置可以包括以下至少一项：载波频点，子载波范围，调度周期，切片类型，切片实例，业务类型，用户标识。
S508、基站DU接收调度指令后，通过公共广播信道，向接入资源被修改的用户广播控制信道信息，用户在更新后的控制信道上监听调度信息。
S509、当有数据，基站DU依据RAN切片控制器所指示的调度机制，在各物理资源上对用户进行调度，并发送调度指令给用户。
S510、用户和基站DU之间进行上/下行传输。
在图5的例子中，增加了RAN切片控制器对切片内不同业务和用户的资源调度，以实现网络可根据业务、用户的差异性，配置其使用共享或专有的无线资源和功能模块。包括对于不同服务等级的用户，配置其使用相应共享等级的网络资源；根据用户接入网络切片的数量，配置其灵活使用部分已接入的功能模块以增强可靠性。
图6是本申请实施例的网络设备600的示意性框图。应理解，网络设备600能够执行图1至图5的方法中由网络设备执行的各个步骤，为了避免重复，此处不再详述。上述网络设备包括RAN切片控制器，网络设备600包括：确定单元610和处理单元620，
所述确定单元610用于用于确定网络切片；所述处理单元620，用于为所述网络切片 配置接入所述无线接入网所需的网络资源，所述网络资源包括以下至少一项：网络功能模块和频谱资源，其中所述网络功能模块包括共享网络功能模块和/或专有网络功能模块，所述频谱资源包括共享频谱资源和/或专有频谱资源。
图7是本申请实施例的网络设备700的示意性框图。应理解，网络设备700能够执行图1至图5的方法中由网络设备执行的各个步骤，为了避免重复，此处不再详述。上述网络设备包括RAN切片控制器，网络设备700包括：
存储器710，用于存储程序；
通信接口720，用于和其他设备进行通信；
处理器730，用于执行存储器710中的程序，当所述程序被执行时，所述处理器730用于确定网络切片；以及为所述网络切片配置接入所述无线接入网所需的网络资源，所述网络资源包括以下至少一项：网络功能模块和频谱资源，其中所述网络功能模块包括共享网络功能模块和/或专有网络功能模块，所述频谱资源包括共享频谱资源和/或专有频谱资源。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory,ROM))、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (17)

  1. 一种通信方法，其特征在于，包括：
    用于管理无线接入网的网络设备确定网络切片；
    所述网络设备为所述网络切片配置接入所述无线接入网所需的网络资源，所述网络资源包括以下至少一项：网络功能模块和频谱资源，其中所述网络功能模块包括共享网络功能模块和/或专有网络功能模块，所述频谱资源包括共享频谱资源和/或专有频谱资源。
  2. 如权利要求1所述的通信方法，其特征在于，所述网络设备为所述网络切片配置接入所述无线接入网所需的网络资源，包括：所述网络设备配置所述网络切片的共享频谱资源在频谱资源上占用的位置、或所述网络切片的共享频谱资源与专有频谱资源之间的占用比例。
  3. 如权利要求1或2所述的通信方法，其特征在于，所述网络设备为所述网络切片配置接入所述无线接入网所需的网络资源，包括：所述网络设备配置所述网络切片的共享网络功能模块和专有网络功能模块之间的连接关系。
  4. 如权利要求1至3中任一项所述的通信方法，其特征在于，所述网络设备为所述网络切片配置接入所述无线接入网所需的网络资源，包括：所述网络设备根据以下信息的至少一项，为所述网络切片配置接入所述无线接入网所需的网络资源：所述网络切片的状态信息、所述网络切片的用户信息、所述网络切片的业务信息。
  5. 如权利要求4所述的通信方法，其特征在于，所述网络设备为所述网络切片配置接入所述无线接入网所需的网络资源，包括：所述网络设备根据所述网络切片的用户信息，配置所述网络切片的第一用户使用所述网络切片的共享网络资源或专用网络资源。
  6. 如权利要求4或5所述的通信方法，其特征在于，所述网络设备为所述网络切片配置接入所述无线接入网所需的网络资源，包括：所述网络设备根据所述网络切片的业务信息，配置所述网络切片的第一类型业务使用所述网络切片的共享网络资源或专用网络资源。
  7. 如权利要求1至6中任一项所述的通信方法，其特征在于，用于管理无线接入网的网络设备确定网络切片，包括：
    所述网络设备接收第一指示信息，所述第一指示信息包括所述网络切片的生命周期管理信息或所述网络切片的用户和业务的接入请求信息；
    所述网络设备根据所述第一指示信息，确定所述网络切片。
  8. 如权利要求7所述的通信方法，其特征在于，所述网络切片的生命周期管理信息包括以下至少一项：所述网络切片的创建信息、所述网络切片的删除信息、所述网络切片的扩容信息、所述网络切片的缩容信息、所述网络切片的签约信息、所述网络切片的服务质量QoS信息。
  9. 一种网络设备，其特征在于，包括：
    确定单元，用于确定网络切片；
    处理单元，用于为所述网络切片配置接入所述无线接入网所需的网络资源，所述网络资源包括以下至少一项：网络功能模块和频谱资源，其中所述网络功能模块包括共享网络 功能模块和/或专有网络功能模块，所述频谱资源包括共享频谱资源和/或专有频谱资源。
  10. 如权利要求9所述的网络设备，其特征在于，在为所述网络切片配置接入所述无线接入网所需的网络资源方面，所述处理单元具体用于配置所述网络切片的共享频谱资源在频谱资源上占用的位置、或所述网络切片的共享频谱资源与专有频谱资源之间的占用比例。
  11. 如权利要求9或10所述的网络设备，其特征在于，在为所述网络切片配置接入所述无线接入网所需的网络资源方面，所述处理单元具体用于配置所述网络切片的共享网络功能模块和专有网络功能模块之间的连接关系。
  12. 如权利要求9至11中任一项所述的网络设备，其特征在于，在为所述网络切片配置接入所述无线接入网所需的网络资源方面，所述处理单元具体用于根据以下信息的至少一项，为所述网络切片配置接入所述无线接入网所需的网络资源：所述网络切片的状态信息、所述网络切片的用户信息、所述网络切片的业务信息。
  13. 如权利要求12所述的网络设备，其特征在于，在为所述网络切片配置接入所述无线接入网所需的网络资源方面，所述处理单元具体用于根据所述网络切片的用户信息，配置所述网络切片的第一用户使用所述网络切片的共享网络资源或专用网络资源。
  14. 如权利要求12或13所述的网络设备，其特征在于，在为所述网络切片配置接入所述无线接入网所需的网络资源方面，所述处理单元具体用于根据所述网络切片的业务信息，配置所述网络切片的第一类型业务使用所述网络切片的共享网络资源或专用网络资源。
  15. 如权利要求9至14中任一项所述的网络设备，其特征在于，在所述确定网络切片方面，所述确定单元具体用于接收第一指示信息，所述第一指示信息包括所述网络切片的生命周期管理信息或所述网络切片的用户和业务的接入请求信息；以及根据所述第一指示信息，确定所述网络切片。
  16. 如权利要求9至15中任一项所述的网络设备，其特征在于，所述网络切片的生命周期管理信息包括以下至少一项：所述网络切片的创建信息、所述网络切片的删除信息、所述网络切片的扩容信息、所述网络切片的缩容信息、所述网络切片的签约信息、所述网络切片的服务质量QoS信息。
  17. 一种计算机存储介质，其特征在于，用于存储计算机程序，所述计算机程序包括用于执行如权利要求1至8中任一项所述的通信方法的指令。
PCT/CN2018/088480 2017-06-01 2018-05-25 通信方法和网络设备 WO2018219229A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710405617.5A CN108990068B (zh) 2017-06-01 2017-06-01 通信方法和网络设备
CN201710405617.5 2017-06-01

Publications (1)

Publication Number Publication Date
WO2018219229A1 true WO2018219229A1 (zh) 2018-12-06

Family

ID=64454445

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/088480 WO2018219229A1 (zh) 2017-06-01 2018-05-25 通信方法和网络设备

Country Status (2)

Country Link
CN (1) CN108990068B (zh)
WO (1) WO2018219229A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021160113A1 (zh) * 2020-02-11 2021-08-19 华为技术有限公司 部署应用实例和调度应用实例的方法和装置

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7015262B2 (ja) * 2019-02-15 2022-02-02 Kddi株式会社 基地局システム、無線ユニット及び無線通信装置
CN111866953B (zh) * 2019-04-26 2023-05-09 中国移动通信有限公司研究院 一种网络资源分配方法、装置和存储介质
CN112152899B (zh) * 2019-06-28 2023-04-07 中兴通讯股份有限公司 一种基于网络切片的数据处理方法及装置
CN112769584B (zh) * 2019-10-21 2023-06-30 中兴通讯股份有限公司 网络切片共享上联口的方法、装置及存储介质
CN111083744B (zh) * 2019-12-31 2022-05-31 北京思特奇信息技术股份有限公司 一种网络切片方法、装置、存储介质和设备
CN113411195B (zh) * 2020-03-17 2022-08-09 中国移动通信集团浙江有限公司 5g切片的物理层配置方法、装置及计算设备
CN113498174A (zh) * 2020-03-20 2021-10-12 北京三星通信技术研究有限公司 一种物理资源划分的方法及设备
CN114079909A (zh) * 2020-08-14 2022-02-22 中国移动通信有限公司研究院 一种网络切片信息处理方法、装置及网络设备
CN112559123A (zh) * 2020-11-18 2021-03-26 山东英特力光通信开发有限公司 一种基于动态资源池虚拟化技术的卫星地面接入站系统
CN114006814B (zh) * 2021-10-11 2023-12-05 中盈优创资讯科技有限公司 一种基于网络的硬切片动态监控方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106550410A (zh) * 2015-09-17 2017-03-29 华为技术有限公司 一种通信控制方法和控制器、用户设备、功能实例
CN106572516A (zh) * 2016-09-28 2017-04-19 华为技术有限公司 一种网络切片选择方法、终端设备及网络设备
US20170141973A1 (en) * 2015-11-13 2017-05-18 Huawei Technologies Co., Ltd. Systems and methods for network slice management

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106341832B (zh) * 2015-07-07 2020-11-06 中国移动通信集团公司 网络切片的管理及选择方法、系统、基站、路由交换设备
WO2017078770A1 (en) * 2015-11-03 2017-05-11 Intel IP Corporation Ran re-architecture for network slicing
CN106549806B (zh) * 2016-10-26 2019-06-18 清华大学 一种网络切片管理器及其管理方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106550410A (zh) * 2015-09-17 2017-03-29 华为技术有限公司 一种通信控制方法和控制器、用户设备、功能实例
US20170141973A1 (en) * 2015-11-13 2017-05-18 Huawei Technologies Co., Ltd. Systems and methods for network slice management
CN106572516A (zh) * 2016-09-28 2017-04-19 华为技术有限公司 一种网络切片选择方法、终端设备及网络设备

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021160113A1 (zh) * 2020-02-11 2021-08-19 华为技术有限公司 部署应用实例和调度应用实例的方法和装置

Also Published As

Publication number Publication date
CN108990068A (zh) 2018-12-11
CN108990068B (zh) 2021-02-05

Similar Documents

Publication Publication Date Title
WO2018219229A1 (zh) 通信方法和网络设备
US11737013B2 (en) Method, terminal device, and network side device for accessing network side device
JP6626204B2 (ja) 無線アクセスネットワークにおけるネットワークスライシングを実行するための方法及びシステム
CN108370398B (zh) 用于多个服务的用户设备状态配置的系统和方法
EP3522589A1 (en) Method and apparatus for managing network slice and computer storage medium
US11191072B2 (en) Information transmission method and radio access network device
EP2672752B1 (en) Wireless bearing building method, access point equipment, user equipment and system
EP3447978B1 (en) Data transmission method and device
EP3796710A1 (en) Radio access network slice generation method, and radio access network
US20240276454A1 (en) Resource allocation method and device for supporting vehicle communication in next generation mobile communication system
WO2021059538A1 (ja) セッション管理装置、ユーザプレーン装置、及びアクセス移動管理装置
EP3565350B1 (en) Method and device for establishing wireless connection
CN114173368B (zh) 一种服务质量QoS的监测方法
KR102480610B1 (ko) 주소 송신 방법, 장치 및 저장매체
WO2017143818A1 (zh) 一种多连接系统中的数据处理方法、装置及计算机存储介质
WO2016101670A1 (zh) 开放式多业务蜂窝网络系统及业务实现方法
CN103814596A (zh) 传输数据的方法、装置和系统
US20150195744A1 (en) Channel Negotiation Method, Device, and System
US20230095067A1 (en) Communication method and communication device
CN106851724B (zh) 一种无线资源处理方法及装置
US12088342B2 (en) Dynamic transport network slicing for converged broadband access
WO2024034227A1 (ja) 通信装置、及び、通信方法
WO2023203938A1 (ja) 端末、基地局、通信方法及び集積回路
CN117897934A (zh) 用于切片调度的方法和装置
KR20110037831A (ko) 기지국에서 확장 케리어를 관리하는 장치 및 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18810285

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18810285

Country of ref document: EP

Kind code of ref document: A1