JP2022511314A - Communication systems and methods for operating communication systems - Google Patents

Abstract

According to one embodiment, the communication system is configured to store for the mobile terminal a limit on the total data rate across multiple communication sessions provided for the mobile terminal in a network slice. The data rate management component includes a data rate quota storage component, a data rate management component, and a notification component configured to notify the data rate management component of the limit value, and the data rate management component is a network. Monitor the data rate of one or more communication connections of the mobile device in the communication system so that the total data rate across multiple communication sessions provided for the mobile device in the slice does not exceed the limit. And configured to control.

Description

The present disclosure relates to communication systems and methods for operating communication systems.

In a communication network such as a 5G mobile wireless communication network, the data rate on the uplink and downlink of a specific network slice, that is, a single UE, is provided by the network slice on the basis of each user device (UE). It may be desirable to introduce and implement limits or quotas on the maximum data rate used by the session.

According to one embodiment, the communication system is
A data rate quota storage component configured to store a total data rate limit specification for the mobile terminal across multiple communication sessions provided for the mobile terminal in a network slice.
Data rate management components and
A notification component configured to notify the data rate management component of the limit value, and the like.
The data rate management component is the said in the communication system so that the total data rate over the plurality of communication sessions provided for the mobile terminal in the network slice does not exceed the limit. It is configured to monitor and control the data rate of one or more communication connections of mobile terminals.

In multiple drawings, similar reference numerals generally refer to the same part throughout different drawings. These drawings are not necessarily to the exact scale, but rather the emphasis is usually on exemplifying the principles of the invention. In the following description, various aspects will be described with reference to the following plurality of drawings.

For example, it shows a wireless communication system configured according to 5G (5th generation) specified by 3GPP (3rd generation partnership project). The definition of the UE rate limit is illustrated. A flow diagram illustrating the propagation of AMBR information (especially UE-Slice-AMBR information, etc.) in 5GS (5G communication system) during UE registration and PDU session establishment is shown. The flow diagram illustrating the propagation of AMBR information (especially UE-Slice-AMBR information, etc.) in 5GS (5G communication system) during UE registration and PDU session establishment according to other embodiments is shown. .. The NEST (Network Slice Type) for a network slice with a first network slice instance and a second network slice instance is illustrated. A communication system according to an embodiment is shown. It is a flow diagram which shows the method for operating a communication system.

The following detailed description will refer to a number of accompanying drawings illustrating specific details and embodiments of the present disclosure in which the invention can be put to practical use. A plurality of other embodiments may be utilized to make structural, logical, and electrical changes without departing from the scope of the invention. The various aspects of the present disclosure are such that some of the plurality of aspects of the present disclosure can be combined with one or more of the other aspects of the present disclosure to form a plurality of new aspects. Not necessarily mutually exclusive.

Various examples corresponding to aspects of the present disclosure will be described below.

Example 1 is a communication system, and the communication system is
A data rate quota storage component configured to store a total data rate limit specification for the mobile terminal across multiple communication sessions provided for the mobile terminal in a network slice.
Data rate management components and
A notification component configured to notify the data rate management component of the limit value, and the like.
The data rate management component is the said in the communication system so that the total data rate over the plurality of communication sessions provided for the mobile terminal in the network slice does not exceed the limit. It is configured to monitor and control the data rate of one or more communication connections of mobile terminals.

Example 2 is the communication system of Example 1, wherein the notification component is configured to notify the data rate management component during a registration procedure for registering the mobile terminal in the communication system. ..

Example 3 is the communication system of Example 1 or 2, wherein the notification component is configured to notify the data rate management component during a registration procedure for registering the mobile terminal in the network slice. Is.

Example 4 is configured such that the notification component notifies the data rate management component during a session establishment procedure for establishing a communication session of the mobile terminal in the network slice. It is a communication system of any one of three.

In Example 5, of Examples 1 to 4, where the data rate allocation storage component stores the maximum data rate or maximum throughput for each mobile terminal for the network slice and specifies the limit. Any one communication system.

In Example 6, the data rate allocation amount storage component is configured to store the subscription information of the mobile terminal, and the designation of the limit value is a part of the subscription information, among Examples 1 to 5. It is one of the communication systems.

Example 7 is a communication system according to any one of Examples 1 to 6, wherein the data rate allocation amount storage component is Unified Data Management.

