WO2018032862A1 - 一种网络配置方法及网络设备 - Google Patents

一种网络配置方法及网络设备 Download PDF

Info

Publication number
WO2018032862A1
WO2018032862A1 PCT/CN2017/087205 CN2017087205W WO2018032862A1 WO 2018032862 A1 WO2018032862 A1 WO 2018032862A1 CN 2017087205 W CN2017087205 W CN 2017087205W WO 2018032862 A1 WO2018032862 A1 WO 2018032862A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobility
terminal
determining
state
session
Prior art date
Application number
PCT/CN2017/087205
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 KR1020197007892A priority Critical patent/KR20190040034A/ko
Priority to EP17840838.1A priority patent/EP3503471B1/en
Priority to KR1020217023603A priority patent/KR102346980B1/ko
Priority to US16/326,534 priority patent/US10992522B2/en
Priority to JP2019510311A priority patent/JP6895511B2/ja
Publication of WO2018032862A1 publication Critical patent/WO2018032862A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/0813Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/0806Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/085Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • H04L67/148Migration or transfer of sessions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W60/00Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08Mobility data transfer

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a network configuration method and a network device.
  • 3GPP TR 22.891 future 5G networks need to provide mobility support with different requirements.
  • different terminals have different mobile paradigms, for example, some terminals access the network in high-speed mobile, while others are nomadic access networks or static access networks; different services It also has different mobility support requirements. For example, some services want to reduce the interruption and packet loss rate during the service transmission process. Therefore, the network is required to shield the application layer from mobility events, including maintaining the Internet Protocol (IP) during the handover process.
  • IP Internet Protocol
  • the address is unchanged, while other applications can use application layer means to support business continuity.
  • IP Internet Protocol
  • TR 23.799 proposes a general state machine model, that is, the state machine of all terminals is unified, and different state machine models of different terminals are also proposed, for example, the POWER_SAVING state is used for the power saving mode terminal, and the simplified terminal is used for the stationary terminal.
  • State machine model The general state machine model in the EPS system is shown in Figures 1 and 2.
  • Per QoS class tunnel that is, the tunnel between a pair of network functions is the type of quality per service per session per session.
  • Per PDU session tunnel the tunnel between a pair of network functions is the type of per session per terminal.
  • the tunnel between a pair of network functions is the type of each node.
  • No tunnel the SDN-Based Approach, means that no tunnel is used for transmission between a pair of network functions.
  • the traditional network in the traditional mobile communication network, such as the LTE network, only a single terminal state machine, a single tunnel model, that is, a per bearer (per bearer) tunnel is supported.
  • the types of terminals are diverse, and the communication scenarios are also different. If these terminals use the same state machine, it will bring signaling waste and state maintenance.
  • unnecessary resource waste such as packet header encapsulation/decapsulation overhead, header Transmission overhead, etc.
  • the embodiment of the present application provides a network configuration method and a network device, which are used to solve the problem of how to dynamically select a mobility state machine and a tunnel type matched with a terminal, and improve resource utilization efficiency.
  • an embodiment of the present application provides a network configuration method, including:
  • the attributes of the terminal include any one or more of the following combinations:
  • the mobility attribute of the terminal is the mobility attribute of the terminal.
  • the set of mobility states of the terminal The set of mobility states of the terminal.
  • the mobility attribute of the terminal includes part or all of a mobility restriction, a mobility model, and a reachability requirement;
  • the session attribute of the terminal includes a type of the session and/or a continuity mode of the session. .
  • the capability of the terminal is a parameter used to represent any one of the following information or a combination of multiple information:
  • the access technology supported by the terminal is the access technology supported by the terminal.
  • the mobility state supported by the terminal is the mobility state supported by the terminal.
  • the configuration parameter includes any one or more of a mobility state allowed by the terminal, a mobility state used by the network side, and a transmission tunnel type of the network side.
  • the determining, according to an attribute of the terminal, a configuration parameter corresponding to the terminal including:
  • a mobility state that the terminal is allowed to use is determined according to the mobility limit, the mobility model, the reachability requirement, and some or all of the capabilities of the terminal.
  • the determining, by the terminal, a mobility state that is allowed to be used includes:
  • the reachability requirement is to support location tracking, determining that the terminal is allowed to enter an idle state, and entering the idle state and leaving the idle state respectively State transition condition.
  • the determining, by the terminal, a mobility state that is allowed to be used includes:
  • the terminal When the mobility is restricted to a non-moving level or a restricted mobility restriction, and the reachability requirement is to support location tracking or support a power saving mode, it is determined that the terminal allows to use the radio resource to control the RRC layer inactive state.
  • the determining, according to an attribute of the terminal, a configuration parameter corresponding to the terminal including:
  • the determining, by the core network side, the mobility state set corresponding to the terminal includes:
  • the determining, by the access network side, the usable mobility state corresponding to the terminal includes:
  • the mobility state of the access network side includes wireless when the mobility is limited to a non-moving level or a restricted mobility restriction, and the reachability requirement is to support location tracking or support a power saving mode
  • the resource controls the RRC layer inactive state.
  • the determining, according to an attribute of the terminal, a configuration parameter corresponding to the terminal including:
  • the network side NAS mobility state set is determined when it is determined that the acquired mobility state set of the terminal is appropriate.
  • the method further includes:
  • a parameter of the RRC layer mobility state or the auxiliary access network node determining the mobility state is generated according to part or all of the mobility state set, the mobility restriction, and the mobility model of the terminal.
  • the determining, according to an attribute of the terminal, a configuration parameter corresponding to the terminal including:
  • a transmission tunnel type of the network side is determined according to part or all of the mobility restriction, the mobility model, the type of the session, and the continuity mode of the session.
  • the determining, according to the mobility restriction, the mobility model, a type of the session, and a part or all of a continuity mode of the session, determining a transmission tunnel type of the network side include:
  • the transmission tunnel type is a simple tunnel type
  • the transmission tunnel type is a simple tunnel type when the mobility is restricted to a restricted mobility restriction, and the type of the session is normal IP data transmission and/or the continuity mode of the session is a non-continuity requirement. Or no tunnel type; or
  • the transmission tunnel model As a tunnel type per session per session;
  • the transmission tunnel model is determined to be a tunnel type per serving quality per session per session.
  • the indicating or configuring the terminal based on the configuration parameter, and/or indicating or configuring the related network function entity or node on the network side includes:
  • the mobility state and/or parameters for determining the mobility state are indicated to the associated access node.
  • the indicating or configuring the terminal based on the configuration parameter, and/or indicating or configuring the related network function entity or node on the network side includes:
  • the user plane function module on the network side is configured according to the transmission tunnel type.
  • the indicating or configuring the terminal based on the configuration parameter, and/or indicating or configuring the related network function entity or node on the network side includes:
  • the mobility state and/or the state transition condition that the terminal is allowed to use is indicated to the terminal.
  • the embodiment of the present application provides a network device, including:
  • a first determining module configured to determine an attribute of the terminal when the terminal accesses the network
  • a second determining module configured to determine, according to an attribute of the terminal, a configuration parameter corresponding to the terminal
  • a processing module configured to indicate or configure the terminal according to the configuration parameter, and/or indicate or configure an associated network function entity or node on the network side.
  • the attributes of the terminal include any one or more of the following combinations:
  • the mobility attribute of the terminal is the mobility attribute of the terminal.
  • the set of mobility states of the terminal The set of mobility states of the terminal.
  • the mobility attribute of the terminal includes part or all of a mobility restriction, a mobility model, and a reachability requirement;
  • the session attribute of the terminal includes a type of the session and/or a continuity mode of the session. .
  • the capability of the terminal is a parameter used to represent any one of the following information or a combination of multiple information:
  • the access technology supported by the terminal is the access technology supported by the terminal.
  • the mobility state supported by the terminal is the mobility state supported by the terminal.
  • the configuration parameter includes any one or more of a mobility state allowed by the terminal, a mobility state used by the network side, and a transmission tunnel type of the network side.
  • the second determining module is specifically configured to:
  • a mobility state that the terminal is allowed to use is determined according to the mobility limit, the mobility model, the reachability requirement, and some or all of the capabilities of the terminal.
  • the second determining module is specifically configured to:
  • the reachability requirement is to support location tracking, determining that the terminal is allowed to enter an idle state, and entering the idle state and leaving the idle state respectively State transition condition.
  • the second determining module is specifically configured to:
  • the terminal When the mobility is restricted to a non-moving level or a restricted mobility restriction, and the reachability requirement is to support location tracking or support a power saving mode, it is determined that the terminal allows to use the radio resource to control the RRC layer inactive state.
  • the second determining module is specifically configured to:
  • the mobility model According to the mobility limit, the mobility model, the reachability requirement, and a portion of the capabilities of the terminal Or all, determining the usable mobility state corresponding to the terminal on the access network side.
  • the second determining module is specifically configured to:
  • the second determining module is specifically configured to:
  • the mobility state of the access network side includes wireless when the mobility is limited to a non-moving level or a restricted mobility restriction, and the reachability requirement is to support location tracking or support a power saving mode
  • the resource controls the RRC layer inactive state.
  • the second determining module is specifically configured to:
  • the network side NAS mobility state set is determined when it is determined that the acquired mobility state set of the terminal is appropriate.
  • the second determining module is further configured to:
  • a parameter of the RRC layer mobility state or the auxiliary access network node determining the mobility state is generated according to part or all of the mobility state set, the mobility restriction, and the mobility model of the terminal.
  • the second determining module is specifically configured to:
  • a transmission tunnel type of the network side is determined according to part or all of the mobility restriction, the mobility model, the type of the session, and the continuity mode of the session.
  • the second determining module is specifically configured to:
  • the transmission tunnel type is a simple tunnel type
  • the transmission tunnel type is a simple tunnel type when the mobility is restricted to a restricted mobility restriction, and the type of the session is normal IP data transmission and/or the continuity mode of the session is a non-continuity requirement. Or no tunnel type; or
  • the transmission tunnel model As a tunnel type per session per session;
  • the transmission tunnel model is determined to be a tunnel type per serving quality per session per session.
  • the processing module is specifically configured to:
  • the mobility state and/or parameters for determining the mobility state are indicated to the associated access node.
  • the processing module is specifically configured to:
  • the user plane function module on the network side is configured according to the transmission tunnel type.
  • the processing module is specifically configured to:
  • the mobility state and/or the state transition condition that the terminal is allowed to use is indicated to the terminal.
  • an embodiment of the present application provides a network server, including a processor, a memory, and a transceiver, where the transceiver receives and transmits data under the control of a processor, and the preset program is stored in the memory, and the processor Read the program in the memory and follow the procedure to perform the following process:
  • the processor determines an attribute of the terminal
  • the processor determines, according to an attribute of the terminal, a configuration parameter corresponding to the terminal;
  • the processor indicates or configures the terminal based on the configuration parameter and/or indicates or configures an associated network function entity or node on the network side.
  • the attributes of the terminal include any one or more of the following combinations:
  • the mobility attribute of the terminal is the mobility attribute of the terminal.
  • the set of mobility states of the terminal The set of mobility states of the terminal.
  • the mobility attribute of the terminal includes part or all of a mobility restriction, a mobility model, and a reachability requirement;
  • the session attribute of the terminal includes a type of the session and/or a continuity mode of the session. .
  • the capability of the terminal is a parameter used to represent any one of the following information or a combination of multiple information:
  • the access technology supported by the terminal is the access technology supported by the terminal.
  • the mobility state supported by the terminal is the mobility state supported by the terminal.
  • the configuration parameter includes any one or more of a mobility state allowed by the terminal, a mobility state used by the network side, and a transmission tunnel type of the network side.
  • the processor is configured according to the mobility limit, the mobility model, and the reachability requirement And a part or all of the capabilities of the terminal, determining a mobility state that the terminal is allowed to use.
  • the processor determines that the terminal is allowed to enter an idle state, and enters the idle state and The state transition condition corresponding to the idle state is respectively left.
  • the processor determines that the terminal allows to use the wireless resource. Control the RRC layer inactive state.
  • the processor determines, according to the mobility limitation, the mobility model, the reachability requirement, and some or all of the capabilities of the terminal, a movement corresponding to the terminal on the core network side. a collection of sexual states;
  • the processor determines that the mobility state set in the core network side includes idle And a state transition condition corresponding to entering the idle state and leaving the idle state, respectively.
  • the processor determines the access network side.
  • the mobility state includes a radio resource control RRC layer inactive state.
  • the processor acquires a mobility state set of the terminal
  • the processor determines the network side NAS mobility state set when it is determined that the acquired mobility state set of the terminal is appropriate.
  • the processor generates an RRC layer mobility state or a parameter that the auxiliary access network node determines the mobility state according to part or all of the mobility state set, the mobility restriction, and the mobility model of the terminal.
  • the processor determines the transmission tunnel type of the network side according to part or all of the mobility restriction, the mobility model, the type of the session, and the continuity mode of the session.
  • the processor determines that the transmission tunnel type is a simple tunnel type
  • the processor determines that the transmission tunnel type is a simple tunnel type or a tunnelless type; or
  • the processor determines that the transmission tunnel type is simple when the mobility is limited to a restricted mobility restriction, and the type of the session is normal IP data transmission and/or the continuity mode of the session is a non-continuity requirement Tunnel type or no tunnel type; or
  • the processor determines that the transmission tunnel model is a tunnel type per session per session;
  • the processor determines that the transmission tunnel model is a tunnel type per serving quality per session per session.
  • the processor configures the mobility state set and/or the state transition condition in the core network;
  • a processor indicates the mobility state and/or parameters for determining the mobility state to the associated access node.
  • the processor configures the user plane function module on the network side according to the transmission tunnel type.
  • the processor indicates to the terminal a mobility state and/or the state transition condition that the terminal is allowed to use.
  • the terminal when the terminal accesses the network, determining an attribute of the terminal; determining, according to an attribute of the terminal, a configuration parameter corresponding to the terminal;
  • the terminal performs indication or configuration and/or indicates or configures related network function entities or nodes on the network side, so that the parameters of the terminal or the network side can be dynamically adjusted according to the attribute information of the terminal, thereby reducing signaling waste and status.
  • the complexity of maintenance and the waste of other resources solve the problem of how to dynamically configure matching parameters for the communication process of the terminal and improve resource utilization efficiency.
  • FIG. 1 is a schematic diagram of a general state machine model of a terminal in an Evolved Packet System (EPS) system according to an embodiment of the present application;
  • EPS Evolved Packet System
  • FIG. 2 is a schematic diagram of a state transition relationship of a terminal in an EPM (EPS mobility management) mobility state registration state in an EPS system according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart of a network configuration method in an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a first implementation manner of determining a mobility state used by the network side in an embodiment of the present application
  • FIG. 5 is a schematic diagram of a process for determining a type of a transmission tunnel on the network side in an embodiment of the present application
  • FIG. 6 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of another network device according to an embodiment of the present application.
  • the network configuration process is as follows:
  • Step 101 When the terminal accesses the network, determine the attribute of the terminal.
  • the network configuration process may be performed by a core network control plane function, where the network side specifically includes a core network and a radio access network (RAN).
  • RAN radio access network
  • the attributes of the terminal include any one or more of the following combinations:
  • the mobility attribute of the terminal is the mobility attribute of the terminal.
  • the set of mobility states of the terminal The set of mobility states of the terminal.
  • the mobility attribute of the terminal includes part or all of the mobility restriction, the mobility model, and the reachability requirement;
  • the session attribute of the terminal includes a type of the session and/or a continuity mode of the session. .
  • the mobility restriction may also be referred to as a mobility level
  • the mobility model is determined based on the mobility law and mobility level of the terminal;
  • the working mode supported by the terminal such as mobile broadband (eMBB) mode, low latency high reliability communication (CriCom) mode, large-scale machine type communication (mIoT) mode, can be used by usage type or dedicated Indicated by the Dedicated Core Network Identifier (DCN ID);
  • eMBB mobile broadband
  • CriCom low latency high reliability communication
  • mIoT large-scale machine type communication
  • DCN ID Dedicated Core Network Identifier
  • Access technologies supported by the terminal such as whether 5G access, 4G access, etc.;
  • the mobility state supported by the terminal for example, whether the power saving state is supported, and the RRC_connected_inactive state.
  • the core network control plane function determines the capability of the terminal and/or the mobility attribute of the terminal and/or the session attribute of the terminal and/or the mobility state of the terminal. set.
  • the mobility level is exemplified by the following three types: no movement, limited movement, and unrestricted movement. Of course, those skilled in the art may also set other mobility levels according to actual conditions, which are not used in the embodiment of the present application. limit. Reachability requirements refer to the network Whether the downlink data reachable terminal (UE) can be guaranteed, that is, the network needs to be able to monitor whether the idle state UE can be paged.
  • the reachability further includes whether the power saving mode is supported, that is, whether the UE supports working in the power saving mode/state; or whether the location tracking is supported, that is, whether the UE needs to report its location information to the network.
  • the reachability may also include other modes, which are not limited in the embodiment of the present application.
  • the session attributes of the terminal mainly include the type of the session and the continuity mode. From different dimensions, the types of sessions include IP type data transmission, non-IP type data transmission; and/or control plane established sessions, user plane established sessions; and/or normal priority sessions, high priority sessions. Wait. Those skilled in the art can define categories based on actual usage.
  • the continuity mode mainly includes the following three types:
  • Mode 1 The anchor point of the session is unchanged, ensuring business continuity and maintaining session continuity;
  • Mode 2 The anchor of the session can be changed, business continuity is not guaranteed, but session continuity is maintained;
  • Mode 3 The anchor of the session can be changed, but there are two sessions for the service, which guarantees business continuity, but does not maintain session continuity.
  • Determining the mobility state supported by the terminal in the capability of the terminal specifically determines that the terminal determines its own mobility state according to its mobility model, terminal capability, configuration, and the like.
  • step S101 After performing the step S101, the method in the embodiment of the present application performs step 102: determining a configuration parameter corresponding to the terminal based on an attribute of the terminal.
  • the configuration parameter includes any one or more of a mobility state allowed by the terminal, a mobility state used by the network side, and a transmission tunnel type of the network side.
  • the configuration parameters are mainly divided into two parts: determining the mobility state allowed by the terminal and determining the configuration parameter on the network side. The following two aspects are respectively described in detail.
  • determining the mobility state allowed by the terminal includes:
  • a mobility state that the terminal is allowed to use is determined according to the mobility limit, the mobility model, the reachability requirement, and some or all of the capabilities of the terminal.
  • the determining a mobility state that the terminal is allowed to use includes:
  • the reachability requirement is to support location tracking, determining that the terminal is allowed to enter an idle state, and entering the idle state and leaving the idle state respectively State transition condition.
  • the determining a mobility state that the terminal is allowed to use includes:
  • RRC Radio Resource Control
  • the configuration parameters on the network side are determined.
  • the configuration parameters on the network side are mainly divided into two aspects: determining a mobility state used by the network side and a transmission tunnel type of the network side.
  • Case A determining the mobility state used by the network side, in the embodiment of the present application, including but not limited to the following two implementation manners:
  • determining the mobility state used by the network side is determined by determining a mobility state set on the core network side and a mobility state usable on the access network side.
  • the control plane function of the core network determines the mobility state of the network side and the terminal according to the capability of the terminal, the mobility limitation of the terminal, the mobility model and the reachability requirement. .
  • the determining, by the core network side, the mobility state set corresponding to the terminal includes:
  • Determining the usable mobility state corresponding to the terminal on the access network side including:
  • the mobility state of the access network side includes wireless when the mobility is limited to a non-moving level or a restricted mobility restriction, and the reachability requirement is to support location tracking or support a power saving mode
  • the resource controls the RRC layer inactive state.
  • the second mode the determining, according to the attributes of the terminal, the configuration parameters corresponding to the terminal on the network side, including:
  • Non-Access Stratum A collection of mobility states.
  • the terminal when the terminal attaches/accesses to the network, the terminal itself determines the state machine model of the terminal according to its mobility model, terminal capability and configuration, etc., and then the terminal indicates or implicitly indicates the determined state machine to the network server.
  • the type for example, is indicated by the UE usage type, ie the mobility state set of the terminal.
  • the control plane function of the core network determines whether the mobility state indicated by the terminal is appropriate according to the mobility limitation of the terminal, the mobility model and the reachability requirement, and the subscription information of the terminal.
  • the subscription information may include: a usage type that the terminal is allowed to use; a reachability feature of the terminal, and the like, which is not limited in the embodiment of the present application.
  • the control plane function of the network core network determines that the determined mobility state set is appropriate, the network side NAS layer mobility state set is determined according to the indication of the terminal.
  • the method further includes:
  • a parameter of the RRC layer mobility state or the auxiliary access network node determining the mobility state is generated according to part or all of the mobility state set, the mobility restriction, and the mobility model of the terminal.
  • control plane function of the core network may also generate an RRC layer mobility state according to the indication of the terminal, the mobility limitation and/or mobility model of the terminal, or assist in determining the mobility state of the access network node.
  • the parameter for example, whether to activate an indication of the RRC_connected_inactive (Radio Resource Control Connection Inactive State) state, or the mobility limit indication of the terminal, the mobility model indication, and the like.
  • Case B determining the type of transmission tunnel on the network side, including:
  • a transmission tunnel type of the network side is determined according to part or all of the mobility restriction, the mobility model, the type of the session, and the continuity mode of the session.
  • the determining, according to the mobility restriction, the mobility model, the type of the session, and some or all of the continuity modes of the session, determining a transmission tunnel type of the network side include:
  • the transmission tunnel type is a simple tunnel type
  • the transmission tunnel type is a simple tunnel type when the mobility is restricted to a restricted mobility restriction, and the type of the session is normal IP data transmission and/or the continuity mode of the session is a non-continuity requirement. Or no tunnel type; or
  • the transmission tunnel model As a tunnel type per session per session;
  • the transmission tunnel model is determined to be a tunnel type per serving quality per session per session.
  • FIG. 5 is a process for determining the type of the transmission tunnel.
  • the control plane function of the core network determines the tunnel type of the session according to the mobility restriction of the terminal, the mobility model, the type of the session, and the continuity mode.
  • PDU Protocol Data Unit
  • step S102 the method in the embodiment of the present application performs step S103: instructing or configuring the terminal based on the configuration parameter, and/or instructing or configuring the related network function entity or node on the network side. .
  • the indicating or configuring the terminal according to the configuration parameter, and/or indicating or configuring the related network function entity or node on the network side includes the following three aspects:
  • the mobility state and/or parameters for determining the mobility state are indicated to the associated access node.
  • the control plane function of the core network determines the mobility state set of the network side and the transition conditions of each state, the parameters are respectively configured to the core network and the relevant nodes of the access network to satisfy the terminal. Mobility requirements.
  • the second aspect is a first aspect:
  • the user plane function module on the network side is configured according to the transmission tunnel type.
  • the control plane function of the core network determines the tunnel type used by the network side to communicate with the terminal
  • the user plane is configured according to the tunnel type, and the tunnel required by the terminal is established.
  • the third aspect is a first aspect:
  • the mobility state and/or the state transition condition that the terminal is allowed to use is indicated to the terminal.
  • the core network control plane function determines the mobility state and/or the state transition condition that the terminal is allowed to use according to the attribute of the terminal, sending an indication for configuring the mobility state to the terminal,
  • the indication is specifically for describing the mobility state, and may also be an indication for starting the mobility state. Therefore, the terminal configures the mobility state after receiving the description of the mobility state; or when the terminal receives the indication for starting the mobility state, starts the mobility state of the corresponding type according to the indication.
  • the network device mainly includes :
  • the first determining module 601 is configured to determine an attribute of the terminal when the terminal accesses the network;
  • a second determining module 602 configured to determine, according to an attribute of the terminal, a configuration parameter corresponding to the terminal;
  • the processing module 603 is configured to indicate or configure the terminal according to the configuration parameter, and/or indicate or configure an associated network function entity or node on the network side.
  • the attributes of the terminal include any one or more of the following combinations:
  • the mobility attribute of the terminal is the mobility attribute of the terminal.
  • the set of mobility states of the terminal The set of mobility states of the terminal.
  • the mobility attribute of the terminal includes part or all of a mobility restriction, a mobility model, and a reachability requirement;
  • the session attribute of the terminal includes a type of the session and/or a continuity mode of the session. .
  • the capability of the terminal is a parameter used to represent any one of the following information or a combination of multiple information:
  • the access technology supported by the terminal is the access technology supported by the terminal.
  • the mobility state supported by the terminal is the mobility state supported by the terminal.
  • the configuration parameter includes any one or more of a mobility state allowed by the terminal, a mobility state used by the network side, and a transmission tunnel type of the network side.
  • the second determining module 602 is specifically configured to:
  • a mobility state that the terminal is allowed to use is determined according to the mobility limit, the mobility model, the reachability requirement, and some or all of the capabilities of the terminal.
  • the second determining module 602 is specifically configured to:
  • the reachability requirement is to support location tracking, determining that the terminal is allowed to enter an idle state, and entering the idle state and leaving the idle state respectively State transition condition.
  • the second determining module 602 is specifically configured to:
  • the terminal When the mobility is restricted to a non-moving level or a restricted mobility restriction, and the reachability requirement is to support location tracking or support a power saving mode, it is determined that the terminal allows to use the radio resource to control the RRC layer inactive state.
  • the second determining module 602 is specifically configured to:
  • the second determining module 602 is specifically configured to:
  • the mobility state set on the core network side includes an idle state, and a state transition condition corresponding to entering the idle state and leaving the idle state respectively.
  • the second determining module 602 is specifically configured to:
  • the mobility state of the access network side includes wireless when the mobility is limited to a non-moving level or a restricted mobility restriction, and the reachability requirement is to support location tracking or support a power saving mode
  • the resource controls the RRC layer inactive state.
  • the second determining module 602 is specifically configured to:
  • the network side NAS mobility state set is determined when it is determined that the acquired mobility state set of the terminal is appropriate.
  • the second determining module 602 is further configured to:
  • a parameter of the RRC layer mobility state or the auxiliary access network node determining the mobility state is generated according to part or all of the mobility state set, the mobility restriction, and the mobility model of the terminal.
  • the second determining module 602 is specifically configured to:
  • a transmission tunnel type of the network side is determined according to part or all of the mobility restriction, the mobility model, the type of the session, and the continuity mode of the session.
  • the second determining module 602 is specifically configured to:
  • the transmission tunnel type is a simple tunnel type
  • the transmission tunnel type is a simple tunnel type when the mobility is restricted to a restricted mobility restriction, and the type of the session is normal IP data transmission and/or the continuity mode of the session is a non-continuity requirement. Or no tunnel type; or
  • the transmission tunnel model As a tunnel type per session per session;
  • the transmission tunnel model is determined to be a tunnel type per serving quality per session per session.
  • processing module 603 is specifically configured to:
  • the mobility state and/or parameters for determining the mobility state are indicated to the associated access node.
  • processing module 603 is specifically configured to:
  • the user plane function module on the network side is configured according to the transmission tunnel type.
  • processing module 603 is specifically configured to:
  • the mobility state and/or the state transition condition that the terminal is allowed to use is indicated to the terminal.
  • the embodiment of the present application provides a network device.
  • the network device mainly includes processing.
  • the processor 701 determines an attribute of the terminal
  • the processor 701 determines, according to an attribute of the terminal, a configuration parameter corresponding to the terminal;
  • the processor 701 indicates or configures the terminal based on the configuration parameter and/or indicates or configures an associated network function entity or node on the network side.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 701 and various circuits of memory represented by memory 702.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 703 can be a plurality of components, including a transmitter and a transceiver, providing means for communicating with various other devices on a transmission medium.
  • the processor 701 is responsible for managing the bus architecture and general processing, and the memory 702 can store data used by the processor 701 in performing operations.
  • the attributes of the terminal include any one or more of the following combinations:
  • the mobility attribute of the terminal is the mobility attribute of the terminal.
  • the set of mobility states of the terminal The set of mobility states of the terminal.
  • the mobility attribute of the terminal includes part or all of a mobility restriction, a mobility model, and a reachability requirement;
  • the session attribute of the terminal includes a type of the session and/or a continuity mode of the session. .
  • the capability of the terminal is a parameter used to represent any one of the following information or a combination of multiple information:
  • the access technology supported by the terminal is the access technology supported by the terminal.
  • the mobility state supported by the terminal is the mobility state supported by the terminal.
  • the configuration parameter includes any one or more of a mobility state allowed by the terminal, a mobility state used by the network side, and a transmission tunnel type of the network side.
  • the processor 701 determines, according to the mobility limitation, the mobility model, the reachability requirement, and some or all of the capabilities of the terminal, a mobility state that the terminal is allowed to use. .
  • the processor 701 determines that the terminal is allowed to enter an idle state, and enters the idle state. A state transition condition corresponding to each of the idle states.
  • the processor 701 determines that the terminal allows wireless use.
  • the resource controls the RRC layer inactive state.
  • the processor 701 determines, according to the mobility limitation, the mobility model, the reachability requirement, and some or all of the capabilities of the terminal, that the core network side corresponds to the terminal. a collection of mobility states;
  • the processor 701 determines, according to the mobility limitation, the mobility model, the reachability requirement, and some or all of the capabilities of the terminal, the available mobility of the access network side corresponding to the terminal. status.
  • the processor 701 determines that the mobility state set in the core network side includes An idle state, and a state transition condition corresponding to entering the idle state and leaving the idle state, respectively.
  • the processor 701 determines the access network side.
  • the mobility state includes a radio resource control RRC layer inactive state.
  • the processor 701 acquires a mobility state set of the terminal.
  • the processor 701 determines, according to the mobility limitation, the mobility model, the reachability requirement, and some or all of the capabilities of the terminal, whether the acquired mobility state set of the terminal is appropriate;
  • the processor 701 determines the network side NAS mobility state set when it is determined that the acquired mobility state set of the terminal is appropriate.
  • the processor 701 generates an RRC layer mobility state or a reference of the auxiliary access network node to determine the mobility state according to part or all of the mobility state set, the mobility restriction, and the mobility model of the terminal. number.
  • the processor 701 determines the transmission tunnel type of the network side according to part or all of the mobility restriction, the mobility model, the type of the session, and the continuity mode of the session. .
  • the processor 701 determines that the transmission tunnel type is a simple tunnel type; or
  • the processor 701 determines that the transmission tunnel type is a simple tunnel type or a tunnelless type; or
  • the processor 701 determines that the transmission tunnel type is Simple tunnel type or no tunnel type; or
  • the processor 701 determines that the transmission tunnel model is a tunnel type per session per session; or
  • the processor 701 determines that the transmission tunnel model is a tunnel type per serving quality per session per session.
  • the processor 701 configures the mobility state set and/or the state transition condition in the core network; and/or
  • the processor 701 indicates the mobility state and/or parameters for determining the mobility state to the associated access node.
  • the processor 701 configures the user plane function module on the network side according to the transmission tunnel type.
  • the processor 701 indicates to the terminal the mobility state and/or the state transition condition that the terminal is allowed to use.
  • the terminal when the terminal accesses the network, determining an attribute of the terminal; determining, according to an attribute of the terminal, a configuration parameter corresponding to the terminal;
  • the terminal performs indication or configuration and/or indicates or configures related network function entities or nodes on the network side, so that the parameters of the terminal or the network side can be dynamically adjusted according to the attribute information of the terminal, thereby reducing signaling waste and status.
  • the complexity of maintenance and the waste of other resources solve the problem of how to dynamically configure matching parameters for the communication process of the terminal and improve resource utilization efficiency.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application may employ one or more computers having computer usable program code embodied therein.
  • the form of a computer program product embodied on a storage medium including but not limited to disk storage and optical storage.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

