WO2021124571A1 - Terminal and wireless base station - Google Patents

Abstract

In the present invention, a UE (200) executes a first header compression according to a first header compression protocol, and a second header compression according to a second header compression protocol. The UE (200) transmits, to a network, first session information indicating the number of first sessions to which the first header compression can be applied.　

Description

Terminals and wireless base stations

The present disclosure relates to terminals and radio base stations that execute processing related to header compression.

The 3rd Generation Partnership Project (3GPP) is a specification of Long Term Evolution (LTE), LTE-Advanced (hereinafter referred to as LTE including LTE-Advanced), and 5th generation mobile communication system for the purpose of further speeding up LTE. Specifications (also called 5G, New Radio (NR) or Next Generation (NG)) are also underway.

Release 16 of 3GPP is a protocol that compresses the header of Ethernet frames in a wired LAN (Local Area Network), specifically, in an NR network, in order to support the Industrial Internet of Things (IIoT). A certain Ethernet Header Compression (EHC) is being studied (Non-Patent Document 1 and Non-Patent Document 2).

3GPP TR 38.825 V16.0.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on NR Industrial Internet of Things (IoT); (Release 16), 3GPP, March 2019 "New WID: Support of NR Industrial Internet of Things (IoT)", RP-190728, 3GPP TSG RAN Meeting # 83, 3GPP, March 2019

However, when EHC is introduced, there are concerns about the following problems. Specifically, the terminal (User Equipment, UE) needs to execute not only EHC but also processing according to RObust Header Compression (ROHC), which is a compression protocol such as an IP header that has been conventionally defined.

Therefore, if both EHC and ROHC are applied at the same time, there is a possibility that the capacity of the terminal will be exceeded. In particular, when the terminal shares memory for EHC and ROHC processing, such a situation is likely to occur, and the terminal cannot properly execute the processing related to header compression.

Therefore, the following disclosure was made in view of such a situation, and even if two types of header compression are executed at the same time, a terminal and a wireless base that can appropriately execute the processing related to the header compression. The purpose is to provide the station.

One aspect of the present disclosure is a control unit (control unit 250) that executes first header compression (EHC) according to the first header compression protocol and second header compression (ROHC) according to the second header compression protocol. , A terminal (UE200) including a transmission unit (radio transmission unit 110) that transmits first session information (maxNumberEHC-contextSessions) indicating the number of first sessions to which the first header compression can be applied to the network.

One aspect of the present disclosure is another radio base station (gNB100B) to which a terminal (UE200) that executes the first header compression according to the first header compression protocol and the second header compression according to the second header compression protocol is connected. ), And the first session information indicating the number of first sessions to which the first header compression according to the first header compression protocol can be applied in the terminal to the other radio base. It is a radio base station (eNB100A) including a transmission unit (inter-node message processing unit 140) for transmitting to the station.

FIG. 1 is an overall schematic configuration diagram of the wireless communication system 10. FIG. 2 is a diagram showing a protocol stack in a network including a remote controller 50 and a device 60 connected using Ethernet. FIG. 3 is a functional block configuration diagram of the UE 200. FIG. 4 is a functional block configuration diagram of the eNB 100A. FIG. 5 is a functional block configuration diagram of the gNB 100B. FIG. 6 is a diagram showing an Ethernet header format and a target of header compression by EHC. FIG. 7 is a diagram showing a notification sequence of the number of ROHC and EHC sessions between the UE 200 and the network. FIG. 8 is a diagram showing a notification sequence of the number of ROHC and EHC sessions between UE200, eNB100A and gNB100B. FIG. 9 is a diagram showing an example of the hardware configuration of the eNB 100A, gNB 100B, and UE 200.

Hereinafter, embodiments will be described based on the drawings. The same functions and configurations are designated by the same or similar reference numerals, and the description thereof will be omitted as appropriate.

(1) Overall Schematic Configuration of Wireless Communication System FIG. 1 is an overall schematic configuration diagram of the wireless communication system 10 according to the present embodiment. The wireless communication system 10 is a wireless communication system that complies with Long Term Evolution (LTE) and 5G New Radio (NR). In addition, LTE may be called 4G, and NR may be called 5G.

In addition, LTE and NR may be interpreted as wireless access technology (RAT), and in this embodiment, LTE may be referred to as a first wireless access technology, and NR may be referred to as a second wireless access technology. Good.

The wireless communication system 10 includes Evolved Universal Terrestrial Radio Access Network 20 (hereinafter, E-UTRAN20) and Next Generation-Radio Access Network 30 (hereinafter, NG RAN30). Further, the wireless communication system 10 includes a terminal 200 (hereinafter, UE200, User Equipment).

E-UTRAN20 includes eNB100A, which is a wireless base station that complies with LTE. NG RAN30 includes gNB100B, which is a radio base station according to 5G (NR). The E-UTRAN20 and NGRAN30 (may be eNB100A or gNB100B) may be simply referred to as a network.

The eNB100A, gNB100B and UE200 support carrier aggregation (CA) that uses multiple component carriers (CC), and dual connectivity (DC) that simultaneously transmits component carriers between multiple NG-RAN Nodes and the UE. be able to.

The eNB100A, gNB100B and UE200 execute wireless communication via a wireless bearer, specifically, SRB Signaling Radio Bearer (SRB) or DRB Data Radio Bearer (DRB).

