JP7371283B1 - A slice controller configured in a mobile communication network and a wireless device that accesses the mobile communication network. - Google Patents

Abstract

An object of the present invention is to control slices set for wireless devices accessing a mobile communication network according to communication conditions. [Solution] A controller includes a receiving unit that repeatedly receives information for determining the traffic amount of each of a plurality of types from a wireless device, and a first determining means for determining whether to map traffic of a type to a first slice or to a second slice of a type different from the first slice; If the determining means determines that the wireless device is mapped to the slice, the mobile communication network is notified of the setting of the first slice for the wireless device, and the wireless device is notified that the first type of traffic is to be transmitted to the first slice. and processing means for performing. [Selection diagram] Figure 4

Description

The present disclosure relates to a slice control technique set for a wireless device accessing a mobile communication network.

Non-Patent Document 1 discloses the results of a demonstration experiment of an SD-WAN (Software Defined Wide Area Network) using a 3GPP (registered trademark) fifth generation (5G) network. According to Non-Patent Document 1, two bases are connected by a transmission path via the Internet and a transmission path via a 5G network and a closed network. In this way, a mobile communication network such as a 5G network can be used as an underlayer network of the SD-WAN.

"SD-WAN demonstration experiment using 5G network confirms its usefulness in IoT and DX usage scenes ~ Network sophistication that takes full advantage of the characteristics of 5G network ~", [Online], 2020 1 23rd, [Searched on January 23rd, 2020], Internet <URL: https://www. nttpc. co. jp/press/2020/01/202001231500. html>

Currently, mobile communication networks are also being virtualized, and wireless devices accessing the mobile communication network are provided with "slices" according to service types. Slices are distinguished from the viewpoint of transmission delay, transmission speed, etc., and currently there are two types: eMMB (Enhanced Mobile Broadband) slices, which are slices for high-speed communication, and URLLC (Ultra) slices, which are slices for highly reliable and low-latency communication. -High Reliability & Low Latency) slices, etc. are defined.

A wireless device connectable to the mobile communication network is installed at a base that uses the mobile communication network as an underlayer network of the SD-WAN. A wireless device relays packets between one or more information processing devices (hereinafter referred to as a personal computer (PC)) and a mobile communication network. That is, the wireless device receives from the first PC a packet transmitted by the first PC at the same base during communication with the second PC at another base, and transmits the packet to the mobile communication network. Further, upon receiving a packet transmitted from the second PC toward the first PC from the mobile communication network, the wireless device transmits the packet to the first PC. Traffic of various characteristics (types) of various applications flows between bases, such as web conferences, file transfers, and e-mails. Additionally, the types of traffic flowing between locations and the amount of traffic change over time. Therefore, it is necessary to control the slices set for wireless devices accessing the mobile communication network, depending on the communication status of each site.

The present disclosure provides a technique for controlling slices set for wireless devices accessing a mobile communication network depending on communication conditions.

According to one aspect of the present disclosure, the controller includes a receiving unit that repeatedly receives information for determining the amount of traffic of each of the plurality of types from a wireless device accessing a mobile communication network, and a receiving unit that repeatedly receives information for determining the traffic amount of each of the plurality of types. determining means for determining whether to map the first type of traffic to a first slice or to a second slice of a type different from the first slice based on a proportion of the traffic amount of the type; If the determining means determines that the first type of traffic mapped to a slice is mapped to the first slice, a process of notifying the mobile communication network of the setting of the first slice for the wireless device; and processing means for notifying the wireless device that a first type of traffic will be transmitted to the first slice.

According to the present disclosure, slices set for wireless devices accessing a mobile communication network can be controlled depending on communication conditions.

An explanatory diagram of communication between bases via SD-WAN. FIG. 1 is a system configuration diagram used to explain the embodiment. The figure which shows the example of the type of slice. FIG. 3 is a sequence diagram of slice control processing according to one embodiment. 1 is a flowchart of processing performed by a controller, according to one embodiment. The figure which shows the example of ToS information. FIG. 2 is a block diagram of a controller according to one embodiment. FIG. 2 is a block diagram of an access device according to one embodiment.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the claimed invention, and not all combinations of features described in the embodiments are essential to the invention. Two or more features among the plurality of features described in the embodiments may be arbitrarily combined. In addition, the same or similar configurations are given the same reference numerals, and duplicate explanations will be omitted.