本申请公开了一种网络配置方法及网络设备,用以解决如何动态的选择与终端匹配的移动性状态机及隧道类型,提高资源利用效率。方法为:终端接入网络时,确定所述终端的属性;基于所述终端的属性,确定与所述终端对应的配置参数;基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置。

Description

一种网络配置方法及网络设备
本申请要求在2016年8月19日提交中国专利局、申请号为201610697386.5、申请名称为“一种网络配置方法及网络设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域,尤其涉及一种网络配置方法及网络设备。
背景技术
1、第三代移动通信标准化组织(3rd Generation Partnership Project,3GPP)研究报告(Technical Report,TR)22.891的按需移动性支持需求介绍
根据3GPP TR 22.891的描述,未来5G网络需要提供不同需求的移动性支持。因为5G网络中存在不同的通信场景:不同的终端具有不同的移动范式,例如有些终端是在高速移动中接入网络的,而另外一些是游牧接入网络或者静态接入网络的;不同的业务也具有不同的移动性支持要求,例如某些业务希望减少在业务传输过程中的中断和丢包率,因此要求网络对应用层屏蔽移动性事件,包括切换过程中保持互联网协议(Internet Protocol,IP)地址不变,而另外一些应用却可以使用应用层手段来支持业务连续性。基于这些考虑,3GPP提出了按需的移动性支持。
2、终端的状态机介绍
目前TR 23.799中既提出了通用的状态机模型,即所有终端的状态机统一,也提出了不同终端的不同状态机模型,例如针对节电模式终端,使用POWER_SAVING状态;针对静止终端,使用简化的状态机模型。EPS系统中的通用状态机模型如图1及图2中所示。
3、终端会话的隧道类型介绍
目前TR 23.799中提出了多种隧道类型,包括:
Per QoS class tunnel,即一对网络功能之间的隧道是每终端每会话每服务质量的类型。
Per PDU session tunnel,即一对网络功能之间的隧道是每终端每会话的类型。
Per Node-level tunnel,即一对网络功能之间的隧道是每节点的类型。
No tunnel,即SDN-Based Approach,即一对网络功能之间不使用隧道进行传输。
传统网络中,在传统移动通信网络中,例如LTE网络,只支持单一的终端状态机,单一隧道模型,即per bearer(每承载)的隧道。然而在下一代网络中,终端的类型多样,通信场景也各不相同,如果这些终端使用相同的状态机,则会为带来信令的浪费和状态维护 的复杂度,另外,在为这些不同场景下的不同终端建立会话连接时,如果无法动态灵活的选择合适的隧道模型,则会带来不必要的资源浪费,例如包头封装/解封开销,包头传输开销等。
因此,如何动态的为终端的通信过程配置匹配的参数,提高资源利用效率是下一代网络亟待解决的问题。
发明内容
本申请实施例提供一种网络配置方法及网络设备,用以解决如何动态的选择与终端匹配的移动性状态机及隧道类型,提高资源利用效率。
本申请实施例提供的具体技术方案如下:
第一方面,本申请实施例提供了一种网络配置方法,包括:
终端接入网络时,确定所述终端的属性;
基于所述终端的属性,确定与所述终端对应的配置参数;
基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置。
可能的实施方式中,所述终端的属性包括以下任意一种或多种的组合:
终端的能力;
终端的移动性属性;
终端的会话属性;
终端的移动性状态集合。
可能的实施方式中,所述终端的移动性属性包括移动性限制、移动性模型和可达性要求中的部分或全部;所述终端的会话属性包括会话的类型和/或会话的连续性模式。
可能的实施方式中,所述终端的能力为用于表征以下任意一种信息或多种信息的组合的参数:
所述终端所支持的工作模式;
所述终端所支持的接入技术;
所述终端所支持的移动性状态。
可能的实施方式中,所述配置参数包括所述终端允许使用的移动性状态,所述网络侧使用的移动性状态,以及所述网络侧的传输隧道类型中的任意一种或多种。
可能的实施方式中,所述基于所述终端的属性,确定与所述终端对应的配置参数,包括:
根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定所述终端允许使用的移动性状态。
可能的实施方式中,所述确定所述终端允许使用的移动性状态,包括:
当所述移动性限制为不受限移动限制,且所述可达性要求为支持位置追踪时,确定所述终端允许进入空闲态,以及进入所述空闲态和离开所述空闲态分别对应的状态转移条件。
可能的实施方式中,所述确定所述终端允许使用的移动性状态,包括:
当所述移动性限制为不移动等级或受限移动限制,且所述可达性要求为支持位置追踪或支持节电模式时,确定所述终端允许使用无线资源控制RRC层非激活态。
可能的实施方式中,所述基于所述终端的属性,确定与所述终端对应的配置参数,包括:
根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定核心网侧与所述终端对应的移动性状态集合;以及
根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定接入网侧与所述终端对应的可使用的移动性状态。
可能的实施方式中,所述确定核心网侧与所述终端对应的移动性状态集合,包括:
当所述移动性限制为不受限移动限制,且所述可达性要求为支持位置追踪时,确定所述核心网侧的所述移动性状态集合中包含空闲态,以及进入所述空闲态和离开所述空闲态分别对应的状态转移条件。
可能的实施方式中,所述确定接入网侧与所述终端对应的可使用的移动性状态,包括:
当所述移动性限制为不移动等级或受限移动限制,且所述可达性要求为支持位置追踪或支持节电模式时,确定所述接入网侧的所述移动性状态中包含无线资源控制RRC层非激活态。
可能的实施方式中,所述基于所述终端的属性,确定与所述终端对应的配置参数,包括:
获取所述终端的移动性状态集合;
根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定获取到的所述终端的移动性状态集合是否合适;
在确定获取到的所述终端的移动性状态集合合适时,确定所述网络侧NAS移动性状态集合。
可能的实施方式中,在所述确定所述网络侧NAS移动性状态之后,所述方法还包括:
根据所述终端的移动性状态集合、移动性限制和移动性模型中的部分或全部,生成RRC层移动性状态或辅助接入网节点确定移动性状态的参数。
可能的实施方式中,所述基于所述终端的属性,确定与所述终端对应的配置参数,包括:
根据所述移动性限制、所述移动性模型、所述会话的类型和所述会话的连续性模式中的部分或全部,确定所述网络侧的传输隧道类型。
可能的实施方式中,所述根据所述移动性限制、所述移动性模型、所述会话的类型和所述会话的连续性模式中的部分或全部,确定所述网络侧的传输隧道类型,包括:
当所述移动性限制为任意限制,且所述会话的类型为非IP数据传输时,确定所述传输隧道类型为简单隧道类型;或
当所述移动性限制为不移动限制,且所述会话的类型为普通IP数据传输时,确定所述传输隧道类型为简单隧道类型或者无隧道类型;或
当所述移动性限制为受限移动限制,且所述会话的类型为普通IP数据传输和/或所述会话的连续性模式为无连续性要求时,确定所述传输隧道类型为简单隧道类型或者无隧道类型;或
当所述移动性限制为不受限移动限制,且所述会话的类型为普通IP数据传输时,确定所述传输隧道模型为每终端每会话的隧道类型;或
当所述移动性限制为不受限移动限制,且所述会话的类型为高优先级IP数据传输时,确定所述传输隧道模型为每终端每会话每服务质量的隧道类型。
可能的实施方式中,所述基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置,包括:
在所述核心网配置所述移动性状态集合,和/或所述状态转移条件;和/或
向所述相关接入节点指示所述移动性状态和/或用于确定所述移动性状态的参数。
可能的实施方式中,所述基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置,包括:
根据所述传输隧道类型,对所述网络侧的用户面功能模块进行配置。
可能的实施方式中,所述基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置,包括:
向所述终端指示所述终端允许使用的移动性状态和/或所述状态转移条件。
第二方面,本申请实施例提供了一种网络设备,包括:
第一确定模块,用于在终端接入网络时,确定所述终端的属性;
第二确定模块,用于基于所述终端的属性,确定与所述终端对应的配置参数;
处理模块,用于基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置。
可能的实施方式中,所述终端的属性包括以下任意一种或多种的组合:
终端的能力;
终端的移动性属性;
终端的会话属性;
终端的移动性状态集合。
可能的实施方式中,所述终端的移动性属性包括移动性限制、移动性模型和可达性要求中的部分或全部;所述终端的会话属性包括会话的类型和/或会话的连续性模式。
可能的实施方式中,所述终端的能力为用于表征以下任意一种信息或多种信息的组合的参数:
所述终端所支持的工作模式;
所述终端所支持的接入技术;
所述终端所支持的移动性状态。
可能的实施方式中,所述配置参数包括所述终端允许使用的移动性状态,所述网络侧使用的移动性状态,以及所述网络侧的传输隧道类型中的任意一种或多种。
可能的实施方式中,所述第二确定模块具体用于:
根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定所述终端允许使用的移动性状态。
可能的实施方式中,所述第二确定模块具体用于:
当所述移动性限制为不受限移动限制,且所述可达性要求为支持位置追踪时,确定所述终端允许进入空闲态,以及进入所述空闲态和离开所述空闲态分别对应的状态转移条件。
可能的实施方式中,所述第二确定模块具体用于:
当所述移动性限制为不移动等级或受限移动限制,且所述可达性要求为支持位置追踪或支持节电模式时,确定所述终端允许使用无线资源控制RRC层非激活态。
可能的实施方式中,所述第二确定模块具体用于:
根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定核心网侧与所述终端对应的移动性状态集合;以及
根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分 或全部,确定接入网侧与所述终端对应的可使用的移动性状态。
可能的实施方式中,所述第二确定模块具体用于:
当所述移动性限制为不受限移动限制,且所述可达性要求为支持位置追踪时,确定所述核心网侧的所述移动性状态集合中包含空闲态,以及进入所述空闲态和离开所述空闲态分别对应的状态转移条件。
可能的实施方式中,所述第二确定模块具体用于:
当所述移动性限制为不移动等级或受限移动限制,且所述可达性要求为支持位置追踪或支持节电模式时,确定所述接入网侧的所述移动性状态中包含无线资源控制RRC层非激活态。
可能的实施方式中,所述第二确定模块具体用于:
获取所述终端的移动性状态集合;
根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定获取到的所述终端的移动性状态集合是否合适;
在确定获取到的所述终端的移动性状态集合合适时,确定所述网络侧NAS移动性状态集合。
可能的实施方式中,所述第二确定模块还用于:
根据所述终端的移动性状态集合、移动性限制和移动性模型中的部分或全部,生成RRC层移动性状态或辅助接入网节点确定移动性状态的参数。
可能的实施方式中,所述第二确定模块具体用于:
根据所述移动性限制、所述移动性模型、所述会话的类型和所述会话的连续性模式中的部分或全部,确定所述网络侧的传输隧道类型。
可能的实施方式中,所述第二确定模块具体用于:
当所述移动性限制为任意限制,且所述会话的类型为非IP数据传输时,确定所述传输隧道类型为简单隧道类型;或
当所述移动性限制为不移动限制,且所述会话的类型为普通IP数据传输时,确定所述传输隧道类型为简单隧道类型或者无隧道类型;或
当所述移动性限制为受限移动限制,且所述会话的类型为普通IP数据传输和/或所述会话的连续性模式为无连续性要求时,确定所述传输隧道类型为简单隧道类型或者无隧道类型;或
当所述移动性限制为不受限移动限制,且所述会话的类型为普通IP数据传输时,确定所述传输隧道模型为每终端每会话的隧道类型;或
当所述移动性限制为不受限移动限制,且所述会话的类型为高优先级IP数据传输时,确定所述传输隧道模型为每终端每会话每服务质量的隧道类型。
可能的实施方式中,所述处理模块具体用于:
在所述核心网配置所述移动性状态集合,和/或所述状态转移条件;和/或
向所述相关接入节点指示所述移动性状态和/或用于确定所述移动性状态的参数。
可能的实施方式中,所述处理模块具体用于:
根据所述传输隧道类型,对所述网络侧的用户面功能模块进行配置。
可能的实施方式中,所述处理模块具体用于:
向所述终端指示所述终端允许使用的移动性状态和/或所述状态转移条件。
第三方面,本申请实施例提供了一种网络服务器,包括处理器、存储器和收发机,其中,收发机在处理器的控制下接收和发送数据,存储器中保存有预设的程序,处理器读取存储器中的程序,按照该程序执行以下过程:
终端接入网络时,处理器确定所述终端的属性;
处理器基于所述终端的属性,确定与所述终端对应的配置参数;
处理器基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置。
可能的实施方式中,所述终端的属性包括以下任意一种或多种的组合:
终端的能力;
终端的移动性属性;
终端的会话属性;
终端的移动性状态集合。
可能的实施方式中,所述终端的移动性属性包括移动性限制、移动性模型和可达性要求中的部分或全部;所述终端的会话属性包括会话的类型和/或会话的连续性模式。
可能的实施方式中,所述终端的能力为用于表征以下任意一种信息或多种信息的组合的参数:
所述终端所支持的工作模式;
所述终端所支持的接入技术;
所述终端所支持的移动性状态。
可能的实施方式中,所述配置参数包括所述终端允许使用的移动性状态,所述网络侧使用的移动性状态,以及所述网络侧的传输隧道类型中的任意一种或多种。
可能的实施方式中,处理器根据所述移动性限制、所述移动性模型、所述可达性要求 和所述终端的能力中的部分或全部,确定所述终端允许使用的移动性状态。
可能的实施方式中,当所述移动性限制为不受限移动限制,且所述可达性要求为支持位置追踪时,处理器确定所述终端允许进入空闲态,以及进入所述空闲态和离开所述空闲态分别对应的状态转移条件。
可能的实施方式中,当所述移动性限制为不移动等级或受限移动限制,且所述可达性要求为支持位置追踪或支持节电模式时,处理器确定所述终端允许使用无线资源控制RRC层非激活态。
可能的实施方式中,处理器根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定核心网侧与所述终端对应的移动性状态集合;以及
处理器根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定接入网侧与所述终端对应的可使用的移动性状态。
可能的实施方式中,当所述移动性限制为不受限移动限制,且所述可达性要求为支持位置追踪时,处理器确定所述核心网侧的所述移动性状态集合中包含空闲态,以及进入所述空闲态和离开所述空闲态分别对应的状态转移条件。
可能的实施方式中,当所述移动性限制为不移动等级或受限移动限制,且所述可达性要求为支持位置追踪或支持节电模式时,处理器确定所述接入网侧的所述移动性状态中包含无线资源控制RRC层非激活态。
可能的实施方式中,处理器获取所述终端的移动性状态集合;
处理器根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定获取到的所述终端的移动性状态集合是否合适;
在确定获取到的所述终端的移动性状态集合合适时,处理器确定所述网络侧NAS移动性状态集合。
可能的实施方式中,处理器根据所述终端的移动性状态集合、移动性限制和移动性模型中的部分或全部,生成RRC层移动性状态或辅助接入网节点确定移动性状态的参数。
可能的实施方式中,处理器根据所述移动性限制、所述移动性模型、所述会话的类型和所述会话的连续性模式中的部分或全部,确定所述网络侧的传输隧道类型。
可能的实施方式中,当所述移动性限制为任意限制,且所述会话的类型为非IP数据传输时,处理器确定所述传输隧道类型为简单隧道类型;或
当所述移动性限制为不移动限制,且所述会话的类型为普通IP数据传输时,处理器确定所述传输隧道类型为简单隧道类型或者无隧道类型;或
当所述移动性限制为受限移动限制,且所述会话的类型为普通IP数据传输和/或所述会话的连续性模式为无连续性要求时,处理器确定所述传输隧道类型为简单隧道类型或者无隧道类型;或
当所述移动性限制为不受限移动限制,且所述会话的类型为普通IP数据传输时,处理器确定所述传输隧道模型为每终端每会话的隧道类型;或
当所述移动性限制为不受限移动限制,且所述会话的类型为高优先级IP数据传输时,处理器确定所述传输隧道模型为每终端每会话每服务质量的隧道类型。
可能的实施方式中,处理器在所述核心网配置所述移动性状态集合,和/或所述状态转移条件;和/或
处理器向所述相关接入节点指示所述移动性状态和/或用于确定所述移动性状态的参数。
可能的实施方式中,处理器根据所述传输隧道类型,对所述网络侧的用户面功能模块进行配置。
可能的实施方式中,处理器向所述终端指示所述终端允许使用的移动性状态和/或所述状态转移条件。
基于上述技术方案,本申请实施例中,当终端接入网络时,确定所述终端的属性;基于所述终端的属性,确定与所述终端对应的配置参数;基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置,使得终端或者网络侧的参数能够根据终端的属性信息动态调整,从而减小了信令的浪费、状态维护的复杂度及其他资源的浪费,解决了如何动态的为终端的通信过程配置匹配的参数,提高资源利用效率的问题。
附图说明
图1为本申请实施例中演进分组系统(Evolved Packet System,EPS)系统中终端的通用状态机模型示意图;
图2为本申请实施例中EPS系统中终端在EMM(EPS mobility management,演进分组系统的移动性管理)注册状态下的状态转换关系示意图;
图3为本申请实施例中网络配置方法的过程示意图;
图4为本申请实施例中确定所述网络侧使用的移动性状态的第一种实现方式示意图;
图5为本申请实施例中确定所述网络侧的传输隧道类型的过程示意图;
图6为本申请实施例中网络设备的结构示意图;
图7为本申请实施例中另一网络设备的结构示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚,下面将结合附图对本申请作进一步地详细描述,显然,所描述的实施例仅仅是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例,都属于本申请保护的范围。
本申请实施例中,如图3所示,网络配置过程如下:
步骤101:终端接入网络时,确定所述终端的属性。
在具体实施过程中,可以由核心网控制面功能执行所述网络配置过程,所述网络侧具体包括核心网及无线接入网(Radio Access Network,RAN)。
本申请实施例中,所述终端的属性包括以下任意一种或多种的组合:
终端的能力;
终端的移动性属性;
终端的会话属性;
终端的移动性状态集合。
本申请实施例中,所述终端的移动性属性包括移动性限制、移动性模型和可达性要求中的部分或全部;所述终端的会话属性包括会话的类型和/或会话的连续性模式。
本申请实施例中,移动性限制也可以称为移动性等级;
移动性模型是基于终端的移动规律和移动性等级确定的;
所述终端的能力为用于表征以下任意一种信息或多种信息的组合的参数:
所述终端所支持的工作模式,例如移动宽带(eMBB)模式,低时延高可靠通信(CriCom)模式,大规模机器类通信(mIoT)模式,实现时可以使用用途类型(usage type)或专用核心网标识(Dedicated Core Network Identifier,DCN ID)来指示;
所述终端所支持的接入技术,例如是否5G接入,4G接入等;
所述终端所支持的移动性状态,例如是否支持power saving状态,RRC_connected_inactive状态。
在具体实施过程中,当终端附着/接入到网络时,核心网控制面功能则确定出终端的能力和/或终端的移动性属性和/或终端的会话属性和/或终端的移动性状态集合。所述移动性等级以如下三种为例:不移动,受限移动及不受限移动,当然,本领域技术人员也可以是根据实际情况设置其他的移动性等级,在本申请实施例中不作限制。可达性要求是指网络 是否能够保证下行数据可到达终端(UE),即网络需要能够监测到空闲态UE是否可以被寻呼到。可达性又包括是否支持节电模式,即,UE是否支持工作在节电模式/状态下;或者是否支持位置追踪,即,UE是否需要向网络报告其位置信息。当然,可达性也可以包含其他模式,在本申请实施例中不作限制。
终端的会话属性,主要包括会话的类型及连续性模式。从不同维度来讲,会话的类型包括IP类型的数据传输,非IP类型的数据传输;和/或控制面建立的会话,用户面建立的会话;和/或普通优先级会话,高优先级会话等。本领域技术人员可以根据实际使用情况定义类别。所述连续性模式主要包含如下三种:
模式1:会话的锚点不变,保证业务连续性,保持会话连续性;
模式2:会话的锚点可以改变,不保证业务连续性,但保持会话连续性;
模式3:会话的锚点可以改变,但有两条会话为业务服务,此时保证业务连续性,但不保持会话连续性。
所述终端的能力中表征所述终端所支持的移动性状态具体为所述终端根据其移动模型,终端能力和配置等确定其自身的移动性状态。
在执行完成步骤S101之后,本申请实施例中的方法便执行步骤102:基于所述终端的属性,确定与所述终端对应的配置参数。
在本申请实施例中,所述配置参数包括所述终端允许使用的移动性状态,所述网络侧使用的移动性状态,以及所述网络侧的传输隧道类型中的任意一种或多种。
在具体实施过程中,本领域技术人员还可以根据实际情况配置网络或者终端的其他参数,在本申请实施例中不作限制。
本申请实施例中,配置参数主要分为确定终端允许使用的移动性状态及确定网络侧的配置参数两个部分,下面分别对这两方面进行详细描述。
第一方面,确定终端允许使用的移动性状态,包括:
根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定所述终端允许使用的移动性状态。
本申请实施例中,所述确定所述终端允许使用的移动性状态,包括:
当所述移动性限制为不受限移动限制,且所述可达性要求为支持位置追踪时,确定所述终端允许进入空闲态,以及进入所述空闲态和离开所述空闲态分别对应的状态转移条件。
本申请实施例中,所述确定所述终端允许使用的移动性状态,包括:
当所述移动性限制为不移动等级或受限移动限制,且所述可达性要求为支持位置追踪 或支持节电模式时,确定所述终端允许使用无线资源控制(Radio Resource Control,RRC)层非激活态。
在具体实施过程中,本领域技术人员还可以根据实际使用情况为终端配置其他移动性状态,在本申请实施例中不作限制。
第二方面,确定网络侧的配置参数。所述网络侧的配置参数主要分为确定网络侧使用的移动性状态及所述网络侧的传输隧道类型两个方面。
情况A,确定所述网络侧使用的移动性状态,在本申请实施例中,包括但不限于以下两种实现方式:
第一种方式,请参考图4,包括:
根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定核心网侧与所述终端对应的移动性状态集合;以及
根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定接入网侧与所述终端对应的可使用的移动性状态。
在具体实施过程中,确定所述网络侧使用的移动性状态分为确定核心网侧的移动性状态集合以及接入网侧可使用的移动性状态。当终端附着/接入到网络时,核心网的控制面功能根据终端的能力、终端的移动性限制、所述移动性模型和可达性要求,确定网络侧与终端进行适配的移动性状态。
在本申请实施例中,所述确定核心网侧与所述终端对应的移动性状态集合,包括:
当所述移动性限制为不受限移动限制,且所述可达性要求为支持位置追踪时,确定所述核心网侧的所述移动性状态集合中包含空闲态,以及进入所述空闲态和离开所述空闲态分别对应的状态转移条件。
所述确定接入网侧与所述终端对应的可使用的移动性状态,包括:
当所述移动性限制为不移动等级或受限移动限制,且所述可达性要求为支持位置追踪或支持节电模式时,确定所述接入网侧的所述移动性状态中包含无线资源控制RRC层非激活态。
第二种方式,所述基于所述终端的属性,确定网络侧与所述终端对应的配置参数,包括:
获取所述终端的移动性状态集合;
根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定获取到的所述终端的移动性状态集合是否合适;
在确定获取到的所述终端的移动性状态集合合适时,确定所述网络侧非接入层 (Non-Access Stratum,NAS)移动性状态集合。
在具体实施过程中,当终端附着/接入到网络时,终端自身根据其移动模型,终端能力和配置等确定终端的状态机模型,然后终端向网络服务器指示或隐含指示其确定的状态机类型,例如利用UE usage type指示,即所述终端的移动性状态集合。此时,核心网的控制面功能则根据终端的移动性限制、移动性模型和可达性要求,以及终端的签约信息,判断终端所指示的移动性状态是否合适。所述签约信息可以包括:终端允许使用的usage type;终端的可达性特征等,在本申请实施例中不作限制。当网核心网的控制面功能判断其确定的移动性状态集合为合适时,则根据终端的指示,确定网络侧NAS层移动性状态集合。
在本申请实施例中,在所述确定所述网络侧NAS移动性状态之后,所述方法还包括:
根据所述终端的移动性状态集合、移动性限制和移动性模型中的部分或全部,生成RRC层移动性状态或辅助接入网节点确定移动性状态的参数。
在具体实施过程中,核心网的控制面功能还可以根据终端的指示,终端的移动性限制和/或移动性模型生成RRC层移动性状态,或者是确定接入网节点的移动性状态的辅助参数,例如是否激活RRC_connected_inactive(无线资源控制连接非激活态)状态的指示,或者终端的移动性限制指示、移动性模型指示等。
情况B,确定网络侧的传输隧道类型,包括:
根据所述移动性限制、所述移动性模型、所述会话的类型和所述会话的连续性模式中的部分或全部,确定所述网络侧的传输隧道类型。
本申请实施例中,所述根据所述移动性限制、所述移动性模型、所述会话的类型和所述会话的连续性模式中的部分或全部,确定所述网络侧的传输隧道类型,包括:
当所述移动性限制为任意限制,且所述会话的类型为非IP数据传输时,确定所述传输隧道类型为简单隧道类型;或
当所述移动性限制为不移动限制,且所述会话的类型为普通IP数据传输时,确定所述传输隧道类型为简单隧道类型或者无隧道类型;或
当所述移动性限制为受限移动限制,且所述会话的类型为普通IP数据传输和/或所述会话的连续性模式为无连续性要求时,确定所述传输隧道类型为简单隧道类型或者无隧道类型;或
当所述移动性限制为不受限移动限制,且所述会话的类型为普通IP数据传输时,确定所述传输隧道模型为每终端每会话的隧道类型;或
当所述移动性限制为不受限移动限制,且所述会话的类型为高优先级IP数据传输时,确定所述传输隧道模型为每终端每会话每服务质量的隧道类型。
在具体实施过程中,请参考图5,为确定传输隧道类型的过程。当终端发起协议数据单元(Protocol Data Unit,PDU)会话连接建立请求时,核心网的控制面功能根据终端的移动性限制、移动性模型,会话的类型和连续性模式,确定会话的隧道类型。
在执行完成步骤S102之后,本申请实施例中的方法便执行步骤S103:基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置。
本申请实施例中,所述基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置,包括如下三个方面:
第一方面:
在所述核心网配置所述移动性状态集合,和/或所述状态转移条件;和/或
向所述相关接入节点指示所述移动性状态和/或用于确定所述移动性状态的参数。
在具体实施过程中,当核心网的控制面功能确定出网络侧的移动性状态集合及各个状态的转移条件后,便分别向核心网及接入网的相关节点配置所述参数,以满足终端的移动性要求。
第二方面:
根据所述传输隧道类型,对所述网络侧的用户面功能模块进行配置。
在具体实施过程中,当核心网的控制面功能确定出网络侧用于与终端进行通信的隧道类型后,便根据所述隧道类型配置用户面,建立终端所需的隧道。
第三方面:
向所述终端指示所述终端允许使用的移动性状态和/或所述状态转移条件。
在具体实施过程中,当核心网控制面功能根据终端的属性确定出终端允许使用的移动性状态和/或所述状态转移条件后,便向所述终端发送用于配置移动性状态的指示,所述指示具体为用于对移动性状态的描述,也可以是用于启动所述移动性状态的指示。从而当终端收到对移动性状态的描述后配置移动性状态;或者当终端收到用于启动所述移动性状态的指示后,根据指示启动对应类型的移动性状态。
基于同一发明构思,本申请实施例中提供了一种网络设备,该网络设备的具体实施可参见方法实施例部分的描述,重复之处不再赘述,如图6所示,该网络设备主要包括:
第一确定模块601,用于在终端接入网络时,确定所述终端的属性;
第二确定模块602,用于基于所述终端的属性,确定与所述终端对应的配置参数;
处理模块603,用于基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置。
可能的实施方式中,所述终端的属性包括以下任意一种或多种的组合:
终端的能力;
终端的移动性属性;
终端的会话属性;
终端的移动性状态集合。
可能的实施方式中,所述终端的移动性属性包括移动性限制、移动性模型和可达性要求中的部分或全部;所述终端的会话属性包括会话的类型和/或会话的连续性模式。
可能的实施方式中,所述终端的能力为用于表征以下任意一种信息或多种信息的组合的参数:
所述终端所支持的工作模式;
所述终端所支持的接入技术;
所述终端所支持的移动性状态。
可能的实施方式中,所述配置参数包括所述终端允许使用的移动性状态,所述网络侧使用的移动性状态,以及所述网络侧的传输隧道类型中的任意一种或多种。
可能的实施方式中,所述第二确定模块602具体用于:
根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定所述终端允许使用的移动性状态。
可能的实施方式中,所述第二确定模块602具体用于:
当所述移动性限制为不受限移动限制,且所述可达性要求为支持位置追踪时,确定所述终端允许进入空闲态,以及进入所述空闲态和离开所述空闲态分别对应的状态转移条件。
可能的实施方式中,所述第二确定模块602具体用于:
当所述移动性限制为不移动等级或受限移动限制,且所述可达性要求为支持位置追踪或支持节电模式时,确定所述终端允许使用无线资源控制RRC层非激活态。
可能的实施方式中,所述第二确定模块602具体用于:
根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定核心网侧与所述终端对应的移动性状态集合;以及
根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定接入网侧与所述终端对应的可使用的移动性状态。
可能的实施方式中,所述第二确定模块602具体用于:
当所述移动性限制为不受限移动限制,且所述可达性要求为支持位置追踪时,确定所 述核心网侧的所述移动性状态集合中包含空闲态,以及进入所述空闲态和离开所述空闲态分别对应的状态转移条件。
可能的实施方式中,所述第二确定模块602具体用于:
当所述移动性限制为不移动等级或受限移动限制,且所述可达性要求为支持位置追踪或支持节电模式时,确定所述接入网侧的所述移动性状态中包含无线资源控制RRC层非激活态。
可能的实施方式中,所述第二确定模块602具体用于:
获取所述终端的移动性状态集合;
根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定获取到的所述终端的移动性状态集合是否合适;
在确定获取到的所述终端的移动性状态集合合适时,确定所述网络侧NAS移动性状态集合。
可能的实施方式中,所述第二确定模块602还用于:
根据所述终端的移动性状态集合、移动性限制和移动性模型中的部分或全部,生成RRC层移动性状态或辅助接入网节点确定移动性状态的参数。
可能的实施方式中,所述第二确定模块602具体用于:
根据所述移动性限制、所述移动性模型、所述会话的类型和所述会话的连续性模式中的部分或全部,确定所述网络侧的传输隧道类型。
可能的实施方式中,所述第二确定模块602具体用于:
当所述移动性限制为任意限制,且所述会话的类型为非IP数据传输时,确定所述传输隧道类型为简单隧道类型;或
当所述移动性限制为不移动限制,且所述会话的类型为普通IP数据传输时,确定所述传输隧道类型为简单隧道类型或者无隧道类型;或
当所述移动性限制为受限移动限制,且所述会话的类型为普通IP数据传输和/或所述会话的连续性模式为无连续性要求时,确定所述传输隧道类型为简单隧道类型或者无隧道类型;或
当所述移动性限制为不受限移动限制,且所述会话的类型为普通IP数据传输时,确定所述传输隧道模型为每终端每会话的隧道类型;或
当所述移动性限制为不受限移动限制,且所述会话的类型为高优先级IP数据传输时,确定所述传输隧道模型为每终端每会话每服务质量的隧道类型。
可能的实施方式中,所述处理模块603具体用于:
在所述核心网配置所述移动性状态集合,和/或所述状态转移条件;和/或
向所述相关接入节点指示所述移动性状态和/或用于确定所述移动性状态的参数。
可能的实施方式中,所述处理模块603具体用于:
根据所述传输隧道类型,对所述网络侧的用户面功能模块进行配置。
可能的实施方式中,所述处理模块603具体用于:
向所述终端指示所述终端允许使用的移动性状态和/或所述状态转移条件。
基于同一发明构思,本申请实施例提供了一种网络设备,该网络设备的具体实施可参见方法实施例部分的描述,重复之处不再赘述,如图7所示,该网络设备主要包括处理器701、存储器702和收发机703,其中,收发机703在处理器701的控制下接收和发送数据,存储器702中保存有预设的程序,处理器701读取存储器702中的程序,按照该程序执行以下过程:
终端接入网络时,处理器701确定所述终端的属性;
处理器701基于所述终端的属性,确定与所述终端对应的配置参数;
处理器701基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置。
其中,在图7中,总线架构可以包括任意数量的互联的总线和桥,具体由处理器701代表的一个或多个处理器和存储器702代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起,这些都是本领域所公知的,因此,本文不再对其进行进一步描述。总线接口提供接口。收发机703可以是多个元件,即包括发送机和收发机,提供用于在传输介质上与各种其他装置通信的单元。处理器701负责管理总线架构和通常的处理,存储器702可以存储处理器701在执行操作时所使用的数据。
可能的实施方式中,所述终端的属性包括以下任意一种或多种的组合:
终端的能力;
终端的移动性属性;
终端的会话属性;
终端的移动性状态集合。
可能的实施方式中,所述终端的移动性属性包括移动性限制、移动性模型和可达性要求中的部分或全部;所述终端的会话属性包括会话的类型和/或会话的连续性模式。
可能的实施方式中,所述终端的能力为用于表征以下任意一种信息或多种信息的组合的参数:
所述终端所支持的工作模式;
所述终端所支持的接入技术;
所述终端所支持的移动性状态。
可能的实施方式中,所述配置参数包括所述终端允许使用的移动性状态,所述网络侧使用的移动性状态,以及所述网络侧的传输隧道类型中的任意一种或多种。
可能的实施方式中,处理器701根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定所述终端允许使用的移动性状态。
可能的实施方式中,当所述移动性限制为不受限移动限制,且所述可达性要求为支持位置追踪时,处理器701确定所述终端允许进入空闲态,以及进入所述空闲态和离开所述空闲态分别对应的状态转移条件。
可能的实施方式中,当所述移动性限制为不移动等级或受限移动限制,且所述可达性要求为支持位置追踪或支持节电模式时,处理器701确定所述终端允许使用无线资源控制RRC层非激活态。
可能的实施方式中,处理器701根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定核心网侧与所述终端对应的移动性状态集合;以及
处理器701根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定接入网侧与所述终端对应的可使用的移动性状态。
可能的实施方式中,当所述移动性限制为不受限移动限制,且所述可达性要求为支持位置追踪时,处理器701确定所述核心网侧的所述移动性状态集合中包含空闲态,以及进入所述空闲态和离开所述空闲态分别对应的状态转移条件。
可能的实施方式中,当所述移动性限制为不移动等级或受限移动限制,且所述可达性要求为支持位置追踪或支持节电模式时,处理器701确定所述接入网侧的所述移动性状态中包含无线资源控制RRC层非激活态。
可能的实施方式中,处理器701获取所述终端的移动性状态集合;
处理器701根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定获取到的所述终端的移动性状态集合是否合适;
在确定获取到的所述终端的移动性状态集合合适时,处理器701确定所述网络侧NAS移动性状态集合。
可能的实施方式中,处理器701根据所述终端的移动性状态集合、移动性限制和移动性模型中的部分或全部,生成RRC层移动性状态或辅助接入网节点确定移动性状态的参 数。
可能的实施方式中,处理器701根据所述移动性限制、所述移动性模型、所述会话的类型和所述会话的连续性模式中的部分或全部,确定所述网络侧的传输隧道类型。
可能的实施方式中,当所述移动性限制为任意限制,且所述会话的类型为非IP数据传输时,处理器701确定所述传输隧道类型为简单隧道类型;或
当所述移动性限制为不移动限制,且所述会话的类型为普通IP数据传输时,处理器701确定所述传输隧道类型为简单隧道类型或者无隧道类型;或
当所述移动性限制为受限移动限制,且所述会话的类型为普通IP数据传输和/或所述会话的连续性模式为无连续性要求时,处理器701确定所述传输隧道类型为简单隧道类型或者无隧道类型;或
当所述移动性限制为不受限移动限制,且所述会话的类型为普通IP数据传输时,处理器701确定所述传输隧道模型为每终端每会话的隧道类型;或
当所述移动性限制为不受限移动限制,且所述会话的类型为高优先级IP数据传输时,处理器701确定所述传输隧道模型为每终端每会话每服务质量的隧道类型。
可能的实施方式中,处理器701在所述核心网配置所述移动性状态集合,和/或所述状态转移条件;和/或
处理器701向所述相关接入节点指示所述移动性状态和/或用于确定所述移动性状态的参数。
可能的实施方式中,处理器701根据所述传输隧道类型,对所述网络侧的用户面功能模块进行配置。
可能的实施方式中,处理器701向所述终端指示所述终端允许使用的移动性状态和/或所述状态转移条件。
基于上述技术方案,本申请实施例中,当终端接入网络时,确定所述终端的属性;基于所述终端的属性,确定与所述终端对应的配置参数;基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置,使得终端或者网络侧的参数能够根据终端的属性信息动态调整,从而减小了信令的浪费、状态维护的复杂度及其他资源的浪费,解决了如何动态的为终端的通信过程配置匹配的参数,提高资源利用效率的问题。
本领域内的技术人员应明白,本申请的实施例可提供为方法、系统、或计算机程序产品。因此,本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机 可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然,本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样,倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。