In the present embodiment, the eNB 100A constitutes the master node (MN) and the gNB100B constitutes the secondary node (SN). Multi-Radio Dual Connectivity (MR-DC), specifically, E-UTRA-NR Dual Connectivity ( EN-DC) is executed.

In other words, UE200 supports dual connectivity that connects to eNB100A and gNB100B.

The eNB100A is included in the master cell group (MCG), and the gNB100B is included in the secondary cell group (SCG). That is, gNB100B is an SN contained in SCG.

The eNB 100A and gNB 100B may be called a radio base station or a network device. In particular, in the present embodiment, the eNB 100A may constitute a radio base station, and the gNB 100B may constitute another radio base station.

Wireless communication system 10 is compatible with Industrial Internet of Things (IIoT). Specifically, the remote controller 50 can be connected to the network (NG RAN30), and the device 60 can be connected to the UE 200. The remote controller 50 remotely controls the device 60 via the 3GPP network.

More specifically, the remote controller 50 can be connected to a network, specifically, a User Plane Function (UPF), using Ethernet, which is a type of wired LAN (Local Area Network). Similarly, device 60 can be connected to UE200 using Ethernet.

Also, in the network, multiple header compressions can be applied. Specifically, RObust Header Compression (ROHC) and Ethernet Header Compression (EHC) can be applied.

ROHC may be interpreted as a protocol or algorithm that compresses the headers of various IP packets.

ROHC is specified by RFC 5795. For IPv4, the size of the uncompressed IP header is 40 bytes, and for IPv6, the size of the uncompressed IP header is 60 bytes. The network performs compression and decompression of IP headers according to ROHC.

EHC may be interpreted as a protocol or algorithm that reduces the overhead caused by the transport of Ethernet headers.

Ethernet frames can be forwarded over the network as an Ethernet PDU session type. Such header compression is especially useful when the payload size is relatively small compared to the overall size of the frame. Such a situation is especially assumed in IIoT using Ethernet.

FIG. 2 shows a protocol stack in a network that includes a remote controller 50 and a device 60 that are connected using Ethernet.

As shown in FIG. 2, Ethernet is a first layer (L1) and second layer (L2) protocol in the OSI (Open Systems Interconnection) reference model. The remote controller 50 is connected to the UPF via Ethernet and the device 60 is connected to the UE 200 via Ethernet.

Within the network, specifically UPF, 5G-AN (AccessNetwork) and UE200, the physical layer (PHY), medium access control layer (MAC), wireless link control layer (RLC), and packet data convergence. Protocol layer (PDCP) and ServiceDataAdaptationProtocol (SDAP) are supported.

Note that gNB100B may be included in 5G-AN, and 5G-AN may be interpreted in the same manner as NG RAN30.

PDUs including Ethernet headers are sent and received between UE200 and UPF. EHC applies between UE200 and UPF.

(2) Functional block configuration of the wireless communication system Next, the functional block configuration of the wireless communication system 10 will be described. Specifically, the functional block configuration of eNB100A, gNB100B and UE200 will be described. In the description of the functional block configuration, the outline of the function of each device will be described, and the details of the operation of each device will be described later.

(2.1) UE200
FIG. 3 is a functional block configuration diagram of the UE 200. As shown in FIG. 3, the UE 200 includes a wireless transmission unit 210, a wireless reception unit 220, a ROHC processing unit 230, an EHC processing unit 240, and a control unit 250.

The wireless transmitter 210 transmits an uplink signal (UL signal) according to LTE or NR. The radio receiver 220 receives a downlink signal (DL signal) according to LTE or NR.

The wireless transmission unit 210 can transmit information (first session information) indicating the number of sessions (number of first sessions) to which EHC (first header compression) can be applied to the network. In the present embodiment, the wireless transmission unit 210 constitutes a transmission unit.

Specifically, the wireless transmitter 210 can transmit maxNumberEHC-contextSessions, which is a type of UE200 capability information (UECapability), to the network.

Further, the wireless transmission unit 210 networks information (second session information) indicating the number of sessions to which ROHC can be applied (number of second sessions) when EHC and ROHC (second header compression) are executed at the same time. Can be sent to.

Specifically, the wireless transmitter 210 can perform maxNumberROHC-eHC-contextSessions, which is a kind of capability information (UECapability) of UE200. The wireless transmitter 210 can also transmit maxNumberROHC-ContextSessions, which is information indicating the number of sessions to which ROHC can be applied, to the network.

MaxNumberEHC-contextSessions, maxNumberROHC-eHC-contextSessions and maxNumberROHC-ContextSessions are transmitted from UE200 to the network. May be included in UE Capability Information.

In addition, UE Capability Information may include an EHC maximum context ID indicating the maximum context ID of EHC. The maxNumberEHC-contextSessions, maxNumberROHC-eHC-contextSessions and EHCmaximumcontextID will be described later.

ROHC processing unit 230 executes processing related to ROHC. Specifically, the ROHC processing unit 230 executes an IP header compression process (UL direction) according to ROHC and an IP header decompression process (DL direction) according to ROHC.

ROHC is specified in Chapter 5.7.3 of RFC 5795 and 3GPP TS 38.323. RFC 5795 Chapter 5.1.2 (Per-Channel Parameters) etc. stipulates MAX_CID. MAX_CID is a non-negative integer and may be interpreted as the highest CID number used by ROHC processor 230. MAX_CID may mean that it can provide enough memory resources to host at least the MAX_CID + 1 context.

Also, one CID value may always be reserved for uncompressed flow. MAX_CID may be configured by a higher layer (such as RRC).