FIG. 1 shows a state in which three bases 3-1 to 3-3 of a certain business operator are connected to an SD-WAN 4. Note that the number of bases is not limited to three, and may be any number greater than or equal to two. Below, the three bases 3-1 to 3-3 will be collectively referred to as base 3. Traffic between the bases 3 is carried, for example, via a slice for the relevant operator that is generated in the SD-WAN 4. The slice for the operator may be, for example, a slice that connects two bases 3 of the operator end-to-end. The SD-WAN 4 is configured with multiple types of networks as underlayer networks, one of which may be a mobile communication network. The mobile communication network is used for the access section of SD-WAN4. Note that a type of network different from the mobile communication network, such as a PON (Passive Optical Network), may also be used as an underlayer network in the access section of the SD-WAN 4. Therefore, for example, one or more of the three bases 3 may be connected to two or more types of networks, such as a mobile communication network and a PON. Furthermore, one or more of the three bases 3 may be connected only to a different type of network than the mobile communication network.

FIG. 2 is a configuration diagram when at least the mobile communication network 42 is used as the access section of the SD-WAN 4. The access device 30 is a wireless device connectable to the mobile communication network 42, and is called a user equipment (UE) or a wireless device (WD) in, for example, 3GPP (registered trademark). In addition to an air interface for accessing the mobile communication network 42, the access device 30 has a LAN interface for communicating with a PC 32, which is an information processing device, via a local area network (LAN) 31. LAN 31 may be a wired LAN and/or a wireless LAN. The access device 30 may further have an interface for accessing other networks of a different type than the mobile communication network 42, such as a PON. The access device 30 may also be called a packet relay (transfer) device that relays (transfers) packets between the LAN 31 and the mobile communication network 42 or other networks, for example.

The PC 32 at the base 3 can communicate with the PC 32 at other bases 3 via the access device 30. Note that at this time, packets sent from the PC 32 of the base 3 to the PC 32 of the other base 3 and packets received from the PC 32 of the other base 3 are transmitted to the mobile communication network 42 to which the access device 30 is connected or other networks. The data is transmitted via the SD-WAN 4, which serves as the underlayer network.

Mobile communication network 42 has a control system 421. Control system 421 includes one or more devices implementing one or more network functions (NF) of the control plane of mobile communication network 42 . In terms of 3GPP fifth generation (5G) mobile communication networks, examples of NFs are Access and Mobility Management Function (AMF), which manages the mobility of user equipment, and Session Management, which manages PDU sessions. function (SMF), policy control function (PCF) that controls policy, network slice selection function (NSSF) that selects SMF of slice, etc. Note that the mobile communication network 42 is not limited to the fifth generation mobile communication network, but may be any generation mobile communication network in which slices can be set.

The controller 1 is configured to be able to communicate with the control system 421 and the access device 30. Note that the communication between the controller 1 and the access device 30 may be via the mobile communication network 42 or may be via another network different from the mobile communication network 42 such as PON. Although not shown, the mobile communications network 42 may be connected to one or more different data networks (DNs), such as the Internet or a closed network operated by an operator of the mobile communications network 42.

In this embodiment, the mobile communication network 42 provides three types of slices: "default", "low delay", and "wideband", as shown in FIG. 3. Hereinafter, slices of types "default", "low delay", and "wideband" will be referred to as a default slice, a low delay slice, and a wideband slice, respectively. The default slice is a slice that is always set for the access device 30 for the SD-WAN 4, and its characteristics are best effort. The priority of the default slice is the lowest among the three types of slices. A low-latency slice is a slice for providing communication with lower delay than a default slice or a broadband slice. The low delay slice has the highest priority among the three types of slices. As an example, the low-latency slice is a 3GPP URLLC slice. A wideband slice is a slice that provides faster communication than a default slice or a low-latency slice. Wideband slices have higher priority than default slices, but lower priority than low delay slices. As an example, the broadband slice is a 3GPP eMMB slice.

FIG. 4 is a sequence diagram of slice control processing according to this embodiment. When the access device 30 accesses the mobile communication network 42 and becomes connected to the mobile communication network 42, the control system 421 sets a default slice for the SD-WAN 4 to the access device 30. Note that a slice for connecting to the Internet may be set in the access device 30 separately from a slice for the SD-WAN 4, but this is omitted because it is irrelevant to the description of the embodiment. Furthermore, in the following description, "slice" means a slice for the SD-WAN 4, unless it is specified otherwise.

