WO2018127046A1 - 一种业务请求处理方法及装置 - Google Patents

一种业务请求处理方法及装置 Download PDF

Info

Publication number
WO2018127046A1
WO2018127046A1 PCT/CN2018/070083 CN2018070083W WO2018127046A1 WO 2018127046 A1 WO2018127046 A1 WO 2018127046A1 CN 2018070083 W CN2018070083 W CN 2018070083W WO 2018127046 A1 WO2018127046 A1 WO 2018127046A1
Authority
WO
WIPO (PCT)
Prior art keywords
core network
slice
service request
network slice
terminal
Prior art date
Application number
PCT/CN2018/070083
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 中国移动通信有限公司研究院
Priority to US16/476,135 priority Critical patent/US20190357132A1/en
Priority to EP18736393.2A priority patent/EP3567935B1/en
Publication of WO2018127046A1 publication Critical patent/WO2018127046A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/14—Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a service request processing method and apparatus.
  • Core network slicing is the process of cutting a physical network into multiple virtual end-to-end networks. Each virtual network is logically independent of each other. Any virtual network failure will not affect other virtual networks. Each virtual network has Different functional features, facing different needs and services.
  • Core network slicing technology tends to be an on-demand network that provides a wide range of connectivity services to a wide range of industries. This connectivity service is defined by a number of custom software features including geographic coverage, duration, capacity, speed, latency. , reliability, security and availability.
  • the base station function is fixed, and the function of the base station per day is set according to the largest set of network functions.
  • the "user-centric" network architecture requires the network to configure network functions according to the needs of users.
  • the technology in the related technologies cannot support the customization requirements of users, and there is a problem that the selection of core network slices cannot be flexibly participated.
  • An object of the present disclosure is to provide a traffic identification method and apparatus for traffic, which solves the problem that the prior art cannot flexibly participate in the selection of a core network slice.
  • an embodiment of the present disclosure provides a service request processing method, including:
  • the first core network slice supporting the service request is selected from the pre-obtained core network slice set, where the core network slice set includes multiple core network slices, and the core network slice includes core network capability.
  • the method before the step of selecting the first core network slice that supports the service request from the pre-obtained core network slice set, the method further includes:
  • the network side And receiving, by the network side, a core network slice set, where the core network slice set is a set of core network slices selected according to the terminal subscription information and the terminal capability parameter.
  • the method further includes:
  • the slice configuration information includes one or more of the following parameters: an identifier of the slice and a core network capability parameter supported by the slice and/or a core network function module.
  • the embodiment of the present disclosure further provides a service request processing method, including:
  • the method before the step of processing the service request based on the core network slice, the method further includes:
  • the core network slice is not in an active state, activate the core network slice, and after activation, enter a step of processing the service request based on the core network slice; otherwise, directly enter based on the core network slice processing The steps of the business request.
  • the method before the step of receiving the service request message sent by the terminal and the slice configuration information of the core network slice, the method further includes:
  • the core network slice set is a set of core network slices selected according to the subscription information of the terminal and the terminal capability parameter.
  • the method further includes:
  • a slice configuration is performed based on the slice configuration information, and an acknowledgement message is sent to the terminal after the slice configuration is completed.
  • the slice configuration information includes one or more of the following parameters: an identifier of the slice and a core network capability parameter supported by the slice and/or a core network function module.
  • the embodiment of the present disclosure further provides a service request processing method, including:
  • the method further includes:
  • a slice configuration is performed based on the slice configuration information, and an acknowledgement message is sent to the network side after the slice configuration is completed.
  • the slice configuration information includes one or more of the following parameters: an identifier of the slice and a core network capability parameter supported by the slice and/or a core network function module.
  • the embodiment of the present disclosure further provides a service request processing method, including:
  • the core network slice includes a core network capability parameter and/or a core Network function module
  • the method before the step of using the core network slice to transmit the service request, the method further includes:
  • the core network slice is not in an active state, activate the core network slice, and after activation, enter a step of transmitting the service request based on the core network slice; otherwise, directly enter based on the core network slice transmission station The steps of the business request.
  • the method further includes:
  • the slice configuration information includes one or more of the following parameters: an identifier of the slice and a core network capability parameter supported by the slice and/or a core network function module.
  • An embodiment of the present disclosure provides a service request processing apparatus, including:
  • a first selection module configured to: when the terminal initiates a service request, select, from a pre-obtained core network slice set, a first core network slice that supports the service request, where the core network slice set includes multiple core network slices,
  • the core network slice includes a core network capability parameter and/or a core network function module;
  • the first sending module is configured to send the slice configuration information and the service request message of the first core network slice to the network side.
  • the device further includes:
  • the first receiving module is configured to receive a core network slice set sent by the network side, where the core network slice set is a set of core network slices selected according to the subscription information of the terminal and the terminal capability parameter.
  • the device further includes:
  • the second receiving module is configured to receive an acknowledgement message sent by the network side after completing the slice configuration based on the slice configuration information.
  • the slice configuration information includes one or more of the following parameters: an identifier of the slice and a core network capability parameter supported by the slice and/or a core network function module.
  • the embodiment of the present disclosure further provides a service request processing apparatus, including:
  • a third receiving module configured to receive a service request message sent by the terminal and slice configuration information of a core network slice, where the core network slice includes a core network capability parameter and/or a core network function module;
  • a first processing module configured to process the service request based on the core network slice.
  • the device further includes:
  • a first determining module configured to determine whether the core network slice is in an active state
  • a first activation module configured to: if the core network slice is not in an active state, activate the core network slice, and after activation, enter a step of processing the service request based on the core network slice; otherwise, directly enter based on The core network slices the step of processing the service request.
  • the device further includes:
  • the second sending module is configured to send a core network slice set to the terminal, where the core network slice set is a set of core network slices selected according to the terminal subscription information and the terminal capability parameter.
  • the device further includes:
  • a first configuration module configured to perform a slice configuration based on the slice configuration information, and send an acknowledgement message to the terminal after completing the slice configuration.
  • the slice configuration information includes one or more of the following parameters: an identifier of the slice and a core network capability parameter supported by the slice and/or a core network function module.
  • the embodiment of the present disclosure further provides a service request processing apparatus, including:
  • a third sending module configured to send a service request message to the network side, where the service request message carries the first service indication information
  • a fourth receiving module configured to receive, by the network side, slice configuration information of a core network slice that supports the service request information that is selected based on the first service request information, where the core network slice includes a core network capability parameter and / or core network function module.
  • the device further includes:
  • a second configuration module configured to perform a slice configuration based on the slice configuration information, and send an acknowledgement message to the network side after completing the slice configuration.
  • the slice configuration information includes one or more of the following parameters: an identifier of the slice and a core network capability parameter supported by the slice and/or a core network function module.
  • the embodiment of the present disclosure further provides a service request processing apparatus, including:
  • a fifth receiving module configured to receive a service request message sent by the terminal, where the service request message carries the first service indication information
  • a second selection module configured to select, according to the first service indication information, a core network slice that supports the service request, and send slice configuration information of the core network slice to the terminal, where the core network slice includes a core Network capability parameters and/or core network function modules;
  • a second processing module configured to process the service request based on the core network slice.
  • the device further includes:
  • a second determining module configured to determine whether the core network slice is in an active state
  • a second activation module configured to activate the core network slice if the core network slice is not in an active state, and after the activation, enter a step of transmitting the service request based on the core network slice; otherwise, directly enter based on The core network slice transmits the service request step.
  • the device further includes:
  • a sixth receiving module configured to receive a slice confirmation message sent by the terminal after completing the slice configuration based on the slice configuration information.
  • the slice configuration information includes one or more of the following parameters: an identifier of the slice and a core network capability parameter supported by the slice and/or a core network function module.
  • Embodiments of the present disclosure also provide a service request processing apparatus, including: a processor, a memory, and a computer program stored on the memory and executable on the processor, when the computer program is executed by the processor. The steps in the above business request processing method are implemented.
  • the first core network slice supporting the service request is selected from the pre-obtained core network slice set, where the core network slice set includes multiple core network slices, and the core
  • the network slice includes a core network capability parameter and/or a core network function module; and sends the slice configuration information and the service request message of the first core network slice to the network side.
  • FIG. 1 is a schematic structural diagram of a network according to an embodiment of the present disclosure
  • FIG. 2 is a schematic flowchart of a service request processing method according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart diagram of another service request processing method according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic flowchart diagram of another service request processing method according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic flowchart diagram of another service request processing method according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a service request processing apparatus according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of another service request processing apparatus according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of another service request processing apparatus according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a service request processing apparatus according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of another service request processing apparatus according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of another service request processing apparatus according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of another service request processing apparatus according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic structural diagram of a service request processing apparatus according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic structural diagram of another service request processing apparatus according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic structural diagram of a service request processing apparatus according to an embodiment of the present disclosure.
  • FIG. 16 is a schematic structural diagram of another service request processing apparatus according to an embodiment of the present disclosure.
  • FIG. 17 is a schematic structural diagram of another service request processing apparatus according to an embodiment of the present disclosure.
  • the embodiments of the present disclosure are directed to the problem that the technology in the related art cannot support user customization, and there is a problem that the selection of the core network slice cannot be flexibly involved, and a service request processing method and apparatus are provided.
  • the first core network slice supporting the service request is selected from the pre-obtained core network slice set, where the core network slice set includes multiple core network slices, and the core
  • the network slice includes a core network capability parameter and/or a core network function module; and sends the slice configuration information and the service request message of the first core network slice to the network side. This allows for flexible participation in core network slice selection.
  • FIG. 1 is a schematic structural diagram of a network according to an embodiment of the present disclosure.
  • the device includes a terminal 11 and an access network device 12 , where the terminal 11 can be a mobile phone, a tablet computer, a personal computer, a notebook computer, A terminal device that can access the network, such as a wearable device, needs to be described, and the specific type of the terminal 11 is not limited in the embodiment of the present disclosure.
  • the terminal 11 can establish communication with the access network device 12, and the access network device 12 can be a base station in the communication system, for example, an evolved base station (eNB), or can be an RNC in the UTRAN system.
  • eNB evolved base station
  • RNC radio network control network
  • the present disclosure is directed to the problem of the inability to flexibly participate in the selection of core network slices in the related art.
  • a method and apparatus for processing a service request are provided.
  • the terminal initiates a service request in the disclosure
  • the first core network slice supporting the service request is selected from a pre-obtained core network slice set, where the core network slice set includes multiple core network slices, and the core network slice includes The core network capability parameter and/or the core network function module; sending the slice configuration information and the service request message of the first core network slice to the network side. This allows for flexible participation in core network slice selection.
  • FIG. 2 is a schematic diagram of a service request processing method according to an embodiment of the present disclosure. As shown in FIG. 2, the method includes the following steps:
  • the terminal initiates a service request, select, from a pre-obtained core network slice set, a first core network slice that supports the service request, where the core network slice set includes multiple core network slices, and the core network slice includes a core.
  • Network capability parameters and/or core network function modules are included in the core network slice set.
  • the terminal initiates a service request, which may be a service request initiated when the terminal accesses the network for the first time, and the service request includes service indication information, such as digital information or signaling.
  • the core network slice matching the service request may be selected from the pre-obtained core network slice set by using the service indication information.
  • the correspondence between the service indication information and the core network slice may be first established, and then the service indication information is identified.
  • a core network slice that supports the service request can be determined.
  • the pre-obtained core network slice set may be selected by the network side according to the subscription information of the terminal and the capability parameter of the terminal, and the foregoing terminal capability parameters, such as EMBB (Enhanced Mobile Broadband), MME (Mobility Management Entity, Mobility) Management Entity).
  • EMBB Enhanced Mobile Broadband
  • MME Mobility Management Entity
  • the above core network slice includes core network capability parameters and/or core network function modules, such as different network feature function capabilities and different network modules.
  • the terminal when the terminal is to initiate a certain service, the terminal sends the slice configuration information of the selected first core network slice to the network side, where the network side may be a core network or a base station.
  • the network side knows the first core network slice, it is determined whether the first core network slice is in an active state, and if the first core network slice is in an inactive state, the first core network slice is activated, and the first core network slice is adopted. Process the business request.
  • the foregoing slice configuration information may be an identifier of a slice and a core network capability parameter supported by the slice and/or a core network function module. In this way, the network side may select the first core network slice to process the service request according to the slice configuration information of the first core network slice, that is, transmit the service request through the first core network slice.
  • the method before the step of selecting the first core network slice that supports the service request from the pre-obtained core network slice set, the method further includes:
  • the network side And receiving, by the network side, a core network slice set, where the core network slice set is a set of core network slices selected according to the terminal subscription information and the terminal capability parameter.
  • the network side selects all the core network slice sets that meet the subscription information and the terminal capability parameters of the terminal, and sends the slice set to the terminal for the terminal to initiate a service request, and selects The core network slice corresponding to the service request initiates a service request, so that the core network slice can be flexibly selected for data transmission, and a certain core network slice resource can be actively requested from the network side.
  • the method further includes:
  • the network side configures the core network slice based on the slice configuration information, where the configuration includes activating the core network slice and other wireless configurations, and sending the configured confirmation message to the terminal.
  • the terminal can learn the situation on the network side by confirming the message.
  • the slice configuration information includes one or more of the following parameters: an identifier of the slice and a core network capability parameter supported by the slice and/or a core network function module.
  • the identifier of the slice may be the name of the slice, the service type that the slice can support, and the core network capability parameter supported by the slice may be the speed of the core network transmission, the transmission capacity, and the like; the core network function module, such as the EMBB capability, MME capabilities, etc.
  • the first core network slice supporting the service request is selected from the pre-obtained core network slice set, where the core network slice set includes multiple core network slices, and the core
  • the network slice includes a core network capability parameter and/or a core network function module; and sends the slice configuration information and the service request message of the first core network slice to the network side. This allows for flexible participation in core network slice selection.
  • FIG. 3 is a schematic flowchart of another service request processing method according to an embodiment of the present disclosure. As shown in FIG. 3, the method includes the following steps:
  • 301 Receive a service request message sent by a terminal and slice configuration information of a core network slice, where the core network slice includes a core network capability parameter and/or a core network function module.
  • the terminal when the terminal is to initiate a certain service, the terminal sends the slice configuration information of the selected first core network slice to the network side, where the network side may be a core network or a base station.
  • the network side knows the first core network slice, it is determined whether the first core network slice is in an active state, and if the first core network slice is in an inactive state, the first core network slice is activated, and the first core network slice is adopted. Process the business request. In this way, the network side may select the first core network slice to process the service request according to the slice configuration information of the first core network slice, that is, transmit the service request through the first core network slice.
  • the service request is transmitted through the core network slice or the service request is mounted to the core network slice, so that the service request sent by the terminal can be flexibly processed, and the effect of the service request processing is improved.
  • the method before the step of processing the service request based on the core network slice, the method further includes:
  • the core network slice is not in an active state, activate the core network slice, and after activation, enter a step of processing the service request based on the core network slice; otherwise, directly enter based on the core network slice processing The steps of the business request.
  • the state of the core network slice is determined, and the core network slice processing service request is used only when the state of the core network is in an active state, thereby improving service request processing.
  • the accuracy of the operation effectively prevents misuse.
  • the method before the step of receiving the service request message sent by the terminal and the slice configuration information of the core network slice, the method further includes:
  • the core network slice set is a set of core network slices selected according to the subscription information of the terminal and the terminal capability parameter.
  • the network side selects all the core network slice sets that meet the subscription information and the terminal capability parameters of the terminal, and sends the slice set to the terminal for the terminal to initiate a service request, and selects The core network slice corresponding to the service request initiates a service request, so that the core network slice can be flexibly selected for data transmission, and a certain core network slice resource can be actively requested from the network side.
  • the method further includes:
  • a slice configuration is performed based on the slice configuration information, and an acknowledgement message is sent to the terminal after the slice configuration is completed.
  • the network side configures the core network slice based on the slice configuration information, where the configuration includes activating the core network slice and other wireless configurations, and sending the configured confirmation message to the terminal.
  • the terminal can learn the situation on the network side by confirming the message.
  • the slice configuration information includes one or more of the following parameters: an identifier of the slice and a core network capability parameter supported by the slice and/or a core network function module.
  • the identifier of the slice may be the name of the slice, the service type that the slice can support, and the core network capability parameter supported by the slice may be the speed of the core network transmission, the transmission capacity, and the like; the core network function module, such as the EMBB capability, MME capabilities, etc.
  • the service request message sent by the terminal and the slice configuration information of the core network slice are received, the core network slice includes a core network capability parameter and/or a core network function module; and the service is processed based on the core network slice request.
  • the network side flexibly selects the core network slice through the slice configuration information of the terminal, and implements the core network slice processing service request, thereby flexibly participating in the selection of the core network slice.
  • FIG. 4 is a schematic flowchart of another service request processing method according to an embodiment of the present disclosure. As shown in FIG. 4, the method includes the following steps:
  • the service request message is sent to the network side, and the service request message carries the first service indication information, where the first service indication information may be digital information or signaling information, etc.
  • a service indication information selects a core network slice.
  • the slice configuration information of the core network slice of the service request information, the core network slice includes a core network capability parameter and/or a core network function module.
  • the core network slice matching the first service request may be selected from the pre-obtained core network slice set by using the first service indication information, and the correspondence between the service indication information and the core network slice may be first established in the process. And then identifying the first service indication information to determine a core network slice supporting the first service request.
  • the pre-obtained core network slice set may be a core network set selected by the network side according to the subscription information of the terminal and the capability parameter of the terminal, where the terminal capability parameters are EMBB (Enhanced Mobile Broadband, Enhanced Mobile Broadband), and MME (Mobile Management). Entity, Mobility Management Entity).
  • the core network slice includes core network capability parameters and/or core network function modules, such as different network feature capabilities and different network modules.
  • the method further includes:
  • a slice configuration is performed based on the slice configuration information, and an acknowledgement message is sent to the network side after the slice configuration is completed.
  • the network side configures the core network slice based on the slice configuration information, where the configuration includes activating the core network slice and other wireless configurations, and sending the configured confirmation message to the terminal.
  • the terminal can learn the situation on the network side by confirming the message.
  • the slice configuration information includes one or more of the following parameters: an identifier of the slice and a core network capability parameter supported by the slice and/or a core network function module.
  • the identifier of the slice may be the name of the slice, the service type that the slice can support, and the core network capability parameter supported by the slice may be the speed of the core network transmission, the transmission capacity, and the like; the core network function module, such as the EMBB capability, MME capabilities, etc.
  • the service request message is sent to the network side, where the service request message carries the first service indication information, and receives the service request information that is selected by the network side and is selected based on the first service request information.
  • the slice configuration information of the core network slice, the core network slice includes a core network capability parameter and/or a core network function module.
  • FIG. 5 is a schematic flowchart of another service request processing method according to an embodiment of the present disclosure. As shown in FIG. 5, the method includes the following steps:
  • the service request message is sent to the network side, and the service request message carries the first service indication information, where the first service indication information may be digital information or signaling information, etc.
  • a service indication information selects a core network slice.
  • the core network slice includes a core network capability parameter and/or Or core network function module.
  • the core network slice matching the first service request may be selected from the pre-obtained core network slice set by using the first service indication information, and the correspondence between the service indication information and the core network slice may be first established in the process. And then identifying the first service indication information to determine a core network slice supporting the first service request.
  • the pre-obtained core network slice set may be a core network set selected by the network side according to the subscription information of the terminal and the capability parameter of the terminal, where the terminal capability parameters are EMBB (Enhanced Mobile Broadband, Enhanced Mobile Broadband), and MME (Mobile Management). Entity, Mobility Management Entity).
  • the core network slice includes core network capability parameters and/or core network function modules, such as different network feature capabilities and different network modules.
  • the service request is transmitted through the core network slice or the service request is mounted to the core network slice, so that the service request sent by the terminal can be flexibly processed, and the effect of the service request processing is improved.
  • the method before the step of using the core network slice to transmit the service request, the method further includes:
  • the core network slice is not in an active state, activate the core network slice, and after activation, enter a step of transmitting the service request based on the core network slice; otherwise, directly enter based on the core network slice transmission station The steps of the business request.
  • the state of the core network slice is determined, and the core network slice processing service request is used only when the state of the core network is in an active state, thereby improving service request processing.
  • the accuracy of the operation effectively prevents misuse.
  • the method further includes:
  • the network side configures the core network slice based on the slice configuration information, where the configuration includes activating the core network slice and other wireless configurations, and sending the configured confirmation message to the terminal.
  • the terminal can learn the situation on the network side by confirming the message.
  • the slice configuration information includes one or more of the following parameters: an identifier of the slice and a core network capability parameter supported by the slice and/or a core network function module.
  • the identifier of the slice may be the name of the slice, the service type that the slice can support, and the core network capability parameter supported by the slice may be the speed of the core network transmission, the transmission capacity, and the like; the core network function module, such as the EMBB capability, MME capabilities, etc.
  • the service request message sent by the terminal is received, where the service request message carries the first service indication information, and according to the first service indication information, the core network slice supporting the service request is selected, and the device is sent.
  • the network side selects the core network slice based on the service request message sent by the terminal, thereby implementing flexible selection of the core network slice.
  • FIG. 6 is a schematic structural diagram of a service request processing apparatus according to an embodiment of the present disclosure.
  • the service request processing apparatus 600 includes:
  • the first selection module 601 is configured to: when the terminal initiates a service request, select, from a pre-obtained core network slice set, a first core network slice that supports the service request, where the core network slice set includes multiple core network slices, where The core network slice includes a core network capability parameter and/or a core network function module;
  • the first sending module 602 is configured to send the slice configuration information and the service request message of the first core network slice to the network side.
  • the service request processing apparatus 600 further includes:
  • the first receiving module 603 is configured to receive a core network slice set sent by the network side, where the core network slice set is a set of core network slices selected according to the subscription information of the terminal and the terminal capability parameter.
  • the service request processing apparatus 600 further includes:
  • the second receiving module 604 is configured to receive an acknowledgement message sent by the network side after completing the slice configuration based on the slice configuration information.
  • the slice configuration information includes one or more of the following parameters: an identifier of the slice and a core network capability parameter supported by the slice and/or a core network function module.
  • service request processing apparatus 600 in this embodiment may be any implementation manner in the method embodiments in the embodiments of the present disclosure, and achieve the same beneficial effects, and details are not described herein again.
  • FIG. 9 is a schematic structural diagram of another service request processing apparatus 900 according to an embodiment of the present disclosure.
  • the service request processing apparatus 900 includes:
  • the third receiving module 901 is configured to receive a service request message sent by the terminal and slice configuration information of a core network slice, where the core network slice includes a core network capability parameter and/or a core network function module;
  • the first processing module 902 is configured to process the service request based on the core network slice.
  • the service request processing apparatus 900 further includes:
  • the first determining module 903 is configured to determine whether the core network slice is in an active state
  • the first activation module 904 is configured to activate the core network slice if the core network slice is not in an active state, and after the activation, enter a step of processing the service request based on the core network slice; otherwise, directly enter The step of processing the service request based on the core network slice.
  • the service request processing apparatus 900 further includes:
  • the second sending module 905 is configured to send a core network slice set to the terminal, where the core network slice set is a set of core network slices selected according to the subscription information of the terminal and the terminal capability parameter.
  • the service request processing apparatus 900 further includes:
  • the first configuration module 906 is configured to perform a slice configuration based on the slice configuration information, and send an acknowledgement message to the terminal after completing the slice configuration.
  • the slice configuration information includes one or more of the following parameters: an identifier of the slice and a core network capability parameter supported by the slice and/or a core network function module.
  • the foregoing service request processing apparatus 900 may be any implementation manner in the method embodiments in the embodiments of the present disclosure, and achieve the same beneficial effects, and details are not described herein again.
  • FIG. 13 is a schematic structural diagram of another service request processing apparatus 1300 according to an embodiment of the present disclosure. As shown in FIG. 13, the service request processing apparatus 1300 includes:
  • the third sending module 1301 is configured to send a service request message to the network side, where the service request message carries the first service indication information;
  • the fourth receiving module 1302 is configured to receive, by the network side, slice configuration information of a core network slice that supports the service request information that is selected based on the first service request information, where the core network slice includes a core network capability parameter. And / or core network function modules.
  • the service request processing apparatus 1300 further includes:
  • the second configuration module 1303 is configured to perform a slice configuration based on the slice configuration information, and send an acknowledgement message to the network side after completing the slice configuration.
  • the slice configuration information includes one or more of the following parameters: an identifier of the slice and a core network capability parameter supported by the slice and/or a core network function module.
  • FIG. 15 is a schematic structural diagram of another service request processing apparatus 1500 according to an embodiment of the present disclosure.
  • the service request processing apparatus 1500 includes:
  • the fifth receiving module 1501 is configured to receive a service request message sent by the terminal, where the service request message carries the first service indication information;
  • the second selection module 1502 is configured to select, according to the first service indication information, a core network slice that supports the service request, and send slice configuration information of the core network slice to the terminal, where the core network slice includes Core network capability parameters and/or core network function modules;
  • the second processing module 1503 is configured to process the service request based on the core network slice.
  • the service request processing apparatus 1500 further includes:
  • the second determining module 1504 is configured to determine whether the core network slice is in an active state
  • a second activation module 1505 configured to activate the core network slice if the core network slice is not in an active state, and after the activation, enter a step of transmitting the service request based on the core network slice; otherwise, directly enter The step of transmitting the service request based on the core network slice.
  • the service request processing apparatus further includes:
  • the sixth receiving module 1506 is configured to receive a slice confirmation message that is sent by the terminal after completing the slice configuration based on the slice configuration information.
  • the slice configuration information includes one or more of the following parameters: an identifier of the slice and a core network capability parameter supported by the slice and/or a core network function module.
  • the service request processing apparatus 1500 may be any implementation manner in the method embodiment in the embodiment of the disclosure, and achieve the same beneficial effects, and details are not described herein again.
  • the disclosed methods and apparatus may be implemented in other ways.
  • 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.
  • each functional unit in various embodiments of the present disclosure may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium.
  • the above software functional unit is stored in a storage medium and includes a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform part of the steps of the transceiving method of the various embodiments of the present disclosure.
  • 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, and the program code can be stored. Medium.