Example 8 is a communication system according to any one of Examples 1 to 7, wherein the data rate management component is a radio access network component of the communication network of the communication system.

In Example 9, the data rate management component is a core network component of the communication network of the communication system, particularly an access and mobility management function, a session management function, a policy control function, a user plane function, or a network data analysis function. Is a communication system according to any one of Examples 1 to 7.

Example 10 is a communication system according to any one of Examples 1 to 9, wherein the notification component is an access and mobility management function, a session management function, a policy control function, or a network data analysis function.

Example 11 is Example 1, wherein the limit is a total data rate limit across a plurality of communication sessions provided for the mobile terminal across multiple core network instances of the network slice within the network slice. It is a communication system of any one of 10 to 10.

Example 12 is a communication system according to any one of Examples 1 to 11, wherein the data rate is an average data rate or an instantaneous data rate over a certain period of time.

Example 13 includes the first communication network that functions as the home communication network of the mobile terminal and the second communication network that functions as the visited communication network of the mobile terminal, and the data rate allocation amount storage configuration thereof. The element is a part of the first communication network, the notification component is a part of the first communication network and / or a part of the second communication network, and the data rate management component is. A communication system according to any one of Examples 1 to 12, which is a part of the second communication network.

In Example 14, the limit value is the limit value of the total downlink data rate over the plurality of communication sessions provided for the mobile terminal in the network slice and / or the mobile terminal in the network slice. It is a communication system according to any one of Examples 1 to 13, which includes a limit value of the total uplink data rate over the plurality of communication sessions provided for the above.

In Example 15, the communication system comprises a plurality of network slices, the data rate management component further monitors the data rate of one or more communication connections of the mobile terminal in the communication system. The total data rate over the plurality of communication sessions provided for the mobile terminal across the plurality of network slices, which is configured to control, does not exceed the first further limit and / or. , The data rate of each session provided for said mobile terminal is a communication system of any one of Examples 1-14, wherein the data rate of each session does not exceed the second further limit of each.

In Example 16, the data rate management component checks whether the establishment of the communication session exceeds the limit value in response to the communication session establishment request by the mobile terminal, and the establishment of the communication session is said. It is a communication system according to any one of Examples 1 to 15, which is configured to reject the communication session establishment request when the limit value is exceeded.

Example 17 is the said limit value where the data rate storage component is implemented by an Operation, Administration and Maintenance entity, or as part of a local configuration or network operator policy. It is a communication system according to any one of Examples 1 to 16 implemented by the memory of the data rate management component configured to store the designation.

Example 18 is a method for operating a communication system, in which a specification of a limit value of a total data rate over a plurality of communication sessions provided for a mobile terminal in a network slice is stored for the mobile terminal. A step of notifying the data rate management component of the limit value, and the sum of the data rate management components over the plurality of communication sessions provided for the mobile terminal in the network slice. A method comprising monitoring and controlling the data rate of one or more communication connections of the mobile terminal in the communication system so that the data rate does not exceed the limit.

Example 19 is the method of Example 18, comprising notifying the data rate management component during a registration procedure for registering the mobile terminal in the communication system.

Example 20 is the method of Example 18 or 19, comprising notifying the data rate management component during a registration procedure for registering the mobile terminal in the network slice.

Example 21 is any one of Examples 18-20, comprising notifying the data rate management component during a session establishment procedure for establishing a communication session for the mobile terminal in the network slice. The method.

Example 22 is any one of Examples 18-21, comprising storing the maximum data rate or maximum throughput for each mobile terminal for the network slice and specifying the limit value. ..

Example 23 includes the step of storing the subscription information of the mobile terminal, and the designation of the limit value is a method of any one of Examples 18 to 22 which is a part of the subscription information.

Example 24 is any one of Examples 18-23, including the step of storing the specifications by Unified Data Management.

Example 25 is any one of Examples 18-24, wherein the data rate management component is a radio access network component of the communication network of the communication system.

In Example 26, the data rate management component is a core network component of the communication network of the communication system, particularly, an access and mobility management function, a session management function, and a policy control. It is a method of any one of Examples 18 to 24, which is a function (Policy Control Function), a user plane function (User Plane Function), or a network data analytics function (Network Data Analytics Function).