In S1, the control system 421 notifies the controller 1 of the slice type set for the access device 30. Although not explicitly shown in FIG. 4, the control system 421 changes the slice type set for the access device 30 every time the slice type set for the access device 30 is added/deleted. Information for the controller 1 to make a determination is notified to the controller 1.

The access device 30 reports traffic information with other bases 3 to the controller 1 in S2. The traffic information is information for determining the amount of traffic for each traffic type in communication with other bases 3 via the mobile communication network 42. In this embodiment, traffic types are classified into the same three types as slice types. Specifically, traffic for applications that require low latency such as web conferencing and remote control is classified as type R, traffic for applications that transmit large amounts of data such as large file transfers is classified as type B, and traffic for other applications is classified as type B. Let traffic be type N. In the following description, traffic of type R will be referred to as R traffic, traffic of type B will be referred to as B traffic, and traffic of type N will be referred to as N traffic.

In this embodiment, traffic information is information indicating the amount of traffic on the sending side and the amount of traffic on the receiving side for each application. Note that the traffic on the transmitting side is the traffic that the access device 30 transmits toward the mobile communication network 42, and the traffic on the receiving side is the traffic that the access device 30 receives from the mobile communication network 42. Further, it is assumed that determination information for determining which traffic type corresponds to the traffic of each application is stored in advance in the controller 1 and the access device 30.

Therefore, the access device 30 aggregates the amount of traffic transmitted to other bases 3 (sending side) and the amount of traffic received from other bases 3 (receiving side) for each application (App). is reported to the controller 1 as traffic information. In the initial state, only the default slice is set for the access device 30, so all traffic is transmitted and received via the default slice regardless of the application. Although not explicitly shown in FIG. 4, the access device 30 repeatedly reports traffic information to the controller 1. For example, traffic information is reported at predetermined intervals.

In S3, the controller 1 determines the type of slice to be used for traffic for each application based on the traffic information. In other words, the mapping between applications and slice types is determined.

FIG. 5 is a flowchart of the process performed by the controller 1 in S3. Note that before starting the process in FIG. 5, the controller 1 calculates the traffic amount for each traffic type and the total traffic amount for each of the sending side and the receiving side, based on the traffic information received from the access device 30. demand. In the following, the traffic volumes on the sending and receiving sides of R traffic are Rt and Rr, the traffic volumes on the sending and receiving sides of B traffic are Bt and Br, and the traffic volumes on the sending and receiving sides of N traffic are Nt. and Nr. Also, let the total traffic amount on the transmitting side be Tt (=Rt+Bt+Nt), and let the total traffic amount on the receiving side be Tr (=Rr+Br+Nr). As described above, determination information for determining the type of application traffic is set in the controller 1 in advance.

In S21, the controller 1 determines whether either Rr/Tr or Rt/Tt is larger than the first threshold. That is, it is determined whether the ratio of R traffic to the total traffic is larger than the first threshold value for either the transmitting side or the receiving side. If either Rr/Tr or Rt/Tt is greater than the first threshold, the controller 1 determines to map the R traffic to the low delay slice in S22. On the other hand, if both Rr/Tr and Rt/Tt are less than or equal to the first threshold, the controller 1 determines to map the R traffic to the default slice in S23.

In S24, the controller 1 determines whether either Br/Tr or Bt/Tt is larger than the second threshold. That is, it is determined whether the ratio of B traffic to the total traffic is larger than the second threshold value for either the sending side or the receiving side. The second threshold may be the same as or different from the first threshold. If either Br/Tr or Bt/Tt is larger than the second threshold, the controller 1 determines to map the B traffic to the broadband slice in S25. On the other hand, if both Br/Tr and Bt/Tt are equal to or less than the second threshold, the controller 1 determines to map the B traffic to the default slice in S26.

Note that in this embodiment, N traffic is always mapped to the default slice. After determining which type of slice the traffic type should be mapped to, the controller 1 determines which type of slice each application should be mapped to based on the determination information.