The EHC processing unit 240 executes processing related to EHC. Specifically, the EHC processing unit 240 executes an Ethernet header compression process (UL direction) according to EHC and an Ethernet decompression process (DL direction) according to EHC.

The Ethernet header subject to EHC may contain at least the following information.

-Destination address-Source (source) address-802.1Q tag-Length / type The Ethernet header includes information other than these, but the information does not have to be subject to EHC. However, we do not refuse to be subject to EHC. EHC will be described later.

The control unit 250 controls each functional block constituting the UE 200. In particular, in the present embodiment, the control unit 250 executes EHC, which is an Ethernet header compression process according to the EHC protocol (first header compression protocol).

Further, the control unit 250 executes ROHC, which is an IP header compression process according to the ROHC protocol (second header compression protocol).

Specifically, the control unit 250 controls the ROHC processing unit 230 and the EHC processing unit 240 to execute header compression and decompression processing according to the ROHC and EHC. The ROHC processing unit 230 and the EHC processing unit 240 may share a memory for header compression and decompression processing according to ROHC and EHC.

ROHC and EHC can be applied to multiple sessions at the same time. That is, the UE 200 can configure one or more ROHC sessions and one or more EHC sessions. Note that the same period may mean that the ROHC session and the EHC session are set simultaneously (simultaneously), but it does not necessarily have to be completely simultaneous in time, and both sessions are performed within a certain period of time. May mean that is set. The session may be called by another name such as context.

(2.2) eNB100A
FIG. 4 is a functional block configuration diagram of the eNB 100A. As shown in FIG. 4, the eNB 100A includes a wireless transmission unit 110, a wireless reception unit 120, a UE capability management unit 130, an inter-node message processing unit 140, and a control unit 150.

The wireless transmission unit 110 transmits a downlink signal (DL signal) according to LTE. The wireless receiver 120 receives an uplink signal (UL signal) according to LTE.

The UE capacity management unit 130 manages the capacity of the UE 200 (UE Capability). Specifically, the UE capability management unit 130 can send an inquiry (UE Capability Inquiry) regarding the capability of the UE 200 to the UE 200.

In addition, the UE capability management unit 130 can receive a response (UE Capability Information) from the UE 200 to the UE Capability Inquiry.

The inter-node message processing unit 140 executes various message processing between the eNB 100A (MN) and the gNB 100B (SN). Specifically, the inter-node message processing unit 140 processes the Inter-node RRC message.

In particular, in the present embodiment, the inter-node message processing unit 140 provides gNB100B (another radio base) with information (first session information) indicating the number of sessions (first session number) to which EHC according to the EHC protocol can be applied in UE200. Can be sent to the station). In the present embodiment, the inter-node message processing unit 140 constitutes a transmission unit.

Inter-node RRC message is specified in 3GPP TS38.331 Chapter 11.2 etc. In the present embodiment, the inter-node message processing unit 140 transmits CG-ConfigInfo to the gNB100B.

In addition to CG-ConfigInfo, the inter-node message may include, for example, a message transmitted from eNB100A to gNB100B such as SgNBmodificationRequest and SgNBReleaseRequest, and a response message from gNB100B to eNB100A such as SgNBmodificationRequestAck and SgNBReleaseRequestAck. Further, the inter-node message is not limited to these messages, and may include, for example, SgNB release required, SgNB addition request, and the like.

CG-ConfigInfo may include maxNumberEHC-contextSessionsSN, which is a type of UE200 capability information (UECapability).

The inter-node message processing unit 140 can transmit information (second session information) indicating the number of sessions to which ROHC can be applied (second session information) to gNB100B when UE200 executes EHC and ROHC at the same time.

Specifically, CG-ConfigInfo may include maxNumberROHC-eHC-contextSessionsSN, which is a kind of UE200 capability information (UECapability).

The control unit 150 controls each functional block constituting the eNB 100A. In particular, in the present embodiment, communication with the gNB100B to which the EHC according to the EHC protocol and the UE200 executing the ROHC according to the ROHC protocol are connected is controlled.

In addition, the control unit 150 executes UE200 and dual connectivity corresponding to LTE and NR.

Specifically, the control unit 150 sets the UE200 and the wireless bearer, and executes dual connectivity to LTE and NR by the UE200 in cooperation with the gNB100B. In this embodiment, E-UTRA-NR Dual Connectivity (EN-DC) is described as an example, but the type of dual connectivity is not particularly limited to EN-DC, and Multi-RAT Dual Connectivity (MR). -DC), including NR-E-UTRA Dual Connectivity (NE-DC), NG-E-UTRA NR Dual Connectivity (NG-EN-DC) and NR-NR Dual Connectivity (NR-DC) Good.

Further, the wireless bearer set as UE200 may include Signaling Radio Bearer (SRB) and Data Radio Bearer (DRB).

(2.3) gNB100B
FIG. 5 is a functional block configuration diagram of the gNB 100B. As shown in FIG. 5, the gNB100B includes a wireless transmission unit 160, a wireless reception unit 170, an inter-node message processing unit 180, and a control unit 190. In the following, the same parts as the eNB100A will be omitted as appropriate.

The wireless transmitter 160 transmits a downlink signal (DL signal) according to NR. The radio receiver 170 receives an uplink signal (UL signal) according to NR.

The inter-node message processing unit 180 executes various message processing between the eNB 100A (MN) and the gNB 100B (SN).