Example 27 is any one of Examples 18-26 that performs notification by an access and mobility management function, a session management function, a policy control function, or a network data analysis function.

Example 28 is the limit value is a limit value of the total data rate over all of the plurality of communication sessions provided for the mobile terminal across the plurality of core network instances of the network slice within the network slice. It is one of the methods of Examples 18 to 27.

Example 29 is any one of Examples 18-28, wherein the data rate is an average data rate or an instantaneous data rate over a period of time.

Example 30 includes and stores a first communication network in which the communication system functions as a home communication network of a mobile terminal and a second communication network in which the communication network functions as a visited communication network of the mobile terminal. Performed and notified by a portion of one communication network is performed by that portion of the first communication network and / or part of the second communication network, and the data rate management component is the second. One of the methods of Examples 18-29, which is part of a communication network.

In Example 31, the limit value is the limit value of the total downlink data rate over the plurality of communication sessions provided for the mobile terminal in the network slice and / or the mobile terminal in the network slice. A method of any one of Examples 18-30, comprising a limit on the total uplink data rate over the plurality of communication sessions provided for.

In Example 32, the communication system comprises a plurality of network slices, the data rate management component further monitors the data rate of one or more communication connections of the mobile terminal in the communication system. The total data rate over the plurality of communication sessions provided for the mobile terminal across the plurality of network slices, thereby being configured to control, does not exceed the first further limit and / or. The data rate for each session provided for said mobile terminal is the method of any one of Examples 18-31, which does not exceed the respective second further limit.

In Example 33, the data rate management component checks whether the establishment of the communication session exceeds the limit value in response to the communication session establishment request by the mobile terminal, and the establishment of the communication session is said. It is one of the methods of Examples 18 to 32 configured to reject the communication session establishment request when the limit value is exceeded.

Example 34 is the said limit value where the data rate storage component is implemented by an Operation, Administration and Maintenance entity, or as part of a local configuration or network operator policy. A method of any one of Examples 18-33 implemented by the memory of the data rate management component that stores the designation.

It should be noted that it is possible to combine one or more of the features of any one of the above examples with any one of the other examples.

According to a further plurality of embodiments, a computer program containing the plurality of instructions and a computer-readable medium are provided, and when the plurality of instructions are executed by the computer, the computer platform can be used in the above-mentioned plurality of examples. Have one of these methods performed.

In the following, various examples will be described in more detail.

FIG. 1 shows a wireless communication system 100, which is configured according to, for example, 5G (5th generation) specified by 3GPP (3rd Generation Partnership Project).

The wireless communication system 100 includes a mobile wireless terminal device 102 such as a UE (user device) and a nano device (NE). The mobile wireless terminal device 102, also referred to as a subscriber terminal, forms the terminal side, while the other components of the wireless communication system 100 described below are part of the mobile wireless communication network side, ie. , Is part of the mobile wireless communication network side (eg, public land mobile network (PLMN), etc.).

Further, the radio communication system 100 includes a radio access network 103, which is configured to provide radio access according to 5G (5th generation) radio access technology (5G new radio). It may include a radio access network node, i.e., a base station. The radio communication system 100 may also be configured according to LTE (Long Term Evolution) or other mobile radio communication standards, but it is noted that 5G is used herein as an example. Should be. Each radio access network node may provide radio communication with the mobile radio terminal device 102 through a radio interface. It should be noted that the radio access network 103 may include any number of radio access network nodes.

The wireless communication system 100 further includes a core network (5GC) 118, which is the access and mobility management function (AMF) 101, unified data management (UDM) 104, and network slice connected to the RAN 103. Includes Selection Function (NSSF) 105. Here and in the following examples, the UDM may further consist of a real UE subscription database, which may be, for example, a UDR (Unified Data). Known as Repository)). The core network 118 further includes AUSF (Authentication Server Function) 114 and PCF (Policy Control Function) 115.

The core network 118 may have multiple network slices 106 and 107, with the operator (also referred to as the Mobile Network Operator, i.e. MNO) for each of the network slices 106 and 107. , Multiple network slice instances 108 and 109 may be created. For example, core network 118 has a first core network slice 106 and a vehicle having three core network slice instances (CNI) 108 for providing Enhanced Mobile Broadband (eMBB). Includes a second core network slice 107 with three core network slice instances (CNI) 109 for providing Vehicle-to-Everyting (V2X) communication.