Returning to FIG. 4, in S3, after determining the mapping of applications to slices, the controller 1 determines which slices to add or delete. For example, in a state where R traffic is mapped to a default slice, if it is determined to map R traffic to a low delay slice, the controller 1 determines to add a low delay slice. On the other hand, in a state where R traffic is mapped to a low-latency slice, if it is determined to map R traffic to a default slice, the controller 1 determines to delete the low-latency slice. In the case of B traffic, the "low delay slice" in the above description of R traffic becomes "wideband slice". In summary, if a slice of a necessary type is not set for the determined mapping, the controller 1 determines to add a slice of the necessary type, and when a slice of a type that is no longer necessary is generated due to the determined mapping, It is determined that the slice of the unnecessary type is to be deleted. The processes after S4 in FIG. 4 can be performed only when there is a slice to be added or a slice to be deleted. In other words, if there is no slice to be added or deleted, the processes of S4 to S6 can be omitted.

In S4, the controller 1 notifies the control system 421 of slices to be added or deleted. Further, in S4, the controller 1 notifies the control system 421 of mapping information indicating the relationship between the application and the type of slice used for the traffic of the application. When the control system 421 receives a notification of a slice to be notified or deleted from the controller 1, it adds or deletes a slice in accordance with the notification. Further, the control system 421 notifies the access device 30 of the mapping information by, for example, higher layer signaling in S5. The mapping information may be in the form of URSP (user equipment route selection policies), for example.

The access device 30 determines the slice in which to transmit the packet of the application traffic received from the PC 32 according to the mapping information. Therefore, the access device 30 may be configured to notify the PC 32 of type of service (ToS) information in S6. ToS information indicates the relationship between an application or traffic type and a value set in the ToS field of a packet header. The PC 32 sets a value in the ToS field of the header of the packet to be transmitted to another base, according to the ToS information. FIG. 6 shows an example of ToS information. According to FIG. 6, a ToS value "1" is stored in the header of a packet transmitted by an application mapped to a low-latency slice, and a ToS value "2" is stored in the header of a packet transmitted by an application mapped to a wideband slice. is stored, and a ToS value "3" is stored in the header of a packet transmitted by an application mapped to the default slice.

The ToS value may be used by access device 30 to determine the slice in which to transmit packets it receives from PC 32. For example, when a web conference application is mapped to a low-latency slice, the PC 32 sets a ToS value of "1" in the header of a transmission packet from the web conference application. Then, the access device 30 transmits the packet with the ToS value "1" set to the low-delay slice. On the other hand, when the web conference application is mapped to the default slice, the PC 32 sets a ToS value of "3" in the header of the packet sent from the web conference application. Then, the access device 30 transmits the packet with the ToS value "3" set to the default slice. Note that the access device 30 may determine the slice to which the packet is to be transmitted based on other information such as the port number of the packet received from the PC 32 instead of the ToS value. In this case, the process of S6 may be omitted.

With the above configuration, it is possible to control the slices set for the access device 30 that accesses the mobile communication network 42 according to the communication status of the base 3.

In addition, in FIG. 5, the controller 1 determines to use a low-latency or wide-band slice for R traffic and B traffic when the ratio of traffic volume on either the sending side or the receiving side is larger than a threshold value. . However, it is also possible to adopt a configuration in which the determination is made based only on the proportion of the traffic amount on the transmitting side and the traffic amount on the receiving side is not used. Conversely, it is also possible to make the determination based only on the ratio of the traffic amount on the receiving side and not to use the traffic amount on the transmitting side. Furthermore, when the ratio of the traffic amount on both the transmitting side and the receiving side is larger than a threshold value, a configuration may be adopted in which a low delay or wideband slice is used. Further, when using the traffic amount on the transmitting side and the traffic amount on the receiving side, the threshold value can be set to be different between the transmitting side and the receiving side. Note that in S21, it is determined whether Rr/Tr or Rt/Tt is larger than the first threshold value, but it may be configured to determine whether Rr/Tr or Rt/Tt is greater than or equal to the first threshold value. . Similarly, in S24, it is determined whether Br/Tr or Bt/Tt is larger than the second threshold value, but even if the configuration is such that it is determined whether Br/Tr or Bt/Tt is larger than the second threshold value, good.

Furthermore, in the sequence of FIG. 4, in S5, the control system 421 notifies the access device 30 of the mapping information through higher layer signaling, but a configuration may also be adopted in which the controller 1 directly notifies the access device 30. . In this case, the mapping information is transmitted to the access device 30 via the mobile communication network 42 as user data in the user plane of the mobile communication network 42, rather than in control plane signaling of the mobile communication network 42, or as user data in the user plane of the mobile communication network 42. is transmitted to the access device 30 via a different PON or the like.