Landscapes

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

Abstract

本公开提供一种业务请求处理方法和装置，该方法可包括：终端发起业务请求时，从预先获得的核心网切片集合中选择支持所述业务请求的第一核心网切片，所述核心网切片集合包括多个核心网切片，所述核心网切片包括核心网能力参数和/或核心网功能模块；发送所述第一核心网切片的切片配置信息和业务请求消息至网络侧。

Description

一种业务请求处理方法及装置
相关申请的交叉引用
本申请主张在2017年1月6日在中国提交的中国专利申请号No.201710009902.5的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种业务请求处理方法及装置。
背景技术
核心网切片是将一个物理网络切割为多个虚拟的端到端的网络，每个虚拟网络逻辑上是相互独立即任何一个虚拟网络故障都不会影响其他的虚拟网络，其中，每个虚拟网络具备各自不同的功能特点，面向不同的需求和服务。核心网切片技术趋向于按需网络，可以给各行各业提供广泛的连接服务，这种连接服务是通过许多定制软件功能定义的，这些软件功能包括地理覆盖区域、持续时间、容量、速度、延迟、可靠性、安全性和可用性等。基站功能是固定的，按照网络功能的最大集合设定每天基站的功能。在5G中，以“用户为中心”的网络架构要求网络能够按照用户的需求配置网络功能，相关技术中的技术无法支撑用户定制化的需求，存在不能灵活的参与核心网切片的选择的问题。
发明内容
本公开的目的在于提供一种流量的业务识别方法及装置，解决了现有技术中不能灵活的参与核心网切片的选择的问题。
为了达到上述目的，本公开实施例提供一种业务请求处理方法，包括：
终端发起业务请求时，从预先获得的核心网切片集合中选择支持所述业务请求的第一核心网切片，所述核心网切片集合包括多个核心网切片，所述核心网切片包括核心网能力参数和/或核心网功能模块；
发送所述第一核心网切片的切片配置信息和业务请求消息至网络侧。
可选的，在所述终端发起业务请求时，从预先获得的核心网切片集合中选择支持所述业务请求的第一核心网切片的步骤之前，还包括：
接收所述网络侧发送的核心网切片集合，所述核心网切片集合是根据终端的签约信息和终端能力参数选择出的核心网切片的集合。
可选的，在所述发送所述业务请求消息给网络侧的步骤之后，还包括：
接收所述网络侧基于所述切片配置信息完成切片配置后发送的确认消息。
可选的，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
本公开实施例还提供一种业务请求处理方法，包括：
接收终端发送的业务请求消息和核心网切片的切片配置信息，所述核心网切片包括核心网能力参数和/或核心网功能模块；
基于所述核心网切片处理所述业务请求。
可选的，在所述基于所述核心网切片处理所述业务请求的步骤之前，还包括：
判断所述核心网切片是否处于激活状态；
若所述核心网切片未处于激活状态，激活所述核心网切片，并在激活之后，进入基于所述核心网切片处理所述业务请求的步骤；否则，直接进入基于所述核心网切片处理所述业务请求的步骤。
可选的，在所述接收终端发送的业务请求消息和核心网切片的切片配置信息的步骤之前，还包括：
发送核心网切片集合至终端，所述核心网切片集合是根据终端的签约信息和终端能力参数选择出的核心网切片的集合。
可选的，在所述基于所述核心网切片处理所述业务请求的步骤之后，还包括：
基于所述切片配置信息进行切片配置，并在完成切片配置后发送确认消息至所述终端。
可选的，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
本公开实施例还提供一种业务请求处理方法，包括：
发送业务请求消息至网络侧，所述业务请求消息携带有第一业务指示信息；
接收所述网络侧发送的基于所述第一业务请求信息选择的支持所述业务请求信息的核心网切片的切片配置信息，所述核心网切片包括核心网能力参数和/或核心网功能模块。
可选的，在所述接收所述网络侧发送的基于所述第一业务请求信息选择的支持所述业务请求信息的核心网切片的切片配置信息的步骤之后，还包括：
基于所述切片配置信息进行切片配置，并在完成切片配置后发送确认消息至所述网络侧。
可选的，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
本公开实施例还提供一种业务请求处理方法，包括：
接收终端发送的业务请求消息，所述业务请求消息携带有第一业务指示信息；
根据所述第一业务指示信息，选择支持所述业务请求的核心网切片，并发送所述核心网切片的切片配置信息至所述终端，所述核心网切片包括核心网能力参数和/或核心网功能模块；
基于所述核心网切片处理所述业务请求。
可选的，在所述使用所述核心网切片传输所述业务请求的步骤之前，还包括：
判断所述核心网切片是否处于激活状态；
若所述核心网切片未处于激活状态，激活所述核心网切片，并在激活之后，进入基于所述核心网切片传输所述业务请求的步骤；否则，直接进入基于所述核心网切片传输所述业务请求的步骤。
可选的，在发送所述核心网切片的切片配置信息至所述终端步骤之后，还包括：
接收所述终端基于所述切片配置信息完成切片配置后发送的切片确认消息。
可选的，所述切片配置信息包括以下参数的一种或多种：切片的标识以 及切片支持的核心网能力参数和/或核心网功能模块。
本公开实施例提供一种业务请求处理装置，包括：
第一选择模块，用于终端发起业务请求时，从预先获得的核心网切片集合中选择支持所述业务请求的第一核心网切片，所述核心网切片集合包括多个核心网切片，所述核心网切片包括核心网能力参数和/或核心网功能模块；
第一发送模块，用于发送所述第一核心网切片的切片配置信息和业务请求消息至网络侧。
可选的，所述装置还包括：
第一接收模块，用于接收所述网络侧发送的核心网切片集合，所述核心网切片集合是根据终端的签约信息和终端能力参数选择出的核心网切片的集合。
可选的，所述装置还包括：
第二接收模块，用于接收所述网络侧基于所述切片配置信息完成切片配置后发送的确认消息。
可选的，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
本公开实施例还提供一种业务请求处理装置，包括：
第三接收模块，用于接收终端发送的业务请求消息和核心网切片的切片配置信息，所述核心网切片包括核心网能力参数和/或核心网功能模块；
第一处理模块，用于基于所述核心网切片处理所述业务请求。
可选的，所述装置还包括：
第一判断模块，用于判断所述核心网切片是否处于激活状态；
第一激活模块，用于若所述核心网切片未处于激活状态，激活所述核心网切片，并在激活之后，进入基于所述核心网切片处理所述业务请求的步骤；否则，直接进入基于所述核心网切片处理所述业务请求的步骤。
可选的，所述装置还包括：
第二发送模块，用于发送核心网切片集合至终端，所述核心网切片集合是根据终端的签约信息和终端能力参数选择出的核心网切片的集合。
可选的，所述装置还包括：
第一配置模块，用于基于所述切片配置信息进行切片配置，并在完成切片配置后发送确认消息至所述终端。
可选的，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
本公开实施例还提供一种业务请求处理装置，包括：
第三发送模块，用于发送业务请求消息至网络侧，所述业务请求消息携带有第一业务指示信息；
第四接收模块，用于接收所述网络侧发送的基于所述第一业务请求信息选择的支持所述业务请求信息的核心网切片的切片配置信息，所述核心网切片包括核心网能力参数和/或核心网功能模块。
可选的，所述装置还包括：
第二配置模块，用于基于所述切片配置信息进行切片配置，并在完成切片配置后发送确认消息至所述网络侧。
可选的，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
本公开实施例还提供一种业务请求处理装置，包括：
第五接收模块，用于接收终端发送的业务请求消息，所述业务请求消息携带有第一业务指示信息；
第二选择模块，用于根据所述第一业务指示信息，选择支持所述业务请求的核心网切片，并发送所述核心网切片的切片配置信息至所述终端，所述核心网切片包括核心网能力参数和/或核心网功能模块；
第二处理模块，用于基于所述核心网切片处理所述业务请求。
可选的，所述装置还包括：
第二判断模块，用于判断所述核心网切片是否处于激活状态；
第二激活模块，用于若所述核心网切片未处于激活状态，激活所述核心网切片，并在激活之后，进入基于所述核心网切片传输所述业务请求的步骤；否则，直接进入基于所述核心网切片传输所述业务请求的步骤。
可选的，所述装置还包括：
第六接收模块，用于接收所述终端基于所述切片配置信息完成切片配置 后发送的切片确认消息。
可选的，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
本公开实施例还提供一种业务请求处理装置，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述业务请求处理方法中的步骤。
本公开的上述技术方案至少具有如下有益效果：
本公开实施例中，终端发起业务请求时，从预先获得的核心网切片集合中选择支持所述业务请求的第一核心网切片，所述核心网切片集合包括多个核心网切片，所述核心网切片包括核心网能力参数和/或核心网功能模块；发送所述第一核心网切片的切片配置信息和业务请求消息至网络侧。通过上述特征，从而本公开实施例中，可以实现灵活的参与核心网切片的选择。
附图说明
图1为本公开实施例提供的网络结构示意图；
图2是本公开实施例提供的一种业务请求处理方法的流程示意图；
图3是本公开实施例提供的另一种业务请求处理方法的流程示意图；
图4是本公开实施例提供的另一种业务请求处理方法的流程示意图；
图5是本公开实施例提供的另一种业务请求处理方法的流程示意图；
图6是本公开实施例提供的一种业务请求处理装置结构示意图；
图7是本公开实施例提供的另一种业务请求处理装置结构示意图；
图8是本公开实施例提供的另一种业务请求处理装置结构示意图；
图9是本公开实施例提供的一种业务请求处理装置结构示意图；
图10是本公开实施例提供的另一种业务请求处理装置结构示意图；
图11是本公开实施例提供的另一种业务请求处理装置结构示意图；
图12是本公开实施例提供的另一种业务请求处理装置结构示意图；
图13是本公开实施例提供的一种业务请求处理装置结构示意图；
图14是本公开实施例提供的另一种业务请求处理装置结构示意图；
图15是本公开实施例提供的一种业务请求处理装置结构示意图；
图16是本公开实施例提供的另一种业务请求处理装置结构示意图；
图17是本公开实施例提供的另一种业务请求处理装置结构示意图。
具体实施方式
为使本公开要解决的技术问题、技术方案和优点更加清楚，下面将结合附图及具体实施例进行详细描述。
本公开实施例针对相关技术中的技术无法支撑用户定制化的需求，存在不能灵活的参与核心网切片的选择的问题，提供一种业务请求处理方法和装置。本公开实施例中，终端发起业务请求时，从预先获得的核心网切片集合中选择支持所述业务请求的第一核心网切片，所述核心网切片集合包括多个核心网切片，所述核心网切片包括核心网能力参数和/或核心网功能模块；发送所述第一核心网切片的切片配置信息和业务请求消息至网络侧。从而可以实现灵活的参与核心网切片的选择。
参见图1，图1为本公开实施例提供的网络结构示意图，如图1所示，包括终端11和接入网设备12，其中，终端11可以是手机、平板电脑、个人计算机、笔记本电脑、可穿戴设备等可以接入网络的终端设备，需要说明的是，在本公开实施例中并不限定终端11的具体类型。终端11可以与接入网设备12建立通信，另外，接入网设备12可以是该通信系统中的基站，例如：演进型基站(eNB，evolved Node B)，或者可以是UTRAN系统中的RNC，需要说明的是，在本公开实施例中并不限定接入网设备12的具体类型。接入网设备12可以与网络侧进行通信，从而进行核心网切片的选择，并通过核心网切片对业务请求进行处理。
本公开针对相关技术中不能灵活的参与核心网切片的选择的问题。提供一种业务请求处理方法和装置。本公开中终端发起业务请求时，从预先获得的核心网切片集合中选择支持所述业务请求的第一核心网切片，所述核心网切片集合包括多个核心网切片，所述核心网切片包括核心网能力参数和/或核心网功能模块；发送所述第一核心网切片的切片配置信息和业务请求消息至网络侧。从而可以实现灵活的参与核心网切片的选择。
参见图2，图2是本公开实施例提供的一种业务请求处理方法的流程示 意图，如图2所示，包括以下步骤：
201、终端发起业务请求时，从预先获得的核心网切片集合中选择支持所述业务请求的第一核心网切片，所述核心网切片集合包括多个核心网切片，所述核心网切片包括核心网能力参数和/或核心网功能模块。
该步骤中，终端发起业务请求时可以是终端第一次接入网络时发起的业务请求，该业务请求包括业务指示信息，例如数字信息或者信令等指示信息。通过这些业务指示信息可以从预先获得的核心网切片集合选择与该业务请求匹配的核心网切片，该过程中可以首先建立业务指示信息与核心网切片之间的对应关系，然后识别业务指示信息就可以确定支持该业务请求的核心网切片。其中，预先获得的核心网切片集合可以是网络侧根据终端的签约信息和终端的能力参数选择出的，上述终端能力参数如EMBB(增强移动宽带，Enhanced Mobile Broadband)、MME(移动管理实体，Mobility Management Entity)。上述核心网切片包括核心网能力参数和/核心网功能模块，如不同的网络特征功能能力、网络不同模块。
202、发送所述第一核心网切片的切片配置信息和业务请求消息至网络侧。
该步骤中，当终端要发起某个业务时，终端将选出的第一核心网切片的切片配置信息发送给网络侧，该网络侧可以是核心网也可以是基站。当网络侧获知第一核网切片时，判断第一核心网切片是否处于激活状态，若第一核心网切片处于未激活状态，将该第一核心网切片激活，并通过该第一核心网切片对业务请求进行处理。其中，上述切片配置信息可以是切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。这样，网络侧可以根据第一核心网切片的切片配置信息选出第一核心网切片对业务请求进行处理即通过第一核心网切片传输业务请求。
可选的，在所述终端发起业务请求时，从预先获得的核心网切片集合中选择支持所述业务请求的第一核心网切片的步骤之前，还包括：
接收所述网络侧发送的核心网切片集合，所述核心网切片集合是根据终端的签约信息和终端能力参数选择出的核心网切片的集合。
该实施方式中，当终端接入网络时，网络侧选出符合终端的签约信息和终端能力参数的所有的核心网切片集合，并将该切片集合发送给终端以供终 端发起业务请求时，选择与该业务请求相对应的核心网切片发起业务请求，这样可以灵活的选择核心网切片进行数据传输，并且可以主动向网络侧请求一定的核心网切片资源。
可选的，在所述发送所述业务请求消息给网络侧的步骤之后，还包括：
接收所述网络侧基于所述切片配置信息完成切片配置后发送的确认消息。
该实施方式中，网路侧在接收到切片配置信息后，基于该切片配置信息对核心网切片进行配置，该配置包括激活核心网切片和其他无线配置，并将配置完的确认消息发送给终端，这样，终端可以通过确认消息来获知网络侧的情况。
可选的，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
该实施方式中，切片的标识可以是切片的名称、切片能够支持的业务类型等；切片支持的核心网能力参数可以为核心网传输的速度、传输的容量等；核心网功能模块如EMBB能力、MME能力等。
本公开实施例中，终端发起业务请求时，从预先获得的核心网切片集合中选择支持所述业务请求的第一核心网切片，所述核心网切片集合包括多个核心网切片，所述核心网切片包括核心网能力参数和/或核心网功能模块；发送所述第一核心网切片的切片配置信息和业务请求消息至网络侧。从而可以实现灵活的参与核心网切片的选择。
参见图3，图3是本公开实施例提供的另一种业务请求处理方法的流程示意图，如图3所示，包括以下步骤：
301、接收终端发送的业务请求消息和核心网切片的切片配置信息，所述核心网切片包括核心网能力参数和/或核心网功能模块。
该步骤中，当终端要发起某个业务时，终端将选出的第一核心网切片的切片配置信息发送给网络侧，该网络侧可以是核心网也可以是基站。当网络侧获知第一核网切片时，判断第一核心网切片是否处于激活状态，若第一核心网切片处于未激活状态，将该第一核心网切片激活，并通过该第一核心网切片对业务请求进行处理。这样，网络侧可以根据第一核心网切片的切片配置信息选出第一核心网切片对业务请求进行处理即通过第一核心网切片传输 业务请求。
302、基于所述核心网切片处理所述业务请求。
该步骤中，通过上述核心网切片对业务请求进行传输或者将业务请求挂载至核心网切片，这样，就可以灵活的处理终端发送的业务请求，提高业务请求处理的效果。
可选的，在所述基于所述核心网切片处理所述业务请求的步骤之前，还包括：
判断所述核心网切片是否处于激活状态；
若所述核心网切片未处于激活状态，激活所述核心网切片，并在激活之后，进入基于所述核心网切片处理所述业务请求的步骤；否则，直接进入基于所述核心网切片处理所述业务请求的步骤。
该实施方式中，当确定处理业务请求的核心网切片时，对核心网切片的状态进行判断，只有当核心网的状态处于激活状态时才使用该核心网切片处理业务请求，从而提高业务请求处理的准确性，有效地防止误操作。
可选的，在所述接收终端发送的业务请求消息和核心网切片的切片配置信息的步骤之前，还包括：
发送核心网切片集合至终端，所述核心网切片集合是根据终端的签约信息和终端能力参数选择出的核心网切片的集合。
该实施方式中，当终端接入网络时，网络侧选出符合终端的签约信息和终端能力参数的所有的核心网切片集合，并将该切片集合发送给终端以供终端发起业务请求时，选择与该业务请求相对应的核心网切片发起业务请求，这样可以灵活的选择核心网切片进行数据传输，并且可以主动向网络侧请求一定的核心网切片资源。
可选的，在所述基于所述核心网切片处理所述业务请求的步骤之后，还包括：
基于所述切片配置信息进行切片配置，并在完成切片配置后发送确认消息至所述终端。
该实施方式中，网路侧在接收到切片配置信息后，基于该切片配置信息对核心网切片进行配置，该配置包括激活核心网切片和其他无线配置，并将 配置完的确认消息发送给终端，这样，终端可以通过确认消息来获知网络侧的情况。
可选的，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
该实施方式中，切片的标识可以是切片的名称、切片能够支持的业务类型等；切片支持的核心网能力参数可以为核心网传输的速度、传输的容量等；核心网功能模块如EMBB能力、MME能力等。
本公开实施例中，接收终端发送的业务请求消息和核心网切片的切片配置信息，所述核心网切片包括核心网能力参数和/或核心网功能模块；基于所述核心网切片处理所述业务请求。这样，网络侧通过终端的切片配置信息灵活选择核心网切片，并实现核心网切片处理业务请求，从而灵活的参与核心网切片的选择。
参见图4，图4是本公开实施例提供的另一种业务请求处理方法的流程示意图，如图4所示，包括以下步骤：
401、发送业务请求消息至网络侧，所述业务请求消息携带有第一业务指示信息。
该步骤中，终端发起业务请求时将业务请求消息发送至网络侧，上述业务请求消息携带第一业务指示信息，该第一业务指示信息可以是数字信息或者信令信息等指示信息，通过该第一业务指示信息选择核心网切片。
402、接收所述网络侧发送的基于所述第一业务请求信息选择的支持所述业务请求信息的核心网切片的切片配置信息，所述核心网切片包括核心网能力参数和/或核心网功能模块。
业务请求信息的核心网切片的切片配置信息，所述核心网切片包括核心网能力参数和/或核心网功能模块。
该步骤中，通过第一业务指示信息可以从预先获得的核心网切片集合选择与该第一业务请求匹配的核心网切片，该过程中可以首先建立业务指示信息与核心网切片之间的对应关系，然后识别第一业务指示信息就可以确定支持该第一业务请求的核心网切片。其中，预先获得的核心网切片集合可以是网络侧根据终端的签约信息和终端的能力参数选择出的核心网集合，上述终 端能力参数如EMBB(增强移动宽带，Enhanced Mobile Broadband)、MME(移动管理实体，Mobility Management Entity)。核心网切片包括核心网能力参数和/核心网功能模块，如不同的网络特征功能能力、网络不同模块。
可选的，在所述接收所述网络侧发送的基于所述第一业务请求信息选择的支持所述业务请求信息的核心网切片的切片配置信息的步骤之后，还包括：
基于所述切片配置信息进行切片配置，并在完成切片配置后发送确认消息至所述网络侧。
该实施方式中，网路侧在接收到切片配置信息后，基于该切片配置信息对核心网切片进行配置，该配置包括激活核心网切片和其他无线配置，并将配置完的确认消息发送给终端，这样，终端可以通过确认消息来获知网络侧的情况。
可选的，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
该实施方式中，切片的标识可以是切片的名称、切片能够支持的业务类型等；切片支持的核心网能力参数可以为核心网传输的速度、传输的容量等；核心网功能模块如EMBB能力、MME能力等。
本公开实施例中，发送业务请求消息至网络侧，所述业务请求消息携带有第一业务指示信息；接收所述网络侧发送的基于所述第一业务请求信息选择的支持所述业务请求信息的核心网切片的切片配置信息，所述核心网切片包括核心网能力参数和/或核心网功能模块。这样，终端在发送业务请求时，获取支持该业务请求的核心网切片，从而实现灵活的参与核心网切片的选择。
参见图5，图5是本公开实施例提供的另一种业务请求处理方法的流程示意图，如图5所示，包括以下步骤：
501、接收终端发送的业务请求消息，所述业务请求消息携带有第一业务指示信息。
该步骤中，终端发起业务请求时将业务请求消息发送至网络侧，上述业务请求消息携带第一业务指示信息，该第一业务指示信息可以是数字信息或者信令信息等指示信息，通过该第一业务指示信息选择核心网切片。
502、根据所述第一业务指示信息，选择支持所述业务请求的核心网切片， 并发送所述核心网切片的切片配置信息至所述终端，所述核心网切片包括核心网能力参数和/或核心网功能模块。
该步骤中，通过第一业务指示信息可以从预先获得的核心网切片集合选择与该第一业务请求匹配的核心网切片，该过程中可以首先建立业务指示信息与核心网切片之间的对应关系，然后识别第一业务指示信息就可以确定支持该第一业务请求的核心网切片。其中，预先获得的核心网切片集合可以是网络侧根据终端的签约信息和终端的能力参数选择出的核心网集合，上述终端能力参数如EMBB(增强移动宽带，Enhanced Mobile Broadband)、MME(移动管理实体，Mobility Management Entity)。核心网切片包括核心网能力参数和/核心网功能模块，如不同的网络特征功能能力、网络不同模块。
503、基于所述核心网切片处理所述业务请求。
该步骤中，通过上述核心网切片对业务请求进行传输或者将业务请求挂载至核心网切片，这样，就可以灵活的处理终端发送的业务请求，提高业务请求处理的效果。
可选的，在所述使用所述核心网切片传输所述业务请求的步骤之前，还包括：
判断所述核心网切片是否处于激活状态；
若所述核心网切片未处于激活状态，激活所述核心网切片，并在激活之后，进入基于所述核心网切片传输所述业务请求的步骤；否则，直接进入基于所述核心网切片传输所述业务请求的步骤。
该实施方式中，当确定处理业务请求的核心网切片时，对核心网切片的状态进行判断，只有当核心网的状态处于激活状态时才使用该核心网切片处理业务请求，从而提高业务请求处理的准确性，有效地防止误操作。
可选的，在发送所述核心网切片的切片配置信息至所述终端步骤之后，还包括：
接收所述终端基于所述切片配置信息完成切片配置后发送的切片确认消息。
该实施方式中，网路侧在接收到切片配置信息后，基于该切片配置信息对核心网切片进行配置，该配置包括激活核心网切片和其他无线配置，并将 配置完的确认消息发送给终端，这样，终端可以通过确认消息来获知网络侧的情况。
可选的，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
该实施方式中，切片的标识可以是切片的名称、切片能够支持的业务类型等；切片支持的核心网能力参数可以为核心网传输的速度、传输的容量等；核心网功能模块如EMBB能力、MME能力等。
本公开实施例中，接收终端发送的业务请求消息，所述业务请求消息携带有第一业务指示信息；根据所述第一业务指示信息，选择支持所述业务请求的核心网切片，并发送所述核心网切片的切片配置信息至所述终端，所述核心网切片包括核心网能力参数和/或核心网功能模块；基于所述核心网切片处理所述业务请求。网络侧基于终端发送的业务请求消息对核心网切片进行选择，从而实现灵活的参与核心网切片的选择。
参见图6，图6是本公开实施例提供的一种业务请求处理装置的结构示意图，如图6所示，业务请求处理装置600包括：
第一选择模块601，用于终端发起业务请求时，从预先获得的核心网切片集合中选择支持所述业务请求的第一核心网切片，所述核心网切片集合包括多个核心网切片，所述核心网切片包括核心网能力参数和/或核心网功能模块；
第一发送模块602，用于发送所述第一核心网切片的切片配置信息和业务请求消息至网络侧。
可选的，如图7所示，所述业务请求处理装置600还包括：
第一接收模块603，用于接收所述网络侧发送的核心网切片集合，所述核心网切片集合是根据终端的签约信息和终端能力参数选择出的核心网切片的集合。
可选的，如图8所示，所述业务请求处理装置600还包括：
第二接收模块604，用于接收所述网络侧基于所述切片配置信息完成切片配置后发送的确认消息。
可选的，所述切片配置信息包括以下参数的一种或多种：切片的标识以 及切片支持的核心网能力参数和/或核心网功能模块。
需要说明的是，本实施例中上述业务请求处理装置600可以是本公开实施例中方法实施例中任意实施方式，且达到相同的有益效果，此处不再赘述。
参见图9，图9是本公开实施例提供的另一种业务请求处理装置900的结构示意图，如图9所示，业务请求处理装置900包括：
第三接收模块901，用于接收终端发送的业务请求消息和核心网切片的切片配置信息，所述核心网切片包括核心网能力参数和/或核心网功能模块；
第一处理模块902，用于基于所述核心网切片处理所述业务请求。
可选的，如图10所示，所述业务请求处理装置900还包括：
第一判断模块903，用于判断所述核心网切片是否处于激活状态；
第一激活模块904，用于若所述核心网切片未处于激活状态，激活所述核心网切片，并在激活之后，进入基于所述核心网切片处理所述业务请求的步骤；否则，直接进入基于所述核心网切片处理所述业务请求的步骤。
可选的，如图11所示，所述业务请求处理装置900还包括：
第二发送模块905，用于发送核心网切片集合至终端，所述核心网切片集合是根据终端的签约信息和终端能力参数选择出的核心网切片的集合。
可选的，如图12所示，所述业务请求处理装置900还包括：
第一配置模块906，用于基于所述切片配置信息进行切片配置，并在完成切片配置后发送确认消息至所述终端。
可选的，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
需要说明的是，本实施例中上述业务请求处理装置900可以是本公开实施例中方法实施例中任意实施方式，且达到相同的有益效果，此处不再赘述。
参见图13，图13是本公开实施例提供的另一种业务请求处理装置1300的结构示意图，如图13所示，业务请求处理装置1300包括：
第三发送模块1301，用于发送业务请求消息至网络侧，所述业务请求消息携带有第一业务指示信息；
第四接收模块1302，用于接收所述网络侧发送的基于所述第一业务请求信息选择的支持所述业务请求信息的核心网切片的切片配置信息，所述核心 网切片包括核心网能力参数和/或核心网功能模块。
可选的，如图14所示，所述业务请求处理装置1300还包括：
第二配置模块1303，用于基于所述切片配置信息进行切片配置，并在完成切片配置后发送确认消息至所述网络侧。
可选的，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
需要说明的是，本实施例中上述业务请求处理装置1300可以是本公开实施例中方法实施例中任意实施方式，且达到相同的有益效果，此处不再赘述。
参见图15，图15是本公开实施例提供的另一种业务请求处理装置1500的结构示意图，如图15所示，业务请求处理装置1500包括：
第五接收模块1501，用于接收终端发送的业务请求消息，所述业务请求消息携带有第一业务指示信息；
第二选择模块1502，用于根据所述第一业务指示信息，选择支持所述业务请求的核心网切片，并发送所述核心网切片的切片配置信息至所述终端，所述核心网切片包括核心网能力参数和/或核心网功能模块；
第二处理模块1503，用于基于所述核心网切片处理所述业务请求。
可选的，如图16所示，所述业务请求处理装置1500还包括：
第二判断模块1504，用于判断所述核心网切片是否处于激活状态；
第二激活模块1505，用于若所述核心网切片未处于激活状态，激活所述核心网切片，并在激活之后，进入基于所述核心网切片传输所述业务请求的步骤；否则，直接进入基于所述核心网切片传输所述业务请求的步骤。
可选的，如图17所示，所述业务请求处理装置还包括：
第六接收模块1506，用于接收所述终端基于所述切片配置信息完成切片配置后发送的切片确认消息。
可选的，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
需要说明的是，本实施例中上述业务请求处理装置1500可以是本公开实施例中方法实施例中任意实施方式，且达到相同的有益效果，此处不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露方法和装置，可 以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理包括，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元，可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述收发方法的部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述是本公开的优选实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本公开所述原理的前提下，还可以作出若干改进和润饰，这些改进和润饰也应视为本公开的保护范围。