Typically, when one network slice is deployed, the network function (NF) is instantiated or (if already instantiated) a network slice instance (NSI). The network functions referenced to form and belong to the network slice instance are configured by the network slice instance identification information.

Specifically, in the example shown, each instance 108 of the first core network slice 106 has a first Session Management Function (SMF) 110 and a first user plane function (User). Each instance 109 of the second core network slice 107 includes a second core network slice 107, including a Plane Function (UPF) 111, and a second session management function (SMF) 112 and a second user plane function (UPF) 113. SMF110 and 112 are functions for processing PDU (Protocol Data Unit) sessions, that is, create, update, and delete PDU sessions, and use the User Plane feature (UPF) for session context. ) Is a function for managing.

S-NSSAI (Single Network Slice Selection Assistance information) identifies network slices and identifies them.
--Slice / Service Type (SST), which refers to the expected behavior of network slices in terms of characteristics and services.
--Slice Differentiator (SD), which is selective information that complements one or more slices / service types to discriminate between multiple network slices of the same slice / service type.
Consists of.

The NSSAI may include one or more S-NSSAI.

The permitted NSSAI is, for example, the NSSAI provided by the serving PLMN (Public Land Mobile Network) during the registration procedure, and the permitted NSSAI is the serving PLMN for the current registration area. Shows the value of S-NSSAI allowed by the network for the UE in.

The configured NSSAI is the NSSAI provided in the UE. The configured NSSAI may be applicable to one or more PLMNs.

The requested NSSAI is the NSSAI that the UE provides to the network during registration to establish a PDU session to the requested network slice.

The core network 118 may further include a Network Data Analytics Function (NWDAF) 117. NWDAF is responsible for providing network analysis information in response to requests from multiple network functions. For example, the network function may request specific analytical information about the load level of a particular network slice. Alternatively, the network function uses a subscribe service to inform NWDAF whether the load level of a network slice changes or reaches a certain threshold. May be guaranteed. The NWDAF117 may have interfaces to various network functions on the mobile wireless communication network side, such as AMF101, SMF110 and 112, and PCF115. For simplicity, only the interface between NWDAF117 and AMF101 is shown.

The wireless communication system 100 may further include an OAM (Operation, Administration and Maintenance) function (or entity) 116, wherein the OAM function is, for example, (their connections are simplified. Implemented by one or more OAM servers connected to RAN103 and core network 118 (although not shown for).

According to various embodiments, in a 5G radio communication system such as the radio communication system 100, the allocation amount associated with the network slice is defined. This means that, for example, the data rates provided by network slices 106 and 107, that is, the total data rate of all PDU sessions for a single UE serving in the network, is limited. Means.

For example, a GST (Generic Network Slice Template) for network slices 106 and 107 may have the attribute "maximum downlink throughput", which is the "maximum downlink throughput". In, the maximum data rate supported by the network slices 106 and 107 is described for each UE 102. These parameters may be used to provide multiple different contract qualities such as gold, silver, and bronze. Here is one example in Table 1.

Similarly, GSTs (general purpose network slice templates) for network slices 106 and 107 may have the attribute "maximum uplink throughput" (in addition to "maximum downlink throughput" in some cases), which ". "Maximum uplink throughput" describes the maximum data rate supported by network slices 106 and 107 for each UE 102 in the uplink. These parameters may be used to provide multiple different contract qualities such as gold, silver, and bronze. One example is similar to the example in Table 1 for the downlink.

It should be noted that the GSMA (GSM Association) defines a Generic Slice Template (GST) to provide a standardized list of attributes for characterizing network slice types. Is.

In the following, a plurality of embodiments that enable the implementation of the maximum data rate (also referred to as throughput) for each network slice as the above maximum data rate will be described. In particular, their maximum data rate is related to the UE's (ie, provided to the UE's) data rate limit for the network slice, and the aggregate of PDU sessions that use the slice is the network slice in DL and UL. Guarantee that the rate will be limited to the rate defined for. This has a potential impact on the method of signaling rate limits and subscription data (eg, propagating such rate limits per slice to the RAN per UE). include.

FIG. 2 illustrates the definition of the rate limit for UE201.

UE200 corresponds to UE107, for example. UE200 is illustrated using three network slices 201, 202, 203.