Specifically, the inter-node message processing unit 180 receives an Inter-node RRC message such as CG-ConfigInfo from the eNB 100A. Further, the inter-node message processing unit 180 may transmit another inter-node message, for example, a response message such as SgNBmodificationRequestAck or SgNBReleaseRequestAck to the eNB 100A.

The control unit 190 controls each functional block constituting the gNB 100B. In particular, in the present embodiment, the control unit 190 executes the UE 200 and dual connectivity corresponding to LTE and NR. The control unit 190 sets the UE200 and the wireless bearer, and cooperates with the eNB100A to execute dual connectivity to LTE and NR by the UE200.

(3) Operation of Wireless Communication System Next, the operation of the wireless communication system 10 will be described. Specifically, the operation related to header compression (ROHC and EHC) between the UE 200 and the network will be described.

(3.1) Outline of EHC First, the outline of EHC will be described. As mentioned above, EHC is specified in 3GPP TR 38.825 and so on.

FIG. 6 shows the Ethernet header format and the target of header compression by EHC. As shown in FIG. 6, the EHC compresses the Ethernet header.

The fields compressed by the EHC protocol are DESTINATION ADDRESS, SOURCE ADDRESS, 802.1Q TAG, and TYPE.

On the other hand, the PREAMBLE, SFD, and FCS fields do not need to be considered in the EHC protocol because they are not transmitted within the network (5GS).

The EHC compressor and EHC decompressor save the original header field information as an "EHC context". Each EHC context may be identified by a unique identifier called the Context ID (CID).

EHC may be configured individually for UL and DL for each DRB. The concept of CID may be used so that the EHC compressor and the EHC decompressor associate the CID with the content of the Ethernet header.

The EHC compressor may send at least one packet with the full header and CID in the case of an Ethernet flow that creates a new context (because the EHC compressor establishes the context).

The EHC header format may include CID, header format display (full header and compressed header), and the like. The EHC function may be provided by PDCP, the EHC header may be located behind the SDAP header and may be encrypted.

The EHC compressor may send the complete header and CID via the PDCP data PDU to establish the context.

Also, ROHC and EHC may be independent (however, as mentioned above, UE200 may share memory for both processes). Both ROHC and EHC may be set for DRB.

In establishing a context (session), the decompression program may send explicit feedback to the EHC compressor after the context is established, that is, when a complete header packet is received in the CID.

When the EHC compressor receives the feedback, it determines that the context has been established normally, and may transmit the compressed header packet from this point.

(3.2) Operation example Next, an operation example related to notification of the number of ROHC and EHC sessions applicable to the UE 200 will be described.

(3.2.1) Operation example 1
FIG. 7 shows a notification sequence of the number of ROHC and EHC sessions between the UE 200 and the network.

As shown in FIG. 7, the network sends a UE Capability Inquiry inquiring about the capability of the UE 200 to the UE 200 (S10).

UE200 returns UECapabilityInformation based on the received UECapabilityInquiry (S20).

In this operation example, UE Capability Information includes EHC maximum context ID. The EHC maximum context ID may mean that the MAX_CID for ROHC can be reused and can provide at least sufficient memory resources to host the EHC maximum context ID + 1 context.

(3.2.2) Operation example 2
In this operation example, maxNumberEHC-contextSessions and / or maxNumberROHC-eHC-contextSessions are notified from UE200.

(3.2.2.1) Operation example 2-1
In this operation example as well, the UE 200 returns UE Capability Information based on the received UE Capability Inquiry, as in the operation example 1.

In this operation example, as shown in FIG. 7, UECapabilityInformation includes maxNumberEHC-contextSessions. As described above, maxNumberEHC-contextSessions indicates the number of sessions (which may be context) to which EHC can be applied (the number of first sessions). The number of sessions is usually the maximum value, but it does not necessarily have to be the maximum value (hereinafter, the same applies to the number of sessions).

maxNumberEHC-contextSessions should be a value that does not exceed the number of sessions that UE200 can set when UE200 executes EHC and ROHC at the same time, that is, even if maxNumberROHC-ContextSessions and maxNumberEHC-contextSessions are set at the same time. It is preferable to set it.

Thereby, in particular, even when the UE200 shares the memory for the EHC and ROHC processing, the UE200 can appropriately execute the processing related to the EHC and the ROHC, respectively.

(3.2.2.2) Operation example 2-2
In this operation example, as shown in FIG. 7, UE Capability Information includes maxNumberROHC-eHC-contextSessions). In operation example 2-1, maxNumberEHC-contextSessions that can be used when EHC is applied alone (ROHC is not applied) are defined, but in this operation example, EHC and ROHC are used while using maxNumberEHC-contextSessions. MaxNumber ROHC-eHC-contextSessions, which indicates the number of ROHC sessions applied when executing at the same time, is used. Sessions that do not perform header compression according to ROHC may be excluded.

In addition, the maximum context ID (MAX_CID) applied when EHC and ROHC are executed at the same time may be specified respectively. For example, the MAX_CID for ROHC applied when EHC and ROHC are executed at the same time may be 1024, and the MAX_CID for EHC may also be 1024. When EHC and ROHC are applied (set) independently, MAX_CID may be 16384, respectively, as in 3GPP Release-15.

Furthermore, information indicating the number of EHC sessions applied when EHC and ROHC are executed at the same time (for example, may be called maxNumberEHC-rOHC-contextSessions) may be transmitted.

Alternatively, information indicating the total number of sessions of EHC and ROHC applied when EHC and ROHC are executed at the same time may be transmitted.