Claims (36)

  1. 一种业务请求处理方法，应用于终端，包括：
    终端发起业务请求时，从预先获得的核心网切片集合中选择支持所述业务请求的第一核心网切片，所述核心网切片集合包括多个核心网切片，所述核心网切片包括核心网能力参数和/或核心网功能模块；
    发送所述第一核心网切片的切片配置信息和业务请求消息至网络侧。
  2. 根据权利要求1所述方法，其中，在所述终端发起业务请求时，从预先获得的核心网切片集合中选择支持所述业务请求的第一核心网切片的步骤之前，还包括：
    接收所述网络侧发送的核心网切片集合，所述核心网切片集合是根据终端的签约信息和终端能力参数选择出的核心网切片的集合。
  3. 根据权利要求1或者2所述方法，其中，在所述发送所述业务请求消息给网络侧的步骤之后，还包括：
    接收所述网络侧基于所述切片配置信息完成切片配置后发送的确认消息。
  4. 根据权利要求3所述方法，其中，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
  5. 一种业务请求处理方法，应用于网络侧，包括：
    接收终端发送的业务请求消息和核心网切片的切片配置信息，所述核心网切片包括核心网能力参数和/或核心网功能模块；
    基于所述核心网切片处理所述业务请求。
  6. 根据权利要求5所述方法，其中，在所述基于所述核心网切片处理所述业务请求的步骤之前，还包括：
    判断所述核心网切片是否处于激活状态；
    若所述核心网切片未处于激活状态，激活所述核心网切片，并在激活之后，进入基于所述核心网切片处理所述业务请求的步骤；否则，直接进入基于所述核心网切片处理所述业务请求的步骤。
  7. 根据权利要求5或者6所述方法，其中，在所述接收终端发送的业务 请求消息和核心网切片的切片配置信息的步骤之前，还包括：
    发送核心网切片集合至终端，所述核心网切片集合是根据终端的签约信息和终端能力参数选择出的核心网切片的集合。
  8. 根据权利要求7所述方法，其中，在所述基于所述核心网切片处理所述业务请求的步骤之后，还包括：
    基于所述切片配置信息进行切片配置，并在完成切片配置后发送确认消息至所述终端。
  9. 根据权利要求8所述方法，其中，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
  10. 一种业务请求处理方法，应用于终端，包括：
    发送业务请求消息至网络侧，所述业务请求消息携带有第一业务指示信息；
    接收所述网络侧发送的基于所述第一业务请求信息选择的支持所述业务请求信息的核心网切片的切片配置信息，所述核心网切片包括核心网能力参数和/或核心网功能模块。
  11. 根据权利要求10所述方法，其中，在所述接收所述网络侧发送的基于所述第一业务请求信息选择的支持所述业务请求信息的核心网切片的切片配置信息的步骤之后，还包括：
    基于所述切片配置信息进行切片配置，并在完成切片配置后发送确认消息至所述网络侧。
  12. 根据权利要求11所述方法，其中，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
  13. 一种业务请求处理方法，应用于网络侧，，包括：
    接收终端发送的业务请求消息，所述业务请求消息携带有第一业务指示信息；
    根据所述第一业务指示信息，选择支持所述业务请求的核心网切片，并发送所述核心网切片的切片配置信息至所述终端，所述核心网切片包括核心 网能力参数和/或核心网功能模块；
    基于所述核心网切片处理所述业务请求。
  14. 根据权利要求13所述方法，其中，在所述基于所述核心网切片传输所述业务请求的步骤之前，还包括：
    判断所述核心网切片是否处于激活状态；
    若所述核心网切片未处于激活状态，激活所述核心网切片，并在激活之后，进入基于所述核心网切片传输所述业务请求的步骤；否则，直接进入基于所述核心网切片传输所述业务请求的步骤。
  15. 根据权利要求13或者14所述方法，其中，在发送所述核心网切片的切片配置信息至所述终端步骤之后，还包括：
    接收所述终端基于所述切片配置信息完成切片配置后发送的切片确认消息。
  16. 根据权利要求15所述方法，其中，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
  17. 一种业务请求处理装置，包括：
    第一选择模块，用于终端发起业务请求时，从预先获得的核心网切片集合中选择支持所述业务请求的第一核心网切片，所述核心网切片集合包括多个核心网切片，所述核心网切片包括核心网能力参数和/或核心网功能模块；
    第一发送模块，用于发送所述第一核心网切片的切片配置信息和业务请求消息至网络侧。
  18. 根据权利要求17所述的装置，其中，所述装置还包括：
    第一接收模块，用于接收所述网络侧发送的核心网切片集合，所述核心网切片集合是根据终端的签约信息和终端能力参数选择出的核心网切片的集合。
  19. 根据权利要求17或者18所述的装置，其中，所述装置还包括：
    第二接收模块，用于接收所述网络侧基于所述切片配置信息完成切片配置后发送的确认消息。
  20. 根据权利要求19所述的装置，其中，所述切片配置信息包括以下参 数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
  21. 一种业务请求处理装置，包括：
    第三接收模块，用于接收终端发送的业务请求消息和核心网切片的切片配置信息，所述核心网切片包括核心网能力参数和/或核心网功能模块；
    第一处理模块，用于基于所述核心网切片处理所述业务请求。
  22. 根据权利要求21所述的装置，其中，所述装置还包括：
    第一判断模块，用于判断所述核心网切片是否处于激活状态；
    第一激活模块，用于若所述核心网切片未处于激活状态，激活所述核心网切片，并在激活之后，进入基于所述核心网切片处理所述业务请求的步骤；否则，直接进入基于所述核心网切片处理所述业务请求的步骤。
  23. 根据权利要求21或者22所述的装置，其中，所述装置还包括：
    第二发送模块，用于发送核心网切片集合至终端，所述核心网切片集合是根据终端的签约信息和终端能力参数选择出的核心网切片的集合。
  24. 根据权利要求23所述的装置，其中，所述装置还包括：
    第一配置模块，用于基于所述切片配置信息进行切片配置，并在完成切片配置后发送确认消息至所述终端。
  25. 根据权利要求24所述的装置，其中，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
  26. 一种业务请求处理装置，包括：
    第三发送模块，用于发送业务请求消息至网络侧，所述业务请求消息携带有第一业务指示信息；
    第四接收模块，用于接收所述网络侧发送的基于所述第一业务请求信息选择的支持所述业务请求信息的核心网切片的切片配置信息，所述核心网切片包括核心网能力参数和/或核心网功能模块。
  27. 根据权利要求26所述的装置，其中，所述装置还包括：
    第二配置模块，用于基于所述切片配置信息进行切片配置，并在完成切片配置后发送确认消息至所述网络侧。
  28. 根据权利要求27所述的装置，其中，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
  29. 一种业务请求处理装置，，包括：
    第五接收模块，用于接收终端发送的业务请求消息，所述业务请求消息携带有第一业务指示信息；
    第二选择模块，用于根据所述第一业务指示信息，选择支持所述业务请求的核心网切片，并发送所述核心网切片的切片配置信息至所述终端，所述核心网切片包括核心网能力参数和/或核心网功能模块；
    第二处理模块，用于基于所述核心网切片处理所述业务请求。
  30. 根据权利要求29所述的装置，其中，所述装置还包括：
    第二判断模块，用于判断所述核心网切片是否处于激活状态；
    第二激活模块，用于若所述核心网切片未处于激活状态，激活所述核心网切片，并在激活之后，进入基于所述核心网切片传输所述业务请求的步骤；否则，直接进入基于所述核心网切片传输所述业务请求的步骤。
  31. 根据权利要求29或者30所述的装置，所述装置还包括：
    第六接收模块，用于接收所述终端基于所述切片配置信息完成切片配置后发送的切片确认消息。
  32. 根据权利要求31所述的装置，其中，所述切片配置信息包括以下参数的一种或多种：切片的标识以及切片支持的核心网能力参数和/或核心网功能模块。
  33. 一种业务请求处理装置，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至4中任一项所述的业务请求处理方法中的步骤。
  34. 一种业务请求处理装置，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求5至9中任一项所述的业务请求处理方法中的步骤。
  35. 一种业务请求处理装置，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器 执行时实现如权利要求10至12中任一项所述的业务请求处理方法中的步骤。
  36. 一种业务请求处理装置，包括：处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求13至16中任一项所述的业务请求处理方法中的步骤。