In addition, in FIG. 4, the access device 30 notifies the controller 1 of the traffic volume for each application, and the controller 1 aggregates the traffic volume for each traffic type such as R traffic and B traffic based on the traffic volume for each application. was. However, the access device 30 may aggregate the amount of traffic for each traffic type, such as R traffic and B traffic, and report it to the controller 1. Furthermore, in this embodiment, the mapping information indicates the mapping between the application type and the slice type, but the mapping information may also indicate the mapping between the traffic type and the slice type. . Even if the mapping information indicates the mapping between the traffic type and the slice type, the access device 30 can determine the mapping between the application type and the slice type based on the determination information.

<Configuration diagram of controller 1>
FIG. 7 is a configuration diagram of the controller 1 according to one embodiment. Each functional block of the controller 1 shown in FIG. 7 can be realized by causing one or more processors of a device including one or more processors and one or more memory devices to execute an appropriate program. . Note that the controller 1 can be realized by one computer (device) or by a plurality of computers that can communicate with each other.

The communication unit 13 has a communication interface with the control system 421 and a communication interface with the access device 30, and each has a transmitting unit and a receiving unit. Note that the communication interface with the control system 421 and the communication interface with the access device 30 may be the same. As explained using FIG. 5, the determination unit 11 determines the mapping between the application or traffic type and the slice type based on the traffic information repeatedly received from the access device 30 via the communication unit 13.

The processing unit 12 performs a process of notifying the mobile communication network 42 of the slice addition or deletion when it becomes necessary to add or delete a slice based on the determination result by the determination unit 11. Furthermore, the processing unit 12 performs a process of notifying the access device 30 of mapping information so that the access device 30 transmits each type of traffic to the corresponding slice according to the determination result. Notification of the mapping information to the access device 30 may be performed, for example, via the control plane of the mobile communication network 42. In this case, the processing unit 12 notifies the control system 421 of the mobile communication network 42 of the mapping information. Additionally, the mapping information may be sent directly from the controller 1 to the access device 30. In this case, the mapping information is transmitted to the access device 30, for example via a user plane of the mobile communication network 42 or a network different from the mobile communication network 42.

<Configuration diagram of access device 30>
FIG. 8 is a configuration diagram of the access device 30 according to one embodiment. Each functional block of the access device 30 shown in FIG. 8 is realized by causing one or more processors of a device including one or more processors and one or more memory devices to execute an appropriate program. obtain.

The communication unit 304 has an air interface for wirelessly communicating with the mobile communication network 42, an interface to the LAN 31, an interface for connecting to another network different from the mobile communication network, and the like. Each interface has a transmitter and a receiver.

The communication processing unit 302 performs traffic relay processing between each interface, that is, packet transfer processing. The reporting unit 301 repeatedly transmits traffic information to the controller 1. The traffic information may be information indicating the amount of traffic for each application or traffic type. The traffic information may also be information indicating the amount of traffic for each direction, that is, the amount of traffic on the sending side and the amount of traffic on the receiving side.

When the communication processing unit 302 receives the mapping information from the controller 1, the communication processing unit 302 uses the slices indicated in the mapping information to transmit traffic to other bases via the mobile communication network 42 according to the mapping information. Send to 42. The notification unit 303 notifies the PC 32 of the ToS information according to the mapping information. The notification can be made to all PCs 32 simultaneously by broadcast, or individually to each PC 32 by unicast, for example.

Note that in the above embodiment, traffic is classified into three types, and slices of three types are used accordingly. However, the number of traffic types is not limited to three, and can be two or more. The number of slice types may be, for example, the same as the number of traffic types. Slices of multiple types include a default slice that is always set.

The controller 1 and the access device 30 according to the present disclosure, when executed by one or more processors of a device having one or more processors, cause the device to function as the controller 1 and the access device 30 described in the above embodiments. It can be realized by a computer program. A computer program may include program instructions executable by one or more processors. The computer program can be stored on a non-transitory computer readable storage medium or distributed over a network.