(3.2.3) Operation example 3
In this operation example, the eNB 100A that receives the UE Capability Information from the UE 200 notifies the gNB 100B that executes dual connectivity of maxNumberEHC-contextSessionsSN and / or maxNumberROHC-eHC-contextSessionsSN.

(3.2.3.1) Operation example 3-1
FIG. 8 shows a notification sequence of the number of ROHC and EHC sessions between UE200, eNB100A and gNB100B.

As shown in FIG. 8, the eNB 100A receives UE Capability Information from the UE 200 (S105). Note that the UE Capability Information may be transmitted as a response to the UE Capability Inquiry transmitted to the UE 200, as shown in FIG.

The eNB100A sends an Inter-node RRC message to the gNB100B (S110). Specifically, the eNB100A transmits CG-ConfigInfo to the gNB100B.

As mentioned above, gNB100B can configure SN and execute dual connectivity with UE200 together with eNB100A.

CG-ConfigInfo may include maxNumberEHC-contextSessionsSN. maxNumberEHC-contextSessionsSN indicates the number of sessions (which may be context) to which UE200 can apply EHC to and from the SN (number of first sessions). The value of maxNumberEHC-contextSessionsSN may be based on maxNumberEHC-contextSessionsSN included in UECapabilityInformation received from UE200.

MaxNumberEHC-contextSessionsSN may be the maximum value of the EHC context (session) that can be set by the SN for the wireless bearer (SN terminated bearer) that is terminated by gNB100B (SN).

GNB100B can determine the number of EHC sessions set for UE200 based on maxNumberEHC-contextSessionsSN. As a result, even when executing UE200 and dual connectivity (MR-DC), the eNB100A (MN) and gNB100B (SN) can set an appropriate number of EHC sessions within the range that does not exceed the capacity of the UE200.

After that, eNB100A and gNB100B execute processing such as SgNB Modification as necessary (S120).

(3.2.3.2) Operation example 3-2
In this operation example, as shown in FIG. 8, CG-ConfigInfo includes maxNumberROHC-eHC-contextSessionsSN. In operation example 3-1, maxNumberEHC-contextSessionsSN that can be used when EHC is applied alone (ROHC is not applied) is defined, but in this operation example, EHC and ROHC are used while using maxNumberEHC-contextSessionsSN. MaxNumber ROHC-eHC-contextSessionsSN, which indicates the number of ROHC sessions applied when executing at the same time, is used.

(4) Action / Effect According to the above-described embodiment, the following action / effect can be obtained. Specifically, the UE 200 can transmit information (first session information: maxNumberEHC-contextSessions) indicating the number of sessions to which EHC (first header compression) can be applied (number of first sessions) to the network.

Therefore, the network can recognize the number of sessions to which EHC can be applied to UE200, and can set an appropriate number of EHC sessions. As a result, the UE 200 can appropriately execute the processing related to the header compression. In particular, when header compression according to EHC and ROHC is executed at the same time, even if the UE 200 shares a memory for EHC and ROHC processing, the processing related to the header compression can be appropriately executed.

In the present embodiment, when UE200 executes EHC and ROHC (second header compression) at the same time, information indicating the number of sessions to which ROHC can be applied (number of second sessions) (second session information: maxNumberROHC- eHC-contextSessions) can be sent to the network.

Therefore, the network can recognize the number of sessions applicable to UE200 for each of EHC and ROHC. As a result, the UE 200 can more reliably execute the processing related to the header compression even when the header compression according to the EHC and the ROHC is executed at the same time.

In addition, the eNB100A can transmit information (first session information: maxNumberEHC-contextSessionsSN) indicating the number of sessions (first session number) to which EHC can be applied according to the EHC protocol in UE200 to gNB100B (other radio base stations).

Therefore, when UE200 executes dual connectivity with eNB100A and gNB100B, the processing related to the header compression can be appropriately executed.

In the present embodiment, the eNB 100A is information indicating the number of sessions to which ROHC can be applied (the number of second sessions) when the UE 200 executes EHC and ROHC at the same time (second session information: maxNumberROHC-eHC-contextSessionsSN). Can be sent to gNB100B.

Therefore, the network can recognize the number of sessions applicable to UE200 for each of EHC and ROHC, and UE200 can more reliably perform header compression according to EHC and ROHC at the same time. Can perform processing related to compression.

(5) Other Embodiments Although the embodiments have been described above, it is obvious to those skilled in the art that various modifications and improvements are possible without being limited to the description of the embodiments.

For example, as described above, a session may be read as a context, or may be called a context session or the like. Alternatively, the session may be interpreted in the same way as a connection, a path, and the like.

Further, the block configuration diagrams (FIGS. 2 to 4) used in the description of the above-described embodiment show the blocks of the functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Further, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically coupled device, or two or more physically or logically separated devices can be directly or indirectly (eg, for example). , Wired, wireless, etc.) and may be realized using these plurality of devices. The functional block may be realized by combining the software with the one device or the plurality of devices.

Functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, and assumption. Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but limited to these I can't. For example, a functional block (constituent unit) for functioning transmission is called a transmitting unit or a transmitter. As described above, the method of realizing each of them is not particularly limited.

Further, the above-mentioned eNB100A, gNB100B and UE200 (the device) may function as a computer for processing the wireless communication method of the present disclosure. FIG. 9 is a diagram showing an example of the hardware configuration of the device. As shown in FIG. 9, the device may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