UDM104 stores subscription data for UE200. According to various embodiments, this subscription data is a subscribed UE-AMBR (Subscribed UE-AMBR), a subscribed Session-AMBR (Subscribed Session-AMBR), and a subscribed Slice-. Includes UE-AMBR (Subscribed Slice-UE-AMBR) (AMBR stands for "aggregate maximum bit rate").

Subscribed UE-AMBR is the largest aggregate shared across all non-guaranteed (non-GBR) quality of service (QoS) flows according to the user's subscription (UE102). Uplink maximum bit rate (MBR) and downlink maximum bit rate.

A subscribed Session-AMBR (Subscribed Session-AMBR) is the largest aggregate uplink and downlink MBR shared across all of the multiple non-GBR QoS flows within each PDU session. Each PDU session is established for each DNN (data network name) and S-NSSAI (ie, network slices 201, 202, 203).

The subscribed Slice-UE-AMBR (Subscribed Slice-UE-AMBR) is the largest aggregated uplink MBR and downlink shared across all multiple non-GBR QoS flows for all multiple PDU sessions. It is an MBR and all of those multiple PDU sessions are established for their respective DNNs and S-NSSAIs, respectively.

FIG. 3 illustrates the propagation of AMBR information (particularly UE-Slice-AMBR information) in 5GS (5G communication system) during UE registration and PDU session establishment. Is shown.

In the flow, for example, UE301 corresponding to UE102, for example, RAN302 corresponding to RAN103, for example, AMF303 corresponding to AMF101, for example, SMF304 corresponding to one of SMF110 and 112, for example, UDM104. UDM305, and PCF306 corresponding to, for example, PCF115.

In FIG. 3, a message exchange or operation related to registration is indicated by "R", and a message exchange or operation related to PDU session establishment is indicated by "P". Message exchanges or operations related to both are indicated by "RP".

In the case of registration (ie, following the registration request by UE301), in 307R, AMF303 acquires UE-AMBR and Slice-UE-AMBR during the registration process. AMF303 stores UE-AMBR and Slice-UE-AMBR as part of the UE context in the 308R.

In the case of PDU session establishment (ie, following the PDU session establishment request by UE301), at 307P, AMF303 acquires UE-AMBR and Slice-UE-AMBR during the PDU session establishment procedure. SMF304 stores Session-AMBR and / or Slice-UE-AMBR in 308P, for example, as part of the session management context for the UE.

In 309P, if the AMF has the Slice-UE-AMBR information available during the registration procedure, the AMF 303 may provide the Slice-UE-AMBR to the SMF 304, which is the PDU session establishment procedure. At that time, Session-AMBR is provided to AMF303.

At 310R, PCF306 acquires the subscribed UE-AMBR and Slice-UE-AMBR when establishing the AMPolicy association. The PCF may update the UE-AMBR as well as the Slice-UE-AMBR (if any) based on the operator policy.

At 310P, PCF306 acquires the subscribed Session-AMBR when establishing the SMPolicy association.

In both registration and PDU establishment, AMF303 provides RAN with UE-AMBR, Slice-UE-AMBR, and Session-AMBR at 311RP.

RAN302 stores UE-AMBR, Slice-UE-AMBR, and Session-AMBR in 312RP.

At 313RP, UE301 receives UE-AMBR, Slice-UE-AMBR, and Session-AMBR information (from AMF303 and SMF304, respectively).

FIG. 3 shows that AMF303 propagates Slice-UE-AMBR in 5GS including RAN302 and UE301, which can also be done by SMF304, for example SMF304. It should be noted that such Slice-UE-AMBR is taken from UDM305 and then propagated further to AMF303, RAN302, PCF306 and UE301.

In addition, Slice-UE-AMBR is also configured to fulfill RAN (or, generally, data rate quotas) in roaming scenarios (eg, Home-routed scenarios, etc.). It should be noted that it may be communicated to the component). In such a case, the Home PLMN (H-PLMN) may communicate the data rate allocation amount to the Visited PLMN (V-PLMN) of the mobile terminal. For example, the V-PLMN AMF retrieves a UE subscription, including Slice-UE-AMBR, from the H-PLMN UDM during the registration procedure. Alternatively, the H-PLMN SMF is the V-PLMN in the Nsmf_PDUSession_Create response message (ie, the response message to the PDU session establishment request).
Provide Slice-UE-AMBR to SMF.