PCT/CN2018/070083 2017-01-06 2018-01-03 一种业务请求处理方法及装置 WO2018127046A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/476,135 US20190357132A1 (en) 2017-01-06 2018-01-03 Method and device for processing service request
EP18736393.2A EP3567935B1 (en) 2017-01-06 2018-01-03 Service request processing method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710009902.5 2017-01-06
CN201710009902.5A CN108282846B (zh) 2017-01-06 2017-01-06 一种业务请求处理方法及装置

Publications (1)

Publication Number Publication Date
WO2018127046A1 true WO2018127046A1 (zh) 2018-07-12

Family

ID=62789125

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/070083 WO2018127046A1 (zh) 2017-01-06 2018-01-03 一种业务请求处理方法及装置

Country Status (4)

Country Link
US (1) US20190357132A1 (zh)
EP (1) EP3567935B1 (zh)
CN (1) CN108282846B (zh)
WO (1) WO2018127046A1 (zh)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018195877A1 (zh) 2017-04-27 2018-11-01 华为技术有限公司 通信方法、装置和系统
CN109862579B (zh) * 2017-11-30 2022-05-17 华为技术有限公司 通信方法和通信装置
CN114554571B (zh) 2018-11-15 2024-06-25 北京小米移动软件有限公司 网络切片的使用方法及装置
US10979892B2 (en) * 2019-07-30 2021-04-13 At&T Intellectual Property I, L.P. Efficient device capabilities enquiry for 5G or other next generations wireless network
CN113133087B (zh) * 2019-12-30 2023-09-05 中国移动通信集团浙江有限公司 针对终端设备配置网络切片的方法及装置
CN113596962A (zh) * 2020-04-30 2021-11-02 维沃移动通信有限公司 信息处理方法、信息处理装置及终端设备
CN114095365B (zh) * 2020-08-24 2023-07-21 中移物联网有限公司 基于5g消息的物联网业务的处理方法及装置
CN114258010A (zh) * 2020-09-25 2022-03-29 中国移动通信有限公司研究院 信息处理方法、装置、设备及可读存储介质
WO2023065092A1 (zh) * 2021-10-18 2023-04-27 Oppo广东移动通信有限公司 Rrc建立原因值的确定方法、装置、设备及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106060900A (zh) * 2016-05-13 2016-10-26 宇龙计算机通信科技(深圳)有限公司 网络切片的接入控制方法及装置、终端化小区和sdn控制器
WO2016192636A1 (en) * 2015-06-01 2016-12-08 Huawei Technologies Co., Ltd. System and method for virtualized functions in control and data planes

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016192636A1 (en) * 2015-06-01 2016-12-08 Huawei Technologies Co., Ltd. System and method for virtualized functions in control and data planes
CN106060900A (zh) * 2016-05-13 2016-10-26 宇龙计算机通信科技(深圳)有限公司 网络切片的接入控制方法及装置、终端化小区和sdn控制器

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CHINA MOBILE: "Discussion and Interim agreement update about network slicing, S 2-166422", 3GPP SA WG 2 MEETING #118, 18 November 2016 (2016-11-18), XP051199405 *
HUAWEI ET AL.: "Update of Solution #1 for Key issue #1, S 2-161503", 3GPP SA WG2 MEETING #114, 15 April 2016 (2016-04-15), XP051086496 *
See also references of EP3567935A4 *