In the following explanation, the word "device" can be read as a circuit, device, unit, etc. The hardware configuration of the device may be configured to include one or more of the devices shown in the figure, or may be configured not to include some of the devices.

Each functional block of the device (see FIGS. 2 to 4) is realized by any hardware element of the computer device or a combination of the hardware elements.

Further, for each function in the device, by loading predetermined software (program) on the hardware such as the processor 1001 and the memory 1002, the processor 1001 performs the calculation, controls the communication by the communication device 1004, and the memory. It is realized by controlling at least one of reading and writing of data in 1002 and storage 1003.

Processor 1001 operates, for example, an operating system to control the entire computer. The processor 1001 may be composed of a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, and the like.

Further, the processor 1001 reads a program (program code), a software module, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. As the program, a program that causes a computer to execute at least a part of the operations described in the above-described embodiment is used. Further, the various processes described above may be executed by one processor 1001 or may be executed simultaneously or sequentially by two or more processors 1001. Processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunication line.

The memory 1002 is a computer-readable recording medium, and is composed of at least one such as ReadOnlyMemory (ROM), ErasableProgrammableROM (EPROM), Electrically ErasableProgrammableROM (EEPROM), and RandomAccessMemory (RAM). May be done. The memory 1002 may be referred to as a register, a cache, a main memory (main storage device), or the like. The memory 1002 can store a program (program code), a software module, or the like that can execute the method according to the embodiment of the present disclosure.

The storage 1003 is a computer-readable recording medium, for example, an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, an optical magnetic disk (for example, a compact disk, a digital versatile disk, or a Blu-ray). It may consist of at least one (registered trademark) disk), smart card, flash memory (eg, card, stick, key drive), floppy (registered trademark) disk, magnetic strip, and the like. Storage 1003 may be referred to as auxiliary storage. The recording medium described above may be, for example, a database, server or other suitable medium containing at least one of memory 1002 and storage 1003.

The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, or the like.

The communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). It may be composed of.

The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).

In addition, each device such as the processor 1001 and the memory 1002 is connected by the bus 1007 for communicating information. Bus 1007 may be configured using a single bus or may be configured using different buses for each device.

Further, the device includes hardware such as a microprocessor, a digital signal processor (Digital Signal Processor: DSP), an Application Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), and a Field Programmable Gate Array (FPGA). The hardware may implement some or all of each functional block. For example, processor 1001 may be implemented using at least one of these hardware.

Further, the notification of information is not limited to the mode / embodiment described in the present disclosure, and may be performed by using another method. For example, information notification includes physical layer signaling (for example, Downlink Control Information (DCI), Uplink Control Information (UCI), upper layer signaling (eg, RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block)). (MIB), System Information Block (SIB)), other signals or a combination thereof. RRC signaling may also be referred to as an RRC message, for example, RRC Connection Setup. ) Message, RRC Connection Reconfiguration message, etc. may be used.

Each aspect / embodiment described in the present disclosure includes LongTermEvolution (LTE), LTE-Advanced (LTE-A), SUPER3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system ( 5G), FutureRadioAccess (FRA), NewRadio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UltraMobileBroadband (UMB), IEEE802.11 (Wi-Fi (registered trademark)) , IEEE802.16 (WiMAX®), IEEE802.20, Ultra-WideBand (UWB), Bluetooth®, and other systems that utilize appropriate systems and at least one of the next-generation systems extended based on them. It may be applied to one. In addition, a plurality of systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A and 5G).

The order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in the present disclosure may be changed as long as there is no contradiction. For example, the methods described in the present disclosure present elements of various steps using exemplary order, and are not limited to the particular order presented.

In some cases, the specific operation performed by the base station in the present disclosure may be performed by its upper node. In a network consisting of one or more network nodes having a base station, various operations performed for communication with a terminal are performed by the base station and other network nodes other than the base station (for example, MME or). It is clear that it can be done by at least one of (but not limited to, S-GW, etc.). Although the case where there is one network node other than the base station is illustrated above, it may be a combination of a plurality of other network nodes (for example, MME and S-GW).

Information and signals (information, etc.) can be output from the upper layer (or lower layer) to the lower layer (or upper layer). Input / output may be performed via a plurality of network nodes.

The input / output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input / output information can be overwritten, updated, or added. The output information may be deleted. The input information may be transmitted to another device.

The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value (Boolean: true or false), or by comparing numerical values (for example, a predetermined value). It may be done by comparison with the value).

Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched with execution. Further, the notification of predetermined information (for example, the notification of "being X") is not limited to the explicit one, but is performed implicitly (for example, the notification of the predetermined information is not performed). May be good.

Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or by any other name, is an instruction, instruction set, code, code segment, program code, program, subprogram, software module. , Applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, features, etc. should be broadly interpreted.

Further, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, a website, where the software uses at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and wireless technology (infrared, microwave, etc.). When transmitted from a server, or other remote source, at least one of these wired and wireless technologies is included within the definition of transmission medium.

The information, signals, etc. described in this disclosure may be represented using any of a variety of different techniques. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description are voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may be represented by a combination of.

Note that the terms explained in the present disclosure and the terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Also, the signal may be a message. Further, the component carrier (CC) may be referred to as a carrier frequency, a cell, a frequency carrier, or the like.

The terms "system" and "network" used in this disclosure are used interchangeably.

In addition, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, relative values from predetermined values, or using other corresponding information. It may be represented. For example, the radio resource may be one indicated by an index.