Claims (36)

  1. 一种网络配置方法,其特征在于,包括:
    终端接入网络时,确定所述终端的属性;
    基于所述终端的属性,确定与所述终端对应的配置参数;
    基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置。
  2. 如权利要求1所述的方法,其特征在于,所述终端的属性包括以下任意一种或多种的组合:
    终端的能力;
    终端的移动性属性;
    终端的会话属性;
    终端的移动性状态集合。
  3. 如权利要求2所述的方法,其特征在于,
    所述终端的移动性属性包括移动性限制、移动性模型和可达性要求中的部分或全部;
    所述终端的会话属性包括会话的类型和/或会话的连续性模式。
  4. 如权利要求3所述的方法,其特征在于,所述终端的能力为用于表征以下任意一种信息或多种信息的组合的参数:
    所述终端所支持的工作模式;
    所述终端所支持的接入技术;
    所述终端所支持的移动性状态。
  5. 如权利要求1所述的方法,其特征在于,所述配置参数包括所述终端允许使用的移动性状态,所述网络侧使用的移动性状态,以及所述网络侧的传输隧道类型中的任意一种或多种。
  6. 如权利要求5所述的方法,其特征在于,所述基于所述终端的属性,确定与所述终端对应的配置参数,包括:
    根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定所述终端允许使用的移动性状态。
  7. 如权利要求6所述的方法,其特征在于,所述确定所述终端允许使用的移动性状态,包括:
    当所述移动性限制为不受限移动,且所述可达性要求为支持位置追踪时,确定所述终 端允许进入空闲态,以及进入所述空闲态和离开所述空闲态分别对应的状态转移条件。
  8. 如权利要求6所述的方法,其特征在于,所述确定所述终端允许使用的移动性状态,包括:
    当所述移动性限制为不移动或受限移动,且所述可达性要求为支持位置追踪或支持节电模式时,确定所述终端允许使用无线资源控制RRC层非激活态。
  9. 如权利要求5所述的方法,其特征在于,所述基于所述终端的属性,确定与所述终端对应的配置参数,包括:
    根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定核心网侧与所述终端对应的移动性状态集合;以及
    根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定接入网侧与所述终端对应的可使用的移动性状态。
  10. 如权利要求9所述的方法,其特征在于,所述确定核心网侧与所述终端对应的移动性状态集合,包括:
    当所述移动性限制为不受限移动限制,且所述可达性要求为支持位置追踪时,确定所述核心网侧的所述移动性状态集合中包含空闲态,以及进入所述空闲态和离开所述空闲态分别对应的状态转移条件。
  11. 如权利要求9所述的方法,其特征在于,所述确定接入网侧与所述终端对应的可使用的移动性状态,包括:
    当所述移动性限制为不移动等级或受限移动限制,且所述可达性要求为支持位置追踪或支持节电模式时,确定所述接入网侧的所述移动性状态中包含RRC层非激活态。
  12. 如权利要求5所述的方法,其特征在于,所述基于所述终端的属性,确定与所述终端对应的配置参数,包括:
    获取所述终端的移动性状态集合;
    根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定获取到的所述终端的移动性状态集合是否合适;
    在确定获取到的所述终端的移动性状态集合合适时,确定所述网络侧非接入层NAS移动性状态集合。
  13. 如权利要求12所述的方法,其特征在于,在所述确定所述网络侧NAS移动性状态之后,所述方法还包括:
    根据所述终端的移动性状态集合、移动性限制和移动性模型中的部分或全部,生成RRC层移动性状态或辅助接入网节点确定移动性状态的参数。
  14. 如权利要求5所述的方法,其特征在于,所述基于所述终端的属性,确定与所述终端对应的配置参数,包括:
    根据所述移动性限制、所述移动性模型、所述会话的类型和所述会话的连续性模式中的部分或全部,确定所述网络侧的传输隧道类型。
  15. 如权利要求14所述的方法,其特征在于,所述根据所述移动性限制、所述移动性模型、所述会话的类型和所述会话的连续性模式中的部分或全部,确定所述网络侧的传输隧道类型,包括:
    当所述移动性限制为任意限制,且所述会话的类型为非互联网协议IP数据传输时,确定所述传输隧道类型为简单隧道类型;或
    当所述移动性限制为不移动限制,且所述会话的类型为普通IP数据传输时,确定所述传输隧道类型为简单隧道类型或者无隧道类型;或
    当所述移动性限制为受限移动限制,且所述会话的类型为普通IP数据传输和/或所述会话的连续性模式为无连续性要求时,确定所述传输隧道类型为简单隧道类型或者无隧道类型;或
    当所述移动性限制为不受限移动限制,且所述会话的类型为普通IP数据传输时,确定所述传输隧道模型为每终端每会话的隧道类型;或
    当所述移动性限制为不受限移动限制,且所述会话的类型为高优先级IP数据传输时,确定所述传输隧道模型为每终端每会话每服务质量的隧道类型。
  16. 如权利要求9-13任一项所述的方法,其特征在于,所述基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置,包括:
    在所述核心网配置所述移动性状态集合,和/或所述状态转移条件;和/或
    向所述相关接入节点指示所述移动性状态和/或用于确定所述移动性状态的参数。
  17. 如权利要求14或15所述的方法,其特征在于,所述基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置,包括:
    根据所述传输隧道类型,对所述网络侧的用户面功能模块进行配置。
  18. 如权利要求6-8任一项所述的方法,其特征在于,所述基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置,包括:
    向所述终端指示所述终端允许使用的移动性状态和/或所述状态转移条件。
  19. 一种网络设备,其特征在于,包括:
    第一确定模块,用于在终端接入网络时,确定所述终端的属性;
    第二确定模块,用于基于所述终端的属性,确定与所述终端对应的配置参数;
    处理模块,用于基于所述配置参数,对所述终端进行指示或配置和/或对网络侧的相关网络功能实体或节点进行指示或配置。
  20. 如权利要求19所述的网络设备,其特征在于,所述终端的属性包括以下任意一种或多种的组合:
    终端的能力;
    终端的移动性属性;
    终端的会话属性;
    终端的移动性状态集合。
  21. 如权利要求20所述的网络设备,其特征在于,
    所述终端的移动性属性包括移动性限制、移动性模型和可达性要求中的部分或全部;
    所述终端的会话属性包括会话的类型和/或会话的连续性模式。
  22. 如权利要求21所述的网络设备,其特征在于,所述终端的能力为用于表征以下任意一种信息或多种信息的组合的参数:
    所述终端所支持的工作模式;
    所述终端所支持的接入技术;
    所述终端所支持的移动性状态。
  23. 如权利要求19所述的网络设备,其特征在于,所述配置参数包括所述终端允许使用的移动性状态,所述网络侧使用的移动性状态,以及所述网络侧的传输隧道类型中的任意一种或多种。
  24. 如权利要求23所述的网络设备,其特征在于,所述第二确定模块具体用于:
    根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定所述终端允许使用的移动性状态。
  25. 如权利要求24所述的网络设备,其特征在于,所述第二确定模块具体用于:
    当所述移动性限制为不受限移动限制,且所述可达性要求为支持位置追踪时,确定所述终端允许进入空闲态,以及进入所述空闲态和离开所述空闲态分别对应的状态转移条件。
  26. 如权利要求24所述的网络设备,其特征在于,所述第二确定模块具体用于:
    当所述移动性限制为不移动等级或受限移动限制,且所述可达性要求为支持位置追踪或支持节电模式时,确定所述终端允许使用RRC无线资源控制层非激活态。
  27. 如权利要求23所述的网络设备,其特征在于,所述第二确定模块具体用于:
    根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分 或全部,确定核心网侧与所述终端对应的移动性状态集合;以及
    根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定接入网侧与所述终端对应的可使用的移动性状态。
  28. 如权利要求27所述的网络设备,其特征在于,所述第二确定模块具体用于:
    当所述移动性限制为不受限移动限制,且所述可达性要求为支持位置追踪时,确定所述核心网侧的所述移动性状态集合中包含空闲态,以及进入所述空闲态和离开所述空闲态分别对应的状态转移条件。
  29. 如权利要求27所述的网络设备,其特征在于,所述第二确定模块具体用于:
    当所述移动性限制为不移动等级或受限移动限制,且所述可达性要求为支持位置追踪或支持节电模式时,确定所述接入网侧的所述移动性状态中包含RRC无线资源控制层非激活态。
  30. 如权利要求23所述的网络设备,其特征在于,所述第二确定模块具体用于:
    获取所述终端的移动性状态集合;
    根据所述移动性限制、所述移动性模型、所述可达性要求和所述终端的能力中的部分或全部,确定获取到的所述终端的移动性状态集合是否合适;
    在确定获取到的所述终端的移动性状态集合合适时,确定所述网络侧NAS移动性状态集合。
  31. 如权利要求30所述的网络设备,其特征在于,所述第二确定模块还用于:
    根据所述终端的移动性状态集合、移动性限制和移动性模型中的部分或全部,生成RRC层移动性状态或辅助接入网节点确定移动性状态的参数。
  32. 如权利要求23所述的网络设备,其特征在于,所述第二确定模块具体用于:
    根据所述移动性限制、所述移动性模型、所述会话的类型和所述会话的连续性模式中的部分或全部,确定所述网络侧的传输隧道类型。
  33. 如权利要求32所述的网络设备,其特征在于,所述第二确定模块具体用于:
    当所述移动性限制为任意限制,且所述会话的类型为非IP数据传输时,确定所述传输隧道类型为简单隧道类型;或
    当所述移动性限制为不移动限制,且所述会话的类型为普通IP数据传输时,确定所述传输隧道类型为简单隧道类型或者无隧道类型;或
    当所述移动性限制为受限移动限制,且所述会话的类型为普通IP数据传输和/或所述会话的连续性模式为无连续性要求时,确定所述传输隧道类型为简单隧道类型或者无隧道类型;或
    当所述移动性限制为不受限移动限制,且所述会话的类型为普通IP数据传输时,确定所述传输隧道模型为每终端每会话的隧道类型;或
    当所述移动性限制为不受限移动限制,且所述会话的类型为高优先级IP数据传输时,确定所述传输隧道模型为每终端每会话每服务质量的隧道类型。
  34. 如权利要求27-31任一项所述的网络设备,其特征在于,所述处理模块具体用于:
    在所述核心网配置所述移动性状态集合,和/或所述状态转移条件;和/或
    向所述相关接入节点指示所述移动性状态和/或用于确定所述移动性状态的参数。
  35. 如权利要求32或33所述的网络设备,其特征在于,所述处理模块具体用于:
    根据所述传输隧道类型,对所述网络侧的用户面功能模块进行配置。
  36. 如权利要求24-26任一项所述的网络设备,其特征在于,所述处理模块具体用于:
    向所述终端指示所述终端允许使用的移动性状态和/或所述状态转移条件。