Also Published As

Publication number Publication date
CN108282846B (zh) 2020-07-03
EP3567935A4 (en) 2020-08-26
US20190357132A1 (en) 2019-11-21
CN108282846A (zh) 2018-07-13
EP3567935A1 (en) 2019-11-13
EP3567935B1 (en) 2023-02-01

Similar Documents

Publication Publication Date Title
WO2018127046A1 (zh) 一种业务请求处理方法及装置
EP3836577B1 (en) Session management method and device for user groups
WO2018045877A1 (zh) 网络切片控制方法及相关设备
WO2018153346A1 (zh) 一种网络切片的选择方法及装置
US11930423B2 (en) Communication method and communications apparatus
WO2020135850A1 (zh) 通信方法和装置
WO2021232910A1 (zh) 一种网络接入方法及通信装置
JP7389225B2 (ja) セキュリティ保護モードを決定するための方法および装置
WO2017167027A1 (zh) 一种网络接入方法、相关设备和系统
CN107734592B (zh) 一种核心网选择方法、接入网实体、ue及系统
WO2021047454A1 (zh) 位置信息获取、位置服务配置方法和通信设备
US11516645B2 (en) Cross-agency communication through an ad-hoc network slice
KR20220158018A (ko) 접속 수립 방법, 통신 장치, 및 시스템
WO2016112674A1 (zh) 一种实现通信的方法、终端、系统及计算机存储介质
WO2019223478A1 (zh) 信息处理方法及装置、网元及存储介质
WO2015103780A1 (zh) 一种承载电路语音业务的方法及装置
US10999729B2 (en) Discovery method and device
US20160088076A1 (en) Method, device and system for obtaining mobile network data resources
WO2022105785A1 (zh) 无线连接建立方法及通信装置
US20220329986A1 (en) Multicast service implementation method and apparatus, and communications device
CN117882422A (zh) Gnb故障检测的优化与回退机制的快速激活
CN114650575A (zh) Pdu会话选择方法、装置、网络功能及存储介质
WO2018112931A1 (zh) 一种信令重定向方法及相关设备
WO2016029820A1 (zh) 一种业务处理方法及系统、设备

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: 18736393

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018736393

Country of ref document: EP

Effective date: 20190806