In addition, Slice-UE-AMBR and / or Session-AMBR are provided by DN-AAA (Data Network-Authentication, Authorization and Accounting) when establishing a PDU session. It should be noted that / or may be updated.

In addition, the NRM (Network Resource Model) in OAM (eg, OAM116, etc.) may be enhanced for AMF, SMF, and RAN with the maximum data rate per slice attribute per UE. good.

FIG. 4 illustrates the propagation of AMBR information (particularly UE-Slice-AMBR information) in 5GS (5G communication system) during UE registration and PDU session establishment according to other embodiments. Shows.

Similar to the embodiment of FIG. 4, in the flow, for example, one of UE401 corresponding to UE102, for example RAN402 corresponding to RAN103, for example AMF403 corresponding to AMF101, for example SMF110 and 112. Corresponding SMF404s, such as UDM405 corresponding to UDM104, and, for example, PCF406 corresponding to PCF115 are included.

On the other hand, the flow additionally includes, for example, NSSF416 corresponding to NSSF105.

Instead of 307R and 307P, NSSF416 gets Slice-UE-AMBR from UDM405 of 407.

In 408, AMF403 gets Slice-UE-AMBR when calling the Nnssf_NSSelection_Get service operation during registration.

Then, 409, 410, 411, 412, 413, 414, 415 are executed in the same manner as 308R, 309P, 308P, 310R, 311RP, 312RP, and 313RP, respectively.

A (NEST) network slice may have multiple network slice instances. The following description provides an approach for dealing with aspects of having multiple network slice instances for NEST.

Network slice instances may be associated with one or more S-NSSAIs, and S-NSSAI may be associated with one or more network slice instances, depending on the operator's operational or deployment needs. Multiple network slice instances associated with the same S-NSSAI may be located in the same tracking area or different tracking areas.

NEST (Network Slice Type) applies to network slices, even when supported by multiple network slice instances. This means, for example, if the "maximum number of terminals" that a network slice supports in NEST is specified and there are multiple network slice instances associated with this network slice (S-NSSAI). The total number of terminals supported by all of the multiple network slice instances in is not greater than the maximum number of terminals specified by NEST. It should be noted that a NEST is a GST that is filled with multiple values.

FIG. 5 illustrates NEST 501 and 502 of a network slice 503 with a first network slice instance 504 and a second network slice instance 505.

NEST501 specifies that the maximum downlink throughput per UE for network slice 503 is 1 [Mbps]. This maximum downlink throughput is, for example, the maximum downlink throughput of the first network slice instance 504 is 400 [kbps], and the maximum downlink throughput of the second network slice instance 505 is 600 [kbps]. As such, it may be distributed, for example, across those two network slice instances 504 and 505. NEST may specify this in detail, as illustrated by the second NEST version 502.

Although FIG. 5 relates to the downlink throughput limit, this may apply similarly to the uplink throughput limit.

In summary, various embodiments provide the communication system illustrated in FIG.

FIG. 6 shows a communication system 600 according to one embodiment.

The communication system 600 includes a data rate quota storage component 601, which is a plurality of communications provided for mobile terminals within a network slice. It is configured to store the specification of the total data rate limit over the session for mobile terminal 602.

The communication system 600 further includes a data rate management component 603 and a notification component 604 configured to notify the data rate management component 603 of limits.

The data rate management component 603 is one of the mobile terminals 602 in the communication system or one of the mobile terminals 602 so that the total data rate over multiple communication sessions provided for the mobile terminal in the network slice does not exceed the limit. It is configured to monitor and control the data rates of multiple communication connections. For example, if the data rate management component knows that the total data rate over those multiple communication sessions, including both existing and new communication sessions, will exceed the limit. The data rate management component 603 is already pre-established even when the total data rate across multiple communication sessions provided for mobile devices in the network slice has not yet exceeded the limit1 In addition to one or more existing communication sessions, new PDU establishment requests sent by the UE to establish new communication sessions within a network slice may be rejected.

According to various embodiments, in other words, the maximum data rate (also referred to as throughput) per mobile device and per network slice, i.e., that is, mobile (eg, may be subscriber dependent). Information about the data rate limit per mobile device (which may be unique to the device) and per network slice is provided by the notification component 604 to the component that fulfills the limit, i.e., the mobile device (for the network slice). (For) Communicate to components that ensure that the limit is not exceeded.