PCT/CN2017/087205 2016-08-19 2017-06-05 一种网络配置方法及网络设备 WO2018032862A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
KR1020197007892A KR20190040034A (ko) 2016-08-19 2017-06-05 네트워크 구성 방법 및 네트워크 장치
EP17840838.1A EP3503471B1 (en) 2016-08-19 2017-06-05 Network configuration method and network device
KR1020217023603A KR102346980B1 (ko) 2016-08-19 2017-06-05 네트워크 구성 방법 및 네트워크 장치
US16/326,534 US10992522B2 (en) 2016-08-19 2017-06-05 Network configuration method and network device
JP2019510311A JP6895511B2 (ja) 2016-08-19 2017-06-05 ネットワーク設定方法及びネットワーク装置

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610697386.5 2016-08-19
CN201610697386.5A CN107769946B (zh) 2016-08-19 2016-08-19 一种网络配置方法及网络设备

Publications (1)

Publication Number Publication Date
WO2018032862A1 true WO2018032862A1 (zh) 2018-02-22

Family

ID=61196266

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/087205 WO2018032862A1 (zh) 2016-08-19 2017-06-05 一种网络配置方法及网络设备

Country Status (7)

Country Link
US (1) US10992522B2 (zh)
EP (1) EP3503471B1 (zh)
JP (1) JP6895511B2 (zh)
KR (2) KR20190040034A (zh)
CN (1) CN107769946B (zh)
TW (1) TWI662816B (zh)
WO (1) WO2018032862A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019145858A (ja) * 2016-06-30 2019-08-29 シャープ株式会社 端末装置、制御装置、及び通信制御方法
BR112020019999A2 (pt) * 2018-04-04 2021-01-26 Guangdong Oppo Mobile Telecommunications Corp., Ltd. método para comunicação, dispositivo de rede e dispositivo terminal
CN112020873B (zh) * 2018-05-03 2022-04-22 华为技术有限公司 用于发送和接收数据包流的方法和相关设备
CN109818807A (zh) * 2019-03-12 2019-05-28 义乌工商职业技术学院 一种移动终端通过计算机共享网络的方法和系统
CN110800329B (zh) * 2019-09-12 2022-07-29 北京小米移动软件有限公司 Ue能力信息的传输方法、装置和存储介质
JP7488848B2 (ja) 2022-06-08 2024-05-22 Kddi株式会社 適切な通信パラメータの選択を可能とする制御装置、基地局装置、制御方法、及びプログラム

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070167182A1 (en) * 2005-12-02 2007-07-19 Tenhunen Jouko U System, apparatus, and method for dynamically configuring application access point settings
CN101155195A (zh) * 2006-09-29 2008-04-02 华为技术有限公司 多播广播业务的实现方法和通信系统、通信设备以及终端
CN101232699A (zh) * 2007-01-23 2008-07-30 华为技术有限公司 确定终端移动性管理类型的方法和系统
CN101772186A (zh) * 2008-12-31 2010-07-07 华为技术有限公司 一种业务信道分配方法、装置及通信系统
WO2011117823A1 (en) * 2010-03-26 2011-09-29 Telefonaktiebolaget L M Ericsson (Publ) Access control for machine-type communication devices

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB0104281D0 (en) 2001-02-21 2001-04-11 Nokia Networks Oy A communication system
CN1898972B (zh) * 2004-12-17 2010-05-05 华为技术有限公司 一种保持会话连续性的方法和系统
US20080095050A1 (en) * 2006-03-07 2008-04-24 Qualcomm Incorporated Method and system for de-assignment of resources in a wireless communication system
US8559321B2 (en) * 2007-06-08 2013-10-15 Qualcomm Incorporated Mobile IP home agent discovery
US8060058B2 (en) * 2007-12-28 2011-11-15 Airvana, Corp. Secure mobile base station connections
US8699426B2 (en) * 2008-03-26 2014-04-15 Qualcomm Incorporated Method and apparatus for resource allocation in wireless communication systems
CN102118796B (zh) * 2009-12-31 2013-04-24 华为技术有限公司 带宽的控制方法、装置及系统
US8761060B2 (en) * 2010-02-12 2014-06-24 Qualcomm Incorporated Controlling access point transmit power based on received access terminal messages
EP3002922A1 (en) 2014-09-30 2016-04-06 Alcatel Lucent Method and system for operating a user equipment device in a private network
US10129799B2 (en) * 2014-11-03 2018-11-13 Alcatel Lucent Mobility management for wireless networks
US20180007528A1 (en) 2015-01-14 2018-01-04 Nokia Solutions And Networks Oy Method, apparatus and system
US10805966B2 (en) * 2016-02-17 2020-10-13 Lg Electronics Inc. Method and terminal for creating, modifying, releasing session in next-generation mobile communication
WO2018006239A1 (zh) * 2016-07-04 2018-01-11 华为技术有限公司 确定用户面协议栈的方法、控制面网元和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070167182A1 (en) * 2005-12-02 2007-07-19 Tenhunen Jouko U System, apparatus, and method for dynamically configuring application access point settings
CN101155195A (zh) * 2006-09-29 2008-04-02 华为技术有限公司 多播广播业务的实现方法和通信系统、通信设备以及终端
CN101232699A (zh) * 2007-01-23 2008-07-30 华为技术有限公司 确定终端移动性管理类型的方法和系统
CN101772186A (zh) * 2008-12-31 2010-07-07 华为技术有限公司 一种业务信道分配方法、装置及通信系统
WO2011117823A1 (en) * 2010-03-26 2011-09-29 Telefonaktiebolaget L M Ericsson (Publ) Access control for machine-type communication devices

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
KR20210095242A (ko) 2021-07-30
US10992522B2 (en) 2021-04-27
TW201807984A (zh) 2018-03-01
JP2019528628A (ja) 2019-10-10
EP3503471B1 (en) 2021-11-17
JP6895511B2 (ja) 2021-06-30
KR102346980B1 (ko) 2022-01-03
US20190207811A1 (en) 2019-07-04
EP3503471A4 (en) 2019-07-17
KR20190040034A (ko) 2019-04-16
CN107769946B (zh) 2020-08-14
TWI662816B (zh) 2019-06-11
CN107769946A (zh) 2018-03-06
EP3503471A1 (en) 2019-06-26