The names used for the above parameters are not limited in any respect. Further, mathematical formulas and the like using these parameters may differ from those explicitly disclosed in this disclosure. Since various channels (eg, PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are in any respect limited names. is not it.

In this disclosure, "Base Station (BS)", "Wireless Base Station", "Fixed Station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", " "Access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "cell group" Terms such as "carrier" and "component carrier" can be used interchangeably. Base stations are sometimes referred to by terms such as macrocells, small cells, femtocells, and picocells.

The base station can accommodate one or more (for example, three) cells (also called sectors). When a base station accommodates multiple cells, the entire base station coverage area can be divided into multiple smaller areas, each smaller area being a base station subsystem (eg, a small indoor base station (Remote Radio)). Communication services can also be provided by Head: RRH).

The term "cell" or "sector" refers to a base station that provides communication services in this coverage, and part or all of the coverage area of at least one of the base station subsystems.

In the present disclosure, terms such as "mobile station (MS)", "user terminal", "user equipment (UE)", and "terminal" may be used interchangeably. ..

Mobile stations can be used by those skilled in the art as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless. It may also be referred to as a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, or the like. At least one of the base station and the mobile station may be a device mounted on the mobile body, the mobile body itself, or the like. The moving body may be a vehicle (eg, car, airplane, etc.), an unmanned moving body (eg, drone, self-driving car, etc.), or a robot (manned or unmanned). ) May be. It should be noted that at least one of the base station and the mobile station includes a device that does not necessarily move during communication operation. For example, at least one of a base station and a mobile station may be an Internet of Things (IoT) device such as a sensor.

Further, the base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, communication between a base station and a mobile station has been replaced with communication between a plurality of mobile stations (for example, it may be called Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.). Each aspect / embodiment of the present disclosure may be applied to the configuration. In this case, the mobile station may have the functions of the base station. In addition, words such as "up" and "down" may be read as words corresponding to communication between terminals (for example, "side"). For example, an uplink channel, a downlink channel, and the like may be read as a side channel.

Similarly, the mobile station in the present disclosure may be read as a base station. In this case, the base station may have the functions of the mobile station.
The radio frame may be composed of one or more frames in the time domain. Each one or more frames in the time domain may be referred to as a subframe.
Subframes may further consist of one or more slots in the time domain. The subframe may have a fixed time length (eg, 1 ms) that is independent of numerology.

The numerology may be a communication parameter that applies to at least one of the transmission and reception of a signal or channel. Numerology includes, for example, SubCarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, wireless frame configuration, transmission / reception. At least one of a specific filtering process performed by the machine in the frequency domain, a specific windowing process performed by the transmitter / receiver in the time domain, and the like may be indicated.

The slot may be composed of one or more symbols (Orthogonal Frequency Division Multiple Access (OFDM) symbol, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) in the time domain. Slots may be unit of time based on numerology.

The slot may include a plurality of mini slots. Each minislot may consist of one or more symbols in the time domain. The mini-slot may also be referred to as a sub-slot. A minislot may consist of a smaller number of symbols than the slot. PDSCH (or PUSCH) transmitted in time units larger than the minislot may be referred to as PDSCH (or PUSCH) mapping type A. The PDSCH (or PUSCH) transmitted using the minislot may be referred to as PDSCH (or PUSCH) mapping type B.

The wireless frame, subframe, slot, minislot and symbol all represent the time unit when transmitting a signal. The radio frame, subframe, slot, minislot and symbol may have different names corresponding to each.

For example, one subframe may be referred to as a transmission time interval (TTI), a plurality of consecutive subframes may be referred to as TTI, and one slot or one minislot may be referred to as TTI. That is, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (eg, 1-13 symbols), or a period longer than 1ms. It may be. The unit representing TTI may be called a slot, a mini slot, or the like instead of a subframe.

Here, TTI refers to, for example, the minimum time unit of scheduling in wireless communication. For example, in an LTE system, a base station schedules each user terminal to allocate radio resources (frequency bandwidth that can be used in each user terminal, transmission power, etc.) in TTI units. The definition of TTI is not limited to this.

The TTI may be a transmission time unit such as a channel-encoded data packet (transport block), a code block, or a code word, or may be a processing unit such as scheduling or link adaptation. When a TTI is given, the time interval (for example, the number of symbols) to which the transport block, code block, code word, etc. are actually mapped may be shorter than the TTI.