This maximum data rate is the uplink data rate, the downlink data rate, the uplink data rate, and the downlink data rate, respectively (that is, the limit value is the downlink data rate limit value and the uplink data rate limit value. It may be a pair of limits including) or may refer to the sum of the uplink data rate and the downlink data rate.

The component which enforces the limit may be a component of the RAN. For example, the component may be a component of the MAC (Medium Access Control) layer, which is with the communication network so that the resulting data rate does not exceed the limit. Perform packet scheduling for connections to and from mobile terminals. Alternatively, the component that fulfills the limit value may be a network function in a mobile core network such as AMF, SMF, PCF, or NWDAF, or a network component in OAM, which network function. Alternatively, the network component may have information about what is the current total data rate that has not yet exceeded the limits across multiple communication sessions provided for mobile terminals within the network slice. Later, if the UE sends a request to establish a new PDU session that may require a certain data rate to be provided, and as a result, the limit will be exceeded. In the mobile core network, the network function rejects the new PDU establishment request sent by the UE. In contrast, if the rate limit is still not exceeded, the network function within the mobile core network will accept the new PDU establishment request.

The component that monitors the current total data rate over multiple communication sessions provided for mobile terminals within a network slice is a component of RAN or a network function within a mobile core network such as UPF. You may. The current data rate of the communication session is then used to calculate the total data rate over all of the multiple communication sessions offered for the mobile device in the network slice, averaged over a period of time. It may be a data rate or a momentary data rate. These one or more monitoring components then further provide such data rate information for a communication session to other network functions within the mobile core network such as SMF, PCF, or NWDAF. Other network functions may include such data either by subscription criteria (eg, by subscription / notification method) or by on-demand criteria (eg, request / response, etc.). Request to get rate information. OAM may also collect such data rate information from one or more of these monitoring components.

A communication system may include one or more communication networks, where one or more communication connections are communication connections between a mobile terminal and one (or more) of the plurality of communication networks. May be good.

The approach in Figure 6 makes it possible to implement rate / throughput limits per UE and per network slice in 5GS, including roaming scenarios. For example, the operator fulfills rate / throughput limits (which may include maximum downlink data rates and / or uplink data rates) per UE and per network slice, for example in a 5G communication system (5GS). May be good.

In addition to the roaming scenario, the approach in Figure 6 is PNI-NPN (Public Network).
It is also applicable in scenarios with Integrated-Non-Public Network), some of the multiple 5GC network functions may be managed by the PNI-NPN, and some of the multiple 5GC network functions. , Provided by PLMN.

Communication system 600 performs, for example, the method illustrated in FIG.

FIG. 7 shows a flow diagram 700 illustrating a method for operating a communication system.

In 701, the specification of the limit value of the total data rate over a plurality of communication sessions provided for the mobile terminal is stored in the network slice.

At 702, the data rate management component is notified about the limit value.

In 703, the data rate management component is one of the mobile terminals in the communication system so that the total data rate over multiple communication sessions provided for the mobile terminal in the network slice does not exceed the limit. Or control the data rate of multiple communication connections.

A plurality of components of a communication system (eg, data rate storage component, notification component, data rate management component, etc.) may be implemented by, for example, one or more circuits. A "circuit" may be understood as any kind of logical implementation entity, which is a special purpose circuit stored in memory, firmware, or any combination thereof. It may be software to be executed or software to be executed by the processor. In this way, the "circuit" may be a hard-wired logic circuit or, for example, a programmable logic circuit such as a microprocessor. The "circuit" may be software executed by a processor such as, for example, any kind of computer program. Other types of implementation of any of the respective functions described above may also be understood as "circuits".

According to another example, the communication network configuration is one or more network slices of the communication network, a UE subscription data component configured to specify the maximum rate / throughput within the network slice per UE. And network slices configured to search the UE subscription data component for the maximum rate / throughput within the network slice and ensure that such limits are maintained within the UE network slice. Contains management components supported by.

Management components may include network functions within a core network such as, for example, AMF, SMF or PCF.

Management components may include functions within a radio access network (RAN).