Similar Documents

Publication Publication Date Title
WO2018032862A1 (zh) 一种网络配置方法及网络设备
WO2018153346A1 (zh) 一种网络切片的选择方法及装置
US20230209328A1 (en) Method and device for establishing session
US20210006421A1 (en) Method and device for controlling qos, smf, upf, ue, pcf and an
WO2019184651A1 (zh) 一种通信方法及装置
WO2018126535A1 (zh) 一种会话管理方法及装置
WO2018170687A1 (zh) 一种ambr确定方法及通信实体
WO2022001761A1 (zh) 通信方法及装置
KR102476193B1 (ko) 레이트 제어 방법, 장치, 및 시스템
EP3836639B1 (en) Synchronization cycle determination methods and devices
WO2019223702A1 (zh) 管理pdu会话的方法、装置和系统
WO2018113504A1 (zh) 一种用户面锚点选择方法及装置
WO2018233451A1 (zh) 通信方法、装置和系统
WO2019076308A1 (zh) 终端设备的状态的确定方法、装置及设备
US20220272577A1 (en) Communication method and communication apparatus
WO2017121224A1 (zh) 一种数据传输方法、装置及系统
JP2019501596A (ja) システム情報送信方法、システム情報更新方法、及びデバイス
EP4185010A1 (en) Method and device for accessing local network
WO2019196668A1 (zh) 一种信息发送方法、密钥生成方法以及装置
TW202119855A (zh) 用於行動通訊系統之基地台及其資料傳輸方法
WO2023011107A1 (zh) 会话策略控制方法、网元、存储介质和电子设备
EP3799514B1 (en) Rate control methods, devices, computer program and system
WO2022104740A1 (zh) 一种非公共网络签约信息更新方法及装置
WO2023061207A1 (zh) 一种通信方法、通信装置及通信系统
WO2022237269A1 (zh) 一种通信方法及装置

Legal Events

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

Ref document number: 17840838

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019510311

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20197007892

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017840838

Country of ref document: EP

Effective date: 20190319