When one slot or one mini slot is called TTI, one or more TTIs (that is, one or more slots or one or more mini slots) may be the minimum time unit for scheduling. Further, the number of slots (number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.

A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel.8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, or the like. TTIs shorter than normal TTIs may also be referred to as shortened TTIs, short TTIs, partial TTIs (partial or fractional TTIs), shortened subframes, short subframes, minislots, subslots, slots, and the like.

The long TTI (for example, normal TTI, subframe, etc.) may be read as a TTI having a time length of more than 1 ms, and the short TTI (for example, shortened TTI, etc.) may be read as less than the TTI length of the long TTI and 1 ms. It may be read as a TTI having the above TTI length.

The resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or a plurality of continuous subcarriers in the frequency domain. The number of subcarriers contained in RB may be the same regardless of numerology, and may be, for example, 12. The number of subcarriers contained in the RB may be determined based on numerology.

Further, the time domain of RB may include one or more symbols, and may have a length of 1 slot, 1 mini slot, 1 subframe, or 1 TTI. Each 1TTI, 1 subframe, etc. may be composed of one or a plurality of resource blocks.

One or more RBs include a physical resource block (Physical RB: PRB), a sub-carrier group (Sub-Carrier Group: SCG), a resource element group (Resource Element Group: REG), a PRB pair, an RB pair, and the like. May be called.

Further, the resource block may be composed of one or a plurality of resource elements (ResourceElement: RE). For example, 1RE may be a radio resource area of 1 subcarrier and 1 symbol.

Bandwidth Part (BWP) (which may also be called partial bandwidth, etc.) may represent a subset of consecutive common resource blocks (RBs) for a neurology in a carrier. Good. Here, the common RB may be specified by the index of the RB with respect to the common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

BWP may include BWP for UL (UL BWP) and BWP for DL (DL BWP). One or more BWPs may be set in one carrier for the UE.

At least one of the configured BWPs may be active, and the UE may not expect to send or receive a given signal / channel outside the active BWP. In addition, "cell", "carrier" and the like in this disclosure may be read as "BWP".

The above-mentioned structures such as wireless frames, subframes, slots, mini slots and symbols are merely examples. For example, the number of subframes contained in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, included in RB. The number of subcarriers, the number of symbols in the TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.

The terms "connected", "coupled", or any variation thereof, mean any direct or indirect connection or connection between two or more elements, and each other. It can include the presence of one or more intermediate elements between two "connected" or "combined" elements. The connection or connection between the elements may be physical, logical, or a combination thereof. For example, "connection" may be read as "access". As used in the present disclosure, the two elements use at least one of one or more wires, cables and printed electrical connections, and, as some non-limiting and non-comprehensive examples, the radio frequency domain. , Electromagnetic energies with wavelengths in the microwave and light (both visible and invisible) regions, etc., can be considered to be "connected" or "coupled" to each other.

The reference signal can also be abbreviated as Reference Signal (RS) and may be called a pilot (Pilot) depending on the applicable standard.

The phrase "based on" as used in this disclosure does not mean "based on" unless otherwise stated. In other words, the statement "based on" means both "based only" and "at least based on".

The "means" in the configuration of each of the above devices may be replaced with a "part", a "circuit", a "device", or the like.

Any reference to elements using designations such as "first", "second" as used in this disclosure does not generally limit the quantity or order of those elements. These designations can be used in the present disclosure as a convenient way to distinguish between two or more elements. Thus, references to the first and second elements do not mean that only two elements can be adopted there, or that the first element must somehow precede the second element.

When "include", "including" and variations thereof are used in the present disclosure, these terms are as comprehensive as the term "comprising". Is intended. Moreover, the term "or" used in the present disclosure is intended not to be an exclusive OR.

In the present disclosure, if articles are added by translation, for example, a, an and the in English, the disclosure may include that the nouns following these articles are plural.

The terms "determining" and "determining" used in this disclosure may include a wide variety of actions. "Judgment" and "decision" are, for example, judgment (judging), calculation (calculating), calculation (computing), processing (processing), derivation (deriving), investigation (investigating), search (looking up, search, inquiry). (For example, searching in a table, database or another data structure), ascertaining may be regarded as "judgment" or "decision". Also, "judgment" and "decision" are receiving (for example, receiving information), transmitting (for example, transmitting information), input (input), output (output), and access. (Accessing) (for example, accessing data in memory) may be regarded as "judgment" or "decision". In addition, "judgment" and "decision" mean that the things such as solving, selecting, choosing, establishing, and comparing are regarded as "judgment" and "decision". Can include. That is, "judgment" and "decision" may include considering some action as "judgment" and "decision". Further, "judgment (decision)" may be read as "assuming", "expecting", "considering" and the like.

In the present disclosure, the term "A and B are different" may mean "A and B are different from each other". The term may mean that "A and B are different from C". Terms such as "separate" and "combined" may be interpreted in the same way as "different".

Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure may be implemented as an amendment or modification without departing from the purpose and scope of the present disclosure, which is determined by the description of the scope of claims. Therefore, the description of the present disclosure is for the purpose of exemplary explanation and does not have any limiting meaning to the present disclosure.

10 Wireless communication system 20 E-UTRAN
30 NG RAN
50 remote controller 60 device 100A eNB
100B gNB
110 Wireless transmitter 120 Wireless receiver 130 UE capability management unit 140 Node-to-node message processing unit 150 Control unit 160 Wireless transmitter 170 Wireless receiver 180 Node-to-node message processing unit 190 Control unit 200 UE
210 Wireless transmitter 220 Wireless receiver 230 ROHC processing unit 240 EHC processing unit 250 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus

Claims (4)

A control unit that executes the first header compression according to the first header compression protocol and the second header compression according to the second header compression protocol, and
A terminal including a transmission unit that transmits first session information indicating the number of first sessions to which the first header compression can be applied to a network. When the first header compression and the second header compression are executed at the same time, the transmission unit requests to transmit the second session information indicating the number of second sessions to which the second header compression can be applied to the network. Item 1. The terminal according to item 1. A control unit that controls communication with another radio base station connected to a terminal that executes the first header compression according to the first header compression protocol and the second header compression according to the second header compression protocol.
A radio base station including a transmission unit that transmits first session information indicating the number of first sessions to which the first header compression according to the first header compression protocol can be applied in the terminal to the other radio base station. The transmitting unit provides second session information indicating the number of second sessions to which the second header compression can be applied when the terminal executes the first header compression and the second header compression at the same time. The radio base station according to claim 3, which is transmitted to the radio base station of.

Images