Information about the maximum rate / throughput in the network slice per UE may also be shared among multiple PLMNs for roaming support. In such cases, the serving network is the network that determines what to do for the roaming UE, so the maximum authorized rate / throughput depends on the policy of the serving network (V-PLMN). It may be different from the maximum subscribed rate / throughput.

Although a plurality of specific embodiments have been described, those skilled in the art will not deviate from the intent and scope of the embodiments of the present disclosure as defined by the appended claims. In it, you should understand that it is possible to make various changes in form and detail. The scope is thus indicated by the appended claims, and therefore all modifications belonging to the meaning and scope of the claims are intended to be covered.

Claims (15)

It ’s a communication system,
Data configured to store a limit value for the total data rate across all of the multiple communication sessions provided for the mobile terminal within the network slice for the network slice and for the mobile terminal. Rate allocation storage components and
Data rate management components and
A notification component configured to notify the data rate management component of the limit value, and the like.
The data rate management component is in the communication system so that the total data rate over all of the plurality of communication sessions provided for the mobile terminal in the network slice does not exceed the limit. Configured to monitor and control the data rate of one or more communication connections of said mobile terminal.
Communications system. The communication system according to claim 1, wherein the notification component is configured to notify the data rate management component during a registration procedure for registering the mobile terminal in the communication system. The communication system according to claim 1 or 2, wherein the notification component is configured to notify the data rate management component during a registration procedure for registering the mobile terminal in the network slice. Of claims 1 to 3, the notification component is configured to notify the data rate management component during a session establishment procedure for establishing a communication session for the mobile terminal in the network slice. The communication system according to any one of the above. The communication system according to any one of claims 1 to 4, wherein the data rate management component is a radio access network component of the communication network of the communication system. The data rate management component is a core network component of the communication network of the communication system, particularly an access and mobility management function, a session management function, a policy control function, a user plane function, or a network data analysis function. The communication system according to any one of Items 1 to 5. The communication system according to any one of claims 1 to 6, wherein the notification component is an access and mobility management function, a session management function, a policy control function, or a network data analysis function. The limit value is a limit value of the total data rate over all of the plurality of communication sessions provided for the mobile terminal across the plurality of core network instances of the network slice within the network slice. The communication system according to any one of 7. The communication system according to any one of claims 1 to 8, wherein the data rate is an average data rate or an instantaneous data rate over a certain period of time. The communication system includes a first communication network that functions as a home communication network of a mobile terminal and a second communication network that functions as a visited communication network of the mobile terminal, and the data rate allocation amount storage component is said. A part of the first communication network, the notification component is a part of the first communication network and / or a part of the second communication network, and the data rate management component is the second. The communication system according to any one of claims 1 to 9, which is a part of a communication network. The limit value is provided for the mobile terminal in the network slice and / or the limit value of the total downlink data rate over the plurality of communication sessions provided for the mobile terminal in the network slice. The communication system according to any one of claims 1 to 10, which includes a limit value of the total uplink data rate over the plurality of communication sessions. The communication system includes a plurality of network slices, and the data rate management component further monitors and controls the data rate of one or more communication connections of the mobile terminal in the communication system. Configured and thereby
The total data rate over the communication sessions provided for the mobile terminal across the network slices does not exceed the first further limit and / or
The communication system according to any one of claims 1 to 11, wherein the data rate of each session provided for the mobile terminal does not exceed the respective second further limit. The data rate management component checks whether the establishment of the communication session exceeds the limit value in response to the request for establishing the communication session by the mobile terminal, and the establishment of the communication session exceeds the limit value. The communication system according to any one of claims 1 to 12, wherein the communication session establishment request is rejected in the case of the case. The data rate quota storage component is implemented by an operation, management, and maintenance entity, or is configured to store the specification of the limit as part of a local configuration or network operator policy. The communication system according to any one of claims 1 to 13, which is implemented by the memory of the data rate management component. A method for operating a communication system,
A step of storing the specification of the total data rate limit for all of the plurality of communication sessions provided for the mobile terminal in the network slice for the network slice and for the mobile terminal.
The step of notifying the data rate management component of the limit value, and
In the communication system, the data rate management component ensures that the total data rate over all of the plurality of communication sessions provided for the mobile terminal in the network slice does not exceed the limit. Including the step of monitoring and controlling the data rate of one or more communication connections of said mobile terminal.
Method.

Images