WO2018184511A1 - 通信方法及通信设备 - Google Patents

通信方法及通信设备 Download PDF

Info

Publication number
WO2018184511A1
WO2018184511A1 PCT/CN2018/081537 CN2018081537W WO2018184511A1 WO 2018184511 A1 WO2018184511 A1 WO 2018184511A1 CN 2018081537 W CN2018081537 W CN 2018081537W WO 2018184511 A1 WO2018184511 A1 WO 2018184511A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
terminal
request
information
network slice
Prior art date
Application number
PCT/CN2018/081537
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 EP18781087.4A priority Critical patent/EP3595358A4/en
Publication of WO2018184511A1 publication Critical patent/WO2018184511A1/zh
Priority to US16/592,598 priority patent/US11096097B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0077—Transmission or use of information for re-establishing the radio link of access information of target access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0058—Transmission of hand-off measurement information, e.g. measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00835—Determination of neighbour cell lists
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/17—Selecting a data network PoA [Point of Attachment]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/302—Reselection being triggered by specific parameters by measured or perceived connection quality data due to low signal strength

Definitions

  • the present application relates to the field of wireless communications, and in particular, to a communication method and a communication device.
  • 5G fifth generation wireless communication technology
  • 5G will support diverse application needs, including support for higher speed experiences and greater bandwidth access, lower latency and highly reliable information interaction, and the connection of larger and lower cost machine-like communication devices. Entry and management, etc.
  • 5G will support a variety of vertical industry applications for vehicle networking, emergency communications, and industrial Internet. Faced with these performance requirements and application scenarios of 5G, 5G networks need to be closer to the specific needs of users, and their customization capabilities need to be further improved.
  • a network slice is a combination of a plurality of network functions (NFs) and corresponding resources for implementing a communication service, including a Core Network (CN) portion and a Radio Access Network (RAN) portion. / or terminal part.
  • a 5G network consists of various network slices that satisfy different connection capabilities.
  • a network slice is a logical network that satisfies the communication service requirements of one type or one use case. Different network slices provide differentiated services for different users and different services.
  • One RAN can support multiple network slices, such as one RAN can support multiple vertical industry applications.
  • a terminal can also support multiple network slices to support the operation of multiple network sliced services.
  • the network slice For the network functions constituting the network slice, it is divided into a public network function and a dedicated network function, wherein the public network function is a network function shared by a plurality of network slices, and the dedicated network function is a network function dedicated to each network slice.
  • the public network function is a network function shared by a plurality of network slices
  • the dedicated network function is a network function dedicated to each network slice.
  • the embodiment of the present application provides a communication method, so as to reduce the risk that a deactivated terminal fails to connect in a mobile state.
  • the embodiment of the present application provides a communication method, including:
  • the first base station When the first base station does not support the network slice to which the terminal belongs, the first base station sends a handover request to the second base station, where the second base station supports the network slice to which the terminal belongs;
  • the first base station receives the handover request reply from the second base station, and sends a first request reply to the terminal, where the first request reply includes configuration information of the second base station.
  • the deactivated terminal When the deactivated terminal is in the process of moving, if the first base station moved to does not support the network slice to which the terminal belongs, the first base station can perform cell redirection for the terminal, and the terminal is redirected to support the network slice to which the terminal belongs. Base station, thus avoiding the risk of connection failure.
  • the first request includes a cell list that allows the terminal to access, and the first base station sends a handover request to the second base station, including: selecting a second base station according to the cell list, and selecting The second base station sends a handover request. Therefore, the terminal can carry the cell list that allows the terminal to access in the first request, thereby improving the efficiency of subsequent access.
  • the first request further includes at least one of the following messages:
  • Network slice indication information configured to notify the first base station of network slice information to which the terminal belongs
  • the reason information is used to notify the first base station of the purpose of sending the first request.
  • the terminal can report its network slice indication information, cause information, and the like to the first base station when the first request is sent, so as to facilitate the first base station decision.
  • the first base station after receiving the first request sent by the terminal, the first base station further includes:
  • the first base station sends a second request to the third base station, where the third base station is a base station that the terminal is camped on, and the second request is used to request context information of the terminal in the third base station, the context
  • the information is configuration information when the terminal resides in the third base station;
  • the first base station receives context information of the third base station.
  • the first base station can acquire context information from the base station where the terminal previously camped for decision making.
  • the above context information includes at least one of the following messages:
  • Flow context information where the flow context information is information of the flow that the terminal has allocated, including at least one of flow ID information, flow priority information, QoS information, and network slice information corresponding to the flow;
  • Bearer information where the bearer information is information about the bearer that has been allocated by the terminal, and includes at least one of bearer ID information, QoS information, and network slice information corresponding to the bearer;
  • the sending, by the first base station, the handover request to the second base station includes:
  • the first base station sends a measurement request to the terminal, where the measurement request is used to obtain a cell list that allows the terminal to access;
  • the first base station sends a handover request to the selected second base station.
  • the embodiment of the present application provides another communication method, including:
  • the first base station When the first base station does not support the network slice to which the terminal belongs, the first base station sends a path transfer request to the common control plane network function CCNF to transfer the path to the network slice supporting the terminal;
  • the first base station receives the path transfer request reply from the CCNF, and sends a first request reply to the terminal, where the first request reply includes configuration information of the CCNF.
  • the deactivated terminal When the deactivated terminal is in the process of moving, if the first base station moved to does not support the network slice to which the terminal belongs, the first base station can perform path redirection for the terminal, and the terminal is redirected to the network slice supporting the terminal, thereby Avoid the risk of connection failure.
  • the embodiment of the present application proposes another communication device, including:
  • the terminal sends a first request to the first base station, where the first request is used to request an RRC connection from the first base station;
  • the terminal receives a first request reply from the first base station, where the first request reply includes configuration information of the second base station, and the second base station is when the first base station does not support the network slice to which the terminal belongs. And determining, by the first base station, a base station that supports a network slice to which the terminal belongs, and the terminal returns to the second base station according to the first request.
  • the method further includes: receiving, by the terminal, a measurement request sent by the first base station, where the measurement request is used to obtain a cell list that allows the terminal to access;
  • the embodiment of the present application provides a communication device, which has the function of realizing the behavior of the first base station in the actual method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the base station includes a processor and a transmitter configured to support the base station to perform the corresponding functions in the above methods.
  • the transceiver is configured to support communication between the base station and the terminal, and send information or instructions involved in the foregoing method to the terminal.
  • the base station can also include a memory for coupling with the processor that stores the necessary program instructions and data for the base station.
  • the embodiment of the present application provides a terminal, where the terminal has a function of implementing terminal behavior in the design of the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the modules can be software and/or hardware.
  • the structure of the terminal includes a transceiver and a processor, and the receiver is configured to support the terminal to receive data or signaling generated by the base station to configure various instructions for the base station and send corresponding instructions.
  • the processor supports the terminal to perform the function of the terminal in the above communication method.
  • the terminal can also include a memory for coupling with the processor that stores the necessary program instructions and data for the base station.
  • a computer program product comprising: computer program code, when the computer program code is processed by a communication unit, processing unit or transceiver of a communication device (eg, a network device or a network management device) When the device is running, the communication device is caused to perform the method in the above implementation manner.
  • a communication unit e.g., a network device or a network management device
  • the communication device is caused to perform the method in the above implementation manner.
  • a computer readable storage medium storing a program that causes a user device to perform the method of the above implementation.
  • the solution provided by the present application can perform a redirection operation for a terminal when the terminal moves to a base station that does not support the network slice to which it belongs, thereby avoiding the risk of connection failure and improving communication efficiency.
  • FIG. 1 is a schematic diagram of a network slicing architecture provided by an embodiment of the present application.
  • FIGS. 2a and 2b are simplified schematic diagrams of an application scenario provided by an embodiment of the present application.
  • FIG. 3 is a signaling interaction diagram of a terminal mobility method according to an embodiment of the present application.
  • FIG. 4 is a signaling interaction diagram of a communication method provided by an embodiment of the present application.
  • FIG. 5 is a signaling interaction diagram of still another communication method provided by an embodiment of the present application.
  • FIG. 6 is a signaling interaction diagram of still another communication method provided by an embodiment of the present application.
  • FIG. 7 is a signaling interaction diagram of still another communication method provided by an embodiment of the present application.
  • FIG. 8 is a signaling interaction diagram of still another communication method provided by an embodiment of the present application.
  • FIG. 9 is a signaling interaction diagram of still another communication method provided by an embodiment of the present application.
  • FIG. 10 is a signaling interaction diagram of still another communication method provided by an embodiment of the present application.
  • FIG. 11 is a signaling interaction diagram of still another communication method according to an embodiment of the present application.
  • FIG. 12 is a signaling interaction diagram of still another communication method according to an embodiment of the present application.
  • FIG. 13 is a signaling interaction diagram of still another communication method according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a communication device according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic block diagram of a communication device according to an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.
  • FIG. 17 is a schematic block diagram of a terminal provided by an embodiment of the present application.
  • system and “network” are used interchangeably herein.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the character "/" in this article generally indicates that the contextual object is an "or" relationship.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • UMTS Universal Mobile Telecommunication System
  • next-generation communication system such as New Radio (NR) system, evolved LTE (eLTE), etc.
  • NR New Radio
  • eLTE evolved LTE
  • FIG. 1 shows a communication system 100 provided by an embodiment of the present application.
  • the terminal 110 communicates with the network device through the wireless link 120.
  • the network device includes a RAN device and a CN device, where the RAN device may be an access point (ACCESS POINT; AP for short) in the WLAN, and a base station in the GSM or CDMA (Base Transceiver) Station (BTS), which may also be a base station (NodeB; NB for short) in WCDMA, or an evolved base station (Evolved Node B; eNB or eNodeB) in LTE, or a relay station or an access point, or an in-vehicle device.
  • ACCESS POINT Access Point
  • AP Access Point
  • BTS Base Transceiver
  • NodeB base station
  • NB evolved base station
  • LTE Long Term Evolution Node B
  • the wearable device, the network device in the future 5G network, or the network device in the future evolved PLMN network may be a 5G base station (for example, Next-Generation Node B (gNB) or Next-Generation Radio (NR). ), Transmission and Reception Point (TRP), Centralized Unit (CU), Distributed Unit (DU), etc.
  • the CN device may be a Mobile Management Entity (MME) in LTE, a gateway (Gateway), or a Control Plane (CP) network function (NF) in a 5G network.
  • MME Mobile Management Entity
  • CP Control Plane
  • NF Network function
  • UP User Plane
  • the CCNF may include, but is not limited to, at least one of an Access and Mobility Management Function (AMF), a Session Management NF (SMF), and the like.
  • the RAN supports multiple network slices in the CN, such as a first network slice 101, a second network slice 102, and a third network slice 103.
  • multiple network slices have both common CP NFs and their own dedicated CP NFs; on the UP plane of the CN, each network slice has dedicated UP NFs.
  • the third network slice also has a common second CCNFs and their dedicated CPs. NFs and UP NFs.
  • the second CCNFs of the third network slice may be CP NFs common to other network slices than the first network slice and the second network slice.
  • the second AMF of the network slice corresponding to the CCNFs is used to manage the access and mobility of the third network slice.
  • the network slice also has the following characteristics: 1. On the core network (CN) side, different network slices can have shared CCNF. 2. On the CN side, different network slices can have specific control plane functions and data plane functions. This network slice specific control plane function and data plane function are called network slice instances. 3. On the Radio Access Network (RAN) side, one RAN device can support the same or different network slices. Illustratively, there are two cases in which different network slices are supported. One case is that all network slices share network resources, support different slices by radio resource management (RRM), and the other is slice of each network. Isolate on resources. 4.
  • RRM radio resource management
  • one user can access multiple network slices, but usually access one CCNF, that is, the user can access multiple NSIs, but access one CCNF, and the user establishes a session on which NSI. Determined by CCNF. Since there are multiple CCNFs on the CN side, in some cases, the RAN device selects CCNF for the user according to the Network Slice Selection Assistance Information (NSSAI). If the selected CCNF is inappropriate, the CCNF will be the user. Redirect.
  • NSSAI Network Slice Selection Assistance Information
  • the network device provides a service for the cell, and the terminal communicates with the network device by using a transmission resource (for example, a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a network device (for example, a cell corresponding to a base station, the cell may belong to a macro base station, a hyper cell, or may belong to a base station corresponding to a small cell, where the small cell may include: a metro cell, a micro cell ( Micro cell), Pico cell, Femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • a transmission resource for example, a frequency domain resource, or a spectrum resource
  • NS1, NS3, and NS4 are supported in the coverage of RAN#A.
  • NS1, NS2, and NS3 are supported in the coverage of RAN#B, and NS2, NS3, and NS4 are supported in the coverage of RAN#C.
  • the coverage of different base stations is basically orthogonal, and the number of intersections is small, and there are many scenarios in which multiple campuses are deployed in the same frequency.
  • FIG. 2b NS1, NS3, and NS4 are supported in the coverage of different base stations within the coverage of RAN#A, and NS2 is supported in the coverage of RAN#B.
  • the coverage of different base stations overlaps, and there are many intersections.
  • the terminal 110 may also be referred to as a user, a user equipment (User Equipment; UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, and a wireless communication.
  • UE User Equipment
  • Device user agent, or user device.
  • the terminal may be a site in a Wireless Local Area Networks (WLAN) (STATION; referred to as ST), which may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, or a wireless local loop ( Wireless Local Loop; referred to as WLL) station, Personal Digital Assistant (PDA) device, handheld device with wireless communication function, relay device, computing device or other processing device connected to wireless modem, vehicle device, A wearable device and a next-generation communication system, for example, a terminal in a fifth-generation (Fifth-Generation; 5G) network or a terminal in a future evolutionary public land mobile network (PLMN) network.
  • WLAN Wireless Local Area Networks
  • ST Wireless Local Area Networks
  • ST Wireless Local Area Networks
  • PDA Personal Digital Assistant
  • ST Wireless Local Loop
  • 5G fifth-generation
  • PLMN future evolutionary public land mobile network
  • the terminal may also be a wearable device.
  • a wearable device which can also be called a wearable smart device, is a general term for applying wearable technology to intelligently design and wear wearable devices such as glasses, gloves, watches, clothing, and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are more than just a hardware device, but they also implement powerful functions through software support, data interaction, and cloud interaction.
  • Generalized wearable smart devices include full-featured, large-size, non-reliable smartphones for full or partial functions, such as smart watches or smart glasses, and focus on only one type of application, and need to work with other devices such as smartphones. Use, such as various smart bracelets for smart signs monitoring, smart jewelry, etc.
  • RNA includes one cell or multiple cells. If multiple cells are included, the multiple cells may belong to one gNB or may belong to multiple gNBs.
  • the network may not be notified, but when the terminal moves out of the RNA, the network needs to be notified.
  • the camping cell means that the terminal changes from the RRC connected state to the Inactive state in the camping cell (deactivated state). )
  • moving to a new serving cell triggers the RAN paging area update process, thereby connecting the interface of the terminal (eg NG2 interface) and the terminal
  • the context information eg, context information
  • the target base station supports the user network slice to which the user belongs, the user can subsequently access the target cell, and the target base station continues to serve. If the target base station does not support the user network slice to which the user currently belongs, there is a risk that the user accesses the target base station.
  • the target base station does not support the user network slice to which the user belongs.
  • the first case is not supported, the target base station does not support the CCNF of the network slice to which the user belongs, and the second unsupported situation is the target.
  • the base station supports the CCNF of the network slice to which the user belongs but does not support the dedicated network function of the network slice (hereinafter collectively referred to as NSI).
  • the network slice corresponding to NS1 is CCNF1+NSI1
  • the network slice corresponding to NS2 is CCNF1+NSI2
  • the network slice corresponding to NS3 is CCNF1+NSI3
  • the network slice corresponding to NS4 is CCNF2+NSI4.
  • the network slice to which the user belongs is NS1 as an example. It is assumed that the network slice supported by the target base station A is NS4, and CCNF1 in the network slice NS1 to which the user belongs is not supported. In this case, the target base station A belongs to the first type that is not supported. It is assumed that the network slice supported by the target base station A is NS2, which supports CCNF1 in the network slice NS1 to which the user belongs, but does not support NSI2. In this case, the target base station A belongs to the second unsupported case.
  • FIG. 13 is a schematic flowchart of a communication method according to an embodiment of the present application, showing detailed communication steps or operations of the method, but the steps or operations are only examples, and the embodiment of the present application may also Other operations or variations of the various operations in FIGS. 4 to 13 are performed. Further, the respective steps in FIGS. 4 to 13 may be performed in a different order from that presented in FIGS. 4 to 13, respectively, and it is possible that not all operations in FIGS. 4 to 13 are to be performed.
  • the communication methods disclosed in the various embodiments of the present application can be applied to different application scenarios.
  • the target base station can perform redirection, thereby avoiding the risk that the terminal cannot access the network.
  • the network slice indication information is used to notify the RAN device (for example, the first base station) of the network slice to which the terminal currently belongs.
  • the network slice indication information may be at least one of the following information: a network slice selection assistance information (NSSAI) allocated by the communication system for the terminal, and a single-network slice selection assistance information (S) -NSSAI), network slice identifier (Slice ID), temporary identifier (Temporary ID).
  • the S-NSSAI may be any one of a Slice/Service Type (SST) and a Slice Differentiator (SD).
  • the temporary identification information is allocated by the AMF to a terminal that has been registered on the CN side, and the temporary identifier can uniquely point to an AMF.
  • the context information is used to convey the configuration information of sessions, flows, or bearers between different network elements.
  • the message types included in different processes may be different.
  • the context information may include one or more of the following messages:
  • Flow context information which may include at least one of a stream ID (or stream ID information), a stream priority, QoS (Quality of Service) information, and network slice information corresponding to the stream.
  • the data radio bearer (DRB) information may include at least one of a bearer ID (or bearer ID information), QoS information, and network slice information corresponding to the bearer.
  • Network slice indication information corresponding to the current session of the terminal including at least one of NSSAI, Slice ID, Temp ID, and S-NSSAI.
  • a mapping policy message which is used to indicate a network slice to which the network slice to which the terminal currently belongs can also be remapped.
  • the terminal currently communicates with the network slice 1 and the network slice 2, and the mapping policy message may include information of the network slice 3 and the network slice 4, indicating that the network slice 1 can also be remapped to the network slice 3 or the network slice 4.
  • the first base station when the first base station does not support the network slice 1, the first base station can also map the network slice 1 to its supported network slice 3 or network slice 4 for service.
  • the mapping policy information provides a network slice to which the first-level station can remap when the first base station does not support the network slice to which the terminal belongs.
  • FIG. 4 is a schematic flowchart diagram of a communication method according to an embodiment of the present application, and the communication method is applicable to the communication system 100 shown in FIG. 1.
  • the application scenario of the communication method shown in FIG. 4 may be: when the cell to which the terminal moves does not support the network slice to which the terminal belongs, the RRC connection is established by using cell redirection.
  • the first base station mentioned in this embodiment is a target base station to which the terminal moves, the second base station is a resident base station where the terminal previously camped, and the third base station is redirected when the first base station does not support the network slice to which the terminal belongs.
  • Base station The communication method includes the following steps:
  • the terminal sends a first request to the first base station, where the first request is used to request an RRC connection from the first base station.
  • the first base station receives the first request, and determines whether the network slice to which the terminal belongs is supported.
  • the first base station acquires the information of the network slice to which the terminal belongs, and the manner of acquiring the information of the network slice to which the terminal belongs, for example, according to parameters carried in the first request or other manners, which will be described in more detail below. .
  • the first base station When the first base station supports the network slice to which the terminal belongs, the first base station establishes an RRC connection with the terminal; when the first base station does not support the network slice to which the terminal belongs, step 303 is performed.
  • the first base station When the first base station does not support the network slice to which the terminal belongs, the first base station sends a handover (HO) request to the second base station, where the second base station supports the network slice to which the terminal belongs.
  • HO handover
  • the first base station may acquire a cell list that allows the terminal to access, to select a second base station that supports the network slice to which the terminal belongs.
  • the first base station obtains a cell list that allows the terminal to access according to the first request or other manner, which will be described in more detail below.
  • the handover request includes context information of the terminal, where the context information is configuration information when the terminal camps in the third base station, and the type of the message included in the context refers to the foregoing definition.
  • the second base station receives the handover request, and sends a handover request reply to the first base station.
  • the handover request reply may include context information of the second base station, including but not limited to the data radio bearer configuration of the second base station, and the mapping between the DRB configuration and the flow (Flow mapping) at least one.
  • the first base station receives the handover request reply, and sends a first request reply to the terminal, where the first request reply includes configuration information of the second base station.
  • the first request reply may be referred to as an RRC Connection Reconfig., including but not limited to context information of the second base station.
  • the terminal receives the first request reply, and performs corresponding session configuration according to the configuration information of the second base station included therein, so as to establish at least one default session on one network slice.
  • the terminal may store the received configuration information and then continue to be in the inactive state, and need to establish at least one default session on at least one network slice, so as to be able to access quickly when entering the active state subsequently; or the second base station may also be used.
  • the RRC configuration complete message is sent to the second base station, and after the RRC configuration is completed, the RRC connection state is entered.
  • the terminal may perform data transmission according to the configured RRC.
  • the terminal initiates an access request to the target base station and the target base station does not support the network slice to which the terminal currently belongs, the terminal avoids the risk of RRC connection failure by redirecting the terminal to other cells that can support the network slice to which the terminal belongs.
  • the first base station is a cell to which the terminal moves (corresponding to the aforementioned "target base station").
  • the first request may be referred to as a RRC Connection Resume Request (RRC Connection Resume Request) for establishing an RRC connection with the first base station.
  • RRC Connection Resume Request RRC Connection Resume Request
  • the first request may include one or more of the following messages:
  • Cell list information including a set of cells that the terminal can currently access.
  • Network slice indication information please refer to the description above.
  • the purpose of transmitting the first request is to transmit data.
  • Carrying the Cause message allows the RAN device to perform congestion control, for example, the RAN device sets the access priority of the transmission data to be higher than the priority of the transmission signaling, that is, when the network is congested, the RAN device preferentially agrees to the terminal that transmits the data. Access to the network.
  • the Cause information can also be used to indicate the type of data, so as to facilitate more accurate congestion control and improve network performance.
  • the data types may include, but are not limited to, Ultra-Reliable Low Latency Communications (URLLC) service data, enhanced mobile broadband communication (eMBB) service data, massive machine type communication (massive machine).
  • URLLC Ultra-Reliable Low Latency Communications
  • eMBB enhanced mobile broadband communication
  • massive machine type communication massive machine type communication
  • mMTC massive machine type communication
  • the first base station may acquire, according to the configured network slice indication information, a network slice to which the terminal currently belongs.
  • the first base station may further acquire the current current location of the terminal by using the following method.
  • the foregoing step 302 includes:
  • the first base station sends a second request to the third base station (corresponding to the base station where the foregoing terminal is camped) for requesting the context information of the terminal in the third base station.
  • This second request may be referred to as a retrieve context request.
  • the first base station may acquire the third base station according to the Resume ID.
  • the third base station receives the second request, and sends the context information to the first base station.
  • This context context information may also be referred to as a Retriveal Context response.
  • For the context information please refer to the foregoing definition.
  • NSSAI, Slice ID, Temp ID, and S-NSSAI are optional, but if the first request does not carry NSSAI, Slice ID, Temp ID, S-NSSAI In any case, at least one of the NSSAI, the Slice ID, the Temp ID, and the S-NSSAI needs to be included in the third base station transmitting the context information to the first base station.
  • the first base station receives the context information, so as to obtain the network slice and related configuration information that the user belongs to, to determine whether it can support the network slice to which the current user belongs.
  • the first base station may select, according to the cell list, a second base station that can support the network slice to which the user belongs.
  • step 303 includes:
  • the first base station sends a measurement request to the terminal, where the measurement request is used to obtain a cell list that the terminal can access.
  • the measurement request includes a measurement configuration and a list of cells that need to be measured.
  • a triggering event or the like is included in the measurement configuration.
  • the cell list to be measured may be a cell set supporting the network slice to which the terminal currently belongs.
  • the measurement request may further include a form indication of the measurement report, where the form indicates a form of the measurement report used to indicate the terminal, for example, the measurement report includes a list of all cells that the terminal is currently accessible, or the measurement report includes The signal quality of all cells in the cell list to be measured, the two exemplary measurement reports may exist separately or in two.
  • the terminal receives the measurement request, generates a measurement report and sends the response in response to the measurement request.
  • the measurement report generated by the terminal includes at least one of a list of all cells currently accessible by the terminal, and a signal quality of all cells in the cell list to be measured.
  • the first base station receives the measurement report, and selects a second base station that supports the user network slice according to the measurement report.
  • the communication method 400 is applied to the communication system 100 shown in FIG. 1.
  • the first base station corresponds to the cell to which the terminal moves
  • the second base station corresponds to the cell that the terminal needs to handover
  • the third base station corresponds to the cell where the terminal previously camped.
  • the communication method consists of the following steps:
  • the terminal sends a first request to the first base station, where the first request is used to request an RRC connection from the first base station. It should be noted that, because the application scenario is different, the description of the first request and the first request of step 301 in the embodiment shown in FIG. 4 is not repeated herein.
  • the first base station receives the first request, and sends a path switch request (Path Switch Request) to the CCNF when the first base station does not support the network slice to which the terminal belongs.
  • a path switch request Path Switch Request
  • the path transfer refers to the transfer of the session from the port of the terminal in the base station where the terminal originally camped to the port in the base station to which the mobile station is moved.
  • the first base station may acquire, according to the configured network slice indication information, the network slice to which the terminal belongs, to determine whether the first base station supports the terminal.
  • the network slice to which it belongs may be acquired, according to the configured network slice indication information, the network slice to which the terminal belongs, to determine whether the first base station supports the terminal. The network slice to which it belongs.
  • the first base station may further acquire the network slice to which the terminal belongs by referring to the manners of steps 3021 to 3023 shown in FIG. 5 .
  • the context information in this embodiment may further include:
  • the path transfer request includes at least one of a flow indication and a semi-accepted flow indication acceptable by the first base station.
  • the semi-accepted flow indication indicates that the first base station can meet its QoS requirements, but network slice remapping is required.
  • the path transfer request may further include at least one of the network slice indication information corresponding to the semi-accepted flow indication, that is, the network slice indication information that is remapped by the first base station according to the mapping policy information.
  • different NSIs represent different tenants, for example, NSI1 is a BMW tenant and NSI2 is a Mercedes tenant. For both tenants, the services they provide may be the same, that is, QoS, but the charges are different.
  • the first base station supports the BMW tenant, NSI1, but does not support the Mercedes-Benz tenant, NSI2. Then, when the terminal of the Mercedes tenant moves to the first base station, according to the mapping policy information described above, the target base station finds that the terminal of the NSI2 can be remapped to the NSI1 to continue the service.
  • the first base station before the path forwarding request is sent to the CCNF, if the first base station determines that the QoS of the at least one session of the terminal can be satisfied according to the first configuration message and can establish a bearer for the terminal, the first base station can establish a bearer for the terminal.
  • the CCNF receives the path transfer request, and sends a Path Switch Request ACK to the first base station.
  • the path transfer request reply includes one or more of the following information:
  • the network slice indication information here is network slice indication information that can be received, and is NSSAI reconfigured by CCNF according to the path transfer request, and may also be referred to as Accept NSSAI.
  • the network slice indication information may be referenced to the foregoing definition, compared to the configured network slice indication information optionally carried in the first request, where some or all of the S-NSSAI changes in the Accepted NSSAI, or are part of the Accept NSSAI
  • the SD information of the S-NSSAI changes. If the S-NSSAI only includes the NSI that the SST cannot specifically indicate, the SD information may further indicate the S-NSSAI, so that the S-NSSAI can indicate the specific NSI.
  • Context information is the flow context information reconfigured by CCNF, including one or more of the priority of the flow, the Aggregate maximum bit rate (AMBR) or the QCI information.
  • the flow context information in the path transfer request reply may be different with respect to the current flow context information of the terminal. For example, after the foregoing terminal is transferred from the NSI2 of the Mercedes-Benz to the NSI1 of the BMW in the core network, although the BMW NSI1 accepts the terminal, the priority in the flow context information is lowered compared to the existing terminal in the first base station.
  • the first base station receives the path transfer request reply, and sends a first request reply to the terminal.
  • the first base station performs configuration according to the information included in the path transfer request reply, where the configuration includes but is not limited to the DRB configuration, and the mapping relationship between the DRB and the flow. At this time, the first base station can support the network slice to which the terminal currently belongs.
  • the first request reply includes all or part of the information and/or DRB configuration in the path transfer request reply.
  • the first request reply may be an RRC recovery request or an RRC reconfiguration request, for the Inactive state or the Idle state of the terminal.
  • the first request reply includes at least one of network slice indication information, updated DRB configuration, and updated mapping relationship between the DRB and the flow.
  • the terminal receives the first request reply, and performs corresponding configuration according to the configuration information included therein.
  • the terminal may store the configuration information so as to be able to access quickly when the user enters the active state, or may complete the synchronization process with the first base station.
  • the terminal configures the DRB according to the information included in the first request reply.
  • the terminal when the first request is returned to the RRC reconfiguration request, the terminal further needs to send an RRC reconfiguration complete message and/or a Flow and DRB mapping relationship to the first base station.
  • the first base station when it is determined that the first base station can support the CCNF of the current network slice of the terminal but does not support the NSI, the first base station may also request the cell to be relocated to the CCNF, such as As shown in FIG. 7, the communication method can also be:
  • the terminal sends a first request to the first base station, where the first request is used to request an RRC connection to the first base station, and the description of step 401 is omitted.
  • the first base station receives the first request, and determines whether the network slice to which the terminal belongs is supported. When the first base station supports the CCNF of the current network slice of the terminal but does not support the NSI, step 503 is performed. For details, refer to the description of step 402 shown in FIG. 6 , and details are not described herein again.
  • the first base station sends a Cell Redirection Request to the CCNF, where it is used to indicate to the CCNF that the terminal is moved by the previous camping cell to the first base station.
  • the cell redirection request includes an ID (UE ID) of the terminal, and the ID of the terminal may be at least one of S-TMSI, TMSI, Resume ID, or other identifier that uniquely indicates the terminal within the coverage of the CCNF.
  • the cell redirection request may further include an ID (Anchor ID) of the cell where the terminal previously camped.
  • the CCNF receives the cell redirection request, and sends a Cell Redirection Request ACK and/or a context setup request message to the first base station.
  • the cell redirection request reply includes an NSSAI (Accepted NSSAI) allocated by the CCNF for the terminal, and the context establishment request message includes context information required for establishing a session for the terminal.
  • context information is established for the NG2 interface.
  • the first base station receives the cell redirection request reply and/or the NG2 interface context setup request message, establishes a corresponding bearer according to the flow context information included therein, and associates the established bearer with the CCNF stream.
  • the first base station sends an NG2 interface context setup request response to the CCNF, where the first base station (RAN side) establishes session indication information (that is, the corresponding bearer established in step 505 and the flow corresponding information of the bearer and the CCNF).
  • the NG2 interface context establishment request reply may further include a corresponding S-NSSAI in the Accepted NSSAI in step 504.
  • the first base station sends a first request reply to the terminal, where the first request reply includes configuration information.
  • the configuration information may include at least one of the foregoing flow context information, the bearer configuration information, and the bearer correspondence with the CCNF.
  • the terminal receives the first request reply, and performs corresponding configuration according to the configuration information included therein.
  • the base station to which the terminal moves to supports the CCNF of the network slice to which the terminal belongs when the base station to which the terminal moves to supports the CCNF of the network slice to which the terminal belongs, but does not support the NSI, the base station can perform CCNF path redirection, and can support the network slice to which the terminal belongs after performing the redirection, thereby reducing the RRC. The risk of a connection failure.
  • the first base station is a base station to which the terminal moves
  • the third base station is a base station where the terminal previously camped.
  • the steps of the communication method include:
  • the terminal sends a first request to the first base station, where the first request is used to request an RRC connection from the first base station.
  • the first base station receives the first request of the terminal, and sends an acquisition context request to the third base station.
  • the context request is used to request the context information of the terminal in the third base station.
  • the context information may refer to the related description in the embodiment shown in FIG. 4. In this embodiment, different parts are described, but the same The part will not be repeated.
  • the obtaining context request includes a Resume ID, and an indication flag (Accept Flag) of whether the network slice currently belongs to the terminal is supported.
  • the third base station receives the acquiring context request, and determines whether the first base station supports the network slice to which the terminal currently belongs. When it is determined that the first base station does not support the NSI of the network slice to which the terminal belongs, the third base station sends a cell redirection request to the CCNF.
  • the cell redirection request includes the ID and/or the terminal ID of the first base station, and the ID may be a PCI, a GCI, or other ID forms.
  • the first request may carry the indication information of whether the first base station supports the network slice to which the terminal belongs, so that the third base station may determine, according to the first request, whether the first base station supports the network to which the terminal belongs. slice.
  • the first base station and the third base station can exchange CCNF and NSI supported by each other, so that the third base station can determine the first base station according to the known CCNF and NSI supported by the first base station. Whether to support the network slice to which the terminal currently belongs.
  • the CCNF receives the cell redirection request, and sends a cell redirection response to the third base station. Specifically, the CCNF can know the first base station to which the terminal needs to be redirected according to the first base station ID carried in the cell redirection request. Reestablishing a session or modifying a session for the terminal according to the network slice supported by the first base station.
  • the cell redirection request acknowledgement includes at least network slice indication information.
  • the network slice indication information is an NSSAI that the CCNF reconfigures according to the cell redirection request, and may also be referred to as “Accepted NSSAI”.
  • the network slice indication information includes at least one of the following information: NSSAI, S-NSSAI, Slice ID, and Temporary ID. Comparing with the configured network slice indication information optionally carried in the first request, some or all of the S-NSSAI in the network slice indication information herein changes, or some or all of the S-NSSAI in the Accept NSSAI The SD information has changed.
  • the cell redirection request acknowledgement may further include updated flow context information, which is generated when the CCNF re-establishes a session or modifies the session.
  • the third base station receives the cell redirection request acknowledgement, and sends a get context request reply to the first base station, where the network slice indication information acquired in step 804 is included.
  • the obtained context request reply may further include updated flow context information.
  • the first base station receives the acquisition context request reply, and configures the DRB.
  • the first base station can perform corresponding configuration because the configuration request information required for configuring the DRB is already included in the response to the context request.
  • the first base station may further generate a mapping of the DRB and the flow.
  • the first base station receives the acquisition context request reply, and sends a path transfer request to the CCNF.
  • the CCNF For details, refer to the description of step 403 in the embodiment shown in FIG. 6. The different parts after the step will be described below, and the similarities between the two will not be repeated here.
  • the CCNF receives the path transfer request and sends a path transfer request reply to the first base station.
  • the CCNF receives the path transfer request and sends a path transfer request reply to the first base station.
  • the first base station receives the path transfer request reply, and sends a first request reply to the terminal.
  • the path transfer request reply For details, refer to the description of step 406 in the embodiment shown in FIG. 6. The different parts after the step will be described below, and the similarities between the two will not be repeated here.
  • the terminal After receiving the first request reply, the terminal performs corresponding configuration.
  • the network indication information and the DRB configuration are stored after the terminal configuration is completed.
  • the third base station may obtain information such as network slice indication information and DRB configuration by interacting with the CCNF, and the DRB configuration and the DRB and flow mapping may be completed before the path transition.
  • FIG. 9 a schematic flowchart of a communication method according to another embodiment of the present application is shown.
  • the first base station receives a first request sent by the terminal, where the first request is used to request an RRC connection from the first base station.
  • the first base station When the first base station does not support the network slice to which the terminal belongs, the first base station sends a cell redirection request to the default CCNF (hereinafter referred to as “SCCNF”), where the cell redirection request includes the terminal ID and the Configured NASSAI.
  • SCCNF default CCNF
  • the first base station may acquire, according to the configured network slice indication information, a network slice to which the terminal belongs, to determine whether the first base station supports the terminal.
  • the network slice may be acquired, according to the configured network slice indication information, a network slice to which the terminal belongs, to determine whether the first base station supports the terminal.
  • the first base station may further obtain the network slice to which the terminal belongs according to the manners of steps 3021 to 3023 shown in FIG. 5, to determine whether the first base station is Supporting the network slice described by the terminal, the different parts after the step will be described below, and the similarities between the two will not be described again.
  • the default CCNF receives the cell redirection request and determines whether CCNF redirection is required (ie, select another CCNF). If it is determined that CCNF redirection is not required, the default CCNF is taken as the target CCNF (hereinafter referred to as the target CCNF is "TCCNF"), and the CCNF of the target is used to provide services to the terminal. If it is determined that CCNF redirection is required, the cell redirection request is forwarded to another CCNF, and the other CCNF is transmitted as the target CCNF.
  • TCCNF target CCNF
  • the TCCNF receives the cell redirection request, and sends a retrieval context request (retrieval Context Request) to the SCCNF, where the acquiring context request includes the terminal ID and/or the Configured NSSAI.
  • the SCCNF receives the context request and feeds back the context information of the terminal to the TCCNF.
  • Context information includes, but is not limited to, flow context information, including at least one of stream priority and QoS.
  • the TCCNF receives the context information, establishes a new session for the terminal according to the flow context information, allocates an Accepted NSSAI, and sends a Cell Redirection Request ACK to the target base station.
  • the cell reselection request response includes at least one of an Accepted NSSAI and a flow context information.
  • the target base station receives the cell reselection request response, saves the new NSSAI, and reconfigures the DRB according to the cell reselection request response, or waits for the subsequent re-configured DRB to enter the active state, and sends the first request reply to the terminal.
  • the target base station when the terminal moves to the target cell corresponding to the cell, if the target base station does not support the CCNF of the network slice to which the terminal belongs, the target base station may be the CCNF requesting the network slice to which the terminal belongs, thereby avoiding the risk of RRC connection failure.
  • FIG. 10 a schematic flowchart of a communication method according to another embodiment of the present application is shown, and the communication method is applied to the communication system 100.
  • the present embodiment can be applied to a scenario where there is no Xn interface between the first base station corresponding to the cell to which the terminal moves and the second base station corresponding to the previously camped cell, or the Xn interface is unavailable due to network congestion.
  • the present embodiment is not limited to the foregoing scenario, and the RAN may adopt the solution even if the Xn interface is available.
  • the embodiment may also be used.
  • the communication method in this embodiment includes the following steps:
  • the terminal sends a first request to the first base station, where the first request may be an RRC recovery request message.
  • the first request may be an RRC recovery request message.
  • the first base station receives the first request, and sends a first Context Request (UE Context Request) to the terminal.
  • the first acquisition context request is used to obtain the terminal side context information.
  • the first base station may send a context request to the terminal to request the context information from the terminal.
  • the context request may include a facility information, configured to indicate to the terminal that the Xn interface between the first base station and the third base station is unavailable or unavailable, and the terminal may feedback the context information according to the Cause information.
  • the terminal receives the context request, and sends the terminal context information to the first base station.
  • the network information includes network slice indication information, where the network slice indication information includes at least one of NSSAI, S-NSSAI, Slice ID, and Temp ID. If the network slice indication information is not included in the first request, at least the configured network slice indication information needs to be included in the terminal context information.
  • the terminal context information may further include a tracking area (TAC), so that the first base station selects the CCNF.
  • TAC tracking area
  • the first base station receives terminal context information sent by the terminal, and sends an acquisition context request to the CCNF.
  • the acquisition context request is used to acquire the context of the CCNF side, including the terminal ID.
  • the acquired context information reference may be made to the definition of the context information in the embodiment shown in FIG. 4, and the differences between the two are described below, and the same portions will not be described herein.
  • the acquiring the context request further includes an ID of the cell corresponding to the third base station, whether the first base station supports the indication information of the network slice to which the terminal belongs, and an indication of whether the Xn interface exists between the first base station and the third base station. At least one of the Accept Flags.
  • the CCNF receives an acquisition context request sent by the first base station, and sends an acquisition context request to the third base station.
  • the acquisition context request includes a terminal ID to indicate to the third base station which context information of the terminal needs to be provided.
  • the second acquisition context request may further include a context form indication, where the third base station is configured to send the context information.
  • the contextual form indication can be a definition in the reference standard or a vendor-specific option.
  • the form of the context information may be in the form of a container or a non-container.
  • the container form means that the context information is included in a container message, and the CCNF does not parse and modify the container message.
  • the non-container format means that the context information is fed back in the form of a non-container, and the CCNF can parse and modify the context information fed back by the third base station.
  • the terminal When the CCNF determines that the first base station supports the network slice to which the terminal belongs, the terminal may be required to send the context information in a container manner, so that the context information may be transparently transmitted to the third base station; when the CCNF determines that the first base station does not support the network slice to which the terminal belongs, The terminal may be required to send context information in a non-easy form, and the CCNF may parse and modify the context information sent by the third base station.
  • the third base station receives the acquisition context request of the CCNF, and feeds back the context information to the CCNF.
  • the CCNF receives the context information and sends the context information to the first base station.
  • the CCNF When the context information received by the CCNF is in the form of a container, the CCNF transparently transmits the context information to the first base station; when the context information received by the CCNF is not in the form of a container, the CCNF parses the context information sent by the third base station. And modifying, specifically, modifying the NSSAI information and the flow context information therein, and transmitting the information to the first base station.
  • the context information includes radio bearer information previously established by the terminal at the third base station, and network slice information corresponding to the radio bearer.
  • the network segment remapped session information (including at least one of a session/stream ID and a session/stream QoS information) may also be included.
  • steps 1008 to 1009 reference may be made to the descriptions of the steps 804 to 404 in the embodiment shown in FIG. 6 or the steps 807 to 809 in the embodiment shown in FIG. 8, and details are not described herein again.
  • FIG. 11 a schematic flowchart of another communication method according to an embodiment of the present application is shown.
  • the method can be applied to communication system 100, which includes the following steps:
  • the RAN device sends a status transfer request to the terminal.
  • the network side may put the terminal in the Inactive state.
  • the above state switching request may be transmitted through RRC signaling.
  • the RAN Notification Area (RNA) and the RAN device may be included to support information about the network slice to which the current terminal belongs; in the second case, all of the TA and the TA may be included.
  • the cell supports the network slice to which the terminal currently belongs; in the third case, it may also include whether the terminal RNA and the RNA support the bitmap information of the network slice to which the terminal currently belongs; or in the fourth case, the current terminal of the support terminal may be included.
  • the manner in which the CCNF or the cell list of the associated network slice is described; or in the fifth case, may include a list of RNA IDs or a list of TAs supporting the network slice to which the terminal currently belongs.
  • RNA may be one cell or may include multiple cells.
  • RPA can be represented by an RNA ID, where the RNA ID represents the coverage of RNA containing one or more fixed cells.
  • the RPA may also be identified by a cell list, such as a physical cell identify (PCI) list, or other list form.
  • PCI physical cell identify
  • RNA is taken as an example by RNA ID.
  • the RRC signaling includes indication information of whether the terminal RNA and the RAN device support the network slice to which the current terminal belongs.
  • the indication information is 1 bit, and is used to indicate that all cells in the current RPA support the network slice to which the terminal belongs.
  • the RRC Release signaling includes a tracking area (TA) and all cells in the TA support the network slice to which the terminal belongs.
  • TA tracking area
  • the RRC signaling includes bitmap information of the network slice, and is used to indicate whether one or more cells in the RNA support the current terminal of the terminal.
  • Network slicing Exemplarily, the bitmap information is a binary string, and the number of bits of the string is the same as the number of cells in the RPA cell list, and a bit in the string can be set to 0 to indicate that the corresponding cell does not support the network to which the terminal belongs.
  • the slice is set to 1 to indicate the network slice to which the corresponding cell support terminal belongs, and vice versa.
  • the PCI list is represented as (PCI#1, PCI#2, PCI#4, PCI#5). If the bitmap information is 0101, it indicates PCI#2 and PCI#. The corresponding cell supports the network slice to which the terminal belongs, and the terminal can access; the cell corresponding to PCI#1 and PCI#4 does not support the network slice to which the terminal belongs, and the terminal may not be able to access.
  • the RRC signaling includes a cell list supporting the current network slice, which may be a PCI list, a GCI list, or other list forms.
  • a cell list supporting the current network slice which may be a PCI list, a GCI list, or other list forms.
  • One indication is that all cells in the network slice cell list support the network slice to which the current terminal belongs, and thus, when the terminal moves to the cell in the network slice cell list, the terminal can access.
  • Another indication is that all cells in the network slice cell list do not support the network slice to which the current terminal belongs. Therefore, when the terminal moves to the cell in the network slice cell list, the terminal may not be able to access, and when the terminal moves to When the network slices a cell other than the cell list, it can access. Therefore, it can adapt to different application scenarios.
  • the RNA ID list or the TA list supporting the current network slice may also be notified.
  • the terminal receives the state switching request, and sends a state transition confirmation message to the RAN device in response to the state switching request.
  • the communication method when the first base station does not support the network slice to which the terminal belongs, the communication method further includes:
  • the first base station receives a first request sent by the terminal, where the first request is used to request an RRC connection from the first base station.
  • the first base station When the first base station does not support the network slice to which the terminal belongs, the first base station sends a first request rejection message to the terminal.
  • the first request rejection message may include a cell list (Cell list) or a target cell ID (Target cell ID) supporting the network slice to which the terminal currently belongs, and frequency point information (Target Frequency, each of the cells supporting the current network slice of the terminal). At least one of the center frequency points of the cells.
  • the first request rejection message When the terminal is in the Inactive state, the first request rejection message may be referred to as an RRC Resume Reject message.
  • the first request rejection message When the terminal is in the Idle state, the first request rejection message may be referred to as an RRC Reject message.
  • the terminal By sending a first request rejection message to the terminal, the terminal is informed that it needs to access other cells, and the cell information capable of assisting the terminal to access the network slice to which it belongs is transmitted to the terminal.
  • the communication method further includes:
  • the first base station sends a UE context request (UE Context Request) to the terminal, and is used to request context information from the terminal.
  • UE Context Request UE Context Request
  • the UE context request may include a reason message to notify the UE of the reason that the Xn interface between the first base station and the third base station is unavailable, and the Xn interface may not be set between the first base station and the third base station. It is also possible that the Xn interface between the first base station and the third base station is unavailable.
  • the terminal receives the UE context request, and sends a UE context reply to the first base station, where the UE context reply includes at least one of NSSAI, S-NSSAI, slice ID, Temp ID, and TAC.
  • the communication device 1400 can include a processor 1401 and a transceiver 1402, the processor and the transceiver being communicatively coupled.
  • the communication device 1400 further includes a memory 1403, and the memory 1403 is communicatively coupled to the processor 1401.
  • the processor 1401, the memory 1403, and the transceiver 1402 are communicatively coupled by a bus 1404.
  • the memory 1403 can be used to store instructions for executing the memory stored instructions to control the transceiver 1402 to transmit information or signal.
  • the processor 1401 and the transceiver 1402 are respectively configured to perform various actions or processes performed by the first base station in the method described in the foregoing embodiments of FIG. 4 to FIG. Here, in order to avoid redundancy, a detailed description thereof will be omitted.
  • Figure 14 only shows a simplified design of the base station.
  • the base station may include any number of transmitters, receivers, processors, controllers, memories, communication units, etc., and all base stations that can implement the present application are within the scope of the present application.
  • FIG. 15 is a schematic block diagram of a communication device of an embodiment of the present application, which may correspond to (eg, may be configured or itself) the first base station described in the above-described communication methods illustrated in FIGS. 4 to 13.
  • the communication device 1500 can include: a sending module 1501, a processing module 1502, a sending module 1503, a sending module 1501, and a processing module 1502 in communication with the sending module 1503.
  • Each module or unit in the communication device 1500 is configured to perform respective actions or processes performed by the first base station in the method described in the foregoing embodiments of FIG. 4 to FIG. 13, respectively.
  • a detailed description thereof will be omitted.
  • FIG. 16 is a simplified structural diagram of a terminal according to an embodiment of the present application, and the communication device may correspond to (for example, may be configured or itself) a terminal described in the above-described communication methods illustrated in FIGS. 4 to 13.
  • the communication device 1600 can include a processor 1601 and a transceiver 1602, the processor and the transceiver being communicatively coupled.
  • the communication device 1600 further includes a memory 1603, and the memory 1603 is communicatively coupled to the processor 1601.
  • the processor 1601, the memory 1603, and the transceiver 1602 may be communicatively coupled by a bus 1604, which may be used to store instructions for executing the memory stored instructions to control the transceiver 1602 to transmit information. Or signal.
  • the processor 1601 and the transceiver 1602 are respectively configured to perform various actions or processes performed by the terminal in the method shown in FIG. 4 to FIG. 13 described above. Here, in order to avoid redundancy, a detailed description thereof will be omitted.
  • Figure 16 only shows a simplified design of the terminal.
  • the base station may include any number of transmitters, receivers, processors, controllers, memories, communication units, etc., and all base stations that can implement the present application are within the scope of the present application.
  • FIG 17 shows a schematic block diagram of a communication device of an embodiment of the present application, which may correspond to (e.g., may be configured or itself) the first base station described in the communication methods illustrated in Figures 4 through 13 above.
  • the communication device 1700 can include a sending module 1701, a processing module 1702, a sending module 1703, a sending module 1701, and a processing module 1702 in communication with the sending module 1703.
  • Each module or unit in the communication device 1700 is configured to perform respective actions or processes performed by the first base station in the method described in the foregoing embodiments of FIG. 4 to FIG. 13, respectively.
  • a detailed description thereof will be omitted.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium such as a solid state disk (SSD)
  • the processor (601, 801, 1001, 1201) in the device embodiment of the present application may be a Central Processing Unit (CPU), a Network Processor (NP), a hardware chip or Any combination thereof.
  • the hardware chip may be an Application-Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof.
  • the PLD may be a Complex Programmable Logic Device (CPLD), a Field-Programmable Gate Array (FPGA), a Generic Array Logic (GAL) or any of the above. combination.
  • the memory (603, 803, 1003, 1203) in the device embodiment of the present application may be a Volotile Memory, such as a Random Access Memory (RAM); or may be non-volatile.
  • Non-Volatile Memory such as Read-Only Memory (ROM), Flash Memory, Hard Disk Drive (HDD), or Solid-State Drive (SSD). ); also a combination of the above types of memories.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of cells is only a logical function division.
  • multiple units or components may be combined or integrated. Go to 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 separate, 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 patent 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 foregoing storage medium includes: a U disk, a mobile hard disk, a read only memory (ROM, abbreviated as Read-Only Memory), a random access memory (RAM, abbreviated as Random Access Memory), 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)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种通信方法，包括：第一基站接收终端发送的第一请求，所述第一请求用于向第一基站请求RRC连接；当第一基站不支持终端所属的网络切片时，第一基站向第二基站发送切换请求，其中，所述第二基站支持终端所属的网络切片；第一基站接收来自第二基站的切换请求回复，并向终端发送第一请求回复，所述第一请求回复包括所述第二基站的配置信息。