With the above configuration, slices set for wireless devices accessing a mobile communication network can be controlled according to communication conditions. Therefore, it will be possible to contribute to Goal 9 of the Sustainable Development Goals (SDGs) led by the United Nations: ``Build resilient infrastructure, promote sustainable industrialization, and expand innovation.''

The invention is not limited to the above-described embodiments, and various modifications and changes can be made within the scope of the invention.

11: Judgment unit, 12: Processing unit, 13: Communication unit

Claims (14)

receiving means for repeatedly receiving information for determining the amount of traffic of each of a plurality of types from a wireless device accessing a mobile communication network;
Based on the proportion of the traffic amount of the first type among the plurality of types, it is determined whether the traffic of the first type is mapped to a first slice or to a second slice of a type different from the first slice. a determination means for determining;
If the determining means determines that the first type of traffic mapped to the second slice is mapped to the first slice, a process of notifying the mobile communication network of the setting of the first slice for the wireless device. and a process of notifying the wireless device that the first type of traffic is to be transmitted to the first slice;
It is equipped with a controller. When the determining means determines that the first type of traffic mapped to the first slice is mapped to the second slice, the processing means directs the mobile communication device to delete the first slice for the wireless device. The controller according to claim 1, wherein the controller performs processing of notifying a network, and processing of notifying the wireless device that the first type of traffic is to be transmitted to the second slice. The process of notifying the wireless device that the first type of traffic will be transmitted to the first slice is the process of notifying the mobile communication network that the first type of traffic will be transmitted to the first slice. and
The controller of claim 1, wherein the mobile communication network notifies the wireless device by control plane signaling of the mobile communication network to send the first type of traffic to the first slice. The processing means instructs the wireless device to transmit the first type of traffic to the first slice via a user plane of the mobile communication network or via a network different from the mobile communication network. The controller of claim 1, wherein the controller notifies. The controller of claim 1, wherein the second slice for the wireless device is always configured to the mobile communication network while the wireless device is connected to the mobile communication network. The determining means determines that the first type of traffic is mapped to the first slice when the proportion of the first type of traffic is greater than the threshold, and the determining means determines that the first type of traffic is mapped to the first slice when the proportion of the first type of traffic is greater than the threshold. The controller according to any one of claims 1 to 5, determining to map the first type of traffic to the second slice if it is smaller. 6. The ratio of the amount of traffic of the first type is the ratio of the amount of traffic of the first type transmitted by the wireless device or the amount of traffic of the first type received by the wireless device. Controller described in. The determining means is configured to determine, as a proportion of the first type of traffic, a first proportion of the first type of traffic transmitted by the wireless device and a first proportion of the first type of traffic received by the wireless device. 2 ratio is determined, and if the first ratio is larger than a first threshold value or the second ratio is larger than a second threshold value, it is determined that the first type of traffic is mapped to the first slice; 6. Any one of claims 1 to 5, wherein if the first ratio is smaller than the first threshold and the second ratio is smaller than the second threshold, it is determined that the first type of traffic is mapped to the second slice. The controller according to item 1. The controller according to any one of claims 1 to 5, wherein the information for determining the amount of traffic for each of the plurality of types is information indicating the amount of traffic for each application. The controller according to any one of claims 1 to 5, wherein the first slice is a slice that allows lower delay or wider bandwidth communication than the second slice. A wireless device accessing a mobile communication network, the wireless device comprising:
a reporting means for repeatedly reporting information for determining the amount of traffic of each of the plurality of types to the controller;
Mapping information indicating the type of slice to be used for each of the plurality of types of traffic determined by the controller based on the traffic amount of each of the plurality of types is transmitted directly from the controller or under the control of the mobile communication network. a receiving means for receiving via the plane;
Transmitting means for transmitting traffic of each of the plurality of types to the mobile communication network using a slice of the type indicated by the mapping information;
A wireless device equipped with the transmitting means transmits traffic from one or more communication devices to the mobile communication network;
The wireless device further includes:
12. The communication apparatus according to claim 11, further comprising a notifying means for notifying the one or more communication devices of values to be set in headers of packets of traffic of each of the plurality of types based on the mapping information received by the receiving means. radio equipment. The wireless device according to claim 12, wherein the value set in the header of the packet indicates the type of the slice used to transmit the packet. The wireless device according to claim 12 or 13, wherein the value set in the header of the packet is set in a type of service (ToS) field of the header of the packet.

Images