Description

通信方法及通信设备
本申请要求于2017年04月04日提交中国专利局、申请号为201710215622.X、申请名称为“通信方法及通信设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信领域，尤其涉及一种通信方法及通信设备。
背景技术
随着无线通信技术的飞速发展，第五代(5th Generation；简称：5G)无线通信技术已是目前业界的热点。5G将支持多样化的应用需求，其中包括支持更高速率体验和更大带宽的接入能力、更低时延和高可靠的信息交互、以及更大规模且低成本的机器类通信设备的接入和管理等。此外，5G将支持面向车联网、应急通信、工业互联网等各种垂直行业应用场景。面对5G这些性能要求和应用场景，5G网络需要更加贴近用户特定需求，其定制化能力需要进一步提升。
为此，5G引入了网络切片这一重要概念。一个网络切片是实现通信业务的多个网络功能(Network Functions；简称NFs)和相应资源的组合，包括核心网(Core Network；简称CN)部分、接入网(Radio Access Network；简称RAN)部分和/或终端部分。5G网络由满足不同连接能力的各种网络切片组成，一个网络切片是满足一类或一个用例的通信服务需求的逻辑网络，不同的网络切片为不同的用户以及不同的业务提供差异化的服务。一个RAN可支持多个网络切片，比如一个RAN可支持多个垂直行业应用。类似地，一个终端也可以支持多个网络切片，即可支持多个网络切片的业务的运行。对于组成网络切片的网络功能而言，分为公共网络功能和专用网络功能，其中公共网络功能是多个网络切片所共享的网络功能，专用网络功能是每一个网络切片所专用的网络功能。在实际网络中，可以存在多个公共网络功能，其中一个公共网络功能可以被多个网络切片所共享，另一个公共网络功能可以被其他多个网络切片所共享，不同的网络切片可以共享不同的公共网络功能。
当去激活(Inactive)态终端移动至某一小区时，需要该小区能够支持终端所属的网络切片，才能继续为其提供服务。然而，当小区移动到的小区不支持终端所属的网络切片时，有拒绝接入地风险。因此，亟待设计一种能够降低接入失败风险的机制。
发明内容
本申请实施例提供一种通信方法，以期降低去激活的终端在移动状态下连接失败的风险。
在一方面，本申请实施例提供一种通信方法，包括：
第一基站接收终端发送的第一请求，所述第一请求用于向第一基站请求无线资源 控制RRC连接；
当第一基站不支持终端所属的网络切片时，第一基站向第二基站发送切换请求，其中，所述第二基站支持终端所属的网络切片；
第一基站接收来自第二基站的切换请求回复，并向终端发送第一请求回复，所述第一请求回复包括所述第二基站的配置信息。
当去激活的终端在移动过程中，如果移动至的第一基站不支持终端所属的网络切片，则第一基站能够为终端进行小区重定向，并讲终端重定向至支持其所属的网络切片的基站，从而避免了连接失败的风险。
在一种可能的设计中，所述第一请求中包括允许终端接入的小区列表，所述第一基站向第二基站发送切换请求包括：根据所述小区列表选择第二基站，并向选中的第二基站发送切换请求。从而，终端能够在第一请求中携带允许终端接入的小区列表，提高后续接入的效率。
在一种可能的设计中，所述第一请求中还包括以下消息中的至少一种：
网络切片指示信息，用于向所述第一基站告知所述终端所属的网络切片信息；
原因信息，用于向第一基站告知发送第一请求的目的。
从而，终端能够在发送第一请求时向第一基站上报其网络切片指示信息、原因信息等，以便于第一基站决策。
在又一种可能的设计中，第一基站接收终端发送的第一请求之后还包括：
第一基站向第三基站发送第二请求，所述第三基站为所述终端之前驻留的基站，所述第二请求用于请求所述终端在第三基站中的上下文信息，所述上下文信息为终端在第三基站中驻留时的配置信息；
第一基站接收所述第三基站的上下文信息。
从而，第一基站可以从终端先前驻留的基站中获取到上下文信息，以便于决策。
在一种可能的设计中，上述上下文信息中包括以下消息中的至少一种：
流上下文信息，所述流上下文信息为所述终端已分配的流的信息，其中包括流ID信息，流优先级信息、QoS信息以及该流对应的网络切片信息中的至少一种；
承载信息，所述承载信息为所述终端已分配的承载的信息，其中包括承载ID信息，QoS信息，以及该承载对应的网络切片信息中的至少一种；
所述流与承载的映射信息；
所述终端的单个网络切片选择辅助信息S-NSSAI、网络切片选择辅助信息NSSAI、网络切片标志Slice ID、临时标识Temp ID中的至少一个。
在又一种可能的设计中，第一基站向第二基站发送切换请求包括：
第一基站向终端发送测量请求，所述测量请求用于获取允许终端接入的小区列表；
第一基站接收测量报告，所述第一基站根据所述测量报告选择第二基站；
第一基站向选中的第二基站发送切换请求。
在又一方面，本申请实施例提出了又一种通信方法，包括：
第一基站接收终端发送的第一请求，所述第一请求用于向第一基站请求无线资源控制RRC连接；
当第一基站不支持终端所属的网络切片时，第一基站向公共控制面网络功能 CCNF发送路径转移请求，以将路径转移至支持终端的网络切片上；
第一基站接收来自CCNF的路径转移请求回复，并向终端发送第一请求回复，所述第一请求回复中包括CCNF的配置信息。
当去激活的终端在移动过程中，如果移动至的第一基站不支持终端所属的网络切片，则第一基站能够为终端进行路径重定向，并讲终端重定向至支持终端的网络切片，从而避免了连接失败的风险。
在另一方面，本申请实施例提出另一种通信设备，包括：
终端向第一基站发送第一请求，所述第一请求用于向所述第一基站请求RRC连接；
所述终端接收来自第一基站的第一请求回复，所述第一请求回复中包括第二基站的配置信息，所述第二基站为当第一基站不支持终端所属的网络切片时，所述第一基站确定的支持终端所属网络切片的基站，所述终端根据所述第一请求回复切换至第二基站。
在一种可能的设计中，所述方法还包括：所述终端接收第一基站发送的测量请求，所述测量请求用于获取允许终端接入的小区列表；
另一方面，本申请实施例提供了一种通信设备，该通信设备具有实现上述方法实际中第一基站行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，基站的结构中包括处理器和发射器，所述处理器被配置为支持基站执行上述方法中相应的功能。所述收发器用于支持基站与终端之间的通信，向终端发送上述方法中所涉及的信息或者指令。所述基站还可以包括存储器，所述存储器用于与处理器耦合，其保存基站必要的程序指令和数据。
又一方面，本申请实施例提供了一种终端，该终端具有实现上述方法设计中终端行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。所述模块可以是软件和/或硬件。
在一个可能的设计中，终端的结构中包括收发器和处理器，所述接收器被配置为支持终端接收上述基站为基站配置各种指令并发送相应该指令生成的数据或信令。所述处理器支持终端执行上述通信方法中终端的功能。所述终端还可以包括存储器，所述存储器用于与处理器耦合，其保存基站必要的程序指令和数据。
又一方面，提供了一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码被通信设备(例如，网络设备或网管设备)的通信单元、处理单元或收发器、处理器运行时，使得通信设备执行上述实现方式中的方法。
又一方面，提供了一种计算机可读存储介质，该计算机可读存储介质存储有程序，该程序使得用户设备执行上述实现方式中的方法。
相较于现有技术，本申请提供的方案可以在终端移动至某一不支持其所属网络切片的基站时，为终端进行重定向操作，从而避免了连接失败的风险，提高通信效率。
本申请的这些和其他方面在以下(多个)实施例的描述中会更加简明易懂。
附图说明
下面对本申请实施例或现有技术描述中使用的附图作简单地介绍：
图1是本申请实施例提供的一种网络切片架构示意图；
图2a和2b分别是本申请实施例提供的一种应用场景的简化示意图；
图3是本申请实施例提供的终端移动方法的信令交互图；
图4是本申请实施例提供的一种通信方法的信令交互图；
图5时本申请实施例提供的又一种通信方法的信令交互图；
图6时本申请实施例提供的又一种通信方法的信令交互图；
图7时本申请实施例提供的又一种通信方法的信令交互图；
图8时本申请实施例提供的又一种通信方法的信令交互图；
图9时本申请实施例提供的又一种通信方法的信令交互图；
图10时本申请实施例提供的又一种通信方法的信令交互图；
图11是本申请实施例提供的又一种通信方法的信令交互图；
图12是本申请实施例提供的又一种通信方法的信令交互图；
图13是本申请实施例提供的又一种通信方法的信令交互图；
图14是本申请实施例提供的一种通信设备的简化结构示意图；
图15是本申请实施例提供的一种通信设备的示意性框图；
图16是本申请实施例提供的一种终端的简化结构示意图；
图17是本申请实施例提供的一种终端的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例进行描述。
在本申请中，“示例性”一词用来表示“用作例子、例证或说明”。本申请中被描述为“示例性”的任何实施例不一定被解释为比其它实施例更优选或更具优势。为了使本领域任何技术人员能够实现和使用本申请，给出了以下描述。在以下描述中，为了解释的目的而列出了细节。应当明白的是，本领域普通技术人员可以认识到，在不使用这些特定细节的情况下也可以实现本申请。在其它实例中，不会对公知的结构和过程进行详细阐述，以避免不必要的细节使本申请的描述变得晦涩。因此，本申请并非旨在限于所示的实施例，而是与符合本申请所公开的原理和特征的最广范围相一致。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
下面以具体地实施例对本申请的技术方案进行详细说明。下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例不再赘述。
应理解，本申请实施例可以应用于各种支持网络切片架构的通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)或下一代通信系统，例如新接入(New Radio，NR)系统，演进的LTE(evolved LTE，eLTE)等。
图1示出了本申请实施例提供的一种通信系统100。终端110通过无线链路120和网络设备进行通信，网络设备包括RAN设备和CN设备，其中RAN设备可以是WLAN中的接入点(ACCESS POINT；简称AP)，GSM或CDMA中的基站(Base Transceiver Station；简称BTS)，也可以是WCDMA中的基站(NodeB；简称NB)，还可以是LTE中的演进型基站(Evolved Node B；简称eNB或eNodeB)，或者中继站或接入点，或者车载设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备，例如可以是5G的基站(例如Next-Generation Node B(简称gNB)或Next-Generation Radio(简称NR)等)，传输与接收点(Transmission and Reception Point；简称TRP)，集中式处理单元(Centralized Unit；简称CU)，分布式处理单元(Distributed Unit；简称DU)等。CN设备可以是LTE中的移动管理实体(Mobile Management Entity；简称MME)，网关(Gateway)，还可以是5G网络中的控制面(Control Plane；简称CP)网络功能(Network Function；简称NF)以及用户面(User Plane；简称UP)网络功能，例如公共控制面网络功能(Common CP NF；简称CCNF)。CCNF可以包含但不限于接入与移动性管理功能(Access and Mobility Management Function，AMF)、会话管理网络功能(Session Management NF；简称SMF)等中的至少一种。RAN支持CN中的多个网络切片，如第一网络切片101、第二网络切片102以及第三网络切片103。其中，在CN的CP面上，多个网络切片既有公共的CP NFs又有各自专用的CP NFs；在CN的UP面上，每个网络切片都具有专用的UP NFs。示例性地，图1中的第一网络切片和第二网络切片既有公共的第一CCNFs又有各自专用的CP NFs和UP NFs；第三网络切片也有公共的第二CCNFs及其专用的CP NFs和UP NFs。应理解，第三网络切片具有的第二CCNFs可以是和除了第一网络切片、第二网络切片之外的其他网络切片所公共的CP NFs。示例性地，在第一CCNFs中有与该CCNFs相对应的网络切片的第一AMF，用于管理第一网络切片和第二网络切片的接入和移动性；在第二CCNFs中有与该CCNFs相对应的网络切片的第二AMF，用于管理第三网络切片的接入和移动性。
网络切片还具备以下特点：1、在核心网(Core Network，CN)侧，不同的网络切片可以具有共享的CCNF。2、在CN侧，不同的网络切片可以具备特定的控制面功能和数据面功能，这种网络切片特定的控制面功能和数据面功能被称为网络切片实例。3、在接入网(Radio Access Network，RAN)侧，一个RAN设备可以支持相同或不同的 网络切片。示例性地，支持不同的网络切片存在两种情况一种情况是所有的网络切片共享网络资源，通过无线资源管理(radio resource management，RRM)来支持不同的切片，另一种情况是各个网络切片在资源上进行隔离。4、从用户侧来看，一个用户可以接入多个网络切片，但通常情况下接入一个CCNF，即用户可以接入多个NSI，但接入一个CCNF，用户在哪一个NSI上建立会话由CCNF决定。由于CN侧会存在多个CCNF，在一些情况下，RAN设备会根据网络切片选择辅助信息(Network Slice Selection Assistance Information，NSSAI)为用户选择CCNF，如果所选择的CCNF不合适，那么CCNF会为用户进行重定向。
另外，在本申请实施例中，网络设备为小区提供服务，终端通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与网络设备进行通信，该小区可以是网络设备(例如基站)对应的小区，小区可以属于宏基站，超级小区(Hyper Cell)，也可以属于小小区(small cell)对应的基站，这里的小小区可以包括：城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
由于不同厂商或运营商的功能或策略存在差异，不同的RAN设备对于网络切片的支持能力是不同的，其覆盖范围内所支持的网络切片也会不同。一种情况请参照图2a，RAN#A的覆盖范围内支持NS1、NS3和NS4，RAN#B的覆盖范围内支持NS1、NS2和NS3，RAN#C的覆盖范围内支持NS2、NS3和NS4。不同基站的覆盖范围基本正交，交叉部分较少，多存在于多校区同频部署的场景。另一种情况请参照图2b，RAN#A的覆盖范围内不同基站的覆盖范围内支持NS1、NS3和NS4，RAN#B的覆盖范围内支持NS2。不同基站的覆盖范围存在重叠，交叉部分较多，多存在于小区异频部署的场景。
终端110也可以称为用户、用户设备(User Equipment；简称UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端可以是无线局域网(Wireless Local Area Networks；简称WLAN)中的站点(STATION；简称ST)，可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol；简称SIP)电话、无线本地环路(Wireless Local Loop；简称WLL)站、个人数字处理(Personal Digital Assistant；简称PDA)设备、具有无线通信功能的手持设备、中继设备，计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备以及下一代通信系统，例如，第五代通信(Fifth-Generation；简称5G)网络中的终端或者未来演进的公共陆地移动网络(Public Land Mobile Network；简称PLMN)网络中的终端等。
作为示例而非限定，在本申请实施例中，该终端还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机 配合使用，如各类进行体征监测的智能手环、智能首饰等。
当终端移动至目标基站，并且需要和目标基站进行信令交互时，例如，需要发送上行数据或者目标基站与先前驻留的小区处于不同的RAN notification area从而需要进行位置更新(例如RAN notification area update)。如果目标基站不支持终端当前所述的网络切片，则有可能导致RRC失败，从而导致上行数据无法发送，或者RAN notification area无法进行位置更新。其中，上述RAN notification area(RNA)包含一个小区或者多个小区，如果包含多个小区，这多个小区可以属于一个gNB，也可以属于多个gNB。当Inactive终端在RNA内部移动时，可以不通知网络，但是当终端移动出RNA时，则需要告知网络。如图3所示，当Inactive态或者Idle态的终端从先前的驻留小区(针对Inactive终端的用户，驻留小区是指终端在该驻留小区从RRC连接状态变为Inactive状态(去激活状态))移动至新的服务小区(以下也称为“目标基站”)后会触发接入网寻呼区域更新(RAN paging area update)过程，从而将终端的接口连接(例如NG2接口)以及终端的上下文信息(例如，上下文信息)更新至新服务小区。如果目标基站支持用户当前所属的用户网络切片，那么用户后续可以接入目标小区，由目标基站继续服务。如果，目标基站不支持用户当前所属的用户网络切片，那么用户接入目标基站存在风险。
以下，对目标基站不支持用户当前所属的用户网络切片的情况作示例性地说明，第一种不支持的情况为目标基站不支持用户所属网络切片的CCNF，第二种不支持的情况为目标基站支持用户所属网络切片的CCNF但是不支持所述网络切片的专属网络功能(下面我们统称为NSI)。以图2a和图2b所示的应用场景为例，NS1对应的网络切片为CCNF1+NSI1、NS2对应的网络切片为CCNF1+NSI2、NS3对应的网络切片为CCNF1+NSI3以及NS4对应的网络切片为CCNF2+NSI4。以用户当前所属的网络切片为NS1为例，假设目标基站A支持的网络切片为NS4，不支持用户当前所属网络切片NS1中的CCNF1，此时目标基站A属于上述第一种不支持的情况。假设目标基站A支持的网络切片为NS2，其支持用户当前所属网络切片NS1中的CCNF1但是不支持NSI2，此时目标基站A属于上述第二种不支持的情况。
以下，结合图4至图13，详细描述本申请的方法实施例。下面以具体的实施例对本申请的技术方案进行详细说明。下面这几个具体的实施例可以相互结合，对于相同或相似的概念或过程可能在某些实施例不再赘述。应理解，图4至图13是本申请实施例的通信方法的示意性流程图，示出了该方法的详细的通信步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图4至图13中的各种操作的变形。此外，图4至图13中的各个步骤可以分别按照与图4至图13所呈现的不同的顺序来执行，并且有可能并非要执行图4至图13中的全部操作。
本申请各个实施例所公开的通信方法，可以应用于不同的应用场景。使得当Inactive态或者Idle态的终端从第三基站移动到目标基站时，即使目标基站不支持用户当前所属的网络切片，目标基站也能进行重定向，避免了终端不能接入网络的风险。
以下先对本申请各个实施例会涉及到的部分参数进行定义。需要说明的是，在不同的实施例中，以下参数包括的具体消息类型可能会存在不同，在同一实施例中，方法执行的不同步骤中所传递地消息内容也可能存在不同。需要说明的时，在描述不同 实施例时，会直接以上下文信息所包括的具体参数进行描述。
网络切片指示信息，用于向RAN设备(例如第一基站)告知终端当前所属的网络切片。网络切片指示信息可以是以下信息的至少一种，通信系统为终端分配的网络切片选择辅助信息(network slice selection assistance information，NSSAI)、单个网络切片选择辅助信息(single-network slice selection assistance information，S-NSSAI)，网络切片标识(Slice ID)、临时标识(Temporary ID)。S-NSSAI可以是切片/服务类型(Slice/Service Type，SST)、网络切片区分标识(Slice Differentiator，SD)中的任意一种。上述临时标识信息由AMF分配给已经在CN侧注册的终端，该临时标识可以唯一指向某一个AMF。
上下文信息，用于传递不同网元之间的会话、流或者承载的配置信息，在不同的流程中，其所包含的消息类型可以不同。具体地，上下文信息可以包括以下消息中的一种或多种：
1.流(Flow)上下文信息，可以包括流ID(或称流ID信息)、流优先级、QoS(Quality of Service)信息以及该流对应的网络切片信息中的至少一种。
2.数据无线承载(Data radio bearer，DRB)信息，可以包括承载ID(或称承载ID信息)、QoS信息，以及该承载对应的网络切片信息中的的至少一种。
3.承载与流的映射(mapping)信息。这是由于对于一个会话而言，核心网采用流的形式，而RAN采用数据无线承载的形式，在RAN需要将数据无线承载与核心网的流对应。
4.终端当前会话对应的网络切片指示信息，其中包括NSSAI、Slice ID、Temp ID，S-NSSAI中的至少一个。
5.映射策略消息，用于指示终端当前所属的网络切片还可以重新映射到的网络切片。例如，终端当前在网络切片1和网络切片2通信，映射策略消息中可以包含网络切片3和网络切片4的信息，表示网络切片1还可以重新映射到网络切片3或者网络切片4。那么，当第一基站不支持网络切片1时，第一基站还可以将网络切片1映射到其所支持的网络切片3或者网络切片4进行服务。该映射策略信息提供了当第一基站不支持终端所属的网络切片时，第一级站可以重新映射至的网络切片。
图4示出了本申请实施例的一种通信方法的流程示意图，该通信方法可应用于图1所示的通信系统100。图4所示的通信方法的应用场景可以为，当终端移动到的小区不支持终端所属的网络切片时，采用小区重定向的方式建立RRC连接。其中，本实施例中提及的第一基站为终端移动至的目标基站，第二基站为终端先前驻留的驻留基站，第三基站为第一基站不支持终端所属的网络切片时重定向的基站。其中，通信方法包含如下步骤：
301、终端向第一基站发送第一请求，所述第一请求用于向第一基站请求RRC连接。
302、第一基站接收第一请求，并判断是否支持终端所属的网络切片。
具体地，第一基站获取终端所属网络切片的信息，其中获取终端所属网络切片的信息的方式，例如根据第一请求中所携带的参数或者是其它方式获取，将在下文进行更为详细地描述。当第一基站支持终端所属的网络切片时，第一基站与终端建立RRC 连接；当第一基站不支持终端所属的网络切片时，执行步骤303。
303、当第一基站不支持终端所属的网络切片时，第一基站向第二基站发送切换(Handover，HO)请求，其中，第二基站支持终端所属的网络切片。
具体地，第一基站可以获取允许终端接入的小区列表，以选择支持终端所属的网络切片的第二基站。第一基站根据第一请求或者是其它方式获取到允许终端接入的小区列表，将在下文进行更为详细地描述。
切换请求中包括终端的上下文信息，该上下文信息为终端在第三基站中驻留时的配置信息，上下文所包括的消息类型请参照前述定义。
304、第二基站接收切换请求，并向第一基站发送切换请求回复。示例性地，切换请求回复中可以包括第二基站的上下文信息，其中包括但不限于第二基站的数据无线承载配置，以及DRB配置与流(Flow)之间的映射关系(Flow mapping)中的至少一个。
305、第一基站接收切换请求回复，并向终端发送第一请求回复，所述第一请求回复中包括第二基站的配置信息。第一请求回复可被称为RRC重配请求(RRC Connection Reconfig.)，其中包括但不限于第二基站的上下文信息。
306、终端接收第一请求回复，根据其中所包含的第二基站的配置信息进行相应的会话配置，从而在一个网络切片上建立至少一个默认会话。
一种情况下，终端可以存储接收到的配置信息然后继续处于inactive状态，需要在至少一个网络切片上建立至少一个默认会话，以便于后续进入active态时能快速接入；或者也可以第二基站完成同步过程，向第二基站发送RRC配置完成消息，在完成了RRC配置以后进入RRC连接状态，当有需要时，终端可以根据已配置的RRC进行数据传输。
若终端向目标基站发起接入请求而目标基站不支持终端当前所属网络切片时，通过将终端重定向至其他可以支持终端所属网络切片的小区接入，从而避免了RRC连接失败的风险。
以下，对第一请求做更为详细地描述，在步骤301中，该第一基站是终端移动到的小区(对应于前述“目标基站”)。该第一请求可被称为RRC恢复请求消息(Radio resource control resume request，RRC Connection Resume Request)，用于在请求建立与第一基站的RRC连接。可选地，第一请求可以包括以下消息中的一种或多种：
1.小区列表信息，其中包括终端当前可以接入的小区的集合。
2.网络切片指示信息，请参照上文描述。
3.原因(Cause)信息，用于向RAN设备告知发送第一请求的目的。在本实施方式中，发送第一请求的目的是为了传输数据。携带Cause消息可以让RAN设备进行拥塞控制，例如使得RAN设备设置传输数据的接入优先级高于传输信令的优先级，也就是说，在网络拥塞的时候，RAN设备优先同意传输数据的终端接入网络。
可选地，Cause信息还可以用于指示数据类型，以便于进行更为精准的拥塞控制，提高网络性能。其中，数据类型可以包括但不限于超可靠低时延通信(Ultra-Reliable Low Latency Communications，URLLC)业务数据、增强的移动宽带通信(enhanced  Mobile BroadBand，eMBB)业务数据、海量机器类通信(massive Machine Type，mMTC)业务数据。
4.恢复标识(Resume ID)，用于标识终端，并使得第一基站找到第三基站。
以下，对第一基站获取终端所属的网络切片的方式做更为详细地描述。
可选地，在步骤302中，当第一请求中包含网络切片指示信息时，第一基站可以根据配置的网络切片指示信息获取终端当前所属的网络切片。
可选地，当第一请求中不包含网络切片指示信息或者根据第一请求中所携带的网络切片指示信息无法确定终端所属的网络切片时时，第一基站还可以采用以下方法获取终端当前所属的网络切片，请参照图5，上述步骤302包括：
3021，第一基站向第三基站(相当于前述终端先前所驻留的基站)发送第二请求，用于请求终端在所述第三基站中的终端的上下文信息。该第二请求可以被称为获取上下文请求(retrieval context request)。
可选地，当第一请求中携带了Resume ID时，第一基站可以根据Resume ID获取到第三基站。
3022、第三基站接收第二请求，并向第一基站发送上下文信息。该上下文上下文信息也可被称为获取上下文回复(Retriveal Context response)。上下文信息请参照前述定义，需要说明的是，NSSAI、Slice ID、Temp ID，S-NSSAI虽然是可选项，但如果在第一请求中未携带NSSAI、Slice ID、Temp ID，S-NSSAI中的任意一个时，则在第三基站向第一基站发送上下文信息中需要包含NSSAI、Slice ID、Temp ID，S-NSSAI中的至少一个。
3023、第一基站接收上下文信息，从而获取到用户当前所属的网络切片及相关的配置信息，以判断其是否可以支持当前用户所属的网络切片。
以下，对第一基站获取允许终端接入的小区列表的方式进行更为详细地描述。
在步骤303中，可选地，当终端第一请求中携带小区列表时，第一基站可以根据小区列表选择可以支持用户所属的网络切片第二基站。
可选地，当终端第一请求中未携带小区列表时，第一基站可以采用以下方式获取小区列表，请继续参照图5，步骤303中包括：
3031、第一基站向终端发送测量请求，该测量请求用于获取终端可以接入的小区列表。
示例性地，测量请求中包括测量配置以及需要测量的小区列表。示例性地，该测量配置中包括触发事件等。该需要测量的小区列表可以是支持终端当前所属网络切片的小区集合。可选地，测量请求中还可以包括测量报告的形式指示，该形式指示用于指示终端的测量报告的形式，例如测量报告中包括终端当前可接入的所有小区的列表，或者测量报告中包括需要测量的小区列表中所有小区的信号质量，上述两种示例性的测量报告的形式可以单独存在，也可以两种同时存在。
3032、终端接收测量请求，响应该测量请求生成测量报告并发送。响应测量请求中所包括的形式指示，终端生成的测量报告中包括终端当前可接入的所有小区的列表、 需要测量的小区列表中所有小区的信号质量的至少一个。
3033、第一基站接收测量报告，根据测量报告选择支持用户网络切片的第二基站。
请参照图6，示出了本申请实施例的另一种通信方法的流程示意图。该通信方法400应用于图1所示通信系统100中，以下第一基站对应终端移动至的小区，第二基站对应终端需要切换的小区，第三基站对应终端先前驻留的小区。通信方法包含以下步骤：
401，终端向第一基站发送第一请求，所述第一请求用于向第一基站请求RRC连接。需要说明的是，由于应用场景不同，第一请求与图4所示实施例中步骤301的第一请求的描述，在此不再赘述。
402、第一基站接收第一请求，当第一基站不支持终端所属的网络切片时，向CCNF发送路径转移请求(Path Switch Request)。其中，路径转移是指会话从终端在原先驻留的基站中的端口转移至移动至的基站中的端口。
可选地，在步骤402中，当第一请求中包含配置的网络切片指示信息时，第一基站可以根据配置的网络切片指示信息获取终端当前所属的网络切片，以判断第一基站是否支持终端所属的网络切片。
可选地，当第一请求中不包含配置的网络切片指示信息时，第一基站还可以参照图5所示步骤3021至3023的方式获取终端当前所属的网络切片。可选地，相对于步骤3022中所描述的上下文信息而言，需要特别说明的时，本实施例中的上下文信息还可以包括：
该路径转移请求中包含第一基站可以接受的流指示和半接受的流指示中的至少一种。其中，半接受的流指示表示第一基站可以满足其QoS需求，但是需要进行网络切片重映射(remapping)。可选地，路径转移请求中还可以包括该半接受的流指示对应的网络切片指示信息中的至少一种，即第一基站根据映射策略信息进行重映射后的网络切片指示信息。举例来说，不同的NSI代表了不同的租户，例如NSI1为宝马租户，NSI2为奔驰租户。对于这两个租户而言，其提供的服务可能都是一样的，也就是QoS一样，但是其收费不一样。由于商业原因，第一基站支持宝马租户即NSI1，却不支持奔驰租户即NSI2。那么，当奔驰租户的终端移动至第一基站时，根据上述的映射策略信息，目标基站发现可以将NSI2的终端重映射到NSI1继续进行服务。
可选地，在向CCNF发送路径转移请求之前，若第一基站根据第一配置消息判断其可以满足终端至少一个会话的QoS且能够为终端建立承载时，则第一基站可以为终端建立承载。
403、CCNF接收路径转移请求，并向第一基站发送路径转移请求回复(Path Switch Request ACK)。其中路径转移请求回复包括以下信息中的一种或多种：
1.网络切片指示信息：这里的网络切片指示信息是可被接收的网络切片指示信息，为CCNF根据路径转移请求重新配置过的NSSAI，也可被称为Accept NSSAI。网络切片指示信息可以参照前述定义，与可选地携带在第一请求中的配置的网络切片指示信息相比较，此处Accepted NSSAI中的部分或全部S-NSSAI发生变化，或者是Accept NSSAI中部分S-NSSAI的SD信息发生变化，若S-NSSAI仅包括SST不能具体指示 到哪一个NSI时，那么SD信息可以对S-NSSAI进一步的指示，从而让S-NSSAI可以指示到具体的NSI；
2.上下文信息：这里为经过CCNF重新配置的流上下文信息，其中包括流的优先级、最大聚合比(Aggregate maximum bit rate，AMBR)或者QCI信息中的一个或多个。相对于终端当前的流上下文信息，路径转移请求回复中的流上下文信息可以不同。例如，以前述终端在核心网从奔驰的NSI2转移至宝马的NSI1后，虽然宝马NSI1接受了终端，但是相较于第一基站中已有的终端，因此流上下文信息中优先级会降低。
404、第一基站接收路径转移请求回复，并向终端发送第一请求回复。
第一基站根据路径转移请求回复中包含的信息进行配置，其中配置包括但不限于DRB配置，以及DRB与流之间的映射关系。此时，第一基站可以支持终端当前所属的网络切片。
第一请求回复中包括路径转移请求回复中的全部或部分信息和/或DRB配置。其中，针对终端的Inactive态或是Idle态，第一请求回复可以是RRC恢复请求，也可以是RRC重配置请求。其中，第一请求回复中包括网络切片指示信息，更新的DRB配置，更新的DRB与流的映射关系中的至少一个。
405、终端接收第一请求回复，根据其中所包含的配置信息进行相应地配置。
终端可以存储配置信息，以便于后续进入active态时能快速接入；或者也可以与第一基站完成同步过程。
可选地，当第一请求回复为RRC恢复请求时，终端根据第一请求回复中所包含的信息配置DRB。
可选地，当第一请求回复为RRC重配置请求时，终端还需要向第一基站发送RRC重配置完成消息和/或Flow与DRB映射关系。
可选地，在另一实施例中，请参照图7，当判断第一基站可以支持终端当前的网络切片的CCNF但不支持NSI时，第一基站还可以向CCNF请求小区的重定位，如图7所示，通信方法还可以为：
501，终端向第一基站发送第一请求，所述第一请求用于向第一基站请求RRC连接，可以参照步骤401的描述，在此不再赘述。
502，第一基站接收第一请求，并判断是否支持终端所属的网络切片。当第一基站支持终端当前的网络切片的CCNF但不支持NSI时，执行步骤503。具体可以参照图6所示步骤402的描述，在此不再赘述。
503，第一基站向CCNF发送小区重定向请求(Cell Redirection Request),用于向CCNF指示终端由先前的驻留小区移动至第一基站。其中，小区重定向请求中包括终端的ID(UE ID)，该终端的ID可以是S-TMSI、TMSI、Resume ID，或者是其他在该CCNF覆盖范围内唯一指示终端的标识中的至少一种。可选地，小区重定向请求还可以包括终端先前驻留小区的ID(Anchor ID)。
504，CCNF接收小区重定向请求，向第一基站发送小区重定向请求回复(Cell Redirection Request ACK)和/或上下文建立请求消息。其中，小区重定向请求回复中包括CCNF为终端分配的NSSAI(Accepted NSSAI)，上下文建立请求消息包括为终 端建立会话所需要的上下文信息。示例性地，为NG2接口建立上下文信息。
505，第一基站接收小区重定向请求回复和/或NG2接口上下文建立请求消息，根据其中所包含的流上下文信息，建立相应的承载，并将建立的承载与CCNF的流相对应。
506，第一基站向CCNF发送NG2接口上下文建立请求回复，其中包含第一基站(RAN侧)建立的会话指示信息(即为步骤505中建立的相应的承载及承载与CCNF的流对应信息)。可选地，当第一基站中的部分会话未建立成功时，NG2接口上下文建立请求回复中还可以包括步骤504中的Accepted NSSAI中相应的的S-NSSAI。
507、第一基站向终端发送第一请求回复，所述第一请求回复中包括配置信息。在本实施例中，配置信息可以包括上述流上下文信息，承载配置信息以及承载与CCNF的流对应关系中的至少一种。
508、终端接收第一请求回复，根据其中包含的配置信息进行相应地配置。
在本实施例中，当终端移动至的基站支持终端所属网络切片的CCNF，但是不支持NSI时，基站能够进行CCNF路径重定向，在进行重定向之后能够支持终端所属的网络切片，降低了RRC连接失败的风险。
在另一个实施例中，请参照图8，示出了本申请另一实施例的通信方法的流程示意图。其中，第一基站为终端移动至的基站，第三基站为终端先前驻留的基站。通信方法的步骤包括：
801，终端向第一基站发送第一请求，所述第一请求用于向第一基站请求RRC连接。
802，第一基站接收终端的第一请求，并向第三基站发送获取上下文请求。其中，获取上下文请求用于请求终端在第三基站中的上下文信息，该上下文信息可以参照图4所示实施例中的相关描述，本实施例中会对二者不同部分进行说明，但对于相同的部分，不再赘述。可选地，该获取上下文请求中包括Resume ID、是否支持终端当前所属网络切片的指示信息(Accept Flag)。
803，第三基站接收获取上下文请求，并判断第一基站是否支持终端当前所属的网络切片。当判定第一基站不支持终端所属的网络切片的NSI时，第三基站向CCNF发送小区重定向请求。小区重定向请求中包括第一基站的ID和/或终端ID，该ID可以是PCI，也可以为GCI，或者是其他ID形式。
示例性地，一种情况下，第一请求中可以携带第一基站是否支持终端当前所属的网络切片的指示信息，从而，第三基站可以根据第一请求确定第一基站是否支持终端所属的网络切片。在另一种情况下，在步骤803之前，第一基站和第三基站可以交互彼此支持的CCNF和NSI，从而第三基站可以根据已获知的第一基站支持的CCNF和NSI，判断第一基站是否支持终端当前所属的网络切片。
804，CCNF接收小区重定向请求，向第三基站发送小区重定向请求回复(cell redirection response)。具体地，CCNF根据小区重定向请求中所携带的第一基站ID，可以知悉终端需要重定向到的第一基站。根据第一基站所支持的网络切片，为终端重新建立会话或者修改会话。示例性地，小区重定向请求确认中至少包括网络切片指示 信息。该网络切片指示信息为CCNF根据小区重定向请求重新配置过的NSSAI，也可以被称为“Accepted NSSAI”。其中，网络切片指示信息包括以下几种信息中的至少一种：NSSAI，S-NSSAI，Slice ID以及Temporary ID。与可选地携带在第一请求中的配置的网络切片指示信息相比较，此处的网络切片指示信息中的部分或全部S-NSSAI发生变化，或者是Accept NSSAI中部分或全部S-NSSAI的SD信息发生变化。可选地，小区重定向请求确认中还可以包括更新的流上下文信息，为CCNF为终端重新建立会话或修改会话时产生的。
805，第三基站接收小区重定向请求确认，并向第一基站发送获取上下文请求回复，其中包含步骤804中获取的网络切片指示信息。可选地，当小区重定向请求确认中包含更新的流上下文信息时，获取上下文请求回复中还可以包含更新的流上下文信息。
806，第一基站接收获取上下文请求回复，并配置DRB。由于获取上下文请求回复中已经包含配置DRB所需要的配置信息，第一基站可以进行相应的配置。可选地，当获取上下文请求中包含更新的流上下文信息，则第一基站还可以生成DRB与流的映射。
807，第一基站接收获取上下文请求回复，并向CCNF发送路径转移请求。具体可以参照图6所示实施例中步骤403的描述，下文会描述关于步骤之后的不同部分，关于二者相同之处在此不再赘述。
808，CCNF接收路径转移请求，并向第一基站发送路径转移请求回复。具体可以参照图6所示实施例中步骤404的描述，下文会描述关于步骤之后的不同部分，关于二者相同之处在此不再赘述。
809，第一基站接收路径转移请求回复，并向终端发送第一请求回复。具体可以参照图6所示实施例中步骤406的描述，下文会描述关于步骤之后的不同部分，关于二者相同之处在此不再赘述。
810，终端在接收到第一请求回复后，进行相应地配置。可选地，终端配置完成后对网络指示信息、DRB配置两者中的一个或者全部进行存储。
在本实施方式中，第三基站可以通过与CCNF交互获得网络切片指示信息以及DRB配置等信息，可以在路径转移之前完成DRB的配置以及DRB与流的映射。
请参照图9，示出了本申请另一实施例的通信方法的流程示意图。
901，第一基站接收终端发送的第一请求，所述第一请求用于向第一基站请求RRC连接；
902，当第一基站不支持终端所属的网络切片时，第一基站向默认的CCNF(以下简称“SCCNF”)发送小区重定向请求，所述小区重定向请求包括终端ID和Configured NASSAI。
可选地，在步骤902中，当第一请求中包含配置的网络切片指示信息时，第一基站可以根据配置的网络切片指示信息获取终端当前所属的网络切片，以判断第一基站是否支持终端所述的网络切片。
可选地，当第一请求中不包含配置的网络切片指示信息时，第一基站还可以参照图5所示步骤3021至3023的方式获取终端当前所属的网络切片，，以判断第一基站 是否支持终端所述的网络切片，下文会描述关于步骤之后的不同部分，关于二者相同之处不再赘述。
903，默认的CCNF接收小区重定向请求，并判断是否需要CCNF重定向(即选择另一个CCNF)。如果判定不需要CCNF重定向，则将该默认的CCNF作为目标的CCNF(以下简称目标的CCNF为“TCCNF”)，该目标的CCNF用于向终端提供服务。如果判定需要CCNF重定向，则将小区重定向请求转发给另一个CCNF，将该另一个CCNF作为目标的CCNF进行传输。
904，TCCNF接收小区重定向请求，并向SCCNF发送获取上下文请求(retrieval Context Request)，获取上下文请求中包括终端ID和/或Configured NSSAI。
905，SCCNF接收上下文请求，并向TCCNF反馈终端的上下文信息。上下文信息中包括但不限于流上下文信息，其中包括流优先级、QoS中的至少一种。
906，TCCNF接收上下文信息，根据流上下文信息为终端建立新的会话，分配Accepted NSSAI，并向目标基站发送小区重选请求应答(Cell Redirection Request ACK)。其中，小区重选请求应答中包括Accepted NSSAI、流上下文信息中的至少一种。
907，目标基站接收小区重选请求应答，保存新的NSSAI，并根据小区重选请求应答重新配置DRB，或者等待后续进入active态时利用重新配置的DRB，并向终端发送第一请求回复。
在本实施例中，当终端移动至目标基站对应小区时，若目标基站不支持终端所属网络切片的CCNF时，目标基站可以为请求支持终端所属网络切片的CCNF，从而避免了RRC连接失败的风险。
请参照图10，示出了本申请又一实施例提出的通信方法的流程示意图，该通信方法应用于通信系统100。本实施例可以应用于如下的场景，终端移动至的小区对应的第一基站和先前驻留的小区对应的第二基站之间没有Xn接口或者由于网络拥塞Xn接口不可用。但是本实施例不限于上述的场景，RAN即使在Xn接口可用的情况下也可以采用本方案，例如第一基站发现不能支持终端当前的网络切片，则也可以采用本实施例。本实施例中通信方法包括如下步骤：
1001、终端向第一基站发送第一请求，该第一请求可以为RRC恢复请求消息。关于第一请求，可以参照图4所示实施例中步骤301的详细描述，下文会描述关于步骤之后的不同部分，关于二者相同之处在此不再赘述。
1002、第一基站接收第一请求，并向终端发送第一获取上下文请求(UE Context Request)。该第一获取上下文请求用于获取终端侧上下文信息，关于上下文信息的具体描述，可以参照图4所示实施例中上下文信息的定义，关于二者不同之处在下文进行描述，关于二者相同部分在此不再赘述。
具体地，当第一请求中未携带配置的网络切片指示信息，或者根据所携带的网络切片指示信息无法查找到对应的CCNF时，第一基站可以向终端发送上下文请求，以向终端请求上下文信息。
可选地，该上下文请求中可以包括Cause信息，用于向终端指示第一基站与第三基站之间的Xn接口没有或者不可用，终端可以根据Cause信息有针对性地反馈上下 文信息。
1003、终端接收上下文请求，并向第一基站发送终端上下文信息。其中，该上下文信息中包括网络切片指示信息，该网络切片指示信息中包括NSSAI、S-NSSAI、Slice ID、Temp ID中的至少一种。需要说明的时，若第一请求中未携带配置的网络切片指示信息，那么需要在终端上下文信息中至少包括配置的网络切片指示信息。
可选地，终端上下文信息中还可以包括跟踪区(TAC)，以便于让第一基站选择CCNF。
1004、第一基站接收终端发送的终端上下文信息，并向CCNF发送获取上下文请求。该获取上下文请求用于获取CCNF侧的上下文，其中包括终端ID。关于所获取的上下文信息的具体描述，可以参照图4所示实施例中上下文信息的定义，关于二者不同之处在下文进行描述，关于二者相同部分在此不再赘述。
可选地，该获取上下文请求中还包括第三基站对应的小区的ID、第一基站是否支持终端所属的网络切片的指示信息、以及第一基站与第三基站之间是否存在Xn接口的指示信息(Accept Flag)中的至少一种。
1005、CCNF接收第一基站发送的获取上下文请求，并向第三基站发送获取上下文请求。该获取上下文请求中包括终端ID，以向第三基站指示需要提供哪个终端的上下文信息。
可选地，第二获取上下文请求中还可以包括上下文形式指示，用于指示第三基站发送上下文信息的形式。该上下文形式指示，可以为参照标准中的定义，或者为厂商自选项。示例性地，上下文信息的形式可以为容器形式(Container)或者是非容器形式(Non-container)。具体地，容器形式是指上下文信息包含在一个容器消息中，CCNF不对容器消息进行解析和修改。非容器形式是指上下文信息以非容器的形式反馈，CCNF可以对第三基站反馈的上下文信息进行解析和修改。
当CCNF确定第一基站支持终端所属的网络切片时，可以要求终端以容器形式发送上下文信息，从而可以将上下文信息透传至第三基站；当CCNF确定第一基站不支持终端所属的网络切片，可以要求终端以非容易形式发送上下文信息，CCNF可以对第三基站发送的上下文信息进行解析和修改。
1006、第三基站接收CCNF的获取上下文请求，并向CCNF反馈上下文信息。
1007、CCNF接收上下文信息，并向第一基站发送上下文信息。
当CCNF接收到的上下文信息为容器形式时，CCNF以容器形式将上下文信息透传至第一基站；当CCNF接收到的上下文信息不为容器形式时，CCNF对第三基站发送的上下文信息进行解析和修改，具体地，对其中的NSSAI信息和流上下文信息进行修改，并发送给第一基站。该上下文信息包括所述终端之前在第三基站建立的无线承载信息，以及该无线承载所对应的网络切片信息。可选的，还可以包括网络切片重映射后的会话信息(包括会话/流的ID、会话/流的QoS信息中的至少一种)。
步骤1008～1009可以参照图6所示实施例中步骤402至404或图8所示实施例中步骤807至809的描述，在此不再赘述。
请参照图11，示出了本申请实施例的另一种通信方法的流程示意图。该方法可以 应用于通信系统100，其包括如下步骤：
1101、RAN设备向终端发送状态转移请求。
例如，当终端处于RRC连接状态，并且一段时间没有数据传输时，为了节省终端能耗，网络侧可以将终端置于Inactive状态。
示例性地，上述状态切换请求可以通过RRC信令传输。在RRC信令中，第一种情况下，可以包括RAN通知区域(RAN Notification Area，RNA)和RAN设备是否支持当前终端所属网络切片的信息；第二种情况下，可以包括TA和TA内所有的小区是否都支持终端当前所属的网络切片；第三种情况下，还可以包括终端RNA和RNA是否支持终端当前所属网络切片的位图信息；或者第四种情况下，可以包括支持终端当前所述的CCNF或者所属的网络切片的小区列表的方式；或者第五种情况下，可以包括支持终端当前所属网络切片的RNA ID列表或者TA列表。
上述RNA可以为一个小区，也可以包括多个小区。当终端在RNA覆盖范围内移动时，不需要告知网络侧；当终端移出RNA覆盖范围内时，需要告知网络侧。RPA可以通过一个RNA ID表示，此时RNA ID表示了包含一个或多个固定小区的RNA的覆盖范围。或者，RPA也可以通过小区列表的形式标识，例如物理小区标识(Physical cell identify，PCI)列表，或者其它列表形式。在本实施例中，以RNA通过RNA ID为例进行说明。
上述第一种情况下，RRC信令中包括终端RNA和RAN设备是否支持当前终端所属网络切片的指示信息。可选地，指示信息为1bit，用于指示当前RPA内的全部小区支持终端所属的网络切片。
上述第二种情况下，RRC Release信令中包括跟踪区(Tracking area，TA)和TA内所有的小区是否都支持终端所属的网络切片。
上述第三种情况下(这种情况下，RPA一定是以小区列表存在的)，RRC信令中包括网络切片的位图信息，用于表示RNA中的一个或多个小区是否支持终端当前所属网络切片。示例性的，位图信息是一个二进制字符串，该字符串的位数与RPA小区列表里的小区数量相同，可以采用将字符串中某一位设置为0表示对应小区不支持终端所属的网络切片，采用设置为1表示对应小区支持终端所属的网络切片，反之亦然。例如，当RPA小区列表中有四个小区时，PCI列表表示为(PCI#1、PCI#2、PCI#4、PCI#5)，如果位图信息为0101，则表示PCI#2和PCI#5对应的小区支持终端所属的网络切片，终端可以接入；表示PCI#1和PCI#4对应的小区不支持终端所属的网络切片，终端可能无法接入，
上述第四种情况下，RRC信令中包括支持当前所属网络切片的小区列表，可以为PCI列表、也可以GCI列表，或者是其它的列表形式。一种指示方式为，在网络切片小区列表中的所有小区支持当前终端所属的网络切片，如此，当终端移动到网络切片小区列表中的小区时，可以接入。另一种指示方式为，在网络切片小区列表中的所有小区不支持当前终端所属的网络切片，如此，当终端移动到网络切片小区列表中的小区时，可能无法接入，而当终端移动到网络切片小区列表以外的小区时，可以接入。从而，可以适应不同的应用场景。
上述第五种情况下，即在改状态转移消息中，还可以通知支持当前所述网络切片 的RNA ID列表或者TA列表。
1102、终端接收状态切换请求，响应该状态切换请求向RAN设备发送状态转换确认消息。
可选地，请参照图12，在又一实施例中，当第一基站不支持终端所属的网络切片时，通信方法还包括：
1201，第一基站接收终端发送的第一请求，第一请求用于向第一基站请求RRC连接。
1202，当第一基站不支持终端所属的网络切片时，第一基站向终端发送第一请求拒绝消息。第一请求拒绝消息中可以包括支持终端当前所属的网络切片的小区列表(Cell list)或者目标基站(Target cell ID)，以及支持终端当前所述网络切片的小区的频点信息(Target Frequency，每个小区的中心频点)中的至少一种。当终端为Inactive态时，第一请求拒绝消息可被称为RRC恢复拒绝消息(RRC Resume Reject)。当终端为Idle态时，第一请求拒绝消息可被称为RRC拒绝消息(RRC Reject)。
其中，第一基站判断终端所述的网络切片的方法可以参照前述方法实施例，在此不再赘述。
通过向终端发送第一请求拒绝消息，告知终端其需要接入其它小区，并将能够辅助终端接入支持其所属的网络切片的小区信息发送给终端。
请参照图13，在又一实施例中，当第一基站与第三基站之间的Xn接口不可用时，通信方法还包括：
1301，第一基站向终端发送UE上下文请求(UE Context Request)，用于向终端请求上下文信息。可选地，UE上下文请求中可以包含原因消息，以向UE通知第一基站与第三基站之间的Xn接口不可用的原因，可以是第一基站与第三基站之间未设置Xn接口，也可能是第一基站与第三基站之间的Xn接口不可用。
1302，终端接收UE上下文请求，并向第一基站发送UE上下文回复，其中UE上下文回复中包括NSSAI，S-NSSAI，slice ID，Temp ID，TAC中的至少一个。
上文结合图1至图13详细描述了本申请实施例的通信方法和通信系统，下文将结合图14至图17详细描述本申请实施例的通信设备。
图14示出了本申请实施例的通信设备的简化结构图，该通信设备可以对应(例如，可以配置于或本身即为)上述图4至图13所示通信方法中描述的第一基站。该通信装置1400可以包括：处理器1401和收发器1402，处理器和收发器通信连接。可选地，该通信装置1400还包括存储器1403，存储器1403与处理器1401通信连接。可选地，处理器1401、存储器1403和收发器1402通过总线1404通信连接，该存储器1403可以用于存储指令，该处理器601用于执行该存储器存储的指令，以控制收发器1402发送信息或信号。其中，处理器1401和收发器1402分别用于执行上述图4至图13实施例所述方法中第一基站所执行的各动作或处理过程。这里，为了避免赘述，省略其详细说明。
可以理解的是，图14仅仅示出了基站的简化设计。在实际应用中，基站可以包含任意数量的发射器，接收器，处理器，控制器，存储器，通信单元等，而所有可以实现本申请的基站都在本申请的保护范围之内。
图15示出了本申请实施例的通信设备的示意性框图，该通信设备可以对应(例如，可以配置于或本身即为)上述图4至图13所示通信方法中描述的第一基站。该通信装置1500可以包括：发送模块1501、处理模块1502、发送模块1503，发送模块1501、处理模块1502与发送模块1503通信连接。该通信设备1500中各模块或单元分别用于执行分别用于执行上述图4至图13实施例所述方法中第一基站所执行的各动作或处理过程。这里，为了避免赘述，省略其详细说明。
图16示出了本申请实施例的终端的简化结构图，该通信设备可以对应(例如，可以配置于或本身即为)上述图4至图13所示通信方法中描述的终端。该通信装置1600可以包括：处理器1601和收发器1602，处理器和收发器通信连接。可选地，该通信装置1600还包括存储器1603，存储器1603与处理器1601通信连接。可选地，处理器1601、存储器1603和收发器1602可以通过总线1604通信连接，该存储器1603可以用于存储指令，该处理器601用于执行该存储器存储的指令，以控制收发器1602发送信息或信号。其中，处理器1601和收发器1602分别用于执行上述图4至图13所示方法中终端所执行的各动作或处理过程。这里，为了避免赘述，省略其详细说明。
可以理解的是，图16仅仅示出了终端的简化设计。在实际应用中，基站可以包含任意数量的发射器，接收器，处理器，控制器，存储器，通信单元等，而所有可以实现本申请的基站都在本申请的保护范围之内。
图17示出了本申请实施例的通信设备的示意性框图，该通信设备可以对应(例如，可以配置于或本身即为)上述图4至图13所示通信方法中描述的第一基站。该通信装置1700可以包括：发送模块1701、处理模块1702、发送模块1703，发送模块1701、处理模块1702与发送模块1703通信连接。该通信设备1700中各模块或单元分别用于执行分别用于执行上述图4至图13实施例所述方法中第一基站所执行的各动作或处理过程。这里，为了避免赘述，省略其详细说明。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是 这种实现不应认为超出本专利申请的范围。
应理解，本申请的装置实施例中的处理器(601、801、1001、1201)可以是中央处理器(Central Processing Unit，简称CPU)，网络处理器(Network Processor，简称NP)，硬件芯片或者其任意组合。上述硬件芯片可以是专用集成电路(Application-Specific Integrated Circuit，简称ASIC)，可编程逻辑器件(Programmable Logic Device，简称PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(Complex Programmable Logic Device，简称CPLD)，现场可编程逻辑门阵列(Field-Programmable Gate Array，简称FPGA)，通用阵列逻辑(Generic Array Logic，简称GAL)或其任意组合。
本申请的装置实施例中的存储器(603、803、1003、1203)可以是易失性存储器(Volatile Memory)，例如随机存取存储器(Random-Access Memory，简称RAM)；也可以是非易失性存储器(Non-Volatile Memory)，例如只读存储器(Read-Only Memory，简称ROM)，快闪存储器(Flash Memory)，硬盘(Hard Disk Drive，简称HDD)或固态硬盘(Solid-State Drive，简称SSD)；还可以是上述种类的存储器的组合。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本专利申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本专利申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包含若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本专利申请各个实施例方法的全部或部分步骤。而前述的存储介质包含：U盘、移动硬盘、只读存储器(ROM，简称Read-Only Memory)、随机存取存储器(RAM，简称Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上，仅为本专利申请的具体实施方式，但本专利申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本专利申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本专利申请的保护范围之内。因此，本专利申请的保护范围应以权利要求的保护范围为准。

Claims (23)

  1. 一种通信方法，其特征在于，包括：
    第一基站接收终端发送的第一请求，所述第一请求用于向第一基站请求无线资源控制RRC连接；
    当第一基站不支持终端所属的网络切片时，第一基站向第二基站发送切换请求，其中，所述第二基站支持终端所属的网络切片；
    第一基站接收来自第二基站的切换请求回复，并向终端发送第一请求回复，所述第一请求回复包括所述第二基站的配置信息。
  2. 如权利要求1所述的通信方法，其特征在于，所述第一请求中包括允许终端接入的小区列表，所述第一基站向第二基站发送切换请求包括：
    根据所述小区列表选择第二基站，并向选中的第二基站发送切换请求。
  3. 如权利要求1或2所述的通信方法，其特征在于，所述第一请求中还包括以下消息中的至少一种：
    网络切片指示信息，用于向所述第一基站告知所述终端所属的网络切片信息；
    原因信息，用于向第一基站告知发送第一请求的目的。
  4. 如权利要求1-3任意一项所述的通信方法，其特征在于，第一基站接收终端发送的第一请求之后还包括：
    第一基站向第三基站发送第二请求，所述第三基站为所述终端之前驻留的基站，所述第二请求用于请求所述终端在第三基站中的上下文信息，所述上下文信息为终端在第三基站中驻留时的配置信息；
    第一基站接收所述第三基站的上下文信息。
  5. 如权利要求4所述的通信方法，其特征在于，所述上下文信息中包括以下消息中的至少一种：
    流上下文信息，所述流上下文信息为所述终端已分配的流的信息，其中包括流ID信息，流优先级信息、QoS信息以及该流对应的网络切片信息中的至少一种；
    承载信息，所述承载信息为所述终端已分配的承载的信息，其中包括承载ID信息，QoS信息，以及该承载对应的网络切片信息中的至少一种；
    所述流与承载的映射信息；
    所述终端的单个网络切片选择辅助信息S-NSSAI、网络切片选择辅助信息NSSAI、网络切片标志Slice ID、临时标识Temp ID中的至少一个。
  6. 如权利要求1所述的通信方法，其特征在于，第一基站向第二基站发送切换请求包括：
    第一基站向终端发送测量请求，所述测量请求用于获取允许终端接入的小区列表；
    第一基站接收测量报告，所述第一基站根据所述测量报告选择第二基站；
    第一基站向选中的第二基站发送切换请求。
  7. 一种通信方法，其特征在于，包括：
    终端向第一基站发送第一请求，所述第一请求用于向所述第一基站请求RRC连接；
    所述终端接收来自第一基站的第一请求回复，所述第一请求回复中包括第二基站的配置信息，所述第二基站为当第一基站不支持终端所属的网络切片时，所述第一基站确定的支持终端所属网络切片的基站，所述终端根据所述第一请求回复切换至第二基站。
  8. 如权利要求7所述的通信方法，其特征在于，所述方法还包括：
    所述终端接收第一基站发送的测量请求，所述测量请求用于获取允许终端接入的小区列表；
    所述终端生成测量报告并向所述第一基站发送。
  9. 一种通信设备，其特征在于，包括：
    收发器，用于接收终端发送的第一请求，所述第一请求用于向第一基站请求RRC连接；
    处理器，当第一基站不支持终端所属的网络切片时，用于生成切换请求，其中，所述第二基站支持终端所属的网络切片；
    收发器，还用于向第二基站发送切换请求以及接收来自第二基站的切换请求回复，并向终端发送第一请求回复，所述第一请求回复包括所述第二基站的配置信息。
  10. 如权利要求9所述的通信设备，其特征在于，所述第一请求中包括允许终端接入的小区列表，所述处理器还用于根据所述小区列表选择第二基站。
  11. 如权利要求9或10所述的通信设备，其特征在于，所述第一请求中还包括以下消息中的至少一种：
    网络切片指示信息，用于向所述第一基站告知所述终端所属的网络切片信息；
    原因信息，用于向第一基站告知发送第一请求的目的。
  12. 如权利要求9-11任意一项所述的通信设备，其特征在于，所述收发器还用于：
    向第三基站发送第二请求，所述第三基站为所述终端之前驻留的基站，所述第二请求用于请求所述终端在第三基站中的上下文信息，所述上下文信息为终端在第三基站中驻留时的配置信息；
    第一基站接收所述第三基站的上下文信息。
  13. 如权利要求12所述的通信设备，其特征在于，所述上下文信息中包括以下消息中的至少一种：
    流上下文信息，所述流上下文信息为所述终端已分配的流的信息，其中包括流ID 信息，流优先级信息、QoS信息以及该流对应的网络切片信息中的至少一种；
    承载信息，所述承载信息为所述终端已分配的承载的信息，其中包括承载ID信息，QoS信息，以及该承载对应的网络切片信息中的至少一种；
    所述流与承载的映射信息；
    所述终端的单个网络切片选择辅助信息S-NSSAI、网络切片选择辅助信息NSSAI、网络切片标志Slice ID、临时标识Temp ID中的至少一个。
  14. 一种终端，其特征在于，包括：
    收发器，用于向第一基站发送第一请求，所述第一请求用于向所述第一基站请求RRC连接，以及用于接收来自第一基站的第一请求回复，所述第一请求回复中包括第二基站的配置信息，所述第二基站为当第一基站不支持终端所属的网络切片时，所述第一基站确定的支持终端所属网络切片的基站；
    所述处理器，用于根据所述第一请求回复切换至第二基站。
  15. 如权利要求14所述的终端，其特征在于，所述收发器还用于接收第一基站发送的测量请求，所述测量请求用于获取允许终端接入的小区列表；
    所述处理器用于生成测量报告，所述收发器还用于发送所述测量报告。
  16. 一种基站，其特征在于，所述基站包括存储器和一个或多个处理器，所述存储器与所述一个或多个处理器耦合，所述一个或多个处理器用于执行如权利要求1-6任意一项所述的方法。
  17. 一种基站，其特征在于，所述基站包括一个或多个处理器，所述一个或多个处理器与存储器耦合，读取所述存储器中的指令并根据所述指令执行如权利要求1-6任意一项所述的方法。
  18. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1-6任意一项所述的方法。
  19. 一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如权利要求1-6任意一项所述的方法。
  20. 一种终端，其特征在于，所述终端包括存储器和一个或多个处理器，所述存储器与所述一个或多个处理器耦合，所述一个或多个处理器用于执行如权利要求7-8任意一项所述的方法。
  21. 一种终端，其特征在于，所述终端包括一个或多个处理器，所述一个或多个处理器与存储器耦合，读取所述存储器中的指令并根据所述指令执行如权利要求7-8任意一项所述的方法。
  22. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行如权利要求7-8任意一项所述的方法。
  23. 一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如权利要求7-8任意一项所述的方法。
PCT/CN2018/081537 2017-04-04 2018-04-02 通信方法及通信设备 WO2018184511A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18781087.4A EP3595358A4 (en) 2017-04-04 2018-04-02 COMMUNICATION METHOD AND COMMUNICATION DEVICE
US16/592,598 US11096097B2 (en) 2017-04-04 2019-10-03 Communication method and communications device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710215622.XA CN108924884B (zh) 2017-04-04 2017-04-04 通信方法及通信设备
CN201710215622.X 2017-04-04

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/592,598 Continuation US11096097B2 (en) 2017-04-04 2019-10-03 Communication method and communications device

Publications (1)

Publication Number Publication Date
WO2018184511A1 true WO2018184511A1 (zh) 2018-10-11

Family

ID=63713093

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/081537 WO2018184511A1 (zh) 2017-04-04 2018-04-02 通信方法及通信设备

Country Status (4)

Country Link
US (1) US11096097B2 (zh)
EP (1) EP3595358A4 (zh)
CN (2) CN108924884B (zh)
WO (1) WO2018184511A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111464324A (zh) * 2019-01-18 2020-07-28 中兴通讯股份有限公司 一种安全通信方法、装置和系统
CN111586893A (zh) * 2020-04-15 2020-08-25 中国联合网络通信集团有限公司 一种终端rrc状态切换方法及装置
CN114554571A (zh) * 2018-11-15 2022-05-27 北京小米移动软件有限公司 网络切片的使用方法及装置

Families Citing this family (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11240720B2 (en) * 2017-06-02 2022-02-01 FG Innovation Company Limited Methods, devices, and systems for service-driven mobility management
US20190380109A1 (en) * 2018-06-11 2019-12-12 Nokia Solutions And Networks Oy Radio access network paging procedure based on network slice
CN110769458B (zh) * 2018-07-27 2021-09-07 华为技术有限公司 通信方法、接入网设备和终端设备
CN109041132B (zh) * 2018-09-26 2021-09-14 电子科技大学 基于空口切片的超低时延上行业务流资源预留和分配方法
CN111385857B (zh) 2018-12-29 2022-12-02 华为技术有限公司 无线通信的方法和装置
EP3905778B1 (en) * 2019-01-16 2024-06-19 Huawei Technologies Co., Ltd. Cell registration method and terminal device
WO2020147120A1 (en) 2019-01-18 2020-07-23 Qualcomm Incorporated Early measurement reporting
WO2020154868A1 (zh) * 2019-01-28 2020-08-06 Oppo广东移动通信有限公司 一种参数配置方法及装置、网络设备
US11490291B2 (en) * 2019-03-28 2022-11-01 Ofinno, Llc Handover for closed access group
CN112188544A (zh) * 2019-07-04 2021-01-05 大唐移动通信设备有限公司 一种基站间用户设备网络切片信息处理的方法和装置
CN112291820B (zh) * 2019-07-25 2022-07-29 华为技术有限公司 切换的方法和装置
FR3101498A1 (fr) * 2019-09-30 2021-04-02 Orange Procédé de contrôle d’un flux de données associé à un processus au sein d’un réseau mutualisé
CN114175727B (zh) * 2019-12-30 2023-04-28 华为技术有限公司 接入网络切片的方法和装置
CN113068239B (zh) * 2020-01-01 2022-05-24 华为技术有限公司 通信方法及相关装置
CN113163457A (zh) * 2020-01-22 2021-07-23 北京三星通信技术研究有限公司 一种会话建立方法及切换方法和设备
US11026149B1 (en) * 2020-01-31 2021-06-01 Dish Wireless Llc Systems and methods for reducing slice access failures
US12114336B2 (en) 2020-02-14 2024-10-08 Kt Corporation Methods for processing multicast/broadcast service data and apparatuses thereof
CN113411815B (zh) * 2020-03-16 2023-07-28 华为技术有限公司 一种接入网络切片的方法及装置
WO2021189496A1 (zh) * 2020-03-27 2021-09-30 华为技术有限公司 用于网络切片的数据传输方法及设备
US20220322221A1 (en) * 2020-04-02 2022-10-06 Nec Corporation Amf apparatus, access network node, and methods therefor
WO2021196171A1 (zh) * 2020-04-03 2021-10-07 Oppo广东移动通信有限公司 网络切片切换的方法、装置及其设备
CN113498121B (zh) * 2020-04-07 2024-06-25 华为技术有限公司 一种通信的方法及装置
KR20230005164A (ko) * 2020-04-20 2023-01-09 지티이 코포레이션 무선 통신에서의 서비스 연속성 보장
CN112512087A (zh) * 2020-04-26 2021-03-16 中兴通讯股份有限公司 网络切换方法、装置、设备及存储介质
CN113747522A (zh) * 2020-05-30 2021-12-03 华为技术有限公司 一种切换方法及装置
WO2021256985A1 (en) * 2020-06-19 2021-12-23 Telefonaktiebolaget Lm Ericsson (Publ) Proactive radio access network configuration update
CN113950108B (zh) * 2020-07-15 2024-05-07 大唐移动通信设备有限公司 一种小区重选方法、装置、终端及网络节点
CN111970721B (zh) * 2020-08-10 2022-08-12 中国联合网络通信集团有限公司 一种网络切片的管理方法和装置
US11836225B1 (en) * 2020-08-26 2023-12-05 T-Mobile Innovations Llc System and methods for preventing unauthorized replay of a software container
CN112888037A (zh) * 2021-01-26 2021-06-01 温州职业技术学院 一种机器视觉信息发送方法及机器视觉远程识别系统
CN112913279B (zh) * 2021-01-26 2023-11-14 北京小米移动软件有限公司 信息发送方法和装置、信息接收方法和装置
CN115225215B (zh) * 2021-03-30 2024-06-14 大唐移动通信设备有限公司 信息获取、发送方法、装置、终端设备及网络设备
CN113225440B (zh) * 2021-04-22 2022-09-02 广西东信易通科技有限公司 一种云通信网络切片的管理方法、计算机设备及存储介质
CN113172633B (zh) * 2021-05-27 2022-06-03 中国平安人寿保险股份有限公司 基于机器人流程自动化rpa的交互方法、装置、设备及介质
CN116261879A (zh) * 2021-10-09 2023-06-13 北京小米移动软件有限公司 信息上报方法、信息上报装置及存储介质
CN114339959A (zh) * 2021-12-31 2022-04-12 赛特斯信息科技股份有限公司 一种5g基站切片匹配方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106060900A (zh) * 2016-05-13 2016-10-26 宇龙计算机通信科技(深圳)有限公司 网络切片的接入控制方法及装置、终端化小区和sdn控制器
CN106375987A (zh) * 2015-07-22 2017-02-01 中兴通讯股份有限公司 一种网络切片的选择方法及系统
WO2017023196A1 (en) * 2015-08-05 2017-02-09 Telefonaktiebolaget Lm Ericsson (Publ) Distributed management of network slices using a gossip protocol
US20170079059A1 (en) * 2015-09-11 2017-03-16 Intel IP Corporation Slicing architecture for wireless communication
US20170086118A1 (en) * 2015-09-18 2017-03-23 Huawei Technologies Co., Ltd. System and Methods for Network Slice Reselection

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10111163B2 (en) * 2015-06-01 2018-10-23 Huawei Technologies Co., Ltd. System and method for virtualized functions in control and data planes
CN111147279A (zh) * 2015-06-01 2020-05-12 华为技术有限公司 用于控制平面和数据平面中的虚拟化功能的系统和方法
US10616820B2 (en) * 2015-08-25 2020-04-07 Lg Electronics Inc. Base station connecting method and user equipment performing same
CN106572517B (zh) * 2015-10-09 2018-12-18 中国移动通信集团公司 网络切片的处理方法、接入网络的选择方法及装置
US11026165B2 (en) * 2016-01-11 2021-06-01 Telefonaktiebolaget Lm Ericsson (Publ) Radio network node, network node, database, configuration control node, and methods performed thereby
US10893455B2 (en) * 2016-04-01 2021-01-12 Telefonaktiebolaget Lm Ericsson (Publ) Handover in a wireless communication network with network slices
EP3449663B1 (en) * 2016-04-11 2022-03-09 Telefonaktiebolaget LM Ericsson (PUBL) Method and apparatus for communication over network slices in wireless communication systems
CN105813195B (zh) * 2016-05-13 2019-05-17 电信科学技术研究院有限公司 一种按需为终端选择移动性管理机制的方法及装置
WO2018017132A1 (en) * 2016-07-22 2018-01-25 Nokia Technologies Oy Security handling for network slices in cellular networks

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106375987A (zh) * 2015-07-22 2017-02-01 中兴通讯股份有限公司 一种网络切片的选择方法及系统
WO2017023196A1 (en) * 2015-08-05 2017-02-09 Telefonaktiebolaget Lm Ericsson (Publ) Distributed management of network slices using a gossip protocol
US20170079059A1 (en) * 2015-09-11 2017-03-16 Intel IP Corporation Slicing architecture for wireless communication
US20170086118A1 (en) * 2015-09-18 2017-03-23 Huawei Technologies Co., Ltd. System and Methods for Network Slice Reselection
CN106060900A (zh) * 2016-05-13 2016-10-26 宇龙计算机通信科技(深圳)有限公司 网络切片的接入控制方法及装置、终端化小区和sdn控制器

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3595358A4

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114554571A (zh) * 2018-11-15 2022-05-27 北京小米移动软件有限公司 网络切片的使用方法及装置
CN111464324A (zh) * 2019-01-18 2020-07-28 中兴通讯股份有限公司 一种安全通信方法、装置和系统
CN111586893A (zh) * 2020-04-15 2020-08-25 中国联合网络通信集团有限公司 一种终端rrc状态切换方法及装置

Also Published As

Publication number Publication date
EP3595358A1 (en) 2020-01-15
CN113163459A (zh) 2021-07-23
CN108924884B (zh) 2021-02-23
CN113163459B (zh) 2024-04-09
US11096097B2 (en) 2021-08-17
EP3595358A4 (en) 2020-03-11
CN108924884A (zh) 2018-11-30
US20200037214A1 (en) 2020-01-30

Similar Documents

Publication Publication Date Title
WO2018184511A1 (zh) 通信方法及通信设备
EP3576458B1 (en) Communication method, source base station, target base station, core network device, and terminal device
US11089535B2 (en) Handover method in mobile network and communications apparatus
US10609608B2 (en) Method for changing connection mode in base station, and base station therefor, and method for changing connection mode in user equipment, and user equipment thereof
EP3611960B1 (en) Network overload control method and device
US10681767B2 (en) Method and apparatus for performing RRC connection resume in wireless communication system
EP3820192B1 (en) Communication method, access network device, and terminal device
EP3145228B1 (en) Method and apparatus for signal transmission and reception of hss/mme in wireless communication system
WO2018176482A1 (zh) 通信方法、核心网设备和接入网设备
WO2019105378A1 (zh) 通信方法和通信装置
US20180124676A1 (en) Terminal, Base Station, Cell Access Method, and Data Transmission Method
US20210400490A1 (en) Communication method and device
US20200053808A1 (en) Radio communication system, radio station, radio terminal, network apparatus, bearer control method, and computer readable medium
EP3629626B1 (en) Communication method and apparatus
US20200196208A1 (en) Method and Apparatus for Selecting Radio Access Network Device
US9503393B2 (en) S-GW relocation and QoS change without mobility
EP3649802B1 (en) Transfer of measurement configuration information in wireless communication networks
WO2021147099A1 (zh) 一种网络切片重定向的方法和装置
CN108924926B (zh) 通信方法及通信装置
EP3457758B1 (en) Data transmission methods and devices
KR20240060670A (ko) 통신 방법 및 장치
WO2022022082A1 (zh) 通信方法和通信装置
EP3031288A1 (en) S-gw relocation and qos change without mobility

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

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

Country of ref document: EP

Effective date: 20191010